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-2005273 | Discussion on the potential coverage enhancement solutions for PUCCH | discussion | Huawei, HiSilicon | FS_NR_cov_enh | Rel-17 |
R1-102-e AI: 8.8.2.2 |
not treated | [WTS] [JSN] | |
R1-2005300 | Discussion on potential approaches and solutions for NR PUCCH coverage enhancement | discussion | Nokia, Nokia Shanghai Bell | Rel-17 |
R1-102-e AI: 8.8.2.2 |
not treated | [WTS] [JSN] | ||
R1-2005396 | Discussion on Solutions for PUCCH coverage enhancement | discussion | vivo | Rel-17 |
R1-102-e AI: 8.8.2.2 |
not treated | [WTS] [JSN] | ||
R1-2005428 | Discussion on potential techniques for PUCCH coverage enhancements | discussion | ZTE | Rel-17 |
R1-102-e AI: 8.8.2.2 |
not treated | [WTS] [JSN] | ||
R1-2005585 | On PUCCH coverage enhancement techniques | discussion | Sony |
R1-102-e AI: 8.8.2.2 |
not treated | [WTS] [JSN] | |||
R1-2005725 | Discussion on potential techniques for PUCCH coverage enhancement | discussion | CATT |
R1-102-e AI: 8.8.2.2 |
not treated | [WTS] [JSN] | |||
R1-2005759 | Discussion on PUCCH coverage enhancement | discussion | NEC | FS_NR_cov_enh | Rel-17 |
R1-102-e AI: 8.8.2.2 |
noted | [WTS] [JSN] | |
R1-2005890 | Discussion on potential techniques for PUCCH coverage enhancement |
discussion revised to R1-2007175 |
Intel Corporation | Rel-17 |
R1-102-e AI: 8.8.2.2 |
revised | [WTS] [JSN] | ||
R1-2006048 | Consideration on PUCCH coverage enhancement | discussion | OPPO |
R1-102-e AI: 8.8.2.2 |
not treated | [WTS] [JSN] | |||
R1-2006163 | PUCCH coverage enhancement | discussion | Samsung |
R1-102-e AI: 8.8.2.2 |
not treated | [WTS] [JSN] | |||
R1-2006227 | Discussion on the PUCCH coverage enhancement | discussion | CMCC |
R1-102-e AI: 8.8.2.2 |
noted | [WTS] [JSN] | |||
R1-2006246 | PUCCH coverage enhancement | discussion | InterDigital, Inc. | FS_NR_cov_enh | Rel-17 |
R1-102-e AI: 8.8.2.2 |
not treated | [WTS] [JSN] | |
R1-2006349 | Discussion on PUCCH coverage enhancements | discussion | Panasonic Corporation | Rel-17 |
R1-102-e AI: 8.8.2.2 |
not treated | [WTS] [JSN] | ||
R1-2006457 | PUCCH coverage enhancements |
discussion revised to R1-2008756 |
Indian Institute of Tech (H) |
R1-102-e AI: 8.8.2.2 |
not treated | [WTS] [JSN] | |||
R1-2006580 | PUCCH coverage enhancement | discussion | Sharp | FS_NR_cov_enh |
R1-102-e AI: 8.8.2.2 |
not treated | [WTS] [JSN] | ||
R1-2006614 | PUCCH coverage enhancement | discussion | Ericsson |
R1-102-e AI: 8.8.2.2 |
not treated | [WTS] [JSN] | |||
R1-2006742 | Potential techniques for PUCCH coverage enhancements | discussion | NTT DOCOMO, INC. | Rel-17 |
R1-102-e AI: 8.8.2.2 |
noted | [WTS] [JSN] | ||
R1-2006821 | Potential coverage enhancement techniques for PUCCH | discussion | Qualcomm Incorporated | Rel-17 |
R1-102-e AI: 8.8.2.2 |
not treated | [WTS] [JSN] | ||
R1-2006880 | Limitations of NR short block-length codes for PUCCH coverage enhancement | discussion | EURECOM | Rel-17 |
R1-102-e AI: 8.8.2.2 |
not treated | [WTS] [JSN] | ||
R1-2006893 | Discussion on potential techniques for PUCCH coverage enhancement | discussion | WILUS Inc. | Rel-17 |
R1-102-e AI: 8.8.2.2 |
not treated | [WTS] [JSN] | ||
R1-2007175 | Discussion on potential techniques for PUCCH coverage enhancement |
discussion revision of R1-2005890 |
Intel Corporation | Rel-17 |
R1-102-e AI: 8.8.2.2 |
not treated | [WTS] [JSN] | ||
R1-2007473 | FL summary of PUCCH coverage enhancement | discussion | Moderator (Qualcomm) | FS_NR_cov_enh | Rel-17 |
R1-102-e AI: 8.8.2.2 |
noted | [WTS] [JSN] |
22 documents (0.3325400352478 seconds)