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 |
---|---|---|---|---|---|---|---|---|---|
R2-2200542 | Futher discussion on UE initiated SCG fast activation |
discussion revision of R2-2110909 |
Futurewei | LTE_NR_DC_enh2-Core | Rel-17 |
R2-116-bis-e AI: 8.2.2.2 |
available | [WTS] [JSN] | |
R2-2200584 | PHR issues for SCG activation | discussion | Samsung Electronics Polska | LTE_NR_DC_enh2-Core |
R2-116-bis-e AI: 8.2.2.2 |
available | [WTS] [JSN] | ||
R2-2200605 | Activation of deactivated SCG | discussion | ZTE Corporation, Sanechips | LTE_NR_DC_enh2-Core | Rel-17 |
R2-116-bis-e AI: 8.2.2.2 |
available | [WTS] [JSN] | |
R2-2200637 | Discussion on activation of deactivated SCG | discussion | Spreadtrum Communications | Rel-17 |
R2-116-bis-e AI: 8.2.2.2 |
available | [WTS] [JSN] | ||
R2-2200649 | UP details of deactivated SCG activation | discussion | Transsion Holdings | Rel-17 |
R2-116-bis-e AI: 8.2.2.2 |
available | [WTS] [JSN] | ||
R2-2200772 | Discussion on SCG activation | discussion | Lenovo, Motorola Mobility | Rel-17 |
R2-116-bis-e AI: 8.2.2.2 |
available | [WTS] [JSN] | ||
R2-2200882 | Open issues in activation of SCG | discussion | Nokia, Nokia Shanghai Bell | LTE_NR_DC_enh2-Core | Rel-17 |
R2-116-bis-e AI: 8.2.2.2 |
available | [WTS] [JSN] | |
R2-2200895 | Remaining issues on SCG (de)activation | discussion | CMCC | LTE_NR_DC_enh2-Core | Rel-17 |
R2-116-bis-e AI: 8.2.2.2 |
available | [WTS] [JSN] | |
R2-2201060 | Activation of deactivated SCG | discussion | Qualcomm Incorporated | Rel-17 |
R2-116-bis-e AI: 8.2.2.2 |
available | [WTS] [JSN] | ||
R2-2201093 | UE initiated SCG activation | discussion | Huawei, HiSilicon | LTE_NR_DC_enh2-Core | Rel-17 |
R2-116-bis-e AI: 8.2.2.2 |
available | [WTS] [JSN] | |
R2-2201097 | Reply LS on efficient activation/de-activation mechanism for one SCG (R2-2109368/R4-2115440) | discussion | Huawei, HiSilicon | LTE_NR_DC_enh2-Core | Rel-17 |
R2-116-bis-e AI: 8.2.2.2 |
noted | [WTS] [JSN] | |
R2-2201117 | On the non-essentiality of MAC CE based SCG deactivation | discussion | Apple | LTE_NR_DC_enh2-Core |
R2-116-bis-e AI: 8.2.2.2 |
available | [WTS] [JSN] | ||
R2-2201249 | Considerations on Activation of Deactivated SCG | discussion | CATT | LTE_NR_DC_enh2-Core | Rel-17 |
R2-116-bis-e AI: 8.2.2.2 |
available | [WTS] [JSN] | |
R2-2201362 | Discussion on SCG activation and deacitvation | discussion | LG Electronics Inc. | LTE_NR_DC_enh2-Core |
R2-116-bis-e AI: 8.2.2.2 |
available | [WTS] [JSN] | ||
R2-2201393 | Activation of deactivated SCG | discussion | vivo | LTE_NR_DC_enh2-Core |
R2-116-bis-e AI: 8.2.2.2 |
available | [WTS] [JSN] | ||
R2-2201431 | SCG/split bearer handling upon SCG deactivation and SCell state upon SCG activation | discussion | Sharp | LTE_NR_DC_enh2-Core | Rel-17 |
R2-116-bis-e AI: 8.2.2.2 |
available | [WTS] [JSN] | |
R2-2201538 | Conditional reconfiguration execution while SCG is deactivated | discussion | Sharp | LTE_NR_DC_enh2-Core | Rel-17 |
R2-116-bis-e AI: 8.2.2.2 |
available | [WTS] [JSN] | |
R2-2201562 | Efficient SCG activation | discussion | Ericsson | LTE_NR_DC_enh2-Core |
R2-116-bis-e AI: 8.2.2.2 |
noted | [WTS] [JSN] | ||
R2-2201592 | UP details of deactivated SCG activation | discussion | Transsion Holdings |
R2-116-bis-e AI: 8.2.2.2 |
withdrawn | [WTS] [JSN] | |||
R2-2201641 | Activation of SCG | discussion | InterDigital | LTE_NR_DC_enh2-Core | Rel-17 |
R2-116-bis-e AI: 8.2.2.2 |
available | [WTS] [JSN] | |
R2-2201702 | Summary of [AT116bis-e][222][DCCA] Uplink aspects (Huawei) | discussion | Huawei | LTE_NR_DC_enh2-Core | Rel-17 |
R2-116-bis-e AI: 8.2.2.2 |
noted | [WTS] [JSN] |
21 documents (0.30417895317078 seconds)