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-2111930 | Further discussion on PUCCH SCell activation_deactivation | discussion | CATT | NR_RRM_enh2-Core | Rel-17 |
R4-100-e AI: 9.10.2.3 |
noted | [WTS] [JSN] | |
R4-2111931 | The requirements for PUCCH SCell activation_deactivation | draftCR | CATT | NR_RRM_enh2-Core | Rel-17 |
R4-100-e AI: 9.10.2.3 |
withdrawn | [WTS] [JSN] | |
R4-2112053 | Discussions on PUCCH SCell Activation/Deactivation delay requirements | discussion | NTT DOCOMO, INC. | NR_RRM_enh2-Core | Rel-17 |
R4-100-e AI: 9.10.2.3 |
noted | [WTS] [JSN] | |
R4-2112126 | Discussion on PUCCH SCell activation and deactivation | discussion | Apple | NR_RRM_enh2-Core | Rel-17 |
R4-100-e AI: 9.10.2.3 |
noted | [WTS] [JSN] | |
R4-2112420 | Further discussion on SCell activation and deactication requirements for PUCCH SCell | discussion | Xiaomi | NR_RRM_enh2-Core | Rel-17 |
R4-100-e AI: 9.10.2.3 |
noted | [WTS] [JSN] | |
R4-2112510 | Discussion on PUCCH SCell activation/deactivation | discussion | CMCC | NR_RRM_enh2-Core |
R4-100-e AI: 9.10.2.3 |
noted | [WTS] [JSN] | ||
R4-2112521 | Discussion on PUCCH SCell activation and deactivation | discussion | MediaTek inc. | NR_RRM_enh2-Core | Rel-17 |
R4-100-e AI: 9.10.2.3 |
noted | [WTS] [JSN] | |
R4-2112638 | Further views on PUCCH SCell activation and deactivation | discussion | vivo | NR_RRM_enh2-Core |
R4-100-e AI: 9.10.2.3 |
noted | [WTS] [JSN] | ||
R4-2112701 | PUCCH SCell activation and deactivation | discussion | Qualcomm Incorporated | NR_RRM_enh2-Core | Rel-17 |
R4-100-e AI: 9.10.2.3 |
noted | [WTS] [JSN] | |
R4-2112876 | Discussion on the activation delay for deactivated PUCCH SCell | discussion | Nokia, Nokia Shanghai Bell | NR_RRM_enh2-Core | Rel-17 |
R4-100-e AI: 9.10.2.3 |
noted | [WTS] [JSN] | |
R4-2113201 | Discussion on PUCCH SCell activation and deactivation | other | ZTE Corporation | NR_RRM_enh2-Core | Rel-17 |
R4-100-e AI: 9.10.2.3 |
noted | [WTS] [JSN] | |
R4-2113277 | RRM requirements for PUCCH SCell ActivationDeactivation | discussion | OPPO | NR_RRM_enh2-Core | Rel-17 |
R4-100-e AI: 9.10.2.3 |
noted | [WTS] [JSN] | |
R4-2114141 | Discussion on requirements for PUCCH SCell activation | discussion | Huawei, Hisilicon | NR_RRM_enh2-Core |
R4-100-e AI: 9.10.2.3 |
noted | [WTS] [JSN] | ||
R4-2114176 | On RRM requirements for SCell (de)activation with PUCCH | discussion | Ericsson | NR_RRM_enh2-Core | Rel-17 |
R4-100-e AI: 9.10.2.3 |
noted | [WTS] [JSN] | |
R4-2115212 | Email discussion summary: [100-e][222] NR_RRM_enh2_3 |
other revised to R4-2115397 |
Moderator (CATT) |
R4-100-e AI: 9.10.2.3 |
revised | [WTS] [JSN] | |||
R4-2115338 | WF on further RRM enhancement for NR and MR-DC - PUCCH SCell activation/deactivation requirements | other | CATT |
R4-100-e AI: 9.10.2.3 |
approved | [WTS] [JSN] | |||
R4-2115339 | LS on beam information of PUCCH Scell in PUCCH SCell activation procedure |
LS out LS To: RAN1, RAN2 LS reply in R2-2109569, R1-2108775, R1-2108944, R1-2109463, R1-2109550, R1-2109587, R1-2112857, R1-2112858 |
Huawei, HiSilicon |
R4-100-e AI: 9.10.2.3 |
approved | [WTS] [JSN] | |||
R4-2115397 | Email discussion summary: [100-e][222] NR_RRM_enh2_3 |
other revision of R4-2115212 |
Moderator (CATT) |
R4-100-e AI: 9.10.2.3 |
noted | [WTS] [JSN] |
18 documents (0.31950402259827 seconds)