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-1914484 | UDC Impacts of DAPS | discussion | CATT | LTE_feMob-Core | Rel-16 |
R2-108 AI: 7.3.2.1.1 |
available | [WTS] [JSN] | |
R2-1914515 | PDCP SN continuity support for RLC UM bearers | discussion | Qualcomm Incorporated |
R2-108 AI: 7.3.2.1.1 |
available | [WTS] [JSN] | |||
R2-1914592 | On Release of source cell in DAPS Handover | discussion | Nokia, Nokia Shanghai Bell | Rel-16 |
R2-108 AI: 7.3.2.1.1 |
noted | [WTS] [JSN] | ||
R2-1914607 | Support the change between normal PDCP entity and DAPS PDCP entity | discussion | Mediatek Inc., Huawei, HiSilicon |
R2-108 AI: 7.3.2.1.1 |
noted | [WTS] [JSN] | |||
R2-1914608 | Draft CR for 38.323 to support the change between normal PDCP and DAPS PDCP | draftCR | Mediatek Inc., Huawei, HiSilicon | NR_Mob_enh-Core | Rel-16 |
R2-108 AI: 7.3.2.1.1 |
available | [WTS] [JSN] | |
R2-1914609 | Draft CR for 36.323 to support the change between normal PDCP and DAPS PDCP | draftCR | Mediatek Inc., Huawei, HiSilicon | LTE_feMob-Core | Rel-16 |
R2-108 AI: 7.3.2.1.1 |
available | [WTS] [JSN] | |
R2-1914610 | RLC UM handling during DAPS HO | discussion | MediaTek Inc., Apple, vivo, OPPO |
R2-108 AI: 7.3.2.1.1 |
noted | [WTS] [JSN] | |||
R2-1914611 | RLC Impacts analysis with DAPS during HO |
discussion revision of R2-1912970 |
Mediatek Inc. | Rel-16 |
R2-108 AI: 7.3.2.1.1 |
noted | [WTS] [JSN] | ||
R2-1914619 | PDCP status reporting in target cell at DAPS handover | discussion | Ericsson | NR_Mob_enh-Core | Rel-16 |
R2-108 AI: 7.3.2.1.1 |
available | [WTS] [JSN] | |
R2-1914620 | RLC retransmissions to source during DAPS HO |
discussion revision of R2-1912356 |
Ericsson | NR_Mob_enh-Core | Rel-16 |
R2-108 AI: 7.3.2.1.1 |
withdrawn | [WTS] [JSN] | |
R2-1914621 | Specification impact from RLC-UM DAPS support |
discussion revision of R2-1912357 |
Ericsson | NR_Mob_enh-Core | Rel-16 |
R2-108 AI: 7.3.2.1.1 |
withdrawn | [WTS] [JSN] | |
R2-1914705 | Remaining PDCP issues of DAPS handover | discussion | vivo | LTE_feMob-Core | Rel-16 |
R2-108 AI: 7.3.2.1.1 |
available | [WTS] [JSN] | |
R2-1914707 | Clarification on the RLC handling of DAPS handover | discussion | vivo | LTE_feMob-Core | Rel-16 |
R2-108 AI: 7.3.2.1.1 |
noted | [WTS] [JSN] | |
R2-1914817 | Discussion on release of source cell in DAPS HO | discussion | ZTE Corporation, Sanechips | LTE_feMob-Core | Rel-16 |
R2-108 AI: 7.3.2.1.1 |
available | [WTS] [JSN] | |
R2-1914838 | SDAP and PDCP handling for DAPS HO | discussion | Intel Corporation | LTE_feMob-Core, NR_Mob_enh-Core | Rel-16 |
R2-108 AI: 7.3.2.1.1 |
available | [WTS] [JSN] | |
R2-1915039 | Remaining FFSs on Data Forwarding for DAPS HO and CHO | discussion | ETRI | NR_Mob_enh-Core | Rel-16 |
R2-108 AI: 7.3.2.1.1 |
available | [WTS] [JSN] | |
R2-1915346 | Discussion on handover preparation for DAPS | discussion | Huawei, HiSilicon | LTE_feMob-Core | Rel-16 |
R2-108 AI: 7.3.2.1.1 |
available | [WTS] [JSN] | |
R2-1915347 | Discussion on PDCP duplication and reordering for DAPS HO | discussion | Huawei, HiSilicon | LTE_feMob-Core | Rel-16 |
R2-108 AI: 7.3.2.1.1 |
available | [WTS] [JSN] | |
R2-1915350 | Draft CR for 36.323 on supporting DAPS handover |
draftCR revised to R2-1916319 |
Huawei, HiSilicon, Mediatek Inc. | LTE_feMob-Core | Rel-16 |
R2-108 AI: 7.3.2.1.1 |
revised | [WTS] [JSN] | |
R2-1915351 | Draft CR for 38.323 on supporting DAPS handover | draftCR | Huawei, HiSilicon, Mediatek Inc. | LTE_feMob-Core | Rel-16 |
R2-108 AI: 7.3.2.1.1 |
endorsed | [WTS] [JSN] | |
R2-1915451 | Remaining issues on the PDCP anchor relocation for DPAS based handover |
discussion revision of R2-1913053 |
NEC | LTE_feMob-Core | Rel-16 |
R2-108 AI: 7.3.2.1.1 |
available | [WTS] [JSN] | |
R2-1915452 | DL PDCP handling for RLC UM |
discussion revision of R2-1913054 |
NEC | LTE_feMob-Core | Rel-16 |
R2-108 AI: 7.3.2.1.1 |
available | [WTS] [JSN] | |
R2-1915496 | On per-DRB DAPS Handover in NR and LTE |
discussion revision of R2-1913157 |
Nokia, Nokia Shanghai Bell | LTE_feMob-Core | Rel-16 |
R2-108 AI: 7.3.2.1.1 |
available | [WTS] [JSN] | |
R2-1915768 | RLC aspects of DAPS handover |
discussion revision of R2-1912357 |
Ericsson | NR_Mob_enh-Core | Rel-16 |
R2-108 AI: 7.3.2.1.1 |
available | [WTS] [JSN] | |
R2-1915909 | When to apply the target network configurations | discussion | LG Electronics Inc. | NR_Mob_enh-Core |
R2-108 AI: 7.3.2.1.1 |
available | [WTS] [JSN] | ||
R2-1915910 | Need of discard indication | discussion | LG Electronics Inc. | NR_Mob_enh-Core |
R2-108 AI: 7.3.2.1.1 |
available | [WTS] [JSN] | ||
R2-1915911 | Need of PDCP status report | discussion | LG Electronics Inc. | NR_Mob_enh-Core |
R2-108 AI: 7.3.2.1.1 |
available | [WTS] [JSN] | ||
R2-1915912 | Discussion on DAPS HO for UM DRB | discussion | LG Electronics Inc. | NR_Mob_enh-Core |
R2-108 AI: 7.3.2.1.1 |
available | [WTS] [JSN] | ||
R2-1915965 | Handling of releasing source stacks for DAPS | discussion | China Telecommunications |
R2-108 AI: 7.3.2.1.1 |
available | [WTS] [JSN] | |||
R2-1916319 | Draft CR for 36.323 on supporting DAPS handover |
draftCR revision of R2-1915350 |
Huawei, HiSilicon, Mediatek Inc. | LTE_feMob-Core | Rel-16 |
R2-108 AI: 7.3.2.1.1 |
endorsed | [WTS] [JSN] |
30 documents (0.35679388046265 seconds)