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-2004563 | ROHC Handling for DAPS Handover without Key Change | discussion | MediaTek Inc. |
R2-ah-38105 AI: 7.3.2 |
available | [WTS] [JSN] | |||
| R2-2004644 | CR on 36.321 for LTE feMob | CR | vivo | 36.321 16.0.0 CR#1474 catB | LTE_feMob-Core | Rel-16 |
R2-ah-38105 AI: 7.3.2 |
available | [WTS] [JSN] |
| R2-2004645 | CR on 38.321 for NR mobility enhancement | CR | vivo | 38.321 16.0.0 CR#744 catB | NR_Mob_enh-Core | Rel-16 |
R2-ah-38105 AI: 7.3.2 |
available | [WTS] [JSN] |
| R2-2004648 | Handling of the source SRB at DAPS failure | discussion | vivo | LTE_feMob-Core | Rel-16 |
R2-ah-38105 AI: 7.3.2 |
available | [WTS] [JSN] | |
| R2-2004697 | RoHC feedback to source cell after UL transmission switch | discussion | Ericsson | LTE_feMob-Core | Rel-16 |
R2-ah-38105 AI: 7.3.2 |
noted | [WTS] [JSN] | |
| R2-2004698 | RoHC handling during DAPS handover without key change |
discussion revision of R2-2002589 |
Ericsson | NR_Mob_enh-Core | Rel-16 |
R2-ah-38105 AI: 7.3.2 |
available | [WTS] [JSN] | |
| R2-2004699 | Open issues for control plane aspects of DAPS handover | discussion | Ericsson | LTE_feMob-Core | Rel-16 |
R2-ah-38105 AI: 7.3.2 |
noted | [WTS] [JSN] | |
| R2-2004787 | Handling of expiry of DataInactivityTimer for DAPS | discussion | NEC | LTE_feMob-Core | Rel-16 |
R2-ah-38105 AI: 7.3.2 |
available | [WTS] [JSN] | |
| R2-2004788 | Solutions for security issue in case of DAPS without key change | discussion | NEC | LTE_feMob-Core | Rel-16 |
R2-ah-38105 AI: 7.3.2 |
available | [WTS] [JSN] | |
| R2-2004878 | Compromised solutions for ROHC related security issue | discussion | Samsung | LTE_feMob-Core |
R2-ah-38105 AI: 7.3.2 |
noted | [WTS] [JSN] | ||
| R2-2004896 | Discussion on old stored RRC message handling upon DAPS HO failure | discussion | OPPO | NR_Mob_enh-Core | Rel-16 |
R2-ah-38105 AI: 7.3.2 |
available | [WTS] [JSN] | |
| R2-2004916 | Discussion on ROHC handling in DAPS HO | discussion | OPPO | LTE_feMob-Core | Rel-16 |
R2-ah-38105 AI: 7.3.2 |
available | [WTS] [JSN] | |
| R2-2004947 | DAPS handover UP remaining key issues | discussion | Qualcomm India Pvt Ltd | NR_Mob_enh-Core, LTE_feMob-Core | Rel-16 |
R2-ah-38105 AI: 7.3.2 |
available | [WTS] [JSN] | |
| R2-2005056 | Discussion on ROHC handling in DAPS HO without key change | discussion | Huawei, HiSilicon | NR_Mob_enh-Core | Rel-16 |
R2-ah-38105 AI: 7.3.2 |
available | [WTS] [JSN] | |
| R2-2005057 | Discussion on transmitting ROHC IR packets in target during DAPS HO | discussion | Huawei, HiSilicon, Vivo, Oppo, Apple, China Telecom, Samsung, LG Electronics, CATT, CMCC, Mediatek Inc., LG Uplus | LTE_feMob-Core | Rel-16 |
R2-ah-38105 AI: 7.3.2 |
noted | [WTS] [JSN] | |
| R2-2005058 | CR on 38.323 for NR mobility enhancement |
CR revision of R2-2003853 revised to R2-2005758 |
Huawei, HiSilicon, Mediatek Inc., LG Electronics | 38.323 16.0.0 CR#452 catC | LTE_feMob-Core | Rel-16 |
R2-ah-38105 AI: 7.3.2 |
revised | [WTS] [JSN] |
| R2-2005059 | CR on 36.323 for LTE feMob |
CR revision of R2-2003854 revised to R2-2005759 |
Huawei, HiSilicon, Mediatek Inc., LG Electronics | 36.323 16.0.0 CR#2822 catC | LTE_feMob-Core | Rel-16 |
R2-ah-38105 AI: 7.3.2 |
revised | [WTS] [JSN] |
| R2-2005060 | Discussion on DAPS CP remaining issue | discussion | Huawei, HiSilicon | LTE_feMob-Core | Rel-16 |
R2-ah-38105 AI: 7.3.2 |
available | [WTS] [JSN] | |
| R2-2005161 | Target cell’s ROHC behaviour for DAPS handover | discussion | Nokia, Nokia Shanghai Bell, Ericsson, Intel Corporation, NEC | LTE_feMob-Core | Rel-16 |
R2-ah-38105 AI: 7.3.2 |
noted | [WTS] [JSN] | |
| R2-2005448 | Discussion of remaining issues for DAPS HO | discussion | CMCC | LTE_feMob-Core | Rel-16 |
R2-ah-38105 AI: 7.3.2 |
available | [WTS] [JSN] | |
| R2-2005497 | Handling of RLC for SRBs | discussion | LG Electronics Inc. | NR_Mob_enh-Core, LTE_feMob-Core |
R2-ah-38105 AI: 7.3.2 |
available | [WTS] [JSN] | ||
| R2-2005500 | ROHC handling for DAPS HO without security key change | discussion | LG Electronics Inc. | NR_Mob_enh-Core, LTE_feMob-Core |
R2-ah-38105 AI: 7.3.2 |
available | [WTS] [JSN] | ||
| R2-2005513 | Remaining issues on fallback from DAPS handover failure | discussion | SHARP Corporation | LTE_feMob-Core | Rel-16 |
R2-ah-38105 AI: 7.3.2 |
available | [WTS] [JSN] | |
| R2-2005753 | Summary of discussion [208] on DAPS UP | discussion | Huawei | NR_Mob_enh-Core, LTE_feMob-Core | Rel-16 |
R2-ah-38105 AI: 7.3.2 |
withdrawn | [WTS] [JSN] | |
| R2-2005758 | CR on 38.323 for NR mobility enhancement |
CR revision of R2-2005058 |
Huawei, HiSilicon, Mediatek Inc., LG Electronics, Nokia, Nokia Shanghai-Bell | 38.323 16.0.0 CR#453 catC | LTE_feMob-Core, NR_Mob_enh-Core | Rel-16 |
R2-ah-38105 AI: 7.3.2 |
agreed | [WTS] [JSN] |
| R2-2005759 | CR on 36.323 for LTE feMob |
CR revision of R2-2005059 |
Huawei, HiSilicon, Mediatek Inc., LG Electronics, Nokia, Nokia Shanghai Bell | 36.323 16.0.0 CR#2823 catC | LTE_feMob-Core | Rel-16 |
R2-ah-38105 AI: 7.3.2 |
agreed | [WTS] [JSN] |
| R2-2005760 | CR on 38.321 for NR mobility enhancement |
CR revision of R2-2003855 |
vivo | 38.321 16.0.0 CR#7441 catB | NR_Mob_enh-Core | Rel-16 |
R2-ah-38105 AI: 7.3.2 |
agreed | [WTS] [JSN] |
| R2-2005761 | CR on 36.321 for even further mobility enhancement in E-UTRAN |
CR revision of R2-2003856 |
vivo | 36.321 16.0.0 CR#14741 catB | LTE_feMob-Core | Rel-16 |
R2-ah-38105 AI: 7.3.2 |
agreed | [WTS] [JSN] |
28 documents (0.35534596443176 seconds)