|
|
| 36.133 | 5895 | - | F | 15.3.0 | Rel-15 | Correcting UE measurement capability in Inactive state for 36133 |
R4-1810638
| agreed | RAN4#88 | Huawei, HiSilicon |
RP-181904
| approved | RAN#81 | RAN4 | 15.4.0 | LTE_5GCN_connec... |
|
|
|
| 36.133 | 5818 | - | B | 15.2.0 | Rel-15 | Enhancing RRC_IDLE mode measurement capability under LTE-NGCN |
R4-1807376
| noted | RAN4#87 | Huawei, HiSilicon |
| | | | | LTE_5GCN_connec... |
|
|
|
| 36.133 | 5817 | 3 | B | 15.2.0 | Rel-15 | Introducing RRC_INACTIVE mode mobility requirements for 36133 |
R4-1808551
| agreed | RAN4#87 | Huawei, HiSilic... |
RP-181082
| approved | RAN#80 | RAN4 | 15.3.0 | LTE_5GCN_connec... |
|
|
|
| 36.133 | 5817 | 2 | B | 15.2.0 | Rel-15 | Introducing RRC_INACTIVE mode mobility requirements for 36133 |
R4-1808465
| revised | RAN4#87 | Huawei, HiSilic... |
| | | | | LTE_5GCN_connec... |
|
|
|
| 36.133 | 5817 | 1 | B | 15.2.0 | Rel-15 | Introducing RRC_INACTIVE mode mobility requirements for 36133 |
R4-1807991
| revised | RAN4#87 | Huawei, HiSilicon |
| | | | | LTE_5GCN_connec... |
|
|
|
| 36.133 | 5817 | - | B | 15.2.0 | Rel-15 | Introducing RRC_INACTIVE mode mobility requirements for 36133 |
R4-1807375
| revised | RAN4#87 | Huawei, HiSilicon |
| | | | | LTE_5GCN_connec... |
|
|
|
| 36.300 | 1345 | - | F | 16.5.0 | Rel-16 | 36300_(R16)_Clarification on paging in RRC_INACTIVE |
R2-2106322
| | RAN2#114-e | ZTE Corporation... |
| | | | | LTE_5GCN_connec... |
|
|
|
| 36.300 | 1252 | 3 | F | 15.7.0 | Rel-15 | Correction on inter-frequency neighbour cell measurements |
R2-1916304
| agreed | RAN2#108 | Ericsson |
RP-192941
| approved | RAN#86 | RAN2 | 15.8.0 | LTE_5GCN_connec... |
|
|
|
| 36.300 | 1252 | 2 | F | 15.7.0 | Rel-15 | (IPA) Correction on inter-frequency neighbour cell measurements |
R2-1915524
| revised | RAN2#108 | Ericsson |
| | | | | LTE_5GCN_connec... |
|
|
|
| 36.300 | 1252 | 1 | F | 15.7.0 | Rel-15 | Correction on inter-frequency neighbour cell measurements |
R2-1913985
| revised | RAN2#107-Bis | Ericsson |
| | | | | LTE_5GCN_connec... |
|
|
|
| 36.300 | 1252 | - | F | 15.7.0 | Rel-15 | Correction on inter-frequency neighbour cell measurements |
R2-1913315
| revised | RAN2#107-Bis | Ericsson |
| | | | | LTE_5GCN_connec... |
|
|
|
| 36.300 | 1243 | 1 | F | 15.6.0 | Rel-15 | Correction on EPS fallback for LTE-5GC |
R2-1911613
| agreed | RAN2#107 | Huawei, HiSilicon |
RP-192196
| approved | RAN#85 | RAN2 | 15.7.0 | LTE_5GCN_connec... |
|
|
|
| 36.300 | 1243 | - | F | 15.6.0 | Rel-15 | Correction on EPS fallback for voice for LTE-5GC (alt 2) |
R2-1909706
| revised | RAN2#107 | Huawei, HiSilicon |
| | | | | LTE_5GCN_connec... |
|
|
|
| 36.300 | 1242 | - | F | 15.6.0 | Rel-15 | Correction on EPS fallback for voice for LTE-5GC (alt 1) |
R2-1909705
| not treated | RAN2#107 | Huawei, HiSilicon |
| | | | | LTE_5GCN_connec... |
|
|
|
| 36.300 | 1239 | 2 | F | 15.5.0 | Rel-15 | RAN sharing with multiple Cell ID broadcast |
| | | |
RP-191428
| approved | RAN#84 | Ericsson, Huawe... | 15.6.0 | NR_newRAT-Core,... |
|
|
|
| 36.300 | 1239 | 1 | F | 15.5.0 | Rel-15 | RAN sharing with multiple Cell ID broadcast |
R2-1908521
| agreed | RAN2#106 | R3 (Ericsson, H... |
RP-191427
| revised | RAN#84 | TSG WG RAN3 | | NR_newRAT-Core,... |
|
|
|
| 36.300 | 1215 | 1 | F | 15.6.0 | Rel-15 | EPS fallback for voice from LTE/5GC |
R2-1908984
| not treated | RAN2#107 | Ericsson |
| | | | | LTE_5GCN_connec... |
|
|
|
| 36.300 | 1215 | - | F | 15.4.0 | Rel-15 | EPS fallback for voice from LTE/5GC |
R2-1900412
| revised | RAN2#105 | Ericsson |
| | | | | LTE_5GCN_connec... |
|
|
|
| 36.300 | 1209 | 1 | F | 15.3.0 | Rel-15 | Removing NG-RAN specific statements |
R2-1818835
| agreed | RAN2#104 | Ericsson, Nokia... |
RP-182676
| approved | RAN#82 | RAN2 | 15.4.0 | LTE_5GCN_connec... |
|
|
|
| 36.300 | 1200 | 3 | F | 15.3.0 | Rel-15 | Inter-RAT Handover from GERAN or UTRAN to E-UTRA configured with EN-DC (36.300) |
R2-1817314
| agreed | RAN2#104 | Ericsson |
RP-182675
| approved | RAN#82 | RAN2 | 15.4.0 | LTE_5GCN_connec... |
|
|
|
| 36.300 | 1195 | 1 | F | 15.3.0 | Rel-15 | Clarification of features not supported in NB-IoT |
R2-1816383
| agreed | RAN2#104 | Huawei, HiSilicon |
RP-182675
| approved | RAN#82 | RAN2 | 15.4.0 | LTE_5GCN_connec... |
|
|
|
| 36.300 | 1185 | - | F | 15.2.0 | Rel-15 | Stage 2 Changes based on CN type indication for Redirection from ng-eNB to E-UTRA |
R2-1813333
| agreed | RAN2#103 | Qualcomm |
RP-181950
| approved | RAN#81 | RAN2 | 15.3.0 | LTE_5GCN_connec... |
|
|
|
| 36.300 | 1183 | - | F | 15.2.0 | Rel-15 | Correction on AS UP confidentiality in E-UTRA connected to 5GC |
R2-1812729
| not treated | RAN2#103 | Huawei, HiSilicon |
| | | | | LTE_5GCN_connec... |
|
|
|
| 36.300 | 1182 | 6 | F | 15.3.0 | Rel-15 | Corrections on handover for E-UTRA connected to 5GC |
R2-1818619
| agreed | RAN2#104 | Huawei, HiSilicon |
RP-182675
| approved | RAN#82 | RAN2 | 15.4.0 | LTE_5GCN_connec... |
|
|
|
| 36.300 | 1182 | 5 | F | 15.3.0 | Rel-15 | Corrections on handover for E-UTRA connected to 5GC |
R2-1818617
| revised | RAN2#104 | Huawei, HiSilicon |
| | | | | LTE_5GCN_connec... |
|
|
|
| 36.300 | 1182 | 4 | F | 15.3.0 | Rel-15 | Corrections on handover for E-UTRA connected to 5GC |
R2-1818076
| revised | RAN2#104 | Huawei, HiSilicon |
| | | | | LTE_5GCN_connec... |
|
|
|
| 36.300 | 1182 | 3 | F | 15.3.0 | Rel-15 | Corrections on handover for E-UTRA connected to 5GC |
R2-1815616
| revised | RAN2#103-Bis | Huawei, HiSilicon |
| | | | | LTE_5GCN_connec... |
|
|
|
| 36.300 | 1182 | 2 | F | 15.3.0 | Rel-15 | Corrections on handover for E-UTRA connected to 5GC |
R2-1815215
| revised | RAN2#103-Bis | Huawei, HiSilicon |
| | | | | LTE_5GCN_connec... |
|
|
|
| 36.300 | 1182 | 1 | F | 15.2.0 | Rel-15 | CR on intra-EUTRA intra 5GS HO and inter-RAT intra 5GS HO |
R2-1813325
| postponed | RAN2#103 | Huawei, HiSilicon |
| | | | | LTE_5GCN_connec... |
|
|
|
| 36.300 | 1182 | - | F | 15.2.0 | Rel-15 | CR on intra-EUTRA intra 5GS HO and inter-RAT intra 5GS HO |
R2-1812721
| revised | RAN2#103 | Huawei, HiSilicon |
| | | | | LTE_5GCN_connec... |
|
|
|
| 36.300 | 1151 | 1 | B | 15.1.0 | Rel-15 | Introduction of E-UTRA connected to 5GCN |
R2-1808971
| agreed | RAN2#102 | Huawei, HiSilicon |
RP-181223
| approved | RAN#80 | RAN2 | 15.2.0 | LTE_5GCN_connec... |
|
|
|
| 36.300 | 1151 | - | B | 15.1.0 | Rel-15 | Introduction of E-UTRA connected to 5GCN |
R2-1808361
| revised | RAN2#102 | Huawei, HiSilicon |
| | | | | LTE_5GCN_connec... |
|
|
|
| 36.300 | 1065 | - | B | 14.4.0 | Rel-15 | Running 36.300 CR for LTE connectivity to 5GCN (Option2) |
R2-1711108
| withdrawn | RAN2#99-Bis | Huawei |
| | | | | LTE_5GCN_connec... |
|
|
|
| 36.300 | 1064 | - | B | 14.4.0 | Rel-15 | Running 36.300 CR for LTE connectivity to 5GCN (Option1) |
R2-1711107
| withdrawn | RAN2#99-Bis | Huawei |
| | | | | LTE_5GCN_connec... |
|
|
|
| 36.304 | 0840 | 1 | F | 16.6.0 | Rel-17 | Correction on PO determination for UE in inactive state |
R2-2204048
| agreed | RAN2#117-e | ZTE corporation... |
RP-220472
| approved | RAN#95-e | RAN2 | 17.0.0 | TEI17, LTE_5GCN... |
|
|
|
| 36.304 | 0838 | - | A | 16.6.0 | Rel-16 | Addition of missing description on handling of Access Identities when cell is reserved for operator use |
R2-2202221
| agreed | RAN2#117-e | Lenovo, Motorol... |
RP-220472
| approved | RAN#95-e | RAN2 | 16.7.0 | LTE_5GCN_connec... |
|
|
|
| 36.304 | 0837 | - | F | 15.7.0 | Rel-15 | Addition of missing description on handling of Access Identities when cell is reserved for operator use |
R2-2202220
| agreed | RAN2#117-e | Lenovo, Motorol... |
RP-220472
| approved | RAN#95-e | RAN2 | 15.8.0 | LTE_5GCN_connec... |
|
|
|
| 36.304 | 0831 | - | F | 16.4.0 | Rel-16 | Correction on PO determination for UE in inactive state-36.304 |
R2-2107727
| postponed | RAN2#115-e | ZTE corporation... |
| | | | | LTE_5GCN_connec... |
|
|
|
| 36.304 | 0830 | - | F | 16.3.0 | Rel-16 | 36304_(R16)_Correction on paging resources determination-Alt2 |
R2-2106320
| revised | RAN2#114-e | ZTE Corporation... |
| | | | | LTE_5GCN_connec... |
|
|
|
| 36.304 | 0829 | - | F | 16.3.0 | Rel-16 | 36304_(R16)_Correction on paging resources determination-Alt1 |
R2-2106313
| | RAN2#114-e | ZTE Corporation... |
| | | | | LTE_5GCN_connec... |
|
|
|
| 36.304 | 0826 | - | F | 16.3.0 | Rel-16 | Correction on PO determination for UE in inactive state-36.304 |
R2-2105754
| postponed | RAN2#114-e | ZTE corporation... |
| | | | | LTE_5GCN_connec... |
|
|
|
| 36.304 | 0776 | - | F | 15.4.0 | Rel-15 | Clarification on UE Inactive AS context |
R2-1916080
| not treated | RAN2#108 | Google Inc. |
| | | | | LTE_5GCN_connec... |
|
|
|
| 36.304 | 0775 | 1 | F | 15.4.0 | Rel-15 | Correction on handling of stored AS context for UP optimization and RRC_INACTIVE state |
R2-1916309
| agreed | RAN2#108 | Huawei, HiSilicon |
RP-192941
| approved | RAN#86 | RAN2 | 15.5.0 | LTE_5GCN_connec... |
|
|
|
| 36.304 | 0775 | - | F | 15.4.0 | Rel-15 | Correction on RRC_INACTIVE state |
R2-1915838
| revised | RAN2#108 | Huawei, HiSilicon |
| | | | | LTE_5GCN_connec... |
|
|
|
| 36.304 | 0772 | 1 | F | 15.4.0 | Rel-15 | Correction to the handling of stored AS context upon CN type change |
R2-1913986
| revised | RAN2#107-Bis | Huawei, HiSilicon |
| | | | | LTE_5GCN_connec... |
|
|
|
| 36.304 | 0772 | - | F | 15.4.0 | Rel-15 | Correction to the handling of stored AS context upon CN type change |
R2-1912758
| revised | RAN2#107-Bis | Huawei, HiSilicon |
| | | | | LTE_5GCN_connec... |
|
|
|
| 36.304 | 0762 | - | F | 15.1.0 | Rel-15 | TS36.304 CR on [104#23][LTE/5GC] Capture NR agreements |
R2-1819117
| agreed | RAN2#104 | Intel Corporation |
RP-182676
| approved | RAN#82 | RAN2 | 15.2.0 | LTE_5GCN_connec... |
|
|
|
| 36.304 | 0758 | - | F | 15.1.0 | Rel-15 | TS36.304 CR on [103bis#43][LTE/eLTE] Capture NR agreements |
R2-1816728
| agreed | RAN2#104 | Intel Corporation |
RP-182675
| approved | RAN#82 | RAN2 | 15.2.0 | LTE_5GCN_connec... |
|
|
|
| 36.304 | 0752 | 2 | F | 15.1.0 | Rel-15 | Clarification of Qoffsettemp for eLTE in 36.304 |
R2-1819130
| agreed | RAN2#104 | LG Electronics ... |
RP-182676
| approved | RAN#82 | RAN2 | 15.2.0 | LTE_5GCN_connec... |
|
|
|
| 36.304 | 0752 | 1 | F | 15.1.0 | Rel-15 | Clarification of Qoffsettemp for eLTE in 36.304 |
R2-1816440
| revised | RAN2#104 | LG Electronics Inc. |
| | | | | LTE_5GCN_connec... |
|
|
|
| 36.304 | 0752 | - | F | 15.1.0 | Rel-15 | Corrections on Qoffsettemp for eLTE in 36.304 |
R2-1815462
| revised | RAN2#103-Bis | LG Electronics ... |
| | | | | LTE_5GCN_connec... |
|
|
|
| 36.304 | 0749 | - | F | 15.0.0 | Rel-15 | Changes due to CN type indication for Redirection from ng-eNB to E-UTRA |
R2-1813334
| | RAN2#103 | Qualcomm |
| | | | | LTE_5GCN_connec... |
|
|
|
| 36.304 | 0745 | 2 | F | 14.7.0 | Rel-14 | Corrections on Qoffsettemp for LTE in 36.304 |
R2-1816441
| not pursued | RAN2#104 | LG Electronics ... |
| | | | | LTE_5GCN_connec... |
|
|
|
| 36.304 | 0745 | 1 | F | 14.7.0 | Rel-14 | Corrections on Qoffsettemp for LTE in 36.304 |
R2-1815485
| revised | RAN2#103-Bis | LG Electronics ... |
| | | | | LTE_5GCN_connec... |
|
|
|
| 36.304 | 0745 | - | F | 14.6.0 | Rel-14 | Corrections on Qoffsettemp for LTE in 36.304 |
R2-1812890
| revised | RAN2#103 | LG Electronics ... |
| | | | | LTE_5GCN_connec... |
|
|
|
| 36.304 | 0744 | 5 | F | 15.1.0 | Rel-15 | Corrections to TS 36.304 for E-UTRA connected to 5GC |
R2-1819193
| agreed | RAN2#104 | Huawei, HiSilicon |
RP-182676
| approved | RAN#82 | RAN2 | 15.2.0 | LTE_5GCN_connec... |
|
|
|
| 36.304 | 0744 | 4 | F | 15.1.0 | Rel-15 | Corrections to TS 36.304 for E-UTRA connected to 5GC |
R2-1818074
| revised | RAN2#104 | Huawei, HiSilicon |
| | | | | LTE_5GCN_connec... |
|
|
|
| 36.304 | 0744 | 3 | F | 15.1.0 | Rel-15 | Corrections to TS 36.304 for E-UTRA connected to 5GC |
R2-1815972
| revised | RAN2#103-Bis | Huawei, HiSilicon |
| | | | | LTE_5GCN_connec... |
|
|
|
| 36.304 | 0744 | 2 | F | 15.1.0 | Rel-15 | Corrections to TS 36.304 for E-UTRA connected to 5GC |
R2-1815210
| revised | RAN2#103-Bis | Huawei, HiSilicon |
| | | | | LTE_5GCN_connec... |
|
|
|
| 36.304 | 0744 | 1 | F | 15.0.0 | Rel-15 | Corrections to TS 36.304 for E-UTRA connected to 5GC |
R2-1813300
| revised | RAN2#103 | Huawei, HiSilicon |
| | | | | LTE_5GCN_connec... |
|
|
|
| 36.304 | 0744 | - | F | 15.0.0 | Rel-15 | Corrections to TS 36.304 for E-UTRA connected to 5GC |
R2-1812722
| revised | RAN2#103 | Huawei, HiSilicon |
| | | | | LTE_5GCN_connec... |
|
|
|
| 36.304 | 0742 | - | F | 15.0.0 | Rel-15 | Correction on RRC_INACTIVE and camping on E-UTRA connected to 5GC in NB-IoT |
R2-1812200
| agreed | RAN2#103 | Nokia, Nokia Sh... |
RP-181950
| approved | RAN#81 | RAN2 | 15.1.0 | LTE_5GCN_connec... |
|
|
|
| 36.304 | 0739 | - | F | 15.0.0 | Rel-15 | Correction on cell (re)selection in RRC_INACTIVE |
R2-1811863
| not treated | RAN2#103 | Google Inc. |
| | | | | LTE_5GCN_connec... |
|
|
|
| 36.304 | 0731 | 1 | F | 15.0.0 | Rel-15 | CR to 36.304 on CN selection for LTE connected to 5GC |
R2-1812995
| agreed | RAN2#103 | Ericsson |
RP-181950
| approved | RAN#81 | RAN2 | 15.1.0 | LTE_5GCN_connec... |
|
|
|
| 36.304 | 0731 | - | F | 15.0.0 | Rel-15 | CR to 36.304 on CN selection for LTE connected to 5GC |
R2-1811162
| revised | RAN2#103 | Ericsson |
| | | | | LTE_5GCN_connec... |
|
|
|
| 36.304 | 0419 | 1 | B | 14.6.0 | Rel-15 | Introduction of E-UTRA connected to 5GCN |
R2-1808972
| agreed | RAN2#102 | Huawei, HiSilicon |
RP-181223
| approved | RAN#80 | RAN2 | 15.0.0 | LTE_5GCN_connec... |
|
|
|
| 36.304 | 0419 | - | B | 14.6.0 | Rel-15 | Introduction of E-UTRA connected to 5GCN |
R2-1808362
| revised | RAN2#102 | Huawei, HiSilicon |
| | | | | LTE_5GCN_connec... |
|
|
|
| 36.306 | 1839 | 1 | F | 16.7.0 | Rel-17 | Correction on PO determination for UE in inactive state |
R2-2203908
| agreed | RAN2#117-e | ZTE corporation... |
RP-220472
| approved | RAN#95-e | RAN2 | 17.0.0 | TEI17, LTE_5GCN... |
|
|
|
| 36.306 | 1819 | - | F | 16.5.0 | Rel-16 | Correction on PO determination for UE in inactive state-36.306 |
R2-2107728
| postponed | RAN2#115-e | ZTE corporation... |
| | | | | LTE_5GCN_connec... |
|
|
|
| 36.306 | 1815 | - | F | 16.4.0 | Rel-16 | Correction on PO determination for UE in inactive state-36.306 |
R2-2105755
| postponed | RAN2#114-e | ZTE corporation... |
| | | | | LTE_5GCN_connec... |
|
|
|
| 36.306 | 1814 | - | F | 16.4.0 | Rel-16 | Introduction of capabilities for IMS video |
R2-2105679
| | RAN2#114-e | Google Inc. |
| | | | | NR_newRAT-Core,... |
|
|
|
| 36.306 | 1813 | - | F | 15.10.0 | Rel-15 | Indication of unsupported capabilities for IMS video |
R2-2105644
| | RAN2#114-e | Google Inc. |
| | | | | NR_newRAT-Core,... |
|
|
|
| 36.306 | 1809 | - | A | 16.4.0 | Rel-16 | IMS video capabilities |
R2-2104260
| not pursued | RAN2#113-bis-e | Google Inc. |
| | | | | NR_newRAT-Core,... |
|
|
|
| 36.306 | 1808 | - | F | 15.10.0 | Rel-15 | IMS video capabilities |
R2-2104259
| not pursued | RAN2#113-bis-e | Google Inc. |
| | | | | NR_newRAT-Core,... |
|
|
|
| 36.306 | 1711 | 1 | F | 15.5.0 | Rel-15 | Correction on the feature downlink SDAP header |
R2-1911614
| agreed | RAN2#107 | Huawei, HiSilicon |
RP-192196
| approved | RAN#85 | RAN2 | 15.6.0 | LTE_5GCN_connec... |
|
|
|
| 36.306 | 1711 | - | F | 15.5.0 | Rel-15 | Correction on the feature downlink SDAP header |
R2-1909703
| revised | RAN2#107 | Huawei, HiSilicon |
| | | | | LTE_5GCN_connec... |
|
|
|
| 36.306 | 1688 | - | F | 15.4.0 | Rel-15 | Corrections to 36.306 on UE AS capabilities due to UE N1 mode capability |
R2-1904857
| not treated | RAN2#105-Bis | Huawei, HiSilicon |
| | | | | NR_newRAT-Core,... |
|
|
|
| 36.306 | 1684 | - | F | 15.3.0 | Rel-15 | Correction on the UE capability of LTE-5GC |
R2-1901874
| postponed | RAN2#105 | Huawei, HiSilicon |
| | | | | LTE_5GCN_connec... |
|
|
|
| 36.306 | 1660 | 3 | F | 15.2.0 | Rel-15 | TS36.306 CR on UE capabilities for mobility and E-UTRA/5GC |
R2-1818968
| agreed | RAN2#104 | Intel Corporation |
RP-182676
| approved | RAN#82 | RAN2 | 15.3.0 | LTE_5GCN_connec... |
|
|
|
| 36.306 | 1660 | 2 | F | 15.2.0 | Rel-15 | TS36.306 CR on UE capabilities for mobility and E-UTRA/5GC |
R2-1816737
| revised | RAN2#104 | Intel Corporation |
| | | | | LTE_5GCN_connec... |
|
|
|
| 36.306 | 1660 | 1 | F | 15.2.0 | Rel-15 | TS36.306 CR on UE capabilities for mobility and E-UTRA/5GC |
R2-1815794
| revised | RAN2#103-Bis | Intel Corporation |
| | | | | LTE_5GCN_connec... |
|
|
|
| 36.306 | 1660 | - | F | 15.2.0 | Rel-15 | TS36.306 CR on UE capabilities for mobility and E-UTRA/5GC |
R2-1815344
| revised | RAN2#103-Bis | Intel Corporation |
| | | | | LTE_5GCN_connec... |
|
|
|
| 36.306 | 1640 | - | B | 15.1.0 | Rel-15 | Introduction of other UE capabilities of E-UTRA connected to 5GC |
R2-1812719
| not treated | RAN2#103 | Huawei, HiSilicon |
| | | | | LTE_5GCN_connec... |
|
|
|
| 36.306 | 1639 | - | B | 15.1.0 | Rel-15 | Introduction of UE capability of E-UTRA connected to 5GC |
R2-1812716
| not treated | RAN2#103 | Huawei, HiSilicon |
| | | | | LTE_5GCN_connec... |
|
|
|
| 36.306 | 1615 | - | B | 15.0.0 | Rel-15 | Introduction of UE capabilities on E-UTRA connected to 5GCN |
R2-1808365
| | RAN2#102 | Huawei, HiSilicon |
| | | | | LTE_5GCN_connec... |
|
|
|
| 36.306 | 1608 | 2 | B | 15.0.0 | Rel-15 | Introduce reportCGI towards NR neighbour cell |
R2-1809230
| agreed | RAN2#102 | vivo |
RP-181223
| approved | RAN#80 | RAN2 | 15.1.0 | LTE_5GCN_connec... |
|
|
|
| 36.306 | 1608 | 1 | F | 15.0.0 | Rel-15 | Introduce reportCGI towards NR neighbour cell |
R2-1809078
| revised | RAN2#102 | vivo |
| | | | | LTE_5GCN_connec... |
|
|
|
| 36.306 | 1608 | - | F | 15.0.0 | Rel-15 | Introduce reportCGI towards NR neighbour cell |
R2-1807632
| revised | RAN2#102 | vivo |
| | | | | LTE_5GCN_connec... |
|
|
|
| 36.331 | 4759 | 1 | F | 16.7.0 | Rel-17 | Correction on PO determination for UE in inactive state |
R2-2204049
| agreed | RAN2#117-e | ZTE corporation... |
RP-220472
| approved | RAN#95-e | RAN2 | 17.0.0 | TEI17, LTE_5GCN... |
|
|
|
| 36.331 | 4742 | - | A | 16.6.0 | Rel-16 | Correction to nas-Container |
R2-2110942
| not pursued | RAN2#116-e | Sequans Communi... |
| | | | | NR_newRAT-Core,... |
|
|
|
| 36.331 | 4741 | - | F | 15.15.0 | Rel-15 | Correction to nas-Container |
R2-2110939
| not pursued | RAN2#116-e | Sequans Communi... |
| | | | | NR_newRAT-Core,... |
|
|
|
| 36.331 | 4733 | - | A | 16.6.0 | Rel-16 | Correction on reestablishmentInfo(R16) |
R2-2110463
| not pursued | RAN2#116-e | ZTE Corporation... |
| | | | | LTE_5GCN_connec... |
|
|
|
| 36.331 | 4732 | - | F | 15.15.0 | Rel-15 | Correction on reestablishmentInfo |
R2-2110462
| not pursued | RAN2#116-e | ZTE Corporation... |
| | | | | LTE_5GCN_connec... |
|
|
|
| 36.331 | 4712 | - | F | 15.14.0 | Rel-15 | On T330 resetting |
R2-2108312
| revised | RAN2#115-e | Ericsson, ZTE C... |
| | | | | LTE_5GCN_connec... |
|
|
|
| 36.331 | 4695 | - | F | 16.5.0 | Rel-16 | Correction on PO determination for UE in inactive state-36.331 |
R2-2107726
| postponed | RAN2#115-e | ZTE corporation... |
| | | | | LTE_5GCN_connec... |
|
|
|
| 36.331 | 4684 | 2 | A | 16.4.0 | Rel-16 | Minor changes collected by Rapporteur for Rel-16 |
R2-2106510
| agreed | RAN2#114-e | Samsung |
RP-211481
| approved | RAN#92-e | RAN2 | 16.5.0 | SPIA_IDC_LTE-Co... |
|
|
|
| 36.331 | 4684 | 1 | F | 16.4.0 | Rel-16 | Minor changes collected by Rapporteur for Rel-16 |
R2-2106500
| revised | RAN2#114-e | Samsung |
| | | | | SPIA_IDC_LTE-Co... |
|
|
|
| 36.331 | 4684 | - | F | 16.4.0 | Rel-16 | Minor changes collected by Rapporteur for Rel-16 |
R2-2106318
| revised | RAN2#114-e | Samsung |
| | | | | SPIA_IDC_LTE-Co... |
|
|
|
| 36.331 | 4683 | 1 | F | 15.13.0 | Rel-15 | Minor changes collected by Rapporteur for Rel-15 |
R2-2106499
| agreed | RAN2#114-e | Samsung |
RP-211481
| approved | RAN#92-e | RAN2 | 15.14.0 | SPIA_IDC_LTE-Co... |
|
|
|
| 36.331 | 4683 | - | F | 15.13.0 | Rel-15 | Minor changes collected by Rapporteur for Rel-15 |
R2-2106317
| revised | RAN2#114-e | Samsung |
| | | | | SPIA_IDC_LTE-Co... |
|
|
|
| 36.331 | 4682 | - | F | 16.4.0 | Rel-16 | Clarification on paging DRX cycle |
R2-2106307
| revised | RAN2#114-e | ZTE Corporation... |
| | | | | LTE_5GCN_connec... |
|
|
|
| 36.331 | 4664 | - | F | 16.4.0 | Rel-16 | Introduction of capabilities for IMS video |
R2-2105794
| | RAN2#114-e | Google Inc. |
| | | | | NR_newRAT-Core,... |
|
|
|
| 36.331 | 4663 | - | F | 16.4.0 | Rel-16 | Correction on PO determination for UE in inactive state-36.331 |
R2-2105753
| postponed | RAN2#114-e | ZTE corporation... |
| | | | | LTE_5GCN_connec... |
|
|
|
| 36.331 | 4651 | 2 | F | 16.4.0 | Rel-16 | Clarification on the initiation of RNA update |
R2-2106756
| | RAN2#114-e | Huawei, HiSilicon |
| | | | | LTE_5GCN_connec... |
|
|
|
| 36.331 | 4651 | 1 | F | 16.4.0 | Rel-16 | Clarification on the initiation of RNA update |
R2-2105624
| agreed | RAN2#114-e | Huawei, HiSilicon |
RP-211481
| approved | RAN#92-e | RAN2 | 16.5.0 | LTE_5GCN_connec... |
|
|
|
| 36.331 | 4651 | - | F | 16.4.0 | Rel-16 | Clarification on the initiation of RNA update |
R2-2104620
| revised | RAN2#113-bis-e | Huawei, HiSilicon |
| | | | | LTE_5GCN_connec... |
|
|
|
| 36.331 | 4643 | - | A | 16.4.0 | Rel-16 | IMS video capabilities |
R2-2104283
| not pursued | RAN2#113-bis-e | Google Inc. |
| | | | | NR_newRAT-Core,... |
|
|
|
| 36.331 | 4642 | - | F | 15.13.0 | Rel-15 | IMS video capabilities |
R2-2104281
| not pursued | RAN2#113-bis-e | Google Inc. |
| | | | | NR_newRAT-Core,... |
|
|
|
| 36.331 | 4590 | - | F | 16.3.0 | Rel-16 | Correction to logged MDT configuration in full configuration |
R2-2101714
| not pursued | RAN2#113-e | Google Inc. |
| | | | | LTE_5GCN_connec... |
|
|
|
| 36.331 | 4586 | - | F | 16.3.0 | Rel-16 | CR on overheatingAssistanceConfig release |
R2-2101659
| merged | RAN2#113-e | Huawei, HiSilicon |
| | | | | LTE_5GCN_connec... |
|
|
|
| 36.331 | 4585 | - | F | 15.12.0 | Rel-15 | CR on overheatingAssistanceConfig release |
R2-2101658
| merged | RAN2#113-e | Huawei, HiSilicon |
| | | | | LTE_5GCN_connec... |
|
|
|
| 36.331 | 4549 | 1 | F | 16.3.0 | Rel-16 | Minor changes collected by Rapporteur for Rel-16 |
R2-2101995
| agreed | RAN2#113-e | Samsung |
RP-210703
| approved | RAN#91-e | RAN2 | 16.4.0 | NR_newRAT-Core,... |
|
|
|
| 36.331 | 4548 | 1 | F | 15.12.0 | Rel-15 | Minor changes collected by Rapporteur for Rel-15 |
R2-2101994
| agreed | RAN2#113-e | Samsung |
RP-210703
| approved | RAN#91-e | RAN2 | 15.13.0 | NR_newRAT-Core,... |
|
|
|
| 36.331 | 4534 | 1 | A | 16.2.1 | Rel-16 | Clarification for SIBs scheduled in schedulingInfoListExt and posSchedulingInfoList |
R2-2011248
| agreed | RAN2#112-e | Ericsson, Intel... |
RP-202786
| approved | RAN#90-e | RAN2 | 16.3.0 | LTE_D2D_Prox-Co... |
|
|
|
| 36.331 | 4534 | - | A | 16.2.1 | Rel-16 | Clarification for SIBs scheduled in schedulingInfoListExt and posSchedulingInfoList |
R2-2011173
| revised | RAN2#112-e | Ericsson, Intel... |
| | | | | LTE_D2D_Prox-Co... |
|
|
|
| 36.331 | 4533 | 1 | F | 15.11.0 | Rel-15 | Clarification for SIBs scheduled in schedulingInfoListExt and posSchedulingInfoList |
R2-2011247
| agreed | RAN2#112-e | Ericsson, Intel... |
RP-202786
| approved | RAN#90-e | RAN2 | 15.12.0 | LTE_D2D_Prox-Co... |
|
|
|
| 36.331 | 4533 | - | F | 15.11.0 | Rel-15 | Clarification for SIBs scheduled in schedulingInfoListExt and posSchedulingInfoList |
R2-2011172
| revised | RAN2#112-e | Ericsson, Intel... |
| | | | | LTE_D2D_Prox-Co... |
|
|
|
| 36.331 | 4458 | 2 | A | 16.3.0 | Rel-16 | Correction to RRC resume and re-establishment |
R2-2101983
| agreed | RAN2#113-e | Google Inc. |
RP-210700
| approved | RAN#91-e | RAN2 | 16.4.0 | LTE_5GCN_connec... |
|
|
|
| 36.331 | 4458 | 1 | A | 16.3.0 | Rel-16 | Correction to RRC resume and re-establishment |
R2-2101084
| revised | RAN2#113-e | Google Inc. |
| | | | | LTE_5GCN_connec... |
|
|
|
| 36.331 | 4458 | - | A | 16.2.1 | Rel-16 | Correction to RRC resume and re-establishment |
R2-2009258
| revised | RAN2#112-e | Google Inc. |
| | | | | LTE_5GCN_connec... |
|
|
|
| 36.331 | 4457 | 2 | F | 15.12.0 | Rel-15 | Correction to RRC resume and re-establishment |
R2-2101982
| agreed | RAN2#113-e | Google Inc. |
RP-210700
| approved | RAN#91-e | RAN2 | 15.13.0 | LTE_5GCN_connec... |
|
|
|
| 36.331 | 4457 | 1 | F | 15.12.0 | Rel-15 | Correction to RRC resume and re-establishment |
R2-2101081
| revised | RAN2#113-e | Google Inc. |
| | | | | LTE_5GCN_connec... |
|
|
|
| 36.331 | 4457 | - | F | 15.11.0 | Rel-15 | Correction to RRC resume and re-establishment |
R2-2009257
| revised | RAN2#112-e | Google Inc. |
| | | | | LTE_5GCN_connec... |
|
|
|
| 36.331 | 4445 | 1 | C | 16.1.1 | Rel-16 | Modification of SI scheduling for extended SIBs and legacy SIBs in a SI message |
| | | |
RP-201996
| withdrawn | RAN#89-e | Samsung | | LTE_D2D_Prox-Co... |
|
|
|
| 36.331 | 4444 | 1 | C | 15.10.0 | Rel-15 | Modification of SI scheduling for extended SIBs and legacy SIBs in a SI message |
| | | |
RP-201995
| withdrawn | RAN#89-e | Samsung | | LTE_D2D_Prox-Co... |
|
|
|
| 36.331 | 4444 | - | C | 15.10.0 | Rel-15 | Modification of SI scheduling for extended SIBs |
R2-2008667
| endorsed | RAN2#111-e | NTT DOCOMO, INC. |
RP-201939
| approved | RAN#89-e | RAN2 | 15.11.0 | NR_newRAT-Core,... |
|
|
|
| 36.331 | 4417 | - | F | 16.1.1 | Rel-16 | 36.331 CR for eab-Param |
R2-2007944
| postponed | RAN2#111-e | vivo |
| | | | | LTE_5GCN_connec... |
|
|
|
| 36.331 | 4238 | - | F | 15.9.0 | Rel-15 | Correction to shortResumeMAC-I calculation for RRC_INACTIVE |
R2-2002645
| not pursued | RAN2#109-bis-e | Ericsson |
| | | | | LTE_5GCN_connec... |
|
|
|
| 36.331 | 4237 | - | F | 16.0.0 | Rel-16 | Correction to shortResumeMAC-I calculation for RRC_INACTIVE |
R2-2002597
| not pursued | RAN2#109-bis-e | Ericsson |
| | | | | LTE_5GCN_connec... |
|
|
|
| 36.331 | 4226 | - | F | 15.8.0 | Rel-15 | Unsecured UE capability handling |
R2-2001614
| | RAN2#109-e | NTT DOCOMO INC. |
| | | | | LTE_euCA-Core, ... |
|
|
|
| 36.331 | 4224 | - | F | 15.8.0 | Rel-15 | Correction on the content of RRCConnectionReconfigurationComplete message |
R2-2001508
| not pursued | RAN2#109-e | Google Inc. |
| | | | | LTE_5GCN_connec... |
|
|
|
| 36.331 | 4184 | - | F | 15.7.0 | Rel-15 | (IPA)Correction on inter-frequency neighbour cell measurements |
R2-1915368
| withdrawn | RAN2#108 | Ericsson |
| | | | | LTE_5GCN_connec... |
|
|
|
| 36.331 | 4183 | - | F | 15.7.0 | Rel-15 | Restoring SDAP and RoHC contexts during Resumption |
R2-1916529
| agreed | RAN2#108 | Intel |
RP-192941
| approved | RAN#86 | RAN2 | 15.8.0 | LTE_5GCN_connec... |
|
|
|
| 36.331 | 4177 | 2 | F | 15.7.0 | Rel-15 | Clarification on UE Inactive AS context |
R2-1916626
| agreed | RAN2#108 | Google Inc. |
RP-192941
| approved | RAN#86 | RAN2 | 15.8.0 | LTE_5GCN_connec... |
|
|
|
| 36.331 | 4177 | 1 | F | 15.7.0 | Rel-15 | Clarification on UE Inactive AS context |
R2-1916313
| revised | RAN2#108 | Google Inc. |
| | | | | LTE_5GCN_connec... |
|
|
|
| 36.331 | 4177 | - | F | 15.7.0 | Rel-15 | Clarification on UE Inactive AS context |
R2-1916082
| revised | RAN2#108 | Google Inc. |
| | | | | LTE_5GCN_connec... |
|
|
|
| 36.331 | 4172 | 3 | C | 15.8.0 | Rel-16 | Correction on non-3GPP paging |
R2-2001738
| agreed | RAN2#109-e | Huawei, HiSilicon |
RP-200367
| approved | RAN#87-e | RAN2 | 16.0.0 | LTE_5GCN_connec... |
|
|
|
| 36.331 | 4172 | 2 | C | 15.8.0 | Rel-16 | Correction on non-3GPP paging |
R2-2002075
| revised | RAN2#109-e | Huawei, HiSilicon |
| | | | | LTE_5GCN_connec... |
|
|
|
| 36.331 | 4172 | 1 | C | 15.7.0 | Rel-16 | Correction on non-3GPP paging |
R2-1916316
| revised | RAN2#108 | Huawei, HiSilicon |
| | | | | LTE_5GCN_connec... |
|
|
|
| 36.331 | 4172 | - | B | 15.7.0 | Rel-16 | Correction on non-3GPP paging |
R2-1915843
| revised | RAN2#108 | Huawei, HiSilicon |
| | | | | LTE_5GCN_connec... |
|
|
|
| 36.331 | 4150 | - | F | 15.7.0 | Rel-15 | Correction to nonCriticalExtension of RRCConnectionRelease |
R2-1915526
| agreed | RAN2#108 | Huawei, HiSilicon |
RP-192941
| approved | RAN#86 | RAN2 | 15.8.0 | LTE_5GCN_connec... |
|
|
|
| 36.331 | 4139 | - | F | 15.7.0 | Rel-15 | Dummify one of the cellReservedForOperatorUse-CRS-flags |
R2-1914631
| withdrawn | RAN2#108 | Ericsson |
| | | | | LTE_5GCN_connec... |
|
|
|
| 36.331 | 4128 | 2 | F | 15.7.0 | Rel-15 | Correction to field conditions in NE-DC |
R2-1915722
| agreed | RAN2#108 | Ericsson |
RP-192938
| approved | RAN#86 | RAN2 | 15.8.0 | NR_newRAT-Core,... |
|
|
|
| 36.331 | 4120 | 4 | F | 15.7.0 | Rel-15 | Correction to SIB5 acquisition for idle mode measurements |
R2-1916305
| agreed | RAN2#108 | Ericsson |
RP-192941
| approved | RAN#86 | RAN2 | 15.8.0 | LTE_5GCN_connec... |
|
|
|
| 36.331 | 4120 | 3 | F | 15.7.0 | Rel-15 | Correction to SIB5 acquisition for idle mode measurements |
R2-1916303
| revised | RAN2#108 | Ericsson |
| | | | | LTE_5GCN_connec... |
|
|
|
| 36.331 | 4120 | 2 | F | 15.7.0 | Rel-15 | (IPA) Correction to SIB5 acquisition for idle mode measurements |
R2-1915367
| revised | RAN2#108 | Ericsson |
| | | | | LTE_5GCN_connec... |
|
|
|
| 36.331 | 4120 | 1 | F | 15.7.0 | Rel-15 | Correction to SIB5 acquisition for idle mode measurements |
R2-1913984
| revised | RAN2#107-Bis | Ericsson |
| | | | | LTE_5GCN_connec... |
|
|
|
| 36.331 | 4120 | - | F | 15.7.0 | Rel-15 | Correction to SIB5 acquisition for idle mode measurements |
R2-1913314
| revised | RAN2#107-Bis | Ericsson |
| | | | | LTE_5GCN_connec... |
|
|
|
| 36.331 | 4106 | - | B | 15.7.0 | Rel-15 | Correction on paging for LTE-5GC |
R2-1912760
| postponed | RAN2#107-Bis | Huawei, HiSilicon |
| | | | | LTE_5GCN_connec... |
|
|
|
| 36.331 | 4104 | 5 | F | 15.8.0 | Rel-15 | Clarification on default configuration and SRB1 for UP-EDT and RRC_INACTIVE |
R2-2001723
| agreed | RAN2#109-e | Huawei, HiSilicon |
RP-200338
| approved | RAN#87-e | RAN2 | 15.9.0 | LTE_eMTC4-Core,... |
|
|
|
| 36.331 | 4104 | 4 | F | 15.8.0 | Rel-15 | Clarification on default configuration and SRB1 for UP-EDT and RRC_INACTIVE |
R2-2000636
| revised | RAN2#109-e | Huawei, HiSilicon |
| | | | | LTE_eMTC4-Core,... |
|
|
|
| 36.331 | 4099 | 2 | F | 15.8.0 | Rel-16 | NAS handling error of nas-Container for security key derivation |
R2-2002105
| agreed | RAN2#109-e | Intel |
RP-200358
| approved | RAN#87-e | RAN2 | 16.0.0 | TEI16, NR_newRA... |
|
|
|
| 36.331 | 4092 | 1 | F | 15.6.0 | Rel-15 | Correction on stop condition of T380 |
R2-1911615
| agreed | RAN2#107 | LG Electronics Inc. |
RP-192196
| approved | RAN#85 | RAN2 | 15.7.0 | LTE_5GCN_connec... |
|
|
|
| 36.331 | 4092 | - | F | 15.6.0 | Rel-15 | Correction on stop condition of T380 |
R2-1911287
| revised | RAN2#107 | LG Electronics Inc. |
| | | | | LTE_5GCN_connec... |
|
|
|
| 36.331 | 4091 | 1 | F | 15.6.0 | Rel-15 | Correction on RRC connection release indication after handover |
R2-1911876
| agreed | RAN2#107 | Google Inc. |
RP-192196
| approved | RAN#85 | RAN2 | 15.7.0 | LTE_5GCN_connec... |
|
|
|
| 36.331 | 4091 | - | F | 15.6.0 | Rel-15 | Correction on RRC connection release indication after handover |
R2-1911281
| revised | RAN2#107 | Google Inc. |
| | | | | LTE_5GCN_connec... |
|
|
|
| 36.331 | 4073 | - | F | 15.6.0 | Rel-15 | Correction to ROHC handling |
R2-1910546
| agreed | RAN2#107 | Google Inc. |
RP-192196
| approved | RAN#85 | RAN2 | 15.7.0 | LTE_5GCN_connec... |
|
|
|
| 36.331 | 4053 | - | F | 15.6.0 | Rel-15 | Correction on Paging message for LTE-5GC |
R2-1909707
| not pursued | RAN2#107 | Huawei, HiSilicon |
| | | | | LTE_5GCN_connec... |
|
|
|
| 36.331 | 4044 | - | F | 15.6.0 | Rel-15 | PDU session release indication to upper layers during Full Configuration in eLTE |
R2-1909410
| agreed | RAN2#107 | Intel Corporation |
RP-192196
| approved | RAN#85 | RAN2 | 15.7.0 | LTE_5GCN_connec... |
|
|
|
| 36.331 | 4043 | - | F | 15.6.0 | Rel-15 | Support of Idle mode measurement in E-UTRA/5GC |
R2-1909405
| agreed | RAN2#107 | Intel Corporation |
RP-192196
| approved | RAN#85 | RAN2 | 15.7.0 | LTE_5GCN_connec... |
|
|
|
| 36.331 | 4042 | 2 | F | 15.6.0 | Rel-15 | Intra-E-UTRA inter-system HO |
R2-1911810
| agreed | RAN2#107 | Intel Corporati... |
RP-192196
| approved | RAN#85 | RAN2 | 15.7.0 | LTE_5GCN_connec... |
|
|
|
| 36.331 | 4042 | 1 | F | 15.6.0 | Rel-15 | Intra-E-UTRA inter-system handover |
R2-1911509
| revised | RAN2#107 | Intel Corporati... |
| | | | | LTE_5GCN_connec... |
|
|
|
| 36.331 | 4042 | - | F | 15.6.0 | Rel-15 | Intra-E-UTRA inter-system handover |
R2-1909395
| revised | RAN2#107 | Intel Corporati... |
| | | | | LTE_5GCN_connec... |
|
|
|
| 36.331 | 4034 | 1 | F | 15.6.0 | Rel-15 | Clarification to fullConfig in EN-DC |
R2-1911723
| agreed | RAN2#107 | Nokia, Nokia Sh... |
RP-192194
| approved | RAN#85 | RAN2 | 15.7.0 | NR_newRAT-Core,... |
|
|
|
| 36.331 | 4032 | - | F | 15.6.0 | Rel-15 | Correcting algorithm key derivation for LTE/5GC in connection resume |
R2-1908985
| agreed | RAN2#107 | Ericsson |
RP-192196
| approved | RAN#85 | RAN2 | 15.7.0 | LTE_5GCN_connec... |
|
|
|
| 36.331 | 4022 | - | F | 15.5.0 | Rel-15 | Correction on Idle mode measurement in RRC_INACTIVE |
R2-1907992
| agreed | RAN2#106 | LG Electronics Inc. |
RP-191384
| approved | RAN#84 | RAN2 | 15.6.0 | LTE_5GCN_connec... |
|
|
|
| 36.331 | 3998 | 1 | F | 15.5.1 | Rel-15 | Clarification on inter-RAT mobility |
R2-1908131
| agreed | RAN2#106 | Google Inc. |
RP-191381
| approved | RAN#84 | RAN2 | 15.6.0 | NR_newRAT-Core,... |
|
|
|
| 36.331 | 3998 | - | F | 15.5.1 | Rel-15 | Clarification on inter-RAT mobility |
R2-1906807
| revised | RAN2#106 | Google Inc. |
| | | | | NR_newRAT-Core,... |
|
|
|
| 36.331 | 3993 | 2 | F | 15.5.1 | Rel-15 | Correction on inter-RAT cell reselection in RRC_INACTIVE |
R2-1908532
| agreed | RAN2#106 | Google Inc. |
RP-191384
| approved | RAN#84 | RAN2 | 15.6.0 | LTE_5GCN_connec... |
|
|
|
| 36.331 | 3993 | 1 | F | 15.5.1 | Rel-15 | Correction on inter-RAT cell reselection in RRC_INACTIVE |
R2-1908133
| revised | RAN2#106 | Google Inc. |
| | | | | LTE_5GCN_connec... |
|
|
|
| 36.331 | 3993 | - | F | 15.5.1 | Rel-15 | Correction on inter-RAT cell reselection in RRC_INACTIVE |
R2-1906715
| revised | RAN2#106 | Google Inc. |
| | | | | LTE_5GCN_connec... |
|
|
|
| 36.331 | 3992 | 2 | F | 15.5.1 | Rel-15 | Correction on leaving RRC_CONNECTED |
R2-1908531
| agreed | RAN2#106 | Google Inc. |
RP-191384
| approved | RAN#84 | RAN2 | 15.6.0 | LTE_5GCN_connec... |
|
|
|
| 36.331 | 3992 | 1 | F | 15.5.1 | Rel-15 | Correction on leaving RRC_CONNECTED |
R2-1908130
| revised | RAN2#106 | Google Inc. |
| | | | | LTE_5GCN_connec... |
|
|
|
| 36.331 | 3992 | - | F | 15.5.1 | Rel-15 | Correction on leaving RRC_CONNECTED |
R2-1906712
| revised | RAN2#106 | Google Inc. |
| | | | | LTE_5GCN_connec... |
|
|
|
| 36.331 | 3991 | 1 | F | 15.5.1 | Rel-15 | Correction on cell reselection while T302 is running |
R2-1908530
| agreed | RAN2#106 | Google Inc. |
RP-191384
| approved | RAN#84 | RAN2 | 15.6.0 | LTE_5GCN_connec... |
|
|
|
| 36.331 | 3991 | - | F | 15.5.1 | Rel-15 | Correction on cell reselection while T302 is running |
R2-1906699
| revised | RAN2#106 | Google Inc. |
| | | | | LTE_5GCN_connec... |
|
|
|
| 36.331 | 3989 | - | F | 15.5.1 | Rel-15 | Correction to RRC Resume |
R2-1906638
| not treated | RAN2#106 | Google Inc. |
| | | | | LTE_5GCN_connec... |
|
|
|
| 36.331 | 3983 | - | F | 15.5.1 | Rel-15 | Ignore additional fields in RRC Release message before security activation |
R2-1906370
| not pursued | RAN2#106 | Intel Corporation |
| | | | | LTE_5GCN_connec... |
|
|
|
| 36.331 | 3982 | 1 | F | 15.5.1 | Rel-15 | Capture NR agreements in eLTE |
R2-1908132
| agreed | RAN2#106 | Intel Corporation |
RP-191384
| approved | RAN#84 | RAN2 | 15.6.0 | LTE_5GCN_connec... |
|
|
|
| 36.331 | 3982 | - | F | 15.5.1 | Rel-15 | Capture NR agreements in eLTE |
R2-1906359
| revised | RAN2#106 | Intel Corporation |
| | | | | LTE_5GCN_connec... |
|
|
|
| 36.331 | 3981 | - | F | 15.5.1 | Rel-15 | Miscellaneous Corrections for UAC in eLTE |
R2-1906358
| agreed | RAN2#106 | Intel Corporation |
RP-191384
| approved | RAN#84 | RAN2 | 15.6.0 | LTE_5GCN_connec... |
|
|
|
| 36.331 | 3942 | - | F | 15.4.0 | Rel-15 | Capture NR agreements into eLTE |
R2-1902770
| agreed | RAN2#105 | Intel Corporation |
RP-190550
| approved | RAN#83 | RAN2 | 15.5.0 | LTE_5GCN_connec... |
|
|
|
| 36.331 | 3929 | 3 | F | 15.4.0 | Rel-15 | Addition of missing condition in SCell release |
R2-1902741
| agreed | RAN2#105 | LG Electronics |
RP-190550
| approved | RAN#83 | RAN2 | 15.5.0 | TEI13, LTE_5GCN... |
|
|
|
| 36.331 | 3929 | 2 | F | 15.4.0 | Rel-15 | Addition of missing condition in SCell release |
R2-1902714
| revised | RAN2#105 | LG Electronics |
| | | | | TEI13, LTE_5GCN... |
|
|
|
| 36.331 | 3924 | 1 | F | 15.4.0 | Rel-15 | Correction on Idle mode measurement in RRC_INACTIVE |
R2-1902283
| not pursued | RAN2#105 | LG Electronics Inc. |
| | | | | LTE_5GCN_connec... |
|
|
|
| 36.331 | 3924 | - | F | 15.4.0 | Rel-15 | Correction on Idle mode measurement in RRC_INACTIVE |
R2-1902013
| revised | RAN2#105 | LG Electronics Inc. |
| | | | | LTE_5GCN_connec... |
|
|
|
| 36.331 | 3918 | 3 | F | 15.4.0 | Rel-15 | Correction to fallback to the RRC connection establishment |
R2-1902336
| agreed | RAN2#105 | Google Inc. |
RP-190550
| approved | RAN#83 | RAN2 | 15.5.0 | LTE_5GCN_connec... |
|
|
|
| 36.331 | 3918 | 2 | F | 15.4.0 | Rel-15 | Correction to fallback to the RRC connection establishment |
R2-1902323
| revised | RAN2#105 | Google Inc. |
| | | | | LTE_5GCN_connec... |
|
|
|
| 36.331 | 3918 | 1 | F | 15.4.0 | Rel-15 | Correction to fallback to the RRC connection establishment |
R2-1902249
| revised | RAN2#105 | Google Inc. |
| | | | | LTE_5GCN_connec... |
|
|
|
| 36.331 | 3918 | - | F | 15.4.0 | Rel-15 | Correction to fallback to the RRC connection establishment |
R2-1901929
| revised | RAN2#105 | Google Inc. |
| | | | | LTE_5GCN_connec... |
|
|
|
| 36.331 | 3916 | - | F | 15.4.0 | Rel-15 | Corrections on LTE-5GC |
R2-1901875
| not treated | RAN2#105 | Huawei, HiSilicon |
| | | | | LTE_5GCN_connec... |
|
|
|
| 36.331 | 3908 | 2 | F | 15.4.0 | Rel-15 | Clarification on Counter check procedure for eLTE |
R2-1902695
| agreed | RAN2#105 | Samsung Researc... |
RP-190550
| approved | RAN#83 | RAN2 | 15.5.0 | LTE_5GCN_connec... |
|
|
|
| 36.331 | 3908 | 1 | F | 15.4.0 | Rel-15 | Clarification on Counter check procedure for eLTE |
R2-1902649
| revised | RAN2#105 | Samsung Researc... |
| | | | | LTE_5GCN_connec... |
|
|
|
| 36.331 | 3908 | - | F | 15.4.0 | Rel-15 | Clarification on Counter check procedure for eLTE |
R2-1901724
| revised | RAN2#105 | Samsung Researc... |
| | | | | LTE_5GCN_connec... |
|
|
|
| 36.331 | 3895 | 1 | F | 15.4.0 | Rel-15 | Clarificaton on access barring handling |
R2-1902325
| postponed | RAN2#105 | Nokia, Nokia Sh... |
| | | | | LTE_5GCN_connec... |
|
|
|
| 36.331 | 3895 | - | F | 15.4.0 | Rel-15 | Clarificaton on access barring handling |
R2-1901380
| revised | RAN2#105 | Nokia, Nokia Sh... |
| | | | | LTE_5GCN_connec... |
|
|
|
| 36.331 | 3884 | 1 | F | 15.4.0 | Rel-15 | Correction on T309 handling |
R2-1902326
| postponed | RAN2#105 | Google Inc. |
| | | | | LTE_5GCN_connec... |
|
|
|
| 36.331 | 3884 | - | F | 15.4.0 | Rel-15 | Correction on T309 handling |
R2-1901151
| revised | RAN2#105 | Google Inc. |
| | | | | LTE_5GCN_connec... |
|
|
|
| 36.331 | 3878 | 2 | F | 15.4.0 | Rel-15 | Small corrections on TS 36.331 |
R2-1902808
| agreed | RAN2#105 | Google Inc. |
RP-190550
| approved | RAN#83 | RAN2 | 15.5.0 | LTE_5GCN_connec... |
|
|
|
| 36.331 | 3878 | 1 | F | 15.4.0 | Rel-15 | Small corrections on TS 36.331 |
R2-1902324
| revised | RAN2#105 | Google Inc. |
| | | | | LTE_5GCN_connec... |
|