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-161809 | NB-PUSCH design | other | Huawei, HiSilicon |
R1-ah-32047 AI: 2.3.1 |
noted | [WTS] [JSN] | |||
| R1-161811 | Remaining details of uplink frame structure design | other | Huawei, HiSilicon |
R1-ah-32047 AI: 2.3.1 |
available | [WTS] [JSN] | |||
| R1-161832 | NB-IoT - Remaining issues for NPUSCH design |
discussion revised to R1-161987 |
Ericsson |
R1-ah-32047 AI: 2.3.1 |
revised | [WTS] [JSN] | |||
| R1-161850 | NB-PUSCH design | discussion | Nokia Networks, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell |
R1-ah-32047 AI: 2.3.1 |
available | [WTS] [JSN] | |||
| R1-161867 | Remaining issues on uplink data transmission for NB-IoT | discussion | ZTE |
R1-ah-32047 AI: 2.3.1 |
available | [WTS] [JSN] | |||
| R1-161868 | Resource allocation of uplink data channel for NB-IoT | discussion | ZTE |
R1-ah-32047 AI: 2.3.1 |
available | [WTS] [JSN] | |||
| R1-161869 | Remaining issue on modulation scheme for uplink of NB-IoT | discussion | ZTE |
R1-ah-32047 AI: 2.3.1 |
available | [WTS] [JSN] | |||
| R1-161879 | Frequency Tracking in Long NB-PUSCH Transmission | discussion | Sony |
R1-ah-32047 AI: 2.3.1 |
available | [WTS] [JSN] | |||
| R1-161880 | Considerations in NB-PUSCH | discussion | Sony |
R1-ah-32047 AI: 2.3.1 |
available | [WTS] [JSN] | |||
| R1-161885 | NB-PUSCH resource allocation | other | Huawei, HiSilicon |
R1-ah-32047 AI: 2.3.1 |
available | [WTS] [JSN] | |||
| R1-161901 | Remaining details of NB-PUSCH | discussion | Intel Corporation |
R1-ah-32047 AI: 2.3.1 |
available | [WTS] [JSN] | |||
| R1-161908 | Discussion on UL TBS/MCS table |
discussion revised to R1-161983 |
MediaTek Inc. |
R1-ah-32047 AI: 2.3.1 |
revised | [WTS] [JSN] | |||
| R1-161909 | Resource allocation of NB-PUSCH | discussion | MediaTek Inc. |
R1-ah-32047 AI: 2.3.1 |
available | [WTS] [JSN] | |||
| R1-161919 | Discussion on NB-IoT PUSCH resource mapping | discussion | Panasonic Corporation | Rel-13 |
R1-ah-32047 AI: 2.3.1 |
available | [WTS] [JSN] | ||
| R1-161920 | NB-IoT PUSCH performance with 15 kHz and 3.75 kHz subcarrier spacing | discussion | Panasonic Corporation | Rel-13 |
R1-ah-32047 AI: 2.3.1 |
available | [WTS] [JSN] | ||
| R1-161929 | Considerations on Modulation Schemes | discussion | Samsung |
R1-ah-32047 AI: 2.3.1 |
withdrawn | [WTS] [JSN] | |||
| R1-161930 | Peformance Evaluations of TPSK | discussion | Samsung |
R1-ah-32047 AI: 2.3.1 |
available | [WTS] [JSN] | |||
| R1-161939 | UL Data Channel Design | other | Qualcomm Inc. |
R1-ah-32047 AI: 2.3.1 |
available | [WTS] [JSN] | |||
| R1-161940 | Description of 8-BPSK and TPSK for the NB-IOT uplink | other | Qualcomm Inc. |
R1-ah-32047 AI: 2.3.1 |
noted | [WTS] [JSN] | |||
| R1-161941 | PAPR and transmission power of UL modulation for NB-IOT | other | Qualcomm Inc. |
R1-ah-32047 AI: 2.3.1 |
available | [WTS] [JSN] | |||
| R1-161954 | Resource allocation for NB-PUSCH | discussion | Sharp |
R1-ah-32047 AI: 2.3.1 |
available | [WTS] [JSN] | |||
| R1-161959 | NB-IoT - NPUSCH Resource Allocation | discussion | Ericsson | Rel-13 |
R1-ah-32047 AI: 2.3.1 |
available | [WTS] [JSN] | ||
| R1-161964 | Discussion on NB-PDSCH/NB-PUSCH transmission for NB-IoT | discussion | Spreadtrum Communications |
R1-ah-32047 AI: 2.3.1 |
available | [WTS] [JSN] | |||
| R1-161970 | Remaining issues on NB-PUSCH design for NB-IoT | other | LG Electronics |
R1-ah-32047 AI: 2.3.1 |
available | [WTS] [JSN] | |||
| R1-161983 | Discussion on UL TBS/MCS table |
discussion revision of R1-161908 |
MediaTek Inc. |
R1-ah-32047 AI: 2.3.1 |
noted | [WTS] [JSN] | |||
| R1-161987 | NB-IoT - Remaining issues for NPUSCH design |
discussion revision of R1-161832 |
Ericsson |
R1-ah-32047 AI: 2.3.1 |
available | [WTS] [JSN] | |||
| R1-161989 | NB-IoT PUSCH performance with CFO estimation and compensation | discussion | Panasonic |
R1-ah-32047 AI: 2.3.1 |
available | [WTS] [JSN] | |||
| R1-161995 | WF on TPSK |
discussion revised to R1-162004 |
Qualcomm, Samsung, Huawei, HiSilicon, Neul, Vodafone, CMCC, CATR, KDDI, China Unicom, China Telecom, Potevio, IITH,CEWiT, Reliance-Jio, Intel |
R1-ah-32047 AI: 2.3.1 |
revised | [WTS] [JSN] | |||
| R1-162002 | WF on Transmission Gaps in NB-PUSCH Repetition | discussion | Sony, Intel, Panasonic, Sequans |
R1-ah-32047 AI: 2.3.1 |
noted | [WTS] [JSN] | |||
| R1-162003 | WF on PUSCH & PDSCH Repetitions | discussion | Sony, Panasonic, CATT, DoCoMo |
R1-ah-32047 AI: 2.3.1 |
noted | [WTS] [JSN] | |||
| R1-162004 | WF on TPSK |
discussion revision of R1-161995 |
Qualcomm, Samsung, Huawei, HiSilicon, Neul, Vodafone, CMCC, CATR, KDDI, China Unicom, China Telecom, Potevio, IITH,CEWiT, Reliance-Jio, Intel, Sony |
R1-ah-32047 AI: 2.3.1 |
noted | [WTS] [JSN] | |||
| R1-162010 | WF on SRS avoidance |
discussion revised to R1-162042 |
Huawei, HiSilicon |
R1-ah-32047 AI: 2.3.1 |
noted | [WTS] [JSN] | |||
| R1-162039 | WF for TBS/MCS table design for NB-PUSCH |
discussion revised to R1-162056 |
Panasonic |
R1-ah-32047 AI: 2.3.1 |
noted | [WTS] [JSN] | |||
| R1-162040 | WF on Transmission Gaps in NB-PUSCH Repetition | discussion | Sony, Intel, Panasonic, Sequans, Ericsson, Spreadtrum, Sierra Wireless, Virtuosys, ZTE, Softbank, Interdigital |
R1-ah-32047 AI: 2.3.1 |
available | [WTS] [JSN] | |||
| R1-162041 | Draft LS on uplink transmission gap in NB-IoT |
discussion revised to R1-162069 |
Sony | NB_IOT-Core | Rel-13 |
R1-ah-32047 AI: 2.3.1 |
revised | [WTS] [JSN] | |
| R1-162042 | Draft WF on configuration to avoid SRS |
discussion revision of R1-162010 |
Huawei, HiSilicon, Nokia, Samsung |
R1-ah-32047 AI: 2.3.1 |
available | [WTS] [JSN] | |||
| R1-162056 | WF for TBS/MCS table design for NB-PUSCH |
discussion revision of R1-162039 |
Panasonic |
R1-ah-32047 AI: 2.3.1 |
agreed | [WTS] [JSN] | |||
| R1-162060 | Summary of NB-PUSCH Subcarrier Allocation | discussion | Huawei, HiSilicon |
R1-ah-32047 AI: 2.3.1 |
noted | [WTS] [JSN] | |||
| R1-162062 | WF on RV cycling for NB-PUSCH repetition | discussion | ZTE, CATT |
R1-ah-32047 AI: 2.3.1 |
available | [WTS] [JSN] | |||
| R1-162064 | Summary of NB-PUSCH Subcarrier Allocation | discussion | Huawei, HiSilicon |
R1-ah-32047 AI: 2.3.1 |
available | [WTS] [JSN] | |||
| R1-162069 | LS on uplink transmission gap in NB-IoT |
LS out LS To: RAN4 revision of R1-162041 |
RAN1, Sony | NB_IOT-Core | Rel-13 |
R1-ah-32047 AI: 2.3.1 |
agreed | [WTS] [JSN] |
41 documents (0.35633993148804 seconds)