IP Library Granted Patent US 12,302,301
Granted Patent B2
US 12,302,301 · App. 17/903,695 · Granted May 13, 2025

Techniques and apparatuses for carrier management

Inventors: Chao Wei (Beijing, CN); Alberto Rico Alvarino (San Diego, CA); Le Liu (San Jose, CA); Wanshi Chen (San Diego, CA); Xiao Feng Wang (San Diego, CA); Hao Xu (Beijing, CN)
Assignee: QUALCOMM Incorporated
H04W72/0453H04L5/0098H04W74/0833
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,302,301
App. No.
17/903,695
Granted
May 13, 2025
Kind
B2
Abstract

A method, base station (BS), user equipment (UE), apparatus, and computer program product for wireless communication are provided. A BS and a UE may communicate using a narrowband Internet of Things (NB-IoT) communication system. However, a frequency, time, and/or power associated with transmission of a SIB1-NB on a non-anchor carrier may not be configured for NB-IoT. In some aspects, the BS may determine parameters, such as a time domain location parameter, a frequency domain location parameter, a quantity of repetitions, a power boosting parameter, and/or the like for a transmission in NB-IoT. In some aspects, a UE may determine to transmit a connection request message on a different carrier than a random access channel message.

Claims (44)

1. A method of wireless communication, comprising:

transmitting, by a base station, a master information block message including an indicator identifying a frequency domain location parameter or a time domain location parameter for a non-anchor carrier or an anchor carrier; and

transmitting, by the base station and using the non-anchor carrier or the anchor carrier, a system information block type 1 (SIB1) message to a user equipment in accordance with the frequency domain location parameter or the time domain location parameter,

wherein the non-anchor carrier is in at least one first physical resource block of a resource block group, and

wherein the non-anchor carrier is in at least one second physical resource block, of the resource block group, that is contiguous to the at least one first physical resource block without any other physical resource blocks of the resource block group between the at least one first physical resource block and the at least one second physical resource block.

2. The method of claim 1 , wherein the SIB1 message is transmitted in a subframe 0 and a subframe 5 of alternating radio frames of the non-anchor carrier.

3. The method of claim 1 , wherein the SIB1 message is transmitted in a subframe 0 of alternating radio frames of the anchor carrier.

4. The method of claim 1 , wherein the non-anchor carrier and the anchor carrier are associated with a common guard band.

5. The method of claim 1 , wherein the at least one second physical resource block is an inband physical resource block.

6. The method of claim 1 , wherein the non-anchor carrier is in a first guardband and the anchor carrier is in a second guardband that is different than the first guardband.

7. The method of claim 1 , wherein a size or a value for the indicator is based at least in part on a deployment mode, and wherein the deployment mode is at least one of:

an in-band deployment mode,

a guard band deployment mode, or

a stand-alone deployment mode.

8. The method of claim 1 , wherein the frequency domain location parameter or the time domain location parameter is based at least in part on an offset indicator identifying a resource block offset with respect to the anchor carrier.

9. The method of claim 1 , a frequency domain location for the non-anchor carrier is opposite a frequency domain location of the anchor carrier with respect to a center frequency.

10. The method of claim 1 , wherein a subframe or frame for the SIB1 message is determined based at least in part on a cell identifier or a repetition configuration.

11. A method of wireless communication, comprising:

transmitting, by a base station, a master information block message including an indicator identifying a frequency domain location parameter or a time domain location parameter for a non-anchor carrier or an anchor carrier; and

transmitting, by the base station and using the non-anchor carrier or the anchor carrier, a system information block type 1 (SIB1) message to a user equipment in accordance with the frequency domain location parameter or the time domain location parameter,

wherein the frequency domain location parameter or the time domain location parameter is based at least in part on an offset indicator identifying a resource block offset with respect to the anchor carrier,

wherein the offset indicator is based at least in part on a resource block group, and

wherein the anchor carrier and the non-anchor carrier are in resource blocks of the resource block group.

12. A base station for wireless communication, comprising: a memory; and one or more processors coupled to the memory and configured to cause the base station to:

transmit a master information block message including an indicator identifying a frequency domain location parameter or a time domain location parameter for a non-anchor carrier or an anchor carrier; and

transmit, using the non-anchor carrier or the anchor carrier, a system information block type 1 (SIB1) message to a user equipment in accordance with the frequency domain location parameter or the time domain location parameter,

