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-2307170 | Handling Msg4 and Msg2 with larger bandwidth | discussion | Samsung Electronics Co., Ltd | NR_redcap_enh-Core | Rel-18 |
R2-123 AI: 7.19.3 |
noted | [WTS] [JSN] | |
| R2-2307249 | Discussion on Msg4 PDSCH with a larger bandwidth for eRedCap Ues | discussion | OPPO | NR_redcap_enh-Core | Rel-18 |
R2-123 AI: 7.19.3 |
available | [WTS] [JSN] | |
| R2-2307257 | Discussion on cellbarring for eRedCap UEs | discussion | OPPO | NR_redcap_enh-Core | Rel-18 |
R2-123 AI: 7.19.3 |
available | [WTS] [JSN] | |
| R2-2307303 | Discussion on access restriction for eRedCap | discussion | vivo, Guangdong Genius | NR_redcap_enh-Core | Rel-18 |
R2-123 AI: 7.19.3 |
available | [WTS] [JSN] | |
| R2-2307304 | Discussion on capability for eRedCap | discussion | vivo, Guangdong Genius | NR_redcap_enh-Core | Rel-18 |
R2-123 AI: 7.19.3 |
available | [WTS] [JSN] | |
| R2-2307356 | Discussion on early indication for eRedcap devices | discussion | Xiaomi Communications |
R2-123 AI: 7.19.3 |
available | [WTS] [JSN] | |||
| R2-2307361 | [Draft] Drafted LS to RAN1 on early indication for eRedcap devices |
LS out LS To: RAN1 |
Xiaomi Communications | NR_redcap_enh-Core | Rel-18 |
R2-123 AI: 7.19.3 |
available | [WTS] [JSN] | |
| R2-2307362 | Discussion on UE capabilities and other impacts for eRedcap devices | discussion | Xiaomi Communications |
R2-123 AI: 7.19.3 |
available | [WTS] [JSN] | |||
| R2-2307470 | Further discussions on early indication and access restrictions for eRedCap | discussion | NEC | NR_redcap_enh-Core | Rel-18 |
R2-123 AI: 7.19.3 |
available | [WTS] [JSN] | |
| R2-2307471 | Discussion on issue of decoding Msg4 | discussion | NEC | NR_redcap_enh-Core | Rel-18 |
R2-123 AI: 7.19.3 |
available | [WTS] [JSN] | |
| R2-2307485 | Discussion on further UE complexity reduction | discussion | CEPRI, CATT | NR_redcap_enh-Core | Rel-18 |
R2-123 AI: 7.19.3 |
noted | [WTS] [JSN] | |
| R2-2307517 | On access restrictions for enhanced RedCap | discussion | Nokia, Nokia Shanghai Bell | NR_redcap_enh-Core | Rel-18 |
R2-123 AI: 7.19.3 |
available | [WTS] [JSN] | |
| R2-2307597 | Msg1 early indication for eRedCap UE | discussion | ZTE Corporation, Sanechips | NR_redcap_enh-Core | Rel-18 |
R2-123 AI: 7.19.3 |
available | [WTS] [JSN] | |
| R2-2307599 | Capability definition and report for eRedCap UE | discussion | ZTE Corporation, Sanechips | NR_redcap_enh-Core | Rel-18 |
R2-123 AI: 7.19.3 |
available | [WTS] [JSN] | |
| R2-2307659 | UE Capability Discussion for Rel-18 eRedCap WI | discussion | Intel Corporation | NR_redcap_enh-Core | Rel-18 |
R2-123 AI: 7.19.3 |
noted | [WTS] [JSN] | |
| R2-2307737 | Discussion on RAN1 LS on Msg.4 PDSCH transmission | discussion | vivo, Huawei, HiSilicon, Apple, MediaTek Inc., Qualcomm Inc., Ericsson, Intel Corporation, CMCC, Guangdong Genius | NR_redcap_enh-Core | Rel-18 |
R2-123 AI: 7.19.3 |
noted | [WTS] [JSN] | |
| R2-2307931 | Discussion on UE capability for eRedCap UEs | discussion | Samsung | NR_redcap_enh-Core | Rel-18 |
R2-123 AI: 7.19.3 |
available | [WTS] [JSN] | |
| R2-2308237 | Early identification and access restriction for eRedCap UEs | discussion | Huawei, HiSilicon | NR_redcap_enh-Core | Rel-18 |
R2-123 AI: 7.19.3 |
noted | [WTS] [JSN] | |
| R2-2308341 | On enhanced RedCap capabilities | discussion | Nokia, Nokia Shanghai Bell | NR_redcap_enh-Core | Rel-18 |
R2-123 AI: 7.19.3 |
available | [WTS] [JSN] | |
| R2-2308404 | Open aspects of initial access for eRedCap UEs |
discussion revision of R2-2305901 |
MediaTek Inc. | NR_redcap_enh-Core | Rel-18 |
R2-123 AI: 7.19.3 |
available | [WTS] [JSN] | |
| R2-2308413 | Discussion on further complexity reduction for eRedCap UE | discussion | Qualcomm Incorporated | NR_redcap_enh-Core |
R2-123 AI: 7.19.3 |
available | [WTS] [JSN] | ||
| R2-2308551 | Access restrictions for eRedCap UE | discussion | Semtech Neuchatel SA |
R2-123 AI: 7.19.3 |
available | [WTS] [JSN] | |||
| R2-2308673 | Considerations on Further reduced UE complexity for eRedcap |
discussion revision of R2-2305932 |
Sequans Communications | NR_redcap_enh-Core | Rel-18 |
R2-123 AI: 7.19.3 |
available | [WTS] [JSN] | |
| R2-2308746 | Random access aspects | discussion | Nokia, Nokia Shanghai Bell | NR_redcap_enh-Core |
R2-123 AI: 7.19.3 |
available | [WTS] [JSN] | ||
| R2-2308807 | Access control for BB BW reduced UEs | discussion | Ericsson | NR_redcap_enh-Core | Rel-18 |
R2-123 AI: 7.19.3 |
available | [WTS] [JSN] | |
| R2-2308808 | Capability signalling for eRedCap UEs | discussion | Ericsson | NR_redcap_enh-Core | Rel-18 |
R2-123 AI: 7.19.3 |
available | [WTS] [JSN] | |
| R2-2308814 | Discussion on Cell barring for eRedCap | discussion | NTT DOCOMO INC. | NR_redcap_enh-Core | Rel-18 |
R2-123 AI: 7.19.3 |
available | [WTS] [JSN] | |
| R2-2308825 | Discussion on optional UE capability filter for eRedCap UE |
discussion revision of R2-2305797 revised to R2-2310813 |
Qualcomm Incorporated, Ericsson, Intel, ZTE, Xiaomi | NR_redcap_enh-Core |
R2-123 AI: 7.19.3 |
available | [WTS] [JSN] | ||
| R2-2308877 | Discussion on Msg1-based early indication for Rel-18 eRedCap UE | discussion | LG Electronics Inc. | NR_redcap_enh-Core | Rel-18 |
R2-123 AI: 7.19.3 |
available | [WTS] [JSN] | |
| R2-2308878 | Discussion on MsgA based early indication | discussion | LG Electronics Inc. | NR_redcap_enh-Core | Rel-18 |
R2-123 AI: 7.19.3 |
available | [WTS] [JSN] | |
| R2-2308882 | Access restrictions for eRedCap | discussion | Nordic Semiconductor ASA |
R2-123 AI: 7.19.3 |
available | [WTS] [JSN] | |||
| R2-2309061 | Report from offline 751 | discussion | vivo | NR_redcap_enh-Core | Rel-18 |
R2-123 AI: 7.19.3 |
noted | [WTS] [JSN] | |
| R2-2309062 | [Draft] Reply LS to RAN1 on Msg4 PDSCH transmission to Rel-18 eRedCap Ues |
LS out LS is reply to R2-2304619 LS To: RAN1 revised to R2-2309269 |
vivo | NR_redcap_enh-Core | Rel-18 |
R2-123 AI: 7.19.3 |
revised | [WTS] [JSN] | |
| R2-2309269 | Reply LS to RAN1 on Msg4 PDSCH transmission to Rel-18 eRedCap Ues |
LS out LS is reply to R2-2304619 LS To: RAN1 revision of R2-2309062 |
RAN2 | NR_redcap_enh-Core | Rel-18 |
R2-123 AI: 7.19.3 |
approved | [WTS] [JSN] | |
| R2-2309534 | Identification and access restriction for eRedCap Ues | discussion | OPPO | NR_redcap_enh-Core | Rel-18 |
R2-123-bis AI: 7.19.3 |
available | [WTS] [JSN] | |
| R2-2309576 | Discussion on RA procedure for eRedCap UEs | discussion | OPPO | NR_redcap_enh-Core | Rel-18 |
R2-123-bis AI: 7.19.3 |
available | [WTS] [JSN] | |
| R2-2309697 | Discussion on LCID selection for feature combination | discussion | CATT | NR_redcap_enh-Core | Rel-18 |
R2-123-bis AI: 7.19.3 |
available | [WTS] [JSN] | |
| R2-2309733 | Discussion on access restriction for eRedCap | discussion | vivo, Guangdong Genius | NR_redcap_enh-Core | Rel-18 |
R2-123-bis AI: 7.19.3 |
available | [WTS] [JSN] | |
| R2-2309734 | Discussion on 2-step RACH for eRedCap |
discussion revised to R2-2311913 |
vivo, Guangdong Genius | NR_redcap_enh-Core | Rel-18 |
R2-123-bis AI: 7.19.3 |
postponed | [WTS] [JSN] | |
| R2-2309809 | Early identification and access restriction for eRedCap UEs | discussion | Huawei, HiSilicon | NR_redcap_enh-Core | Rel-18 |
R2-123-bis AI: 7.19.3 |
noted | [WTS] [JSN] | |
| R2-2309810 | Discussion on UE capability of eRedCap UEs | discussion | Huawei, HiSilicon | NR_redcap_enh-Core | Rel-18 |
R2-123-bis AI: 7.19.3 |
noted | [WTS] [JSN] | |
| R2-2310341 | On simplifying RA resource access for (e)RedCap | discussion | Apple | NR_redcap_enh-Core | Rel-18 |
R2-123-bis AI: 7.19.3 |
available | [WTS] [JSN] | |
| R2-2310454 | eRedCap UEs behaviour without eRedCap RA-partition | discussion | NEC | NR_redcap_enh-Core | Rel-18 |
R2-123-bis AI: 7.19.3 |
available | [WTS] [JSN] | |
| R2-2310459 | eRedCap UE behaviour without eRedCap RA-partition | discussion | Samsung | NR_redcap_enh-Core | Rel-18 |
R2-123-bis AI: 7.19.3 |
available | [WTS] [JSN] | |
| R2-2310460 | Remaining issues in further reduced UE complexity in FR1 | discussion | Samsung | NR_redcap_enh-Core | Rel-18 |
R2-123-bis AI: 7.19.3 |
available | [WTS] [JSN] | |
| R2-2310604 | Discussion on Msg1-based early indication for Rel-18 eRedCap UE | discussion | LG Electronics Inc. | NR_redcap_enh-Core | Rel-18 |
R2-123-bis AI: 7.19.3 |
available | [WTS] [JSN] | |
| R2-2310627 | Discussion on eRedCap UEs behavior with RA-partition |
discussion revised to R2-2311214 |
Xiaomi Communications |
R2-123-bis AI: 7.19.3 |
revised | [WTS] [JSN] | |||
| R2-2310645 | Discussion on remaining issues on early indication for eRedcap |
discussion revised to R2-2311219 |
Xiaomi Communications |
R2-123-bis AI: 7.19.3 |
revised | [WTS] [JSN] | |||
| R2-2310723 | Discussion on bit rate and BW reduction for eRedCap | discussion | Nokia, Nokia Shanghai Bell, Ericsson, NTT DOCOMO, Intel, Semtech, BT, Deutsche Telekom | NR_redcap_enh-Core | Rel-18 |
R2-123-bis AI: 7.19.3 |
noted | [WTS] [JSN] | |
| R2-2310812 | Discussion on further complexity reduction for eRedCap UE | discussion | Qualcomm Incorporated | NR_redcap_enh-Core |
R2-123-bis AI: 7.19.3 |
noted | [WTS] [JSN] | ||
| R2-2310813 | Discussion on optional UE capability filter for eRedCap UE |
discussion revision of R2-2308825 |
Qualcomm Incorporated, Ericsson, Intel, ZTE, Xiaomi | NR_redcap_enh-Core |
R2-123-bis AI: 7.19.3 |
noted | [WTS] [JSN] | ||
| R2-2310831 | Remaining issues of Msg1 early indication and access restriction | discussion | ZTE Corporation, Sanechips | NR_redcap_enh-Core | Rel-18 |
R2-123-bis AI: 7.19.3 |
available | [WTS] [JSN] | |
| R2-2310832 | Remaining issues of eRedCap UE capabilities | discussion | ZTE Corporation, Sanechips | NR_redcap_enh-Core | Rel-18 |
R2-123-bis AI: 7.19.3 |
available | [WTS] [JSN] | |
| R2-2310874 | Resource partition for eRedCap | discussion | Nokia, Nokia Shanghai Bell | NR_redcap_enh-Core |
R2-123-bis AI: 7.19.3 |
available | [WTS] [JSN] | ||
| R2-2310875 | Summary of [Post123][756] eRedCap UE behaviour without eRedCap RA partition | discussion | Nokia, Nokia Shanghai Bell | NR_redcap_enh-Core |
R2-123-bis AI: 7.19.3 |
available | [WTS] [JSN] | ||
| R2-2311061 | Discussion on capability signaling for eRedCap UEs | discussion | Ericsson | NR_redcap_enh-Core | Rel-18 |
R2-123-bis AI: 7.19.3 |
available | [WTS] [JSN] | |
| R2-2311062 | Selection of RA resources for eRedCap UEs | discussion | Ericsson | NR_redcap_enh-Core | Rel-18 |
R2-123-bis AI: 7.19.3 |
available | [WTS] [JSN] | |
| R2-2311197 | Msg1 Early Indication for eRedcap | discussion | Sequans Communications | NR_redcap_enh-Core | Rel-18 |
R2-123-bis AI: 7.19.3 |
available | [WTS] [JSN] | |
| R2-2311214 | Discussion on eRedCap UEs behavior with RA-partition |
discussion revision of R2-2310627 |
Beijing Xiaomi Mobile Software | NR_redcap-Core | Rel-18 |
R2-123-bis AI: 7.19.3 |
available | [WTS] [JSN] | |
| R2-2311219 | Discussion on remaining issues on early indication for eRedcap |
discussion revision of R2-2310645 |
Beijing Xiaomi Mobile Software | NR_redcap-Core | Rel-18 |
R2-123-bis AI: 7.19.3 |
available | [WTS] [JSN] | |
| R2-2311428 | WF on selection of RA resource set for eRedCap | discussion | Nokia, Nokia Shanghai Bell, Samsung, Xiaomi | NR_redcap_enh-Core | Rel-18 |
R2-123-bis AI: 7.19.3 |
noted | [WTS] [JSN] |
61 documents (0.32154297828674 seconds)