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-1905547 | Remaining issues in Fast MCG Recovery | discussion | Qualcomm Incorporated | LTE_NR_DC_CA_enh-Core |
R2-106 AI: 11.10.5 |
not treated | [WTS] [JSN] | ||
| R2-1905548 | Discussion on handling of error scenarios related to fast MCG recovery |
discussion revision of R2-1903068 |
Qualcomm Incorporated | LTE_NR_DC_CA_enh-Core | Rel-16 |
R2-106 AI: 11.10.5 |
not treated | [WTS] [JSN] | |
| R2-1905549 | Discussion on PDCP out of delivery issue in Fast MCG recovery | discussion | Qualcomm Incorporated | LTE_NR_DC_CA_enh-Core |
R2-106 AI: 11.10.5 |
withdrawn | [WTS] [JSN] | ||
| R2-1905590 | Fast MCG recovery for MR-DC enhancement | discussion | OPPO | LTE_NR_DC_CA_enh-Core | Rel-16 |
R2-106 AI: 11.10.5 |
not treated | [WTS] [JSN] | |
| R2-1905826 | Additional use cases for MCG fast recovery | discussion | vivo |
R2-106 AI: 11.10.5 |
noted | [WTS] [JSN] | |||
| R2-1905827 | Remaining issues on MCG fast recovery |
discussion revision of R2-1903342 |
vivo |
R2-106 AI: 11.10.5 |
not treated | [WTS] [JSN] | |||
| R2-1905828 | Discussion on the MCG failure via Scell |
discussion revision of R2-1903341 revised to R2-1909204 |
vivo |
R2-106 AI: 11.10.5 |
not treated | [WTS] [JSN] | |||
| R2-1905890 | Consideration on MCG failure recovery | discussion | SHARP Corporation | LTE_NR_DC_CA_enh-Core | Rel-16 |
R2-106 AI: 11.10.5 |
not treated | [WTS] [JSN] | |
| R2-1905986 | SRB primary path handling for MR-DC | discussion | Ericsson, Interdigital | LTE_NR_DC_CA_enh-Core | Rel-16 |
R2-106 AI: 11.10.5 |
not treated | [WTS] [JSN] | |
| R2-1905987 | UL path switch in case of failure in MR-DC (37.340) | discussion | Ericsson | LTE_NR_DC_CA_enh-Core | Rel-16 |
R2-106 AI: 11.10.5 |
withdrawn | [WTS] [JSN] | |
| R2-1905988 | UL path switch in case of failure in (NG)EN-DC (36.331) | discussion | Ericsson | LTE_NR_DC_CA_enh-Core | Rel-16 |
R2-106 AI: 11.10.5 |
withdrawn | [WTS] [JSN] | |
| R2-1905989 | Primary path for SRBs (38.331) | discussion | Ericsson | LTE_NR_DC_CA_enh-Core | Rel-16 |
R2-106 AI: 11.10.5 |
withdrawn | [WTS] [JSN] | |
| R2-1905990 | Fast MCG recovery in MR-DC | discussion | Ericsson | LTE_NR_DC_CA_enh-Core | Rel-16 |
R2-106 AI: 11.10.5 |
not treated | [WTS] [JSN] | |
| R2-1905991 | Fast MCG recovery in NR-DC and NE-DC (38.331) | discussion | Ericsson | LTE_NR_DC_CA_enh-Core | Rel-16 |
R2-106 AI: 11.10.5 |
withdrawn | [WTS] [JSN] | |
| R2-1905992 | Fast MCG recovery in (NG)EN-DC (36.331) | discussion | Ericsson | LTE_NR_DC_CA_enh-Core | Rel-16 |
R2-106 AI: 11.10.5 |
withdrawn | [WTS] [JSN] | |
| R2-1905993 | Fast MCG recovery via SUL | discussion | Ericsson | LTE_NR_DC_CA_enh-Core | Rel-16 |
R2-106 AI: 11.10.5 |
not treated | [WTS] [JSN] | |
| R2-1905994 | Fast MCG recovery via SUL (38.331) | discussion | Ericsson | LTE_NR_DC_CA_enh-Core | Rel-16 |
R2-106 AI: 11.10.5 |
withdrawn | [WTS] [JSN] | |
| R2-1905995 | Fast MCG recovery via SRB3 | discussion | Ericsson | LTE_NR_DC_CA_enh-Core | Rel-16 |
R2-106 AI: 11.10.5 |
not treated | [WTS] [JSN] | |
| R2-1905996 | PCell failure handling in CA duplication | discussion | Ericsson | LTE_NR_DC_CA_enh-Core | Rel-16 |
R2-106 AI: 11.10.5 |
not treated | [WTS] [JSN] | |
| R2-1905997 | Measurements for Scell failure report | discussion | Ericsson | LTE_NR_DC_CA_enh-Core | Rel-16 |
R2-106 AI: 11.10.5 |
not treated | [WTS] [JSN] | |
| R2-1905998 | Measurements for Scell failure report (38.331) | discussion | Ericsson | LTE_NR_DC_CA_enh-Core | Rel-16 |
R2-106 AI: 11.10.5 |
withdrawn | [WTS] [JSN] | |
| R2-1905999 | Fast MCG recovery via SCells of MCG | discussion | Ericsson | LTE_NR_DC_CA_enh-Core | Rel-16 |
R2-106 AI: 11.10.5 |
withdrawn | [WTS] [JSN] | |
| R2-1906000 | Handling of SCG failure when MCG is suspended | discussion | Ericsson | LTE_NR_DC_CA_enh-Core | Rel-16 |
R2-106 AI: 11.10.5 |
withdrawn | [WTS] [JSN] | |
| R2-1906001 | Necessity of timeout timer for fast MCG recovery | discussion | Ericsson | LTE_NR_DC_CA_enh-Core | Rel-16 |
R2-106 AI: 11.10.5 |
not treated | [WTS] [JSN] | |
| R2-1906037 | Fast Recovery with CA |
discussion revised to R2-1909111 |
Nokia, Nokia Shanghai Bell | LTE_NR_DC_CA_enh-Core | Rel-16 |
R2-106 AI: 11.10.5 |
not treated | [WTS] [JSN] | |
| R2-1906038 | Failure Cases |
discussion revised to R2-1909110 |
Nokia, Nokia Shanghai Bell | LTE_NR_DC_CA_enh-Core | Rel-16 |
R2-106 AI: 11.10.5 |
not treated | [WTS] [JSN] | |
| R2-1906087 | Fast MCG link recovery | discussion | MediaTek Inc. | LTE_NR_DC_CA_enh-Core |
R2-106 AI: 11.10.5 |
not treated | [WTS] [JSN] | ||
| R2-1906183 | Handling of integrity failure on split SRB |
discussion revision of R2-1900354 revised to R2-1910533 |
Nokia, Nokia shanghai Bell | LTE_NR_DC_CA_enh-Core | Rel-16 |
R2-106 AI: 11.10.5 |
not treated | [WTS] [JSN] | |
| R2-1906391 | Further Aspects of Fast MCG Link Recovery | discussion | InterDigital | LTE_NR_DC_CA_enh-Core | Rel-16 |
R2-106 AI: 11.10.5 |
not treated | [WTS] [JSN] | |
| R2-1906693 | RRC Resume via. SCG |
discussion revised to R2-1909978 |
Nokia, Nokia Shanghai Bell | LTE_NR_DC_CA_enh-Core | Rel-16 |
R2-106 AI: 11.10.5 |
not treated | [WTS] [JSN] | |
| R2-1906788 | Issues on Fast MCG Link Recovery | discussion | Samsung | Rel-16 |
R2-106 AI: 11.10.5 |
not treated | [WTS] [JSN] | ||
| R2-1906789 | Discussion on FailureInformation |
discussion revision of R2-1904917 revised to R2-1911457 |
Samsung | Rel-16 |
R2-106 AI: 11.10.5 |
not treated | [WTS] [JSN] | ||
| R2-1906921 | Fallback mechanisum for fast recovery | discussion | CATT | LTE_NR_DC_CA_enh-Core | Rel-16 |
R2-106 AI: 11.10.5 |
not treated | [WTS] [JSN] | |
| R2-1907103 | MCG fast recovery via SCG | discussion | ZTE Corporation, Sanechips | LTE_NR_DC_CA_enh-Core | Rel-16 |
R2-106 AI: 11.10.5 |
noted | [WTS] [JSN] | |
| R2-1907104 | Discussion on solutions for MCG fast recovery | discussion | ZTE Corporation, Sanechips | LTE_NR_DC_CA_enh-Core | Rel-16 |
R2-106 AI: 11.10.5 |
not treated | [WTS] [JSN] | |
| R2-1907173 | MCG Fast Recovery |
discussion revision of R2-1903612 |
Apple | LTE_NR_DC_CA_enh-Core | Rel-16 |
R2-106 AI: 11.10.5 |
not treated | [WTS] [JSN] | |
| R2-1907213 | Utilization of MCG Failure Recovery via SCG link |
discussion revision of R2-1905058 revised to R2-1911314 |
LG Electronics Inc | LTE_NR_DC_CA_enh-Core | Rel-16 |
R2-106 AI: 11.10.5 |
not treated | [WTS] [JSN] | |
| R2-1907493 | MCG failure recovery via split SRB1 | discussion | Huawei, HiSilicon | LTE_NR_DC_CA_enh-Core | Rel-16 |
R2-106 AI: 11.10.5 |
not treated | [WTS] [JSN] | |
| R2-1907494 | Draft CR on TS 38.331 to support MCG failure recovery via split SRB1 | draftCR | Huawei, HiSilicon | LTE_NR_DC_CA_enh-Core | Rel-16 |
R2-106 AI: 11.10.5 |
not treated | [WTS] [JSN] | |
| R2-1907495 | Draft CR on TS 36.331 to support MCG failure recovery via split SRB1 | draftCR | Huawei, HiSilicon | LTE_NR_DC_CA_enh-Core | Rel-16 |
R2-106 AI: 11.10.5 |
not treated | [WTS] [JSN] | |
| R2-1907496 | Discussion on MCG RLF due to UL problems when both UL and SUL are configured |
discussion revised to R2-1911143 |
Huawei, HiSilicon | LTE_NR_DC_CA_enh-Core | Rel-16 |
R2-106 AI: 11.10.5 |
not treated | [WTS] [JSN] | |
| R2-1907497 | Discussion on MCG failure recovery via SRB3 |
discussion revised to R2-1911144 |
Huawei, HiSilicon | LTE_NR_DC_CA_enh-Core | Rel-16 |
R2-106 AI: 11.10.5 |
not treated | [WTS] [JSN] | |
| R2-1907498 | Draft LS to RAN3 on support of MCG failure recovery via SRB3 |
LS out LS To: RAN3 revised to R2-1911145 |
Huawei, HiSilicon | LTE_NR_DC_CA_enh-Core | Rel-16 |
R2-106 AI: 11.10.5 |
not treated | [WTS] [JSN] | |
| R2-1907499 | DraftCR on 37.340 for support of MCG link fast recovery via SRB3 |
draftCR revised to R2-1911146 |
Huawei, HiSilicon | LTE_NR_DC_CA_enh-Core | Rel-16 |
R2-106 AI: 11.10.5 |
not treated | [WTS] [JSN] | |
| R2-1907500 | Draft CR on TS 38.331 to support MCG failure recovery via SRB3 |
draftCR revised to R2-1911147 |
Huawei, HiSilicon | LTE_NR_DC_CA_enh-Core | Rel-16 |
R2-106 AI: 11.10.5 |
not treated | [WTS] [JSN] | |
| R2-1907501 | Draft CR on TS 36.331 to support MCG failure recovery via SRB3 |
draftCR revised to R2-1911148 |
Huawei, HiSilicon | LTE_NR_DC_CA_enh-Core | Rel-16 |
R2-106 AI: 11.10.5 |
not treated | [WTS] [JSN] | |
| R2-1907502 | Ensuring timely completion of MCG recovery in all cases |
discussion revised to R2-1910946 |
Huawei, HiSilicon | LTE_NR_DC_CA_enh-Core | Rel-16 |
R2-106 AI: 11.10.5 |
not treated | [WTS] [JSN] | |
| R2-1907503 | Draft CR on 36.331 for the timer of fast MCG recovery | draftCR | Huawei, HiSilicon | LTE_NR_DC_CA_enh-Core | Rel-16 |
R2-106 AI: 11.10.5 |
not treated | [WTS] [JSN] | |
| R2-1907504 | Draft CR on 38.331 for the timer of fast MCG recovery | draftCR | Huawei, HiSilicon | LTE_NR_DC_CA_enh-Core | Rel-16 |
R2-106 AI: 11.10.5 |
not treated | [WTS] [JSN] | |
| R2-1907505 | Enabling MN change without releasing SCG link |
discussion revised to R2-1911149 |
Huawei, HiSilicon | LTE_NR_DC_CA_enh-Core | Rel-16 |
R2-106 AI: 11.10.5 |
not treated | [WTS] [JSN] | |
| R2-1907506 | Discussion on PDCP SN issue for MCG failure recovery | discussion | Huawei, HiSilicon | LTE_NR_DC_CA_enh-Core | Rel-16 |
R2-106 AI: 11.10.5 |
noted | [WTS] [JSN] | |
| R2-1907543 | UL path switch in case of failure in MR-DC (37.340) | draftCR | Ericsson | LTE_NR_DC_CA_enh-Core | Rel-16 |
R2-106 AI: 11.10.5 |
not treated | [WTS] [JSN] | |
| R2-1907544 | UL path switch in case of failure in (NG)EN-DC (36.331) | draftCR | Ericsson | LTE_NR_DC_CA_enh-Core | Rel-16 |
R2-106 AI: 11.10.5 |
not treated | [WTS] [JSN] | |
| R2-1907545 | Primary path for SRBs (38.331) | draftCR | Ericsson | LTE_NR_DC_CA_enh-Core | Rel-16 |
R2-106 AI: 11.10.5 |
not treated | [WTS] [JSN] | |
| R2-1907546 | Fast MCG recovery in NR-DC and NE-DC (38.331) | draftCR | Ericsson | LTE_NR_DC_CA_enh-Core | Rel-16 |
R2-106 AI: 11.10.5 |
not treated | [WTS] [JSN] | |
| R2-1907547 | Fast MCG recovery in (NG)EN-DC (36.331) | draftCR | Ericsson | LTE_NR_DC_CA_enh-Core | Rel-16 |
R2-106 AI: 11.10.5 |
not treated | [WTS] [JSN] | |
| R2-1907548 | Fast MCG recovery via SUL (38.331) | draftCR | Ericsson | LTE_NR_DC_CA_enh-Core | Rel-16 |
R2-106 AI: 11.10.5 |
not treated | [WTS] [JSN] | |
| R2-1907549 | Measurements for Scell failure report (38.331) | draftCR | Ericsson | LTE_NR_DC_CA_enh-Core | Rel-16 |
R2-106 AI: 11.10.5 |
not treated | [WTS] [JSN] | |
| R2-1907550 | Handling of SCG failure when MCG is suspended (38.331) | draftCR | Ericsson | LTE_NR_DC_CA_enh-Core | Rel-16 |
R2-106 AI: 11.10.5 |
not treated | [WTS] [JSN] | |
| R2-1907613 | MCG RLF reporting via SCell |
discussion revision of R2-1904658 revised to R2-1910909 |
Samsung Research America | LTE_NR_DC_CA_enh-Core |
R2-106 AI: 11.10.5 |
not treated | [WTS] [JSN] | ||
| R2-1907889 | Applicability of using SCG for fast MCG recovery | discussion | OPPO |
R2-106 AI: 11.10.5 |
not treated | [WTS] [JSN] | |||
| R2-1907988 | PDCP issue in Fast MCG link Recovery | discussion | LG Electronics | LTE_NR_DC_CA_enh-Core | Rel-16 |
R2-106 AI: 11.10.5 |
not treated | [WTS] [JSN] | |
| R2-1908050 | Discussion on MCG failure | discussion | NTT DOCOMO INC. | LTE_NR_DC_CA_enh-Core | Rel-16 |
R2-106 AI: 11.10.5 |
not treated | [WTS] [JSN] | |
| R2-1908054 | Bounded Time for MCG Recovery and MCG Recovery Criteria | discussion | LG Electronics France |
R2-106 AI: 11.10.5 |
not treated | [WTS] [JSN] | |||
| R2-1908055 | Triggering and transport of MCG failure reporting | discussion | LG Electronics France |
R2-106 AI: 11.10.5 |
not treated | [WTS] [JSN] |
65 documents (0.35563492774963 seconds)