wherein the non-anchor carrier is in at least one first physical resource block, of a resource block group, and

wherein the non-anchor carrier is in at least one second physical resource block, of the resource block group, that is contiguous to the at least one first physical resource block without any other physical resource blocks of the resource block group between the at least one first physical resource block and the at least one second physical resource block.

13. The base station of claim 12 , wherein the one or more processors are configured to cause the base station to transmit the SIB1 message in a subframe 0 and a subframe 5 of alternating radio frames of the non-anchor carrier.

14. The base station of claim 12 , wherein the one or more processors are configured to cause the base station to transmit the SIB1 message in a subframe 0 of alternating radio frames of the anchor carrier.

15. The base station of claim 12 , wherein the non-anchor carrier is in a first guardband and the anchor carrier is in a second guardband that is different than the first guardband.

16. The base station of claim 12 , wherein a size or a value for the indicator is based at least in part on a deployment mode, and wherein the deployment mode is at least one of:

an in-band deployment mode,

a guard band deployment mode, or

a stand-alone deployment mode.

17. The base station of claim 12 , a frequency domain location for the non-anchor carrier is opposite a frequency domain location of the anchor carrier with respect to a center frequency.

18. The base station of claim 12 , wherein the one or more processors are configured to cause the base station to determine a subframe or frame for the SIB1 message based at least in part on a cell identifier or a repetition configuration.

19. The base station of claim 12 , wherein the non-anchor carrier and the anchor carrier are associated with a common guard band, or wherein the at least one second physical resource block is an inband physical resource block.

20. A base station for wireless communication, comprising: a memory; and one or more processors coupled to the memory and configured to cause the base station to:

transmit a master information block message including an indicator identifying a frequency domain location parameter or a time domain location parameter for a non-anchor carrier or an anchor carrier; and

transmit, using the non-anchor carrier or the anchor carrier, a system information block type 1 (SIB1) message to a user equipment in accordance with the frequency domain location parameter or the time domain location parameter,

wherein the frequency domain location parameter or the time domain location parameter is based at least in part on an offset indicator identifying a resource block offset with respect to the anchor carrier,

wherein the offset indicator is based at least in part on a resource block group, and

wherein the anchor carrier and the non-anchor carrier are in resource blocks of the resource block group.

