WO2016159680A1 - Procédé de communication de machine à machine permettant une extension de couverture, appareil et système permettant de mettre en œuvre ledit procédé - Google Patents

Procédé de communication de machine à machine permettant une extension de couverture, appareil et système permettant de mettre en œuvre ledit procédé Download PDF

Info

Publication number
WO2016159680A1
WO2016159680A1 PCT/KR2016/003318 KR2016003318W WO2016159680A1 WO 2016159680 A1 WO2016159680 A1 WO 2016159680A1 KR 2016003318 W KR2016003318 W KR 2016003318W WO 2016159680 A1 WO2016159680 A1 WO 2016159680A1
Authority
WO
WIPO (PCT)
Prior art keywords
terminal
mtc
data
information
base station
Prior art date
Application number
PCT/KR2016/003318
Other languages
English (en)
Korean (ko)
Inventor
오혁준
Original Assignee
오혁준
송현용
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
Priority claimed from KR1020150169116A external-priority patent/KR20160118913A/ko
Priority claimed from US14/987,778 external-priority patent/US9510134B2/en
Priority claimed from US15/069,928 external-priority patent/US9654902B2/en
Application filed by 오혁준, 송현용 filed Critical 오혁준
Publication of WO2016159680A1 publication Critical patent/WO2016159680A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L7/00—Arrangements for synchronising receiver with transmitter

