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-1914486 | Consideration on WA or MCG Fast Recovery Upon RLF | discussion | CATT | NR_Mob_enh-Core | Rel-16 |
R2-108 AI: 6.9.3.2 |
available | [WTS] [JSN] | |
| R2-1914639 | Further details on CHO failure handling | discussion | Ericsson | NR_Mob_enh-Core |
R2-108 AI: 6.9.3.2 |
noted | [WTS] [JSN] | ||
| R2-1914700 | Discussion on the timer design for CHO | discussion | vivo | NR_Mob_enh-Core | Rel-16 |
R2-108 AI: 6.9.3.2 |
available | [WTS] [JSN] | |
| R2-1914814 | Discussion on fast RLF recovery when applying CHO and fast MCG recovery | discussion | ZTE Corporation, Sanechips | NR_Mob_enh-Core | Rel-16 |
R2-108 AI: 6.9.3.2 |
available | [WTS] [JSN] | |
| R2-1914984 | CHO execution with multiple candidate cells before HOF |
discussion revision of R2-1912812 |
Futurewei | NR_Mob_enh-Core | Rel-16 |
R2-108 AI: 6.9.3.2 |
available | [WTS] [JSN] | |
| R2-1915009 | Further discussion on RLF recovery in CHO | discussion | SHARP | NR_Mob_enh-Core, LTE_feMob-Core | Rel-16 |
R2-108 AI: 6.9.3.2 |
available | [WTS] [JSN] | |
| R2-1915071 | T312 mechanism for conditional handover | discussion | ITRI | NR_Mob_enh-Core |
R2-108 AI: 6.9.3.2 |
available | [WTS] [JSN] | ||
| R2-1915130 | Remaining issues for failure handling | discussion | Lenovo, Motorola Mobility | Rel-16 |
R2-108 AI: 6.9.3.2 |
noted | [WTS] [JSN] | ||
| R2-1915454 | RLF report for CHO |
discussion revision of R2-1913057 |
NEC | NR_Mob_enh-Core | Rel-16 |
R2-108 AI: 6.9.3.2 |
noted | [WTS] [JSN] | |
| R2-1915497 | On RLF reporting for CHO and DAPS | discussion | Nokia, Nokia Shanghai Bell | NR_Mob_enh-Core | Rel-16 |
R2-108 AI: 6.9.3.2 |
available | [WTS] [JSN] | |
| R2-1915499 | Failure Handling via CHO recovery | discussion | Nokia, Nokia Shanghai Bell | NR_Mob_enh-Core | Rel-16 |
R2-108 AI: 6.9.3.2 |
noted | [WTS] [JSN] | |
| R2-1916052 | Clarification on failure handling using CHO | discussion | Samsung R&D Institute UK |
R2-108 AI: 6.9.3.2 |
withdrawn | [WTS] [JSN] | |||
| R2-1916224 | Fast failure recovery in CHO | discussion | Samsung R&D Institute India |
R2-108 AI: 6.9.3.2 |
available | [WTS] [JSN] | |||
| R2-1916256 | Discussion on the use case of CHO failure recovery | discussion | Beijing Xiaomi Software Tech |
R2-108 AI: 6.9.3.2 |
available | [WTS] [JSN] | |||
| R2-1916276 | The Reporting of CHO failure | discussion | CMCC |
R2-108 AI: 6.9.3.2 |
available | [WTS] [JSN] |
15 documents (0.35949301719666 seconds)