|
|
| 36.306 | 1678 | 1 | F | 15.3.0 | Rel-15 | UE capability for eLCID support |
R2-1902459
| agreed | RAN2#105 | Qualcomm Incorp... |
RP-190553
| approved | RAN#83 | RAN2 | 15.4.0 | TEI15, INOBEARR... |
|
|
|
| 36.306 | 1678 | - | F | 15.3.0 | Rel-15 | UE capability for eLCID support |
R2-1900783
| revised | RAN2#105 | Qualcomm Incorp... |
| | | | | TEI15, INOBEARR... |
|
|
|
| 36.306 | 1674 | - | F | 15.3.0 | Rel-15 | Correction to eLCID support |
R2-1900343
| not pursued | RAN2#105 | Nokia, Nokia Sh... |
| | | | | INOBEARRAN-Core |
|
|
|
| 36.306 | 1613 | 1 | B | 15.0.0 | Rel-15 | Introduction of increased number of E-UTRAN data bearers |
R2-1809258
| agreed | RAN2#102 | Ericsson, Samsung |
RP-181254
| approved | RAN#80 | RAN2 | 15.1.0 | INOBEARRAN-Core |
|
|
|
| 36.306 | 1613 | - | B | 15.0.0 | Rel-15 | Introduction of increased number of E-UTRAN data bearers |
R2-1807940
| revised | RAN2#102 | Ericsson, Samsung |
| | | | | INOBEARRAN-Core |
|
|
|
| 36.306 | 1583 | - | B | 15.0.0 | Rel-15 | Introduction of INOBEAR in 36.306 |
R2-1805375
| not treated | RAN2#101-Bis | Ericsson |
| | | | | INOBEARRAN-Core |
|
|
|
| 36.321 | 1421 | - | F | 15.4.0 | Rel-15 | Correction to description of L field in the MAC PDU subheader |
R2-1901215
| withdrawn | RAN2#105 | Huawei, HiSilicon |
| | | | | INOBEARRAN-Core |
|
|
|
| 36.321 | 1286 | 1 | B | 15.1.0 | Rel-15 | Introduction of increased number of E-UTRAN data bearers |
R2-1809259
| agreed | RAN2#102 | Samsung |
RP-181254
| approved | RAN#80 | RAN2 | 15.2.0 | INOBEARRAN-Core |
|
|
|
| 36.321 | 1286 | - | B | 15.1.0 | Rel-15 | Introduction of increased number of E-UTRAN data bearers |
R2-1807941
| revised | RAN2#102 | Samsung |
| | | | | INOBEARRAN-Core |
|
|
|
| 36.321 | 1268 | - | B | 15.1.0 | Rel-15 | CR to 36.321 on introduction of extended LCID field |
R2-1806037
| not treated | RAN2#101-Bis | LG Electronics Inc. |
| | | | | INOBEARRAN-Core |
|
|
|
| 36.321 | 1258 | - | B | 15.1.0 | Rel-15 | LCID space extension |
R2-1805373
| not treated | RAN2#101-Bis | Ericsson |
| | | | | INOBEARRAN-Core |
|
|
|
| 36.321 | 1254 | - | B | 15.1.0 | Rel-15 | Introduction of DRB number extension |
R2-1805119
| not treated | RAN2#101-Bis | ZTE, Sanechips |
| | | | | INOBEARRAN-Core |
|
|
|
| 36.331 | 4071 | - | F | 15.6.0 | Rel-15 | Clarification on inter-node message |
R2-1910535
| agreed | RAN2#107 | Google Inc. |
RP-192196
| approved | RAN#85 | RAN2 | 15.7.0 | INOBEARRAN-Core |
|
|
|
| 36.331 | 3861 | 1 | F | 15.4.0 | Rel-15 | UE capability for eLCID support |
R2-1902458
| agreed | RAN2#105 | Qualcomm Incorp... |
RP-190553
| approved | RAN#83 | RAN2 | 15.5.0 | TEI15, INOBEARR... |
|
|
|
| 36.331 | 3861 | - | F | 15.4.0 | Rel-15 | UE capability for eLCID support |
R2-1900782
| revised | RAN2#105 | Qualcomm Incorp... |
| | | | | TEI15, INOBEARR... |
|
|
|
| 36.331 | 3835 | - | F | 15.4.0 | Rel-15 | Correction to eLCID support |
R2-1900344
| not treated | RAN2#105 | Nokia, Nokia Sh... |
| | | | | INOBEARRAN-Core |
|
|
|
| 36.331 | 3446 | 2 | B | 15.2.2 | Rel-15 | Introduction of increased number of E-UTRAN data bearers |
R2-1813090
| agreed | RAN2#103 | Samsung |
RP-181958
| approved | RAN#81 | RAN2 | 15.3.0 | INOBEARRAN-Core |
|
|
|
| 36.331 | 3446 | 1 | B | 15.1.0 | Rel-15 | Introduction of increased number of E-UTRAN data bearers |
R2-1809260
| revised | RAN2#102 | Samsung |
| | | | | INOBEARRAN-Core |
|
|
|
| 36.331 | 3446 | - | B | 15.1.0 | Rel-15 | Introduction of increased number of E-UTRAN data bearers |
R2-1807942
| revised | RAN2#102 | Samsung |
| | | | | INOBEARRAN-Core |
|
|
|
| 36.331 | 3337 | - | B | 15.1.0 | Rel-15 | Introduction of INOBEAR in 36.331 |
R2-1805374
| not treated | RAN2#101-Bis | Ericsson |
| | | | | INOBEARRAN-Core |
|