WO2019031921A1 - Procédé et dispositif d'émission ou de réception de signal sans fil dans un système de communication sans fil - Google Patents

Procédé et dispositif d'émission ou de réception de signal sans fil dans un système de communication sans fil Download PDF

Info

Publication number
WO2019031921A1
WO2019031921A1 PCT/KR2018/009187 KR2018009187W WO2019031921A1 WO 2019031921 A1 WO2019031921 A1 WO 2019031921A1 KR 2018009187 W KR2018009187 W KR 2018009187W WO 2019031921 A1 WO2019031921 A1 WO 2019031921A1
Authority
WO
WIPO (PCT)
Prior art keywords
transmission
pdsch
interval
npusch
reception
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/KR2018/009187
Other languages
English (en)
Korean (ko)
Inventor
박창환
신석민
안준기
양석철
황승계
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
LG Electronics Inc
Original Assignee
LG Electronics Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by LG Electronics Inc filed Critical LG Electronics Inc
Priority to JP2020507574A priority Critical patent/JP6905636B2/ja
Priority to KR1020207006926A priority patent/KR102225951B1/ko
Priority to CN201880065397.9A priority patent/CN111247862B/zh
Priority to EP18843838.6A priority patent/EP3668236B1/fr
Publication of WO2019031921A1 publication Critical patent/WO2019031921A1/fr
Priority to US16/786,624 priority patent/US10779272B2/en
Anticipated expiration legal-status Critical
Priority to US17/018,342 priority patent/US11356998B2/en
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling

