WO2019023849A1 - Autorisations de liaison montante et de liaison descendante pour opérations à bande étroite - Google Patents

Autorisations de liaison montante et de liaison descendante pour opérations à bande étroite Download PDF

Info

Publication number
WO2019023849A1
WO2019023849A1 PCT/CN2017/095169 CN2017095169W WO2019023849A1 WO 2019023849 A1 WO2019023849 A1 WO 2019023849A1 CN 2017095169 W CN2017095169 W CN 2017095169W WO 2019023849 A1 WO2019023849 A1 WO 2019023849A1
Authority
WO
WIPO (PCT)
Prior art keywords
data channel
grants
harq
grant
collision
Prior art date
Application number
PCT/CN2017/095169
Other languages
English (en)
Inventor
Chao Wei
Kapil Bhattad
Hao Xu
Alberto Rico Alvarino
Original Assignee
Qualcomm Incorporated
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Qualcomm Incorporated filed Critical Qualcomm Incorporated
Priority to PCT/CN2017/095169 priority Critical patent/WO2019023849A1/fr
Priority to JP2020504334A priority patent/JP2020529164A/ja
Priority to PCT/CN2018/097029 priority patent/WO2019024737A1/fr
Priority to CN201880047197.0A priority patent/CN110892690B/zh
Priority to EP18840636.7A priority patent/EP3662625A4/fr
Priority to BR112020001788-4A priority patent/BR112020001788A2/pt
Priority to TW107125667A priority patent/TWI762683B/zh
Priority to CA3068759A priority patent/CA3068759A1/fr
Priority to KR1020207002986A priority patent/KR20200035034A/ko
Publication of WO2019023849A1 publication Critical patent/WO2019023849A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0058—Allocation criteria
    • H04L5/0064—Rate requirement of the data, e.g. scalable bandwidth, data priority
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1812—Hybrid protocols; Hybrid automatic repeat request [HARQ]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0044—Arrangements for allocating sub-channels of the transmission path allocation of payload
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1822—Automatic repetition systems, e.g. Van Duuren systems involving configuration of automatic repeat request [ARQ] with parallel processes
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signaling, i.e. of overhead other than pilot signals

