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-2007584 | Potential solutions for PUCCH coverage enhancement |
discussion revised to R1-2009747 |
Huawei, HiSilicon | FS_NR_cov_enh | Rel-17 |
R1-103-e AI: 8.8.2.2 |
not treated | [WTS] [JSN] | |
R1-2007681 | Discussion on Solutions for PUCCH coverage enhancement |
discussion revised to R1-2008942 |
vivo | FS_NR_cov_enh | Rel-17 |
R1-103-e AI: 8.8.2.2 |
revised | [WTS] [JSN] | |
R1-2007744 | Discussion on potential techniques for PUCCH coverage enhancements |
discussion revised to R1-2009696 |
ZTE | FS_NR_cov_enh | Rel-17 |
R1-103-e AI: 8.8.2.2 |
not treated | [WTS] [JSN] | |
R1-2007875 | Discussion on potential techniques for PUCCH coverage enhancement | discussion | CATT | FS_NR_cov_enh | Rel-17 |
R1-103-e AI: 8.8.2.2 |
not treated | [WTS] [JSN] | |
R1-2007955 | On potential techniques for PUCCH coverage enhancement |
discussion revised to R1-2009602 |
Intel Corporation | FS_NR_cov_enh | Rel-17 |
R1-103-e AI: 8.8.2.2 |
not treated | [WTS] [JSN] | |
R1-2007995 | Discussion on PUCCH coverage enhancements | discussion | China Telecom | FS_NR_cov_enh | Rel-17 |
R1-103-e AI: 8.8.2.2 |
not treated | [WTS] [JSN] | |
R1-2008027 | Discussion on PUCCH coverage enhancement | discussion | CMCC | FS_NR_cov_enh | Rel-17 |
R1-103-e AI: 8.8.2.2 |
not treated | [WTS] [JSN] | |
R1-2008079 | Discussion on PUCCH coverage enhancement | discussion | NEC | FS_NR_cov_enh | Rel-17 |
R1-103-e AI: 8.8.2.2 |
not treated | [WTS] [JSN] | |
R1-2008182 | PUCCH coverage enhancement | discussion | Samsung | FS_NR_cov_enh | Rel-17 |
R1-103-e AI: 8.8.2.2 |
not treated | [WTS] [JSN] | |
R1-2008272 | PUCCH coverage enhancement schemes | discussion | OPPO | FS_NR_cov_enh | Rel-17 |
R1-103-e AI: 8.8.2.2 |
not treated | [WTS] [JSN] | |
R1-2008371 | On PUCCH coverage enhancement techniques | discussion | Sony | FS_NR_cov_enh | Rel-17 |
R1-103-e AI: 8.8.2.2 |
withdrawn | [WTS] [JSN] | |
R1-2008379 | Discussion on PUCCH coverage enhancements | discussion | Panasonic Corporation | FS_NR_cov_enh | Rel-17 |
R1-103-e AI: 8.8.2.2 |
not treated | [WTS] [JSN] | |
R1-2008400 | PUCCH coverage enhancement | discussion | Sharp | FS_NR_cov_enh | Rel-17 |
R1-103-e AI: 8.8.2.2 |
not treated | [WTS] [JSN] | |
R1-2008404 | Discussions on PUCCH coverage enhancement | discussion | LG Electronics | FS_NR_cov_enh | Rel-17 |
R1-103-e AI: 8.8.2.2 |
not treated | [WTS] [JSN] | |
R1-2008420 | PUCCH coverage enhancement | discussion | Ericsson | FS_NR_cov_enh | Rel-17 |
R1-103-e AI: 8.8.2.2 |
not treated | [WTS] [JSN] | |
R1-2008484 | PUCCH coverage enhancements | discussion | InterDigital, Inc. | FS_NR_cov_enh | Rel-17 |
R1-103-e AI: 8.8.2.2 |
not treated | [WTS] [JSN] | |
R1-2008560 | Potential techniques for PUCCH coverage enhancements | discussion | NTT DOCOMO, INC. | FS_NR_cov_enh | Rel-17 |
R1-103-e AI: 8.8.2.2 |
not treated | [WTS] [JSN] | |
R1-2008627 | Potential coverage enhancement techniques for PUCCH |
discussion revised to R1-2009315 |
Qualcomm Incorporated | FS_NR_cov_enh | Rel-17 |
R1-103-e AI: 8.8.2.2 |
revised | [WTS] [JSN] | |
R1-2008704 | Discussion on approaches and solutions for NR PUCCH coverage enhancement | discussion | Nokia, Nokia Shanghai Bell | FS_NR_cov_enh | Rel-17 |
R1-103-e AI: 8.8.2.2 |
not treated | [WTS] [JSN] | |
R1-2008730 | Discussion on potential techniques for PUCCH coverage enhancement | discussion | WILUS Inc. | FS_NR_cov_enh | Rel-17 |
R1-103-e AI: 8.8.2.2 |
not treated | [WTS] [JSN] | |
R1-2008756 | PUCCH coverage enhancements |
discussion revision of R1-2006457 |
Indian Institute of Tech (H) | FS_NR_cov_enh | Rel-17 |
R1-103-e AI: 8.8.2.2 |
not treated | [WTS] [JSN] | |
R1-2008759 | Low-PAPR Sequence-Based Approaches for PUCCH Coverage Enhancement |
discussion revised to R1-2008938 |
EURECOM | FS_NR_cov_enh | Rel-17 |
R1-103-e AI: 8.8.2.2 |
revised | [WTS] [JSN] | |
R1-2008938 | Low-PAPR Sequence-Based Approaches for PUCCH Coverage Enhancement |
discussion revision of R1-2008759 revised to R1-2009451 |
EURECOM | FS_NR_cov_enh | Rel-17 |
R1-103-e AI: 8.8.2.2 |
revised | [WTS] [JSN] | |
R1-2008942 | Discussion on Solutions for PUCCH coverage enhancement |
discussion revision of R1-2007681 revised to R1-2009648 |
vivo Mobile Communication (S) | FS_NR_cov_enh | Rel-17 |
R1-103-e AI: 8.8.2.2 |
not treated | [WTS] [JSN] | |
R1-2009315 | Potential coverage enhancement techniques for PUCCH |
discussion revision of R1-2008627 revised to R1-2009360 |
Qualcomm Incorporated | FS_NR_cov_enh | Rel-17 |
R1-103-e AI: 8.8.2.2 |
revised | [WTS] [JSN] | |
R1-2009321 | FL summary of PUCCH coverage enhancement |
discussion revised to R1-2009405 |
Moderator (Qualcomm) | FS_NR_cov_enh | Rel-17 |
R1-103-e AI: 8.8.2.2 |
noted | [WTS] [JSN] | |
R1-2009360 | Potential coverage enhancement techniques for PUCCH |
discussion revision of R1-2009315 revised to R1-2009552 |
Qualcomm Incorporated | FS_NR_cov_enh | Rel-17 |
R1-103-e AI: 8.8.2.2 |
revised | [WTS] [JSN] | |
R1-2009405 | FL summary#2 of PUCCH coverage enhancement |
discussion revision of R1-2009321 |
Moderator (Qualcomm) | FS_NR_cov_enh | Rel-17 |
R1-103-e AI: 8.8.2.2 |
noted | [WTS] [JSN] | |
R1-2009451 | Low-PAPR Sequence-Based Approaches for PUCCH Coverage Enhancement |
discussion revision of R1-2008938 |
EURECOM | FS_NR_cov_enh | Rel-17 |
R1-103-e AI: 8.8.2.2 |
not treated | [WTS] [JSN] | |
R1-2009552 | Potential coverage enhancement techniques for PUCCH |
discussion revision of R1-2009360 revised to R1-2009711 |
Qualcomm Incorporated | FS_NR_cov_enh | Rel-17 |
R1-103-e AI: 8.8.2.2 |
revised | [WTS] [JSN] | |
R1-2009602 | On potential techniques for PUCCH coverage enhancement |
discussion revision of R1-2007955 |
Intel Corporation | FS_NR_cov_enh | Rel-17 |
R1-103-e AI: 8.8.2.2 |
not treated | [WTS] [JSN] | |
R1-2009648 | Discussion on Solutions for PUCCH coverage enhancement |
discussion revision of R1-2008942 |
vivo Mobile Communication | FS_NR_cov_enh | Rel-17 |
R1-103-e AI: 8.8.2.2 |
not treated | [WTS] [JSN] | |
R1-2009696 | Discussion on potential techniques for PUCCH coverage enhancements |
discussion revision of R1-2007744 |
ZTE | FS_NR_cov_enh | Rel-17 |
R1-103-e AI: 8.8.2.2 |
not treated | [WTS] [JSN] | |
R1-2009711 | Potential coverage enhancement techniques for PUCCH |
discussion revision of R1-2009552 revised to R1-2009802 |
Qualcomm Incorporated | FS_NR_cov_enh | Rel-17 |
R1-103-e AI: 8.8.2.2 |
revised | [WTS] [JSN] | |
R1-2009737 | PUCCH DTX detection performance | discussion | Ericsson | FS_NR_cov_enh | Rel-17 |
R1-103-e AI: 8.8.2.2 |
not treated | [WTS] [JSN] | |
R1-2009747 | Potential solutions for PUCCH coverage enhancement |
discussion revision of R1-2007584 |
Huawei, HiSilicon | FS_NR_cov_enh | Rel-17 |
R1-103-e AI: 8.8.2.2 |
not treated | [WTS] [JSN] | |
R1-2009784 | LS on PUCCH and PUSCH repetition |
LS out LS To: RAN4 |
RAN1, Qualcomm | FS_NR_cov_enh | Rel-17 |
R1-103-e AI: 8.8.2.2 |
approved | [WTS] [JSN] | |
R1-2009802 | Potential coverage enhancement techniques for PUCCH |
discussion revision of R1-2009711 |
Qualcomm Incorporated | FS_NR_cov_enh | Rel-17 |
R1-103-e AI: 8.8.2.2 |
not treated | [WTS] [JSN] |
38 documents (0.32018399238586 seconds)