TW201921871A - Uplink and downlink grants for narrowband operations - Google Patents

Abstract

Aspects of the present disclosure provide techniques and apparatus for wireless communication. In one aspect, a method is provided which may be performed by a wireless device such as a user equipment (UE), which can be an Internet-of-things (IoT) device. 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, sending or receiving information in response to the received interlaced UL and DL grants.

Description

Uplink and downlink grants for narrowband operation

This patent application claims the priority of the international patent application number PCT / CN2017 / 095169, which was assigned to the assignee on July 31, 2017.

Certain aspects of this case are related to wireless communications, and more specifically, to uplink (UL) and downlink (DL) authorizations for narrowband operation.

Wireless communication systems are widely deployed to provide a variety of communication content, such as voice and data. Such systems may be multiplexed access systems capable of supporting communication with multiple users by sharing the available system resources (eg, bandwidth and transmit power). Examples of such multiplexing technologies include Code Division Multiplexing (CDMA) systems, Time Division Multiplexing (TDMA) systems, Frequency Division Multiplexing (FDMA) systems, and third-generation partner programs (3GPP) Long Term Evolution (LTE) / Advanced LTE (LTE-A) system and Orthogonal Frequency Division Multiplexing Access (OFDMA) system.

Generally, a wireless multiplexing communication system can support communication of multiple wireless terminals simultaneously. Each terminal communicates with one or more base stations (BS) via transmissions on the forward and reverse links. The forward link (or downlink) refers to the communication link from the BS to the terminal, and the reverse link (or uplink) refers to the communication link from the terminal to the BS. The communication link can be established via a single-in-single-out, multiple-in-single-out or a multiple-in-multiple-out (MIMO) system.

The wireless communication network may include multiple BSs that can support communication for multiple wireless devices. The wireless device may include a user equipment (UE). Machine type communication (MTC) may refer to communication involving at least one remote device on at least one end of the communication, and may include a form of data communication involving one or more entities that do not necessarily require human interaction. For example, the MTC UE may include a UE capable of MTC communication with a MTC server and / or other MTC devices via a public land mobile network (PLMN). Wireless devices may include Internet of Things (IoT) devices (eg, narrowband IoT (NB-IoT) devices). IoT can refer to a network of physical objects, devices, or "things." IoT devices may be embedded with, for example, electronic devices, software or sensors, and may have a network connection, which enables such devices to collect and exchange data.

Some next-generation, NR, or 5G networks can include multiple base stations, and each base station supports communications from multiple communications devices (such as UEs) simultaneously. In an LTE or LTE-A network, a set of one or more BSs may define an eNodeB (eNB). In other examples (eg, in a next-generation or 5G network), a wireless multiplex communication system may include communication with multiple central units (eg, CU, Central Node (CN), Access Node Controller (ANC) Etc.) multiple decentralized units (such as edge unit (EU), edge node (EN), radio head (RH), smart radio head (SRH), transmission and reception point (TRP), etc.) The set of one or more decentralized units (DUs) in communication can define an access node (eg, AN, New Radio Base Station (NR BS), NR NB, Network Node, gNB, 5G BS, Access Point (AP) )Wait). The BS or DU may communicate with the UE collective on the downlink channel (for example, for transmission from the BS or to the UE) and the uplink channel (for example, for transmission from the UE to the BS or DU).

These multiplexed access technologies have been adopted in various telecommunication standards to provide shared protocols that enable different wireless devices to communicate at the city, national, regional, and even global levels. NR (for example, 5G radio access) is an example of an emerging telecommunications standard. NR is a set of enhancements to the LTE mobile service standard promulgated by 3GPP. NR is designed to use OFDMA with Cyclic Prefix (CP) and other open standards on the downlink (DL) and uplink (UL) by increasing spectrum efficiency, reducing costs, improving services, leveraging new spectrum Better integration to better support mobile broadband Internet access and support for beamforming, MIMO antenna technology and carrier aggregation.

However, as the demand for mobile broadband access continues to increase, there is a need for further improvements in LTE, MTC, IoT, and NR (new radio) technologies. Preferably, these improvements should apply to other multiplexed access technologies and telecommunications standards that use them.

Each of the systems, methods, and devices in this case has several aspects, none of which is solely responsible for its desired attributes. Without limiting the scope of the content of this case as expressed by the scope of the appended patent applications, some features will now be briefly discussed. After considering this discussion, and especially after reading the section entitled "Detailed Description", it will be understood how the features of the content of this case provide improved communication between access points and stations in a wireless network. advantage.

Certain aspects of the content of this case relate generally to uplink and downlink operations for narrowband operation.

Certain aspects of the subject matter provide a method performed by a wireless device such as a user equipment (UE). The method roughly includes: monitoring a control channel in a narrow frequency band of a system bandwidth for uplink (UL) or downlink (DL) grants; receiving interlaced UL and DL grants; and responding to the received interlaced UL And DL authorization to send or receive information.

Certain aspects of the subject matter provide a method performed by a wireless device such as a UE. The method roughly includes: monitoring a control channel in a narrow frequency band of a system bandwidth for uplink (UL) or downlink (DL) grants; receiving two consecutive UL or DL grants, of which consecutive UL or DL grants Having the same HARQ process identification (ID); and selecting one of the authorizations to be used based at least in part on at least one of the following: an authorization that meets an energy metric threshold, an authorization that is received first, or an authorization that is received second, Alternatively, two authorizations are selected, where the authorization is considered as a hybrid automatic repeat request (HARQ) retransmission.

Certain aspects of the subject matter provide a method performed by a wireless device such as a UE. The method roughly includes: monitoring a control channel in a narrow frequency band of a system bandwidth for uplink (UL) or downlink (DL) grants; receiving two consecutive UL or DL grants; and responding to the two received Continuous UL and DL authorization to send or receive information; and to identify conflicts in response to sending or receiving information, the conflict including at least one of: a conflict between a first DL data channel and a second DL data channel, and a second DL Conflict between the data channel and the first HARQ-ACK signal transmission for the first DL data channel, the first HARQ-ACK signal transmission for the first DL data channel and the second DL data channel Conflict between the second HARQ-ACK signal transmission, or conflict between the first UL data channel and the second UL data channel.

Certain aspects of the present case 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 narrow bandwidth of the system bandwidth; and transmitting or Receive information.

Certain aspects of the present case provide a method performed by a wireless device such as a base station (BS). The method roughly includes: transmitting two consecutive uplink (UL) or downlink (DL) grants to a user equipment (UE) on a control channel in a narrow frequency band of a system bandwidth, the continuous UL or DL Authorizations have the same HARQ process identification (ID), where the authorization to be used is selected by the UE based at least in part on at least one of the following: an authorization that meets the energy metric threshold, the authorization received first, or the second authorization received Or the UE selects two grants to use, where the grants are considered as Hybrid Automatic Repeat Request (HARQ) retransmissions.

Certain aspects of the present case provide a method performed by a wireless device such as a base station (BS). The method roughly includes: transmitting two consecutive UL or DL grants to a user equipment (UE) on a control channel in a narrow frequency band of a system bandwidth; sending or Receiving information, in response to sending or receiving information, identifying conflicts including at least one of: a conflict between a first DL data channel and a second DL data channel, and a second DL data channel and the first DL data channel Conflict between the first HARQ-ACK signal transmission for the first HARQ-ACK signal transmission for the first DL data channel and the second HARQ-ACK signal transmission for the second DL data channel Conflict between the first UL data channel and the second UL data channel.

Many other aspects are provided, including methods, devices, systems, computer program products, computer-readable media, and processing systems. To achieve the foregoing and related objectives, one or more aspects include features fully described below and specifically pointed out in the scope of the patent application. The following description and the annexed drawings set forth in detail certain illustrative features of one or more aspects. However, the features only indicate some of the various ways in which the principles of the various aspects can be adopted, and the description is intended to include all such aspects and their equivalent transformations.

Various aspects of the content of this case provide techniques for uplink and downlink operation for narrowband operation. The techniques described herein can be used in various wireless communication networks such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, and other networks. The terms "network" and "system" are often used interchangeably. CDMA networks can implement radio technologies such as Universal Terrestrial Radio Access (UTRA), cdma2000, and so on. 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. TDMA networks can implement radio technologies such as the Global System for Mobile Communications (GSM). OFDMA networks can implement radio technologies such as Evolved UTRA (E-UTRA), Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM®, and more. UTRA and E-UTRA are part of the Universal Mobile Telecommunications System (UMTS). 3GPP Long Term Evolution (LTE) and Advanced LTE (LTE-A) in Frequency Division Duplex (FDD) and Time Division Duplex (TDD) are new versions of UMTS using E-UTRA, which uses OFDMA on the downlink And SC-FDMA is used on the uplink. UTRA, E-UTRA, UMTS, LTE, LTE-A, and GSM are described in documents from an organization named "3rd Generation Partnership Project" (3GPP). Cdma2000 and UMB are described in documents from an organization named "3rd Generation Partnership Project 2" (3GPP2). NR (for example, 5G radio access) is an example of an emerging telecommunications standard. NR is a set of enhancements to the LTE mobile service standard released by 3GPP. The techniques described herein can be used for the wireless networks and radio technologies mentioned above as well as other wireless networks and radio technologies. For clarity, some aspects of these technologies are described below for LTE / LTE-Advanced, and LTE / LTE-Advanced (LTE-A) terminology is used in most of the description below. LTE and LTE-A are commonly referred to as LTE.

Note that although various aspects commonly used in 3G and / or 4G wireless technologies can be described herein, aspects of the content of this case can be applied to communication systems based on other generations, such as 5G and later versions. Exemplary wireless communication network

FIG. 1 illustrates an exemplary wireless communication network 100 in which aspects of the present disclosure may be practiced. For example, the technology provided herein can be used for UL and DL authorization for narrowband operation in the wireless communication network 100. The wireless communication network 100 can be a NB-IoT and / or enhanced / evolved machine type communication (EMTC) network. The wireless communication network 100 may include a base station (BS) 110 and a user equipment (UE) 120. In various aspects, the BS 110 may determine at least one narrow frequency region in a wide frequency region for communication with the UE 120. The UE 120 may be a low-cost device, such as an NB-IoT device or an eMTC UE. The UE 120 may determine a narrowband area and receive, send, monitor, or decode information on the narrowband area to communicate with the BS 110.

The 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. The wireless communication network 100 may include multiple BSs 110 and other network entities. BS is the entity that communicates with the UE and can also be called NR BS, Node B (NB), Evolution / Enhanced NB (eNB), 5G NB, gNB, Access Point (AP), and Transmission Receive Point (TRP) Wait. Each BS can provide communication coverage for a specific geographic area. In 3GPP, the term "cell" may refer to a coverage area of a BS and / or a BS subsystem serving the coverage area, depending on the context in which the term is used.

BS can provide communication coverage for macro cells, pico cells, femto cells, and / or other types of cells. Macro cells can cover a relatively large geographic area (eg, several kilometers in radius) and can allow unrestricted access for UEs with service subscriptions. Pico cells can cover a small geographic area and can allow unlimited access for UEs with service subscription. A femtocell may cover a small geographic area (eg, a home) and may allow restricted access to UEs (eg, UEs in a closed user group (CSG)) associated with the femtocell. The BS for macro cells can be referred to as a macro BS. The BS for a pico cell may be referred to as a pico BS. The BS for a femtocell may be referred to as a femto BS or a home BS. In the example shown in FIG. 1, BS 110a may be a macro BS for macro cells 102a, BS 110b may be a pico BS for pico cells 102b, and BS 110c may be a femto cell for femto cells 102c. Pico BS. A BS can support one or more (eg, three) cells. The terms "base station" and "cell" are used interchangeably herein.

