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-2000199 Corrections on HARQ-ACK feedback discussion Huawei, HiSilicon NR_unlic-Core Rel-16 R1-ah-37786

AI: 7.2.2.2.3

not treated [WTS] [JSN]
R1-2000257 Remaining issues on HARQ operation for NR-U discussion vivo Rel-16 R1-ah-37786

AI: 7.2.2.2.3

withdrawn [WTS] [JSN]
R1-2000311 Remaining issues on HARQ operation for NR-U discussion vivo Rel-16 R1-ah-37786

AI: 7.2.2.2.3

not treated [WTS] [JSN]
R1-2000391 Maintenance on the HARQ for NR-U discussion ZTE, Sanechips R1-ah-37786

AI: 7.2.2.2.3

not treated [WTS] [JSN]
R1-2000412 Discussion on remaining issues on HARQ enhancement for NR-U discussion Beijing Xiaomi Mobile Software R1-ah-37786

AI: 7.2.2.2.3

not treated [WTS] [JSN]
R1-2000439 Remaining issues on Enhancements to HARQ for NR-U operation discussion MediaTek Inc. R1-ah-37786

AI: 7.2.2.2.3

not treated [WTS] [JSN]
R1-2000472 Discussion on the remaining issues of HARQ enhancements discussion OPPO Rel-16 R1-ah-37786

AI: 7.2.2.2.3

not treated [WTS] [JSN]
R1-2000503 Remaining issues on NR-U HARQ scheduling and feedback other Nokia, Nokia Shanghai Bell R1-ah-37786

AI: 7.2.2.2.3

not treated [WTS] [JSN]
R1-2000592 Text proposals for HARQ enhancement for NR-U discussion Lenovo, Motorola Mobility R1-ah-37786

AI: 7.2.2.2.3

not treated [WTS] [JSN]
R1-2000612 HARQ enhancement for NR-U discussion Samsung NR_unlic-Core Rel-16 R1-ah-37786

AI: 7.2.2.2.3

not treated [WTS] [JSN]
R1-2000665 Remaining issues of HARQ procedure for NR-U discussion LG Electronics NR_unlic-Core Rel-16 R1-ah-37786

AI: 7.2.2.2.3

not treated [WTS] [JSN]
R1-2000726 Enhancements to HARQ for NR-unlicensed discussion Intel Corporation Rel-16 R1-ah-37786

AI: 7.2.2.2.3

not treated [WTS] [JSN]
R1-2000828 HARQ enhancement discussion Ericsson NR_unlic-Core Rel-16 R1-ah-37786

AI: 7.2.2.2.3

not treated [WTS] [JSN]
R1-2000849 Remaining issues on HARQ enhancement discussion Apple NR_unlic-Core Rel-16 R1-ah-37786

AI: 7.2.2.2.3

not treated [WTS] [JSN]
R1-2000874 Remaining issues and corrections on HARQ enhancement for NR-U discussion Sharp NR_unlic-Core Rel-16 R1-ah-37786

AI: 7.2.2.2.3

not treated [WTS] [JSN]
R1-2000958 TP for Enhancements to Scheduling and HARQ Operation for NR-U discussion Qualcomm Incorporated NR_unlic-Core Rel-16 R1-ah-37786

AI: 7.2.2.2.3

not treated [WTS] [JSN]
R1-2000997 Correction on HARQ process discussion ASUSTeK NR_unlic-Core Rel-16 R1-ah-37786

AI: 7.2.2.2.3

not treated [WTS] [JSN]
R1-2001000 Remaining issues on NR-U HARQ procedures discussion Google Inc. NR_unlic-Core Rel-16 R1-ah-37786

AI: 7.2.2.2.3

not treated [WTS] [JSN]
R1-2001043 Feature lead summary#1 on NR-U HARQ and multi-PUSCH scheduling discussion

revised to R1-2001191

Huawei NR_unlic-Core Rel-16 R1-ah-37786

AI: 7.2.2.2.3

revised [WTS] [JSN]
R1-2001191 Feature lead summary#2 on NR-U HARQ and multi-PUSCH scheduling discussion

revision of R1-2001043

Huawei NR_unlic-Core Rel-16 R1-ah-37786

AI: 7.2.2.2.3

noted [WTS] [JSN]
R1-2001268 Feature lead summary of email discussion 100e-NR-unlic-NRU-HARQandULscheduling-02 (Type-3 HARQ-ACK codebook) discussion Huawei NR_unlic-Core Rel-16 R1-ah-37786

AI: 7.2.2.2.3

endorsed [WTS] [JSN]
R1-2001269 Feature lead summary of email discussion 100e-NR-unlic-NRU-HARQandULscheduling-01 (enhanced Type-2 HARQ-ACK codebook) discussion Huawei NR_unlic-Core Rel-16 R1-ah-37786

AI: 7.2.2.2.3

endorsed [WTS] [JSN]
R1-2001270 Feature lead summary of email discussion 100e-NR-unlic-NRU-HARQandULscheduling-03 (multi-PUSCH scheduling with DCI 0_1) discussion Huawei NR_unlic-Core Rel-16 R1-ah-37786

AI: 7.2.2.2.3

endorsed [WTS] [JSN]

23 documents (0.35928702354431 seconds)