Positioning Rel-17

RAN1#101-e

8.2 Study on NR Positioning Enhancements

Please refer to RP-193237 for detailed scope of the SI

R1-2005095 Session notes for 8.2 (Study on NR positioning enhancements) Ad-Hoc Chair (Ericsson)

Notes incorporated below.

R1-2003638 Work plan for Study on NR Positioning Enhancements CATT, Intel, Ericsson

R1-2004649 TR skeleton for TR 38.857: Study on NR Positioning Enhancements Ericsson

R1-2004701 FL Summary for NR Positioning Enhancements Moderator (CATT)

Further to initial conference call:

[101-e-NR-Pos-Enh] – Da Ren (CATT)

Email discussion/approval on Rel-17 NR Positioning Enhancements prioritizing evaluation scenarios and assumptions until 6/4

R1-2004868 FL Summary#2 of Study on NR Positioning Enhancements Moderator (CATT)

Update on 6/7: post e-meeting additional email discussion/approval

[101-e-Post-NR-Pos-Enh] – Ren Da (CATT)

Email discussion/approval prioritizing remaining evaluation assumptions till 6/17

Focusing on high priority proposals first, target 6/11 for early approvals
Followed by medium priority/low priority proposals

8.2.1 Additional scenarios for evaluation

R1-2003639 Summary of discussion on IIoT Scenarios for NR Positioning Enhancements CATT

R1-2003906 Additional scenarios for evaluation Samsung

· Proposal 1: The target positioning requirements should be defined following the IIoT use cases with positioning level 1, 2 and 8 in Table 8.1.7 in TR 22.804.

· Proposal 2: InF-SH should be considered as baseline scenario for evaluation.

· Proposal 3: Positioning accuracy including relative positioing accuracy should be the baseline metric for evaluation. Latency, signalling overhead and UE power consumption can be considered additionally as metrics for evaluation in an analytical manner.

· Proposal 4: Evaluation parameters in the below table can be a starting point with addtional consideration to include IIoT channel model in TR 38.901.

Decision: The document is noted.

R1-2003963 Discussions on IIoT scenarios for positioning CMCC

Proposal 1: The IIoT logistics and warehousing use case should be considered with the following positioning requirements:

· Horizontal positioning accuracy: < 0.1m (for 90% UEs);

· Vertical positioning accuracy: < 0.2m (for 90% UEs);

· End-to-end latency: < 10ms

Proposal 2: The InF-DH scenario should be defined as the evaluation scenario.

Proposal 3: The common InF scenario parameters can be defined based on that for the corresponding scenarios given in Table 7.8-7 in TR 38.901.

Proposal 4: Regarding the UE distribution in the common InF-DH scenario parameter, the UE height should be uniformly distributed within a pre-defined range, e.g., UE antenna height ~U([0.5]m~[9]m).

Decision: The document is noted.

R1-2004141 Discussion on additional scenarios for evaluation LG Electronics

· Proposal 1: For performance requirement of IIOT use case in Rel.17:

o Selecting one or multiple scenarios in appendix #1 for target IIOT scenario(s), and then define the appropriate target positioning requirements.

o Analyzing based on CDF of horizontal and/or vertical positioning accuracy should be used.

o Only the perspective of physical layer such as preparation time, BWP switching, RS preparation time, BWP switching, RS Rx/Tx processing time, etc. should be discussed for aspect of positioning latency.

o The issues related with power consumption, scalability/capacity and network efficiency could be evaluated analytically.

· Proposal 2: For IIOT InF scenarios:

o If one scenario is required, InF-SH scenario is appropriate and then InF-DH scenario should be considered in the next priority.

· Proposal 3: For parameters in IIOT InF scenarios:

o Common parameters (in Table 4-1 [R1-2003639]): selecting one of bandwidths in each carrier (FR1 and FR2) would be preferred.

o Scenario parameters (in Table 4-3 [R1-2003639]): fixed value of height both UE and gNB should be applied for each evaluation.

· Proposal 4: For DL PRS and UL SRS configuration:

o It is not necessary to consider additional parameters. But, detail values of several parameters would be adjusted according to further discussion.

Decision: The document is noted.

R1-2004190 Considerations on Scenarios for Evaluations of IIoT Positioning Sony

· Observation 1: There are quite substantial performance requirements gap between NR positioning rel-16 requirements and positioning requirements of the identified 5G use-cases in bothTable 1 (TR 22.261) and Table 2 (TR 22.804).

· Proposal 1: RAN1 needs to define intermediate positioning requirements derived from Table 1 and Table 2.

· Proposal 2: The requirement parameters to be used for the evaluation of NR positioning enhancements are:

o Horizontal accuracy and its corresponding minimum cumulative distributive function (cdf) target.

o Vertical accuracy and its corresponding minimum cdf target.

o Latency

· Proposal 3: Positioning requirements as follows: Horizontal positioning error < [1]m for [FFS] % of UEs, Vertical positioning error < [1]m for [FFS] % of UEs, and End to end latency < [1]s.

· Proposal 4: Prioritize RAT-dependent techniques during NR Rel-17 study item.

· Proposal 5: Select InF-DL and InF-DH scenarios for the evaluation of IIoT positioning in Rel-17.

· Proposal 6: Use the scenarios parameters in TR 38.901 as the baseline parameters. Additional parameter modification, such as number of BS, multi-beam operation can be further studied.

Decision: The document is noted.

R1-2003284 IIOT Scenarios for Positioning Futurewei

R1-2003295 Discussion on scenarios and evaluation methodology for Rel-17 positioning Huawei, HiSilicon

R1-2003427 Discussion on additional scenarios for NR positioning evaluation vivo

R1-2003479 Additional scenarios for evaluation on positioning enhancements ZTE

R1-2003640 IIoT use cases and scenarios for evaluation of NR Positioning Enhancements CATT

R1-2003719 Additional scenarios for evaluation of NR positioning Nokia, Nokia Shanghai Bell

R1-2003767 I-IoT scenarios for NR positioning evaluations Intel Corporation

R1-2004063 Discussion on Scenarios for Evaluation OPPO

R1-2004199 View on scenarios and evaluation parameters for Rel 17 positioning enhancement CEWiT

R1-2004490 Considerations on Additional Scenarios for Evaluation Qualcomm Incorporated

R1-2004517 Additional scenarios and considerations for NR positioning Fraunhofer IIS, Fraunhofer HHI

R1-2004650 Additional scenarios for performance evaluations Ericsson

Decision: As per email decision posted on June 4^th,

Agreement:

· InF-SH and InF-DH models in TR 38.901 are adopted as the baseline scenarios for defining the channel models, parameters and modelling techniques for performance evaluations in the Rel. 17 positioning enhancements at least for IIoT use cases

· Note: Modifications to parameters in the InF-DH models will be discussed separately.

· Note: Target performance and performance gap identification will be discussed separately.

· Note: Individual companies may consider additional InF models in TR 38.901 as complementary evaluation scenarios in their simulation investigation and the evaluation results can be considered to be captured in the TR 38.857.

· Note: Target positioning requirements may not necessarily be reached for all scenarios.

Agreement (Proposal 4.1-1, Revision #2, in Section 4.1 of R1-2004868):

· Adopt the parameters defined in Table below as the baseline parameters for all scenarios in the evaluation of the positioning performance in Rel-17.

· Note: Individual companies may consider additional parameter values or different parameter settings in their simulation investigation

· Note: Optional scenarios and assumptions will be discussed separately and can be included

Table: Common scenario parameters applicable for all scenarios

	FR1 Specific Values	FR2 Specific Values
Carrier frequency, GHz	3.5GHz	28GHz
Bandwidth, MHz	100MHz	400MHz
Subcarrier spacing, kHz	30kHz for 100MHz	120kHz
gNB model parameters
gNB noise figure, dB	5dB	7dB
UE model parameters
UE noise figure, dB	9dB – Note 1	13dB – Note 1
UE max. TX power, dBm	23dBm – Note 1	23dBm – Note 1 EIRP should not exceed 43 dBm.
UE antenna configuration	Panel model 1 – Note 1 Mg = 1, Ng = 1, P = 2, dH = 0.5λ, (M, N, P, Mg, Ng) = (1, 2, 2, 1, 1)	Baseline: Multi-panel Configuration 1 and Panel Configuration a – Note 1 - Multi-panel Configuration 1: (Mg, Ng) = (1, 2); Θmg,ng=90°; Ω0,1=Ω0,0+180°; (dg,H, dg,V)=(0,0) - Panel Configuration a: - Each antenna array has shape dH=dV=0.5λ - Config a: (M, N, P) = (2, 4, 2), - the polarization angles are 0° and 90° - The antenna elements of the same polarization of the same panel is virtualized into one TXRU - Optional: FFS: ~~Provided by company~~
UE antenna radiation pattern	Omni, 0dBi	Antenna model according to Table 6.1.1-2 in TR 38.855
PHY/link level abstraction	Explicit simulation of all links, individual parameters estimation is applied. Companies to provide description of applied algorithms for estimation of signal location parameters.
Network synchronization	The network synchronization error, per UE dropping, is defined as a truncated Gaussian distribution of (T1 ns) rms values between an eNB and a timing reference source which is assumed to have perfect timing, subject to a largest timing difference of T2 ns, where T2 = 2*T1 – That is, the range of timing errors is [-T2, T2] – T1: 0ns (perfectly synchronized), 50ns (Optional)
Note 1: According to 3GPP TR 38.802 Note 2: According to 3GPP TR 38.901

R1-2004961 FL Summary#3 of Study on NR Positioning Enhancements Moderator (CATT)

Decision: As per email decision posted on June 5^th,

Agreement:

Optional: The following UE antenna configuration can be considered

· 4 UE panels:

o The antenna elements of the same polarization of the same panel is virtualized into one TXRU

· FFS: Other details

Agreement:

Absolute-time-of arrival model defined in TR 38.901 without modification is considered in the evaluation of all scenarios.

Agreement:

Blockage model is not considered in the evaluation of all scenarios

Agreement: (Proposal 5.1-4, Revision 3, in Section 5.1 of R1-2004961)

· Adopt the parameters defined in the Table below as the baseline parameters for all InF scenarios in the evaluation of positioning performance in Rel-17.

· Note: Individual companies may consider additional parameter values or different parameter settings in their simulation investigation

Table: Parameters common to InF scenario(s)

		FR1 Specific Values		FR2 Specific Values	Comments (to each of the parameter)
Channel model		InF-SH, InF-DH ~~FFS: InF-SL, InF-DL, InF-HH~~		InF-SH, InF-DH ~~FFS: InF-SL, InF-DL, InF-HH~~
Layout	Hall size	InF-SH: (baseline) 300x150 m (optional) 120x60 m InF-DH: (baseline) 120x60 m (optional) 300x150 m
	BS locations	18 BSs on a square lattice with spacing D, located D/2 from the walls. - for the small hall (L=120m x W=60m): D=20m - for the big hall (L=300m x W=150m): D=50m
	Room height	10m
Total gNB TX power, dBm		24dBm	24dBm EIRP should not exceed 58 dBm
gNB antenna configuration		(M, N, P, Mg, Ng) = (4, 4, 2, 1, 1), dH=dV=0.5λ – Note 1	(M, N, P, Mg, Ng) = (4, 8, 2, 1, 1), dH=dV=0.5λ – Note 1 One TXRU per polarization per panel is assumed
gNB antenna radiation pattern		Single sector – Note 1	3-sector antenna configuration – Note 1
Peneteration loss		0dB
Number of floors		1
UE horizontal drop procedure		Uniformly distributed over the horizontal evaluation area for obtaining the CDF values for positioning accuracy, The evaluation area should be at least the convex hull of the horizontal BS deployment. It can also be the whole hall area if the CDF values for positioning accuracy is obtained from whole hall area.
UE antenna height		Baseline: 1.5m (Optional): FFS
UE mobility		3km/h (Optional): FFS
Min gNB-UE distance (2D), m		0m
gNB antenna height		Baseline: 8m (Optional): FFS
Clutter parameters: {density , height ,size }		Low clutter density: {20%, 2m, 10m} High clutter density: See Proposal 5.1-7
Note 1: According to Table A.2.1-7 in 3GPP TR 38.802

Agreement:

· Optional: For evaluating vertical positioning performance, UE antenna height can be uniformly distributed within [0.5, X2]m, where X2 = 2m for InF-SH and X2= for InF-DH defined in TR 38.901.

Agreement:

Clutter parameters {density , height ,size } for high clutter density are set as follows:

· (Baseline): {40%, 2m, 2m} for fixed UE antenna height and gNB antenna height

· (Optional): {40%, 3m, 5m}

· (Optional): {60%, 6m, 2m}

Agreement:

It will be left to companies to define the configurations for DL PRS and UL SRS for the evaluation of positioning performance.

Note: Configurations of DL PRS and UL SRS supported by Rel-16 specifications are used for evaluation of the achievable performance based on Rel-16 positioning technologies.

Agreement:

CDFs of positioning errors are used as performance metrics in NR positioning evaluation with at least the following percentiles 50%, 67%, 80%, 90%.

Note: In addition to overall positioning accuracy performance, companies are encouraged to report the estimation accuracy of UE/gNB measurements (e.g., RSTD) for performance comparison.

Agreement:

For TR 38.857, the template used in TR 38.855 for the inclusion of simulation results is reused. In addition, the following parameters should be provided for each scenario together with the simulation results.

Parameter	[Source 1, scenario, FRx]
Channel model (baseline, otherwise state any modifications)
Reference Signal Physical Structure and Resource Allocation (RE pattern)
Reference signal (type of sequence, number of ports, …)
Number of sites
Number of symbols used per slot per positioning estimate
Number of slots per positioning estimate
Power-boosting level
Uplink power control (applied/not applied)
interference modelling (ideal muting, or other)
Description of Measurement Algorithm (e.g. super resolution, interference cancellation, ….)
Description of positioning technique / applied positioning algorithm (e.g. Least square, taylor series, etc)
Network synchronization assumptions
Beam-related assumption (beam sweeping / alignment assumptions at the tx and rx sides)
Precoding assumptions (codebook, nrof antenna elements used, etc)
Additional notes, if any

Agreement:

CDF values for positioning accuracy for IIoT scenarios are derived based on:

Case 1 (Required): The UEs inside the convex hull of the horizontal BS deployment area.
Case 2 (Optional): All the UEs

R1-2005049 FL Summary#4 of Study on NR Positioning Enhancements Moderator (CATT)

Decision: As per email decision posted on June 6^th,

Agreement:

Optional: For evaluating vertical positioning performance, gNB antenna height can also be set to two fixed heights, which is either {4, 8} m, or {max(4,), 8}.

Agreement:

· Network efficiency and UE efficiency can be evaluated at least in an analytical manner.

· FFS: the definition of efficiency metric (e.g., the positioning performance (accuracy, latency) vs. PRS/SRS resource utilization etc.)

· Note: It will be up to each company on whether to use other methods (e.g., numerical simulation) for the evaluation.

8.2.2 Evaluation of achievable positioning accuracy and latency

R1-2003296 Performance evaluation for Rel-17 positioning Huawei, HiSilicon

· Observation 1: Bandwidth is still an important factor affecting positioning accuracy.

o When the bandwidth is doubled, the corresponding positioning error is reduced by almost half.

· Observation 2: The beamforming of the transmitted signal can further improve the positioning accuracy, but the gain is limited for non-MUSIC algorithm (case 1, case 5, and case 9).

· Observation 3: Super resolution algorithms (e.g., MUSIC) can greatly improve positioning accuracy at least for beamformed procoder (case 5 and case 6, case 9 and case 10).

· Observation 4: Rel-16 DL-TDOA with 100MHz@FR1 can achieve 0.58m@90% in case10. The performance gap to the target performance [0.2-0.5m]@90% is derived accordingly.

Decision: The document is noted.

R1-2003428 Evaluation of achievable accuracy and latency for NR positioning enhancements vivo

Proposal 1: The vertical positioning target for RAT-dependent techniques shouldn’t be the same as the horizontal positioning.

Proposal 2: The vertical positioning evaluation with RAT-dependent techniques can be put on a lower priority.

Proposal 3: UE location measurement time needs to be evaluated and reduced.

Proposal 4: The overhead for low latency positioning needs to be evaluated.

Observation 1:

· Sub meter and cm level positioning accuracy are required for general commercial and IIoT scenarios.

· The target latency less than 100ms and even 10ms are required for general commercial and IIoT scenarios.

Observation 2: For DL-TDOA positioning，the exemplary performance targets [0.2m 80%] can be achieved in InF-HH and InF-SH.

Observation 3: For DL-TDOA positioning，the exemplary performance targets [0.2m 80%] cannot be met In InF-SL, InF-DH and InF-DL scenarios for both FR1 and FR2.

Observation 4: For UL- TDOA positioning，the exemplary performance targets [0.2m 80%] can be achieved in InF-HH and InF-SH.

Observation 5: For UL- TDOA positioning，the exemplary performance targets [0.2m 80%] cannot be met In InF-SL, InF-DH and InF-DL scenarios for both FR1 and FR2.

Observation 6: For UL-AOA positioning，the exemplary performance targets [0.2m 80%] cannot be achieved in 5 InF scenarios.

Observation 7: For UL AOA\ZOA joint positioning, the vertical exemplary performance targets [0.2m 80%] can’t be achieved in 5 InF scenarios.

Observation 8: For RTT positioning，the exemplary performance targets [0.2m 80%] can be achieved in InF-HH and InF-SH.

Observation 9: For RTT positioning，the exemplary performance targets [0.2m 80%] cannot be met In InF-DL, InF-DH and InF-DL scenarios for both FR1 and FR2.

Observation 10: RTT positioning is not sensitive to synchronization error between network nodes.

Observation 11: Even with no excess delay ，the exemplary performance targets [0.2m 80%] cannot be achieved In InF-DH scenarios for both FR1 and FR2.

Observation 12: The upper bound of positioning in DH scenarios is [0.75m 80%] by R16 technique.

Observation 13: Positioning accuracy performance can be improved with the delay elimination algorithm in DH scenarios, but the result is still far away from the target accuracy [0.2m 80%].

Observation 14: The evaluation result of latency exceeds the target latency, even if the target is 100ms.

Observation 15: UE location measurement time is the majority part of total positioning latency. Current Rel-16 UE location measurement time itself exceeds the target latency of 100 ms.

Observation 16: The longer period of positioning reference signal, the greater the delay time.

Observation 17: 10ms latency target can’t be satisfied with Rel-16 positioning.

Observation 18: 100ms latency target can be satisfied with small periodicity and heavy load of PRS.

Decision: The document is noted.

R1-2003480 Evaluation results of additional scenarios for positioning ZTE

· Observation 1: The sub-meter(<1m) horizontal commercial requirement for at least 80% of UEs can be met only in InF-SH scenario with perfect synchronization with 400 MHz Bandwidth.

· Observation 2: The positioning accuracy from high to low are InF-SH，InF-SL, InF-DH, InF-DL. The positioning accuracy of dense clutter scenarios (InF-DL, InF-DH) are much worse than sparse clutter scenarios (InF-SL, InF-SH).

· Observation 3: The simulation cases with synchronization error lead to significant performance degradation. For ex.,

o 9 m performance loss in InF-SH scenario compared with perfect synchronization with 100 MHz Bandwidth for at least 80% UEs.

o 7 m performance loss in InF-SH scenario compared with perfect synchronization with 400 MHz Bandwidth for at least 80% UEs.

· Observation 4: The positioning accuracy increases with LOS probability. DL-TDOA method for InF-DH scenario can meet sub-meter(<1m) horizontal commercial requirement only when the LOS probability is comparable to InH scenario.

· Observation 5: The fingerprint based method can get initial positioning which is more accurate than DL-TDOA method for InF-DH scenario with the configurations according to Table 7.8-7 in TS 38.855.

Decision: The document is noted.

R1-2003547 Evaluation of Rel-16 Positioning for IIOT Futurewei

R1-2003641 Discussion of evaluation of NR positioning performance CATT

R1-2003668 Evaluation of DL-AoD technique under IIOT scenario MediaTek Inc.

R1-2003720 Views on evaluation of achievable positioning accuracy and latency Nokia, Nokia Shanghai Bell

R1-2004725 Initial analysis of NR positioning performance in I-IoT scenarios Intel Corporation (rev of R1-2003768)

R1-2003907 Evaluation of achievable positioning accuracy and latency Samsung

R1-2003964 Discussions on evaluation methodology of latency CMCC

R1-2004064 Evaluation of NR positioning in IIOT scenario OPPO

R1-2004191 Considerations on Evaluation of Positioning Accuracy and Latency Sony

R1-2004491 Initial Evaluation of achievable Positioning Accuracy & Latency Qualcomm Incorporated

R1-2004518 Evaluation of positioning enhancements Fraunhofer IIS, Fraunhofer HHI

R1-2004651 Evaluation of Achievable Positioning Accuracy and Latency Ericsson

8.2.3 Potential positioning enhancements

Note: a placeholder, no treatment during the e-Meeting

R1-2003285 IIOT Positioning techniques Consideration Futurewei

R1-2003297 Discussion of positioning enhancement Huawei, HiSilicon

R1-2003429 Discussion on potential positioning enhancements vivo

R1-2003481 Potential NR positioning enhancements for Rel.17 ZTE

R1-2003642 Discussion of NR positioning enhancements CATT

R1-2003669 Views on Positioning enhancement for Rel-17 MediaTek Inc.

R1-2003701 Potential positioning enhancements BUPT

R1-2003721 Initial views on potential positioning enhancements Nokia, Nokia Shanghai Bell

R1-2003769 Potential NR positioning enhancements Intel Corporation

R1-2003908 Potential positioning enhancements Samsung

R1-2003965 Discussions on potential positioning enhancements CMCC

R1-2003977 Positioning enhancements for RRC IDLE and RRC INACTIVE state UE Beijing Xiaomi Mobile Software

R1-2003988 Discussion on potential positioning enhancements Spreadtrum Communications

R1-2004065 Discussions on NR Positioning Enhancements OPPO

R1-2004142 Discussion on potential positioning enhancements LG Electronics

R1-2004175 On Potential Rel-17 NR Positioning Enhancements Lenovo, Motorola Mobility

R1-2004192 Potential Techniques for Positioning Enhancements Sony

R1-2004420 Discussion on potential techniques for NR Positioning Enhancements NTT DOCOMO, INC.

R1-2004492 Initial thoughts on Potential Positioning Enhancements Qualcomm Incorporated

R1-2004652 Potential enhancements for NR positioning in release 17 Ericsson

8.2.44 Other

R1-2003430 Discussion on power consumption model for NR positioning enhancements vivo

R1-2003643 Discussion of NLOS IIoT channel modelling for NR positioning enhancement CATT

R1-2003909 Uplink Transmission Based Relative Positioning Samsung

R1-2004066 Analysis of NR Positioning for IIOT Scenarios OPPO

R1-2004609 Discussion of sidelink positioning Huawei, HiSilicon

R1-2004653 PRS separation based on Cyclic shifts Ericsson

RAN1#102-e

8.5 Study on NR Positioning Enhancements

Please refer to RP-200928 for detailed scope of the SI

R1-2007386 Session notes for 8.5 (Study on NR Positioning Enhancements) Ad-Hoc Chair (Ericsson)

R1-2006913 TP for additional scenarios and channel models in TR 38.857 Ericsson

8.5.1 Additional scenarios for evaluation

R1-2005251 Additional consideration on evaluation methodology Huawei, HiSilicon

· Proposal 1: Adopt the following modeling of the impact on DL TOA and UL TOA from gNB/UE Rx and Tx calibration error

· Proposal 2: Consider to adopt the following simplified physical layer latency representation

· Proposal 3: Adopt the following parameter for PRS RRM power evaluation

N: Number of TRPs for intra-frequency measurement & search	Synchronous case
N: Number of TRPs for intra-frequency measurement & search	FR1	FR2
N=8	200	320

· Proposal 4: Adopt the calibration configuration with FTP traffic model for positioning based on PRS and SRS.

o Both configuration with no CDRX and configuration with CDRX as agreed in the calibration configuration are evaluated.

o For configuration with CDRX, PRS may or may be received in on-duration and SRS should always be configured in on-duration.

· Proposal 5: Consider to adopt the resource utilization of PRS and SRS as the metric for network efficiency.

· Proposal 6: Consider to adopt additional (M,N,P,Mg,Ng) = (1,4,1,1,1) antenna configuration for gNB.

· Proposal 7: Consider evaluating positioning with explicit ground reflection and wall reflection.

Decision: The document is noted.

R1-2005710 Remaining issues on additional scenarios for evaluation of NR Positioning Enhancements CATT

· Proposal 1: We prefer the following numbers for Rel-17 target positioning requirements:

o In Rel-17 target positioning requirements for commercial use cases are defined as follows:

§ Horizontal position accuracy (< 1 m) for 90%of UEs

§ Vertical position accuracy (<3m) for 90% of UEs

§ End-to-end latency for position estimation of UE (<100 ms)

§ Physical layer latency for position estimation of UE (<10 ms)

o In Rel-17 target positioning requirements for IIoT use cases are defined as follows:

§ Horizontal position accuracy (< X m) for 90%of UEs

· X = 0.2m

§ Vertical position accuracy (< Y m) for 90% of UEs

· Y = 1m

§ End-to-end latency for position estimation of UE (<100ms)

§ Physical layer latency for position estimation of UE (< 10ms).

· Proposal 2: Reusing the absolute-time-of arrival model for InF scenarios defined in TR 38.901 to the evaluation of IOO scenario. The values of parameters and for generation of the excess delay in NLOS for IOO scenario are shown in the below Table:

Scenario		IOO
		-7.5
		0.4

· Proposal 3: A common mobility model for the movement of UE should be considered with the following details of the mobility model as the starting point:

o UE mobility can be optionally considered in evaluation with the following details.

§ Spatial consistency should be considered according to TR 38.901 (Section 7.6.3)

§ Track mode: linear track with fixed path trajectory

§ Velocity & acceleration:

· Option 1: constant speed 30km/h, zero acceleration.

· Option 2: initial constant acceleration period + constant speed 30Km/h period

§ Position update rate: the time interval between two position update of a track >1ms

Decision: The document is noted.

R1-2006427 Additional scenarios for evaluation of NR positioning Nokia, Nokia Shanghai Bell

· Proposal 1: Approximate absolute time of arrival models for UMi, UMa, and IOO scenarios are applicable however, some parameters of the absolute time of arrival models are left to individual companies.

o One way is to add an additional delay with absolute LOS delay to LOS and NLOS fast fading channels to (7.5-27) and (7.5-30) respectively in TR38.901. The excess delay in NLOS can be ignored for UMi, UMa, and IOO for the simplified models or brought by individual companies (i.e., no agreed values).

· Proposal 2: Do not define additional details for the optional UE antenna configuration of 4 UE panels.

· Proposal 3: Do not define the details of the optional mobility model.

· Proposal 4: RAN1 may define the latency study scope, and interested companies can study the latency performance

o As a baseline, the latency of PRS transmission period and transmission occasions (i.e. , ) for one UE’s measurement report to achieve the accuracy requirement can be used.

o Latency of LMF averaging can be considered to achieve the accuracy requirement over multiple UE measurement report occasions. (i.e. , ).

o The time for UE to report the measurements can be considered as well.

· Proposal 5: Interested companies can study positioning performance accuracy over resource allocation/configuration (e.g., comb size, number of symbols, etc) and PRS transmission occasions as PRS/SRS resource utilization.

Decision: The document is noted.

R1-2005283 Remaining Issues on Evaluation Assumptions FUTUREWEI

R1-2005379 Discussion on additional scenarios for NR positioning evaluation vivo

R1-2005462 Evaluation assumptions for NR positioning enhancements ZTE

R1-2005577 Remaining Issues on Scenarios for Evaluation of NR Positioning Sony

R1-2005877 Remaining details on additional scenarios for NR positioning evaluations Intel Corporation

R1-2005990 Discussion on Scenarios for Evaluation OPPO

R1-2006066 Additionnal scenarios for evaluation BUPT

R1-2006148 Additional scenarios for evaluation Samsung

R1-2006214 Remaining issues on target performance requirement of IIoT use case CMCC

R1-2006238 UE mobility model for evaluation InterDigital, Inc.

R1-2006374 Discussion on additional scenarios for evaluation for NR positioning LG Electronics

R1-2006458 Additional scenarios for evaluation Fraunhofer IIS, Fraunhofer HHI

R1-2006808 Considerations on Additional Scenarios for Evaluation Qualcomm Incorporated

R1-2006914 Remaining details on additional scenarios for evaluation Ericsson

[102-e-NR-Pos-Enh-Eval-Addl-Scenarios] – Florent (Ericsson)

Email discussion/approval on additional scenarios for evaluation until 8/20; address any remaining aspects by 8/26

R1-2007103 FL summary for additional scenarios for evaluation of NR positioning enhancements Moderator (Ericsson)

R1-2007209 FL summary#2 for additional scenarios for evaluation of NR positioning enhancements Moderator (Ericsson)

R1-2007285 FL summary#3 for additional scenarios for evaluation of NR positioning enhancements Moderator (Ericsson)

R1-2007367 FL summary#4 for additional scenarios for evaluation of NR positioning enhancements Moderator (Ericsson)

Agreement:

Physical Layer Latency Start and End times are defined as follows:

Method	Start	End
UE assisted DL-only & DL-ECID & Multi-RTT	Transmission of the PDSCH from the gNB carrying the LPP Request Location Information message	Successful decoding of the PUSCH carrying the LPP Provide Location Information message
UL-only method & UL ECID & Multi-RTT	Reception by the gNB of the NRPPa measurement request message	The transmission by the gNB of the NRPPa measurement response message
UE-based	Transmission of the PDSCH from the gNB carrying the LPP Request Location Information if applicable, otherwise, · Alt. 1: transmission of the PUSCH carrying the MG Request from the UE. · Alt. 2: Transmission of the PDSCH from the gNB carrying the LPP message containing the assistance data · Alt. 3: Start of the Reception of DL PRS Note: Suggest to downselect this at the next meeting. Note: The high layers latency components may be subject to adjustment for different alternatives.	Successful decoding of the PUSCH at gNB carrying the LPP Provide Location Information message if applicable, otherwise Calculation of Location Estimate at the UE

Conclusion:

RAN1 will not define additional optional values for UE and gNB antenna heights for evaluations.

Conclusion:

RAN1 will not define additional details for the optional UE antenna configuration of 4 UE panels for evaluations.

Conclusion:

For power consumption evaluation, it is up to each company to detail their methodology (including power model) for evaluation.

Agreement:

Apply the timing errors as follows:

· For each UE drop,

o For each panel (in case of multiple panels)

§ Draw a random sample for the Tx error according to [-2*Y,2*Y] and another random sample for the Rx error according to the same [-2*Y,2*Y] distribution.

· For each gNB

o For each panel (in case of multiple panels)

§ Draw a random sample for the Tx error according to [-2*X,2*X] and another random sample for the Rx error according to the same [-2*X,2*X] distribution.

· Any additional Time varying aspects of the timing errors, if simulated, can be left up to each company to report.

· For UE evaluation assumptions in FR2, it is assumed that the UE can receive or transmit at most from one panel at a time with a panel activation delay of 0ms.

Conclusion:

For UE mobility, the details of the optional mobility model are left to companies.

Agreement:

PRS/SRS resource utilization is the metric used to evaluate network efficiency

· FFS: what is included in resource utilization, e.g. PRS/SRS/MG configurations, beam sweeping assumptions

Agreement:

For the absolute time of arrival modelling in IOO, UMa, Umi, companies may provide the details of their model, if any.

8.5.2 Evaluation of achievable positioning accuracy and latency

R1-2005878 NR Positioning Performance in I-IoT Scenarios Intel Corporation

· Observation 1:

o Performance of the Rel.16 positioning techniques highly depends on the measurement data set used in the estimation

o Usage of the LOS links only provides better performance compared to the case when both LOS and NLOS links are utilized

o The required performance can be achieved, if the sufficient amount of the LOS links can be detected and the NLOS links can be discarded based on the LOS/NLOS links classification

· Observation 2: Combination of the Multi-RTT and vertical AoA measurements further improves positioning performance in the InF scenarios

· Observation 3: Usage of the practical LOS/NLOS classification algorithms provides significant improvement in the positioning accuracy and should be considered as an enhancement for Rel.17 positioning techniques

· Observation 4: Provided analysis for average delay latency and resource utilization required for DL/UL positioning procedure shows the benefit of on demand resource allocation for transmission of positioning reference signals

Decision: The document is noted.

R1-2005380 Evaluation of achievable positioning accuracy and latency vivo

· Proposal 1: The requirements should be achieved at least with the baseline parameter assumptions.

· Proposal 2:

o For UE-to-UE case, the End-to-end latency of for a TTFF positioning as below function (1) and (2) for UE-based and UE-assisted respectively.

o For LCS-to-UE case, the End-to-end latency for a TTFF positioning as below function (3).

· Proposal 3

o is the periodicity of PRS

o is up to UE ability and the signal that needs to measure, as usually

o is the periodicity of the measurement gap

o is the time to request the gap

o is the time required by UE to configure gaps; RRC reconfiguration delay

o is the time to report

· Proposal 4: Physical layer latency needs to be reduced in R17.

· Proposal 5: The network efficiency and UE efficiency for low latency positioning needs to be enhanced.

· Proposal 6: Support quantitative evaluation of power consumption for positioning in Rel-17.

o The power consumption model as below for PRS measurement should be considered.

For frequency layer i, the power of PRS measurement is represented as:

For Nf frequency layers, the total power is

where

- is total power over slots over which measurements are carried out in frequency layer i

- is the slot average power for PRS measurements in frequency layer i

- is the number of slot over which measurements are carried out

- is the power for measurement gap switching

- is total power for Nf frequency layers

Decision: The document is noted.

R1-2006459 Evaluation of positioning enhancements Fraunhofer IIS, Fraunhofer HHI

· Proposal 1: Technologies allowing a reliable LOS/NLOS detection and/or a ToA quality indicator shall be studied with high priority.

· Proposal 2: Characterize the positioning technologies versus channel parameters. At least the following complementary analysis shall be derived from the simulations:

o ToA estimator accuracy relative to the delay introduced by the AToA model.

o ToA estimator accuracy versus K-factor.

Decision: The document is noted.

R1-2005252 Performance evaluation for Rel-17 positioning Huawei, HiSilicon

R1-2005463 Evaluation results based on NR Rel-16 positioning ZTE

R1-2005578 Initial Views on Evaluation of Positioning Accuracy and Latency Sony

R1-2006970 Discussion of evaluation of NR positioning performance CATT (Revision of R1-2005711)

R1-2005991 Evaluation of NR positioning in IIOT scenario OPPO

R1-2006067 Evaluation of achievable positioning accuracy and latency BUPT

R1-2006149 Evaluation of achievable positioning accuracy and latency Samsung

R1-2006197 Evaluation of DL-TDOA and DL-AoD techniques under IIOT scenarios MediaTek Inc.

R1-2006215 Discussion on achievable positioning latency CMCC

R1-2006239 Discussion on evaluation of latency InterDigital, Inc.

R1-2006323 Considerations for Positioning Latency Evaluation Lenovo, Motorola Mobility

R1-2006375 Discussion on evaluation of achievable positioning accuracy and latency for NR positioning LG Electronics

R1-2006428 Initial results on evaluation of achievable positioning accuracy and latency Nokia, Nokia Shanghai Bell

R1-2006623 Positioning evaluation results for additional commercial use cases CEWiT

R1-2006809 Evaluation of achievable Positioning Accuracy & Latency Qualcomm Incorporated

R1-2006915 Evaluation of achievable positioning accuracy and latency Ericsson

[102-e-NR-Pos-Enh-Eval-Acc-Lat] – Alexey (Intel)

Email discussion/approval on achievable positioning accuracy and latency until 8/20; address any remaining aspects by 8/25

R1-2007105 Feature lead summary #1 for email discussion [102-e-NR-Pos-Enh-Eval-Acc-Lat] Moderator (Intel)

R1-2007262 Feature lead summary #2 for email discussion [102-e-NR-Pos-Enh-Eval-Acc-Lat] Moderator (Intel Corporation)

Agreement:

Text proposal for LS to RAN WG2 and CC SA WG2 and RAN WG3 for analysis of latency of NR positioning protocols defined in Rel.16:

RAN1 evaluates physical layer latency and its potential reduction for NR Rel-17 positioning solutions. In order to evaluate End-To-End latency of NR positioning solutions the input from RAN2 is needed on latency components of NR/NG-RAN/5GC higher layer positioning protocols. RAN1 respectfully asks if RAN2 can provide a list of latency components with corresponding range of values for the existing and any potential enhanced NR positioning solutions, keeping in mind the End-To-End latency described as desired in the study item description (RP-200928)

Agreement:

Physical layer latency for DL only, UL only, DL+UL positioning solutions for UE-based and UE-assisted approaches are separately studied

Agreement:

Capture the following in TR as an observation:

· Performance analysis of baseline I-IoT InF scenarios shows that InF-SH scenario is characterized by high probability of LOS links. In InF-DH the probability of LOS links is reduced substantially while probability of NLOS links is increased accordingly.

Conclusion:

Evaluations show that high probability of NLOS links and propagation delay offset imposed by NLOS links may cause performance degradation of positioning accuracy, that was especially observed in InF-DH scenario
Initial evaluations have also shown that under certain ideal assumptions (e.g., synchronization error, Rx/Tx calibration error) the effective LOS/NLOS classification/detection, outlier determination/rejection techniques may be beneficial to improve NR positioning accuracy
Note: Additional evaluations need to be performed before deciding whether and how to capture the above in the TR

Conclusion:

It is observed that calibration errors of UE/gNB Tx/Rx timing may negatively impact accuracy of timing-based methods of Rel.16 positioning solutions when precise UE positioning is targeted.

Note: Additional evaluations need to be performed before deciding whether and how to capture the above in the TR

Conclusion:

Evaluations show that network synchronization errors may cause accuracy degradation of the DL-TDOA or UL-TDOA Rel-16 positioning solutions

Note: Additional evaluations need to be performed before deciding whether and how to capture the above in the TR

Agreement:

FFS whether Rel.16 granularity of timing measurement reports is enough to avoid degradation in I-IoT scenarios and meet positioning requirements

R1-2007263 Draft LS on Latency of NR Positioning Protocols Intel Corporation

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

R1-2007359 Template for collection of NR positioning evaluation results Moderator (Intel Corporation)

Further revised in R1-2007413 Template for collection of NR positioning evaluation results Moderator (Intel Corporation)

Agreement:

· At least the following information is provided for positioning physical layer latency analysis:

o Source initiating request for positioning measurements/location for a given UE (UE, Network)

o Destination awaiting for positioning measurements/location for a given UE (UE, Network)

o Start and end triggers/events for physical layer latency evaluation

§ For Rel.16 solutions, it is based on specification for each solution

o Initial and final RRC State of positioned UE (RRC IDLE, INACTIVE, CONNECTED) at the start and end time for the physical layer latency evaluation

o Positioning

§ technique (enumeration): (1) DL-TDOA, (2) DL AoD, (3) UL-TDoA, (4) UL-AoA, (5) Multi-RTT, (6) E-CID

§ type: DL, UL, DL+UL

§ mode: UE-based, UE-assisted

o Latency component w/ value range and description, including information on any parallel (simultaneous) components

o Total latency value

· Latency components are recommended to be captured in table and ordered consequently in time starting from the earliest one:

Source [UE, NW]/Destination [UE, NW] Positioning technique [DL-TDOA, E-CID, …], type [DL, UL, DL+UL], mode [UE-A, UE-B], Initial and Final RRC States [IDLE, INACTIVE, CONNECTED]
Latency Component	Value Range	Description of Latency Component
Start trigger
Name of component 1
Name of component 2

Name of last component
End trigger
Total values

Final summary in:

R1-2007358 Feature lead summary #3 for email discussion [102-e-NR-Pos-Enh-Eval-Acc-Lat] Moderator (Intel Corporation)

8.5.3 Potential positioning enhancements

Including positioning techniques, DL/UL positioning reference signals, signalling and procedures for improved accuracy, reduced latency, network efficiency (scalability, RS overhead, etc.), and device efficiency (power consumption, complexity, etc.).

R1-2006194 Views on positioning enhancement for Rel-17 MediaTek Inc.

· Proposal 2-1: The combined technique usage of DL-TDOA and multiple-RTT, or of DL-TDOA and UL-TDOA, can be considered as DL-TDOA enhancement to improve accuracy for both UE-assisted and UE-based mode

· Proposal 2-2: For UE-based DL-TDOA, when combining with multiple-RTT or UL-TDOA, the measurement results at gNB side (gNB RX-TX time difference or UL-RTOA) can provide to the UE to reduce the impact of synchronization error between TRPs

· Proposal 3-1: Study the impact of channel spacing, timing offset and power imbalance among CCs to the positioning performance for intra-band contiguous CA

· Proposal 3-2: Study whether interband CA can be utilized for LOS detection due to different path loss and reflection properties over different bands

· Proposal 3-3: Study whether intra-band non-contiguous CA can be utilized under conventional receiver and under advanced receiver providing super resolution, and the corresponding requirement on timing offset and power imbalance among CCs

· Proposal 5-1: Study RSRP measurement for first-arriving path as accuracy improvement for DL-AoD technique

· Proposal 5-2: RAN1 should take the lead for defining the mapping of a number of RSRP measurements to the angle for DL-AoD enhancement in Rel-17

· Proposal 6-1: Study the feasibility of carrier phase measurement at least starting from Rel-17

· Proposal 8-1: In RRC idle state, consider downlink only measurement with UE based mode for positioning

· Proposal 8-2: In RRC inactive state with UE assisted mode, the network may trigger the UE by paging the UE for a new cause of measurement for positioning, and the UE may respond with the RACH procedure

· Proposal 8-3: The preamble transmission in Msg1/MsgA can also serve the purpose of requesting uplink measurement results as assistance information

· Proposal 8-4: In RRC inactive state with UE based mode, the combined usage of DL-TDOA and UL-TDOA can be considered. Msg4 for 4-step RA and MsgB for 2-step RA with flexible payload size may carry the uplink measurement results to the UE for synchronization error cancellation

· Proposal 9-1: Increase the maximum cyclic shift number for each comb for the staggering SRS structure

· Proposal 9-2: The amount of the phase rotation applied to the REs across symbols with SRS transmission may follow the order of occupied subcarriers

Decision: The document is noted.

R1-2006810 Potential Positioning Enhancements for NR Rel-17 Positioning Qualcomm Incorporated

Proposal 1: At least for the purpose of improved accuracy, additional support and enhancements for UE-based positioning should be supported, including, but not limited to:

· Enhancements of the assistance data (e.g. RTD enhancements, beam-shape assistance data)

· UE-based UL and DL & UL methods (e.g., UE-Based Multi-RTT)

Proposal 2: For the purpose of improved accuracy, study further DL PRS bundling in frequency domain, with considerations for both licensed and unlicensed operation and “PRS stitching” in both intra-band and inter-band scenarios.

Proposal 3: For the purpose of improved accuracy, study further SRS for Positioning bunding in time domain & inter-slot SRS repetition.

Proposal 4: For the purpose of improved accuracy, study further the reporting of additional motion state / kinematics constraints information for both UE-based and UE-assisted including but not limited to:

o Signaling of side information / constraints on potential trajectory, path, velocity, direction of the target device.

Proposal 5: For the purpose of improved accuracy, study further UE and/or network assistance for UE and network calibration (group delay, NW synchronization) :

· Methods/signaling to mitigate the group delay calibration errors in Multi-RTT (e.g., enabling differential Multi-RTT, enabling calibration gaps; other schemes are not precluded)

· Enhancing TDOA and Multi-RTT reporting for assisting with network synchronization

· More explicitly conveying any adjustment for group delay

Proposal 6: NR Rel-17 should target PHY-layer and High-layer enhancements to support a 10 msec End-To-End latency consider the following targets in the respective working groups:

· PHY-layer latency of which includes the time from location request/triggering to successful decoding of the positioning measurement report from the serving gNB

· High-layer latency of ms which includes the time to collect the measurements from the TRPs, perform the position estimation, and transmit the estimate to the external client.

Proposal 7: For the purpose of reduced latency, study further enhancements in MG configuration & triggering (e.g., DCI/MAC-CE triggered MG, Positioning-specific MG, band-specific/layer-specific MG)

Proposal 8: For the purpose of reduced latency, study further Low-layer (e.g., DCI, MAC-CE) triggering of DL/UL PRS transmission and muting.

Proposal 9: For the purpose of reduced latency, study further Enhanced PRS processing capabilities and PRS instances with reduced time-domain foot-print.

Proposal 10: For the purpose of reduced latency, study further Low-layer (e.g., DCI, MAC-CE) triggering of DL/UL Location Information Reporting.

Proposal 11: For the purpose of reduced latency, study further reporting of Positioning information directly to the serving gNB either by RRC, MAC-CE or UCI.

Proposal 12: To support ultra-low latency, study further enhancements to positioning architecture and signalling.

Proposal 13: At least for the purpose of efficiency, study further on-demand PRS and SRS transmissions, including, but not limited to, the following aspects:

· Required signaling & procedures to enable a target device to request/recommend specific PRS configurations (e.g., on-demand ON/OFF switching, bandwidth, TRPs, beam directions), and/or Positioning methods.

Proposal 14: For the purpose of enhanced efficiency, study further relation of DRX to DL/UL positioning reference signals, signaling, procedures and measurement accuracy including, but not limited to:

· DL PRS reception and UL SRS for positioning transmission outside DRX active time

· Measurement Accuracy requirements outside DRX active time

· Any required signaling from the UE to LMF or serving gNB, or serving gNB to the LMF

Proposal 15: For the purpose of enhanced efficiency, study further PRS processing without MG and DL/UL PRS prioritization over other channels and procedures.

Proposal 16: For the purpose of enhanced efficiency, study further support and enhancements for NR Positioning in the RRC Idle/Inactive state, including but not limited to

· Transmission of UL PRS signals & Reception of DL PRS signals

· Enablement of Rel-16 DL-only UE-assisted methods, DL/UL methods, UL-only methods

Proposal 17: For the purpose of enhanced efficiency, study further Positioning measurements derived on other reference signals and channels.

Decision: The document is noted.

R1-2006916 Potential positioning enhancements Ericsson

· Proposal 1: The network should configure values P and Q for the measurements to be performed and reported by the UE, where P is the number of paths and Q is the number of beams.

· Proposal 2: Magnitude, SNR, Doppler frequency, angle of arrival of every path should be reported.

· Proposal 3: It shall be unambiguously defined what additional paths a UE shall report.

· Proposal 4: LOS detection mechanisms should be studied within the Rel. 17 positioning enhancement study item.

· Proposal 5: Following measurements should be specified in Rel-17. These measurements can be part of rich reporting.

o Location and magnitude of the first peak.

o Location and magnitude of the highest peak.

o Components of PDP/CIR around first/highest peak.

· Proposal 6: Consider absolute time reporting in release 17 measurement reports

· Proposal 7: Send LS to RAN4, requesting RAN4 to investigate the possibility to define two (or multiple) sets of requirements (based on UE-capabilities) for RSTD accuracy, UE RX-TX time difference accuracy and UE TX timing accuracy in order to accommodate for both general purpose eMBB UEs and for UEs requiring high (sub-meter) accuracy positioning in e.g. I-IoT scenarios.

· Proposal 8: Study and specify methods to estimate UE RX and TX timing errors per UE antenna panel (due to filter group delays etc.) in order to enhance UL TDOA, DL TDOA and RTT positioning accuracy. Potential methods may include both reporting of what antenna panel has been used by the UE for a measurement or a SRS transmission and network control of what antenna panel the UE shall use for a measurement or a SRS transmission.

· Proposal 9: In order to maintain accuracy, the target latency must factor the need for tracking measurement, i.e. UE mobility.

· Proposal 10: Allow configuration of DL-PRS with any combination of comb-factor and symbol length, including symbol length 1.

· Proposal 11: Introduce signaling of a threshold relative to the strongest peak for the UE search of the first peak and define the DL RSTD and UE RX-TX time difference measurements based on the first identified peak which is stronger than the strength of the strongest peak multiplied with the signaled relative threshold factor.

· Proposal 12: RAN1 to study network control of thresholds for the UE search for the first peak including threshold relative to the estimated noise level (aimed at avoiding noise peaks), threshold relative to the strongest peak (aimed at avoiding channel peaks with delay longer than the measurement range) and delay dependent thresholds (aimed at avoiding side peaks).

· Proposal 13: cyclic shifts for DL PRS is considered in rel17, with configurable cyclic shifts and configurable maximum number of cyclic shift.

· Proposal 14: The cyclic shift of the UL SRS with staggered pattern can be configured to be 1) the same in each symbol, according to REL-15 behavior or 2) per SRS resource, across all symbols in the SRS resource, according to equation 1 above

· Proposal 15: The maximum number of available cyclic shifts nSRScs,max for the SRS for positioning is configurable by the gNodeB as part of the RRC configuration.

· Proposal 16: Assume Rel-16 single-DCI based Multi-TRP architecture for IIoT scenario in order to reduce latency associated with positioning.

· Proposal 17: In Rel-17 positioning, consider configuration of positioning measurement reports via RRC to reduce latency.

· Proposal 18: TRS is a candidate for positioning in release 17.

· Proposal 19: Support reuse of Rel-15 SRS resource set for gNB Rx-Tx and UE Rx-Tx measurements for positioning in NR.

· Proposal 20: Send an LS to RAN4 regarding UE Rx-Tx requirements

Note: There is no impact to specifications managed by RAN1

Decision: The document is noted.

R1-2005253 Positioning enhancement in Rel-17 Huawei, HiSilicon

R1-2005284 Positioning Enhancements FUTUREWEI

R1-2005381 Discussion on potential positioning enhancements vivo

R1-2005464 Discussion on potential NR positioning enhancements ZTE

R1-2005579 Discussion on Positioning Enhancements Sony

R1-2005712 Discussion of NR positioning enhancements CATT

R1-2005769 Potential positioning enhancements TCL Communication Ltd.

R1-2005879 Potential Enhancements of NR Positioning Design Intel Corporation

R1-2005992 Discussions on NR Positioning Enhancements OPPO

R1-2006068 Potential positioning enhancements BUPT

R1-2006150 Potential positioning enhancements Samsung

R1-2006216 Discussion on potential positioning enhancements CMCC

R1-2006240 Discussion on potential positioning enhancements InterDigital, Inc.

R1-2006250 Discussion on potential positioning enhancements Spreadtrum Communications

R1-2006324 On Potential NR Positioning Enhancements Lenovo, Motorola Mobility

R1-2006376 Discussion on potential enhancements for NR positioning LG Electronics

R1-2006429 Views on potential positioning enhancements Nokia, Nokia Shanghai Bell

R1-2006460 Potential positioning enhancements Fraunhofer IIS, Fraunhofer HHI

R1-2006522 Initial Views on Potential Positioning Enhancements Apple

R1-2006547 Potential positioning enhancements Beijing Xiaomi Electronics

R1-2006621 Discussion on positioning enhancements for Rel 17 CEWiT

R1-2006732 Discussion on potential techniques for NR Positioning Enhancements NTT DOCOMO, INC.

R1-2006859 Discussion on Potential positioning enhancements CAICT

[102-e-NR-Pos-Enh-Pot-Pos-Enh] – Ren Da (CATT)

Email discussion/approval on potential positioning enhancements until 8/21; address any remaining aspects by 8/27

R1-2006972 FL Summary for Potential Positioning Enhancements Moderator (CATT)

R1-2007111 FL Summary#2 for Potential Positioning Enhancements Moderator (CATT)

R1-2007172 FL Summary#3 for Potential Positioning Enhancements Moderator (CATT)

R1-2007210 FL Summary#4 for Potential Positioning Enhancements Moderator (CATT)

R1-2007343 FL Summary#5 for Potential Positioning Enhancements Moderator (CATT)

Agreement:

Partial staggering and non-staggering RE mapping of SRS for positioning with different combinations of comb-factors and symbol lengths will be investigated in Rel-17.

· The methods/signalling for addressing potential time-domain aliasing due to the partial/non-staggering RE mapping will be included in the study.

Agreement:

· Semi-persistent and a-periodic transmission and reception of DL PRS will be investigated in Rel-17.

o FFS: the details on when and how to enable semi-persistent and a-periodic DL PRS

o FFS: to be supported for which positioning methods, e.g.,

§ UE-assisted and/or UE-based positioning

§ DL positioning and/or Multi-RTT

· On-demand transmission and reception of DL PRS will be investigated in Rel-17.

o FFS: the details on when and how to enable on-demand DL PRS

o FFS: to be supported for which positioning methods, e.g.,

§ UE-assisted and/or UE-based positioning

§ DL positioning and/or Multi-RTT

· Notes:

o Semi-persistent means MAC-CE triggered

o Aperiodic would correspond to DCI-triggered

o On-demand corresponds to the UE-initiated or network-initiated request of PRS and/or SRS. So, it is NOT the same as whether PRS is DCI-triggered or MAC-CE triggered. It is about UE or LMF request/suggesting/recommending specific PRS pattern, ON/OFF, periodicity, BW, etc.

Agreement:

· Multipath mitigation techniques will be investigated in this SI for improving positioning accuracy, which may include, but not limited to the following:

o The applicable scenarios and performance benefits of multipath mitigation techniques

o The methods/measurement/signaling for the LOS/NLOS detection and identification

o The measurements for supporting the multipath mitigation/utilization

o The procedure and signaling for supporting the multipath mitigation/utilization

o Implementation-based solutions (e.g., outlier rejection) without the need of any additional specified method/measurements/procedures/signaling.

· Note: The above study applies to DL only, UL only, DL+UL positioning solutions for UE-based and UE-assisted positioning.

Agreement:

· NR positioning for UEs in RRC_IDLE state and UEs in RRC_INACTIVE state will be investigated in Rel-17, including the benefits on latency, network/UE efficiency and UE power consumption

· FFS: which positioning methods to be supported, e.g., DL positioning, UL positioning, DL+UL positioning and/or Multi-RTT

· FFS: the details of how to enable the UE positioning in RRC_IDLE state and RRC_INACTIVE state

o Reference signals (e.g., based on DL PRS signals, UL SRS signals, both of them, etc.)

o Signaling and procedures (e.g., based on PRACH procedure, paging triggered UL SRS transmission, etc.)

Agreement:

· For reducing NR positioning latency, more efficient signaling & procedures will be investigated to enable a device to request and report positioning information, which may include, but not limited to, the following aspects:

o DL PRS/UL SRS configuration, activation or triggering.

o The request for positioning information (the assistance data, etc.).

o The report of positioning information (the measurement report, etc.).

· Note: It is not within RAN1 scope to analyze positioning architecture enhancements to enable such more efficient signaling & procedures.

· Note: RAN1 does not make any assumptions on whether the LCS architecture specified in TS 23.273 is enhanced or not.

Agreement:

· Aggregating multiple DL positioning frequency layers of the same or different bands for improving positioning performance for both intra-band and inter-band scenarios will be investigated in Rel-17, which may take into account at least the following

o The scenarios and performance benefits of aggregating multiple DL positioning frequency layers

o The impact of channel spacing, timing offset, phase offset, frequency error, and power imbalance among CCs to the positioning performance for intra-band contiguous/ non-contiguous and inter-band scenarios

o UE complexity considerations

· Note: What is captured in the TR will be discussed separately.

Agreement:

Simultaneous transmission by the UE and reception by the gNB of the SRS for positioning across multiple CCs and multiple slots can be investigated in Rel-17, which may consider

· The scenarios and performance benefits of the enhancement

· The impact of channel spacing, TA and timing offset, phase offset, frequency error, and power imbalance across slots or CCs to the positioning performance for intra-band contiguous/ non-contiguous and inter-band scenarios

Agreement:

The scenario, benefits, and methods for improving the accuracy of the UL AoA and DL-AoD methods for both UE-based and network-based (including UE-assisted) positioning can be investigated in Rel-17.

Agreement:

The scenario, benefits, methods and signaling for improving positioning accuracy in the presence of the UE Rx/Tx transmission delays, and/or and gNB Rx/Tx transmission delays, will be investigated for UE-based and network-based (including UE-assisted) positioning in Rel-17.

8.5.44 Other

R1-2005382 Discussion on power consumption model for NR positioning enhancements vivo

R1-2005465 Channel state estimation based on prior channel information ZTE

R1-2005713 Discussion of NLOS channel modelling and network time synchronization for NR positioning CATT

R1-2005993 Analysis of NR Positioning for IIOT Scenarios OPPO

R1-2006151 Uplink Transmission Based Relative Positioning Samsung

R1-2006241 Discussion on positioning during idle/inactive mode InterDigital, Inc.

R1-2006398 Analysis of positioning service latency Huawei, HiSilicon

R1-2006523 Analysis for L1 Positioning Latency Apple

R1-2006917 PRS with cyclic shifts Ericsson

RAN1#103-e

8.5 Study on NR Positioning Enhancements

Please refer to RP-202094 for detailed scope of the SI

R1-2009835 Session notes for 8.5 (Study on NR Positioning Enhancements) Ad-Hoc Chair (Ericsson)

R1-2008762 TR 38.857 v0.1.0: Study on NR Positioning Enhancements Ericsson

Further revised in R1-2009400, in R1-2009418.

Decision:TR draft in R1-2009418 is endorsed with the following modifications:

Remove all instances of “can be investigated in Rel-17”
Add agreement on DL PRS aggregation into Section 7

as v0.1.0 in R1-2009430 TR 38.857 v0.1.0: Study on NR Positioning Enhancements Ericsson

R1-2009431 TR 38.857 v0.1.1: Study on NR Positioning Enhancements Ericsson

Decision: The update is endorsed as v0.1.1 in R1-2009544

R1-2009665 TR 38.857 v0.1.2: Study on NR Positioning Enhancements Ericsson

Decision: The update is endorsed as v0.2.0 in R1-2009670 with the following modifications:

Change “For the issues related to LOS/NLOS issues in positioning” to “For the issues related to mitigating effects of multipath/NLOS for positioning” in Section 8.4
Remove company names
Move tables in Section 8.4 to an Appendix
Remove “(as per the optional model)” in “For issues related to gNB/UE TX/RX timing errors (as per the optional model)” in Section 8.4

R1-2009671 TR 38.857 v0.2.1: Study on NR Positioning Enhancements Ericsson

R1-2009743 TR 38.857 v0.2.2: Study on NR Positioning Enhancements Ericsson

Decision: From GTW session on Nov. 13^th, the update is endorsed in principle as v0.3.0 in R1-2009745 with the following changes:

Merge 10.8, 10.9 and 10.10 as per Qualcomm’s comments
Remove individual company observations as per Nokia’s comments
Update per agreements made in the last GTW

R1-2009842 TR 38.857 v0.4.0: Study on NR Positioning Enhancements Rapporteur (Ericsson)

Decision: As per email decision posted on Nov. 20^th, v0.4.0 is endorsed as baseline for future updates – to be submitted for information to next plenary.

8.5.1 Additional scenarios for evaluation

R1-2007575 Scenarios and evaluation assumption for IIoT positioning Huawei, HiSilicon

R1-2007664 Discussion on additional scenarios for NR positioning evaluation vivo

R1-2007753 Remaining issues on evaluation assumptions ZTE

R1-2007858 Remaining issues on additional scenarios for evaluation of NR Positioning Enhancements CATT

R1-2007907 Remaining Issues on Evaluation Assumptions FUTUREWEI

R1-2007944 NR positioning scenarios Intel Corporation

R1-2008014 Remaining issues on target performance requirement of IIoT use case CMCC

R1-2008224 Discussion on Additional Scenarios for Evaluation of NR Positioning OPPO

R1-2008299 Additional scenarios for evaluation of NR positioning Nokia, Nokia Shanghai Bell

R1-2008363 Considerations on Additional Scenarios for Evaluation Sony

R1-2008415 Discussions on additional scenarios for evaluation for NR positioning LG Electronics

R1-2008488 Discussion on evaluation assumptions for latency InterDigital, Inc.

R1-2008617 Considerations on Additional Scenarios for Evaluation Qualcomm Incorporated

R1-2008763 Remaining details on additional scenarios for evaluation Ericsson

R1-2009343 FL summary for additional scenarios for evaluation Moderator (Ericsson)

[103-e-NR-ePos-01] – Florent (Ericsson)

Email discussion/approval on additional scenarios for evaluation and TR updates until 11/4; address any remaining aspects by 11/12

R1-2009364 Output#1 of [103-e-NR-ePos-01] Email discussion on additional scenarios for evaluation Moderator (Ericsson)

R1-2009417 Output#2 of [103-e-NR-ePos-01] Email discussion on additional scenarios for evaluation Moderator (Ericsson)

Conclusion:

When reporting network efficiency, the methodology is left up to each company and details should be provided.

Conclusion:

For SRS bandwidth stitching and PRS bandwidth stitching, when modelling the effect of phase offset between two PFLs (for 2CCs in the UL), a uniformly distributed phase offset is applied to the 2nd PFL (2^nd CC in the UL) with respect to the 1st PFL (1^st CC in the UL).

· If phase offset modeled, companies to provide how the phase offset is modeled in their evaluations.

Agreement:

· In Rel-17 target positioning requirements for commercial use cases are defined as follows:

o Horizontal position accuracy (< 1 m) for 90% of UEs

o Vertical position accuracy (< 3 m) for 90% of UEs

o End-to-end latency for position estimation of UE (< 100 ms)

o Physical layer latency for position estimation of UE (< 10 ms)

· In Rel-17 target positioning requirements for IIoT use cases are defined as follows:

o Horizontal position accuracy (< 0.2 m) for 90% of UEs

o Vertical position accuracy (< 1 m) for 90% of UEs

o End-to-end latency for position estimation of UE (< 100ms, in the order of 10 ms is desired)

o Physical layer latency for position estimation of UE (<10ms)

· Note 1: Target positioning requirements may not necessarily be reached for all scenarios and deployments

· Note 2: For some scenarios the requirement for Horizontal position accuracy can be relaxed to < 0.5 m in IIoT use cases.

· Note 3: All positioning techniques may not achieve the target positioning requirements over all scenarios

Final summary in:

R1-2009503 Output#3 of [103-e-NR-ePos-01] Email discussion on additional scenarios for evaluation Moderator (Ericsson)

8.5.2 Evaluation of achievable positioning accuracy and latency

[103-e-NR-ePos-04] – Ren Da(CATT)/Alexey (Intel)/Florent (Ericsson)

Email discussion/approval on collection of simulation results until 11/6

This thread was closed on Nov 9^th, after performing and submitting additional evaluations as shown in below revised contributions.

R1-2009433 Evaluation results for Rel-16 positioning and Rel-17 enhancement Huawei, HiSilicon (rev of R1-2007576)

R1-2007665 Evaluation of NR positioning performance vivo

R1-2007720 Evaluation of achievable positioning accuracy BUPT

R1-2007754 Evaluation of achievable accuracy and latency ZTE

R1-2007859 Discussion of evaluation of NR positioning performance CATT

R1-2007908 NLOS Identification and Mitigation FUTUREWEI

R1-2009390 Update of Evaluation Results for NR Positioning Intel Corporation (rev of R1-2007945)

R1-2007997 NR Positioning Latency Evaluations Lenovo, Motorola Mobility

R1-2008225 Evaluation of NR positioning in IIOT scenario OPPO

R1-2009555 Results on evaluation of achievable positioning accuracy and latency Nokia, Nokia Shanghai Bell (rev of R1-2008300)

R1-2009502 Discussion on Performance evaluation of Rel-17 positioning Sony (rev of R1-2008364)

R1-2008416 Discussions on evaluation of achievable positioning accuracy and latency for NR positioning LG Electronics

R1-2008489 Evaluation of achievable positioning latency InterDigital, Inc.

R1-2009708 Evaluation of achievable Positioning Accuracy & Latency Qualcomm Incorporated (rev of R1-2009361, rev of R1-2008618)

R1-2009428 Evaluation of positioning enhancements Fraunhofer IIS, Fraunhofer HHI (rev of R1-2008709)

R1-2008720 Positioning evaluation results on potential enhancements for additional use cases CEWiT

R1-2008764 Evaluation of achievable positioning accuracy and latency Ericsson

R1-2009345 Feature lead summary for evaluation of NR Positioning enhancements - AI 8.5.2 Moderator (Intel Corporation)

[103-e-NR-ePos-02] – Alexey (Intel)

Email discussion/approval on achievable positioning accuracy and latency including observations/conclusions based on evaluation results until 11/3; address any remaining aspects by 11/11

R1-2009375 Summary #1 of RAN WG1 E-mail Discussion [103-e-NR-ePos-02] - AI 8.5.2 Moderator (Intel Corporation)

Agreement:

Capture the following observations (On horizontal positioning accuracy in InF-SH) in the TR (editorial modifications and addition of references for the sources can be added when incorporating into the TR):

For the case without modeling synchronization and gNB/UE TX/RX timing errors in the InF-SH scenario.

· Based on the results provided by a majority of sources, sub-meter level @ 90% of horizontal positioning accuracy is achieved by Rel.16 solutions.

· Results were provided by [12] out of [17] sources for FR1 and by [9] sources out of [17] for FR2

o For NR positioning evaluations in FR1 band, the following is observed with respect to horizontal positioning accuracy:

§ Accuracy of ≤ 0.2m @ 90% is achieved in contributions from [3] sources and is not achieved in contributions from [9] sources

§ Accuracy of ≤ 0.5m @ 90% is achieved in contributions from [7] sources and is not achieved in contributions from [5] sources

o For NR positioning evaluations in FR2 band, the following is observed with respect to horizontal positioning accuracy:

§ Accuracy of ≤ 0.2m @ 90% is achieved in contributions from [6] sources and is not achieved in contributions from [3] sources

§ Accuracy of ≤ 0.5m @ 90% is achieved in contributions from [8] sources and is not achieved in contributions from [1] sources

R1-2009376 Summary #2 of RAN WG1 E-mail Discussion [103-e-NR-ePos-02] - AI 8.5.2 Moderator (Intel Corporation)

From GTW sessions:

Agreement:

Capture the following observations on horizontal positioning accuracy in InF-DH (Editorial modifications and updates to references to be made when capturing in the TR):

For the case without modeling synchronization and gNB/UE TX/RX timing errors in the baseline InF-DH scenario.

Based on the results provided by a majority of sources, sub-meter level @ 90% of horizontal positioning accuracy is not achieved by Rel.16 based solutions.
Results were provided by [13] sources (Huawei R1-2007576, BUPT R1-2007720, ZTE R1-2007754, CATT R1-2007859, FUTUREWEI R1-2007908, OPPO R1-2008225, Nokia R1- 2008300, Sony R1-2008364, CEWiT R1-2008720, Ericsson R1-2008764, QC R1-2008618, vivo R1-2007665, Intel R1-2007945) out of [17] for FR1 and by [9] sources (Huawei R1-2007576, BUPT R1-2007720, ZTE R1-2007754, CATT R1-2007859, Sony R1-2008364, Ericsson R1-2008764, QC R1-2008618, vivo R1-2007665, Intel R1-2007945) out of [17] for FR2

For NR positioning evaluations in FR1 band, the following is observed with respect to horizontal positioning accuracy:

Accuracy of ≤ 0.2m @ 90% is achieved in contribution from [1] source (CATT R1-2007859) and is not achieved in contributions from [12] sources (Huawei R1-2007576, BUPT R1-2007720, ZTE R1-2007754, FUTUREWEI R1-2007908, OPPO R1-2008225, Nokia R1- 2008300, Sony R1-2008364, CEWiT R1-2008720, Ericsson R1-2008764, QC R1-2008618, vivo R1-2007665, Intel R1-2007945)
Accuracy of ≤ 0.5m @ 90% is achieved in contributions from [4] sources (BUPT R1-2007720, CATT R1-2007859, QC R1-2009361, vivo R1-2007665) and is not achieved in contributions from [9] sources (Huawei R1-2007576, ZTE R1-2007754, FUTUREWEI R1-2007908, OPPO R1-2008225, Nokia R1- 2008300, Sony R1-2008364, CEWiT R1-2008720, Ericsson R1-2008764, Intel R1-2007945)

For NR positioning evaluations in FR2 band, the following is observed with respect to horizontal positioning accuracy:

Accuracy of ≤ 0.2m @ 90% is achieved in contributions from [3] sources (BUPT R1-2007720, QC R1-2008618, vivo R1-2007665) and is not achieved in contributions from [6] sources (Huawei R1-2007576, ZTE R1-2007754, CATT R1-2007859, Sony R1-2008364, Ericsson R1-2008764, Intel R1-2007945)
Accuracy of ≤ 0.5m @ 90% is achieved in contributions from [3] sources (BUPT R1-2007720, QC R1-2008618, vivo R1-2007665) and is not achieved in contributions from [6] sources (Huawei R1-2007576, ZTE R1-2007754, CATT R1-2007859, Sony R1-2008364, Ericsson R1-2008764, Intel R1-2007945)

Agreement:

Capture the following observations on vertical positioning accuracy in InF-SH (Editorial modifications and updates to references to be made when capturing in the TR):

For the case without modeling synchronization and gNB/UE TX/RX timing errors in the InF-SH scenario.

Results were provided by [4] sources (ZTE R1-2007754, CATT R1-2007859, vivo R1-2007665, Intel R1-2007945) out of [17] for FR1 and by [4] sources (ZTE R1-2007754, CATT R1-2007859, QC R1-2008618, Intel R1-2007945) out of [17] for FR2 band

For NR positioning evaluations in FR1 band, the following is observed with respect to vertical positioning accuracy:

Accuracy of ≤ 1m @ 90% is achieved in contribution from [2] sources (ZTE R1-2007754, vivo R1-2007665) and is not achieved from [2] sources (CATT R1-2007859, Intel R1-2007945)

For NR positioning evaluations in FR2 band, the following is observed with respect to vertical positioning accuracy:

Accuracy of ≤ 1m @ 90% is achieved in contribution from [4] sources (ZTE R1-2007754, CATT R1-2007859, QC R1-2008618, Intel R1-2009390) [and is not achieved by [0] sources]

Agreement:

Capture the following observations on vertical positioning accuracy in InF-DH (Editorial modifications and updates to references to be made when capturing in the TR):

For the case without modeling synchronization and gNB/UE TX/RX timing errors in the InF-DH scenario (including evaluations with variable gNB/UE heights).

Results were provided by [5] sources (ZTE R1-2007754, CATT R1-2007859, vivo R1-2007665, Intel R1-2007945, Huawei R1-2007576) out of [17] for FR1 and by [4] sources (ZTE R1-2007754, CATT R1-2007859, Intel R1-2007945, Huawei R1-2007576) out of [17] for FR2 band

For NR positioning evaluations in FR1 band, the following is observed with respect to vertical positioning accuracy:

Accuracy of ≤ 1m @ 90% is achieved in contribution from [2] sources (CATT R1-2007859, vivo R1-2007665) and is not achieved from [3] sources (ZTE R1-2007754, Intel R1-2007945, Huawei R1-2007576)

For NR positioning evaluations in FR2 band, the following is observed with respect to vertical positioning accuracy:

Accuracy of ≤ 1m @ 90% is achieved in contribution from [1] source (Huawei R1-2007576) and is not achieved from [3] sources (ZTE R1-2007754, CATT R1-2007859, Intel R1-2007945)

R1-2009406 Summary #3 of RAN WG1 E-mail Discussion [103-e-NR-ePos-02] - AI 8.5.2 Moderator (Intel Corporation)

R1-2009407 Summary #4 of RAN WG1 E-mail Discussion [103-e-NR-ePos-02] - AI 8.5.2 Moderator (Intel Corporation)

R1-2009606 Summary #5 of RAN WG1 E-mail Discussion [103-e-NR-ePos-02] - AI 8.5.2 Moderator (Intel Corporation)

R1-2009607 Summary #6 of RAN WG1 E-mail Discussion [103-e-NR-ePos-02] - AI 8.5.2 Moderator (Intel Corporation)

R1-2009762 Discussion on DL PRS and SRS for Positioning Measurement Time ([103-e-NR-ePos-02]) Moderator (Intel Corporation)

Agreement:

Capture the following in the TR:

Evaluation results for LOS/NLOS identification, outlier rejection, NLOS mitigation based on triangle inequality algorithms in indoor factory scenarios were provided by [12] sources (OPPO, Futurewei, vivo, Intel, Qualcomm, ZTE, Huawei, CeWiT, Nokia, Sony, Fraunhofer, Ericsson) out of [17] sources
NR positioning utilizing LOS/NLOS identification, outlier rejection, NLOS mitigation based on triangle inequality algorithms improve performance of positioning accuracy with respect to solutions that do not apply these techniques
From the evaluations,

[9] sources (Futurewei, Intel, ZTE, Huawei, CeWiT, Nokia, Sony, Fraunhofer, Ericsson) evaluated LOS/NLOS identification with additional specification changes relative to Rel.16 solutions
[2] sources (vivo, Qualcomm) evaluated outlier rejection algorithm (implementation-based algorithm that can be applied for Rel.16 solutions without specification changes)
[1] source (OPPO) evaluated NLOS mitigation using triangle-based inequality algorithm (implementation-based algorithm that can be applied for Rel.16 solutions without specification changes)

Comparative analysis of LOS/NLOS identification with specification changes vs implementation based methods (outlier rejection algorithms) was done by 6 sources (Intel, Huawei, vivo, Qualcomm, ZTE, Oppo)

Three sources (Intel, Huawei, ZTE) observe that NR positioning based on LOS/NLOS identification outperforms NR positioning utilizing outlier rejection
Three sources (vivo, Qualcomm, Oppo) observe that NR positioning utilizing outlier rejection outperforms NR positioning utilizing LOS/NLOS identification

Agreement:

Capture the following in the TR:

Evaluation results of gNB/UE TX/RX timing errors (as per the optional model) are provided by [7] sources (Huawei, ZTE, Qualcomm, Intel, CATT, Ericsson, vivo) out of [17] sources)

Capture summary of results provided in Tables in Section 2.1.2.3 of R1-2009606 in TR with the following modifications

Removal of the numbers in brackets after “YES”/”No”.
Change “barely” to “NO”

Agreement:

Capture the following in the TR:

Evaluation results for aggregation of DL positioning frequency layers were provided by [5] sources (Intel, Qualcomm, Huawei, vivo, Ericsson) out of [17].
Aggregation of NR positioning frequency layers improves positioning accuracy under certain scenarios, configurations, and assumptions on modelled impairments such as: bandwidth and spacing of aggregated layers, timing offset and frequency offset over frequency layers, phase discontinuity and possible amplitude imbalance.

One source (Huawei) observes that aggregation with phase continuity can help to improve the positioning accuracy, and discontinuous aggregation can approach the performance of contiguous aggregation with the same frequency span
One source (Intel) has shown that aggregation of frequency layers (without modeling impairements) improves the positioning accuracy for intra-band contiguous configuration and that further study is needed for other cases including impairments
One source (Ericsson) has observed that PRS aggregation shows potential gains without modeling phase error, but these gains are lost when the phase error between CCs becomes too large
One source (Qualcomm) has analyzed aggregation of 2 and 4 frequency layers for different channel spacings, time and phase offset across frequency layers
One source (vivo R1-2007666) has analyzed aggregation of 2 frequency layers for different time offset values and observed that:

For the case without impairements modeling, aggregation of multiple DL positioning frequency layers 50MHz+50MHz, performance target [0.2m @ 90%] cannot be achieved in both InF-SH and InF-DH.
For the case without impairements modeling, aggregation of multiple DL positioning frequency layers 50MHz+50MHz, the performance is worse than 100MHz but better than 50MHz.
The performance of aggregation of frequency layers degrades if timing offset is increased

Agreement:

Capture the following observations (Editorial modifications and updates to references to be made when capturing in the TR):

Summary table on physical layer latency for Rel.16 DL-TDOA/DL-AOD UE-Assisted NR positioning from discussion round #1 in the TR in Section 3.1.1 of R1-2009606
Summary of physical layer latency for Rel.16 DL-TDOA/DL-AOD UE-assisted NR positioning in FR1 was provided by [11] sources
Summary of physical layer latency for Rel.16 DL-TDOA/DL-AOD UE-assisted NR positioning in FR2 was provided by [4] sources
For evaluation in FR1,

results from [11] sources out of [11] sources (Qualcomm, Huawei, ZTE, vivo, Lenovo, LGE, CATT, Nokia, OPPO, Interdigital, Intel) show that minimum estimated physical layer latency for Rel.16 DL-TDOA/DL-AOD UE-assisted NR positioning exceeds 10ms
results from [2] (ZTE, Intel) sources out of [11] sources (Qualcomm, Huawei, ZTE, vivo, Lenovo, LGE, CATT, Nokia, OPPO, Interdigital, Intel) show that minimum estimated physical layer latency for Rel.16 DL-TDOA/DL-AOD UE-assisted NR positioning exceeds 100ms

For evaluation in FR2,

results from [4] sources out of [4] sources (ZTE, vivo, Lenovo, OPPO) show that minimum estimated physical layer latency for Rel.16 DL-TDOA/DL-AOD UE-assisted NR positioning exceeds 10ms
results from [2] (ZTE, vivo) sources out of [4] sources (ZTE, vivo, Lenovo, OPPO) show that minimum estimated physical layer latency for Rel.16 DL-TDOA/DL-AOD UE-assisted NR positioning exceeds 100ms

The following list provides the major physical layer latency components for Rel.16 DL TDOA/DL-AOD UE-assisted NR Positioning

DL PRS alignment, transmission, measurement (including processing time) and report delay
Measurement gap request, configuration and alignment time
UE/gNB higher layer (LPP/RRC) processing times

Agreement:

Capture the following observations (Editorial modifications and updates to references to be made when capturing in the TR):

Capture summary table in Section 3.2.1 of R1-2009606 on physical layer latency for Rel.16 UL-TDOA/UL-AOA NR positioning from discussion round #1 in the TR
Summary of physical layer latency for Rel.16 UL-TDOA/UL-AOA NR positioning in FR1 was provided by [8] sources (Huawei, vivo, LGE, CATT, Nokia, OPPO, Interdigital, Intel)
Summary of physical layer latency for Rel.16 UL-TDOA/UL-AOA NR positioning in FR2 was provided by [2] sources (vivo, OPPO)
For evaluation in FR1,

results from [3] sources (Huawei, CATT, Nokia) out of [8] sources (Huawei, vivo, LGE, CATT, Nokia, OPPO, Interdigital, Intel) show that minimum estimated physical layer latency for Rel.16 UL-TDOA/UL-AOA NR positioning does not exceed 10ms
results from [8] sources out of [8] sources (Huawei, vivo, LGE, CATT, Nokia, OPPO, Interdigital, Intel) show that minimum estimated physical layer latency for Rel.16 UL-TDOA/UL-AOA NR positioning does not exceed 100ms

For evaluation in FR2,

results from [2] sources out of [2] sources (vivo, OPPO) show that minimum estimated physical layer latency for Rel.16 UL-TDOA/UL-AOA NR positioning exceeds 10ms
results from [1] (OPPO) sources out of [2] sources (vivo, OPPO) show that minimum estimated physical layer latency for Rel.16 UL-TDOA/UL-AOA NR positioning does not exceed 100ms

The following list provides the major physical layer latency components for Rel.16 UL-TDOA/UL-AOA NR Positioning

SRS for positioning processing time
SRS for positioning alignment time (depends on periodic or aperiodic SRS for positioning)
gNB higher layer processing delays (RRC/ NRPPa processing times)

Agreement:

Capture the following observations (Editorial modifications and updates to references to be made when capturing in the TR):

Capture summary table on physical layer latency for Rel.16 Multi-RTT UE-assisted NR positioning from discussion round #1 in the TR
Summary of physical layer latency for Rel.16 Multi-RTT UE-assisted NR positioning in FR1 was provided by [6] sources (Qualcomm, Huawei, vivo, LGE, Interdigital, Intel)
Summary of physical layer latency for Rel.16 Multi-RTT UE-assisted NR positioning in FR2 was provided by [0] sources
For evaluation in FR1,

results from [6] sources (Qualcomm, Huawei, vivo, LGE, Interdigital, Intel) out of [6] sources (Qualcomm, Huawei, vivo, LGE, Interdigital, Intel) show that minimum estimated physical layer latency for Rel.16 Multi-RTT UE-assisted NR positioning exceeds 10ms
results from [4] sources (Qualcomm, Huawei, vivo, Interdigital) out of [6] sources (Qualcomm, Huawei, vivo, LGE, Interdigital, Intel) show that minimum estimated physical layer latency for Rel.16 Multi-RTT UE-assisted NR positioning does not exceed 100ms

The following list provides the major physical layer latency components for Rel.16 Multi-RTT UE-assisted NR positioning

DL PRS alignment, transmission, measurement time and report delay
Measurement gap request, configuration, alignment time
SRS for positioning processing time
SRS for positioning alignment time (depends on periodic or aperiodic SRS for positioning)
UE/gNB higher layer (LPP/RRC/NRPPa) processing times

Agreement:

Capture the following observations (Editorial modifications and updates to references to be made when capturing in the TR):

Capture summary table on physical layer latency for Rel.16 E-CID NR positioning from discussion round #1 in the TR
Summary of physical layer latency for Rel.16 E-CID NR positioning in FR1 was provided by [3] sources (Huawei, ZTE, LGE)
Summary of physical layer latency for Rel.16 E-CID NR positioning in FR2 was provided by [0] sources
For evaluation in FR1,

results from [2] sources (ZTE, LGE) out of [3] sources (Huawei, ZTE, LGE) show that minimum estimated physical layer latency for Rel.16 E-CID NR positioning exceeds 10ms
results from [3] sources (Huawei, ZTE, LGE) out of [3] sources (Huawei, ZTE, LGE) show that minimum estimated physical layer latency for Rel.16 E-CID NR positioning does not exceed 100ms

The following list provides the major physical layer latency components for Rel.16 E-CID NR positioning

Higher layer signaling processing

Agreement:

Capture the following observations (Editorial modifications and updates to references to be made when capturing in the TR):

Capture summary table on physical layer latency for Rel.16 DL-only UE-based NR positioning from discussion round #1 in the TR
Summary of physical layer latency for Rel.16 DL-only UE-based NR positioning in FR1 was provided by [6] sources (Qualcomm, Huawei, vivo, Lenovo, OPPO, Interdigital)
Summary of physical layer latency for Rel.16 DL-only UE-based NR positioning in FR2 was provided by [2] sources (vivo, Lenovo)
For evaluation in FR1,

results from [4] sources (Huawei, vivo, OPPO, Interdigital) out of [6] sources (Qualcomm, Huawei, vivo, Lenovo, OPPO, Interdigital) show that minimum estimated physical layer latency for Rel.16 DL-only UE-based NR positioning exceeds 10ms
results from [6] sources out of [6] sources (Qualcomm, Huawei, vivo, Lenovo, OPPO, Interdigital) show that minimum estimated physical layer latency for Rel.16 DL-only UE-based NR positioning does not exceed 100ms

For evaluation in FR2,

results from [2] sources out of [2] sources (vivo, Lenovo) show that minimum estimated physical layer latency for Rel.16 DL-only UE-based NR positioning exceeds 10ms
results from [1] (vivo) sources out of [2] sources (vivo, Lenovo) show that minimum estimated physical layer latency for Rel.16 DL-only UE-based NR positioning exceeds 100ms

The following list provides the major physical layer latency components for Rel.16 DL-only UE-based NR positioning

DL PRS alignment, transmission, measurement time and, if requested, report delay
Measurement gap request, configuration, alignment time
Higher layer (LPP/RRC) processing times

Agreement:

Capture the following observations (Editorial modifications and updates to references to be made when capturing in the TR):

For the case without modeling synchronization and gNB/UE TX/RX timing errors in the UMa scenario

Based on the results provided, 10 m level @ 90% of horizontal positioning accuracy is achieved by Rel.16 in UMa scenario
Results were provided by [2] sources (Ericsson R1-2008764, QC R1-2008618) out of [17] for FR1 band

For NR positioning evaluations for UMa scenario in FR1 band, the following is observed with respect to horizontal positioning accuracy:

Accuracy of ≤ 1m @ 80% is achieved for the outdoor UEs in contributions from [1] source (QC, R1-2008618) out of [2] sources (Ericsson R1-2008764, QC R1-2008618) in the scenario without absolute time of arrival modelling. Zero sources met an accuracy of ≤ 1m @ 90%.
Accuracy of ≤ 10m @ 90% is achieved for the outdoor UEs in contributions from [2] sources (Ericsson R1-2008764, QC R1-2008618) out of [2] sources in the scenario without absolute time of arrival modelling
Accuracy of ≤ 10m @ 90% is achieved for the indoor UEs in contributions from [1] source (Ericsson R1-2008764) out of [2] sources in the scenario without absolute time of arrival modelling

Agreement:

Capture the following observations (Editorial modifications and updates to references to be made when capturing in the TR):

For the case without modeling synchronization and gNB/UE TX/RX timing errors in the UMi scenario

Results were provided by [4] sources (Nokia R1- 2008300, Ericsson R1-2008764, QC R1-2008618, Fraunhofer R1-2009428) out of [17] for FR1 band

For NR positioning evaluations for UMi scenario in FR1 band, the following is observed with respect to horizontal positioning accuracy:

Accuracy of ≤ 1m @ 90% is achieved in contributions from [2] sources (Ericsson R1-2008764, QC R1-2008618) and is not achieved from [2] sources (Nokia R1- 2008300, Fraunhofer R1-2009428) in the scenario without absolute time of arrival modelling
Accuracy of ≤ 1m @ 90% is not achieved from [2] sources (QC R1-2008618, Fraunhofer) in a scenario with absolute time of arrival modelling

Agreement:

Capture the following observations (Editorial modifications and updates to references to be made when capturing in the TR):

For the case without modeling synchronization and gNB/UE TX/RX timing errors in the IOO scenario

Based on the results provided by a majority of the sources, 1 m level @ 90% of horizontal positioning accuracy is achieved by Rel.16 in IOO scenario
Results were provided by [5] sources (CATT R1-2007859, Nokia R1- 2008300, Sony R1-2008364, Ericsson R1-2008764, vivo R1-2007665) out of [17] for FR1 and [5] sources (CATT R1-2007859, Sony R1-2008364, Ericsson R1-2008764, QC R1-2008618, vivo R1-2007665) out of [17] for FR2 band

For NR positioning evaluations for IOO scenario in FR1 band, the following is observed with respect to horizontal positioning accuracy:

Accuracy of ≤ 1m @ 90% is achieved in contributions from [4] sources (CATT R1-2007859, Sony R1-2008364, Ericsson R1-2008764, vivo R1-2007665) and is not achieved from [1] source (Nokia R1- 2008300) in the scenario without absolute time of arrival modelling
Accuracy of ≤ 1m @ 90% is achieved from [1] source (vivo R1-2005380) in a scenario with absolute time of arrival modelling

For NR positioning evaluations for IOO scenario in FR2 band, the following is observed with respect to horizontal positioning accuracy:

Accuracy of ≤ 1m @ 90% is achieved in contributions from [5] sources (CATT R1-2007859, Sony R1-2008364, Ericsson R1-2008764, QC R1-2008618, vivo R1-2007665) in the scenario without absolute time of arrival modelling
Accuracy of ≤ 1m @ 90% is achieved from [1] source (vivo R1-2005380) in a scenario with absolute time of arrival modelling

Agreement:

Capture the following observations (Editorial modifications and updates to references to be made when capturing in the TR):

The results for the UE efficiency (power saving) in the RRC_IDLE/RRC_INACTIVE states were analyzed by 2 sources (Huawei/HiSi, vivo) out of 17 sources (assumptions may be different between the different sources)
In one source (Huawei/HiSi), the following observations were made:

RRC_IDLE/RRC_INACTIVE state positioning can save about 7%-40% power consumption compared to C-DRX configuration

In one source (vivo), the following observations were made:

Positioning report in the RRC_IDLE state can provide 44.32 % of power saving gain compared to the report in the RRC_CONNECTED state
Positioning measurement and report in the RRC_IDLE state can provide at least 48.38 % of power saving gain compared to the measurement and report in the RRC_CONNECTED state

Conclusion:

Estimated minimum DL PRS measurement time in Rel.16 can be 88.5ms depending on DL PRS configuration settings

Note: The following assumptions are made

One DL PRS frequency layer in FR1
CSSF = 1
NRxBeam, i = 1,
Nsample = 4 (DL PRS RSTD measurements are done across 4 DL PRS periods)
Both DL PRS periodicity and MGRP are equal to 20ms
Configured DL PRS resources are within UE DL PRS processing capacity (N,T) = (0.5ms, 8ms)

Conclusion:

SRS for positioning measurement time of 12 ms can be achieved under certain SRS for positioning configuration settings depending on the frame configuration

Note: The following assumptions are made

SRS for positioning alignement time 0.5 ms
SRS for positioning transmission time 0.5ms
SRS for positioning processing time 5 ms
30 kHz SCS in FR1
Single SRS resource set with single SRS resource
Four SRS instances

Note: Considering UL link budget and interference on SRS for positioning signals, the longer transmission time may be needed that will further increase SRS for positioning measurement time

Agreement:

Capture the following observations in the TR (Editorial modifications and updates to references to be made when capturing in the TR):

· The results for the PRS resource utilization were analyzed by 3 sources (Huawei/HiSi, vivo, CATT) out of 17 sources

· In one source (Huawei), the PRS resource utilization was evaluated for the case of 160 ms DL PRS periodicity, 30 kHz subcarrier spacing, and 12, 4, and 1 symbol per PRS resource:

o PRS with 12, 4, and 1 symbol has positioning resource utilization of 2.14 %, 0.714 %, and 0.179 %, respectively

· In one source (vivo), the PRS resource utilization was evaluated:

o In FR1, for 20 ms DL PRS periodicity and MG periodicity, 3ms MGL, 30 kHz subcarrier spacing, comb 6 and 6 symbols per PRS resource, 18 positioning sites and 1 beams per site, PRS resource utilization is 3.21% while the MGL/MGRP (UE overhead) is 15%.

o In FR2, for 20 ms DL PRS periodicity, 20ms for MGL and MGRP, 120 kHz subcarrier spacing, comb 6 and 6 symbols per PRS resource, 18 positioning sites and 64 beams per site, PRS resource utilization is 51.42% while the MGL/MGRP (UE overhead) is 100%

o It was observed by the source that the network and device efficiency can be improved by on-demand PRS (assuming the same latency) compared to periodic PRS

· In one source (CATT), the PRS resource utilization was evaluated for the case of 20 ms DL PRS periodicity, 30 kHz subcarrier spacing, and 12 symbols per PRS resource:

o PRS with 12 symbols has positioning resource utilization of 2.1 %.

8.5.3 Potential positioning enhancements

R1-2007552 Positioning Enhancements FUTUREWEI

R1-2007577 Positioning enhancement in Rel-17 Huawei, HiSilicon

R1-2007666 Discussion on potential positioning enhancements vivo

R1-2007721 Potential positioning enhancements BUPT

R1-2007755 Discussion on potential NR positioning enhancements ZTE

R1-2007860 Discussion of NR positioning enhancements CATT

R1-2007886 Potential positioning enhancements TCL Communication Ltd.

R1-2007946 NR positioning enhancements Intel Corporation

R1-2007998 Potential NR Positioning Enhancements Lenovo, Motorola Mobility

R1-2008015 Discussion on potential positioning enhancements CMCC

R1-2008083 Potential positioning enhancements Xiaomi

R1-2008168 Potential positioning enhancements Samsung

R1-2008226 Discussions on NR Positioning Enhancements OPPO

R1-2008301 Views on potential positioning enhancements Nokia, Nokia Shanghai Bell

R1-2008365 Considerations on potential positioning enhancements Sony

R1-2008417 Discussions on potential enhancements for NR positioning LG Electronics

R1-2008491 Discussion on potential positioning enhancements InterDigital, Inc.

R1-2008519 Views on positioning enhancement for Rel-17 MediaTek Inc.

R1-2008550 Discussion on potential techniques for NR Positioning Enhancements NTT DOCOMO, INC.

R1-2008619 Potential Positioning Enhancements for NR Rel-17 Positioning Qualcomm Incorporated

R1-2008841 Potential positioning enhancements Fraunhofer IIS, Fraunhofer HHI (rev of R1-2008710)

R1-2008718 Discussion on positioning enhancements for Release 17 CEWiT

R1-2008765 Potential positioning enhancements Ericsson

R1-2009285 Discussion on Potential positioning enhancements CAICT

R1-2009314 FL Summary for Potential Positioning Enhancements Moderator (CATT)

[103-e-NR-ePos-03] – Ren Da (CATT)

Email discussion/approval on potential positioning enhancements until 11/02; address any remaining aspects by 11/10

R1-2009366 FL Summary#2 for Potential Positioning Enhancements Moderator (CATT)

Agreement:

· NR positioning for UEs in RRC_INACTIVE state is recommended for normative work, including

o DL, UL and DL+UL positioning methods

o UE-based and UE-assisted positioning solutions

Support of UE positioning measurements for UEs in RRC_inactive state

Options that can be considered include DL-PRS or DL-PRS and SSB

Support of gNB positioning measurements for UEs in RRC_inactive state

The details of how to enable the UE positioning in RRC_ INACTIVE state can be further discussed during normative work. These details may include, but are not limited to the following aspects:

UL reference signals (e.g., SRS for positioning, PRACH preambles) for UL measurements
Signalling and procedures for support the assistance data delivery, DL-PRS configuration, UL reference signals for positioning resource configuration, measurement reporting), which may be developed based on the enhancements of existing signalling and procedures (e.g., existing 2-step and/or 4-step PRACH procedures, paging procedure, small data transmission).

R1-2009395 FL Summary#3 for Potential Positioning Enhancements Moderator (CATT)

R1-2009396 FL Summary#4 for Potential Positioning Enhancements Moderator (CATT)

R1-2009397 FL Summary#5 for Potential Positioning Enhancements Moderator (CATT)

R1-2009398 FL Summary#6 for Potential Positioning Enhancements Moderator (CATT)

R1-2009399 FL Summary#7 for Potential Positioning Enhancements Moderator (CATT)

R1-2009673 FL Summary#8 for Potential Positioning Enhancements Moderator (CATT)

R1-2009678 FL Summary#9 for Potential Positioning Enhancements Moderator (CATT)

R1-2009679 FL Summary#10 for Potential Positioning Enhancements Moderator (CATT)

Agreement:

Capture the following in the TR:

From a physical layer perspective, on-demand transmission and reception of DL PRS, which includes at least the following is recommended

· UE-initiated request of on-demand DL PRS transmission

· LMF (network)-initiated request of on-demand DL PRS transmission

Above enhancements are recommended for both DL and DL+UL positioning methods and both UE-based and UE-assisted positioning solutions.

Agreement:

Capture the following in the TR:

Simultaneous transmission by the gNB and reception by the UE of intra-band one or more contiguous carriers in one or more contiguous PFLs can be studied further and if needed, specified during normative work

· From both gNB and UE perspective, the applicability and feasibility of this enhancement for different scenarios, configurations, bands and RF architectures, can be further studied

Agreement:

Capture the following in the TR:

Simultaneous transmission by the UE and aggregated reception by the gNB of the SRS for positioning in multiple contiguous intra-band carriers can be studied further and if needed, specified during normative work.

· From both gNB and UE perspective, the applicability and feasibility of this enhancement for different scenarios, configurations, particular bands and RF architectures, can be further studied.

Agreement:

Capture the following in the TR:

· The methods, measurements, signaling, and procedures for improving positioning accuracy in the presence of the UE Rx/Tx timing delays, and/or and gNB Rx/Tx timing delays are recommended for normative work, including

o DL, UL and DL+UL positioning methods

o UE-based and UE-assisted positioning solutions

· Note: The details of the solutions are left for further discussion in normative work.

Agreement:

Capture the following in the TR:

The enhancements of the procedure, measurements, reporting, and signalling for improving the accuracy of

· UL AoA is recommended for normative work for network-based positioning solutions.

· DL-AoD is recommended for normative work for UE-based and network-based (including UE-assisted) positioning solutions.

Agreement:

Capture the following in the TR:

Enhancements of information reporting from UE and gNB for supporting multipath/NLOS mitigation can be studied further, and if needed, specified during normative work for improving positioning accuracy.

· Note: The details of the enhancements of reporting are left for further discussion in normative work, which may include, but are not limited to the following information associated with multi-path, e.g., LOS/NLOS identification, time of arrival of the multi-path components, signal power and/or relative power, power delay profile, angle, and/or polarization information, coherence bandwidth, etc.

Agreement:

Capture the following in the TR:

Aperiodic reception of DL PRS from the TRPs of the serving gNB and aperiodic reception of DL PRS from the TRPs of the neighbouring gNBs can be studied further and if needed, specified during normative work.

· Note: Aperiodic reception in the above corresponds to DCI-triggered reception

Agreement:

Capture the following in the TR:

Semi-persistent reception of DL PRS from the TRPs of the serving gNB and Semi-persistent reception of DL PRS from the TRPs of the neighbouring gNBs can be studied further and if needed, specified during normative work.

· Note: Semi-persistent reception in the above corresponds to MAC-CE activated reception

Agreement:

Capture the following in the TR:

The enhancements of signaling & procedures for reducing NR positioning latency are recommended for normative work, including DL and DL+UL positioning methods

The details of the solutions are left for further discussion in normative work, which may include the following aspects:

Latency reduction related to the measurement gap
Latency reduction related to the reporting and request of the measurements (e.g., via RRC signaling, MAC-CE and/or physical layer procedure, and/or priority rules)
Latency reduction related to measurement time

The following enhancements of signaling & procedures for reducing NR positioning latency can be studied and specified, if needed

Latency reduction related to the request and response of positioning assistance data (e.g., via RRC signaling, MAC-CE and/or physical layer procedure)
Latency reduction related to the reception of DL PRS (e.g., priority rules for the reception of DL PRS)

No assumptions are made on whether the LCS architecture specified in TS 23.273 is enhanced or not.

Agreement:

Capture the following in the TR:

From a physical layer perspective, it is feasible for a UE to perform DL positioning measurement in RRC_IDLE state.

· Note: This does not imply that measurements have to be reported in RRC_IDLE state.

Conclusion:

It is up to RAN2 to decide whether to support the enhancements of NR positioning reporting of DL positioning measurements and/or positioning estimates for RRC_IDLE UEs.

Agreement:

Capture the following for the Conclusions section of the TR (Modifications can be made based on further discussion as necessary):

------------------------------------------------------- Begin Text ------------------------------------------------------

This study focused on the analysis of potential enhancements and solutions necessary to support the high accuracy, low latency, high network efficiency and device efficiency to NR positioning targeting both general commercial and IIOT use cases.

In the study item, Rel-17 target positioning requirements for RAT dependent solutions were discussed and defined for general commercial use cases and IIoT use cases, including horizontal and vertical positioning accuracy, and physical layer and end-to-end positioning latency (see Section 5). Additional scenarios and channel models for evaluating Rel-17 NR positioning enhancements were developed for the evaluation of the achievable positioning performance of the enhancements (see Section 6).

The potential positioning enhancements for improving positioning accuracy, reducing latency, and improving network and device efficiency of NR positioning were studied. The potential positioning enhancements, which were investigated rigorously in this study, as outlined in Section 7.X.

NR positioning accuracy with Rel.16 positioning solutions were evaluated under the condition that gNB time synchronization error and gNB/UE TX/RX timing errors are not modelled for InF-SH scenario and InF-DH scenario for both FR1 and FR2 bands. The evaluation results show:

· For horizontal positioning accuracy,

o in the InF-SH scenario, based on the results provided [by a majority of sources], sub-meter level @ 90% is achieved in both FR1 and FR2 bands.

o in the InF-DH scenario, based on the results provided [by a majority of sources], sub-meter level @ 90% is not achieved in both FR1 and FR2 bands.

· For vertical positioning accuracy

o in the InF-SH scenario,

§ sub-meter level @ 90% is achieved by some sources but not achieved by some other sources in FR1 band

§ sub-meter level @ 90% is achieved by all sources in FR2 band;

o in the InF-DH scenario,

§ sub-meter level @ 90% is achieved by some sources and is not achieved by some other sources in both FR1 and FR2 bands

For the case without modeling synchronization and gNB/UE TX/RX timing errors in the IOO scenario

· Based on the results provided by a majority of the sources, 1 m level @ 90% of horizontal positioning accuracy is achieved by Rel.16 in IOO scenario

For the case without modeling synchronization and gNB/UE TX/RX timing errors in the UMa scenario

· Based on the results provided, 10 m level @ 90% of horizontal positioning accuracy is achieved by Rel.16 in UMa scenario

For the case without modeling synchronization and gNB/UE TX/RX timing errors in the UMi scenario

· Based on the results provided by some of the companies, 1 m level @ 90% of horizontal positioning accuracy is achieved by Rel.16 in UMi scenario

The impact of NLOS/multipath on NR positioning accuracy and the resolutions for NLOS/multipath mitigation were investigated. NR positioning utilizing LOS/NLOS identification, outlier rejection, NLOS mitigation based on triangle inequality algorithms improve performance of positioning accuracy with respect to solutions that do not apply these techniques.

The impact of gNB/UE TX/RX timing errors on NR positioning accuracy were investigated. Evaluation results show the gNB/UE TX/RX timing errors have significant impact on positioning accuracy.

Aggregation of NR positioning frequency layers for improving positioning accuracy were investigated. Evaluation results show that aggregation of NR positioning frequency layers improves positioning accuracy under certain scenarios, configurations, and assumptions on modelled impairments as outlined in Section [8.4].

Physical layer latency for Rel.16 DL-TDOA/DL-AOD UE-Assisted, UL-TDOA/UL-AOA, Multi-RTT, E-CID and DL-only UE-based NR positioning were investigated, and the major physical layer latency components for these NR positioning techniques were also identified as shown in Section [8.4].

The UE efficiency (power saving) in the RRC_IDLE/RRC_INACTIVE states were also analysed, and power saving gains are observed with detailed observations related to power savings are outlined in Section [8.4].

The network efficiency in terms of resource utilization was analyzed and benefits of potential positioning enhancements observed are outlined in Section [8.4].

The potential positioning enhancements for improving positioning accuracy, reducing latency, and improving network and device efficiency of NR positioning were studied.

The following enhancements have been recommended for normative work

- NR positioning for UEs in RRC_INACTIVE state, including

o DL, UL and DL+UL positioning methods

o UE-based and UE-assisted positioning solutions

o Support of UE positioning measurements for UEs in RRC_inactive state

§ Options that can be considered include DL-PRS or DL-PRS and SSB

o Support of gNB positioning measurements for UEs in RRC_inactive state

- On-demand transmission and reception of DL PRS, which includes at least

o UE-initiated request of on-demand DL PRS transmission

o LMF (network)-initiated request of on-demand DL PRS transmission

o Above enhancements are recommended for both DL and DL+UL positioning methods and both UE-based and UE-assisted positioning solutions.

- The methods, measurements, signaling, and procedures for improving positioning accuracy in the presence of the UE Rx/Tx timing delays, and/or and gNB Rx/Tx timing delays, including

o DL, UL and DL+UL positioning methods

o UE-based and UE-assisted positioning solutions

- The enhancements of the procedure, measurements, reporting, and signalling for improving the accuracy of

o UL AoA for network-based positioning solutions.

o DL-AoD for UE-based and network-based (including UE-assisted) positioning solutions

- The enhancements of signaling & procedures for reducing NR positioning latency related to, including DL and DL+UL positioning methods:

o the measurement gap

o the measurement request and reporting (e.g., via RRC signaling, MAC-CE and/or physical layer procedure, and/or priority rules)

o the measurement time

The following enhancements are considered beneficial for the purpose of improving positioning accuracy, reducing latency, improving network and/or device efficiency and are being recommended to be studied further and if needed, specified during normative work

- Simultaneous transmission by the gNB and aggregated reception by the UE of intra-band one or more contiguous carriers in one or more contiguous PFLs

- Simultaneous transmission by the UE and aggregated reception by the gNB of the SRS for positioning in multiple contiguous intra-band carriers

- Enhancements of information reporting from UE and gNB for supporting multipath/NLOS mitigation

- Aperiodic reception of DL PRS from the TRPs of the serving gNB and aperiodic reception of DL PRS from the TRPs of the neighbouring gNBs

- Semi-persistent reception of DL PRS from the TRPs of the serving gNB and Semi-persistent reception of DL PRS from the TRPs of the neighbouring gNBs

- Enhancements of signaling & procedures for reducing NR positioning latency related to

o the request and response of positioning assistance data (e.g., via RRC signaling, MAC-CE and/or physical layer procedure)

o the reception of DL PRS (e.g., priority rules for the reception of DL PRS

From a physical layer perspective, it is feasible for a UE to perform DL positioning measurement in RRC_IDLE state. This does not imply that measurements have to be reported in RRC_IDLE state.

It is recommended to proceed with a normative work to support NR positioning enhancements.

------------------------------------------------------- End Text ------------------------------------------------------

8.5.44 Other

R1-2007667 Discussion on new techniques for NR positioning vivo

R1-2007756 Channel state estimation based on prior channel information ZTE

R1-2007861 Discussion of NLOS channel modelling and network time synchronization for NR positioning CATT

R1-2007910 Polarization-based LOS Detection FUTUREWEI

R1-2008169 Uplink Transmission Based Relative Positioning Samsung

R1-2008227 Analysis of NR Positioning Requirements OPPO

R1-2008302 Additional considerations for positioning enhancements Nokia, Nokia Shanghai Bell

R1-2008321 Evaluations on additional channel model features Huawei, HiSilicon

R1-2008492 Discussion on positioning failure and mobility modeling InterDigital, Inc.

R1-2008766 PRS with cyclic shifts Ericsson

RAN1#104-e

8.5 NR Positioning Enhancements

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

R1-2102194 Session notes for 8.5 (Study on NR Positioning Enhancements) Ad-Hoc Chair (Ericsson)

Incomong LS from RAN2

R1-2102071 LS to capture Text Proposal for TR 38.857 RAN2, Ericsson

R1-2102147 LS to capture Text Proposal for TR 38.857 RAN2, Ericsson

8.5.1 Accuracy improvements by mitigating UE Rx/Tx and/or gNB Rx/Tx timing delays

Including DL, UL and DL+UL positioning methods, and UE-based and UE-assisted positioning solutions.

R1-2100445 Discussion on methods for RX/TX timing delay mitigating vivo

· Proposal 1: ‘Reference UE’ based differential positioning method should be supported to assist UE and gNB Rx/Tx timing delay mitigating.

o ‘The reference UE’ can measure/transmit positioning signals from/to multiple TRPs and report the measurement results to the LMF as normal UEs

o The accurate and reliable location of ‘the reference UE’ should be known by the LMF and the UE itself

· Proposal 2: AoA-based RX/TX timing delay mitigating method should be considered as an alternative method to ‘reference UE’ based differential positioning method.

· Proposal 3: To avoid Rx/Tx timing delay from affecting angle estimation for DL-AoD and UL-AoA method, support to limit to only one TXRU (or panel) used by the gNB for positioning.

Decision: The document is noted.

R1-2101468 Enhancements on Timing Error Mitigations for improved Accuracy Qualcomm Incorporated

· Proposal 1: Support UE and gNB reporting enhancements for the purpose of providing information, to the entity performing the positioning calculation, related to which measurements can be assumed to have a same Tx, or Rx, or Rx-Tx timing error.

o Applicable to both UE-assisted and UE-based methods

o FFS: Further signaling details, capabilities, procedures

· Proposal 2: Support mechanisms and signaling to enable PRS reception by TRPs and associated reporting of gNB measurements derived on PRS reception and/or PRS transmission timing.

o FFS: Signaling details and procedures

· Proposal 3: Support enhancements in the reporting of the positioning measurements (from the UE and the gNB) to enable reporting in a single report multiple measurements:

o Enable multiple measurement reporting in a single report with timestamps derived on the same TRP & PRS resources

· Proposal 4: Include transmit time difference information for each DL-PRS Resource of a TRP with respect to a reference in the position calculation assistance data.

o FFS: Details on the transmit time difference signaling

· Proposal 5: Support Tx Timing Adjustment information Reporting from UEs to the LMF for DL+UL or UL-only positioning.

Decision: The document is noted.

R1-2100128 Enhancement of timing-based positioning by mitigating UE Rx/Tx and/or gNB Rx/Tx timing delays OPPO

R1-2100195 Enhancement to mitigate gNB and UE Rx/Tx timing error Huawei, HiSilicon

R1-2100293 Positioning accuracy improvement by mitigating timing delay ZTE

R1-2100308 Disussion on accuracy improvements of NR positioning enhancements CAICT

R1-2100385 Discussion on accuracy improvements by mitigating UE Rx/Tx and/or gNB Rx/Tx timing delays CATT

R1-2100548 Initial views on mitigating UE and gNB Rx/Tx timing errors Nokia, Nokia Shanghai Bell

R1-2100657 Mitigation of UE and gNB Tx/Rx timing errors Intel Corporation

R1-2100697 Positioning enhancement by UE Assistance TCL Communication Ltd.

R1-2100708 Discussion on accuracy improvement by mitigating UE Rx/Tx and gNB Rx/Tx timing delays LG Electronics

R1-2100752 Techniques to improve accuracy in the presence of UE Rx/Tx and/or gNB Rx/Tx timing delays InterDigital, Inc.

R1-2101046 Discussion on gNB/UE Rx/Tx timing delay mitigation solutions CMCC

R1-2101131 On methods for Rx/Tx timing delays mitigation Fraunhofer IIS, Fraunhofer HHI

R1-2101140 The mitigation of RX/TX timing delays for higher accuracy MediaTek Inc.

R1-2101210 Discussion on accuracy improvements on timing based positioning solutions Samsung

R1-2101387 Positioning accuracy enhancements under UE and/or gNB Tx/Rx timing errors Apple

R1-2101527 NR positioning enhancements by mitigating timing delays China Telecom

R1-2101754 Techniques mitigating UE Rx/Tx timing delays Ericsson

R1-2102201 [DRAFT] LS on UE/TRP Tx/Rx Timing Errors CATT

[104-e-NR-ePos-01] – Ren Da (CATT)

Email discussion/approval on accuracy improvements by mitigating UE Rx/Tx and/or gNB Rx/Tx timing delays with checkpoints for agreements on Jan-28, Feb-02, Feb-05

R1-2101764 FL Summary for accuracy improvements by mitigating UE Rx/Tx and/or gNB Rx/Tx timing delays Moderator (CATT)

R1-2101951 FL Summary #2 for accuracy improvements by mitigating UE Rx/Tx and/or gNB Rx/Tx timing delays Moderator (CATT)

Agreement:

· Study specification impact for enabling a reference device with known location to support the following functionalities:

o Measure DL PRS and report associated measurements (e.g., RSTD, Rx-Tx time difference, RSRP) to the LMF;

o Transmit SRS and enable TRPs to measure and report measurements (e.g., RTOA, Rx-Tx time difference, AOA) associated with the reference device to the LMF;

o FFS: The details of the signalling, the measurements, the parameters related to the Rx and Tx timing delays, AoD and AOA enhancements and measurement calibrations;

o FFS: The report of device location coordinate information to the LMF if the LMF does not have the information

o FFS: The device with the known location being a UE and/or a gNB

o FFS: Precision to which location of reference device is known

Note: RAN1 assumes using these enhancements for the purpose of network synchronization is NOT within the scope of the WI

R1-2102035 FL Summary #3 for accuracy improvements by mitigating UE Rx/Tx and/or gNB Rx/Tx timing delays Moderator (CATT)

Agreement:

The following definitions are used for the purpose of discussion of internal timing errors (these terms are not agreed to be included in the specifications):

Tx timing error: From a signal transmission perspective, there will be a time delay from the time when the digital signal is generated at baseband to the time when the RF signal is transmitted from the Tx antenna. For supporting positioning, the UE/TRP may implement an internal calibration/compensation of the Tx time delay for the transmission of the DL PRS/UL SRS signals, which may also include the calibration/compensation of the relative time delay between different RF chains in the same TRP/UE. The compensation may also possibly consider the offset of the Tx antenna phase center to the physical antenna center. However, the calibration may not be perfect. The remaining Tx time delay after the calibration, or the uncalibrated Tx time delay is defined as Tx timing error.
Rx timing error: From a signal reception perspective, there will be a time delay from the time when the RF signal arrives at the Rx antenna to the time when the signal is digitized and time-stamped at the baseband. For supporting positioning, the UE/TRP may implement an internal calibration/compensation of the Rx time delay before it reports the measurements that are obtained from the DL PRS/UL SRS signals, which may also include the calibration/compensation of the relative time delay between different RF chains in the same TRP/UE. The compensation may also possibly consider the offset of the Rx antenna phase center to the physical antenna center. However, the calibration may not be perfect. The remaining Rx time delay after the calibration, or the uncalibrated Rx time delay is defined as Rx timing error.
UE Tx ‘timing error group’ (UE Tx TEG): A UE Tx TEG is associated with the transmissions of one or more UL SRS resources for the positioning purpose, which have the Tx timing errors within a certain margin.
TRP Tx ‘timing error group’ (TRP Tx TEG): A TRP Tx TEG is associated with the transmissions of one or more DL PRS resources, which have the Tx timing errors within a certain margin.
UE Rx ‘timing error group’ (UE Rx TEG): A UE Rx TEG is associated with one or more DL measurements, which have the Rx timing errors within a certain margin.
TRP Rx ‘timing error group’ (TRP Rx TEG): A TRP Rx TEG is associated with one or more UL measurements, which have the Rx timing errors within a margin.
UE RxTx ‘timing error group’ (UE RxTx TEG): A UE RxTx TEG is associated with one or more UE Rx-Tx time difference measurements, and one or more UL SRS resources for the positioning purpose, which have the ‘Rx timing errors+Tx timing errors’ within a certain margin.
TRP RxTx ‘timing error group’ (TRP RxTx TEG): A TRP RxTx TEG is associated with one or more gNB Rx-Tx time difference measurements and one or more DL PRS resources, which have the ‘Rx timing errors+Tx timing errors’ within a certain margin.

R1-2102122 FL Summary #4 for accuracy improvements by mitigating UE Rx/Tx and/or gNB Rx/Tx timing delays Moderator (CATT)

Conclusion:

Study the following options for mitigating TRP Tx timing errors and/or UE Rx timing errors for DL TDOA:

· Option 1:

o Support a TRP to provide the association information of DL PRS resources with Tx TEGs to LMF

· Option 2:

o Support LMF to provide the association information of DL PRS resources with Tx TEGs to UE for UE-based positioning

· Option 3:

o Support a TRP to provide the Tx timing errors per Tx TEG to LMF

· Option 4:

o Support LMF to provide the Tx timing errors per Tx TEG of TRP to a UE for UE-based positioning

· Option 5:

o Support a UE to provide the association information of RSTD measurements with UE Rx TEG(s) to LMF when the UE reports the RSTD measurements to LMF

· Option 6:

o Support LMF to provide Rx timing errors per Rx TEG to a UE for UE-based positioning

· Option7:

o Support a UE to provide Rx timing errors per Rx TEG to LMF for UE-assisted positioning

· Option 8:

o Support a TRP to provide the Tx timing error differences between Tx TEGs of the TRP to LMF

· Option 9:

o Support LMF to provide the Tx timing error differences between Tx TEGs of a TRP to a UE for UE-based positioning

· Option10:

o Support a UE to provide Rx timing error differences between Rx TEGs to LMF for UE-assisted positioning

· FFS: details of the signalling, procedures, and UE capability

· FFS: How the TEGs are determined by the UE or TRP (could be by implementation, i.e., no specification impact)

· Note: Other options are not precluded.

· Note: Depending on the discussion results, none/one/multiple of the above options may be adopted in Rel-17.

Conclusion:

Study the following option(s) for mitigating UE Tx and TRP Rx timing errors for UL TDOA:

· Option 1:

o Support a TRP to provide the association information of RTOA measurements with Rx TEGs to LMF when the TRP reports the RTOA measurements

· Option 2:

o Support a UE to provide the association information of SRS resources for positioning with UE Tx TEG(s) to LMF for UL TDOA positioning.

· Option 3:

o Support a UE to provide Tx timing errors per Tx TEG to LMF for UL TDOA positioning.

· Option 4:

o Support a UE to provide Tx timing error differences between Tx TEGs to LMF for UL TDOA positioning.

· FFS: the details of the signalling, procedures, and UE capability

· FFS: How the TEGs are determined by the UE or TRP (could be by implementation, i.e., no specification impact)

· Note: Other options are not precluded.

· Note: Depending on the discussion results, none/one/multiple of the above options may be adopted in Rel-17.

Conclusion:

Study the following options for mitigating UE Rx/Tx timing errors in DL+UL positioning:

· Option 1:

o Support UE to provide the association information of UE Rx-Tx time difference measurements with UE Rx TEGs in the measurement report to LMF

· Option 2:

o Support UE to provide the association information of UE Rx-Tx time difference measurements with UE Tx TEGs in the measurement report to LMF

· Option 3:

o Combination of Option 1 and Option 2;

· Option 4:

o Support UE to provide the association information of UE Rx-Tx time difference measurements with UE RxTx TEGs in a measurement report to LMF for multi-RTT positioning

§ FFS: the definition of UE RxTxTEG. It includes both UE Rx timing and Tx timing errors.

· Option 5:

o Support UE to provide the association information of DL-RSTD measurements with UE RxTx TEGs in a measurement report to LMF for simultaneous DL-TDOA and UL-TDOA configuration for positioning

· Option 6:

o Support UE to provide the timing errors per Rx/Tx TEG, or the timing error differences between the Tx/Rx TEGs to LMF

· Option 7:

o Support UE to provide the timing errors per RxTx TEG, or the Tx timing error differences between the RxTx TEGs to LMF

· FFS: the details of signaling, procedures and UE capability

· FFS: How the TEGs are determined by the UE or TRP (could be by implementation, i.e., no specification impact)

· Note: Other options are not precluded.

· Note: Depending on the discussion results, none/one/multiple of the above options may be adopted in Rel-17.

Conclusion:

Study the following options for mitigating gNB Rx/Tx timing errors in DL+UL positioning:

· Option 1:

o Support TRP to provide the association information of gNB Rx-Tx time difference measurements with TRP Rx TEGs in the measurement report to LMF

· Option 2:

o Support TRP to provide the association information of gNB Rx-Tx time difference measurements with TRP Tx TEGs in the measurement report to LMF

· Option 3:

o Combination of Option 1 and Option 2;

· Option 4:

o Support TRP to provide the association information of gNB Rx-Tx time difference measurements with TRP RxTx TEGs in a measurement report to LMF for multi-RTT positioning

· Option 5:

o Support TRP to provide the timing errors per Rx/Tx TEG, or the timing error differences between the Tx/Rx TEGs to LMF

· Option 6:

o Support TRP to provide the timing errors per RxTx TEG, or the Tx timing error differences between the RxTx TEGs to LMF

· FFS: the details of signalling and procedures

· FFS: How the TEGs are determined by the UE or TRP (could be by implementation, i.e., no specification impact)

· Note: Other options are not precluded.

· Note: Depending on the discussion results, none/one/multiple of the above options may be adopted in Rel-17.

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

Agreement:

Support enabling

· A UE to report one or more measurement instances (of RSTD, DL RSRP, and/or UE Rx-Tx time difference measurements) in a single measurement report to LMF for UE-assisted positioning, and

· A TRP to report one or more measurement instances (of RTOA, UL RSRP, and/or gNB Rx-Tx time difference measurements) in a single measurement report to LMF, and

· Each measurement instance is reported with its own timestamp

· FFS: The measurement instances are within a [configured] measurement time window

· FFS: Each UE measurement instance can be configured with N instances of the DL-PRS Resource Set

· FFS: N (including N=1)

· FFS: Each TRP measurement instance can be configured with M SRS measurement time occasions

· FFS: M (including M=1)

· FFS: details of signalling, procedures, and UE capability if any

· FFS: whether and how to consider the additional enhancement related to measurement reporting of multi-paths and quality metric

· Note 1: A measurement instance refers to one or more measurements, which can either be the same or different types, which are obtained from the same DL PRS resource(s), or the same UL SRS resource(s).

· Note 2: This enhancement has no intention to change the mapping of measurement types to Rel-16 positioning techniques and no intention to introduce new positioning techniques either.

Final summary in R1-2102204.

8.5.2 Accuracy improvements for UL-AoA positioning solutions

R1-2100237 Enhancement for UL AoA positioning Huawei, HiSilicon

· Proposal 1: Introduce a calibration UE with the known location to mitigate the gNB angle error.

· Proposal 2: Support LMF assisted angle calibration.

· Proposal 3: Support enhanced angle measurement defined with respect to the ULA antenna direction.

· Proposal 4: Rel-17 should support angle information report associated with multi-paths.

· Proposal 5: Support UL AoA enhancement for TRPs with the antenna element spacing larger than a half wavelength.

Decision: The document is noted.

R1-2100863 Discussion on accuracy improvements for UL-AoA positioning method Sony

· Proposal 1: Introduce uncertainty of the AoA (uAoA) parameter in the UL-AoA measurement report from gNB to the Location Server (LS).

· Proposal 2: Introduce SRS resource ID information of the associated AoA / SRS-RSRP measurement in the UL-AoA measurement report from gNB to LS.

Decision: The document is noted.

R1-2100129 Enhancements for UL AoA Positioning OPPO

R1-2100294 Accuracy improvement for UL-AoA positioning solutions ZTE

R1-2100386 Discussion on accuracy improvements for UL-AoA positioning solutions CATT

R1-2100446 Discussion on potential enhancements for UL-AoA method vivo

R1-2100488 Discussion on improving the accuracy of UL AoA positioning solutions FUTUREWEI

R1-2100497 Accuracy improvements for UL-AoA positioning solutions BUPT

R1-2100549 Initial views on enhancing UL AoA Nokia, Nokia Shanghai Bell

R1-2100658 NR positioning enhancements for UL-AoA method Intel Corporation

R1-2100659 NR positioning enhancements for DL-AoD method Intel Corporation

R1-2100709 Discussion on accuracy improvement for UL-AoA positioning LG Electronics

R1-2100753 Discussions on techniques to improve accuracy for UL-AoA positioning solutions InterDigital, Inc.

R1-2101047 Discussion on UL-AoA enhancement CMCC

R1-2101132 UL-AoA positioning enhancements Fraunhofer IIS, Fraunhofer HHI

R1-2101211 Discussion on accuracy improvements for UL-AoA positioning solutions Samsung

R1-2101388 Accuracy enhancements for DL-AoD positioning technique Apple

R1-2101469 Potential Enhancements on UL-AOA positioning Qualcomm Incorporated

R1-2101617 Discussion on UL-AoA positioning enhancements NTT DOCOMO, INC.

R1-2101755 Enhancements of UL-AoA positioning solutions Ericsson

[104-e-NR-ePos-02] – Alexey (Intel)

Email discussion/approval on accuracy improvements for UL-AoA positioning solutions with checkpoints for agreements on Jan-28, Feb-02, Feb-05

R1-2101859 Feature Lead Summary #1 for NR Positioning UL-AoA Enhancements Moderator (Intel Corporation)

R1-2101860 Feature Lead Summary #2 for NR Positioning UL-AoA Enhancements Moderator (Intel Corporation)

R1-2102036 Feature Lead Summary #3 for NR Positioning UL-AoA Enhancements Moderator (Intel Corporation)

Agreement:

NR supports at least the following additional assistance signaling from LMF to gNB/TRP to facilitate UL measurements of UL-AOA

Indication of expected AoA/ZoA value and uncertainty (of the expected AoA/ZoA value) range(s)
FFS: Details of procedure for providing the assistance
FFS: Reference angle of expected AoA/ZoA

Agreement:

Further study which option is used to potentially enhance signaling of UL-AOA measurement report in case of a linear array antenna

· Option 1: gNB reports UL-AOA measurement which is a function of the actual azimuth and zenith angles of arrival in a given coordinate system

· Option 2: The z-axis of LCS is defined along the linear array axis. gNB reports only the ZoA relative to z-axis in the LCS, and the LCS-to-GCS translation function is used to set up the specific z-axis direction

Other options are not precluded from the study

R1-2102046 Feature Lead Summary #4 for NR Positioning UL-AoA Enhancements Moderator (Intel Corporation)

Agreement:

NR supports reporting of M > 1 UL-AOA (AoA/ZoA) measurement values by gNB to the LMF at least for the first arrival path

FFS: Supporting of UL-AOA measurements for additional paths
FFS: Supporting of N >= 1 UL-AOA values per path for additional paths
FFS: Whether the multiple values can correspond to the same time stamp.

FFS: Further details of measurement and reporting
Note: The reporting by gNB to the LMF is optional

8.5.3 Accuracy improvements for DL-AoD positioning solutions

Including UE-based and network-based (including UE-assisted) positioning solutions

R1-2100130 Enhancements for DL-AoD positioning OPPO

· Proposal 1: To enhance the performance of DL AoD, support UE-specific beam refinement on DL PRS resource for DL-AoD measurement.

· Proposal 2: In DL-AoD UE measurement reporting, support the UE to report the RSRP of a few DL PRS resources carrying adjacent Tx beam directions.

· Proposal 3: The UE uses the LOS path of one DL PRS resource to measure the RSRP measurement report for DL-AoD.

· Proposal 4: In DL-AoD measurement report, besides the RSRP measurement of DL PRS resources for each TRP, the UE also reports the relative time-of-arrival of those reported DL PRS resources of each TRP.

Decision: The document is noted.

R1-2100550 Initial views on enhancing DL AoD Nokia, Nokia Shanghai Bell

· Proposal 1: RAN1 to study beam orientation errors and potential correction mechanisms in order to improve the positioning accuracy achievable with DL-AoD. Including:

o UE-based positioning: the beam offset (BO) could be signaled to the UE, as either an indicator, e.g. low/medium/high, each specifying an error range or as a specific value computed by the network

o UE-assisted positioning: LMF should be aware of the BO and compensate for the errors when computing the position estimate.

o Signaling aspects:

§ LMF signals to TRPs that a BO recomputation and beam re-tuning is needed.

§ UE measurement reports to facilitate BO identification and potential correction.

· Proposal 2: Support timing based measurement and report for improving positioning accuracy of DL-AoD.

· Proposal 3: Study angle difference measurements for AoA of DL PRS resources in Rel-17.

Decision: The document is noted.

R1-2100238 Enhancement for DL AoD positioning Huawei, HiSilicon

R1-2100295 Accuracy improvements for DL-AoD positioning solutions ZTE

R1-2100387 Discussion on accuracy improvements for DL-AoD positioning solutions CATT

R1-2100447 Discussion on potential enhancements for DL-AoD method vivo

R1-2100489 Discussion on improving the accuracy of DL AoD positioning solutions FUTUREWEI

R1-2100710 Discussion on accuracy improvement for DL-AoD positioning LG Electronics

R1-2100750 Accuracy improvements for DL-AoD positioning solutions InterDigital, Inc.

R1-2100864 Discussion on accuracy improvements for DL-AoD positioning method Sony

R1-2101048 Discussion on DL-AoD enhancement CMCC

R1-2101121 Accuracy improvements for DL-AoD positioning solutions Xiaomi

R1-2101133 DL-AoD positioning enhancements Fraunhofer IIS, Fraunhofer HHI

R1-2101141 Accuracy enhancement for DL-AOD technique MediaTek Inc.

R1-2101212 Accuracy improvements for DL-AoD positioning solutions Samsung

R1-2101389 Accuracy enhancements for UL-AoA positioning technique Apple

R1-2101470 Potential Enhancements on DL-AoD positioning Qualcomm Incorporated

R1-2101501 Potential DL-AoD Positioning Enhancements Lenovo, Motorola Mobility

R1-2101618 Discussion on DL-AoD positioning enhancements NTT DOCOMO, INC.

R1-2101756 Enhancements of DL-AoD positioning solutions Ericsson

[104-e-NR-ePos-03] – Florent (Ericsson)

Email discussion/approval on accuracy improvements for DL-AoD positioning solutions with checkpoints for agreements on Jan-28, Feb-02, Feb-05

R1-2101920 FL summary for AI 8.5.3 Accuracy improvements for DL-AoD positioning solutions Moderator (Ericsson)

R1-2102093 FL summary #3 for AI 8.5.3 Accuracy improvements for DL-AoD positioning solutions Moderator (Ericsson)

Agreement:

For UE-assisted DL AOD, select one of the following options for reporting of RSRP measurements per TRP

Option 1: Up to 8 measurements in a measurement report (as in release 16)
Option 2: Up to 8 measurements in a measurement report, for the same Rx beam index
Option 3: Up to N>=8 measurements

Note: Multiple measurements corresponding to different Rx Beam index may be reported for a given PRS resource.
FFS: value for N.

Agreement:

For both UE-based and UE-assisted DL-AOD study the following enhancements that enable the UE to measure and report (for UE-assisted) information related to the first arriving path

Option 1: Information corresponds to PRS-RSRP of the first arriving path
Option 2: Information corresponds to the angle of departure of the first arriving path
Option 3: Information corresponds to the arrival time of the first path
Option 4: Information corresponds to phase of the CIR corresponding to the first arriving path
Option 5: Information corresponds to received signal value (amplitude and phase of the channel estimated from the first path which can be achieved as a combination of option 1 and option 4) of the first arriving path

FFS: Reporting of additional path to the first arriving path.
FFS: Measurement definition details
FFS: additional assistance data to support these enhancements
FFS: how the “first path” is selected among PRS resources in a PRS resource set
Note 1: Supporting multiple options as well as none of the options above is not precluded.

Agreement:

For UE-assisted DL-AOD positioning method, study the following options to enable the UE to measure/report a PRS resource with an additional, adjacent PRS resources measurement/report:

Option 1: UE can be requested to measure and report on specific PRS resources
Option 2: Enhancing the assistance data to identify adjacent beams
Option 3: Enhancing the reporting to include the measurements of adjacent beams
FFS: Detailed signaling and procedure
FFS: How to define adjacent beams
Note: Depending on the discussion results, none/one/multiple of above options may be adopted in Rel-17

Final summary in R1-2102239.

8.5.44 Other

R1-2100131 Discussion on NR Positioning Enhancements OPPO

R1-2100296 Other accuracy enhancements for NR positioning ZTE

R1-2100388 Potential techniques for Rel-17 positioning enhancements CATT

R1-2100448 Discussion on idle and inactive states positioning vivo

R1-2100551 Additional views on positioning enhancements Nokia, Nokia Shanghai Bell

R1-2100711 Discussion on latency and efficiency enhancement for NR positioning LG Electronics

R1-2100751 Discussions on LOS/NLOS detection InterDigital, Inc.

R1-2101142 Solving the synchronization error by the combination of measurements for DL-TDOA and UL-TDOA MediaTek Inc.

R1-2101213 Discussion on differential beamforming for positioning enhancement Samsung

R1-2101252 Considerations on other enhancements for positioning accuracy Huawei, HiSilicon

R1-2101757 PRS with Cyclic shifts Ericsson

RAN1#104-bis-e

8.5 NR Positioning Enhancements

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

R1-2103982 Session notes for 8.5 (NR Positioning Enhancements) Ad-Hoc Chair (Ericsson)

R1-2103034 Work Plan for NR Positioning Enhancements Work Item Intel Corporation, CATT, Ericsson

8.5.1 Accuracy improvements by mitigating UE Rx/Tx and/or gNB Rx/Tx timing delays

Including DL, UL and DL+UL positioning methods, and UE-based and UE-assisted positioning solutions.

R1-2102348 Enhancement to mitigate gNB and UE Rx/Tx timing error Huawei, HiSilicon

R1-2102364 Accuracy improvements by mitigating UE Rx/Tx and/or gNB Rx/Tx timing delays BUPT

R1-2102399 Enhancement of timing-based positioning by mitigating UE Rx/Tx and/or gNB Rx/Tx timing delays OPPO

R1-2102526 Discussion on potential enhancements for RX/TX timing delay mitigating vivo

R1-2102635 Discussion on accuracy improvements by mitigating UE Rx/Tx and/or gNB Rx/Tx timing delays CATT

R1-2102668 Positioning accuracy improvement by mitigating timing delay ZTE

R1-2102869 Discussion on positioning enhancement by mitigating timing delays China Telecom

R1-2102886 Discussion on mitigation of gNB/UE Rx/Tx timing errors CMCC

R1-2103002 Views on mitigating UE and gNB Rx/Tx timing errors Nokia, Nokia Shanghai Bell

R1-2103005 Discussion on accuracy improvements by mitigating timing delays InterDigital, Inc.

R1-2103035 Mitigation of UE Rx/Tx and gNB Rx/Tx timing errors Intel Corporation

R1-2103109 Positioning accuracy enhancements under timing errors Apple

R1-2103170 Enhancements on Timing Error Mitigations for improved Accuracy Qualcomm Incorporated

R1-2103243 Accuracy improvements by mitigating UE Rx/Tx and/or gNB Rx/Tx timing delays Samsung

R1-2103306 Discussion on mitigating UE Rx/Tx and gNB Rx/Tx timing delays Sony

R1-2103372 Enhancements for mitigation of Tx/Rx Delays Lenovo, Motorola Mobility

R1-2103580 Discussion on mitigating UE and gNB Rx/Tx timing delays NTT DOCOMO, INC.

R1-2103600 Mitigation of RX/TX timing delays for higher accuracy MediaTek Inc.

R1-2103621 Discussion on accuracy improvement by mitigating UE Rx/Tx and gNB Rx/Tx timing delays LG Electronics

R1-2103681 On methods for Rx/Tx timing delays mitigation Fraunhofer IIS, Fraunhofer HHI

R1-2103682 Discussion on mitigation of Tx-Rx timing delays CEWiT, IITM, IITH

R1-2103771 Techniques mitigating Rx/Tx timing delays Ericsson (rev of R1-2103735)

R1-2103781 FL Summary for accuracy improvements by mitigating UE Rx/Tx and/or gNB Rx/Tx timing delays Moderator (CATT)

[104b-e-NR-ePos-01] – Ren Da (CATT)

Email discussion/approval on accuracy improvements by mitigating UE Rx/Tx and/or gNB Rx/Tx timing delays with checkpoints for agreements on Apr-15, Apr-20

R1-2103875 FL Summary #2 for accuracy improvements by mitigating UE Rx/Tx and/or gNB Rx/Tx timing delays Moderator (CATT)

R1-2103992 FL Summary #4 for accuracy improvements by mitigating UE Rx/Tx and/or gNB Rx/Tx timing delays Moderator (CATT)

Agreement:

· Support the following for mitigating TRP Tx timing errors and/or UE Rx timing errors for DL TDOA

o Support a UE to provide the association information of RSTD measurements with UE Rx TEG(s) to the LMF when the UE reports the RSTD measurements to the LMF if the UE has multiple TEGs

o Support a TRP providing the association information of DL PRS resources with Tx TEGs to the LMF if the TRP has multiple TEGs

o Support the LMF to provide the association information of DL PRS resources with Tx TEGs to a UE for UE-based positioning if the TRP has multiple TEGs

o FFS: the details of the signalling, procedures, and UE capability

· Send an LS to RAN4 to check if there is any issue to support the above enhancements

Agreement:

Support the following for mitigating UE Tx timing errors and/or TRP Rx timing errors for UL TDOA

· Support a TRP to provide the association information of RTOA measurements with TRP Rx TEG(s) to the LMF when the TRP reports the RTOA measurements to the LMF if the TRP has multiple Rx TEGs

· Support a UE to provide under capability the association information of UL SRS resources for positioning with Tx TEGs to the LMF if the UE has multiple Tx TEGs

o FFS: Whether to support a UE to provide the association information of UL SRS resources for MIMO with Tx TEGs to the LMF if the UE has multiple Tx TEGs

o FFS: Whether the association information is sent directly from UE to LMF, or is first provided to gNB and then forwarded to LMF

· FFS: the details of the Signaling, procedures, and UE capability

Agreement:

For mitigating UE/TRP Tx/Rx timing errors for DL+UL positioning, support one of the following alternatives:

· Alt.1: Support a UE to provide the association information of a UE Rx-Tx time difference measurement with a pair of {Rx TEG, Tx TEG} to LMF, where the Rx TEG is used to receive the DL PRS and the Tx TEG is used to transmit the UL Positioning SRS;

· Alt.2: Support a UE to provide the association information of a UE Rx-Tx time difference measurement with a UE RxTx TEG to LMF according to the one of the 2 following options:

o Option 1: the UE RxTx TEG is associated with one or more {DL PRS resource, UL Positioning SRS resource} pairs

§ FFS: whether UE provides the association information of DL PRS resources to UE Rx TEG to LMF for UE RxTx measurements specifically

o Option 2: the UE RxTx TEG is associated with one or more {Rx TEG, Tx TEG} pairs where the Rx TEG is used to receive the DL PRS and the Tx TEG is used to transmit the UL Positioning SRS.

· For both alterntives, the UE may provide the association information of SRS resources for positioning to UE Tx TEG to LMF

o FFS: Whether the association information is sent directly from UE to LMF, or is first provided to gNB and then forwarded to LMF

· FFS: the details of the signalling, procedures, and UE capability

Agreement:

· For mitigating UE/TRP Tx/Rx timing errors for DL+UL positioning, support one of the following alternatives:

o Alt.1: Support a gNB to provide the association information of a gNB Rx-Tx time difference measurement with a pair of {Rx TEG, Tx TEG} to LMF

o Alt. 2: Support a gNB to provide the association information of a gNB Rx-Tx time difference measurement with a TRP RxTx TEG to LMF, if the TRP has multiple RxTx TEGs, according to the one of the 2 following options:

§ Option 1: the TRP RxTx TEG is associated with one or more {DL PRS resource, UL Positioning SRS resource} pairs

· FFS: whether gNB provides the association information of UL Positioning SRS resources to TRP Rx TEG to LMF, if the TRP has multiple Rx TEGs, for gNB RxTx measurements specifically

§ Option 2: the TRP RxTx TEG is associated with one or more {Rx TEG, Tx TEG} pairs where the Rx TEG is used to receive the UL Positioning SRS and the Tx TEG is used to transmit the DL PRS.

o For both alternatives, the gNB may provide the association information of DL PRS resources to TRP Tx TEG to LMF if the TRP has multiple Tx TEGs.

· FFS: the details of the signalling, procedures

R1-2104053 [DRAFT] LS on UE/TRP Tx/Rx Timing Errors CATT

Decision: As per email decision posted on April 20^th, the draft LS is endorsed. Final version is approved in R1-2104111.

8.5.2 Accuracy improvements for UL-AoA positioning solutions

R1-2102400 Enhancements for UL AoA Positioning OPPO

R1-2102527 Discussion on potential enhancements for UL-AoA method vivo

R1-2102636 Discussion on accuracy improvements for UL-AoA positioning solutions CATT

R1-2102669 Accuracy improvement for UL-AoA positioning solutions ZTE

R1-2102784 Accuracy Improvement of UL-AoA Positioning FUTUREWEI

R1-2102887 Discussion on UL-AoA enhancements CMCC

R1-2103003 Views on enhancing UL AoA Nokia, Nokia Shanghai Bell

R1-2103006 Discussion on UL-AoA positioning solutions InterDigital, Inc.

R1-2103036 Enhancements of UL-AoA positioning solution Intel Corporation

R1-2103110 Accuracy enhancements for UL-AoA positioning technique Apple

R1-2103171 Potential Enhancements on UL-AOA positioning Qualcomm Incorporated

R1-2103244 Accuracy improvements for UL-AoA positioning solutions Samsung

R1-2103307 Discussion on accuracy improvements for UL-AoA positioning method Sony

R1-2103400 Enhancement for UL AoA positioning Huawei, HiSilicon

R1-2103581 Discussion on UL-AoA positioning enhancements NTT DOCOMO, INC.

R1-2103622 Discussion on accuracy improvement for UL-AoA positioning LG Electronics

R1-2103683 UL-AoA positioning enhancements Fraunhofer IIS, Fraunhofer HHI

R1-2103684 Discussion on potential enhancements for UL AoA positioning CEWiT, IITM, IITH

R1-2103736 Enhancements of UL-AoA positioning solutions Ericsson

[104b-e-NR-ePos-02] – Alexey (Intel)

Email discussion/approval on accuracy improvements for UL-AoA positioning solutions with checkpoints for agreements on Apr-15, Apr-20

R1-2103794 Feature Lead Summary #0 for Enhancements of UL-AOA Positioning Moderator (Intel)

R1-2103862 Feature Lead Summary #1 for Enhancements of UL-AOA Positioning Moderator (Intel)

R1-2103863 Feature Lead Summary #2 for Enhancements of UL-AOA Positioning Moderator (Intel)

Agreement:

· The following option is supported to enhance signaling of UL-AOA measurement report in case of a linear array

o Option 2: The z-axis of LCS is defined along the linear array axis. gNB reports only the ZoA relative to z-axis in the LCS, and the LCS-to-GCS translation function is used to set up the specific z-axis direction

· UL-AOA signalling details for support of Option 2 are left up to RAN WG3

Agreement:

· Uncertainty range for expected UL AoA/ZoA is defined as follows

o Expected azimuth angle of arrival as (φ_AOA - Δφ_AOA/2, φ_AOA + Δφ_AOA/2)

§ φ_AOA - expected azimuth angle of arrival, Δφ_AOA – uncertainty range for expected azimuth angle of arrival

o Expected zenith angle of arrival as (θ_AOA - Δθ_AOA/2, θ_AOA + Δθ_AOA/2)

§ θ_AOA - expected zenith angle of arrival, Δθ_AOA – uncertainty range for expected zenith angle of arrival

· Select one of the following coordinate system alternatives for signaling UL AoA/ZoA assistance information

o Alt.1: Only GCS is supported for AoA/ZoA assistance information indication

o Alt.2: Both GCS and LCS are supported for AoA/ZoA assistance information indication

· FFS: Additional signaling for AoA/ZoA assistance information (expected value and uncertainty range)

Agreement:

Reporting to LMF of M > 1 UL-AOA (AoA/ZoA) measurement values associated with the first arrival path and corresponding to the same timestamp is supported.

8.5.3 Accuracy improvements for DL-AoD positioning solutions

Including UE-based and network-based (including UE-assisted) positioning solutions

R1-2102401 Enhancements for DL-AoD positioning OPPO

R1-2102528 Discussion on potential enhancements for DL-AoD method vivo

R1-2102574 Discussion on enhancements for DL-AoD positioning CAICT

R1-2102637 Discussion on accuracy improvements for DL-AoD positioning solutions CATT

R1-2102670 Accuracy improvements for DL-AoD positioning solutions ZTE

R1-2102785 Accuracy Improvement of DL-AoD Positioning FUTUREWEI

R1-2102870 Disscussion on accuracy improvements for DL-AoD positioning method China Telecom

R1-2102888 Discussion on DL-AoD enhancements CMCC

R1-2102987 Accuracy improvements for DL-AoD positioning solutions Xiaomi

R1-2103004 Views on enhancing DL AoD Nokia, Nokia Shanghai Bell

R1-2103007 Discussion on DL-AoD positioning solutions InterDigital, Inc.

R1-2103037 Enhancements of DL-AoD positioning solution Intel Corporation

R1-2103111 Accuracy enhancements for DL-AoD positioning technique Apple

R1-2103172 Potential Enhancements on DL-AoD positioning Qualcomm Incorporated

R1-2103245 Accuracy improvements for DL-AoD positioning solutions Samsung

R1-2103308 Discussion on accuracy improvements for DL-AoD positioning method Sony

R1-2103373 DL-AoD Positioning Enhancements Lenovo, Motorola Mobility

R1-2103401 Enhancement for DL AoD positioning Huawei, HiSilicon

R1-2103582 Discussion on DL-AoD positioning enhancements NTT DOCOMO, INC.

R1-2103623 Discussion on accuracy improvement for DL-AoD positioning LG Electronics

R1-2103649 Accuracy enhancement for DL-AOD technique MediaTek Inc.

R1-2103685 DL-AoD positioning enhancements Fraunhofer IIS, Fraunhofer HHI

R1-2103686 Discussion on potential enhancements for DL-AoD positioning CEWiT, IITM, IITH

R1-2103737 Enhancements of DL-AoD positioning solutions Ericsson

[104b-e-NR-ePos-03] – Florent (Ericsson)

Email discussion/approval on accuracy improvements for DL-AoD positioning solutions with checkpoints for agreements on Apr-15, Apr-20

R1-2103865 FL summary #1 for AI 8.5.3 Accuracy improvements for DL-AoD positioning solutions Moderator (Ericsson)

R1-2103951 FL summary #2 for AI 8.5.3 Accuracy improvements for DL-AoD positioning solutions Moderator (Ericsson)

R1-2104047 FL summary #2 for AI 8.5.3 Accuracy improvements for DL-AoD positioning solutions Moderator (Ericsson)

Agreement:

Regarding support of angle calculation enhancement for DL-AoD:

· Support gNB providing the beam/antenna information to the LMF.

o The gNB beam/antenna information can be provided to the UE for UE-based DL-AoD

o FFS: the details of contents of the beam/antenna information

o FFS: the details of how to provide the beam/antenna information.

o Note: The antenna information is related to reducing the overhead of beam information

· Send an LS to RAN2/RAN3 regarding the option of angle report from gNB to LMF for UE-A DL-AoD requesting them to consider this option in Rel-17.

Agreement:

Support the following enhancements under UE capability for both UE-B and UE-A DL-AOD positioning method

Enhancing the signaling to UE for the purpose of PRS resource(s) measurement and (for UE-A) report

FFS: The detailed signaling (e.g, the boresight direction for UE-A DL-AoD, further spatial information of PRS resources, processing prioritization of PRS resources)

FFS: The following options

Option 1: Enhancing the reporting to include the measurements of adjacent beams PRS resources that related with each other indicated by the assistance data.
Option 2: UE can be requested to measure and report on specific PRS resources

Agreement:

For the purpose of both UE-B and UE-A DL-AoD, and with regards to the support of AOD measurements with an expected uncertainty window, study further whether to support at most one of the following options:

Option 1: Indication of expected DL-AoD/ZoD value and uncertainty (of the expected DL-AoD/ZoD value) range(s) is signaled by the LMF to the UE

Single Expected DL-AoD/ZoD and uncertainty (of the expected DL-AoD/ZoD value) range(s) can be provided to the UE for each [TRP]

Option 2: Indication of expected DL-AoA/ZoA value and uncertainty (of the expected DL-AoA/ZoA value) range(s) is signaled by the LMF to the UE

Single Expected DL-AoA/ZoA and uncertainty (of the expected DL-AoA/ZoA value) range(s) can be provided to the UE for each [TRP]

Option 3: Indication of expected AoD/ZoD or AoA/ZoA value and uncertainty is not introduced.

FFS: details of signaling

FFS: Applicability of this agreement to other Positioning methods

R1-2104088 [DRAFT] LS on DL-AoD angle calculation enhancement Ericsson

Decision: As per email decision posted on April 20^th, the draft LS is endorsed. Final version is approved in R1-2104089.

8.5.4 Latency improvements for both DL and DL+UL positioning methods

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

8.5.5 Potential enhancements of information reporting from UE and gNB for multipath/NLOS mitigation

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

8.5.66 Other

Including aspects for RAN2-led on-demand transmission and reception of DL PRS for DL and DL+UL positioning for UE-based and UE-assisted positioning solutions, and RAN2-led methods/measurements/signalling and procedures to support positioning for UEs in RRC_ INACTIVE state, for UE-based and UE-assisted positioning solutions

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

The following is not treated/withdrawn.

R1-2102802 Carrier Phase Based Positioning for NR DanKook University

RAN1#105-e

8.5 NR Positioning Enhancements

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

R1-2106232 Session notes for 8.5 (NR Positioning Enhancements) Ad-Hoc Chair (Ericsson)

[105-e-NR-ePos-LS-01] - Alex (Qualcomm)

Email discussion/approval for the reply LS to R1-2102306 till 5/25

R1-2106162 Email discussion/approval for the reply LS to R1-2102306 Moderator (Qualcomm)

R1-2106270 Draft reply LS to SA2 on Scheduling Location in Advance Qualcomm Incorporated

Decision: As per decision posted on May 27^th, the draft LS is endorsed. Final version is approved in R1-2106312.

8.5.1 Accuracy improvements by mitigating UE Rx/Tx and/or gNB Rx/Tx timing delays

Including DL, UL and DL+UL positioning methods, and UE-based and UE-assisted positioning solutions.

R1-2104277 Enhancement to mitigate gNB and UE Rx/Tx timing error Huawei, HiSilicon

R1-2104359 Discussion on potential enhancements for RX/TX timing delay mitigating vivo

R1-2104520 Discussion on accuracy improvements by mitigating UE Rx/Tx and/or gNB Rx/Tx timing delays CATT

R1-2104590 Positioning accuracy improvement by mitigating timing delay ZTE

R1-2104611 Discussion on mitigation of gNB/UE Rx/Tx timing errors CMCC

R1-2104671 Enhancements on Timing Error Mitigations for improved Accuracy Qualcomm Incorporated

R1-2104739 Enhancement of timing-based positioning by mitigating UE Rx/Tx and/or gNB Rx/Tx timing delays OPPO

R1-2104871 Discussion on accuracy improvements by mitigating timing delays InterDigital, Inc.

R1-2104905 Mitigation of UE/gNB TX/RX Timing Errors Intel Corporation

R1-2105105 Positioning accuracy enhancements under timing errors Apple

R1-2105168 Discussion on mitigating UE Rx/Tx and gNB Rx/Tx timing delays Sony

R1-2105310 Discussion on accuracy improvements by mitigating UE Rx/Tx and/or gNB Rx/Tx timing delays Samsung

R1-2105482 Discussion on accuracy improvement by mitigating UE Rx/Tx and gNB Rx/Tx timing delays LG Electronics

R1-2105512 Views on mitigating UE and gNB Rx/Tx timing errors Nokia, Nokia Shanghai Bell

R1-2105699 Discussion on mitigating UE and gNB Rx/Tx timing delays NTT DOCOMO, INC.

R1-2105759 Mitigation of RX/TX timing delays for higher accuracy MediaTek Inc.

R1-2105856 On methods for Rx/Tx timing delays mitigation Fraunhofer IIS, Fraunhofer HHI

R1-2105859 Enhancements for mitigation of Tx/Rx Delays Lenovo, Motorola Mobility

R1-2105908 Techniques mitigating Rx/Tx timing delays Ericsson

R1-2105967 FL Summary for accuracy improvements by mitigating UE Rx/Tx and/or gNB Rx/Tx timing delays Moderator (CATT)

[105-e-NR-ePos-01] – Ren Da (CATT)

Email discussion/approval on accuracy improvements by mitigating UE Rx/Tx and/or gNB Rx/Tx timing delays with checkpoints for agreements on May 25, May 27

R1-2106091 FL Summary#2 for accuracy improvements by mitigating UE Rx/Tx and/or gNB Rx/Tx timing delays Moderator (CATT)

R1-2106156 FL Summary#3 for accuracy improvements by mitigating UE Rx/Tx and/or gNB Rx/Tx timing delays Moderator (CATT)

R1-2106259 FL Summary#4 for accuracy improvements by mitigating UE Rx/Tx and/or gNB Rx/Tx timing delays Moderator (CATT)

From GTW sessions:

Agreement:

· For mitigating UE Tx timing errors for UL TDOA, support one of the following options:

o Option 1:

§ Subject to UE’s capability, support a UE providing the association information of UL SRS resources for positioning with Tx TEGs directly to the LMF if the UE has multiple Tx TEGs.

§ FFS: Support LMF to forward the association information provided by the UE to the serving and neighboring gNBs

o Option 2:

§ Subject to UE’s capability, support a UE providing the association information of UL SRS resources for positioning with Tx TEGs to the serving gNB if the UE has multiple Tx TEGs.

§ Support the serving gNB to forward the association information provided by the UE to the LMF

§ FFS: Support LMF to forward the association information from the serving gNB for the UE to the neighboring gNBs

· FFS: UE should be able to report capability information related to Tx TEGs to LMF via LPP signaling

· Support gNB to report the associated SRS resource ID/resource set ID of the RTOA measurement to LMF

Agreement:

Send an LS to RAN2/RAN3 (cc SA2), including the following content:

· RAN1 has evaluated the use of positioning reference units (PRUs) with known locations for positioning and observes improvements in using PRUs for enhancing the positioning performance. But, RAN1 has not identified specification enhancements needed in RAN1 specifications. RAN1 kindly requests RAN2/RAN3 (cc SA2) to determine if and what specification enhancements are adopted for PRUs for positioning.

Notes:

The term “positioning reference unit (PRU)” is only used as a terminology in this discussion. PRU does not necessarily mean an introduction of a new network node.
PRU may support, at least, some of the Rel-16 positioning functionalities of UE, if agreed, which is up to RAN2. The positioning functionalities may include, but not limited to, the following:

Provide the positioning measurements (e.g., RSTD, RSRP, Rx-Tx time differences)
Transmit the UL SRS signals for positioning

PRU may be requested by the LMF to provide its own known location coordinate information to the LMF. If the antenna orientation information of the PRU is known, the information may also be requested by the LMF.

R1-2106265 [Draft] LS on positioning reference unit (PRU) for enhancing the positioning performance CATT

Decision: As per decision posted on May 27^th, the draft LS is endorsed. Final version is approved in R1-2106326.

Agreement:

For mitigating UE Tx/Rx timing errors for DL+UL positioning, a UE may support, up to UE capability, one or both of the following options:

· Option 1: Reporting of UE RxTx TEG ID is supported by the UE

o FFS: Further details on how the RxTx TEG IDs are related/associated to Tx TEG IDs and/or Rx TEG IDs and to the Rx-Tx measurements.

· Option 2: Reporting of UE RxTx TEG ID is not supported by the UE; reporting of Rx TEG ID and Tx TEG ID is supported.

· In either option, a Tx TEG ID is associated with (downselection needed)

o Alt. 1: an UL SRS resource for positioning corresponding to the Tx timing of the Rx-Tx measurement

o Alt. 2: the Tx timing of the Rx-Tx measurement

o Alt. 3: one or more UL SRS resources for positioning

· Note: An Rx TEG ID is associated with one DL PRS resource (or more DL PRS resources) corresponding to the Rx time of the measurement

· FFS: How to resolve potential mismatch between UE and gNB Rx-Tx time difference measurements (e.g. UE provides the UE Rx-Tx measurements associated with a Tx TEG with SRS1, while gNB provides the gNB Rx-Tx measurements with a Rx TEG associated with SRS2).

· FFS: The potential impact and modification on the definition of Rx-Tx time difference measurements

Final summary in:

R1-2106339 FL Summary#5 for accuracy improvements by mitigating UE Rx/Tx and/or gNB Rx/Tx timing delays Moderator (CATT)

8.5.2 Accuracy improvements for UL-AoA positioning solutions

R1-2104278 Enhancement for UL AoA positioning Huawei, HiSilicon

R1-2104360 Discussion on potential enhancements for UL-AoA method vivo

R1-2104521 Discussion on accuracy improvements for UL-AoA positioning solutions CATT

R1-2104591 Accuracy improvement for UL-AoA positioning solutions ZTE

R1-2104612 Discussion on UL-AoA enhancements CMCC

R1-2104672 Potential Enhancements on UL-AOA positioning Qualcomm Incorporated

R1-2104740 Enhancements for UL AoA Positioning OPPO

R1-2104872 Discussion on enhancements for UL-AoA positioning solutions InterDigital, Inc.

R1-2104906 NR Positioning UL-AoA Enhancements Intel Corporation

R1-2105106 Positioning Accuracy enhancements for UL-AoA Apple

R1-2105169 Discussion on accuracy improvements for UL-AoA positioning method Sony

R1-2105311 Discussion on accuracy improvements for UL-AoA positioning solutions Samsung

R1-2105483 Discussion on accuracy improvement for UL-AoA positioning LG Electronics

R1-2105513 Views on enhancing UL AoA Nokia, Nokia Shanghai Bell

R1-2105658 Discussion on UL AoA positioning enhancements PML

R1-2105700 Discussion on UL-AoA positioning enhancements NTT DOCOMO, INC.

R1-2105857 UL-AoA positioning enhancements Fraunhofer IIS, Fraunhofer HHI

R1-2105909 Enhancements of UL-AoA positioning solutions Ericsson

[105-e-NR-ePos-02] – Alexey (Intel)

Email discussion/approval on accuracy improvements for UL-AoA positioning solutions and with lower priority any issues related to the Others section, with checkpoints for agreements on May 24, May 27

R1-2106021 Feature lead summary#0 for e-mail discussion [105-e-NR-ePos-02] Moderator (Intel Corporation)

R1-2106022 Feature lead summary#1 for e-mail discussion [105-e-NR-ePos-02] Moderator (Intel Corporation)

R1-2106023 Feature lead summary#2 for e-mail discussion [105-e-NR-ePos-02] Moderator (Intel Corporation)

From GTW sessions:

Agreement:

Both GCS and LCS are supported for UL AoA/ZoA assistance information indication.

Note: Existing signalling can be used for obtaining LCS to GCS translation information

Agreement:

Granularity of 0.1 degrees is applied for the expected AoA (φAOA), expected ZoA (θZOA ) and the corresponding uncertainty values

Agreement:

LMF to gNB signalling of UL AoA/ZoA assistance information (expected value and uncertainty range) is supported for UL-TDOA and Multi-RTT positioning methods

Agreement:

Send an LS to RAN3 (potentially also to RAN2 at least as cc) capturing RAN1 agreements on UL AOA/ZOA assistance information (expected value and uncertainty range) and request them to define signalling

R1-2106201 Draft LS on support of UL-AOA/ZOA assistance information signalling for NR positioning Intel Corporation

Decision: As per decision posted on May 27^th, the draft LS is endorsed. Final version is approved in R1-2106202.

MCC to correct the sourcing information to RAN1 only.

Agreement:

NR supports gNB reporting of the first arrival path UL-AOA/ZOA measurement per SRS for positioning resource and SRS for MIMO resource

Note: The use of SRS for MIMO resource is transparent to the UE

Final summary in:

R1-2106334 Feature lead summary#3 for e-mail discussion [105-e-NR-ePos-02] Moderator (Intel Corporation)

8.5.3 Accuracy improvements for DL-AoD positioning solutions

Including UE-based and network-based (including UE-assisted) positioning solutions

R1-2104228 Accuracy improvements for DL-AoD positioning solutions BUPT

R1-2104279 Enhancement for DL AoD positioning Huawei, HiSilicon

R1-2104361 Discussion on potential enhancements for DL-AoD method vivo

R1-2104522 Discussion on accuracy improvements for DL-AoD positioning solutions CATT

R1-2104592 Accuracy improvements for DL-AoD positioning solutions ZTE

R1-2104613 Discussion on DL-AoD enhancements CMCC

R1-2104673 Potential Enhancements on DL-AoD positioning Qualcomm Incorporated

R1-2104741 Enhancements for DL-AoD positioning OPPO

R1-2104842 Discussion on enhancements for DL-AoD positioning CAICT

R1-2104844 Carrier Phase Based Downlink Angle of Departure Measurement DanKook University

Late submission

R1-2104873 Discussion on enhancements for DL-AoD positioning solutions InterDigital, Inc.

R1-2104907 NR Positioning DL-AoD Enhancements Intel Corporation

R1-2105107 Positioning Accuracy enhancements for DL-AoD Apple

R1-2105170 Discussion on accuracy improvements for DL-AoD positioning method Sony

R1-2105312 Discussion on accuracy improvements for DL-AoD positioning solutions Samsung

R1-2105484 Discussion on accuracy improvement for DL-AoD positioning LG Electronics

R1-2105514 Views on enhancing DL AoD Nokia, Nokia Shanghai Bell

R1-2105563 Accuracy improvements for DL-AoD positioning solutions Xiaomi

R1-2105701 Discussion on DL-AoD positioning enhancements NTT DOCOMO, INC.

R1-2105858 DL-AoD positioning enhancements Fraunhofer IIS, Fraunhofer HHI

R1-2105860 DL-AoD Positioning Enhancements Lenovo, Motorola Mobility

R1-2105910 Enhancements of DL-AoD positioning solutions Ericsson

[105-e-NR-ePos-03] – Florent (Ericsson)

Email discussion/approval on accuracy improvements for DL-AoD positioning solutions with checkpoints for agreements on May 25, May 27

R1-2106079 FL summary #1 for AI 8.5.3 Accuracy improvements for DL-AoD positioning solutions Moderator (Ericsson)

R1-2106144 FL summary#2 for AI 8.5.3 Accuracy improvements for DL-AoD positioning solutions Moderator (Ericsson)

R1-2106255 FL summary#3 for AI 8.5.3 Accuracy improvements for DL-AoD positioning solutions Moderator (Ericsson)

From GTW sessions:

Agreement:

For both UE-based and UE-assisted DL-AOD, the UE can be requested subject to UE capability to measure and report (for UE-assisted) the PRS RSRP of the first path

FFS: Details of measurement and reporting of PRS RSRP of the first path

Agreement:

For UE-assisted DL-AOD positioning method, select one or more of the following to enhance the signalling to the UE for the purpose of PRS resource(s) measurement and reporting:

Option 1: the LMF explicitly identify adjacent beams in the assistance data (AD)
Option 2: the LMF send the beam information in the AD with an order of priority of PRS resources.
Option 3: the LMF includes boresight direction information for each PRS resource in the assistance data.
Option 4: the LMF send the beam information in the AD with indicated subset of PRS resources.
FFS: Detailed signalling and procedure
FFS: How to define adjacent beams

Agreement:

For the beam/antenna information to be optionally provided to the LMF by the gnodeB, select one or more of the following:

Option 1: the gNB reports the antenna configuration including at least the following parameter:

o the number of antenna elements (vertical and horizontal)

o antenna spacing dh and dv

o FFS: For DFT-based beams, precoder information for each PRS resource

§ Check whether the already reported boresight directions are sufficient, or whether more information is needed

o FFS: Antenna Element pattern Information

§ FFS: Details

o FFS: If additional information about panel/orientation is needed

· Option 2: the gNB reports a mapping of angle and beam gains for each of the PRS resources.

o FFS: representation of the mapping (e.g. parametric function approximating the beam response, or gain/angle table, beamwidth, intersection point of multiple beams (angle, RSRP)intersection point)

· Other options are not precluded

· In either option, the gNB beam/antenna information can optionally be provided to the UE by the LMF for UE-based DL-AoD

Agreement:

For both UE-based and UE-assisted DL methods, at least for two-stage PRS beam sweeping, study further at least the following:

Enhancements in the association between resources belonging to two DL PRS resource sets of the same TRP

Companies are encouraged to evaluate whether other potential enhancements in this subagenda or other subagendas (e.g. additional beam information, on-demand PRS framework) could be used to enable this feature (potentially by implementation).
Note: Two-stage PRS beam sweeping corresponds to different DL PRS resource sets

8.5.4 Latency improvements for both DL and DL+UL positioning methods

R1-2104280 Positioning latency enhancements Huawei, HiSilicon

R1-2104362 Discussion on latency enhancement for NR positioning vivo

R1-2104523 Discussion on latency improvements for both DL and DL+UL positioning methods CATT

R1-2104593 Discussion on latency reduction for NR positioning ZTE

R1-2104614 Discussion on latency improvement for positioning CMCC

R1-2104674 Enhancements for Latency Improvements for Positioning Qualcomm Incorporated

R1-2104742 Enhancements on Latency Reduction in NR Positioning OPPO

R1-2104874 Discussion on latency improvements for DL and DL+UL positioning methods InterDigital, Inc.

R1-2104908 NR Positioning Latency Reduction Intel Corporation

R1-2105108 Views on Rel-17 positioning latency reduction Apple

R1-2105171 Considerations on Latency Improvements for DL and DL+UL positioning methods Sony

R1-2105313 Discussion on latency improvements for both DL and DL+UL positioning methods Samsung

R1-2105485 Discussion on latency improvements for NR positioning LG Electronics

R1-2105515 Views on PHY Latency Reductions Nokia, Nokia Shanghai Bell

R1-2105564 Latency improvements for both DL and DL+UL positioning method Xiaomi

R1-2105760 Aspects for physical latency improvement MediaTek Inc.

R1-2105861 Positioning Latency Reduction Enhancements Lenovo, Motorola Mobility

R1-2105911 Latency improvements for both DL and DL+UL positioning methods Ericsson

[105-e-NR-ePos-04] – Su (Huawei)

Email discussion/approval on latency improvements for both DL and DL+UL positioning methods with checkpoints for agreements on May 24, May 27

R1-2105989 FL summary #1 of 8.5.4 latency improvements for DL and DL+UL methods Moderator (Huawei)

R1-2105990 FL summary #2 of 8.5.4 latency improvements for DL and DL+UL methods Moderator (Huawei)

R1-2105991 FL summary #3 of 8.5.4 latency improvements for DL and DL+UL methods Moderator (Huawei)

R1-2106183 FL summary #4 of 8.5.4 latency improvements for DL and DL+UL methods Moderator (Huawei)

From GTW sessions:

Agreement:

M-sample (1<=M<4) PRS processing corresponding to measurements performed within M instances of the DL PRS resource set on a PRS resource, subject to UE capability, is beneficial from a RAN1 perspective for latency reduction.

· One sample corresponds to one instance

· Send an LS to RAN4 informing that

o M-sample (1<=M<4) measurements corresponding to measurements performed within M (1<=M<4) instances of the DL PRS resource set on a PRS resource are beneficial for reduction of measurement latency from RAN1 point of view.

o RAN4 is requested to check the feasibility of measurements performed within M (1<=M<4) instances of the DL PRS resource set and identify the impact on requirements/side condition.

· RAN1 to further study at least the following aspects for allowing M-sample (1<=M<4) PRS processing

o Details of UE capability

o Signaling details, e.g., to indicate whether measurement is based on one or more samples

o Whether the PRS sample processing time is defined and the relation with (N, T).

§ Note: This may have RAN4 dependency

R1-2106184 [DRAFT] LS on PRS processing samples Moderator (Huawei)

Decision: As per decision posted on May 28^th, the draft LS is endorsed. Final version is approved in R1-2106185.

Agreement:

RAN1 to further study at least the following aspects for MG enhancement with regards to MG requesting and configuration/activation/triggering for the purpose of latency reduction for positioning:

· Preconfiguration of multiple MGs

· Triggering/activation of MG(s) with lower layer signalling (DCI or DL MAC CE)

· Request of MG(s) with lower layer signalling by the UE to the gNB

· Request/determination of MG(s) by LMF indication to the gNB/UE

· Note: The combination of the above items is possible.

Agreement:

· Further study the following options (with the same numerology) to support PRS measurement without MGs for latency reduction in Rel-17

o Option 1: The PRS is from the serving cell and UE measurement is inside the active DL BWP

o Option 2: The PRS can be from the serving cell and non-serving cell, and UE measurement is inside the active DL BWP

o Option 3: The PRS (from the serving cell or non-serving cell) used for UE measurement may extend outside or be completely outside the active DL BWP (including with potentially a different numerology)

o Note: RAN1 strives not to increase the PRS measurement time compared with Rel-16 MG-based measurement

· The following aspects are FFS

o PRS processing prioritization window

o Mechanism to trigger UE DL PRS measurements and report

o UE/gNB assumptions on processing of DL PRS and other DL physical channels / signals

o UE DL PRS processing capabilities

· Note: Companies are encouraged to compare the latency benefits of introducing MG-less PRS measurements over MG-based PRS measurements

· Note: Depending on the comparison of latency benefits (and other considerations such as complexity) between introducing MG-less PRS measurements and MG-based PRS measurements, none/one/multiple of the above options should be adopted in Rel-17.

Agreement:

Send an LS to RAN2 informing that

Ÿ From RAN1 perspective, it is beneficial to support a finer granularity for location response time in order to reduce latency.

Ÿ RAN2 is requested to check if it can be supported and design the signaling details if supported.

R1-2106315 [DRAFT] LS on granularity of response time Huawei

Decision: As per decision posted on May 28^th, the draft LS is endorsed. Final version is approved in R1-2106316.

8.5.5 Potential enhancements of information reporting from UE and gNB for multipath/NLOS mitigation

R1-2104198 NLOS Mitigation Enhancements FUTUREWEI

R1-2104281 Enhancements to support multi-path and NLOS mitigation Huawei, HiSilicon

R1-2104363 Discussion on potential enhancements for multipath/NLOS mitigation vivo

R1-2104524 Discussion on potential enhancements of information reporting from UE and gNB for multipath/NLOS mitigation CATT

R1-2104594 Enhancements on NLOS mitigation for NR positioning ZTE

R1-2104675 Multipath Reporting in NR Positioning Qualcomm Incorporated

R1-2104743 Discussion on multipath/NLOS mitigation for NR positioning OPPO

R1-2104856 Potential enhancements of information reporting from UE for multipath/NLOS mitigation China Telecom

R1-2104875 Discussion on multipath/NLOS mitigation for positioning InterDigital, Inc.

R1-2104909 Mitigation of NLOS Problem for NR Positioning Intel Corporation

R1-2105109 Views on potential enhancements for NLOS mitigation in Rel-17 positioning Apple

R1-2105172 Discussion on enhanced reporting from UE and gNB for Multipath/NLOS mitigation Sony

R1-2105314 Discussion on potential enhancements of information reporting from UE and gNB for multipath/NLOS mitigation Samsung

R1-2105486 Discussion on multipath/NLOS mitigation for positioning LG Electronics

R1-2105516 Views on LoS/NLoS Identification and Mitigation Nokia, Nokia Shanghai Bell

R1-2105565 Potential enhancements for multipath/NLOS mitigation Xiaomi

R1-2105702 Discussion on multipath/NLOS mitigation for NR positioning NTT DOCOMO, INC.

R1-2105862 Accuracy enhancements based on NLOS/Multipath Information Reporting Lenovo, Motorola Mobility

R1-2105865 Potential positioning enhancements for multipath/NLOS mitigation Fraunhofer IIS, Fraunhofer HHI

R1-2105912 Potential enhancements of information reporting from UE and gNB for multipath/NLOS mitigation Ericsson

[105-e-NR-ePos-05] – Ryan (Nokia)

Email discussion/approval on potential enhancements of information reporting from UE and gNB for multipath/NLOS mitigation with checkpoints for agreements on May 25, May 27

R1-2106043 Feature Lead Summary #1 for Potential multipath/NLOS mitigation Moderator (Nokia)

R1-2106087 Feature Lead Summary #2 for Potential multipath/NLOS mitigation Moderator (Nokia)

R1-2106163 Feature Lead Summary #3 for Potential multipath/NLOS mitigation Moderator (Nokia)

From GTW sessions:

Agreement:

· Study reporting of LoS/NLoS indicators for DL, UL, and DL+UL positioning measurements taken at both UE and TRP at least for UE assisted positioning.

· Study the following options (or combinations of the following options) for LoS/NLoS indicators

o Option 1: Binary (i.e., hard) value indicators

o Option 2: Soft value indicators (i.e., [0,1]).

§ FFS: Format and criteria for determination

o FFS: additional information or options

· FFS: LoS/NLoS indicators for UE-based positioning

Agreement:

· Study multipath reporting enhancements for DL, UL, and DL+UL positioning to enable LoS/NLoS/multipath identification and mitigation at the LMF for UE-assisted positioning.

o FFS: Details of the enhancements.

Agreement:

For multipath reporting enhancements, study reporting from TRP to LMF, angle, timing, phase (of additional paths) and power for the additional N paths (value of N is part of the study).

· Note: Companies are not obligated to provide inputs for all parameters in their study

Agreement:

For multipath reporting enhancements, study reporting from UE to LMF, relative timing of additional paths (additional to the first path) and the power (at least relative power) at least per DL PRS resource per additional path for at least DL-AoD reporting (the number of paths is part of the study).

Agreement:

· Study whether to support up to N>2 additional paths in the measurement reports from UE to LMF for at least DL-TDOA and multi-RTT,

o FFS: Exact value of N.

o FFS: reporting the power of the paths in addition to the timing.

o FFS: LMF requesting additional M non-distinct paths corresponding to the first path.

· Note 1: This agreement applies to N additional paths (i.e., not including the “first” path).

· Note 2: Rel-16 supports N=2 already.

Agreement:

As part of studying LoS/NLoS information reporting, study at least the following options for information to enable/assist LoS/NLoS detection:

· Option 1: Polarization information reporting from UE/gNB to LMF.

· Option 2: Coherence bandwidth information reporting from UE/gNB to LMF.

· Option 3: Propagation time difference information reporting from UE/gNB to LMF.

· Option 4: RSRP reporting from UE/gNB to LMF with finer granularity

· Option 5: Ricean factor and the variance of Channel Frequency Response (CFR) information reporting from UE/gNB to LMF

· Option 6: No specification impact outside of LoS/NLoS reporting

Note: Companies are encouraged to identify differences in information reporting and any performance gains compared with multipath information reporting

8.5.66 Other

Including aspects for RAN2-led on-demand transmission and reception of DL PRS for DL and DL+UL positioning for UE-based and UE-assisted positioning solutions, and RAN2-led methods/measurements/signalling and procedures to support positioning for UEs in RRC_ INACTIVE state, for UE-based and UE-assisted positioning solutions

R1-2104364 Discussion on inactive state positioning and on-demand PRS vivo

R1-2104525 Discussion on on-demand transmission and reception of DL PRS and positioning solutions for UEs in RRC_ INACTIVE state CATT

R1-2104595 Discussion on items led by RAN2 for NR positioning ZTE

R1-2104615 Discussion on NW/UE efficiency enhancements CMCC

R1-2104676 Enhancements Related to On Demand PRS And Positioning in RRC Inactive State Qualcomm Incorporated

R1-2104744 Discussion on positioning for UE in RRC_INACTIVE and on-demand PRS OPPO

R1-2104876 Discussion on on-demand PRS and INACTIVE mode positioning InterDigital, Inc.

R1-2104880 Carrier/Subcarrier Phase Based Enhancement for 5G NR Positioning DanKook University

Late submission

R1-2104910 Support of On-demand DL PRS and NR Positioning for UEs in RRC-INACTIVE state Intel Corporation

R1-2105315 Discussion on positioning in inactive state Samsung

R1-2105487 Discussion on other enhancements for positioning LG Electronics

R1-2105517 Additional views on Inactive Mode Positioning and on-demand PRS Nokia, Nokia Shanghai Bell

R1-2105534 Discussion on UL and DL+UL positioning in INACTIVE state Huawei, HiSilicon

R1-2105566 On-demand PRS and positioning for in-active state UE Xiaomi

R1-2105892 Potential physical layer impact to the RAN2-led topics MediaTek Inc.

R1-2105913 On-demand transmission and reception of DL PRS for DL and DL+UL positioning Ericsson

From GTW sessions:

Agreement:

Ÿ For potential signaling of one or more parameters (such signaling is not yet agreed) for both UE- and LMF- initiated on-demand DL PRS request, consider at least the following (all parameters will not necessarily be supported and all parameters may not be applicable to both UE-initiated and LMF-initiated on-demand DL PRS request)

o Start/end time of DL PRS transmission

o DL PRS resource bandwidth

o DL-PRS resource set IDs

o DL PRS resource IDs

o DL PRS transmission periodicity and offset

o DL PRS resource repetition factor

o Number of DL PRS symbols per DL PRS resource

o DL PRS muting patterns

o DL PRS QCL information

o Number of TRPs

o Number of PRS resources per PRS resource set

o Number frequency layers or frequency layer indicator

o Beam directions

o Combsize, start PRB, Point A of DL PRS

o ON/OFF indicator of the DL PRS

Ÿ FFS additional parameters indicated for UE and/or LMF initiated on-demand DL PRS request

Agreement:

NR positioning supports DL PRS-RSRP (section 5.1.28 in the TS 38.215) and DL RSTD (section 5.1.29 in the TS 38.215) measurements by UEs in RRC_INACTIVE state

FFS additional potential impact on RAN1

RAN1#106-e

8.5 NR Positioning Enhancements

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

R1-2108605 Session notes for 8.5 (NR Positioning Enhancements) Ad-Hoc Chair (Ericsson)

8.5.1 Accuracy improvements by mitigating UE Rx/Tx and/or gNB Rx/Tx timing delays

Including DL, UL and DL+UL positioning methods, and UE-based and UE-assisted positioning solutions.

R1-2106449 Enhancement to mitigate gNB and UE Rx/Tx timing error Huawei, HiSilicon

R1-2106549 Positioning accuracy improvement by mitigating timing delay ZTE

R1-2106595 Discussion on potential enhancements for RX/TX timing delay mitigating vivo

R1-2106809 On mitigating Rx/Tx timing delays Sony

R1-2106888 Discussion on accuracy improvements by mitigating UE Rx/Tx and/or gNB Rx/Tx timing delays Samsung

R1-2106971 Discussion on mitigating UE and gNB Rx/Tx timing errors CATT

R1-2107057 Views on mitigating UE and gNB Rx/Tx timing errors Nokia, Nokia Shanghai Bell

R1-2107213 Enhancement of timing-based positioning by mitigating UE Rx/Tx and/or gNB Rx/Tx timing delays OPPO

R1-2107345 Enhancements on Timing Error Mitigations for improved Accuracy Qualcomm Incorporated

R1-2107403 Discussion on mitigation of gNB/UE Rx/Tx timing errors CMCC

R1-2107542 Discussion on accuracy improvement by mitigating UE Rx/Tx and gNB Rx/Tx timing delays LG Electronics

R1-2107590 Details of UE/gNB RX/TX Timing Errors Mitigation Intel Corporation

R1-2107643 Discussion on accuracy improvements by mitigating timing delays InterDigital, Inc.

R1-2107740 Positioning accuracy enhancements under timing errors Apple

R1-2107822 Mitigation of RX/TX timing delays for higher accuracy MediaTek Inc.

R1-2107858 Discussion on mitigating UE and gNB Rx/Tx timing delays NTT DOCOMO, INC.

R1-2108101 On methods for Rx/Tx timing delays mitigation Fraunhofer IIS, Fraunhofer HHI

R1-2108142 Enhancements for mitigation of Tx/Rx Delays Lenovo, Motorola Mobility

R1-2108164 Techniques mitigating Rx/Tx timing delays Ericsson

[106-e-NR-ePos-01] – Ren Da (CATT)

Email discussion/approval on accuracy improvements by mitigating UE Rx/Tx and/or gNB Rx/Tx timing delays with checkpoints for agreements on August 19, 24 and 27

R1-2108241 FL Summary for accuracy improvements by mitigating UE Rx/Tx and/or gNB Rx/Tx timing delays Moderator (CATT)

Decision: From GTW session on Aug 16^th,

Agreement:

· Subject to UE capability, support a UE to include one UE Rx TEG ID for the RSTD reference time and one UE Rx TEG ID for each DL RSTD measurement (including each additional DL RSTD measurement), in a DL TDOA measurement report. These UE Rx TEG IDs can be the same or different.

· Note: RSTD reference time is related to the DL_PRS_Reference_Info IE

R1-2108242 FL Summary #2 for accuracy improvements by mitigating UE Rx/Tx and/or gNB Rx/Tx timing delays Moderator (CATT)

Decision: From GTW session on Aug 18^th,

Agreement:

Make the following modification of the previous agreement:

For mitigating UE Tx/Rx timing errors for DL+UL positioning, a UE ~~may~~ should support, up to UE capability, either one or both of the following options:

Option 1: Reporting of UE RxTx TEG ID ~~is supported~~ ~~by the UE~~

FFS: Further details on how the UE RxTx TEG IDs are related/associated to UE Tx TEG IDs and/or UE Rx TEG IDs and to the UE Rx-Tx measurements.

Option 2: Reporting of ~~UE RxTx TEG ID is not supported by the UE; reporting of~~ UE Rx TEG ID and UE Tx TEG ID ~~is supported~~.
In either option, a UE Tx TEG ID is associated with (downselection needed)

Alt. 1: an UL SRS resource for positioning corresponding to the Tx timing of the UE Rx-Tx measurement
Alt. 2: the Tx timing of the UE Rx-Tx measurement
Alt. 3: one or more UL SRS resources for positioning

Note: An UE Rx TEG ID is associated with one DL PRS resource (or more DL PRS resources) corresponding to the Rx time of the measurement
FFS: How to resolve potential mismatch between UE and gNB Rx-Tx time difference measurements (e.g. UE provides the UE Rx-Tx measurements associated with a Tx TEG with SRS1, while gNB provides the gNB Rx-Tx measurements with a Rx TEG associated with SRS2).
FFS: The potential impact and modification on the definition of Rx-Tx time difference measurements

Agreement:

· Subject to UE capability, support the LMF to request a UE to optionally measure the same DL PRS resource of a TRP with N different UE Rx TEGs and report the corresponding multiple RSTD measurements.

o FFS: N=[2, 3, 4] or other values, where the maximum value of N depends on UE capability.

o FFS: whether the TRP can be either a “RSTD” reference TRP or a neighbour TRP

o FFS: details of the signalling, procedures, and UE capability

o FFS: The multiple RSTD measurements can share the same time stamp

o Note: All RSTD measurements are relative to a single reference timing

· Support the LMF to request a TRP to optionally measure the same SRS resource of a UE with M different TRP Rx TEGs and report the corresponding multiple RTOA measurements.

o FFS: M = [2, 3, 4] or other values

o FFS: details of the signalling, procedures

o FFS: The multiple RTOA measurements can share the same time stamp

R1-2108243 FL Summary #3 for accuracy improvements by mitigating UE Rx/Tx and/or gNB Rx/Tx timing delays Moderator (CATT)

From GTW session:

Agreement:

· Consider supporting one of the following alternatives related to the UE Rx-Tx time difference (decision to be made in RAN1#106b):

o Option 1:

§ Subject to UE capability, the UE may report an additional UL Timestamp associated to a UE Rx-Tx measurement, corresponding to the timing of the uplink subframe of a positioning SRS.

§ Add the following to the UE Rx-Tx time difference definition (similar to the definition for HD-FDD UE in TS 36.214):

· If the UE does not transmit SRS in subframe #j, and if the UE reports an additional timestamp for the positioning SRS associated to the measurement, it shall compensate for the difference in the transmit timing of uplink subframe #j and the transmission timing of the subframe containing positioning SRS.

o Option 2:

§ Subject to a UE capability, a UE may optionally report Timing Adjustment (TA) change information

· Option 3A: The TA change information is included in the UE Tx TEG report

· Option 3B: The TA change information is included in the Rx-Tx measurement report

· Note: TA change information corresponds to: Tx Timing change with a timestamp that this change occurred.

o Option 3:

§ Subject to UE capability, the UE may report an additional UL Timestamp associated to a UE Rx-Tx measurement, corresponding to the timing of the uplink subframe of a positioning SRS.

§ Add the following to the UE Rx-Tx time difference definition (similar to the definition for HD-FDD UE in TS 36.214):

· If the UE does not transmit SRS in subframe #j, and if the UE reports an additional timestamp for the positioning SRS associated to the measurement, it is up to UE to compensate for the difference in the transmit timing of uplink subframe #j and the transmission timing of the subframe containing positioning SRS, or include the difference (Timing Adjustment change) without compensation within the report

o Other options are not precluded.

Agreement:

Consider the following options (both could be selected) until RAN1#106b-e

· Option 1: Support LMF to optionally indicate the measurement time window (MTW) for a UE for the measurement instances included in a measurement report.

· Option 2: Support LMF to optionally indicate the measurement time window for a gNB for the measurement instances included in a measurement report.

· FFS: the details of the MTW configuration.

· Any requirements can be discussed by RAN4 after decision on the options is made.

R1-2108244 FL Summary #4 for accuracy improvements by mitigating UE Rx/Tx and/or gNB Rx/Tx timing delays Moderator (CATT)

From GTW session:

Agreement:

If a Tx TEG ID is reported with a UE Rx-Tx time difference measurement, the UE should also report the association of the Tx TEG ID to the UL SRS resource(s)

FFS: how the the association of the Tx TEG ID to the UL SRS resource(s) is determined by UE.
FFS: details of the signalling

Agreement:

If a RxTx TEG ID is reported with a UE Rx-Tx time difference measurement, the UE may optionally also report a Tx TEG ID.

Final summary in R1-2108245.

8.5.2 Accuracy improvements for UL-AoA positioning solutions

R1-2106450 Enhancement for UL AoA positioning Huawei, HiSilicon

R1-2106550 Accuracy improvement for UL-AoA positioning solutions ZTE

R1-2106596 Discussion on potential enhancements for UL-AoA method vivo

R1-2106810 Considerations on UL-AoA enhancements Sony

R1-2106889 Discussion on accuracy improvements for UL-AoA positioning solutions Samsung

R1-2106972 Discussion on enhancements for UL-AoA positioning method CATT

R1-2107058 Views on enhancing UL AoA Nokia, Nokia Shanghai Bell

R1-2107214 Enhancements for UL AoA Positioning OPPO

R1-2107346 Potential Enhancements on UL-AOA positioning Qualcomm Incorporated

R1-2107404 Discussion on UL-AoA enhancements CMCC

R1-2107543 Discussion on accuracy improvement for UL-AoA positioning LG Electronics

R1-2107591 Remaining Details of NR Positioning UL-AoA Enhancements Intel Corporation

R1-2107645 Discussion on enhancements for UL-AoA positioning solutions InterDigital, Inc.

R1-2107741 Positioning Accuracy enhancements for UL-AoA Apple

R1-2107859 Discussion on UL-AoA positioning enhancements NTT DOCOMO, INC.

R1-2108102 UL-AoA positioning enhancements Fraunhofer IIS, Fraunhofer HHI

R1-2108165 Enhancements of UL-AoA positioning solutions Ericsson

R1-2108176 Discussion on enhancements for UL AoA positioning CEWiT

[106-e-NR-ePos-02] – Alexey (Intel)

Email discussion/approval on accuracy improvements for UL-AoA positioning solutions, with checkpoints for agreements on August 19, 24 and 27

R1-2108289 Feature Lead Summary#1 for E-mail Discussion [106-e-NR-ePos-02] Moderator (Intel)

Decision: From GTW session on Aug 18^th,

Agreement:

The maximum number of UL-AOAs values (pair of AOA & ZOA values) to be reported per SRS resource for the first arrival path corresponding to the same timestamp is 8.

Conclusion:

It is up to RAN3 to decide how to support indication of UL AoA/ZoA assistance information in LCS for LCS to GCS translation.

Decision: As per email decision posted on Aug 19^th,

Agreement:

Further study and conclude whether association of UL-AOA, UL-TDOA, Multi-RTT measurements with ARP (Antenna Reference Point) information is supported at RAN1#106bis-e.

R1-2108290 Feature Lead Summary#2 for E-mail Discussion [106-e-NR-ePos-02] Moderator (Intel Corporation)

Decision: From GTW session on Aug 20^th,

Agreement:

Reporting of one UL-RTOA and multiple UL-AOAs measurements for the first arrival path per SRS resource for positioning and per SRS resource for MIMO in a single gNB report to LMF is supported

The above measurements are associated with SRS resource ID which is also reported to LMF
FFS: Reporting of RSRP for the first arrival path
Note: The use of SRS for MIMO resource is transparent to the UE
FFS: Reporting of gNB Rx-Tx

Decision: As per email decision posted on Aug 25^th,

Agreement:

Reporting of one gNB Rx-Tx time difference and multiple UL-AOAs measurements for the first arrival path per SRS resource for positioning in a single gNB report to LMF is supported

The above measurements are associated with SRS resource ID which is also reported to LMF
FFS: Reporting of RSRP for the first arrival path

Final summary in R1-2108291.

8.5.3 Accuracy improvements for DL-AoD positioning solutions

Including UE-based and network-based (including UE-assisted) positioning solutions

R1-2106451 Enhancement for DL AoD positioning Huawei, HiSilicon

R1-2106551 Accuracy improvement for DL-AoD positioning solutions ZTE

R1-2106597 Discussion on potential enhancements for DL-AoD method vivo

R1-2106811 Considerations on DL-AoD enhancements Sony

R1-2106890 Discussion on accuracy improvements for DL-AoD positioning solutions Samsung

R1-2106973 Discussion on enhancements for DL-AoD positioning method CATT

R1-2107059 Views on enhancing DL AoD Nokia, Nokia Shanghai Bell

R1-2107169 Discussion on enhancements for DL-AoD positioning CAICT

R1-2107215 Enhancements for DL-AoD positioning OPPO

R1-2107347 Potential Enhancements on DL-AoD positioning Qualcomm Incorporated

R1-2107405 Discussion on DL-AoD enhancements CMCC

R1-2107544 Discussion on accuracy improvement for DL-AoD positioning LG Electronics

R1-2107592 DL-AoD Enhancements for Precise NR Positioning Intel Corporation

R1-2107646 Discussion on enhancements for DL-AoD positioning solutions InterDigital, Inc.

R1-2107742 Positioning Accuracy enhancements for DL-AoD Apple

R1-2107823 Accuracy enhancement for DL-AOD technique MediaTek Inc.

R1-2107860 Discussion on DL-AoD positioning enhancements NTT DOCOMO, INC.

R1-2107922 Accuracy improvements for DL-AoD positioning solutions Xiaomi

R1-2108103 DL-AoD positioning enhancements Fraunhofer IIS, Fraunhofer HHI

R1-2108143 Discussion on DL-AoD Positioning Enhancements Lenovo, Motorola Mobility

R1-2108166 Enhancements of DL-AoD positioning solutions Ericsson

R1-2108174 Discussion on enhancements for DL-AoD positioning CEWiT

[106-e-NR-ePos-03] – Florent (Ericsson)

Email discussion/approval on accuracy improvements for DL-AoD positioning solutions with checkpoints for agreements on August 19, 24 and 27

R1-2108311 FL summary #1 for AI 8.5.3 Accuracy improvements for DL-AoD positioning solutions Moderator (Ericsson)

R1-2108507 FL summary #2 for AI 8.5.3 Accuracy improvements for DL-AoD positioning solutions Moderator (Ericsson)

From GTW session on Aug 24^th,

Agreement:

For the beam/antenna information to be optionally provided to the LMF by the gnodeB, decide to support one of the following options:

· Option 2.1: The gNB reports quantized version of the relative Power/Angle response per PRS resource per TRP

o The relative power is defined with respect to the peak power of that resource

o FFS: How many relative power levels can be included (e.g., single -3 dB power-levels, multiple power-levels, etc).

· Option 2.2: The gNB reports quantized version of the relative Power between PRS resources per angle per TRP.

o The relative power is defined with respect to the peak power in each angle

o For each angle, at least two PRS resources are reported.

· FFS: support of multiple levels of quantization

· FFS: how the report is constructed

· FFS: overhead reduction mechanisms, including reusing of associated-dl-PRS-ID as a way of signaling that 2 TRPs have the same beam information

· The gNB beam/antenna information can optionally be provided to the UE by the LMF

· Note: Up to RAN2 & RAN3 the signaling/procedures on how the LMF receives this information from the gNBs

· Send an LS to RAN2 & RAN3 with this agreement

R1-2108577 FL summary #3 for AI 8.5.3 Accuracy improvements for DL-AoD positioning solutions Moderator (Ericsson)

Agreement:

For definition of the path PRS RSRP, consider the following options until RAN1#106b-e:

Option 1: the measured path PRS RSRP correspond to the power of the channel impulse response, at a certain path delay, over which the DL PRS is received.
Option 2: the path PRS RSRP correspond to the accumulated power of the channel impulse response over which the DL PRS is received, over a time duration corresponding to the given path delay

FFS: whether/how is the window conveyed to the UE (i.e., fixed in specification or configured in measurement request or determined by the UE)

FFS on relationship with the UE DL PRS measurement bandwidth.
FFS: normalization of the path RSRP measurement with DL PRS RSRP (i.e. RSRP for all path as defined in Rel-16) could be included in the measurement definition.
FFS: Further details of the definition, e.g. definition of the certain path delay
Up to RAN4 to define any test/requirement for the measurement.

R1-2108623 FL summary #4 for AI 8.5.3 Accuracy improvements for DL-AoD positioning solutions Moderator (Ericsson)

Agreement:

· For UE-A DL-AOD, support reporting more than 8 DL PRS RSRP measurements per TRP.

o Note: Multiple RSRPs corresponding to same or different Rx Beam index should be able to be reported for a given PRS resource for different timestamps.

· FFS: Limit the maximum number of DL PRS RSRP associated with the same Rx beam index

R1-2108645 [DRAFT] LS on beam/antenna information for DL AOD in NR positioning Moderator (Ericsson)

Decision: As per email decision posted on Aug 27^th, the draft LS is endorsed. Final LS is approved in R1-2108646.

8.5.4 Latency improvements for both DL and DL+UL positioning methods

R1-2106452 Positioning latency enhancements Huawei, HiSilicon

R1-2106552 Discussion on latency reduction for NR positioning ZTE

R1-2106598 Discussion on latency enhancement for NR positioning vivo

R1-2106812 Considerations on latency improvements for positioning Sony

R1-2106891 Discussion on latency improvements for both DL and DL+UL positioning methods Samsung

R1-2106974 Discussion on latency reduction for NR positioning CATT

R1-2107060 Views on PHY Latency Reductions Nokia, Nokia Shanghai Bell

R1-2107134 Discussion on latency improvements for positioning methods China Telecom

R1-2107216 Enhancements on Latency Reduction in NR Positioning OPPO

R1-2107348 Enhancements for Latency Improvements for Positioning Qualcomm Incorporated

R1-2107406 Discussion on latency improvement for positioning CMCC

R1-2107545 Discussion on latency improvements for NR positioning LG Electronics

R1-2107593 Latency Reduction Solutions for NR Positioning Intel Corporation

R1-2107647 Discussion on latency improvements for DL and DL+UL positioning methods InterDigital, Inc.

R1-2107743 Views on Rel-17 positioning latency reduction Apple

R1-2107828 Aspects of physical latency improvement MediaTek Inc.

R1-2107861 Discussion on latency improvements for both DL and DL+UL positioning methods NTT DOCOMO, INC.

R1-2107923 Latency improvements for both DL and DL+UL positioning method Xiaomi

R1-2108144 Positioning Latency Reduction Enhancements Lenovo, Motorola Mobility

R1-2108167 Latency improvements for both DL and DL+UL positioning methods Ericsson

[106-e-NR-ePos-04] – Su (Huawei)

Email discussion/approval on latency improvements for both DL and DL+UL positioning methods with checkpoints for agreements on August 19, 24 and 27

R1-2108248 FL summary #1 of 8.5.4 latency improvements for DL and DL+UL methods Moderator (Huawei)

From GTW session:

Agreement:

Subject to UE capability, support LMF to explicitly request UE to report the measurement with either M-sample or 4-sample, if RAN4 has supported M-sample measurement.

FFS signalling details.

Agreement:

For the purpose of positioning latency reduction, with potential support of a new mechanism of MG request, consider the following options with a decision to be made in RAN1#106b.

Option. 1: by LMF (via a NRPPa message)
Option. 2: by UE (via UCI or UL MAC CE)

Agreement:

For the purpose of positioning latency reduction, with potential support a new MG activation and deactivation procedure, consider the following options with a decision to be made in RAN1#106b (and RAN4 to be informed about any decision made)

Option. 1: DCI
Option. 2: DL MAC CE
Option. 3: UE autonomously applies the MG

FFS whether deactivation can be implicit via configurable number of the MG occasions

R1-2108249 FL summary #2 of 8.5.4 latency improvements for DL and DL+UL methods Moderator (Huawei)

R1-2108250 FL summary #3 of 8.5.4 latency improvements for DL and DL+UL methods Moderator (Huawei)

R1-2108583 FL summary #4 of 8.5.4 latency improvements for DL and DL+UL methods Moderator (Huawei)

From GTW session:

Working assumption:

Subject to UE capability, support PRS measurement outside the MG, within a PRS processing window, and UE measurement inside the active DL BWP with PRS having the same numerology as the active DL BWP.

Inside the PRS processing window, subject to the UE determining that DL PRS to be higher priority, support the following UE capabilities:

Capability 1: PRS prioritization over all other DL signals/channels in all symbols inside the window.

Cap. 1A: The DL signals/channels from all DL CCs (per UE) are affected.
Cap. 1B: Only the DL signals/channels from a certain band/CC are affected.

FFS: band or CC

Capability 2: PRS prioritization over other DL signals/channels only in the PRS symbols inside the window
A UE shall be able to declare a PRS processing capability outside MG.

FFS: Details of capability signalling (e.g., per UE or per band, etc.)

For the purpose of this feature, PRS-related conditions are expected to be specified, with the following to be down-selected:

Alt. 1: Applicable to serving cell PRS only
Alt. 2: Applicable to all PRS under conditions to PRS of non-serving cell.

Note: When the UE determines higher priority for other DL signals/channels over the PRS measurement/processing, the UE is not expected to measure/process DL PRS which is applicable to all of the above capability options.
Further study

Further details of which other DL signals/channels to be prioritized
How the UE determines DL PRS’s priority based on one or more of the following:

Opt. 1: Based on indication/configuration from serving gNB
Opt. 2: Other options (e.g., implicit, signalling from LMF, etc)

Whether UE can do the measurement for both inside MG (if MG is configured) and outside MG in a measurement period
How to do the PRS measurement when the conditions cannot be satisfied, e.g. when BWP switching happens
Prioritization conditions of processing PRS over other DL channels/signals or vice versa.

Send an LS to RAN2, RAN3 and RAN4 informing them of this working assumption and requesting feedback in case they have concerns.

R1-2108638 [DRAFT] LS on PRS measurement outside the measurement gap Moderator (Huawei)

Decision: As per email decision posted on Aug 27^th, the draft LS is endorsed. Final version is approved in R1-2108639.

8.5.5 Potential enhancements of information reporting from UE and gNB for multipath/NLOS mitigation

R1-2106453 Enhancements to support multi-path and NLOS mitigation Huawei, HiSilicon

R1-2106553 Enhancements on NLOS and Multi-path mitigation for NR positioning ZTE

R1-2106599 Discussion on potential enhancements for multipath/NLOS mitigation vivo

R1-2106813 Discussion on enhanced reporting for multipath/NLOS mitigation Sony

R1-2106892 Discussion on potential enhancements of information reporting from UE and gNB for multipath/NLOS mitigation Samsung

R1-2106975 Discussion on information reporting from UE and gNB for multipath/NLOS mitigation CATT

R1-2107061 Views on LoS/NLoS Identification and Mitigation Nokia, Nokia Shanghai Bell

R1-2107096 NLOS Mitigation Enhancements FUTUREWEI

R1-2107135 Discussion on multipath/NLOS identification and mitigation for positioning enhancement China Telecom

R1-2107217 Discussion on multipath/NLOS mitigation for NR positioning OPPO

R1-2107349 Multipath Reporting in NR Positioning Qualcomm Incorporated

R1-2107546 Discussion on multipath/NLOS mitigation for positioning LG Electronics

R1-2107594 Solutions for Mitigation of NLOS Problem for NR Positioning Intel Corporation

R1-2107648 Discussion on multipath/NLOS mitigation for positioning InterDigital, Inc.

R1-2107744 Views on potential enhancements for NLOS mitigation in Rel-17 positioning Apple

R1-2107862 Discussion on multipath/NLOS mitigation for NR positioning NTT DOCOMO, INC.

R1-2107924 Potential enhancements for multipath/NLOS mitigation Xiaomi

R1-2108104 Potential positioning enhancements for multipath/NLOS mitigation Fraunhofer IIS, Fraunhofer HHI

R1-2108145 Accuracy enhancements based on NLOS/Multipath Information Reporting Lenovo, Motorola Mobility

R1-2108168 Potential enhancements of information reporting from UE and gNB for multipath/NLOS mitigation Ericsson

R1-2108175 Discussion on enhancements of multipath/NLOS reporting from UE and gNB CEWiT

[106-e-NR-ePos-05] – Ryan (Nokia)

Email discussion/approval on potential enhancements of information reporting from UE and gNB for multipath/NLOS mitigation with checkpoints for agreements on August 19, 24 and 27

R1-2108280 Feature Lead Summary #1 for Potential multipath/NLOS mitigation Moderator (Nokia)

From GTW session:

Agreement:

· For up to N>2 additional paths, support reporting relative timing (to the first detected path) in the measurement reports from UE to LMF for at least DL-TDOA and multi-RTT

o FFS: Definition of additional paths for N>2

o FFS: Whether power is additionally reported and if reported whether power is relative to first detected path or total power

· Support one of the following options for maximum value of N at RAN1#106-b (any further criteria for selection to be discussed during RAN1#106):

o Option 1: N = 4

o Option 2: N = 8

o Option 3: N = 16

o Option 4: N = 32

Agreement:

· For multipath reporting enhancements, support reporting from TRP to LMF, angle, timing, for up to additional N>2 paths for at least UL-TDOA and multi-RTT.

o FFS: Definition of additional paths for N>2

o FFS: Whether power is additionally reported and if reported whether power is relative to first detected path or total power

· Down select between the following options for N at RAN1#106-b (any further criteria for selection to be discussed during RAN1#106):

o Option 1: N = 4

o Option 2: N = 8

o Option 3: N = 16

o Option 4: N = 32

R1-2108281 Feature Lead Summary #2 for Potential multipath/NLOS mitigation Moderator (Nokia)

From GTW session on Aug 24^th,

Agreement:

Support LoS/NLoS indicators which are reported to the LMF for DL and DL+UL positioning measurements taken at UE for UE-assisted positioning or UL and DL+UL measurements at the TRP for NG-RAN assisted positioning.

Reporting from UE is subject to UE capability

Positioning assistance data from LMF is enhanced for UE-based positioning by including LoS/NLoS indicators.
FFS: Other kinds of positioning assistance data enhancements
For LoS/NLoS detection method(s), there is no additional measurement IEs or assistance data outside of LoS/NloS indicator reporting (i.e., Option 6 from prior agreement).
Note 1: No RAN4 requirements are expected for the LoS/NLoS indicators in RAN1’s understanding
Note 2: LoS/NLoS indicators can be complementary to outlier rejection algorithms.

R1-2108282 Feature Lead Summary #3 for Potential multipath/NLOS mitigation Moderator (Nokia)

From GTW session:

Agreement:

Reporting multiple UL-AoA values per additional path is supported for at least UL TDOA and multi-RTT.

FFS: maximum number of UL-AoA values per additional path.

R1-2108629 Feature Lead Summary #4 for Potential multipath/NLOS mitigation Moderator (Nokia)

Agreement:

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

For LoS/NLoS indicators, a single-indicator can be reported and the supported values are a discrete set in the interval [0, 1].

· FFS: the number of discrete values to be supported

· Note: This does not preclude using binary values only which is up to UE/TRP implementation

· Note: Single-indicator means that one value in the interval [0, 1] is used for the LoS/NLoS indication

8.5.66 Other

R1-2106554 Discussion on items led by RAN2 for NR positioning ZTE

R1-2106600 Discussion on inactive state positioning and on-demand PRS vivo

R1-2106814 Considerations on positioning in RRC Inactive and on-demand PRS Sony

R1-2106893 Discussion on demand positioning and positioning in inactive state Samsung

R1-2106976 Discussion on on-demand DL PRS and positioning for UEs in RRC_ INACTIVE state CATT

R1-2107062 Additional views on Inactive Mode Positioning and on-demand PRS Nokia, Nokia Shanghai Bell

R1-2107170 Discussion on other enhancements for on-demand PRS and INACTIVE mode positioning CAICT

R1-2107218 Discussion on positioning for UE in RRC_INACTIVE and on-demand PRS OPPO

R1-2107350 Enhancements Related to On Demand PRS And Positioning in RRC Inactive State Qualcomm Incorporated

R1-2107407 Discussion on RAN2-led items for positioning CMCC

R1-2107595 On-demand DL PRS Signalling and NR Positioning for UEs in RRC-INACTIVE state Intel Corporation

R1-2107649 Discussion on on-demand PRS and INACTIVE mode positioning InterDigital, Inc.

R1-2107664 Discussion on RAN2 led objectives for NR positioning Huawei, HiSilicon

R1-2107830 Potential physical layer impact to the RAN2-led topics MediaTek Inc.

R1-2107831 Discussion on other enhancements for positioning LG Electronics

R1-2107863 Discussion on positioning for UEs in RRC_INACTIVE state NTT DOCOMO, INC.

R1-2107925 On-demand PRS and positioning for in-active state UE Xiaomi

R1-2108105 Considerations on SRS transmission for positioning in RRC_INACTIVE state Fraunhofer IIS, Fraunhofer HHI

R1-2108146 Discussion on On-Demand PRS and RRC_INACTIVE Positioning Lenovo, Motorola Mobility

R1-2108169 On-demand transmission and reception of DL PRS for DL and DL+UL positioning Ericsson

[106-e-NR-ePos-06] – Alexey (Intel)

Email discussion/approval on issues in the Others section including the LSs in R1-2106411 and R1-2106412 from AI5 and any reply LSs necessary, with checkpoints for agreements on August 19, 24 and 27

R1-2108292 Feature Lead Summary#1 for E-mail Discussion [106-e-NR-ePos-06] Moderator (Intel Corporation)

From GTW session on Aug 18^th:

Agreement:

· The following lists of on-demand DL-PRS parameters are discussed/prepared by RAN1 and provided as input to RAN2:

o List#1: List of parameters for UE-initiated on-demand DL PRS request

o List#2: List of parameters for LMF-initiated on-demand DL PRS request

· For the following lists of on-demand DL-PRS parameters, send an LS to RAN2 to check whether RAN2 would like RAN1 to send the list of parameters and request feedback as early as possible:

o List #3: List of parameters for UE-initiated on-demand DL PRS request associated with pre-configured set of on-demand DL PRS configurations

o List #4: List of parameters for LMF-initiated on-demand DL PRS request associated with pre-configured set of on-demand DL PRS configurations

R1-2108382 Draft LS to RAN2 with update on RAN1 discussion for on-demand DL PRS Moderator (Intel Corporation)

Decision: As per email decision posted on Aug 19^th, the draft LS is endorsed. Final LS is approved in R1-2108383.

R1-2108293 Feature Lead Summary#2 for E-mail Discussion [106-e-NR-ePos-06] Moderator (Intel Corporation)

From GTW session on Aug 24^th,

Agreement:

From RAN1 perspective, it is feasible to support transmission of SRS for positioning by UEs in RRC _INACTIVE state for UL and DL+UL positioning under certain validation criteria

· FFS: Type(s) of SRS for positioning (i.e., periodic, semi-persistent, aperiodic)

· FFS: Details of validation criteria which may also be discussed in RAN2

· Send LS to RAN2 informing them of this agreement

Agreement:

Open loop power control defined in Rel.16 for transmission of SRS for positioning by RRC_CONNECTED UEs is applicable for RRC_INACTIVE UEs.

Agreement:

Spatial relation defined in Rel.16 for transmission of SRS for positioning by RRC_CONNECTED UEs is applicable for RRC_INACTIVE UEs.

Conclusion:

It is up to RAN2 to define TA procedures for SRS for positioning transmission by RRC_INACTIVE UEs.

R1-2108563 Draft LS to RAN2 on SRS for Positioning Transmission by UEs in RRC_INACTIVE State Moderator (Intel Corporation)

Decision: As per email decision posted on Aug 26^th, the draft LS is endorsed. Final LS is approved in R1-2108564.

R1-2108294 Feature Lead Summary#3 for E-mail Discussion [106-e-NR-ePos-06] Moderator (Intel Corporation)

From GTW session:

Agreement:

At least the following list of on-demand DL PRS parameters is supported for UE-initiated and LMF-initiated on-demand DL PRS requests

1. DL PRS Periodicity

2. DL PRS resource bandwidth

3. DL PRS QCL information

Conclude on remaining parameters at RAN1#106-bis-e

//Handled under NWM – See RAN1-106-e-NWM-NR-ePos-07 as the document name

[106-e-NR-ePos-07] – Florent (Ericsson)

Email discussion/approval on LS in R1-2106435 from AI5 and any reply LS as necessary, with checkpoints for agreements until August 24^th.

R1-2106435 LS on determination of location estimates in local co-ordinates SA2, Ericsson

R1-2108508 Draft reply LS on determination of location estimates in local co-ordinates Moderator (Ericsson)

Decision: As per email decision posted on Aug 28^th, the draft LS is endorsed. Final LS is approved in R1-2108509.

RAN1#106-bis-e

8.5 NR Positioning Enhancements

Please refer to RP-210903 for detailed scope of the WI.

Incoming LS(s) related to this work/study item under agenda item 5: R1-2108696, R1-2108697, R1-2108706, R1-2108707, R1-2108711, R1-2108718, R1-2108698.

R1-2110614 Session notes for 8.5 (NR Positioning Enhancements) Ad-Hoc Chair (Ericsson)

[106bis-e-R17-RRC-NR-ePos] – Ren Da (CATT)

Email discussion on Rel-17 RRC parameters for positioning enhancement

- 1^st check point: October 14

- Final check point: October 19

R1-2110390 FL Summary #3 for Rel-17 RRC parameters for positioning enhancement Moderator (CATT)

Document is noted. For consolidation under 8 in [106bis-e-R17-RRC].

R1-2110690 Summary of RAN1 agreements for Rel-17 NR Positioning Enhancements WI rapporteur (CATT)

8.5.1 Accuracy improvements by mitigating UE Rx/Tx and/or gNB Rx/Tx timing delays

Including DL, UL and DL+UL positioning methods, and UE-based and UE-assisted positioning solutions.

R1-2108730 Remaining issues of mitigating Rx/Tx timing error Huawei, HiSilicon

R1-2108878 Positioning accuracy improvement by mitigating timing delay ZTE

R1-2108975 Discussion on potential enhancements for RX/TX timing delay mitigating vivo

R1-2109051 Enhancement of timing-based positioning by mitigating UE Rx/Tx and/or gNB Rx/Tx timing delays OPPO

R1-2109224 Further discussion on mitigating UE and gNB Rx/Tx timing errors CATT

R1-2109283 Discussion on mitigation of gNB/UE Rx/Tx timing errors CMCC

R1-2109363 Views on mitigating UE and gNB Rx/Tx timing errors Nokia, Nokia Shanghai Bell

R1-2109490 Discussion on accuracy improvements by mitigating UE Rx/Tx and/or gNB Rx/Tx timing delays Samsung

R1-2109611 Mitigation of UE and gNB RX/TX Timing Errors Intel Corporation

R1-2109679 Discussion on mitigating UE and gNB Rx/Tx timing delays NTT DOCOMO, INC.

R1-2109790 Discussion on mitigating Rx/Tx timing delays Sony

R1-2110035 Positioning accuracy enhancements under timing errors Apple

R1-2110088 Discussion on accuracy improvement by mitigating UE Rx/Tx and gNB Rx/Tx timing delays LG Electronics

R1-2110133 Discussion on accuracy improvements by mitigating timing delays InterDigital, Inc.

R1-2110187 Remaining Issues for Timing Error Mitigation for improved Accuracy Qualcomm Incorporated

R1-2110254 Mitigation of RX/TX timing delays for higher accuracy MediaTek Inc.

R1-2110298 Considerations for mitigation of Tx/Rx Delays Lenovo, Motorola Mobility

R1-2110349 Techniques mitigating Rx/Tx timing delays Ericsson

[106bis-e-NR-ePos-01] – Ren Da (CATT)

Email discussion/approval on accuracy improvements by mitigating UE Rx/Tx and/or gNB Rx/Tx timing delays with checkpoints for agreements on October 14 and 19

R1-2110391 FL Summary for accuracy improvements by mitigating UE Rx/Tx and/or gNB Rx/Tx timing delays Moderator (CATT)

R1-2110392 FL Summary #2 for accuracy improvements by mitigating UE Rx/Tx and/or gNB Rx/Tx timing delays Moderator (CATT)

From Oct 13^th GTW session

Working assumption:

· For mitigating UE Tx timing errors for UL TDOA, subject to UE’s capability, support the serving gNB to request a UE to provide the association information of UL SRS resources for positioning with Tx TEGs to the serving gNB if the UE supports multiple UE Tx TEGs for UL TDOA.

o The serving gNB should forward the association information provided by the UE to the LMF.

§ FFS: whether to support the serving gNB to forward the association information to the neighboring gNBs

o UE should report its capability of supporting multiple UE Tx TEGs for UL TDOA to serving gNB.

· For mitigating UE Tx timing errors for Multi-RTT, subject to UE’s capability, support the LMF to request a UE to provide the association information of UL SRS resources for positioning with Tx TEGs directly to the LMF if the UE supports multiple Tx TEGs for Multi-RTT.

o FFS: whether to support the LMF to forward the association information to the serving and neighboring gNBs

o UE should report its capability of supporting multiple UE Tx TEGs for Multi-RTT directly to the LMF.

· FFS: Mitigation of UE Tx timing errors when Multi-RTT, UL-TDOA and/or DL-TDOA are used.

Decision: As per email decision posted on Oct 15^th,

Agreement:

Make the following modification on the previous agreement made in RAN#106e:

o N=[2, 3, 4, 6, 8] (FFS: other values), where the maximum value of N depends on UE capability

o The TRP can be either a “RSTD” reference TRP or a neighbour TRP

o FFS: details of the signalling, procedures, and UE capability

o The timestamps of the multiple RSTD measurements in the same measurement report can be the same or different.

o Note: All RSTD measurements are relative to a single reference timing

· Support the LMF to request a TRP to optionally measure the same SRS resource of a UE with M different TRP Rx TEGs and report the corresponding multiple RTOA measurements.

o M = [2, 3, 4, 6, 8] (FFS: other values)

o FFS: details of the signalling, procedures

o The timestamps of the multiple RTOA measurements in the same measurement report can be the same or different.

R1-2110393 FL Summary #3 for accuracy improvements by mitigating UE Rx/Tx and/or gNB Rx/Tx timing delays Moderator (CATT)

From Oct 18^th GTW session

Agreement:

· For mitigating TRP Tx/Rx timing errors for DL+UL positioning, when a gNB reports a gNB Rx-Tx time difference measurement, the gNB can support either or both of the following options:

o Option 1: Reporting of a TRP RxTx TEG ID, and optionally a TRP Tx TEG ID

o Option 2: Reporting of a TRP Rx TEG ID and a TRP Tx TEG ID

o Note: The TRP Rx TEG ID is associated with one UL positioning SRS resource (or more UL positioning SRS resources) corresponding to the Rx time of the gNB Rx-Tx time difference measurement.

· If a TRP Tx TEG ID is reported with a gNB Rx-Tx time difference measurement, the gNB also reports the association of the TRP Tx TEG ID to the DL PRS resource(s) to the LMF under the condition that the TRP has more than one DL PRS resource.

o FFS: how the association of the Tx TEG ID to the DL PRS resource(s) is determined by the TRP and how the association is reported to the LMF.

o FFS: details of the signalling

R1-2110579 FL Summary #4 for accuracy improvements by mitigating UE Rx/Tx and/or gNB Rx/Tx timing delays Moderator (CATT)

Decision: As per email decision posted on Oct 20^th,

Agreement:

· Support the following parameters and values related to the accuracy enhancement for mitigating UE Rx/Tx and/or gNB Rx/Tx timing errors:

Parameter Description	Values in specifications (e.g., TS 37.355, TS 38.455)	Values that can be signaled as part of UE Capability	Comments
The maximum number of UE RxTEGs [for UE-assisted DL TDOA and/or Multi-RTT]	[32]	[1, 2,4,6,8,12,16,24,32] FFS: per UE/band /FL/FR	The parameter is used for supporting DL-TDOA and/or Multi-RTT
The maximum number of UE TxTEGs [for UL-TDOA and/or Multi-RTT]	[8]	[1, 2,4,6,8] FFS: per UE/band /FL/FR	The parameter is used for supporting UL-TDOA and/or Multi-RTT
The maximum number of UE-RxTx TEGs	[256]	[1, 2,4,6,8,12,16,24,32,64, 128, 256] FFS: per UE/band /FL/FR	The parameter is used for supporting Multi-RTT

· Note: Above proposal does not constrain in any way how features and feature sets are defined. The values in the table above may or may not be signalled to be different for different features or feature sets.

8.5.2 Accuracy improvements for UL-AoA positioning solutions

R1-2108731 Remaining issues of UL AoA enhancements Huawei, HiSilicon

R1-2108879 Accuracy improvement for UL-AoA positioning solutions ZTE

R1-2108976 Discussion on potential enhancements for UL-AoA method vivo

R1-2109052 Enhancements for UL AoA Positioning OPPO

R1-2109225 Further discussion on enhancements for UL-AoA positioning method CATT

R1-2109364 Views on enhancing UL AoA Nokia, Nokia Shanghai Bell

R1-2109491 Discussion on accuracy improvements for UL-AoA positioning solutions Samsung

R1-2109612 Remaining Aspects of NR Positioning UL-AoA Enhancements Intel Corporation

R1-2109680 Discussion on UL-AoA positioning enhancements NTT DOCOMO, INC.

R1-2109791 Considerations on enhancements for UL-AoA Sony

R1-2109863 TRP Rx-ARP information reporting Fraunhofer IIS, Fraunhofer HHI

R1-2110036 Positioning Accuracy enhancements for UL-AoA Apple

R1-2110089 Discussion on accuracy improvement for UL-AoA positioning LG Electronics

R1-2110134 Enhancements for UL-AoA positioning solutions InterDigital, Inc.

R1-2110188 Potential Enhancements on UL-AOA positioning Qualcomm Incorporated

R1-2110345 Discussion on enhancements for UL AoA positioning CEWiT

R1-2110350 Enhancements of UL-AoA positioning solutions Ericsson

[106bis-e-NR-ePos-02] – Alexey (Intel)

Email discussion/approval on accuracy improvements for UL-AoA positioning solutions, with checkpoints for agreements on October 14 and 19

R1-2110453 Feature Lead Summary#1 for E-mail Discussion [106bis-e-NR-ePos-02] Moderator (Intel Corporation)

From Oct 11^th GTW session

Agreement:

For the first arrival path measurements on SRS for positioning resource,

gNB can report to LMF the following set of measurements {one SRS-RSRP, multiple UL-AOAs (AoA/ZoA pairs), one UL-RTOA}
gNB can report to LMF the following set of measurements {one SRS-RSRP, multiple UL-AOAs (AoA/ZoA pairs), one-gNB Rx-Tx time difference}
FFS additional option: gNB can report to LMF the following set of measurements {multiple SRS-RSRP, multiple UL-AOAs (AoA/ZoA pairs), one UL-RTOA, one-gNB Rx-Tx time difference}
All gNB measurements above are associated with SRS resource ID and timestamp, which are also reported to LMF

For the first arrival path measurements on SRS for MIMO resource,

gNB can report to LMF the following set of measurements {one SRS-RSRP, multiple UL-AOAs (AoA/ZoA pairs), one UL-RTOA}
FFS: gNB can report to LMF the following set of measurements {multiple SRS-RSRP, multiple UL-AOAs (AoA/ZoA pairs), one UL-RTOA}
All gNB measurements above are associated with SRS resource ID and timestamp, which are also reported to LMF
Note: The operation of SRS for MIMO is transparent to the UE

R1-2110454 Feature Lead Summary#2 for E-mail Discussion [106bis-e-NR-ePos-02] Moderator (Intel Corporation)

From Oct 13^th GTW session

Agreement:

Association of UL-AOA positioning measurements with gNB ARP is supported in Rel.17.

Final summary in R1-2110455.

8.5.3 Accuracy improvements for DL-AoD positioning solutions

Including UE-based and network-based (including UE-assisted) positioning solutions.

R1-2108732 Remaining issues of DL AoD enhancements Huawei, HiSilicon

R1-2108880 Accuracy improvement for DL-AoD positioning solutions ZTE

R1-2108977 Discussion on potential enhancements for DL-AoD method vivo

R1-2109053 Enhancements for DL-AoD positioning OPPO

R1-2109226 Further discussion on enhancements for DL-AoD positioning method CATT

R1-2109284 Discussion on DL-AoD enhancements CMCC

R1-2109346 Discussion on enhancements for DL-AoD positioning CAICT

R1-2109365 Views on enhancing DL AoD Nokia, Nokia Shanghai Bell

R1-2109413 Accuracy improvements for DL-AoD positioning solutions Xiaomi

R1-2109492 Discussion on accuracy improvements for DL-AoD positioning solutions Samsung

R1-2109613 Solutions for NR Positioning DL-AoD Enhancements Intel Corporation

R1-2109681 Discussion on DL-AoD positioning enhancements NTT DOCOMO, INC.

R1-2109792 Considerations on enhancements for DL-AoD Sony

R1-2109864 DL-AoD positioning enhancements Fraunhofer IIS, Fraunhofer HHI

R1-2110037 Positioning Accuracy enhancements for DL-AoD Apple

R1-2110090 Discussion on accuracy improvement for DL-AoD positioning LG Electronics

R1-2110148 Enhancements for DL-AoD positioning solutions InterDigital, Inc.

R1-2110189 Remaining Issues on Potential Enhancements for DL-AoD positioning Qualcomm Incorporated

R1-2110256 Accuracy enhancement for DL-AOD technique MediaTek Inc.

R1-2110299 Discussion on DL-AoD Positioning Enhancements Lenovo, Motorola Mobility

R1-2110343 Discussion on enhancements for DL-AoD positioning CEWiT

R1-2110351 Enhancements of DL-AoD positioning solutions Ericsson

[106bis-e-NR-ePos-03] – Florent (Ericsson)

Email discussion/approval on accuracy improvements for DL-AoD positioning solutions with checkpoints for agreements on October 14 and 19

R1-2110460 FL summary #1 for AI 8.5.3 Accuracy improvements for DL-AoD positioning solutions Moderator (Ericsson)

R1-2110500 FL summary #2 for AI 8.5.3 Accuracy improvements for DL-AoD positioning solutions Moderator (Ericsson)

R1-2110578 FL summary #3 for AI 8.5.3 Accuracy improvements for DL-AoD positioning solutions Moderator (Ericsson)

From Oct 18^th GTW session

Agreement:

The measured path DL PRS RSRP for i^th path delay is defined as the power of the received DL PRS signal configured for the measurement at the i^th path delay of the channel response, and

path DL PRS RSRP for 1st path delay is the power corresponding to the first detected path
FFS: Whether the path RSRP measurement is normalized with PRS RSRP.
FFS: Whether the definition of the i^th path delay (other than i=1) is required.
Note: UE may choose to use a time window to compute path DL PRS RSRP by UE implementation (there is no impact to specifications managed by RAN1 for this)
Note: This does not imply that the path delay has to be reported in DL-AoD positioning
Send LS to RAN4 to check the details of the definition and feedback if they identify any update is necessary

Agreement:

The agreement from RAN1#106e on the number of DL PRS RSRP measurements per TRP is extended as follows:

For UE-A DL-AOD, support reporting ~~more than 8~~ up to 16 N DL PRS RSRP measurements per TRP, where N is UE capability and candidate values include {16,24}.
For UE-A DL-AOD, support reporting ~~more than 8~~ up to 16 M first path PRS RSRP measurements per TRP, where M is a UE capability

FFS: Values of M. Candidate values include {2,4,8,16,24}.
FFS: Whether M is always equal to N

Note: Multiple RSRPs corresponding to same or different Rx Beam index should be able to be reported for a given PRS resource for same or different timestamps.
Note: the maximum number of DL PRS RSRP associated with the same Rx beam index is up to the UE implementation

R1-2110626 [DRAFT] LS on definition of DL PRS path RSRP Moderator (Ericsson)

Decision: As per email decision poste on Oct 21^st, the draft LS is endorsed, assuming “Dates of next TSG RAN1 meeting” modified to “Dates of next TSG RAN WG1 meeting”. Final LS is approved in R1-2110627.

Final summary in R1-2110625.

8.5.4 Latency improvements for both DL and DL+UL positioning methods

R1-2108733 Enhancements to positioning latency improvements Huawei, HiSilicon

R1-2108881 Discussion on latency reduction for NR positioning ZTE

R1-2108978 Discussion on latency enhancement for NR positioning vivo

R1-2109054 Enhancements on Latency Reduction in NR Positioning OPPO

R1-2109227 Further discussion on latency reduction for NR positioning CATT

R1-2109255 Discussion on latency improvement for positioning methods China Telecom

R1-2109285 Discussion on latency improvement for positioning CMCC

R1-2109366 Views on PHY Latency Reductions Nokia, Nokia Shanghai Bell

R1-2109414 Latency improvements for both DL and DL+UL positioning method Xiaomi

R1-2109493 Discussion on latency improvements for both DL and DL+UL positioning methods Samsung

R1-2109614 Solutions for NR Positioning Latency Reduction Intel Corporation

R1-2109682 Discussion on latency improvements for both DL and DL+UL positioning methods NTT DOCOMO, INC.

R1-2109793 Considerations on latency improvements for NR positioning Sony

R1-2110038 Views on Rel-17 positioning latency reduction Apple

R1-2110091 Discussion on latency improvements for NR positioning LG Electronics

R1-2110149 Latency improvements for both DL and DL+UL positioning methods InterDigital, Inc.

R1-2110190 Remaining issues on Latency Improvements for Positioning Qualcomm Incorporated

R1-2110257 Physical latency improvement aspects MediaTek Inc.

R1-2110300 Enhancements for Positioning Latency Reduction Lenovo, Motorola Mobility

R1-2110352 Latency improvements for both DL and DL+UL positioning methods Ericsson

[106bis-e-NR-ePos-04] – Su (Huawei)

Email discussion/approval on latency improvements for both DL and DL+UL positioning methods with checkpoints for agreements on October 14 and 19

R1-2110445 FL summary #1 of 8.5.4 latency improvements for DL and DL+UL methods Moderator (Huawei)

R1-2110446 FL summary #2 of 8.5.4 latency improvements for DL and DL+UL methods Moderator (Huawei)

From Oct 13^th GTW session

Agreement:

Support the following options (in the agreement made in RAN1#106-e) for a new mechanism of MG activation request for the purpose of positioning.

Option 2: by UE (via UCI or UL MAC CE)

Select only one of UCI and UL MAC CE in RAN1#106bis-e

Option 1: by LMF (via an NRPPa message)

Note: This is transparent to the UE

Decision: As per email decision posted on Oct 17^th,

Conclusion:

Potential enhancements to latency reduction with respect to MG sharing with other RRM procedures is up to RAN4 to decide.

R1-2110447 FL summary #3 of 8.5.4 latency improvements for DL and DL+UL methods Moderator (Huawei)

From Oct 18^th GTW session

Agreement:

For PRS measurement outside MG, support the following Alt. 2 in the working assumption made in RAN1#106-e with the following update of the PRS cell condition.

· Alt. 2: Applicable to all PRS (serving and/or non-serving cell) under conditions to PRS of non-serving cell.

o The conditions at least include that the Rx timing difference between PRS from the non-serving cell and that from the serving cell is within a threshold

§ The UE is not expected to determine whether the above condition is satisfied by performing measurements and instead can be determined using assistance data

· FFS: Rx timing difference between PRS from the non-serving cell and that from the serving cell is determined by the expected RSTD and expected RSTD uncertainty.

o Further discuss the necessity on the following additional conditions

§ When the PRS is higher priority than other channels/signals, for capability 1A and 1B, the PRS from the non-serving cell have to be inside the PRS prioritization window.

§ When the PRS is higher priority than other channels/signals, for capability 2, the PRS from the non-serving cell have to be in the same symbols as the PRS of the serving cell since the serving cell does not know the symbol position of neighbour cell PRS.

Agreement:

With regards to UE determining the PRS priority with other DL signal/channels within the PRS processing window for PRS measurement outside MG, support the priority indicated by gNB.

FFS: What are the other DL signals/channels

With regards to the PRS processing window for PRS measurement outside MG, at least support the window indicated by gNB.

Decision: As per email decision posted on Oct 20^th,

Agreement:

For the PRS processing sample number M, at least M = 1 is supported.

Agreement:

Introduce a new UE capability on lower Rx beam sweeping factor (<8) to reduce the PRS measurement latency for FR2 positioning frequency layers.

· Send an LS to RAN4 to confirm.

MCC post meeting: Due to late decision, there was no time to the LS content to RAN4; postponed to next meeting.

Agreement:

Support using UL MAC CE for MG activation request by UE (Option 2) for the purpose of positioning.

Agreement:

Support the following option (from the agreement made in RAN1#106-e) for a new MG activation procedure to be performed by the gNB for the purpose of positioning.

· Option 2: DL MAC CE

· FFS: Deactivation process

Agreement:

With regards to MG activation by DL MAC CE, further study

· DL MAC CE payload

· The necessity of pre-configuration of MGs in higher layers.

Final summary in R1-2110605.

8.5.5 Potential enhancements of information reporting from UE and gNB for multipath/NLOS mitigation

R1-2108734 Remaining issues of NLOS mitigation and multi-path reporting Huawei, HiSilicon

R1-2108807 NLOS Mitigation Enhancements FUTUREWEI

R1-2108882 Enhancements on NLOS and Multi-path mitigation for NR positioning ZTE

R1-2108979 Discussion on potential enhancements for multipath/NLOS mitigation vivo

R1-2109055 Discussion on multipath/NLOS mitigation for NR positioning OPPO

R1-2109228 Further discussion on information reporting from UE and gNB for multipath/NLOS mitigation CATT

R1-2109367 Views on LoS/NLoS Identification and Mitigation Nokia, Nokia Shanghai Bell

R1-2109415 Potential enhancements for multipath/NLOS mitigation Xiaomi

R1-2109494 Discussion on potential enhancements of information reporting from UE and gNB for multipath/NLOS mitigation Samsung

R1-2109615 Solutions for Mitigation of NLOS Problem for NR Positioning Intel Corporation

R1-2109683 Discussion on multipath/NLOS mitigation for NR positioning NTT DOCOMO, INC.

R1-2109794 Considerations on multipath/NLOS mitigation for NR positioning Sony

R1-2109866 Potential positioning enhancements for multipath/NLOS mitigation Fraunhofer IIS, Fraunhofer HHI

R1-2110039 Views on potential enhancements for NLOS mitigation in Rel-17 positioning Apple

R1-2110092 Discussion on multipath/NLOS mitigation for positioning LG Electronics

R1-2110150 Discussion on multipath/NLOS mitigation for positioning InterDigital, Inc.

R1-2110191 Remaining Issues on Multipath Reporting in NR Positioning Qualcomm Incorporated

R1-2110301 Remaining issues for NLOS/Multipath Information Reporting Lenovo, Motorola Mobility

R1-2110344 Discussion on enhancements of multipath/NLOS reporting from UE and gNB CEWiT

R1-2110464 Potential enhancements of information reporting from UE and gNB for multipath/NLOS mitigation Ericsson (rev of R1-2110353)

[106bis-e-NR-ePos-05] – Ryan (Nokia)

Email discussion/approval on potential enhancements of information reporting from UE and gNB for multipath/NLOS mitigation with checkpoints for agreements on October 14 and 19

R1-2110435 Feature Lead Summary #1 for Potential multipath/NLOS mitigation Moderator (Nokia)

From Oct 11^th GTW session

Agreement:

For hybrid positioning methods where UL TDOA and multi-RTT are used in addition to UL AoA, support reporting of up to M=8 UL-AoA values per additional path

R1-2110436 Feature Lead Summary #2 for Potential multipath/NLOS mitigation Moderator (Nokia)

From Oct 13^th GTW session

Possible working assumption:

Supported LoS/NLoS indicator values are [0, 0.1, …, 0.9, 1] (in steps of 0.1) with the values corresponding to the likelihood of LoS

A value of 1 corresponds to LoS and a value of 0 corresponds to NLoS
Note: A UE does not have to support the 0.1 step size or all the values in the set and can choose to only report from a subset including the subset [0,1]. Whether a UE capability is defined to differentiate between reporting of hard and soft values can be further discussed.
FFS: Define a capability allowing the UE to indicate whether the UE can support the step size of 0.1 (soft values) or it can only support values in the subset [0, 1] (hard values)

R1-2110609 Feature Lead Summary #4 for Potential multipath/NLOS mitigation Moderator (Nokia)

From Oct 19^th GTW session

Agreement:

· For UE-based positioning, support the following options for LoS/NLoS indicators within positioning assistance data:

o Option 1 (Working assumption): LMF associates UE-based LoS/NloS indicators with each DL PRS resource for each TRP

o Option 2: LMF associates UE-based LoS/NloS indicators with each TRP

· Note: For option 1, one LoS/NloS indicator is associated with one DL-PRS resource

Agreement:

· For UL-TDOA, UL-AoA and Multi-RTT one LoS/NLoS indicator can be associated with each UL RTOA, UL SRS RSRP, UL-AoA and/or gNB Rx-Tx time difference measurement, respectively, and reported by gNB for each TRP that performed measurements for a given UE

· For UL-TDOA, UL-AoA and Multi-RTT one LoS/NLoS indicator can be associated and reported by a TRP for a given UE

· For DL-AoD and Multi-RTT one LoS/NLoS indicator can be associated with each DL PRS RSRP and/or UE Rx-Tx time difference measurement, respectively, and reported by UE for each TRP

· For DL-AoD and Multi-RTT one LoS/NLoS indicator can be associated with each TRP in the measurement report from the UE

· For DL-TDOA one LoS/NLoS indicator can be associated with each RSTD measurement performed with a target TRP and one LoS/NLoS indicator is associated with the RSTD measurement performed with a reference TRP

· For DL-TDOA one LoS/NLoS indicator can be associated with each target TRP and one LoS/NLoS indicator can be associated with the reference TRP in the measurement report

· FFS: Dependence of indication of a LOS/Nlos indicator on the presence of Rx beam index for DL-AoD

· FFS: Whether the above bullets apply to additional path measurements.

Decision: As per email decision posted on Oct 20^th,

Agreement:

Support reporting the path RSRP for the first path and for additional paths as part of DL-TDOA, UL-TDOA, and multi-RTT reporting enhancements.

· FFS: Support introducing a request from the LMF to the UE/TRP when the path-RSRP for additional paths is desired to be reported.

· FFS: Support of path RSRP for additional paths as part of DL-AoD.

8.5.66 Other

R1-2108883 Discussion on items led by RAN2 for NR positioning ZTE

R1-2108980 Discussion on inactive state positioning and on-demand PRS vivo

R1-2109056 Discussion on positioning for UE in RRC_INACTIVE and on-demand PRS OPPO

R1-2109229 Further discussion on on-demand DL PRS and positioning for UEs in RRC_ INACTIVE state CATT

R1-2109286 Discussion on RAN2-led items for positioning CMCC

R1-2109347 Discussion on enhancements of INACTIVE mode positioning and on-demand PRS CAICT

R1-2109368 Additional views on Inactive Mode Positioning and on-demand PRS Nokia, Nokia Shanghai Bell

R1-2109416 On-demand PRS and positioning for UE in RRC_INACTIVE state Xiaomi

R1-2109495 Discussion on on demand positioning and positioning in inactive state Samsung

R1-2109616 Support of On-demand DL PRS and NR Positioning in RRC_INACTIVE State Intel Corporation

R1-2109684 Discussion on positioning for UEs in RRC_INACTIVE state NTT DOCOMO, INC.

R1-2109744 Discussion on INACTIVE state positioning and on-demand PRS Huawei, HiSilicon

R1-2109795 Considerations on on-demand PRS and positioning in RRC Inactive Mode Sony

R1-2109867 Considerations for on-Demand PRS and positioning in RRC_INACTIVE state Fraunhofer IIS, Fraunhofer HHI

R1-2110093 Discussion on other enhancements for positioning LG Electronics

R1-2110151 On-demand PRS and positioning during INACTIVE mode InterDigital, Inc.

R1-2110192 Remaining issues on enhancements Related to On Demand PRS And Positioning in RRC Inactive State Qualcomm Incorporated

R1-2110261 Potential physical layer impact to the RAN2-led topics MediaTek Inc.

R1-2110302 Discussion on On-Demand PRS and RRC_INACTIVE Positioning Lenovo, Motorola Mobility

R1-2110354 Further details for on-demand PRS reception and SRS in RRC_INACTIVE Ericsson

[106bis-e-NR-ePos-06] – Alexey (Intel)

Email discussion/approval on RAN2-led aspects in the Others section with checkpoints for agreements on October 14 and 19

R1-2110456 Feature Lead Summary#1 for E-mail Discussion [106bis-e-NR-ePos-06] Moderator (Intel Corporation)

R1-2110457 Feature Lead Summary#2 for E-mail Discussion [106bis-e-NR-ePos-06] Moderator (Intel Corporation)

From Oct 13^th GTW session

Agreement:

Send LS to RAN2 with the outcome of RAN1 discussion on types of SRS for positioning to be supported by UEs in RRC_INACTIVE state
From RAN1 perspective, support of semi-persistent SRS for positioning by RRC_INACTIVE UEs is feasible
It is up to RAN2 to confirm support of semi-persistent SRS for positioning by RRC_INACTIVE UEs and determine necessary signalling details

Agreement:

For RRC_INACTIVE UEs, SRS for positioning bandwidth, SCS and CP type are configured by RRC and can be different from that of initial UL BWP configured by the system information

Decision: As per email decision posted on Oct 15^th,

Agreement:

· For OLPC of SRS for positioning transmission by RRC_INACTIVE UEs,

o Reuse validity criteria for pathloss measurement defined for RRC_CONNECTED UEs in Rel.16

§ FFS on UE fallback behavior (i.e. whether to reuse fallback to pathloss measurement by RRC_INACTIVE UE for the cell, from which the SS/PBCH is received to obtain MIB, is not accurate)

· For spatial relation of SRS for positioning transmission by RRC_INACTIVE UEs,

o FFS whether to define validity criteria or reuse validity criteria for OLPC pathloss measurement to determine whether spatial relation with configured RS is valid

Agreement:

· The following list of parameters is supported for UE-initiated and LMF initiated on-demand DL PRS request

o Start/end time of DL PRS transmission

o DL PRS resource repetition factor

o Number of DL PRS resource symbols per DL PRS resource

o DL-PRS CombSizeN

o Number of DL PRS frequency layers

o ON/OFF indicator (for LMF initiated request only)

· FFS values for requested on-demand DL PRS parameters and whether parameters are resource-specific, TRP-specific, or PFL-specific

R1-2110458 Feature Lead Summary#3 for E-mail Discussion [106bis-e-NR-ePos-06] Moderator (Intel Corporation)

From Oct 19^th GTW session

R1-2110597 Draft LS on support of SP-SRS for positioning by RRC_INACTIVE UEs Moderator (Intel Corporation)

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

Agreement:

From RAN1 perspective, in RRC_INACTIVE state, reception of DL PRS has lower priority than other DL signals/channels (SSB, SIB1, CORESET0, MSG2/MSGB, paging, DL SDT)

FFS how to determine conflicts in DL PRS and other DL signals/channels reception by UE
FFS how to handle retuning time for the case when DL PRS and other DL signals/channels are allocated in different BW and/or have the same or different SCS as initial DL BWP

Send LS to RAN4 (cc RAN2) and ask if there is any feedback

R1-2110643 Draft LS on DL PRS reception priority by RRC_INACTIVE Ues Moderator (Intel)

Decision: As per email decision posted on Oct 20^th, the draft LS is endorsed. Final version is approved in R1-2110644.

RAN1#107-e

8.5 NR Positioning Enhancements

Please refer to RP-210903 for detailed scope of the WI.

R1-2112792 Session notes for 8.5 (NR Positioning Enhancements) Ad-Hoc Chair (Huawei)

Rel-17 CRs related to Pos_enh

R1-2112426 Introduction of NR positioning enhancements Intel Corporation

Decision: Draft CR to 38.215 inc. agreements up to RAN1#106b-e. Endorsed, and to be revised to final CR for RAN submission after RAN1#107-e.

R1-2112487 Introduction of NR Positioning Enhancements Nokia

Decision: Draft CR to 38.214 inc. agreements up to RAN1#106b-e. Endorsed, and to be revised to final CR for RAN submission after RAN1#107-e.

[107-e-R17-RRC-NR-ePos] – Ren Da (CATT)

Email discussion on Rel-17 RRC parameters for positioning enhancement

- Email discussion to start on November 15

R1-2112508 FL Summary for Rel-17 RRC parameters for positioning enhancement Moderator (CATT)

Document is noted. For consolidation under 8 in [107-e-R17-RRC].

8.5.1 Accuracy improvements by mitigating UE Rx/Tx and/or gNB Rx/Tx timing delays

Including DL, UL and DL+UL positioning methods, and UE-based and UE-assisted positioning solutions.

R1-2110850 Remaining issues of mitigating Rx/Tx timing error Huawei, HiSilicon

R1-2110956 Positioning accuracy improvement by mitigating timing delay ZTE

R1-2111013 Remaining issues on potential enhancements for RX/TX timing delay mitigating vivo

R1-2111256 Remaining issues on mitigating UE and gNB Rx/Tx timing errors CATT

R1-2111289 Enhancement of timing-based positioning by mitigating UE Rx/Tx and/or gNB Rx/Tx timing delays OPPO

R1-2111364 Views on mitigating UE and gNB Rx/Tx timing errors Nokia, Nokia Shanghai Bell

R1-2111397 Remaining issues on mitigating Rx/Tx timing delays Sony

R1-2111495 Remaining Details of UE/gNB RX/TX Timing Errors Mitigation Intel Corporation

R1-2111609 Discussion on mitigation of gNB/UE Rx/Tx timing errors CMCC

R1-2111738 Discussion on accuracy improvements by mitigating UE Rx/Tx and/or gNB Rx/Tx timing delays Samsung

R1-2111797 Discussion on accuracy improvements by mitigating timing delays InterDigital, Inc.

R1-2111874 Positioning accuracy enhancements under timing errors Apple

R1-2111973 Discussion on accuracy improvement by mitigating UE Rx/Tx and gNB Rx/Tx timing delays LG Electronics

R1-2112071 Mitigation of RX/TX timing delays for higher accuracy MediaTek Inc.

R1-2112108 Discussion on mitigating UE and gNB Rx/Tx timing delays NTT DOCOMO, INC.

R1-2112217 Remaining Issues on Timing Error Mitigations for improved Accuracy Qualcomm Incorporated

R1-2112323 Considerations for mitigation of Tx/Rx Delays Lenovo, Motorola Mobility

R1-2112339 Techniques mitigating Rx/Tx timing delays Ericsson

[107-e-NR-ePos-01] – Ren Da (CATT)

Email discussion/approval on accuracy improvements by mitigating UE Rx/Tx and/or gNB Rx/Tx timing delays with checkpoints for agreements on November 15 and 19

R1-2112510 FL Summary for accuracy improvements by mitigating UE Rx/Tx and/or gNB Rx/Tx timing delays Moderator (CATT)

From Nov 12^th GTW session

Agreement

Confirm and modify the working assumption with the following modifications:

o The serving gNB should forward the association information provided by the UE to the LMF.

§ ~~FFS: whether to support the serving gNB to forward the association information to the neighboring gNBs~~

o UE should report its capability of supporting multiple UE Tx TEGs for UL TDOA to serving gNB.

· For mitigating UE Tx timing errors for Multi-RTT, subject to UE’s capability, support the LMF to request a UE to provide the association information of UL SRS resources for positioning with Tx TEGs directly to the LMF if the UE supports multiple Tx TEGs for Multi-RTT.

o ~~FFS: whether to support the LMF to forward the association information to the serving and neighboring gNBs~~

o UE should report its capability of supporting multiple UE Tx TEGs for Multi-RTT directly to the LMF.

· Note: For mitigating UE Tx timing errors when both UL-TDOA and Multi-RTT, or UL-TDOA and DL-TDOA are used, the UE should provide the association information of UL SRS resources for positioning with Tx TEGs, subject to UE capability (in the bullets above):

o to the serving gNB if a request to provide the association information is received from the gNB

o to the LMF if a request to provide the association information is received from the LMF.

· ~~FFS: Mitigation of UE Tx timing errors when Multi-RTT, UL-TDOA and/or DL-TDOA are used.~~

R1-2112511 FL Summary #2 for accuracy improvements by mitigating UE Rx/Tx and/or gNB Rx/Tx timing delays Moderator (CATT)

From Nov 16^th GTW session

Agreement

Make the following modification on the previous agreement made in RAN#106bis-e:

Subject to UE capability, support the LMF to request a UE to optionally measure the same DL PRS resource of a TRP with N different UE Rx TEGs and report the corresponding multiple RSTD measurements.

N=[2, 3, 4, 6, 8] ~~(FFS: other values),~~ where the maximum value of N depends on UE capability, and applies to all DL PRS positioning frequency layers
Note: If N is not explicitly included in the request, it is up to UE to determine the number of different UE Rx TEGs to measure the same DL PRS resource within its capability

The TRP can be either a “RSTD” reference TRP or a neighbour TRP
FFS: details of the signalling, procedures, and UE capability
The timestamps of the multiple RSTD measurements in the same measurement report can be the same or different.
Note: All RSTD measurements are relative to a single reference timing

Support the LMF to request a TRP to optionally measure the same SRS resource of a UE with M different TRP Rx TEGs and report the corresponding multiple RTOA measurements.

o M = [2, 3, 4, 6, 8] ~~(FFS: other values)~~ applies to all configured SRS resources ~~for positioning~~

Note: If M is not explicitly included in the request, it is up to TRP to determine the number of different TRP Rx TEGs to measure the same SRS resources for positioning
FFS: details of the signalling, procedures
The timestamps of the multiple RTOA measurements in the same measurement report can be the same or different.

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

Agreement

Each measurement instance in a TRP measurement report can be configured by LMF with either N=1 or 4 SRS measurement time occasions.

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

Agreement

· Subject to UE capability, support the LMF to request a UE to optionally measure the same DL PRS resource of a TRP with N different UE Rx TEGs and report the corresponding multiple UE Rx-Tx time difference measurements.

§ N=[2, 3, 4, 6, 8], where the maximum value of N depends on UE capability, and applies to all DL PRS positioning frequency layers

§ Note: If N is not explicitly included in the request, it is up to UE to determine the number of different UE Rx TEGs to measure the same DL PRS resource within its capability

o FFS: details of the signalling, procedures, and UE capability

o The timestamps of the multiple UE Rx-Tx time difference measurements in the same measurement report can be the same or different.

· Support the LMF to request a TRP to optionally measure the same SRS resource of a UE with M different TRP Rx TEGs and report the corresponding multiple gNB Rx-Tx time difference measurements.

o M = [2, 3, 4, 6, 8] applies to all configured SRS resources.

o Note: If M is not explicitly included in the request, it is up to TRP to determine the number of different TRP Rx TEGs to measure the same SRS resources

o FFS: details of the signalling, procedures

o The timestamps of the multiple gNB Rx-Tx time difference measurements in the same measurement report can be the same or different.

R1-2112512 FL Summary #3 for accuracy improvements by mitigating UE Rx/Tx and/or gNB Rx/Tx timing delays Moderator (CATT)

R1-2112513 FL Summary #4 for accuracy improvements by mitigating UE Rx/Tx and/or gNB Rx/Tx timing delays Moderator (CATT)

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

Agreement

· For UL-TDOA, supporting the following for the serving gNB to request a UE to report the Tx TEG association information between UE Tx TEG IDs and SRS resources for positioning, subject to UE capability of supporting UE Tx TEG:

o Based on a configured periodicity, a UE may report the UE Tx TEG association for the SRS resources for positioning that have already been transmitted during the configured period

§ It is up to RAN2 to decide how to indicate the change of the Tx TEG association during the configured period (e.g., using the timestamps)

§ It is up to RAN4 to decide when the Tx TEG association is changed

o The values of the configurable periodicities are up to RAN2

o Note: Tx TEG association information reporting by single request/response mode is assumed already supported with the previous agreement.

· Send an LS to RAN2/RAN4 (cc: RAN3)

o to RAN2, including the following RAN1’s agreement related to the reporting of the UE Tx TEG, for RAN2 to work on the signaling

o to RAN4 for checking the agreement and work on how to decide when the Tx TEG association is changed

Agreement

Subject to UE capability, support the LMF to request a UE to optionally measure the same DL PRS resource of a TRP with N different UE RxTx TEGs with the same UE Tx TEG, and report the corresponding multiple UE Rx-Tx time difference measurements.

N=[2, 3, 4, 6, 8], where the maximum value of N depends on UE capability, and applies to all DL PRS positioning frequency layers
Note: If N is not explicitly included in the request, it is up to UE to determine the number of different UE RxTx TEGs to measure the same DL PRS resource within its capability

FFS: details of the signalling, procedures, and UE capability
The timestamps of the multiple UE Rx-Tx time difference measurements in the same measurement report can be the same or different.

Support the LMF to request a TRP to optionally measure the same SRS resource of a UE with M different TRP RxTx TEGs with the same TRP Tx TEG and report the corresponding multiple gNB Rx-Tx time difference measurements.

M = [2, 3, 4, 6, 8] applies to all configured SRS resources.
Note: If M is not explicitly included in the request, it is up to TRP to determine the number of different TRP RxTx TEGs to measure the same SRS resources
FFS: details of the signalling, procedures
The timestamps of the multiple gNB Rx-Tx time difference measurements in the same measurement report can be the same or different.

Agreement

The maximum number of reported RSTD measurements obtained from different DL PRS resources per UE Rx TEG per target TRP is 4.

The target TRP can be the same as the RSTD reference TRP or a neighbor TRP
Note: The number of DL PRS resources per target TRP in a measurement report is still limited to 4 as in Rel-16.

The maximum number of reported RTOA measurements obtained from different UL SRS resources for positioning per TRP Rx TEG for a UE is 4.
The maximum number of reported UE Rx-Tx time difference measurements obtained from different DL PRS resources per UE Rx TEG for a TRP is 4.
The maximum number of reported gNB Rx-Tx time difference measurements obtained from different UL SRS resources per TRP Rx TEG for a UE is 4.
The maximum number of reported UE Rx-Tx time difference measurements obtained from different DL PRS resources per UE RxTx TEG for a TRP is 4.
The maximum number of reported gNB Rx-Tx time difference measurements obtained from different UL SRS resources per TRP RxTx TEG for a UE is 4.
Signaling details are left to RAN2 and RAN3

R1-2112967 [DRAFT] LS on the reporting of the Tx TEG association information Moderator (CATT)

Decision: As per email decision posted on Dec 1^st, the draft LS is endorsed. Final version is approved in R1-2112968.

8.5.2 Accuracy improvements for UL-AoA positioning solutions

R1-2110851 Remaining issues of UL AoA enhancements Huawei, HiSilicon

R1-2110957 Remaining issues on UL-AOA positioning solutions ZTE

R1-2111014 Remaining issues on potential enhancements for UL-AoA method vivo

R1-2111257 Remaining issues on enhancements for UL-AoA positioning method CATT

R1-2111290 Enhancements for UL AoA Positioning OPPO

R1-2111365 Views on enhancing UL AoA Nokia, Nokia Shanghai Bell

R1-2111398 Remaining aspects of UL-AoA enhancements Sony

R1-2111496 Remaining Details of NR Positioning UL-AoA Enhancements Intel Corporation

R1-2111739 Discussion on accuracy improvements for UL-AoA positioning solutions Samsung

R1-2111798 Enhancements for UL-AoA positioning solutions InterDigital, Inc.

R1-2111875 Positioning Accuracy enhancements for UL-AoA Apple

R1-2111974 Discussion on accuracy improvement for UL-AoA positioning LG Electronics

R1-2112109 Discussion on UL-AoA positioning enhancements NTT DOCOMO, INC.

R1-2112218 Remaining Issues on Potential Enhancements on UL-AOA positioning Qualcomm Incorporated

R1-2112340 Enhancements of UL-AoA positioning solutions Ericsson

//Handled under NWM – See RAN1-107-e-NWM-NR-ePos-02 as the document name

[107-e-NR-ePos-02] – Alexey (Intel)

Email discussion/approval on accuracy improvements for UL-AoA positioning solutions, with checkpoints for agreements on November 15 and 19

Decision: As per email posted on Nov 16^th,

Agreement

· ARP location is associated with UL measurements for NR Positioning (UL AOA, UL-RTOA, UL SRS-RSRP, UL SRS-RSRPP and gNB Rx-Tx time difference measurements)

· Use of ARP ID for potential overhead reduction in NRPPa signaling is up to RAN3

· Send LS to RAN3 to enable relevant signaling in RAN3 specification

R1-2112566 Feature Lead Summary#1 for E-mail Discussion [107-e-NR-ePos-02] Moderator (Intel Corporation)

From Nov 16^th GTW session

Agreement

Definition for UL SRS-RSRPP:

· UL SRS reference signal received path power (UL SRS-RSRPP) is defined as the power of the received UL SRS signal configured for the measurement at the i-th path delay of the channel response, where UL SRS-RSRPP for 1st path delay is the power corresponding to the first detected path.

o Working assumption: For frequency range 1, the reference point for the UL SRS-RSRPP shall be the antenna connector of the gNB. For frequency range 2, UL SRS-RSRPP shall be measured based on the combined signal from antenna elements corresponding to a given receiver branch.

o FFS: For frequency range 1 and 2, if receiver diversity is in use by the gNB, the reported UL SRS-RSRPP value shall not be lower than the corresponding UL SRS-RSRPP of any of the individual receiver branches

o FFS: Note: First and additional paths RSRP, when provided in the same report, use the same RX branch(es) selected for the first arrival path and for the UL SRS-RSRP if the UL SRS-RSRP is reported

§ FFS: whether/how to capture the note in the specifications

Send LS to RAN4

R1-2112739 Draft LS on ARP association with UL measurements for NR positioning Moderator (Intel Corporation)

Decision: As per email posted on Nov 19^th, the draft LS is stable and endorsed. Final version to RAN3 is approved in R1-2112740.

R1-2112567 Feature Lead Summary#2 for E-mail Discussion [107-e-NR-ePos-02] Moderator (Intel Corporation)

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

Agreement

Apply the following changes to the definition for UL SRS-RSRPP in the previous agreement:

Definition

UL SRS reference signal received path power (UL SRS-RSRPP) is defined as the power of the received UL SRS signal configured for the measurement at the i-th path delay of the channel response, where UL SRS-RSRPP for 1st path delay is the power corresponding to the first detected path.

· Working assumption: For frequency range 1, the reference point for the UL SRS-RSRPP shall be the antenna connector of the gNB. For frequency range 2, UL SRS-RSRPP shall be measured based on the combined signal from antenna elements corresponding to a given receiver branch.

· FFS: For frequency range 1 and 2, if receiver diversity is in use by the gNB, the reported UL SRS-RSRPP value shall not be lower than the corresponding UL SRS-RSRPP of any of the individual receiver branches

· ~~FFS: Note: First and additional paths RSRP, when provided in the same report, use the same RX branch(es) selected for the first arrival path and for the UL SRS-RSRP if the UL SRS-RSRP is reported~~

o ~~FFS: whether/how to capture the note in the specifications~~

Note: The following two options are supported by gNB to LMF:

· Option 1 (RX diversity for the first path UL SRS-RSRPP)

o The same RX branch(es) as applied for the first path UL SRS-RSRPP measurements are used for the additional paths UL SRS-RSRPP measurements if those are provided together

o For frequency range 1 and 2, if receiver diversity is in use by the gNB for UL SRS-RSRPP measurements, then reported UL SRS-RSRPP value for the first path shall not be lower than the corresponding UL SRS-RSRPP for the first path of any of the individual receiver branches

· Option 2 (RX diversity for UL SRS-RSRP)

o The same RX branch(es) as applied for UL SRS-RSRP measurements are used for UL SRS-RSRPP measurements (i.e., the first and additional paths UL SRS-RSRPP if those are provided)

R1-2112743 Draft LS on UL SRS-RSRPP definition Moderator (Intel Corporation)

Decision: As per email posted on Nov 19^th, the draft LS is stable and endorsed. Final version to RAN4 is approved in R1-2112744.

Final summary in R1-2112568.

8.5.3 Accuracy improvements for DL-AoD positioning solutions

Including UE-based and network-based (including UE-assisted) positioning solutions.

R1-2110852 Remaining issues of DL AoD enhancements Huawei, HiSilicon

R1-2110958 Accuracy improvement for DL-AoD positioning solutions ZTE

R1-2111015 Remaining issues on potential enhancements for DL-AoD method vivo

R1-2111258 Remaining issues on enhancements for DL-AoD positioning method CATT

R1-2111291 Enhancements for DL-AoD positioning OPPO

R1-2111366 Views on enhancing DL AoD Nokia, Nokia Shanghai Bell

R1-2111399 Remaining aspects of DL-AoD enhancements Sony

R1-2111497 Remaining Details of DL-AoD Enhancements for NR Positioning Intel Corporation

R1-2111574 Accuracy improvements for DL-AoD positioning solutions Xiaomi

R1-2111610 Discussion on DL-AoD enhancements CMCC

R1-2111654 Discussion on enhancements for DL-AoD positioning CAICT

R1-2111740 Discussion on accuracy improvements for DL-AoD positioning solutions Samsung

R1-2111799 Enhancements for DL-AoD positioning solutions InterDigital, Inc.

R1-2111876 Positioning Accuracy enhancements for DL-AoD Apple

R1-2111975 Discussion on accuracy improvement for DL-AoD positioning LG Electronics

R1-2112072 Accuracy enhancement for DL-AOD technique MediaTek Inc.

R1-2112110 Discussion on DL-AoD positioning enhancements NTT DOCOMO, INC.

R1-2112219 Remaining Issues on Potential Enhancements for DL-AoD positioning Qualcomm Incorporated

R1-2112324 Remaining issues on DL-AoD Positioning Enhancements Lenovo, Motorola Mobility

R1-2112341 Enhancements of DL-AoD positioning solutions Ericsson

R1-2112367 DL-AoD positioning enhancements Fraunhofer IIS, Fraunhofer HHI

[107-e-NR-ePos-03] – Florent (Ericsson)

Email discussion/approval on accuracy improvements for DL-AoD positioning solutions with checkpoints for agreements on November 15 and 19

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

Conclusion

The current definition of measured path DL PRS RSRP for ith path delay is sufficient and will not be discussed further in AI 8.5.3

· Note: discussion in other agenda items, if necessary, is not precluded.

R1-2112641 FL summary #1 for AI 8.5.3 Accuracy improvements for DL-AoD positioning solutions Moderator (Ericsson)

From Nov 16^th GTW session

Agreement

From the RAN1 perspective, for the TRP beam/antenna information to be optionally provided by the LMF to the UE for UE-based DL-AoD:

· The LMF provides the quantized version of the relative Power between PRS resources per angle per TRP.

o The relative power is defined with respect to the peak power in each angle

o For each angle, at least two PRS resources are reported.

o Note: the peak power per angle is not provided

· Note: up to RAN3 to decide how the TRP beam information is provided to the LMF for both UE-assisted and UE-based

· Send an LS to RAN2/RAN3 to decide on the signaling details

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

Agreement

For reporting of DL PRS RSRPP and PRS RSRP in UE-A DL-AOD

· The maximum number of DL PRS RSRPP M is a UE capability and its candidate values include {2,4,8,16,24}.

· The capabilities for DL PRS RSRPP (M value) and DL PRS RSRP (N values) are such that M is less than or equal to N.

R1-2112642 FL summary #2 for AI 8.5.3 Accuracy improvements for DL-AoD positioning solutions Moderator (Ericsson)

From Nov 19^th GTW session

Agreement

For the purpose of both UE-B and UE-A DL-AoD, and with regards to the support of AOD measurements with an expected uncertainty window, the following is supported

· Indication of expected angle value and uncertainty (of the expected azimuth and zenith angle value) range(s) is signaled by the LMF to the UE

· The type of expected angle and uncertainty can be requested by the UE, between the following options

§ Option 1: Indication of expected DL-AoD/ZoD value and uncertainty (of the expected DL-AoD/ZoD value) range(s) is signaled by the LMF to the UE

§ Option 2: Indication of expected DL-AoA/ZoA value and uncertainty (of the expected DL-AoA/ZoA value) range(s) is signaled by the LMF to the UE

Agreement

For UE-assisted DL-AOD positioning method, to enhance the signaling to the UE for the purpose of PRS resource(s) reporting, the LMF may indicate in the assistance data (AD), one or both the following:

· option 1: subject to UE capability, for each PRS resource, a subset of PRS resources for the purpose of prioritization of DL-AOD reporting:

o a UE may include the requested PRS measurement for the subset of the PRS in the DL-AoD additional measurements if the requested PRS measurement of the associated PRS is reported

§ The requested PRS measurement can be DL PRS RSRP and/or path PRS RSRP.

o UE may report PRS measurements only for the subset of PRS resources.

o Note: The subset associated with a PRS resource can be in a same or different PRS resource set than the PRS resource

option 2: subject to UE capability, for each PRS resource, the boresight direction information.
Note: Either case does not imply any restriction on UE measurement

· FFS: prioritization of the PRS resources and resource subsets to be measured

R1-2112843 [DRAFT] LS on TRP beam/antenna information Moderator (Ericsson)

Decision: As per email posted on Nov 19^th, the draft LS is endorsed. Final version to RAN2/RAN3 is approved in R1-2112844.

Final summary in R1-2112643.

8.5.4 Latency improvements for both DL and DL+UL positioning methods

R1-2110853 Enhancements to positioning latency improvements Huawei, HiSilicon

R1-2110959 Discussion on latency reduction for NR positioning ZTE

R1-2111016 Remaining issues on latency enhancement for NR positioning vivo

R1-2111259 Remaining issues on latency reduction for NR positioning CATT

R1-2111292 Enhancements on Latency Reduction in NR Positioning OPPO

R1-2111367 Views on PHY Latency Reductions Nokia, Nokia Shanghai Bell

R1-2111400 Remaining issues on latency improvements for NR positioning Sony

R1-2111435 Discussion on latency improvement for positioning China Telecom

R1-2111498 Remaining Open Aspects of NR Positioning Latency Reduction Intel Corporation

R1-2111575 Latency improvements for both DL and DL+UL positioning method Xiaomi

R1-2111611 Discussion on latency improvement for positioning CMCC

R1-2111741 Discussion on latency improvements for both DL and DL+UL positioning methods Samsung

R1-2111800 Latency improvements for both DL and DL+UL positioning methods InterDigital, Inc.

R1-2111877 Views on Rel-17 positioning latency reduction Apple

R1-2111976 Discussion on latency improvements for NR positioning LG Electronics

R1-2112073 Physical latency improvement aspects MediaTek Inc.

R1-2112111 Discussion on latency improvements for both DL and DL+UL positioning methods NTT DOCOMO, INC.

R1-2112220 Remaining issues on Latency Improvements for Positioning Qualcomm Incorporated

R1-2112325 Remaining issues on Positioning Latency Reduction Lenovo, Motorola Mobility

R1-2112342 Latency improvements for both DL and DL+UL positioning methods Ericsson

[107-e-NR-ePos-04] – Su (Huawei)

Email discussion/approval on latency improvements for both DL and DL+UL positioning methods with checkpoints for agreements on November 15 and 19

R1-2112457 Summary #1 of [107-e-NR-ePos-04] latency improvements Moderator (Huawei)

From Nov 12^th GTW session

Agreement

Preconfiguration of MG(s) in RRC is supported from RAN1 perspective.

· Each MG in the preconfiguration is associated with an ID

· The information in the UL MAC CE for MG activation request by the UE can be one ID associated with the preconfiguration of the MG

· Send an LS to RAN2 and RAN3

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

Conclusion

Include in the LS the following content:

· RAN1 understands it is up to RAN2 and/or RAN3 to decide how gNB determines the preconfiguration of MG(s).

Conclusion

For the MG activation request to the gNB by the LMF, it is up to RAN3 to design the necessary information to be transferred in the NRPPa message.

· Include it in the LS to RAN2 and RAN3.

Agreement

The DL MAC CE for MG activation indicates the ID associated with the preconfigured MG.

R1-2112411 Draft LS on lower Rx beam sweeping factor for latency improvement Moderator (Huawei)

Decision: As per email decision posted on Nov 18^th, the draft LS to RAN4 is endorsed. Final version is approved in R1-2112767.

R1-2112458 Summary #2 of [107-e-NR-ePos-04] latency improvements Moderator (Huawei)

From Nov 18^th GTW session

Agreement

The following options are supported subject to UE capability for priority handling of PRS when PRS measurement is outside MG.

· Option 1: UE may indicates support of two priority states.

o State 1: PRS is higher priority than all PDCCH/PDSCH/CSI-RS

o State 2: PRS is lower priority than all PDCCH/PDSCH/CSI-RS

· Option 2: UE may indicate support of three priority states

o State 1: PRS is higher priority than all PDCCH/PDSCH/CSI-RS

o State 2: PRS is lower priority than PDCCH and URLLC PDSCH and higher priority than other PDSCH/CSI-RS

§ Note: The URLLC channel corresponds a dynamically scheduled PDSCH whose PUCCH resource for carrying ACK/NAK is marked as high-priority.

o State 3: PRS is lower priority than all PDCCH/PDSCH/CSI-RS

· Option 3: UE may indicate support of single priority state

o State 1: PRS is higher priority than all PDCCH/PDSCH/CSI-RS

Note: SSB is a separate issue.

R1-2112783 [DRAFT] Draft LS on latency improvement for PRS measurement with MG Moderator (Huawei)

Decision: As per email posted on Nov 20^th, the draft LS is endorsed. Final version to RAN2/RAN3 is approved in R1-2112784.

Decision: As per email posted on Nov 20^th,

Agreement

For the purpose of determining conditions for measuring the PRS outside of a MG, the expected Rx timing difference between the PRS from the non-serving cell and that from the serving cell is determined by expected RSTD and expected RSTD uncertainty in the assistance data.

Send an LS to request RAN4 study and determine the threshold, which is used to be compared against with the Rx timing difference to determine whether the PRS from the non-serving cell satisfy the condition of PRS measurement outside MG.

· Examples for the threshold: CP length, 50% of the OFDM symbol, 1ms

· Other options can also be considered by RAN4

· Note: the requirement on whether UE needs to calculate the expected Rx time difference and/or compare against the threshold is also a part of the study request

Agreement

At least the following parameters for PRS processing window from the gNB to the UE are supported.

· Starting slot

· Periodicity

· Duration/length

· Cell and SCS information associated with the above parameters

Discuss during the maintenance phase on the necessity of other parameters including but not limited to

· Processing type (associated with the corresponding UE capability 1A/1B/2)

· Band/CC-ID as needed depending on each scenario on which the PRS processing window is applied

· The above cell and SCS information to determine where/when the PRS processing window is applied

Note: Indication of processing type does not suggest UE indication of multiple capabilities among (1A/1B/2) is already supported, which is a separate discussion.

Note: Some of the parameters above may not be mandatory for a PRS processing window

Agreement

The priority of PRS for UE supporting two priority states and three priority states can at least be indicated in RRC.

Agreement

For capability 1A as per working assumption made in RAN1#106-e, the DL signalings/channels in a per UE fashion (i.e. both across NR & LTE) inside the PRS processing window are dropped if the DL PRS is determined to be higher priority.

For capability 1B as per working assumption made in RAN1#106-e, only the DL signalings/channels from a certain band inside the PRS processing window are dropped if the DL PRS is determined to be higher priority.

Working assumption:

Subject to UE capability, support PRS measurement outside the MG, within a PRS processing window, and UE measurement inside the active DL BWP with PRS having the same numerology as the active DL BWP.

Inside the PRS processing window, subject to the UE determining that DL PRS to be higher priority, support the following UE capabilities:

Capability 1: PRS prioritization over all other DL signals/channels in all symbols inside the window.

Cap. 1A: The DL signals/channels from all DL CCs (per UE) are affected.
Cap. 1B: Only the DL signals/channels from a certain band/CC are affected.

FFS: band or CC

Capability 2: PRS prioritization over other DL signals/channels only in the PRS symbols inside the window
A UE shall be able to declare a PRS processing capability outside MG.

FFS: Details of capability signalling (e.g., per UE or per band, etc.)

Agreement

PRS processing window request to the gNB by the LMF is supported from RAN1 perspective.

· It is up to RAN3 to design the necessary information to be transferred in the NRPPa message.

· Note: It is up to gNB to determine the usage of measurement gap or PRS processing window

· Include it in the LS to RAN2 and RAN3.

Agreement

For PRS processing window configuration and indication, at least the following mechanism is supported

· RRC (pre-)configuration for PRS processing window configuration and DL MAC CE activation for PRS processing window, respectively.

Include it in the LS to RAN2 and request RAN2 to decide whether DL MAC CE is feasible for this indication.

R1-2112880 Draft LS on PRS processing window Moderator (Huawei)

Decision: As per email posted on Dec 1^st, the draft LS is endorsed. Final version is approved in R1-2112881.

R1-2112882 Draft LS on the condition of PRS measurement outside the MG Moderator (Huawei)

Decision: As per email posted on Dec 1^st, the draft LS is endorsed. Final version is approved in R1-2112883.

Final summary in R1-2112459.

8.5.5 Potential enhancements of information reporting from UE and gNB for multipath/NLOS mitigation

R1-2110854 Remaining issues of NLOS mitigation and multi-path reporting Huawei, HiSilicon

R1-2110860 Enhancements on NLoS mitigation for NR positioning PML

R1-2110960 Enhancements on NLOS and Multi-path mitigation for NR positioning ZTE

R1-2111017 Remaining issues on potential enhancements for multipath/NLOS mitigation vivo

R1-2111260 Remaining issues on information reporting from UE and gNB for multipath/NLOS mitigation CATT

R1-2111293 Discussion on multipath/NLOS mitigation for NR positioning OPPO

R1-2111368 Views on LoS/NLoS Identification and Mitigation Nokia, Nokia Shanghai Bell

R1-2111401 Remaining issues on multipath/NLOS mitigation for NR positioning Sony

R1-2111499 Remaining Details of NLOS Mitigation Solutions for NR Positioning Intel Corporation

R1-2111576 Potential enhancements for multipath/NLOS mitigation Xiaomi

R1-2111742 Discussion on potential enhancements of information reporting from UE and gNB for multipath/NLOS mitigation Samsung

R1-2111801 Discussion on multipath/NLOS mitigation for positioning InterDigital, Inc.

R1-2111878 Views on potential enhancements for NLOS mitigation in Rel-17 positioning Apple

R1-2111977 Discussion on multipath/NLOS mitigation for positioning LG Electronics

R1-2112112 Discussion on multipath/NLOS mitigation for NR positioning NTT DOCOMO, INC.

R1-2112221 Remaining Issues on Multipath Reporting in NR Positioning Qualcomm Incorporated

R1-2112326 Remaining issues on NLOS/Multipath Reporting Lenovo, Motorola Mobility

R1-2112343 Potential enhancements of information reporting from UE and gNB for multipath/NLOS mitigation Ericsson

R1-2112368 Potential positioning enhancements for multipath/NLOS mitigation Fraunhofer IIS, Fraunhofer HHI

[107-e-NR-ePos-05] – Ryan (Nokia)

Email discussion/approval on potential enhancements of information reporting from UE and gNB for multipath/NLOS mitigation with checkpoints for agreements on November 15 and 19

R1-2112492 Feature Lead Summary #1 for Potential multipath/NLOS mitigation Moderator (Nokia)

From Nov 12^th GTW session

Agreement

· For enhanced multipath reporting support N=8 for the value of maximum number of additional paths.

o Define a UE capability for the UE to report its supported value of maximum number of additional paths (no larger than 8)

Agreement

· Support the LMF to request DL PRS-RSRPP together with timing measurement as part of DL-TDOA and multi-RTT reporting enhancements

o Note: This applies to the first path and also to additional paths.

· Support the LMF to request UL SRS-RSRPP together with timing measurement as part of UL-TDOA and multi-RTT reporting enhancements

o Note: This applies to the first path and also to additional paths.

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

Conclusion

· Do not support LoS/NloS indicators for additional paths.

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

Agreement

Confirm the working assumption on UE-based LoS/NloS indicators option 1 with the following revision:

· Option 1: LMF associates UE-based LoS/NloS indicators with each DL PRS resource for each TRP, provided the LMF can give different values for Los/NLos indicators of different DL PRS resource of one TRP.

R1-2112493 Feature Lead Summary #2 for Potential multipath/NLOS mitigation Moderator (Nokia)

From Nov 18^th GTW session

Conclusion

The criteria for reporting additional path is left to UE/TRP implementation.

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

Conclusion

· LoS/NloS indicator dependency on Rx beam index is not introduced.

Agreement

· Support the following two options of values for LoS/NLoS indicator reporting from UE/TRP:

o Soft values: [0, 0.1, …, 0.9, 1] (in steps of 0.1)

o Hard values: [0, 1]

· The values correspond to the likelihood of LoS, with a value of 1 corresponding to LoS and a value of 0 corresponding to NLoS

Final summary in R1-2112494.

8.5.66 Other

R1-2110961 Discussion on items led by RAN2 for NR positioning ZTE

R1-2111018 Remaining issues on inactive state positioning and on-demand PRS vivo

R1-2111261 Remaining issues on on-demand DL PRS and positioning for UEs in RRC_ INACTIVE state CATT

R1-2111294 Discussion on positioning for UE in RRC_INACTIVE and on-demand PRS OPPO

R1-2111369 Additional views on Inactive Mode Positioning and on-demand PRS Nokia, Nokia Shanghai Bell

R1-2111402 Remaining Aspects of On-demand PRS and positioning in RRC Inactive Mode Sony

R1-2111500 Remaining Details for On-demand DL PRS Signaling and NR Positioning in RRC_INACTIVE state Intel Corporation

R1-2111577 On-demand PRS and positioning for UE in RRC_INACTIVE state Xiaomi

R1-2111596 Positioning in RRC_INACTIVE mode and on-demand PRS request Quectel

R1-2111612 Discussion on RAN2-led items for positioning CMCC

R1-2111655 Discussion on enhancements of INACTIVE mode positioning and on-demand PRS CAICT

R1-2111743 Discussion on on demand positioning and positioning in inactive state Samsung

R1-2111802 On-demand PRS and positioning during INACTIVE mode InterDigital, Inc.

R1-2111879 DL-PRS conflict resolution for UE in RRC_INACTIVE Apple

R1-2111932 Discussion on INACTIVE state positioning and on-demand PRS Huawei, HiSilicon

R1-2111978 Discussion on other enhancements for positioning LG Electronics

R1-2112222 Remaining issues on enhancements Related to On Demand PRS And Positioning in RRC Inactive State Qualcomm Incorporated

R1-2112327 Discussion on On-Demand PRS and RRC_INACTIVE Positioning Lenovo, Motorola Mobility

R1-2112344 Further details for on-demand PRS reception and SRS in RRC_INACTIVE Ericsson

R1-2112369 Considerations for on-demand PRS and positioning in RRC_INACTIVE state Fraunhofer IIS, Fraunhofer HHI

[107-e-NR-ePos-06] – Alexey (Intel)

Email discussion/approval on RAN2-led aspects in the Others section with checkpoints for agreements on November 15 and 19

R1-2112569 Feature Lead Summary#1 for E-mail Discussion [107-e-NR-ePos-06] Moderator (Intel Corporation)

From Nov 12^th GTW session

Agreement

For UE in RRC_INACTIVE state can support DL PRS processing outside and inside of the initial DL BWP:

· For DL PRS processing outside of the initial DL BWP, the SCS, CP type of DL PRS can be the same or different as for the initial DL BWP

· For DL PRS processing inside of the initial DL BWP, the SCS, CP type of DL PRS is the same as for the initial DL BWP.

· Potential impact of retuning time and expected RSTD assistance information on DL PRS reception performance is up to RAN4

· UE capability(ies) will be defined for DL PRS processing in RRC_INACTIVE state

o details are FFS

· Send an LS to RAN4 on agreed by RAN1 UE behavior for reception of DL PRS in RRC INACTIVE state

R1-2112570 Feature Lead Summary#2 for E-mail Discussion [107-e-NR-ePos-06] Moderator (Intel Corporation)

From Nov 16^th GTW session

Agreement

For spatial relation of SRS for positioning by RRC_INACTIVE UEs,

· Validity criteria for pathloss measurement (OLPC) is reused to determine validity of spatial relation for configured RS

· If the UE determines that the UE is not able to meet the above validity criteria for spatial relation then the UE stops transmission of SRS resource for positioning

· Note: the RS for spatial relation is a periodic or semi-persistent RS

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

R1-2112741 Draft LS on DL PRS processing by UEs in RRC_INACTIVE state Moderator (Intel Corporation)

Decision: The draft Ls is stable and endorsed. Final version is approved in R1-2112742.

Agreement

For OLPC of SRS for positioning by RRC_INACTIVE UEs, the following UE behaviour is used

· If the UE determines that it is not able to accurately measure pathloss for pathloss reference RS, UE stops transmission on corresponding SRS resource set for positioning

R1-2112571 Feature Lead Summary#3 for E-mail Discussion [107-e-NR-ePos-06] Moderator (Intel Corporation)

From Nov 19^th GTW session

Agreement

The following options are supported for SRS for positioning transmission by RRC_INACTIVE UEs:

· Option 1:

o Subject to UE capability (which is a prerequisite for option 2), a UE may be configured with an SRS for Positioning associated with the initial UL BWP and transmitted, during the RRC_INACTIVE state, inside the initial UL BWP with the same CP and SCS as configured for initial UL BWP.

· Option 2:

o Subject to UE capability, a UE may be configured with an SRS for Positioning where the following parameters are additionally configured for the transmission of the SRS for Positioning during the RRC_INACTIVE state: frequency location and bandwidth, SCS, CP length.

§ The UE shall not transmit the SRS for Positioning when it is expected to perform UL transmissions in the initial UL BWP in RRC_INACTIVE state.

RAN1 assumes that

· SRS for positioning for UEs in RRC_INACTIVE state is configured using the SRS-PosResourceSet IE

Send LS to RAN2 to define signaling for SRS for positioning configuration for RRC_INACTIVE UEs

Agreement

From RAN1 perspective, for LMF-initiated request of on-demand DL PRS, the following group of on-demand DL PRS parameters is defined and signaled

· per resource set per positioning frequency layer per FR

o DL PRS Periodicity

o DL PRS Resource Bandwidth

o DL PRS Resource Repetition Factor

o Number of DL PRS Resource Symbols per DL PRS Resource

o DL-PRS CombSizeN

Two options for indication of DL PRS QCL-Info, either

· Option 1: per resource set per positioning frequency layer per FR

o LMF recommends a list of QCL sources

· Option 2: per resource set per positioning frequency layer per FR

o LMF requests to provide the QCL information in the assistance data in NRPPa

· per FR

o Number of DL PRS frequency layers

· either per resource set per positioning frequency layer or per UE

o Start/end time of DL PRS transmission

· either per resource, or per resource set, or per UE

o ON/OFF indicator (for LMF initiated request only)

Agreement

From RAN1 perspective, for UE-initiated request of on-demand DL PRS, the following group of on-demand DL PRS parameters is defined and signalled

· per positioning frequency layer per FR

o DL PRS Periodicity

o DL PRS Resource Bandwidth

o DL PRS Resource Repetition Factor

o Number of DL PRS Resource Symbols per DL PRS Resource

o DL-PRS CombSizeN

· per FR

o Number of DL PRS frequency layers

· per UE

o Start/end time of DL PRS transmission

Two options for indication of DL PRS QCL-Info, either

· Option 1: per resource set per positioning frequency layer per FR

o UE recommends a list of QCL sources

· Option 2: per resource set per positioning frequency layer per FR

o UE requests to provide the QCL information in the assistance data

R1-2112845 Draft LS on configuration and transmission of SRS for positioning in RRC_INACTIVE state Moderator (Intel)

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

RAN1#107-bis-e

8.55 Maintenance on NR Positioning Enhancements

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

RAN1#108-e

8.5 Maintenance on NR Positioning Enhancements

R1-2202785 Session notes for 8.5 (Maintenance on NR Positioning Enhancements) Ad-Hoc Chair (Huawei)

[108-e-R17-RRC-ePos] – Ren Da (CATT)

Email discussion on Rel-17 RRC parameters for positioning enhancement

- 1^st check point for first LS in [108-e-R17-RRC]: February 24

- Final check point for second LS in [108-e-R17-RRC] if necessary: March 3

R1-2202495 FL Summary for Rel-17 RRC parameters for positioning enhancement Moderator (CATT)

R1-2202496 FL Summary #2 for Rel-17 RRC parameters for positioning enhancement Moderator (CATT)

Document is noted. For consolidation under 8 in [108-e-R17-RRC].

R1-2201317 Discussion on the reporting of the Tx TEG association information CATT

Decision: As per email decision posted on Feb 25^th,

Agreement

Provide the following response to RAN2 LS (R1-2201317)

RAN1 would like to confirm the following:

· The parameter numOfUERxTEG-PerPRSResource is a duplication of MeasPRSwithDiffRxTEGs_Request_RSTD.

· The correct value range of maxNumOfUE-RxTEG is 32.

· The parameter [srs-PosResourceSetId] is not needed.

The numOfUERxTEG-PerPRSResource and [srs-PosResourceSetId] will be removed when RAN1 provides the updated RRC parameter list to RAN2.

Decision: As per email decision posted on Mar 1^st,

Agreement

· If a UE is configured with SRS for positioning in multiple CCs, when the UE reports UE Tx TEG(s) for UL-TDOA or Multi-RTT, the frequency information of SRS for positioning resources should be included in the report;

· It is up to RAN2/RAN3 to decide how the frequency information of SRS for positioning resources is included in the report of the UE Tx TEG(s)

· Send LS to RAN2/RAN3 for the signaling design

R1-2202846 [DRAFT] LS on frequency information of SRS for positioning resources Moderator(CATT)

Decision: From Mar 3^rd GTW session, the draft LS is endorsed. Final version is approved in R1-2202847.

R1-2202620 LS to RAN1 on positioning issues needing further input RAN2, Intel

R1-2202848 [DRAFT] Reply LS on positioning issues needing further input Moderator (CATT, Intel)

Decision: As per email decision posted on Mar 3^rd, the draft LS is endorsed. Final version to R1-2202620(R2-2203597) is approved in R1-2202849.

8.5.1 Accuracy improvements by mitigating UE Rx/Tx and/or gNB Rx/Tx timing delays

Including DL, UL and DL+UL positioning methods, and UE-based and UE-assisted positioning solutions.

R1-2200920 Maintenance of Rx/Tx timing error Huawei, HiSilicon

R1-2201093 Maintenance on enhancements for RX/TX timing delay mitigating vivo

R1-2201193 Remaining issues on timing delay mitigation for NR positioning ZTE

R1-2201239 Enhancement of timing-based positioning by mitigating UE Rx/Tx and/or gNB Rx/Tx timing delays OPPO

R1-2201361 Remaining issues on mitigating UE and gNB Rx/Tx timing errors CATT

R1-2201582 Remaining Issues on Mitigating Rx/Tx Timing Delays Sony

R1-2201634 Maintenance of mitigating UE and gNB Rx/Tx timing errors Nokia, Nokia Shanghai Bell

R1-2201697 Maintenance for mitigation UE Rx/Tx and/or gNB Rx/Tx timing delays Intel Corporation

R1-2201824 Discussion on accuracy improvements by mitigating timing delays InterDigital, Inc.

R1-2201856 Remaining issues on UE/gNB Rx/Tx timing errors mitigation CMCC

R1-2202014 Discussion on accuracy improvements by mitigating UE Rx/Tx and/or gNB Rx/Tx timing delays Samsung

R1-2202140 Maintenance for Timing Error Mitigations for improved Accuracy Qualcomm Incorporated

R1-2202291 Discussion on accuracy improvement by mitigating UE Rx/Tx and gNB Rx/Tx timing delays LG Electronics

R1-2202366 Maintenance for Rx/Tx timing delays mitigation Fraunhofer IIS, Fraunhofer HHI

R1-2202370 Tx/Rx timing error mitigation maintenance issues Lenovo, Motorola Mobility

R1-2202389 Techniques mitigating Rx/Tx timing delays Ericsson

[108-e-R17-ePos-01] – Ren Da (CATT)

Email discussion for maintenance on accuracy improvements by mitigating UE Rx/Tx and/or gNB Rx/Tx timing delays

- 1^st check point: February 25

- Final check point: March 3

R1-2202497 FL Summary for accuracy improvements by mitigating UE Rx/Tx and/or gNB Rx/Tx timing delays Moderator (CATT)

From Feb 22^nd GTW session

Agreement

Provide the following responses to RAN4’s LS on Rel-15 SRS for UE/gNB Rx-Tx time difference measurement:

· The use of Rel-15 SRS for UE Rx-Tx time difference measurement and/or gNB Rx-Tx time difference measurement for the purpose of positioning is currently not specified in Rel-16.

· RAN1 has discussed the use of Rel-15 SRS for UE Rx-Tx time difference measurement and gNB Rx-Tx time difference measurement for the purpose of positioning in Rel-17, but has concluded not to specify it in Rel-17.

Draft reply LS to

R1-2200900 LS on SRS for multi-RTT positioning RAN4, Huawei

R1-2202658 Draft reply LS on SRS for multi-RTT positioning Moderator (Huawei)

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

R1-2202498 FL Summary #2 for accuracy improvements by mitigating UE Rx/Tx and/or gNB Rx/Tx timing delays Moderator (CATT)

Decision: As per email decision posted on Feb 26^th,

Agreement

The TP below for TS 38.214 section 5.1.6.5 is endorsed

----------------- Start of TP ----------------

5.1.6.5 PRS reception procedure

The UE may report a UE Rx TEG ID via higher layer parameter [ueRxTEG-ID] for a RSTD reference time dl-PRS-ReferenceInfo and a UE Rx TEG ID for each DL RSTD measurement, where the DL RSTD can be DL RSTD measurement in NR-DL-TDOA-MeasElement and/or NR-DL-TDOA-AdditionalMeasurementElement.

----------------- End of TP ----------------

R1-2202499 FL Summary #3 for accuracy improvements by mitigating UE Rx/Tx and/or gNB Rx/Tx timing delays Moderator (CATT)

From Feb 28^th GTW session

Agreement

Provide the following response to RAN2 LS (R1-2202620):

· A “Rx TEG” is associated with one or more measurements obtained from one or multiple received RS resources. The Rx timing error differences between any pair of the measurements belonging to the same Rx TEG are within a certain margin.

· A “Tx TEG” is associated with one or more transmitted RS resources. The Tx timing error differences between any pair of the RS resources belonging to the same Tx TEG are within a certain margin.

· The “group” means that for a set of multiple measurements or a set of multiple RS resources, if the error difference between any pair within the set is within the margin, the set is intuitively considered as timing error group, and is associated with a TEG ID.

· The definitions of the Tx/Rx timing delays/errors and Rx/Tx/RxTx TEGs in RAN2’s LS that RAN2 plans on using as a baseline are correct with the following changes.

o UE RxTx ‘timing error group’ (UE RxTx TEG): Rx timing errors and Tx timing errors, associated with UE reporting of one or more UE Rx-Tx time difference measurements, which have the 'Rx timing errors+Tx timing errors' differences within a certain margin

o TRP RxTx ‘timing error group’ (TRP RxTx TEG): Rx timing errors and Tx timing errors, associated with TRP reporting of one or more gNB Rx-Tx time difference measurements, which have the 'Rx timing errors+Tx timing errors' differences within a certain margin

· RAN1 is not planning on changing the definitions of UE Rx/Tx/RxTx TEGs specified in TS 38.214.

Conclusion

From RAN1 perspective, no change to RAN1 specifications is needed in order to support PRU in Rel-17.

R1-2202500 FL Summary #4 for accuracy improvements by mitigating UE Rx/Tx and/or gNB Rx/Tx timing delays Moderator (CATT)

From Mar 3^rd GTW session

Agreement

RAN2’s question: “whether the LMF determined “correction information” obtained from PRU measurements need to be provided to target UEs for UE-based mode of operation, and if so, kindly asks RAN1 to provide further details on the specific “correction information” which need to be provided to target UEs” in RAN2 LSs [R1-2200857]:

Providing the following response to RAN2:

· RAN1 has discussed the issue of whether to provide “correction information” obtained from PRU measurements from LMF to target UEs for UE-based positioning, but RAN1 cannot conclude whether to introduce ~~new~~ “correction information” for UE-based positioning in Rel-17.

· RAN1 has decided no more discussion on “correction information” obtained from PRU measurements for UE-based positioning in Rel-17.

Agreement

RAN2’s question: “RAN1 to provide further details on the “PRU antenna orientation information” which should be provided to an LMF” (in RAN2 LS R1-2200857).

Provide the following response:

· In Rel-17, there is no need to support PRU to provide the antenna orientation information to LMF, and thus no need to specify the PRU antenna orientation information.

Chair’s note: the two agreements above don’t revert RAN1 agreements on PRU made in Rel-17. It is not expected to have any RAN1 specification impact for PRU in Rel-17.

R1-2202911 [DRAFT] Reply LS on Positioning Reference Units (PRUs) for enhancing positioning performance Moderator(CATT)

Decision: As per email decision posted on Mar 3^rd, the draft LS is endorsed. Final version to R1-2200857(R2-2111488) is approved in R1-2202912.

Decision: As per email decision posted on Mar 3^rd,

Agreement

Provide the following response to RAN2’s question “RAN1 already agreed that periodic reporting for UL-TDOA should be supported, what is the purpose of periodically reporting the same information? Or only a-periodic report is required (i.e., a report when the TEG association has changed)?” in RAN2 LS R1-2202620:

· RAN1’s decision to support periodicity reporting of UE Tx TEG association for the SRS resources for positioning was made mainly based on the consideration of the signalling simplicity. In RAN1’s view, further signalling optimization is up to RAN2.

Agreement

· The association between measurement instances and UE measurements in the report to LMF should be defined as follows:

o For each indicated positioning method in a measurement report, multiple measurement instances are associated with the indicated positioning method.

§ E.g., a UE reports in a single NR-XXX-ProvideLocationInformation, multiple NR-XXX-SignalMeasurementInformation elements for UE assisted positioning, and NR-XXX-LocationInformation for UE-based positioning.

· It is up to RAN2 on how to implement above agreement

· It is up to RAN3 to implement the association between measurement instances and gNB measurements in the report to LMF

· Send an LS to RAN2/RAN3, asking them to take above information into account in their signalling work.

R1-2202921 [DRAFT] LS on multiple measurement instances Moderator(CATT)

Decision: As per email decision posted on Mar 3^rd, the draft LS is endorsed. Final version is approved in R1-2202922.

8.5.2 Accuracy improvements for UL-AoA positioning solutions

R1-2200921 Correction to SRS-RSRP and SRS-RSRPP Huawei, HiSilicon

R1-2201094 Maintenance on enhancements for UL-AoA method vivo

R1-2201194 Remaining issues on UL-AOA positioning solutions ZTE

R1-2201240 Enhancements for UL AoA Positioning OPPO

R1-2201362 Remaining issues on enhancements for UL-AoA positioning method CATT

R1-2201635 Maintenance of enhancing UL AoA Nokia, Nokia Shanghai Bell

R1-2201698 Maintenance of Rel.17 NR positioning solutions for UL-AoA method Intel Corporation

R1-2201825 Remaining issues for UL-AoA positioning solutions InterDigital, Inc.

R1-2201857 Remaining issues on UL-AoA enhancements CMCC

R1-2202015 Discussion on accuracy improvements for UL-AoA positioning solutions Samsung

R1-2202141 Maintenance on Potential Enhancements on UL-AOA positioning Qualcomm Incorporated

R1-2202292 Discussion on accuracy improvement for UL-AoA positioning LG Electronics

R1-2202390 Enhancements of UL-AoA positioning solutions Ericsson

[108-e-R17-ePos-02] – Alexey (Intel)

Email discussion for maintenance on accuracy improvements for UL-AoA positioning solutions

- 1^st check point: February 25

- Final check point: March 3

R1-2202520 Feature Lead Summary#1 for E-mail Discussion [108-e-NR-ePos-02] Moderator (Intel Corporation)

From Feb 23^rd GTW session

Agreement

Measurement definition of UL SRS-RSRPP is revised to include information on reference point as shown below:

Definition

The reference point for UL SRS-RSRPP shall be:

- for type 1-C base station TS 38.104 [9]: the Rx antenna connector,

- for type 1-O or 2-O base station TS 38.104 [9]: based on the combined signal from antenna elements corresponding to a given receiver branch

- for type 1-H base station TS 38.104 [9]: the Rx Transceiver Array Boundary connector.

For frequency range 1, the reference point for the UL SRS-RSRPP shall be the antenna connector of the gNB. For frequency range 2, UL SRS-RSRPP shall be measured based on the combined signal from antenna elements corresponding to a given receiver branch.

For frequency range 1 and 2, if receiver diversity is in use by the gNB for UL SRS-RSRPP measurements:

- The reported UL SRS-RSRPP value for the first and additional paths shall be provided for the same receiver branch(es) as applied for UL SRS-RSRP measurements, or

- The reported UL SRS-RSRPP value for the first path shall not be lower than the corresponding UL SRS-RSRPP for the first path of any of the individual receiver branches and the reported UL SRS-RSRPP for the additional paths shall be provided for the same receiver branch(es) as applied UL SRS-RSRPP for the first path.

Agreement

Definition for UL SRS-RSRPP measurement is modified as follows:

· UL SRS reference signal received path power (UL SRS-RSRPP) is defined as the power of the linear average of the channel response at the i-th path delay of the resource elements that carry the received UL SRS signal configured for the measurement, where UL SRS-RSRPP for 1st path delay is the power contribution corresponding to the first detected path in time.

Agreement

The gNB can be requested to measure and report to the LMF the UL SRS-RSRPP of the first path using at least the following option:

· Option 1: if the UL SRS-RSRPP is reported only for the first path (and UL SRS-RSRP is not reported), then the UL SRS-RSRPP of the first path is reported using the absolute reporting as defined in the mapping Table 13.3.1-1 of TS 38.133 for SRS-RSRP.

Decision: As per email decision posted on Mar 2^nd,

Agreement

If both UL SRS-RSRP and UL SRS-RSRPP of the first path are reported, then UL SRS-RSRPP of the first path is reported using the absolute reporting as defined in the mapping Table 13.3.1-1 of TS 38.133 for SRS-RSRP.

Final summary in R1-2202522.

8.5.3 Accuracy improvements for DL-AoD positioning solutions

Including UE-based and network-based (including UE-assisted) positioning solutions.

R1-2200922 Maintenance of DL-AoD enhancements Huawei, HiSilicon

R1-2201095 Maintenance on enhancements for DL-AoD method vivo

R1-2201195 Remaining issues on DL-AoD positioning solutions ZTE

R1-2201241 Enhancements for DL-AoD positioning OPPO

R1-2201363 Remaining issues on enhancements for DL-AoD positioning method CATT

R1-2201636 Maintenance of enhancing DL AoD Nokia, Nokia Shanghai Bell

R1-2201699 Maintenance of Rel.17 NR positioning solutions for DL-AoD method Intel Corporation

R1-2201826 Remaining issues for DL-AoD positioning solutions InterDigital, Inc.

R1-2201858 Remaining issues on DL-AoD enhancements CMCC

R1-2201946 Remaining issues on accuracy improvements for DL-AoD positioning solutions Xiaomi

R1-2202016 Discussion on accuracy improvements for DL-AoD positioning solutions Samsung

R1-2202142 Maintenance on Potential Enhancements for DL-AoD positioning Qualcomm Incorporated

R1-2202293 Discussion on accuracy improvement for DL-AoD positioning LG Electronics

R1-2202367 Maintenance for Rel-17 DL-AoD Fraunhofer IIS, Fraunhofer HHI

R1-2202371 DL-AoD Positioning Maintenance Lenovo, Motorola Mobility

R1-2202391 Enhancements of DL-AoD positioning solutions Ericsson

[108-e-R17-ePos-03] – Florent (Ericsson)

Email discussion for maintenance on accuracy improvements for DL-AoD positioning solutions

- 1^st check point: February 25

- Final check point: March 3

R1-2202603 FL summary #1 for AI 8.5.3 Accuracy improvements for DL-AoD positioning solutions Moderator (Ericsson)

From Feb 23^rd GTW session

Agreement

The following definition for DL PRS RSRPP in 38.215 is endorsed:

· DL PRS reference signal received path power (DL PRS-RSRPP), is defined as the power of the linear average of the channel response at the i-th path delay of the resource elements that carry DL PRS signal configured for the measurement, where DL PRS-RSRPP for the 1st path delay is the power contribution corresponding to the first detected path in time.

Decision: As per email decision posted on Feb 26^th,

Agreement

In the beam antenna Assistance data element, support signaling enabling to refer the beam information of a TRP with another TRP with the same beam information in Local Coordinate System (LCS).

Agreement

Only GCS is supported for reference angle for expected angle and uncertainty of DL-AoD positioning.

Agreement

The TP below for TS 38.214 section 5.1.6.5 is endorsed

----------------Start of TP for TS38.214---------------------

5.1.6.5 PRS reception procedure

……

For each PRS resource, Tthe UE may be configured, subject to UE capability, with [DL-AOD-PRS resource-Subset] that is associated with thisa PRS resource, where the subset of PRS resources associated with the PRS resource can be in the same or different PRS resource set than the PRS resource. The UE may include UE measurements for the subset of PRS resources in [NR-DL-AoD-AdditionalMeasurementElement] if the UE measurements of the associated PRS resource are reported, where the UE measurement can be DL PRS-RSRP and/or DL PRS-RSRPP. The UE may report DL PRS-RSRP and/or DL PRS-RSRPP measurements only for the subset of PRS resources. Subject to UE capability, the UE may be configured with higher layer parameter [DL-AOD Boresight direction] for each PRS resource.

----------------End of TP for TS38.214---------------------

R1-2202604 FL summary #2 for AI 8.5.3 Accuracy improvements for DL-AoD positioning solutions Moderator (Ericsson)

From Mar 1^st GTW session

Agreement

For the reporting of first path DL-PRS RSRPP in DL AOD,

· For the 1^st measurement, the report includes DL PRS RSRP and optionally DL PRS RSRPP using absolute reporting

· For additional measurement, at least one of the two following measurement is reported:

o First path DL PRS RSRPP can be optionally reported using differential reporting with the first measurement of DL PRS RSRPP,

o DL PRS RSRP can be optionally reported using differential reporting with the first measurement of DL PRS RSRP.

· Send the agreement in an LS reply to RAN2 as a reply regarding the question "For RAN1 agreements "The requested PRS measurement can be DL PRS RSRP and/or path PRS RSRP.", is there a need to request and provide only the RSRPP measurements for the additional measurements (without legacy RSRP)?"

Agreement

The expected angle value and uncertainty for DL-AoD methods also applies to DL-TDOA and Multi-RTT

· Note: This does not imply any restriction on UE measurement

· Send an LS to RAN2 with this agreement in reply to the question "RAN2 understand "angle assistance information" applies for DL-AOD positioning method. It is unclear to RAN2 on whether it also applies for DL-TDOA and Multi-RTT?"

Decision: As per email decision posted on Mar 3^rd,

Agreement

For the beam/antenna information the power resolution of the information can be configured with a fixed resolution and range according to:

· Option 1: a linear range in dB

o The resolution of the range is 0.1 or 1 dB

o Span of the range is from -30 to 0dB.

Conclusion

Expected DL-AoD and DL-AOA is provided to the UE for each TRP instead of ARP.

Agreement

For the configuration of the AoA/AoD uncertainty window:

· The granularity is set as:

o Option 1: the granularity of the uncertainty range and expected AOD/AOA for AoD/AoA is 1 degree

· The uncertainty range is

o Expected Azimuth DL-AoD/DL-AoA uncertainty range is configurable within [0, 60] with an step size of 1 degrees. Expected Zenith DL-AoD/DL-AoA uncertainty range is configurable within [0, 30] with an step size of 1 degrees.

o the angles are interpreted as follow

§ Range of Expected azimuth angle of arrival as (φAOA – ΔφAOA/2, φAOA + ΔφAOA/2)

§ φAOA – expected azimuth angle of arrival, ΔφAOA – uncertainty range for expected azimuth angle of arrival.

§ Range of Expected zenith angle of arrival as (θAOA – ΔθAOA/2, θAOA + ΔθAOA/2)

§ θAOA – expected zenith angle of arrival, ΔθAOA – uncertainty range for expected zenith angle of arrival.

§ Range of Expected azimuth angle of departure as (φAOD – ΔφAOD/2, φAOD + ΔφAOD/2)

§ φAOD – expected azimuth angle of departure, ΔφAOD – uncertainty range for expected azimuth angle of departure.

§ Range of Expected zenith angle of departure as (θAOD- ΔθAOD/2, θAOA + ΔθAOA/2)

§ θAOD – expected zenith angle of departure, ΔθAOD – uncertainty range for expected zenith angle of departure.

Final summary in R1-2202605.

8.5.4 Latency improvements for both DL and DL+UL positioning methods

R1-2200923 Maintenance of PRS measurement outside MG Huawei, HiSilicon

R1-2201096 Maintenance on latency enhancement for NR positioning vivo

R1-2201196 Remaining issues on latency reduction for NR positioning ZTE

R1-2201242 Enhancements on Latency Reduction in NR Positioning OPPO

R1-2201364 Remaining issues on latency reduction for NR positioning CATT

R1-2201480 Remaining issues on latency improvements for both DL and DL+UL positioning methods NTT DOCOMO, INC.

R1-2201583 Remaining Issues on Latency Improvements for Positioning Methods Sony

R1-2201637 Maintenance of PHY Latency Reductions Nokia, Nokia Shanghai Bell

R1-2201774 Remaining issues on Rel-17 positioning latency reduction Apple

R1-2201827 Latency improvements for both DL and DL+UL positioning methods InterDigital, Inc.

R1-2201859 Remaining issues on latency enhancements CMCC

R1-2201947 Remaining issues on latency improvements for both DL and DL+UL positioning method Xiaomi

R1-2202017 Discussion on latency improvements for both DL and DL+UL positioning methods Samsung

R1-2202143 Maintenance on Latency Improvements for Positioning Qualcomm Incorporated

R1-2202294 Discussion on latency improvements for NR positioning LG Electronics

R1-2202392 Latency improvements for both DL and DL+UL positioning methods Ericsson

[108-e-R17-ePos-04] – Su (Huawei)

Email discussion for maintenance on latency improvements for both DL and DL+UL positioning methods

- 1^st check point: February 25

- Final check point: March 3

R1-2202513 Summary #1 of [108-e-R17-ePos-04] latency improvements Moderator (Huawei)

From Feb 25^th GTW session

Agreement

· The PRS processing window is configured per DL BWP.

· Processing type, to be selected from 1A, 1B and 2, will be provided associated with the PRS processing window if and only if multiple processing types per band in the UE capability signaling is supported.

· No need to provide band ID and CC ID associated with the PRS processing window.

· A single priority indicator is provided for a PRS processing window, which applies to all PRS within the PRS processing window for the corresponding DL BWP.

· The maximum number of activated PRS processing windows per DL BWP is 1.

· The maximum number of activated PRS processing windows across all active DL BWPs is 4.

o The maximum number of activated PRS processing windows overlapping in time across all active DL BWPs is 1

Decision: As per email decision posted on Feb 26^th,

Agreement

The maximum number of preconfigured MGs is 16.

Agreement

The maximum number of MGs per activation/deactivation is 1.

Conclusion

RAN1 understand that the priority between SSB and PRS is up to RAN4 to define.

Agreement

Inside each single instance of a PRS processing window, a single PFL can be measured. This is applicable to all Types of MG-less PRS processing.

Agreement

· For a UE configured with preconfigured Measurement gap(s) for Positioning, when the UE receives an activation command, as described in clause [6.1.3.X] of [10, TS 38.321], for a preconfigured Measurement Gap for Positioning activation, and when the UE would transmit a PUCCH with HARQ-ACK information in slot n corresponding to the PDSCH carrying the ~~selection~~ command, the corresponding actions in [10, TS 38.321] and the UE assumptions shall be applied starting from the first slot that is after slot where is the SCS configuration for the PUCCH.

· For a UE configured with Positioning Processing Window(s), when the UE receives an activation command, as described in clause [6.1.3.X] of [10, TS 38.321], for a PRS processing window activation, and when the UE would transmit a PUCCH with HARQ-ACK information in slot n corresponding to the PDSCH carrying the ~~selection~~ command, the corresponding actions in [10, TS 38.321] and the UE assumptions shall be applied starting from the first slot that is after slot where is the SCS configuration for the PUCCH.

R1-2202514 Summary #2 of [108-e-R17-ePos-04] latency improvements Moderator (Huawei)

From Feb 28^th GTW session

Agreement

UE may indicate support of more than one processing types and corresponding capability on a band on which it supports PRS processing outside the MG inside the PRS processing window.

· It is up to the gNB to decide which processing type to use

Decision: As per email decision posted on Mar 1^st,

Agreement

For capability 2 as per working assumption made in RAN1#106-e

· For FR1, only the DL signals/channels from a certain CC inside the PRS processing window, which overlap with DL PRS symbols in time, are dropped if the DL PRS is determined to be higher priority

· For FR2, only the DL signals/channels from a certain band inside the PRS processing window, which overlap with DL PRS symbols in time, are dropped if the DL PRS is determined to be higher priority

For the DL signals/channels from a different FR2 band than the FR2 band of the DL PRS for capability 1B and 2, subject to dropping due to the same Rx beam across multiple FR2 bands if the DL PRS is determined to be higher priority, it is up to RAN4 to define.

· Send an LS to RAN4

Agreement

The M-sample indication is applicable for all concurrent NR positioning methods and for all positioning frequency layers

R1-2202841 Draft LS on the dropping rule of DL signals/channels for capability 1B and 2 Moderator (Huawei)

Decision: As per email decision posted on Mar 3^rd, the draft LS is endorsed. Final LS is approved in R1-2202842.

Decision: As per email decision posted on Mar 3^rd,

Agreement

The maximum number of preconfigured PRS processing window per DL BWP is 4.

Agreement

The maximum number of PRS processing windows that can be activated/deactivated by a DL MAC CE is 1.

Agreement

The following TP for clause 5.1.6.5 of TS 38.214 is endorsed:

The UE is expected to measure the DL PRS resource outside the active DL BWP or with a numerology different from the numerology of the active DL BWP if the measurement is made during a configured measurement gap. When the UE is expected to measure the DL PRS resource, the UE may request a measurement gap via higher layer parameter NR-PRS-MeasurementInfoList [12, TS 38.331] or as specified in clause X of [10, TS 38.321]. The UE may be preconfigured with one or more measurement gaps each associated with an [ID]. When the UE requests activation or deactivation of a measurement gap as specified in clause [X] of [10, TS 38.321] it can request one of the preconfigured measurement gaps by referring to the [ID]. The UE may have one of the preconfigured measurement gap(s) activated or deactivated as specified in clause[X] of [10, TS 38.321].

R1-2202515 Summary #3 of [108-e-R17-ePos-04] latency improvements Moderator (Huawei)

From Mar 3^rd GTW session (to be incorporated in the overall response to R1-2202620)

Agreement

Endorse the following reply to R1-2202620(R2-2203597).

With regards to the issue of preconfigured MG

Issue: FFS on whether MG activation/deactivation request from the LMF can also be applicable to R16 MG configuration in addition to positioning MG preconfiguration, i.e. Can LMF ask the gNB to configure the MG (e.g. via RRC) directly?

RAN1 Answer: It is RAN1 understanding that the reception of MG activation request from the LMF facilitates gNB to activate the preconfigured MG, and gNB does not expect to be asked by the LMF to configure MG with RRC, but RAN1 also understands gNB may still configure the MG with RRC as in Rel-16, given that gNB behaviour for this is up to gNB implementation.

With regards to the issues of PRS processing window

Issues:

FFS:Whether PRS processing window configuration is provided per BWP or not is up to RAN1 to decide.

FFS: Whether UE can be configured with multiple PRS processing windows should be decided by RAN1.

FFS on the max number of PPW configurations (from Stage 2 discussion)

FFS: whether UE should monitor PDCCH during RAR window/msgB window ot or contention resolution timer for the affected symbols by PPW

RAN1 Answer:

RAN1 agreed that PRS processing window configuration is provided per DL BWP.

UE can be configured with multiple PRS processing windows in one DL BWP.

The maximum number of PPW configuration is 4 per DL BWP, but the number of activated PRS processing window per DL BWP is 1. In addition, RAN1 would like to note the maximum number of activated PRS processing windows across all active DL BWPs is 4, and those activated PRS processing windows are not overlapping in time.

It is RAN1 understanding that UE should monitor PDCCH during RAR window/msgB window or contention resolution timer for the affected symbols by the PRS processing window.

8.5.5 Potential enhancements of information reporting from UE and gNB for multipath/NLOS mitigation

R1-2200924 Maintenance of multi-path enhancements Huawei, HiSilicon

R1-2201097 Maintenance on enhancements for multipath/NLOS mitigation vivo

R1-2201197 Remaining issues on NLOS and Multi-path mitigation for NR positioning ZTE

R1-2201243 Discussion on multipath/NLOS mitigation for NR positioning OPPO

R1-2201365 Remaining issues on information reporting from UE and gNB for multipath/NLOS mitigation CATT

R1-2201481 Remaining issues on multipath/NLOS mitigation for NR positioning NTT DOCOMO, INC.

R1-2201638 Maintenance of LoS/NLoS Identification and Mitigation Nokia, Nokia Shanghai Bell

R1-2201700 Maintenance of Rel.17 NR positioning solutions for NLOS/multipath mitigation Intel Corporation

R1-2201890 Remaining issues for multipath/NLOS mitigation for positioning InterDigital, Inc.

R1-2201948 Remaining issues on potential enhancements for multipath/NLOS mitigation Xiaomi

R1-2202018 Discussion on potential enhancements of information reporting from UE and gNB for multipath/NLOS mitigation Samsung

R1-2202393 Potential enhancements of information reporting from UE and gNB for multipath/NLOS mitigation Ericsson

[108-e-R17-ePos-05] – Ryan (Nokia)

Email discussion for maintenance on potential enhancements of information reporting from UE and gNB for multipath/NLOS mitigation

- 1^st check point: February 25

- Final check point: March 3

R1-2202556 Feature Lead Summary #1 for Maintenance of multipath/NLOS mitigation Moderator (Nokia)

Decision: As per email decision posted on Feb 25^th,

Conclusion:

Do not support additional path reporting for DL-AoD in Rel-17.

Agreement

The following TP to TS 38.214 is endorsed:

-------------------------- Start of Text Proposal for TS 38.214 --------------------------

5.1.6.5 PRS reception procedure

…

The UE may be configured to measure and report via higher layer parameter [AdditionalPath-relativeTiming-Request], subject to UE capability, the timing and the quality metrics of up to 8 additional detected paths, that are associated with each RSTD or UE Rx – Tx time difference. The timing of each additional path is reported relative to the path timing used for determining nr-RSTD or nr-UE-RxTxTimeDiff. For UE positioning measurement reporting in higher layer parameters NR-DL-TDOA-SignalMeasurementInformation or NR-Multi-RTT-SignalMeasurementInformation, the UE may be configured to measure and report, subject to UE capability, the ~~path~~ DL PRS- RSRPP of the first path and the up to 8 additional paths that are associated with each RSTD or UE Rx – Tx time difference.

…

-------------------------- End of Text Proposal for TS 38.214 --------------------------

R1-2202557 Feature Lead Summary #2 for Maintenance of multipath/NLOS mitigation Moderator (Nokia)

R1-2202558 Feature Lead Summary #3 for Maintenance of multipath/NLOS mitigation Moderator (Nokia)

No consensus on differential reporting of RSRPP, as per the end of the meeting.

Final summary in R1-2202559.

8.5.66 Other

R1-2201098 Maintenance on inactive state positioning and on-demand PRS vivo

R1-2201198 Remaining issues on items led by RAN2 for NR positioning ZTE

R1-2201244 Discussion on positioning for UE in RRC_INACTIVE and on-demand PRS OPPO

R1-2201366 Remaining issues on on-demand DL PRS and positioning for UEs in RRC_ INACTIVE state CATT

R1-2201399 Use cases and applications on Carrier Phase Based Positioning for NR Locaila

R1-2201440 Discussion on remaining issue for on-demand DL PRS China Telecom

R1-2201639 Maintenance of Inactive Mode Positioning and on-demand PRS Nokia, Nokia Shanghai Bell

R1-2201701 Maintenance of Rel.17 NR positioning solutions for RRC_INACTIVE UEs Intel Corporation

R1-2201860 Remaining issues on RAN2-led items CMCC

R1-2201891 Remaining issues for on-demand PRS InterDigital, Inc.

R1-2201910 Discussion on enhancements of INACTIVE mode positioning and on-demand PRS CAICT

R1-2201949 Remaining issues on positioning for UE in RRC_INACTIVE state Xiaomi

R1-2202019 Discussion on demand positioning and positioning in inactive state Samsung

R1-2202145 Maintenance on enhancements Related to On Demand PRS And Positioning in RRC Inactive State Qualcomm Incorporated

R1-2202295 Discussion on other enhancements for positioning LG Electronics

R1-2202372 On-Demand PRS and RRC_INACTIVE Positioning Maintenance Lenovo, Motorola Mobility

R1-2202394 Further details for on-demand PRS reception and SRS in RRC_INACTIVE Ericsson

R1-2202421 Maintenance of RRC_INACTIVE state positioning Huawei, HiSilicon

[108-e-R17-ePos-06] – Alexey (Intel)

Email discussion for maintenance on RAN2-led aspects in the Others section

- 1^st check point: February 25

- Final check point: March 3

R1-2202523 Feature Lead Summary#1 for E-mail Discussion [108-e-NR-ePos-06] Moderator (Intel Corporation)

From Feb 22^nd GTW session

Agreement

· Send reply to LS from RAN4 WG (cc to RAN2) clarifying that

o From RAN1 perspective, PRS processing window defined for PRS measurements outside measurement gap is not supported in RRC_INACTIVE state in Rel-17

Draft reply LS to

R1-2200903 LS on the applicability of PRS processing window in RRC_INACTIVE state RAN4, CATT

R1-2202618 [Draft] Reply LS on the applicability of PRS processing window in RRC_INACTIVE state Moderator (CATT)

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

Decision: As per email decision posted on Feb 25^th,

Agreement

The TP to TS 38.213 (Section 7.3.1) in proposal 4.1-2 in section 4.1.2 of R1-2202523 is endorsed as modified below:

--- Start of TP ---

7.3.1 UE behaviour

If the UE is in the RRC_CONNECTED state and determines that the UE is not able to accurately measure , рor the UE is not provided with pathlossReferenceRS-Pos, the UE calculates using a RS resource obtained from the SS/PBCH block of the serving cell that the UE uses to obtain MIB. If the UE is in the RRC_INACTIVE state and determines that the UE is not able to accurately measure , the UE does not transmit the SRS resource set for positioning.

--- End of TP ---

Agreement

· The TP to TS 38.214 (Section 5.1.6.5) in proposal 4.2-2 in section 4.2.2 of R1-2202523 is endorsed.

· The TP to TS 38.214 (Section 5.1.6.5) in proposal 4.3-2 in section 4.3.2 of R1-2202523 is endorsed.

R1-2202524 Feature Lead Summary#2 for E-mail Discussion [108-e-NR-ePos-06] Moderator (Intel Corporation)

Working assumption

For Option 2 of SRS for positioning transmission in RRC_INACTIVE, a UE capability for switching time between SRS Tx and other Tx in initial UL BWP or Rx in initial DL BWP is introduced

· The capability is reported per band

o The capability applies at least to TDD

o FFS: FDD

· The switching time value(s) are left up to RAN4 discussion

· If the transmission of SRS for positioning with the switching time overlaps/collides in time domain with other DL reception or UL transmission at least for TDD, the SRS for positioning transmission is dropped in the symbol(s) where the overlap/collision occurs

o Note: Transmission of SRS for positioning with the switching time covers the following example TDD cases:

a) “switching after SRS” (i.e., transmission of SRS + switching time)

b) “switching before SRS” (i.e., switching time + transmission of SRS)

Decision: As per email decision posted on Mar 3^rd,

Agreement

For Option 2 of SRS for positioning configuration,

· The feature is supported at least for NUL in Rel.17

· The SRS for positioning is configured in the same band and CC as the initial UL BWP

o Signaling details are up to RAN2

· The following is up to UE capability indication

o Support of different SCS, CP type from the initial UL BWP

o Support a different center frequency between the SRS for positioning and the initial UL BWP

o Whether bandwidth of SRS for positioning may not include bandwidth of the CORESET#0 and SSB

Final summary in R1-2202525.

RAN1#109-e

8.5 Maintenance on NR Positioning Enhancements

R1-2205563 Session notes for 8.5 (Maintenance on NR Positioning Enhancements) Ad-Hoc Chair (Huawei)

R1-2205097 Moderator Summary for preparation phase on maintenance of Rel-17 WI on NR positioning enhancements Moderator (CATT)

R1-2203040 Questions concerning the implementation of RAN1 agreements in NRPPa RAN3, Ericsson

[109-e-R17-ePos-01] – Florent (Ericsson)

Email discussion under 8.5 on LS in R1-2203040, covering issues 1-5 and 7-1 in R1-2205097 by May 13.

R1-2205525 Moderator Summary for [109-e-R17-ePos-01] on LS in R1-2203040 Moderator (Ericsson)

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

Agreement

The agreement from RAN1#108e on LMF initiated request of on-demand PRS is amended as follow:

· Note: no RAN1 specification impact is expected

· Send the agreement as part of the reply LS to RAN3

Agreement

● From RAN1 perspective, for LMF-initiated request of on-demand DL PRS, the following group of on-demand DL PRS parameters is defined and signaled

○ per resource set per positioning frequency layer per FR

1. DL PRS Periodicity

2. DL PRS Resource Bandwidth

3. DL PRS Resource Repetition Factor

4. Number of DL PRS Resource Symbols per DL PRS Resource

5. DL-PRS CombSizeN

● Two options for indication of DL PRS QCL-Info, either

○ Option 1: per resource set per positioning frequency layer per FR

· LMF recommends a list of QCL sources

○ Option 2: per resource set per positioning frequency layer per FR

♦ LMF requests to provide the QCL information in the assistance data in NRPPa

○ per FR

♦ Number of DL PRS frequency layers

○ either per resource set per positioning frequency layer or per UETRP

♦ Start/end time of DL PRS transmission

○ either per resource, or per resource set, or per UETRP

♦ ON/OFF indicator (for LMF initiated request only)

R1-2205600 [DRAFT] LS reply on questions concerning the implementation of RAN1 agreements in NRPPa Moderator (Ericsson)

Decision: As per email decision posted on May 21^st, the draft LS response is endorsed. Final LS is approved in R1-2205602.

[109-e-R17-ePos-06] – Ren Da (CATT)

Email discussion on updates to RRC parameters from new agreements, until May 17

R1-2205404 FL Summary of updates to RRC parameters for Rel-17 positioning enhancements Moderator (CATT)

Decision: As per email decision posted on May 19^th,

Agreement

Adopt the following changes to the previous agreement made in RAN1#105e

· For both UE-based and UE-assisted DL-AOD, the UE can be requested subject to UE capability to measure and report (for UE-assisted) ~~the~~N PRS RSRPP of the first path, where N can be {1, 2, 3, …, 24}.

R1-2205539 Updated RRC parameters for Rel-17 positioning enhancements Moderator (CATT)

R1-2205405 [Draft] LS on updates of RRC parameters for Rel-17 positioning enhancements CATT

Decision: As per email decision posted on May 20^th, the draft LS with attachment R1-2205539 are endorsed. Final LS to RAN2 is approved in R1-2205406.

[109-e-R17-ePos-07] – Ryan (Nokia)

Email discussion on LS R1-2205493 on expected AoA and AoD parameters, until May 20

R1-2205617 Summary #1 for discussion on reply LS related to expected AOA/AOD Moderator (Nokia)

R1-2205618 [DRAFT] Reply LS on expected AoA and AoD parameters Nokia

Decision: As per email decision posted on May 20^th, the draft LS is endorsed. Final LS response to R1-2205493 is approved in R1-2205619.

8.5.1 Accuracy improvements

For any maintenance on accuracy improvements related enhancements

R1-2203099 Maintenance of Rel-17 positioning accuracy improvements Huawei, HiSilicon

R1-2205095 Maintenance of NR Positioning Accuracy Nokia, Nokia Shanghai Bell (rev of R1-2203175)

R1-2203436 Maintenance on enhancements of accuracy improvements for NR positioning CATT

R1-2203515 Maintenance on accuracy improvements for NR positioning enhancements vivo

R1-2203619 Remaining issues on accuracy improvement for Rel-17 positioning ZTE

R1-2203864 Maintenance on accuracy improvement related enhancement Samsung

R1-2203960 Maintenance of Rel-17 Positioning Accuracy Enhancement OPPO

R1-2204127 Remaining issues for accuracy enhancements for NR positioning InterDigital, Inc.

R1-2204275 Remaining issues on accuracy improvements CMCC

R1-2204346 Remaining issue on accuracy improvements NTT DOCOMO, INC.

R1-2204942 Maintenance of accuracy improvements for NR positioning enhancements Ericsson

R1-2204985 Maintenance on Accuracy Improvements Qualcomm Incorporated

[109-e-R17-ePos-02] – Ren Da (CATT)

Email discussion under 8.5.1 for maintenance on accuracy improvements by mitigating UE Rx/Tx and/or gNB Rx/Tx timing delays, for issues 1-1, 1-2, 1-6, 1-9, 1-13, 1-14, 1-15, 1-16 in R1-2205097, including discussion on LS in R1-2203024

- 1^st check point: May 13 (any RRC impact by May 12)

- Final check point: May 18

R1-2205161 FL Summary for mitigating UE/gNB Rx/Tx timing delays Moderator (CATT)

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

Conclusion

RAN1 will not further discuss how to define the framework for Tx TEG unless RAN4 explicitly sends an LS with an action to RAN1.

· Include the conclusion in reply LS to RAN4.

Agreement

It is RAN1’s understanding that when the TEG feature is combined with the reporting of multiple measurement instances as liaised in R1-2202922, the applicability of a reported UE/TRP Rx/RxTx TEG is limited to the measurements contained within the single measurement instance of a measurement report in which the Rx/RxTx TEG information is provided, and only to measurements that are tagged with the corresponding Rx/RxTx TEG ID.

· Include above statement in reply LS to RAN2, RAN3, RAN4

Conclusion

RAN1 will not further discuss how to handle change/updates of the UE Tx TEG association in higher-layer signaling unless RAN2 explicitly sends an LS with an action to RAN1.

· Include the conclusion in reply LS to RAN2.

Agreement

· Support up to 32 measurement instances in a single measurement report.

· Inform RAN2/RAN3 on RAN1’s decision

Agreement

· TP1 (for TS38.214 v17.1.0, clause 5.1.6.5) and TP2 (for TS38.214 v17.1.0, clause 6.2.1.4) of (Round 2) Proposal 7-1 in section 7.1 of R1-2205161 are endorsed.

Agreement

· The Text Proposal (for TS38.214 v17.1.0, clause 6.2.1.4) of (Round 3) Proposal 7-2 in section 7.2 of R1-2205161 is endorsed.

Decision: As per email decision posted on May 20^th,

Agreement

Include the following in the reply LS to RAN4, RAN2, RAN3:

· In RAN1’s understanding, each measurement instance may allow up to 8 reports (or changes) of the TEG-SRS association information for each TEG ID.

· RAN1 kindly requests RAN4 for the confirmation of the understanding.

Agreement

In the reply LS to RAN4 (cc RAN2/RAN3),

· Ask RAN4 whether UE Rx/RxTx TEG margins are provided to LMF as UE capability, or as LPP signalling parameters outside of UE capability signaling. If RAN4 considers UE Rx/RxTx TEG margins are provided to LMF as LPP signalling parameters outside of UE capability signaling, further ask RAN4 the following questions:

o Whether a single timing error margin value is provided per Rx TEG/RxTx TEG type in a single LPP message, even if it has multiple measurement instances;

o Whether the timing error margin values for a Rx TEG/RxTx TEG type in different LPP messages can be different;

· RAN1 understands the TRP Rx/RxTx TEG margins are provided to the LMF via an NRPPa message and which message to contain the TEG margins is up to RAN3.

Agreement

In the reply LS to RAN4 (cc RAN2/RAN3), request RAN4 to confirm the following RAN1’s understanding:

· If a UE/TRP supports both Rx TEG(s) and RxTx TEG(s), the UE/TRP may select different timing error margin values for the Rx TEG(s) and RxTx TEG(s).

Final summary in R1-2205162 FL Summary #2 for mitigating UE/gNB Rx/Tx timing delays Moderator (CATT)

R1-2205381 [Draft] Reply LS on the UE/TRP TEG framework CATT

Decision: As per email decision posted on May 21^st, the draft reply LS is endorsed. Final version is approved in R1-2205382.

[109-e-R17-ePos-03] – Florent (Ericsson)

Email discussion under 8.5.1 for maintenance on accuracy improvements for UL-AoA and DL-AoD positioning solutions, for issues 2-2, 3-1, 3-2, 3-3, 3-5, 3-6, 3-8, 3-10 and 3-15 in R1-2205097

- 1^st check point: May 13 (any RRC impact by May 12)

- Final check point: May 18

R1-2205524 Moderator Summary for [109-e-R17-ePos-03] maintenance on accuracy improvements for UL-AoA and DL-AoD positioning solutions Moderator (Ericsson)

Decision: As per email decision posted on May 19^th,

Agreement

For DL-AoD, the additional RSRPP measurement takes from -30 dB to 30 dB as the reporting range in reference to the first RSRPP measurement

· Send an LS to RAN2 and RAN4 informing of the agreement.

Decision: As per email decision posted on May 20^th,

Agreement

In response to RAN3’s question in the LS R1-2203040: information on the Rx Diversity options does not need to be signalled to LMF.

· Note: when UL SRS-RSRP is reported, whether to use Option1 or Option 2 for UL SRS-RSRPP is up to gNB implementation.

Agreement

Support reporting absolute RSRPP for the PRS-RSRPP measurement in DL-TdoA and multi-RTT for at least the additional paths.

Conclusion

With regards to DL PRS-RSRPP reporting for DL-TDOA and Multi-RTT, the Rx branch corresponding to the reported DL PRS-RSRPP if the Rx diversity is in use by the UE is up to UE implementation.

[109-e-R17-ePos-04] – Ryan (Nokia)

Email discussion under 8.5.1 for maintenance on enhancements of information reporting from UE and gNB for multipath/NLOS mitigation, for issue 4-1 in R1-2205097

- 1^st check point: May 13 (any RRC impact by May 12)

- Final check point: May 18

R1-2205201 Feature Lead Summary #1 for Potential multipath/NLOS mitigation Moderator (Nokia)

See the conclusion in x5201.

8.5.22 Other

For any other maintenance issues on NR Positioning Enhancements

R1-2203176 Maintenance of Other NR positioning enhancements Nokia, Nokia Shanghai Bell

R1-2203437 Maintenance on latency reduction for NR positioning CATT

R1-2203516 Discussion on other maintenance issues on NR positioning enhancements vivo

R1-2203620 Remaining issues other than accuracy improvement for Rel-17 Positioning ZTE

R1-2203786 Remaining issues on PRS collision detection xiaomi

R1-2203865 Maintenance on latency and efficiency improvement related enhancement Samsung

R1-2203961 Maintenance of Rel-17 Positioning enhancement other than accuracy enhancement OPPO

R1-2204128 Remaining issues for NR positioning InterDigital, Inc.

R1-2204276 Remaining issues on latency improvements CMCC

R1-2204522 Discussion on maintenance for NR positioning other enhancements LG Electronics

R1-2204903 Maintenance of Rel-17 positioning latency and efficiency improvements Huawei, HiSilicon

R1-2204943 Remaining issues for NR positioning enhancements Ericsson

R1-2204986 Maintenance on Other Issues in NR Positioning Enhancements Qualcomm Incorporated

[109-e-R17-ePos-05] – Su (Huawei)

Email discussion under 8.5.2 for maintenance on latency improvements for both DL and DL+UL positioning methods for issues 5-1, 5-2, 5-3, 5-4, 5-5, 5-6, 5-7, 5-8, 5-9, 5-10, 5-11, 5-12, 5-18 and 6-4 in R1-2205097, and on positioning for UEs in RRC_ INACTIVE for issues 6-1, 6-2, 6-3, 6-6, 6-7, 6-9 in R1-2205097, including discussion on LSs in R1-2203022 R1-2203023 R1-2203026 R1-2203028

- 1^st check point: May 13 (any RRC impact by May 12)

- Final check point: May 18

R1-2205255 Summary #1 of [109-e-R17-ePos-05] on latency improvements and RRC_INACTIVE Moderator (Huawei)

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

Agreement

Support the LMF to request the Rx beam sweeping factor.

Agreement

The request from LMF on the Rx beam sweeping factor is a single bit per positioning method, which can take two values.

· Value 1: Equal to the UE’s reported Rx beam sweeping factor in the corresponding capability for the band UE supports the feature, and equal to 8 for the FR2 bands that UE does not support the feature.

· Value 2: Equal to 8 (default assumption) for FR2 bands.

· The bit value should be set to the same across DL-TDOA, DL-AoD, and Multi-RTT for hybrid positioning.

Agreement

Reply to the RAN4’s question in LS R1-2203026 with

· RAN1 already agreed in RAN1#108-e that inside each single instance of a PRS processing window, a single PFL can be measured. This is applicable to all Types of MG-less PRS processing.

· In addition, it is RAN1 understanding that the applicable number of positioning frequency layers for the gapless PRS measurement within a PRS processing window is one across all instances of the PRS processing window.

Agreement

· The Text Proposal (for TS38.214 v17.1.0, clause 5.1.6.5) of Proposal 2.9.1-1a in section 5.1 of R1-2205255 is endorsed.

Agreement

For Option 2 of SRS for positioning transmission in RRC_INACTIVE, the UE capability of switching time between SRS Tx and other Tx in initial UL BWP is introduced also for FDD.

· The switching time value(s) are left up to RAN4 discussion

· If the transmission of SRS for positioning with the switching time collides in time domain with other UL transmission for FDD, the SRS for positioning transmission is dropped in the symbols where the collision occurs.

Decision: As per email decision posted on May 17^th,

Agreement

· The Text Proposal (for TS38.214 v17.1.0, clause 5.1.6.5) of Proposal 2.4.1-1a in section 5.1 of R1-2205255 is endorsed.

R1-2205449 Draft reply LS on lower Rx beam sweeping factor for latency improvement Moderator (Huawei)

Decision: As per email decision posted on May 17^th, the draft reply LS to R1-2203022 is endorsed. Approved in R1-2205450.

R1-2205451 Draft reply LS on applicable number of PFL for the gapless PRS measurement Moderator (Huawei)

Decision: As per email decision posted on May 17^th, the draft reply LS to R1-2203026 is endorsed. Approved in R1-2205452.

Decision: As per email decision posted on May 19^th,

Conclusion

UL MAC CE based request for a PRS processing window by the UE to the gNB is not supported

Conclusion

It is RAN1 understanding that the maximum number of PPWs that can be activated/deactivated by a single DL MAC-CE is up to RAN2.

· The previous agreement of maximum number of PPWs that can be activated/deactivated by a single DL MAC-CE is reverted.

Note: It means from RAN1 perspective, RAN1 intends to agree that up to 4 PPWs can be activated/deactivated by a single DL MAC CE as specified in TS 38.321 v17.0.0.

Agreement

For Option 2 of SRS for positioning transmission in RRC_INACTIVE, the UE capability of switching time between SRS Tx and other Tx in initial UL BWP is introduced also for SUL.

· The switching time value(s) are left up to RAN4 discussion

· If the transmission of SRS for positioning in SUL with the switching time collides in time domain with other UL transmission for SUL, the SRS for positioning transmission is dropped in the symbols where the collision occurs.

Agreement

The feature of Option 2 SRS transmission in RRC_INACTIVE state is supported for SUL.

· Network identifies UE support of the feature by

o The SRS resource capability reported for an SUL band, and

o The supported NUL+SUL band combination that follows the capability reporting of FG 6-16 and FG 6-17

Agreement

For the transmission of SRS (option 1 and option 2) associated with SUL

· No UL carrier selection is specified.

· Simultaneous transmission of SRS for positioning on NUL and SUL in RRC_INACTIVE state is not supported.

Decision: As per email decision posted on May 20^th,

Agreement

The PRS collision detection timeline for the case when PRS is lower priority than the DL signals/channels is define as following.

· For an activated type 1A and type 1B PRS processing window

o If UE determines the presence of other DL signals/channels except SSB of higher priority than PRS in the PPW no later than [N symbol/T ms] before the start of the PPW, UE expects to receive the DL signals/channels and drop the all DL PRS in the PPW.

· For an activated type 2 PRS processing window

o If UE determines the presence of other DL signals/channels except SSB of higher priority than PRS on a PRS symbol no later than [N symbol/T ms] before the PRS symbol, UE expects to receive the DL signals/channels and drop the PRS symbol.

Agreement

The PRS collision detection timeline for the case when PRS is lower priority than the DL signals/channels is define as following.

· For a type 1A and type 1B PRS processing window

o If UE determines the presence of other DL signals/channels except SSB of higher priority than PRS in the PPW later than [N symbol/T ms] before the start of the PPW, UE is not required to receive the other DL signals/channels except SSB of higher priority and may receive the DL PRS in the PPW.

· For a type 2 PRS processing window considered active

o If UE determines the presence of other DL signals/channels except SSB of higher priority than PRS on a PRS symbol later than [N symbol/T ms] before the PRS symbol, UE is not required to receive the other DL signals/channels except SSB of higher priority and may receive the PRS symbol.

· Note 1: This implies that if the scheduling of other DL signals/channels of higher priority arrives too late, UE may consider the PRS as higher priority than the other DL signals/channels.

· Note 2: If the scheduling of other DL signals/channels of higher priority arrives too late, it is up to UE implementation whether to receive the other DL signals/channels.

Agreement

· For UE supporting Type-1A or Type-1B PRS processing window, UE may report (N, T) and (N2, N2) in the capability signalling

o The reported (N, T) in the capability signalling is similar to the legacy (N, T) in FG 13-1, which assumes to measure the N ms of PRS within a PPW but the processing of the measured PRS may be outside the PRS processing window.

o The reported (N2, T2) in the capability signalling assumes to measure and process the N2 ms of PRS only within the PRS processing window length (which covers the T2).

o Add the following Note to the corresponding FG in the UE feature spreadsheet

§ Note: The (N2, T2) UE capabilities is interpreted such that the UE is capable of measuring up to N2 ms PRS within a PPW and is capable of completing the PRS processing within the PPW, e.g., if the time duration from the last symbol of the measured PRS resource(s) inside the PPW, to the end of PPW is not smaller than T2 ms

· For UE supporting Type-2 PRS processing window, UE may report (N, T) in the capability signalling similar to the legacy (N, T) in FG 13-1

o Assuming the UE to measure the PRS within the PRS processing window and but the processing of the measured PRS may be outside a PRS processing window.

· Note: when the processing time T exceeds the PPW length, other DL data channels/signals that are outside of the PPW but within the periodic T can be received by the UE.

· Discuss in the UE feature session the values {N, T} for all types.

Final summary in R1-2205256.

RAN1#110

8.55 Maintenance on NR Positioning Enhancements

R1-2208136 Session notes for 8.5 (Maintenance on NR Positioning Enhancements) Ad-Hoc Chair (Huawei)

[110-R17-Pos] Email to be used for sharing updates on online/offline schedule, details on what is to be discussed in online/offline sessions, tdoc number of the moderator summary for online session, etc – Ren Da (CATT)

R1-2205773 Maintenance of Rel-17 positioning Huawei, HiSilicon

R1-2205774 Correction to the condition of Rx beam index reporting Huawei, HiSilicon

R1-2205775 Correction of SRS and BWP restriction Huawei, HiSilicon

R1-2205906 Draft CR on DL-AOD positioning measurement for 38.214 ZTE

R1-2205907 Alignment CR on positioning for 38.214 ZTE

R1-2205908 Draft CR on RSTD measurement for 38.214 ZTE

R1-2205909 Draft CR on PRS processing sample for 38.214 ZTE

R1-2205910 Draft CR on PPW timeline issue for 38.214 ZTE

R1-2205911 Draft CR on remaining issues of PPW for 38.214 ZTE

R1-2205912 Discussion on some remaining issues for NR positioning ZTE

R1-2205913 Draft CR on RRC_INACTIVE positioning issue for 38.214 ZTE

R1-2206270 Corrections on M-sample measurement OPPO

R1-2206271 Correction for TEG-based DL positioning methods OPPO

R1-2206272 Correction for TEG-based UL positioning methods OPPO

R1-2206367 Correction on the definition of timing advance (TADV) CATT

R1-2206368 Correction on PRS reception procedure CATT

R1-2206486 Maintenance of NR Positioning Enhancements Nokia, Nokia Shanghai Bell

R1-2206487 Correction on PRS measurement outside MG Nokia, Nokia Shanghai Bell

R1-2206488 Correction on PRS collision timeline Nokia, Nokia Shanghai Bell

R1-2206489 Correction on PRS RSTD and PRS RSRPP reporting Nokia, Nokia Shanghai Bell

R1-2206662 Draft CR on UE TX TEG description for 38.214 ZTE

R1-2206742 Correction on accuracy improvements for NR positioning vivo

R1-2206743 Correction on latency and efficiency improvements for NR positioning vivo

R1-2206744 Discussion on accuracy improvements for NR positioning vivo

R1-2206745 Discussion on latency and efficiency improvements for NR positioning vivo

R1-2206797 Maintenance on NR Positioning Enhancements Samsung

R1-2206798 Draft CR on NR Positioning Enhancements Samsung

R1-2207194 Draft CR on NR R17 Positioning PPW Action Timelines Qualcomm Incorporated

R1-2207195 Maintenance for NR R17 Positioning Qualcomm Incorporated

R1-2207609 Draft CR on DL PRS measurement within DL PRS processing window Ericsson

R1-2207610 Motivation for Draft CR on DL PRS measurement within DL PRS processing window Ericsson

R1-2207611 Draft CR for higher layer parameter alignment Ericsson

R1-2207643 Correction of Rx diversity option for DL-PRS RSRPP reporting Huawei, HiSilicon

R1-2207644 Correction to PPW Huawei, HiSilicon

R1-2207645 Correction of BWP for SRS Huawei, HiSilicon

From AI 5

R1-2207812 LS on DL-PRS measurements with reduced samples capability RAN2, ZTE

R1-2207906 Summary on LS for reduced PRS samples capability Moderator (ZTE)

Agreement

· RAN1 is not willing to revise the FG 27-3-1. RAN1 thinks a unified design is desirable and recommends RAN4 to change FG 14-2 to per band.

R1-2207940 Reply LS on DL-PRS measurements with reduced samples capability RAN1, ZTE

Decision: Reply LS is approved.

From AI 5

R1-2205712 LS on timing advance (TADV) report mapping for NR UL E-CID positioning RAN4, Ericsson

R1-2207892 Summary of discussion on LS on timing advance (TADV) report mapping for NR UL E-CID positioning Moderator (Ericsson)

Conclusion: No response is needed from RAN1, and there is no impact to RAN1 specifications.

R1-2207689 FL Summary for mitigating UE/gNB Rx/Tx timing delays Moderator (CATT)

Agreement

· Adopt the following changes for TS 38.214 and prepare the corresponding CR (Moderator (CATT)

------- Proposed changes for TS 38.214 -------

5.1.6.5 PRS reception procedure

The UE may be configured to measure and report, subject to UE capability, up to 4 DL RSTD measurements per pair of dl-PRS-ID with each measurement between a different pair of DL PRS resources or DL PRS resource sets within the DL PRS configured for those dl-PRS-ID. If the UE is not configured to report with multiMeasInSameReport-r17, tThe up to 4 measurements being performed on the same pair of dl-PRS-ID and all DL RSTD measurements in the same report use a single reference timing. If the UE is configured to report with multiMeasInSameReport-r17, the up to 4 measurements being performed on the same pair of dl-PRS-ID and all DL RSTD measurements in the same measurement instance of the same report use a single reference timing.

R1-2207943 Correction on PRS reception procedure Moderator (CATT), ZTE, vivo

Decision: Revise R1-2207943 to delete “draft” from the title, and to show all changes with revision marks. Final CR (38.214, Rel-17, CR#0292r1, Cat F) is agreed in R1-2208170.

Agreement

· Adopt the following changes to TS 38.214 and prepare the corresponding CR (Moderator(CATT)

------- Proposed changes for TS 38.214 -------

6.2.1.4 UE sounding procedure for positioning purposes

<Unchanged parts omitted>

For operation on the same carrier, if an SRS configured by the higher parameter SRS-PosResource collides with a scheduled PUSCH, the SRS is dropped in the symbols where the collision occurs.

The UE does not expect to be configured with SRS-PosResource on a carrier of a serving cell with slot formats comprised of DL and UL symbols, not configured for PUSCH/PUCCH transmission.

~~The UE may be configured, subject to UE capability, to report~~ ~~UE Tx TEGs (Timing Error Group), where~~

Timing Error Group (TEG) at UE side is defined:

- UE Tx TEG is associated with the transmissions of one or more UL SRS resources for the positioning purpose, which have the Tx timing error difference within a certain margin.

The UE may be configured to report, subject to UE capability, association information of the already transmitted SRS resource(s) configured by the higher layer parameter SRS-PosResource with UE Tx TEG(s) via higher layer parameter [ueTxTEG].

<Unchanged parts omitted>

R1-2207944 Correction on UE sounding procedure for positioning purposes Moderator(CATT), ZTE, vivo

Decision: Revise R1-2207944 to show all changes with revision marks. Final CR (38.214, Rel-17, CR#0293r1, Cat F) is agreed in R1-2208171.

R1-2207973 FL Summary for mitigating UE/gNB Rx/Tx timing delays Moderator (CATT)

Agreement

· The parameter name alignments TPs for TS 38.214 in Proposal 4-6.1 and Proposal 4-6.2 in section 4 of R1-2207973 are recommended to the specification editors.

R1-2207746 Feature Lead Summary #1 for Maintenance of NR positioning Enhancements (AOD topics) Moderator (Ericsson)

R1-2205906 Draft CR on DL-AOD positioning measurement for 38.214 ZTE

Agreement

· Endorse in principle the draft CR in R1-2205906, and prepare the corresponding CR (Moderator (Ericsson)

R1-2207988 CR on DL-AOD positioning measurement for 38.214 Moderator (Ericsson), ZTE

Decision: (38.214, Rel-17, CR#0294, Cat F) is agreed.

Agreement

· Adopt the following modifications into TS 38.214 for PRS RSRPP reporting, and prepare the corresponding CR (Moderator (Ericsson)

< Unchanged parts are omitted >

The UE may be configured to measure and report, subject to UE capability, up to 24 DL PRS-RSRP measurements on different DL PRS resources associated with the same dl-PRS-ID. When the UE reports DL PRS-RSRP measurements from one DL PRS resource set, the UE may indicate which DL PRS-RSRP measurements associated with the same higher layer parameter nr-DL-PRS-RxBeamIndex [17, TS 37.355] have been performed using the same spatial domain filter for reception if for each nr-DL-PRS-RxBeamIndex reported there are at least 2 DL PRS-RSRP measurements associated with it within the DL PRS resource set. The UE may be configured to measure and optionally report ~~via higher layer signaling nr-DL-PRS-FirstPathRSRP-Result,~~ subject to UE capability, up to 24 DL PRS RSRPP for the first detected path on different DL PRS resources associated with the same dl-PRS-ID.

The UE may be configured to optionally report a differential DL RSRPP for a PRS resource with reference to [nr-DL-PRS-FirstPathRSRP-Result] and/or a differential DL PRS RSRP with reference to [nr-DL-PRS-RSRP-Result] via higher layer parameter [NR-DL-AoD-AdditionalMeasurementElement].

< Unchanged parts are omitted >

R1-2207989 CR on PRS RSRPP reporting for 38.214 Moderator (Ericsson), vivo

Decision: (38.214, Rel-17, CR#0295, Cat F) is agreed.

Agreement

· Adopt the following modifications into TS 38.215, and prepare the corresponding CR (Moderator (Ericsson)

========================= Unchanged parts =========================

5.1.35 DL PRS reference signal received path power (DL PRS-RSRPP)

Definition

DL PRS reference signal received path power (DL PRS-RSRPP), is defined as the power of the linear average of the channel response at the i-th path delay of the resource elements that carry DL PRS signal configured for the measurement, where DL PRS-RSRPP for the 1st path delay is the power contribution corresponding to the first detected path in time.

For frequency range 1, the reference point for the DL PRS-RSRPP shall be the antenna connector of the UE. For frequency range 2, DL PRS-RSRPP shall be measured based on the combined signal from antenna elements corresponding to a given receiver branch.

For frequency range 1 and 2, if receiver diversity is in use by the UE for DL PRS-RSRPP measurements, the reported DL PRS-RSRPP value included in the higher layer parameter NR-DL-AoD-MeasElement for the first and additional measurements shall be provided for the same receiver branch(es) as applied for DL PRS-RSRP measurements.

Applicable for

RRC_CONNECTED,

RRC_INACTIVE

R1-2207990 CR on PRS RSRPP for 38.215 Moderator (Ericsson), Huawei, HiSilicon

Decision: (38.215, Rel-17, CR#0045, Cat F) is agreed.

MCC: Apply the correct CR# before submission to plenary.

R1-2207747 Feature Lead Summary #2 for Maintenance of NR positioning Enhancements (AOD topics) Moderator (Ericsson)

R1-2205907 Alignment CR on positioning for 38.214 ZTE

Agreement

Endorse the draft CR R1-2205907 as part of the alignment CR from the specification editors, excluding the following changes:

If Tthe UE is ~~expected~~ to measure the DL PRS resource outside the active DL BWP or with a numerology different from the numerology of the active DL BWP, if the measurement isshould be made during a configured measurement gap.

Agreement

· Endorse the TP below for TS38.214

----- Start of TP -----

5.1.6.5 PRS reception procedure

< Unchanged parts are omitted >

The UE may be configured to measure and report, subject to UE capability, up to 24 DL PRS-RSRP measurements on different DL PRS resources associated with the same dl-PRS-ID. When the UE reports DL PRS-RSRP measurements from one DL PRS resource set, the UE may indicate which DL PRS-RSRP measurements associated with the same higher layer parameter nr-DL-PRS-RxBeamIndex [17, TS 37.355] have been performed using the same spatial domain filter for reception if for each nr-DL-PRS-RxBeamIndex reported there are at least 2 DL PRS-RSRP measurements associated with it within the DL PRS resource set. When the UE reports DL PRS-RSRP measurements for a DL PRS resource, the reported multiple DL PRS-RSRP measurements associated with the same or different higher layer parameter nr-DL-PRS-RxBeamIndex may have the same or different timestamps. The UE may be configured to measure and optionally report via higher layer signaling nr-DL-PRS-FirstPathRSRP-Result, subject to UE capability, up to 24 DL PRS RSRPP for the first detected path on different DL PRS resources associated with the same dl-PRS-ID.

< Unchanged parts are omitted >

----- End of TP -----

R1-2208243 Correction on PRS reception procedure Moderator (Ericsson), CATT

Decision: (38.214, Rel-17, CR#0326, Cat F) is agreed.

R1-2207825 Summary #1 of positioning latency improvements and RRC_INACTIVE Moderator (Huawei)

Conclusion

· For FG 27-3-3, UE shall report either component 2a or component 2b, but not both components.

R1-2207826 Summary #2 of positioning latency improvements and RRC_INACTIVE Moderator (Huawei)

Agreement

· Endorse the TP of proposal 2.2-1b in R1-2207826 regarding capturing the priority states to clause 5.1.6.5 of TS 38.214.

Final CR (38.214, Rel-17, CR#0301, Cat F) is agreed in:

R1-2208017 CR on priority states within the PRS processing window Moderator (Huawei), Ericsson, HiSilicon

Agreement

· Endorse the TP of proposal 3.1-1c in R1-2207826 regarding PRS reception and SRS transmission in RRC_INACTIVE state to clauses 5.1.6.5 and 6.2.1.4 of TS 38.214.

Final CR (38.214, Rel-17, CR#0305, Cat F) is agreed in:

R1-2208021 CR on PRS reception and SRS transmission outside initial BWP Moderator (Huawei), vivo, ZTE, HiSilicon

Agreement

· Endorse the draft CRs R1-2205909 and R1-2206270 regarding the reduced PRS processing samples to clause 5.1.6.5 of TS 38.214.

Final CRs in:

R1-2208018 CR on PRS processing sample for 38.214 Moderator (Huawei), ZTE

(38.214, Rel-17, CR#0302, Cat F) is agreed

R1-2208019 Corrections on M-sample measurement Moderator (Huawei), OPPO

(38.214, Rel-17, CR#0303, Cat F) is agreed

Agreement

· Endorse the TP of proposal 2.9-2a in R1-2207826 to clause 5.1.6.5 of TS 38.214.

Final CR (38.214, Rel-17, CR#0304, Cat F) is agreed in:

R1-2208020 CR on the positioning frequency layer within a PPW and UE capability for the PPW Moderator (Huawei), ZTE

Agreement

· The changes in R1-2207611 are endorsed, and recommended to be merged into the editor alignment CR.

Agreement

· The changes in R1-2207645 regarding BWP for SRS to clause 7.3.1 of TS 38.213 are endorsed.

Final CR (38.213, Rel-17, CR#0336, Cat F) is agreed in:

R1-2208022 Correction of BWP for SRS Moderator (Huawei), HiSilicon

Agreement

With regards to the action time for the PRS prioritization over other DL channels

· Alt.1: support N = N2 (clause 6.4 of TS 38.214) for the subcarrier spacing of the PDCCH.

Further revised as follows:

With regards to the action time for the PRS prioritization over other DL channels

· Alt.1: support N = N2 (clause 6.4 of TS 38.214) for the subcarrier spacing of the ~~PDCCH~~PRS.

R1-2208218 Draft CR on completing the PPW processing timeline Moderator (Huawei), Qualcomm, ZTE, Nokia

Agreement

Decision: The draft CR is endorsed. Final CR (38.214, Rel-17, CR#0324, Cat F) is agreed in:

R1-2208239 CR on completing the PPW processing timeline Moderator (Huawei), Qualcomm, ZTE, Nokia

Final summary in R1-2208217.

RAN1#110-bis-e

8.55 Maintenance on NR Positioning Enhancements

R1-2210681 Session notes for 8.5 (Maintenance on NR Positioning Enhancements) Ad-Hoc Chair (Huawei)

[110bis-e-R17-Pos-01] – Ren (CATT)

Email discussion to determine maintenance issues to be handled in RAN1#110bis-e by October 12

- Additional email discussions will be set up once the maintenance issues for RAN1#110bis-e are determined

R1-2210266 Summary for preparation phase on maintenance of Rel-17 WI on NR positioning enhancements Moderator (CATT)

Decision: As per email decision posted on Oct 12th,

Conclusion of [110bis-e-R17-Pos-01]:

For Rel-17 maintenance, the following the issues described in R1-2210266 are to be handled at RAN1#110bis-e:

· For accuracy improvements by mitigating UE Rx/Tx and/or gNB Rx/Tx timing delays: 1-1, 1-2

· For accuracy improvements for DL-AoD positioning solutions: 3-1, 3-2, 3-3

· For information reporting from UE and gNB for multipath/NLOS mitigation: 4-2. Additionally 4-1 and 4-3 (as recommendation for editor’s alignment CR)

· For latency improvements for both DL and DL+UL positioning methods: 5-1, 5-4, 5-5. Additionally 5-3 (as recommendation for editor’s alignment CR)

· For RRC_ INACTIVE positioning: 6-1

From AI 5.

/To be handled using NWM – please use 110bis-e-NWM-R17-Pos-02 as the document name

R1-2208604 Correction on SCS for NR DL PRS vivo

[110bis-e-R17-Pos-02] – Qi (Samsung)

Email discussion on incoming RAN2 LS in R1-2208325 on the support of positioning in FR2-2

R1-2210527 Summary of discussion on incoming RAN2 LS in R1-2208325 on the support of positioning in FR2-2 Moderator (Samsung)

Decision: As per email decision posted on Oct 15th,

Conclusion

DL-PRS with 480/960 kHz SCS are not supported in FR2-2 in R17.

Conclusion

From RAN1 perspective, companies have different views on whether SRS for positioning with 480/960 kHz SCS are supported in FR2-2 in R17, and RAN1 will not optimize the specifications for SRS for positioning with 480/960 kHz SCS in FR2-2 in R17.

Agreement

· The draft LS reply to RAN2 simply providing these conclusions is endorsed based on the text provided in section 7.1 of R1-2210527. Final LS is approved in R1-2210528.

R1-2208734 Correction on DL PRS subcarrier spacings for FR2-2 Nokia, Nokia Shanghai Bell

Decision: As per email decision posted on Oct 16th,

Agreement

· The draft CR in R1-2208734 is endorsed in principle. Final CR (TS38.214, Rel-17, CR#0353, Cat F) is agreed in

R1-2210595 Correction on DL PRS subcarrier spacings for FR2-2 Moderator (Samsung), Nokia, Nokia Shanghai Bell, vivo

R1-2208939 Correction on UE Tx TEG association information reporting CATT

R1-2208940 Discussion on UE Tx TEG association information reporting CATT

R1-2209211 Draft CR on UE TEG framework ZTE

R1-2210101 Draft CR to 38.214 on definition of UE Tx TEG Ericsson

[110bis-e-R17-ePos-03] – Ren Da (CATT)

Email discussion for maintenance on accuracy improvements by mitigating UE Rx/Tx and/or gNB Rx/Tx timing delays for issues 1-1, 1-2 in R1-2210266

- Check points: October 14, October 19

R1-2210435 FL Summary for maintenance on accuracy improvements by mitigating UE Rx/Tx and/or gNB Rx/Tx timing delays Moderator (CATT)

R1-2210737 CR on UE TEG framework Moderator (CATT), ZTE

Decision: As per email decision posted on Oct 19th, the draft CR to 38.214 in R1-2210736 on error margins for Rx/RxTx TEGs is postponed to the next meeting.

R1-2208601 Correction on missing of DL PRS-RSRPP vivo

R1-2209837 Correction to the Rx beam reporting condition for DL-AoD Huawei, HiSilicon

R1-2210211 Adding DL PRS-RSRPP to the applicable measurements Huawei, HiSilicon

R1-2210212 Correction to the applied positioning method for RSRP and RSRPP reporting Huawei, HiSilicon

[110bis-e-R17-ePos-04] – Florent (Ericsson)

Email discussion for maintenance on accuracy improvements for DL-AoD positioning solutions for issues 3-1, 3-2, 3-3 in R1-2210266

- Check points: October 14, October 19

R1-2210477 Feature Lead Summary #1 for maintenance on accuracy improvements for DL-AoD positioning solutions Moderator (Ericsson)

Decision: As per email decision posted on Oct 19th,

For issue 3-2

R1-2210628 Correction to the Rx beam reporting condition for DL-AoD Moderator (Ericsson), Huawei, HiSilicon

Agreement

· The draft CR in R1-2210628 is endorsed in principle. Final CR is agreed in R1-2210635 (TS38.214, Rel-17, CR#0359, Cat F).

For issue 3-1

R1-2210627 Correction adding DL PRS-RSRPP to the applicable measurements Moderator (Ericsson), vivo, Huawei, HiSilicon

Agreement

· The draft CR in R1-2210627 is endorsed in principle. Final CR is agreed in R1-2210634 (TS38.214, Rel-17, CR#0358, Cat F).

R1-2208603 Correction on description of LoS/NLoS indicator vivo

R1-2208732 Correction on PRS RSTD and PRS RSRPP reporting Nokia, Nokia Shanghai Bell

R1-2208731 Maintenance of NR Positioning Enhancements Nokia, Nokia Shanghai Bell

R1-2209458 Alignment CR on positioning for 38.214 ZTE

[110bis-e-R17-ePos-05] Email discussion for maintenance on enhancements of information reporting from UE and gNB for multipath/NLOS mitigation for issues 4-2, and for issues 4-1 and 4-3 as recommendation for editor’s alignment CR, in R1-2210266 – Ryan (Nokia)

- Check points: October 14, October 19

R1-2210461 Feature Lead Summary #1 for Maintenance of multipath/NLOS mitigation Moderator (Nokia)

Decision: As per email decision posted on Oct 15th,

For alignment TS38.214 CR:

· Text proposal provided in R1-2209458 Draft CR to 38.214 is endorsed for the editorial corrections.

R1-2208472 Maintenance of Rel-17 NR positioning Huawei, HiSilicon

R1-2208602 Correction on description alignment of ‘DL signals and channels‘ vivo

R1-2208731 Maintenance of NR Positioning Enhancements Nokia, Nokia Shanghai Bell

R1-2208733 Correction on SRS for positioning switching time Nokia, Nokia Shanghai Bell

R1-2209209 Draft CR on collision in PPW for inter-band case ZTE

R1-2209210 Draft CR on priority issue in PPW ZTE

R1-2209701 Discussion on SSB priority on PRS Samsung

R1-2209702 Draft CR for SSB priority on PRS Samsung

R1-2209703 Discussion on SRS collision timeline check in inactive state Samsung

R1-2209704 Draft CR for SRS collision timeline check in inactive state Samsung

R1-2209705 Discussion on PRS collision handling for UL signals in PPW Samsung

R1-2209706 Draft CR for PRS collision handling for UL signals in PPW Samsung

R1-2209838 Correction to the collision timeline for PRS and UL - 38.214 Huawei, HiSilicon

R1-2209839 Correction to the collision timeline for PRS and UL - 38.213 Huawei, HiSilicon

R1-2209840 Correction to the PRS processing window Huawei, HiSilicon

R1-2210213 Correction to numerology and CP for positioning in RRC_INACTIVE state Huawei, HiSilicon

[110bis-e-R17-ePos-06] Email discussion for maintenance on latency improvements for both DL and DL+UL positioning methods for issues 5-1, 5-4, 5-5, and 5-3 (as recommendation for editor’s alignment CR) in R1-2210266, and on positioning for UEs in RRC_ INACTIVE for issue 6-1 in R1-2210266 – Su (Huawei)

- Check points: October 14, October 19

R1-2210557 Summary #1 of [110bis-e-R17-ePos-06] positioning latency improvements and RRC_INACTIVE Moderator (Huawei),

Decision: As per email decision posted on Oct 15th,

For alignment TS38.214 CR:

· Text proposal provided in R1-2208602 Draft CR to 38.214 is endorsed for the editorial corrections.

Agreement

· Endorse the following change to clause 6.2.1.4 of TS 38.214.

*Reason for change:*	Currently for SRS for positioning transmission in RRC Inactive mode some dropping rules are defined when the transmission is outside the initial UL BWP. However, the specification simply states “with the switching time” which is not clear what switching time is referred to and is not clear that it is the transmission plus the switching time.

*Summary of change:*	In Clause 6.2.1.4, clarify the switching time when the UE applies dropping rules for RRC Inactive mode transmission of SRS for positioning.

*Consequences if not approved:*	Unclear UE behvaior and incomplete specifications.

6.2.1.4 UE sounding procedure for positioning purposes

Subject to UE capability, the UE may be configured with an SRS resource for positioning associated with the initial UL BWP, and the SRS resource is transmitted inside the initial UL BWP during RRC_INACTIVE mode with the same CP and numerology as configured for the initial UL BWP. Subject to UE capability, the UE may be configured with an SRS resource for positioning outside the initial BWP including frequency location and bandwidth, numerology, and CP length for transmission of the SRS in RRC_INACTIVE mode. If the transmission of SRS for positioning outside the initial BWP in RRC_INACTIVE mode along with the switching time, indicated in higher layer parameter switchingTimeSRS-TX-OtherTX-, in unpaired spectrum, subject to UE capability, collides in time domain with other DL signals or channels or UL signals or channels, the SRS for positioning transmission is dropped in the symbol(s) where the collision occurs. If the transmission of SRS for positioning outside the initial BWP in RRC_INACTIVE mode along with the switching time, indicated in higher layer parameter switchingTimeSRS-TX-OtherTX, in paired spectrum or SUL band, subject to UE capability, collides in time domain with UL signals or channels on the same carrier, the SRS for positioning transmission is dropped in the symbol(s) where the collision occurs. The SRS resource for positioning outside the initial BWP in RRC_INACTIVE mode is configured in the same band and CC as the initial UL BWP.

Corresponding draft CR in:

R1-2210559 [draft] Correction on SRS for positioning switching time Moderator (Huawei), Nokia, Nokia Shanghai Bell

Decision: As per email decision posted on Oct 19th, the draft CR is endorsed. Final CR (TS38.214, Rel-17, CR#0350, Cat F) is agreed in R1-2210560.

R1-2210759 Draft CR on collision in Type 1B and Type 2 PPW for FR2 inter-band case Moderator (Huawei), ZTE

Decision: As per email decision posted on Oct 19th, the draft CR is endorsed. Final CR (TS38.214, Rel-17, CR#0366, Cat F) is agreed in R1-2210760.

Final summary in R1-2210558.

RAN1#111

8.55 Maintenance on NR Positioning Enhancements

R1-2212835 Session notes for 8.5 (Maintenance on NR Positioning Enhancements) Ad-Hoc Chair (Huawei)

Endorsed and contents incorporated below.

[111-R17-Pos] – Ren Da (CATT)

To be used for sharing updates on online/offline schedule, details on what is to be discussed in online/offline sessions, tdoc number of the moderator summary for online session, etc

Maintenance on accuracy improvements by mitigating UE Rx/Tx and/or gNB Rx/Tx timing delays

R1-2212544 FL Summary for mitigating UE/gNB Rx/Tx timing delays Moderator (CATT)

Configuration of UE Tx TEG association information reporting

R1-2211163 Discussion on configuration of UE Tx TEG association information reporting CATT

R1-2211162 Correction on configuration of UE Tx TEG association information reporting CATT

Agreement

· Draft CR in R1-2211162 is endorsed in principle.

Final CR (TS38.214, Rel-17, CR#0374, Cat F) is agreed in:

R1-2212754 Correction on configuration of UE Tx TEG association information reporting Moderator(CATT), CATT

MCC post-meeting: Clean-up of the CR coversheet is needed before submission to RAN.

UE TEG margin value report

R1-2211499 Draft CR on UE TEG margin value report ZTE

R1-2212503 draft CR for maintenance of NR positioning enhancements Ericsson

R1-2212752 Draft CR on UE TEG margin value report Moderator(CATT), ZTE, Ericsson

Agreement

· Draft CR in R1-2212752 is endorsed in principle.

Final CR is agreed in R1-2212753 (TS38.214, Rel-17, CR#0373, Cat F).

MCC post-meeting: Clean-up of the CR coversheet is needed before submission to RAN.

Maintenance on accuracy improvements for UL-AoA and DL-AoD positioning solutions

R1-2212600 Feature lead summary for maintenance of NR positioning enhancements Moderator (Ericsson)

Clarification of the limitation of 24 RSRP/RSRPP reports for AOD and 32 RSRP /RSRPP for DL-TDOA and Multi-RTT

R1-2210899 Remaining issues of Rel-17 positioning enhancements Huawei, HiSilicon

Conclusion

The maximum number of DL PRS-RSRPs and DL PRS-RSRPPs for the first path per TRP is 32 for DL-TDOA and Multi-RTT. No specification change needed.

Maintenance of multipath/NLOS mitigation

R1-2212604 Feature Lead Summary #1 for Maintenance of multipath/NLOS mitigation Moderator (Nokia)

RSRPP and RSTD measurement

R1-2211308 Maintenance of NR Positioning Enhancements Nokia, Nokia Shanghai Bell

R1-2211309 Correction on PRS RSTD and PRS RSRPP reporting Nokia, Nokia Shanghai Bell

Conclusion

It is RAN1’s understanding that the UE, when measuring DL PRS RSRPP and DL PRS RSTD on the same DL PRS resource, is to use the same first path for both measurements. No specification change needed.

Conclusion

It is RAN1’s understanding that the UE, when measuring DL PRS RSRPP and UE Rx-Tx time difference on the same DL PRS resource, is to use the same first path for both measurements. No specification change needed.

Maintenance on latency improvements for both DL and DL+UL positioning methods, and on positioning for UEs in RRC_ INACTIVE

R1-2212729 Summary #1 of positioning latency improvements and RRC_INACTIVE positioning Moderator (Huawei)

SSB in priority state st3

R1-2211308 Maintenance of NR Positioning Enhancements Nokia, Nokia Shanghai Bell

R1-2211310 Correction on DL PRS priority states in PPW Nokia, Nokia Shanghai Bell

R1-2212869 Correction on PRS processing during RACH procedure Moderator (Huawei), ZTE

Agreement

· The following text proposal with regards to the priority between PRS and SSB to clause 5.1.6.5 of TS 38.214 is endorsed.

The UE is expected to measure the DL PRS outside the measurement gap, subject to UE capability, if the DL PRS is inside the active DL BWP and has the same numerology as the active DL BWP and is within the DL PRS processing window indicated by higher layer parameter DL-PPW-PreConfig. The UE is not expected to measure the DL PRS outside the measurement gap if the expected received timing difference between the DL PRS from the non-serving cell and that from the serving cell, determined by the higher layer parameters nr-DL-PRS-ExpectedRSTD and nr-DL-PRS-ExpectedRSTD-Uncertainty, is larger than maximum Rx timing difference provided by UE capability. For receiving the DL PRS outside the measurement gap and within the DL PRS processing window, the priority between DL PRS and SSB is defined in [11, TS 38.133] and the UE determines the DL PRS priority as indicated by higher layer parameter priority subject to UE capability or as implied by UE capability, except for SSB:

- with value 'st1' where the DL PRS is higher priority than all the DL signal/channels ~~except SSB~~, or

- with value 'st2' where the DL PRS is lower priority than PDCCH and the PDSCH scheduled by DCI formats 1_1 or 1_2 with the priority indicator field in the corresponding DCI format set to 1, and is higher priority than other DL signals/channels ~~except SSB~~, or

- with value 'st3' where the DL PRS is lower priority than all the DL signals/channels ~~except SSB~~.

R1-2212867 Correction on DL PRS priority states in PPW Moderator (Huawei), Nokia, Nokia Shanghai Bell

Decision: The draft CR in R1-2212867 is endorsed. Final CR (TS 38.214, Rel-17, CR#0379, Cat F) is agreed in R1-2212868.

PRS and UL in the PPW

R1-2212020 Discussion on PRS collision handling for UL signals in PPW Samsung

R1-2212021 Draft CR for PRS collision handling for UL signals in PPW Samsung

Conclusion

RAN1 will not define the collision detection timeline between PRS and UL in the PPW, and the changes in R1-2212021 are not pursued.

PPW in RACH procedure

R1-2211498 Draft CR on priority issue in PPW ZTE

UE behaviour of other DL signals and channels

R1-2212494 Corrections on UE behaviour of other DL signals and channels Huawei, HiSilicon

N2 symbol interpretation

R1-2212495 Corrections on N2 symbols on the collision action timeline Huawei, HiSilicon

Conclusion

Regarding the N2 symbol interpretation for the collision timeline in the PPW:

· N2 symbol is associated with the actual UE PUSCH preparation capability.

Note: If UE supports PUSCH preparation capability 2, the N2 in the table 6.4-2 of 38.214 should be used.

Editorial corrections

R1-2212466 Corrections on parameters for NR positioning Huawei, HiSilicon

R1-2212731 Corrections on parameters for NR positioning Moderator (Huawei)

Decision:

For alignment TS 38.214 CR

The changes in the draft CR R1-2212731 (revised from R1-2212466) are endorsed for the editorial corrections.

Final summary in R1-2212730.

RAN1#112

8.55 Maintenance on NR Positioning Enhancements

R1-2302055 Session notes for 8.5 (Maintenance on NR Positioning Enhancements) Ad-Hoc Chair (Huawei)

[112-R17-Pos] – Ren Da (CATT)

To be used for sharing updates on online/offline schedule, details on what is to be discussed in online/offline sessions, tdoc number of the moderator summary for online session, etc

R1-2301831 FL Summary for Maintenance on NR Positioning Enhancements Moderator (CATT)

From Tuesday session

R1-2300801 Alignment CR for NR positioning in 38.214 ZTE

R1-2301971 Summary #1 of PRS configuration and editorial corrections Moderator (ZTE)

Conclusion

· The change on positioning part in R1-2300801 is not pursued. It is up to editor of TS38.214 to consider the remaining editorial change.

R1-2301210 Correction on TEG reporting Nokia, Nokia Shanghai Bell

R1-2301905 Summary #1 of Correction on TEG reporting Moderator (Nokia)

Conclusion

· The text proposal in R1-2301210 is endorsed as an editorial correction and is provided to the TS38.214 editor for the alignment CR.

R1-2301753 Correction to the DL-AoD priority subset Huawei, HiSilicon

R1-2301891 Summary #1 of correction on DL-AoD priority subset Moderator (Huawei)

Conclusion

· The text proposal below is endorsed as an editorial correction and is provided to the TS38.214 editor for the alignment CR.

------ Start of TP ------

5.1.6.5 PRS reception procedure

========================= Unchanged parts =========================

A DL PRS resource is defined by:

- nr-DL-PRS-ResourceID determines the DL PRS resource configuration identity. All DL PRS resource IDs are locally defined within a DL PRS resource set.

- dl-PRS-SequenceID is used to initialize c_init value used in pseudo random generator as described in Clause 7.4.1.7.2 of [4, TS 38.211] for generation of DL PRS sequence for a given DL PRS resource.

- dl-PRS-CombSizeN-AndReOffset defines the starting RE offset of the first symbol within a DL PRS resource in frequency. The relative RE offsets of the remaining symbols within a DL PRS resource are defined based on the initial offset and the rule described in Clause 7.4.1.7.3 of [4, TS 38.211].

- dl-PRS-ResourceSlotOffset determines the starting slot of the DL PRS resource with respect to corresponding DL PRS resource set slot offset.

- dl-PRS-ResourceSymbolOffset determines the starting symbol of a slot configured with the DL PRS resource.

- dl-PRS-QCL-Info defines any quasi co-location information of the DL PRS resource with other reference signals. The DL PRS may be configured with QCL 'typeD' with a DL PRS associated with the same dl-PRS-ID, or with rs-Type set to 'typeC', 'typeD', or 'typeC-plus-typeD' with a SS/PBCH Block from a serving or non-serving cell.

- dl-PRS-ResourcePrioritySubset defines a subset of DL-PRS resources for the DL PRS resource for the purpose of prioritization of ~~DL-AoD~~ measurement reporting as described in TS37.355.

========================= Unchanged parts =========================

------ End of TP ------

R1-2301754 Editorial corrections to NR positioning enhancements Huawei, HiSilicon

R1-2301892 Summary #1 of PRS editorial corrections Moderator (Huawei)

Conclusion

· The changes in the draft CR R1-2301754 are endorsed for the editorial corrections of TS38.214 and provided to the spec editor for the alignment CR.