The wireless communication network 100 may also include a relay station. A relay station is an entity that receives a data transmission from an upstream station (for example, BS 110 or UE 120) and sends the data transmission to a downstream station (for example, UE 120 or BS 110). The relay station may also be a UE that relays transmissions for other UEs. In the example shown in FIG. 1, the relay station 110 d may communicate with the macro BS 110 a and the UE 120 d so as to realize communication between the BS 110 a and the UE 120 d. The relay station may also be called a relay BS, a relay, and the like.

The wireless communication network 100 may be a heterogeneous network including different types of BSs (eg, a macro BS, a pico BS, a femto BS, a relay BS, etc.). The different types of BSs may have different transmit power levels, different coverage areas, and different effects on interference in the wireless communication network 100. For example, the macro BS may have a high transmission power level (for example, 5 to 40 watts), and the pico BS, femto BS, and relay BS may have a lower transmission power level (for example, 0.1 to 2 watts).

The network controller 130 may be coupled to a group of BSs and provide coordination and control for those BSs. The network controller 130 can communicate with the BS via the backhaul. The BSs can also communicate with each other directly or indirectly, such as via wireless or wired backhaul.

UEs 120 (eg, UE 120a, UE 120b, UE 120c) may be dispersed throughout the wireless communication network 100, and each UE may be stationary or mobile. The UE may also be referred to as an access terminal, terminal, mobile station, subscriber unit, station, customer premises equipment (CPE), and so on. 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 wireless phone, a wireless area loop (WLL) station, a tablet computer, Cameras, drones, robots / robot devices, small laptops, smart computers, ultrabooks, medical devices, medical devices, healthcare devices, biosensors / devices, such as smart watches, smart clothes, smart glasses, virtual reality Environment glasses, smart bracelets and / or smart jewelry (such as smart rings, smart bracelets, etc.) wearables, entertainment equipment (such as music equipment, video equipment, gaming equipment, satellite radio equipment, etc.), industrial manufacturing equipment, navigation / Location equipment (eg, GNSS (Global Navigation Satellite System) equipment based on, for example, GPS (Global Positioning System), Beidou, GLONASS, Galileo, ground-based equipment, etc.), or any device configured to communicate via wireless or wired media Other suitable equipment. Some UEs can be implemented as IoT (Internet of Things) UEs. IoT UE includes, for example, robots / robot devices, drones, remote devices, sensors, meters, monitors, cameras, location tags, etc., which can interact with the BS, another device (eg, remote device), or some other entity communication. The IoT UE may include MTC / eMTC UE, NB-IoT UE, and other types of UE. A wireless node may provide, for example, a connection for or to a network (eg, a wide area network such as the Internet or a cellular network) via a wired or wireless communication link.

One or more UEs 120 (eg, an LTE network) in the wireless communication network 100 may be narrow-bandwidth UEs. As used herein, a device with limited communication resources (eg, a smaller bandwidth) may be referred to collectively as a narrow-band UE. Similarly, legacy devices such as legacy and / or advanced UEs (eg, in LTE) may be generically referred to as broadband UEs. Generally, a wideband UE can operate on a larger amount of bandwidth than a narrowband UE.

In FIG. 1, a solid line with double arrows indicates a desired transmission 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 potential interfering transmissions between the UE and the BS.

In general, any number of wireless networks can be deployed in a given geographic area. Each wireless network can support a specific radio access technology (RAT) and can operate on one or more frequencies. RAT can also be called radio technology, air interface, etc. Frequency can also be called carrier, frequency channel, and so on. Each frequency can support a single RAT in a given geographic area in order to avoid interference between wireless networks of different RATs. In some cases, NR or 5G RAT networks can be deployed.

In some examples, access to the air interface may be scheduled, where the scheduling entity (eg, BS 110) allocates resources for communication between some or all of its devices and devices within its service area or cell. The scheduling entity may be responsible for scheduling, assigning, reconfiguring, and releasing resources of one or more subordinate entities. For scheduled communications, subordinate entities use resources allocated by the scheduling entity. BS 110 is not the only entity that can function as a scheduling entity. In some examples, the UE 120 may function as a scheduling entity, scheduling resources for one or more subordinate entities (eg, one or more other UEs 120). In this example, the UE functions as a scheduling entity, while other UEs use the resources scheduled by the UE for wireless communication. The UE can function as a scheduling entity in a peer-to-peer (P2P) network and / or a mesh network. In the mesh network example, in addition to communicating with the scheduling entity, the UEs can also optionally communicate directly with each other.

Therefore, in a wireless communication network that has scheduled access to time-frequency resources and has a honeycomb configuration, a P2P configuration, and a mesh configuration, the scheduling entity and one or more subordinate entities can use the scheduled resources to perform communication.

FIG. 2 illustrates a block diagram of a design of the BS 110 and the UE 120, and the BS 110 and the UE 120 may be one of the BS 110 and the UE 120 in FIG. The BS 110 may be equipped with T antennas 234a to 234t, and the UE 120 may be equipped with R antennas 252a to 252r, where usually T ≧ 1 and R ≧ 1.

At BS 110, the transmit processor 220 may receive data for one or more UEs from the data source 212, and select one or more modulation and coding schemes for each UE based on the channel quality indicator (CQI) received from the UEs. (MCS), based on one (or more) MCSs selected for the UE (eg, coding and modulation) for each UE's profile and provides profile symbols for all UEs. The transmitting processor 220 may also process system information (for example, for static resource partition information (SRPI), etc.) and control information (for example, CQI request, authorization, upper-layer signal transmission, etc.), and provide management burden symbols and control symbols. The processor 220 may also generate reference symbols for reference signals (for example, cell-specific reference signals (CRS)) and synchronization signals (for example, primary synchronization signal (PSS) and secondary synchronization signal (SSS)). If applicable, the transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., precoding) on data symbols, control symbols, management burden symbols, and / or reference symbols, and may output T outputs The symbol stream is provided to T modulators (MOD) 232a to 232t. Each modulator 232 may process a corresponding output symbol stream (eg, for OFDM, etc.) to obtain an output sample stream. Each modulator 232 may further process (eg, convert to analog, amplify, filter, and upconvert) the output sample stream to obtain a downlink signal. The T downlink signals from the modulators 232a to 232t may be transmitted via the T antennas 234a to 234t, respectively.

At the UE 120, the antennas 252a to 252r may receive downlink signals from the base station 110 and / or other BSs, and may provide the received signals to the demodulator (DEMOD) 254a to 254r, respectively. Each demodulator 254 can condition (eg, filter, amplify, down-convert, and digitize) its received signal to obtain input samples. Each demodulator 254 may further process the input samples (eg, for OFDM, etc.) to obtain received symbols. The MIMO detector 256 can obtain received symbols from all R demodulators 254a to 254r, and if applicable, perform MIMO detection on the received symbols and provide the detected symbols. The receiving processor 258 may process (eg, demodulate and decode) the detected symbols, provide decoded data for the UE 120 to the data slot 260, and provide decoded control information and system information to the controller / processor 280 . The channel processor can determine the reference signal received power (RSRP), received signal strength indicator (RSSI), reference signal received quality (RSRQ), CQI, and so on.

On the uplink, at the UE 120, the transmit processor 264 can receive and process data from the data source 262 and control information from the controller / processor 280 (for example, used for data including RSRP, RSSI, RSRQ, CQI, etc. report). The processor 264 may also generate reference symbols for one or more reference signals. If applicable, the symbols from the transmit processor 264 may be precoded by the TX MIMO processor 266, further processed by the modulators 254a to 254r (eg, for SC-FDM, OFDM, etc.) and transmitted to the BS 110. At BS 110, uplink signals from UE 120 and other UEs can be received by antenna 234, processed by demodulator 232, detected by MIMO detector 236 (if applicable), and further processed by receiving processor 238 To obtain the decoded data and control information sent by the UE 120. The processor 238 may provide the decoded data to the data slot 239 and the decoded control information to the controller / processor 240. The BS 110 may include a communication unit 244 and communicate with the network controller 130 via the communication unit 244. The network controller 130 may include a communication unit 294, a controller / processor 290, and a memory 292.

Controllers / processors 240 and 280 may direct operations at BS 110 and UE 120, respectively, to perform the techniques provided herein. For example, the processor 240 and / or other processors and modules at the BS 110 and the processor 280 and / or other processors and modules at the UE 120 may perform or direct operations at the BS 110 and the UE 120, respectively. For example, the controller / processor 280 and / or other controllers / processors and modules at the UE 120 may perform or direct operations 1500 shown in FIG. 15, operations 1600 shown in FIG. 16, and operations shown in FIG. Shown operation 1700. The memories 242 and 282 can store data and codes for the BS 110 and the UE 120, respectively. The scheduler 246 may schedule the UE for data transmission on the downlink and / or uplink.

FIG. 3 illustrates an exemplary frame structure 300 for frequency division duplexing (FDD) in a wireless communication system (eg, such as the wireless communication network 100). Transmission isolines of each of the downlink and uplink can be divided into units of a radio frame. Each radio frame may have a predetermined duration (for example, 10 milliseconds (ms)) and may be divided into 10 sub-frames with indices of 0 to 9. Each subframe can include two time slots. Therefore, each radio frame can include 20 time slots with indices 0 to 19. Each time slot may include L symbol periods, for example, seven symbol periods for a common cyclic prefix (as shown in FIG. 3) or six symbol periods for an extended cyclic prefix. An index of 0 to 2L-1 can be assigned to the 2L symbol period in each subframe.

In some wireless communication systems (eg, LTE), a BS (eg, such as BS 110) may transmit PSS and SSS on the downlink at the center of the system bandwidth of each cell supported by the BS. PSS and SSS can be transmitted in symbol periods 6 and 5 in sub-frames 0 and 5 of each radio frame with a normal cyclic prefix, as shown in FIG. 3. A UE (eg, such as UE 120) may use PSS and SSS for cell search and acquisition. The BS can transmit CRS over the system bandwidth for each cell supported by the BS. The CRS may be transmitted in certain symbol periods of each sub-frame and may be used by the UE to perform channel estimation, channel quality measurement, and / or other functions. The BS may also transmit the Physical Broadcast Channel (PBCH) in symbol periods 0 to 3 in slot 1 of some radio frames. PBCH can carry some system information. The BS may transmit other system information such as a system information block (SIB) on a physical downlink shared channel (PDSCH) in some subframes. The BS can transmit control information / data on the physical downlink control channel (PDCCH) in the first B symbol periods of the sub-frame, where B can be configured for each sub-frame. The BS may transmit traffic data and / or other data on the PDSCH in the remaining symbol periods of each sub-frame.

In some systems (for example, such as NR or 5G systems), the BS may transmit these or other signals in these locations or different locations of the sub-frame.

FIG. 4 illustrates two exemplary sub-frame formats 410 and 420 with a common loop prefix. Available time-frequency resources can be divided into resource blocks (RBs). Each RB can cover 12 subcarriers in a time slot, and can include multiple resource elements (RE). Each RE can cover a subcarrier in a symbol period, and can be used to send a modulation symbol. The modulation symbol can be real or complex value.