Definitions

  • the present invention relates to a method of communication of things, an apparatus and a system for performing the same, and more particularly, to a method of communication of things for coverage expansion, an apparatus and system for performing the same.
  • IoT communication terminals for example, Machine Type Communication (MTC) terminals-and low cost of IoT terminals such as MTC terminals at a low price is a key factor in implementing the Internet of Things (IoT). to be.
  • MTC Machine Type Communication
  • MTC terminals can be used for various applications, low power consumption is required, and communication for infrequent small burst transmissions is expected.
  • telecommunications terminals such as MTC terminals, such as electricity, water, and gas meters, can be deployed deep within the building and coverage improvements compared to LTE cell coverage defined previously. May be required.
  • MTC terminals are installed in the basement of a building or in a place that is insulated with metal foil or shielded by a metal window or thin walled building. For these installation reasons, the MTC terminal experiences penetration losses on the air interface than the general LTE terminal.
  • MTC terminals present in the extreme coverage scenario may have characteristics such as very low data rate, large delay tolerance, and no-mobility, so some messages and / or when communicating using the MTC terminal Channels may not be needed.
  • Techniques for improving the coverage of the MTC terminal should take into account coverage, power consumption, cell frequency efficiency, impact on standards, manufacturing cost, complexity, and the like.
  • MTC machine type communication
  • even a small frequency band width of about 1.4 MHz requires a technology that works well in the existing commercial network regardless of the current bandwidth of the base station.
  • the current MTC Machine Type Communication
  • since the data rate is about 100kbps (fixed bandwidth to 1.4MHz) there is a need for a method that can significantly expand the coverage while maintaining low power in the MTC terminal.
  • SCH shared channel
  • BCH broadcast channel
  • PDCCH Physical Downlink Control Channel
  • this single receive RF and bandwidth reduction technique will reduce downlink coverage, and further coverage improvement to compensate for this coverage loss. Skill is required.
  • E PDCCH (Enhanced) Physical Downlink Coverage supplementation for Control Channel (PHY) and Physical Downlink Shared Channel (PDSCH) is needed.
  • MTC terminals need more than 20dB of coverage extension, but since only 1.4MHz bandwidth is used and only one RF chain is limited, data reception performance is greatly reduced compared to conventional mobile communication terminals. none. Therefore, a variety of advanced technologies are required to increase the performance even in such an environment to obtain 20 dB or more of coverage.
  • RACH uplink random access channel
  • RACH which is a kind of data request signal transmitted by the terminal to the base station at any time for connection and data transmission of the base station of the terminal, serves as a start of communication initiated by all the terminals, and thus a far-away MTC terminal having an extended coverage of 20 dB or more.
  • a base station can successfully receive an RACH signal transmitted from and successfully transmit a response signal to the corresponding MTC terminal in a long distance.
  • the base station and / or the terminal can distinguish the MTC coverage extension terminal and the general mobile communication terminal in advance, it is possible to greatly increase the efficiency in MTC coverage extension communication. Therefore, a technique for distinguishing an MTC coverage extension terminal from a general terminal is also required in an RACH process in which a terminal attempts initial access.
  • system information, control information, and data excluding a master information block (MIB) using a system bandwidth of a predetermined size at the base station And transmitting at least one of the at least one of the at least one of the at least one of the at least one of the system information, the control information, and the data except for the master information block (MIB) at the base station.
  • Frequency hopping is performed using a hopping pattern and transmitted to the MTC terminal.
  • the frequency hopping pattern may be generated or determined using at least one of a cell identifier (ID), a terminal identifier (ID), a system frame number (SFN), and a subframe index.
  • the frequency hopping pattern may be transmitted to the MTC terminal using persistent scheduling.
  • a primary synchronization signal (PSS) / secondary synchronization signal (SSS) used for synchronization and a PBCH indicating system information may not perform the frequency hopping.
  • the frequency hopping may only be performed within a particular narrowband set.
  • the specific narrowband set may be set identically for uplink transmission and the downlink transmission.
  • the base station informs the IoT terminal of an available narrowband set using system information including at least one of a MIB and an SIB that are broadcasted to the IoT terminals in the network.
  • the MIB and / or SIB encoding may be encoded with a code indicating a specific number to inform the MTC of the usage information about the available narrowband set.
  • an uplink thing communication method from a MTC terminal to a base station includes at least one of control information, a random access signal, and data using a system bandwidth of a predetermined size in the MTC terminal. And transmitting to the base station, wherein at least one of the control information, a random access signal, and data is performed by performing frequency hopping using a hopping pattern between narrow bands smaller than the system bandwidth. Transmit to base station.
  • a downlink thing communication method from a base station for coverage extension to a thing communication terminal uses system bandwidth of a predetermined size.
  • the system information-the system information includes a master information block (MIB) and an SIB ( And at least one of control information and data to the MTC terminal, wherein at least one of the system information, control information and data is repeated to the MTC terminal. send.
  • the repetitive transmission may be transmitted to the MTC using fixed scheduling, but the constant scheduling may be transmitted by fixing the repetitive transmission pattern.
  • Repeated transmission of the MIB (Master Information Block) may be transmitted using one of a method of transmitting the same signal and a method of transmitting the same data but different types of signals.
  • the method of transmitting the same data but having different forms of signals may transmit the same data but with different coding.
  • the MTC terminal may be operated by being divided into a small coverage terminal and a large coverage terminal according to channel conditions.
  • Machine type communication (MTC) communication method for coverage extension uses a PRACH signal to distinguish between the MTC coverage extension terminal and the general terminal.
  • the MTC coverage extension terminal In order to distinguish the MTC coverage extension terminal and the general terminal, it may be classified with a PRACH preamble.
  • the MTC coverage extension terminal may be divided into time and frequency resource positions.
  • the MTC coverage extension terminal may be distinguished with a specific pattern indicating the MTC terminal.
  • the MTC coverage extension terminal may be distinguished with a pattern generated by combining and combining a specific pattern indicating the MTC terminal and the existing PRACH preamble.
  • a method of distinguishing an MTC coverage extension terminal from a general terminal by using a pattern generated by combining and combining a specific pattern representing an MTC terminal and an existing PRACH preamble is repeatedly transmitted as it is when the existing PRACH preamble is repeated. You can change the code values of the TDM, FDM pattern, or CDM.
  • the MTC coverage improvement terminal and the general terminal may be distinguished by combining a CDM and a repeating transmission pattern.
  • the narrowband usage information is transmitted from the thing communication terminal.
  • the system information or the downlink control channel a set of available narrowbands may be informed to MTS terminals in the network.
  • a method of communication of things performs multi-subframe scheduling during downlink frequency hopping.
  • Machine type communication (MTC) communication method for coverage expansion for achieving the object of the present invention to efficiently respond to the change caused by the difference in the transmission channel according to the coverage difference It's an adaptive way of doing things.
  • the change in the transport channel or the difference in the transport channel state experienced by the UE is based on the change of the transport channel or the difference in the transport channel state based on the PRACH, the pilot signal in the PUSCH, or the sounding signal received uplink to the base station. I can figure it out.
  • the change of the transmission channel or the difference in the state of the transmission channel encountered by the UE it is possible to adaptively operate the number of repetitive transmissions, frequency hopping patterns, and the like. The number of repetitive transmissions, frequency hopping patterns, etc.
  • the terminals that need to operate in a place such as a distance to the terminal or a basement are inferior to a general channel environment, and thus, the number of repetitive transmissions and the frequency hopping pattern may be differently operated according to the difference of the transmission channel state.
  • the required coverage level can be inferred from the estimated channel state based on the PRACH, the DMRS in the PUSCH, or the sounding signals. That is, since the number of repetitive transmissions required for the IoT terminal on the ground and the IoT terminal in the ground may be greatly different from each other, the number of repetitive transmissions, frequency hopping patterns, etc. may be changed according to the difference in the transmission channel state experienced by the IoT terminal. It can be operated differently.
  • ⁇ may be embodied in a computer program, software, firmware or hardware included in a computer-readable medium for execution by a computer or a processor.
  • Examples of computer-readable media include electronic signals (sent over a wired or wireless connection) and computer-readable storage media.
  • Examples of computer-readable storage media include read only memory (ROM), random access memory (RAM), registers, cache memory, semiconductor memory devices, internal hard disks and removable disks.
  • Optical media such as, but not limited to, magnetic media, magnetic-optical media, CD-ROM disks, and digital versatile disks (DVDs).
  • the processor associated with the software may be used to implement a radio frequency transceiver for use in a WTRU, UE, terminal, base station, RNC, or any host computer.
  • the processor includes a digital signal processor (DSP), a microprocessor, one or more microprocessors associated with the DSP core, a controller, a microcontroller, application specific integrated circuits (ASICs), a field programmable gate array. (field programmable gate array; FPGA) circuits, integrated circuits (ICs), state machines, and the like.
  • DSP digital signal processor
  • ASICs application specific integrated circuits
  • FPGA field programmable gate array
  • FIG. 1 is a schematic block diagram of an MTC terminal according to an embodiment of the present invention.
  • FIG. 2 is a schematic block diagram of an MTC communication system according to an embodiment of the present invention.
  • FIG. 3 is a conceptual diagram illustrating an example of a resource grid for one downlink slot in an LTE system.
  • FIG. 4 is a conceptual diagram illustrating a structure of a downlink subframe in an LTE system.
  • FIG. 5 shows a structure of an uplink subframe in an LTE system.
  • FIG. 6 is a conceptual diagram illustrating an example of a downlink frame structure according to an embodiment of the present invention.
  • FIG. 7 shows an example of a frequency hopping pattern according to another embodiment of the present invention.
  • FIG. 8 is a conceptual diagram illustrating a case in which a narrow band having a size of 6PRB is arranged to align with an existing legacy PRB mapping according to an embodiment of the present invention.
  • FIG. 9 is a conceptual diagram illustrating a case where a narrow band having a 5PRB size is arranged to align with an existing legacy PRB mapping according to another embodiment of the present invention.
  • FIG. 10 is a conceptual diagram for supporting a downlink narrowband terminal in an existing wideband system according to an embodiment of the present invention.
  • 11 is a conceptual diagram for supporting an uplink narrowband terminal in an existing wideband system according to an embodiment of the present invention.
  • FIG. 12 is a conceptual diagram illustrating a pattern in which frequency hopping occurs between narrow bands having a 6PRB size using an overall system bandwidth larger than a 1.4 MHz bandwidth according to another embodiment of the present invention.
  • 13 and 14 are multi for PUSCH transmission in accordance with an embodiment of the present invention is a conceptual diagram showing a sub-frame scheduling (Cross-subframe scheduling) by way of example - the sub-frame scheduling (Multi-subframe scheduling) or a cross.
  • 15 is a conceptual diagram illustrating a CRC masking method for a terminal ID in order to reduce overhead according to an embodiment of the present invention.
  • 16 exemplarily shows additional information transmitted using the reserved 10-bit of the LTE MIB.
  • FIG. 17 illustrates an example of a data transmission method for a low data rate based IoT sensor application according to another embodiment of the present invention.
  • first and second may be used to describe various components, but the components should not be limited by the terms. The terms are used only for the purpose of distinguishing one component from another.
  • the first component may be referred to as the second component, and similarly, the second component may also be referred to as the first component.
  • the terminal may be a mobile station (MS), user equipment (UE), user terminal (UT), wireless terminal, access terminal (AT), terminal, fixed or mobile subscriber unit, subscriber station (SS) Subscriber Stations, cellular telephones, wireless devices, wireless communication devices, Wireless Transmit / Receive Units (WTRUs), mobile nodes, mobiles, mobile stations, personal digital assistants (PDAs) ), Smartphone, laptop, netbook, personal computer, wireless sensor, consumer electronics (CE) or other terms.
  • Various embodiments of the terminal may be photographed such as a cellular telephone, a smart phone having a wireless communication function, a personal digital assistant (PDA) having a wireless communication function, a wireless modem, a portable computer having a wireless communication function, or a digital camera having a wireless communication function.
  • Devices wearable devices with wireless communications capabilities, gaming devices with wireless communications capabilities, music storage and playback appliances with wireless communications capabilities, Internet home appliances with wireless Internet access and browsing, as well as combinations of such functions It may include a portable unit or terminals, but is not limited thereto.
  • a base station generally refers to a fixed point for communicating with a terminal, and includes a base station, a Node-B, an eNode-B, an advanced base station (ABS), HR-BS, site controller, base transceiver system (BTS), access point (AP), or any other type of interfacing device capable of operating in a wireless environment may be included.
  • the base station may include other base stations and / or network elements (not shown), such as a base station controller (BSC), radio network controller (RNC), relay nodes, and the like. It can be part.
  • BSC base station controller
  • RNC radio network controller
  • the base station may be configured to transmit and / or receive wireless signals within a particular geographic area, which may be referred to as a cell (not shown).
  • the cell may also be divided into cell sectors.
  • a cell associated with a base station can be divided into three sectors.
  • the base station may include three transceivers, one transceiver for each sector of the cell.
  • the base station may use multiple-input multiple output (MIMO) technology, and thus may utilize multiple transceivers for each sector of the cell.
  • MIMO multiple-input multiple output
  • the MTC terminal includes a terminal for implementing M2M communication by embedding a sensor and a communication function.
  • the MTC terminal may include a Machine Type Communication (MTC) terminal, a narrowband LTE (Narrow band LTE) terminal, and a Cellular IoT (CIoT) terminal.
  • MTC Machine Type Communication
  • narrowband LTE Near band LTE
  • CCIoT Cellular IoT
  • FIG. 3 is a conceptual diagram illustrating an example of a resource grid for one downlink slot in an LTE system.
  • a downlink slot includes a plurality of OFDM symbols in the time domain and N RB resource blocks (RBs) in the frequency domain.
  • the number NRB of resource blocks included in the downlink slot may depend on the downlink transmission bandwidth set in the cell. For example, in an LTE system, the NRB may have any value between 6 and 110 depending on the bandwidth.
  • One resource block may include a plurality of subcarriers in the frequency domain.
  • the structure of the uplink slot may also be the same as that of the downlink slot.
  • Each element on the resource grid is called a resource element.
  • Resource elements on the resource grid may be identified by an index pair (k, l) in the slot.
  • one resource block includes 7 X 12 resource elements including 7 OFDM symbols in a time domain and 12 subcarriers in a frequency domain, but the number and subcarriers of an OFDM symbol in one resource block are illustrated.
  • the number of is not limited thereto.
  • the number of OFDM symbols and the number of subcarriers can be variously changed according to the length of a cyclic prefix (CP), frequency spacing, and the like.
  • CP cyclic prefix
  • the number of subcarriers in one OFDM symbol may be selected and used among 128, 256, 512, 1024, 1536 and 2048.
  • the number of subcarriers in one OFDM symbol may use a number smaller than 128, for example, 64, 32, 16, 8, when using a narrower bandwidth than the present for MTC. Can be adjusted according to the bandwidth.
  • the bandwidth of the LTE system can be very flexible and can vary from about 1 MHz to 20 MHz. If a narrower band is used for the IoT, the bandwidth of the LTE system can be used even below 1 MHz.
  • FIG. 4 is a conceptual diagram illustrating a structure of a downlink subframe in an LTE system.
  • one downlink subframe may include two slots in a time domain, and each slot may include seven OFDM symbols in a normal CP.
  • the leading up to 3 OFDM symbols (up to 4 OFDM symbols for 1.4Mhz bandwidth) of the first slot in the subframe are the control regions to which control channels are allocated and the remaining OFDM symbols are the physical downlink shared channel (PDSCH). May be a data area to be allocated.
  • PDSCH physical downlink shared channel
  • the PDCCH includes resource allocation and transmission format of downlink-shared channel (DL-SCH), resource allocation information of uplink shared channel (UL-SCH), paging information on PCH, system information on DL-SCH, and random access transmitted on PDSCH. Resource allocation of higher layer control messages such as responses, sets of transmit power control commands for individual UEs in any UE group, activation of voice over internet protocol (VoIP), and the like.
  • a plurality of PDCCHs may be transmitted in the control region, and the terminal may monitor the plurality of PDCCHs.
  • the PDCCH may be transmitted on an aggregation of one or several consecutive control channel elements (CCEs).
  • CCEs control channel elements
  • CCE is a logical allocation unit used to provide a PDCCH with a coding rate according to a state of a radio channel.
  • the CCE corresponds to a plurality of resource element groups.
  • the format of the PDCCH and the number of possible bits of the PDCCH may be determined according to the correlation between the number of CCEs and the coding rate provided by the CCEs.
  • the base station determines the PDCCH format according to the DCI to be sent to the terminal, and attaches a cyclic redundancy check (CRC) to the control information.
  • CRC cyclic redundancy check
  • RNTI a unique radio network temporary identifier
  • the PDCCH is for a specific terminal, a unique identifier of the terminal, for example, a cell-RNTI (C-RNTI) may be masked to the CRC.
  • C-RNTI cell-RNTI
  • a paging indication identifier for example, PRNTI (paging-RNTI) may be masked to the CRC.
  • SI-RNTI system information-RNTI
  • RA-RNTI random access-RNTI
  • FIG. 5 shows a structure of an uplink subframe in an LTE system.
  • the uplink subframe may be divided into a control region and a data region in the frequency domain.
  • the control region may be allocated a physical uplink control channel (PUCCH) for transmitting uplink control information.
  • the data region may be allocated a physical uplink shared channel (PUSCH) for transmitting data.
  • the terminal When indicated by the higher layer, the terminal may support simultaneous transmission of the PUSCH and the PUCCH.
  • PUCCH for one UE may be allocated as an RB pair in a subframe.
  • Resource blocks belonging to a resource block pair occupy different subcarriers in each of a first slot and a second slot.
  • the frequency occupied by the resource block belonging to the resource block pair allocated to the PUCCH may be changed based on a slot boundary. This is called that the RB pair allocated to the PUCCH is frequency-hopped at the slot boundary.
  • the terminal may obtain a frequency diversity gain by transmitting uplink control information through different subcarriers over time.
  • m is a location index indicating a logical frequency domain location of a resource block pair allocated to a PUCCH in a subframe.
  • the uplink control information transmitted on the PUCCH includes a hybrid automatic repeat request (HARQ) acknowledgment (ACK) / non-acknowledgement (NACK), a channel quality indicator (CQI) indicating a downlink channel state, and an uplink radio resource allocation request. (scheduling request) and the like.
  • HARQ hybrid automatic repeat request
  • ACK acknowledgment
  • NACK non-acknowledgement
  • CQI channel quality indicator
  • the PUSCH may be mapped to the UL-SCH which is a transport channel.
  • the uplink data transmitted on the PUSCH may be a transport block which is a data block for the UL-SCH transmitted during the TTI.
  • the transport block may be user information.
  • the uplink data may be multiplexed data.
  • the multiplexed data may be a multiplexed transport block and control information for the UL-SCH.
  • the control information multiplexed on the data may include a CQI, a precoding matrix indicator (PMI), a HARQ, a rank indicator (RI), and the like.
  • the uplink data may consist of control information only.
  • the MTC terminal needs more than 20 dB of coverage extension, but only 1,4 MHz bandwidth should be used, and only one reception RF chain may be used, and data reception performance is significantly higher than that of the conventional mobile communication terminal. There is no choice but to fall.
  • the maximum bandwidth for a single carrier supported by a normal LTE terminal is 20 MHz.
  • One of the technologies that can reduce the cost of the MTC terminal is to reduce the maximum bandwidth supported by the terminal to a bandwidth less than 20MHz (for example, 5Mhz, 3Mhz, 1.4Mhz, 200Khz, etc.).
  • Techniques for reducing the maximum bandwidth that these terminals can support may be applied to downlink and / or uplink, RF components and / or baseband components, data and / or control channels.
  • the frequency location of the reduced bandwidth (data channel and / or control channel) less than 20 MHz may be fixed at the center of the carrier bandwidth, may be fixed at both ends of the carrier band, or It may be fixed only at one end, or may be changed for each MTC terminal in a semi-statically, dynamically, or a predetermined pattern.
  • the location on the frequency axis of the reduced bandwidth (narrowband) less than 20 MHz used for the data channel and / or control channel may be aligned in RB units.
  • the location on the frequency axis of the reduced bandwidth smaller than 20 MHz used for the data channel and / or control channel is 6-PRB for 1.4 MHz, so for example, for 10 MHz bandwidth, the total number of PRBs is 50 It is not divided by 6, leaving an extra PRB.
  • the position on the frequency axis of the extra PRB of the reduced bandwidth (narrowband) smaller than 20 MHz used for the data channel and / or control channel is left. You can leave the center of the carrier bandwidth, you can leave both ends of the carrier band, or you can leave only one end of the carrier band.
  • the overall system bandwidth can be 20 MHz, 10 Hz, 5 MHz or 3 MHz, for example.
  • the reduced 1.4 MHz bandwidth may correspond to, for example, 6 physical resource blocks (PRBs).
  • the reduced 200KHz or 180KHz bandwidth may correspond to 1 RB.
  • the downlink does not apply a frequency hopping separately because it has the same effect as a frequency hopping by distributing and allocating resources in the frequency domain through frequency distributed scheduling (FDS) scheduling.
  • Frequency hopping through an uplink physical layer data transmission channel (for example, a PUSCH (Physical Uplink Shared Channel)) is applied to only a link. That is, in case of legacy LTE, frequency hopping is not applied separately for downlink data transmission, and frequency hopping through an uplink physical layer data transmission channel (for example, PUSCH (Physical Uplink Shared Channel)) only for uplink data transmission.
  • PUSCH Physical Uplink Shared Channel
  • FDS scheduling can be used only when the entire bandwidth is wide.
  • bandwidth is limited to 1.4 MHz or 200 KHz or 180 KHz, frequency hopping of the entire (data channel and / or control channel) is performed. Method is required.
  • the hopping pattern may be periodic or aperiodic. That is, the hopping pattern may not be periodic when data transmission is completed before the period is repeated.
  • the MTC terminal transmits data using the total system bandwidth larger than the 1.4 MHz bandwidth, but performs frequency hopping of the 1.4 MHz band using a periodic hopping pattern such as TSTD (Time Switched Transmit Diversity). Data can be transferred.
  • the hopping pattern may be periodic or aperiodic. That is, the hopping pattern may not be periodic when data transmission is completed before the period is repeated.
  • the data may be transmitted to the terminal through frequency hopping through the downlink physical layer data transmission channel PDSCH.
  • the data may be transmitted to a base station by frequency hopping through an uplink physical layer data transmission channel (for example, a physical uplink shared channel (PUSCH)).
  • PUSCH physical uplink shared channel
  • frequency hopping may be performed using an overall system bandwidth larger than 1.4 MHz bandwidth.
  • system information-for example, SIB (System Information Block)-, control information-for example, PDCCH, (E) PDCCH- the entire system larger than 1.4MHz bandwidth Bandwidth can be used to transmit by frequency hopping.
  • PSS Primary Synchronization Signal
  • SSS Secondary Synchronization Signal
  • FIG. 6 is a conceptual diagram illustrating an example of a downlink frame structure according to an embodiment of the present invention.
  • One frame may consist of ten subframes having a length of 1ms. Each frame may be identified by a system frame number (SFN). SFN can be used to control various transmission periods that may have periods longer than one frame, such as paging and sleep-mode periods or channel status reporting periods.
  • SFN system frame number
  • FIG. 6 shows an example in which PBCH, PCFICH, PDCCH, and PDSCH are mapped to a downlink frame.
  • a PDCCH is allocated to transmit a downlink control signal for controlling a terminal.
  • the region where the PDCCHs of the plurality of terminals are mapped may be referred to as a PDCCH region or a control region.
  • the PCFICH carries information on the number of OFDM symbols used for the allocation of the PDCCH in the subframe.
  • Information on the number of OFDM symbols to which the PDCCH is allocated is called a control format indicator (CFI). All terminals in the cell must search the area to which the PDCCH is allocated, and thus CIF can be set to a cell-specific value.
  • CFI control format indicator
  • All terminals in the cell must search the area to which the PDCCH is allocated, and thus CIF can be set to a cell-specific value.
  • the control region to which the PDCCH is allocated is allocated to the foremost OFDM symbols of the downlink subframe, and the PDCCH may be allocated to up to three OFDM symbols.
  • CIF is set to 3, so that the PDCCH is allocated within the three OFDM symbols in the previous subframe.
  • the UE detects its own PDCCH in the control region and may detect its PDSCH through the PDCCH detected in the control region.
  • the PCFICH may not be transmitted every TTI, but a fixed control format indicator (CFI) may be used or only a specific TTI may be used.
  • CFI control format indicator
  • the value may be promised or transmitted through MIB or SIB.
  • an e-PDCCH (enhanced PDCCH) may be introduced as a new control channel.
  • the e-PDCCH may be allocated to the data region instead of the existing control region to which the PDCCH is allocated.
  • the e-PDCCH is defined, it is possible to transmit a control signal for each UE, and solve a problem that the existing PDCCH region may be insufficient.
  • a hopping pattern (FH1A, FH2A, FH3A, ... or FH1B, FH2B, FH3B,... Frequency hopping in the 1.4 MHz band using ..) to downlink data, system information (e.g., System Information Block), control information (e.g., PDCCH, e-PDCCH).
  • system information e.g., System Information Block
  • control information e.g., PDCCH, e-PDCCH
  • the hopping pattern for the SIB may be implicitly / explicitly obtained by using information included in the MIB and a cell ID obtained during synchronization.
  • the data may be transmitted by frequency hopping through the downlink physical layer data transmission channel PDSCH, unlike the existing LTE.
  • the data may be transmitted by frequency hopping through an uplink physical layer data transmission channel (for example, (PUSCH (Physical Uplink Shared Channel)).
  • PUSCH Physical Uplink Shared Channel
  • the bandwidth is larger than 1.4 MHz.
  • Frequency hopping may be performed using the entire system bandwidth.
  • control information for example, PUCCH
  • a random access signal for example, Even when transmitting PRACH, etc.
  • frequency hopping may be performed using the entire system bandwidth larger than the 1.4 MHz bandwidth.
  • the MTC terminal may perform communication with a base station using a narrow band.
  • the narrow band is a minimum band used for transmitting information, signals, and data between the MTC terminal and the base station and may be used in units of PRBs or subcarriers.
  • frequency hopping between subcarriers within a narrow band may be performed, or inter-band narrow frequency hopping may be performed in units of narrow bands.
  • PSS Primary Synchronization Signal
  • SSS Secondary Synchronization Signal
  • PBCH Physical Broadcasting Channel
  • PSS Primary Synchronization Signal
  • SSS Secondary Synchronization Signal
  • PBCH Physical Broadcasting Channel
  • the time may be longer. For example, in order to transmit existing 6-PRB data divided into 1-PRB, data must be transmitted for 6 TTIs.
  • a narrow band according to an embodiment of the present invention may be defined in units of PRBs.
  • the narrow band may continuously define the position of the PRB, but may use adjacent bands based on the center 72 subcarriers. It may or may not be symmetric about the center. It can be set to extend left and right even if it is not symmetrical or not symmetrical from the center until PRB which is not defined as narrow band.
  • the narrowband may be assigned from the low frequency or the high frequency, and may be assigned in the left direction and the right direction with the center as the starting point.
  • the narrowband may be ordered in the form of a circular loop in a clockwise or counterclockwise direction starting from the left or the right with respect to the center.
  • the narrowband defined within the range of 72 subcarriers excluding the center DC is defined as the central band, and the narrowest band on the left side of the middle band is the lowest narrowband and the rightmost band on the center narrowband.
  • the narrowband in can be defined as the highest narrowband.
  • the offset may be set to align or link the uplink narrowband with the legacy PUCCH and / or PRACH.
  • the position of the uplink narrowband may be determined by the legacy PUCCH and / or PRACH + offset.
  • a part of the system bandwidth for communication between the MTC terminal and the base station may be set instead of using the entire system bandwidth for the communication between the MTC terminal and the base station.
  • the narrowband may be defined as a set of contiguous physical resource blocks (PRBs).
  • a narrow band set should be set identically for uplink transmission and downlink transmission. That is, in the case of the TDD transmission scheme, the uplink transmission and the downlink transmission should be set to have the same set of subcarriers.
  • a plurality of narrow bands may be set.
  • the narrowbands may be set so as not to overlap between narrowbands in order to reduce interference between MTC terminals.
  • the narrow band may be set as a function of the system bandwidth. In reality, in the presence of a large number of terminals, it may be difficult to determine a set of narrow bands so that they do not completely overlap 100% between each narrow band. Some improvement can be made. Therefore, even if a narrow set of overlapping bands is defined, the frequency hopping pattern can be determined not to overlap.
  • the downlink narrow band that is completely overlapped within the center 72 subcarriers (excluding the system DC) range may be defined as a center narrow band.
  • a broadcasting signal that all MTC terminals should receive may be transmitted.
  • the central narrowband may be used for frequency hopping between narrowbands.
  • the central narrowband may be used for frequency hopping in downlink or uplink data transmission. For example, frequency hopping may be performed using the central narrow band in downlink PDSCH and / or PDCCH transmission.
  • FIGS. 10 and 11 will be described in detail.
  • a plurality of non-overlapped downlink narrow bands may be specified for the system bandwidth.
  • a non-overlapped downlink narrowband of 3 MHz may be defined for one cell.
  • the number of usable narrowbands and the number of subbands can be determined based on the system bandwidth of the cell.
  • the number of narrow bands that can be set can be determined based on the system bandwidth of the cell.
  • the total bandwidth used by the narrow band (the number of narrow bands x the bandwidth of one narrow band) may be 1/2 or less of the system bandwidth.
  • some PRBs in the system may not be included in any narrowband established.
  • Some of the bands not used exclusively for the MTC can be separated from the narrow band of the MTC. It is possible to transmit messages, signals and data of a specific downlink or uplink using an edge of the system bandwidth or a central narrowband.
  • narrowbands may overlap with the central narrowband at least for system bandwidth.
  • the system bandwidth is 3 MHz
  • other narrow bands may be implemented to overlap with the central narrow band.
  • a narrowband not adjacent to the central narrowband may have a size of 6PRB.
  • FIG. 7 shows an example of a frequency hopping pattern according to another embodiment of the present invention.
  • the horizontal axis is the time axis
  • the vertical axis is the frequency axis
  • ⁇ may be data or system information, paging, etc. for MTC communication.
  • ⁇ may be 6 PRBs (ie, 1.4 MHz), or may be 1 PRB.
  • the hopping may be performed in 1.4MHz units, or in 200Khz units, or by splitting the 1.4MHz bandwidth to hop within the entire 1.4MHz.
  • FIG. 7 illustrates an example of a frequency hopping pattern when data and / or system information and a paging signal are transmitted between a base station and an MTC terminal through downlink or uplink.
  • the frequency hopping pattern is illustrated in FIG. 13. Without limitation, various hopping patterns may be used.
  • frequency hopping may be performed to transmit data and / or system information and paging using the total system bandwidth larger than the 1.4 MHz bandwidth.
  • a transmission diversity effect may be obtained.
  • FIG. 8 is a conceptual diagram illustrating a case in which a narrow band having a size of 6PRB is arranged to align with an existing legacy PRB mapping according to an embodiment of the present invention.
  • a narrow band has a size of 6 PRBs.
  • the center frequency of the narrow band may be arranged to match the center frequency of the system bandwidth, and the narrow band may be aligned with the existing legacy PRB mapping.
  • the center frequency of the narrow band does not coincide with the center frequency of the system bandwidth as shown in FIG. 5, and the narrow band may be arranged to align with the existing legacy PRB mapping. .
  • FIG. 9 is a conceptual diagram illustrating a case where a narrow band having a 5PRB size is arranged to align with an existing legacy PRB mapping according to another embodiment of the present invention.
  • the narrow band has a size of 5 PRBs, and the center frequency of the narrow band corresponds to the center frequency of the system bandwidth.
  • Narrow bands can be arranged to align with existing legacy PRB mapping.
  • the center frequency of the narrow band does not coincide with the center frequency of the system bandwidth, and may be arranged such that the narrow band is aligned with the existing legacy PRB mapping.
  • a narrow band according to embodiments of the present invention may have a size smaller than 6 PRBs, for example, 5 PRBs, 4 PRBs, 3 PRBs, and a size larger than 6 PRBs, for example. It may have 7 PRBs, 8 PRBs, 9 PRBs or 12 PRBs that are twice the size, 18 PRBs that are three times the size.
  • Narrow band size may be fixedly used in one of a plurality of sizes selectively, or may be adaptively used depending on the situation. For example, if the narrowband size is made smaller, the number of narrowbands increases, so that a plurality of MTC terminals may be supported or more hoppable bands may be provided in frequency hopping. Increasing the narrow band size can increase the transmission data rate.
  • FIG. 10 is a conceptual diagram for supporting a downlink narrowband terminal in an existing wideband system according to an embodiment of the present invention.
  • FIG. 10 illustrates one subframe, eg, 1 ms, of a downlink frequency of a legacy legacy terminal.
  • Each cell may be implemented to support an existing legacy terminal and an MTC terminal according to an embodiment of the present invention.
  • PSS / SSS, MIB, and SIB are located in a center 6PRB, and in the case of an MTC terminal according to an embodiment of the present invention, a narrow band ) May be set to be aligned with the center 6PRB (including PSS / SSS, MIB, and SIB) of the downlink frequency of the legacy legacy terminal, or may be retuned to work with an offset. have.
  • the downlink narrow band may be re-tuned to a new frequency different from the center 6PRB frequency position. Specifically, the location of the new downlink narrowband region may be set to the downlink center frequency + offset of the legacy terminal.
  • the downlink narrow band region may include a narrow band control channel based on an E-PDCCH, for example, the downlink narrow band ( N-band region may include E-PDCCH and PDSCH.
  • the downlink narrow band region is illustrated as one narrow band region in FIG. 10 but may be configured as a plurality of narrow band regions.
  • 11 is a conceptual diagram for supporting an uplink narrowband terminal in an existing wideband system according to an embodiment of the present invention.
  • FIG. 11 illustrates one subframe of an uplink frequency of a legacy legacy terminal, for example, 1 ms.
  • Each cell may be implemented to support an existing legacy terminal and an MTC terminal according to an embodiment of the present invention.
  • a PUSCH is located in a center 6PRB, and in the case of an MTC terminal according to an embodiment of the present invention, a narrow band is a legacy legacy terminal.
  • the offset may be set to be aligned with the center 6PRB (including PUSCH) of the uplink frequency or re-tuned to work with the uplink frequency.
  • the uplink narrow band may be retuned to a new frequency different from the center 6PRB frequency position. Specifically, the position of the new uplink narrowband region may be set to an uplink center frequency + offset of the legacy terminal.
  • the uplink narrow band region may include, for example, a PUSCH and a PUCCH.
  • the uplink narrow band region may be set to one narrow band region or may be set to a plurality of narrow band regions.
  • the uplink narrowband region may be set in 1-RB units or sub-carrier units.
  • FIG. 12 is a conceptual diagram illustrating a pattern in which frequency hopping occurs between narrow bands having a size of 6PRB using an overall system bandwidth greater than a 1.4 MHz bandwidth according to another embodiment of the present invention.
  • a plurality of narrowbands to be used may be preset, a PRB index may be allocated to each narrowband, and the location of the narrowband to be used by the MTC terminal may be informed using the PRB index.
  • the narrow bands NB1, NB2, ..., NB8 have sizes of 6 PRBs, and eight narrow bands NB1, NB2, ..., NB8 We have PRB indexes 0-5, 6-11, ..., 42-47 for each.
  • eight narrow bands NB1, NB2, NB3, NB4, NB5, NB6, NB7, and NB8 are NB6, NB5, NB8, NB7, NB1, It has NB2, NB4, NB3 hopping pattern.
  • user information may be used for frequency hopping in uplink
  • system information may be used for frequency hopping in downlink.
  • the frequency hopping pattern may directly or indirectly form a base station ID and / or a terminal ID. It can be generated or determined by using, and control information or resources can be allocated by using a base station ID (or cell ID) and / or a terminal ID directly or indirectly.
  • Each hopping pattern is generated as a function of base station ID in order to prevent collision between hopping patterns between base stations and hopping patterns by directly or indirectly utilizing terminal IDs to prevent hopping patterns between multiple MTC terminals in the same base station.
  • Create The hopping pattern is a pattern that determines which frequency band (PRB unit or narrow band unit) is to be transmitted for each time unit performing hopping in a two-dimensional pattern of time and frequency. Therefore, in order to prevent hopping patterns of different base stations from each other, the hopping frequency bands used at the same time must be different according to the base station IDs.
  • This sequence is orthogonal or quasi-orthogonal to minimize the possibility of collision of the hopping pattern.
  • the terminal ID is used to minimize the possibility of collision of the hopping pattern between the terminals in the same base station. Even if some collisions of the hopping patterns occur, data may be restored by gains due to repetitive transmission, and thus only the mutually orthogonal hopping patterns are not used.
  • a frequency hopping pattern may be determined or generated with a base station ID (or cell ID) and / or SFN.
  • SFN is an important parameter exchanged between the base station and the terminal for time synchronization.
  • the base station may change the start, stop, end and period of hopping patterns, hopping frequency band sets, and hopping time units using or using the SFN.
  • the hopping time unit can be operated smaller than the frame unit as a slot or subframe unit.
  • the base station ID may include a Cell ID.
  • the terminal ID may include, for example, an International Mobile Subscriber Identity (IMSI), a Temporary Mobile Subscriber Identity (TMSI), a Globally Unique Temporary Identifier (GURI), or a Radio Network Temporary Identifier (RNTI).
  • IMSI International Mobile Subscriber Identity
  • TMSI Temporary Mobile Subscriber Identity
  • GURI Globally Unique Temporary Identifier
  • RNTI Radio Network Temporary Identifier
  • a method of generating a hopping pattern by indirectly using a base station ID and / or a terminal ID includes generating the first specific sequence with the corresponding base station ID and / or the terminal IDs first, and then generating the generated first specific sequence.
  • the final hopping pattern is defined and used through the secondary deformation. Secondary modifications may include combinations with other hopping patterns, different precoding applications depending on frequency or time, scrambling or cyclic shifts.
  • IMSI is a very important information for security, so when the IMSI is used, the method of generating a hopping pattern by allowing the UE to determine the hopping pattern on its own without directly exchanging IMSI is also indirectly used to generate the hopping pattern. Belongs.
  • the entity that actually generates the hopping pattern and transmits the signal may be a base station in downlink and an uplink in terminal.
  • Information about the hopping pattern may be exchanged as control information (signaling) between the base station and the terminal.
  • the mutual IDs are known to each other so that the information about the hopping pattern itself may not be exchanged. Accordingly, by adding the frequency hopping information through MIB, SIB, or PDCCH / EPDCCH, only the frequency hopping may be notified to reduce the overhead caused by exchanging information about the frequency hopping pattern.
  • 15 is a conceptual diagram illustrating a CRC masking method for a terminal ID in order to reduce overhead according to an embodiment of the present invention.
  • the terminal data is not transmitted by adding the UE ID to the terminal data.
  • the MTC terminal multiplies its terminal ID. If the terminal ID is correct, CRC error does not occur when CRC masking, and if the terminal ID is incorrect, CRC error is generated when CRC masking, thereby reducing overhead by not transmitting the terminal ID. That is, in the case of MTC communication according to an embodiment of the present invention, for example, when the CRC masking method described above is applied to a broadcast channel, the MTC is partially used by using resources of a broadcast channel carrying information common to all terminals.
  • the UE instead of transmitting all the N bits of data as in legacy LTE, the UE provides only limited resource allocation information by using data of bits smaller than N. By enabling transmission within a resource, MTC communication is possible while reducing overhead.
  • MIB MTC system information
  • MTC-MIB MTC-Master Information Block
  • MTC-SIB MTC-System Information Block
  • the Master Information Block is transmitted every 40 ms through the PBCH at a transmission time interval (TTI), which consists of four OFDM symbols located on 72 center subcarriers in each corresponding frame. Mapped.
  • TTI transmission time interval
  • 16 exemplarily shows additional information transmitted using the reserved 10-bit of the LTE MIB.
  • additional information transmitted using the reserved 10-bit may be, for example,
  • the CFI indicates the number of OFDM symbols used to transmit control channels (PDCCH, PHICH) in each subframe
  • the PCFICH indicates the size of the control region as the number of OFDM symbols. Tell me directly or indirectly if this starts.
  • persistent scheduling may improve performance by reducing overhead (or by allocating resources), for example, by minimizing (or allocating resources) control signals for scheduling when transmitting a specific pattern (repetitive pattern or frequency hopping pattern).
  • the fixed scheduling is, for example, a method of fixing a specific pattern and transmitting it periodically or aperiodically, a method of notifying the pattern first and continuing to transmit the pattern, and a set of several patterns ( and a method of transmitting a pattern selected from the set of patterns periodically or aperiodically in advance.
  • the frequency hopping on / off (1021), the information about the repetition pattern (1023) is a specific frequency hopping pattern group or a specific repeating pattern group to be used by the base station using the MIB or SIB You can also send
  • Information sent to the MIB can also be sent in the SIB. Therefore, transmission of bits related to persistent scheduling may be performed in SIB. However, important information with high priority may be transmitted through the MIB. Alternatively, information necessary for decoding the SIB may be transmitted through the MIB.
  • Information on whether 1025 uses persistent scheduling may not be transmitted through a MIB, SIB, or a specific channel. That is, instead of transmitting 1025 information on whether to use persistent scheduling through a MIB, SIB, or a specific channel, by simply using persistent scheduling that transmits a fixed location of a resource. It is possible to reduce signaling overhead and to enable stable communication. At this time, a frequency hopping pattern, a repetitive transmission pattern, and the like can also be used in a permanent manner.
  • a fixed scheduling persistent scheduling
  • the transmission pattern itself such as a pattern, can also be fixed to reduce overhead.
  • the MTC terminal receives such system information, and has a system function by defining a specific function in the standard that receives an additional terminal ID such as RNTI, GUTI, IMSI, TMSI of the MTC terminal as input.
  • the base station may transmit the system information (MIB or SIB) including the direct ID information of the specific MTC terminal.
  • the DRX cycle may be determined by substituting the IMSI value of the MTC terminal itself in the SFN (System Frame Number) transmitted from the base station to the MIB and SIB1.
  • the MTC terminal may be configured to recognize a system frame number (SFN) by receiving the MIB and SIB1 from the base station, and set the DRX cycle parameter by applying the IMSI value of the MTC terminal to the SFN.
  • SFN system frame number
  • the DRX cycle is determined as described above, its frequency hopping pattern or repetitive transmission pattern may be determined in the same manner as described above.
  • MIB MTC system information
  • MTC machine type communication
  • system information for MTC communication such as MTC-MIB / MTC-SIB is separately transmitted.
  • the MIB system information is preferably transmitted repeatedly to improve performance.
  • the coverage extension is required more than 20dB, but only bandwidth of 1,4MHz should be used, and if one receiving RF chain is used, the data reception performance is inevitably deteriorated compared to the conventional mobile communication terminal. Therefore, there is a need for a variety of advanced technologies that can increase the performance even in this environment to achieve 20dB or more of coverage. These methods include a method for greatly improving SNR through repetitive transmission and a method for securing diversity gain by frequency hopping the 1.4 MHz band for the entire system band.
  • this repetitive transmission has a problem of increasing power consumption, so the number of repetitive transmissions should be minimized whenever possible. Therefore, it should be used with additional performance improvement techniques such as frequency hopping and beamforming.
  • the band of 1,4 MHz is fixed to the center frequency of each frame as described above, and thus it is impossible to use the frequency hopping technique. Therefore, we have to rely on repetitive transmission.
  • repeated transmission includes a method of transmitting the same signal and a method of transmitting the same data but having different forms of signals, for example, different coding.
  • data, and control information the same information is transmitted but different signal types, for example, different codings, can result in a precoding diversity effect.
  • the same information is transmitted, but the coding is differently transmitted to 1, 1, 1, 1, 1, .. once, 1, -1, Can be sent in the form 1, -1, ...
  • the repetition transmission method for the MIB may be selected from the following three repetition methods.
  • the base station repeatedly transmits the MIB at a predetermined period (for example, 40 m).
  • the base station dynamically determines whether to repeatedly transmit the MIB every predetermined period (for example, 40 ms).
  • the base station repeatedly transmits the MIB according to the pattern.
  • the pattern may be composed of predefined periods.
  • the pattern may consist of a plurality of 40 ms or predefined time intervals.
  • Repeated transmission of system information or data other than the MIB includes a method of transmitting the same signal and a method of transmitting the same data but different signals.
  • the repetition transmission method for system information or data other than the MIB may be selected from the following three repetition methods.
  • the base station repeatedly transmits system information or data other than the MIB at a predetermined period (for example, 40 m).
  • the base station dynamically determines whether to repeatedly transmit system information or data other than the MIB every predetermined period (for example, 40 ms).
  • the base station repeatedly transmits system information or data other than the MIB according to the pattern.
  • the pattern may be composed of predefined periods.
  • the pattern may consist of a plurality of 40 ms or predefined time intervals.
  • the MTC communication may not only repeatedly transmit the MIB but also perform bundling that repetitions or aggregates and transmits control information including virtually all data or system information, for example, a system information block (SIB).
  • SIB system information block
  • TTI bundling is also a kind of repetition technique. The only difference is that in case of TTI bundling, repetitive transmission is performed on consecutive subframes. Coverage expansion can be achieved by using the TTI bundling technique for all data or system information. Bundling is a kind of repetitive transmission, but it is different from general repetitive transmission. In applying HARQ, it is possible to send data of the next TTI only when ACK is received. However, when NACK is received, it is not possible to send new data until it is properly received. In situations where the bandwidth is so narrow that even a lot of data needs to be sent repeatedly, this operation can take too much time to send data, which can also affect internal buffer control. Therefore, bundling technology is to bundle and send data corresponding to several TTIs to be sent at once.
  • the MTC repetitive transmission technique according to another embodiment of the present invention may perform repetitive transmission in downlink.
  • the downlink will be described as an example.
  • the MTC repetitive transmission technique can adaptively adjust the constraints upon frequency hopping according to channel conditions and / or data characteristics / personality.
  • the MTC repetitive transmission technique adaptively adjusts a hopping bandwidth, a prohibition band, a prohibition time / pause time, and a hopping period pattern during frequency hopping according to channel conditions and / or data characteristics / personality. Or variable. That is, the frequency hopping pattern can be changed according to the channel situation (confirmed in the standard conference), and specifically, the MTC terminal is divided into small and large coverage terminals for coverage extension according to the channel situation. can do.
  • MTC communication The further the distance from the base station, the weaker the signal strength, the more difficult communication is.
  • One of the purposes of MTC communication is to extend the communication range by 20 dB, and to enable MTC communication even in a place where the strength of radio waves is 20 dB smaller than the existing LTE.
  • the intensity of the radio wave decreases, the SNR may be lowered, and communication may not be possible because the SNR may not be met.
  • the intensity of the radio wave does not fall only when it is far away from the base station, but in the case of an underground terminal, a metal-closed space such as an iron gate, underwater, etc., as in the case of the IoT terminal used as a sensor, the strength of the radio wave is close even if the distance from the base station is close. Will fall significantly.
  • the MTC terminal can register with a desired base station. Therefore, in order to cope with such 20dB propagation loss, a method for improving SNR of 20dB or more is required.
  • One of the methods is the aforementioned repetition transmission technique. However, if a lot of repetition transmissions are performed, the data rate decreases and the transmission time takes a long time, so it is not good for power consumption and also takes up resources. Therefore, the number of repetition transmissions is reduced as much as possible. There is a need.
  • the MTC terminal is largely small and large coverage terminals according to a loss amount of a predetermined propagation intensity (for example, 10 dB, 12 dB, 13 dB, 14 dB, 15 dB, etc.) (or according to the SNR).
  • a predetermined propagation intensity for example, 10 dB, 12 dB, 13 dB, 14 dB, 15 dB, etc.
  • the data rate is reduced by reducing the number of repetition transmissions when the strength of the radio wave does not drop significantly or when the loss of the radio wave intensity does not become as large as 20 dB.
  • the MTC repetitive transmission technique may adaptively adjust the frequency hopping pattern according to channel conditions and / or data characteristics / personality.
  • the MTC repetitive transmission technique may adaptively adjust or vary the frequency hopping range according to channel conditions and / or data characteristics / personality.
  • the MTC repetitive transmission technique may adaptively adjust the frequency hopping bandwidth according to channel conditions and / or data characteristics / personality.
  • Frequency hopping patterns may be used by selectively selecting specific bands depending on channel conditions and / or data characteristics / personality. If the channel state of a particular frequency band is not good, the frequency band can be implemented not to be used. When the channel state of a specific frequency band is good, the frequency hopping may be implemented using only the frequency band.
  • a guard band or a prohibition period may be adaptively adjusted according to channel conditions and / or data characteristics / personality. That is, the frequency hopping pattern may be used by designating a specific band as a prohibition band according to the channel state or by designating a specific time as the prohibition time according to the channel state.
  • the MTC repetitive transmission technique may adaptively adjust the frequency hopping period according to channel conditions and / or data characteristics / personality.
  • the MTC repetitive transmission technique may adaptively adjust the length of the frequency hopping pattern according to channel conditions and / or data characteristics / personality.
  • the MTC repetitive transmission technique may adaptively adjust the frequency hopping pattern repetition number according to channel conditions and / or data characteristics / personality.
  • the MTC repetitive transmission technique may adaptively adjust the frequency hopping pattern repetition number according to channel conditions and / or data characteristics / personality.
  • frequency hopping may not be performed. In this case, information on whether frequency hopping is used or not may be transmitted from the base station to the MTC terminal.
  • the MTC repetitive transmission technique may adaptively change the hopping pattern according to the importance of the data and the characteristics / nature of the data. For example, important data such as MIB, SIB, control information, 119 emergency data is more important than general data, in this case, the diversity gain is increased by increasing the number (or frequency) of hopping pattern repetition, thereby reducing the reception error. It can improve performance. Alternatively, it may be difficult to inform the hopping pattern of such important data, so that frequency hopping may be implemented.
  • the MTC repetitive transmission technique may adaptively change the hopping pattern according to the amount of data. Frequency hopping may be slow when there is a lot of transmission data.
  • the frequency hopping bandwidth may be 6PRB, 5PRB, 4PRB, 3PRB, 2PRB, or 1PRB depending on the amount of transmitted data.
  • the prohibition time, the prohibition band, the prohibition bandwidth, the frequency hopping start time, the frequency hopping end time, and the like may inform the MTC terminal from the base station.
  • MTC repetitive transmission technology can be applied to paging, SIB, RAR.
  • the MTC repetitive transmission technique according to another embodiment of the present invention can be implemented to use a predefined frequency band without using frequency hopping for the PSS, SSS, or PBCH that the MTC terminal first receives.
  • the MTC repetitive transmission technique according to another embodiment of the present invention may adaptively adjust a position at which frequency hopping starts according to the type of MTC terminal.
  • the position at which frequency hopping is started for each MTC terminal may be adjusted differently.
  • the MTC repetitive transmission technique according to another embodiment of the present invention may be applied to uplink.
  • the frequency hopping may be performed only within the specific narrowband set by limiting to a specific narrowband set.
  • narrowband usage information such as the specific narrowband set may be informed in the following manner.
  • the base station informs the MTC terminal of an available narrowband set by using system information such as MIB or SIB that is broadcasted to all MTC terminals in the network repeatedly in the network.
  • the terminal may be used in common.
  • MIB and / or SIB encoding may be encoded with a code indicating a specific number to inform MTC terminal of available narrowband set usage information.
  • the available narrowband set usage information may be informed to the MTC terminal.
  • MIB and / or SIB data is multiplied by a specific code representing each narrowband set to be encoded and transmitted, for example, when the base station operates a total of 10 narrowband sets.
  • MIB and / or SIB data is multiplied by a specific code representing each narrowband set.
  • the MIB and / or SIB data is multiplied with a code representing a specific narrowband set, and the MTC terminal multiplies the received MIB and / or SIB data by changing 10 codes, thereby successfully decoding the double CRC error.
  • the narrowband set may be directly informed to the MTC terminal through the MIB and / or SIB or 10 types in advance. It is also possible to tell the MTC terminal to use RBs several times and RBs as narrowband sets directly without setting a narrowband set of. Resource location of the PDSCH transmitting the SIB may be informed by the PDCCH. If a narrowband set is used, it is necessary to know which narrowband set to use to receive PDCCH or PDSCH. Therefore, the narrowband to which the SIB is predetermined is to be sent or the narrowband to be sent to the SIB should be informed via the MIB.
  • PDSCH transmitting SIB is frequency hopping
  • the MIB may inform only the narrowband set of the PDSCH for the SIB and the narrowband set to be used for the actual data transmission through the SIB.
  • narrowband set information may be transmitted using a PDCCH. In this case, a narrowband set should be previously determined for a PDCCH commonly used by the entire MTC terminal.
  • the terminal ID such as RNTI, IMSI, GUTI, etc. may be substituted into a predetermined equation to determine a narrowband set or a frequency hopping pattern allocated to the MTC terminal itself. That is, the system information and the terminal ID may be used together to determine the narrowband set or the frequency hopping pattern allocated to each MTC terminal in the network.
  • a downlink control channel for example, PDCCH
  • PDCCH downlink control channel
  • the terminal ID such as RNTI, IMSI, TMSI, or GUTI may be substituted into a predetermined equation to determine a narrowband set or frequency hopping pattern allocated to the MTC terminal itself. That is, the downlink control channel transmitted to a specific group of users and the terminal ID may be used together to determine a narrowband set or a frequency hopping pattern allocated to each MTC terminal in the network.
  • a downlink control channel delivered to a specific user may be used to inform a specific user of a narrowband set available to a specific user terminal.
  • the cell ID, the system frame number (SFN), the subframe index (Subframe) as well as the terminal ID such as RNTI, IMSI, TMSI, or GUTI are used.
  • index, and slot index (Slot index) can be further utilized to determine the available narrowband set or frequency hopping pattern.
  • a narrowband set assigned to each independent MTC terminal in a network by substituting a system frame number (SFN) transmitted from the base station as system information such as MIB and SIB1 and an IMSI value of the MTC terminal itself in a predetermined equation.
  • SFN system frame number
  • the frequency hopping pattern can be determined.
  • independent scheduling for each MTC terminal can be made by adjusting each subfrane / slot multi-subframe scheduling information by additionally utilizing subframe index and slot index as well as SFN and terminal ID. Allow information to be determined.
  • subframe index and slot index can be used to control each subfrane / slot multi-subframe scheduling information for the corresponding slot or subframe. Independent scheduling information may be determined for each terminal.
  • the frequency hopping period may be informed to the MTC terminal, and when the frequency hopping period is completed, the narrowband set available in the control information (MIB, SIB, PDCCH or EPDCCH) may be informed and the narrowband set may be used until the next frequency hopping period.
  • MIB, SIB, PDCCH or EPDCCH the narrowband set available in the control information
  • the coverage enhanced level can be divided into a plurality of stages.
  • the extent to which coverage can be extended can be managed in two stages.
  • All channels within the MTC terminal may be set to the same coverage enhanced level.
  • a coverage level is configured for all channels in an MTC terminal (A single CE level is configured for all channels in a UE).
  • One Coverage Enhanced level may consist of a set of repetition times for at least PDSCH, PUSCH and / or MPDCCH (One CE level can be configured with a set of repetition numbers at least for PDSCH, PUSCH & MPDCCH ).
  • Which mode of mode 1 or mode 2 is used may be known for all channels in the MTC terminal (Which modes is used is known for all channels in a UE).
  • mode 1 describes the case where the repetition agrees with no repetitions and the low number of repetitions (Mode 1 describes behaviors for no repetitions and small number of repetitions). (Mode 2 describes behaviors agreed for large number of repetitions).
  • the information repeatedly transmitted here may be system information MIB, system information other than MIB, or data.
  • mapping of each coverage enhanced level to the mode may be indicated by RRC or signal.
  • the HARQ process number can be adaptively adjusted according to each coverage enhanced level. For example, it may be adjusted so that the HARQ process number decreases as the coverage gets further (or covers farther).
  • the HARQ process number can be up to two, three, or four.
  • the MTC terminal may receive only one when multiple information is received at the same time.
  • the method of determining the priority may be implemented to receive and decode the priorities in order of MIB-> SIB-> Paging-> Data.
  • an RACH process in an MTC terminal is important.
  • MTC machine type communication
  • RACH process in MTC terminal for coverage improvement when repetition transmission is performed on a signal (eg, PRACH preamble) transmitted from a terminal to a base station for performance improvement,
  • a signal eg, PRACH preamble
  • a signal for example, PRACH preamble
  • PRACH preamble may be repeatedly transmitted from the MTC terminal according to a predefined period.
  • the MTC terminal may be configured to dynamically determine whether to transmit a signal (for example, PRACH preamble) at every repetition period.
  • parameters related to repetitive transmission such as repetition and / or repetition period may be determined by the base station or the network, or may be determined by the MTC terminal or may use a preset value.
  • the signal (eg, PRACH preamble) may be repeatedly transmitted according to a repetition pattern composed of a specific number of consecutive periods.
  • the base station determines the existence of the MTC terminal (or MTC coverage extension terminal) with the PRACH preamble sent by the MTC terminal. That is, the PRACH preamble set is made separately for the MTC terminal, and the base station may distinguish between the MTC terminal (or MTC coverage extension terminal) and the general terminal (or general MTC terminal) due to the difference in the PRACH preamble.
  • the PRACH preamble of the existing LTE can be used as it is, but the code set and resource information to be used as the MTC-SIB can be informed. It is possible to divide and manage the PRACH code set into several. Accordingly, the base station can determine the CE level based on whether the terminal transmitting the PRACH to the set and the resource is the MTC terminal and the number of repetitive transmissions or the resource information.
  • the PRACH preamble is a kind of code and may use a Zadoff chu code.
  • the PRACH preamble is not binary code but may be multiplied by a binary code to create a new code.
  • the method for distinguishing MTC coverage improvement terminal from a general terminal without transmitting or receiving separate control signals is as follows.
  • the base station can maximize efficiency by dividing the MTC terminal and a general LTE / LTE-A terminal (Legacy terminal), and by operating a small coverage (large coverage) terminal and a laser coverage (larger coverage) terminal within the MTC terminal. .
  • a method of classifying a PRACH preamble is a method in which a base station defines and operates a set of dedicated PRACH preambles for a separate MTC terminal.
  • the existing PRACH preamble is used as it is, but when the existing PRACH preamble is repeated, the TDM or FDM pattern is not repeatedly sent as it is.
  • the MTC coverage improvement terminal and the general terminal can be distinguished by implementing a code value of the CDM. Specifically, 100110 is repeatedly sent. According to the index of the repetition pattern (for example, 0 to 5 can be assigned depending on the type of the repetition pattern), 100110 is sent as it is, and then inverted to send 011001. As a result, the MTC coverage improvement terminal can be distinguished from the general terminal.
  • resource allocation patterns such as TDM / FDM can be changed based on this new_code.
  • TDM and FDM can be sent by periodically changing the code itself, or can be divided into TDM, FDM pattern itself.
  • the code is changed differently according to the repetitive transmission pattern.
  • the change pattern has a unique specific pattern representing the MTC CE terminal.
  • one specific pattern indicating the MTC terminal includes a CRC pattern currently being used in the downlink control channel, and in the downlink control channel, the CRC output may be XORed with the C-RNTI. Therefore, this can be seen as a code change based on ID such as C-RNTI.
  • the resource allocation pattern is a method of periodically changing a time and frequency position of a transmitted resource with a certain pattern when repeatedly transmitting a code that is repeatedly transmitted many times.
  • the PRACH code is assigned to a specific time and frequency location, there is also a method for recognizing the MTC CE terminal.
  • the above example is a method for distinguishing an MTC coverage improvement terminal from a general terminal by combining a CDM and a repeating transmission pattern. That is, as one of methods for recycling the PRACH code used in the existing LTE, the MTC terminal may combine the repeated transmission pattern with the existing PRACH code because the PRACH needs to be repeatedly transmitted several times. That is, the MTC coverage improvement terminal and the general terminal can be distinguished by simply modifying and using the existing PRACH preamble code in a specific pattern for each repeated transmission. In order to distinguish between the MTC coverage improvement terminal and the general terminal, the modification can be easily made without any collision with any existing code.
  • Another method is a method of combining a specific code representing the MTC terminal of the above 3) and the existing PRACH preamble code.
  • LTE finds out what its own PDCCH is through blind decoding in case of PDCCH.
  • the method used is a method of transmitting a new CRC generated by XORing its ID (C-RNTI in the case of LTE) with the CRC and transmitting it to the DPCCH. Therefore, the receiver can easily identify whether it is its own PDCCH through blind CRC check. This way, if you use any code that is fundamentally transformed into any other code (e.g. XOR) with certain other code, you will be able to easily determine whether it is modified or not. Using this concept is method 3).
  • one specific code indicating the MTC terminal is determined, and the specific code is combined / modified with the existing PRACH code.
  • the existing PRACH code is not a binary code, it cannot be simply transformed by XOR, and it must be modified by other methods such as multiplication.
  • the RAR message and the paging message may be applied to three reception modes as follows for the MTC terminal having low complexity and the MTC terminal operating in the cell extension mode.
  • the RAR message and the paging message are received by the PDSCH scheduled by the M-PDCCH, that is, by the PDSCH whose schedule information is transmitted by the M-PDCCH.
  • the RAR message and the paging message are received in the DCI of the M-PDCCH.
  • Receiving a single MAC RAR within a narrow band may support using the DCI of the M-PDCCH of Option 2.
  • Receiving multiple MAC RARs within a narrow band may support the use of a PDSCH scheduled by M-PDCCH of Option 1.
  • a part of the MAC RAR may be received by the DCI of the M-PDCCH and the remaining part of the MAC RAR may be included in the PDSCH.
  • the MTC terminal is received by the MTC terminal using PDSCH or PDSCH scheduled with M-PDCCH without using DCI of M-PDCCH. You may.
  • the base station may indicate whether to support the reception mode of the RAR or paging message in the SIB. For example, if the base station indicates that it only supports option 1, then option 1 may be used for the single MAC RAR as well, which is received by the PDSCH scheduled by the M-PDCCH.
  • the MTC terminals of the present invention can be used in various applications, low power consumption is required, and can be applied when communication for infrequent small burst transmissions is used.
  • MTC terminals may be applied to wearable devices for smart metering for power metering, implementation of health-related applications, and the like.
  • FIG. 1 is a schematic block diagram of an MTC terminal according to an embodiment of the present invention
  • Figure 2 is a schematic block diagram of an MTC communication system according to an embodiment of the present invention.
  • the MTC terminal 100 includes a transceiver 120, a processor 110, and an antenna 130, and according to the embodiments of the present invention as described above with the base station 120.
  • MTC communication including MTC frequency hopping, MTC system information (MIB) transmission, and MTC UE uplink random access is performed.
  • MIB MTC system information
  • the transceiver 120 receives data and control signals (downlink data presence message, etc.) from the base station 120 through the antenna 130 through the downlink (152), and the uplink (to the base station 120) Data and control signals (downlink data transmission request messages, etc.) are transmitted via uplink 154.
  • the processor 110 may control the transceiver 100 to determine when to transmit a control signal (downlink data transmission request message, etc.).
  • Processor 110 may be a general purpose processor, special purpose processor, conventional processor, digital signal processor (DSP), microprocessor, one or more microprocessors associated with a DSP core, controller, microcontroller, application specific integrated circuit specific integrated circuits (ASICs), field programmable gate array (FPGA) circuits, integrated circuits (ICs), state machines, and the like.
  • the processor 110 may perform signal coding, data processing, power control, input / output processing, and / or any other functionality that enables the terminal to operate in a wireless environment.
  • the processor 110 may be coupled to the transceiver 120.
  • FIG. 2 shows processor 110 and transceiver 120 as separate components, processor 110 and transceiver 120 may be integrated together in an electronic package or chip.
  • antenna 130 may be an antenna configured to transmit and / or receive RF signals.
  • antenna 130 may be, for example, a emitter / detector configured to transmit and / or receive IR, UV, or visible light signals.
  • antenna 130 may be configured to transmit and receive both RF and optical signals.
  • Antenna 130 may be configured to transmit and / or receive any combination of wireless signals.
  • the transceiver 120 may be configured to modulate the signals to be transmitted by the antenna 130 and to demodulate the signals received by the antenna 130.
  • the base station can be one or more over an air interface that can be any suitable wireless communication link (e.g., radio frequency (RF), microwave, infrared (IR), ultraviolet (UV), visible light, etc.). Communicate with the terminal.
  • RF radio frequency
  • IR infrared
  • UV ultraviolet
  • visible light etc.
  • the MTC communication system can be a multiple access system and can employ channel access schemes such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA and the like.
  • a base station and an MTC terminal of a RAN may be configured such as a Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which can set up an air interface using wideband CDMA (WCDMA).
  • WCDMA may include communication protocols such as High-Speed Packet Access (HSPA) and / or Evolved HSPA (HSPA +).
  • HSPA may include High-Speed Downlink Packet Access (HSDPA) and / or High-Speed Uplink Packet Access (ULSPA).
  • the base station and the MTC terminals are Evolved UTRA (Evolved UTRA) that can configure the air interface using Long Term Evolution (LTE) and / or LTE-Advanced (LTE-A); Radio technology such as E-UTRA).
  • Evolved UTRA Evolved UTRA
  • LTE Long Term Evolution
  • LTE-A LTE-Advanced
  • Radio technology such as E-UTRA
  • the base station and the MTC terminal may include IEEE 802.16 (i.e., worldwide interoperability for microwave access (WiMAX), CDMA2000, CDMA2000 1X, CDMA 2000 Evolution-Data Optimized (EV-DO), interim standard 2000 (IS). -2000), Interim Standard 95 (IS-95), Interim Standard 856 (IS-856), Global System for Mobile communications (GSM), Enhanced Data Rate for GSM Evolution (Enhanced) Radio technologies such as Data rates for GSM Evolution (EDGE) and GSM / EDGE RAN (GERAN) can be implemented.
  • IEEE 802.16 i.e., worldwide interoperability for microwave access (WiMAX), CDMA2000, CDMA2000 1X, CDMA 2000 Evolution-Data Optimized (EV-DO), interim standard 2000 (IS). -2000), Interim Standard 95 (IS-95), Interim Standard 856 (IS-856), Global System for Mobile communications (GSM), Enhanced Data Rate for GSM Evolution (Enhanced) Radio technologies such as Data rates for GSM Evolution (EDGE) and G
  • the base station of FIG. 2 may be, for example, a wireless router, HNB, HeNB, or AP and may utilize any suitable RAT that facilitates wireless access in a localized area, such as a place of business, home, vehicle, campus, etc. Can be.
  • the base station and MTC terminals may implement a radio technology such as IEEE 802.11 to establish a wireless local area network (WLAN).
  • base stations and terminals may implement a radio technology such as IEEE 802.15 to establish a wireless personal area network (WPAN).
  • WLAN wireless local area network
  • WPAN wireless personal area network
  • the base station and MTC terminals may utilize a cellular-based RAT (eg, WCDMA, CDMA2000, GSM, LTE, LTE-A, etc.) to configure the picocell or femtocell.
  • a cellular-based RAT eg, WCDMA, CDMA2000, GSM, LTE, LTE-A, etc.
  • the base station can directly access the Internet.
  • the base station may not be required to access the Internet through the core network.
  • the power level or coding scheme of RS signals which are a kind of pilot signal between successive multi-sub frames, should not be changed, and the cell-specific reference signal (CRS) may be a power level or
  • a reference signal (RS) signal transmitted by a terminal such as a UE-specific reference signal (URS) / demodulation reference signal (DMRS) is a power level or subframe per subframe in the existing LTE / LTE-A standard. Coding schemes may change. Therefore, when multi-subframe scheduling is performed, the power level or coding scheme of the UE spedicific RSs is not changed in the multi-subframe.
  • multi-subframe scheduling may be supported when unicast PDSCH transmission is scheduled by EPDCCH (PDCCH for MTC communication).
  • multi-subframe scheduling may be supported when unicast PDSCH transmission is scheduled by EPDCCH (PDCCH for MTC communication).
  • Multi-subframe scheduling or cross-subframe scheduling (Cross-subframe scheduling) is one of the PDSCH (or PUSCH) UE burst can be scheduled within the existing one subframe of, and for the UE burst
  • the scheduling information is a scheduling method deviating from the method determined by one PDCCH / EPDCCH control information corresponding thereto, and a specific UE burst may be scheduled over several subframes by one PDCCH / EPDCCH control information.
  • one PDCCH / EPDCCH control information for a specific UE in a specific subframe in a conventional method in which scheduling information of a PDSCH burst for a corresponding UE in a corresponding subframe is determined as one PDCCH / EPDCCH control information for a specific UE in a specific subframe.
  • a PDSCH burst for a specific UE may be allocated through several subframes.
  • multiple PUSCH transmissions (or multiple PDSCH transmissions) in a single downlink control information (DCI) format by using multi-sub frame scheduling or cross-sub frame scheduling. Can be scheduled to significantly reduce the downlink control overhead (control overhead)
  • the uplink data rate is increased by 2.33 times in the PUSCH transmission of FIG. 14 compared to the PUSCH transmission in FIG. 13.
  • Such multi-sub frame scheduling or cross-sub frame scheduling can also be applied to downlink PDSCH transmission.
  • EPDCCH for coverage enhancement multi-subframe scheduling is a coverage improvement sub-frame scheduling (Multi-subframe scheduling) or cross
  • Sches-subframe scheduling is a coverage improvement sub-frame scheduling (Multi-subframe scheduling) or cross
  • scheduling Multi-subframe scheduling
  • cross-scheduling the sub-frame cross-subframe scheduling
  • Multi-subframe scheduling or cross-case of the sub-frame scheduling (Cross-subframe scheduling) can significantly reduce the down-link control overhead (control overhead), which may increase the data rate, power consumption, The number of subframe swaging can be reduced.
  • control overhead control overhead
  • common multi-subframe scheduling information is informed by using system information such as MIB or SIB broadcasted to all MTC terminals in the network repeatedly, and all MTC terminals in the network can be used in common.
  • system information such as MIB or SIB broadcasted to all MTC terminals in the network repeatedly, and all MTC terminals in the network can be used in common.
  • the system information and the terminal ID can be used together to determine the multi-subframe scheduling information allocated to each MTC terminal in the network.
  • the multi-subframe scheduling information allocated to the MTC terminal itself may be uniquely determined. That is, the common downlink multi-subframe scheduling information transmitted to a specific group of users and the terminal ID may be used together to determine the multi-subframe scheduling information allocated to each MTC terminal in the network.
  • the multi-subframe scheduling information can be informed to a specific user, and the specific user terminal can be used.
  • SFN System Frame Number
  • MIB and SIB1 System Frame Number
  • ID value of the MTC terminal itself by substituting the formula for determining the predetermined multi-subframe scheduling information independently for each MTC terminal in the network.
  • independent scheduling for each MTC terminal can be made by adjusting each subfrane / slot multi-subframe scheduling information by additionally utilizing subframe index and slot index as well as SFN and terminal ID. Allow information to be determined.
  • the start point and end point of the subframe using the same scheduling as control information can be informed by using semi-static scheduling.
  • two or more of a repetition period, a multi-subframe scheduling period, and a frequency hopping pattern period can be operated to coincide.
  • the above methods can reduce the size of control information to be transmitted in common. If there is information that can be shared between different patterns, the overhead can be reduced compared to sending separately.
  • persistent scheduling is a method currently used for LTE VoIP, and since voice has a real time characteristic, data must be constantly transmitted every subframe. To do this, it is complicated to load scheduling information in each subframe every time in PDCCH / EPDCCH. Therefore, if scheduling is performed only once in PDCCH / EPDCCH, the same scheduling information continues from the next subframe. As a technique of reusing this, in case of MTC terminal, it is not voice but data, but the amount of data is small, so only the duration for performing persistent scheduling is determined and informed.
  • a part of the system bandwidth for communication between the MTC terminal and the base station may be set instead of using the entire system bandwidth for the communication between the MTC terminal and the base station.
  • the narrowband may be defined as a set of contiguous physical resource blocks (PRBs).
  • a narrow band set should be set identically for uplink transmission and downlink transmission. That is, in the case of the TDD transmission scheme, the uplink transmission and the downlink transmission should be set to have the same set of subcarriers.
  • Repetitive transmission information, scheduling information, frequency hopping information sharing between uplink and downlink of MTC terminal Repetitive transmission information, scheduling information, frequency hopping information sharing between uplink and downlink of MTC terminal
  • the repetition level, scheduling information, and frequency hopping pattern for repetitive transmission are DL / DL (UL). ) Can share with each other.
  • repetitive transmission may include a case of repetitive transmission of MIB, SIB, PDCCH, (E) PDCCH, PUSCH, PUCCH, PBCH, PRACH preamble, paging, or random access response (RAR).
  • the repetition level means the number of repetitions and the like during repetitive transmission.
  • bundling is a technique for repetition or gathering and transmitting SIB, PDCCH, (E) PDCCH, PUSCH, PUCCH, PBCH, and PRACH.
  • resource location information on whether to use persistent scheduling and persistent scheduling may be shared in downlink / uplink.
  • frequency hopping period and narrowband usage information during frequency hopping may also be shared in downlink / uplink.
  • the narrowband usage information may include an available narrowband set and narrowband size information.
  • the narrow band may have a size smaller than 6 PRBs, eg, 5 PRBs, 4 PRBs, 3 PRBs, and may be larger than 6 PRBs, eg, 7 PRBs, 8 PRBs, 9 PRBs. It may have a PRB or 12 PRBs that are twice the size and 18 PRBs that are three times the size.
  • Narrow band size may be fixedly used in one of a plurality of sizes selectively, or may be adaptively used depending on the situation. For example, if the narrowband size is made smaller, the number of narrowbands increases, so that a plurality of MTC terminals may be supported or more hoppable bands may be provided in frequency hopping. Increasing the narrow band size can increase the transmission data rate.
  • the method of sharing in downlink (DL) / uplink (UL) includes a repetition level, scheduling information, and frequency hopping pattern of downlink based on downlink in uplink. Can be used as is. Or uplink information (repletion level) by inputting downlink information (repletion level, scheduling information, frequency hopping pattern, etc.) according to a predetermined rule in uplink. ), Scheduling information, frequency hopping pattern, and the like.
  • the repetition level, scheduling information, and frequency hopping pattern of the uplink may be used as it is based on the uplink in the downlink.
  • the downlink information (repletion level) is input by inputting uplink information (repletion level, scheduling information, frequency hopping pattern, etc.) according to a predetermined rule in downlink. ), Scheduling information, frequency hopping pattern, and the like.
  • the MTC terminal can know the repetition level of the random access response (RAR) transmission from the repetition level of the most recent PRACH.
  • the MTC terminal can know from which subframe the RAR transmission starts from the most recent PRACH resource set.
  • RAR Random Access Response
  • the MTC terminal can know from which frequency resource (s) the RAR transmission occurs from the most recent PRACH resource set.
  • FIG. 17 illustrates an example of a data transmission method for a low data rate based IoT sensor application according to another embodiment of the present invention.
  • FIG. 17 shows an example of a data transmission method when applied to an IoT sensor by dividing 1RB into 12 again within a 200KHz (eg, 1 RB) data rate of a GSM system. Since the data transmission method of FIG. 17 uses a low data rate of about 1/6 of the MTC data rate, the data transmission method may be mainly applied to a low speed IoT sensor rather than an image data transmission purpose.
  • a pilot and data are transmitted from a transmitter as shown in FIG. 17.
  • the pilot 1101-N can be added and transmitted.
  • the pilot 1101-N may be generated by copying a pilot 1101-0.
  • the receiver decodes data 1002-1 and decodes data using both pilot 1000-0 and pilot 1001-1 to decode data 1002-1 using only pilot 1001-0 (or pilot 1001-1). Compared with the restoration, the performance can be improved.
  • the receiver decodes the data 1002-2 by using both the pilot 1000-1 and the pilot 1001-2 to decode the data using only the pilot 1001-1 (or the pilot 1001-2). Compared with this, the performance can be improved.
  • the receiver decodes data 1002-N only the pilot 1001- (N-1) (or pilot 1001-N) is decoded by decoding the data using both pilot 1000- (N-1) and pilot 1001-N. The performance can be improved as compared with the case of decoding data. If a preamble (RS) or reference signal (RS) exists before the 1101-0 pilot, the 1101-0 pilot may be omitted.
  • RS preamble
  • RS reference signal
  • the PRACH preamble it is possible to transmit using a smaller bandwidth than the subcarrier space. Reducing the bandwidth has the effect of increasing the SNR.
  • the bandwidth is reduced, the data rate is reduced, but since the data is not transmitted since it is a preamble, there is no side effect due to the reduction of the data rate.
  • the UCI information that the PUCCH needs to send may be transmitted as the PUSCH instead of the PUCCH.
  • the UCI information transmitted by the PUCCH may be transmitted through the PRACH preamble.
  • the MTC may operate without transmitting some of the UCI information that the PUCCH should send instead of using the PUCCH.
  • 6 PRB data can be divided and transmitted over several TTI. For example, if only 3PRB can be operated within the bandwidth to be operated, 6PRB signals may be divided and transmitted twice. When using 1 PRB (180kHz, about 200kHz), it can be divided into 6 times.
  • Existing LTE uses TDD / FDD type of Full Deuplex.
  • the existing LTE can be transmitted and received at the same time, but in this case, since both the transceiver is operating, the power consumption is increased and the complexity is increased. If the data rate does not need to be fast like MTC, the half duplex scheme can be applied to reduce power consumption and complexity by only one transmission or reception at a time.
  • a method for performing random access between a MTC terminal and a base station is provided.
  • the random access may use a Physical Random Access Channel (PRACH) signal to distinguish a coverage extension MTC terminal from a general MTC terminal.
  • PRACH Physical Random Access Channel
  • the method of performing the random access may include performing a random access procedure by using the received system information in the terminal.
  • a method for performing random access between a MTC terminal and a base station is provided.
  • the method of performing the random access may include performing a random access procedure by using the received system information in the terminal.
  • the MTC terminal may transmit a random access preamble to the base station.
  • the base station may receive a random access preamble and transmit a random access response (RAR) message to the MTC.
  • RAR random access response
  • the MTC terminal may transmit an RRC connection request message in response to the random access response message.
  • the RRC connection request message may include a terminal ID.
  • the base station may recognize or identify the MTC terminal based on the terminal ID and prepare for resource allocation.
  • the base station may transmit an RRC connection setup message to the MTC terminal.