Definitions

  • Certain aspects of the present disclosure generally relate to wireless communications and, more particularly, to uplink (UL) and downlink (DL) grants for narrowband operations.
  • UL uplink
  • DL downlink
  • Wireless communication systems are widely deployed to provide various types of communication content such as voice, data, and so on. These systems may be multiple-access systems capable of supporting communication with multiple users by sharing the available system resources (e.g., bandwidth and transmit power) .
  • multiple-access systems include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) /LTE-Advanced (LTE-A) systems and orthogonal frequency division multiple access (OFDMA) systems.
  • CDMA code division multiple access
  • TDMA time division multiple access
  • FDMA frequency division multiple access
  • 3GPP 3rd Generation Partnership Project
  • LTE Long Term Evolution
  • LTE-A LTE-Advanced
  • OFDMA orthogonal frequency division multiple access
  • a wireless multiple-access communication system can simultaneously support communication for multiple wireless terminals.
  • Each terminal communicates with one or more base stations (BSs) via transmissions on the forward and reverse links.
  • the forward link refers to the communication link from the BSs to the terminals
  • the reverse link refers to the communication link from the terminals to the BSs.
  • This communication link may be established via a single-input single-output, multiple-input single-output or a multiple-input multiple-output (MIMO) system.
  • MIMO multiple-input multiple-output
  • a wireless communication network may include a number of BSs that can support communication for a number of wireless devices.
  • Wireless devices may include user equipments (UEs) .
  • Machine type communications may refer to communication involving at least one remote device on at least one end of the communication and may include forms of data communication which involve one or more entities that do not necessarily need human interaction.
  • MTC UEs may include UEs that are capable of MTC communications with MTC servers and/or other MTC devices through Public Land Mobile Networks (PLMN) , for example.
  • Wireless devices may include Internet-of-Things (IoT) devices (e.g., narrowband IoT (NB-IoT) devices) .
  • IoT may refer to a network of physical objects, devices, or “things” .
  • IoT devices may be embedded with, for example, electronics, software, or sensors and may have network connectivity, which enable these devices to collect and exchange data.
  • next generation, NR, or 5G networks may include a number of base stations, each simultaneously supporting communication for multiple communication devices, such as UEs.
  • a set of one or more BSs may define an e NodeB (eNB) .
  • eNB e NodeB
  • a wireless multiple access communication system may include a number of distributed units (e.g., edge units (EUs) , edge nodes (ENs) , radio heads (RHs) , smart radio heads (SRHs) , transmission reception points (TRPs) , etc.
  • distributed units e.g., edge units (EUs) , edge nodes (ENs) , radio heads (RHs) , smart radio heads (SRHs) , transmission reception points (TRPs) , etc.
  • central units e.g., CU, central nodes (CNs) , access node controllers (ANCs) , etc.
  • central units e.g., CU, central nodes (CNs) , access node controllers (ANCs) , etc.
  • a set of one or more distributed units (DUs) in communication with a CU, may define an access node (e.g., AN, a new radio base station (NR BS) , a NR NB, a network node, a gNB, a 5G BS, an access point (AP) , etc. ) .
  • a BS or DU may communicate with a set of UEs on downlink channels (e.g., for transmissions from a BS or to a UE) and uplink channels (e.g., for transmissions from a UE to a BS or DU) .
  • downlink channels e.g., for transmissions from a BS or to a UE
  • uplink channels e.g., for transmissions from a UE to a BS or DU
  • NR e.g., 5G radio access
  • LTE long term evolution
  • NR is a set of enhancements to the LTE mobile standard promulgated by 3GPP.
  • NR is designed to better support mobile broadband Internet access by improving spectral efficiency, lowering costs, improving services, making use of new spectrum, and better integrating with other open standards using OFDMA with a cyclic prefix (CP) on the downlink (DL) and on the uplink (UL) as well as support beamforming, MIMO antenna technology, and carrier aggregation.
  • OFDMA OFDMA with a cyclic prefix
  • DL downlink
  • UL uplink
  • carrier aggregation carrier aggregation
  • Certain aspects of the present disclosure generally relate to uplink and downlink operations for narrowband operations.
  • Certain aspects of the present disclosure provide a method, performed by a wireless device, such as a user equipment (UE) .
  • the method generally includes monitoring a control channel in a narrowband of a system bandwidth for an uplink (UL) or a downlink (DL) grant, receiving interlaced UL and DL grants, and sending or receiving information in response to the received interlaced UL and DL grants.
  • a wireless device such as a user equipment (UE)
  • the method generally includes monitoring a control channel in a narrowband of a system bandwidth for an uplink (UL) or a downlink (DL) grant, receiving interlaced UL and DL grants, and sending or receiving information in response to the received interlaced UL and DL grants.
  • UL uplink
  • DL downlink
  • Certain aspects of the present disclosure provide a method, performed by a wireless device, such as a UE.
  • the method generally includes monitoring a control channel in a narrowband of a system bandwidth for an uplink (UL) or a downlink (DL) grant, receiving two consecutive UL or DL grants, wherein the consecutive UL or DL grants have a same HARQ process identification (ID) , and selecting a grant to use based, at least in part, on at least one of: a grant that meets an energy metric threshold, a grant that is received first, or a grant that is received second; or selecting both grants to use, wherein the grants are treated as hybrid automatic repeat request (HARQ) retransmissions.
  • HARQ hybrid automatic repeat request
  • Certain aspects of the present disclosure provide a method, performed by a wireless device, such as a UE.
  • the method generally includes monitoring a control channel in a narrowband of a system bandwidth for an uplink (UL) or a downlink (DL) grant, receiving two consecutive UL or DL grants, sending or receiving information in response to the received two consecutive UL and DL grants, and in response to the sending or receiving information, identifying a collision, the collision comprising at least one of: collision between first DL data channel and second DL data channel, collision between the second DL data channel and first HARQ acknowledgement (HARQ-ACK) signaling for the first DL data channel, collision between first HARQ-ACK signaling for the first DL data channel and second HARQ-ACK signaling for the second DL data channel, or collision between first UL data channel and second UL data channel.
  • HARQ-ACK HARQ acknowledgement
  • Certain aspects of the present disclosure provide a method, performed by a wireless device, such as a base station (BS) .
  • the method generally includes transmitting interlaced uplink (UL) and downlink (DL) grants on a control channel in a narrowband of a system bandwidth, and sending or receiving information in response to the transmitted interlaced UL and DL grants.
  • UL uplink
  • DL downlink
  • Certain aspects of the present disclosure provide a method, performed by a wireless device, such as a base station (BS) .
  • the method generally includes transmitting, to a user equipment (UE) , two consecutive uplink (UL) or downlink (DL) grants on a control channel in a narrowband of a system bandwidth, wherein the consecutive UL or DL grants have a same HARQ process identification (ID) , wherein a grant to use is selected by the UE based, at least in part, on at least one of: a grant that meets an energy metric threshold, a grant that is received first, or a grant that is received second; or both grants are selected to use by the UE, wherein the grants are treated as hybrid automatic repeat request (HARQ) retransmissions.
  • HARQ hybrid automatic repeat request
  • Certain aspects of the present disclosure provide a method, performed by a wireless device, such as a base station (BS) .
  • the method generally includes transmitting, to a user equipment (UE) , two consecutive UL or DL grants on a control channel in a narrowband of a system bandwidth, sending or receiving information in response to the transmitted two consecutive UL and DL grants, wherein, in response to the sending or receiving information, identifying a collision comprising at least one of: collision between first DL data channel and second DL data channel, collision between the second DL data channel and first HARQ acknowledgement (HARQ-ACK) signaling for the first DL data channel, collision between first HARQ-ACK signaling for the first DL data channel and second HARQ-ACK signaling for the second DL data channel; or collision between first UL data channel and second UL data channel.
  • HARQ-ACK HARQ acknowledgement
  • the one or more aspects comprise the features hereinafter fully described and particularly pointed out in the claims.
  • the following description and the annexed drawings set forth in detail certain illustrative features of the one or more aspects. These features are indicative, however, of but a few of the various ways in which the principles of various aspects may be employed, and this description is intended to include all such aspects and their equivalents.
  • FIG. 1 is a block diagram conceptually illustrating an example of a wireless communication network, in accordance with certain aspects of the present disclosure.
  • FIG. 2 shows a block diagram conceptually illustrating an example of a base station (BS) in communication with a user equipment (UE) in a wireless communications network, in accordance with certain aspects of the present disclosure.
  • BS base station
  • UE user equipment
  • FIG. 3 is a block diagram conceptually illustrating an example of a frame structure in a wireless communications network, in accordance with certain aspects of the present disclosure.
  • FIG. 4 is a block diagram conceptually illustrating two exemplary subframe formats with the normal cyclic prefix, in accordance with certain aspects of the present disclosure.
  • FIG. 5 illustrates an exemplary subframe configuration for enhanced/evolved machine type communications (eMTC) , in accordance with certain aspects of the present disclosure.
  • eMTC enhanced/evolved machine type communications
  • FIG. 6 illustrates an example deployment of narrowband Internet-of-Things (NB-IoT) , in accordance with certain aspects of the present disclosure.
  • NB-IoT narrowband Internet-of-Things
  • FIG. 7 illustrates an example logical architecture of a distributed radio access network (RAN) , in accordance with certain aspects of the present disclosure.
  • RAN radio access network
  • FIG. 8 illustrates an example physical architecture of a distributed RAN, in accordance with certain aspects of the present disclosure.
  • FIG. 9 is a diagram illustrating an example of a downlink (DL) -centric subframe, in accordance with certain aspects of the present disclosure.
  • FIG. 10 is a diagram illustrating an example of an uplink (UL) -centric subframe, in accordance with certain aspects of the present disclosure.
  • FIG. 11 illustrates an example of Release 13 HARQ process timing and an example of Release 14 HARQ process timing, in accordance with certain aspects of the present disclosure.
  • FIG. 12 illustrates example interlaced grants (DL followed by UL) in accordance with certain aspects of the present disclosure.
  • FIG. 13 illustrates example interlaced grants (UL followed by DL) in accordance with certain aspects of the present disclosure.
  • FIG. 14 illustrates example interlaced NPDCCH and NPUSCH in accordance with certain aspects of the present disclosure.
  • FIG. 15 is a flow diagram illustrating example operations for receiving interlaced uplink and downlink grants in a narrowband of a system bandwidth, in accordance with certain aspects of the present disclosure.
  • FIG. 16 is a flow diagram illustrating example operations for UE behavior when receiving back to back UL grants or DL grants with same HARQ IDs, in accordance with certain aspects of the present disclosure.
  • FIG. 17 is a flow diagram illustrating example operations for UE behavior in connection with collisions when receiving back to back UL grants or DL grants, in accordance with certain aspects of the present disclosure.
  • a CDMA network may implement a radio technology such as universal terrestrial radio access (UTRA) , cdma2000, etc.
  • UTRA includes wideband CDMA (WCDMA) , time division synchronous CDMA (TD-SCDMA) , and other variants of CDMA.
  • cdma2000 covers IS-2000, IS-95 and IS-856 standards.
  • a TDMA network may implement a radio technology such as global system for mobile communications (GSM) .
  • GSM global system for mobile communications
  • An OFDMA network may implement a radio technology such as evolved UTRA (E-UTRA) , ultra mobile broadband (UMB) , IEEE 802.11 (Wi-Fi) , IEEE 802.16 (WiMAX) , IEEE 802.20, etc.
  • E-UTRA evolved UTRA
  • UMB ultra mobile broadband
  • IEEE 802.11 Wi-Fi
  • WiMAX IEEE 802.16
  • IEEE 802.20 etc.
  • UTRA and E-UTRA are part of universal mobile telecommunication system (UMTS) .
  • 3GPP Long Term Evolution (LTE) and LTE-Advanced (LTE-A) in both frequency division duplex (FDD) and time division duplex (TDD) , are new releases of UMTS that use E-UTRA, which employs OFDMA on the downlink and SC-FDMA on the uplink.
  • LTE Long Term Evolution
  • LTE-A LTE-Advanced
  • FDD frequency division duplex
  • TDD time division duplex
  • LTE Universal Terrestrial Radio Access
  • 3GPP 3rd Generation Partnership Project
  • cdma2000 and UMB are described in documents from an organization named “3rd Generation Partnership Project 2” (3GPP2) .
  • NR e.g., 5G radio access
  • NR is an example of an emerging telecommunication standard.
  • NR is a set of enhancements to the LTE mobile standard promulgated by 3GPP.
  • the techniques described herein may be used for the wireless networks and radio technologies mentioned above as well as other wireless networks and radio technologies. For clarity, certain aspects of the techniques are described below for LTE/LTE- Advanced, and LTE/LTE-Advanced (LTE-A) terminology is used in much of the description below.
  • LTE and LTE-A are referred to generally as LTE.
  • FIG. 1 illustrates an example wireless communication network 100, in which aspects of the present disclosure may be practiced.
  • wireless communication network 100 may be narrowband Internet-of-things (NB-IoT) and/or an enhanced/evolved machine type communications (eMTC) network.
  • Wireless communication network 100 may include base stations (BSs) 110 and user equipment (UEs) 120.
  • BSs base stations
  • UEs user equipment
  • a BS 110 can determine at least one narrowband region of a wideband region for communication with a UE 120.
  • UE 120 which may be a low cost device, such a NB-IoT device or an eMTC UE, can determine the narrowband region and receive, send, monitor, or decode information on the narrowband region for communication with BS 110.
  • Wireless communication network 100 may be a long term evolution (LTE) network or some other wireless network, such as a new radio (NR) or 5G network.
  • Wireless communication network 100 may include a number of BSs 110 and other network entities.
  • a BS is an entity that communicates with UEs and may also be referred to as a NR BS, a Node B (NB) , an evolved/enhanced NB (eNB) , a 5G NB, a gNB, an access point (AP) , a transmission reception point (TRP) , etc.
  • Each BS may provide communication coverage for a particular geographic area.
  • the term “cell” can refer to a coverage area of a BS and/or a BS subsystem serving this coverage area, depending on the context in which the term is used.
  • a BS may provide communication coverage for a macro cell, a pico cell, a femto cell, and/or other types of cell.
  • a macro cell may cover a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by UEs with service subscription.
  • a pico cell may cover a relatively small geographic area and may allow unrestricted access by UEs with service subscription.
  • a femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by UEs having association with the femto cell (e.g., UEs in a closed subscriber group (CSG) ) .
  • a BS for a macro cell may be referred to as a macro BS.
  • a BS for a pico cell may be referred to as a pico BS.
  • a BS for a femto cell may be referred to as a femto BS or a home BS.
  • BS 110a may be a macro BS for a macro cell 102a
  • BS 110b may be a pico BS for a pico cell 102b
  • BS 110c may be a femto BS for a femto cell 102c.
  • a BS may support one or multiple (e.g., three) cells.
  • the terms “base station” and “cell” may be used interchangeably herein.
  • Wireless communication network 100 may also include relay stations.
  • a relay station is an entity that can receive a transmission of data from an upstream station (e.g., BS 110 or UE 120) and send a transmission of the data to a downstream station (e.g., UE 120 or BS 110) .
  • a relay station may also be a UE that can relay transmissions for other UEs.
  • relay station 110d may communicate with macro BS 110a and UE 120d in order to facilitate communication between BS 110a and UE 120d.
  • a relay station may also be referred to as a relay BS, a relay, etc.
  • Wireless communication network 100 may be a heterogeneous network that includes BSs of different types, e.g., macro BSs, pico BSs, femto BSs, relay BSs, etc. These different types of BSs may have different transmit power levels, different coverage areas, and different impact on interference in wireless communication network 100.
  • macro BSs may have a high transmit power level (e.g., 5 to 40 Watts) whereas pico BSs, femto BSs, and relay BSs may have lower transmit power levels (e.g., 0.1 to 2 Watts) .
  • Network controller 130 may couple to a set of BSs and may provide coordination and control for these BSs.
  • Network controller 130 may communicate with the BSs via a backhaul.
  • the BSs may also communicate with one another, e.g., directly or indirectly via a wireless or wireline backhaul.
  • UEs 120 may be dispersed throughout wireless communication network 100, and each UE may be stationary or mobile.
  • a UE may also be referred to as an access terminal, a terminal, a mobile station, a subscriber unit, a station, a Customer Premises Equipment (CPE) , etc.
  • CPE Customer Premises Equipment
  • a UE may be a cellular phone (e.g., a smart phone) , a personal digital assistant (PDA) , a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet, a camera, a drone, a robot/robotic device, a netbook, a smartbook, an ultrabook, a medical device, medical equipment, a healthcare device, a biometric sensor/device, a wearable device such as a smart watch, smart clothing, smart glasses, virtual reality goggles, a smart wristband, and/or smart jewelry (e.g., a smart ring, a smart bracelet, etc.
  • PDA personal digital assistant
  • WLL wireless local loop
  • an entertainment device e.g., a music device, a video device, a gaming device, a satellite radio, etc.
  • industrial manufacturing equipment e.g., a navigation/positioning device (e.g., GNSS (global navigation satellite system) devices based on, for example, GPS (global positioning system) , Beidou, GLONASS, Galileo, terrestrial-based devices, etc. ) , or any other suitable device configured to communicate via a wireless or wired medium.
  • GNSS global navigation satellite system
  • Some UEs may be implemented as IoT (Internet of things) UEs.
  • IoT UEs include, for example, robots/robotic devices, drones, remote devices, sensors, meters, monitors, cameras, location tags, etc., that may communicate with a BS, another device (e.g., remote device) , or some other entity.
  • IoT UEs may include MTC/eMTC UEs, NB-IoT UEs, as well as other types of UEs.
  • a wireless node may provide, for example, connectivity for or to a network (e.g., a wide area network such as Internet or a cellular network) via a wired or wireless communication link.
  • One or more UEs 120 in the wireless communication network 100 may be a narrowband bandwidth UE.
  • devices with limited communication resources e.g. smaller bandwidth, may be referred to generally as narrowband UEs.
  • legacy devices such as legacy and/or advanced UEs (e.g., in LTE) may be referred to generally as wideband UEs.
  • wideband UEs are capable of operating on a larger amount of bandwidth than narrowband UEs.
  • a solid line with double arrows indicates desired transmissions between a UE and a serving BS, which is a BS designated to serve the UE on the downlink and/or uplink.
  • a dashed line with double arrows indicates potentially interfering transmissions between a UE and a BS.
  • any number of wireless networks may be deployed in a given geographic area.
  • Each wireless network may support a particular radio access technology (RAT) and may operate on one or more frequencies.
  • a RAT may also be referred to as a radio technology, an air interface, etc.
  • a frequency may also be referred to as a carrier, a frequency channel, etc.
  • Each frequency may support a single RAT in a given geographic area in order to avoid interference between wireless networks of different RATs.
  • NR or 5G RAT networks may be deployed.
  • a scheduling entity e.g., a BS 110
  • the scheduling entity may be responsible for scheduling, assigning, reconfiguring, and releasing resources for one or more subordinate entities.
  • subordinate entities utilize resources allocated by the scheduling entity.
  • BSs 110 are not the only entities that may function as a scheduling entity.
  • UE 120 may function as a scheduling entity, scheduling resources for one or more subordinate entities (e.g., one or more other UEs 120) .
  • the UE is functioning as a scheduling entity, and other UEs utilize resources scheduled by the UE for wireless communication.
  • a UE may function as a scheduling entity in a peer-to-peer (P2P) network, and/or in a mesh network. In a mesh network example, UEs may optionally communicate directly with one another in addition to communicating with the scheduling entity.
  • P2P peer-to-peer
  • a scheduling entity and one or more subordinate entities may communicate utilizing the scheduled resources.
  • FIG. 2 shows a block diagram of a design of BS 110 and UE 120, which may be one of the BSs 110 and one of the UEs 120 in FIG. 1.
  • BS 110 may be equipped with T antennas 234a through 234t
  • UE 120 may be equipped with R antennas 252a through 252r, where in general T ⁇ 1 and R ⁇ 1.
  • transmit processor 220 may receive data from a data source 212 for one or more UEs, select one or more modulation and coding schemes (MCS) for each UE based on channel quality indicators (CQIs) received from the UE, process (e.g., encode and modulate) the data for each UE based on the MCS (s) selected for the UE, and provide data symbols for all UEs. Transmit processor 220 may also process system information (e.g., for static resource partitioning information (SRPI) , etc. ) and control information (e.g., CQI requests, grants, upper layer signaling, etc. ) and provide overhead symbols and control symbols.
  • MCS modulation and coding schemes
  • Processor 220 may also generate reference symbols for reference signals (e.g., the cell-specific reference signal (CRS)) and synchronization signals (e.g., the primary synchronization signal (PSS) and the secondary synchronization signal (SSS) ) .
  • Transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., precoding) on the data symbols, the control symbols, the overhead symbols, and/or the reference symbols, if applicable, and may provide T output symbol streams to T modulators (MODs) 232a through 232t. Each modulator 232 may process a respective output symbol stream (e.g., for OFDM, etc. ) to obtain an output sample stream.
  • T modulators modulators
  • Each modulator 232 may further process (e.g., convert to analog, amplify, filter, and upconvert) the output sample stream to obtain a downlink signal.
  • T downlink signals from modulators 232a through 232t may be transmitted via T antennas 234a through 234t, respectively.
  • antennas 252a through 252r may receive the downlink signals from base station 110 and/or other BSs and may provide received signals to demodulators (DEMODs) 254a through 254r, respectively.
  • Each demodulator 254 may condition (e.g., filter, amplify, downconvert, and digitize) its received signal to obtain input samples.
  • Each demodulator 254 may further process the input samples (e.g., for OFDM, etc. ) to obtain received symbols.
  • MIMO detector 256 may obtain received symbols from all R demodulators 254a through 254r, perform MIMO detection on the received symbols if applicable, and provide detected symbols.
  • Receive processor 258 may process (e.g., demodulate and decode) the detected symbols, provide decoded data for UE 120 to data sink 260, and provide decoded control information and system information to controller/processor 280.
  • a channel processor may determine reference signal received power (RSRP) , received signal strength indicator (RSSI) , reference signal receive quality (RSRQ) , CQI, etc.
  • transmit processor 264 may receive and process data from data source 262 and control information (e.g., for reports comprising RSRP, RSSI, RSRQ, CQI, etc. ) from controller/processor 280. Processor 264 may also generate reference symbols for one or more reference signals. The symbols from transmit processor 264 may be precoded by TX MIMO processor 266 if applicable, further processed by modulators 254a through 254r (e.g., for SC-FDM, OFDM, etc. ) , and transmitted to BS 110.
  • control information e.g., for reports comprising RSRP, RSSI, RSRQ, CQI, etc.
  • Processor 264 may also generate reference symbols for one or more reference signals.
  • the symbols from transmit processor 264 may be precoded by TX MIMO processor 266 if applicable, further processed by modulators 254a through 254r (e.g., for SC-FDM, OFDM, etc. ) , and transmitted to BS 110.
  • the uplink signals from UE 120 and other UEs may be received by antennas 234, processed by demodulators 232, detected by MIMO detector 236 if applicable, and further processed by receive processor 238 to obtain decoded data and control information sent by UE 120.
  • Processor 238 may provide the decoded data to data sink 239 and the decoded control information to controller/processor 240.
  • BS 110 may include communication unit 244 and communicate to network controller 130 via communication unit 244.
  • Network controller 130 may include communication unit 294, controller/processor 290, and memory 292.
  • Controllers/processors 240 and 280 may direct the operation at BS 110 and UE 120, respectively, to perform techniques presented herein.
  • processor 240 and/or other processors and modules at BS 110, and processor 280 and/or other processors and modules at UE 120 may perform or direct operations of BS 110 and UE 120, respectively.
  • controller/processor 280 and/or other controllers/processors and modules at UE 120 may perform or direct operations 1500 shown in FIG. 15, operations 1600 shown in FIG. 16, and operations 1700 shown in FIG. 17.
  • Memories 242 and 282 may store data and program codes for BS 110 and UE 120, respectively.
  • Scheduler 246 may schedule UEs for data transmission on the downlink and/or uplink.
  • FIG. 3 shows an exemplary frame structure 300 for frequency division duplexing (FDD) in a wireless communication system (e.g., such as wireless communication network 100) .
  • the transmission timeline for each of the downlink and uplink may be partitioned into units of radio frames.
  • Each radio frame may have a predetermined duration (e.g., 10 milliseconds (ms) ) and may be partitioned into 10 subframes with indices of 0 through 9.
  • Each subframe may include two slots.
  • Each radio frame may thus include 20 slots with indices of 0 through 19.
  • Each slot may include L symbol periods, for example, seven symbol periods for a normal cyclic prefix (as shown in FIG. 3) or six symbol periods for an extended cyclic prefix.
  • the 2L symbol periods in each subframe may be assigned indices of 0 through 2L–1.
  • a BS may transmit a PSS and a SSS on the downlink in the center of the system bandwidth for each cell supported by the BS.
  • the PSS and SSS may be transmitted in symbol periods 6 and 5, respectively, in subframes 0 and 5 of each radio frame with the normal cyclic prefix, as shown in FIG. 3.
  • the PSS and SSS may be used by UEs (e.g., such as UEs 120) for cell search and acquisition.
  • the BS may transmit a CRS across the system bandwidth for each cell supported by the BS.
  • the CRS may be transmitted in certain symbol periods of each subframe and may be used by the UEs to perform channel estimation, channel quality measurement, and/or other functions.
  • the BS may also transmit a physical broadcast channel (PBCH) in symbol periods 0 to 3 in slot 1 of certain radio frames.
  • PBCH physical broadcast channel
  • the PBCH may carry some system information.
  • the BS may transmit other system information such as system information blocks (SIBs) on a physical downlink shared channel (PDSCH) in certain subframes.
  • SIBs system information blocks
  • PDSCH physical downlink shared channel
  • the BS may transmit control information/data on a physical downlink control channel (PDCCH) in the first B symbol periods of a subframe, where B may be configurable for each subframe.
  • the BS may transmit traffic data and/or other data on the PDSCH in the remaining symbol periods of each subframe.
  • a BS may transmit these or other signals in these locations or in different locations of the subframe.
  • FIG. 4 shows two exemplary subframe formats 410 and 420 with the normal cyclic prefix.
  • the available time frequency resources may be partitioned into resource blocks (RBs) .
  • RB resource blocks
  • Each RB may cover 12 subcarriers in one slot and may include a number of resource elements (REs) .
  • Each RE may cover one subcarrier in one symbol period and may be used to send one modulation symbol, which may be a real or complex value.
  • Subframe format 410 may be used for two antennas.
  • a CRS may be transmitted from antennas 0 and 1 in symbol periods 0, 4, 7 and 11.
  • a reference signal is a signal that is known a priori by a transmitter and a receiver and may also be referred to as pilot.
  • a CRS is a reference signal that is specific for a cell, e.g., generated based on a cell identity (ID) .
  • ID cell identity
  • Subframe format 420 may be used with four antennas.
  • a CRS may be transmitted from antennas 0 and 1 in symbol periods 0, 4, 7 and 11 and from antennas 2 and 3 in symbol periods 1 and 8.
  • a CRS may be transmitted on evenly spaced subcarriers, which may be determined based on cell ID. CRSs may be transmitted on the same or different subcarriers, depending on their cell IDs.
  • REs not used for the CRS may be used to transmit data (e.g., traffic data, control data, and/or other data) .
  • E-UTRA Evolved Universal Terrestrial Radio Access
  • An interlace structure may be used for each of the downlink and uplink for FDD in LTE.
  • Q interlaces with indices of 0 through Q–1 may be defined, where Q may be equal to 4, 6, 8, 10, or some other value.
  • Each interlace may include subframes that are spaced apart by Q frames.
  • interlace q may include subframes q, q+Q, q+ 2Q, etc., where q ⁇ ⁇ 0, ..., Q-1 ⁇ .
  • the wireless network may support hybrid automatic retransmission request (HARQ) for data transmission on the downlink and uplink.
  • HARQ hybrid automatic retransmission request
  • a transmitter e.g., a BS
  • a receiver e.g., a UE
  • all transmissions of the packet may be sent in subframes of a single interlace.
  • each transmission of the packet may be sent in any subframe.
  • a UE may be located within the coverage of multiple BS. One of these BSs may be selected to serve the UE. The serving BS may be selected based on various criteria such as received signal strength, received signal quality, pathloss, etc. Received signal quality may be quantified by a signal-to-noise-and-interference ratio (SINR) , or a RSRQ, or some other metric.
  • SINR signal-to-noise-and-interference ratio
  • RSRQ radio-to-noise-and-interference ratio
  • the UE may operate in a dominant interference scenario in which the UE may observe high interference from one or more interfering BS.
  • the wireless communication network may support a 180 kHz deployment for narrowband operation (e.g., NB-IoT) with different deployment modes.
  • narrowband operations may be deployed in-band, for example, using RBs within a wider system bandwidth.
  • narrowband operations may use one RB within the wider system bandwidth of an existing network (e.g., such as an LTE network) .
  • the 180 kHz bandwidth for the RB may have to be aligned with a wideband RB.
  • narrowband operations may be deployed in the unused RBs within a carrier guard-band (e.g., LTE) .
  • a carrier guard-band e.g., LTE
  • the 180 kHz RB within the guard band may be aligned with a 15 kHz tone grid of wideband LTE, for example, in order to use the same Fast Fourier Transform (FFT) and/or reduce interference in-band legacy LTE communications.
  • FFT Fast Fourier Transform
  • LTE long term evolution
  • DL and UL link budgets are designed for coverage of high end devices, such as state-of-the-art smartphones and tablets, which may support a relatively large DL and UL link budget.
  • one or more UEs in the wireless communication network may be devices that have limited communication resources, such as narrowband UEs, as compared to other (wideband) devices in the wireless communication network.
  • narrowband UEs various requirements may be relaxed as only a limited amount of information may need to be exchanged. For example, maximum bandwidth may be reduced (relative to wideband UEs) , a single receive radio frequency (RF) chain may be used, peak rate may be reduced (e.g., a maximum of 100 bits for a transport block size) , transmit power may be reduced, Rank 1 transmission may be used, and half duplex operation may be performed.
  • RF radio frequency
  • MTC UEs may have a relaxed switching time to transition from transmitting to receiving (or receiving to transmitting) .
  • the switching time may be relaxed from 20 ⁇ s for regular UEs to 1ms for MTC UEs.
  • Release 12 MTC UEs may still monitor downlink (DL) control channels in the same way as regular UEs, for example, monitoring for wideband control channels in the first few symbols (e.g., PDCCH) as well as narrowband control channels occupying a relatively narrowband, but spanning a length of a subframe (e.g., enhanced PDCCH or ePDCCH) .
  • DL downlink
  • eMTC enhanced MTC
  • LTE Release 13 LTE Release 13
  • eMTC may provide MTC UEs with coverage enhancements up to 15dB.
  • eMTC UEs can support narrowband operation while operating in a wider system bandwidth (e.g., 1.4/3/5/10/15/20MHz) .
  • a conventional legacy control region 510 may span system bandwidth of a first few symbols, while a narrowband region 530 of the system bandwidth (spanning a narrow portion of a data region 520) may be reserved for an MTC physical downlink control channel (referred to herein as an M-PDCCH) and for an MTC physical downlink shared channel (referred to herein as an M-PDSCH) .
  • M-PDCCH MTC physical downlink control channel
  • M-PDSCH MTC physical downlink shared channel
  • an MTC UE monitoring the narrowband region may operate at 1.4MHz or 6 resource blocks (RBs) .
  • eMTC UEs may be able to operate in a cell with a bandwidth larger than 6 RBs. Within this larger bandwidth, each eMTC UE may still operate (e.g., monitor/receive/transmit) while abiding by a 6-physical resource block (PRB) constraint.
  • PRB 6-physical resource block
  • different eMTC UEs may be served by different narrowband regions (e.g., with each spanning 6-PRB blocks) .
  • the system bandwidth may span from 1.4 to 20 MHz, or from 6 to 100 RBs, multiple narrowband regions may exist within the larger bandwidth.
  • An eMTC UE may also switch or hop between multiple narrowband regions in order to reduce interference.
  • the Internet-of-Things may refer to a network of physical objects, devices, or “things” .
  • IoT devices may be embedded with, for example, electronics, software, or sensors and may have network connectivity, which enable these devices to collect and exchange data.
  • IoT devices may be sensed and controlled remotely across existing network infrastructure, creating opportunities for more direct integration between the physical world and computer-based systems and resulting in improved efficiency, accuracy, and economic benefit.
  • Systems that include IoT devices augmented with sensors and actuators may be referred to cyber-physical systems.
  • Cyber-physical systems may include technologies such as smart grids, smart homes, intelligent transportation, and/or smart cities.
  • Each “thing” e.g., IoT device
  • Each “thing” may be uniquely identifiable through its embedded computing system may be able to interoperate within existing infrastructure, such as Internet infrastructure.
  • NB-IoT may refer to a narrowband radio technology specially designed for the IoT.
  • NB-IoT may focus on indoor coverage, low cost, long battery life, and large number of devices.
  • NB-IoT may allow for narrowband deployments utilizing one PRB (e.g., 180 kHz + 20 kHz guard band) .
  • NB-IoT deployments may utilize higher layer components of certain systems (e.g., LTE) and hardware to allow for reduced fragmentation and cross compatibility with, for example, NB-LTE/NB-IoT and/or eMTC.
  • FIG. 6 illustrates an example deployment 600 of NB-IoT, according to certain aspects of the present disclosure.
  • Three NB-IoT deployment configurations include in-band, guard-band, and standalone.
  • NB-IoT may coexist with a legacy system (e.g., GSM, WCDMA, and/or LTE system (s)) deployed in the same frequency band.
  • the wideband LTE channel may be deployed in various bandwidths between 1.4 MHz to 20 MHz.
  • a dedicated RB 602 within that bandwidth may be available for use by NB-IoT and/or the RBs 1204 may be dynamically allocated for NB-IoT.
  • one RB, or 200 kHz, of a wideband channel (e.g., LTE) may be used for NB-IoT.
  • Certain systems may include unused portions of the radio spectrum between carriers to guard against interference between adjacent carriers.
  • NB-IoT may be deployed in a guard band 606 of the wideband channel.
  • NB-IoT may be deployed standalone (not shown) .
  • one 200 MHz carrier may be utilized to carry NB-IoT traffic and GSM spectrum may be reused.
  • Deployments of NB-IoT may include synchronization signals such as PSS for frequency and timing synchronization and SSS to convey system information.
  • PSS/SSS timing boundaries may be extended as compared to the existing PSS/SSS frame boundaries in legacy systems (e.g., LTE) , for example, from 10 ms to 40 ms.
  • legacy systems e.g., LTE
  • a UE is able to receive a PBCH transmission, which may be transmitted in subframe 0 of a radio frame.
  • New radio may refer to radios configured to operate according to a new air interface (e.g., other than Orthogonal Frequency Divisional Multiple Access (OFDMA) -based air interfaces) or fixed transport layer (e.g., other than Internet Protocol (IP) ) .
  • NR may utilize OFDM with a CP on the uplink and downlink and include support for half-duplex operation using TDD.
  • NR may include Enhanced Mobile Broadband (eMBB) service targeting wide bandwidth (e.g. 80 MHz beyond) , millimeter wave (mmW) targeting high carrier frequency (e.g. 60 GHz) , massive MTC (mMTC) targeting non-backward compatible MTC techniques, and/or mission critical targeting ultra reliable low latency communications (URLLC) service.
  • eMBB Enhanced Mobile Broadband
  • mmW millimeter wave
  • mMTC massive MTC
  • URLLC ultra reliable low latency communications
  • a single component carrier (CC) bandwidth of 100 MHZ may be supported.
  • NR RBs may span 12 sub-carriers with a sub-carrier bandwidth of 75 kHz over a 0.1 ms duration.
  • Each radio frame may consist of 50 subframes with a length of 10 ms. Consequently, each subframe may have a length of 0.2 ms.
  • Each subframe may indicate a link direction (e.g., DL or UL) for data transmission and the link direction for each subframe may be dynamically switched.
  • Each subframe may include DL/UL data as well as DL/UL control data.
  • UL and DL subframes for NR may be as described in more detail below with respect to FIGs. 9 and 10.
  • NR may support a different air interface, other than an OFDM-based interface.
  • NR networks may include entities such central units (CUs) or distributed units (DUs) .
  • the NR RAN may include a CU and DUs.
  • a NR BS e.g., a NB, an eNB, a gNB, a 5G NB, a TRP, an AP, etc.
  • a NR cells can be configured as access cells (ACells) or data only cells (DCells) .
  • the RAN e.g., a CU or DU
  • DCells may be cells used for carrier aggregation or dual connectivity, but not used for initial access, cell selection/reselection, or handover. In some cases DCells may not transmit synchronization signals—in some case cases DCells may transmit synchronization signals.
  • FIG. 7 illustrates an example logical architecture 700 of a distributed RAN, according to aspects of the present disclosure.
  • 5G access node 706 may include access node controller (ANC) 702.
  • ANC 702 may be a CU of the distributed RAN.
  • the backhaul interface to the next generation core network (NG-CN) 704 may terminate at ANC 702.
  • the backhaul interface to neighboring next generation access nodes (NG-ANs) 710 may terminate at ANC 702.
  • ANC 702 may include one or more TRPs 708.
  • TRP may be used interchangeably with “cell” , BS, NR BS, NB, eNB, 5G NB, gNB, AP, etc.
  • TRPs 708 may comprise a DU.
  • TRPs 708 may be connected to one ANC (e.g., ANC 702) or more than one ANC (not illustrated) .
  • ANC e.g., ANC 702
  • TRP 708 may be connected to more than one ANC.
  • TRP 708 may include one or more antenna ports.
  • TRPs 708 may be configured to individually (e.g., dynamic selection) or jointly (e.g., joint transmission) serve traffic to a UE.
  • Logical architecture 700 may be used to illustrate fronthaul definition.
  • the architecture may be defined that support fronthauling solutions across different deployment types.
  • logical architecture 700 may be based on transmit network capabilities (e.g., bandwidth, latency, and/or jitter) .
  • Logical architecture 700 may share features and/or components with LTE.
  • NG-AN 710 may support dual connectivity with NR.
  • NG-AN 710 may share a common fronthaul for LTE and NR.
  • Logical architecture 700 may enable cooperation between and among TRPs 708. For example, cooperation may be preset within a TRP and/or across TRPs via ANC 702. In some cases, no inter-TRP interface may be needed/present.
  • a dynamic configuration of split logical functions may be present within logical architecture 700.
  • the packet data convergence protocol (PDCP) , radio link control (RLC) , and medium access control (MAC) protocols may be adaptably placed at ANC 702 or TRP 708.
  • PDCP packet data convergence protocol
  • RLC radio link control
  • MAC medium access control
  • FIG. 8 illustrates an example physical architecture 800 of a distributed RAN, according to aspects of the present disclosure.
  • Centralized core network unit (C-CU) 802 may host core network functions.
  • C-CU 802 may be centrally deployed.
  • C-CU 802 functionality may be offloaded (e.g., to advanced wireless services (AWS) ) , in an effort to handle peak capacity.
  • AWS advanced wireless services
  • Centralized RAN unit (C-RU) 804 may host one or more ANC functions.
  • C-RU 804 may host core network functions locally.
  • C-RU 804 may have distributed deployment.
  • C-RU 804 may be closer to the network edge.
  • DU 806 may host one or more TRPs. DU 806 may be located at edges of the network with radio frequency (RF) functionality.
  • RF radio frequency
  • FIG. 9 is a diagram showing an example of a DL-centric subframe 900.
  • DL-centric subframe 900 may include control portion 902.
  • Control portion 902 may exist in the initial or beginning portion of DL-centric subframe 900.
  • Control portion 902 may include various scheduling information and/or control information corresponding to various portions of DL-centric subframe 900.
  • control portion 902 may be a physical DL control channel (PDCCH) , as shown in FIG. 9.
  • DL-centric subframe 900 may also include DL data portion 904.
  • DL data portion 904 may sometimes be referred to as the payload of DL-centric subframe 900.
  • DL data portion 904 may include the communication resources utilized to communicate DL data from the scheduling entity (e.g., UE or BS) to the subordinate entity (e.g., UE) .
  • DL data portion 904 may be a physical DL shared channel (PDSCH) .
  • PDSCH physical DL shared channel
  • DL-centric subframe 900 may also include common UL portion 906.
  • Common UL portion 906 may sometimes be referred to as an UL burst, a common UL burst, and/or various other suitable terms.
  • Common UL portion 906 may include feedback information corresponding to various other portions of DL-centric subframe 900.
  • common UL portion 906 may include feedback information corresponding to control portion 902.
  • Non-limiting examples of feedback information may include an acknowledgment (ACK) signal, a negative acknowledgment (NACK) signal, a HARQ indicator, and/or various other suitable types of information.
  • Common UL portion 906 may include additional or alternative information, such as information pertaining to random access channel (RACH) procedures, scheduling requests (SRs) , and various other suitable types of information.
  • RACH random access channel
  • SRs scheduling requests
  • the end of DL data portion 904 may be separated in time from the beginning of common UL portion 906.
  • This time separation may sometimes be referred to as a gap, a guard period, a guard interval, and/or various other suitable terms.
  • This separation provides time for the switch-over from DL communication (e.g., reception operation by the subordinate entity) to UL communication (e.g., transmission by the subordinate entity) .
  • DL communication e.g., reception operation by the subordinate entity
  • UL communication e.g., transmission by the subordinate entity
  • FIG. 10 is a diagram showing an example of an UL-centric subframe 1000.
  • UL-centric subframe 1000 may include control portion 1002.
  • Control portion 1002 may exist in the initial or beginning portion of UL-centric subframe 1000.
  • Control portion 1002 in FIG. 10 may be similar to control portion 1002 described above with reference to FIG. 9.
  • UL-centric subframe 1000 may also include UL data portion 1004.
  • UL data portion 1004 may sometimes be referred to as the payload of UL-centric subframe 1000.
  • the UL portion may refer to the communication resources utilized to communicate UL data from the subordinate entity (e.g., UE) to the scheduling entity (e.g., UE or BS) .
  • control portion 1002 may be a PDCCH.
  • the data portion may be a physical uplink shared channel (PUSCH) .
  • PUSCH physical uplink shared channel
  • control portion 1002 may be separated in time from the beginning of UL data portion 1004. This time separation may sometimes be referred to as a gap, guard period, guard interval, and/or various other suitable terms. This separation provides time for the switch-over from DL communication (e.g., reception operation by the scheduling entity) to UL communication (e.g., transmission by the scheduling entity) .
  • UL-centric subframe 1000 may also include common UL portion 1006.
  • Common UL portion 1006 in FIG. 10 may be similar to common UL portion 906 described above with reference to FIG. 9.
  • Common UL portion 1006 may additionally or alternatively include information pertaining to CQI, sounding reference signals (SRSs) , and various other suitable types of information.
  • SRSs sounding reference signals
  • two or more subordinate entities may communicate with each other using sidelink signals.
  • Real-world applications of such sidelink communications may include public safety, proximity services, UE-to-network relaying, vehicle-to-vehicle (V2V) communications, Internet of Everything (IoE) communications, IoT communications, mission-critical mesh, and/or various other suitable applications.
  • a sidelink signal may refer to a signal communicated from one subordinate entity (e.g., UE1) to another subordinate entity (e.g., UE2) without relaying that communication through the scheduling entity (e.g., UE or BS) , even though the scheduling entity may be utilized for scheduling and/or control purposes.
  • the sidelink signals may be communicated using a licensed spectrum (unlike wireless local area networks, which typically use an unlicensed spectrum) .
  • a UE may operate in various radio resource configurations, including a configuration associated with transmitting pilots using a dedicated set of resources (e.g., a RRC dedicated state, etc. ) or a configuration associated with transmitting pilots using a common set of resources (e.g., an RRC common state, etc. ) .
  • a dedicated set of resources e.g., a RRC dedicated state, etc.
  • a common set of resources e.g., an RRC common state, etc.
  • the UE may select a common set of resources for transmitting a pilot signal to the network.
  • a pilot signal transmitted by the UE may be received by one or more network access devices, such as an AN, a DU, or portions thereof.
  • Each receiving network access device may be configured to receive and measure pilot signals transmitted on the common set of resources, and also receive and measure pilot signals transmitted on dedicated sets of resources allocated to the UEs for which the network access device is a member of a monitoring set of network access devices for the UE.
  • One or more of the receiving network access devices, or a CU to which receiving network access device (s) transmit the measurements of the pilot signals may use the measurements to identify serving cells for the UEs, or to initiate a change of serving cell for one or more of the UEs.
  • certain systems may support narrowband operation.
  • the narrowband operation may include support for communications on a 6 RB band and half-duplex operation (e.g., capability to transmit and receive, but not both simultaneously) for up to, e.g., 15 dB coverage enhancements.
  • These systems may reserve a portion of the system bandwidth for control, which may be an MTC physical downlink control channel (MPDCCH) .
  • the MPDCCH may be transmitted in a narrowband, may use at least one subframe, and may rely on demodulation reference signal (DMRS) demodulation for decoding of the control channel. Coverage may be increased by performing repetition/bundling of signals.
  • DMRS demodulation reference signal
  • NB-IoT narrowband Internet-of-things operation
  • NB-IOT narrowband Internet-of-things operation
  • NB-IoT may use 180 kHz bandwidth.
  • NB-IoT may offer standalone, in-band, or guard band deployment scenarios. Standalone deployment may use new bandwidth, whereas guard band deployment may be done using bandwidth typically reserved in the guard band of an existing network, such as long term evolution (LTE) .
  • LTE long term evolution
  • In-band deployment on the other hand may use the same resource blocks in the LTE carrier of the existing LTE network.
  • NB-IoT may offer increased coverage.
  • NB-IoT may define a new narrowband control channel (e.g., Narrowband PDCCH (NPDCCH) ) , data, and references signals that fit in 1 RB.
  • NPDCCH Narrowband PDCCH
  • NB-IoT terminology is used in much of the description below.
  • the gap between NPDCCH for UL grant and the associated NPUSCH (narrowband PUSCH) transmission is at least 8ms (e.g., exact delay is determined by a field in the UL grant) and the gap between the NPDCCH for DL grant and the associated NPDSCH (narrowband PDSCH) is at least 5ms (e.g., exact delay is determined by a filed in the DL grant) .
  • NPUSCH and NPDSCH are examples of shared channels or data channels.
  • channel may refer to the channel on which signaling/data/information is transmitted or received, or to the signaling/data/information that is transmitted or received on the channel.
  • Rel-13 only a single HARQ process is supported in NB-IoT. After receiving one NPDCCH for DL grant or UL grant, UE stops monitoring the NPDCCH until finishing the data transmission.
  • UE may be required to continue monitoring any NPDCCH search space containing candidates ending at least 2 ms (x 1 ⁇ 2 ms) before the start of the first NPDSCH or NPUSCH.
  • Figure 11 illustrates an example of Release 13 HARQ process timing and an example of Release 14 HARQ process timing.
  • the time gap between a NPDCCH for DL grant and an associated NPDSCH is 5ms or more.
  • UE stops monitoring for NPDCCH and after 5ms or more, UE starts receiving downlink transmission (e.g., data transmission, such as repetition data transmission to improve coverage) on NPDSCH.
  • UE receives NPDCCH for UL grant, stops monitoring for NPDCCH, and transmits (e.g., data transmission) on uplink on the associated NPUSCH after 8ms or more.
  • UE is required to continue monitor for a second NPDCCH (NPDCCH2) after receiving a first NPDCCH (NPDCCH1) .
  • NPDCCH2 NPDCCH2
  • UE monitors for the second NPDCCH until 2ms or more before the start of the NPDSCH (NPDSCH1) transmission associated with the first NPDCCH.
  • the two back to back NPDCCHs are either both for DL grant or both for UL grant.
  • UE receives two consecutive UL grants or two consecutive DL grants.
  • Receiving consecutive UL grants comprises receiving a UL grant as the next grant after a UL grant
  • receiving consecutive DL grants comprises receiving a DL grant as the next grant after a DL grant.
  • the DL and UL subframes can interlace during NPUSCH/NPDSCH transmission.
  • UE may receive some DL subframes for a DL packet (e.g., associated with NPDCCH for DL grant) , followed by UL transmission for an UL packet (e.g., associated with NPDCCH for UL grant) , then followed by repetition for the same DL packet, followed again by some repetitions of the same UL packet, and so on.
  • an UE may only receive two DL grants back to back or two UL grants back to back for NB-IoT, and receiving interlaced UL and DL grants by a UE is not supported.
  • NB-IoT For Rel-15, extending NB-IoT to TDD mode may be discussed.
  • parallel uplink and downlink transmission means for example, UE receives DL transmission of DL packet followed by UL transmission of a UL packet, followed by repetition of the same DL packet followed by repletion of same UL packet.
  • the DL/UL grants would also need to be interlaced, and this feature is not supported by the current standard specification.
  • Receiving interlaced UL and DL grants comprises receiving a DL grant as the next grant after an UL grant, or receiving an UL grant as the next grant after a DL grant.
  • Interlacing UL and DL grants is needed in order to support interlacing UL and DL transmission, especially for TDD.
  • Interlacing UL and DL grants may also be beneficial for FDD, for example, to improve UL/DL transmission efficiency (e.g., for some current TDM-based applications, for UL data transmission, may need to finish DL data transmission first) .
  • Interlaced UL and DL grants can be supported so that an UE can receive two grants, one for UL and one for DL, before the start of the corresponding NPUSCH or NPDSCH transmission.
  • the rules of timing limitation between NPDCCH and NPDSCH/NPUSCH can be unchanged.
  • the gap between the 2 nd NPDCCH to the start of NPDSCH or NPUSCH may be ⁇ 2ms.
  • an UE is not required to monitor the NPDCCH (e.g., for a third grant) between the start of NPDSCH to HARQ-ACK. This simplifies UE implementation and conserves UE power because otherwise the UE would need to receive DL control information in addition to receiving data at the same time.
  • there is no restriction on the order of interlaced UL and DL grants e.g., the first grant can be either UL or DL grant.
  • Figure 12 illustrates example interlaced grants (DL followed by UL) in accordance with certain aspects of the present disclosure.
  • first grant is UL grant and second grant is DL grant.
  • Time delay from a grant to the associated data transmission may be the same as described above (e.g., 8ms or more between UL grant and associated NPUSCH transmission, 5ms or more between DL grant and associated NPDSCH transmission) .
  • UL data transmission e.g., on NPUSCH
  • the order of data transmission is different.
  • the UL data transmission (e.g., on NPUSCH) takes place before DL data transmission (e.g., on NPDSCH) .
  • UL data transmission (e.g., on NPUSCH) takes place after HARQ-ACK associated with the DL data transmission (e.g., on NPDSCH) . Therefore, the order of data transmission is determined by, for example, the delay between the NPDCCH and the associated data transmission (e.g., determined by a field in NPDCCH) .
  • Figure 13 illustrates example interlaced grants (UL followed by DL) in accordance with certain aspects of the present disclosure. Figure 13 illustrates similar concepts as Figure 12.
  • NPUSCH and NPDCCH interlacing may be supported, e.g., an UE can continue to monitor the NPDCCH search space when doing NPUSCH transmission.
  • TDD UL-DL configuration there may be some DL subframes (SFs) between UL transmission, and UE may switch from UL transmission (e.g., NPUSCH transmission) to monitoring NPDCCH search space during the DL SFs.
  • SFs DL subframes
  • an UE may be required to continue to monitor the search space unless the DL subframe is used for NPDSCH.
  • a guard subframe is needed to switch from UL to DL or from DL to UL then the associated DL or UL transmission will be postponed to a next available SF in case of interlacing DL and UL data transmission. If a few OFDM symbols are needed to switch from UL to DL or from DL to UL, then for example the associated DL or UL transmission in the subframe may be punctured in the case of interlacing DL and UL data transmission.
  • the switch when the switch is from UL to DL, then the first two symbols in a second subframe (DL) may be punctured, and when the switch is from DL to UL, then the last symbol in the first subframe (DL) and the first symbol in the second subframe (UL) may be punctured.
  • Figure 14 illustrates example interlaced NPDCCH and NPUSCH in accordance with certain aspects of the present disclosure.
  • TDD UL-DL configuration 1 is illustrated.
  • NPDCCH NPDCCH1 for UL grant is received by UE.
  • a set of repetitions of uplink data transmission (e.g., for enhanced coverage) may be sent on NPUSCH.
  • the number of repetitions is 8 (e.g., 8 subframes) .
  • Due to TDD frame structure there may be some DL subframes between repetitions of the uplink data on NPUSCH. Normally, UE does not utilize these DL subframes between NPUSCH transmissions because it would not be efficient.
  • these DL SFs may be utilized to monitor for NPDCCH.
  • a guard subframe is used for switching from UL to DL so that a first DL subframe may serve as a guard subframe (indicated by “G” in Figure 14) and a second, adjacent DL subframe may be used for NPDCCH (e.g., NPDCCH2) . If a few OFDM symbols are used for switching from UL to DL, then there is no need for guard subframes and the second NPDCCH (NPDCCH2) can be transmitted in the DL subframe right after the UL subframe.
  • Interlaced UL/DL grants can be supported with or without two HARQ processes support. If interlacing UL and DL grants is supported with two HARQ processes, up to 4 NPDCCHs can be received, e.g., two for DL and two for UL grants. In case of back-to-back DL grants or UL grants, the two grants could have same or different HARQ IDs. Same HARQ IDs may mean repetition transmission (e.g., retransmission of a first NPDCCH) . For different HARQ IDs, the two HARQ IDs may appear in any order, or the first grant may always have HARQ ID 0 and second grant HARQ ID 1 (e.g., fixed order) .
  • UE can discard one of them; for example, A) discard the one with lowest energy; B) always discard either the first one or the second one; or C) combination of the two, e.g., always discard first one if both have energy above some threshold.
  • an UE honors both grants treating them as HARQ retransmissions.
  • UE’s support of interlacing UL and DL grants can be separate, or independent from its support of two HARQ processes (e.g., UE can support interlacing UL and DL grants, or two HARQ processes, or both) .
  • the support of interlacing UL and DL grants may be indicated separately by an UE for the support of two HARQ processes.
  • UE may indicate the support of interlacing UL and DL grants using capability signaling and indicate the support of two HARQ processes independently (e.g., using different capability signaling) when it attaches to a network.
  • example timelines for two HARQ processes are shown below.
  • Timeline 1 NPDCCH1 NPDCCH2 NPDSCHA ACKA NPDSCHB ACKB
  • Timeline 2 NPDCCH1 NPDCCH2 NPDSCHA NPDSCHB ACKA ACKB
  • NPDSCH A may always map to NPDCCH 1 and NPDSCH B may always map to NPDCCH2, and other mappings may be treated as error case and UE may discard one of the grants.
  • both mappings e.g., NPDSCHA to NPDCCH1 or NPDCCH 2 are allowed.
  • techniques for uplink and downlink grants in narrowband operations are desirable. Accordingly, techniques presented herein may be used for uplink and downlink grants in narrowband operations (e.g., NB-IoT) .
  • narrowband operations e.g., NB-IoT
  • FIG. 15 is a flow diagram illustrating example operations 1500 for receiving interlaced UL and DL grants, according to aspects described herein.
  • Operations 1500 may be performed, for example, by a UE (e.g., UE 120) which may be a low cost, IoT device, such as an NB-IoT device.
  • Operations 1500 may begin, at 1502, by monitoring a control channel in a narrowband of a system bandwidth for an uplink (UL) or a downlink (DL) grant.
  • the UE receives interlaced UL and DL grants.
  • the UE sends or receives information in response to the received interlaced UL and DL grants.
  • FIG. 16 is a flow diagram illustrating example operations 1600 for UE behavior when receiving back to back UL grants or DL grants with same HARQ IDs, according to aspects described herein.
  • Operations 1600 may be performed, for example, by a UE (e.g., UE 120) which may be a low cost, IoT device, such as an NB-IoT device.
  • Operations 1600 may begin, at 1602, by monitoring a control channel in a narrowband of a system bandwidth for an uplink (UL) or a downlink (DL) grant.
  • the UE receives two consecutive UL or DL grants, wherein the consecutive UL or DL grants have a same HARQ process identification (ID) .
  • ID HARQ process identification
  • the UE selects a grant to use based, at least in part, on at least one of: a grant that meets an energy metric threshold; a grant that is received first; or a grant that is received second.
  • the UE can alternatively select both grants to use, wherein the grants are treated as HARQ retransmissions.
  • eNB may schedule a UE such that there are collisions across channels, e.g., through incorrect scheduling.
  • a collision may occur, e.g., when two or more sets of information are transmitted or received on the same resource (e.g., subframe) simultaneously.
  • a UE may have two back to back NPDSCHs whose ACKs collide or have the second NPDSCH collide with ACK for the first NPDSCH, etc.
  • back to back NPUSCHs there may be similar types of collisions. If interlaced UL and DL grants are implemented, there may also be collisions of NPUSCH with NPDSCH, NPUSCH with ACK, etc. Example UE behavior in case of such collisions is illustrated herein and may be applicable to TDD and/or FDD.
  • FIG. 17 is a flow diagram illustrating example operations 1700 for UE behavior in connection with collisions when receiving back to back UL grants or DL grants, according to aspects described herein.
  • Operations 1700 may be performed, for example, by a UE (e.g., UE 120) which may be a low cost, IoT device, such as an NB-IoT device.
  • Operations 1700 may begin, at 1702, by monitoring a control channel in a narrowband of a system bandwidth for an uplink (UL) or a downlink (DL) grant.
  • UL uplink
  • DL downlink
  • the UE receives two consecutive UL or DL grants.
  • the UE sends or receives information in response to the received two consecutive UL and DL grants.
  • the UE in response to the sending or receiving information, the UE identifies a collision, the collision comprising at least one of: collision between first DL data channel and second DL data channel; collision between the second DL data channel and first HARQ acknowledgement (HARQ-ACK) signaling for the first DL data channel; collision between first HARQ-ACK signaling for the first DL data channel and second HARQ-ACK signaling for the second DL data channel; or collision between first UL data channel and second UL data channel.
  • HARQ-ACK HARQ acknowledgement
  • both NPDSCHs may be treated as valid NPDSCHs and attempt may be made to decode using 1 ) non-colliding subframes in both NPDSCHs (e.g., UE decodes both of them) or 2) colliding SFs only for one of the NPDSCH (e.g., UE decodes only one of the two, the first one, the second one, or based on associated control channel energy metrics) .
  • only one of the NPDSCHs may be monitored –e.g., the first NPDSCH, or the second NPDSCH, or based on the corresponding NPDCCH energy metrics (e.g., associated control channel energy detection) .
  • the first NPDSCH may refer to the NPDSCH starting first or whose NPDCCH started first
  • the second NPDSCH may refer to the NPDSCH starting second or whose NPDCCH started second.
  • NPDSCH to ACK collision In the case ofNPDSCH to ACK collision (e.g., ACK for a first NPDSCH is colliding with a second NPDSCH) , in one aspect, treat it as incorrect grant and drop one of the NPDSCH and corresponding ACK (similar to NPDSCH to NPDSCH collision) .
  • ACK may be dropped. (entirely or partly, e.g., on colliding subframes) .
  • NPDSCH may be dropped (entirely or partly, e.g., on colliding subframes) .
  • Colliding SFs could include SFs containing ACK/NPDSCH as well as guard SFs for switch from UL to DL, etc.
  • ACK to ACK collision in one aspect, treat it as incorrect grant and drop one of the NPDSCHs (similar to NPDSCH to NPDSCH collision) or ACKs.
  • one of the NPUSCHs may be dropped.
  • one of the NPUSCHs may be punctured and the other NPUSCH may be transmitted fully.
  • the dropped or punctured NPUSCH may be the first one always, the second one always, or based on NPDCCH energy metric.
  • NPUSCH to NPDSCH collision in one aspect, treat it as incorrect grant and drop either NPUSCH or NPDSCH (for example, the first, or the second, or based on the NPDCCH energy metrics etc. ) .
  • NPUSCH or NPDSCH for example, the first, or the second, or based on the NPDCCH energy metrics etc.
  • one of the NPUSCH or NPDSCH may be dropped or punctured.
  • the dropped or punctured channel may be the first one always, the second one always, or based on NPDCCH energy metrics.
  • NPUSCH to HARQ-ACK collision in one aspect, only one of them is retained in colliding SFs by prioritizing one channel over the other (e.g., HARQ-ACK prioritized over NPUSCH) .
  • HARQ-ACK may be multiplexed on NPUSCH (e.g., HARQ-ACK is used to modulate the DMRS of NPUSCH in colliding SFs) .
  • identifying encompasses a wide variety of actions. For example, “identifying” may include calculating, computing, processing, deriving, investigating, looking up (e.g., looking up in a table, a database or another data structure) , ascertaining and the like. Also, “identifying” may include receiving (e.g., receiving information) , accessing (e.g., accessing data in a memory) and the like. Also, “identifying” may include resolving, selecting, choosing, establishing and the like.
  • the term “or” is intended to mean an inclusive “or” rather than an exclusive “or. ” That is, unless specified otherwise, or clear from the context, the phrase, for example, “X employs A or B” is intended to mean any of the natural inclusive permutations. That is, for example the phrase “X employs A or B” is satisfied by any of the following instances: X employs A; X employs B; or X employs both A and B.
  • reference to an element in the singular is not intended to mean “one and only one” unless specifically so stated, but rather “one or more.
  • “at least one of: a, b, or c” is intended to cover: a, b, c, a-b, a-c, b-c, and a-b-c, as well as any combination with multiples of the same element (e.g., a-a, a-a-a, a-a-b, a-a-c, a-b-b, a-c-c, b-b, b-b-b, b-b-c, c-c, and c-c-c or any other ordering of a, b, and c) .
  • the term “and/or, ” when used in a list of two or more items means that any one of the listed items can be employed by itself, or any combination of two or more of the listed items can be employed.
  • the composition can contain A alone; B alone; C alone; A and B in combination; A and C in combination; B and C in combination; or A, B, and C in combination.
  • a device may have an interface to communicate a frame for transmission or reception.
  • a processor may output a frame, via a bus interface, to an RF front end for transmission.
  • a device may have an interface to obtain a frame received from another device.
  • a processor may obtain (or receive) a frame, via a bus interface, from an RF front end for transmission.
  • the methods disclosed herein comprise one or more steps or actions for achieving the described method.
  • the method steps and/or actions may be interchanged with one another without departing from the scope of the claims.
  • the order and/or use of specific steps and/or actions may be modified without departing from the scope of the claims.
  • the various operations of methods described above may be performed by any suitable means capable of performing the corresponding functions.
  • the means may include various hardware and/or software component (s) and/or module (s) , including, but not limited to a circuit, an application specific integrated circuit (ASIC) , or processor.
  • ASIC application specific integrated circuit
  • those operations may be performed by any suitable corresponding counterpart means-plus-function components.
  • means for monitoring, means for identifying, means for selecting, means for determining, means for performing, means for transmitting, means for receiving, means for sending, means for signaling, means for requesting, and/or means for deriving may include one or more processors, transmitters, receivers, antennas, and/or other elements of the user equipment 120 and/or the base station 110 illustrated in FIG. 2.
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • FPGA field programmable gate array
  • One or more aforementioned devices or processors may execute software.
  • a general-purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine.
  • a processor may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.
  • a software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, phase change memory, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.
  • An exemplary storage medium is coupled to the processor such that the processor can read information from, and write information to, the storage medium.
  • the storage medium may be integral to the processor.
  • the processor and the storage medium may reside in an ASIC.
  • the ASIC may reside in a user terminal.
  • the processor and the storage medium may reside as discrete components in a user terminal.
  • the functions described may be implemented in hardware, software, or combinations thereof. If implemented in software, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium.
  • Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another.
  • a storage media may be any available media that can be accessed by a general purpose or special purpose computer.
  • such computer-readable media can comprise RAM, ROM, EEPROM, CD/DVD or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to carry or store desired program code means in the form of instructions or data structures and that can be accessed by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor. Also, any connection is properly termed a computer-readable medium.
  • Disk and disc includes compact disc (CD) , laser disc, optical disc, digital versatile disc (DVD) , floppy disk and disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above should also be included within the scope of computer-readable media.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Selon certains aspects, la présente invention concerne des procédés et un appareil de communication sans fil. Selon un aspect, l'invention concerne un procédé qui peut être exécuté par un dispositif sans fil, un équipement d'utilisateur (UE) par ex., qui peut être un dispositif de l'Internet des objets (IoT). D'un point de vue général, le procédé consiste à : surveiller un canal de commande dans une bande étroite d'une bande passante système pour une autorisation de liaison montante (UL) ou de liaison descendante (DL) ; recevoir des autorisations UL et DL entrelacées ; et envoyer ou recevoir des informations en réponse aux autorisations UL et DL entrelacées reçues.