The sub-frame format 410 can be used for two antennas. CRS can be transmitted from antennas 0 and 1 in symbol periods 0, 4, 7 and 11. The reference signal is a signal known a priori by the transmitter and receiver, and may also be referred to as a pilot frequency. CRS is a cell-specific reference signal, for example, generated based on a cell identification (ID). In FIG. 4, for a given RE with a label Ra, a modulation symbol may be transmitted on the RE from the antenna a, and a modulation symbol may not be transmitted on the RE from other antennas. The sub-frame format 420 can be used with four antennas. CRS can 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. For the sub-frame formats 410 and 420, the CRS can be transmitted on evenly spaced subcarriers, which can be determined according to the cell ID. CRS can be transmitted on the same or different subcarriers, depending on the cell ID of the CRS. For sub-frame formats 410 and 420, REs that are not used for CRS can be used to transmit data (eg, traffic data, control data, and / or other data).

PSS, SSS, CRS, and PBCH in LTE are described in the publicly available 3GPP TS 36.211 entitled "Evolved Universal Terrestrial Radio Access (E-UTRA); Physical Channels and Modulation".

For FDD in LTE, a staggered structure can be used for each of the downlink and uplink. For example, Q interlaces with indices 0 to Q -1 can be defined, where Q can be equal to 4, 6, 8, 10, or some other value. Each interlace may include sub-frames separated by Q frames. In particular, the interlace q may include sub-frames q, q + Q, q + 2Q, etc., where q ∈ {0, ..., Q-1}.

The wireless network can support Hybrid Automatic Repeat Request (HARQ) for data transmission on the downlink and uplink. For HARQ, a transmitter (eg, BS) may send one or more transmissions of a packet until the receiver (eg, UE) correctly decodes the packet or encounters some other termination condition. For synchronous HARQ, all transmissions of a packet can be sent in a single interleaved subframe. For asynchronous HARQ, each transmission of a packet can be sent in any subframe.

The UE may be located within the coverage area of multiple BSs. One of the 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, path loss, and the like. The received signal quality can be quantified by the signal-to-noise-and-interference ratio (SINR) or RSRQ or some other metric. The UE may operate in situations where there is significant interference, where the UE may observe high interference from one or more interfering BSs.

The wireless communication network can support 180 kHz deployment for narrowband operation (eg, NB-IoT) in different deployment modes. In one example, narrowband operation may be deployed in-band, for example, using RBs within a wider system bandwidth. In one case, narrowband operation may use one RB within the wider system bandwidth of an existing network (eg, an LTE network). In this case, the 180kHz bandwidth of the RB may have to be aligned with the wideband RB. In one example, narrowband operation may be deployed in unused RBs within a carrier guard band (eg, LTE). In this deployment, a 180kHz RB in the guard band can be aligned with a 15kHz tone grid of broadband LTE, for example, to use the same fast Fourier transform (FFT) and / or reduce in-band interference for traditional LTE communications. Exemplary Narrowband Communication

Traditional LTE designs (for example, for traditional "non-MTC" devices) focus on improvements in spectrum efficiency, universal coverage, and enhanced quality of service (QoS) support. Current LTE system downlink (DL) and uplink (UL) link budgets are designed to cover high-end devices, such as state-of-the-art smartphones and tablets, which can support relatively large DL and UL links budget.

However, as mentioned above, compared with other (broadband) devices in the wireless communication network, one or more UEs in the wireless communication network (for example, the wireless communication network 100) may be devices with limited communication resources, such as narrow-band UEs. . For narrowband UEs, various requirements can be relaxed, as only a limited amount of information may need to be exchanged. For example, you can reduce the maximum bandwidth (relative to a broadband UE), you can use a single receive radio frequency (RF) chain, you can reduce the peak rate (for example, the maximum transmission bit size is 100 bits), you can reduce the transmit power, you can use Rank 1 transmission, and can perform half-duplex operation.

In some cases, if a half-duplex operation is performed, the MTC UE may have a relaxed handover time from transmission to reception (or from reception to transmission). For example, the handover time can be relaxed from 20 μs for a general UE to 1 ms for an MTC UE. Release 12 MTC UEs can still monitor downlink (DL) control channels in the same way as general UEs, for example, monitoring wideband control channels (eg, PDCCH) in the first few symbols and occupying relatively narrow frequencies but spanning sub-frames Narrow channel control channel of length (for example, enhanced PDCCH or ePDCCH).

Certain standards (for example, LTE Release 13) may introduce support for various additional MTC enhancements, referred to herein as enhanced MTC (or eMTC). For example, eMTC can provide MTC UE with coverage enhancement up to 15dB.

As shown in the sub-frame structure 500 of FIG. 5, the eMTC UE can support narrow-band operation while operating in a wider system bandwidth (for example, 1.4 / 3/5/10/15 / 20MHz). In the example shown in FIG. 5, the general traditional control region 510 can span the system bandwidth of the first few symbols, and a narrow frequency region 530 (a narrow portion of the data region 520) that can retain the system bandwidth is used for the MTC entity. The downlink control channel (referred to herein as M-PDCCH) and the MTC entity downlink shared channel (referred to herein as M-PDSCH). In some cases, an MTC UE monitoring a narrow frequency region may operate at 1.4 MHz or 6 resource blocks (RB).

However, as mentioned before, the eMTC UE can operate in cells with a bandwidth greater than 6 RBs. Within this larger bandwidth, each eMTC UE can still operate (e.g., monitor / receive / transmit) while complying with the 6 physical resource block (PRB) constraints. In some cases, different eMTC UEs may be served by different narrow frequency regions (eg, each spanning a 6-PRB block). Because the system bandwidth can span from 1.4 to 20 MHz, or from 6 to 100 RBs, there can be multiple narrow-band regions within a larger bandwidth. The eMTC UE can also switch or hop between multiple narrow frequency regions to reduce interference. Exemplary Narrowband IoT Road

The Internet of Things (IoT) can refer to a network of physical objects, devices, or "things." IoT devices may be embedded with, for example, electronic devices, software or sensors, and may have a network connection, which enables such devices to collect and exchange data. IoT devices can be remotely sensed and controlled across existing network infrastructure, creating opportunities for more direct integration between the physical world and computer-based systems, thereby increasing efficiency, accuracy, and economic efficiency. A system including an IoT device enhanced with sensors and actuators may be referred to as a cyber-physical system. Information entity systems may include technologies such as smart networks, smart homes, smart transportation, and / or smart cities. Each "thing" (e.g., IoT device) can be uniquely identified via its embedded computing system and can operate interactively within existing infrastructure (e.g., Internet infrastructure).

