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-161800 | Draft Agenda of the Ad-hoc on NB-IoT | agenda | RAN1 Chair | NB_IOT-Core | Rel-13 |
R1-ah-32047 AI: 2.1 |
approved | [WTS] [JSN] | |
| R1-161801 | NB-MIB design | other | Huawei, HiSilicon |
R1-ah-32047 AI: 2.2.1 |
available | [WTS] [JSN] | |||
| R1-161802 | Remaining details of NB-PDCCH design | other | Huawei, HiSilicon |
R1-ah-32047 AI: 2.2.2 |
noted | [WTS] [JSN] | |||
| R1-161803 | DCI for NB-IoT | other | Huawei, HiSilicon |
R1-ah-32047 AI: 2.2.2 |
available | [WTS] [JSN] | |||
| R1-161804 | System information transmission | other | Huawei, HiSilicon |
R1-ah-32047 AI: 2.2.4 |
available | [WTS] [JSN] | |||
| R1-161805 | NB-PDSCH design | other | Huawei, HiSilicon |
R1-ah-32047 AI: 2.2.3 |
noted | [WTS] [JSN] | |||
| R1-161806 | NB-SSS design | other | Huawei, HiSilicon |
R1-ah-32047 AI: 2.2.5 |
available | [WTS] [JSN] | |||
| R1-161807 | Remaining details of downlink reference signal design | other | Huawei, HiSilicon |
R1-ah-32047 AI: 2.2.6 |
noted | [WTS] [JSN] | |||
| R1-161808 | UCI for NB-IoT | other | Huawei, HiSilicon |
R1-ah-32047 AI: 2.3.3 |
available | [WTS] [JSN] | |||
| R1-161809 | NB-PUSCH design | other | Huawei, HiSilicon |
R1-ah-32047 AI: 2.3.1 |
noted | [WTS] [JSN] | |||
| R1-161810 | NB-DMRS design | other | Huawei, HiSilicon |
R1-ah-32047 AI: 2.3.2 |
available | [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-161812 | NB-PRACH design | other | Huawei, HiSilicon, Neul |
R1-ah-32047 AI: 2.3.4 |
noted | [WTS] [JSN] | |||
| R1-161813 | Remaining NB-IoT random access physical layer aspects | other | Huawei, HiSilicon |
R1-ah-32047 AI: 2.3.4 |
available | [WTS] [JSN] | |||
| R1-161814 | Downlink power allocation | other | Huawei, HiSilicon |
R1-ah-32047 AI: 2.2.8 |
available | [WTS] [JSN] | |||
| R1-161815 | Uplink power control | other | Huawei, HiSilicon |
R1-ah-32047 AI: 2.3.5 |
noted | [WTS] [JSN] | |||
| R1-161816 | Reply LS on questions on NB-IoT |
LS in LS is reply to S2-160937 source LS: S2-161333 LS To: RAN2, RAN3, CT1, SA3 |
SA2, Vodafone | NB_IOT-Core | Rel-13 |
R1-ah-32047 AI: 2.1 |
treated | [WTS] [JSN] | |
| R1-161817 | LS on available subframes for paging |
LS in source LS: R2-161943 LS To: RAN1 LS reply in R1-161985 |
RAN2, Huawei | NB_IOT-Core | Rel-13 |
R1-ah-32047 AI: 2.1 |
treated | [WTS] [JSN] | |
| R1-161818 | LS on updates for TS 36.300 |
LS in source LS: R2-161885 LS To: RAN1, RAN3 LS reply in R1-163900, R1-163932, R1-163937 |
RAN2, Huawei | NB_IOT-Core | Rel-13 |
R1-ah-32047 AI: 2.1 |
treated | [WTS] [JSN] | |
| R1-161819 | LS on per-UE configuration to allow exception reporting |
LS in LS is reply to C1-160784 source LS: C1-161430 LS To: RAN2 |
CT1, Qualcomm | NB_IOT-Core | Rel-13 |
R1-ah-32047 AI: 2.1 |
treated | [WTS] [JSN] | |
| R1-161820 | NB-IoT - Remaining issues for NPBCH and MIB | discussion | Ericsson |
R1-ah-32047 AI: 2.2.1 |
noted | [WTS] [JSN] | |||
| R1-161821 | NB-IoT - DCI content | discussion | Ericsson |
R1-ah-32047 AI: 2.2.2 |
available | [WTS] [JSN] | |||
| R1-161822 | NB-IoT - Search space design considerations | discussion | Ericsson |
R1-ah-32047 AI: 2.2.2 |
available | [WTS] [JSN] | |||
| R1-161823 | NB-IoT - Timing relations | discussion | Ericsson |
R1-ah-32047 AI: 2.2.2 |
available | [WTS] [JSN] | |||
| R1-161824 | NB-IoT - Common search space design for paging | discussion | Ericsson |
R1-ah-32047 AI: 2.2.2 |
available | [WTS] [JSN] | |||
| R1-161825 | NB-IoT - Remaining issues for NPDSCH design |
discussion revised to R1-161986 |
Ericsson |
R1-ah-32047 AI: 2.2.3 |
revised | [WTS] [JSN] | |||
| R1-161826 | NB-IoT - NPDSCH resource allocation | discussion | Ericsson |
R1-ah-32047 AI: 2.2.3 |
available | [WTS] [JSN] | |||
| R1-161827 | NB-IoT - System information | discussion | Ericsson |
R1-ah-32047 AI: 2.2.4 |
withdrawn | [WTS] [JSN] | |||
| R1-161828 | NB-IoT - SI change indication in DCI format for paging | discussion | Ericsson |
R1-ah-32047 AI: 2.2.4 |
available | [WTS] [JSN] | |||
| R1-161829 | NB-IoT - NSSS Design | discussion | Ericsson |
R1-ah-32047 AI: 2.2.5 |
available | [WTS] [JSN] | |||
| R1-161830 | NB-IoT - Synchronization Channel Evaluations | discussion | Ericsson |
R1-ah-32047 AI: 2.2.5 |
noted | [WTS] [JSN] | |||
| R1-161831 | NB-IoT - Remaining issues for NRS | discussion | Ericsson |
R1-ah-32047 AI: 2.2.6 |
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-161833 | NB-IoT - UL Reference signals | discussion | Ericsson |
R1-ah-32047 AI: 2.3.2 |
available | [WTS] [JSN] | |||
| R1-161834 | NB-IoT - NPRACH sequences | discussion | Ericsson |
R1-ah-32047 AI: 2.3.4 |
noted | [WTS] [JSN] | |||
| R1-161835 | NB-IoT - NPRACH configurations | discussion | Ericsson |
R1-ah-32047 AI: 2.3.4 |
available | [WTS] [JSN] | |||
| R1-161836 | NB-IoT - Remaining issues for random access procedure | discussion | Ericsson |
R1-ah-32047 AI: 2.3.4 |
available | [WTS] [JSN] | |||
| R1-161837 | NB-IoT - Valid subframes | discussion | Ericsson |
R1-ah-32047 AI: 2.4 |
available | [WTS] [JSN] | |||
| R1-161838 | NB-IoT - Collision handling | discussion | Ericsson |
R1-ah-32047 AI: 2.4 |
available | [WTS] [JSN] | |||
| R1-161839 | Design of MIB content for NB-IoT | discussion | Nokia Networks, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell |
R1-ah-32047 AI: 2.2.1 |
noted | [WTS] [JSN] | |||
| R1-161840 | NB-PDCCH design for NB-IoT | discussion | Nokia Networks, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell |
R1-ah-32047 AI: 2.2.2 |
available | [WTS] [JSN] | |||
| R1-161841 | DCI design for NB-IoT | discussion | Nokia Networks, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell |
R1-ah-32047 AI: 2.2.2 |
available | [WTS] [JSN] | |||
| R1-161842 | NB-PDSCH design for NB-IoT | discussion | Nokia Networks, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell |
R1-ah-32047 AI: 2.2.3 |
available | [WTS] [JSN] | |||
| R1-161843 | Time discontinuous transmission for NB-IoT | discussion | Nokia Networks, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell |
R1-ah-32047 AI: 2.2.3 |
available | [WTS] [JSN] | |||
| R1-161844 | Remaining issues on NB-SIB1 transmission for NB-IoT | discussion | Nokia Networks, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell |
R1-ah-32047 AI: 2.2.4 |
available | [WTS] [JSN] | |||
| R1-161845 | SI scheduling for NB-IoT | discussion | Nokia Networks, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell |
R1-ah-32047 AI: 2.2.4 |
available | [WTS] [JSN] | |||
| R1-161846 | Remaining issues on paging for NB-IoT | discussion | Nokia Networks, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell |
R1-ah-32047 AI: 2.2.4 |
noted | [WTS] [JSN] | |||
| R1-161847 | Remaining issues on NB-RS design for NB-IoT | discussion | Nokia Networks, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell |
R1-ah-32047 AI: 2.2.6 |
available | [WTS] [JSN] | |||
| R1-161848 | Physical layer measurements for NB-IoT | discussion | Nokia Networks, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell |
R1-ah-32047 AI: 2.2.7 |
noted | [WTS] [JSN] | |||
| R1-161849 | Multi-carrier operation in NB-IoT | discussion | Nokia Networks, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell |
R1-ah-32047 AI: 2.2.8 |
available | [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-161851 | On UL DMRS design for NB-IoT | discussion | Nokia Networks, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell |
R1-ah-32047 AI: 2.3.2 |
available | [WTS] [JSN] | |||
| R1-161852 | UCI for NB-IoT | discussion | Nokia Networks, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell |
R1-ah-32047 AI: 2.3.3 |
available | [WTS] [JSN] | |||
| R1-161853 | Remaining issues on NB-PRACH design for NB-IoT | discussion | Nokia Networks, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell |
R1-ah-32047 AI: 2.3.4 |
available | [WTS] [JSN] | |||
| R1-161854 | Remaining issues on random access procedure for NB-IoT | discussion | Nokia Networks, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell |
R1-ah-32047 AI: 2.3.4 |
available | [WTS] [JSN] | |||
| R1-161855 | UL power control for NB-IoT | discussion | Nokia Networks, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell |
R1-ah-32047 AI: 2.3.5 |
available | [WTS] [JSN] | |||
| R1-161856 | Timing relationships for NB-IoT | discussion | Nokia Networks, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell |
R1-ah-32047 AI: 2.4 |
available | [WTS] [JSN] | |||
| R1-161857 | Definition of phase alignment for NB-IoT single tone UL modulation | discussion | Nokia Networks, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell |
R1-ah-32047 AI: 2.3.5 |
available | [WTS] [JSN] | |||
| R1-161858 | Remaining details of NB-MIB contents for NB-IoT | discussion | ZTE |
R1-ah-32047 AI: 2.2.1 |
noted | [WTS] [JSN] | |||
| R1-161859 | Remaining issues on NB-PDCCH design for NB-IoT | discussion | ZTE |
R1-ah-32047 AI: 2.2.2 |
noted | [WTS] [JSN] | |||
| R1-161860 | Further considerations on NB-PDSCH design for NB-IoT | discussion | ZTE |
R1-ah-32047 AI: 2.2.3 |
available | [WTS] [JSN] | |||
| R1-161861 | Remaining issues on NB-SIB1 design for NB-IoT | discussion | ZTE |
R1-ah-32047 AI: 2.2.4 |
available | [WTS] [JSN] | |||
| R1-161862 | Remaining issues on paging transmission for NB-IoT | discussion | ZTE |
R1-ah-32047 AI: 2.2.4 |
available | [WTS] [JSN] | |||
| R1-161863 | Details on NB-PSS and NB-SSS design for NB-IoT |
discussion revised to R1-161993 |
ZTE |
R1-ah-32047 AI: 2.2.5 |
revised | [WTS] [JSN] | |||
| R1-161864 | Remaining issue on NB-RS for NB-IoT | discussion | ZTE |
R1-ah-32047 AI: 2.2.6 |
available | [WTS] [JSN] | |||
| R1-161865 | Downlink measurement for NB-IoT | discussion | ZTE |
R1-ah-32047 AI: 2.2.7 |
noted | [WTS] [JSN] | |||
| R1-161866 | DL power allocation for NB-IoT | discussion | ZTE |
R1-ah-32047 AI: 2.2.8 |
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-161870 | Uplink DM RS design for NB-IoT | discussion | ZTE |
R1-ah-32047 AI: 2.3.2 |
noted | [WTS] [JSN] | |||
| R1-161871 | UCI transmission for NB-IoT | discussion | ZTE |
R1-ah-32047 AI: 2.3.3 |
available | [WTS] [JSN] | |||
| R1-161872 | Remaining issues on single tone PRACH for NB-IoT | discussion | ZTE |
R1-ah-32047 AI: 2.3.4 |
noted | [WTS] [JSN] | |||
| R1-161873 | UL power control for NB-IoT | discussion | ZTE |
R1-ah-32047 AI: 2.3.5 |
available | [WTS] [JSN] | |||
| R1-161874 | Collision handling for NB-IoT | discussion | Nokia Networks, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell |
R1-ah-32047 AI: 2.4 |
available | [WTS] [JSN] | |||
| R1-161875 | NB-IoT - Uplink control information | discussion | Ericsson | Rel-13 |
R1-ah-32047 AI: 2.3.3 |
available | [WTS] [JSN] | ||
| R1-161876 | Considerations on NB-PDCCH | discussion | Sony |
R1-ah-32047 AI: 2.2.2 |
available | [WTS] [JSN] | |||
| R1-161877 | NB-PDCCH Timing and Collision | discussion | Sony |
R1-ah-32047 AI: 2.2.2 |
available | [WTS] [JSN] | |||
| R1-161878 | Considerations in NB-PDSCH | discussion | Sony |
R1-ah-32047 AI: 2.2.3 |
noted | [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-161881 | UCI Transmission in NB-IoT | discussion | Sony |
R1-ah-32047 AI: 2.3.3 |
available | [WTS] [JSN] | |||
| R1-161882 | Paging transmission | other | Huawei, HiSilicon |
R1-ah-32047 AI: 2.2.4 |
available | [WTS] [JSN] | |||
| R1-161883 | Physical layer measurements | other | Huawei, HiSilicon |
R1-ah-32047 AI: 2.2.7 |
available | [WTS] [JSN] | |||
| R1-161884 | Summary of RAN2 open items with possible RAN1 dependence | other | Huawei, HiSilicon |
R1-ah-32047 AI: 2.4 |
available | [WTS] [JSN] | |||
| R1-161885 | NB-PUSCH resource allocation | other | Huawei, HiSilicon |
R1-ah-32047 AI: 2.3.1 |
available | [WTS] [JSN] | |||
| R1-161886 | Remaining details of multi-carrier NB-IoT operation | other | Huawei, HiSilicon |
R1-ah-32047 AI: 2.2.3 |
available | [WTS] [JSN] | |||
| R1-161887 | DMRS Density Effects on eNB CFO Estimation |
discussion revised to R1-161984 |
Sierra Wireless, S.A. | Rel-13 |
R1-ah-32047 AI: 2.3.2 |
revised | [WTS] [JSN] | ||
| R1-161888 | Remaining details of NB-MIB design | discussion | Intel Corporation |
R1-ah-32047 AI: 2.2.1 |
available | [WTS] [JSN] | |||
| R1-161889 | Remaining details of NB-PDCCH design | discussion | Intel Corporation |
R1-ah-32047 AI: 2.2.2 |
available | [WTS] [JSN] | |||
| R1-161890 | NB-PDCCH search space design | discussion | Intel Corporation |
R1-ah-32047 AI: 2.2.2 |
available | [WTS] [JSN] | |||
| R1-161891 | Remaining details of NB-IoT timing relationships | discussion | Intel Corporation |
R1-ah-32047 AI: 2.2.3 |
available | [WTS] [JSN] | |||
| R1-161892 | Remaining details of NB-PDSCH design | discussion | Intel Corporation |
R1-ah-32047 AI: 2.2.3 |
available | [WTS] [JSN] | |||
| R1-161893 | Remaining details of NB-IoT multi-carrier operation | discussion | Intel Corporation |
R1-ah-32047 AI: 2.2.3 |
available | [WTS] [JSN] | |||
| R1-161894 | NB-IoT system information and paging transmission | discussion | Intel Corporation |
R1-ah-32047 AI: 2.2.4 |
available | [WTS] [JSN] | |||
| R1-161895 | Remaining details of NB-IoT Primary Synchronization Signal design | discussion | Intel Corporation |
R1-ah-32047 AI: 2.2.5 |
available | [WTS] [JSN] | |||
| R1-161896 | NB-IoT Secondary Synchronization Signal Design | discussion | Intel Corporation |
R1-ah-32047 AI: 2.2.5 |
available | [WTS] [JSN] | |||
| R1-161897 | Receiver algorithms and complexity analyses for NB-IoT synchronization | discussion | Intel Corporation |
R1-ah-32047 AI: 2.2.5 |
available | [WTS] [JSN] | |||
| R1-161898 | Synchronization and cell search in NB-IoT: Performance evaluations | discussion | Intel Corporation |
R1-ah-32047 AI: 2.2.5 |
available | [WTS] [JSN] | |||
| R1-161899 | Remaining details of NB-IoT reference signals design | discussion | Intel Corporation |
R1-ah-32047 AI: 2.2.6 |
available | [WTS] [JSN] | |||
| R1-161900 | Physical layer measurements for NB-IoT | discussion | Intel Corporation |
R1-ah-32047 AI: 2.2.7 |
available | [WTS] [JSN] | |||
| R1-161901 | Remaining details of NB-PUSCH | discussion | Intel Corporation |
R1-ah-32047 AI: 2.3.1 |
available | [WTS] [JSN] | |||
| R1-161902 | UCI and DL HARQ-ACK feedback for NB-IoT | discussion | Intel Corporation |
R1-ah-32047 AI: 2.3.3 |
available | [WTS] [JSN] | |||
| R1-161903 | Remaining details of NB-PRACH and random access | discussion | Intel Corporation |
R1-ah-32047 AI: 2.3.4 |
available | [WTS] [JSN] | |||
| R1-161904 | On the need for UL transmission gaps for HD-FDD UEs in extreme coverage | discussion | Intel Corporation |
R1-ah-32047 AI: 2.3.5 |
available | [WTS] [JSN] | |||
| R1-161905 | Discussion on NPRACH baseband signal generation |
discussion revised to R1-162983 |
NEC Corporation |
R1-ah-32047 AI: 2.3.4 |
available | [WTS] [JSN] | |||
| R1-161906 | DCI format design | discussion | MediaTek Inc. |
R1-ah-32047 AI: 2.2.2 |
noted | [WTS] [JSN] | |||
| R1-161907 | Discussion on DL TBS/MCS table | discussion | MediaTek Inc. |
R1-ah-32047 AI: 2.2.3 |
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-161910 | Discussion on UCI transmission for NB-IOT | discussion | MediaTek Inc. |
R1-ah-32047 AI: 2.3.3 |
available | [WTS] [JSN] | |||
| R1-161911 | Performance evaluation of UL ACK/NACK transmission for NB-IOT | discussion | MediaTek Inc. |
R1-ah-32047 AI: 2.3.3 |
available | [WTS] [JSN] | |||
| R1-161912 | Resource allocation of NB-PDSCH | discussion | MediaTek Inc. |
R1-ah-32047 AI: 2.2.3 |
available | [WTS] [JSN] | |||
| R1-161913 | Discussions on HARQ process |
discussion revision of R1-160770 |
MediaTek Inc. |
R1-ah-32047 AI: 2.4 |
available | [WTS] [JSN] | |||
| R1-161914 | Remaining Issues on NB-MIB for NB-IoT | discussion | InterDigital Communications |
R1-ah-32047 AI: 2.2.1 |
available | [WTS] [JSN] | |||
| R1-161915 | NB-PDCCH for NB-IoT | discussion | InterDigital Communications |
R1-ah-32047 AI: 2.2.2 |
available | [WTS] [JSN] | |||
| R1-161916 | Paging for NB-IoT | discussion | InterDigital Communications |
R1-ah-32047 AI: 2.2.4 |
noted | [WTS] [JSN] | |||
| R1-161917 | Remaining Issues on RS for NB-IoT | discussion | InterDigital Communications |
R1-ah-32047 AI: 2.2.6 |
available | [WTS] [JSN] | |||
| R1-161918 | PRACH for NB-IoT | discussion | InterDigital Communications |
R1-ah-32047 AI: 2.3.4 |
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-161921 | Start timing indication method of NB-PDSCH and NB-PUSCH | discussion | Panasonic Corporation |
R1-ah-32047 AI: 2.2.2 |
noted | [WTS] [JSN] | |||
| R1-161922 | NB-MIB contents on the deployment and CRS usage | discussion | Panasonic Corporation |
R1-ah-32047 AI: 2.2.1 |
available | [WTS] [JSN] | |||
| R1-161923 | Resource indication method for NB-PUSCH with ACK/NACK only | discussion | Panasonic Corporation |
R1-ah-32047 AI: 2.3.3 |
available | [WTS] [JSN] | |||
| R1-161924 | TBS/MCS indication method for NB-PDSCH/PUSCH | discussion | Panasonic Corporation |
R1-ah-32047 AI: 2.2.2 |
available | [WTS] [JSN] | |||
| R1-161925 | Remaining Details on NB-MIB Design | discussion | Samsung |
R1-ah-32047 AI: 2.2.1 |
available | [WTS] [JSN] | |||
| R1-161926 | DCI Design | discussion | Samsung |
R1-ah-32047 AI: 2.2.2 |
available | [WTS] [JSN] | |||
| R1-161927 | Discussions on Downlink Scheduling | discussion | Samsung |
R1-ah-32047 AI: 2.2.3 |
available | [WTS] [JSN] | |||
| R1-161928 | Remaining Issues on Reference Signal Design | discussion | Samsung |
R1-ah-32047 AI: 2.2.6 |
noted | [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-161931 | Remaining Details on Uplink DM-RS Design | discussion | Samsung |
R1-ah-32047 AI: 2.3.2 |
available | [WTS] [JSN] | |||
| R1-161932 | NB-PBCH Design | other | Qualcomm Inc. |
R1-ah-32047 AI: 2.2.1 |
available | [WTS] [JSN] | |||
| R1-161933 | NB-PDCCH Design | other | Qualcomm Inc. |
R1-ah-32047 AI: 2.2.2 |
noted | [WTS] [JSN] | |||
| R1-161934 | NB-PDSCH Design | other | Qualcomm Inc. |
R1-ah-32047 AI: 2.2.3 |
noted | [WTS] [JSN] | |||
| R1-161935 | System information and paging | other | Qualcomm Inc. |
R1-ah-32047 AI: 2.2.4 |
noted | [WTS] [JSN] | |||
| R1-161936 | NB-PSS and NB-SSS Design |
other revised to R1-161981 |
Qualcomm Inc. |
R1-ah-32047 AI: 2.2.5 |
revised | [WTS] [JSN] | |||
| R1-161937 | Reference Signal Design | other | Qualcomm Inc. |
R1-ah-32047 AI: 2.2.6 |
available | [WTS] [JSN] | |||
| R1-161938 | Physical Layer Measurements | other | Qualcomm Inc. |
R1-ah-32047 AI: 2.2.7 |
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-161942 | Uplink narrowband DM-RS | other | Qualcomm Inc. |
R1-ah-32047 AI: 2.3.2 |
available | [WTS] [JSN] | |||
| R1-161943 | Uplink control information | other | Qualcomm Inc. |
R1-ah-32047 AI: 2.3.3 |
available | [WTS] [JSN] | |||
| R1-161944 | Random Access Channel Design | other | Qualcomm Inc. |
R1-ah-32047 AI: 2.3.4 |
available | [WTS] [JSN] | |||
| R1-161945 | Receiver complexity and performance for NB-IoT synchronization |
discussion revised to R1-161992 |
MediaTek Inc. |
R1-ah-32047 AI: 2.2.5 |
revised | [WTS] [JSN] | |||
| R1-161946 | Secondary synchronization signal design for NB-IoT |
discussion revision of R1-160835 |
MediaTek Inc. |
R1-ah-32047 AI: 2.2.5 |
available | [WTS] [JSN] | |||
| R1-161947 | Few issues on NB-PDSCH subframes | discussion | MediaTek Inc. |
R1-ah-32047 AI: 2.2.3 |
available | [WTS] [JSN] | |||
| R1-161948 | Remaining issues on NB-RS | discussion | MediaTek Inc. |
R1-ah-32047 AI: 2.2.6 |
available | [WTS] [JSN] | |||
| R1-161949 | Support of discontinuous resource mapping for NB-IoT DL | discussion | Intel Corporation |
R1-ah-32047 AI: 2.2.2 |
noted | [WTS] [JSN] | |||
| R1-161950 | On baseband signal generation for NB-IoT downlink | discussion | Intel Corporation |
R1-ah-32047 AI: 2.2.5 |
available | [WTS] [JSN] | |||
| R1-161951 | Remaining issues of NB-MIB design | discussion | NTT DOCOMO, INC. |
R1-ah-32047 AI: 2.2.1 |
available | [WTS] [JSN] | |||
| R1-161952 | Remaining issues of NB-PDSCH design | discussion | NTT DOCOMO, INC. |
R1-ah-32047 AI: 2.2.3 |
noted | [WTS] [JSN] | |||
| R1-161953 | Views on UL ACK/NACK transmissions for NB-IoT | discussion | NTT DOCOMO, INC. |
R1-ah-32047 AI: 2.3.3 |
available | [WTS] [JSN] | |||
| R1-161954 | Resource allocation for NB-PUSCH | discussion | Sharp |
R1-ah-32047 AI: 2.3.1 |
available | [WTS] [JSN] | |||
| R1-161955 | NB-PUSCH/NB-PDSCH coding and repetition for NB-IoT | other | CATT |
R1-ah-32047 AI: 2.2.3 |
available | [WTS] [JSN] | |||
| R1-161956 | Remaining issues on NB-MIB | other | CATT |
R1-ah-32047 AI: 2.2.1 |
noted | [WTS] [JSN] | |||
| R1-161957 | NB-PSS signal design | other | Huawei, HiSilicon |
R1-ah-32047 AI: 2.2.5 |
available | [WTS] [JSN] | |||
| R1-161958 | NB-PSS evaluation |
other revised to R1-161994 |
Huawei, HiSilicon |
R1-ah-32047 AI: 2.2.5 |
revised | [WTS] [JSN] | |||
| R1-161959 | NB-IoT - NPUSCH Resource Allocation | discussion | Ericsson | Rel-13 |
R1-ah-32047 AI: 2.3.1 |
available | [WTS] [JSN] | ||
| R1-161960 | Remaining issues on NB-IoT syncronization signal design | discussion | Nokia Networks, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell |
R1-ah-32047 AI: 2.2.5 |
available | [WTS] [JSN] | |||
| R1-161961 | Comparison of NB-PSS codes | discussion | Spreadtrum Communications |
R1-ah-32047 AI: 2.2.5 |
available | [WTS] [JSN] | |||
| R1-161962 | On the reference signal design for NB-IoT | discussion | Spreadtrum Communications |
R1-ah-32047 AI: 2.2.6 |
noted | [WTS] [JSN] | |||
| R1-161963 | Performance evaluation of NB-PBCH | discussion | Spreadtrum Communications |
R1-ah-32047 AI: 2.2.6 |
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-161965 | Discussion on NB-MIB contents for NB-IoT | other | LG Electronics |
R1-ah-32047 AI: 2.2.1 |
available | [WTS] [JSN] | |||
| R1-161966 | Discussions on NB-PDCCH for NB-IoT | other | LG Electronics |
R1-ah-32047 AI: 2.2.2 |
available | [WTS] [JSN] | |||
| R1-161967 | Discussions on NB-PDSCH design for NB-IoT | other | LG Electronics |
R1-ah-32047 AI: 2.2.3 |
available | [WTS] [JSN] | |||
| R1-161968 | Synchronization signal design for NB-IoT |
other revised to R1-162054 |
LG Electronics |
R1-ah-32047 AI: 2.2.5 |
noted | [WTS] [JSN] | |||
| R1-161969 | Discussions on measurement for NB-IoT | other | LG Electronics |
R1-ah-32047 AI: 2.2.7 |
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-161971 | Discussions on uplink narrowband DMRS for NB-IoT | other | LG Electronics |
R1-ah-32047 AI: 2.3.2 |
noted | [WTS] [JSN] | |||
| R1-161972 | Summary of email discussion [84-11] on DM-RS and phase rotation for NB-IoT | other | LG Electronics |
R1-ah-32047 AI: 2.3.2 |
noted | [WTS] [JSN] | |||
| R1-161973 | Remaining details on UCI support for NB-IoT | other | LG Electronics |
R1-ah-32047 AI: 2.3.3 |
available | [WTS] [JSN] | |||
| R1-161974 | Summary of email discussion [84-10] on UCI for NB-IoT | other | LG Electronics, Huawei, HiSilicon |
R1-ah-32047 AI: 2.3.3 |
noted | [WTS] [JSN] | |||
| R1-161975 | Remaining issues on RACH procedure for NB-IoT | other | LG Electronics |
R1-ah-32047 AI: 2.3.4 |
available | [WTS] [JSN] | |||
| R1-161976 | NB-PBCH Resource Mapping for Frequency Tracking | discussion | Sony |
R1-ah-32047 AI: 2.2.1 |
available | [WTS] [JSN] | |||
| R1-161977 | DCI parameters for NB-IoT | discussion | Sony |
R1-ah-32047 AI: 2.2.2 |
available | [WTS] [JSN] | |||
| R1-161978 | Views on DL HARQ ACK/NACK feedback for NB-IoT | discussion | KT Corp. |
R1-ah-32047 AI: 2.3.3 |
available | [WTS] [JSN] | |||
| R1-161979 | Remaining issues of uplink DMRS for NB-IoT | discussion | Lenovo (Beijing) Ltd | Rel-13 |
R1-ah-32047 AI: 2.3.2 |
available | [WTS] [JSN] | ||
| R1-161980 | On NB-PSS receiver complexity | other | Neul |
R1-ah-32047 AI: 2.2.5 |
noted | [WTS] [JSN] | |||
| R1-161981 | NB-PSS and NB-SSS Design |
other revision of R1-161936 |
Qualcomm Inc. |
R1-ah-32047 AI: 2.2.5 |
noted | [WTS] [JSN] | |||
| R1-161982 | Email summary of [84-07] Discussion on MCS/TBS/Repetition aspect of NB-IoT | discussion | Panasonic |
R1-ah-32047 AI: 2.2.2 |
withdrawn | [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-161984 | DMRS Density Effects on eNB CFO Estimation |
discussion revision of R1-161887 |
Sierra Wireless, S.A. | Rel-13 |
R1-ah-32047 AI: 2.3.2 |
noted | [WTS] [JSN] | ||
| R1-161985 | RAN1, Reply LS on available subframes for paging |
LS out LS is reply to R1-161817 LS To: RAN2 |
RAN1, Huawei | NB_IOT-Core | Rel-13 |
R1-ah-32047 AI: 2.1 |
agreed | [WTS] [JSN] | |
| R1-161986 | NB-IoT - Remaining issues for NPDSCH design |
discussion revision of R1-161825 |
Ericsson |
R1-ah-32047 AI: 2.2.3 |
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-161988 | WF on NB-MIB contents on the deployment and CRS usage | discussion | Panasonic |
R1-ah-32047 AI: 2.2.1 |
withdrawn | [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-161990 | NB-PDCCH contents | discussion | Panasonic |
R1-ah-32047 AI: 2.2.2 |
noted | [WTS] [JSN] | |||
| R1-161991 | TBS/MCS table design for NB-PDSCH and NB-PUSCH |
discussion revised to R1-161999 |
Panasonic |
R1-ah-32047 AI: 2.2.2 |
noted | [WTS] [JSN] | |||
| R1-161992 | Receiver complexity and performance for NB-IoT synchronization |
discussion revision of R1-161945 |
MediaTek Inc. |
R1-ah-32047 AI: 2.2.5 |
available | [WTS] [JSN] | |||
| R1-161993 | Details on NB-PSS and NB-SSS design for NB-IoT |
discussion revision of R1-161863 |
ZTE |
R1-ah-32047 AI: 2.2.5 |
noted | [WTS] [JSN] | |||
| R1-161994 | NB-PSS evaluation |
other revision of R1-161958 |
Huawei, HiSilicon |
R1-ah-32047 AI: 2.2.5 |
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-161996 | WF on UL DMRS for single tone transmission | discussion | Huawei, HiSilicon |
R1-ah-32047 AI: 2.3.2 |
noted | [WTS] [JSN] | |||
| R1-161997 | WF on ACK/NACK transmission for NB-PDSCH | discussion | Huawei, HiSilicon |
R1-ah-32047 AI: 2.3.3 |
noted | [WTS] [JSN] | |||
| R1-161998 | List of Open Issues in RAN2 NBIoT | discussion | Vodafone |
R1-ah-32047 AI: 2.4 |
noted | [WTS] [JSN] | |||
| R1-161999 | TBS/MCS table design for NB-PDSCH and NB-PUSCH |
discussion revision of R1-161991 revised to R1-162005 |
Panasonic |
R1-ah-32047 AI: 2.2.2 |
revised | [WTS] [JSN] | |||
| R1-162000 | WF on NB-RS | discussion | Intel Corporation, ALU, ASB, Huawei, HiSi, Interdigital, MediaTek, Nokia, Panasonic, Samsung |
R1-ah-32047 AI: 2.2.6 |
noted | [WTS] [JSN] | |||
| R1-162001 | WF on phase rotation of single tone NB-PUSCH | discussion | Huawei, HiSilicon |
R1-ah-32047 AI: 2.3.2 |
noted | [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-162005 | TBS/MCS table design for NB-PDSCH and NB-PUSCH |
discussion revision of R1-161999 revised to R1-162013 |
Panasonic |
R1-ah-32047 AI: 2.2.2 |
revised | [WTS] [JSN] | |||
| R1-162006 | [Draft] WF on NB-SIB1 |
discussion revised to R1-162009 |
Huawei, HiSilicon |
R1-ah-32047 AI: 2.2.4 |
revised | [WTS] [JSN] | |||
| R1-162007 | WF from offline discussion on NB-SS |
discussion revised to R1-162047 |
Intel |
R1-ah-32047 AI: 2.2.5 |
noted | [WTS] [JSN] | |||
| R1-162008 | [Draft] WF on NB-PDCCH |
discussion revised to R1-162015 |
Huawei, HiSilicon |
R1-ah-32047 AI: 2.2.2 |
noted | [WTS] [JSN] | |||
| R1-162009 | WF on NB-SIB1 details |
discussion revision of R1-162006 |
Huawei, HiSilicon |
R1-ah-32047 AI: 2.2.4 |
agreed | [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-162011 | WF on PHR for NB-IoT |
discussion revised to R1-162045 |
Huawei, HiSilicon |
R1-ah-32047 AI: 2.3.5 |
revised | [WTS] [JSN] | |||
| R1-162012 | WF on open loop power control | discussion | Huawei, HiSilicon |
R1-ah-32047 AI: 2.3.5 |
noted | [WTS] [JSN] | |||
| R1-162013 | TBS/MCS table design for NB-PDSCH and NB-PUSCH |
discussion revision of R1-162005 |
Panasonic |
R1-ah-32047 AI: 2.2.3 |
agreed | [WTS] [JSN] | |||
| R1-162014 | [DRAFT] LS on NB-SIB1 Details | discussion | Huawei | NB_IOT-Core | Rel-13 |
R1-ah-32047 AI: 2.2.4 |
withdrawn | [WTS] [JSN] | |
| R1-162015 | WF on NB-PDCCH |
discussion revision of R1-162008 |
Huawei, HiSilicon |
R1-ah-32047 AI: 2.2.2 |
agreed | [WTS] [JSN] | |||
| R1-162016 | WF on NB-PSS | discussion | Intel Corporation, Acorn Technologies, CEWiT, ETRI, IITH, InterDigital, ITL, KT Corporation, Lenovo, Reliance-Jio, Samsung, Sequans Communications, Sierra Wireless, WILUS Inc. |
R1-ah-32047 AI: 2.2.5 |
available | [WTS] [JSN] | |||
| R1-162017 | [Draft] WF on PDSCH Power Offset | discussion | Qualcomm |
R1-ah-32047 AI: 2.2.6 |
noted | [WTS] [JSN] | |||
| R1-162018 | WF on LTE CRS Signaling Support | discussion | Intel, Ericsson, Sony, LG, Nokia, ALU, ASB, Huawei, HiSi, Interdigital, CATT, Sierra Wireless, Spreadtrum, ZTE |
R1-ah-32047 AI: 2.2.6 |
noted | [WTS] [JSN] | |||
| R1-162019 | WF on NB-RS Power Allocation | discussion | Intel, Ericsson, Sony, Nokia, ALU, ASB, Qualcomm, ZTE, MediaTek, Sierra Wireless, Spreadtrum, Panasonic, Vodafone |
R1-ah-32047 AI: 2.2.6 |
noted | [WTS] [JSN] | |||
| R1-162020 | WF on mode indication in MIB | discussion | Ericsson |
R1-ah-32047 AI: 2.2.1 |
noted | [WTS] [JSN] | |||
| R1-162021 | WF on PRB indexing in MIB | discussion | Ericsson, LGE |
R1-ah-32047 AI: 2.2.1 |
agreed | [WTS] [JSN] | |||
| R1-162022 | WF on ACK/NACK transmission of NB-PDSCH | discussion | Huawei, HiSilicon, MediaTek, Panasonic |
R1-ah-32047 AI: 2.3.3 |
noted | [WTS] [JSN] | |||
| R1-162023 | WF on UL DM-RS Sequence Generation | discussion | Qualcomm |
R1-ah-32047 AI: 2.3.2 |
noted | [WTS] [JSN] | |||
| R1-162024 | WF on UL Phase Rotation | discussion | Qualcomm, LGE |
R1-ah-32047 AI: 2.3.2 |
noted | [WTS] [JSN] | |||
| R1-162025 | WF on DM-RS design for NB-PUSCH | discussion | LGE |
R1-ah-32047 AI: 2.3.2 |
noted | [WTS] [JSN] | |||
| R1-162026 | [Draft] WF on DM-RS for multi-tone transmission | discussion | LGE |
R1-ah-32047 AI: 2.3.2 |
noted | [WTS] [JSN] | |||
| R1-162027 | WF on PRACH | discussion | Nokia Networks, ALU, ASB |
R1-ah-32047 AI: 2.3.4 |
noted | [WTS] [JSN] | |||
| R1-162028 | WF on SI Scheduling | discussion | Nokia Networks, ALU, ASB, Intel, Ericsson |
R1-ah-32047 AI: 2.2.4 |
noted | [WTS] [JSN] | |||
| R1-162029 | WF on Starting Subframe of Paging CSS for NB-IoT | discussion | Ericsson |
R1-ah-32047 AI: 2.2.4 |
noted | [WTS] [JSN] | |||
| R1-162030 | WF on DL Transmission Gap for NB-IoT | discussion | Ericsson, Intel, Sony, ZTE |
R1-ah-32047 AI: 2.2.3 |
noted | [WTS] [JSN] | |||
| R1-162031 | WF on MIB content |
discussion revised to R1-162059 |
ZTE, Ericsson, MediaTek, Intel |
R1-ah-32047 AI: 2.2.1 |
revised | [WTS] [JSN] | |||
| R1-162032 | WF on indicating FDD/TDD in MIB | discussion | Qualcomm, Ericsson, IITH, Samsung, CATT, MediaTek, Panasonic, LG |
R1-ah-32047 AI: 2.2.1 |
noted | [WTS] [JSN] | |||
| R1-162033 | WF on NB-PRACH sequence | discussion | Huawei, HiSilicon, Neul, Intel, Ericsson |
R1-ah-32047 AI: 2.3.4 |
noted | [WTS] [JSN] | |||
| R1-162034 | WF on PO for paging | discussion | ZTE, Ericsson |
R1-ah-32047 AI: 2.2.4 |
noted | [WTS] [JSN] | |||
| R1-162035 | WF on usage of NB-SSS for enhanced channel estimation |
discussion revision of R1-162049 revised to R1-162049 |
Spreadtrum, Huawei |
R1-ah-32047 AI: 2.2.5 |
revised | [WTS] [JSN] | |||
| R1-162036 | WF on NB-IoT Multi-Carrier Operation | discussion | Intel Corporation, MediaTek, Ericsson, ALU, ASB, Nokia, Panasonic, Huawei, HiSilicon, Sony |
R1-ah-32047 AI: 2.2.3 |
noted | [WTS] [JSN] | |||
| R1-162037 | WF on timing relationships for random access | discussion | Huawei, HiSilicon |
R1-ah-32047 AI: 2.3.4 |
noted | [WTS] [JSN] | |||
| R1-162038 | RAN1 agreements for Rel-13 NB-IoT | other | ETSI | NB_IOT-Core | Rel-13 |
R1-ah-32047 AI: 2.4 |
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-162043 | WF on UCI | discussion | LGE |
R1-ah-32047 AI: 2.3.3 |
noted | [WTS] [JSN] | |||
| R1-162044 | WF on uplink power control of NB-IoT | discussion | Huawei, HiSilicon |
R1-ah-32047 AI: 2.3.5 |
noted | [WTS] [JSN] | |||
| R1-162045 | WF on PHR of NB-IoT |
discussion revision of R1-162011 |
Huawei, HiSilicon, Ericsson |
R1-ah-32047 AI: 2.3.5 |
noted | [WTS] [JSN] | |||
| R1-162046 | [DRAFT] LS on direct SI update indication for NB-IoT |
discussion revised to R1-162068 |
Ericsson, Huawei | NB_IOT-Core | Rel-13 |
R1-ah-32047 AI: 2.2.4 |
revised | [WTS] [JSN] | |
| R1-162047 | WF from offline discussion on NB-SS |
discussion revision of R1-162007 |
Intel |
R1-ah-32047 AI: 2.2.5 |
noted | [WTS] [JSN] | |||
| R1-162048 | Summary of evaluation results for NB-PSS | discussion | Huawei, HiSilicon, Neul, Ericsson, MediaTek, Spreadtrum |
R1-ah-32047 AI: 2.2.5 |
noted | [WTS] [JSN] | |||
| R1-162049 | WF on usage of NB-SSS for enhanced channel estimation |
discussion revision of R1-162035 revised to R1-162035 |
Spreadtrum, Huawei, HiSilicon |
R1-ah-32047 AI: 2.2.5 |
available | [WTS] [JSN] | |||
| R1-162050 | WF on NB-PRACH sequence | discussion | ZTE |
R1-ah-32047 AI: 2.3.4 |
noted | [WTS] [JSN] | |||
| R1-162051 | WF on including partial HyperSFN in MIB | discussion | Ericsson, ZTE, Huawei, HiSilicon |
R1-ah-32047 AI: 2.2.1 |
noted | [WTS] [JSN] | |||
| R1-162052 | Timing advance for NB-IoT | discussion | Ericsson |
R1-ah-32047 AI: 2.3.4 |
noted | [WTS] [JSN] | |||
| R1-162053 | WF on the number of repetitions for NB-PDSCH and NB-PUSCH | discussion | Huawei, HiSilicon |
R1-ah-32047 AI: 2.2.3 |
available | [WTS] [JSN] | |||
| R1-162054 | Synchronization signal design for NB-IoT |
discussion revision of R1-161968 |
LG Electronics |
R1-ah-32047 AI: 2.2.5 |
available | [WTS] [JSN] | |||
| R1-162055 | UL grant in RAR | discussion | Huawei, HiSilicon |
R1-ah-32047 AI: 2.3.4 |
noted | [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-162057 | WF on NB-IoT Multi-Carrier Operation in Standalone Mode | discussion | Intel Corporation, MediaTek, Ericsson, ZTE, Sony, Fujitsu |
R1-ah-32047 AI: 2.2.3 |
noted | [WTS] [JSN] | |||
| R1-162058 | Evaluation on cross correlation of DMRS sequence | discussion | LGE |
R1-ah-32047 AI: 2.3.2 |
noted | [WTS] [JSN] | |||
| R1-162059 | WF on MIB content |
discussion revision of R1-162031 |
ZTE, Ericsson, MediaTek, Intel |
R1-ah-32047 AI: 2.2.1 |
noted | [WTS] [JSN] | |||
| R1-162060 | Summary of NB-PUSCH Subcarrier Allocation | discussion | Huawei, HiSilicon |
R1-ah-32047 AI: 2.3.1 |
noted | [WTS] [JSN] | |||
| R1-162061 | WF on UL ACK/NAK transmission | discussion | Qualcomm, Mediatek, Huawei, HiSilicon |
R1-ah-32047 AI: 2.3.3 |
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-162063 | WF on NB-PSS Design | discussion | Huawei, HiSilicon, Ericsson, MediaTek, Neul, ASTRI, CATR, Beijing Xinwei Telecom Techn, Potevio, Huawei Device , Coolpad, TD Tech Ltd, ST Microelectronics, Chengdu TD Tech Ltd, China Unicom, Telecom Italia S.p.A, Spreadtrum, CATT, u-blox AG, Deutsche Telekom AG |
R1-ah-32047 AI: 2.2.5 |
noted | [WTS] [JSN] | |||
| R1-162064 | Summary of NB-PUSCH Subcarrier Allocation | discussion | Huawei, HiSilicon |
R1-ah-32047 AI: 2.3.1 |
available | [WTS] [JSN] | |||
| R1-162065 | LS on NB-IoT |
LS out LS To: RAN2 |
RAN1, Huawei | NB_IOT-Core | Rel-13 |
R1-ah-32047 AI: 2.4 |
agreed | [WTS] [JSN] | |
| R1-162066 | LS on NB-IoT |
LS out LS To: RAN4 |
RAN1, Huawei | NB_IOT-Core | Rel-13 |
R1-ah-32047 AI: 2.4 |
agreed | [WTS] [JSN] | |
| R1-162067 | WF on reference point of NB-PDSCH/NB-PUSH | discussion | Panasonic, Mediatek, Interdigital, Sony, DOCOMO, Ericsson, Sierra |
R1-ah-32047 AI: 2.2.2 |
noted | [WTS] [JSN] | |||
| R1-162068 | LS on direct SI update indication for NB-IoT |
LS out LS To: RAN2 revision of R1-162046 |
RAN1, Ericsson, Huawei | NB_IOT-Core | Rel-13 |
R1-ah-32047 AI: 2.2.4 |
agreed | [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] | |
| R1-162070 | LS on RRC parameter list for NB-IoT |
LS out LS To: RAN2 |
RAN1, Huawei | NB_IOT-Core | Rel-13 |
R1-ah-32047 AI: 2.4 |
agreed | [WTS] [JSN] | |
| R1-162071 | NB-IoT L1 parameters spreadsheet | other | Huawei | NB_IOT-Core | Rel-13 |
R1-ah-32047 AI: 2.4 |
agreed | [WTS] [JSN] |
272 documents (1.090234041214 seconds)