Landscapes

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

Abstract

Un procédé de communication de machine à machine permettant une extension de couverture comprend les étapes consistant à : attribuer une bande passante de système ayant une taille prédéterminée en vue d'une transmission ; et transmettre des informations et/ou des données de système, à l'exception d'un bloc d'informations maître (MIB), en utilisant la bande passante de système ayant la taille prédéterminée. Lesdites informations et/ou données de système, à l'exception du MIB, sont transmises en effectuant un saut de fréquence à l'aide d'un modèle de saut périodique. Une couverture peut donc être étendue tout en maintenant une faible puissance.
PCT/KR2016/003318 2015-04-02 2016-03-31 Procédé de communication de machine à machine permettant une extension de couverture, appareil et système permettant de mettre en œuvre ledit procédé WO2016159680A1 (fr)

Applications Claiming Priority (14)

Application Number Priority Date Filing Date Title
KR10-2015-0046893 2015-04-02
KR20150046893 2015-04-02
KR10-2015-0057580 2015-04-23
KR20150057580 2015-04-23
KR10-2015-0073249 2015-05-26
KR20150073249 2015-05-26
KR10-2015-0075325 2015-05-28
KR20150075325 2015-05-28
KR1020150169116A KR20160118913A (ko) 2015-04-02 2015-11-30 커버리지 확장을 위한 사물 통신 방법, 이를 수행하는 장치 및 시스템
KR10-2015-0169116 2015-11-30
US14/987,778 2016-01-05
US14/987,778 US9510134B2 (en) 2015-04-02 2016-01-05 Method for performing machine type communication for the purpose of coverage improvement, apparatuses and systems for performing the same
US15/069,928 US9654902B2 (en) 2015-05-22 2016-03-14 Methods for performing machine type communication for the purpose of coverage enhancement apparatuses and systems for performing the same
US15/069,928 2016-03-14

