|
| 36.305 | 0119 | - | B | 17.3.0 | Rel-18 | Bluetooth AoA/AoD support [BT-AoA-AoD] |
R2-2312944
| agreed | RAN2#124 | Ericsson |
RP-233883
| approved | RAN#102 | RAN2 | 18.0.0 | TEI18 |
|
|
| 36.305 | 0118 | 2 | C | 17.3.0 | Rel-18 | SSR Satellite PCV Residuals [Rel18PCV] |
R2-2313063
| agreed | RAN2#124 | Swift Navigatio... |
RP-233883
| approved | RAN#102 | RAN2 | 18.0.0 | TEI18 |
|
|
| 36.305 | 0118 | 1 | C | 17.3.0 | Rel-18 | SSR Satellite PCV Residuals [Rel18PCV] |
R2-2309320
| revised | RAN2#123 | Swift Navigatio... |
| | | | | TEI18 |
|
|
| 36.305 | 0118 | - | C | 17.3.0 | Rel-18 | SSR Satellite PCV Residuals [Rel18PCV] |
R2-2309112
| revised | RAN2#123 | Swift, Ericsson |
| | | | | TEI18 |
|
|
| 36.305 | 0117 | 1 | A | 17.2.0 | Rel-17 | Zero Yaw clarification for SSR positioning |
R2-2305260
| agreed | RAN2#122 | Swift Navigatio... |
RP-231411
| approved | RAN#100 | RAN2 | 17.3.0 | NR_pos-Core |
|
|
| 36.305 | 0117 | - | A | 17.2.0 | Rel-17 | Zero Yaw clarification for SSR positioning |
R2-2304315
| revised | RAN2#121-bis-e | Swift Navigatio... |
| | | | | NR_pos-Core |
|
|
| 36.305 | 0116 | 1 | F | 16.4.0 | Rel-16 | Zero Yaw clarification for SSR positioning |
R2-2305259
| agreed | RAN2#122 | Swift Navigatio... |
RP-231411
| approved | RAN#100 | RAN2 | 16.5.0 | NR_pos-Core |
|
|
| 36.305 | 0116 | - | F | 16.4.0 | Rel-16 | Zero Yaw clarification for SSR positioning |
R2-2304314
| revised | RAN2#121-bis-e | Swift Navigatio... |
| | | | | NR_pos-Core |
|
|
| 36.305 | 0115 | 1 | A | 17.2.0 | Rel-17 | APC clarification for SSR positioning |
R2-2305255
| agreed | RAN2#122 | Swift Navigatio... |
RP-231409
| approved | RAN#100 | RAN2 | 17.3.0 | LCS_LTE_acc_enh-Core |
|
|
| 36.305 | 0115 | - | A | 17.2.0 | Rel-17 | APC clarification for SSR positioning |
R2-2304310
| revised | RAN2#121-bis-e | Swift Navigatio... |
| | | | | NR_pos-Core |
|
|
| 36.305 | 0114 | 1 | A | 16.4.0 | Rel-16 | APC clarification for SSR positioning |
R2-2305254
| agreed | RAN2#122 | Swift Navigatio... |
RP-231409
| approved | RAN#100 | RAN2 | 16.5.0 | LCS_LTE_acc_enh-Core |
|
|
| 36.305 | 0114 | - | A | 16.4.0 | Rel-16 | APC clarification for SSR positioning |
R2-2304309
| revised | RAN2#121-bis-e | Swift Navigatio... |
| | | | | NR_pos-Core |
|
|
| 36.305 | 0113 | 1 | F | 15.5.0 | Rel-15 | APC clarification for SSR positioning |
R2-2305253
| agreed | RAN2#122 | Swift Navigatio... |
RP-231409
| approved | RAN#100 | RAN2 | 15.6.0 | LCS_LTE_acc_enh-Core |
|
|
| 36.305 | 0113 | - | F | 15.5.0 | Rel-15 | APC clarification for SSR positioning |
R2-2304308
| revised | RAN2#121-bis-e | Swift Navigatio... |
| | | | | NR_pos-Core |
|
|
| 36.305 | 0112 | - | A | 17.2.0 | Rel-17 | Update Stage 2 SSR Phase Bias description to include yaw |
R2-2212518
| | RAN2#120 | Swift Navigatio... |
| | | | | NR_pos-Core |
|
|
| 36.305 | 0111 | - | F | 16.4.0 | Rel-16 | Update Stage 2 SSR Phase Bias description to include yaw |
R2-2212516
| | RAN2#120 | Swift Navigatio... |
| | | | | NR_pos-Core |
|
|
| 36.305 | 0110 | - | F | 17.1.0 | Rel-17 | Correction on the mean orbit error projection in TS 36.305 |
R2-2208419
| agreed | RAN2#119-e | Swift Navigatio... |
RP-222524
| approved | RAN#97-e | RAN2 | 17.2.0 | NR_pos_enh-Core |
|
|
| 36.305 | 0109 | - | F | 17.0.0 | Rel-17 | 36.305 CR for Positioning WI |
R2-2206245
| agreed | RAN2#118-e | Intel Corporation |
RP-221725
| approved | RAN#96 | RAN2 | 17.1.0 | NR_pos_enh-Core |
|
|
| 36.305 | 0108 | - | F | 17.0.0 | Rel-17 | Correction on the reference file of BDS Signal B3I |
R2-2204689
| | RAN2#118-e | CATT, CAICT |
| | | | | NR_pos_enh-Core |
|
|
| 36.305 | 0107 | 1 | B | 16.4.0 | Rel-17 | Introduction of B2a and B3I signal in BDS system and GNSS Positioning Integrity |
R2-2204097
| agreed | RAN2#117-e | CATT, CAICT, CM... |
RP-220479
| approved | RAN#95-e | RAN2 | 17.0.0 | NR_pos_enh-Core |
|
|
| 36.305 | 0107 | - | B | 16.4.0 | Rel-17 | Introduction of B2a and B3I signal in BDS system and GNSS Positioning Integrity |
R2-2202405
| revised | RAN2#117-e | CATT, CAICT, CM... |
| | | | | NR_pos_enh-Core |
|
|
| 36.305 | 0106 | 1 | B | 16.4.0 | Rel-17 | Introduction of B2a and B3I signal in BDS system in A-GNSS |
R2-2203610
| endorsed | RAN2#117-e | CATT, CAICT, CM... |
| | | | | NR_pos_enh-Core |
|
|
| 36.305 | 0106 | - | B | 16.4.0 | Rel-17 | Introduction of B2a and B3I signal in BDS system in A-GNSS |
R2-2202403
| revised | RAN2#117-e | CATT, CAICT, CM... |
| | | | | NR_pos_enh-Core |
|
|
| 36.305 | 0105 | - | F | 16.3.0 | Rel-16 | Correction on user-plane positioning support by SUPL |
R2-2107959
| agreed | RAN2#115-e | Samsung, Qualco... |
RP-212441
| approved | RAN#93-e | RAN2 | 16.4.0 | LCS_LTE |
|
|
| 36.305 | 0104 | 2 | F | 16.2.0 | Rel-16 | Correction to LTE stage2 spec for MO-LR |
R2-2105047
| agreed | RAN2#114-e | Huawei, HiSilicon |
RP-211476
| approved | RAN#92-e | RAN2 | 16.3.0 | TEI16, LCS_LTE |
|
|
| 36.305 | 0104 | 1 | F | 16.2.0 | Rel-16 | Correction to LTE stage2 spec for MO-LR |
R2-2104526
| revised | RAN2#113-bis-e | Huawei, HiSilicon |
| | | | | LCS_LTE, TEI16 |
|
|
| 36.305 | 0104 | - | F | 16.2.0 | Rel-16 | Correction to LTE stage2 spec for MO-LR |
R2-2104264
| revised | RAN2#113-bis-e | Huawei, HiSilicon |
| | | | | LCS_LTE, TEI16 |
|
|
| 36.305 | 0103 | - | F | 16.2.0 | Rel-16 | Correction to LTE stage2 spec for MO-LR |
R2-2104047
| withdrawn | RAN2#113-bis-e | Huawei, HiSilicon |
| | | | | LCS_LTE, TEI16 |
|
|
| 36.305 | 0102 | - | A | 16.2.0 | Rel-16 | Correction on SUPL support of positioning methods |
R2-2103218
| not pursued | RAN2#113-bis-e | Samsung |
| | | | | UTRA_LTE_iPos_e... |
|
|
| 36.305 | 0101 | - | A | 15.5.0 | Rel-15 | Correction on SUPL support of positioning methods |
R2-2103217
| not pursued | RAN2#113-bis-e | Samsung |
| | | | | UTRA_LTE_iPos_e... |
|
|
| 36.305 | 0100 | - | F | 14.3.0 | Rel-14 | Correction on SUPL support of positioning methods |
R2-2103216
| not pursued | RAN2#113-bis-e | Samsung |
| | | | | UTRA_LTE_iPos_e... |
|
|
| 36.305 | 0099 | - | A | 16.2.0 | Rel-16 | corrections on the indication for the not provided assistance data and location information in TS36.305 |
R2-2100396
| not pursued | RAN2#113-e | CATT |
| | | | | UTRA_LTE_iPos_e... |
|
|
| 36.305 | 0098 | - | A | 15.5.0 | Rel-15 | corrections on the indication for the not provided assistance data and location information in TS36.305 |
R2-2100395
| not pursued | RAN2#113-e | CATT |
| | | | | UTRA_LTE_iPos_e... |
|
|
| 36.305 | 0097 | - | F | 14.3.0 | Rel-14 | corrections on the indication for the not provided assistance data and location information in TS36.305 |
R2-2100394
| not pursued | RAN2#113-e | CATT |
| | | | | UTRA_LTE_iPos_e... |
|
|
| 36.305 | 0096 | - | A | 16.2.0 | Rel-16 | corrections on the descriptions of RequestLocationInformation message in TS36.305 |
R2-2100393
| not pursued | RAN2#113-e | CATT |
| | | | | UTRA_LTE_iPos_e... |
|
|
| 36.305 | 0095 | - | A | 15.5.0 | Rel-15 | corrections on the descriptions of RequestLocationInformation message in TS36.305 |
R2-2100392
| not pursued | RAN2#113-e | CATT |
| | | | | UTRA_LTE_iPos_e... |
|
|
| 36.305 | 0094 | - | F | 14.3.0 | Rel-14 | corrections on the descriptions of RequestLocationInformation message in TS36.305 |
R2-2100391
| not pursued | RAN2#113-e | CATT |
| | | | | UTRA_LTE_iPos_e... |
|
|
| 36.305 | 0093 | - | F | 16.2.0 | Rel-16 | Minor corrections on TS 36.305 |
R2-2008803
| | RAN2#112-e | CATT |
| | | | | NR_newRAT-Core |
|
|
| 36.305 | 0092 | - | F | 16.1.0 | Rel-16 | UE E-CID measurement reporting |
R2-2008259
| agreed | RAN2#111-e | Nokia, Nokia Sh... |
RP-201934
| approved | RAN#89-e | RAN2 | 16.2.0 | LCS_LTE, TEI16 |
|
|
| 36.305 | 0091 | 1 | F | 15.5.0 | Rel-15 | UE E-CID measurement reporting |
R2-2008257
| revised | RAN2#111-e | Nokia, Nokia Sh... |
| | | | | LCS_LTE |
|
|
| 36.305 | 0091 | - | F | 15.5.0 | Rel-15 | UE E-CID measurement reporting |
R2-2008051
| revised | RAN2#111-e | Nokia, Nokia Sh... |
| | | | | LCS_LTE |
|
|
| 36.305 | 0090 | - | A | 16.1.0 | Rel-16 | Correction on 36.305 in Table 4.3-1Supported versions of UE positioning methods |
R2-2006668
| | RAN2#111-e | CATT |
| | | | | NR_newRAT-Core |
|
|
| 36.305 | 0089 | - | F | 15.5.0 | Rel-15 | Correction on 36.305 in Table 4.3-1Supported versions of UE positioning methods |
R2-2006667
| not pursued | RAN2#111-e | CATT |
| | | | | NR_newRAT-Core |
|
|
| 36.305 | 0088 | 1 | F | 16.0.0 | Rel-16 | Update B1I signal ICD file to v3.0 in BDS system in A-GNSS |
R2-2005895
| agreed | RAN2#110-e | CATT, CAICT, Hu... |
RP-201190
| approved | RAN#88-e | RAN2 | 16.1.0 | TEI16 |
|
|
| 36.305 | 0088 | - | F | 16.0.0 | Rel-16 | Update B1I signal ICD file to v3.0 in BDS system in A-GNSS |
R2-2004792
| revised | RAN2#110-e | CATT, CAICT, Hu... |
| | | | | TEI16 |
|
|
| 36.305 | 0087 | 1 | A | 16.0.0 | Rel-16 | CR to clarify the meaning of GNSS term in 36.305 Rel-16 |
R2-2004735
| agreed | RAN2#110-e | ESA, Nokia, Nok... |
RP-201175
| approved | RAN#88-e | RAN2 | 16.1.0 | NR_pos-Core |
|
|
| 36.305 | 0087 | - | A | 16.0.0 | Rel-16 | CR to clarify the meaning of GNSS term in 36.305 Rel-16 |
R2-2003992
| revised | RAN2#109-bis-e | ESA, Nokia, Nok... |
| | | | | NR_pos-Core |
|
|
| 36.305 | 0086 | 1 | F | 15.4.0 | Rel-15 | CR to clarify the meaning of GNSS term in 36.305 Rel-15 |
R2-2004734
| agreed | RAN2#110-e | ESA, Nokia, Nok... |
RP-201175
| approved | RAN#88-e | RAN2 | 15.5.0 | NR_pos-Core |
|
|
| 36.305 | 0086 | - | F | 15.4.0 | Rel-15 | CR to clarify the meaning of GNSS term in 36.305 Rel-15 |
R2-2003991
| revised | RAN2#109-bis-e | ESA, Nokia, Nok... |
| | | | | NR_pos-Core |
|
|
| 36.305 | 0085 | 1 | B | 15.4.0 | Rel-16 | CR for the introduction of SSR positioning support into LTE |
R2-2002111
| agreed | RAN2#109-e | ESA, Intel Corp... |
RP-200345
| approved | RAN#87-e | RAN2 | 16.0.0 | NR_pos-Core |
|
|
| 36.305 | 0085 | - | B | 15.4.0 | Rel-16 | Stage 2 CR for the introduction of SSR positioning support into LTE |
R2-2001080
| revised | RAN2#109-e | ESA, Intel Corp... |
| | | | | NR_pos-Core |
|
|
| 36.305 | 0084 | 5 | B | 15.4.0 | Rel-16 | CR of TS 36.305 for introducing NavIC in LTE |
R2-2002240
| agreed | RAN2#109-e | Reliance Jio, C... |
RP-200365
| approved | RAN#87-e | RAN2 | 16.0.0 | LCS_NAVIC |
|
|
| 36.305 | 0084 | 4 | B | 15.4.0 | Rel-16 | CR of TS 36.305 for introducing NavIC in LTE |
R2-2001954
| revised | RAN2#109-e | Reliance Jio, M... |
| | | | | LCS_NAVIC |
|
|
| 36.305 | 0084 | 3 | B | 15.4.0 | Rel-16 | CR of TS 36.305 for introducing NavIC in LTE |
R2-2000158
| revised | RAN2#109-e | Reliance Jio, M... |
| | | | | LCS_NAVIC |
|
|
| 36.305 | 0084 | 2 | B | 15.4.0 | Rel-16 | CR of TS 36.305 for introducing NavIC in LTE |
R2-1916408
| revised | RAN2#108 | Reliance Jio, M... |
| | | | | LCS_NAVIC |
|
|
| 36.305 | 0084 | 1 | B | 15.4.0 | Rel-16 | CR of TS 36.305 for introducing NavIC in LTE |
R2-1914766
| revised | RAN2#108 | Reliance Jio, M... |
| | | | | LCS_NAVIC |
|
|
| 36.305 | 0084 | - | B | 15.4.0 | Rel-16 | CR of TS 36.305 for introducing NavIC in LTE |
R2-1913937
| revised | RAN2#107-Bis | Reliance Jio, M... |
| | | | | LCS_NAVIC |
|
|
| 36.305 | 0083 | 1 | B | 15.4.0 | Rel-16 | Introduction of B1C signal in BDS system in A-GNSS |
R2-2000238
| agreed | RAN2#109-e | CATT, CAICT, CM... |
RP-200357
| approved | RAN#87-e | RAN2 | 16.0.0 | TEI16 |
|
|
| 36.305 | 0083 | - | B | 15.4.0 | Rel-16 | Introduction of B1C signal in BDS system in A-GNSS |
R2-1912203
| revised | RAN2#107-Bis | CATT, CAICT, CM... |
| | | | | TEI16 |
|
|
| 36.305 | 0082 | 1 | F | 15.3.0 | Rel-15 | Minor updates for motion sensors |
R2-1908250
| agreed | RAN2#106 | Sony, Ericsson |
RP-191384
| approved | RAN#84 | RAN2 | 15.4.0 | LCS_LTE_acc_enh-Core |
|
|
| 36.305 | 0082 | - | F | 15.3.0 | Rel-15 | Minor mirror correction to motions sensor |
R2-1907052
| revised | RAN2#106 | Sony, Ericsson |
| | | | | LCS_LTE_acc_enh-Core |
|
|
| 36.305 | 0081 | - | B | 15.3.0 | Rel-15 | Enable fast RRC connection release in NB-IoT positioning procedure |
R2-1904335
| not treated | RAN2#105-Bis | CMCC |
| | | | | NB_IOTenh2-Core |
|
|
| 36.305 | 0080 | 3 | F | 15.2.0 | Rel-15 | Support of additional sensor methods (IMU) |
R2-1902723
| agreed | RAN2#105 | Sony, Ericsson |
RP-190550
| approved | RAN#83 | RAN2 | 15.3.0 | LCS_LTE_acc_enh-Core |
|
|
| 36.305 | 0080 | 2 | F | 15.2.0 | Rel-15 | Support of additional sensor methods (IMU) |
R2-1902475
| revised | RAN2#105 | Sony, Ericsson |
| | | | | LCS_LTE_acc_enh-Core |
|
|
| 36.305 | 0080 | 1 | F | 15.2.0 | Rel-15 | Support of additional sensor methods (IMU) |
R2-1902470
| revised | RAN2#105 | Sony, Ericsson |
| | | | | LCS_LTE_acc_enh-Core |
|
|
| 36.305 | 0080 | - | F | 15.2.0 | Rel-15 | Support of additional sensor methods (IMU) |
R2-1901433
| revised | RAN2#105 | Sony, Ericsson |
| | | | | LCS_LTE_acc_enh-Core |
|
|
| 36.305 | 0079 | - | F | 15.1.0 | Rel-15 | Capture use of motion information from motion sensors |
R2-1818168
| withdrawn | RAN2#104 | Nokia, Nokia Sh... |
| | | | | LCS_LTE_acc_enh-Core |
|
|
| 36.305 | 0078 | - | B | 15.1.0 | Rel-15 | Introduction of motion sensors in 36.305 |
R2-1817635
| noted | RAN2#104 | Ericsson, Sony |
| | | | | LCS_LTE_acc_enh-Core |
|
|
| 36.305 | 0077 | 2 | F | 15.1.0 | Rel-15 | Capture use of motion information from motion sensors |
R2-1818499
| agreed | RAN2#104 | Nokia, Nokia Sh... |
RP-182674
| approved | RAN#82 | RAN2 | 15.2.0 | LCS_LTE_acc_enh-Core |
|
|
| 36.305 | 0077 | 1 | F | 15.1.0 | Rel-15 | Capture use of motion information from motion sensors |
R2-1815659
| revised | RAN2#103-Bis | Nokia, Nokia Sh... |
| | | | | LCS_LTE_acc_enh-Core |
|
|
| 36.305 | 0077 | - | F | 15.1.0 | Rel-15 | Capture use of motion information from motion sensors |
R2-1815346
| revised | RAN2#103-Bis | Nokia, Nokia Sh... |
| | | | | LCS_LTE_acc_enh-Core |
|
|
| 36.305 | 0076 | 1 | F | 15.0.0 | Rel-15 | Broadcast of assistance data |
R2-1813167
| agreed | RAN2#103 | Qualcomm Incorp... |
RP-181952
| approved | RAN#81 | RAN2 | 15.1.0 | LCS_LTE_acc_enh-Core |
|
|
| 36.305 | 0076 | - | F | 15.0.0 | Rel-15 | Broadcast of assistance data |
R2-1812354
| revised | RAN2#103 | Qualcomm Incorp... |
| | | | | LCS_LTE_acc_enh-Core |
|
|
| 36.305 | 0075 | - | B | 14.3.0 | Rel-15 | Addition of broadcast of positioning assistance data |
R2-1808639
| | RAN2#102 | Ericsson |
| | | | | LCS_LTE_acc_enh-Core |
|
|
| 36.305 | 0074 | 1 | B | 14.3.0 | Rel-15 | RTK Stage 2 CR for 36.305 |
R2-1808892
| agreed | RAN2#102 | ESA |
RP-181219
| approved | RAN#80 | RAN2 | 15.0.0 | LCS_LTE_acc_enh-Core |
|
|
| 36.305 | 0074 | - | B | 14.3.0 | Rel-15 | RTK Stage 2 CR for 36.305 |
R2-1808058
| revised | RAN2#102 | ESA |
| | | | | LCS_LTE_acc_enh-Core |
|
|
| 36.305 | 0073 | 1 | B | 14.3.0 | Rel-15 | IMU stage 2 CR for 36.305 |
R2-1808887
| not pursued | RAN2#102 | Sony, Ericsson |
| | | | | LCS_LTE_acc_enh-Core |
|
|
| 36.305 | 0073 | - | B | 14.3.0 | Rel-15 | IMU stage 2 CR for 36.305 |
R2-1808038
| revised | RAN2#102 | Sony, Ericsson |
| | | | | LCS_LTE_acc_enh-Core |
|
|
| 36.305 | 0072 | - | B | 14.3.0 | Rel-15 | Support of additional sensor methods (IMU) |
R2-1805334
| | RAN2#101-Bis | Sony, Ericsson |
| | | | | LCS_LTE_acc_enh-Core |
|
|
| 36.305 | 0071 | 1 | F | 14.3.0 | Rel-14 | Clarification on LPP Message size due to limitations at the lower layers |
R2-1711849
| postponed | RAN2#99-Bis | Intel Corporation |
| | | | | LCS_LTE |
|
|
| 36.305 | 0071 | - | F | 14.3.0 | Rel-14 | Clarification on LPP Message size due to limitations at the lower layers |
R2-1711475
| revised | RAN2#99-Bis | Intel Corporation |
| | | | | LCS_LTE |
|
|
| 36.305 | 0070 | 2 | F | 14.2.0 | Rel-14 | Clarification to positioning measurement in idle state |
R2-1709904
| agreed | RAN2#99 | Ericsson |
RP-171915
| approved | RAN#77 | RAN2 | 14.3.0 | NB_IOTenh-Core |
|
|
| 36.305 | 0070 | 1 | F | 14.2.0 | Rel-14 | Clarification to positioning measurement in idle state |
R2-1709728
| revised | RAN2#99 | Ericsson |
| | | | | NB_IOTenh-Core |
|
|
| 36.305 | 0070 | - | F | 14.2.0 | Rel-14 | Clarification to positioning measurement in idle state |
R2-1708282
| revised | RAN2#99 | Ericsson |
| | | | | NB_IOTenh-Core |
|
|
| 36.305 | 0069 | 1 | F | 14.1.0 | Rel-14 | Clarification to positioning measurement in idle state |
R2-1705913
| agreed | RAN2#98 | Ericsson |
RP-171224
| approved | RAN#76 | RAN2 | 14.2.0 | NB_IOTenh-Core |
|
|
| 36.305 | 0069 | - | F | 14.1.0 | Rel-14 | Clarification to positioning measurement in idle state |
R2-1705016
| revised | RAN2#98 | Ericsson |
| | | | | NB_IOTenh-Core |
|
|
| 36.305 | 0068 | - | F | 14.1.0 | Rel-14 | Corrections to UE positioning measurements in Idle State |
R2-1703045
| noted | RAN2#97-Bis | Ericsson |
| | | | | NB_IOTenh-Core |
|
|
| 36.305 | 0067 | - | F | 14.0.0 | Rel-14 | Further Indoor positioning enhancements corrections |
R2-1701757
| agreed | RAN2#97 | NextNav, AT&T, ... |
RP-170647
| approved | RAN#75 | RAN2 | 14.1.0 | UTRA_LTE_iPos_e... |
|
|
| 36.305 | 0066 | 2 | B | 14.0.0 | Rel-14 | Support of UE positioning measurements in Idle State |
R2-1702401
| agreed | RAN2#97 | Qualcomm Incorp... |
RP-170637
| approved | RAN#75 | RAN2 | 14.1.0 | NB_IOTenh-Core |
|
|
| 36.305 | 0066 | 1 | B | 14.0.0 | Rel-14 | Support of UE positioning measurements in Idle State |
R2-1702278
| revised | RAN2#97 | Qualcomm Incorp... |
| | | | | NB_IOTenh-Core |
|
|
| 36.305 | 0066 | - | B | 14.0.0 | Rel-14 | Support of UE positioning measurements in Idle State |
R2-1701113
| revised | RAN2#97 | Qualcomm Incorp... |
| | | | | NB_IOTenh-Core |
|
|
| 36.305 | 0065 | - | B | 13.0.0 | Rel-14 | Reusing Available WLAN Measurements as E-CID Assistance Data |
R2-169165
| agreed | RAN2#96 | RAN3 (contact: ... |
RP-162326
| approved | RAN#74 | RAN2 | 14.0.0 | UTRA_LTE_iPos_e... |
|
|
| 36.305 | 0064 | - | B | 13.0.0 | Rel-13 | Multipath RSTD Stage-2 CR |
R2-168382
| not pursued | RAN2#96 | Ericsson |
| | | | | UTRA_LTE_iPos_e... |
|
|
| 36.305 | 0063 | 1 | B | 13.0.0 | Rel-14 | CR for 36.305 Further Indoor positioning enhancements |
R2-169081
| agreed | RAN2#96 | NextNav |
RP-162326
| approved | RAN#74 | RAN2 | 14.0.0 | UTRA_LTE_iPos_e... |
|
|
| 36.305 | 0063 | - | B | 13.0.0 | Rel-14 | Running CR for 36.305 Further Indoor positioning enhancements |
R2-167633
| revised | RAN2#96 | NextNav |
| | | | | UTRA_LTE_iPos_e... |
|
|
| 36.305 | 0062 | - | B | 13.0.0 | Rel-14 | Introduction of WLAN AP assistance data and UE-based WLAN positioning method (Stage-2) |
R2-165427
| | RAN2#95 | Intel Corporation |
| | | | | UTRA_LTE_iPos_e... |
|
|
| 36.305 | 0061 | 2 | B | 12.2.0 | Rel-13 | RAT-Independent positioning enhancements |
R2-157059
| agreed | RAN2#92 | NextNav, AT&T, ... |
RP-152068
| approved | RAN#70 | RAN2 | 13.0.0 | UTRA_LTE_iPos_e... |
|
|
| 36.305 | 0061 | 1 | B | 12.2.0 | Rel-13 | RAT-Independent positioning enhancements |
R2-157015
| revised | RAN2#92 | NextNav, AT&T, ... |
| | | | | UTRA_LTE_iPos_e... |
|
|
| 36.305 | 0061 | - | B | 12.2.0 | Rel-13 | RAT-Independent positioning enhancements |
R2-156629
| revised | RAN2#92 | NextNav, AT&T, ... |
| | | | | |
|
|
| 36.305 | 0060 | - | F | 12.1.0 | Rel-12 | BDS update to version 2.0 |
R2-145275
| agreed | RAN2#88 | Nokia Corporati... |
RP-142120
| approved | RAN#66 | R2 | 12.2.0 | LCS_BDS-LTE-Core |
|
|
| 36.305 | 0059 | - | B | 12.0.0 | Rel-12 | Addition of Inter-RAT Measurements to Stage 2 Location Specification |
R2-142948
| agreed | RAN2#86 | RAN3 (contact: ... |
RP-140890
| approved | RAN#64 | R2 | 12.1.0 | LCS_LTE_RFPMT-Core |
|
|
| 36.305 | 0058 | - | B | 11.3.0 | Rel-12 | Introduction of BDS in LTE |
R2-133853
| agreed | RAN2#84 | CATR, ZTE, CATT... |
RP-132000
| approved | RAN#62 | R2 | 12.0.0 | LCS_BDS-LTE-Core |
|
|
| 36.305 | 0056 | - | B | 11.2.0 | Rel-11 | Network Based Positioning Support SRS Update for intra-MME handover |
R2-130694
| agreed | RAN2#81 | RAN3 |
RP-130244
| approved | RAN#59 | R2 | 11.3.0 | LCS_LTE-NBPS-Core |
|
|
| 36.305 | 0055 | - | F | 11.1.0 | Rel-11 | SLmAP Stage 2 Clarification |
R2-125989
| agreed | RAN2#80 | RAN3 |
RP-121949
| approved | RAN#58 | R2 | 11.2.0 | LCS_LTE-NBPS-Core |
|
|
| 36.305 | 0054 | - | B | 11.1.0 | Rel-11 | Network Based Positioning Support SRS Update for intra-MME handover |
R2-125987
| agreed | RAN2#80 | RAN3 (TruePosition) |
RP-121734
| postponed | RAN#58 | R3 | | LCS_LTE-NBPS-Core |
|
|
| 36.305 | 0053 | - | B | 11.1.0 | Rel-11 | Network Based Positioning Support SRS Update |
R2-125986
| agreed | RAN2#80 | RAN3 |
RP-121949
| approved | RAN#58 | R2 | 11.2.0 | LCS_LTE-NBPS-Core |
|
|
| 36.305 | 0052 | - | A | 11.1.0 | Rel-11 | Correlation of LPPa class 2 procedures involved in an LPPa transaction |
R2-125982
| agreed | RAN2#80 | RAN3 |
RP-121931
| approved | RAN#58 | R2 | 11.2.0 | LCS_LTE, TEI10 |
|
|
| 36.305 | 0051 | - | F | 10.4.0 | Rel-10 | Correlation of LPPa class 2 procedures involved in an LPPa transaction |
R2-125981
| agreed | RAN2#80 | RAN3 |
RP-121931
| approved | RAN#58 | R2 | 10.5.0 | LCS_LTE, TEI10 |
|
|
| 36.305 | 0050 | - | F | 11.1.0 | Rel-11 | Correction of E-CID Measurement Initiation |
R2-125973
| agreed | RAN2#80 | RAN3 |
RP-121931
| approved | RAN#58 | R2 | 11.2.0 | LCS_LTE, TEI11 |
|
|
| 36.305 | 0049 | - | A | 11.1.0 | Rel-11 | Addition of Network Triggered Service Request for LPP and LPPa Positioning |
R2-126066
| agreed | RAN2#80 | Qualcomm Incorp... |
RP-121931
| approved | RAN#58 | R2 | 11.2.0 | LCS_LTE |
|
|
| 36.305 | 0048 | - | A | 10.4.0 | Rel-10 | Addition of Network Triggered Service Request for LPP and LPPa Positioning |
R2-126065
| agreed | RAN2#80 | Qualcomm Incorp... |
RP-121931
| approved | RAN#58 | R2 | 10.5.0 | LCS_LTE |
|
|
| 36.305 | 0047 | - | F | 9.9.0 | Rel-9 | Addition of Network Triggered Service Request for LPP and LPPa Positioning |
R2-126064
| agreed | RAN2#80 | Qualcomm Incorp... |
RP-121931
| approved | RAN#58 | R2 | 9.10.0 | LCS_LTE |
|
|
| 36.305 | 0046 | - | A | 11.1.0 | Rel-11 | Cleanup of TS36.305 |
R2-125271
| agreed | RAN2#80 | Huawei, HiSilicon |
RP-121931
| approved | RAN#58 | R2 | 11.2.0 | LCS_LTE |
|
|
| 36.305 | 0045 | - | A | 10.4.0 | Rel-10 | Cleanup of TS36.305 |
R2-125270
| agreed | RAN2#80 | Huawei, HiSilicon |
RP-121931
| approved | RAN#58 | R2 | 10.5.0 | LCS_LTE |
|
|
| 36.305 | 0044 | - | F | 9.9.0 | Rel-9 | Cleanup of TS36.305 |
R2-125269
| agreed | RAN2#80 | Huawei, HiSilicon |
RP-121931
| approved | RAN#58 | R2 | 9.10.0 | LCS_LTE |
|
|
| 36.305 | 0043 | 1 | B | 11.0.0 | Rel-11 | Network Based Positioning Support |
R2-124291
| agreed | RAN2#79 | RAN3 (TruePosition) |
RP-121374
| approved | RAN#57 | R2 | 11.1.0 | LCS_LTE-NBPS-Core |
|
|
| 36.305 | 0043 | - | C | 11.0.0 | Rel-11 | Network Based Positioning Support |
R2-124290
| revised | RAN2#79 | RAN3 |
| | | - | | LCS_LTE-NBPS-Core |
|
|
| 36.305 | 0042 | - | F | 11.0.0 | Rel-11 | Correction to SRS configuration for UTDOA |
R2-124319
| agreed | RAN2#79 | Ericsson |
RP-121374
| approved | RAN#57 | R2 | 11.1.0 | LCS_LTE-NBPS-Core |
|
|
| 36.305 | 0041 | - | A | 11.0.0 | Rel-11 | Clarification on the case that the eNB functions as an LCS client |
R2-124211
| agreed | RAN2#79 | Samsung |
RP-121394
| approved | RAN#57 | R2 | 11.1.0 | LCS_LTE |
|
|
| 36.305 | 0041 | - | A | 11.0.0 | Rel-11 | Clarification on the case that the eNB functions as an LCS client |
R2-124211
| agreed | RAN2#79 | Samsung |
RP-121358
| reissued | RAN#57 | R2 | | LCS_LTE |
|
|
| 36.305 | 0040 | - | A | 11.0.0 | Rel-11 | Addition of Network Triggered Service Request for LPP and LPPa Positioning |
R2-124214
| withdrawn | RAN2#79 | Qualcomm Incorp... |
| | | - | | LCS_LTE |
|
|
| 36.305 | 0039 | - | A | 10.3.0 | Rel-10 | Addition of Network Triggered Service Request for LPP and LPPa Positioning |
R2-124213
| withdrawn | RAN2#79 | Qualcomm Incorp... |
| | | - | | LCS_LTE |
|
|
| 36.305 | 0038 | - | F | 9.8.0 | Rel-9 | Addition of Network Triggered Service Request for LPP and LPPa Positioning |
R2-124212
| withdrawn | RAN2#79 | Qualcomm Incorp... |
| | | - | | LCS_LTE |
|
|
| 36.305 | 0037 | - | A | 10.3.0 | Rel-10 | Clarification on the case that the eNB functions as an LCS client |
R2-124210
| agreed | RAN2#79 | Samsung |
RP-121394
| approved | RAN#57 | R2 | 10.4.0 | LCS_LTE |
|
|
| 36.305 | 0037 | - | A | 10.3.0 | Rel-10 | Clarification on the case that the eNB functions as an LCS client |
R2-124210
| agreed | RAN2#79 | Samsung |
RP-121358
| reissued | RAN#57 | R2 | | LCS_LTE |
|
|
| 36.305 | 0036 | - | F | 9.8.0 | Rel-9 | Clarification on the case that the eNB functions as an LCS client |
R2-124209
| agreed | RAN2#79 | Samsung |
RP-121394
| approved | RAN#57 | R2 | 9.9.0 | LCS_LTE |
|
|
| 36.305 | 0036 | - | F | 9.8.0 | Rel-9 | Clarification on the case that the eNB functions as an LCS client |
R2-124209
| agreed | RAN2#79 | Samsung |
RP-121358
| reissued | RAN#57 | R2 | | LCS_LTE |
|
|
| 36.305 | 0035 | 1 | C | 11.0.0 | Rel-11 | Number of SRS transmissions |
R2-124336
| agreed | RAN2#79 | TruePosition |
RP-121374
| approved | RAN#57 | R2 | 11.1.0 | LCS_LTE-NBPS-Core |
|
|
| 36.305 | 0035 | - | C | 11.0.0 | Rel-11 | Draft CR for 36.305 for NBPS Support in LTE |
R2-124320
| revised | RAN2#79 | TruePosition |
| | | - | | LCS_LTE-NBPS-Core |
|
|
| 36.305 | 0034 | 1 | B | 10.3.0 | Rel-11 | CR for 36.305 NBPS Support in LTE |
R2-123137
| agreed | RAN2#78 | TruePosition |
RP-120820
| approved | RAN#56 | R2 | 11.0.0 | LCS_LTE-NBPS-Core |
|
|
| 36.305 | 0034 | - | B | 10.3.0 | Rel-11 | CR for 36.305 NBPS Support in LTE |
R2-123103
| revised | RAN2#78 | TruePosition |
| | | - | | LCS_LTE-NBPS-Core |
|
|
| 36.305 | 0030 | - | A | 10.2.0 | Rel-10 | Clarification on E-CID method |
R2-114580
| agreed | RAN2#75 | Huawei, HiSilicon |
RP-111279
| approved | RAN#53 | R2 | 10.3.0 | LCS_LTE |
|
|
| 36.305 | 0029 | - | F | 9.7.0 | Rel-9 | Clarification on E-CID method |
R2-114579
| agreed | RAN2#75 | Huawei, HiSilicon |
RP-111279
| approved | RAN#53 | R2 | 9.8.0 | LCS_LTE |
|
|
| 36.305 | 0028 | - | A | 10.1.0 | Rel-10 | Corrections to the LPP protocol layering |
R2-112732
| agreed | RAN2#74 | Huawei,HiSilicon |
RP-110830
| approved | RAN#52 | R2 | 10.2.0 | LCS_LTE |
|
|
| 36.305 | 0027 | - | F | 9.6.0 | Rel-9 | Corrections to the LPP protocol layering |
R2-112731
| agreed | RAN2#74 | Huawei,HiSilicon |
RP-110830
| approved | RAN#52 | R2 | 9.7.0 | LCS_LTE |
|
|
| 36.305 | 0026 | - | A | 10.1.0 | Rel-10 | Corrections to align stage2 with stage3 specification |
R2-112730
| agreed | RAN2#74 | CATT |
RP-110830
| approved | RAN#52 | R2 | 10.2.0 | TEI9, LCS_LTE |
|
|
| 36.305 | 0025 | - | F | 9.6.0 | Rel-9 | Corrections to align stage2 with stage3 specification |
R2-112729
| agreed | RAN2#74 | CATT |
RP-110830
| approved | RAN#52 | R2 | 9.7.0 | TEI9, LCS_LTE |
|
|
| 36.305 | 0024 | - | A | 10.0.0 | Rel-10 | Alignment of LPPa descriptions to Stage 3 |
R2-111754
| agreed | RAN2#73 | RAN3 |
RP-110269
| approved | RAN#51 | R2 | 10.1.0 | LCS_LTE |
|
|
| 36.305 | 0023 | - | F | 9.5.0 | Rel-9 | Alignment of LPPa descriptions to Stage 3^^ |
R2-111753
| agreed | RAN2#73 | RAN3 |
RP-110269
| approved | RAN#51 | R2 | 9.6.0 | LCS_LTE |
|
|
| 36.305 | 0022 | - | F | 9.4.0 | Rel-9 | Alignment of LPPa descriptions to stage 3 |
R2-106946
| agreed | RAN2#72 | RAN3 |
RP-101207
| approved | RAN#50 | R2 | 9.5.0 | LCS_LTE |
|
|
| 36.305 | 0019 | - | F | 9.3.0 | Rel-9 | Clarifications to LPP transferred information |
R2-104976
| agreed | RAN2#71 | HTC |
RP-100852
| approved | RAN#49 | R2 | 9.4.0 | LCS_LTE |
|
|
| 36.305 | 0018 | - | F | 9.3.0 | Rel-9 | Corrections on LPP session identifier in Stage 2 |
R2-104271
| agreed | RAN2#71 | HTC |
RP-100852
| approved | RAN#49 | R2 | 9.4.0 | LCS_LTE |
|
|
| 36.305 | 0017 | - | F | 9.2.0 | Rel-9 | Correction on LPP session definition in LPP stage 2 |
R2-103411
| agreed | RAN2#70 | HTC |
RP-100558
| approved | RAN#48 | R2 | 9.3.0 | LCS_LTE |
|
|
| 36.305 | 0016 | - | F | 9.2.0 | Rel-9 | Miscelleanous corrections to LPP stage 2 |
R2-103410
| agreed | RAN2#70 | HTC |
RP-100558
| approved | RAN#48 | R2 | 9.3.0 | LCS_LTE |
|
|
| 36.305 | 0015 | - | F | 9.1.0 | Rel-9 | Transfer of LPPa PDUs over S1 |
R2-101931
| agreed | RAN2#69 | RAN3 (Alcatel-L... |
RP-100304
| approved | RAN#47 | R2 | 9.2.0 | LCS_LTE |
|
|
| 36.305 | 0014 | - | F | 9.1.0 | Rel-9 | Clarification on Error Case Handling |
R2-101777
| agreed | RAN2#69 | Huawei |
RP-100304
| approved | RAN#47 | R2 | 9.2.0 | LCS_LTE |
|
|
| 36.305 | 0013 | - | F | 9.1.0 | Rel-9 | Add LPP procedures to align with 36.355 |
R2-101780
| agreed | RAN2#69 | Huawei |
RP-100304
| approved | RAN#47 | R2 | 9.2.0 | LCS_LTE |
|
|
| 36.305 | 0012 | - | F | 9.1.0 | Rel-9 | Clarification of information transfer for OTDOA |
R2-101778
| agreed | RAN2#69 | Huawei |
RP-100304
| approved | RAN#47 | R2 | 9.2.0 | LCS_LTE |
|
|
| 36.305 | 0011 | - | B | 9.1.0 | Rel-9 | clarification on routing id |
R2-101865
| agreed | RAN2#69 | Huawei |
RP-100304
| approved | RAN#47 | R2 | 9.2.0 | LCS_LTE |
|
|
| 36.305 | 0010 | - | F | 9.1.0 | Rel-9 | Updates to LPPa material in stage 2 |
R2-101008
| agreed | RAN2#69 | RAN3 (contact: ... |
RP-100304
| approved | RAN#47 | R2 | 9.2.0 | LCS_LTE |
|
|
| 36.305 | 0009 | - | F | 9.1.0 | Rel-9 | Updates to LPP material in stage 2 |
R2-100971
| agreed | RAN2#69 | Qualcomm Incorp... |
RP-100304
| approved | RAN#47 | R2 | 9.2.0 | LCS_LTE |
|
|
| 36.305 | 0008 | 1 | F | 9.1.0 | Rel-9 | Stage 2 updates to align with stage 3 |
R2-101776
| agreed | RAN2#69 | Ericsson, ST-Er... |
RP-100304
| approved | RAN#47 | R2 | 9.2.0 | LCS_LTE |
|
|
| 36.305 | 0007 | - | F | 9.1.0 | Rel-9 | Clarification on positioning procedure |
R2-100969
| agreed | RAN2#69 | Huawei, Qualcom... |
RP-100304
| approved | RAN#47 | R2 | 9.2.0 | LCS_LTE |
|
|
| 36.305 | 0006 | - | F | 9.1.0 | Rel-9 | Clarification on E-CID parameters |
R2-100968
| agreed | RAN2#69 | Huawei, CATT, Q... |
RP-100304
| approved | RAN#47 | R2 | 9.2.0 | LCS_LTE |
|
|
| 36.305 | 0005 | - | F | 9.0.0 | Rel-9 | Transfer of LPPa PDU over S1 |
R2-097526
| agreed | RAN2#68 | RAN3 |
RP-091340
| approved | RAN#46 | R2 | 9.1.0 | LCS_LTE |
|
|
| 36.305 | 0004 | - | C | 9.0.0 | Rel-9 | Removal of capability storage at MME |
R2-097368
| agreed | RAN2#68 | Qualcomm Europe |
RP-091340
| approved | RAN#46 | R2 | 9.1.0 | LCS_LTE |
|
|
| 36.305 | 0001 | 1 | C | 9.0.0 | Rel-9 | Removal of UE-based OTDOA and ECID from LPP stage 2 |
R2-097363
| agreed | RAN2#68 | Qualcomm Europe |
RP-091340
| approved | RAN#46 | R2 | 9.1.0 | LCS_LTE |
|
|
| 36.305 | | - | B | | Rel-13 | Introduction of WLAN, BT, Sensor, and UE autonomous positioning |
R2-154822
| withdrawn | RAN2#91-BIS | |
| | | | | |
|