NB-IoT can refer to narrow-band radio technology specifically designed for the IoT. NB-IoT can focus on indoor coverage, low cost, long battery life, and a large number of devices. To reduce the complexity of the UE, NB-IoT can allow narrowband deployment with one PRB (eg, 180kHz + 20kHz guard band). NB-IoT deployments can utilize higher-level components of certain systems (eg, 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 exemplary deployment 600 of NB-IoT according to some aspects of the content of this case. Three NB-IoT deployment configurations include in-band, guard band, and standalone. For in-band deployment configurations, NB-IoT can coexist with traditional systems (eg, GSM, WCDMA, and / or LTE systems) deployed in the same frequency band. For example, a broadband LTE channel can be deployed in various bandwidths between 1.4MHz and 20MHz. As shown in FIG. 6, the dedicated RB 602 in the bandwidth can be used by the NB-IoT and / or the RB 1204 can be dynamically allocated for the NB-IoT. As shown in FIG. 6, in an in-band deployment, one RB or 200 kHz of a broadband channel (for example, LTE) can be used for NB-IoT.

Some systems (eg, LTE) may include unused portions of the radio spectrum between carriers to prevent interference between adjacent carriers. In some deployments, NB-IoT may be deployed in a guard band 606 of a wideband channel.

In other deployments, NB-IoT can be deployed independently (not shown). For example, in a stand-alone deployment, a 200MHz carrier can be used to carry NB-IoT traffic, and the GSM spectrum can be reused.

The deployment of NB-IoT may include synchronization signals such as PSS for frequency and timing synchronization and SSS for carrying system information. For NB-IoT operation, compared to existing PSS / SSS frame boundaries in traditional systems (eg, LTE), PSS / SSS timing boundaries can be extended, for example, from 10 ms to 40 ms. Based on the timing boundary, the UE can receive the PBCH transmission, and the PBCH transmission can be transmitted in subframe 0 of the radio frame. Exemplary NR / 5G RAN architecture

New Radio (NR) may refer to a configuration based on a new air interface (eg, in addition to an air interface based on orthogonal frequency division multiplexing access (OFDMA)) or a fixed transport layer (eg, except for the Internet Protocol (IP) Beyond) operating radio technology. NR can utilize OFDM with CP on the uplink and downlink, and includes supporting half-duplex operation using TDD. NR may include enhanced mobile broadband (eMBB) services for wide bandwidths (eg, over 80MHz), millimeter waves (mmW) for high carrier frequencies (eg, 60GHz), and large-scale MTC that is not compatible with older MTC technologies (MMTC), and / or mission-critical for ultra-reliable low-latency communications (URLLC) services.

Can support 100MHz single component carrier (CC) bandwidth. The NR RB can span 12 subcarriers with a subcarrier bandwidth of 75 kHz and has a duration of 0.1 ms. Each radio frame can be composed of 50 sub-frames with a length of 10ms. Therefore, each subframe can have a length of 0.2 ms. Each subframe can indicate a link direction (eg, DL or UL) for data transmission, and the link direction of each subframe can be dynamically switched. Each sub-frame may include DL / UL data and DL / UL control data. The UL and DL sub-frames for NR are described in more detail below in relation to FIGS. 9 and 10.

Beamforming can be supported and beam directions can be dynamically configured. It can also support MIMO transmission with precoding. The MIMO configuration in DL can support up to 8 transmit antennas, and multi-layer DL transmission with up to 8 streams, and up to 2 streams per UE. Can support multi-layer transmission with up to 2 streams per UE. Aggregation of multiple cells can be supported with up to 8 serving cells. Alternatively, the NR can support different air interfaces other than the OFDM-based interface. An NR network may include entities such as a central unit (CU) or a decentralized unit (DU).

NR RAN may include CU and DU. The NR BS (for example, NB, eNB, gNB, 5G NB, TRP, AP, etc.) may correspond to one or more BSs. NR cells can be configured as accessor cells (ACell) or data cells only (DCell). For example, a RAN (eg, CU or DU) can configure a cell. DCells can be cells used for carrier aggregation or dual connectivity, but not for initial access, cell selection / reselection, or handover. In some cases, the DCell may not transmit a synchronization signal-in some cases, the DCell may transmit a synchronization signal.

7 illustrates an example logical architecture 700 of a decentralized RAN according to various aspects of the content of this case. A 5G access node 706 may include an access node controller (ANC) 702. ANC 702 may be a CU of a decentralized RAN. The reload interface to the Next Generation Core Network (NG-CN) 704 may terminate at ANC 702. The loadback interface to the adjacent next-generation access node (NG-AN) 710 may terminate at ANC 702. ANC 702 may include one or more TRPs 708. As mentioned above, TRP can be used interchangeably with "Cell", BS, NR BS, NB, eNB, 5G NB, gNB, AP, etc.

The TRP 708 may include a DU. The TRP 708 can be connected to one ANC (such as ANC 702) or more than one ANC (not shown). For example, for RAN sharing, Radio as a Service (RaaS), and service-specific AND deployments, the TRP 708 can connect to more than one ANC. The TRP 708 may include one or more antenna ports. The TRP 708 may be configured to provide traffic to the UE individually (eg, dynamically selected) or jointly (eg, joint transmission).

The logical architecture 700 may be used to illustrate a fronthaul definition. The architecture can be defined as a fronthaul solution that supports different deployment types. For example, the logic architecture 700 may be based on transmitting network capabilities (eg, bandwidth, latency, and / or signal interference). The logical architecture 700 may share features and / or components with LTE. According to various aspects, NG-AN 710 can support dual connection with NR. NG-AN 710 can share the shared fronthaul of LTE and NR. The logical architecture 700 may enable coordination between TRPs 708. For example, coordination may be preset within the TRP and / or preset across the TRP via ANC 702. In some cases, an inter-TRP interface may not be needed / present.

There may be a dynamic configuration of split logic functions within the logic architecture 700. Packet Data Convergence Protocol (PDCP), Radio Link Control (RLC), and Media Access Control (MAC) protocols may be suitably placed at ANC 702 or TRP 708.

FIG. 8 illustrates an exemplary physical architecture 800 of a decentralized RAN according to various aspects of the present disclosure. A centralized core network unit (C-CU) 802 can accommodate core network functions. C-CU 802 can be deployed centrally. C-CU 802 functions can be offloaded (for example, to Advanced Wireless Services (AWS)) in an effort to handle peak capacity.

A centralized RAN unit (C-RU) 804 can accommodate one or more ANC functions. Optionally, the C-RU 804 can accommodate core network functions at the local end. C-RU 804 may have a decentralized deployment. The C-RU 804 can be closer to the edge of the network.

The DU 806 can accommodate one or more TRPs. The DU 806 can be located at the edge of the network and has radio frequency (RF) capabilities.

FIG. 9 is a diagram illustrating an example of the sub-frame 900 centered on the DL. The DL-centric sub-frame 900 may include a control portion 902. The control part 902 may exist in the initial or start part of the sub-frame 900 centered on the DL. The control part 902 may include various schedule information and / or control information corresponding to each part of the sub-frame 900 centered on the DL. In some configurations, the control section 902 may be a physical DL control channel (PDCCH), as shown in FIG. 9. The DL-centric sub-frame 900 may also include a DL data portion 904. The DL data portion 904 may sometimes be referred to as the payload of the DL-centric sub-frame 900. The DL data portion 904 may include communication resources for transmitting DL data from a scheduling entity (eg, UE or BS) to a subordinate entity (eg, UE). In some configurations, the DL data portion 904 may be a physical DL shared channel (PDSCH).

The DL-centric sub-frame 900 may also include a common UL portion 906. The shared UL portion 906 may sometimes be referred to as a UL short pulse, a shared UL short pulse, and / or various other suitable terms. The common UL portion 906 may include feedback information corresponding to various other portions of the DL-centric sub-frame 900. For example, the common UL section 906 may include feedback information corresponding to the control section 902. Non-limiting examples of feedback information may include acknowledgement (ACK) signals, negative acknowledgement (NACK) signals, HARQ indicators, and / or various other suitable types of information. The shared UL portion 906 may include additional or alternative information, such as information related to the random access channel (RACH) procedure, scheduling request (SR), and various other suitable types of information. As shown in FIG. 9, the end of the DL data portion 904 may be separated in time from the start of the common UL portion 906. This time interval may sometimes be referred to as a gap, a guard period, a guard interval, and / or various other suitable terms. This interval provides time for switching from DL communication (for example, a receiving operation by a subordinate entity) to UL communication (for example, a transmission by a subordinate entity). Those of ordinary skill in the art will understand that the above is just an example of a DL-centric sub-frame, and there may be alternative structures with similar characteristics without necessarily deviating from the aspect described herein.

FIG. 10 is a diagram illustrating an example of a UL sub-frame 1000. The UL-centric sub-frame 1000 may include a control portion 1002. The control part 1002 may exist in the initial or start part of the UL sub-frame 1000. The control section 1002 in FIG. 10 may be similar to the control section 902 described above with reference to FIG. 9. The UL-centric sub-frame 1000 may also include a UL data portion 1004. The UL data portion 1004 may sometimes be referred to as the payload of the UL-centric sub-frame 1000. The UL data part may refer to a communication resource for transmitting UL data from a subordinate entity (for example, UE) to a scheduling entity (for example, UE or BS). In some configurations, the control section 1002 may be a PDCCH. In some configurations, the data portion may be a physical uplink shared channel (PUSCH).

As shown in FIG. 10, the end of the control section 1002 may be separated in time from the start of the UL data section 1004. This time interval may sometimes be referred to as a gap, a guard period, a guard interval, and / or various other suitable terms. This interval provides time for switching from DL communication (for example, a receiving operation by a scheduling entity) to UL communication (for example, a transmission by a scheduling entity). The UL-centric sub-frame 1000 may also include a common UL portion 1006. The common UL portion 1006 in FIG. 10 may be similar to the common UL portion 906 described above with reference to FIG. 9. The shared UL portion 1006 may additionally or alternatively include information related to CQI, sounding reference signals (SRS), and various other suitable types of information. Those of ordinary skill in the art will understand that the above is just an example of a UL-centric sub-frame, and there may be alternative structures with similar characteristics without necessarily deviating from the aspect described herein.

In some cases, two or more subordinate entities (eg, UEs) may use side link signals to communicate with each other. Practical applications of such side-link communications can include public safety, proximity services, UE-to-network relays, vehicle-to-vehicle (V2V) communications, Internet of Everything (IoE) communications, IoT communications, mission-critical grids, and / or various Other suitable applications. In general, a side link signal may refer to a subordinate entity without relaying the communication via a scheduling entity (eg, UE or BS) (even if the scheduling entity can be used for scheduling and / or control purposes). (For example, UE1) a signal transmitted to another subordinate entity (for example, UE2). In some examples, a licensed spectrum may be used to transmit side-link signals (as opposed to a wireless local area network, which typically uses unlicensed spectrum).

The UE can operate in various radio resource configurations, including configurations associated with transmitting pilot frequencies using a dedicated resource set (eg, RRC dedicated status, etc.) or associated with transmitting pilot frequencies using a shared resource set (eg, RRC shared status, etc.) Configuration. When operating in the RRC dedicated state, the UE may select a dedicated resource set for transmitting pilot frequency signals to the network. When operating in the RRC shared state, the UE may select a shared resource set for transmitting pilot frequency signals to the network. In either case, the pilot signal transmitted by the UE may be received by one or more network access devices (such as AN or DU) or portions thereof. Each receiving network access device may be configured to receive and measure a pilot frequency signal transmitted on a shared resource set, and also receive and measure a signal allocated to a UE (for the UE, the network access device is the A pilot frequency signal transmitted on a dedicated resource set of the UE's network access equipment monitoring group). The CU receiving one or more measurements of the network access device or receiving pilot frequency signals to the network access device may use the measurements to identify serving cells for the UE or initiate Serving Cell Changes. Exemplary uplink and downlink grants for narrowband

As mentioned above, some systems (eg, eMTC systems of version 13 or higher) may support narrowband operation. For example, narrowband operation may include support for communication on the 6RB band and half-duplex operation for up to, for example, 15dB coverage enhancement (eg, the ability to perform transmission and reception but not both). These systems may reserve a part of the system bandwidth for control, which may be the MTC entity downlink control channel (MPDCCH). The MPDCCH can be transmitted in a narrow frequency, at least one sub-frame can be used, and the control channel can be decoded depending on demodulation reference signal (DMRS) demodulation. Coverage can be increased by performing signal repetition / accompanying.

Certain systems (for example, NB-IoT systems with version 13 or higher) can support narrowband IoT operations (NB-IOT). NB-IoT can use 180 kHz bandwidth. NB-IoT can provide independent, in-band or guard band deployment solutions. Standalone deployments can use new bandwidths, while guardband deployments can be done with bandwidths that are usually reserved in the guardbands of existing networks, such as Long Term Evolution (LTE). In another aspect, the in-band deployment can use the same resource block in the LTE carrier of the existing LTE network. NB-IoT may provide increased coverage. NB-IoT can define a new narrowband control channel (eg, narrowband PDCCH (NPDCCH)), data and reference signals suitable for 1RB. For clarity, some aspects of these technologies are described below for NB-IoT, and NB-IoT terminology is used in most of the description below.

Currently, in some systems such as NB-IoT, only half-duplex (HD) FDD (Frequency Division Duplex) operation is supported. The UE cannot monitor UL and DL simultaneously and does not need to support parallel UL and DL transmissions. A rule that defines timing constraints such that the gap between the NPDCCH for UL grant and the associated NPUSCH (narrowband PUSCH) transmission is at least 8ms (for example, the exact delay is determined by the field in the UL grant) and is used for DL The gap between the authorized NPDCCH and the associated NPDSCH (narrowband PDSCH) is at least 5ms (for example, the exact delay is determined by the field in the DL grant). NPUSCH and NPDSCH are examples of shared channels or data channels. According to the context, "channel" may refer to a channel that transmits or receives signal transmission / data / information, or refers to a signal transmission / data / information transmitted or received on the channel. In Rel-13, only a single HARQ process is supported in NB-IoT. After receiving one NPDCCH for DL grant or UL grant, the UE stops monitoring the NPDCCH until the data transmission is completed. In Rel-14, for NB-IoT, there may be two back-to-back DL grants or two back-to-back UL grants for two HARQ processes. For example, after receiving one DL or UL grant, the UE may be required to continue Monitor any NPDCCH search space containing candidates and end at least 2 ms ( x ₁ ≧ 2 ms) before the first NPDSCH or NPUSCH starts.

FIG. 11 illustrates an example of a version 13 HARQ process timing and an example of a version 14 HARQ process timing. As shown for Release 13, the time gap between the NPDCCH for DL grant and the associated NPDSCH is 5 ms or longer. After receiving the NPDCCH, the UE stops monitoring the NPDCCH, and after 5 ms or more, the UE starts receiving downlink transmissions on the NPDSCH (for example, data transmission, such as repeated data transmission to improve coverage). After receiving the data transmission, the UE transmits ACK information after 12ms or more. For the uplink instance, the UE receives the NPDCCH for UL grant, stops monitoring the NPDCCH, and transmits on the uplink (eg, data transmission) on the associated NPUSCH after 8 ms or more. As shown for Release 14, the UE needs to continue to monitor the second NPDCCH (NPDCCH2) after receiving the first NPDCCH (NPDCCH1). The UE monitors the second NPDCCH until 2ms or more before the start of NPDSCH (NPDSCH1) transmission associated with the first NPDCCH. As shown for Release 14, the two back-to-back NPDCCHs can be used for both DL grant and UL grant. That is, the UE receives two consecutive UL grants or two consecutive DL grants. Receiving consecutive UL grants includes receiving one UL grant as the next grant after one UL grant, and receiving consecutive DL grants includes receiving one DL grant as the next grant after one DL grant.

Unlike HD-FDD, for TDD, the DL and UL subframes can be interleaved during NPUSCH / NPDSCH transmission. To support NB-IoT TDD DL and UL transmissions, the UE may receive some DL sub-frames for DL packets (eg, associated with NPDCCH for DL grant), followed by UL transmissions for UL packets (eg, Associated with NPDCCH for UL grant) followed by repetitions of the same DL packet, followed by some repetitions of the same UL packet, and so on.

According to the Rel-14 specification, for NB-IoT, the UE can receive only two back-to-back DL grants or two back-to-back UL grants, and does not support UE receiving interleaved UL and DL grants. For Rel-15, we can discuss the extension of NB-IoT to TDD mode. For TDD, parallel uplink and downlink transmission means, for example, that the UE receives a DL transmission of a DL packet, followed by a UL transmission of a UL packet, followed by a repeat of the same DL packet, followed by a repeat of the same UL packet. In order to support such interleaved DL / UL transmission, DL / UL authorization also needs to be interleaved, and the current standard specification does not support this feature. Receiving interleaved UL and DL grants includes receiving a DL grant as the next grant after a UL grant, or receiving a UL grant as the next grant after a DL grant. Interlaced UL and DL grants are required to support interlaced UL and DL transmissions, especially for TDD. Interleaving UL and DL authorization may also be beneficial for FDD, for example, to improve UL / DL transmission efficiency (for example, for some current TDM-based applications, for UL data transmission, DL data transmission may need to be completed first).

It can support interleaved UL and DL grants, so that the UE can receive two grants before the corresponding NPUSCH or NPDSCH transmission starts, one for UL and one for DL. The timing restriction rules between NPDCCH and NPDSCH / NPUSCH can remain unchanged. For example, the gap between the second NPDCCH and the start of NPDSCH or NPUSCH may be ≧ 2 ms. In addition, for HD-FDD, the UE is not required to monitor the NPDCCH (eg, for the third grant) from the start of NPDSCH to HARQ-ACK. This simplifies the implementation of the UE and saves UE power, because otherwise the UE needs to receive DL control information in addition to receiving data. In one aspect, there is no restriction on the order of the interleaved UL and DL grants. For example, the first grant may be a UL or DL grant.

FIG. 12 illustrates an exemplary interleaved grant (UL followed by DL) according to some aspects of the content of the present case. In one example, the first grant is a UL grant and the second grant is a DL grant. The time delay from grant to associated data transmission can be the same as described above (for example, 8ms or more between UL grant and associated NPUSCH transmission, 5ms between DL grant and associated NPDSCH transmission Or more). In this example, UL data transmission (for example, on NPUSCH) occurs between DL data transmission (for example, on NPDSCH) and HARQ-ACK associated with DL data transmission. In the second example, the order of data transmission is different. Here, UL data transmission (for example, on NPUSCH) occurs before DL data transmission (for example, on NPDSCH). In a third example, UL data transmission (for example, on NPUSCH) occurs after HARQ-ACK associated with DL data transmission (for example, on NPDSCH). Therefore, the order of data transmission is determined by, for example, the delay between the NPDCCH and the associated data transmission (for example, determined by a field in the NPDCCH).

FIG. 13 illustrates an exemplary interlaced grant (DL after UL) according to some aspects of the content of this case. FIG. 13 illustrates a concept similar to that of FIG. 12.

For NB-IoT in TDD mode, NPUSCH and NPDCCH interleaving can be supported. For example, the UE can continue to monitor the NPDCCH search space while performing NPUSCH transmission. Due to the TDD UL-DL configuration, there may be some DL sub-frames (SF) between UL transmissions, and the UE may switch from UL transmission (eg, NPUSCH transmission) to monitor NPDCCH search space during DL SF. In one aspect, if the subframe is indicated as DL according to the TDD UL-DL configuration, the UE is required to continue to monitor the search space unless the DL subframe is used for NPDSCH. In the case of interleaved DL and UL data transmission, if a protection subframe is needed to switch from UL to DL or from DL to UL, the DL or UL communication associated with the protection subframe can be transmitted The schedule is for communications that occur during this protection sub-frame) to be postponed to the next available SF. In the case of interleaved DL and UL data transmission, if several OFDM symbols are needed to switch from UL to DL or from DL to UL, for example, the associated DL or UL communication may be punctured in the subframe. For example, when switching from UL to DL, the first two symbols in the second sub-frame (DL) can be punctured, and when switching from DL to UL, the first sub-frame (DL) can be punctured. The last symbol in the frame and the first symbol in the second sub-frame (UL) are punctured.

FIG. 14 illustrates an exemplary interleaved NPDCCH and NPUSCH according to some aspects of the present content. In this example, TDD UL-DL configuration 1 is illustrated. First, the UE receives an NPDCCH (NPDCCH1) for UL grant. Based on the UL grant, a set of repetitions of uplink data transmissions (eg, for enhanced coverage) can be sent on the NPUSCH. As shown, the number of repetitions is 8 (for example, 8 subframes). Due to the TDD frame structure, there may be some DL sub-frames between the repetitions of uplink data on the NPUSCH. Generally, the UE does not utilize these DL sub-frames between NPUSCH transmissions because it is not efficient. In one aspect of the content of this case, the DL SFs can be used to monitor the NPDCCH. In this example, the protection subframe is used to switch from UL to DL, so that the first DL subframe can be used as a protection subframe (indicated by "G" in FIG. 14), and the second, adjacent DL The subframe can be used for NPDCCH (eg, NPDCCH2). If several OFDM symbols are used to switch from UL to DL, there is no need to protect the subframe, and the second NPDCCH (NPDCCH2) can be transmitted in the DL subframe immediately after the UL subframe.

With or without the support of two HARQ processes, interlaced UL / DL authorization can be supported. If two HARQ processes are used to support interleaved UL and DL grants, up to 4 NPDCCHs can be received, for example, two for DL grants and two for UL grants. In the case of back-to-back DL grant or UL grant, both grants may have the same or different HARQ IDs. The same HARQ ID may indicate repeated transmission (eg, retransmission of the first NPDCCH). For different HARQ IDs, two HARQ IDs can appear in any order, or the first authorization can always have HARQ ID 0 and the second authorization can have HARQ ID 1 (eg, a fixed order). If the UE detects two grants with the same HARQ ID (for example, two NPDCCHs associated with the same data), the UE can discard one of them; for example, A) discard the one with the lowest energy; B) always discard The first or the second; or C) a combination of the two, for example, if both energies are above a certain threshold, the first is always discarded. In another aspect, the UE respects the two grants and treats them as HARQ retransmissions. UE's support for interleaved UL and DL grants can be independent or independent of its support for two HARQ processes (for example, the UE can support interleaved UL and DL grants, or two HARQ processes, or both). Support for interleaved UL and DL grants may be indicated by the UE in a way that is independent of support for two HARQ processes. For example, the UE may use capability signaling to indicate support for interleaved UL and DL grants and independently indicate support for two HARQ procedures when it is attached to the network (eg, using different capability signaling).