PCT/CN2017/095169 2017-07-31 2017-07-31 Autorisations de liaison montante et de liaison descendante pour opérations à bande étroite WO2019023849A1 (fr)

Priority Applications (9)

Application Number Priority Date Filing Date Title
PCT/CN2017/095169 WO2019023849A1 (fr) 2017-07-31 2017-07-31 Autorisations de liaison montante et de liaison descendante pour opérations à bande étroite
JP2020504334A JP2020529164A (ja) 2017-07-31 2018-07-25 狭帯域動作用のアップリンク許可およびダウンリンク許可
PCT/CN2018/097029 WO2019024737A1 (fr) 2017-07-31 2018-07-25 Autorisations de liaison montante et de liaison descendante pour opérations à bande étroite
CN201880047197.0A CN110892690B (zh) 2017-07-31 2018-07-25 用于窄带操作的上行链路和下行链路授权
EP18840636.7A EP3662625A4 (fr) 2017-07-31 2018-07-25 Autorisations de liaison montante et de liaison descendante pour opérations à bande étroite
BR112020001788-4A BR112020001788A2 (pt) 2017-07-31 2018-07-25 concessões uplink e downlink para operações de banda estreita
TW107125667A TWI762683B (zh) 2017-07-31 2018-07-25 用於窄頻操作的上行鏈路和下行鏈路授權
CA3068759A CA3068759A1 (fr) 2017-07-31 2018-07-25 Autorisations de liaison montante et de liaison descendante pour operations a bande etroite
KR1020207002986A KR20200035034A (ko) 2017-07-31 2018-07-25 협대역 동작들을 위한 업링크 및 다운링크 승인들

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2017/095169 WO2019023849A1 (fr) 2017-07-31 2017-07-31 Autorisations de liaison montante et de liaison descendante pour opérations à bande étroite

