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 |
|---|---|---|---|---|---|---|---|---|---|
| R1-2108742 | Discussion on Msg3 repetition for coverage enhancement | discussion | Huawei, HiSilicon | NR_cov_enh-Core | Rel-17 |
R1-106-bis-e AI: 8.8.3 |
not treated | [WTS] [JSN] | |
| R1-2108849 | Discussion on support of Type A PUSCH repetitions for Msg3 | discussion | ZTE | NR_cov_enh-Core | Rel-17 |
R1-106-bis-e AI: 8.8.3 |
not treated | [WTS] [JSN] | |
| R1-2108923 | Discussion on Type A PUSCH repetitions for Msg3 | discussion | Spreadtrum Communications | NR_cov_enh-Core | Rel-17 |
R1-106-bis-e AI: 8.8.3 |
not treated | [WTS] [JSN] | |
| R1-2108993 | Discussion on Type A PUSCH repetitions for Msg3 | discussion | vivo | NR_cov_enh-Core | Rel-17 |
R1-106-bis-e AI: 8.8.3 |
not treated | [WTS] [JSN] | |
| R1-2109092 | Type A PUSCH repetitions for Msg3 coverage | discussion | OPPO | NR_cov_enh-Core | Rel-17 |
R1-106-bis-e AI: 8.8.3 |
not treated | [WTS] [JSN] | |
| R1-2109134 | Discussion on PUSCH repetition for Msg3 | discussion | NEC | NR_cov_enh-Core | Rel-17 |
R1-106-bis-e AI: 8.8.3 |
not treated | [WTS] [JSN] | |
| R1-2109244 | Discussion on Type A PUSCH repetitions for Msg3 | discussion | CATT | NR_cov_enh-Core | Rel-17 |
R1-106-bis-e AI: 8.8.3 |
not treated | [WTS] [JSN] | |
| R1-2109252 | Remaining issues on type A PUSCH repetitions for Msg3 | discussion | China Telecom | NR_cov_enh-Core | Rel-17 |
R1-106-bis-e AI: 8.8.3 |
not treated | [WTS] [JSN] | |
| R1-2109299 | Discussion on type A PUSCH repetitions for Msg3 | discussion | CMCC | NR_cov_enh-Core | Rel-17 |
R1-106-bis-e AI: 8.8.3 |
not treated | [WTS] [JSN] | |
| R1-2109428 | Discussion on Type A PUSCH repetition for Msg3 | discussion | Xiaomi | NR_cov_enh-Core | Rel-17 |
R1-106-bis-e AI: 8.8.3 |
not treated | [WTS] [JSN] | |
| R1-2109458 | Discussion on Type A PUSCH repetitions for Msg.3 | discussion | Panasonic Corporation | NR_cov_enh-Core | Rel-17 |
R1-106-bis-e AI: 8.8.3 |
not treated | [WTS] [JSN] | |
| R1-2109508 | Type A PUSCH repetitions for Msg3 | discussion | Samsung | NR_cov_enh-Core | Rel-17 |
R1-106-bis-e AI: 8.8.3 |
not treated | [WTS] [JSN] | |
| R1-2109628 | On Msg3 PUSCH repetition | discussion | Intel Corporation | NR_cov_enh-Core | Rel-17 |
R1-106-bis-e AI: 8.8.3 |
not treated | [WTS] [JSN] | |
| R1-2109696 | Type A PUSCH repetitions for Msg3 | discussion | NTT DOCOMO, INC. | NR_cov_enh-Core | Rel-17 |
R1-106-bis-e AI: 8.8.3 |
not treated | [WTS] [JSN] | |
| R1-2109815 | Type A PUSCH repetitions for Msg3 | discussion | ETRI | NR_cov_enh-Core | Rel-17 |
R1-106-bis-e AI: 8.8.3 |
not treated | [WTS] [JSN] | |
| R1-2109890 | Approaches and solutions for Type A PUSCH repetitions for Msg3 | discussion | Nokia, Nokia Shanghai Bell | NR_cov_enh-Core | Rel-17 |
R1-106-bis-e AI: 8.8.3 |
not treated | [WTS] [JSN] | |
| R1-2110004 | Type-A PUSCH repetition for msg3 | discussion | Sharp | NR_cov_enh-Core | Rel-17 |
R1-106-bis-e AI: 8.8.3 |
not treated | [WTS] [JSN] | |
| R1-2110050 | Discussion on Msg3 Coverage Enhancement | discussion | Apple | NR_cov_enh-Core | Rel-17 |
R1-106-bis-e AI: 8.8.3 |
not treated | [WTS] [JSN] | |
| R1-2110100 | Discussion on coverage enhancement for Msg3 PUSCH | discussion | LG Electronics | NR_cov_enh-Core | Rel-17 |
R1-106-bis-e AI: 8.8.3 |
not treated | [WTS] [JSN] | |
| R1-2110126 | Type A PUSCH Repetition for Msg3 | discussion | Ericsson | NR_cov_enh-Core | Rel-17 |
R1-106-bis-e AI: 8.8.3 |
not treated | [WTS] [JSN] | |
| R1-2110205 | Type A PUSCH repetition for Msg3 | discussion | Qualcomm Incorporated | NR_cov_enh-Core | Rel-17 |
R1-106-bis-e AI: 8.8.3 |
not treated | [WTS] [JSN] | |
| R1-2110236 | Type A PUSCH repetitions for Msg3 | discussion | InterDigital, Inc. | NR_cov_enh-Core | Rel-17 |
R1-106-bis-e AI: 8.8.3 |
not treated | [WTS] [JSN] | |
| R1-2110330 | Discussion on Type A PUSCH repetitions for Msg3 | discussion | WILUS Inc. | NR_cov_enh-Core | Rel-17 |
R1-106-bis-e AI: 8.8.3 |
not treated | [WTS] [JSN] | |
| R1-2110417 | Feature lead summary #1 on support of Type A PUSCH repetitions for Msg3 | discussion | Moderator (ZTE) | NR_cov_enh-Core | Rel-17 |
R1-106-bis-e AI: 8.8.3 |
noted | [WTS] [JSN] | |
| R1-2110418 | Feature lead summary #2 on support of Type A PUSCH repetitions for Msg4 | discussion | Moderator (ZTE) | NR_cov_enh-Core | Rel-17 |
R1-106-bis-e AI: 8.8.3 |
noted | [WTS] [JSN] | |
| R1-2110419 | Feature lead summary #3 on support of Type A PUSCH repetitions for Msg5 | discussion | Moderator (ZTE) | NR_cov_enh-Core | Rel-17 |
R1-106-bis-e AI: 8.8.3 |
noted | [WTS] [JSN] | |
| R1-2110585 | Reply LS on Msg3 repetition in coverage enhancement |
LS out LS is reply to R2-2109195 LS To: RAN2 |
RAN1, ZTE | NR_cov_enh-Core | Rel-17 |
R1-106-bis-e AI: 8.8.3 |
approved | [WTS] [JSN] | |
| R1-2110589 | Summary of discussion on reply LS for Msg3 repetition in coverage enhancement | discussion | Moderator (ZTE) | NR_cov_enh-Core | Rel-17 |
R1-106-bis-e AI: 8.8.3 |
noted | [WTS] [JSN] |
28 documents (0.3270628452301 seconds)