As one aspect of the content of this case, the exemplary isochrones of two HARQ processes are illustrated below.

Isochronous 1: NPDCCH1 NPDCCH2 NPDSCHA ACKA NPDSCHB ACKB

Isochronous 2: NPDCCH1 NPDCCH2 NPDSCHA NPDSCHB ACKA ACKB

In one aspect, only one of the isochronous lines is allowed (eg, fixed timing). In another aspect, two isochrones are allowed. For the mapping of NPDCCH to NPDSCH, in one aspect, NPDSCH A may always be mapped to NPDCCH 1 and NPDSCH B may always be mapped to NPDCCH 2 and other mappings may be considered as error conditions and the UE may discard one of the grants. In another aspect, two mappings are allowed (eg, NPDSCHA to NPDCCH1 or NPDCCH 2).

Thus, techniques for uplink and downlink grants in narrow-band operation are desired. Therefore, the techniques provided herein can be used for uplink and downlink grants in narrow-band operation (eg, NB-IoT).

FIG. 15 is a flowchart illustrating an exemplary operation 1500 for receiving interlaced UL and DL grants according to aspects described herein. Operations 1500 may be performed, for example, by a UE (eg, UE 120), which may be a low cost IoT device, such as a NB-IoT device. Operation 1500 may begin at 1502, at 1502, monitoring a control channel in a narrow band of system bandwidth for uplink (UL) or downlink (DL) grants. At 1504, the UE receives interlaced UL and DL grants. At 1506, the UE sends or receives information in response to the received interleaved UL and DL grants. In one aspect, the UE may monitor the control channel search space and receive the DL grant as the next grant after the UL grant and after starting to send information on the uplink data channel in response to the UL grant. In one aspect, the uplink data channel may be on a different carrier than the control channel search space. In one aspect, the uplink data channel may be an uplink shared channel. For example, the uplink shared channel may be a narrow-band entity uplink shared channel (NPUSCH).

FIG. 16 is a flowchart illustrating exemplary operations 1600 of UE behavior when receiving back-to-back UL grants or DL grants with the same HARQ ID according to various aspects described herein. Operations 1600 may be performed, for example, by a UE (eg, UE 120), which may be a low cost IoT device, such as a NB-IoT device. Operation 1600 may begin at 1602, at 1602, monitoring a control channel in a narrow band of system bandwidth for uplink (UL) or downlink (DL) grants. At 1604, the UE receives two consecutive UL or DL grants, where the consecutive UL or DL grants have the same HARQ process identification (ID). At 1606, the UE selects one authorization to be used in the authorization based at least in part on at least one of: an authorization that meets an energy metric threshold; an authorization that is received first; or a second received authorization. At 1608, the UE may instead choose to use two grants, where the grant is treated as a hybrid HARQ retransmission. Exemplary UL and / or DL conflict handling

In the case where two HARQ processes are configured, it is possible that the eNB can schedule the UE so that there is a conflict across channels, for example, via incorrect scheduling. For example, conflicts can occur when two or more sets of information are transmitted or received on the same resource (eg, a sub-frame) simultaneously. For example, the UE may have two back-to-back NPDSCHs, the ACKs of the two NPDSCHs conflict, or the second NPDSCH and the ACK of the first NPDSCH may conflict. For back-to-back NPUSCH, there may be similar types of collisions. If interleaved UL and DL grants are implemented, there may also be conflicts between NPUSCH and NPDSCH, and conflicts between NPUSCH and ACK. Exemplary UE behavior in the case of such a conflict is illustrated herein and may be applicable to TDD and / or FDD. Conflict handling for back-to-back DL or UL authorization

FIG. 17 is a flowchart illustrating an exemplary operation 1700 of UE behavior related to collisions when receiving back-to-back UL grant or DL grant according to aspects described herein. Operations 1700 may be performed, for example, by a UE (eg, UE 120), which may be a low-cost IoT device, such as a NB-IoT device. Operation 1700 may begin at 1702, at 1702, monitoring a control channel in a narrow band of system bandwidth for uplink (UL) or downlink (DL) grants. At 1704, the UE receives two consecutive UL or DL grants. At 1706, the UE sends or receives information in response to the two consecutive UL and DL grants received. At 1708, in response to sending or receiving information, the UE recognizes a conflict that includes at least one of the following: a conflict between the first DL data channel and a second DL data channel, and a second DL data channel with the first DL data channel. Conflict between the first HARQ-ACK signal transmission of the data channel, the first HARQ-ACK signal transmission for the first DL data channel and the second HARQ-ACK signal transmission for the second DL data channel Between the first UL data channel and the second UL data channel.

In the case where NPDSCH and NPDSCH conflict, in one aspect, even if there is a conflict, two NPDSCH can be regarded as valid NPDSCH, and 1) non-conflicting sub-frames in two NPDSCH can be used to decode (for example, , The UE decodes both) or uses 2) the conflicting SF for only one of the NPDSCHs to decode (eg, the UE decodes only one, the first, the second, or based on the associated control channel energy metric ). In another aspect, only one of the NPDSCHs may be monitored-for example, the first NPDSCH or the second NPDSCH, or based on a corresponding NPDCCH energy metric (eg, associated control channel energy detection). The first NPDSCH may refer to the NPDSCH that starts first or its NPDCCH first, and the second NPDSCH may refer to the NPDSCH that starts second or its NPDCCH starts second.

In the case where the NPDSCH conflicts with the ACK (for example, the ACK for the first NPDSCH conflicts with the second NPDSCH), in one aspect, it is regarded as incorrect authorization and one of the NPDSCH and the corresponding ACK is discarded (Similar to the conflict between NPDSCH and NPDSCH). In another aspect, the ACK can be dropped. (All or partly, for example, on a conflict sub-frame). In another aspect, the NPDSCH may be dropped (in whole or in part, for example, on a collision sub-frame). The conflicting SF may include an SF including ACK / NPDSCH, a protection SF for switching from UL to DL, and the like.