Publications (1)

Publication Number Publication Date
WO2016159680A1 true WO2016159680A1 (fr) 2016-10-06

Family

ID=57004475

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2016/003318 WO2016159680A1 (fr) 2015-04-02 2016-03-31 Procédé de communication de machine à machine permettant une extension de couverture, appareil et système permettant de mettre en œuvre ledit procédé

Country Status (1)

Country Link
WO (1) WO2016159680A1 (fr)

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018200472A1 (fr) * 2017-04-24 2018-11-01 Intel IP Corporation Canaux de commande de liaison descendante physique (pdcch) et pdcch améliorés (epdcch) dans des agencements d'amélioration de couverture à large bande (wce)
CN110139247A (zh) * 2018-02-08 2019-08-16 北京三星通信技术研究有限公司 物理信道传输的方法及设备
WO2020032736A1 (fr) * 2018-08-09 2020-02-13 엘지전자 주식회사 Procédé pour améliorer les performances d'émission et de réception d'un canal de commande de liaison descendante de type lte mtc et appareil associé
EP3876565A4 (fr) * 2018-10-30 2022-07-13 Beijing Xiaomi Mobile Software Co., Ltd. Procédé et dispositif de transmission de données, et support d'informations lisible
US11785624B2 (en) 2018-02-08 2023-10-10 Samsung Electronics Co., Ltd. Method for transmitting physical channels, user equipment therefor, method and user equipment for relay transmission

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20130032548A (ko) * 2011-09-23 2013-04-02 삼성전자주식회사 광대역 단말과 협대역 단말을 함께 운용하는 무선통신시스템에서 협대역 단말의 시스템 접속 방법 및 장치
KR20140071480A (ko) * 2011-09-30 2014-06-11 인터디지탈 패튼 홀딩스, 인크 감소된 채널 대역폭을 사용하는 장치 통신
WO2015030523A1 (fr) * 2013-08-29 2015-03-05 엘지전자 주식회사 Procédé et dispositif pour la transmission d'informations d'état de canal dans un système d'accès sans fil supportant une communication de type machine

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20130032548A (ko) * 2011-09-23 2013-04-02 삼성전자주식회사 광대역 단말과 협대역 단말을 함께 운용하는 무선통신시스템에서 협대역 단말의 시스템 접속 방법 및 장치
KR20140071480A (ko) * 2011-09-30 2014-06-11 인터디지탈 패튼 홀딩스, 인크 감소된 채널 대역폭을 사용하는 장치 통신
WO2015030523A1 (fr) * 2013-08-29 2015-03-05 엘지전자 주식회사 Procédé et dispositif pour la transmission d'informations d'état de canal dans un système d'accès sans fil supportant une communication de type machine

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
NEC: "Frequency Hopping Schemes for LTE Rel-13 MTC", R1-150286, 3GPP TSG RAN WG1 MEETING #80, 18 February 2015 (2015-02-18), Athens, Greece, XP050933496 *
NOKIA NETWORKS ET AL.: "PBCH/MIB Enhancement for MTC", R1-150262, 3GPP TSG RAN WG 1 MEETING #80, 18 February 2015 (2015-02-18), Athens, Greece, XP050933474 *