Assignments (2)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 28, 2022
From: WEI, CHAO; RICO ALVARINO, ALBERTO; LIU, LE; CHEN, WANSHI; WANG, XIAO FENG; XU, HAO
To: QUALCOMM INCORPORATED
Reel/Frame 062220/0875 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 21, 2022
From: WEI, CHAO; RICO ALVARINO, ALBERTO; LIU, LE; CHEN, WANSHI; XU, HAO; WANG, XIAO FENG
To: QUALCOMM INCORPORATED
Reel/Frame 062167/0480 →
Priority Claims (1)
WO PCT/CN2017/111308 · Nov 16, 2017 · international
Continuity (2)
Continuation 16756729
Related Publication 20220417931A1 · Dec 29, 2022
References Cited (189)
US 8705461B2 · Bala · 2014 [cited by examiner]
US 9119132B2 · Luo et al. · 2015 [cited by applicant]
US 9560635B2 · Wei et al. · 2017 [cited by applicant]
US 9713026B2 · Gaal et al. · 2017 [cited by applicant]
US 10104651B2 · Chen et al. · 2018 [cited by applicant]
US 10165423B2 · Rico Alvarino et al. · 2018 [cited by applicant]
US 10397889B2 · Shin · 2019 [cited by examiner]
US 10404360B2 · Sridharan et al. · 2019 [cited by applicant]
US 10420087B2 · Shin · 2019 [cited by examiner]
US 10420102B2 · Somichetty et al. · 2019 [cited by applicant]
US 10469158B2 · Sridharan et al. · 2019 [cited by applicant]
US 10469159B2 · Sridharan et al. · 2019 [cited by applicant]
US 10498435B2 · Sridharan et al. · 2019 [cited by applicant]
US 10524258B2 · Somichetty et al. · 2019 [cited by applicant]
US 10542538B2 · Somichetty et al. · 2020 [cited by applicant]
US 10932260B2 · Somichetty et al. · 2021 [cited by applicant]
US 10939432B2 · Somichetty et al. · 2021 [cited by applicant]
US 10939475B2 · Rathonyi · 2021 [cited by examiner]
US 10945265B2 · Somichetty et al. · 2021 [cited by applicant]
US 10958337B2 · Sridharan et al. · 2021 [cited by applicant]
US 11050483B2 · Sridharan et al. · 2021 [cited by applicant]
US 11134477B2 · Terry · 2021 [cited by examiner]
US 11523427B2 · Lee · 2022 [cited by examiner]
US 20090093257A1 · Rinne et al. · 2009 [cited by applicant]
US 20110310856A1 · Hariharan et al. · 2011 [cited by applicant]
US 20120100847A1 · Rahman · 2012 [cited by applicant]
US 20130083749A1 · Xu et al. · 2013 [cited by applicant]
US 20130250882A1 · Dinan · 2013 [cited by applicant]
US 20130272215A1 · Khoryaev et al. · 2013 [cited by applicant]
US 20130315159A1 · Xia et al. · 2013 [cited by applicant]
US 20140029568A1 · Wang et al. · 2014 [cited by applicant]
US 20140119332A1 · Kim et al. · 2014 [cited by applicant]
US 20140204961A1 · Hooli et al. · 2014 [cited by applicant]
US 20140307685A1 · Takano et al. · 2014 [cited by applicant]
US 20140328230A1 · Park et al. · 2014 [cited by applicant]
US 20150078220A1 · Hu et al. · 2015 [cited by applicant]
US 20150124663A1 · Chen et al. · 2015 [cited by applicant]
US 20150327324A1 · Wei et al. · 2015 [cited by applicant]
US 20160127952A1 · You et al. · 2016 [cited by applicant]
US 20160198450A1 · Wei et al. · 2016 [cited by applicant]
US 20160315752A1 · Chen et al. · 2016 [cited by applicant]
US 20160345118A1 · Oh · 2016 [cited by applicant]
US 20160366007A1 · Hwang et al. · 2016 [cited by applicant]
US 20170012755A1 · Wang et al. · 2017 [cited by applicant]
US 20170041122A1 · Li et al. · 2017 [cited by applicant]
US 20170070968A1 · Kim et al. · 2017 [cited by applicant]
US 20170163396A1 · Blankenship · 2017 [cited by applicant]
US 20170180086A1 · Xiong et al. · 2017 [cited by applicant]
US 20170187563A1 · Shin et al. · 2017 [cited by applicant]
US 20170195102A1 · Xiong et al. · 2017 [cited by applicant]
US 20170202025A1 · Ouchi et al. · 2017 [cited by applicant]
US 20170251443A1 · Shin et al. · 2017 [cited by applicant]
US 20170273059A1 · You et al. · 2017 [cited by applicant]
US 20170279472A1 · Wong et al. · 2017 [cited by applicant]
US 20170311276A1 · Tsai et al. · 2017 [cited by applicant]
US 20170373900A1 · Adhikary et al. · 2017 [cited by applicant]
US 20180007667A1 · You et al. · 2018 [cited by applicant]
US 20180014284A1 · Yi et al. · 2018 [cited by applicant]
US 20180049047A1 · Lin et al. · 2018 [cited by applicant]
US 20180049151A1 · Yoon et al. · 2018 [cited by applicant]
US 20180062699A1 · Horiuchi et al. · 2018 [cited by applicant]
US 20180069593A1 · Yi · 2018 [cited by applicant]
US 20180077703A1 · Sun et al. · 2018 [cited by applicant]
US 20180124789A1 · Yerramalli et al. · 2018 [cited by applicant]
US 20180176893A1 · Zhang et al. · 2018 [cited by applicant]
US 20180241495A1 · Xue et al. · 2018 [cited by applicant]
US 20180248671A1 · Bhattad et al. · 2018 [cited by applicant]
US 20180287846A1 · Kim et al. · 2018 [cited by applicant]
US 20180316464A1 · Stern-Berkowitz et al. · 2018 [cited by applicant]
US 20180317244A1 · Um et al. · 2018 [cited by applicant]
US 20190013984A1 · Liang et al. · 2019 [cited by applicant]
US 20190069277A1 · Awad et al. · 2019 [cited by applicant]
US 20190124663A1 · Liu et al. · 2019 [cited by applicant]
US 20190150164A1 · Nam et al. · 2019 [cited by applicant]
US 20190182021A1 · Shokri Razaghi et al. · 2019 [cited by applicant]
US 20190215872A1 · Park et al. · 2019 [cited by applicant]
US 20190253231A1 · Park · 2019 [cited by examiner]
US 20190349138A1 · Hosseini et al. · 2019 [cited by applicant]
US 20200059390A1 · Zhang · 2020 [cited by examiner]
US 20200112955A1 · Somichetty et al. · 2020 [cited by applicant]
US 20200396722A1 · Han · 2020 [cited by examiner]
US 20210099944A1 · Hoglund et al. · 2021 [cited by applicant]
US 20210105821A1 · Niu et al. · 2021 [cited by applicant]
US 20210111824A1 · Park · 2021 [cited by examiner]
US 20210112591A1 · Lee et al. · 2021 [cited by applicant]
US 20210144641A1 · Sun · 2021 [cited by examiner]
US 20210400667A1 · Wei et al. · 2021 [cited by applicant]
US 20220353660A1 · Ye · 2022 [cited by examiner]
US 20240243893A1 · Park · 2024 [cited by examiner]
CN 1404668A · 2003 [cited by applicant]
CN 102035786A · 2011 [cited by applicant]
CN 103457711A · 2013 [cited by applicant]
CN 103563273A · 2014 [cited by applicant]
CN 103621032A · 2014 [cited by applicant]
CN 104904135A · 2015 [cited by applicant]
CN 105612709A · 2016 [cited by applicant]
CN 105656597A · 2016 [cited by applicant]
CN 105794287A · 2016 [cited by applicant]
CN 105827371A · 2016 [cited by applicant]
CN 106160974A · 2016 [cited by applicant]
CN 106162874A · 2016 [cited by applicant]
CN 107046721A · 2017 [cited by applicant]
EP 3264829A1 · 2018 [cited by applicant]
EP 3300287A1 · 2018 [cited by applicant]
EP 3522433A1 · 2019 [cited by applicant]
EP 3439389B1 · 2021 [cited by applicant]
JP 2017139673A · 2017 [cited by applicant]
JP 2018533877A · 2018 [cited by applicant]
JP 2019500795A · 2019 [cited by applicant]
JP 2020507277A · 2020 [cited by applicant]
JP 2020513227A · 2020 [cited by applicant]
JP 2021503206A · 2021 [cited by applicant]
KR 20030018280A · 2003 [cited by applicant]
KR 20160137347A · 2016 [cited by applicant]
KR 20170003547A · 2017 [cited by applicant]
KR 20170012150A · 2017 [cited by applicant]
WO 2009049167 · 2009 [cited by applicant]
WO 2014042373A1 · 2014 [cited by applicant]
WO 2014165838 · 2014 [cited by applicant]
WO 2014186456 · 2014 [cited by applicant]
WO 2015018368A1 · 2015 [cited by applicant]
WO 2016119162A1 · 2016 [cited by applicant]
WO 2016119446A1 · 2016 [cited by applicant]
WO 2016123292A1 · 2016 [cited by applicant]
WO 2016154835A1 · 2016 [cited by applicant]
WO 2016159697A1 · 2016 [cited by applicant]
WO 2016172293 · 2016 [cited by applicant]
WO 2016182639A1 · 2016 [cited by applicant]
WO 2016186044A1 · 2016 [cited by applicant]
WO 2016190537A1 · 2016 [cited by applicant]
WO 2016190620A1 · 2016 [cited by applicant]
WO 2016209833A1 · 2016 [cited by applicant]
WO 2017011093 · 2017 [cited by applicant]
WO 2017011105 · 2017 [cited by applicant]
WO 2017078802A1 · 2017 [cited by applicant]
WO 2017136003A1 · 2017 [cited by applicant]
WO 2017167839A1 · 2017 [cited by applicant]
WO 2018026199A1 · 2018 [cited by applicant]
WO 2018030936A1 · 2018 [cited by applicant]
WO 2018152027 · 2018 [cited by applicant]
WO 2019096431A1 · 2019 [cited by applicant]
3GPP TS 36.211: “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Physical Channels and Modulation (Release 14)”, V14.1.0 (Dec.… [cited by applicant]
3GPP TS 36.213: “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Physical Layer Procedures (Release 14)”, V14.1.0 (Dec. 2016),… [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (EUTRA); Physical Channels and Modulation (Release 14)”, 3GPP Standard; 3GPP TS 36.211,… [cited by applicant]
Alcatel-Lucent Shanghai Bell: “Considerations of TDD NB-IOT” [online], 3GPP TSG RAN WG1 adhoc_LTE_NB-IOT_1601 R1-160181, Nov. 8, 2016, 4 Pages, Internet URL: http://www.3gpp.org/ftp/tsg_ran/WG1_RL1/TSGR1_AH/LTE_NB-IOT_1… [cited by applicant]
Ericsson: “NB-IoT—Synchronization Channel Design”, 3GPP TSG-RAN WG1 NB-IoT AdHoc, R1-160079, Jan. 18-22, 2016, Budapest, Hungary, pp. 1-6. [cited by applicant]
Ericsson: “Power Consumption and Latency Reduction by Increasing the Maximum NPUSCH Transport Block Size”, 3GPP TSG-RAN1#86bis, R1-1610399, Oct. 10-14, 2016, pp. 1-4. [cited by applicant]
Huawei, et al., “DCI for NB-IoT”, 3GPPTSG-RAN WG1 NB-IoT Ad-Hoc Meeting, 3GPP Draft, R1-160032, 3rd Generation Partnership Project (3GPP), Mobile Competence Centre, 650, Route Des Lucioles, F-06921 Sophia-Antipolis Cede… [cited by applicant]
Huawei., et al., “On Multi-PRB Operation”, 3GPP TSG RAN WG1Meeting #84, R1-161039, 3rd Generation Partnership Project, Mobile Competence Centre, 650, Route Des Lucioles, F-06921, Sophia-Antipolis Cedex, France, vol. RAN… [cited by applicant]
Huawei., et al., “Remaining Details of NB-PDCCH Design”, 3GPP TSG RAN WG1 NB-IoT Ad-Hoc Meeting #2, R1-161802, Sophia-Antipolis, France, Mar. 22-24, 2016, 5 Pages. [cited by applicant]
Huawei, et al., “TDD Support for NB-IoT in Rel-15”, 3GPP TSG RAN Meeting #74, 3GPP draft, RP-162161, 3rd Generation Partnership Project (3GPP), Mobile Competence Centre; 650, Route Des Lucioles; F-06921 Sophia-Antipolis… [cited by applicant]
Huawei, et al., “TS 36.300 Section 5 for NB-IoT up to RAN1#84,” 3GPP Draft; R1-161554, 3rd Generation Partnership Project (3GPP), Mobile Competence Centre; 650, Route Des Lucioles; F-06921 Sophia-Antipolis Cedex; France… [cited by applicant]
Huawei, et al., “Synchronization Signal Design”, 3GPP Draft, 3GPP TSG RAN WG1 Meeting #84, R1-160311, 3rd Generation Partnership Project (3GPP), Mobile Competence Centre, 650, Route Des Lucioles, F-06921 Sophia-Antipoli… [cited by applicant]
Intel Corporation: “Design of Synchronization Signals and System Information for TDD Support in feNB-IoT”, 3GPP Draft, R1-1717347, 3GPP TSG RAN WG1 Meeting #90bis, 3rd Generation Partnership Project (3GPP), Mobile Compe… [cited by applicant]
Intel Corporation: “Frame Structure for New Radio Interface,” 3GPP TSG RAN WG1 Meeting #84bis, R1-162726, Busan, Korea Apr. 11-15, 2016, (Apr. 1, 2016), 5 pages. [cited by applicant]
Intel Corporation: “On Layer 1 Design and Procedures for NB-IoT Downlink”, 3GPP TSG RAN WG1 Meeting #83, R1-156529, Nov. 7, 2015, 8 Pages. [cited by applicant]
International Search Report and Written Opinion—PCT/CN2018/103208—ISA/EPO—Oct. 29, 2018. [cited by applicant]
International Search Report and Written Opinion—PCT/CN2017/111308—ISA/EPO—Jul. 30, 2018. [cited by applicant]
Lenovo., et al., “Views on TDD Downlink Aspect for R.15 NBIoT,” 3GPP TSG RAN WG1 Meeting #90bis, R1-1717440, Prague, P.R. Czech Oct. 9-13, 2017 (Oct. 13, 2017), 5 pages. [cited by applicant]
LG Electronics: “Discussion on Multiple PRB Operation for SIB1 Transmission” [online], 3GPP Draft, 3GPP TSG RAN1 #84, R1-160615 NB-SIB, 3rd Generation Partnership Project (3GPP), Mobile Competence Centre, 650, Route Des… [cited by applicant]
LG Electronics: “Discussion on PDSCH Transmission for MTC”, 3GPP TSG RAN WG1 Meeting #82, R1-154235, Beijing, China, 3GPP (Server Release Date: Aug. 14, 2015), pp. 1-11, Aug. 24, 2015-Aug. 28, 2015. [cited by applicant]
Nokia, et al., “Existing Downlink Signals for OTDOA Positioning in NB-IoT”, 3GPP TSG RAN WG1 Meeting #86bis, 3GPP Draft, R1-1608881, 3rd Generation Partnership Project (3GPP), Mobile Competence Centre, 650, Route Des Lu… [cited by applicant]
Nokia Networks., et al., “Synchronization Signal Design for NB-IoT”, [online], 3GPP TSG-RAN WG1 # 84 R1-160449, Feb. 5, 2016, 7 Pages, Retrieved from the Internet URL: http://www.3gpp.org/ftp/tsg_ran/WG1_RL1/ TSGR1_84/D… [cited by applicant]
Nokia Networks, et al., “Synchronization Signal Design for NB-IoT”, 3GPP TSG-RAN WG1 Meeting # 84, 3GPP Draft, R1-161104, 3rd Generation Partnership Project (3GPP), vol. RAN WG1, No. St Julian's, Malta, Feb. 15, 2016-Fe… [cited by applicant]
Nokia Networks: “On the Synchronization Signal Design for NB-IoT”, 3GPP TSG-RAN WG1 Meeting #83, 3GPP Draft, R1-157274, 3rd Generation Partnership Project (3GPP), Mobile Competence Centre, 650, Route Des Lucioles, F-069… [cited by applicant]
Nokia Networks: “On the TDD Support for NB-IoT”, 3GPP Draft, 3GPP TSG RAN WG1 NB-IoT Adhoc, R1-160011, 3rd Generation Partnership Project (3GPP), Mobile Competence Centre, 650, Route Des Lucioles, F-06921 Sophia-Antipol… [cited by applicant]
Nokia Networks: “Synchronization Signal Design for NB-IoT”, 3GPP TSG-RAN WG1 NB-IoT Adhoc, R1-160012, Budapest, Hungary, Jan. 18-20, 2016, 7 Pages. [cited by applicant]
NTT DOCOMO: “Views on Remaining Issues of NB-PDSCH”, 3GPP TSG RAN WG1 Meeting #84bis, R1-163168, Busan, Korea Apr. 11-15, 2016, pp. 1-4. [cited by applicant]
Qualcomm Incorporated: “Physical Channel Time and Frequency Relationship”,3GPPTSG RAN WG1 #82 BIS, 3GPP Draft, R1-155704, Physical Channel Time and Frequency Relationship, 3rd Generation Partnership Project (3GPP), Mobi… [cited by applicant]
Rapporteur W (Ericsson): “RAN1 Agreements for Rel-13 eMTC Sorted and Edited by Topic,” 3GPP Draft, 3GPP TSG RAN WG1 Meeting #84, R1-161546, RAN1 Agreements for Rel-13 eMTC Sorted by Topic with SPEC Impacts—with Change T… [cited by applicant]
Samsung: “Discussion on DL Common Channel/Signal for TDD NB-IoT”, 3GPP Draft, R1-1713549, 3GPP TSG RAN WG1 Meeting #90, 3rd Generation Partnership Project (3GPP), Mobile Competence Centre, 650, Route Des Lucioles, F-069… [cited by applicant]
Samsung: “Discussion on DL Common Channel/Signal for TDD NB-IoT,” 3GPP TSG RAN WG1 Meeting #90bis, R1-1717570, Prague, CZ, Oct. 9-13 2017 (Oct. 13, 2017), pp. 1-4. [cited by applicant]
Samsung: “Discussion on Forward Compatibility for NR,” 3GPP Draft; R1-166743, Forward Compatibility Final, 3rd Generation Partnership Project (3GPP), Mobile Competence Centre; 650, Route Des Lucioles; F-06921, Sophia-An… [cited by applicant]
Session Chairman (Qualcomm Inc): “Summary of Ad-Hoc Session on Further LTE Physical Layer Enhancements for MTC”, 3GPP TSG RAN WG1 Meeting #83, R1-157892, Anaheim, CA, USA, Nov. 16, 2015-Nov. 20, 2015, 23 Pages, 3GPP Ser… [cited by applicant]
Spreadtrum Communications: “Discussion on NB-PDSCH/NB-PUSCH Transmission for NB-IoT”, 3GPP TSG RAN WG1 NB-IoT Ad-Hoc Meeting, R1-161964, Sophia Antipolis, France, 3GPP (Server Release Date: Mar. 15, 2016), 3 Pages, Mar.… [cited by applicant]
Supplementary European Search Report—EP18879196—Search Authority—Munich—Jul. 5, 2021. [cited by applicant]
Taiwan Search Report—TW107140776—TIPO—Dec. 16, 2021. [cited by applicant]
Wei H., “The Optimization of TD-LTE Special Sub-Frame Configuration” Optimal Design of TD-LTE Special Subframe Ratio, Mobile Communications, Issue 6, May 26, 2014, 5 Pages. [cited by applicant]
Wi Rapporteur (Ericsson): “RAN1 Agreements for Rel-13 NB-IoT”, 3GPP TSG-RAN WG1 Meeting #85, 3GPP Draft; R1-165977, 3rd Generation Partnership Project (3GPP), Mobile Competence Centre, 650, Route Des Lucioles, F-06921, … [cited by applicant]
Wi Rapporteur (Ericsson): “RAN1 Agreements for Rel-13 NB-IoT” [online], 3GPP TSG-RAN WG1 NB-IoT Ad-Hoc Meeting R1-162038, Mar. 24, 2016, 19 Pages, URL: http://www.3gpp.org/ftp/tsg_ran/WG1_RL1/TSGR1_AH/LTE_NB-IOT_1603/Do… [cited by applicant]
ZTE: “Detailed Design on Downlink Aspects to Support TDD NB-IoT”, 3GPP Draft, 3GPP TSG RAN WG1 Meeting #90bis, R1-1717202, Downlink Aspects for NB-IoT TDD, 3rd Generation Partnership Project (3GPP), Mobile Competence Ce… [cited by applicant]
ZTE: “NB-PSS and NB-SSS Design for NB-IoT”, 3GPP TSG RAN WG1 Meeting #84, 3GPP Draft, R1-161221 NB-PSS and NB-SSS_Updated, 3rd Generation Partnership Project (3GPP), Mobile Competence Centre, 650, Route Des Lucioles, F-… [cited by applicant]
ZTE: “Remaining Issues on NB-PDCCH Design of NB-IoT”, 3GPP TSG RAN WG1 Meeting #84bis, R1-162757, Busan, Korea, Apr. 11-5, 2016, pp. 1-5. [cited by applicant]
ZTE: “Support of HARQ-ACK Bundling for MTC”, R1-1609830, 3GPP TSG RAN WG1 Meeting #86bis, Lisbon, Portugal, Oct. 10-14, 2016, 5 Pages. [cited by applicant]
Huawei, et al., “TDD Support in NB-IoT”, 3GPP TSG-RAN WG2 Meeting #99bis, R2-1711332, Prague, Czech Republic, Oct. 9-13, 2017, pp. 1-9. [cited by applicant]
LG Electronics: “Discussion on PDSCH transmission for MTC”, 3GPP TSG RAN WG1 Meeting #81, R1-152701, Fukuoka, Japan, May 25-29, 2015, pp. 1-9. [cited by applicant]
Samsung: “DL/UL HARQ Timing for Low Cost MTC UEs in Enhanced Coverage”, 3GPP TSG RAN WG1 #80b, R1-151586, No. Belgrade, Serbia, Apr. 20, 2015-Apr. 24, 2015, 3 Pages. [cited by applicant]
Sony: “Monitoring of NPDCCH after NPDSCH/NPUSCH Transmission”, 3GPP TSG RAN WG1 Meeting #85, R1-164291, No. Nanjing, China, May 24, 2016-May 27, 2016, 2 Pages. [cited by applicant]
Deutsche Telekom, et al., “Way Forward NB-IOT and EMTC Evolution and UE Capability”, 3GPP TSG RAN Meeting #76, RP-171420, West Palm Beach, USA, Jun. 5-8, 2017, 4 Pages. [cited by applicant]