In the case of ACK and ACK conflict, in one aspect, it is regarded as incorrect authorization and one of NPDSCH (similar to NPDSCH-to-NPDSCH collision) or ACK is discarded. In another aspect, only the first or second ACK is sent. In another aspect, the first ACK is sent completely and the second ACK is punctured, or vice versa. If only one NPDSCH is successfully decoded, an ACK corresponding to the NPDSCH can be sent, and for a failed NPDSCH, the ACK transmission corresponding to the failed NPDSCH can be punctured.

In the case where the NPUSCH conflicts with the NPUSCH, in one aspect, one of the NPUSCH may be discarded. In another aspect, one of the NPUSCHs can be punctured and the other NPUSCH can be completely transmitted. For example, the NPUSCH that is dropped or punctured may always be the first, always the second, or based on the NPDCCH energy metric. Interleaved UL and DL grant conflict handling

In the case where the NPUSCH conflicts with the NPDSCH, in one aspect, it is regarded as an incorrect authorization and the NPUSCH or NPDSCH is discarded (for example, the first or second one, or based on the NPDCCH energy metric, etc.). In another aspect, it is considered a valid authorization, but by prioritizing one channel over another channel, only one of them is retained in the conflicting SF. For example, one of NPUSCH or NPDSCH may be dropped or punctured. For example, the dropped or punctured channel may be always the first, always the second, or based on the NPDCCH energy metric.

In the case where NPUSCH conflicts with HARQ-ACK, in one aspect, by prioritizing one channel over another channel (for example, HARQ-ACK takes priority over NPUSCH), only one of them is reserved in the conflicting SF. In another aspect, HARQ-ACK may be multiplexed on the NPUSCH (eg, HARQ-ACK is used to modulate the DMRS of the NPUSCH in the conflicting SF).

As used herein, the term "identify" includes a variety of operations. For example, "identification" can include calculations, calculations, processing, exporting, investigating, viewing (such as viewing in a table, database, or other data structure), ascertainment, and so on. In addition, "identification" may include receiving (eg, receiving information), accessing (eg, accessing data in memory), and the like. In addition, "identification" may include solving, selecting, selecting, creating, etc.

Furthermore, the term "or" is intended to mean an inclusive "or" rather than an exclusive "or". That is, unless otherwise specified or clearly indicated by context, for example, the term "X uses A or B" is intended to mean any natural inclusive arrangement. That is, for example, the term "X uses A or B" is satisfied by any of the following: X uses A; X uses B; or X uses both A and B. As used herein, a reference to an element in the singular does not mean "one and only one", unless specifically stated otherwise, but rather "one or more." For example, the articles "a" and "an" used in this application and the scope of the appended patents should generally be construed to mean "one or more" unless specified otherwise or clearly indicated by the context. Unless specifically stated otherwise, the term "some" refers to one or more. References to "at least one" in the list of items refer to any combination of those items, including individual members. By way of example, "at least one of a, b, or c" is intended to cover: a, b, c, ab, ac, bc, and abc and any combination with multiple identical elements (eg, aa, aaa, aab, aac, abb, acc, bb, bbb, bbb, cc, and ccc, or any other ordering of a, b, and c). As used herein, including in the scope of patent applications, the term "and / or" when used in a list of two or more items indicates that any of the listed items may be used alone or may use the Any combination of two or more. For example, if a composition is described as containing components A, B, and / or C, the composition may include A alone; B alone; C alone; A and B combined; A and C combined; B and C A combination; or a combination of A, B, and C.

In some cases, the device may have an interface for transmitting frames for transmission or reception, rather than actually transmitting frames. For example, the processor can output the frame to the RF front-end for transmission via a bus interface. Similarly, the device may have an interface for obtaining a frame received from another device instead of actually receiving the frame. For example, the processor may obtain (or receive) transmitted frames from the RF front-end via a bus interface.

The methods disclosed herein include one or more steps or operations for implementing the method. The method steps and / or operations may be interchanged with one another without departing from the scope of the claim. That is, unless a specific order of steps or operations is specified, the order and / or use of specific steps and / or operations may be modified without departing from the scope of the claim.

The various operations of the above methods may be performed by any suitable means capable of performing the corresponding functions. The component may include various hardware and / or software components and / or modules, including but not limited to circuits, application-specific integrated circuits (ASICs) or processors. In general, in the case of the operations illustrated in the figures, such operations may be performed by any suitable corresponding means function.

For example, components for monitoring, components for identification, components for selection, components for decision-making, components for execution, components for transmission, components for receiving, components for sending, The means for signalling the notification, the means for requesting and / or the means for exporting may include one or more processors, launchers of the user equipment 120 and / or the base station 110 shown in FIG. 2 Receiver, receiver, antenna, and / or other components.

Those skilled in the art will understand that information and signals may be represented using any of a variety of different technologies and techniques. For example, the materials, instructions, commands, information, signals, bits, symbols, and chips mentioned in the above description can be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or optical particles, or a combination thereof. .

Those skilled in the art will further understand that the various exemplary logical blocks, modules, circuits, and algorithm steps described in connection with the disclosure herein may be implemented as hardware, software, or a combination thereof. In order to clearly indicate this interchangeability between hardware and software, various exemplary components, blocks, modules, circuits, and steps have been described above in their functional aspects. Whether such functions are implemented as hardware or software depends on the specific application and design constraints imposed on the entire system. Those skilled in the art can implement the described functions in a flexible manner for each specific application, but this kind of decision in parity should not be interpreted as a departure from the scope of this case.

The various exemplary logic blocks, modules, and circuits described in conjunction with the disclosure herein can be used with general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), Programmable gate arrays (FPGAs) or other programmable logic devices, individual gate or transistor logic, individual hardware components, or any combination thereof to implement or execute. One or more of the aforementioned devices or processors may execute software. Software should be broadly interpreted to mean instructions, instruction sets, codes, code snippets, code, programs, subprograms, software modules, applications, software applications, packaged software, routines, subroutines, objects, Executable programs, running threads, procedures, functions, etc., whether they are called software, firmware, middleware, microcode, hardware description language, or whatever. A general-purpose processor may be a microprocessor, but in the alternative, the processor may be any general processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, such as 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.

The steps of a method or algorithm described in conjunction with the disclosure herein can be directly embodied as hardware, a software module executed by a processor, or a combination thereof. The software module can be located in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, phase change memory, scratchpad, hard disk, removable disk, CD-ROM or other fields Any other form of storage medium known. An exemplary storage medium is coupled to the processor such that the processor can read information from, and write information to, the storage medium. In the alternative, 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. In the alternative, the processor and the storage medium may reside as individual components in a user terminal.

In one or more exemplary designs, the functions described may be implemented in hardware, software, or a combination thereof. If implemented in software, these functions may be stored or transmitted as one or more instructions or code on a computer-readable medium. Computer-readable media includes computer storage media and communication media, including any media that facilitates transfer of computer programs from one place to another. Storage media can be any available media that can be accessed by a general purpose or special purpose computer. By way of example, and not limitation, such computer-readable media may include RAM, ROM, EEPROM, CD / DVD or other optical disk storage, magnetic disk storage, or other magnetic storage devices, or can be used for instructions or data structures. Any form of media that carries or stores the required code components and can be accessed by a general purpose or special purpose computer or general purpose or special purpose processor. Also, any connection is properly termed a computer-readable medium. For example, if coaxial, fiber optic, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave are used to deliver software from a website, server, or other remote source, coaxial, fiber optic, Twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of media. Disks and optical discs as used herein include compact discs (CDs), laser discs, optical discs, digital versatile discs (DVDs), floppy discs, and Blu-ray discs, where magnetic discs typically reproduce data magnetically, and optical discs use lasers The material is reproduced optically. The above combination is also included in the category of computer-readable media.

Previous descriptions of the content of this case are provided to enable those skilled in the art to implement or use the content of this case. Various modifications to the content of the present case will be apparent to those skilled in the art, and the general principles defined herein may be applied to other variations without departing from the scope of the content of the present case. Therefore, the content of this case is not intended to be limited to the examples and designs described herein, but should be given the broadest scope consistent with the principles and novel features disclosed herein.

100‧‧‧Wireless communication network

102a‧‧‧Macrocell

102b‧‧‧ picocell

102c‧‧‧ femtocell

110a‧‧‧BS / Macro BS

110b‧‧‧BS

110c‧‧‧BS

110d‧‧‧ relay station

110‧‧‧BS

120‧‧‧User Equipment (UE)

120a‧‧‧UE

120b‧‧‧UE

120c‧‧‧UE

120d‧‧‧UE

130‧‧‧Network Controller

212‧‧‧Source

220‧‧‧Processor

230‧‧‧Transmit (TX) Multiple Input Multiple Output (MIMO) Processor

232a‧‧‧Modulator (MOD)

232t‧‧‧Modulator (MOD)

234a‧‧‧antenna

234t‧‧‧antenna

236‧‧‧MIMO Detector

238‧‧‧Receiving processor

239‧‧‧Data slot

240‧‧‧Controller / Processor

242‧‧‧Memory

244‧‧‧Communication Unit

246‧‧‧Scheduler

252a‧‧‧antenna

252r‧‧‧antenna

254a‧‧‧ Demodulator (DEMOD)

254r‧‧‧ Demodulator (DEMOD)

256‧‧‧MIMO Detector

258‧‧‧Receiving Processor

260‧‧‧Data slot

262‧‧‧Source

264‧‧‧Processor

266‧‧‧TX MIMO Processor

280‧‧‧Controller / Processor

282‧‧‧Memory

290‧‧‧controller / processor

292‧‧‧Memory

294‧‧‧communication unit

300‧‧‧Frame structure

410‧‧‧Sub frame format

420‧‧‧Sub frame format

500‧‧‧ subframe structure

510‧‧‧ traditional control area

520‧‧‧Data area

530‧‧‧Narrowband area

600‧‧‧ deployment

602‧‧‧dedicated RB

606‧‧‧ guard band

700‧‧‧Logic Architecture

702‧‧‧Access Node Controller (ANC)

704‧‧‧Next Generation Core Network (NG-CN)

706‧‧‧5G access node

708‧‧‧TRP

710‧‧‧Neighbor Next Generation Access Node (NG-AN)

800‧‧‧ physical structure

802‧‧‧Centralized Core Network Unit (C-CU)

804‧‧‧Centralized RAN Unit (C-RU)

806‧‧‧DU

900‧‧‧ DL-centered sub frame

902‧‧‧Control section

904‧‧‧DL Information Section

906‧‧‧ shares UL part

1000‧‧‧ UL-centric sub frame

1002‧‧‧Control section

1004‧‧‧UL Information Section

1006‧‧‧ shares UL part

1500‧‧‧ operation

1502‧‧‧step

1504‧‧‧step

1506‧‧‧step

1600‧‧‧ Operation

1602‧‧‧step

1604‧‧‧step

1606‧‧‧step

1608‧‧‧step

1700‧‧‧operation

1702‧‧‧step

1704‧‧‧step

1706‧‧‧step

1708‧‧‧step

Therefore, for a way to understand the above features of the content of the present case in detail, a more specific description briefly summarized above can be obtained by referring to some of the aspects shown in the drawings. It should be noted, however, that the drawings only illustrate some typical aspects of the content of this case, and therefore should not be considered as a limitation on its scope, as the description may allow other equivalent aspects.

