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-2100101 | Discussion on HARQ-ACK enhancements for eURLLC | discussion | ZTE | NR_IIOT_URLLC_enh-Core | Rel-17 |
R1-104-e AI: 8.3.1.1 |
not treated | [WTS] [JSN] | |
| R1-2100181 | HARQ-ACK enhancements for Rel-17 URLLC/IIoT | discussion | OPPO | NR_IIOT_URLLC_enh-Core | Rel-17 |
R1-104-e AI: 8.3.1.1 |
not treated | [WTS] [JSN] | |
| R1-2100226 | UE feedback enhancements for HARQ-ACK | discussion | Huawei, BUPT, China Southern Power Grid, HiSilicon | NR_IIOT_URLLC_enh-Core | Rel-17 |
R1-104-e AI: 8.3.1.1 |
not treated | [WTS] [JSN] | |
| R1-2100268 | HARQ-ACK Enhancements for IIoT/URLLC | discussion | Ericsson | NR_IIOT_URLLC_enh-Core | Rel-17 |
R1-104-e AI: 8.3.1.1 |
not treated | [WTS] [JSN] | |
| R1-2100302 | UE feedback enhancements for HARQ-ACK | discussion | CAICT | NR_IIOT_URLLC_enh-Core | Rel-17 |
R1-104-e AI: 8.3.1.1 |
not treated | [WTS] [JSN] | |
| R1-2100376 | UE feedback enhancements for HARQ-ACK | discussion | CATT | NR_IIOT_URLLC_enh-Core | Rel-17 |
R1-104-e AI: 8.3.1.1 |
not treated | [WTS] [JSN] | |
| R1-2100436 | HARQ-ACK enahncements for Rel-17 URLLC | discussion | vivo | NR_IIOT_URLLC_enh-Core | Rel-17 |
R1-104-e AI: 8.3.1.1 |
not treated | [WTS] [JSN] | |
| R1-2100574 | On UE feedback enhancements for HARQ-ACK | discussion | MediaTek Inc. | NR_IIOT_URLLC_enh-Core | Rel-17 |
R1-104-e AI: 8.3.1.1 |
not treated | [WTS] [JSN] | |
| R1-2100649 | UE HARQ feedback enhancements for URLLC/IIoT | discussion | Intel Corporation | NR_IIOT_URLLC_enh-Core | Rel-17 |
R1-104-e AI: 8.3.1.1 |
not treated | [WTS] [JSN] | |
| R1-2100728 | HARQ-ACK Feedback Enhancements for URLLC/IIoT | discussion | Nokia, Nokia Shanghai Bell | NR_IIOT_URLLC_enh-Core | Rel-17 |
R1-104-e AI: 8.3.1.1 |
not treated | [WTS] [JSN] | |
| R1-2100803 | Discussion on physical Layer feedback enhancements | discussion | Spreadtrum Communications | NR_IIOT_URLLC_enh-Core | Rel-17 |
R1-104-e AI: 8.3.1.1 |
not treated | [WTS] [JSN] | |
| R1-2100855 | Considerations on HARQ-ACK enhancements for URLLC | discussion | Sony | NR_IIOT_URLLC_enh-Core | Rel-17 |
R1-104-e AI: 8.3.1.1 |
not treated | [WTS] [JSN] | |
| R1-2100880 | Discussion on UE feedback enhancement for HARQ-ACK | discussion | LG Electronics | NR_IIOT_URLLC_enh-Core | Rel-17 |
R1-104-e AI: 8.3.1.1 |
not treated | [WTS] [JSN] | |
| R1-2100911 | Discussion on UE feedback enhancements for HARQ-ACK | discussion | China Telecom | NR_IIOT_URLLC_enh-Core | Rel-17 |
R1-104-e AI: 8.3.1.1 |
not treated | [WTS] [JSN] | |
| R1-2100920 | UE feedback enhancements for HARQ-ACK | discussion | TCL Communication Ltd. | NR_IIOT_URLLC_enh-Core | Rel-17 |
R1-104-e AI: 8.3.1.1 |
not treated | [WTS] [JSN] | |
| R1-2100948 | UE feedback enhancements for HARQ-ACK | discussion | NEC | NR_IIOT_URLLC_enh-Core | Rel-17 |
R1-104-e AI: 8.3.1.1 |
not treated | [WTS] [JSN] | |
| R1-2100968 | Discussion on UE feedback enhancements for HARQ-ACK | discussion | Asia Pacific Telecom, FGI | NR_IIOT_URLLC_enh-Core | Rel-17 |
R1-104-e AI: 8.3.1.1 |
not treated | [WTS] [JSN] | |
| R1-2100993 | HARQ-ACK feedback enhancement for IIoT/URLLC | discussion | Lenovo, Motorola Mobility | NR_IIOT_URLLC_enh-Core | Rel-17 |
R1-104-e AI: 8.3.1.1 |
not treated | [WTS] [JSN] | |
| R1-2101013 | Discussion on UE feedback enhancements for HARQ-ACK | discussion | Panasonic Corporation | NR_IIOT_URLLC_enh-Core | Rel-17 |
R1-104-e AI: 8.3.1.1 |
not treated | [WTS] [JSN] | |
| R1-2101039 | Discussion on UE feedback enhancements for HARQ-ACK |
discussion revised to R1-2102910 |
CMCC | NR_IIOT_URLLC_enh-Core | Rel-17 |
R1-104-e AI: 8.3.1.1 |
not treated | [WTS] [JSN] | |
| R1-2101075 | UE feedback enhancements for HARQ-ACK | discussion | ETRI | NR_IIOT_URLLC_enh-Core | Rel-17 |
R1-104-e AI: 8.3.1.1 |
not treated | [WTS] [JSN] | |
| R1-2101114 | UE feedback enhancement for HARQ-ACK | discussion | Xiaomi | NR_IIOT_URLLC_enh-Core | Rel-17 |
R1-104-e AI: 8.3.1.1 |
not treated | [WTS] [JSN] | |
| R1-2101201 | On HARQ-ACK reporting enhancements | discussion | Samsung | NR_IIOT_URLLC_enh-Core | Rel-17 |
R1-104-e AI: 8.3.1.1 |
not treated | [WTS] [JSN] | |
| R1-2101290 | HARQ-ACK enhancements for IIoT and URLLC | discussion | InterDigital, Inc. | NR_IIOT_URLLC_enh-Core | Rel-17 |
R1-104-e AI: 8.3.1.1 |
not treated | [WTS] [JSN] | |
| R1-2101378 | Views on UE feedback enhancements for HARQ-ACK | discussion | Apple | NR_IIOT_URLLC_enh-Core | Rel-17 |
R1-104-e AI: 8.3.1.1 |
not treated | [WTS] [JSN] | |
| R1-2101459 | HARQ-ACK enhancement for IOT and URLLC | discussion | Qualcomm Incorporated | NR_IIOT_URLLC_enh-Core | Rel-17 |
R1-104-e AI: 8.3.1.1 |
noted | [WTS] [JSN] | |
| R1-2101539 | UE feedback enhancements for HARQ-ACK | discussion | Sharp | NR_IIOT_URLLC_enh-Core | Rel-17 |
R1-104-e AI: 8.3.1.1 |
not treated | [WTS] [JSN] | |
| R1-2101612 | Discussion on HARQ-ACK feedback enhancements for Rel.17 URLLC | discussion | NTT DOCOMO, INC. | NR_IIOT_URLLC_enh-Core | Rel-17 |
R1-104-e AI: 8.3.1.1 |
not treated | [WTS] [JSN] | |
| R1-2101675 | Discussion on HARQ-ACK enhancement for URLLC/IIoT | discussion | WILUS Inc. | NR_IIOT_URLLC_enh-Core | Rel-17 |
R1-104-e AI: 8.3.1.1 |
not treated | [WTS] [JSN] | |
| R1-2101817 | Moderator summary #1 on HARQ-ACK feedback enhancements for NR Rel-17 URLLC/IIoT | discussion | Moderator (Nokia) | NR_IIOT_URLLC_enh-Core | Rel-17 |
R1-104-e AI: 8.3.1.1 |
noted | [WTS] [JSN] | |
| R1-2101818 | Moderator summary #2 on HARQ-ACK feedback enhancements for NR Rel-17 URLLC/IIoT | discussion | Moderator (Nokia) | NR_IIOT_URLLC_enh-Core | Rel-17 |
R1-104-e AI: 8.3.1.1 |
noted | [WTS] [JSN] |
31 documents (0.32619905471802 seconds)