Cited By (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018200472A1 (fr) * 2017-04-24 2018-11-01 Intel IP Corporation Canaux de commande de liaison descendante physique (pdcch) et pdcch améliorés (epdcch) dans des agencements d'amélioration de couverture à large bande (wce)
CN110139247A (zh) * 2018-02-08 2019-08-16 北京三星通信技术研究有限公司 物理信道传输的方法及设备
US11785624B2 (en) 2018-02-08 2023-10-10 Samsung Electronics Co., Ltd. Method for transmitting physical channels, user equipment therefor, method and user equipment for relay transmission
CN110139247B (zh) * 2018-02-08 2024-04-12 北京三星通信技术研究有限公司 物理信道传输的方法及设备
WO2020032736A1 (fr) * 2018-08-09 2020-02-13 엘지전자 주식회사 Procédé pour améliorer les performances d'émission et de réception d'un canal de commande de liaison descendante de type lte mtc et appareil associé
US11621760B2 (en) 2018-08-09 2023-04-04 Lg Electronics Inc. Method for improving transmission and reception performance of LTE MTC downlink control channel and apparatus therefor
US11855732B2 (en) 2018-08-09 2023-12-26 Lg Electronics Inc. Method for improving transmission and reception performance of LTE MTC downlink control channel and apparatus therefor
EP3876565A4 (fr) * 2018-10-30 2022-07-13 Beijing Xiaomi Mobile Software Co., Ltd. Procédé et dispositif de transmission de données, et support d'informations lisible

Similar Documents

Publication Publication Date Title
WO2016190537A1 (fr) Procédé de communication de machine à machine permettant une extension de couverture, et appareil et système permettant de mettre en œuvre ledit procédé
WO2020231096A1 (fr) Procédé et appareil permettant de réaliser une communication dans un système de communication sans fil
WO2019124891A1 (fr) Procédé et appareil pour bloc d'accès initial sur un spectre sans licence nr autonome
WO2021034120A1 (fr) Procédé et appareil pour déceler une opération de récupération de défaillance de faisceau dans un système de communication sans fil
WO2020159303A1 (fr) Procédé et appareil de transmission dans un système de communication sans fil, nœud radio et support lisible par ordinateur
WO2020027570A1 (fr) Procédé et appareil d'indication d'un temps d'occupation de canal dans un système de communication sans fil
WO2020256379A1 (fr) Procédé et appareil pour répétition de bloc ss/pbch
WO2018203617A1 (fr) Procédé de réception de signal de synchronisation, et appareil correspondant
WO2018203616A1 (fr) Procédé de réception de signal de synchronisation et dispositif associé
WO2018231010A1 (fr) Procédé d'émission-réception de canal de liaison descendante et appareil associé
WO2016117981A1 (fr) Procédé et dispositif pour la prise en charge de la communication de données dans un système de communication sans fil
WO2016175486A1 (fr) Procédé et appareil lc pour réception de canal de commande en liaison descendante
WO2021157938A1 (fr) Procédé et dispositif permettant de transmettre/recevoir des informations de commande de liaison descendante dans un système de communication sans fil
WO2020032695A1 (fr) Procédé et appareil de planification de transmission multiple dans un système de communication sans fil
EP3827633A1 (fr) Procédé et appareil de planification de transmission multiple dans un système de communication sans fil
WO2022145882A1 (fr) Procédé et appareil pour transmettre et recevoir un pdcch dans un système de communication sans fil
WO2015126202A1 (fr) Procédé d'émission répétitive de canal pour extension de couverture, et terminal associé
WO2015163645A1 (fr) Procédé et terminal pour transmettre un signal de référence de sondage dans un système de communication sans fil
WO2016171399A1 (fr) Procédé d'émission et de réception d'un canal de données, et dispositif lc
WO2015182970A1 (fr) Procédé pour réaliser une mesure de signal de découverte et équipement utilisateur
WO2015133766A1 (fr) Procédé de réglage de la puissance en liaison descendante dans un schéma de modulation d'ordre élevé, et terminal correspondant
WO2015133778A1 (fr) Procédé et appareil pour transmettre un canal de commande de liaison montante dans un système de communication sans fil
WO2021162483A1 (fr) Procédé et appareil pour la transmission ou la réception d'un canal de liaison descendante depuis de multiples points de transmission/réception dans un système de communication sans fil
WO2015108308A1 (fr) Procédé pour exécuter une procédure de recherche de cellule, et équipement d'utilisateur pour exécuter une procédure de recherche d'après un signal de recherche dans un système de communications sans fil
WO2021162423A1 (fr) Procédé et dispositif de transmission pour transmettre/recevoir un canal de liaison montante provenant de multiples points de transmission/réception dans un système de communication sans fil

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: 16773461

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 16773461

Country of ref document: EP

Kind code of ref document: A1