Definitions

  • the present invention relates to a wireless communication system, and more particularly, to a wireless signal transmission and reception method and apparatus.
  • the wireless communication system includes a Narrowband Internet of Things (NB-IoT) -based wireless communication system.
  • NB-IoT Narrowband Internet of Things
  • a wireless communication system is a multiple access system capable of supporting communication with multiple users by sharing available system resources (bandwidth, transmission power, etc.).
  • multiple access systems include a code division multiple access (CDMA) system, a frequency division multiple access (FDMA) system, a time division multiple access (TDMA) system, an orthogonal frequency division multiple access (OFDMA) system, a single carrier frequency division multiple access) systems.
  • CDMA code division multiple access
  • FDMA frequency division multiple access
  • TDMA time division multiple access
  • OFDMA orthogonal frequency division multiple access
  • a method for a terminal to receive a signal in a wireless communication system comprising: repetitively transmitting a Physical Uplink Shared Channel (PUSCH); And repeatedly receiving a Physical Downlink Shared Channel (PDSCH) in a DL interval immediately following the repeated transmission of the PUSCH.
  • PUSCH Physical Uplink Shared Channel
  • PDSCH Physical Downlink Shared Channel
  • each PDSCH corresponds to a corresponding (K > 1) in an OFDM (Orthogonal Frequency Division Multiplexing) symbol after the k-th time in each time unit in which the UE is operating in a guard-band or stand-
  • a method is provided in which signal reception is skipped at the beginning of the DL interval.
  • a terminal used in a wireless communication system comprising: a Radio Frequency (RF) module; And a processor configured to repeatedly transmit a Physical Uplink Shared Channel (PUSCH) and repeatedly receive a Physical Downlink Shared Channel (PDSCH) in a DL interval immediately following the repeated transmission of the PUSCH,
  • PUSCH Physical Uplink Shared Channel
  • PDSCH Physical Downlink Shared Channel
  • each PDSCH is received from the kth and subsequent Orthogonal Frequency Division Multiplexing (OFDM) symbols in each corresponding time unit in the DL interval (k> 1) - band or stand-alone mode, a terminal is provided in which signal reception is skipped at the beginning of the DL interval upon repeated reception of the PDSCH.
  • OFDM Orthogonal Frequency Division Multiplexing
  • the terminal may include a Narrowband Internet of Things (NB-IoT) terminal.
  • NB-IoT Narrowband Internet of Things
  • signal reception may be skipped in a portion of at least a first OFDM symbol of a first time unit of the DL interval upon repeated reception of the PDSCH .
  • a signal may be received from the first OFDM symbol in the second and subsequent time units of consecutive time units in the DL interval at the time of repeated reception of the PDSCH.
  • the repeated transmission of the PUSCH and the repeated reception of the PDSCH can be performed in a time division multiplexing (TDM) manner on the same carrier.
  • TDM time division multiplexing
  • the PUSCH includes a Narrowband PUSCH (NPUSCH)
  • the PDSCH includes a Narrowband PDSCH (NPDSCH)
  • the subcarrier interval used for transmission of the NPDSCH may be 15 kHz.
  • the wireless communication system may comprise a 3rd Generation Partnership Project (3GPP) -based wireless communication system.
  • 3GPP 3rd Generation Partnership Project
  • wireless signal transmission and reception can be efficiently performed in a wireless communication system.
  • FIG. 1 illustrates physical channels used in a 3GPP LTE (-A) system, which is an example of a wireless communication system, and a general signal transmission method using them.
  • -A 3GPP LTE
  • Fig. 2 illustrates the structure of a radio frame.
  • FIG. 3 illustrates a resource grid of a downlink slot.
  • FIG 5 illustrates a structure of an uplink subframe used in LTE (-A).
  • Figure 6 illustrates the structure of a self-contained subframe.
  • Figure 7 illustrates the frame structure defined in 3GPP NR.
  • Figure 8 illustrates the placement of an in-band anchor carrier at an LTE bandwidth of 10 MHz.
  • FIG. 9 illustrates a location where an NB-IoT downlink physical channel / signal is transmitted in an FDD LTE system.
  • FIG. 10 illustrates resource allocation of NB-IoT signal and LTE signal in in-band mode.
  • FIG. 11 illustrates scheduling when a multi-carrier is configured.
  • FIG. 16 illustrates a base station and a terminal that can be applied to the present invention.
  • CDMA code division multiple access
  • FDMA frequency division multiple access
  • TDMA time division multiple access
  • OFDMA orthogonal frequency division multiple access
  • CDMA may be implemented in radio technology such as Universal Terrestrial Radio Access (UTRA) or CDMA2000.
  • UTRA Universal Terrestrial Radio Access
  • TDMA may be implemented in a wireless technology such as Global System for Mobile communications (GSM) / General Packet Radio Service (GPRS) / Enhanced Data Rates for GSM Evolution (EDGE).
  • GSM Global System for Mobile communications
  • GPRS General Packet Radio Service
  • EDGE Enhanced Data Rates for GSM Evolution
  • OFDMA may be implemented in wireless technologies such as IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802-20, and Evolved UTRA (E-UTRA).
  • UTRA is part of the Universal Mobile Telecommunications System (UMTS).
  • 3rd Generation Partnership Project (3GPP) Long term evolution (LTE) is part of E-UMTS (Evolved UMTS) using E-UTRA and LTE-A (Advanced) is an evolved version of 3GPP LTE.
  • 3GPP LTE / LTE-A is mainly described, but the technical idea of the present invention is not limited thereto.
  • a terminal receives information from a base station through a downlink (DL), and the terminal transmits information through an uplink (UL) to a base station.
  • the information transmitted and received by the base station and the terminal includes data and various control information, and various physical channels exist depending on the type / use of the information transmitted / received.
  • FIG. 1 is a view for explaining a physical channel used in a 3GPP LTE (-A) system and a general signal transmission method using the same.
  • the terminal that is powered on again or the cell that has entered a new cell performs an initial cell search operation such as synchronizing with the base station in step S101.
  • a mobile station receives a primary synchronization channel (P-SCH) and a secondary synchronization channel (S-SCH) from a base station and synchronizes with the base station and stores information such as a cell identity .
  • the terminal can receive the physical broadcast channel (PBCH) from the base station and obtain the in-cell broadcast information.
  • the UE can receive the downlink reference signal (DL RS) in the initial cell search step to check the downlink channel state.
  • PBCH physical broadcast channel
  • DL RS downlink reference signal
  • the UE Upon completion of the initial cell search, the UE receives a Physical Downlink Control Channel (PDCCH) and a physical downlink control channel (PDSCH) according to physical downlink control channel information in step S102, System information can be obtained.
  • PDCCH Physical Downlink Control Channel
  • PDSCH physical downlink control channel
  • the terminal may perform a random access procedure such as steps S103 to S106 to complete the connection to the base station.
  • the UE transmits a preamble through a Physical Random Access Channel (PRACH) (S103), and transmits a response message for a preamble through the physical downlink control channel and the corresponding physical downlink shared channel (S104).
  • PRACH Physical Random Access Channel
  • S105 additional physical random access channel
  • S106 physical downlink control channel and corresponding physical downlink shared channel reception
  • the UE having performed the procedure described above transmits a physical downlink control channel / physical downlink shared channel reception step S107 and a physical uplink shared channel (PUSCH) / physical downlink shared channel
  • a Physical Uplink Control Channel (PUCCH) transmission (S108) may be performed.
  • the control information transmitted from the UE to the Node B is collectively referred to as Uplink Control Information (UCI).
  • the UCI includes HARQ ACK / NACK (Hybrid Automatic Repeat and Request Acknowledgment / Negative ACK), SR (Scheduling Request), CSI (Channel State Information)
  • the CSI includes a Channel Quality Indicator (CQI), a Precoding Matrix Indicator (PMI), a Rank Indication (RI), and the like.
  • the UCI is generally transmitted through the PUCCH, but may be transmitted via the PUSCH when the control information and the traffic data are to be simultaneously transmitted. In addition, UCI can be transmitted non-periodically through the PUSCH according to the request / instruction of the network.
  • Fig. 2 illustrates the structure of a radio frame.
  • the uplink / downlink data packet transmission is performed in units of subframes, and a subframe is defined as a time interval including a plurality of symbols.
  • the 3GPP LTE standard supports a Type 1 radio frame structure applicable to Frequency Division Duplex (FDD) and a Type 2 radio frame structure applicable to TDD (Time Division Duplex).
  • FDD Frequency Division Duplex
  • TDD Time Division Duplex
  • the downlink radio frame is composed of 10 subframes, and one subframe is composed of two slots in a time domain.
  • the time taken for one subframe to be transmitted is called a transmission time interval (TTI).
  • TTI transmission time interval
  • the length of one subframe may be 1 ms and the length of one slot may be 0.5 ms.
  • One slot includes a plurality of OFDM symbols in the time domain and a plurality of resource blocks (RBs) in the frequency domain.
  • RBs resource blocks
  • a resource block (RB) as a resource allocation unit may include a plurality of consecutive subcarriers in one slot.
  • the number of OFDM symbols included in the slot may vary according to the configuration of the CP (Cyclic Prefix).
  • CP has an extended CP and a normal CP.
  • the number of OFDM symbols included in one slot may be seven.
  • the OFDM symbol is configured by the extended CP, since the length of one OFDM symbol is increased, the number of OFDM symbols included in one slot is smaller than that of the normal CP.
  • the number of OFDM symbols included in one slot may be six. If the channel state is unstable, such as when the UE moves at a high speed, an extended CP may be used to further reduce inter-symbol interference.
  • the slot When a normal CP is used, the slot includes 7 OFDM symbols, so that the subframe includes 14 OFDM symbols.
  • the first three OFDM symbols at the beginning of a subframe may be allocated to a physical downlink control channel (PDCCH), and the remaining OFDM symbols may be allocated to a physical downlink shared channel (PDSCH).
  • PDCCH physical downlink control channel
  • PDSCH physical downlink shared channel
  • the Type 2 radio frame is composed of two half frames.
  • the half frame includes 4 (5) normal sub-frames and 1 (0) special sub-frames.
  • the normal subframe is used for uplink or downlink according to the UL-DL configuration (Uplink-Downlink Configuration).
  • the subframe consists of two slots.
  • Table 1 illustrates a subframe configuration in a radio frame according to the UL-DL configuration.
  • Uplink-downlink configuration Downlink-to-Uplink Switch point periodicity Subframe number 0 One 2 3 4 5 6 7 8 9 0 5ms D S U U U D S U U U One 5ms D S U U D D S U U D 2 5ms D S U D D D S U D D 3 10ms D S U U U D D D D D D 4 10ms D S U U D D D D D D 5 10ms D S U D D D D D D D D 6 5ms D S U U U D S U U D S U U D
  • D denotes a downlink subframe
  • U denotes an uplink subframe
  • S denotes a special subframe.
  • the special subframe includes a downlink pilot time slot (DwPTS), a guard period (GP), and an uplink pilot time slot (UpPTS).
  • DwPTS is used for initial cell search, synchronization, or channel estimation in the UE.
  • UpPTS is used to synchronize the channel estimation at the base station and the uplink transmission synchronization of the UE.
  • the guard interval is a period for eliminating the interference occurring in the uplink due to the multi-path delay of the downlink signal between the uplink and the downlink.
  • the structure of the radio frame is merely an example, and the number of subframes, the number of slots, and the number of symbols in the radio frame can be variously changed.
  • FIG. 3 illustrates a resource grid of a downlink slot.
  • the downlink slot includes a plurality of OFDM symbols in the time domain.
  • one downlink slot includes seven OFDM symbols, and one resource block (RB) is illustrated as including 12 subcarriers in the frequency domain.
  • Each element on the resource grid is referred to as a Resource Element (RE).
  • One RB includes 12 x 7 REs.
  • the number NDL of RBs included in the downlink slot depends on the downlink transmission band.
  • the structure of the uplink slot may be the same as the structure of the downlink slot.
  • FIG. 4 illustrates a structure of a downlink subframe.
  • a maximum of 3 (4) OFDM symbols located in front of a first slot in a subframe corresponds to a control region to which a control channel is allocated.
  • the remaining OFDM symbol corresponds to a data area to which a physical downlink shared chanel (PDSCH) is allocated, and the basic resource unit of the data area is RB.
  • Examples of downlink control channels used in LTE include physical control format indicator channel (PCFICH), physical downlink control channel (PDCCH), physical hybrid ARQ indicator channel (PHICH), and the like.
  • the PCFICH is transmitted in the first OFDM symbol of the subframe and carries information about the number of OFDM symbols used for transmission of the control channel in the subframe.
  • the PHICH is a response to an uplink transmission and carries an HARQ ACK / NACK (acknowledgment / negative-acknowledgment) signal.
  • the control information transmitted via the PDCCH is referred to as DCI (downlink control information).
  • the DCI includes uplink or downlink scheduling information or an uplink transmission power control command for an arbitrary terminal group.
  • the control information transmitted through the PDCCH is called DCI (Downlink Control Information).
  • the DCI format defines the formats 0, 3, 3A and 4 for the uplink and formats 1, 1A, 1B, 1C, 1D, 2, 2A, 2B and 2C for the downlink.
  • the type of the information field, the number of information fields, and the number of bits of each information field are different.
  • the DCI format may include a hopping flag, an RB assignment, a modulation coding scheme (MCS), a redundancy version (RV), a new data indicator (NDI), a transmit power control (TPC) A HARQ process number, a precoding matrix indicator (PMI) confirmation, and the like.
  • the size (size) of the control information matched to the DCI format differs according to the DCI format.
  • an arbitrary DCI format can be used for transmission of two or more types of control information.
  • DCI format 0 / 1A is used to carry either DCI format 0 or DCI format 1, which are separated by a flag field.
  • the PDCCH includes a transmission format and a resource allocation of a downlink shared channel (DL-SCH), resource allocation information on an uplink shared channel (UL-SCH), paging information on a paging channel (PCH), system information , Resource allocation information of a higher-layer control message such as a random access response transmitted on the PDSCH, transmission power control command for an individual terminal in an arbitrary terminal group, activation of VoIP (voice over IP), and the like .
  • a plurality of PDCCHs may be transmitted within the control domain.
  • the UE can monitor a plurality of PDCCHs.
  • the PDCCH is transmitted on one or a plurality of consecutive control channel element (CCE) aggregations.
  • CCE control channel element
  • the CCE is a logical allocation unit used to provide a PDCCH of a predetermined coding rate according to a state of a radio channel.
  • the CCE corresponds to a plurality of resource element groups (REGs).
  • the format of the PDCCH and the number of bits of the available PDCCH are determined according to the correlation between the number of CCEs and the code rate provided by the CCE.
  • the base station determines the PDCCH format according to the DCI to be transmitted to the UE, and adds a CRC (cyclic redundancy check) to the control information.
  • the CRC is masked with a unique identifier (called a radio network temporary identifier (RNTI)) according to the owner of the PDCCH or usage purpose.
  • RNTI radio network temporary identifier
  • the unique identifier of the terminal e.g., C-RNTI (cell-RNTI)
  • C-RNTI cell-RNTI
  • a paging indication identifier e.g., P-RNTI (p-RNTI)
  • SI-RNTI system information identifier
  • RA-RNTI random access-RNTI
  • the PDCCH carries a message known as Downlink Control Information (DCI), and the DCI includes resource allocation and other control information for one terminal or terminal group.
  • DCI Downlink Control Information
  • a plurality of PDCCHs may be transmitted in one subframe.
  • Each PDCCH is transmitted using one or more CCEs (Control Channel Elements), and each CCE corresponds to nine sets of four resource elements.
  • the four resource elements are referred to as Resource Element Groups (REGs).
  • REGs Resource Element Groups
  • Four QPSK symbols are mapped to one REG.
  • the resource element assigned to the reference signal is not included in the REG, and thus the total number of REGs within a given OFDM symbol depends on the presence of a cell-specific reference signal.
  • REG is also used for other downlink control channels (PCFICH and PHICH). That is, REG is used as a basic resource unit of the control area.
  • PCFICH downlink control channels
  • PHICH PHICH
  • PDCCH formats are supported as listed in Table 2.
  • PDCCH format Number of CCEs (n) Number of REGs Number of PDCCH bits 0 One 9 72 One 2 8 144 2 4 36 288 3 5 72 576
  • CCEs are used consecutively numbered, and in order to simplify the decoding process, a PDCCH with a format composed of n CCEs can only be started with a CCE having the same number as a multiple of n.
  • the number of CCEs used for transmission of a specific PDCCH is determined by the base station according to the channel condition. For example, if the PDCCH is for a terminal with a good downlink channel (e.g., close to the base station), a single CCE may be sufficient. However, for a terminal with a bad channel (e. G., Near cell boundaries), eight CCEs may be used to obtain sufficient robustness.
  • the power level of the PDCCH can be adjusted to meet the channel conditions.
  • the approach introduced in LTE is to define a limited set of CCE locations where the PDCCH can be located for each terminal.
  • a limited set of CCE locations where a terminal can locate its PDCCH may be referred to as a Search Space (SS).
  • SS Search Space
  • the search space has a different size according to each PDCCH format.
  • UE-specific and common search spaces are separately defined.
  • the UE-Specific Search Space (USS) is set individually for each UE, and the range of the Common Search Space (CSS) is known to all UEs.
  • the UE-specific and common search space may overlap for a given UE.
  • the base station in the given subframe may not be able to find CCE resources to transmit PDCCH to all available UEs.
  • a UE-specific hopping sequence is applied to the starting position of the UE-specific search space.
  • Table 3 shows the sizes of common and UE-specific search spaces.
  • the terminal In order to keep the computational load under the total number of blind decodings (BDs) under control, the terminal is not required to search all defined DCI formats simultaneously. Generally, within a UE-specific search space, the terminal always searches formats 0 and 1A. Formats 0 and 1A have the same size and are separated by flags in the message. In addition, the terminal may be required to receive an additional format (e.g., 1, 1B or 2 depending on the PDSCH transmission mode set by the base station). In the common search space, the terminal searches Formats 1A and 1C. Further, the terminal can be set to search Format 3 or 3A.
  • BDs blind decodings
  • Formats 3 and 3A have the same size as formats 0 and 1A and can be distinguished by scrambling the CRC with different (common) identifiers, rather than with a terminal-specific identifier.
  • PDSCH transmission scheme according to transmission mode, and information contents of DCI formats are listed below.
  • Transmission mode 1 Transmission from single base station antenna port
  • Transmission mode 7 Single-antenna port (port 5) transmission
  • Transmission Mode 8 Transmission of dual-layer transmission (ports 7 and 8) or single-antenna port (ports 7 or 8)
  • Transmission mode 9 Transmission of up to 8 layers (ports 7 to 14) or single-antenna port (ports 7 or 8)
  • ⁇ Format 1 Resource allocation for single codeword PDSCH transmission (transmission modes 1, 2 and 7)
  • ⁇ Format 1A Compact signaling of resource allocation for single codeword PDSCH (all modes)
  • Format 1B Compact resource allocation for PDSCH (mode 6) using rank-1 closed-loop precoding
  • ⁇ Format 1C Very compact resource allocation for PDSCH (eg, paging / broadcast system information)
  • ⁇ Format 1D Compact resource allocation for PDSCH (mode 5) using multi-user MIMO
  • ⁇ Format 3 / 3A Power control command with 2-bit / 1-bit power adjustment value for PUCCH and PUSCH
  • FIG 5 illustrates a structure of an uplink subframe used in LTE (-A).
  • the subframe 500 is composed of two 0.5 ms slots 501. Assuming a length of a normal cyclic prefix (CP), each slot is composed of 7 symbols 502, and one symbol corresponds to one SC-FDMA symbol.
  • a resource block (RB) 503 is a resource allocation unit corresponding to 12 subcarriers in the frequency domain and one slot in the time domain.
  • the structure of the uplink sub-frame of the LTE (-A) is roughly divided into a data area 504 and a control area 505.
  • the data region refers to a communication resource used for transmitting data such as voice and packet transmitted to each terminal and includes a physical uplink shared channel (PUSCH).
  • PUSCH physical uplink shared channel
  • the control region means a communication resource used for transmitting an uplink control signal, for example, a downlink channel quality report from each terminal, a reception ACK / NACK for a downlink signal, an uplink scheduling request, etc., and a PUCCH Control Channel).
  • a sounding reference signal (SRS) is transmitted through a SC-FDMA symbol located last in the time axis in one subframe.
  • the SRSs of the UEs transmitted in the last SC-FDMA of the same subframe can be classified according to the frequency location / sequence.
  • the SRS is used to transmit the uplink channel state to the base station, and is periodically transmitted according to the subframe period / offset set by the upper layer (e.g., RRC layer) or aperiodically transmitted according to the request of the base station.
  • FIG. 6 illustrates the structure of a self-contained subframe.
  • the hatched area indicates the DL control area and the black part indicates the UL control area.
  • the unmarked area may be used for DL data transmission or for UL data transmission. Since DL transmission and UL transmission are sequentially performed in one subframe, DL data can be transmitted in a subframe and UL ACK / NACK can be received. As a result, when a data transmission error occurs, the time required to retransmit the data is reduced, and the transfer latency of the final data can be minimized.
  • PDFICH, PHICH, and PDCCH can be transmitted, and in the DL data interval, PDSCH can be transmitted.
  • the PUCCH can be transmitted, and in the UL data interval, the PUSCH can be transmitted.
  • the GP provides a time gap in the process of switching from the transmission mode to the reception mode or from the reception mode to the transmission mode. Some OFDM symbols at the time of switching from DL to UL within a subframe can be set to GP.
  • OFDM parameters such as subcarrier spacing (SCS) and duration of an OFDM symbol (OS) based thereon may be set differently between a plurality of cells merged into one UE.
  • the (absolute time) interval of a time resource e.g., SF, slot or TTI
  • TU Time Unit
  • the symbol may include an OFDM symbol and an SC-FDMA symbol.
  • Figure 7 illustrates the frame structure defined in 3GPP NR.
  • 3GPP NR Like the radio frame structure of LTE / LTE-A (see FIG. 2), one radio frame in 3GPP NR is composed of 10 subframes, and each subframe has a length of 1 ms.
  • One subframe includes one or more slots and the slot length depends on the SCS.
  • 3GPP NR supports SCS at 15KHz, 30KHz, 60KHz, 120KHz and 240KHz.
  • the slot corresponds to the TTI in Fig.
  • Table 4 illustrates that the number of symbols per slot, the number of slots per frame, and the number of slots per subframe are different according to SCS.
  • NB-IoT Narrow Band - Internet of Things
  • 3GPP LTE Long Term Evolution
  • NR Universal Terrestrial Radio Service
  • some technical configurations may be modified and interpreted (eg, LTE band -> NR band, subframe -> slot).
  • NB-IoT supports three operating modes: in-band, guard-band and stand-alone. The same requirements apply to each mode.
  • In-band mode Some of the resources in the LTE band are allocated to the NB-IoT.
  • the NB-IoT terminal searches for an anchor carrier in units of 100 kHz for initial synchronization, and the center frequency of the anchor carrier in in-band and guard-bands should be located within ⁇ 7.5 kHz from a 100 kHz channel raster .
  • the middle six PRBs of LTE PRBs are not allocated to NB-IoT. Anchor carriers can therefore only be located in a specific PRB.
  • Figure 8 illustrates the placement of an in-band anchor carrier at an LTE bandwidth of 10 MHz.
  • a DC (Direct Current) subcarrier is located in the channel raster.
  • PRB indices 4, 9, 14, 19, 30, 35, 40, and 45 are located at a center frequency of ⁇ 2.5 kH from the channel raster because the center frequency interval between adjacent PRBs is 180 kHz.
  • the center frequency of a PRB suitable for an anchor carrier at an LTE bandwidth of 20MHz is located at ⁇ 2.5kHz from the channel raster, and the center frequency of a PRB suitable for an anchor carrier at LTE bandwidths of 3MHz, 5MHz and 15MHz is ⁇ 7.5kHz from the channel raster Located.
  • the PRB immediately adjacent to the edge PRB of LTE at 10 MHz and 20 MHz bandwidths is centered at ⁇ 2.5 kHz from the channel raster.
  • the center frequency of the anchor carrier can be positioned at ⁇ 7.5 kHz from the channel raster by using the guard frequency band corresponding to three subcarriers from the edge PRB.
  • Stand-alone mode anchor carriers are arranged in a 100kHz channel raster and all GSM carriers, including DC carriers, can be used as NB-IoT anchor carriers.
  • NB-IoT supports multi-carrier and can be used in combination of in-band + in-band, in-band + guard band, guard band + guard band and stand-alone + stand-alone.
  • the NB-IoT downlink uses an OFDMA scheme with a 15 kHz subcarrier spacing. This provides orthogonality between subcarriers to facilitate coexistence with LTE systems.
  • the NB-IoT downlink is provided with physical channels such as Narrowband Physical Broadcast Channel (NPBCH), Narrowband Physical Downlink Shared Channel (NPDSCH), and Narrowband Physical Downlink Control Channel (NPDCCH).
  • NPSS Narrowband Primary Synchronization Signal
  • NRS Narrowband Reference Signal
  • the NPBCH transmits the MIB-NB (Master Information Block-Narrowband), which is the minimum system information required for the NB-IoT terminal to access the system, to the UE.
  • the NPBCH signal has a total of eight Repeat transmission is possible.
  • the TBS (Transport Block Size) of the MIB-NB is 34 bits, and is updated every 640 ms TTI cycle.
  • the MIB-NB includes information such as an operation mode, a system frame number (SFN), a number of Hyper-SFN, a cell-specific reference signal (CRS) port number, and a channel raster offset.
  • SFN system frame number
  • CRS cell-specific reference signal
  • the NPSS consists of a ZC (Zadoff-Chu) sequence with a sequence length of 11 and a root index of 5.
  • NPSS can be generated according to the following equation.
  • S (1) for the OFDM symbol index 1 can be defined as shown in Table 5.
  • NSSS consists of a combination of a ZC sequence with a sequence length of 131 and a binary scrambling sequence such as a Hadamard sequence.
  • the NSSS indicates the PCID through the combination of the sequences to the NB-IoT terminals in the cell.
  • NSSS can be generated according to the following equation.
  • Equation (2) the variables applied to Equation (2) can be defined as follows.
  • the binary sequence b q (m) is defined as shown in Table 6, and b 0 (m) to b 3 (m) correspond to 1, 32, 64 and 128 columns of the 128th order Hadamard matrix, respectively.
  • Cyclic shift of the frame number n f (cyclic shift) ⁇ f may be defined as shown in Equation (4).
  • nf denotes a radio frame number.
  • mod represents a modulo function.
  • the NRS is provided as a reference signal for channel estimation necessary for downlink physical channel demodulation and is generated in the same manner as LTE.
  • NB-PCID Nearband-Physical Cell ID
  • NCell ID NB-IoT base station ID
  • NPDCCH has the same transmit antenna configuration as NPBCH and carries DCI. Three types of DCI formats are supported.
  • the DCI format N0 includes NPUSCH (Narrowband Physical Uplink Shared Channel) scheduling information, and the DCI formats N1 and N2 include NPDSCH scheduling information.
  • NPDCCH can transmit up to 2048 repetitions to improve coverage.
  • NPDSCH is used to transmit data (e.g., TB) on a transport channel such as a downlink-shared channel (DL-SCH) or a paging channel (PCH).
  • DL-SCH downlink-shared channel
  • PCH paging channel
  • FIG. 9 illustrates a location where an NB-IoT downlink physical channel / signal is transmitted in an FDD LTE system.
  • the NPBCH is transmitted in the first subframe of each frame, the NPSS is transmitted in the sixth subframe of each frame, and the NSSS is transmitted in the last (e.g., tenth) subframe of every even frame.
  • the NB-IoT terminal acquires frequency, symbols, and frame synchronization using the synchronization signals NPSS and NSSS and searches for 504 PCIDs (i.e., base station IDs).
  • the LTE synchronization signal is transmitted over six PRBs, and the NB-IoT synchronization signal is transmitted over one PRB.
  • the uplink physical channel is composed of NPRACH (Narrowband Physical Random Access Channel) and NPUSCH, and supports single-tone transmission and multi-tone transmission.
  • Single-tone transmission is supported for subcarrier spacing of 3.5 kHz and 15 kHz, and multi-tone transmission is only supported for 15 kHz subcarrier spacing.
  • the 15 Hz subcarrier spacing in the uplink can maintain the orthogonality with the LTE to provide optimal performance, but the 3.75 kHz subcarrier spacing can degrade the orthogonality, resulting in performance degradation due to interference.
  • the NPRACH preamble consists of four symbol groups, each symbol group consisting of a CP and five (SC-FDMA) symbols.
  • NPRACH only supports single-tone transmission of 3.75kHz subcarrier spacing and provides a CP of 66.7 ⁇ s and 266.67 ⁇ s to support different cell radiuses.
  • Each group of symbols performs frequency hopping and the hopping pattern is as follows.
  • the subcarriers transmitting the first symbol group are determined in a pseudo-random manner.
  • the second symbol group has one subcarrier hop, the third symbol group has six subcarrier hopping, and the fourth symbol group has one subcarrier hop.
  • the frequency hopping procedure is repeatedly applied.
  • the NPRACH preamble can be repeatedly transmitted up to 128 times.
  • NPUSCH supports two formats. NPUSCH format 1 is used for UL-SCH transmission and the maximum TBS is 1000 bits. NPUSCH Format 2 is used for uplink control information transmission such as HARQ ACK signaling. NPUSCH format 1 supports single- / multi-tone transmission, and NPUSCH format 2 supports only single-tone transmission. For single-tone transmission, use pi / 2-BPSK and quadrature phase shift keying (pi / 4-QPSK) to reduce the Peat-to-Average Power Ratio (PAPR).
  • PAPR Peat-to-Average Power Ratio
  • all resources contained in 1 PRB can be allocated to the NB-IoT.
  • resource mapping is limited in order to coexist with the existing LTE signal. For example, resources (0 to 2 OFDM symbols in each subframe) classified as the LTE control channel assignment region in the in-band mode can not be allocated to the NPSS / NSSS, and the NPSS / NSSS symbols mapped to the LTE CRS RE Is punctured.
  • the NPSS and the NSSS are not transmitted in the OFDM symbols corresponding to the control region of the LTE system (for example, the first three OFDM symbols in the subframe) regardless of the operation mode for ease of implementation.
  • the LTE CRS RE and the NPSS / NSS RE colliding on the physical resource are mapped so as not to affect the LTE system.
  • the NB-IoT terminal After the NPBCH demodulation, the NB-IoT terminal obtains information on the number of CRS antenna ports, but still can not know the information on the LTE control channel allocation region. Therefore, the NPDSCH that transmits SIB1 (System Information Block type 1) data is not mapped to the resource classified as the LTE control channel allocation region.
  • SIB1 System Information Block type 1
  • an RE that is not actually allocated to the LTE CRS can be allocated to the NPDSCH. Since the NB-IoT UE has acquired all the information related to the resource mapping after receiving the SIB1, the Node B maps the NPDSCH (excluding SIB1) and the NPDCCH to the available resources based on the LTE control channel information and the CRS antenna port number can do.
  • a DL / UL anchor-carrier is basically configured, and a DL (and UL) non-anchor carrier can be additionally configured.
  • the RRCConnectionReconfiguration may include information about the non-anchor carriers.
  • the terminal receives data only on the DL non-anchor carrier.
  • the synchronization signals (NPSS, NSSS), the broadcast signals (MIB, SIB) and the paging signal are provided only in the anchor-carrier.
  • the terminal listens to only DL non-anchor carriers while in the RRC_CONNECTED state. Similarly, if a UL non-anchor carrier is configured, the terminal transmits data only on UL non-anchor carriers, and simultaneous transmissions on UL non-anchor carriers and UL anchor-carriers are not allowed. When transitioning to the RRC_IDLE state, the terminal returns to the anchor-carrier.
  • UE1 is configured with anchor-carrier
  • UE2 is configured with DL / UL non-anchor carrier additionally
  • UE3 is configured with DL non-anchor carrier additionally configured. Accordingly, the carrier in which data is transmitted / received in each UE is as follows.
  • UE2 data reception (DL non-anchor-carrier), data transmission (UL non-anchor-carrier)
  • - UE3 data reception (DL non-anchor-carrier), data transmission (UL anchor-carrier)
  • the NB-IoT terminal can not simultaneously perform transmission and reception, and transmission / reception operations are limited to one band. Therefore, even if a multi-carrier is configured, the terminal requires only one transmit / receive chain in the 180 kHz band.
  • the present invention proposes (1) a UL / DL interlaced scheduling method, (2) a downlink early termination method, (3) an uplink early termination method, and (4) a switching time securing method.
  • the UL / DL interlaced scheduling method proposed by the present invention can be applied to a system supporting many repetitions in downlink and uplink transmission / reception. Particularly, when the downlink and the uplink are alternately present during repeated transmission / reception, they can be more effectively applied.
  • the present invention is described based on the NB-IoT system of 3GPP LTE Rel-13 and Rel-14, but can be applied to systems requiring repeated transmission such as release and eMTC and other general systems .
  • the present invention can be effectively applied when the amount of downlink and uplink resources are different according to the UL / DL configuration like TDD, in other duplex mode systems, when the downlink and uplink resources are insufficient for repeated transmission .
  • NPDCCH can be generalized to PDCCH or (physical) downlink control channel
  • NPDSCH can be generalized to PDSCH or (physical) downlink shared channel, (physical) downlink data channel
  • NPUSCH can be generalized to PUSCH or (physical) uplink shared channel, (physical) uplink data channel.
  • the TDD system exists in a downlink and an uplink in a crossing manner in units of a specific period in the time domain (e.g., 5 msec or 10 msec in the case of LTE). If a system such as the NB-IoT, which is characterized by iterative transmission for one HARQ process, does not allow downlink reception before completing the uplink transmission, downlink resources appearing at a specific period may be wasted. In addition, even if uplink transmission is not allowed before the downlink reception is completed, resources may be wasted. In order to overcome this problem, we propose a UL / DL interlaced scheduling scheme that can transmit and receive uplink and downlink.
  • a system such as the NB-IoT, which is characterized by iterative transmission for one HARQ process
  • the UE needs to receive an UL grant and a DL grant in a downlink resource (e.g., a subframe or a slot) in order to perform uplink data transmission and downlink data reception.
  • a downlink resource e.g., a subframe or a slot
  • a method of including both an UL grant and a DL grant in one DCI is needed rather than receiving the UL grant and the DL grant independently of each other.
  • a method of UL / DL scheduling with a single DCI and the DCI may require additional fields to distinguish between "UL Grant", "DL Grant" or "UL / DL Grant”. The following may be considered:
  • DCI (hereinafter referred to as DL / UL joint DCI) capable of simultaneously scheduling UL and DL” can be defined as "DCI capable of scheduling UL and DL separately” and another format (eg, payload size) have.
  • the terminal may not attempt to detect two DCI formats at the same time.
  • the DCI format N0 includes NPUSCH (Narrowband Physical Uplink Shared Channel) scheduling information
  • the DCI format N1 includes NPDSCH scheduling information.
  • the DCI format N0 and the DCI format N1 have the same payload size.
  • the values from 0 to 3 represented by 2 bits can indicate "DL scheduling”, “UL scheduling”, “UL / DL scheduling”, and "DL / UL scheduling", respectively.
  • the UL / DL and the DL / UL can be used after the DCI to distinguish whether the UL starts first or the DL starts first.
  • the UL scheduling delay i.e., the DCI-to-NPUSCH delay
  • the DL ACK / NACK delay i.e., the NPDSCH-to-ACK / NACK delay
  • the UL scheduling delay and the DL ACK / NACK delay can be simultaneously set to one delay value, thereby effectively reducing the DCI payload size.
  • NPUSCH format 1 For example, if the number of repeated transmissions remaining in NPUSCH format 1 is insufficient to repeatedly transmit an ACK / NACK, some ACK / NACK repetitive transmissions are piggybacked in the remaining NPUSCH format 1 and the remaining ACK / NACK repetitive transmissions are transmitted in NPUSCH format 2 Lt; / RTI > If the remaining number of repetitive transmissions of NPUSCH format 1 is sufficient to repeatedly transmit ACK / NACK, piggyback ACK / NACK to NPUSCH format 1 and transmit the remaining NPUSCH format 1 repeated transmission interval, NPUSCH format 1 transmits ACK / NACK can be transmitted without piggyback.
  • a single DCI (DL / UL joint DCI) reports only a single value with respect to delay, and the corresponding value is ACK / NACK delay (NPDSCH-to-ACK / NACK) and UL scheduling delay NPUSCH delay).
  • ACK / NACK delay NPDSCH-to-ACK / NACK
  • UL scheduling delay NPUSCH delay ACK / NACK delay
  • Commonly applied here may mean that the same delay information is derived from a single value or (2) each delay information is derived independently from a single value. (2), a plurality of different delay information can be derived from a single value.
  • an SCH indicates NPUSCH or NPDSCH according to a resource (i.e., UL, DL), and U / D grant means a case where an uplink and a downlink are scheduled on one NPDCCH ).
  • UL and DL denote UL carriers and DL carriers, respectively, or UL resources (e.g., subframes, slots) and DL resources (e.g., subframes, slots) of the same carrier.
  • the U / D grant may mean a case where the UL scheduling information and the downlink scheduling information are transmitted through the NPDCCH at a time when they do not overlap in time.
  • a / N denotes ACK / NACK information for DL-SCH data (e.g., transport block).
  • the DL-SCH data may be transmitted on the NPDSCH, and the UL-SCH data may be transmitted on the NPUSCH.
  • the change in hatching in the UL and DL means that the scrambling sequence and / or the redundancy version are changed during the repetitive transmission of the physical channel.
  • FIGS. 12 to 14 it is assumed that an NPUSCH format 1 subframe exists after an NPDSCH-to-ACK / NACK delay (for example, k0) from the last subframe reception time of the DL-SCH ACK / NACK for -SCH may be piggybacked to NPUSCH format 1 (Figs. 12-13) or transmitted separately (Fig. 14).
  • FIG. 12 illustrates a case where a UL-SCH (e.g., NPUSCH) and a DL-SCH subframe terminate at a similar time point
  • FIG. 13 illustrates a case where a UL-SCH subframe exists after the last subframe of the DL- .
  • the DL grant can be monitored during transmission of the UL-SCH subframe.
  • FIG. 14 shows a case where there is no UL-SCH subframe after the last subframe of the DL-SCH.
  • DL NPDCCH can be monitored in the subframe (see FIG. 13).
  • the UE may not expect a new uplink scheduling (during uplink transmission).
  • the UE additionally monitors the DCI of the NPDCCH during the repeated transmission of UL data in the DL subframe period And can be expected to be for downlink scheduling.
  • the expected DCI for downlink scheduling may be a DL compact DCI format.
  • the DL grant DCI format and the UL grant DCI format can be normally monitored.
  • the DL compact DCI format is a format that is unlikely to be interpreted as an UL grant.
  • the DL compact DCI format may be a format in which " Flag for format N0 / format N1 discrimination " is omitted in DCI format N0 / N1.
  • the DCI format NO and the DCI format N1 have the same payload size and are separated using a 1-bit flag for format N0 / format N1 division.
  • the UE When the UE repeatedly receives the DL data (when the DL data is repeatedly received in one DL HARQ process), it is determined that the UE has not received the ACK / NACK
  • the NPDCCH can be monitored during a specific DL subframe period. At this time, if the DL HARQ process of the UE is all scheduled and is receiving downlink, the UE may not expect a new downlink scheduling (during downlink reception). Accordingly, when all the DL HARQ processes of the UE are scheduled to be downlink-received and a part of the UL HARQ process is not scheduled, the UE additionally monitors the DCI of the NPDCCH (during a specific DL subframe period) for uplink scheduling Can be expected.
  • the expected DCI for uplink scheduling may be UL compact DCI format.
  • the UL compact DCI can be used for UL early termination (e.g., methods # 6-8).
  • the DL grant DCI format and the UL grant DCI format can be normally monitored.
  • the UL compact DCI format is a format that is unlikely to be interpreted as a DL grant.
  • the UL compact DCI format may be a format in which " Flag for format N0 / format N1 discrimination " is omitted in DCI format N0 / N1.
  • the UL compact DCI format may be a format designed to request to report an ACK / NACK for the DL data being received.
  • the UE transmits an ACK / NACK (or only in the case of ACK) for the DL data to the indicated UL resource (e.g., NPUSCH ) Can be reported using.
  • NPDCCH monitoring may not be performed in the DL subframe period (e.g., NPDCCH monitoring is skipped).
  • ⁇ UL / DL interlaced scheduling may only be applicable to UEs at or above a certain CE (Coverage Enhancement) level.
  • CE Crossage Enhancement
  • MME Mobility Management Entity
  • CE levels i.e., CE levels 0 to 2.
  • messages are repeatedly transmitted several times depending on the terminal location.
  • UEs below (or beyond) a certain CE level may not monitor NPDCCH (eg, skip NPDCCH monitoring) before the scheduled UL or DL HARQ process is completed.
  • NPDCCH eg, skip NPDCCH monitoring
  • a UE having two or more HARQ processes can monitor the NPDCCH even before the scheduled UL or DL HARQ process is completed.
  • ⁇ UL / DL interlaced scheduling may only be applicable for NPDCCHs that are set to a specific Rmax or less (or greater).
  • Rmax represents the number of NPDCCH repetitive transmissions.
  • ⁇ UL / DL interlaced scheduling can only schedule NPUSCH and / or NPDSCH over (or below) a certain number of repetitive transmissions.
  • NPDCCH monitoring can be performed in a specific downlink subframe / slot interval before NPUSCH transmission corresponding to the set number of repetition transmissions is completed (e.g., see FIG. 13).
  • the UE can perform the NPDCCH detection attempt in the NPDCCH monitoring carrier (see FIG. 11) for a certain period of time.
  • the specific time may be a UL gap or a value allowed to track downlink synchronization.
  • ⁇ NPUSCH can direct the gap section for NPDCCH monitoring in the UL grant that directed transmission.
  • the UL / DL interlaced scheduling can effectively use downlink and uplink sub-frames (slots) discretely crossing on the time axis.
  • UL / DL interlaced scheduling requires additional NPDCCH monitoring, which can consume more power of the UE.
  • the UE can expect UL / DL interlaced scheduling only under certain conditions or additionally perform NPDCCH monitoring. For example, if the number of downlink subframes existing between uplink repetition transmissions is smaller than a specific value (or ratio) or equal to or smaller than the maximum number of repetitive transmissions (Rmax) of NPDCCH, Can be performed.
  • NPDCCH may be additionally monitored in the corresponding interval if a condition of postpone NPUSCH transmission for a certain period occurs for downlink synchronization tracking. This can be set considering the UL / DL switching gap of the UE. It is also possible to explicitly set a specific interval for NPDCCH monitoring during NPUSCH repeat transmission in the UL grant scheduling NPUSCH.
  • the measurement accuracy of the NB-IoT system which uses a narrow band and supports a large MCL (Max Coupling Loss), is relatively poor compared to a system using a wide band. Accordingly, the base station can set the NPDSCH repetitive transmission count to an excessively high value based on the incorrect measurement measured by the UE. In this case, the UE can decode successfully before receiving the NPDSCH for the set number of repeated transmissions. In order to overcome this waste of resources, a method is needed to report DL ACK / NACK before NPDSCH iterative reception is completed. In particular, when the uplink and the downlink resources intersect on the time axis as in the TDD system, a method of quickly reporting an ACK / NACK using the uplink resources existing in the downlink repeated reception can be effectively applied.
  • the ACK can be reported quickly from the uplink resources existing in the downlink repeated reception.
  • the DL decoding result reported in the uplink can be allowed only for the ACK.
  • the UE transmits an ACK / NACK resource set in the uplink resource (eg, subframe, slot) corresponding to the ACK / NACK reporting delay which is earlier than the longest ACK / NACK reporting delay only when an ACK is generated during NPDSCH repeated reception Can be used to report an ACK.
  • the uplink resource eg, subframe, slot
  • ACK or NACK can be reported using the last ACK / NACK resource (ie, the ACK / NACK resource set in the longest ACK / NACK reporting delay) have.
  • ACK or NACK is reported using the last ACK / NACK resource set can do.
  • the base station may set up a plurality of DL ACK / NACK reporting resources.
  • each DL ACK / NACK report resource may correspond to each ACK / NACK report delay.
  • ACK / NACK resources 1 to N-1 can be used only when the decoding result of the NPDSCH being received is ACK, when a plurality of DL ACK / NACK report resources are sequentially 1 to N (N> 1).
  • NACK resource N to report ACK or NACK.
  • the ACK / NACK resource N corresponds to the longest ACK / NACK reporting delay.
  • NPUSCH format 1 transmission is performed with NPDSCH repeated reception and NPDSCH decoding result ACK is generated, NPUSCH format 1 during transmission can be stopped for a specific time and ACK can be transmitted through NPUSCH format 2.
  • the ACK may be in NPUSCH format 1 during transmission, and the data in the position where ACK is carried in NPUSCH format 1 may be punctured.
  • NACK may not be piggybacked to NPUSCH format 1.
  • Method # 5 Method of simultaneously transmitting ACK / NACK and UL data
  • ⁇ ACK / NACK and UL data can be multiplexed (ACK / NACK piggyback)
  • NPUSCH format 1 for NPUSCH format 1 and NPUSCH format 2 for ACK / NACK reporting can be FDM if the number of tones in NPUSCH format 1 for UL data transmission is less than 1RB (12 tones).
  • the ACK / NACK can be mapped to the DMRS double-sided OFDM symbol of NPUSCH format 1 in the time axis, and the NPUSCH format 1 data on both sides of the DMRS can be punctured.
  • ACK / NACK can be transmitted, omitting some repetitive transmission of NPUSCH format 1.
  • the base station When the number of tones of NPUSCH Format 1 is smaller than 1RB, the base station multiplexes data resources that can be piggybacked by ACK (or ACK / NACK) and data resources that do not piggyback ACK (or ACK / NACK) ACK (or ACK / NACK) and data can be distinguished.
  • NPUSCH format 1 that piggybacks ACK / NACK may be allowed to be transmitted at a higher power than NPUSCH format 1 that does not piggyback ACK / NACK.
  • ⁇ ACK / NACK and UL data can be transmitted separately.
  • the scheduling delay can be set to one value. After the scheduling delay, transmission of NPUSCH format 2 for ACK / NACK reporting may be initiated first, and NPUSCH format 1 may be transmitted serially after NPUSCH format 2 repeat transmission is complete. That is, NPUSCH format 1 and NPUSCH format 2 for ACK / NACK reporting can be TDM.
  • ACK / NACK can be transmitted in a special subframe.
  • a plurality of ACK / NACK reporting delays can be set for the corresponding DL HARQ process.
  • the UE can report an ACK using the ACK / NACK resources allocated to the ACK / NACK reporting delay which is earlier than the longest ACK / NACK reporting delay only when an ACK is generated during NPDSCH repeated reception. If the ACK / NACK reporting delay is not reported before the longest ACK / NACK reporting delay, the ACK / NACK resource set in the UL resource (eg, subframe, slot) corresponding to the last ACK / NACK resource ACK or NACK can always be reported using NACK resources.
  • the measurement accuracy of the NB-IoT system which uses a narrow band and supports a large MCL, is relatively poor compared to a system using a wide band. Accordingly, the base station can set the NPUSCH repetition transmission number to an excessively high value based on the incorrect measurement measured at the terminal. Therefore, the base station can successfully decode before receiving the NPUSCH for the set number of repeated transmissions. In this case, the ACK for the UL data is quickly fed back to the downlink, thereby reducing unnecessary use of UL resources and preventing unnecessary power consumption of the terminal.
  • NPDCH monitoring can be performed in the downlink subframe interval before NPUSCH repeat transmission is completed.
  • Explicit ACK channels can be monitored.
  • the NACK may not be transmitted separately before NPUSCH repeat transmission is completed.
  • the NPDCCH DCI that the UE monitors before completing the NPUSCH iterative transmission for a specified number of times may be a UL compact DCI designed for UL early termination.
  • the UE may attempt blind decoding only on the UL compact DCI designed for UL early termination.
  • the maximum number of repetitive transmissions of the UL compact DCI may be smaller than the maximum number of repetitive transmissions of the (normal) DCI for the UL grant.
  • NPDCCH monitoring for UL early termination may not be attempted. Since monitoring the NPDCCH in the DL subframe always present during the NPUSCH repetition transmission may cause unnecessary power consumption. Accordingly, NPDCCH monitoring for UL early termination can be omitted when the probability that the NPUSCH that is being repeatedly transmitted is decoded to ACK is very small. For example, certain conditions are as follows.
  • the number of downlink subframes that can be monitored by NPDCCH during repetitive transmission of NPUSCH is shorter than a certain value (i.e., the number of DL subframes that can feed back ACK for early termination of UL is smaller than a predetermined value)
  • ⁇ NPDSCH is interlaced scheduling and is proceeding by interlacing NPUSCH transmission and NPDSCH reception. That is, when UL / DL data is being transmitted / received by interlaced scheduling, it is possible to preferentially receive NPDSCH instead of NPDCCH monitoring in a downlink subframe interval existing during NPUSCH repeated transmission.
  • An ACK for a UL HARQ process can be transmitted in a DL subframe having an NPUSCH transmission time and a specific time interval.
  • the NACK may not be transmitted separately.
  • the ACK / NACK channel monitoring during NPUSCH repeat transmission for UL early termination may be designed with an explicit ACK channel (synchronous ACK / NACK).
  • the explicit ACK channel may be designed to always report an ACK in a downlink resource / interval having a specific relationship with the NPUSCH transmission resource.
  • the resources (e.g., transmission time / frequency tone) for the explicit ACK channel may be the starting subframe (or slot) of NPUSCH Format 1, the location / number of tones and / Can be defined and reserved in relation to the number of transmissions.
  • the UE can monitor the ACK for the corresponding UL HARQ process in the promised downlink resource during the transmission of the NPUSCH Format 1. [ If ACK is not detected, the terminal can continue to transmit NPUSCH format 1 that was being transmitted.
  • the implicit ACK / NACK method is a method of interpreting an ACK / NACK for UL data by feedbacking an NDI (UL grant) for a UL HARQ process that has been completed or being transmitted. At this time, if the NDI for the UL HARQ process is toggled, it is instructed / interpreted to transmit new data in the corresponding UL HARQ process. If the NDI is not toggled, the UL HARQ process is terminated or retransmitted Can be instructed / interpreted.
  • transceiver switching times are required for DL-to-UL and UL-to-DL switching.
  • Use of the last interval of a (physical) channel previously transmitted in UL-to-DL or DL-to-UL interlaced transmission / reception and / or the first interval of (physical) channel transmitted subsequently There may be restrictions.
  • a method of securing a time gap is required.
  • a concrete method may be applied differently depending on an operation mode and the like.
  • a time used for securing a time gap (i.e., a period in which the UE does not expect to receive a downlink signal or an uplink signal transmission is not allowed) is used for transmission of a TTI or one physical channel
  • a time gap i.e., a period in which the UE does not expect to receive a downlink signal or an uplink signal transmission is not allowed
  • the channel of the time interval within which the transmission is allowed or expected to be received within a basic unit time if it corresponds to a part of the basic unit time (e.g., a subframe, a slot). For example, it is possible to ignore the signal of the interval used for the time gap or to differentiate the rate-matching of the transmission / reception channel considering the time gap interval.
  • Interlaced scheduling and transmission / reception of interlaced channels may require different time gaps depending on the operating mode.
  • An explicit time gap between NPDCCH / NPDSCH reception and NPUSCH transmission may not be required.
  • an explicit time gap between NPDCCH / NPDSCH reception and NPUSCH transmission may not be defined.
  • the 'GP + UpPTS' section included in the special subframe between DL and UL can be utilized as a guard time for the time gap (see FIG. 2 (b)).
  • the terminal in the DwPTS of the special subframe just before NPUSCH transmission, the terminal may be set not to receive the NPDCCH / NPDSCH. This may vary depending on the DwPTS length. Also, the NPDCCH / NPDSCH of the DwPTS section not received may not be included in the total number of iterations.
  • the control area size of the first DL subframe receiving DL after UL transmission (right) It can be set to another value larger than the value set in the -IoT system information block. That is, when the UL / DL interlacing operation is performed, the UE can interpret the control area in the first DL subframe that receives the DL after UL transmission (right) differently from the value broadcasted in the system information block have. On the other hand, in the DL sub-frame other than the first DL sub-frame, the size of the control area can be interpreted as the same as the value broadcasted in the system information block.
  • An explicit time gap between NPDCCH / NPDSCH reception and NPUSCH transmission may not be required.
  • an explicit time gap may not be defined between NPUSCH transmission and NPDCCH / NPDSCH reception.
  • the 'GP + UpPTS' section included in the special subframe between DL and UL can be utilized as a guard time for the time gap. Therefore, even if the UpPTS can be used for the NPUSCH transmission, the UpPTS of the special subframe following the DL reception may not be used. That is, the UE can select / analyze differently depending on whether UL / DL interlacing is applied / not operated, whether or not the UpPTS of the special subframe is used for NPUSCH transmission.
  • UpPTS can be used for NPUSCH transmission in the application / operation of UL / DL interlacing, the UpPTS of the special subframe following the DL reception is not used.
  • UpPTS of a special subframe following DL reception can be used for NPUSCH transmission.
  • an explicit gap can be defined between NPUSCH transmission and NPDCCH / NPDSCH reception.
  • a particular subframe or slot is used as a guard time, there may be a restriction on the use of some consecutive DL subframes after UL subframe (right) depending on whether UL / DL interlacing is applied / operated.
  • the virtual control area is utilized as the guard time, the number of OFDM symbols constituting the control area may have any value other than zero. That is, in the guard-band and stand-alone operation modes, the number of symbols in the control area is assumed to be 0.
  • the UE may skip receiving the downlink signal (e.g., NPDCCH / NPDSCH) at the beginning of the first DL subframe after UL transmission (e.g., NPUSCH) (immediately).
  • a downlink signal e.g., NPDCCH / NPDSCH
  • the guard time for switching is understood to be an implicit gap in that a certain number of symbols (e.g., corresponding to the control area size of a particular value in the previous example) are not always used between NPUSCH transmission and NPDCCH / NPDSCH reception .
  • the number of symbols for transceiver switching is not independently signaled and can be assumed to be a specific value. Accordingly, the UE may skip receiving the downlink signal (e.g., NPDCCH / NPDSCH) at the beginning of the first DL subframe (or consecutive DL subframe) after UL transmission (e.g., NPUSCH) (immediately).
  • a terminal e.g., an NB-IoT terminal
  • the UL interval includes a plurality of time units (e.g., TTI, subframe, slot), and each PUSCH may be transmitted on a corresponding time unit in the UL interval. Thereafter, the UE can be scheduled to repeatedly receive the PDSCH in the DL interval immediately following the repeated transmission of the PUSCH.
  • the DL interval also includes a plurality of time units (e.g., TTI, subframe, slot), and each PDSCH may be received via a corresponding time unit in the DL interval.
  • each PDSCH can be received from the k-th and later OFDM symbols in each corresponding time unit in the DL interval.
  • k is an integer greater than one and may be received via system information SI (e.g., NB-IoT system information block).
  • the signal reception (process) may be skipped at the beginning of the DL interval at the time of repeated reception of the PDSCH.
  • the first PDSCH may skip signal reception (process) at a portion of at least the first OFDM symbol of the corresponding time unit.
  • the second and subsequent PDSCHs may be received from the first OFDM symbol in the corresponding time unit.
  • the repeated transmission of the PUSCH and the repeated reception of the PDSCH can be performed in the TDM manner on the same carrier.
  • the UL / DL resource configuration on the carrier can be indicated by the UL / DL configuration in Table 1.
  • the PUSCH may include NPUSCH and the PDSCH may include NPDSCH.
  • N The subcarrier interval used for transmission of the PDSCH may be 15 kHz.
  • the wireless communication system may also include a 3GPP-based wireless communication system.
  • guard time intervals e.g., subframe, slot, symbol (s), symbol portions
  • puncturing or rate matching e.g., subframe, slot, symbol (s), symbol portions
  • the punctured time interval may be the first symbol of the uplink interval or the last symbol of the uplink interval or the first symbol of the downlink interval or the last symbol of the downlink interval, And a downlink.
  • the interval used for puncturing may be differently applied among the listed intervals depending on whether a reference signal is included in the punctured time interval.
  • the terminal when receiving a downlink signal (e.g., NPDCCH / NPDSCH) immediately after uplink transmission (e.g., NPUSCH transmission), the first OFDM symbol (i.e., UL subframe) (I.e., the first OFDM symbol of the subsequent DL subframe) is actually transmitted by the base station, the terminal may not receive the downlink signal from the first OFDM symbol (or at least a part of the first OFDM symbol) of the downlink interval NPDCCH / NPDSCH reception is skipped). That is, it can be interpreted that the corresponding OFDM symbol is punctured in the specific mobile station.
  • a downlink signal e.g., NPDCCH / NPDSCH
  • uplink transmission e.g., NPUSCH transmission
  • the first OFDM symbol i.e., UL subframe
  • the terminal may not receive the downlink signal from the first OFDM symbol (or at least a part of the first OFDM symbol) of the downlink interval NPDCCH / N
  • the UEs that do not perform UL / DL interlacing do not require much transceiver switching time, or are sufficiently absorbed by the transceiver switching time with an offset equal to the TA (Timing Advance) value of the uplink transport channel,
  • the OFDM symbol can be transmitted without puncturing it.
  • the transceiver switching time may not be required. In this case, the UE can normally receive the first OFDM symbol of the downlink reception interval (immediately after the UL transmission).
  • the data of the transmission channel in the transmission period excluding the guard time interval in the subframe may be rate-matched or punctured according to the number of repetitions of the transmission channel. For example, if the number of iterations is smaller than a certain value, the guard time can be rate-matched considering the resources (e.g., RE) of the remaining time period. On the other hand, if the number of repetitions is larger than a certain value, the guard time interval is punctured and rate-matching may not be applied to the remaining time intervals except guard time.
  • the same mapping between repetitive transmissions i.e., the same RE between repetitive transmissions by puncturing
  • a coding gain due to rate- Lt; / RTI &gt is mapped to the same information.
  • the interval and interlacing scheduling constraints or transmit / receive constraints used to ensure transceiver switching time may vary depending on the mode of operation of the carrier.
  • the time for frequency retuning may vary depending on the operating mode of the carrier used after the frequency retuning. For example, in the case of frequency retuning from the uplink carrier to the downlink carrier, a 1 msec gap may not be needed when the downlink carrier is in the in-band operation mode. In this case, the UE can expect to receive the first part of the NB-IoT channel (for example, the first OFDM symbol after the CFI value of the LTE legacy terminal set to the NB-IoT terminal) or the first symbol within 1msec I can not.
  • the terminal may not expect the NB-IoT channel for the first 1 msec or expect the NB-IoT channel for the slot-based time. That is, the concrete method of securing the frequency retuning time may vary depending on whether or not an interval in which the NB-IoT channel / signal is not expected to be received is included in the time for frequency retuning.
  • the interval and interlacing scheduling constraints or send / receive constraints used to secure the transceiver switching time may be different depending on whether the carrier is anchor-carrier or non-anchor carrier. For example, when frequency retuning is performed on a downlink carrier from an uplink carrier, a 1 msec gap may not be needed when the downlink carrier is a non-anchor carrier. In this case, the UE also expects to receive a part of the first symbol of the NB-IoT channel (i.e., the first OFDM symbol after the CFI value of the LTE legacy terminal set to the NB-IoT UE) The explicit guard time may not be defined. On the other hand, in the case of an anchor carrier, an explicit guard time can be defined so that the NB-IoT channel is not expected for the first 1 msec or the NB-IoT channel is not expected for the slot time.
  • the interval and interlacing scheduling constraints or send / receive constraints used to secure the transceiver switching time may vary depending on whether the guard time interval required for UL-to-DL switching includes valid or invalid subframes.
  • Intervals and interlacing scheduling constraints or transmit / receive constraints used to secure transceiver switching time may vary depending on whether the TA is applied to the UL channel transmitted by the UE in the UL interval of the UL-to-DL interval. For example, in the case of transmitting NPRACH, since TA is not applied, there may be restrictions on the use of the following DL sub-frame for the transceiver switching gap in the UL-to-DL period. That is, some downlink OFDM symbols or some subframes (e.g., 1 msec) may require use constraints (puncturing or rate-matching). In addition, the required DL constraint interval may vary according to the NPRACH format transmitted by the UE.
  • the DL constraint interval may be set to another value (e.g., a punctured or rate-matched interval).
  • the DL channel / signal following the NPUSCH transmission to which the TA is applied can be defined to be received by the UE.
  • specific conditions that may not receive the DL channel / signal may be defined according to the above listed conditions (operation mode, anchor / non-anchor carrier, valid / invalid subframe, etc.).
  • Method # 9 can be defined not to be applied in a situation where npusch-AllSymbols and srs-SubframeConfig are set to apply Method # 10 below or to avoid SRS transmission of existing LTE terminals.
  • method # 9 may not be applied when the UE is instructed to omit the last symbol transmission (at least one) when transmitting the UL in the UL valid subframe immediately prior to reception of the DL valid subframe.
  • the DL valid subframe means a subframe in which NPDCCH or NPDSCH transmission can be performed
  • the UL valid subframe means a subframe in which NPUSCH transmission can be performed.
  • the terminal operation is the same as in FIG.
  • the terminal does not apply the signal reception (process) skipped at the beginning of the DL subframe immediately after the subframe in which the NPUSCH is transmitted. That is, the UE can receive the NPDSCH signal from the first symbol of the DL subframe immediately after the subframe in which the NPUSCH is transmitted.
  • Method # 10 Method for securing time gap and / or RF switching gap for transceiver switching (DL-to-UL and UL-to-DL) utilizing SRS interval setting
  • Method # 9 is a method for preventing a terminal from receiving a part of a downlink signal after switching and transition.
  • a method of securing a time gap using the SRS transmission interval is a method of securing a time gap by allowing / promising not to transmit a part of an uplink signal before switching.
  • Table 7 shows an example of setting npusch-AllSymbols and srs-SubframeConfig to avoid SRS transmission of existing LTE terminals.
  • srs-SubframeConfig indicates a subframe period / offset used to define a set of subframes in which SRS transmission is set in the cell.
  • npusch-AllSymbols or similar parameters, indicating that the NPUSCH last symbol is not transmitted, or that the last symbol of a consecutive UL valid subframe is not transmitted, or UL valid subframe and DL valid subframe (Indicating that the frame should not transmit the last symbol in the UL valid subframe of the adjacent interval) is false, it may instruct to omit the last symbol transmission of the UL valid subframe.
  • the proposed interpretation / instruction can be applied only to the following. The following items can be combined.
  • - UL / DL interlacing can only be applied to terminals that are set up or performed. That is, even if the information is configured in the cell in common, UL UL symbol transmission can be omitted only for the UEs that are actually set to perform the UL / DL interlacing operation.
  • NPDCCH monitoring interval is set to 1msec or more after NPUSCH Format 2 transmission, or if there is an interval in which the UE is not allowed to receive in the valid DL subframe immediately following UL transmission, the UL last symbol transmission
  • the skipping operation may not be applied.
  • the operation of omitting the UL last symbol transmission may not be applied since the control region of the sub-frame may be utilized in the UL-to-DL gap. Therefore, the operation of omitting the UL last symbol transmission only in the guard-band / stand-alone operation mode can be applied.
  • Method # 10 may not be configured or may be defined to omit the operation of Method # 10.
  • the proposed method # 9 and # 10 are used not only to secure the transceiver switching gap and the RF switching gap but also the relay / channel and relay-terminal link / channel and relay of the base station-relay when the NB-IoT / eMTC relay is introduced It can also be used to mitigate interference between relay links / channels.
  • the relay divides time into 1) performing communication with the base station, 2) performing communication with a terminal serviced by the relay, or 3) performing communication with the relay of the next hop, ) Intervals may be required, and Proposed Methods # 9 and # 10 may be utilized to ensure this.
  • the UL / DL interlaced scheduling scheme proposed by the present invention may correspond to the terminal capability, for example, related to the number of HARQ processes. That is, a terminal supporting only a single-HARQ may not expect interlaced scheduling. However, according to the UL / DL configuration in the TDD system, the throughput obtained through the interlaced scheduling may be larger than the throughput obtained by the 2-HARQ. Therefore, a terminal supporting only a single-HARQ process can be informed that it supports interlaced scheduling with a separate capability signal.
  • the base station may perform interlaced scheduling only when it meets such a specific scheme or a specific condition.
  • the Node B may transmit the NPDSCH to be scheduled to the UE and the NPUSCH to be scheduled in the UL in a specific memory size (e.g., a reference memory size or a 2-HARQ buffer set with reference to the HARQ buffer, The reference memory size set as a reference) can be interlaced.
  • the reception soft-buffer of the UE can calculate the number of bits for representing the LLR for each information bit by designating the base station or a specific value in the standard. If the UE receives interleaved scheduling that does not satisfy this requirement, a part or all of the buffer may be overwritten with newly received or transmitted information, or late interleaved scheduling may be ignored .
  • FIG. 16 illustrates a base station and a terminal that can be applied to the present invention.
  • a wireless communication system includes a base station (BS) 110 and a terminal (UE) 120. If the wireless communication system includes a relay, the base station or the terminal may be replaced by a relay.
  • BS base station
  • UE terminal
  • the base station 110 includes a processor 112, a memory 114, and a radio frequency (RF) unit 116.
  • the processor 112 may be configured to implement the procedures and / or methods suggested by the present invention.
  • the memory 114 is coupled to the processor 112 and stores various information related to the operation of the processor 112.
  • the RF unit 116 is coupled to the processor 112 and transmits and / or receives wireless signals.
  • the terminal 120 includes a processor 122, a memory 124 and a radio frequency unit 126.
  • the processor 122 may be configured to implement the procedures and / or methods suggested by the present invention.
  • the memory 124 is coupled to the processor 122 and stores various information related to the operation of the processor 122.
  • the RF unit 126 is coupled to the processor 122 and transmits and / or receives radio signals.
  • the embodiments of the present invention have been mainly described with reference to a signal transmission / reception relationship between a terminal and a base station.
  • This transmission / reception relationship is equally or similarly extended to the signal transmission / reception between the terminal and the relay or between the base station and the relay.
  • the specific operation described herein as being performed by the base station may be performed by its upper node, in some cases. That is, it is apparent that various operations performed for communication with a terminal in a network including a plurality of network nodes including a base station can be performed by a network node other than the base station or the base station.
  • a base station may be replaced by terms such as a fixed station, a Node B, an eNode B (eNB), an access point, and the like.
  • the terminal may be replaced by terms such as a UE (User Equipment), a Mobile Station (MS), and a Mobile Subscriber Station (MSS).
  • UE User Equipment
  • MS Mobile Station
  • MSS Mobile Subscriber Station
  • Embodiments in accordance with the present invention may be implemented by various means, for example, hardware, firmware, software, or a combination thereof.
  • an embodiment of the present invention may include one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs) field programmable gate arrays, processors, controllers, microcontrollers, microprocessors, and the like.
  • ASICs application specific integrated circuits
  • DSPs digital signal processors
  • DSPDs digital signal processing devices
  • PLDs programmable logic devices
  • an embodiment of the present invention may be implemented in the form of a module, a procedure, a function, or the like for performing the functions or operations described above.
  • the software code can be stored in a memory unit and driven by the processor.
  • the memory unit may be located inside or outside the processor, and may exchange data with the processor by various well-known means.
  • the present invention can be used in a terminal, a base station, or other equipment of a wireless mobile communication system.

