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-2307082 | Use of low-power receiver in RRC Idle/Inactive | discussion | Qualcomm Incorporated | FS_NR_LPWUS | Rel-18 |
R2-123 AI: 7.22.2 |
available | [WTS] [JSN] | |
R2-2307261 | Discussion on coverage impact for LP-WUR | discussion | OPPO | FS_NR_LPWUS | Rel-18 |
R2-123 AI: 7.22.2 |
available | [WTS] [JSN] | |
R2-2307274 | Discussion on LP-WUS in RRC IDLE and INACTIVE | discussion | Continental Automotive |
R2-123 AI: 7.22.2 |
available | [WTS] [JSN] | |||
R2-2307307 | Discussion on LP-WUS WUR in RRC_IDLE/INACTIVE | discussion | vivo | FS_NR_LPWUS | Rel-18 |
R2-123 AI: 7.22.2 |
available | [WTS] [JSN] | |
R2-2307344 | General considerations on the procedure for RRC_IDLE_INACTIVE | discussion | Xiaomi Communications |
R2-123 AI: 7.22.2 |
available | [WTS] [JSN] | |||
R2-2307423 | Discussion on LP-WUS in RRC_IDLE&INACTIVE state | discussion | CATT | FS_NR_LPWUS | Rel-18 |
R2-123 AI: 7.22.2 |
available | [WTS] [JSN] | |
R2-2307453 | MR/LR UE behaviours for paging and mobility in RRC_IDLE/INACTIVE state | discussion | Huawei, HiSilicon | FS_NR_LPWUS | Rel-18 |
R2-123 AI: 7.22.2 |
available | [WTS] [JSN] | |
R2-2307461 | Discussion on the considerations for LPWUS in RRC_IDLE INACTIVE | discussion | NEC Corporation | FS_NR_LPWUS |
R2-123 AI: 7.22.2 |
available | [WTS] [JSN] | ||
R2-2307516 | LP-WUS in RRC IDLE and INACTIVE | discussion | Nokia, Nokia Shanghai Bell | FS_NR_LPWUS | Rel-18 |
R2-123 AI: 7.22.2 |
available | [WTS] [JSN] | |
R2-2307591 | RAN2 impacts of LP-WUS in idle or inactive mode |
discussion revision of R2-2305960 |
ZTE Corporation, Sanechips | FS_NR_LPWUS | Rel-18 |
R2-123 AI: 7.22.2 |
available | [WTS] [JSN] | |
R2-2307848 | RAN2 impact of LP-WUS in RRC_IDLE/INACTIVE state |
discussion revised to R2-2308977 |
Apple | FS_NR_LPWUS | Rel-18 |
R2-123 AI: 7.22.2 |
revised | [WTS] [JSN] | |
R2-2308168 | Considerations on LP-WUR in RRC Idle/Inactive mode | discussion | Sony | FS_NR_LPWUS | Rel-18 |
R2-123 AI: 7.22.2 |
available | [WTS] [JSN] | |
R2-2308460 | LP-WUS in RRC Idle/ Inactive Mode | discussion | Lenovo | FS_NR_LPWUS | Rel-18 |
R2-123 AI: 7.22.2 |
available | [WTS] [JSN] | |
R2-2308748 | On LP-WUS in RRC_CONNECTED |
discussion revision of R2-2306312 |
Nokia, Nokia Shanghai Bell | FS_NR_LPWUS |
R2-123 AI: 7.22.2 |
available | [WTS] [JSN] | ||
R2-2308809 | LP-WUS/WUR for RRC Idle and Inactive | discussion | Ericsson | FS_NR_LPWUS | Rel-18 |
R2-123 AI: 7.22.2 |
noted | [WTS] [JSN] | |
R2-2308828 | On impact to IDLE/INACTIVE procedures to support LP-WUR | discussion | SAMSUNG R&D INSTITUTE INDIA | Rel-18 |
R2-123 AI: 7.22.2 |
available | [WTS] [JSN] | ||
R2-2308977 | RAN2 impact of LP-WUS in RRC_IDLE/INACTIVE state |
discussion revision of R2-2307848 |
Apple | FS_NR_LPWUS | Rel-18 |
R2-123 AI: 7.22.2 |
available | [WTS] [JSN] | |
R2-2309267 | Report of [Offline-026][LP-WUS] Idle/inactive aspects | discussion | vivo | FS_NR_LPWUS | Rel-18 |
R2-123 AI: 7.22.2 |
noted | [WTS] [JSN] | |
R2-2309493 | Use of low-power receiver in RRC Idle/Inactive | discussion | Qualcomm Incorporated | FS_NR_LPWUS | Rel-18 |
R2-123-bis AI: 7.22.2 |
available | [WTS] [JSN] | |
R2-2309536 | Discussion on LP-WUS in RRC_IDLE/INACTIVE | discussion | OPPO | FS_NR_LPWUS | Rel-18 |
R2-123-bis AI: 7.22.2 |
available | [WTS] [JSN] | |
R2-2309735 | Discussion on LP-WUS WUR in RRC_IDLE INACTIVE |
discussion revised to R2-2311916 |
vivo | FS_NR_LPWUS | Rel-18 |
R2-123-bis AI: 7.22.2 |
available | [WTS] [JSN] | |
R2-2309818 | Further considerations on LP-WUS in RRC_IDLE&INACTIVE states | discussion | CATT | FS_NR_LPWUS | Rel-18 |
R2-123-bis AI: 7.22.2 |
available | [WTS] [JSN] | |
R2-2309858 | LP-WUS in RRC_IDLE/INACATIVE | discussion | LG Electronics Inc. | FS_NR_LPWUS | Rel-18 |
R2-123-bis AI: 7.22.2 |
available | [WTS] [JSN] | |
R2-2310039 | General considerations on the procedure for RRC_IDLE_INACTIVE | discussion | Xiaomi Communications |
R2-123-bis AI: 7.22.2 |
available | [WTS] [JSN] | |||
R2-2310062 | Discussion on LPWUS in RRC_IDLE INACTIVE | discussion | NEC Corporation. | FS_NR_LPWUS | Rel-18 |
R2-123-bis AI: 7.22.2 |
available | [WTS] [JSN] | |
R2-2310313 | RAN2 impact of LP-WUS in RRC_IDLE/INACTIVE state | discussion | Apple | FS_NR_LPWUS | Rel-18 |
R2-123-bis AI: 7.22.2 |
available | [WTS] [JSN] | |
R2-2310483 | Remaining issues on LP-WUS in RRC_IDLE/INACTIVE state | discussion | Huawei, HiSilicon | FS_NR_LPWUS | Rel-18 |
R2-123-bis AI: 7.22.2 |
available | [WTS] [JSN] | |
R2-2310722 | LP-WUS in RRC IDLE and INACTIVE | discussion | Nokia, Nokia Shanghai Bell | FS_NR_LPWUS | Rel-18 |
R2-123-bis AI: 7.22.2 |
available | [WTS] [JSN] | |
R2-2310778 | Considerations on LP-WUR in RRC Idle/Inactive mode | discussion | Sony | FS_NR_LPWUS | Rel-18 |
R2-123-bis AI: 7.22.2 |
available | [WTS] [JSN] | |
R2-2310827 | Remaining issues of LP-WUS in idle or inactive mode | discussion | ZTE Corporation, Sanechips | FS_NR_LPWUS | Rel-18 |
R2-123-bis AI: 7.22.2 |
available | [WTS] [JSN] | |
R2-2311064 | LP-WUS/WUR for RRC Idle and Inactive | discussion | Ericsson | FS_NR_LPWUS | Rel-18 |
R2-123-bis AI: 7.22.2 |
available | [WTS] [JSN] | |
R2-2311171 | On impact to IDLE/INACTIVE procedures to support LP-WUR | discussion | Samsung R&D Institute India | Rel-18 |
R2-123-bis AI: 7.22.2 |
available | [WTS] [JSN] | ||
R2-2311216 | LP-WUS in RRC Idle/ Inactive Mode | discussion | Lenovo | FS_NR_LPWUS |
R2-123-bis AI: 7.22.2 |
available | [WTS] [JSN] | ||
R2-2311336 | Summary of [AT123bis][510][LP-WUS] connected mode (vivo) | discussion | vivo | FS_NR_LPWUS | Rel-18 |
R2-123-bis AI: 7.22.2 |
noted | [WTS] [JSN] |
34 documents (0.32397294044495 seconds)