|
|
| 36.300 | 1334 | - | F | 16.4.0 | Rel-16 | Clarification on manufacturer based UE capability ID |
R2-2101029
| not pursued | RAN2#113-e | Nokia, Nokia Sh... |
| | | | | RACS-RAN-Core |
|
|
|
| 36.300 | 1294 | - | B | 16.1.0 | Rel-16 | Signalling UE capability Identity |
R2-2005871
| agreed | RAN2#110-e | R3 (Huawei) |
RP-201180
| approved | RAN#88-e | RAN2 | 16.2.0 | RACS-RAN-Core |
|
|
|
| 36.300 | 1258 | 1 | B | 16.0.0 | Rel-16 | Introduction of RACS and DL RRC segmentation |
R2-2001687
| agreed | RAN2#109-e | MediaTek Inc., ... |
RP-200351
| approved | RAN#87-e | RAN2 | 16.1.0 | RACS-RAN-Core, TEI16 |
|
|
|
| 36.300 | 1258 | - | B | 16.0.0 | Rel-16 | Introduction of RACS and DL RRC segmentation |
R2-2000421
| revised | RAN2#109-e | MediaTek Inc. |
| | | | | RACS-RAN-Core |
|
|
|
| 36.306 | 1853 | - | C | 17.0.0 | Rel-17 | Introduction of uplink RRC Segmentation capability |
R2-2206781
| agreed | RAN2#118-e | Huawei, HiSilicon |
RP-221758
| approved | RAN#96 | RAN2 | 17.1.0 | RACS-RAN-Core |
|
|
|
| 36.306 | 1852 | - | C | 16.8.0 | Rel-16 | Introduction of uplink RRC Segmentation capability |
R2-2206780
| agreed | RAN2#118-e | Huawei, HiSilicon |
RP-221758
| approved | RAN#96 | RAN2 | 16.9.0 | RACS-RAN-Core |
|
|
|
| 36.306 | 1783 | 1 | F | 16.1.0 | Rel-16 | CR on UE capability of segmentation for UE capability information |
R2-2008206
| agreed | RAN2#111-e | Huawei, HiSilicon |
RP-201931
| approved | RAN#89-e | RAN2 | 16.2.0 | RACS-RAN-Core |
|
|
|
| 36.306 | 1783 | - | F | 16.1.0 | Rel-16 | CR on UE capability of segmentation for UE capability information |
R2-2007807
| revised | RAN2#111-e | Huawei, HiSilicon |
| | | | | RACS-RAN-Core |
|
|
|
| 36.331 | 4915 | 1 | A | 17.3.0 | Rel-17 | Correction on UL RRC segmentation processing delay requirements |
R2-2302198
| agreed | RAN2#121 | Ericsson |
RP-230687
| approved | RAN#99 | RAN2 | 17.4.0 | RACS-RAN-Core |
|
|
|
| 36.331 | 4915 | - | F | 17.3.0 | Rel-17 | Correction on UL RRC segmentation processing delay requirements |
R2-2301407
| revised | RAN2#121 | Ericsson |
| | | | | RACS-RAN-Core |
|
|
|
| 36.331 | 4914 | 1 | F | 16.11.0 | Rel-16 | Correction on UL RRC segmentation processing delay requirements |
R2-2302197
| agreed | RAN2#121 | Ericsson |
RP-230687
| approved | RAN#99 | RAN2 | 16.12.0 | RACS-RAN-Core |
|
|
|
| 36.331 | 4914 | - | F | 16.11.0 | Rel-16 | Correction on UL RRC segmentation processing delay requirements |
R2-2301406
| revised | RAN2#121 | Ericsson |
| | | | | RACS-RAN-Core |
|
|
|
| 36.331 | 4826 | - | C | 17.0.0 | Rel-17 | Introduction of uplink RRC Segmentation capability |
R2-2206779
| agreed | RAN2#118-e | Huawei, HiSilicon |
RP-221758
| approved | RAN#96 | RAN2 | 17.1.0 | RACS-RAN-Core |
|
|
|
| 36.331 | 4825 | - | C | 16.8.0 | Rel-16 | Introduction of uplink RRC Segmentation capability |
R2-2206778
| agreed | RAN2#118-e | Huawei, HiSilicon |
RP-221758
| approved | RAN#96 | RAN2 | 16.9.0 | RACS-RAN-Core |
|
|
|
| 36.331 | 4768 | - | F | 16.7.0 | Rel-16 | Correction on UL message segmentation |
R2-2202991
| not pursued | RAN2#117-e | Samsung |
| | | | | RACS-RAN-Core |
|
|
|
| 36.331 | 4256 | 2 | F | 16.0.0 | Rel-16 | Correction to transfer of UE capabilities at HO for RACS and correction of ASN.1 review issues [N012] [N013] |
R2-2004710
| agreed | RAN2#110-e | MediaTek Inc., ... |
RP-201180
| approved | RAN#88-e | RAN2 | 16.1.0 | RACS-RAN-Core |
|
|
|
| 36.331 | 4256 | 1 | F | 16.0.0 | Rel-16 | Correction to transfer of UE capabilities at HO for RACS (36.331) |
R2-2003906
| revised | RAN2#109-bis-e | MediaTek Inc., ... |
| | | | | RACS-RAN-Core |
|
|
|
| 36.331 | 4256 | - | F | 16.0.0 | Rel-16 | Correction to transfer of UE capabilities at HO for RACS (36.331) |
R2-2003305
| revised | RAN2#109-bis-e | MediaTek Inc., ... |
| | | | | RACS-RAN-Core |
|
|
|
| 36.331 | 4189 | 1 | B | 15.8.0 | Rel-16 | Introduction of UECapabilityInformation segmentation in 36.331 |
R2-2001690
| agreed | RAN2#109-e | MediaTek Inc., ... |
RP-200351
| approved | RAN#87-e | RAN2 | 16.0.0 | RACS-RAN-Core |
|
|
|
| 36.331 | 4189 | - | B | 15.8.0 | Rel-16 | Introduction of UECapabilityInformation segmentation in 36.331 |
R2-2000423
| revised | RAN2#109-e | MediaTek Inc., ... |
| | | | | RACS-RAN-Core |
|
|
|
| 36.413 | 1840 | - | F | 16.7.0 | Rel-16 | (S1AP CR) support the UE Radio Capability for Paging in RACS context |
R3-215336
| revised | RAN3#114-e | Nokia, Nokia Sh... |
| | | | | RACS-RAN-Core |
|
|
|
| 36.413 | 1746 | 5 | B | 16.1.0 | Rel-16 | Signalling UE capability Identity |
R3-204486
| agreed | RAN3#108-e | Huawei, Samsung... |
RP-201078
| approved | RAN#88-e | RAN3 | 16.2.0 | RACS-RAN-Core |
|
|
|
| 36.420 | 0021 | - | B | 15.2.0 | Rel-16 | Introducing RACS |
R3-203425
| | RAN3#108-e | Ericsson |
| | | | | RACS-RAN-Core |
|
|
|
| 36.423 | 1468 | 4 | B | 16.1.0 | Rel-16 | X2AP support for Radio Capability Signaling Optimization |
R3-204487
| agreed | RAN3#108-e | Samsung, CATT, ... |
RP-201078
| approved | RAN#88-e | RAN3 | 16.2.0 | RACS-RAN-Core |
|
|
|
| 37.340 | 0213 | - | B | 16.1.0 | Rel-16 | Supporting of RACS for EN-DC and MR-DC |
R2-2005878
| agreed | RAN2#110-e | R3 (CATT, ZTE, ... |
RP-201180
| approved | RAN#88-e | RAN2 | 16.2.0 | RACS-RAN-Core |
|
|
|
| 38.300 | 0336 | - | F | 16.4.0 | Rel-16 | Clarification on manufacturer based UE capability ID |
R2-2101030
| not pursued | RAN2#113-e | Nokia, Nokia Sh... |
| | | | | RACS-RAN-Core |
|
|
|
| 38.300 | 0317 | 3 | F | 16.3.0 | Rel-16 | Dynamic UMTS Radio Capability impact on SRVCC and RACS |
R2-2011231
| agreed | RAN2#112-e | Huawei, HiSilic... |
RP-202776
| approved | RAN#90-e | RAN2 | 16.4.0 | SRVCC_NR_to_UMT... |
|
|
|
| 38.300 | 0317 | 2 | F | 16.3.0 | Rel-16 | Dynamic UMTS Radio Capability impact on SRVCC and RACS |
R2-2011163
| revised | RAN2#112-e | Huawei, HiSilic... |
| | | | | SRVCC_NR_to_UMT... |
|
|
|
| 38.300 | 0317 | 1 | F | 16.3.0 | Rel-16 | Dynamic UMTS Radio Capability impact on SRVCC and RACS |
R2-2010790
| revised | RAN2#112-e | Huawei, HiSilic... |
| | | | | SRVCC_NR_to_UMT... |
|
|
|
| 38.300 | 0317 | - | F | 16.3.0 | Rel-16 | Dynamic UMTS Radio Capability impact on SRVCC and RACS |
R2-2010259
| revised | RAN2#112-e | Huawei, HiSilic... |
| | | | | SRVCC_NR_to_UMT... |
|
|
|
| 38.300 | 0187 | 1 | B | 16.0.0 | Rel-16 | Introduction of RACS and DL RRC segmentation |
R2-2001688
| agreed | RAN2#109-e | MediaTek Inc., ... |
RP-200351
| approved | RAN#87-e | RAN2 | 16.1.0 | RACS-RAN-Core, TEI16 |
|
|
|
| 38.300 | 0187 | - | B | 16.0.0 | Rel-16 | Introduction of RACS and DL RRC segmentation |
R2-2000422
| revised | RAN2#109-e | MediaTek Inc. |
| | | | | RACS-RAN-Core |
|
|
|
| 38.306 | 0750 | - | C | 17.0.0 | Rel-17 | Introduction of uplink RRC Segmentation capability |
R2-2206785
| agreed | RAN2#118-e | Huawei, HiSilicon |
RP-221756
| approved | RAN#96 | RAN2 | 17.1.0 | RACS-RAN-Core |
|
|
|
| 38.306 | 0749 | - | C | 16.8.0 | Rel-16 | Introduction of uplink RRC Segmentation capability |
R2-2206784
| agreed | RAN2#118-e | Huawei, HiSilicon |
RP-221756
| approved | RAN#96 | RAN2 | 16.9.0 | RACS-RAN-Core |
|
|
|
| 38.306 | 0392 | 1 | F | 16.1.0 | Rel-16 | CR on UE capability of segmentation for UE capability information |
R2-2008205
| merged | RAN2#111-e | Huawei, HiSilicon |
| | | | | RACS-RAN-Core |
|
|
|
| 38.306 | 0392 | - | F | 16.1.0 | Rel-16 | CR on UE capability of segmentation for UE capability information |
R2-2007806
| revised | RAN2#111-e | Huawei, HiSilicon |
| | | | | RACS-RAN-Core |
|
|
|
| 38.331 | 4627 | - | A | 18.0.0 | Rel-18 | Clarification on UE capability segmentation |
R2-2401755
| agreed | RAN2#125 | Huawei, HiSilicon |
RP-240652
| approved | RAN#103 | RAN2 | 18.1.0 | RACS-RAN-Core |
|
|
|
| 38.331 | 4626 | - | A | 17.7.0 | Rel-17 | Clarification on UE capability segmentation |
R2-2401754
| agreed | RAN2#125 | Huawei, HiSilicon |
RP-240652
| approved | RAN#103 | RAN2 | 17.8.0 | RACS-RAN-Core |
|
|
|
| 38.331 | 4625 | - | F | 16.15.1 | Rel-16 | Clarification on UE capability segmentation |
R2-2401753
| agreed | RAN2#125 | Huawei, HiSilicon |
RP-240652
| approved | RAN#103 | RAN2 | 16.16.0 | RACS-RAN-Core |
|
|
|
| 38.331 | 3926 | 1 | F | 17.3.0 | Rel-17 | Correction to security protection requirement for ULDedicatedMessageSegment |
R2-2302236
| agreed | RAN2#121 | Google Inc. |
RP-230687
| approved | RAN#99 | RAN2 | 17.4.0 | RACS-RAN-Core, ... |
|
|
|
| 38.331 | 3926 | - | F | 17.3.0 | Rel-17 | Correction to security protection requirement for ULDedicatedMessageSegment |
R2-2301830
| revised | RAN2#121 | Google Inc. |
| | | | | RACS-RAN-Core, ... |
|
|
|
| 38.331 | 3890 | 2 | A | 17.3.0 | Rel-17 | Correction on UL RRC segmentation processing delay requirements |
R2-2302109
| agreed | RAN2#121 | Ericsson |
RP-230687
| approved | RAN#99 | RAN2 | 17.4.0 | RACS-RAN-Core |
|
|
|
| 38.331 | 3890 | 1 | A | 17.3.0 | Rel-17 | Correction on UL RRC segmentation processing delay requirements |
R2-2302200
| revised | RAN2#121 | Ericsson |
| | | | | RACS-RAN-Core |
|
|
|
| 38.331 | 3890 | - | A | 17.3.0 | Rel-17 | Correction on UL RRC segmentation processing delay requirements |
R2-2301409
| revised | RAN2#121 | Ericsson |
| | | | | RACS-RAN-Core |
|
|
|
| 38.331 | 3889 | 1 | F | 16.11.0 | Rel-16 | Correction on UL RRC segmentation processing delay requirements |
R2-2302199
| agreed | RAN2#121 | Ericsson |
RP-230687
| approved | RAN#99 | RAN2 | 16.12.0 | RACS-RAN-Core |
|
|
|
| 38.331 | 3889 | - | F | 16.11.0 | Rel-16 | Correction on UL RRC segmentation processing delay requirements |
R2-2301408
| revised | RAN2#121 | Ericsson |
| | | | | RACS-RAN-Core |
|
|
|
| 38.331 | 3193 | - | A | 17.0.0 | Rel-17 | Introduction of uplink RRC Segmentation capability |
R2-2206783
| agreed | RAN2#118-e | Huawei, HiSilicon |
RP-221765
| approved | RAN#96 | RAN2 | 17.1.0 | RACS-RAN-Core |
|
|
|
| 38.331 | 3192 | - | C | 16.8.0 | Rel-16 | Introduction of uplink RRC Segmentation capability |
R2-2206782
| agreed | RAN2#118-e | Huawei, HiSilicon |
RP-221765
| approved | RAN#96 | RAN2 | 16.9.0 | RACS-RAN-Core |
|
|
|
| 38.331 | 2920 | - | F | 16.7.0 | Rel-16 | Correction on UL message segmentation |
R2-2202990
| not pursued | RAN2#117-e | Samsung |
| | | | | RACS-RAN-Core |
|
|
|
| 38.331 | 2380 | - | F | 16.3.1 | Rel-16 | Clarification on manufacturer based UE capability ID |
R2-2101031
| not pursued | RAN2#113-e | Nokia, Nokia Sh... |
| | | | | RACS-RAN-Core |
|
|
|
| 38.331 | 1911 | 2 | F | 16.1.0 | Rel-16 | Correction on the UE Capability presence upon SN addition and SN change |
R2-2008204
| agreed | RAN2#111-e | Huawei, HiSilic... |
RP-201931
| approved | RAN#89-e | RAN2 | 16.2.0 | RACS-RAN-Core |
|
|
|
| 38.331 | 1911 | 1 | F | 16.1.0 | Rel-16 | Correction on the UE Capability presence upon SN addition and SN change |
R2-2008104
| revised | RAN2#111-e | Huawei, HiSilic... |
| | | | | RACS-RAN-Core |
|
|
|
| 38.331 | 1911 | - | F | 16.1.0 | Rel-16 | Correction on the UE Capability presence upon SN addition and SN change |
R2-2007805
| revised | RAN2#111-e | Huawei, HiSilicon |
| | | | | RACS-RAN-Core |
|
|
|
| 38.331 | 1553 | 3 | F | 16.0.0 | Rel-16 | Correction to transfer of UE capabilities at HO for RACS and minor ASN.1 correction (38.331) |
R2-2005802
| agreed | RAN2#110-e | ZTE Corporation... |
RP-201180
| approved | RAN#88-e | RAN2 | 16.1.0 | RACS-RAN-Core |
|
|
|
| 38.331 | 1553 | 2 | F | 16.0.0 | Rel-16 | Correction to transfer of UE capabilities at HO for RACS and minor ASN.1 correction (38.331) |
R2-2005539
| revised | RAN2#110-e | ZTE Corporation... |
| | | | | RACS-RAN-Core |
|
|
|
| 38.331 | 1553 | 1 | F | 16.0.0 | Rel-16 | Correction to transfer of UE capabilities at HO for RACS (38.331) |
R2-2003905
| revised | RAN2#109-bis-e | ZTE Corporation... |
| | | | | RACS-RAN-Core |
|
|
|
| 38.331 | 1553 | - | F | 16.0.0 | Rel-16 | Correction to transfer of UE capabilities at HO for RACS (38.331) |
R2-2003290
| revised | RAN2#109-bis-e | ZTE Corporation... |
| | | | | RACS-RAN-Core |
|
|
|
| 38.331 | 1485 | - | B | 15.8.0 | Rel-16 | Introduction of UE radio capability ID in inter-node RRC messages |
R2-2000356
| noted | RAN2#109-e | ZTE Corporation... |
| | | | | RACS-RAN-Core |
|
|
|
| 38.331 | 1441 | 1 | B | 15.8.0 | Rel-16 | Introduction of UECapabilityInformation segmentation in TS38.331 |
R2-2001689
| agreed | RAN2#109-e | ZTE Corporation... |
RP-200351
| approved | RAN#87-e | RAN2 | 16.0.0 | RACS-RAN-Core |
|
|
|
| 38.331 | 1441 | - | B | 15.8.0 | Rel-16 | Introduction of UECapabilityInformation segmentation in TS38.331 |
R2-2000354
| revised | RAN2#109-e | ZTE Corporation... |
| | | | | RACS-RAN-Core |
|
|
|
| 38.331 | 1181 | - | B | 15.6.0 | Rel-16 | Introduction of UECapabilityInformation segmentation in TS38.331 |
R2-1910101
| endorsed | RAN2#107 | ZTE corporation... |
| | | | | RACS-RAN-Core |
|
|
|
| 38.410 | 0025 | 2 | B | 16.1.0 | Rel-16 | Introducing Radio Capability Optimisation (RACS) |
R3-204439
| agreed | RAN3#108-e | Nokia, Nokia Sh... |
RP-201078
| approved | RAN#88-e | RAN3 | 16.2.0 | RACS-RAN-Core |
|
|
|
| 38.413 | 0688 | - | F | 16.7.0 | Rel-16 | (NGAP CR) support the UE Radio Capability for Paging in RACS context |
R3-215335
| revised | RAN3#114-e | Nokia, Nokia Sh... |
| | | | | RACS-RAN-Core |
|
|
|
| 38.413 | 0416 | - | F | 16.2.0 | Rel-16 | NGAP tabular corrections and asn.1 review |
R3-204724
| agreed | RAN3#109-e | Rapporteur (Nokia) |
RP-201554
| reissued | RAN#89-e | RAN3 | 16.3.0 | NR_newRAT-Core,... |
|
|
|
| 38.413 | 0416 | - | F | 16.2.0 | Rel-16 | NGAP tabular corrections and asn.1 review |
R3-204724
| agreed | RAN3#109-e | Rapporteur (Nokia) |
RP-201948
| approved | RAN#89-e | RAN3 | 16.3.0 | NR_newRAT-Core,... |
|
|
|
| 38.413 | 0347 | 6 | B | 16.1.0 | Rel-16 | Introducing Radio Capability Optimisation (RACS) |
R3-204488
| agreed | RAN3#108-e | Ericsson, Qualc... |
RP-201078
| approved | RAN#88-e | RAN3 | 16.2.0 | RACS-RAN-Core |
|
|
|
| 38.413 | 0315 | - | B | 16.0.0 | Rel-16 | Introduction of RACS support |
R3-200288
| | RAN3#107-e | Qualcomm Incorp... |
| | | | | RACS-RAN-Core |
|
|
|
| 38.423 | 0430 | 1 | F | 16.2.0 | Rel-16 | Rapporteur’s corrections to TS 38.423 v16.2.0 |
R3-205691
| agreed | RAN3#109-e | Ericsson |
RP-201556
| reissued | RAN#89-e | RAN3 | 16.3.0 | NR_Mob_enh-Core... |
|
|
|
| 38.423 | 0430 | 1 | F | 16.2.0 | Rel-16 | Rapporteur’s corrections to TS 38.423 v16.2.0 |
R3-205691
| agreed | RAN3#109-e | Ericsson |
RP-201949
| approved | RAN#89-e | RAN3 | 16.3.0 | NR_Mob_enh-Core... |
|
|
|
| 38.423 | 0430 | - | F | 16.2.0 | Rel-16 | Rapporteur’s corrections to TS 38.423 v16.2.0 |
R3-205056
| revised | RAN3#109-e | Ericsson |
| | | | | 5G_V2X_NRSL, NR... |
|
|
|
| 38.423 | 0300 | 5 | B | 16.1.0 | Rel-16 | Supporting of RACS in XnAP |
R3-204489
| agreed | RAN3#108-e | CATT, Samsung, ... |
RP-201078
| approved | RAN#88-e | RAN3 | 16.2.0 | RACS-RAN-Core |
|