Landscapes

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

Abstract

La présente invention concerne un système de communication sans fil et, plus précisément, un procédé comprenant les étapes consistant : à transmettre de manière répétée un PUSCH ; et à recevoir de manière répétée le PDSCH dans une durée DL suivant immédiatement la transmission répétée du PDSCH. Lorsqu'un terminal fonctionne dans un mode intrabande, chaque PDSCH est reçu d'un symbole OFDM suivant un k-ième symbole OFDM dans chaque unité de temps correspondante dans la durée DL (k >1), et dans le cas où le terminal fonctionne dans un mode bande de garde ou un mode autonome, la réception de signal est ignorée au niveau d'une partie de début de la durée de DL lorsque le PDSCH est reçu de manière répétée.
PCT/KR2018/009187 2017-08-10 2018-08-10 Procédé et dispositif d'émission ou de réception de signal sans fil dans un système de communication sans fil Ceased WO2019031921A1 (fr)

Priority Applications (6)

Application Number Priority Date Filing Date Title
JP2020507574A JP6905636B2 (ja) 2017-08-10 2018-08-10 無線通信システムにおいて無線信号の送受信方法及び装置
KR1020207006926A KR102225951B1 (ko) 2017-08-10 2018-08-10 무선 통신 시스템에서 무선 신호 송수신 방법 및 장치
CN201880065397.9A CN111247862B (zh) 2017-08-10 2018-08-10 用于无线通信系统中的无线信号发送或接收的方法和装置
EP18843838.6A EP3668236B1 (fr) 2017-08-10 2018-08-10 Procédé et dispositif d'émission ou de réception de signal sans fil dans un système de communication sans fil
US16/786,624 US10779272B2 (en) 2017-08-10 2020-02-10 Method and device for wireless signal transmission or reception in wireless communication system
US17/018,342 US11356998B2 (en) 2017-08-10 2020-09-11 Method and device for wireless signal transmission or reception in wireless communication system