Publications (1)

Publication Number Publication Date
WO2019023849A1 true WO2019023849A1 (fr) 2019-02-07

Family

ID=65233203

Family Applications (2)

Application Number Title Priority Date Filing Date
PCT/CN2017/095169 WO2019023849A1 (fr) 2017-07-31 2017-07-31 Autorisations de liaison montante et de liaison descendante pour opérations à bande étroite
PCT/CN2018/097029 WO2019024737A1 (fr) 2017-07-31 2018-07-25 Autorisations de liaison montante et de liaison descendante pour opérations à bande étroite

Family Applications After (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/097029 WO2019024737A1 (fr) 2017-07-31 2018-07-25 Autorisations de liaison montante et de liaison descendante pour opérations à bande étroite

Country Status (8)

Country Link
EP (1) EP3662625A4 (fr)
JP (1) JP2020529164A (fr)
KR (1) KR20200035034A (fr)
CN (1) CN110892690B (fr)
BR (1) BR112020001788A2 (fr)
CA (1) CA3068759A1 (fr)
TW (1) TWI762683B (fr)
WO (2) WO2019023849A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112042148A (zh) * 2019-04-03 2020-12-04 联发科技股份有限公司 基于多下行链路控制信息的多发送接收点接收操作的控制技术

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112311515B (zh) * 2019-08-01 2022-03-29 北京华为数字技术有限公司 一种反馈信息传输方法及装置
CN115348610B (zh) * 2022-10-18 2023-03-24 成都市以太节点科技有限公司 一种毫米波多链路自适应通信方法、电子设备及存储介质

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103378932A (zh) * 2012-04-26 2013-10-30 华为技术有限公司 数据传输方法、用户设备及基站

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CA2850569C (fr) * 2011-09-30 2020-03-10 Interdigital Patent Holdings, Inc. Communication entre dispositifs a l'aide d'une largeur de bande de canal reduite
US9113463B2 (en) * 2011-11-04 2015-08-18 Qualcomm Incorporated Resource management for enhanced PDCCH
CA2862674C (fr) * 2012-01-30 2017-05-30 Zte (Usa) Inc. Procede et systeme pour le multiplexage de canal de commande de liaison descendante physique
US9743363B2 (en) * 2014-06-24 2017-08-22 Qualcomm Incorporated CCA clearance in unlicensed spectrum
CN104333873A (zh) * 2014-11-28 2015-02-04 东莞宇龙通信科技有限公司 信道检测方法及系统、具有基站功能的设备和终端
US10652872B2 (en) * 2015-07-20 2020-05-12 Lg Electronics Inc. Downlink control information receiving method and user equipment, and downlink control information transmitting method and base station
CN108352932B (zh) * 2015-11-04 2022-03-04 交互数字专利控股公司 用于窄带lte操作的方法和过程
US10454646B2 (en) * 2015-11-14 2019-10-22 Qualcomm Incorporated Sounding reference signal transmissions in enhanced machine type communication

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103378932A (zh) * 2012-04-26 2013-10-30 华为技术有限公司 数据传输方法、用户设备及基站

Non-Patent Citations (5)

* Cited by examiner, † Cited by third party
Title
HUAWEI ET AL.: "Remaining details for 2 HARQ processes", 3GPP TSG RAN WG1 MEETING #88 RI -1701754, 17 February 2017 (2017-02-17), XP051208920 *
MEDIATEK INC: "Remaining issues for Rel-14 NB-loT 2 HARQ processes", 3GPP TSG RAN WGI MEETING #88 RI-1702750, 17 February 2017 (2017-02-17), XP051209897 *
QUALCOMM INCORPORATED: "Summary of email discussion on frame structure", 3GPP TSG-RAN WGI #85 RL-164696, 27 May 2016 (2016-05-27), XP051089939 *
ZTE ET AL.: "WF on UL HARQ-ACK feedback", 3GPP TSG RAN WG1 MEETING #89 RI-1709541, 19 May 2017 (2017-05-19), XP051285259 *
ZTE: "Remaining issues and HARQ bundling for 2 HARQ processes for NB-loT", 3GPP TSG RAN WGI MEETING #88 R1-1701909, 17 February 2017 (2017-02-17), XP051209072 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112042148A (zh) * 2019-04-03 2020-12-04 联发科技股份有限公司 基于多下行链路控制信息的多发送接收点接收操作的控制技术
CN112042148B (zh) * 2019-04-03 2023-10-13 联发科技股份有限公司 无线通信方法、无线通信装置及其计算机可读介质

Also Published As

Publication number Publication date
EP3662625A1 (fr) 2020-06-10
WO2019024737A1 (fr) 2019-02-07
KR20200035034A (ko) 2020-04-01
BR112020001788A2 (pt) 2020-07-21
CA3068759A1 (fr) 2019-02-07
TW201921871A (zh) 2019-06-01
JP2020529164A (ja) 2020-10-01
TWI762683B (zh) 2022-05-01
EP3662625A4 (fr) 2021-03-03
CN110892690B (zh) 2023-02-17
CN110892690A (zh) 2020-03-17

Similar Documents

Publication Publication Date Title
CN110832939B (zh) 用于补充上行链路随机接入配置的技术和装置
AU2017271996B2 (en) Uplink transmission gaps in eMTC
EP3469755B1 (fr) Détermination de la largeur de bande et de la présence de signaux de référence dans des systèmes à bande étroite
EP3577834B1 (fr) Allocation de ressources pour canal de commande de liaison montante physique (pucch)
EP3616464B1 (fr) Transition rapide en mode veille de communications de type machine améliorées après libération de connexion
WO2017213795A1 (fr) Multidiffusion et/ou diffusion pour des communications de type machine améliorées et/ou l'internet des objets à bande étroite
WO2019047152A1 (fr) Techniques et appareils pour améliorer une nouvelle couverture radio
CN110892690B (zh) 用于窄带操作的上行链路和下行链路授权
EP3665816B1 (fr) Techniques et appareils pour une transmission de communication à faible latence ultra-fiable à l'aide de ressources sans autorisation
WO2019169576A1 (fr) Niveau d'amélioration de couverture (ce) et techniques de détermination de puissance d'émission destinés à un équipement d'utilisateur (ue) dans une couverture étendue
US11375515B2 (en) Enhanced non-linear interference cancellation (NLIC) operation
WO2018223303A1 (fr) Améliorations de canal d'accès aléatoire pour systèmes à bande étroite

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 17919802

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 17919802

Country of ref document: EP

Kind code of ref document: A1