Please enter the search related information in the fields below. Partial information works, e.g. "SP-21
" in the "tdoc" field lists all TSG SA documents from 2021. Regular expressions mostly work in all fields (e.g. "2[34].501
" in the "Spec" field lists all documents related to 23.501 and 24.501. Capitalization is disregarded, i.e. "3GPP
" gives the same results as "3gpp
".
Download results in JSON format
tdoc | Title | Type / Revs | Source | Spec / CR | S/WID | Release | Meeting | Status | Links |
---|---|---|---|---|---|---|---|---|---|
R4-2009897 | Discussion on dormancy Scell | discussion | MediaTek inc. | LTE_NR_DC_CA_enh-Core | Rel-16 |
R4-96-e AI: 7.5.3.2.2 |
noted | [WTS] [JSN] | |
R4-2010118 | Scell BWP dormancy | discussion | Qualcomm Incorporated | LTE_NR_DC_CA_enh-Core | Rel-16 |
R4-96-e AI: 7.5.3.2.2 |
noted | [WTS] [JSN] | |
R4-2010365 | On SCell dormancy RRM requirements | discussion | vivo | LTE_NR_DC_CA_enh-Core | Rel-16 |
R4-96-e AI: 7.5.3.2.2 |
noted | [WTS] [JSN] | |
R4-2010669 | On SCell Dormancy Switching Delay | discussion | Ericsson | LTE_NR_DC_CA_enh-Core | Rel-16 |
R4-96-e AI: 7.5.3.2.2 |
noted | [WTS] [JSN] | |
R4-2010670 | CR 38.133 SCell dormancy switching of multiple SCells |
CR revised to R4-2012119 |
Ericsson | 38.133 16.4.0 CR#1017 catF | LTE_NR_DC_CA_enh-Core | Rel-16 |
R4-96-e AI: 7.5.3.2.2 |
revised | [WTS] [JSN] |
R4-2010703 | CR on delay requirements for SCell dormancy | CR | OPPO | 38.133 16.4.0 CR#1018 catB | LTE_NR_DC_CA_enh-Core | Rel-16 |
R4-96-e AI: 7.5.3.2.2 |
agreed | [WTS] [JSN] |
R4-2010754 | Discussion on RRM requirements for SCell dormancy | discussion | NEC | LTE_NR_DC_CA_enh-Core | Rel-16 |
R4-96-e AI: 7.5.3.2.2 |
noted | [WTS] [JSN] | |
R4-2010755 | Reply LS on SCell Dormancy |
LS out LS is reply to R1-2005081 LS To: RAN1 |
NEC | LTE_NR_DC_CA_enh-Core | Rel-16 |
R4-96-e AI: 7.5.3.2.2 |
noted | [WTS] [JSN] | |
R4-2011152 | Discussion on SCell dormancy |
LS out LS is reply to R1-2005081 LS To: RAN1 |
Huawei, Hisilicon | LTE_NR_DC_CA_enh-Core | Rel-16 |
R4-96-e AI: 7.5.3.2.2 |
noted | [WTS] [JSN] | |
R4-2011153 | CR on requirements for SCell dormancy |
CR revised to R4-2012120 |
Huawei, Hisilicon | 38.133 16.4.0 CR#1081 catF | LTE_NR_DC_CA_enh-Core | Rel-16 |
R4-96-e AI: 7.5.3.2.2 |
revised | [WTS] [JSN] |
R4-2011154 | CR on interruption requirements for SCell dormancy 36133 |
CR revised to R4-2012121 |
Huawei, Hisilicon | 36.133 16.6.0 CR#6946 catB | LTE_NR_DC_CA_enh-Core | Rel-16 |
R4-96-e AI: 7.5.3.2.2 |
revised | [WTS] [JSN] |
R4-2011319 | Remaining open issues on NR SCell dormancy | discussion | ZTE | LTE_NR_DC_CA_enh-Core | Rel-16 |
R4-96-e AI: 7.5.3.2.2 |
noted | [WTS] [JSN] | |
R4-2012119 | CR 38.133 SCell dormancy switching of multiple SCells |
CR revision of R4-2010670 revised to R4-2012275 |
Ericsson | 38.133 16.4.0 CR#10171 catF | LTE_NR_DC_CA_enh-Core | Rel-16 |
R4-96-e AI: 7.5.3.2.2 |
revised | [WTS] [JSN] |
R4-2012120 | CR on requirements for SCell dormancy |
CR revision of R4-2011153 revised to R4-2012276 |
Huawei, Hisilicon | 38.133 16.4.0 CR#10811 catF | LTE_NR_DC_CA_enh-Core | Rel-16 |
R4-96-e AI: 7.5.3.2.2 |
revised | [WTS] [JSN] |
R4-2012121 | CR on interruption requirements for SCell dormancy 36133 |
CR revision of R4-2011154 revised to R4-2012277 |
Huawei, Hisilicon | 36.133 16.6.0 CR#69461 catB | LTE_NR_DC_CA_enh-Core | Rel-16 |
R4-96-e AI: 7.5.3.2.2 |
revised | [WTS] [JSN] |
R4-2012275 | CR 38.133 SCell dormancy switching of multiple SCells |
CR revision of R4-2012119 |
Ericsson | 38.133 16.4.0 CR#10172 catF | LTE_NR_DC_CA_enh-Core | Rel-16 |
R4-96-e AI: 7.5.3.2.2 |
agreed | [WTS] [JSN] |
R4-2012276 | CR on requirements for SCell dormancy |
CR revision of R4-2012120 |
Huawei, Hisilicon | 38.133 16.4.0 CR#10812 catF | LTE_NR_DC_CA_enh-Core | Rel-16 |
R4-96-e AI: 7.5.3.2.2 |
agreed | [WTS] [JSN] |
R4-2012277 | CR on interruption requirements for SCell dormancy 36133 |
CR revision of R4-2012121 |
Huawei, Hisilicon | 36.133 16.6.0 CR#69462 catB | LTE_NR_DC_CA_enh-Core | Rel-16 |
R4-96-e AI: 7.5.3.2.2 |
agreed | [WTS] [JSN] |
18 documents (0.36272978782654 seconds)