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-2200064 | Discussion on efficient activation/de-activation mechanism for one SCG | discussion | MediaTek (Shenzhen) Inc. | LTE_NR_DC_enh2-Core | Rel-17 |
R4-101-bis-e AI: 6.22.2.2 |
noted | [WTS] [JSN] | |
| R4-2200249 | On efficient activation/de-activation mechanism for one SCG | discussion | Apple | LTE_NR_DC_enh2-Core |
R4-101-bis-e AI: 6.22.2.2 |
noted | [WTS] [JSN] | ||
| R4-2200250 | CR on interruptions due to SCG activation/deactivation | draftCR | Apple | LTE_NR_DC_enh2-Core | Rel-17 |
R4-101-bis-e AI: 6.22.2.2 |
revised | [WTS] [JSN] | |
| R4-2200424 | Efficient activation and deactivation mechanism for one SCG | discussion | Qualcomm Incorporated | LTE_NR_DC_enh2-Core | Rel-17 |
R4-101-bis-e AI: 6.22.2.2 |
noted | [WTS] [JSN] | |
| R4-2200526 | Discussion on efficient activation for one SCG | discussion | Intel Corporation | LTE_NR_DC_enh2 | Rel-17 |
R4-101-bis-e AI: 6.22.2.2 |
noted | [WTS] [JSN] | |
| R4-2200527 | DraftCR on interruptions due to RRM measurements on deactivated SCG | draftCR | Intel Corporation | LTE_NR_DC_enh2 | Rel-17 |
R4-101-bis-e AI: 6.22.2.2 |
revised | [WTS] [JSN] | |
| R4-2200652 | Further discussion on efficient activation deactivation mechanism for one SCG | discussion | vivo | LTE_NR_DC_enh2-Core | Rel-17 |
R4-101-bis-e AI: 6.22.2.2 |
noted | [WTS] [JSN] | |
| R4-2201150 | Discussion on efficient activation/de-activation mechanism for one SCG | discussion | OPPO | LTE_NR_DC_enh2-Core | Rel-17 |
R4-101-bis-e AI: 6.22.2.2 |
noted | [WTS] [JSN] | |
| R4-2201181 | Discussion on efficient activation/de-activation mechanism for one SCG | discussion | Huawei, Hisilicon | LTE_NR_DC_enh2-Core |
R4-101-bis-e AI: 6.22.2.2 |
noted | [WTS] [JSN] | ||
| R4-2201691 | Views on efficient activation/de-activation mechanism for one SCG | discussion | Nokia, Nokia Shanghai Bell | LTE_NR_DC_enh2-Core | Rel-17 |
R4-101-bis-e AI: 6.22.2.2 |
noted | [WTS] [JSN] | |
| R4-2201761 | CR on TS36.133 for interruptions due to SCG activation/deactivation | draftCR | Apple | LTE_NR_DC_enh2-Core | Rel-17 |
R4-101-bis-e AI: 6.22.2.2 |
revised | [WTS] [JSN] | |
| R4-2201887 | On efficient (de)activation of SCG | discussion | Ericsson | LTE_NR_DC_enh2-Core | Rel-17 |
R4-101-bis-e AI: 6.22.2.2 |
noted | [WTS] [JSN] | |
| R4-2201890 | Interruptions requirments due to RLM/BFD on deactivated SCG | draftCR | Ericsson | LTE_NR_DC_enh2-Core | Rel-17 |
R4-101-bis-e AI: 6.22.2.2 |
revised | [WTS] [JSN] |
13 documents (0.34122204780579 seconds)