Applications Claiming Priority (14)

Application Number Priority Date Filing Date Title
US201762543928P 2017-08-10 2017-08-10
US62/543,928 2017-08-10
US201762586208P 2017-11-15 2017-11-15
US62/586,208 2017-11-15
US201762591137P 2017-11-27 2017-11-27
US62/591,137 2017-11-27
US201862662204P 2018-04-24 2018-04-24
US62/662,204 2018-04-24
KR10-2018-0050204 2018-04-30
KR20180050204 2018-04-30
KR20180053607 2018-05-10
KR10-2018-0053607 2018-05-10
KR10-2018-0056995 2018-05-18
KR20180056995 2018-05-18

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/786,624 Continuation US10779272B2 (en) 2017-08-10 2020-02-10 Method and device for wireless signal transmission or reception in wireless communication system

Publications (1)

Publication Number Publication Date
WO2019031921A1 true WO2019031921A1 (fr) 2019-02-14

Family

ID=65272400

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2018/009187 Ceased WO2019031921A1 (fr) 2017-08-10 2018-08-10 Procédé et dispositif d'émission ou de réception de signal sans fil dans un système de communication sans fil

Country Status (1)

Country Link
WO (1) WO2019031921A1 (fr)

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017069470A1 (fr) * 2015-10-19 2017-04-27 엘지전자 주식회사 Procédé et équipement d'utilisateur pour recevoir des signaux de liaison descendante, et procédé et station de base pour transmettre des signaux de liaison descendante

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017069470A1 (fr) * 2015-10-19 2017-04-27 엘지전자 주식회사 Procédé et équipement d'utilisateur pour recevoir des signaux de liaison descendante, et procédé et station de base pour transmettre des signaux de liaison descendante