FIG. 1 is a block diagram conceptually illustrating an example of a wireless communication network according to some aspects of the present disclosure.

FIG. 2 illustrates a block diagram conceptually illustrating an example of a base station (BS) communicating with a user equipment (UE) in a wireless communication network according to some aspects of the content of the present case.

FIG. 3 is a block diagram conceptually illustrating an example of a frame structure in a wireless communication network according to some aspects of the present disclosure.

FIG. 4 is a block diagram conceptually illustrating two exemplary sub-frame formats with ordinary loop prefixes according to certain aspects of the present disclosure.

FIG. 5 illustrates an exemplary sub-frame configuration for enhanced / evolved machine type communication (eMTC) according to some aspects of the present disclosure.

FIG. 6 illustrates an exemplary deployment of a narrowband IoT circuit (NB-IoT) according to some aspects of the content of the present case.

FIG. 7 illustrates an exemplary logical architecture of a decentralized radio access network (RAN) according to some aspects of the present disclosure.

FIG. 8 illustrates an exemplary physical architecture of a decentralized RAN according to certain aspects of the present disclosure.

FIG. 9 is a diagram illustrating an example of a downlink (DL) -centric sub-frame according to some aspects of the present content.

FIG. 10 is a diagram illustrating an example of an uplink (UL) -centric sub-frame according to some aspects of the content of the present case.

FIG. 11 illustrates an example of a version 13 HARQ process timing and an example of a version 14 HARQ process timing according to some aspects of the content of the present case.

FIG. 12 illustrates an exemplary interleaved grant (UL followed by DL) according to some aspects of the content of the present case.

FIG. 13 illustrates an exemplary interlaced grant (DL after UL) according to some aspects of the content of this case.

FIG. 14 illustrates an exemplary interleaved NPDCCH and NPUSCH according to some aspects of the present content.

15 is a flowchart illustrating an exemplary operation for receiving interlaced uplink and downlink grants in a narrow frequency band of a system bandwidth according to some aspects of the present invention.

16 is a flowchart illustrating an exemplary operation of UE behavior when receiving back-to-back UL grant or DL grant with the same HARQ ID according to some aspects of the content of the present case.

17 is a flowchart illustrating an exemplary operation of a UE behavior related to a collision when receiving back-to-back UL grant or DL grant according to some aspects of the content of the present case.

For ease of understanding, the same element symbols are used to indicate the same elements that are common in the drawings when possible. It is anticipated that the elements disclosed in one aspect may be advantageously used in other aspects without special description.

Domestic hosting information (please note in order of hosting institution, date, and number) None

Information on foreign deposits (please note in order of deposit country, institution, date, and number) None

Claims (63)

