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-1912132 | Discussion on the Working Assumption Related Issues | discussion | CATT | NR_Mob_enh-Core | Rel-16 |
R2-107 AI: 6.9.3.2 |
not treated | [WTS] [JSN] | |
R2-1912341 | Discussion on the HOF for CHO |
discussion revision of R2-1909538 |
vivo | NR_Mob_enh-Core | Rel-16 |
R2-107 AI: 6.9.3.2 |
withdrawn | [WTS] [JSN] | |
R2-1912454 | Discussion on the timer design for CHO | discussion | vivo | NR_Mob_enh-Core | Rel-16 |
R2-107 AI: 6.9.3.2 |
not treated | [WTS] [JSN] | |
R2-1912741 | Discussion on failure handling for CHO | discussion | Huawei, HiSilicon | NR_Mob_enh-Core, LTE_feMob-Core | Rel-16 |
R2-107 AI: 6.9.3.2 |
not treated | [WTS] [JSN] | |
R2-1912784 | Confirmation of WA for failure handling | discussion | Intel Corporation, InterDigital Inc., China Telecom, OPPO, MediaTek, Lenovo, Motorola Mobility, vivo, Spreadtrum, ITRI, Sharp, Panasonic, Xiaomi, ZTE Corporation, Sanechips, LG Electronics, CATT, NEC, Ericsson, Google Inc., Apple | LTE_feMob-Core, NR_Mob_enh-Core | Rel-16 |
R2-107 AI: 6.9.3.2 |
noted | [WTS] [JSN] | |
R2-1912812 | Access handling for multiple candidate cells in CHO |
discussion revised to R2-1914984 |
Futurewei Technologies | Rel-16 |
R2-107 AI: 6.9.3.2 |
not treated | [WTS] [JSN] | ||
R2-1912972 | Discussion on the use case of CHO failure recovery | discussion | Beijing Xiaomi Software Tech |
R2-107 AI: 6.9.3.2 |
not treated | [WTS] [JSN] | |||
R2-1913000 | Mobility Failure Handling with Conditional Handover Candidates | discussion | MediaTek Inc. |
R2-107 AI: 6.9.3.2 |
not treated | [WTS] [JSN] | |||
R2-1913057 | Failure handling and RLF report for CHO |
discussion revised to R2-1915454 |
NEC | NR_Mob_enh-Core | Rel-16 |
R2-107 AI: 6.9.3.2 |
not treated | [WTS] [JSN] | |
R2-1913089 | Failure handling with CHO candidate |
discussion revision of R2-1910615 |
Lenovo, Motorola Mobility | Rel-16 |
R2-107 AI: 6.9.3.2 |
not treated | [WTS] [JSN] | ||
R2-1913153 | Failure handling in the presence of prepared CHO candidates | discussion | Nokia, Nokia Shanghai Bell | NR_Mob_enh-Core | Rel-16 |
R2-107 AI: 6.9.3.2 |
not treated | [WTS] [JSN] | |
R2-1913484 | Discussion on fast RLF recovery when applying CHO and fast MCG recovery | discussion | ZTE Corporation, Sanechips | NR_Mob_enh-Core | Rel-16 |
R2-107 AI: 6.9.3.2 |
not treated | [WTS] [JSN] | |
R2-1913904 | Discussion on Fast failure recovery alternatives to WA | discussion | Samsung Electronics Polska |
R2-107 AI: 6.9.3.2 |
not treated | [WTS] [JSN] | |||
R2-1913908 | Discussion on Performing CHO instaed of RRE in CHO | discussion | Samsung, Nokia, Nokia Shanghai Bell, Qualcomm Incorporated |
R2-107 AI: 6.9.3.2 |
not treated | [WTS] [JSN] |
14 documents (0.34123802185059 seconds)