Non-Patent Citations (5)

* Cited by examiner, † Cited by third party
Title
CATT: "NB-PUSCH/NB-PDSCH coding and repetition for NB-IoT", RL-161955, 3GPP TSG RAN WG1 NB-IOT AD-HOC MEETING, 16 March 2016 (2016-03-16), Sophia Antipolis , France, XP051081071 *
LG ELECTRONICS: "SPS support in NB-IoT", RL-1707573, 3GPP TSG RAN WG1 MEETING #89, 6 May 2017 (2017-05-06), Hangzhou, Fhina, XP051261915 *
NOKIA: "Un resource allocationand TBS determination tor PDSCH and CP-OFDM based PUSCH in NR", RL-1708521, 3GPP TSG RAN WG1 MEETING #89, 6 May 2017 (2017-05-06), Hangzhou, China, XP051262520 *
PARK, DONG HYEON ET AL.: "The Trend of NB-IOT Related Standardization in 3Gpp", TTA JOURNAL, vol. 166, July 2016 (2016-07-01), KOREA, pages 58 - 6, XP009519441 *
See also references of EP3668236A4 *

Similar Documents

Publication Publication Date Title
WO2020145769A1 (fr) Procédé de transmission de canal partagé de liaison montante dans un système de communication sans fil et dispositif faisant appel à celui-ci
WO2017052199A1 (fr) Procédé et équipement utilisateur permettant la réception d'informations de commande de liaison descendante, et procédé et station de base permettant l'émission d'informations de commande de liaison descendante
WO2019160364A1 (fr) Procédé et appareil d'émission et de réception de signal sans fil dans un système de communication sans fil
WO2019050368A1 (fr) Procédé et appareil de transmission et de réception de signaux sans fil dans un système de communication sans fil
WO2019031951A1 (fr) Procédé et dispositif de transmission ou de réception de signal sans fil dans un système de communication sans fil
WO2019031787A1 (fr) Procédé et dispositif permettant de recevoir un signal dans un système de communication sans fil
WO2018203722A1 (fr) Procédés d'émission et de réception de signaux entre terminal et station de base dans un système de communication sans fil, et dispositifs pour les prendre en charge
WO2014017746A1 (fr) Procédé et terminal pour effectuer harq
WO2012144801A2 (fr) Dispositif et procédé de transmission de signal dans un système de communication sans fil
WO2016163802A1 (fr) Procédé d'exécution de cca dans un système d'accès sans fil supportant une bande sans licence, et appareil le supportant
WO2016167606A1 (fr) Procédé pour réaliser une rétroaction par un terminal dans un système de communication sans fil et appareil associé
WO2016122258A1 (fr) Procédé et équipement utilisateur de réception de signal, et procédé et station de base de réception de signal
WO2013006006A2 (fr) Procédé et appareil de transmission d'un signal dans un système de communication sans fil
WO2016108673A1 (fr) Procédé de transmission d'informations de commande de liaison montante et équipement utilisateur, et procédé de réception d'informations de commande de liaison montante et station de base
WO2014185673A1 (fr) Procédé de communications prenant en considération le type de support et appareil associé
WO2017217797A1 (fr) Procédé et appareil d'émission et de réception d'un signal sans fil dans un système de communication sans fil
WO2019031936A1 (fr) Procédé et dispositif pour transmettre/recevoir un signal radio dans un système de communication sans fil
WO2014051254A1 (fr) Procédé de transmission sur la liaison montante, et dispositif de transmission sur la liaison montante
WO2016021954A1 (fr) Procédé d'émission de signal de liaison montante et équipement d'utilisateur ainsi que procédé de réception de signal de liaison montante et station de base
WO2014137105A1 (fr) Procédé de réception d'informations de commande sur epdcch
WO2017003265A1 (fr) Procédé et dispositif pour émettre un signal dans un système de communication sans fil
WO2017014549A1 (fr) Procédé de réception d'informations de commande de liaison descendante et équipement utilisateur, et procédé de transmission d'informations de commande de liaison descendante et station de base
WO2016085295A1 (fr) Procédé et appareil pour réaliser une communication de dispositif à dispositif directe dans un système de communication sans fil prenant en charge une bande non autorisée
WO2018030813A1 (fr) Procédé et dispositif d'émission et de réception d'un signal sans fil dans un système de communication sans fil
WO2016114626A1 (fr) Procédé et dispositif de transmission et de réception de message de commande partagé dans un système d'accès sans fil prenant en charge une communication de type machine

Legal Events

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

Ref document number: 18843838

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2020507574

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 20207006926

Country of ref document: KR

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2018843838

Country of ref document: EP

Effective date: 20200310