|
|
| 36.331 | 5173 | - | F | 19.0.0 | Rel-19 | Correction for the redirection from E-UTRAN TN to NB-IoT NTN [IoT-TN-NTN-redir] |
R2-2507910
| endorsed | RAN2#131bis | Google, Samsung... |
| | | | | TEI19 |
|
|
|
| 36.331 | 5172 | - | B | 19.0.0 | Rel-19 | CR to 36.304 Introduction of MINT in EPS |
R2-2507569
| withdrawn | RAN2#131bis | LG Electronics Inc. |
| | | | | MINT_Ph2 |
|
|
|
| 36.331 | 5171 | 3 | B | 19.0.0 | Rel-19 | Introduction of MINT in EPS |
R2-2507936
| endorsed | RAN2#131bis | LG Electronics ... |
| | | | | MINT_Ph2 |
|
|
|
| 36.331 | 5171 | 2 | B | 19.0.0 | Rel-19 | Introduction of MINT in EPS |
R2-2507741
| revised | RAN2#131bis | LG Electronics ... |
| | | | | MINT_Ph2 |
|
|
|
| 36.331 | 5171 | 1 | B | 19.0.0 | Rel-19 | Introduction of MINT in EPS |
R2-2507740
| | RAN2#131bis | LG Electronics ... |
| | | | | MINT_Ph2 |
|
|
|
| 36.331 | 5171 | - | B | 19.0.0 | Rel-19 | CR to 36.331 Introduction of MINT in EPS |
R2-2507568
| revised | RAN2#131bis | LG Electronics ... |
| | | | | MINT_Ph2 |
|
|
|
| 36.331 | 5170 | - | A | 18.7.0 | Rel-18 | Introduce UE capability for UE coarse location reporting |
R2-2507480
| | RAN2#131bis | Xiaomi |
| | | | | LTE_NBIOT_eMTC_... |
|
|
|
| 36.331 | 5169 | - | F | 17.14.0 | Rel-17 | Introduce UE capability for UE coarse location reporting |
R2-2507479
| not pursued | RAN2#131bis | Xiaomi |
| | | | | LTE_NBIOT_eMTC_... |
|
|
|
| 36.331 | 5168 | 2 | F | 19.0.0 | Rel-19 | Corrections to LTE-based 5G Broadcast Phase 2 after ASN.1 review |
R2-2507927
| endorsed | RAN2#131bis | Qualcomm Incorp... |
| | | | | LTE_terr_bcast_... |
|
|
|
| 36.331 | 5168 | 1 | F | 19.0.0 | Rel-19 | Corrections to LTE-based 5G Broadcast Phase 2 after ASN.1 review |
R2-2507926
| revised | RAN2#131bis | Qualcomm Incorp... |
| | | | | LTE_terr_bcast_... |
|
|
|
| 36.331 | 5168 | - | F | 19.0.0 | Rel-19 | Corrections to LTE-based 5G Broadcast Phase 2 after ASN.1 review |
R2-2507469
| revised | RAN2#131bis | Qualcomm Incorp... |
| | | | | LTE_terr_bcast_... |
|
|
|
| 36.331 | 5167 | - | F | 19.0.0 | Rel-19 | Correction on R19 SONMDT in TS 36.331 |
R2-2507422
| endorsed | RAN2#131bis | Huawei, HiSilicon |
| | | | | NR_ENDC_SON_MDT... |
|
|
|
| 36.331 | 5166 | - | A | 19.0.0 | Rel-19 | Correction on event triggered based logged MDT configuration |
R2-2507415
| not pursued | RAN2#131bis | Huawei, HiSilic... |
| | | | | NR_ENDC_SON_MDT... |
|
|
|
| 36.331 | 5165 | - | A | 18.7.0 | Rel-18 | Correction on event triggered based logged MDT configuration |
R2-2507414
| not pursued | RAN2#131bis | Huawei, HiSilic... |
| | | | | NR_ENDC_SON_MDT... |
|
|
|
| 36.331 | 5164 | 1 | F | 17.14.0 | Rel-17 | Correction on event triggered based logged MDT configuration |
R2-2507700
| not pursued | RAN2#131bis | Huawei, HiSilic... |
| | | | | NR_ENDC_SON_MDT... |
|
|
|
| 36.331 | 5164 | - | F | 17.14.0 | Rel-17 | Correction on event triggered based logged MDT configuration |
R2-2507413
| revised | RAN2#131bis | Huawei, HiSilic... |
| | | | | NR_ENDC_SON_MDT... |
|
|
|
| 36.331 | 5163 | - | B | 19.0.0 | Rel-19 | NB-IoT NTN to NR NTN Cell Selection |
R2-2507356
| | RAN2#131bis | EchoStar, Boost... |
| | | | | IoT_NTN_enh-Core |
|
|
|
| 36.331 | 5162 | 1 | F | 19.0.0 | Rel-19 | Rapporteur correction on CAS muting for LTE based 5G broadcast [5GB_CASMuting] |
R2-2507263
| endorsed | RAN2#131bis | Huawei, HiSilic... |
| | | | | TEI19 |
|
|
|
| 36.331 | 5162 | - | F | 19.0.0 | Rel-19 | Rapporteur correction on CAS muting for LTE based 5G broadcast [5GB_CASMuting] |
R2-2507139
| revised | RAN2#131bis | Huawei, HiSilic... |
| | | | | TEI19 |
|
|
|
| 36.331 | 5161 | 3 | F | 19.0.0 | Rel-19 | Rapporteur correction on IoT NTN TDD |
R2-2507788
| endorsed | RAN2#131bis | Huawei, HiSilicon |
| | | | | IoT_NTN_TDD |
|
|
|
| 36.331 | 5161 | 2 | F | 19.0.0 | Rel-19 | Rapporteur correction on IoT NTN TDD |
R2-2507772
| revised | RAN2#131bis | Huawei, HiSilicon |
| | | | | IoT_NTN_TDD |
|
|
|
| 36.331 | 5161 | 1 | F | 19.0.0 | Rel-19 | Rapporteur correction on IoT NTN TDD |
R2-2507262
| revised | RAN2#131bis | Huawei, HiSilicon |
| | | | | IoT_NTN_TDD |
|
|
|
| 36.331 | 5161 | - | F | 19.0.0 | Rel-19 | Rapporteur correction on IoT NTN TDD |
R2-2507062
| revised | RAN2#131bis | Huawei, HiSilicon |
| | | | | IoT_NTN_TDD |
|
|
|
| 36.331 | 5160 | 2 | F | 19.0.0 | Rel-19 | Rapporteur correction on IoT NTN Ph3 |
R2-2507787
| endorsed | RAN2#131bis | Huawei, HiSilicon |
| | | | | IoT_NTN_Ph3-Core |
|
|
|
| 36.331 | 5160 | 1 | F | 19.0.0 | Rel-19 | Rapporteur correction on IoT NTN Ph3 |
R2-2507261
| revised | RAN2#131bis | Huawei, HiSilicon |
| | | | | IoT_NTN_Ph3-Core |
|
|
|
| 36.331 | 5160 | - | F | 19.0.0 | Rel-19 | Rapporteur correction on IoT NTN Ph3 |
R2-2507059
| revised | RAN2#131bis | Huawei, HiSilicon |
| | | | | IoT_NTN_Ph3-Core |
|
|
|
| 36.331 | 5159 | - | A | 18.7.0 | Rel-18 | Correction on GNSS position acquisition |
R2-2506977
| not pursued | RAN2#131bis | Xiaomi |
| | | | | LTE_NBIOT_eMTC_... |
|
|
|
| 36.331 | 5158 | - | F | 17.14.0 | Rel-17 | Correction on GNSS position acquisition |
R2-2506976
| not pursued | RAN2#131bis | Xiaomi |
| | | | | LTE_NBIOT_eMTC_... |
|
|
|
| 36.331 | 5157 | 1 | F | 19.0.0 | Rel-19 | Corrections on LTE TN to NR NTN IDLE mode mobility in TS 36.331 |
R2-2507786
| endorsed | RAN2#131bis | CATT |
| | | | | LTE_TN_NR_NTN_mob |
|
|
|
| 36.331 | 5157 | - | F | 18.6.0 | Rel-19 | Corrections on LTE TN to NR NTN IDLE mode mobility in TS 38.331 |
R2-2506869
| revised | RAN2#131bis | CATT |
| | | | | LTE_TN_NR_NTN_mob |
|
|
|
| 36.331 | 5156 | 2 | B | 18.6.0 | Rel-19 | Introduction of IoT TN to NTN redirection [IoT_TN_NTN_redir] |
R2-2506653
| agreed | RAN2#131 | Samsung, Ericss... |
RP-252797
| approved | RAN#109 | RAN2 | 19.0.0 | TEI19 |
|
|
|
| 36.331 | 5156 | 1 | B | 18.6.0 | Rel-19 | Introduction of IoT TN to NTN redirection [IoT-TN-NTN-redir] |
R2-2506518
| revised | RAN2#131 | Samsung, Ericss... |
| | | | | TEI19 |
|
|
|
| 36.331 | 5156 | - | B | 18.6.0 | Rel-19 | Introduction of redirection from NR TN to NR NTN to 36.331 [NR-TN-NTN-redir] |
R2-2506428
| revised | RAN2#131 | Samsung, Ericss... |
| | | | | TEI19 |
|
|
|
| 36.331 | 5155 | 1 | B | 18.6.0 | Rel-19 | Introduction of MINT in EPS |
R2-2506827
| not pursued | RAN2#131bis | Google |
| | | | | TEI19 |
|
|
|
| 36.331 | 5155 | - | B | 18.6.0 | Rel-19 | Introduction of MINT in EPS |
R2-2506192
| revised | RAN2#131 | Google |
| | | | | TEI19 |
|
|
|
| 36.331 | 5154 | - | B | 18.6.0 | Rel-19 | CR to TS 36.331 - Introduction of RRC Release with Redirection for NB-IoT NTN to NR-NTN |
R2-2506179
| | RAN2#131 | Aalyria |
| | | | | IoT_NTN_enh-Cor... |
|
|
|
| 36.331 | 5153 | - | F | 18.6.0 | Rel-19 | k-Mac extension for IoT NTN |
R2-2506174
| | RAN2#131 | THALES, Samsung |
| | | | | IoT_NTN_Ph3-Core |
|
|
|
| 36.331 | 5152 | 1 | F | 18.6.0 | Rel-18 | Clarification of satellite identifiers |
R2-2506277
| agreed | RAN2#131 | THALES, Samsung... |
RP-252769
| approved | RAN#109 | RAN2 | 18.7.0 | IoT_NTN_enh-Core |
|
|
|
| 36.331 | 5152 | - | F | 18.6.0 | Rel-18 | Clarification of satellite identifiers |
R2-2506173
| revised | RAN2#131 | THALES, Samsung... |
| | | | | IoT_NTN_enh-Core |
|
|
|
| 36.331 | 5151 | - | B | 18.6.0 | Rel-19 | NB-IoT NTN to NR NTN Cell Selection |
R2-2506098
| | RAN2#131 | EchoStar, Qualc... |
| | | | | IoT_NTN_enh-Core |
|
|
|
| 36.331 | 5150 | 2 | B | 18.6.0 | Rel-19 | Introduction of R19 SONMDT features in TS 36.331 |
R2-2506564
| agreed | RAN2#131 | Huawei, HiSilicon |
RP-252783
| approved | RAN#109 | RAN2 | 19.0.0 | NR_ENDC_SON_MDT... |
|
|
|
| 36.331 | 5150 | 1 | B | 18.6.0 | Rel-19 | Introduction of R19 SONMDT features in TS 36.331 |
R2-2506379
| revised | RAN2#131 | Huawei, HiSilicon |
| | | | | NR_ENDC_SON_MDT... |
|
|
|
| 36.331 | 5150 | - | B | 18.6.0 | Rel-19 | Introduction of R19 SONMDT features in TS 36.331 |
R2-2506081
| revised | RAN2#131 | Huawei, HiSilicon |
| | | | | NR_ENDC_SON_MDT... |
|
|
|
| 36.331 | 5149 | - | B | 18.6.0 | Rel-19 | SatSwitchwithReSync support for IoT NTN |
R2-2505939
| | RAN2#131 | Skylo Technolog... |
| | | | | IoT_NTN_Ph3-Core |
|
|
|
| 36.331 | 5148 | 2 | A | 18.6.0 | Rel-18 | Correction on inter-RAT FR2 measurement capabilities |
R2-2506621
| agreed | RAN2#131 | Nokia, Qualcomm... |
RP-252767
| approved | RAN#109 | RAN2 | 18.7.0 | NR_MG_enh-Core |
|
|
|
| 36.331 | 5148 | 1 | A | 18.6.0 | Rel-18 | Correction on inter-RAT FR2 measurement capabilities |
R2-2506371
| revised | RAN2#131 | Nokia, Qualcomm... |
| | | | | NR_MG_enh-Core |
|
|
|
| 36.331 | 5148 | - | A | 18.6.0 | Rel-18 | Correction on inter-RAT FR2 measurement capabilities |
R2-2505898
| revised | RAN2#131 | Nokia |
| | | | | NR_MG_enh-Core |
|
|
|
| 36.331 | 5147 | 2 | F | 17.13.0 | Rel-17 | Correction on inter-RAT FR2 measurement capabilities |
R2-2506620
| agreed | RAN2#131 | Nokia, Qualcomm... |
RP-252767
| approved | RAN#109 | RAN2 | 17.14.0 | NR_MG_enh-Core |
|
|
|
| 36.331 | 5147 | 1 | F | 17.13.0 | Rel-17 | Correction on inter-RAT FR2 measurement capabilities |
R2-2506370
| revised | RAN2#131 | Nokia, Qualcomm... |
| | | | | NR_MG_enh-Core |
|
|
|
| 36.331 | 5147 | - | F | 17.13.0 | Rel-17 | Correction on inter-RAT FR2 measurement capabilities |
R2-2505897
| revised | RAN2#131 | Nokia |
| | | | | NR_MG_enh-Core |
|
|
|
| 36.331 | 5146 | 3 | F | 18.6.0 | Rel-18 | Clarification on UTC time offset in IoT NTN |
R2-2506630
| agreed | RAN2#131 | ZTE Corporation... |
RP-252769
| approved | RAN#109 | RAN2 | 18.7.0 | LTE_NBIOT_eMTC_... |
|
|
|
| 36.331 | 5146 | 2 | F | 18.6.0 | Rel-18 | Clarification on UTC time offset in IoT NTN |
R2-2506283
| revised | RAN2#131 | ZTE Corporation... |
| | | | | LTE_NBIOT_eMTC_... |
|
|
|
| 36.331 | 5146 | 1 | A | 18.6.0 | Rel-18 | Clarification on UTC time offset in IoT NTN |
R2-2506282
| revised | RAN2#131 | ZTE Corporation... |
| | | | | LTE_NBIOT_eMTC_... |
|
|
|
| 36.331 | 5146 | - | A | 18.6.0 | Rel-18 | Clarification on UTC time offset in IoT NTN |
R2-2505886
| revised | RAN2#131 | ZTE Corporation... |
| | | | | LTE_NBIOT_eMTC_... |
|
|
|
| 36.331 | 5145 | - | F | 17.13.0 | Rel-17 | Clarification on UTC time offset in IoT NTN |
R2-2505881
| | RAN2#131 | ZTE Corporation... |
| | | | | LTE_NBIOT_eMTC_... |
|
|
|
| 36.331 | 5144 | - | B | 18.6.0 | Rel-19 | Introduction of LTE-based 5G Broadcast Phase 2 |
R2-2505741
| endorsed | RAN2#131 | Huawei, HiSilic... |
| | | | | LTE_terr_bcast_Ph2 |
|
|
|
| 36.331 | 5143 | 1 | B | 18.6.0 | Rel-19 | Introduction of LTE-based 5G Broadcast Phase 2 |
R2-2506344
| agreed | RAN2#131 | Qualcomm Incorp... |
RP-252794
| approved | RAN#109 | RAN2 | 19.0.0 | LTE_terr_bcast_... |
|
|
|
| 36.331 | 5143 | - | B | 18.6.0 | Rel-19 | Introduction of LTE-based 5G Broadcast Phase 2 |
R2-2505411
| revised | RAN2#131 | Qualcomm Incorp... |
| | | | | LTE_terr_bcast_... |
|
|
|
| 36.331 | 5142 | - | B | 18.6.0 | Rel-19 | NB-IoT NTN to NR NTN Cell Selection |
R2-2505409
| withdrawn | RAN2#131 | EchoStar, Qualc... |
| | | | | IoT_NTN_enh-Core |
|
|
|
| 36.331 | 5141 | - | B | 18.6.0 | Rel-19 | Introduction of LTE TN to NR NTN IDLE mode mobility |
R2-2505233
| withdrawn | RAN2#131 | CATT |
| | | | | LTE_TN_NR_NTN_mob |
|
|
|
| 36.331 | 5140 | - | B | 18.6.0 | Rel-19 | Introduction of NB-IoT satellite information in E-UTRAN [EUTRAN-to-NBIoTNTN] |
R2-2505367
| agreed | RAN2#131 | Google, Samsung... |
RP-252796
| approved | RAN#109 | RAN2 | 19.0.0 | TEI19 |
|
|
|
| 36.331 | 5139 | 2 | B | 18.6.0 | Rel-19 | Introduction of CAS muting in LTE-based 5G broadcast [5GB_CASMuting] |
R2-2506342
| agreed | RAN2#131 | Huawei, HiSilic... |
RP-252797
| approved | RAN#109 | RAN2 | 19.0.0 | TEI19 |
|
|
|
| 36.331 | 5139 | 1 | B | 18.6.0 | Rel-19 | Introduction of CAS muting in LTE-based 5G broadcast [5GB_CASMuting] |
R2-2506334
| revised | RAN2#131 | Huawei, HiSilic... |
| | | | | TEI19 |
|
|
|
| 36.331 | 5139 | - | B | 18.6.0 | Rel-19 | Introduction of CAS muting in LTE-based 5G broadcast [5GB_CASMuting] |
R2-2505331
| revised | RAN2#131 | Huawei, HiSilic... |
| | | | | TEI19 |
|
|
|
| 36.331 | 5138 | 1 | B | 18.6.0 | Rel-19 | Introduction of IoT NTN TDD mode |
R2-2506558
| agreed | RAN2#131 | Huawei, HiSilicon |
RP-252795
| approved | RAN#109 | RAN2 | 19.0.0 | IoT_NTN_TDD-Core |
|
|
|
| 36.331 | 5138 | - | B | 18.6.0 | Rel-19 | Introduction of IoT NTN TDD mode |
R2-2505248
| revised | RAN2#131 | Huawei, HiSilicon |
| | | | | IoT_NTN_TDD-Core |
|
|
|
| 36.331 | 5137 | 2 | B | 18.6.0 | Rel-19 | Introduction of IoT NTN Ph3 |
R2-2506573
| agreed | RAN2#131 | Huawei, HiSilicon |
RP-252792
| approved | RAN#109 | RAN2 | 19.0.0 | IoT_NTN_Ph3-Core |
|
|
|
| 36.331 | 5137 | 1 | B | 18.6.0 | Rel-19 | Introduction of IoT NTN Ph3 |
R2-2506557
| revised | RAN2#131 | Huawei, HiSilicon |
| | | | | IoT_NTN_Ph3-Core |
|
|
|
| 36.331 | 5137 | - | B | 18.6.0 | Rel-19 | Introduction of IoT NTN Ph3 |
R2-2505246
| revised | RAN2#131 | Huawei, HiSilicon |
| | | | | IoT_NTN_Ph3-Core |
|
|
|
| 36.331 | 5136 | 1 | A | 18.6.0 | Rel-18 | Correction on LTE RLF report logging |
R2-2506353
| agreed | RAN2#131 | CATT |
RP-252766
| approved | RAN#109 | RAN2 | 18.7.0 | LTE_feMob-Core |
|
|
|
| 36.331 | 5136 | - | A | 18.6.0 | Rel-18 | Correction on LTE RLF report logging |
R2-2505204
| revised | RAN2#131 | CATT |
| | | | | LTE_feMob-Core |
|
|
|
| 36.331 | 5135 | 1 | A | 17.13.0 | Rel-17 | Correction on LTE RLF report logging |
R2-2506352
| agreed | RAN2#131 | CATT |
RP-252766
| approved | RAN#109 | RAN2 | 17.14.0 | LTE_feMob-Core |
|
|
|
| 36.331 | 5135 | - | A | 17.13.0 | Rel-17 | Correction on LTE RLF report logging |
R2-2505203
| revised | RAN2#131 | CATT |
| | | | | LTE_feMob-Core |
|
|
|
| 36.331 | 5134 | 1 | F | 16.20.0 | Rel-16 | Correction on LTE RLF report logging |
R2-2506351
| agreed | RAN2#131 | CATT |
RP-252766
| approved | RAN#109 | RAN2 | 16.21.0 | LTE_feMob-Core |
|
|
|
| 36.331 | 5134 | - | F | 16.20.0 | Rel-16 | Correction on LTE RLF report logging |
R2-2505202
| revised | RAN2#131 | CATT |
| | | | | LTE_feMob-Core |
|
|
|
| 36.331 | 5133 | 1 | A | 18.5.0 | Rel-18 | Miscellaneous non-controversial corrections |
R2-2504840
| agreed | RAN2#130 | Samsung |
RP-251691
| approved | RAN#108 | RAN2 | 18.6.0 | NR_newRAT-Core,... |
|
|
|
| 36.331 | 5133 | - | F | 18.5.0 | Rel-18 | Miscellaneous non-controversial corrections |
R2-2504453
| revised | RAN2#130 | Samsung |
| | | | | NR_newRAT-Core |
|
|
|
| 36.331 | 5132 | 1 | A | 17.12.0 | Rel-17 | Miscellaneous non-controversial corrections |
R2-2504839
| agreed | RAN2#130 | Samsung |
RP-251691
| approved | RAN#108 | RAN2 | 17.13.0 | NR_newRAT-Core,... |
|
|
|
| 36.331 | 5132 | - | A | 17.12.0 | Rel-17 | Miscellaneous non-controversial corrections |
R2-2504452
| revised | RAN2#130 | Samsung |
| | | | | NR_newRAT-Core |
|
|
|
| 36.331 | 5131 | 2 | F | 16.19.0 | Rel-16 | Miscellaneous non-controversial corrections |
R2-2504838
| agreed | RAN2#130 | Samsung |
RP-251691
| approved | RAN#108 | RAN2 | 16.20.0 | NR_newRAT-Core,... |
|
|
|
| 36.331 | 5131 | 1 | F | 16.19.0 | Rel-16 | Miscellaneous non-controversial corrections |
R2-2504553
| revised | RAN2#130 | Samsung |
| | | | | NR_newRAT-Core |
|
|
|
| 36.331 | 5131 | - | F | 16.19.0 | Rel-16 | Miscellaneous non-controversial corrections |
R2-2504451
| revised | RAN2#130 | Samsung |
| | | | | NR_newRAT-Core |
|
|
|
| 36.331 | 5130 | - | A | 18.5.0 | Rel-18 | Clarification to NTN SI message accumulation over SI-windows |
R2-2504337
| not pursued | RAN2#130 | Nordic Semicond... |
| | | | | LTE_NBIOT_eMTC_NTN |
|
|
|
| 36.331 | 5129 | - | F | 17.12.0 | Rel-17 | Clarification to NTN SI message accumulation over SI-windows |
R2-2504336
| not pursued | RAN2#130 | Nordic Semicond... |
| | | | | LTE_NBIOT_eMTC_NTN |
|
|
|
| 36.331 | 5128 | 1 | A | 18.5.0 | Rel-18 | Correction to explicit indication of epoch in SIB31 |
R2-2504764
| agreed | RAN2#130 | Nordic Semicond... |
RP-251693
| approved | RAN#108 | RAN2 | 18.6.0 | LTE_NBIOT_eMTC_NTN |
|
|
|
| 36.331 | 5128 | - | A | 18.5.0 | Rel-18 | Correction to explicit indication of epoch in SIB31 |
R2-2504333
| revised | RAN2#130 | Nordic Semicond... |
| | | | | LTE_NBIOT_eMTC_NTN |
|
|
|
| 36.331 | 5127 | 1 | F | 17.12.0 | Rel-17 | Correction to explicit indication of epoch in SIB31 |
R2-2504763
| agreed | RAN2#130 | Nordic Semicond... |
RP-251693
| approved | RAN#108 | RAN2 | 17.13.0 | LTE_NBIOT_eMTC_NTN |
|
|
|
| 36.331 | 5127 | - | F | 17.12.0 | Rel-17 | Correction to explicit indication of epoch in SIB31 |
R2-2504332
| revised | RAN2#130 | Nordic Semicond... |
| | | | | LTE_NBIOT_eMTC_NTN |
|
|
|
| 36.331 | 5126 | - | A | 18.5.0 | Rel-18 | Correction on MBMS Interest Indication |
R2-2504326
| withdrawn | RAN2#130 | Samsung |
| | | | | TEI15 |
|
|
|
| 36.331 | 5125 | 2 | F | 18.6.0 | Rel-18 | Correction on MBMS Interest Indication |
R2-2506354
| agreed | RAN2#131 | Samsung, Nokia,... |
RP-252769
| approved | RAN#109 | RAN2 | 18.7.0 | LTE_terr_bcast-... |
|
|
|
| 36.331 | 5125 | 1 | F | 18.6.0 | Rel-18 | Correction on MBMS Interest Indication |
R2-2505700
| revised | RAN2#131 | Samsung, Nokia,... |
| | | | | LTE_terr_bcast-... |
|
|
|
| 36.331 | 5125 | - | A | 18.5.0 | Rel-18 | Correction on MBMS Interest Indication |
R2-2504325
| revised | RAN2#130 | Samsung |
| | | | | TEI15 |
|
|
|
| 36.331 | 5124 | - | A | 17.12.0 | Rel-17 | Correction on MBMS Interest Indication |
R2-2504324
| postponed | RAN2#130 | Samsung |
| | | | | TEI15 |
|
|
|
| 36.331 | 5123 | - | A | 16.19.0 | Rel-16 | Correction on MBMS Interest Indication |
R2-2504323
| postponed | RAN2#130 | Samsung |
| | | | | TEI15 |
|
|
|
| 36.331 | 5122 | - | F | 15.23.0 | Rel-15 | Correction on MBMS Interest Indication |
R2-2504322
| postponed | RAN2#130 | Samsung |
| | | | | TEI15 |
|
|
|
| 36.331 | 5121 | 2 | F | 18.6.0 | Rel-18 | Corrections on IoT NTN SIB33 |
R2-2506275
| agreed | RAN2#131 | Samsung |
RP-252769
| approved | RAN#109 | RAN2 | 18.7.0 | IoT_NTN_enh-Core |
|
|
|
| 36.331 | 5121 | 1 | F | 18.6.0 | Rel-18 | Various corrections on connected mode RRM for IoT NTN |
R2-2505914
| revised | RAN2#131 | Samsung |
| | | | | IoT_NTN_enh-Core |
|
|
|
| 36.331 | 5121 | - | F | 18.5.0 | Rel-18 | Various corrections on connected mode RRM for IoT NTN |
R2-2504095
| revised | RAN2#130 | Samsung |
| | | | | IoT_NTN_enh-Core |
|
|
|
| 36.331 | 5120 | - | A | 18.5.0 | Rel-18 | Introducing UE capability for A4 A5 ReportOnLeave |
R2-2504020
| agreed | RAN2#130 | ZTE Corporation... |
RP-251688
| approved | RAN#108 | RAN2 | 18.6.0 | LTE_Aerial-Core |
|
|
|
| 36.331 | 5119 | - | A | 17.12.0 | Rel-17 | Introducing UE capability for A4 A5 ReportOnLeave |
R2-2504019
| agreed | RAN2#130 | ZTE Corporation... |
RP-251688
| approved | RAN#108 | RAN2 | 17.13.0 | LTE_Aerial-Core |
|
|
|
| 36.331 | 5118 | - | A | 16.19.0 | Rel-16 | Introducing UE capability for A4 A5 ReportOnLeave |
R2-2504018
| agreed | RAN2#130 | ZTE Corporation... |
RP-251688
| approved | RAN#108 | RAN2 | 16.20.0 | LTE_Aerial-Core |
|
|
|
| 36.331 | 5117 | - | F | 15.23.0 | Rel-15 | Introducing UE capability for A4 A5 ReportOnLeave |
R2-2504017
| agreed | RAN2#130 | ZTE Corporation... |
RP-251688
| approved | RAN#108 | RAN2 | 15.24.0 | LTE_Aerial-Core |
|
|
|
| 36.331 | 5116 | 2 | A | 18.5.0 | Rel-18 | Correction to NeedForGap capability |
R2-2504837
| agreed | RAN2#130 | Huawei, HiSilicon |
RP-251688
| approved | RAN#108 | RAN2 | 18.6.0 | NR_newRAT-Core,... |
|
|
|
| 36.331 | 5116 | 1 | A | 18.5.0 | Rel-18 | Correction to NeedForGap capability |
R2-2503982
| revised | RAN2#130 | Huawei, HiSilicon |
| | | | | NR_newRAT-Core,... |
|
|
|
| 36.331 | 5116 | - | A | 18.5.0 | Rel-18 | Correction to NeedForGap capability (R18) |
R2-2503941
| revised | RAN2#130 | Huawei, HiSilicon |
| | | | | NR_newRAT-Core,... |
|
|
|
| 36.331 | 5115 | 1 | A | 17.12.0 | Rel-17 | Correction to NeedForGap capability |
R2-2504836
| agreed | RAN2#130 | Huawei, HiSilicon |
RP-251688
| approved | RAN#108 | RAN2 | 17.13.0 | NR_newRAT-Core,... |
|
|
|
| 36.331 | 5115 | - | A | 17.12.0 | Rel-17 | Correction to NeedForGap capability |
R2-2503940
| revised | RAN2#130 | Huawei, HiSilicon |
| | | | | NR_newRAT-Core,... |
|
|
|
| 36.331 | 5114 | 1 | F | 16.19.0 | Rel-16 | Correction to NeedForGap capability |
R2-2504835
| agreed | RAN2#130 | Huawei, HiSilicon |
RP-251688
| approved | RAN#108 | RAN2 | 16.20.0 | NR_newRAT-Core,... |
|
|
|
| 36.331 | 5114 | - | F | 16.19.0 | Rel-16 | Correction to NeedForGap capability |
R2-2503939
| revised | RAN2#130 | Huawei, HiSilicon |
| | | | | NR_newRAT-Core,... |
|
|
|
| 36.331 | 5113 | 1 | F | 16.19.0 | Rel-16 | Correction on timeUntilReconnection in RLF report |
R2-2504086
| agreed | RAN2#130 | ZTE Corporation... |
RP-251690
| approved | RAN#108 | RAN2 | 16.20.0 | NR_SON_MDT-Core |
|
|
|
| 36.331 | 5113 | - | F | 16.19.0 | Rel-16 | Correction on timeUntilReconnection in RLF report |
R2-2503116
| revised | RAN2#129bis | ZTE Corporation... |
| | | | | NR_SON_MDT-Core |
|
|
|
| 36.331 | 5112 | - | F | 18.5.0 | Rel-18 | Correction on release procedures when HARQ feedback is not configured |
R2-2502687
| not pursued | RAN2#129bis | Samsung |
| | | | | IoT_NTN_enh-Core |
|
|
|
| 36.331 | 5111 | - | F | 18.5.0 | Rel-18 | Correction on deprioritisationReq delete |
R2-2502836
| not pursued | RAN2#129bis | Google |
| | | | | LTE-L23, TEI11 |
|
|
|
| 36.331 | 5110 | 3 | B | 18.6.0 | Rel-19 | Introduction of ANR reporting of HSDN cells [ANR_HSDN] |
R2-2506086
| agreed | RAN2#131 | Huawei, HiSilic... |
RP-252796
| approved | RAN#109 | RAN2 | 19.0.0 | TEI19 |
|
|
|
| 36.331 | 5110 | 2 | B | 18.5.0 | Rel-19 | Introduction of ANR reporting of HSDN cells [ANR_HSDN] |
R2-2504232
| revised | RAN2#130 | Huawei, HiSilic... |
| | | | | TEI19 |
|
|
|
| 36.331 | 5110 | 1 | B | 18.5.0 | Rel-19 | Introduction of ANR reporting of HSDN cells [ANR_HSDN] |
R2-2502997
| revised | RAN2#129bis | Huawei, HiSilic... |
| | | | | TEI19 |
|
|
|
| 36.331 | 5110 | - | B | 18.5.0 | Rel-19 | Introduction of ANR reporting of HSDN cells [ANR_HSDN] |
R2-2502785
| revised | RAN2#129bis | Huawei, HiSilic... |
| | | | | TEI19 |
|
|
|
| 36.331 | 5109 | 2 | A | 18.5.0 | Rel-18 | Correction on timeUntilReconnection in RLF report |
R2-2504088
| agreed | RAN2#130 | ZTE Corporation... |
RP-251692
| approved | RAN#108 | RAN2 | 18.6.0 | NR_ENDC_SON_MDT... |
|
|
|
| 36.331 | 5109 | 1 | A | 18.5.0 | Rel-18 | Correction on timeUntilReconnection in RLF report |
R2-2503103
| revised | RAN2#129bis | ZTE Corporation... |
| | | | | NR_ENDC_SON_MDT... |
|
|
|
| 36.331 | 5109 | - | A | 18.5.0 | Rel-18 | Correction on timeUntilReconnection in RLF report |
R2-2502529
| revised | RAN2#129bis | ZTE Corporation... |
| | | | | NR_ENDC_SON_MDT... |
|
|
|
| 36.331 | 5108 | 2 | F | 17.12.0 | Rel-17 | Correction on timeUntilReconnection in RLF report |
R2-2504087
| agreed | RAN2#130 | ZTE Corporation... |
RP-251692
| approved | RAN#108 | RAN2 | 17.13.0 | NR_ENDC_SON_MDT... |
|
|
|
| 36.331 | 5108 | 1 | F | 17.12.0 | Rel-17 | Correction on timeUntilReconnection in RLF report |
R2-2503102
| revised | RAN2#129bis | ZTE Corporation... |
| | | | | NR_ENDC_SON_MDT... |
|
|
|
| 36.331 | 5108 | - | F | 17.12.0 | Rel-17 | Correction on timeUntilReconnection in RLF report |
R2-2502528
| revised | RAN2#129bis | ZTE Corporation... |
| | | | | NR_ENDC_SON_MDT... |
|
|
|
| 36.331 | 5107 | - | A | 18.5.0 | Rel-18 | Correction on carrier frequency information in RRCConnectionRelease. |
R2-2502250
| not pursued | RAN2#129bis | CATT, Qualcomm ... |
| | | | | NR_NTN_solution... |
|
|
|
| 36.331 | 5106 | - | F | 17.12.0 | Rel-17 | Correction on carrier frequency information in RRCConnectionRelease. |
R2-2502249
| not pursued | RAN2#129bis | CATT, Qualcomm ... |
| | | | | NR_NTN_solution... |
|
|
|
| 36.331 | 5105 | 2 | F | 18.5.0 | Rel-18 | Correction on SIB33 reception in RRC_CONNECTED |
R2-2504067
| agreed | RAN2#130 | Huawei, HiSilicon |
RP-251696
| approved | RAN#108 | RAN2 | 18.6.0 | IoT_NTN_enh-Core |
|
|
|
| 36.331 | 5105 | 1 | F | 18.5.0 | Rel-18 | Correction on SIB33 reception in RRC_CONNECTED |
R2-2503061
| endorsed | RAN2#129bis | Huawei, HiSilicon |
| | | | | IoT_NTN_enh-Core |
|
|
|
| 36.331 | 5105 | - | F | 18.5.0 | Rel-18 | Correction on SIB33 reception in RRC_CONNECTED |
R2-2501968
| revised | RAN2#129bis | Huawei, HiSilicon |
| | | | | IoT_NTN_enh-Core |
|
|
|
| 36.331 | 5104 | - | F | 18.5.0 | Rel-18 | Correction on Initiation of NR SCG failure information |
R2-2501908
| merged | RAN2#129bis | CATT |
| | | | | LTE_NR_DC_CA_en... |
|
|
|
| 36.331 | 5103 | - | F | 17.12.0 | Rel-17 | Correction on Initiation of NR SCG failure information |
R2-2501907
| merged | RAN2#129bis | CATT |
| | | | | LTE_NR_DC_CA_en... |
|
|
|
| 36.331 | 5102 | - | F | 16.19.0 | Rel-16 | Correction on Initiation of NR SCG failure information |
R2-2501906
| merged | RAN2#129bis | CATT |
| | | | | LTE_NR_DC_CA_en... |
|
|
|
| 36.331 | 5101 | 1 | F | 18.4.0 | Rel-18 | Correction on GNSS procedure |
R2-2501526
| agreed | RAN2#129 | ZTE Corporation... |
RP-250660
| approved | RAN#107 | RAN2 | 18.5.0 | IoT_NTN_enh-Core |
|
|
|
| 36.331 | 5101 | - | F | 18.4.0 | Rel-18 | Correction on GNSS procedure |
R2-2501269
| revised | RAN2#129 | ZTE Corporation... |
| | | | | IoT_NTN_enh-Core |
|
|
|
| 36.331 | 5100 | - | F | 18.4.0 | Rel-18 | Clarification on the mapping of RSRP thresholds to CE levels |
R2-2501146
| agreed | RAN2#129 | MediaTek Inc. |
RP-250660
| approved | RAN#107 | RAN2 | 18.5.0 | LTE_MTCe2_L1-Co... |
|
|
|
| 36.331 | 5099 | - | A | 18.4.0 | Rel-18 | Correction on the UE behaviours upon setting CEF report |
R2-2501115
| not pursued | RAN2#129 | Huawei, HiSilicon |
| | | | | eMDT_UMTSLTE-Co... |
|
|
|
| 36.331 | 5098 | - | F | 17.11.0 | Rel-17 | Correction on the UE behaviours upon setting CEF report |
R2-2501114
| not pursued | RAN2#129 | Huawei, HiSilicon |
| | | | | eMDT_UMTSLTE-Co... |
|
|
|
| 36.331 | 5097 | - | A | 18.4.0 | Rel-18 | First reconfiguration after reestablishment with SN-terminated bearers |
R2-2500959
| | RAN2#129 | Huawei, HiSilicon |
| | | | | NR_newRAT-Core |
|
|
|
| 36.331 | 5096 | - | A | 17.11.0 | Rel-17 | First reconfiguration after reestablishment with SN-terminated bearers |
R2-2500958
| | RAN2#129 | Huawei, HiSilicon |
| | | | | NR_newRAT-Core |
|
|
|
| 36.331 | 5095 | - | A | 16.18.0 | Rel-16 | First reconfiguration after reestablishment with SN-terminated bearers |
R2-2500957
| | RAN2#129 | Huawei, HiSilicon |
| | | | | NR_newRAT-Core |
|
|
|
| 36.331 | 5094 | - | F | 15.23.0 | Rel-15 | First reconfiguration after reestablishment with SN-terminated bearers |
R2-2500956
| | RAN2#129 | Huawei, HiSilicon |
| | | | | NR_newRAT-Core |
|
|
|
| 36.331 | 5093 | - | D | 17.11.0 | Rel-17 | Clarification on Inclination value description |
R2-2500940
| withdrawn | RAN2#129 | THALES |
| | | | | NR_NTN_solution... |
|
|
|
| 36.331 | 5092 | 3 | A | 18.4.0 | Rel-18 | Clarification on Inclination value description |
R2-2501563
| agreed | RAN2#129 | Thales |
RP-250658
| approved | RAN#107 | RAN2 | 18.5.0 | LTE_NBIOT_eMTC_NTN |
|
|
|
| 36.331 | 5092 | 2 | A | 18.4.0 | Rel-18 | Clarification on Inclination value description |
R2-2501542
| revised | RAN2#129 | THALES |
| | | | | IoT_NTN_enh-Core |
|
|
|
| 36.331 | 5092 | 1 | A | 18.4.0 | Rel-18 | Clarification on Inclination value description |
R2-2501407
| revised | RAN2#129 | THALES |
| | | | | IoT_NTN_enh-Core |
|
|
|
| 36.331 | 5092 | - | A | 18.4.0 | Rel-18 | Clarification on Inclination value description |
R2-2500939
| revised | RAN2#129 | THALES |
| | | | | IoT_NTN_enh-Core |
|
|
|
| 36.331 | 5091 | 3 | F | 17.11.0 | Rel-17 | Clarification on Inclination value description |
R2-2501562
| agreed | RAN2#129 | Thales |
RP-250658
| approved | RAN#107 | RAN2 | 17.12.0 | LTE_NBIOT_eMTC_NTN |
|
|
|
| 36.331 | 5091 | 2 | F | 17.11.0 | Rel-17 | Clarification on Inclination value description |
R2-2501541
| revised | RAN2#129 | THALES |
| | | | | LTE_NBIoT_eMTC_... |
|
|
|
| 36.331 | 5091 | 1 | F | 17.11.0 | Rel-17 | Clarification on Inclination value description |
R2-2501402
| revised | RAN2#129 | THALES |
| | | | | LTE_NBIoT_eMTC_... |
|
|
|
| 36.331 | 5091 | - | F | 17.11.0 | Rel-17 | Clarification on Inclination value description |
R2-2500938
| revised | RAN2#129 | THALES |
| | | | | LTE_NBIoT_eMTC_... |
|
|
|
| 36.331 | 5090 | 2 | B | 18.4.0 | Rel-19 | RAN Notification Area Update (RNA) for Multimedia Priority Service (MPS) [MPS_RNAU_ResumeCause] |
R2-2501536
| postponed | RAN2#129 | Peraton Labs, C... |
| | | | | TEI19 |
|
|
|
| 36.331 | 5090 | 1 | F | 18.4.0 | Rel-18 | RAN Notification Area Update (RNA) for Multimedia Priority Service (MPS) |
R2-2501339
| revised | RAN2#129 | Peraton Labs, A... |
| | | | | TEI18 |
|
|
|
| 36.331 | 5090 | - | F | 18.4.0 | Rel-18 | RAN Notification Area Update (RNA) for Multimedia Priority Service (MPS) |
R2-2500388
| revised | RAN2#129 | Peraton Labs |
| | | | | TEI18 |
|
|
|
| 36.331 | 5089 | 1 | A | 18.4.0 | Rel-18 | Corrections on network signalling of maximum number of UL segments [Max-RRC-SegUL] |
R2-2501368
| agreed | RAN2#129 | Lenovo |
RP-250659
| approved | RAN#107 | RAN2 | 18.5.0 | TEI17 |
|
|
|
| 36.331 | 5089 | - | A | 18.4.0 | Rel-18 | Corrections on network signalling of maximum number of UL segments [Max-RRC-SegUL] |
R2-2500385
| revised | RAN2#129 | Lenovo |
| | | | | TEI17 |
|
|
|
| 36.331 | 5088 | 1 | F | 17.11.0 | Rel-17 | Corrections on network signalling of maximum number of UL segments [Max-RRC-SegUL] |
R2-2501367
| agreed | RAN2#129 | Lenovo |
RP-250659
| approved | RAN#107 | RAN2 | 17.12.0 | TEI17 |
|
|
|
| 36.331 | 5088 | - | F | 17.11.0 | Rel-17 | Corrections on network signalling of maximum number of UL segments [Max-RRC-SegUL] |
R2-2500384
| revised | RAN2#129 | Lenovo |
| | | | | TEI17 |
|
|
|
| 36.331 | 5087 | 2 | A | 18.4.0 | Rel-18 | Correction on MPDCCH parameter in PUR-Config |
R2-2501596
| agreed | RAN2#129 | ZTE Corporation... |
RP-250657
| approved | RAN#107 | RAN2 | 18.5.0 | LTE_eMTC5-Core |
|
|
|
| 36.331 | 5087 | 1 | A | 18.4.0 | Rel-18 | Correction on MPDCCH parameter in PUR-Config |
R2-2501358
| revised | RAN2#129 | ZTE Corporation... |
| | | | | LTE_eMTC5-Core |
|
|
|
| 36.331 | 5087 | - | A | 18.4.0 | Rel-18 | Correction on MPDCCH parameter in PUR-Config |
R2-2500372
| revised | RAN2#129 | ZTE Corporation... |
| | | | | LTE_eMTC5-Core |
|
|
|
| 36.331 | 5086 | 2 | A | 17.11.0 | Rel-17 | Correction on MPDCCH parameter in PUR-Config |
R2-2501595
| agreed | RAN2#129 | ZTE Corporation... |
RP-250657
| approved | RAN#107 | RAN2 | 17.12.0 | LTE_eMTC5-Core |
|
|
|
| 36.331 | 5086 | 1 | A | 17.11.0 | Rel-17 | Correction on MPDCCH parameter in PUR-Config |
R2-2501357
| revised | RAN2#129 | ZTE Corporation... |
| | | | | LTE_eMTC5-Core |
|
|
|
| 36.331 | 5086 | - | A | 17.11.0 | Rel-17 | Correction on MPDCCH parameter in PUR-Config |
R2-2500371
| revised | RAN2#129 | ZTE Corporation... |
| | | | | LTE_eMTC5-Core |
|
|
|
| 36.331 | 5085 | 2 | F | 16.18.0 | Rel-16 | Correction on MPDCCH parameter in PUR-Config |
R2-2501594
| agreed | RAN2#129 | ZTE Corporation... |
RP-250657
| approved | RAN#107 | RAN2 | 16.19.0 | LTE_eMTC5-Core |
|
|
|
| 36.331 | 5085 | 1 | F | 16.18.0 | Rel-16 | Correction on MPDCCH parameter in PUR-Config |
R2-2501356
| revised | RAN2#129 | ZTE Corporation... |
| | | | | LTE_eMTC5-Core |
|
|
|
| 36.331 | 5085 | - | F | 16.18.0 | Rel-16 | Correction on MPDCCH parameter in PUR-Config |
R2-2500369
| revised | RAN2#129 | ZTE Corporation... |
| | | | | LTE_eMTC5-Core |
|
|
|
| 36.331 | 5084 | 1 | A | 18.3.1 | Rel-18 | Introduction of network signalling of maximum number of UL segments [Max-RRC-SegUL] |
R2-2411253
| agreed | RAN2#128 | Huawei, HiSilicon |
RP-243227
| approved | RAN#106 | RAN2 | 18.4.0 | TEI17 |
|
|
|
| 36.331 | 5084 | - | A | 18.3.1 | Rel-18 | Introduction of network signalling of maximum number of UL segments [Max-RRC-SegUL] |
R2-2411229
| revised | RAN2#128 | Huawei, HiSilicon |
| | | | | TEI17 |
|
|
|
| 36.331 | 5083 | 1 | B | 17.10.0 | Rel-17 | Introduction of network signalling of maximum number of UL segments [Max-RRC-SegUL] |
R2-2411252
| agreed | RAN2#128 | Huawei, HiSilicon |
RP-243227
| approved | RAN#106 | RAN2 | 17.11.0 | TEI17 |
|
|
|
| 36.331 | 5083 | - | B | 17.10.0 | Rel-17 | Introduction of network signalling of maximum number of UL segments [Max-RRC-SegUL] |
R2-2411228
| revised | RAN2#128 | Huawei, HiSilicon |
| | | | | TEI17 |
|
|
|
| 36.331 | 5082 | - | F | 18.3.1 | Rel-18 | Capability on measurement gap enhancements |
R2-2411210
| agreed | RAN2#128 | Huawei, HiSilicon |
RP-243220
| approved | RAN#106 | RAN2 | 18.4.0 | NR_MG_enh2-Core |
|
|
|
| 36.331 | 5081 | - | F | 18.3.0 | Rel-18 | Correction to satellite ID in system infromation |
R2-2410866
| agreed | RAN2#128 | Ericsson, Samsung |
RP-243228
| approved | RAN#106 | RAN2 | 18.4.0 | IoT_NTN_enh-Core |
|
|
|
| 36.331 | 5080 | 1 | F | 18.3.1 | Rel-18 | Addition of reference to 38.304 for Qoffsettemp handling |
R2-2411015
| agreed | RAN2#128 | Nokia |
RP-243233
| approved | RAN#106 | RAN2 | 18.4.0 | TEI18 |
|
|
|
| 36.331 | 5080 | - | A | 18.3.1 | Rel-18 | Addition of reference to 38.304 for Qoffsettemp handling |
R2-2410562
| revised | RAN2#128 | Nokia |
| | | | | TEI12 |
|
|
|
| 36.331 | 5079 | - | A | 17.10.0 | Rel-17 | Addition of reference to 38.304 for Qoffsettemp handling |
R2-2410561
| | RAN2#128 | Nokia |
| | | | | TEI12 |
|
|
|
| 36.331 | 5078 | - | A | 16.17.0 | Rel-16 | Addition of reference to 38.304 for Qoffsettemp handling |
R2-2410560
| | RAN2#128 | Nokia |
| | | | | TEI12 |
|
|
|
| 36.331 | 5077 | - | F | 15.23.0 | Rel-15 | Addition of reference to 38.304 for Qoffsettemp handling |
R2-2410559
| | RAN2#128 | Nokia |
| | | | | TEI12 |
|
|
|
| 36.331 | 5076 | 1 | F | 18.3.1 | Rel-18 | Correction on SIB33(-NB) for IoT NTN |
R2-2410964
| agreed | RAN2#128 | Nokia, Nokia Sh... |
RP-243228
| approved | RAN#106 | RAN2 | 18.4.0 | IoT_NTN_enh-Core |
|
|
|
| 36.331 | 5076 | - | F | 18.3.1 | Rel-18 | Correction on SIB33(-NB) for IoT NTN |
R2-2410308
| revised | RAN2#128 | Nokia, Nokia Sh... |
| | | | | IoT_NTN_enh-Core |
|
|
|
| 36.331 | 5075 | - | A | 18.3.1 | Rel-18 | Correction on broadcast of assistance data-r18 |
R2-2410235
| not pursued | RAN2#128 | Huawei, HiSilicon |
| | | | | LCS_LTE_acc_enh-Core |
|
|
|
| 36.331 | 5074 | - | A | 17.10.0 | Rel-17 | Correction on broadcast of assistance data-r17 |
R2-2410234
| not pursued | RAN2#128 | Huawei, HiSilicon |
| | | | | LCS_LTE_acc_enh-Core |
|
|
|
| 36.331 | 5073 | - | A | 16.17.0 | Rel-16 | Correction on broadcast of assistance data-r16 |
R2-2410233
| not pursued | RAN2#128 | Huawei, HiSilicon |
| | | | | LCS_LTE_acc_enh-Core |
|
|
|
| 36.331 | 5072 | - | F | 15.23.0 | Rel-15 | Correction on broadcast of assistance data-r15 |
R2-2410232
| not pursued | RAN2#128 | Huawei, HiSilicon |
| | | | | LCS_LTE_acc_enh-Core |
|
|
|
| 36.331 | 5071 | - | A | 18.3.1 | Rel-18 | Correction on SI Reception in IoT-NTN |
R2-2410027
| | RAN2#128 | vivo |
| | | | | LTE_NBIOT_eMTC_NTN |
|
|
|
| 36.331 | 5070 | - | F | 17.10.0 | Rel-17 | Correction on SI Reception in IoT-NTN |
R2-2410026
| | RAN2#128 | vivo |
| | | | | LTE_NBIOT_eMTC_NTN |
|
|
|
| 36.331 | 5069 | 2 | F | 18.3.1 | Rel-18 | Correction to NR Beam Reporting in LTE RRC |
R2-2411016
| agreed | RAN2#128 | Apple, ZTE Corp... |
RP-243230
| approved | RAN#106 | RAN2 | 18.4.0 | NR_newRAT-Core,... |
|
|
|
| 36.331 | 5069 | 1 | F | 18.3.1 | Rel-18 | Correction to NR Beam Reporting in LTE RRC |
R2-2410891
| revised | RAN2#128 | Apple, ZTE Corp... |
| | | | | NR_newRAT-Core |
|
|
|
| 36.331 | 5069 | - | F | 18.3.1 | Rel-18 | Correction to NR Beam Reporting in LTE RRC |
R2-2409946
| revised | RAN2#128 | Apple, ZTE Corp... |
| | | | | NR_newRAT-Core |
|
|
|
| 36.331 | 5068 | 1 | F | 16.17.0 | Rel-16 | Correction on SI Reception in RRC CONNECTED |
R2-2411017
| agreed | RAN2#128 | vivo |
RP-243222
| approved | RAN#106 | RAN2 | 16.18.0 | LTE_eMTC5-Core |
|
|
|
| 36.331 | 5068 | - | F | 16.17.0 | Rel-16 | Minor Corrections on TS36.331 |
R2-2409880
| revised | RAN2#128 | vivo |
| | | | | LTE_eMTC5-Core |
|
|
|
| 36.331 | 5067 | 1 | F | 17.10.0 | Rel-17 | Correction on SI Reception in RRC CONNECTED |
R2-2411018
| agreed | RAN2#128 | vivo |
RP-243224
| approved | RAN#106 | RAN2 | 17.11.0 | LTE_eMTC5-Core,... |
|
|
|
| 36.331 | 5067 | - | A | 17.10.0 | Rel-17 | Minor Corrections on TS36.331 |
R2-2409879
| revised | RAN2#128 | vivo |
| | | | | LTE_eMTC5-Core |
|
|
|
| 36.331 | 5066 | 2 | F | 18.3.1 | Rel-18 | Correction on SI Reception in RRC CONNECTED |
R2-2411204
| agreed | RAN2#128 | vivo |
RP-243228
| approved | RAN#106 | RAN2 | 18.4.0 | LTE_eMTC5-Core,... |
|
|
|
| 36.331 | 5066 | 1 | F | 18.3.1 | Rel-18 | Correction on SI Reception in RRC CONNECTED |
R2-2411019
| revised | RAN2#128 | vivo |
| | | | | LTE_eMTC5-Core,... |
|
|
|
| 36.331 | 5066 | - | A | 18.3.1 | Rel-18 | Minor Corrections on TS36.331 |
R2-2409878
| revised | RAN2#128 | vivo |
| | | | | LTE_eMTC5-Core |
|
|
|
| 36.331 | 5065 | 7 | B | 18.6.0 | Rel-19 | Introduction of LTE TN to NR NTN IDLE mode mobility |
R2-2506535
| agreed | RAN2#131 | CATT |
RP-252793
| approved | RAN#109 | RAN2 | 19.0.0 | LTE_TN_NR_NTN_m... |
|
|
|
| 36.331 | 5065 | 6 | B | 18.6.0 | Rel-19 | Introduction of LTE TN to NR NTN IDLE mode mobility |
R2-2506144
| revised | RAN2#131 | CATT |
| | | | | LTE_TN_NR_NTN_m... |
|
|
|
| 36.331 | 5065 | 5 | B | 18.5.0 | Rel-19 | Introduction of LTE TN to NR NTN IDLE mode mobility |
R2-2504530
| revised | RAN2#130 | CATT |
| | | | | LTE_TN_NR_NTN_m... |
|
|
|
| 36.331 | 5065 | 4 | B | 18.5.0 | Rel-19 | Introduction of LTE TN to NR NTN IDLE mode mobility |
R2-2503463
| withdrawn | RAN2#130 | CATT |
| | | | | LTE_TN_NR_NTN_m... |
|
|
|
| 36.331 | 5065 | 3 | B | 18.4.0 | Rel-19 | Introduction of LTE TN to NR NTN IDLE mode mobility |
R2-2501418
| revised | RAN2#129 | CATT |
| | | | | LTE_TN_NR_NTN_m... |
|
|
|
| 36.331 | 5065 | 2 | B | 18.4.0 | Rel-19 | Introduction of LTE TN to NR NTN IDLE mode mobility |
R2-2500529
| revised | RAN2#129 | CATT |
| | | | | LTE_TN_NR_NTN_m... |
|