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-1914489 | Remaining Issues of CHO Configuration | discussion | CATT | NR_Mob_enh-Core | Rel-16 |
R2-108 AI: 6.9.3.1 |
available | [WTS] [JSN] | |
| R2-1914491 | Discussion on a configuration mismatch between a UE and a target gNB |
discussion revision of R2-1913675 |
KDDI Corporation |
R2-108 AI: 6.9.3.1 |
available | [WTS] [JSN] | |||
| R2-1914513 | Consecutive Conditional Handover |
discussion revision of R2-1912464 |
Apple Inc. | NR_Mob_enh-Core | Rel-16 |
R2-108 AI: 6.9.3.1 |
available | [WTS] [JSN] | |
| R2-1914634 | Remaining open issues for CHO | discussion | Ericsson | NR_Mob_enh-Core |
R2-108 AI: 6.9.3.1 |
noted | [WTS] [JSN] | ||
| R2-1914635 | Handling of a HO command while UE is monitoring CHO | discussion | Ericsson | NR_Mob_enh-Core |
R2-108 AI: 6.9.3.1 |
available | [WTS] [JSN] | ||
| R2-1914636 | Suspend/Release while monitoring CHO in NR | discussion | Ericsson | NR_Mob_enh-Core |
R2-108 AI: 6.9.3.1 |
available | [WTS] [JSN] | ||
| R2-1914638 | TP for 38.331 on CHO | draftCR | Ericsson | NR_Mob_enh-Core | Rel-16 |
R2-108 AI: 6.9.3.1 |
available | [WTS] [JSN] | |
| R2-1914697 | RRC remaining issues for conditional handover configuration |
discussion revision of R2-1912339 |
vivo | NR_Mob_enh-Core | Rel-16 |
R2-108 AI: 6.9.3.1 |
available | [WTS] [JSN] | |
| R2-1914698 | Discussion on CHO release |
discussion revision of R2-1912340 revised to R2-2000375 |
vivo | NR_Mob_enh-Core | Rel-16 |
R2-108 AI: 6.9.3.1 |
available | [WTS] [JSN] | |
| R2-1914699 | Discussion on the number of prepared cells for CHO |
discussion revision of R2-1912342 |
vivo | NR_Mob_enh-Core | Rel-16 |
R2-108 AI: 6.9.3.1 |
available | [WTS] [JSN] | |
| R2-1914702 | Discussion on the DC configuration in conditional handover | discussion | vivo | NR_Mob_enh-Core | Rel-16 |
R2-108 AI: 6.9.3.1 |
available | [WTS] [JSN] | |
| R2-1914812 | Further issues on CHO configuration and execution | discussion | ZTE Corporation, Sanechips | NR_Mob_enh-Core | Rel-16 |
R2-108 AI: 6.9.3.1 |
available | [WTS] [JSN] | |
| R2-1914813 | Discussion on CHO execution condition | discussion | ZTE Corporation, Sanechips | NR_Mob_enh-Core | Rel-16 |
R2-108 AI: 6.9.3.1 |
available | [WTS] [JSN] | |
| R2-1914837 | Handling of CHO configuration and requirement (compliance check) | discussion | Intel Corporation | LTE_feMob-Core, NR_Mob_enh-Core | Rel-16 |
R2-108 AI: 6.9.3.1 |
noted | [WTS] [JSN] | |
| R2-1914886 | On Maximum Number of CHO Candidate Cells and Nodes | discussion | Charter Communications, Inc | NR_Mob_enh, LTE_feMob, NR_Mob_enh-Core, LTE_feMob-Core | Rel-16 |
R2-108 AI: 6.9.3.1 |
withdrawn | [WTS] [JSN] | |
| R2-1914888 | Compliance Check for CHO Target Cell Configurations | discussion | MediaTek Inc. |
R2-108 AI: 6.9.3.1 |
available | [WTS] [JSN] | |||
| R2-1915160 | Compliance check for CHO configuration | discussion | OPPO | NR_Mob_enh-Core | Rel-16 |
R2-108 AI: 6.9.3.1 |
available | [WTS] [JSN] | |
| R2-1915161 | CHO configuration handling upon source configuration update | discussion | OPPO | NR_Mob_enh-Core | Rel-16 |
R2-108 AI: 6.9.3.1 |
available | [WTS] [JSN] | |
| R2-1915217 | Discussion on the maximum number of configured CHO candidate cells | discussion | CMCC | Rel-16 |
R2-108 AI: 6.9.3.1 |
available | [WTS] [JSN] | ||
| R2-1915498 | On when to decode and non-compliance with target cell configuration | discussion | Nokia, Nokia Shanghai Bell | NR_Mob_enh-Core | Rel-16 |
R2-108 AI: 6.9.3.1 |
noted | [WTS] [JSN] | |
| R2-1915736 | CHO configuration/ execution, remaining aspects | discussion | Samsung Telecommunications | NR_Mob_enh-Core | Rel-16 |
R2-108 AI: 6.9.3.1 |
available | [WTS] [JSN] | |
| R2-1915767 | Validity of CHO configurations based on security configuration |
discussion revision of R2-1913668 |
SHARP Corporation | Rel-16 |
R2-108 AI: 6.9.3.1 |
noted | [WTS] [JSN] | ||
| R2-1915844 | Discussion on configuration aspect for CHO |
discussion revision of R2-1912739 revised to R2-2001384 |
Huawei, HiSilicon, China Telecom | NR_Mob_enh-Core, LTE_feMob-Core | Rel-16 |
R2-108 AI: 6.9.3.1 |
available | [WTS] [JSN] | |
| R2-1915845 | Discussion on execution aspect for CHO |
discussion revision of R2-1912740 |
Huawei, HiSilicon | NR_Mob_enh-Core, LTE_feMob-Core | Rel-16 |
R2-108 AI: 6.9.3.1 |
available | [WTS] [JSN] | |
| R2-1915930 | Further Detail on CHO Release | discussion | Apple | NR_Mob_enh-Core | Rel-16 |
R2-108 AI: 6.9.3.1 |
available | [WTS] [JSN] | |
| R2-1915963 | Further details of CHO configuration and execution | discussion | China Telecom |
R2-108 AI: 6.9.3.1 |
available | [WTS] [JSN] | |||
| R2-1916051 | Measurement aspects for CHO |
discussion revision of R2-1912529 |
Samsung R&D Institute UK |
R2-108 AI: 6.9.3.1 |
available | [WTS] [JSN] | |||
| R2-1916053 | Normal handover using conditional handover configuration | discussion | Samsung R&D Institute UK |
R2-108 AI: 6.9.3.1 |
available | [WTS] [JSN] | |||
| R2-1916194 | Discussion on multiple triggering conditions for CHO | discussion | Samsung Electronics Polska | NR_Mob_enh-Core |
R2-108 AI: 6.9.3.1 |
available | [WTS] [JSN] | ||
| R2-1916197 | CHO compliance check and handling | discussion | CMCC | Rel-16 |
R2-108 AI: 6.9.3.1 |
available | [WTS] [JSN] | ||
| R2-1916205 | Measurement ID Swapping Issue for CHO |
discussion revised to R2-2001537 |
LG Electronics Inc. | NR_Mob_enh-Core | Rel-16 |
R2-108 AI: 6.9.3.1 |
available | [WTS] [JSN] | |
| R2-1916206 | Consideration of CHO Release After HO | discussion | LG Electronics Inc. | NR_Mob_enh-Core | Rel-16 |
R2-108 AI: 6.9.3.1 |
available | [WTS] [JSN] | |
| R2-1916209 | Consideration of Compliance Check in CHO |
discussion revision of R2-1913862 |
LG Electronics Inc. | NR_Mob_enh-Core | Rel-16 |
R2-108 AI: 6.9.3.1 |
available | [WTS] [JSN] | |
| R2-1916226 | CHO UE behaviour upon transitioning to RRC_INACTIVE/RRC_IDLE | discussion | Samsung R&D Institute India |
R2-108 AI: 6.9.3.1 |
available | [WTS] [JSN] | |||
| R2-1916274 | On Maximum Number of CHO Candidate Cells and Nodes | discussion | Charter Communications, Inc | NR_Mob_enh, LTE_feMob, NR_Mob_enh-Core, LTE_feMob-Core | Rel-16 |
R2-108 AI: 6.9.3.1 |
available | [WTS] [JSN] |
35 documents (0.36510705947876 seconds)