A method for wireless communication by a user equipment (UE) includes the following steps: monitoring a narrowband of a system bandwidth for an uplink (UL) grant or a downlink (DL) grant A control channel; receiving interleaved UL and DL grants; and sending or receiving information in response to the received interleaved UL and DL grants. The method of claim 1, wherein receiving the interleaved UL and DL grants includes at least one of: receiving a DL grant as a next grant after a UL grant, or receiving a UL grant as a DL grant after Next authorization. The method of claim 1, wherein the interleaved UL and DL grants are received before the start of the sending or receiving information in response to the interleaved UL and DL grants. The method of claim 1, wherein the UE monitors a control channel search space, and receives a DL after the UL grant and in response to the start of the transmission of information on an uplink data channel authorized by the UL. Authorize as the next authorization. The method of claim 4, wherein the uplink data channel is on a carrier different from the control channel search space. The method according to claim 4, wherein a sub-frame after the UE sends information on the UL data channel and a sub-frame before a sub-frame for DL communication is used as a protection Sub frame. The method of claim 6, wherein a communication associated with the protection sub-frame is deferred to the next available sub-frame. The method of claim 1, wherein each of the interleaved UL and DL grants supports one or more Hybrid Automatic Repeat Request (HARQ) procedures. The method of claim 8, wherein each of the interleaved UL and DL grants supports two HARQ procedures. The method of claim 8, wherein the UE indicates support for at least one of the following via a capability signal transfer: two HARQ processes for each UL or DL grant, or interleaving of UL and DL grants. The method as described in claim 1, further comprising the steps of: transmitting or receiving information in response to the received interleaved UL and DL grants, identifying a conflict, the conflict including at least one of the following: UL data A conflict between the channel and the DL data channel, or a conflict between the UL data channel and a hybrid ARQ acknowledgement (HARQ-ACK) signal transmission. The method according to claim 11, wherein the HARQ-ACK signal transmission includes an acknowledgement or a negative acknowledgement (NACK), and wherein the HARQ-ACK signal transmission is directed to the DL data channel. The method according to claim 11, wherein the conflict includes the conflict between the UL data channel and the DL data channel, and the method also includes at least one of the following steps: Deciding to use the UL data channel and the DL data channel One, or for the sub-frames that conflict between the UL data channel and the DL data channel, it is decided to use the sub-frames of one of the UL data channel and the DL data channel. The method of claim 13, wherein the step of deciding to use is based at least in part on an energy metric threshold. The method according to claim 12, wherein the conflict includes the conflict between the UL data channel and the HARQ-ACK signal transmission, and the method also includes at least one of the following steps: For the UL data channel and the HARQ-ACK The sub-frames that conflict between signal transmissions decide to transmit the HARQ-ACK signal transmission, or to multiplex the HARQ-ACK signal transmission with the UL data channel. The method of claim 15, wherein the step of multiplexing the HARQ-ACK signal and the UL data channel includes the following steps: for a sub-signal that conflicts between the UL data channel and the HARQ-ACK signal transmission Block, using the HARQ-ACK signal to transmit a demodulation reference signal (DMRS) that modulates the UL data channel. The method of claim 1, wherein the UE is configured for a narrowband IoT (NB-IoT). The method of claim 1, wherein the UE is configured for time division duplex (TDD) operation. The method of claim 1, wherein the UE is configured for frequency division duplex (FDD) operation. The method according to claim 1, wherein the control channel includes a narrowband entity downlink control channel (NPDCCH). The method of claim 1, wherein the step of transmitting information comprises the following steps: transmitting information in an uplink data channel in response to the received UL grant; and wherein the receiving information includes responding to the DL grant Receive information in the downlink data channel. The method of claim 1, wherein the uplink data channel includes a narrowband entity uplink shared channel (NPUSCH), and wherein the downlink data channel includes a narrowband entity downlink shared channel (NPDSCH) ). The method according to claim 11, wherein the DL data channel includes a narrowband entity downlink shared channel (NPDSCH), the HARQ-ACK includes a hybrid automatic repeat request (HARQ) acknowledgement or negative acknowledgement, and the UL The data channel includes a narrow-band physical uplink shared channel (NPUSCH). A method for wireless communication by a user equipment (UE) includes the following steps: monitoring a narrowband of a system bandwidth for an uplink (UL) grant or a downlink (DL) grant A control channel; receiving two consecutive UL or DL grants, where the consecutive UL or DL grants have an identical HARQ process identification (ID); and selecting the grants based at least in part on at least one of the following One authorization to be used: an authorization that meets an energy metric threshold, the authorization received first, or the second authorization received, or the use of two authorizations, where these authorizations are considered as hybrid automatic repeat request (HARQ) retransmissions pass. The method of claim 24, wherein the step of receiving two consecutive UL or DL grants includes at least one of the following steps: receiving one UL grant as the next grant after one UL grant; or after one DL grant Receive a DL grant as the next grant. The method of claim 24, wherein the UE is configured for a narrowband IoT (NB-IoT). The method according to claim 24, wherein the control channel comprises a narrowband physical downlink control channel (NPDCCH). A method for wireless communication by a user equipment (UE) includes the following steps: Monitoring a system in a narrow band of a system bandwidth for an uplink (UL) or a downlink (DL) authorization A control channel; receiving two consecutive UL or DL grants; sending or receiving information in response to the two consecutive UL and DL grants received; and identifying a conflict, the conflict in response to the transmitted or received information Including at least one of the following: conflict between the first DL data channel and the second DL data channel, and the second DL data channel and the first HARQ-ACK signal for the first DL data channel are transmitted Conflict between the first HARQ-ACK signal transmission for the first DL data channel and the second HARQ-ACK signal transmission for the second DL data channel, or between the first UL data channel and the first Conflicts between two UL data channels. The method of claim 28, wherein the step of receiving two consecutive UL or DL grants includes at least one of the following steps: receiving a UL grant as a next grant after a UL grant; or after a DL grant A DL grant is received as the next grant. The method according to claim 28, wherein the conflict includes the conflict between the first DL data channel and the second DL data channel, and the method also includes at least one of the following steps: selecting only the first DL One of the data channel or the second DL data channel for monitoring; or for a sub-frame that conflicts between the first DL data channel and the second DL data channel, only the first DL data channel or the One of the second DL data channels is monitored. The method of claim 30, wherein the selecting step includes the following steps: selecting the first DL data channel signal transmission; selecting the second DL data channel signal transmission; or selecting the first DL data channel signal based at least in part on an energy metric threshold. Signal transmission of the first or second DL data channel. The method of claim 28, wherein the conflict includes the conflict between the second DL data channel and the first HARQ-ACK signal transmission for the first DL data channel, and the method also includes the following steps At least one step of: determining not to use the first HARQ-ACK signal transmission; or determining not to use the second DL data channel. The method of claim 32, wherein the step of deciding not to use the first HARQ-ACK signal transmission includes the following steps: deciding not to use all sub-frames for the first HARQ-ACK signal transmission or to use only A sub-frame for transmitting the first HARQ-ACK signal that conflicts with the second DL data channel. The method according to claim 32, wherein the step of deciding not to use the second DL data channel includes the following steps: deciding not to use all sub-frames for the second DL sharing or only to use with the A HARQ-ACK signal transmits conflicting sub-frames of the second DL data channel. The method of claim 28, wherein the conflicting sub-frame includes at least one of the following: a sub-frame for an ACK, a sub-frame for a DL data channel, or a protection sub-frame. The method of claim 28, wherein the conflict includes between the first HARQ-ACK signal transmission for the first DL data channel and the second HARQ-ACK signal transmission for the second DL data channel In the conflict, the method also includes at least one of the following steps: sending one of the first HARQ-ACK signal transmission or the second HARQ-ACK signal transmission, or sending the first HARQ-ACK signal transmission or One of the second HARQ-ACK signal transmission and the other of the first HARQ-ACK signal transmission or the second HARQ-ACK signal transmission are truncated. The method according to claim 36, wherein only one of the first DL data channel and the second DL data channel is successfully decoded, and the method also includes the following steps: for the first DL data channel and the second DL data channel The one successfully decoded in the DL data channel sends a HARQ-ACK; and the HARQ-ACK is deleted for the other of the first DL data channel signal transmission and the second DL data channel signal transmission. The method of claim 28, wherein the conflict includes the conflict between the first UL data channel and the second UL data channel, and the method also includes at least one of the following steps: Deciding to transmit the first UL One of the data channel and the second UL data channel, or decide to transmit one of the first UL data channel and the second UL data channel and delete the first UL data channel and the second UL data channel The other. The method of claim 38, wherein the step of deciding transmission or the step of puncturing is based at least in part on an energy metric threshold. The method of claim 28, wherein the DL data channel includes a narrowband entity downlink shared channel (NPDSCH), the HARQ-ACK includes a hybrid automatic repeat request (HARQ) acknowledgement or negative acknowledgement, and the UL The data channel includes a narrow-band physical uplink shared channel (NPUSCH). The method of claim 28, wherein the UE is configured for a narrowband IoT (NB-IoT). The method of claim 28, wherein the control channel includes a narrowband physical downlink control channel (NPDCCH), the first DL data channel and the second DL data channel include an NPDSCH, and the first UL data The channel and the second UL data channel include an NPUSCH. A method for wireless communication by a base station (BS) includes the following steps: transmitting a staggered uplink (UL) to a user equipment (UE) on a control channel in a narrow band of a system bandwidth And downlink (DL) grants; and receiving information from or sending information to the UE in response to these transmitted interleaved UL and DL grants. A method for wireless communication by a base station (BS) includes the following steps: transmitting two consecutive uplinks to a user equipment (UE) on a control channel in a narrow band of a system bandwidth ( UL) or downlink (DL) grants, these consecutive UL or DL grants have the same HARQ process identification (ID), where: the UE selects the grant among these grants based at least in part on at least one of the following: One authorization used: an authorization that meets an energy metric threshold, the first received authorization, or the second received authorization, or the UE selects two authorizations for use, where these authorizations are considered as hybrid automatic retransmission requests ( HARQ) retransmission. A method for wireless communication by a base station (BS) includes the following steps: transmitting two consecutive UL or DL grants to a user equipment (UE) on a control channel in a narrow band of a system bandwidth ; Sending or receiving information in response to the two consecutive UL and DL grants transmitted; and in response to the sending or receiving information, identifying a conflict including at least one of: a first DL data channel and a second DL A conflict between data channels, a conflict between the second DL data channel and a first HARQ-ACK (HARQ-ACK) signal transmission for the first DL data channel, a first for the first DL data channel A conflict between the HARQ-ACK signal transmission and a second HARQ-ACK signal transmission for the second DL data channel, or a conflict between the first UL data channel and the second UL data channel. A device for wireless communication by a user equipment (UE) includes: a device for monitoring a system bandwidth in a narrow band for an uplink (UL) grant or a downlink (DL) grant; Means for a control channel; means for receiving interleaved UL and DL grants; and means for sending or receiving information in response to the received interleaved UL and DL grants. An apparatus for wireless communication by a user equipment (UE) includes: a narrowband for monitoring a system bandwidth for an uplink (UL) grant or a downlink (DL) grant; A component of a control channel; a component for receiving two consecutive UL or DL authorizations, wherein the consecutive UL or DL authorizations have an identical HARQ process identification (ID); and a component for the following operations: at least Select one of these authorizations to use based in part on at least one of the following: an authorization that meets an energy metric threshold, the authorization received first, or the second authorization received, or the use of two authorizations, where Authorization is considered a Hybrid Automatic Repeat Request (HARQ) retransmission. An apparatus for wireless communication by a user equipment (UE) includes: a narrowband for monitoring a system bandwidth for an uplink (UL) grant or a downlink (DL) grant; A control channel component; a component for receiving two consecutive UL or DL grants; a component for sending or receiving information in response to the two consecutive UL and DL grants received; and a response for The sending or receiving information is used to identify a conflicting component. The conflict includes at least one of the following: a conflict between a first DL data channel and a second DL data channel, and the second DL data channel being used for the first DL Conflict between the first HARQ-ACK signal transmission of the data channel, the first HARQ-ACK signal transmission for the first DL data channel and the second HARQ-ACK for the second DL data channel A conflict between signal transmissions, or a conflict between a first UL data channel and a second UL data channel. A device for wireless communication by a base station (BS) includes: transmitting a staggered uplink (UL) to a user equipment (UE) on a control channel in a narrow frequency band of a system bandwidth; And means for receiving downlink and DL grants; and means for receiving information from or transmitting information to the UE in response to the transmitted interleaved UL and DL grants. A device for wireless communication by a base station (BS) includes: a control channel in a narrow frequency band of a system bandwidth for transmitting two consecutive uplinks to a user equipment (UE) ( A component of a UL) or downlink (DL) grant, the consecutive UL or DL grants have an identical HARQ process identification (ID), where: the UE selects the grants based at least in part on at least one of One authorization to be used: an authorization that meets an energy metric threshold, the authorization received first, or the second received authorization, or the UE selects two authorizations for use, where these authorizations are considered as hybrid automatic retransmission Request (HARQ) retransmission. A device for wireless communication by a base station (BS) includes: transmitting two consecutive UL or DL authorizations to a user equipment (UE) on a control channel in a narrow frequency band of a system bandwidth; Means for sending or receiving information in response to the two consecutive UL and DL grants transmitted; and means for identifying a conflict including at least one of the following in response to the sending or receiving information : Conflict between the first DL data channel and the second DL data channel, and the conflict between the second DL data channel and the first HARQ-ACK signal transmission for the first DL data channel is used for Conflict between the first HARQ-ACK signal transmission of the first DL data channel and the second HARQ-ACK signal transmission for the second DL data channel, or between the first UL data channel and the second UL data channel Conflict. An apparatus for wireless communication by a user equipment (UE) includes: one or more processors configured to: monitor for an uplink (UL) grant or a downlink (DL) grant A control channel in a narrow band of a system bandwidth; receiving interlaced UL and DL grants; and sending or receiving information in response to the received interlaced UL and DL grants; and a memory coupled to the One or more processors. An apparatus for wireless communication by a user equipment (UE) includes: one or more processors configured to: monitor for an uplink (UL) grant or a downlink (DL) grant A control channel in a narrow band of a system bandwidth; receiving two consecutive UL or DL grants, where the consecutive UL or DL grants have the same HARQ process identification (ID); and based at least in part on At least one of them selects one of the authorizations to be used: an authorization that meets an energy metric threshold, the authorization received first, or the second authorization received, or the use of two authorizations, where the authorizations are considered Hybrid Automatic Repeat Request (HARQ) retransmission; and a memory coupled to the one or more processors. An apparatus for wireless communication by a user equipment (UE) includes: one or more processors configured to: monitor for an uplink (UL) grant or a downlink (DL) grant A control channel in a narrow band of a system bandwidth; receiving two consecutive UL or DL grants; sending or receiving information in response to the two consecutive UL and DL grants received; and responding to the sending Or receiving information to identify a conflict, the conflict including at least one of the following: a conflict between a first DL data channel and a second DL data channel, the second DL data channel and a first DL data channel used for the first DL data channel A conflict between HARQ acknowledgement (HARQ-ACK) signal transfers, between a first HARQ-ACK signal transfer for the first DL data channel and a second HARQ-ACK signal transfer for the second DL data channel A conflict, or a conflict between a first UL data channel and a second UL data channel; and a memory coupled to the one or more processors. A device for wireless communication by a base station (BS) includes: one or more processors configured to: to a user equipment (UE) on a control channel in a narrow band of a system bandwidth Transmitting interlaced uplink (UL) and downlink (DL) grants; and receiving information from or sending information to the UE in response to the transmitted interlaced UL and DL grants; and a memory, Coupled to the one or more processors. A device for wireless communication by a base station (BS) includes: one or more processors configured to: to a user equipment (UE) on a control channel in a narrow band of a system bandwidth Transmitting two consecutive uplink (UL) or downlink (DL) grants, the consecutive UL or DL grants having an identical HARQ process identification (ID), wherein: the UE is based at least in part on the following at least One of them selects one of the authorizations to be used: an authorization that meets an energy metric threshold, the authorization received first, or the second authorization received, or two authorizations selected by the UE for use, among which Considered as a hybrid automatic repeat request (HARQ) retransmission; and a memory coupled to the one or more processors. A device for wireless communication by a base station (BS) includes: one or more processors configured to: to a user equipment (UE) on a control channel in a narrow band of a system bandwidth Transmitting two consecutive UL or DL grants; sending or receiving information in response to the two consecutive UL and DL grants transmitted; and in response to the sending or receiving information, identifying a conflict including at least one of the following: A conflict between a first DL data channel and a second DL data channel, and a conflict between the second DL data channel and a first HARQ acknowledgement (HARQ-ACK) signal transmission for the first DL data channel, Conflict between the first HARQ-ACK signal transmission of the first DL data channel and the second HARQ-ACK signal transmission for the second DL data channel, or between the first UL data channel and the second UL data channel Conflicts; and a memory coupled to the one or more processors. A computer-readable medium has executable code stored thereon for wireless communication by a user equipment (UE). The executable code includes: used for an uplink (UL) authorization or a downlink Code for a control channel in a narrow band authorized to monitor a system bandwidth; code for receiving interleaved UL and DL authorization; and code for responding to the received interleaved UL and DL A code authorized to send or receive information. A computer-readable medium has executable code stored thereon for wireless communication by a user equipment (UE). The executable code includes: used for an uplink (UL) authorization or a downlink (DL) authorization to monitor a control channel code in a narrow band of a system bandwidth; a code for receiving two consecutive UL or DL authorizations, where the continuous UL or DL authorizations of the lamp have the same HARQ process identification (ID); and a code for: selecting an authorization to be used among such authorizations based at least in part on at least one of: an authorization that meets an energy metric threshold, an authorization that is received first, or Two received authorizations, or two authorizations are selected, where these authorizations are considered as Hybrid Automatic Repeat Request (HARQ) retransmissions. A computer-readable medium has executable code stored thereon for wireless communication by a user equipment (UE). The executable code includes: used for an uplink (UL) authorization or a downlink (DL) authorized to monitor a control channel code in a narrow band of a system bandwidth; a code to receive two consecutive UL or DL authorizations; used to respond to the two consecutive received two consecutive A code authorized by UL and DL to send or receive information; and a code for identifying a conflict in response to the sent or received information, the conflict including at least one of the following: between the first DL data channel and the second DL data channel Conflict between the second DL data channel and the first HARQ-ACK signal transmission for the first DL data channel, and the first HARQ-ACK signal for the first DL data channel A conflict between the transfer and the second HARQ-ACK signal transfer for the second DL data channel, or a conflict between the first UL data channel and the second UL data channel. A computer-readable medium has executable code stored thereon for wireless communication by a base station (BS). The executable code includes: a control channel for a narrow bandwidth of a system bandwidth A code for transmitting interlaced uplink (UL) and downlink (DL) grants to a user equipment (UE); and for receiving from the UE in response to the transmitted interlaced UL and DL grants Information or a code to send information to the UE. A computer-readable medium has executable code stored thereon for wireless communication by a base station (BS). The executable code includes: a control channel for a narrow bandwidth of a system bandwidth Transmitting two consecutive uplink (UL) or downlink (DL) authorization codes to a user equipment (UE), the consecutive UL or DL authorizations having the same HARQ process identification (ID), Wherein, the UE selects one of the authorizations to be used based at least in part on at least one of the following: an authorization that meets an energy metric threshold, an authorization received first, or a second received authorization, or the UE Two authorizations are selected for use, where these authorizations are considered as Hybrid Automatic Repeat Request (HARQ) retransmissions. A computer-readable medium has executable code stored thereon for wireless communication by a base station (BS). The executable code includes: a control channel for a narrow bandwidth of a system bandwidth Transmitting two consecutive UL or DL authorization codes to a user equipment (UE); codes for sending or receiving information in response to the two consecutive UL and DL authorizations transmitted; and for responding The sending or receiving information is used to identify a conflicting code including at least one of the following: a conflict between a first DL data channel and a second DL data channel, and the second DL data channel being used for the first DL data Conflict between the first HARQ-ACK signal transmission of the channel, the first HARQ-ACK signal transmission for the first DL data channel and the second HARQ-ACK signal for the second DL data channel A conflict between transmissions, or a conflict between a first UL data channel and a second UL data channel.