WO2020032681A1 - Procédé d'émission et de réception de signaux dans un système de communication radio, et appareil prenant en charge ledit procédé - Google Patents

Procédé d'émission et de réception de signaux dans un système de communication radio, et appareil prenant en charge ledit procédé Download PDF

Info

Publication number
WO2020032681A1
WO2020032681A1 PCT/KR2019/010070 KR2019010070W WO2020032681A1 WO 2020032681 A1 WO2020032681 A1 WO 2020032681A1 KR 2019010070 W KR2019010070 W KR 2019010070W WO 2020032681 A1 WO2020032681 A1 WO 2020032681A1
Authority
WO
WIPO (PCT)
Prior art keywords
transport block
harq
present disclosure
various embodiments
gap
Prior art date
Application number
PCT/KR2019/010070
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
Application filed by 엘지전자 주식회사 filed Critical 엘지전자 주식회사
Publication of WO2020032681A1 publication Critical patent/WO2020032681A1/fr

Links

Images

Classifications

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

Definitions

  • Various embodiments of the present disclosure relate to a wireless communication system, and more particularly, to a method for transmitting and receiving a signal in a wireless communication system and an apparatus supporting the same.
  • Wireless access systems are widely deployed to provide various kinds of communication services such as voice and data.
  • a wireless access system is a multiple access system capable of supporting communication with multiple users by sharing available system resources (bandwidth, transmission power, etc.).
  • multiple access systems include code division multiple access (CDMA) systems, frequency division multiple access (FDMA) systems, time division multiple access (TDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, and single carrier frequency (SC-FDMA). division multiple access) system.
  • CDMA code division multiple access
  • FDMA frequency division multiple access
  • TDMA time division multiple access
  • OFDMA orthogonal frequency division multiple access
  • SC-FDMA single carrier frequency division multiple access
  • Massive Machine Type Communications which connects multiple devices and objects to provide various services anytime and anywhere, is also being considered in next-generation communication.
  • a communication system design considering a service / UE that is sensitive to reliability and latency is being considered.
  • Various embodiments of the present disclosure may provide a method for transmitting and receiving a signal in a wireless communication system and an apparatus for providing the same.
  • various embodiments of the present disclosure may provide a method for transmitting and receiving a signal based on multiple transport blocks and an apparatus supporting the same in a system to which repetitive transmission is applied to physical signal / channel transmission.
  • Various embodiments of the present disclosure may provide a method for transmitting and receiving a signal in a wireless communication system and an apparatus supporting the same.
  • a method for receiving a signal in a wireless communication system includes: receiving downlink control information (DCI) for scheduling a first transport block and a second transport block, based on the DCI, the first transport block in a first time resource; And receiving the second transport block within a second time resource based on the receiving and the DCI.
  • DCI downlink control information
  • a gap may be established between the first time resource and the second time resource.
  • receiving the first transport block may include repeatedly receiving the first transport block within the first time resource based on the DCI.
  • receiving the second transport block may include repeatedly receiving the second transport block within the second time resource based on the DCI.
  • the size of the gap may be determined based on the time required for the device to combine and decode the first transport block repeatedly received within the first time resource. have.
  • the size of the gap may be determined as the first size.
  • the first size may be determined to be zero.
  • the size of the gap may be determined as the second size.
  • the method may further include transmitting, within the gap, a hybrid automatic repeat and request acknowledgment (HARQ-ACK) associated with the first transport block.
  • HARQ-ACK hybrid automatic repeat and request acknowledgment
  • a HARQ process number associated with the second transport block may be determined based on an HARQ-ACK associated with the first transport block.
  • the HARQ process number associated with the second transport block is a HARQ process number associated with the first transport block. Can be determined as the next HARQ process number.
  • the HARQ process number associated with the second transport block is equal to the HARQ process number associated with the first transport block. The same can be determined.
  • the NACK may include information requesting to change a transmission parameter associated with the second transport block.
  • the second transport block may be configured based on the information requesting to change the transmission parameter.
  • the transmission parameter is one of information about a redundancy version associated with the second transport block or information about a modulation and coding scheme associated with the second transport block. It may contain the above.
  • transmitting the HARQ-ACK associated with the first transport block may include obtaining HARQ-ACK associated with each of a plurality of sub-blocks included in the first transport block. Bundling HARQ-ACK associated with each of the plurality of sub-blocks to obtain HARQ-ACK associated with the first transport block and within the gap, HARQ associated with the first transport block. May include transmitting an -ACK.
  • an apparatus for receiving a signal in a wireless communication system may comprise at least one memory and at least one processor coupled with the at least one memory.
  • the at least one processor is configured to: receive downlink control information (DCI) for scheduling a first transport block and a second transport block, and based on the DCI, The first transport block may be received in one time resource, and the second transport block may be received in a second time resource based on the DCI.
  • DCI downlink control information
  • a gap may be established between the first time resource and the second time resource.
  • the one or more processors may transmit a hybrid automatic repeat and request acknowledgment (HARQ-ACK) associated with the first transport block within the gap.
  • HARQ-ACK hybrid automatic repeat and request acknowledgment
  • the HARQ process number associated with the second transport block may be determined based on the HARQ-ACK associated with the first transport block.
  • an apparatus for transmitting a signal in a wireless communication system may comprise at least one memory and at least one processor coupled with the at least one memory.
  • the at least one processor is configured to: transmit downlink control information (DCI) for scheduling a first transport block and a second transport block, and in the first time resource
  • DCI downlink control information
  • the first transport block can be transmitted, and the second transport block can be transmitted within a second time resource.
  • a gap may be established between the first time resource and the second time resource.
  • the device may communicate with one or more of a mobile terminal, a network, and an autonomous vehicle other than the vehicle that includes the device.
  • a signal transmission / reception method based on multiple transport blocks and an apparatus supporting the same may be provided.
  • the length of the multiple transport block is less than or equal to a certain length, by not setting the above-described gap or setting the size of the gap to 0, there is an effect of increasing the signal transmission / reception effect in the system. have.
  • the terminal reports the HARQ-ACK for the transport block received before the gap in the above-described gap period, and receives after the gap according to the reported HARQ-ACK value.
  • HARQ-ACK feedback can be performed more effectively, and network overhead can be reduced.
  • FIG. 1 is a diagram illustrating a physical channel that can be used in various embodiments of the present disclosure and a signal transmission method using the same.
  • FIG. 2 is a diagram illustrating a radio frame structure based on an LTE system to which various embodiments of the present disclosure are applicable.
  • FIG. 3 is a diagram illustrating a slot structure based on an LTE system to which various embodiments of the present disclosure are applicable.
  • FIG. 4 is a diagram illustrating an uplink subframe structure based on an LTE system to which various embodiments of the present disclosure are applicable.
  • FIG. 5 is a diagram illustrating a downlink subframe structure based on an LTE system to which various embodiments of the present disclosure are applicable.
  • FIG. 6 is a diagram illustrating a radio frame structure based on an NR system to which various embodiments of the present disclosure are applicable.
  • FIG. 7 illustrates a slot structure based on an NR system to which various embodiments of the present disclosure are applicable.
  • FIG. 8 is a diagram illustrating a self-contained slot structure to which various embodiments of the present disclosure are applicable.
  • FIG. 9 is a diagram illustrating one REG structure based on an NR system to which various embodiments of the present disclosure are applicable.
  • FIG. 10 is a diagram illustrating a frame structure based on an NB-IoT system to which various embodiments of the present disclosure are applicable.
  • FIG. 11 is a diagram illustrating transmission of an NB-IoT downlink physical channel / signal in an FDD LTE system to which various embodiments of the present disclosure are applicable.
  • FIG. 12 is a diagram illustrating an NPUSCH format to which various embodiments of the present disclosure are applicable.
  • FIG. 13 is a diagram illustrating an operation when a multi-carrier is configured in an FDD NB-IoT to which various embodiments of the present disclosure are applicable.
  • WUS 14 is a diagram illustrating a wake-up signal (WUS) signal transmission according to various embodiments of the present disclosure.
  • FIG. 15 is a diagram illustrating operations of a terminal and a base station in a wireless communication system to which various embodiments of the present disclosure are applicable.
  • 16 is a diagram illustrating a transmission / reception structure based on multiple transport blocks according to various embodiments of the present disclosure.
  • 17 illustrates a transmission / reception structure based on multiple transport blocks and sub-blocks according to various embodiments of the present disclosure.
  • FIG. 18 is a diagram illustrating a HARQ-ACK transmission and reception structure according to various embodiments of the present disclosure.
  • FIG. 19 is a diagram illustrating a bundled HARQ-ACK transmission and reception structure according to various embodiments of the present disclosure.
  • FIG. 20 is a diagram illustrating a transmission / reception structure based on a compact DCI / indication signal according to various embodiments of the present disclosure.
  • 21 is a diagram illustrating a network initial access and subsequent communication process according to various embodiments of the present disclosure.
  • 22 illustrates an example of preamble transmission in an NB-IoT RACH according to various embodiments of the present disclosure.
  • FIG. 23 is a diagram illustrating an example of a DRX operation according to various embodiments of the present disclosure.
  • 24 is a diagram schematically illustrating a method of operating a terminal and a base station according to various embodiments of the present disclosure.
  • 25 is a flowchart illustrating a method of operating a terminal according to various embodiments of the present disclosure.
  • 26 is a flowchart illustrating a method of operating a base station according to various embodiments of the present disclosure.
  • FIG 27 illustrates an apparatus in which various embodiments of the present disclosure may be implemented.
  • 29 illustrates a wireless device that can be applied to various embodiments of the present disclosure.
  • FIG. 30 illustrates another example of a wireless device applied to various embodiments of the present disclosure.
  • 31 illustrates a portable device applied to various embodiments of the present disclosure.
  • FIG. 32 illustrates a vehicle or autonomous driving vehicle applied to various embodiments of the present disclosure.
  • each component or feature may be considered to be optional unless otherwise stated.
  • Each component or feature may be embodied in a form that is not combined with other components or features.
  • some components and / or features may be combined to form the various embodiments of the present disclosure.
  • the order of the operations described in the various embodiments of the present disclosure may be changed. Some components or features of one embodiment may be included in another embodiment or may be replaced with corresponding components or features of another embodiment.
  • the base station has a meaning as a terminal node of the network that directly communicates with the terminal. Certain operations described as performed by the base station in this document may be performed by an upper node of the base station in some cases.
  • various operations performed for communication with a terminal in a network composed of a plurality of network nodes including a base station may be performed by the base station or other network nodes other than the base station.
  • the 'base station' may be replaced by terms such as a fixed station, a Node B, an eNode B (eNB), a gNode B (gNB), an advanced base station (ABS), or an access point. Can be.
  • a terminal may be a user equipment (UE), a mobile station (MS), a subscriber station (SS), or a mobile subscriber station (MSS). ), A mobile terminal, or an advanced mobile station (AMS).
  • UE user equipment
  • MS mobile station
  • SS subscriber station
  • MSS mobile subscriber station
  • AMS advanced mobile station
  • the transmitting end may refer to a fixed and / or mobile node that provides a data service or a voice service
  • the receiving end may mean a fixed and / or mobile node that receives a data service or a voice service. Therefore, in uplink, a mobile station may be a transmitting end and a base station may be a receiving end. Similarly, in downlink, a mobile station may be a receiving end and a base station may be a transmitting end.
  • Various embodiments of the present disclosure may be supported by standard documents disclosed in at least one of the wireless access systems IEEE 802.xx system, 3rd Generation Partnership Project (3GPP) system, 3GPP LTE system, 3GPP 5G NR system and 3GPP2 system.
  • 3GPP 3rd Generation Partnership Project
  • 3GPP LTE / LTE-A system as well as a 3GPP NR system will be described as an example of a wireless access system in which various embodiments of the present disclosure can be used.
  • CDMA code division multiple access
  • FDMA frequency division multiple access
  • TDMA time division multiple access
  • OFDMA orthogonal frequency division multiple access
  • SC-FDMA single carrier frequency division multiple access
  • CDMA may be implemented by a radio technology such as Universal Terrestrial Radio Access (UTRA) or CDMA2000.
  • TDMA may be implemented with wireless technologies such as Global System for Mobile communications (GSM) / General Packet Radio Service (GPRS) / Enhanced Data Rates for GSM Evolution (EDGE).
  • GSM Global System for Mobile communications
  • GPRS General Packet Radio Service
  • EDGE Enhanced Data Rates for GSM Evolution
  • OFDMA may be implemented in a wireless technology such as IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802-20, Evolved UTRA (E-UTRA), or the like.
  • UTRA is part of the Universal Mobile Telecommunications System (UMTS).
  • 3GPP Long Term Evolution (LTE) is part of an Evolved UMTS (E-UMTS) using E-UTRA, and employs OFDMA in downlink and SC-FDMA in uplink.
  • LTE-A (Advanced) system is an improved system of the 3GPP LTE system.
  • a terminal receives information from a base station through downlink (DL) and transmits information to the base station through uplink (UL).
  • the information transmitted and received by the base station and the terminal includes general data information and various control information, and various physical channels exist according to the type / use of the information they transmit and receive.
  • FIG. 1 is a diagram illustrating a physical channel that can be used in various embodiments of the present disclosure and a signal transmission method using the same.
  • an initial cell search operation such as synchronization with a base station is performed (S11).
  • the terminal receives a Primary Synchronization Channel (P-SCH) and a Secondary Synchronization Channel (S-SCH) from the base station, synchronizes with the base station, and obtains information such as a cell ID.
  • P-SCH Primary Synchronization Channel
  • S-SCH Secondary Synchronization Channel
  • the terminal may receive a physical broadcast channel (PBCH) signal from the base station to obtain broadcast information in a cell.
  • PBCH physical broadcast channel
  • the terminal may receive a downlink reference signal (DL RS) in the initial cell search step to confirm the downlink channel state.
  • DL RS downlink reference signal
  • the UE After the initial cell search, the UE receives a physical downlink control channel (PDCCH) and a physical downlink control channel (PDSCH) according to the physical downlink control channel information to provide more detailed system information. It can be obtained (S12).
  • a physical downlink control channel (PDCCH)
  • a physical downlink control channel (PDSCH)
  • the terminal may perform a random access procedure (S13 to S16) to complete the access to the base station.
  • the UE transmits a preamble through a physical random access channel (PRACH) (S13), and a RAR (preamble) for the preamble through a physical downlink control channel and a corresponding physical downlink shared channel. Random Access Response) may be received (S14).
  • the UE transmits a Physical Uplink Shared Channel (PUSCH) using scheduling information in the RAR (S15), and a contention resolution procedure such as receiving a physical downlink control channel signal and a corresponding physical downlink shared channel signal (S16).
  • PUSCH Physical Uplink Shared Channel
  • the UE After performing the above-described procedure, the UE subsequently receives a physical downlink control channel signal and / or a physical downlink shared channel signal (S17) and a physical uplink shared channel (PUSCH) as a general uplink / downlink signal transmission procedure.
  • a transmission (Uplink Shared Channel) signal and / or a Physical Uplink Control Channel (PUCCH) signal may be transmitted (S18).
  • UCI uplink control information
  • HARQ-ACK / NACK Hybrid Automatic Repeat and reQuest Acknowledgement / Negative-ACK
  • SR Scheduling Request
  • CQI Channel Quality Indication
  • PMI Precoding Matrix Indication
  • RI Rank Indication
  • UCI is periodically transmitted through PUCCH, but may be transmitted through PUSCH when control information and data should be transmitted at the same time.
  • the UE may transmit the UCI aperiodically through the PUSCH according to the request / instruction of the network.
  • FIG. 2 is a diagram illustrating a radio frame structure based on an LTE system to which various embodiments of the present disclosure are applicable.
  • the LTE system supports frame type 1 for frequency division duplex (FDD), frame type 2 for time division duplex (TDD), and frame type 3 for unlicensed cell (UCell).
  • FDD frequency division duplex
  • TDD time division duplex
  • Uell unlicensed cell
  • SCells secondary cells
  • PCell primary cell
  • time resources eg, subframes, slots, and subslots
  • TU time unit
  • the type 1 frame structure can be applied to both full duplex Frequency Division Duplex (FDD) systems and half duplex FDD systems.
  • FDD Frequency Division Duplex
  • the downlink radio frame is defined as ten 1 ms subframes (SFs).
  • the subframe includes 14 or 12 symbols according to a cyclic prefix (CP). If a normal CP is used, the subframe includes 14 symbols. If extended CP is used, the subframe includes 12 symbols.
  • CP cyclic prefix
  • the symbol may mean an OFDM (A) symbol or an SC-FDM (A) symbol according to a multiple access scheme.
  • the symbol may mean an OFDM (A) symbol in downlink and an SC-FDM (A) symbol in uplink.
  • the OFDM (A) symbol is referred to as a Cyclic Prefix-OFDM (A) symbol
  • the SC-FDM (A) symbol is a DFT-s-OFDM (A) (Discrete Fourier Transform-spread-OFDM) symbol. (A)) may be referred to as a symbol.
  • One subframe may be defined as one or more slots according to SCS (Subcarrier Spacing) as follows.
  • SCS Subcarrier Spacing
  • subframe #i is defined as one 1ms slot # 2i.
  • Table 1 illustrates the subslot configuration in one subframe (usually CP).
  • Type 2 frame structure is applied to the TDD system.
  • the type 2 frame structure consists of two half frames.
  • the half frame includes 4 (or 5) general subframes and 1 (or 0) special subframes.
  • the general subframe is used for uplink or downlink according to the UL-Downlink configuration.
  • the subframe consists of two slots.
  • Table 2 illustrates a subframe configuration in a radio frame according to the UL-DL configuration.
  • D represents a DL subframe
  • U represents a UL subframe
  • S represents a special subframe.
  • the special subframe includes a downlink pilot time slot (DwPTS), a guard period (GP), and an uplink pilot time slot (UpPTS).
  • DwPTS is used for initial cell search, synchronization or channel estimation at the terminal.
  • UpPTS is used for channel estimation at the base station and synchronization of uplink transmission of the terminal.
  • the guard period is a period for removing interference generated in the uplink due to the multipath delay of the downlink signal between the uplink and the downlink.
  • Table 3 illustrates the configuration of the special subframe.
  • X is set by higher layer signaling (eg, RRC (Radio Resource Control) signaling, etc.) or is given as 0.
  • RRC Radio Resource Control
  • FIG. 3 is a diagram illustrating a slot structure based on an LTE system to which various embodiments of the present disclosure are applicable.
  • one slot includes a plurality of OFDM symbols in a time domain and a plurality of resource blocks (RBs) in a frequency domain.
  • the symbol may mean a symbol section.
  • the slot structure may be represented by a resource grid composed of N DL / UL RB ⁇ RB sc subcarriers and N DL / UL symb symbols.
  • N DL RB represents the number of RBs in the downlink slot
  • N UL RB represents the number of RBs in the UL slot.
  • N DL RB and N UL RB depend on the DL bandwidth and the UL bandwidth, respectively.
  • N DL symb represents the number of symbols in the DL slot
  • N UL symb represents the number of symbols in the UL slot
  • N RB sc represents the number of subcarriers constituting the RB.
  • the number of symbols in the slot can be changed in various ways according to the length of the SCS, CP (see Table 1). For example, one slot includes 7 symbols in the case of a normal CP, but one slot includes 6 symbols in the case of an extended CP.
  • RB is defined as N DL / UL symb (eg, 7) consecutive symbols in the time domain, and N RB sc (eg, 12) consecutive subcarriers in the frequency domain.
  • the RB may mean a physical resource block (PRB) or a virtual resource block (VRB), and the PRB and the VRB may be mapped one-to-one.
  • Two RBs, one located in each of two slots of a subframe, may be referred to as an RB pair.
  • Two RBs constituting the RB pair may have the same RB number (or also referred to as an RB index).
  • a resource composed of one symbol and one subcarrier is called a resource element (RE) or tone.
  • RE resource element
  • Each RE in a resource grid may be uniquely defined by an index pair (k, l) in a slot.
  • k is an index given from 0 to N DL / UL RB NN RB sc ⁇ 1 in the frequency domain
  • l is an index given from 0 to N DL / UL symb ⁇ 1 in the time domain.
  • FIG. 4 is a diagram illustrating an uplink subframe structure based on an LTE system to which various embodiments of the present disclosure are applicable.
  • one subframe 400 includes two 0.5 ms slots 401.
  • Each slot is composed of a plurality of symbols 402 and one symbol corresponds to one SC-FDMA symbol.
  • the RB 543 is a resource allocation unit corresponding to 12 subcarriers in the frequency domain and one slot in the time domain.
  • the structure of an uplink subframe is largely divided into a data region 404 and a control region 405.
  • the data area means a communication resource used in transmitting data such as voice and packet transmitted from each terminal, and includes a PUSCH (Physical Uplink Shared Channel).
  • the control region means a communication resource used to transmit an uplink control signal, for example, a downlink channel quality report from each user equipment, a reception ACK / NACK for the downlink signal, an uplink scheduling request, and a PUCCH (Physical Uplink). Control Channel).
  • the SRS Sounding Reference Signal
  • SC-FDMA symbol located last on the time axis in one subframe.
  • FIG. 5 is a diagram illustrating a downlink subframe structure based on an LTE system to which various embodiments of the present disclosure are applicable.
  • up to three (or four) OFDM (A) symbols located in front of the first slot in a subframe correspond to a control region to which a downlink control channel is allocated.
  • the remaining OFDM (A) symbol corresponds to a data region to which a PDSCH is allocated, and the basic resource unit of the data region is RB.
  • the downlink control channel includes a Physical Control Format Indicator Channel (PCFICH), a Physical Downlink Control Channel (PDCCH), a Physical Hybrid-ARQ Indicator Channel (PHICH), and the like.
  • the PCFICH is transmitted in the first OFDM symbol of a subframe and carries information about the number of OFDM symbols (ie, the size of the control region) used for transmission of control channels within the subframe.
  • the PHICH is a response channel for uplink transmission and carries a HARQ (Hybrid Automatic Repeat Request) acknowledgment (ACK) / Negative-Acknowledgement (NACK) signal.
  • Control information transmitted through the PDCCH is referred to as downlink control information (DCI).
  • DCI includes uplink resource allocation information, downlink resource allocation information, or an uplink transmission (Tx) power control command for a certain terminal group.
  • FIG. 6 is a diagram illustrating a radio frame structure based on an NR system to which various embodiments of the present disclosure are applicable.
  • the NR system can support a number of numerologies.
  • the numerology may be defined by subcarrier spacing (SCS) and cyclic prefix (CP) overhead.
  • the plurality of subcarrier spacings may be derived by scaling the basic subcarrier spacing to an integer N (or ⁇ ).
  • N or ⁇
  • the used numerology may be selected independently of the cell's frequency band.
  • various frame structures according to a number of numerologies may be supported.
  • OFDM orthogonal frequency division multiplexing
  • NR supports a number of pneumatics (eg, subcarrier spacing) to support various 5G services. For example, if the subcarrier spacing is 15 kHz, it supports wide area in traditional cellular bands, and if the subcarrier spacing is 30 kHz / 60 kHz, it is dense-urban, lower latency. Latency and wider carrier carrier bandwidth are supported, and when the subcarrier spacing is 60 kHz or higher, it supports a bandwidth greater than 24.25 GHz to overcome phase noise.
  • pneumatics eg, subcarrier spacing
  • the NR frequency band is defined by two types of frequency ranges, FR1 and FR2.
  • FR1 is in the sub 6 GHz range
  • FR2 is in the above 6 GHz range, which can mean millimeter wave (mmWave).
  • mmWave millimeter wave
  • Table 5 below illustrates the definition of the NR frequency band.
  • T c 1 / ( ⁇ f max * N f ), which is the basic time unit for NR. .
  • ⁇ f max 480 * 10 3 Hz
  • N f 4096 which is a value related to a fast Fourier transform (FFT) or an inverse fast Fourier transform (IFFT) size.
  • FFT fast Fourier transform
  • IFFT inverse fast Fourier transform
  • the slots are n ⁇ s ⁇ ⁇ 0,... In increasing order within the subframe.
  • N slot ⁇ frame -1 ⁇ .
  • One slot is composed of N ⁇ symb consecutive OFDM symbols, and N ⁇ symb depends on a cyclic prefix (CP).
  • CP cyclic prefix
  • the start of slot n ⁇ s in a subframe is aligned in time with the start of OFDM symbol n ⁇ s * N ⁇ symb within the same subframe.
  • Table 6 shows the number of symbols for each slot according to the SCS, the number of slots for each frame and the number of slots for each subframe when the general CP is used, and Table 7 shows the number of slots for each SCS when the extended CSP is used. It indicates the number of symbols, the number of slots per frame, and the number of slots per subframe.
  • N slot symb represents the number of symbols in a slot
  • N frame ⁇ slot represents the number of slots in a frame
  • N subframe ⁇ slot represents the number of slots in a subframe
  • OFDM (A) numerology eg, SCS, CP length, etc.
  • a numerology eg, SCS, CP length, etc.
  • the (absolute time) section of a time resource eg, SF, slot, or TTI
  • a time unit TU
  • one subframe may include four slots.
  • mini-slot may include two, four or seven symbols or may include more or fewer symbols.
  • FIG. 7 illustrates a slot structure based on an NR system to which various embodiments of the present disclosure are applicable.
  • one slot may include a plurality of symbols in the time domain.
  • one slot may include seven symbols in the case of a normal CP, and one slot may include six symbols in the case of an extended CP.
  • the carrier may include a plurality of subcarriers in the frequency domain.
  • Resource block is defined as a plurality of consecutive subcarriers (eg, 12) in the frequency domain.
  • the bandwidth part (BWP) is defined as a plurality of consecutive (P) RBs in the frequency domain, and may correspond to one numerology (eg, SCS, CP length, etc.).
  • numerology eg, SCS, CP length, etc.
  • the carrier may include up to N (eg 5) BWPs. Data communication is performed through an activated BWP, and only one BWP may be activated by one UE. Each element in the resource grid is referred to as a resource element (RE), one complex symbol may be mapped.
  • RE resource element
  • FIG. 8 is a diagram illustrating a self-contained slot structure to which various embodiments of the present disclosure are applicable.
  • the independent slot structure is a slot structure in which a downlink control channel, a downlink / uplink data, and an uplink control channel can be included in one slot. Can be.
  • the base station and the UE may sequentially perform DL transmission and UL transmission in one slot, and may transmit and receive DL data and transmit and receive UL ACK / NACK for the DL data in the one slot.
  • this structure reduces the time taken to retransmit data in the event of a data transmission error, thereby minimizing the delay of the final data transfer.
  • a time gap of a certain length is required for the base station and the UE to switch from the transmission mode to the reception mode or from the reception mode to the transmission mode.
  • some OFDM symbols at the time of switching from DL to UL in the independent slot structure may be set to a guard period (GP).
  • the independent slot structure includes both the DL control region and the UL control region.
  • the control regions may be selectively included in the independent slot structure.
  • the independent slot structure according to various embodiments of the present disclosure may include a case in which both the DL control region and the UL control region are included as well as the case in which both the DL control region and the UL control region are included as shown in FIG. 8. .
  • one slot may be configured in the order of a DL control area / DL data area / UL control area / UL data area, or may be configured in the order of a UL control area / UL data area / DL control area / DL data area.
  • the PDCCH may be transmitted in the DL control region, and the PDSCH may be transmitted in the DL data region.
  • PUCCH may be transmitted in the UL control region, and PUSCH may be transmitted in the UL data region.
  • Downlink Control Information for example, DL data scheduling information, UL data scheduling information, and the like may be transmitted in the PDCCH.
  • DCI Downlink Control Information
  • uplink control information for example, positive acknowledgment / negative acknowledgment (ACK / NACK) information, channel state information (CSI) information, and scheduling request (SR) for DL data may be transmitted.
  • ACK / NACK positive acknowledgment / negative acknowledgment
  • CSI channel state information
  • SR scheduling request
  • the PDSCH carries downlink data (eg, DL-shared channel transport block, DL-SCH TB), and modulation methods such as Quadrature Phase Shift Keying (QPSK), 16 Quadrature Amplitude Modulation (QAM), 64 QAM, and 256 QAM are used. Apply.
  • a codeword is generated by encoding the TB.
  • the PDSCH can carry up to two codewords. Scrambling and modulation mapping are performed for each codeword, and modulation symbols generated from each codeword are mapped to one or more layers. Each layer is mapped to a resource together with a DMRS (Demodulation Reference Signal) to generate an OFDM symbol signal, and is transmitted through a corresponding antenna port.
  • DMRS Demodulation Reference Signal
  • the PDCCH carries downlink control information (DCI) and a QPSK modulation method is applied.
  • DCI downlink control information
  • One PDCCH is composed of 1, 2, 4, 8, 16 CCEs (Control Channel Elements) according to an aggregation level (AL).
  • One CCE consists of six Resource Element Groups (REGs).
  • REG is defined by one OFDM symbol and one (P) RB.
  • FIG. 9 is a diagram illustrating one REG structure based on an NR system to which various embodiments of the present disclosure are applicable.
  • D represents a resource element (RE) to which DCI is mapped
  • R represents an RE to which DMRS is mapped.
  • DMRS is mapped to the 1st, 5th, 9th RE in the frequency domain direction in one symbol.
  • CORESET is defined as a set of REGs with a given neurology (eg, SCS, CP length, etc.). A plurality of OCRESET for one terminal may be overlapped in the time / frequency domain.
  • CORESET may be set through system information (eg, MIB) or UE-specific higher layer (eg, Radio Resource Control, RRC, layer) signaling.
  • system information eg, MIB
  • UE-specific higher layer eg, Radio Resource Control, RRC, layer
  • RRC Radio Resource Control
  • the number of RBs and the number of symbols (up to three) constituting the CORESET may be set by higher layer signaling.
  • PUSCH carries uplink data (eg, UL-shared channel transport block, UL-SCH TB) and / or uplink control information (UCI), and uses a Cyclic Prefix-Orthogonal Frequency Division Multiplexing (CP-OFDM) waveform. Or based on a Discrete Fourier Transform-spread-Orthogonal Frequency Division Multiplexing (DFT-s-OFDM) waveform.
  • DFT-s-OFDM Discrete Fourier Transform-spread-Orthogonal Frequency Division Multiplexing
  • the UE when transform precoding is not possible (eg, transform precoding is disabled), the UE transmits a PUSCH based on a CP-OFDM waveform, and when conversion precoding is possible (eg, transform precoding is enabled), the UE is CP-OFDM.
  • PUSCH may be transmitted based on the waveform or the DFT-s-OFDM waveform.
  • PUSCH transmissions are dynamically scheduled by UL grants in DCI or semi-static based on higher layer (eg RRC) signaling (and / or Layer 1 (L1) signaling (eg PDCCH)). Can be scheduled (configured grant).
  • PUSCH transmission may be performed based on codebook or non-codebook.
  • the PUCCH carries uplink control information, HARQ-ACK and / or scheduling request (SR), and is divided into Short PUCCH and Long PUCCH according to the PUCCH transmission length.
  • Table 8 illustrates the PUCCH formats.
  • PUCCH format 0 carries a maximum of 2 bits of UCI, and is mapped and transmitted based on a sequence. Specifically, the terminal transmits one sequence of the plurality of sequences through the PUCCH of PUCCH format 0 to transmit a specific UCI to the base station. The UE transmits the PUCCH having PUCCH format 0 in the PUCCH resource for the SR configuration only when transmitting the positive SR.
  • PUCCH format 1 carries a UCI of up to two bits in size, and modulation symbols are spread by an orthogonal cover code (OCC) (set differently depending on whether frequency hopping) in the time domain.
  • OCC orthogonal cover code
  • the DMRS is transmitted in a symbol in which a modulation symbol is not transmitted (that is, transmitted by time division multiplexing (TDM)).
  • PUCCH format 2 carries a UCI having a bit size larger than 2 bits, and modulation symbols are transmitted by DMRS and Frequency Division Multiplexing (FDM).
  • the DM-RS is located at symbol indexes # 1, # 4, # 7 and # 10 in a given resource block with a density of 1/3.
  • PN Pulseudo Noise sequence is used for the DM_RS sequence.
  • Frequency hopping may be activated for two symbol PUCCH format 2.
  • PUCCH format 3 is not UE multiplexed in the same physical resource blocks and carries a UCI of a bit size larger than 2 bits.
  • the PUCCH resource of PUCCH format 3 does not include an orthogonal cover code.
  • the modulation symbol is transmitted after being time division multiplexed (DMD) with DMRS.
  • PUCCH format 4 supports multiplexing up to 4 terminals in the same physical resource block, and carries UCI of a bit size larger than 2 bits.
  • the PUCCH resource in PUCCH format 3 includes an orthogonal cover code.
  • the modulation symbol is transmitted after being time division multiplexed (DMD) with DMRS.
  • NB-IoT Nearband Internet of Things
  • NB-IoT represents a narrowband IoT technology that supports low-power wide area networks through existing wireless communication systems (eg, LTE, NR).
  • NB-IoT may refer to a system for supporting low complexity and low power consumption through a narrowband.
  • the NB-IoT system uses OFDM parameters such as subcarrier spacing (SCS) in the same manner as the existing system, and thus does not need to allocate an additional band separately for the NB-IoT system.
  • SCS subcarrier spacing
  • one PRB of the existing system band can be allocated for NB-IoT. Since the NB-IoT terminal recognizes a single PRB as each carrier, the PRB and the carrier may be interpreted to have the same meaning in the description of the NB-IoT.
  • the description of the NB-IoT mainly describes the case that is applied to the existing LTE system, the following description can be extended to the next-generation system (eg, NR system, etc.).
  • the content related to the NB-IoT herein may be extended to MTC for a similar technical purpose (eg, low-power, low-cost, improved coverage, etc.).
  • NB-IoT may be replaced with other equivalent terms such as NB-LTE, NB-IoT enhancement, enhanced NB-IoT, further enhanced NB-IoT, NB-NR, and the like.
  • NB-IoT supports three modes of operation: in-band, guard-band, and stand-alone, with the same requirements for each mode.
  • In-band mode allocate some of the resources in the LTE band to the NB-IoT.
  • Guard-band mode utilizing the guard frequency band of LTE, the NB-IoT carrier is arranged as close as possible to the edge subcarrier of LTE.
  • NB-IoT UE searches for anchor carrier in 100kHz unit for initial synchronization, and the center frequency of anchor carrier in in-band and guard-band should be located within ⁇ 7.5kHz from 100kHz channel raster. .
  • the anchor carrier may be located only in a particular PRB.
  • NB-IoT supports multi-carriers, and a combination of in-band + in-band, in-band + guard-band, guard band + guard-band, stand-alone + stand-alone can be used.
  • FIG. 10 is a diagram illustrating a frame structure based on an NB-IoT system to which various embodiments of the present disclosure are applicable.
  • the NB-IoT frame structure may be set differently according to the subcarrier spacing (SCS).
  • 10A illustrates a frame structure when the subcarrier interval is 15 kHz
  • FIG. 10B illustrates a frame structure when the subcarrier interval is 3.75 kHz.
  • the frame structure of FIG. 10 (a) may be used in downlink / uplink
  • the frame structure of FIG. 10 (b) may be used only in uplink.
  • the NB-IoT frame structure for the 15 kHz subcarrier interval may be set to be the same as the frame structure of legacy systems (ie, LTE systems) (see FIG. A2). That is, a 10 ms NB-IoT frame may include ten 1 ms NB-IoT subframes, and the 1 ms NB-IoT subframe may include two 0.5 ms NB-IoT slots. Each 0.5ms NB-IoT slot may include seven symbols.
  • the 15 kHz subcarrier interval can be applied to both downlink and uplink.
  • the symbol includes an OFDMA symbol in downlink and an SC-FDMA symbol in uplink.
  • the system band is 1.08 MHz and is defined by 12 subcarriers.
  • the 15kHz subcarrier interval is applied to both the downlink and the uplink, and since the orthogonality with the LTE system is guaranteed, coexistence with the LTE system can be smoothly performed.
  • the 10 ms NB-IoT frame includes five 2 ms NB-IoT subframes, and the 2 ms NB-IoT subframe includes seven symbols and one.
  • Guard period (GP) symbol may include.
  • the 2ms NB-IoT subframe may be represented by an NB-IoT slot or an NB-IoT resource unit (RU).
  • the symbol may include an SC-FDMA symbol.
  • the system band is 1.08 MHz and is defined by 48 subcarriers.
  • the 3.75 kHz subcarrier spacing is applied only to the uplink, and the orthogonality with the LTE system may be degraded, resulting in performance degradation due to interference.
  • FIG. 10 illustrates an NB-IoT frame structure based on an LTE system frame structure, and the illustrated NB-IoT frame structure may be extended to a next-generation system (eg, an NR system).
  • a next-generation system eg, an NR system
  • the subframe interval may be replaced with the subframe interval of Table 6.
  • FIG. 11 is a diagram illustrating transmission of an NB-IoT downlink physical channel / signal in an FDD LTE system to which various embodiments of the present disclosure are applicable.
  • NB-IoT downlink uses an OFDMA scheme having a 15 kHz subcarrier spacing. This provides orthogonality between subcarriers to facilitate coexistence with LTE systems.
  • NB-IoT downlink is provided with physical channels such as narrowband physical broadcast channel (NPBCH), narrowband physical downlink shared channel (NPDSCH), narrowband physical downlink control channel (NPDCCH), narrowband primary synchronization signal (NPSS), narrowband (NSSS) Physical signals such as Primary Synchronization Signal (NRS) and Narrowband Reference Signal (NRS) are provided.
  • NPBCH narrowband physical broadcast channel
  • NPDSCH narrowband physical downlink shared channel
  • NPDCCH narrowband physical downlink control channel
  • NPSS narrowband primary synchronization signal
  • NSSS narrowband Physical signals
  • NRS Primary Synchronization Signal
  • NRS Narrowband Reference Signal
  • the NPBCH delivers MIB-NB (Master Information Block-Narrowband), which is the minimum system information necessary for the NB-IoT terminal to access the system, to the terminal.
  • the NPBCH signal can be transmitted eight times in total to improve coverage.
  • the transport block size (TBS) of the MIB-NB is 34 bits and is newly updated every 640ms TTI period.
  • the MIB-NB includes information such as an operation mode, a system frame number (SFN), a hyper-SFN, a number of cell-specific reference signal (CRS) ports, a channel raster offset, and the like.
  • the NRS is provided as a reference signal for channel estimation required for downlink physical channel demodulation and is generated in the same manner as in LTE.
  • NB-PCID Nearband-Physical Cell ID
  • NCell ID NB-IoT base station ID
  • NPDCCH has the same transmit antenna configuration as NPBCH and carries DCI. Three DCI formats are supported. DCI format N0 includes narrowband physical uplink shared channel (NPUSCH) scheduling information, and DCI formats N1 and N2 include NPDSCH scheduling information. NPDCCH can be repeated up to 2048 times to improve coverage.
  • NPUSCH narrowband physical uplink shared channel
  • the NPDSCH is used to transmit data (eg, TB) of a transport channel such as a downlink-shared channel (DL-SCH) and a paging channel (PCH).
  • a transport channel such as a downlink-shared channel (DL-SCH) and a paging channel (PCH).
  • the maximum TBS is 680 bits, and up to 2048 repetitive transmissions can be used to improve coverage.
  • the downlink physical channel / signal is transmitted through one PRB and supports 15kHz subcarrier spacing / multi-tone transmission.
  • NPSS is transmitted in the sixth subframe of every frame and NSSS is transmitted in the last (eg, tenth) subframe of every even frame.
  • the terminal may acquire frequency, symbol, and frame synchronization using the sync signals NPSS and NSSS, and search for 504 physical cell IDs (ie, base station IDs).
  • NPBCH is transmitted in the first subframe of every frame and carries the NB-MIB.
  • the NRS is provided as a reference signal for downlink physical channel demodulation and is generated in the same manner as in LTE.
  • NB-PCID Physical Cell ID
  • NCell ID NB-IoT base station ID
  • NPDCCH and NPDSCH may be transmitted in the remaining subframes except NPSS / NSSS / NPBCH.
  • NPDCCH and NPDSCH cannot be transmitted together in the same subframe.
  • NPDCCH carries DCI and DCI supports three types of DCI formats.
  • DCI format N0 includes narrowband physical uplink shared channel (NPUSCH) scheduling information
  • DCI formats N1 and N2 include NPDSCH scheduling information.
  • NPDCCH can be repeated up to 2048 times to improve coverage.
  • the NPDSCH is used to transmit data (eg, TB) of a transport channel such as a downlink-shared channel (DL-SCH) and a paging channel (PCH).
  • a transport channel such as a downlink-shared channel (DL-SCH) and a paging channel (PCH).
  • the maximum TBS is 680 bits, and up to 2048 repetitive transmissions can be used to improve coverage.
  • the uplink physical channel includes a narrowband physical random access channel (NPRACH) and an NPUSCH, and supports single-tone transmission and multi-tone transmission.
  • NPRACH narrowband physical random access channel
  • NPUSCH NPUSCH
  • Single-tone transmissions are supported for subcarrier spacings of 3.5 kHz and 15 kHz, and multi-tone transmissions are only supported for 15 kHz subcarrier intervals.
  • FIG. 12 is a diagram illustrating an NPUSCH format to which various embodiments of the present disclosure are applicable.
  • NPUSCH supports two formats. NPUSCH format 1 is used for UL-SCH transmission and the maximum TBS is 1000 bits. NPUSCH format 2 is used for uplink control information transmission such as HARQ ACK signaling. NPUSCH format 1 supports single- / multi-tone transmissions, and NPUSCH format 2 supports only single-tone transmissions. For single-tone transmission, pi / 2-BPSK (Binary Phase Shift Keying) and pi / 4-QPSK (Quadrature Phase Shift Keying) are used to reduce the Peer-to-Average Power Ratio (PAPR). The NPUSCH may have a different number of slots occupied by one resource unit (RU) according to resource allocation.
  • RU resource unit
  • the RU represents the smallest resource unit to which a TB is mapped, and consists of N UL symb * N UL slots contiguous SC-FDMA symbols in the time domain and N RU sc contiguous subcarriers in the frequency domain.
  • N UL symb represents the number of SC-FDMA symbols in the slot
  • N UL slots represents the number of slots
  • N RU sc represents the number of subcarriers constituting the RU.
  • Table 9 illustrates the configuration of an RU according to NPUSCH format and subcarrier spacing.
  • the NPUSCH format and SCS supported depend on the uplink-downlink configuration. See Table 9 for uplink-downlink configuration.
  • Scheduling information for transmitting UL-SCH data (eg, UL-SCH TB) is included in DCI format NO, and DCI format NO is transmitted through NPDCCH.
  • the DCI format NO includes information about the start time of the NPUSCH, the number of repetitions, the number of RUs used for TB transmission, the number of subcarriers and resource positions in the frequency domain, MCS, and the like.
  • DMRSs are transmitted in one or three SC-FDMA symbols per slot according to the NPUSCH format.
  • DMRS is multiplexed with data (e.g. TB, UCI) and is only transmitted in the RU that contains the data transmission.
  • FIG. 13 illustrates an operation when a multi-carrier is configured in an FDD NB-IoT to which various embodiments of the present disclosure are applicable.
  • DL / UL anchor-carrier is basically configured, and DL (and UL) non-anchor carrier may be further configured.
  • the RRCConnectionReconfiguration may include information about the non-anchor carrier. If a DL non-anchor carrier is configured, the terminal receives data only from the DL non-anchor carrier. On the other hand, synchronization signals NPSS and NSSS, broadcast signals MIB and SIB, and paging signals are provided only at anchor-carriers. If the DL non-anchor carrier is configured, the terminal listens to only the DL non-anchor carrier while in the RRC_CONNECTED state.
  • the terminal transmits data only on the UL non-anchor carrier, and simultaneous transmission on the UL non-anchor carrier and the UL anchor-carrier is not allowed.
  • the terminal returns to the anchor-carrier.
  • UE1 is configured only with an anchor-carrier
  • UE2 is additionally configured with a DL / UL non-anchor carrier
  • UE3 is configured with an additional DL non-anchor carrier. Accordingly, carriers to which data is transmitted / received in each UE are as follows.
  • UE1 data reception (DL anchor-carrier), data transmission (UL anchor-carrier)
  • UE2 data reception (DL non-anchor-carrier), data transmission (UL non-anchor-carrier)
  • UE3 data reception (DL non-anchor-carrier), data transmission (UL anchor-carrier)
  • the NB-IoT terminal cannot simultaneously perform transmission and reception, and transmission / reception operations are limited to one band each. Therefore, even if the multi-carrier is configured, the terminal requires only one transmit / receive chain in the 180 kHz band.
  • Table 10 illustrates system information defined in the NB-IoT.
  • the system information acquisition / modification process is performed only in the RRC_IDLE state.
  • the UE does not expect to receive the SIB information in the RRC_CONNECTED state.
  • the terminal may be notified through paging or direct indication.
  • the base station may change the terminal to the RRC_IDLE state.
  • the MIB-NB is transmitted through the NPBCH and updated every 640ms period. MIB-NB is first transmitted in subframe # 0 of a radio frame satisfying SFN mod 0, and is transmitted in subframe # 0 of every radio frame. The MIB-NB is transmitted through eight independently decodable blocks, and each block is repeatedly transmitted eight times.
  • Table 11 illustrates the field configuration of the MIB-NB.
  • SIB1-NB is transmitted through NPDSCH and has a period of 2056 ms. SIB1-NB is transmitted in subframe # 4 of even-numbered radio frames (ie, eight radio frames) within 16 consecutive radio frames.
  • the index of the first radio frame in which SIB1-NB is transmitted is derived according to the NPDSCH repetition number (Nrep) and PCID. Specifically, when Nrep is 16 and PCID is 2n, 2n + 1, the index of the first radio frame is ⁇ 0, 1 ⁇ , Nrep is 8, and PCID is 2n, 2n + 1.
  • the index of the first radio frame corresponding to the PCID and the odd PCID is ⁇ 0, 16 ⁇ .
  • SIB1-NB repeats Nrep times within 2560ms and is evenly distributed within 2560ms. TBS and Nrep of SIB1-NB are indicated by SystemInformationBlockType1-NB in MIB-NB.
  • Table 12 shows the number of repetitions according to SystemInformationBlockType1-NB.
  • SI messages ie, information after the SIB2-NB
  • SI-window a periodically occurring time domain window
  • Scheduling information of the SI message is provided by the SIB1-NB.
  • Each SI message is associated with one SI-window, and the SI-windows of different SI messages do not overlap each other. That is, only a corresponding SI is transmitted in one SI-window.
  • the lengths of all SI windows are the same and can be set.
  • WUS 14 is a diagram illustrating a wake-up signal (WUS) signal transmission according to various embodiments of the present disclosure.
  • the NB-IoT terminal and the bandwidth reduced low complexity / coverage enhancement (BL / CE) terminal may use WUS to reduce power consumption associated with paging monitoring according to cell configuration.
  • WUS bandwidth reduced low complexity / coverage enhancement
  • the WUS may instruct the terminal to receive the paging in the cell by monitoring the MPDCCH or NPDCCH.
  • PO means a time resource / interval (eg, subframe, slot) in which a PDCCH scrambled with P-RNTI can be transmitted for paging.
  • One or a plurality of PO (s) is included in a paging frame (PF), and the PF may be periodically set based on the UE ID.
  • the UE ID may be determined based on the International Mobile Subscriber Identity (IMSI) of the terminal.
  • IMSI International Mobile Subscriber Identity
  • paging hyper-frames PH
  • the PTW is defined in the PH, and the UE monitors the PO (s) in the PF in the PTW.
  • the UE may monitor N paging occasions later to receive a paging message.
  • the paging operation of the mobility management entity does not know that the base station uses WUS.
  • the WUS may be transmitted in a "Configured maximum WUS duration" (hereinafter, referred to as a WUS window) before the PO.
  • the UE may expect to repeat WUS transmission in the WUS window, but the actual number of WUS transmissions may be less than the maximum number of WUS transmissions in the WUS window. For example, the number of WUS repetitions may be small for a terminal in good coverage.
  • the resource / chance to which a WUS can be transmitted in the WUS window is referred to as a WUS resource.
  • the WUS resource may be defined as a plurality of consecutive OFDM symbols and a plurality of consecutive subcarriers.
  • the WUS resource may be defined as a plurality of consecutive OFDM symbols and a plurality of consecutive subcarriers in a subframe or slot.
  • the WUS resource may be defined as 14 consecutive OFDM symbols and 12 consecutive subcarriers.
  • a gap exists between the WUS window and the PO, and the terminal does not monitor the WUS in the gap.
  • the terminal may monitor a paging related signal in one or more POs associated with the WUS (window).
  • the UE in the RRC_IDLE state may receive paging in the anchor carrier or the non-anchor carrier based on the system information.
  • Various embodiments of the present disclosure provide a method of scheduling multiple transmission / transport blocks (multi-TB), particularly in a system in which repetition is applied in physical signal / channel transmission. And devices that support it.
  • Narrowband radio frequency or bandwidth reduced may cause problems in terms of coverage.
  • an iterative transmission method is introduced to increase coverage.
  • the repetitive transmission method may mean a method of repeatedly transmitting the same physical signal / channel by a predetermined time unit such as a symbol and / or a slot and / or a subframe.
  • a data repetitive transmission method using multi-subframe repetition has been introduced as a method for increasing coverage.
  • the terminal / base station may combine and detect / decode physical signals / channels transmitted in succession. For example, the terminal / base station can improve discovery / decoding performance by applying a method such as symbol level combining to a physical signal / channel transmitted continuously.
  • the gain through the above-described method such as symbol level combining may be obtained when the mobility of the terminal is very low or very low, and thus the radio environment between symbols or subframes in which repeated transmission is performed is almost constant. On the contrary, when a phenomenon such as deep fading occurs, for example, the reception performance of a physical signal / channel repeatedly transmitted may be affected for a long time.
  • time domain resource consumption is increased by repeatedly transmitting the physical signal / channel, a resource cost problem and a scheduling restriction problem between different terminals may occur from a base station perspective.
  • the coverage enhancement effect also increases, but conversely, since time domain resources consumed also increase, resource efficiency decreases and a problem of scheduling between different terminals may occur.
  • Various embodiments of the present disclosure may relate to various methods that may be applied when transmission of multiple transport block structures is used, particularly in systems where repetitive transmission is applied to physical signal / channel transmission.
  • Various embodiments of the present disclosure may relate to various methods that may be applied when one or more transport blocks may be indicated through one downlink control information (DCI).
  • DCI downlink control information
  • Various embodiments of the present disclosure may be applied even when multiple downlink control information (multiple DCI) is used for multiple transport block transmission or when transmission is performed through a pre-configured resource without downlink control information. have.
  • multiple DCI multiple downlink control information
  • the names of the respective physical channels supported by the NB-IoT system and the MTC system may be prefixed with "N-" or "M-" in front of the names of the physical channels of the legacy system.
  • prefixed channels are channels that are used similarly to the physical channels of legacy systems and can be clearly understood by those of ordinary skill in the art.
  • this prefix may be omitted, and may be mixed with the names of the physical channels of the legacy system.
  • various embodiments of the present disclosure have been described based on names of physical channels of a legacy system, and the above description will be clearly understood by those skilled in the art.
  • FIG. 15 is a diagram illustrating operations of a terminal and a base station in a wireless communication system to which various embodiments of the present disclosure are applicable.
  • a base station may transmit downlink control information (DCI) for scheduling a multi-transport block (TB) to a terminal, and the terminal may transmit the same.
  • DCI downlink control information
  • TB multi-transport block
  • the base station may transmit a multiple transport block scheduled by the DCI to the terminal, and the terminal may receive it based on the DCI (S1503).
  • the terminal may transmit a multiple transport block scheduled by DCI to the base station, and the base station may receive it (S1503).
  • one DCI may include a DL grant (DL grant or DL assignment) for scheduling a plurality of transport blocks to be transmitted in downlink, and the terminal is included in one DCI.
  • the plurality of transport blocks may be received from the base station based on the received DL grant.
  • one DCI may include a UL grant for scheduling a plurality of transport blocks to be transmitted in uplink, and the terminal includes a UL grant included in one DCI.
  • the plurality of transport blocks can be transmitted to the base station based on.
  • a gap may be set between time resources to which each transport block included in the multiple transport blocks is mapped.
  • Various embodiments of the present disclosure may relate to a method in which multiple transport block transmissions are used for a transmit / receive structure using a HARQ process.
  • a transmit / receive structure (using a HARQ process) based on a HARQ (Hybrid Automatic Repeat and request) process means that a terminal and a base station assign a HARQ process number to each transport block, It may refer to a transmission / reception structure capable of retransmission (to used).
  • HARQ Hybrid Automatic Repeat and request
  • a gap may mean a time axis interval between each transport block and / or time domain resources to which sub blocks constituting the transport block are mapped, and the size thereof may be a time unit ( For example, subframes / slots / symbols, etc.).
  • a gap may be defined as an interval between time intervals (resources) to which each PDSCH transport block is mapped.
  • gaps may be replaced with terms that may be understood to have similar meanings to one of ordinary skill in the art, such as intervals, intervals, gaps, and the like.
  • the size of the gap may be related to a time axis distance between the end of the time interval in which the transport block configured before the gap is transmitted and the start of the time interval in which the transport block configured after the gap is transmitted.
  • the gap may have a constant (time unit) size and may be set by constant signaling indicating on / off.
  • constant signaling may be defined indicating the size of the gap.
  • the signaling may be SIB signaling and / or RRC signaling and / or DCI signaling and the like.
  • the size of the gap (or the presence or absence of the gap) may be set according to a predetermined condition without explicit signaling.
  • 16 is a diagram illustrating a transmission / reception structure based on multiple transport blocks according to various embodiments of the present disclosure.
  • the terminal when the terminal detects a DCI scheduling a multiple HARQ process, the terminal may assume a structure in which a transport block corresponding to each HARQ process number is sequentially transmitted.
  • each transport block is composed of a plurality of time domain resources (eg, subframes and / or slots and / or symbols)
  • the terminal transmits the next transmission after all time domain resources constituting one transport block are transmitted.
  • a transport block in case of uplink, may be transmitted from a terminal based on a PUSCH (or (N) PUSCH format 1).
  • a transport block may be transmitted from a base station based on the PDSCH.
  • FIG. 16 an example in which a multiple transport block transmission / reception structure using a HARQ process (2-HARQ process) according to various embodiments of the present disclosure is applied to an NB-IoT system is illustrated.
  • one DCI may schedule two PDSCH transport blocks associated with each HARQ process.
  • the terminal receiving the DCI may recognize / assume or confirm that numbers corresponding to the HARQ process numbers are sequentially assigned to each transport block.
  • the UE may recognize / assume or confirm that the first transport block is a PDSCH transport block corresponding to HARQ # 1 and the second transport block is a PDSCH transport block corresponding to HARQ # 2.
  • a PDSCH transport block corresponding to HARQ # 1 and / or a PDSCH transport block corresponding to HARQ # 2 may include one or more (or plural) time domain resources, eg, subframes and / or slots and / or symbols.
  • the terminal may decode each PDSCH based on combining. For example, after the transmission of all the transport blocks scheduled by the DCI is completed (for example, after the PDSCH transport block corresponding to HARQ # 2 is received), the UE transmits an ACK / NACK based on each HARQ process. Can be.
  • one DCI may schedule two PUSCH transport blocks associated with each HARQ process.
  • the terminal receiving the DCI may sequentially assign a number corresponding to each HARQ process number to each scheduled transmission block, or may recognize / assume or confirm that the terminal is assigned.
  • the UE sequentially assigns HARQ process numbers such that the first transport block is a PUSCH transport block corresponding to HARQ # 1, and the second transport block is a PUSCH transport block corresponding to HARQ # 2, or recognizes or assumes that it has been assigned. You can check it.
  • a PUSCH transport block corresponding to HARQ # 1 and / or a PUSCH transport block corresponding to HARQ # 2 may include one or more (or plural) time domain resources, eg, subframes and / or slots and / or symbols. It can be configured as. For example, when repeated transmission using time domain resources is applied to each PUSCH transport block composed of a plurality of time domain resources, the base station may decode each PUSCH received from the terminal based on combining.
  • a gap of a predetermined size may exist between a first PDSCH transport block corresponding to HARQ # 1 and a second PDSCH transport block corresponding to HARQ # 2.
  • the base station may transmit the second PDSCH transport block with a gap.
  • a gap of a predetermined size may be provided between transport blocks to ensure a processing time of a terminal.
  • a bandwidth limited / coverage enhanced (BL / CE) terminal since combining is applied to a plurality of time domain resources to decode each PDSCH transport block as described above, it may take time accordingly.
  • a gap of a certain size may be provided between each transport block to ensure a time required for the UE to perform combining.
  • a gap of a certain size may exist between each transport block, and the predetermined size may be determined by considering each processing time of the BL / CE terminal. It may be set to a size that can guarantee the time to prepare for the transmission of the block, or complete the reception of each transport block. According to various embodiments of the present disclosure, such a gap may be equally applied to the case of the PUSCH transmitted by the terminal as well as the PDSCH received by the terminal. That is, in the example of FIG. 16, the UE may be configured to set a gap between a PUSCH transport block corresponding to HARQ # 1 and a PUSCH transport block corresponding to HARQ # 2 or to leave a predetermined gap between transport blocks.
  • a gap may be set between each transport block.
  • a gap between transport blocks may be determined based on the transmission length of each transport block or the sum of the transmission lengths of all transport blocks.
  • a transmission length of a plurality of PDSCHs scheduled by one DCI is greater than or equal to a predetermined length, it may be to guarantee a downlink gap for guaranteeing another downlink transmission.
  • an uplink compensation gap for compensating time / frequency error is guaranteed. It may be to.
  • a gap is established or configured between each transport block when the transmission length of each of the plurality of PDSCH (or PUSCH) transport blocks scheduled with one DCI is greater than or equal to a certain length (or a certain threshold).
  • Conditions can be set.
  • a condition may be set such that a gap is set or configured between each transport block when the sum of transmission lengths of the plurality of PDSCHs (or PUSCHs) transport blocks scheduled with one DCI is equal to or greater than a certain length (or a certain threshold). Can be.
  • the terminal may set / configure or set / configure a gap of a predetermined size g1 between two transport blocks.
  • g1 may be configured or configured to ensure a minimum processing time of the terminal.
  • g1 0 may be set.
  • a transmission length of an entire transport block satisfies a condition in which a downlink or uplink gap occurs.
  • the UE may assume that a gap of a predetermined size g2 is set / configured or set / configured between two transport blocks.
  • g2 may be configured or configured to ensure another downlink transmission of the base station.
  • g2 may be configured or configured for the terminal to compensate for time / frequency error.
  • the base station may instruct the terminal to turn on / off gaps between transport blocks. That is, the base station may instruct the terminal on the basis of constant signaling whether a gap is set or configured between transport blocks.
  • the terminal may identify or confirm that a gap is set or configured between transport blocks based on the signaling received from the base station. For example, SIB signaling and / or RRC signaling and / or DCI signaling may be used as the signaling.
  • a terminal that is instructed to set a gap between transport blocks from a base station (or a terminal that is configured to set a gap between transport blocks from a base station) has a predetermined size between two transport blocks of a received downlink signal. It can be assumed that the gap of is set / configured.
  • a terminal that is instructed to set a gap between transport blocks from a base station may have a predetermined size between two transport blocks of an uplink signal to transmit. It can be assumed that the gap of is set / configured, or set / configured.
  • the transmission length of each transport block or the entire transport block does not satisfy the condition that the gap occurs, that is, each If the length of a transport block or the sum of the lengths of each transport block is less than / less than a predetermined threshold, there may be no gap between multiple transport blocks.
  • the size of the gap may be set to 0 when the length of each transport block or the entire transport block does not satisfy a predetermined condition.
  • the base station instructed the terminal that the gap is set or configured between the transport block (for example, indicating that the gap is On). Even in this case, when the sum of the lengths of the multiple transport blocks or the lengths of the multiple transport blocks of the downlink signal received from the base station is equal to or less than a predetermined threshold, or the length or multiple of the multiple transport blocks of the uplink signal to be transmitted by the terminal When the sum of the lengths of the transport blocks is equal to or less than a predetermined threshold, a gap may not be set / configured between multiple transport blocks, or the size of the gap may be set to zero.
  • 17 illustrates a transmission / reception structure based on multiple transport blocks and sub-blocks according to various embodiments of the present disclosure.
  • the terminal when the terminal detects a DCI scheduling a multiple HARQ process, the terminal may assume a structure in which a transport block corresponding to each HARQ process number is sequentially transmitted.
  • each transport block is composed of a plurality of time domain resources (eg, subframes and / or slots and / or symbols), and the time domain resources are used for repetitive transmission, the terminal configures each transport block.
  • a subblock may be formed by dividing time domain resources, and a structure in which subblocks are transmitted in a form in which HARQ process numbers are repeatedly repeated may be expected.
  • a transport block in case of uplink, may be transmitted from a terminal based on a PUSCH (or (N) PUSCH format 1).
  • a transport block may be transmitted from a base station based on the PDSCH.
  • the gap between all subblocks may not be the same size. That is, gaps may exist between transmissions of each subblock, and each gap may have the same size or may have a different size. For example, when an uplink compensation gap or a downlink gap for a specific use is required, the gap for this use may be set or configured to be larger than the gap between other subblocks.
  • FIG. 17 an example of applying a multiple transport block transmission / reception structure using a HARQ process (2-HARQ process) and a sub block according to various embodiments of the present disclosure is illustrated in an NB-IoT system.
  • one DCI may schedule two PDSCH transport blocks.
  • each transport block is composed of a plurality of time domain resources (eg, subframes and / or slots and / or symbols), and the corresponding time domain resources are used for repetitive transmission
  • the terminal may transmit each transport block. It may be recognized / assumed or confirmed that the time domain resource constituting the subframe is composed of a plurality of subblocks.
  • the UE may recognize / assume or confirm that different HARQ process numbers are assigned to each of the plurality of sub blocks. That is, the terminal may recognize / assume or confirm the form in which sub-blocks associated with each HARQ process number are repeatedly received by being crossed. For example, the terminal may transmit ACK / NACK based on each HARQ process after the second transport block is received.
  • the UE has a first transport block divided into two subblocks, a first subblock is a PDSCH subblock corresponding to HARQ # 1, and a second subblock is a PDSCH subblock corresponding to HARQ # 2. Can be recognized or assumed.
  • the UE has a second transport block divided into two subblocks, a first subblock is a PDSCH subblock corresponding to HARQ # 1, and a second subblock is a PDSCH subblock corresponding to HARQ # 2. Can be recognized or assumed.
  • one DCI may schedule two PUSCH transport blocks.
  • each transport block is composed of a plurality of time domain resources (eg, subframes and / or slots and / or symbols), and the corresponding time domain resources are used for repetitive transmission
  • the terminal may transmit each transport block.
  • the time domain resource constituting the P may be configured by a plurality of subblocks, or may be recognized / assumed to be confirmed.
  • the UE may assign a different HARQ process number to each of a plurality of subblocks constituting each transport block, or may recognize / assume or confirm that it has been assigned.
  • the terminal may transmit the PUSCH to the base station in a form in which sub-blocks associated with each HARQ process number are crossed and repeatedly transmitted.
  • the base station may receive each PUSCH transport block composed of a plurality of time domain resources from the terminal and decode based on the combining.
  • the UE is configured or configured such that the first transport block is divided into two subblocks, the first subblock is a PUSCH subblock corresponding to HARQ # 1, and the second subblock is a PUSCH subblock corresponding to HARQ # 2.
  • the UE is configured or configured such that the second transport block is divided into two subblocks, the first subblock is a PUSCH subblock corresponding to HARQ # 1, and the second subblock is a PUSCH subblock corresponding to HARQ # 2. Cognitive / assumed to confirmed.
  • each subblock there may be a gap between each subblock.
  • a gap may exist between the second (or last) PDSCH subblock included in the first PDSCH transport block and the first PDSCH subblock included in the second PDSCH transport block.
  • a gap may exist between the second (or last) PUSCH subblock included in the first PDSCH transport block and the first PDSCH subblock included in the second PDSCH transport block.
  • the gaps between each subblock may have the same size and may have different sizes. That is, gaps may exist between transmissions of each subblock, and each gap may have the same size or may have a different size. For example, when an uplink compensation gap or a downlink gap for a specific use is required, the gap for this use may be set or configured to be larger than the gap between other subblocks.
  • the gap between the other subblocks described above may have a size 0, which may mean that the gap may not be set or configured between certain subblocks.
  • a gap is set or configured between the first PDSCH transport block and the second PDSCH transport block for the purpose of guaranteeing a time for transmission preparation or completion of transmission of each transport block in consideration of the processing time of the UE.
  • the gap may not be set or configured between the subblocks constituting the subblock, or may be set or configured to be smaller than the gap between the transport blocks.
  • a gap is set or configured between the first PUSCH transport block and the second PUSCH transport block in consideration of an uplink compensation gap, and no gap is set or configured between subblocks constituting each transport block, or a transport block. It can be set or configured smaller than the gap between.
  • FIG. 18 is a diagram illustrating a HARQ-ACK transmission and reception structure according to various embodiments of the present disclosure.
  • the user equipment in a downlink transmission / reception in which a base station transmits a plurality of transport blocks to a user equipment, when a gap is set or configured between transport blocks, the user equipment transmits a preceding transport block within a gap period configured between the transport blocks. That is, HARQ-ACK for the transport blocks configured before the gap period may be transmitted.
  • the information configured in the transport block after the gap period may vary according to HARQ-ACK reported in the gap period.
  • the terminal succeeds in receiving transport blocks configured before the gap period (ie, ACK):
  • the terminal may report ACK information to the base station based on the HARQ-ACK channel associated with the gap period.
  • the UE receives the transmission block corresponding to the HARQ process number next to the HARQ process number corresponding to the transport block configured before the gap period. You can expect.
  • the terminal may expect to receive a new transport block having the same HARQ process number as the previous transport block but having different data from the previous transport block.
  • This exemplary embodiment may be advantageous when the base station wants to schedule a larger number of transport block (s) than the number of HARQ processes that the terminal can manage with one DCI.
  • the terminal fails to receive the transport blocks configured before the gap period (ie, NACK):
  • the terminal may transmit or report NACK information to the base station based on (using) the HARQ-ACK channel associated with the gap period.
  • the NACK information may include information requesting to change the transmission parameter of the transport block.
  • the transmission parameter may include a redundancy version (RV), a modulation and coding scheme (MCS), and the like.
  • the UE does not explicitly transmit or report NACK information based on the HARQ-ACK channel associated with the gap period (eg, the corresponding HARQ-ACK channel). May not notify the base station of the NACK by transmitting certain information to the base station.
  • the UE receives a transmission block configured before the gap interval (ie, a transport block corresponding to NACK) or retransmits the information from the base station.
  • a transmission block configured before the gap interval ie, a transport block corresponding to NACK
  • retransmission may be based on the information.
  • the retransmitted transport block may be configured based on the information requesting to change the transmission parameter in the NACK information.
  • HARQ feedback in the above-described gap period may be performed when certain conditions related to the gap period are satisfied. For example, when the time length between the HARQ feedback completion time in the gap period and the transmission block (that is, start time of DCI scheduled for transmission after the gap period) is equal to or greater than a predetermined threshold value or more, HARQ feedback within the gap period may be allowed.
  • the predetermined threshold value to a specific value may be a value at which a time required for generating a next transport block by detecting the HARQ feedback received from the terminal and reflecting the same may be guaranteed.
  • HARQ feedback information may be reflected for the next transport block transmitted after a specific time after HARQ feedback in the above-described gap period. That is, in an exemplary embodiment, when the HARQ feedback end time in the gap period and the start time of the next transport block are longer than a specific time, the HARQ feedback information may be changed in the information of the corresponding transport block. For example, in case of NACK, a transport block configured before a gap period may be retransmitted, and in case of ACK, a transport block corresponding to a next HARQ process number may be transmitted.
  • FIG. 18 an example in which a HARQ-ACK feedback method is applied to an NB-IoT system in a multiple transport block transmission / reception structure using a HARQ process (2-HARQ process) according to various embodiments of the present disclosure is illustrated.
  • the multiple transport block transmit / receive structure is described in 3.1.1. It may be configured according to the transmission and reception structure based on the HARQ process according to various embodiments of the present disclosure described above in the section.
  • HARQ-ACK for HARQ # 1 may be transmitted within a gap configured between a PDSCH transport block corresponding to HARQ # 1 and a PDSCH transport block corresponding to HARQ # 2. That is, HARQ-ACK for HARQ # 1 may be transmitted at the position of A / N 1 in FIG. 18.
  • the base station when HARQ-ACK received from the UE at the position of A / N 1 is ACK, the base station assumes that transmission of the PDSCH transport block corresponding to HARQ # 1 is completed and corresponds to HARQ # 2. Transmission of the PDSCH transport block may begin.
  • the base station may retransmit the PDSCH corresponding to HARQ # 1 to the terminal at the next transport block transmission timing.
  • the HARQ-ACK associated with the HARQ process number associated with the immediately preceding PDSCH transport block may be reported at the location of A / N 2.
  • the base station may transmit a PDSCH corresponding to HARQ # 2 in the PDSCH transport block immediately before A / N 2, and the UE A HARQ-ACK for HARQ # 2 may be transmitted to the base station at the location of / N 2.
  • the base station may retransmit the PDSCH corresponding to HARQ # 1 to the UE in the PDSCH transport block immediately before A / N 2, and the UE May transmit HARQ-ACK for the HARQ # 1 associated with the retransmitted PDSCH to the base station at A / N 2 position.
  • the UE may receive a PDSCH corresponding to the NACK in a time interval after the gap without explicit signaling such as DCI. .
  • the terminal may assume that the operations described above in Section 3.1.3 are repeatedly performed until all HARQ processes are terminated.
  • the repetition may be stopped when one or more of the following conditions are satisfied.
  • the following conditions may be for guaranteeing downlink scheduling for changes in the wireless communication environment and / or other purposes of the terminal.
  • the base station may retransmit the PDSCH without explicit DCI transmission and reception, and the terminal may re-receive it.
  • FIG. 19 is a diagram illustrating a bundled HARQ-ACK transmission and reception structure according to various embodiments of the present disclosure.
  • a terminal may receive transport blocks (or sub-blocks) corresponding to all HARQ process numbers indicated from a DL grant in case of downlink. Thereafter, the bundled HARQ-ACK may be transmitted for the received transport blocks (or sub-blocks). For example, the terminal obtains 1-bit ACK / NACK information for each transport block (or sub-block), and bundles it based on an AND operation to 1-bit for all transport blocks (or sub-blocks) received. ACK / NACK information can be obtained.
  • the bundled HARQ-ACK is represented by an ACK.
  • the bundled HARQ-ACKs are NACKs. It can be expressed as.
  • the bundled HARQ-ACK may be transmitted within a gap established between transmissions of a transport block (or sub-block).
  • the bundled HARQ-ACK is bundled-NACK, that is, when the reception of a transport block (or sub-block) associated with the bundled HARQ-ACK is bundled-NACK, After the transmission time of the HARQ-ACK, it can be expected that the corresponding transport block (or sub-block) to be retransmitted without additional DCI monitoring.
  • the bundled HARQ-ACK when the bundled HARQ-ACK is bundled-ACK, that is, when the reception of a transport block (or sub-block) associated with the bundled HARQ-ACK is bundled-ACK, it may be configured to monitor the DCI to receive a new grant.
  • FIG. 19 an example of applying a bundled HARQ-ACK transmission / reception structure according to various embodiments of the present disclosure to an NB-IoT system is illustrated.
  • the corresponding multiple transport block transmit / receive structure is described in 3.1.1. It may be configured according to the transmission and reception structure based on the HARQ process according to various embodiments of the present disclosure described above in section 3.1.2 or 3.1.2.
  • bundled HARQ-ACK is in a gap configured between sub-blocks. Can be sent from.
  • the UE may expect that the preceding transport blocks (or sub-blocks) are retransmitted after the bundled HARQ-ACK transmission time point, without additional DCI monitoring. have. That is, in the exemplary embodiment, when the bundled HARQ-ACK is bundled-NACK, the UE is a transport block (or sub-block) corresponding to the bundled-NACK (scheduled by the previous DL grant), without additional DCI monitoring ) Can be expected to be retransmitted after the bundled HARQ-ACK transmission time.
  • the terminal may report HARQ-ACK to the base station.
  • the HARQ-ACK may be a HARQ-ACK multiplexed to be divided by HARQ processes.
  • the UE acquires 1-bit ACK / NACK information for N transport blocks (or sub-blocks), and multiplexes it, and includes an N-bit sequence of bits each representing ACK / NACK information for each N HARQ processes.
  • HARQ-ACK information can be obtained.
  • the UE when the UE reports a bundled-NACK within a gap configured between transport blocks (or sub-blocks), the UE may transmit a transport block (or sub-block associated with the bundled-NACK after the corresponding bundled-NACK transmission). You can expect to resend.
  • the terminal after retransmission of a transport block (or sub-block) is terminated, the terminal may report HARQ-ACK for the corresponding retransmitted transport block (or sub-block).
  • the HARQ-ACK may be multiplexed so that each HARQ process of the retransmitted transport block (or sub-block) is distinguished.
  • the UE when the bundled HARQ-ACK is bundled-ACK, the UE no longer performs monitoring for the remaining sub-blocks scheduled by the previous DCI, and may be configured / configured to monitor the new DCI. Can be.
  • the terminal may receive the next transport blocks (or sub-blocks) based on the DL grant of the new DCI, and after the end of transmission of the next transport blocks (or sub-blocks), bundled thereto.
  • the HARQ-ACK may be reported.
  • FIG. 20 is a diagram illustrating a transmission / reception structure based on a compact DCI / indication signal according to various embodiments of the present disclosure.
  • the compact DCI may mean a DCI having a smaller information size and a shorter repetition size in preparation for the DCI in which the terminal expects scheduling associated with multiple transport block transmission. Can be.
  • the compact DCI may include HARQ process number information and / or retransmission delay time information of the corresponding transport block (corresponding to NACK), and may be transmitted.
  • Information on a transport block size (TBS) may be omitted.
  • the compact DCI is configured to perform (N) PDCCH or MPDCCH format (eg, DCI format for scheduling a single transport block or multiple transport block scheduling).
  • N PDCCH or MPDCCH format
  • Information indicating a DCI format For example, if all of the transport blocks received by the UE are ACK, the compact DCI is configured to perform (N) PDCCH or MPDCCH format (eg, DCI format for scheduling a single transport block or multiple transport block scheduling).
  • N PDCCH or MPDCCH format
  • the indication signal may refer to a signal that provides information to the terminal to distinguish between the retransmission operation and the DCI monitoring operation.
  • WUS wake-up-signal
  • a terminal transmits transport blocks (or sub-blocks) corresponding to all HARQ process numbers indicated from a UL grant in the case of uplink. Afterwards, a compact DCI (or indication signal) can be expected.
  • the UE may transmit a preceding transport block (or sub-block) after a compact DCI (or indication signal) reception time without additional DCI monitoring. Can listen again.
  • the terminal when the compact DCI (or indication signal) indicates DCI monitoring, the terminal may be configured / configured to monitor the DCI for receiving a new grant.
  • FIG. 20 an example in which a transmit / receive structure based on compact DCI according to various embodiments of the present disclosure is applied to an NB-IoT system is illustrated.
  • the corresponding multiple transport block transmit / receive structure is described in 3.1.1. It may be configured according to the transmission and reception structure based on the HARQ process according to various embodiments of the present disclosure described above in section 3.1.2 or 3.1.2.
  • compact DCI (or indication signal) is inter-sub-block. Can be received within the configured gap.
  • the terminal may continue to expect transmission of the previous DL grant scheduled PDSCH.
  • the terminal when the compact DCI (or indication signal) instructs to monitor the next DCI, the terminal no longer performs monitoring for the remaining previously scheduled sub-blocks, and monitors the new DCI.
  • the various embodiments of the present disclosure described above are some of various implementation manners of the present disclosure, and it is clearly understood by those skilled in the art that the various embodiments of the present disclosure are not limited to the above-described embodiments. Can be.
  • the various embodiments of the present disclosure described above may be implemented independently, other various embodiments of the present disclosure may be configured in the form of a combination (or merge) of some embodiments.
  • the information on whether the various embodiments of the present disclosure described above are applied is a signal (eg, a physical layer signal or a higher layer signal) predefined by the base station to the terminal. Rules can be defined to inform via.
  • a terminal may perform a network access procedure to perform the above-described procedures and / or methods. For example, while accessing a network (eg, a base station), the terminal may receive and store system information and configuration information necessary to perform the above-described procedures and / or methods in a memory. Configuration information required for various embodiments of the present disclosure may be received through higher layer (eg, RRC layer; Medium Access Control, MAC, layer, etc.) signaling.
  • higher layer eg, RRC layer; Medium Access Control, MAC, layer, etc.
  • a physical channel and a reference signal may be transmitted using beam-forming.
  • a beam management process may be involved to align the beam between the base station and the terminal.
  • a signal proposed in various embodiments of the present disclosure may be transmitted / received using beam-forming.
  • RRC Radio Resource Control
  • beam alignment may be performed based on SSB (or SS / PBCH block).
  • beam alignment in the RRC CONNECTED mode may be performed based on CSI-RS (in DL) and SRS (in UL).
  • an operation related to a beam may be omitted in the following description.
  • the base station may periodically transmit the SSB (S2102).
  • SSB includes PSS / SSS / PBCH.
  • SSB may be transmitted using beam sweeping.
  • the base station can transmit the RMSI (Remaining Minimum System Information) and OSI (Other System Information) (S2104).
  • the RMSI may include information (eg, PRACH configuration information) necessary for the terminal to initially access the base station.
  • the terminal identifies the best SSB after performing SSB detection.
  • the terminal may transmit the RACH preamble (Message 1, Msg1) to the base station by using the PRACH resources linked / corresponding to the index (ie, beam) of the best SSB (S2106).
  • the beam direction of the RACH preamble is associated with a PRACH resource.
  • the association between the PRACH resource (and / or RACH preamble) and the SSB (index) may be established through system information (eg, RMSI).
  • the base station transmits a random access response (RAR) (Msg2) (R2108) in response to the RACH preamble (S2108), the terminal uses Msg3 (eg, RRC Connection Request) by using the UL grant in the RAR
  • Msg4 may include an RRC Connection Setup.
  • subsequent beam alignment may be performed based on SSB / CSI-RS (in DL) and SRS (in UL).
  • the terminal may receive the SSB / CSI-RS (S2114).
  • the SSB / CSI-RS may be used by the terminal to generate a beam / CSI report.
  • the base station may request the terminal to the beam / CSI report through the DCI (S2116).
  • the terminal may generate a beam / CSI report based on the SSB / CSI-RS and transmit the generated beam / CSI report to the base station through the PUSCH / PUCCH (S2418).
  • the beam / CSI report may include a beam measurement result, information on a preferred beam, and the like.
  • the base station and the terminal may switch the beam based on the beam / CSI report (S2120a, S2120b).
  • the terminal and the base station may perform the above-described procedures and / or methods.
  • the terminal and the base station process information in a memory according to various embodiments of the present disclosure based on configuration information obtained in a network access process (eg, system information acquisition process, RRC connection process through RACH, etc.).
  • the wireless signal may be transmitted, or the received wireless signal may be processed and stored in a memory.
  • the radio signal may include at least one of PDCCH, PDSCH, and RS (Reference Signal) in downlink, and at least one of PUCCH, PUSCH, and SRS in uplink.
  • the process of accessing an NB-IoT network is further described based on LTE. The following description may be extended to NR as well.
  • the PSS, SSS and PBCH of S702 are replaced with NPSS, NSSS and NPBCH in NB-IoT, respectively.
  • the NB-IoT RACH process is basically the same as the LTE RACH process and is different in the following matters.
  • the RACH preamble format is different.
  • the preamble is based on code / sequence (eg, zadoff-chu sequence), whereas in NB-IoT the preamble is a subcarrier.
  • the NB-IoT RACH process is performed based on the CE level. Therefore, PRACH resources are allocated differently for each CE level.
  • the uplink resource allocation request is performed using the RACH procedure in the NB-IoT.
  • 22 is a diagram illustrating preamble transmission in an NB-IoT RACH.
  • the NPRACH preamble may consist of four symbol groups, and each symbol group may be composed of a CP and a plurality of SC-FDMA symbols.
  • the SC-FDMA symbol may be replaced with an OFDM symbol or a DFT-s-OFDM symbol.
  • the NPRACH only supports single-tone transmissions with 3.75kHz subcarrier spacing, and offers 66.7 ⁇ s and 266.67 ⁇ s length CPs to support different cell radii.
  • Each symbol group performs frequency hopping and the hopping pattern is as follows. The subcarrier transmitting the first symbol group is determined in a pseudo-random manner.
  • the second symbol group is one subcarrier leap
  • the third symbol group is six subcarrier leaps
  • the fourth symbol group is one subcarrier leap.
  • the frequency hopping procedure is repeatedly applied, and the NPRACH preamble can perform ⁇ 1, 2, 4, 8, 16, 32, 64, 128 ⁇ repetitive transmission to improve coverage.
  • NPRACH resources may be configured for each CE level.
  • the UE may select the NPRACH resource based on the CE level determined according to the downlink measurement result (eg, RSRP) and transmit the RACH preamble using the selected NPRACH resource.
  • the NPRACH may be transmitted on an anchor carrier or on a non-anchor carrier with NPRACH resources configured.
  • FIG. 23 is a diagram illustrating a DRX operation according to various embodiments of the present disclosure.
  • a terminal may perform a DRX operation while performing the procedures and / or methods described above.
  • a terminal configured with DRX may lower power consumption by discontinuously receiving a DL signal.
  • DRX may be performed in a Radio Resource Control (RRC) _IDLE state, an RRC_INACTIVE state, and an RRC_CONNECTED state.
  • RRC Radio Resource Control
  • the DRX is used to discontinuously receive the paging signal.
  • DRX is used for discontinuous reception of PDCCH.
  • DRX performed in the RRC_CONNECTED state is referred to as RRC_CONNECTED DRX.
  • the DRX cycle includes On Duration and Opportunity for DRX.
  • the DRX cycle defines the time interval in which On Duration repeats periodically.
  • On Duration indicates a time interval that the UE monitors to receive the PDCCH.
  • the UE performs PDCCH monitoring for On Duration. If there is a PDCCH successfully detected during PDCCH monitoring, the UE operates an inactivity timer and maintains an awake state. On the other hand, if there is no PDCCH successfully detected during PDCCH monitoring, the UE enters a sleep state after the On Duration ends. Therefore, when DRX is configured, PDCCH monitoring / reception may be performed discontinuously in the time domain in performing the above-described / proposed procedures and / or methods.
  • a PDCCH reception opportunity (eg, a slot having a PDCCH search space) may be set discontinuously according to the DRX configuration.
  • PDCCH monitoring / reception may be continuously performed in the time domain in performing the above-described / proposed procedure and / or method.
  • a PDCCH reception opportunity (eg, a slot having a PDCCH search space) may be set continuously.
  • PDCCH monitoring may be limited in the time interval set as the measurement gap.
  • Table 13 shows a procedure of UE related to DRX (RRC_CONNECTED state).
  • DRX configuration information is received through higher layer (eg, RRC) signaling, and whether DRX ON / OFF is controlled by the DRX command of the MAC layer. If DRX is configured, the UE may discontinuously perform PDCCH monitoring in performing the procedure and / or method described / proposed in various embodiments of the present disclosure.
  • MAC-CellGroupConfig includes configuration information necessary to set a medium access control (MAC) parameter for a cell group.
  • the MAC-CellGroupConfig may also include configuration information regarding the DRX.
  • MAC-CellGroupConfig may include information as follows in defining DRX.
  • Value of drx-OnDurationTimer defines the length of the start section of the DRX cycle
  • Value of drx-InactivityTimer defines the length of time interval in which the UE wakes up after a PDCCH opportunity where a PDCCH indicating initial UL or DL data is detected.
  • Value of drx-HARQ-RTT-TimerDL Defines the length of the maximum time interval after DL initial transmission is received until DL retransmission is received.
  • Value of drx-HARQ-RTT-TimerDL Defines the length of the maximum time interval after a grant for UL initial transmission is received until a grant for UL retransmission is received.
  • drx-LongCycleStartOffset Defines the length of time and start time of the DRX cycle
  • drx-ShortCycle defines the length of time of the short DRX cycle
  • the UE maintains a wake-up state and performs PDCCH monitoring at every PDCCH opportunity.
  • the DRX is used to discontinuously receive the paging signal.
  • DRX performed in the RRC_IDLE (or RRC_INACTIVE) state is referred to as RRC_IDLE DRX.
  • PDCCH monitoring / reception may be performed discontinuously in the time domain in performing the above-described / proposed procedures and / or methods.
  • DRX may be configured for discontinuous reception of a paging signal.
  • the terminal may receive DRX configuration information from the base station through higher layer (eg, RRC) signaling.
  • the DRX configuration information may include configuration information about a DRX cycle, a DRX offset, a DRX timer, and the like.
  • the UE repeats the On Duration and the Sleep duration according to the DRX cycle.
  • the UE may operate in a wakeup mode at On duration and may operate in a sleep mode at Sleep duration. In the wake-up mode, the terminal may monitor a paging occasion (PO) to receive a paging message.
  • PO paging occasion
  • the PO means a time resource / interval (eg, subframe, slot) in which the terminal expects to receive a paging message.
  • PO monitoring includes monitoring a PDCCH (or MPDCCH, NPDCCH) (hereinafter, paging PDCCH) scrambled with P-RNTI in a PO.
  • the paging message may be included in the paging PDCCH or may be included in the PDSCH scheduled by the paging PDCCH.
  • One or a plurality of PO (s) is included in a paging frame (PF), and the PF may be periodically set based on the UE ID.
  • the PF corresponds to one radio frame, and the UE ID may be determined based on the International Mobile Subscriber Identity (IMSI) of the terminal.
  • IMSI International Mobile Subscriber Identity
  • the UE monitors only one PO per DRX cycle.
  • the terminal receives a paging message indicating a change of its ID and / or system information from the PO
  • the terminal performs a RACH process to initialize (or reset) the connection with the base station, or receives new system information from the base station ( Or acquisition).
  • PO monitoring may be performed discontinuously in the time domain to perform RACH for connection with a base station or to receive (or obtain) new system information from the base station. Can be.
  • the maximum cycle duration may be limited to 2.56 seconds.
  • a terminal in which data transmission and reception are intermittently performed such as an MTC terminal or an NB-IoT terminal
  • unnecessary power consumption may occur during a DRX cycle.
  • PSM power saving mode
  • PGW paging time window or a paging transmission window
  • PH Paging Hyper-frames
  • PTW is defined in the PH.
  • the UE may monitor a paging signal by performing a DRX cycle in a PTW duration to switch to a wake-up mode in its PO.
  • One or more DRX cycles (eg, wake-up mode and sleep mode) of FIG. 22C may be included in the PTW section.
  • the number of DRX cycles in the PTW interval may be configured by the base station through a higher layer (eg, RRC) signal.
  • FIG. 24 is a diagram schematically illustrating a method of operating a terminal and a base station according to various embodiments of the present disclosure
  • FIG. 25 is a flowchart illustrating a method of operating a terminal according to various embodiments of the present disclosure
  • FIG. 26 is a present disclosure
  • a base station may transmit downlink control information (DCI) for scheduling both a first transport block and a second transport block to a terminal. And, the terminal may receive this (S2401, S2501, S2601). That is, according to various embodiments of the present disclosure, a plurality of transport blocks may be scheduled by one DCI.
  • DCI downlink control information
  • the base station may transmit a first transport block associated with the above-described DCI (S2401, S2501, S2601) to the terminal, the terminal based on the above-described DCI (S2401, S2501, S2601)
  • the first transport block can be received in the first time resource (S2403, S2503, S2603).
  • the base station may transmit a second transport block associated with the above-described DCI (S2401, S2501, S2601) to the terminal, the terminal based on the above-described DCI (S2401, S2501, S2601)
  • the second transport block can be received in the second time resource (S2407, S2507, S2607).
  • each of the first time resource and the second time resource may be a time resource scheduled by the above-described DCI (S2401, S2501, S2601).
  • the first transport block can be transmitted and received repeatedly in a first time resource.
  • the second transport block can be repeatedly transmitted and received within a second time resource.
  • a gap may be established / configured between the first time resource and the second time resource.
  • the terminal may transmit a HARQ-ACK associated with the first transport block to the base station in response to the first transport block in the gap, the base station may receive it (S2405, S2505, S2605).
  • the HARQ process number associated with the second transport block may be determined based on the HARQ-ACKs S2405, S2505, S2605 associated with the first transport block described above.
  • the HARQ process number associated with the second transport block is equal to the HARQ process number associated with the first transport block. The same can be determined.
  • the HARQ process number associated with the second transport block is the HARQ process number associated with the first transport block.
  • Next HARQ process number may be determined.
  • FIG 27 illustrates an apparatus in which various embodiments of the present disclosure may be implemented.
  • the device illustrated in FIG. 27 may be a user equipment (UE) and / or a base station (eg, eNB or gNB) adapted to perform the above-described mechanism, or any device performing the same task.
  • UE user equipment
  • base station eg, eNB or gNB
  • the apparatus may include a digital signal processor (DSP) / microprocessor 210 and a radio frequency (RF) module (transceiver) 235.
  • the DSP / microprocessor 210 is electrically connected to the transceiver 235 to control the transceiver 235.
  • the device depending on the designer's choice, includes a power management module 205, a battery 255, a display 215, a keypad 220, a SIM card 225, a memory device 230, an antenna 240, and a speaker ( 245 and input device 250 may be further included.
  • FIG. 27 may represent a terminal that includes a receiver 235 configured to receive a request message from the network and a transmitter 235 configured to transmit timing transmit / receive timing information to the network. Such a receiver and a transmitter may configure the transceiver 235.
  • the terminal may further include a processor 210 connected to the transceiver 235.
  • 27 may also show a network device including a transmitter 235 configured to transmit a request message to a terminal and a receiver 235 configured to receive transmission and reception timing information from the terminal.
  • the transmitter and receiver may configure the transceiver 235.
  • the network further includes a processor 210 coupled to the transmitter and the receiver.
  • the processor 210 may calculate a latency based on the transmission and reception timing information.
  • a processor included in a terminal (or a communication device included in the terminal) and a base station (or a communication device included in the base station) may control a memory and operate as follows. .
  • a terminal or base station may include at least one transceiver; One or more memories; And one or more processors connected to the transceiver and the memory.
  • the memory may store instructions that enable one or more processors to perform the following operations.
  • the communication device included in the terminal or the base station may be configured to include the one or more processors and the one or more memories, and the communication device includes the one or more transceivers or does not include the one or more transceivers. It may be configured to be connected to the one or more transceivers without.
  • one or more processors may include downlink control information for scheduling both a first transport block and a second transport block.
  • downlink control information DCI downlink control information
  • one or more processors included in the terminal may receive the first transport block within the first time resource based on the above-described DCI.
  • one or more processors included in the terminal may receive a second transport block within a second time resource based on the above-described DCI.
  • a gap may be established between the first time resource and the second time resource, and one or more processors included in the terminal may include a first response in response to the first transport block within the gap.
  • the HARQ-ACK associated with the transport block may be transmitted.
  • one or more processors included in a base station may transmit a DCI scheduling both the first transport block and the second transport block. have.
  • one or more processors included in the base station may transmit the first transport block within the first time resource associated with the above-described DCI.
  • one or more processors included in the base station may transmit a second transport block within a second time resource associated with the above-described DCI.
  • a gap may be established between the first time resource and the second time resource, and one or more processors included in the base station may include a first response in response to the first transport block within the gap.
  • a HARQ-ACK associated with a transport block can be received.
  • a communication system 1 applied to various embodiments of the present disclosure includes a wireless device, a base station, and a network.
  • the wireless device refers to a device that performs communication using a radio access technology (eg, 5G New RAT (Long Term), Long Term Evolution (LTE)), and may be referred to as a communication / wireless / 5G device.
  • the wireless device may be a robot 100a, a vehicle 100b-1, 100b-2, an eXtended Reality (XR) device 100c, a hand-held device 100d, a home appliance 100e. ), IoT (Internet of Thing) device (100f), AI device / server 400 may be included.
  • the vehicle may include a vehicle having a wireless communication function, an autonomous vehicle, a vehicle capable of performing inter-vehicle communication, and the like.
  • the vehicle may include an unmanned aerial vehicle (UAV) (eg, a drone).
  • UAV unmanned aerial vehicle
  • XR devices include AR (Augmented Reality) / VR (Virtual Reality) / MR (Mixed Reality) devices, Head-Mounted Device (HMD), Head-Up Display (HUD), television, smartphone, It may be implemented in the form of a computer, a wearable device, a home appliance, a digital signage, a vehicle, a robot, and the like.
  • the portable device may include a smartphone, a smart pad, a wearable device (eg, smart watch, smart glasses), a computer (eg, a notebook, etc.).
  • the home appliance may include a TV, a refrigerator, a washing machine, and the like.
  • IoT devices may include sensors, smart meters, and the like.
  • the base station and the network may be implemented as a wireless device, and the specific wireless device 200a may operate as a base station / network node to other wireless devices.
  • the wireless devices 100a to 100f may be connected to the network 300 through the base station 200.
  • AI Artificial Intelligence
  • the network 300 may be configured using a 3G network, a 4G (eg LTE) network or a 5G (eg NR) network.
  • the wireless devices 100a-100f may communicate with each other via the base station 200 / network 300, but may also communicate directly (e.g. sidelink communication) without going through the base station / network.
  • the vehicles 100b-1 and 100b-2 may perform direct communication (e.g. vehicle to vehicle (V2V) / vehicle to everything (V2X) communication).
  • the IoT device eg, sensor
  • the IoT device may directly communicate with another IoT device (eg, sensor) or another wireless device 100a to 100f.
  • Wireless communication / connection 150a, 150b, 150c may be performed between the wireless devices 100a-100f / base station 200 and base station 200 / base station 200.
  • the wireless communication / connection is various wireless connections such as uplink / downlink communication 150a, sidelink communication 150b (or D2D communication), inter-base station communication 150c (eg relay, integrated access backhaul), and the like.
  • Technology eg, 5G NR
  • wireless communication / connections 150a, 150b, 150c, the wireless device and the base station / wireless device, the base station and the base station may transmit / receive radio signals to each other.
  • wireless communication / connections 150a, 150b, 150c may transmit / receive signals over various physical channels.
  • various signal processing processes eg, channel encoding / decoding, modulation / demodulation, resource mapping / demapping, etc.
  • resource allocation processes may be performed.
  • 29 illustrates a wireless device that can be applied to various embodiments of the present disclosure.
  • the first wireless device 100 and the second wireless device 200 may transmit and receive wireless signals through various wireless access technologies (eg, LTE and NR).
  • the ⁇ first wireless device 100 and the second wireless device 200 ⁇ may refer to the ⁇ wireless device 100x, the base station 200 ⁇ and / or the ⁇ wireless device 100x, the wireless device 100x of FIG. 28. ⁇ .
  • the first wireless device 100 includes one or more processors 102 and one or more memories 104, and may further include one or more transceivers 106 and / or one or more antennas 108.
  • the processor 102 controls the memory 104 and / or the transceiver 106 and may be configured to implement the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed herein.
  • the processor 102 may process the information in the memory 104 to generate the first information / signal, and then transmit the wireless signal including the first information / signal through the transceiver 106.
  • the processor 102 may receive the radio signal including the second information / signal through the transceiver 106 and store the information obtained from the signal processing of the second information / signal in the memory 104.
  • the memory 104 may be coupled to the processor 102 and may store various information related to the operation of the processor 102. For example, the memory 104 may perform instructions to perform some or all of the processes controlled by the processor 102 or to perform descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed herein. Can store software code that includes them.
  • processor 102 and memory 104 may be part of a communication modem / circuit / chip designed to implement wireless communication technology (eg, LTE, NR).
  • the transceiver 106 may be coupled to the processor 102 and may transmit and / or receive wireless signals via one or more antennas 108.
  • the transceiver 106 may include a transmitter and / or a receiver.
  • the transceiver 106 may be mixed with a radio frequency (RF) unit.
  • RF radio frequency
  • a wireless device may mean a communication modem / circuit / chip.
  • the second wireless device 200 may include one or more processors 202, one or more memories 204, and may further include one or more transceivers 206 and / or one or more antennas 208.
  • the processor 202 controls the memory 204 and / or the transceiver 206 and may be configured to implement the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed herein.
  • the processor 202 may process the information in the memory 204 to generate third information / signal, and then transmit the wireless signal including the third information / signal through the transceiver 206.
  • the processor 202 may receive the radio signal including the fourth information / signal through the transceiver 206 and then store information obtained from the signal processing of the fourth information / signal in the memory 204.
  • the memory 204 may be connected to the processor 202 and store various information related to the operation of the processor 202. For example, the memory 204 may perform instructions to perform some or all of the processes controlled by the processor 202 or to perform descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed herein. Can store software code that includes them.
  • processor 202 and memory 204 may be part of a communication modem / circuit / chip designed to implement wireless communication technology (eg, LTE, NR).
  • the transceiver 206 may be coupled with the processor 202 and may transmit and / or receive wireless signals via one or more antennas 208.
  • the transceiver 206 may include a transmitter and / or a receiver.
  • the transceiver 206 may be mixed with an RF unit.
  • a wireless device may mean a communication modem / circuit / chip.
  • One or more protocol layers may be implemented by one or more processors 102, 202, although not limited thereto.
  • one or more processors 102 and 202 may implement one or more layers (eg, functional layers such as PHY, MAC, RLC, PDCP, RRC, SDAP).
  • One or more processors 102, 202 may employ one or more Protocol Data Units (PDUs) and / or one or more Service Data Units (SDUs) in accordance with the descriptions, functions, procedures, suggestions, methods, and / or operational flowcharts disclosed herein. Can be generated.
  • PDUs Protocol Data Units
  • SDUs Service Data Units
  • One or more processors 102, 202 may generate messages, control information, data, or information in accordance with the descriptions, functions, procedures, suggestions, methods, and / or operational flowcharts disclosed herein.
  • One or more processors 102, 202 may generate signals (eg, baseband signals) including PDUs, SDUs, messages, control information, data or information in accordance with the functions, procedures, suggestions and / or methods disclosed herein.
  • signals eg, baseband signals
  • One or more processors 102, 202 may receive signals (eg, baseband signals) from one or more transceivers 106, 206, and include descriptions, functions, procedures, suggestions, methods, and / or operational flowcharts disclosed herein.
  • a PDU, an SDU, a message, control information, data, or information can be obtained.
  • One or more processors 102, 202 may be referred to as a controller, microcontroller, microprocessor, or microcomputer.
  • One or more processors 102, 202 may be implemented by hardware, firmware, software, or a combination thereof.
  • ASICs Application Specific Integrated Circuits
  • DSPs Digital Signal Processors
  • DSPDs Digital Signal Processing Devices
  • PLDs Programmable Logic Devices
  • FPGAs Field Programmable Gate Arrays
  • the descriptions, functions, procedures, suggestions, methods, and / or operational flowcharts disclosed herein may be implemented using firmware or software, and the firmware or software may be implemented to include modules, procedures, functions, and the like.
  • the descriptions, functions, procedures, suggestions, methods, and / or operational flowcharts disclosed herein may be included in one or more processors (102, 202) or stored in one or more memories (104, 204) of It may be driven by the above-described processor (102, 202).
  • the descriptions, functions, procedures, suggestions, methods, and / or operational flowcharts disclosed herein may be implemented using firmware or software in the form of code, instructions, and / or a set of instructions.
  • One or more memories 104, 204 may be coupled to one or more processors 102, 202 and may store various forms of data, signals, messages, information, programs, codes, instructions, and / or instructions.
  • One or more memories 104, 204 may be comprised of ROM, RAM, EPROM, flash memory, hard drive, registers, cache memory, computer readable storage medium, and / or combinations thereof.
  • One or more memories 104, 204 may be located inside and / or outside one or more processors 102, 202.
  • one or more memories 104, 204 may be coupled with one or more processors 102, 202 through various techniques, such as a wired or wireless connection.
  • One or more transceivers 106 and 206 may transmit user data, control information, wireless signals / channels, etc., as mentioned in the methods and / or operational flowcharts of this document, to one or more other devices.
  • One or more transceivers 106 and 206 may receive, from one or more other devices, user data, control information, wireless signals / channels, etc., as mentioned in the description, functions, procedures, suggestions, methods and / or operational flowcharts disclosed herein. have.
  • one or more transceivers 106 and 206 may be coupled with one or more processors 102 and 202 and may transmit and receive wireless signals.
  • one or more processors 102 and 202 may control one or more transceivers 106 and 206 to transmit user data, control information or wireless signals to one or more other devices.
  • one or more processors 102 and 202 may control one or more transceivers 106 and 206 to receive user data, control information or wireless signals from one or more other devices.
  • one or more transceivers 106, 206 may be coupled with one or more antennas 108, 208, and one or more transceivers 106, 206 may be connected to one or more antennas 108, 208 through the description, functions, and features disclosed herein.
  • one or more antennas may be a plurality of physical antennas or a plurality of logical antennas (eg, antenna ports).
  • One or more transceivers 106, 206 may process the received wireless signal / channel or the like in an RF band signal to process received user data, control information, wireless signals / channels, etc. using one or more processors 102,202.
  • the baseband signal can be converted.
  • One or more transceivers 106 and 206 may use the one or more processors 102 and 202 to convert processed user data, control information, wireless signals / channels, etc. from baseband signals to RF band signals.
  • one or more transceivers 106 and 206 may include (analog) oscillators and / or filters.
  • FIG. 30 illustrates another example of a wireless device applied to various embodiments of the present disclosure.
  • the wireless device may be implemented in various forms depending on the use-example / service (see FIG. 28).
  • the wireless devices 100 and 200 correspond to the wireless devices 100 and 200 of FIG. 29, and various elements, components, units / units, and / or modules It can be composed of).
  • the wireless device 100, 200 may include a communication unit 110, a control unit 120, a memory unit 130, and additional elements 140.
  • the communication unit may include communication circuitry 112 and transceiver (s) 114.
  • communication circuitry 112 may include one or more processors 102, 202 and / or one or more memories 104, 204 of FIG. 29.
  • the transceiver (s) 114 may include one or more transceivers 106, 206 and / or one or more antennas 108, 208 of FIG. 29.
  • the controller 120 is electrically connected to the communication unit 110, the memory unit 130, and the additional element 140, and controls various operations of the wireless device. For example, the controller 120 may control the electrical / mechanical operation of the wireless device based on the program / code / command / information stored in the memory unit 130. In addition, the control unit 120 transmits the information stored in the memory unit 130 to the outside (eg, other communication devices) through the communication unit 110 through a wireless / wired interface, or externally (eg, through the communication unit 110). Information received through a wireless / wired interface from another communication device) may be stored in the memory unit 130.
  • the outside eg, other communication devices
  • Information received through a wireless / wired interface from another communication device may be stored in the memory unit 130.
  • the additional element 140 may be configured in various ways depending on the type of wireless device.
  • the additional element 140 may include at least one of a power unit / battery, an I / O unit, a driver, and a computing unit.
  • the wireless device may be a robot (FIGS. 28, 100 a), a vehicle (FIGS. 28, 100 b-1, 100 b-2), an XR device (FIGS. 28, 100 c), a portable device (FIGS. 28, 100 d), a home appliance. (FIGS. 28, 100e), IoT devices (FIGS.
  • the server may be implemented in the form of an AI server / device (FIGS. 28 and 400), a base station (FIGS. 28 and 200), a network node, or the like.
  • the wireless device may be used in a mobile or fixed location depending on the usage-example / service.
  • various elements, components, units / units, and / or modules in the wireless devices 100 and 200 may be entirely interconnected through a wired interface, or at least a part of them may be wirelessly connected through the communication unit 110.
  • the control unit 120 and the communication unit 110 are connected by wire in the wireless device 100 or 200, and the control unit 120 and the first unit (eg, 130 and 140) are connected through the communication unit 110. It can be connected wirelessly.
  • each element, component, unit / unit, and / or module in wireless device 100, 200 may further include one or more elements.
  • the controller 120 may be composed of one or more processor sets.
  • the controller 120 may be configured as a set of a communication control processor, an application processor, an electronic control unit (ECU), a graphics processing processor, a memory control processor, and the like.
  • the memory unit 130 may include random access memory (RAM), dynamic RAM (DRAM), read only memory (ROM), flash memory, volatile memory, and non-volatile memory. volatile memory) and / or combinations thereof.
  • the mobile device may include a smart phone, a smart pad, a wearable device (eg, smart watch, smart glasses), a portable computer (eg, a notebook, etc.).
  • the mobile device may be referred to as a mobile station (MS), a user terminal (UT), a mobile subscriber station (MSS), a subscriber station (SS), an advanced mobile station (AMS), or a wireless terminal (WT).
  • MS mobile station
  • UT user terminal
  • MSS mobile subscriber station
  • SS subscriber station
  • AMS advanced mobile station
  • WT wireless terminal
  • the portable device 100 includes an antenna unit 108, a communication unit 110, a control unit 120, a memory unit 130, a power supply unit 140a, an interface unit 140b, and an input / output unit 140c. ) May be included.
  • the antenna unit 108 may be configured as part of the communication unit 110.
  • Blocks 110 to 130 / 140a to 140c respectively correspond to blocks 110 to 130/140 of FIG. 30.
  • the communication unit 110 may transmit and receive signals (eg, data, control signals, etc.) with other wireless devices and base stations.
  • the controller 120 may control various components of the mobile device 100 to perform various operations.
  • the control unit 120 may include an application processor (AP).
  • the memory unit 130 may store data / parameters / programs / codes / commands necessary for driving the portable device 100. In addition, the memory unit 130 may store input / output data / information and the like.
  • the power supply unit 140a supplies power to the portable device 100 and may include a wired / wireless charging circuit, a battery, and the like.
  • the interface unit 140b may support the connection of the mobile device 100 to another external device.
  • the interface unit 140b may include various ports (eg, audio input / output port and video input / output port) for connecting to an external device.
  • the input / output unit 140c may receive or output image information / signal, audio information / signal, data, and / or information input from a user.
  • the input / output unit 140c may include a camera, a microphone, a user input unit, a display unit 140d, a speaker, and / or a haptic module.
  • the input / output unit 140c obtains information / signals (eg, touch, text, voice, image, and video) input from the user, and the obtained information / signal is stored in the memory unit 130. Can be stored.
  • the communication unit 110 may convert the information / signal stored in the memory into a wireless signal, and directly transmit the converted wireless signal to another wireless device or to the base station.
  • the communication unit 110 may receive a radio signal from another wireless device or a base station, and then restore the received radio signal to original information / signal.
  • the restored information / signal may be stored in the memory unit 130 and then output in various forms (eg, text, voice, image, video, heptic) through the input / output unit 140c.
  • the vehicle or autonomous vehicle may be implemented as a mobile robot, a vehicle, a train, an aerial vehicle (AV), a ship, or the like.
  • AV aerial vehicle
  • the vehicle or the autonomous vehicle 100 may include an antenna unit 108, a communication unit 110, a control unit 120, a driving unit 140a, a power supply unit 140b, a sensor unit 140c, and autonomous driving. It may include a portion 140d.
  • the antenna unit 108 may be configured as part of the communication unit 110. Blocks 110/130 / 140a through 140d respectively correspond to blocks 110/130/140 in FIG.
  • the communication unit 110 may transmit and receive signals (eg, data, control signals, etc.) with other vehicles, a base station (e.g. base station, road side unit, etc.), a server, and other external devices.
  • the controller 120 may control various elements of the vehicle or the autonomous vehicle 100 to perform various operations.
  • the control unit 120 may include an electronic control unit (ECU).
  • the driving unit 140a may cause the vehicle or the autonomous vehicle 100 to travel on the ground.
  • the driver 140a may include an engine, a motor, a power train, wheels, a brake, a steering device, and the like.
  • the power supply unit 140b supplies power to the vehicle or the autonomous vehicle 100, and may include a wired / wireless charging circuit, a battery, and the like.
  • the sensor unit 140c may obtain vehicle status, surrounding environment information, user information, and the like.
  • the sensor unit 140c includes an inertial measurement unit (IMU) sensor, a collision sensor, a wheel sensor, a speed sensor, an inclination sensor, a weight sensor, a heading sensor, a position module, a vehicle forward / Reverse sensors, battery sensors, fuel sensors, tire sensors, steering sensors, temperature sensors, humidity sensors, ultrasonic sensors, illuminance sensors, pedal position sensors, and the like.
  • the autonomous driving unit 140d is a technology for maintaining a driving lane, a technology for automatically adjusting speed such as adaptive cruise control, a technology for automatically driving along a predetermined route, and automatically setting a route when a destination is set. Technology and the like.
  • the communication unit 110 may receive map data, traffic information data, and the like from an external server.
  • the autonomous driving unit 140d may generate an autonomous driving route and a driving plan based on the obtained data.
  • the controller 120 may control the driving unit 140a to move the vehicle or the autonomous vehicle 100 along the autonomous driving path according to the driving plan (eg, speed / direction adjustment).
  • the communication unit 110 may acquire the latest traffic information data aperiodically from an external server and may obtain the surrounding traffic information data from the surrounding vehicles.
  • the sensor unit 140c may acquire vehicle state and surrounding environment information.
  • the autonomous driving unit 140d may update the autonomous driving route and the driving plan based on the newly obtained data / information.
  • the communication unit 110 may transmit information regarding a vehicle location, an autonomous driving route, a driving plan, and the like to an external server.
  • the external server may predict traffic information data in advance using AI technology or the like based on information collected from the vehicle or autonomous vehicles, and provide the predicted traffic information data to the vehicle or autonomous vehicles.
  • the vehicle 33 illustrates a vehicle applied to various embodiments of the present disclosure.
  • the vehicle may also be implemented as a vehicle, train, vehicle, ship, or the like.
  • the vehicle 100 may include a communication unit 110, a control unit 120, a memory unit 130, an input / output unit 140a, and a position measuring unit 140b.
  • blocks 110 to 130 / 140a to 140b correspond to blocks 110 to 130/140 of FIG. 30, respectively.
  • the communication unit 110 may transmit and receive signals (eg, data, control signals, etc.) with other vehicles or external devices such as a base station.
  • the controller 120 may control various components of the vehicle 100 to perform various operations.
  • the memory unit 130 may store data / parameters / programs / codes / commands supporting various functions of the vehicle 100.
  • the input / output unit 140a may output an AR / VR object based on the information in the memory unit 130.
  • the input / output unit 140a may include a HUD.
  • the location measuring unit 140b may acquire location information of the vehicle 100.
  • the location information may include absolute location information of the vehicle 100, location information in a driving line, acceleration information, location information with surrounding vehicles, and the like.
  • the position measuring unit 140b may include a GPS and various sensors.
  • the communication unit 110 of the vehicle 100 may receive map information, traffic information, and the like from an external server and store the received map information in the memory unit 130.
  • the location measuring unit 140b may obtain vehicle location information through GPS and various sensors and store the location information in the memory unit 130.
  • the controller 120 may generate a virtual object based on map information, traffic information, and vehicle location information, and the input / output unit 140a may display the generated virtual object on a glass window in the vehicle (1410 and 1420).
  • the controller 120 may determine whether the vehicle 100 is normally driven in the driving line based on the vehicle position information. When the vehicle 100 deviates abnormally from the driving line, the controller 120 may display a warning on the glass window in the vehicle through the input / output unit 140a.
  • the controller 120 may broadcast a warning message regarding a driving abnormality to surrounding vehicles through the communication unit 110. According to a situation, the controller 120 may transmit the location information of the vehicle and the information regarding the driving / vehicle abnormality to the related organization through the communication unit 110.
  • various embodiments of the present disclosure may be implemented through a device and / or a terminal.
  • the scheduler includes a base station, a network node, a transmission terminal, a reception terminal, a wireless device, a wireless communication device, a vehicle, a vehicle equipped with an autonomous driving function, a drone (Unmanned Aerial Vehicle, UAV), and AI (Artificial Intelligence). Module, robot, Augmented Reality (AR) device, Virtual Reality (VR) device or other device.
  • UAV Unmanned Aerial Vehicle
  • AI Artificial Intelligence
  • Module robot, Augmented Reality (AR) device, Virtual Reality (VR) device or other device.
  • the terminal may be a Personal Digital Assistant (PDA), a cellular phone, a Personal Communication Service (PCS) phone, a Global System for Mobile (GSM) phone, a Wideband CDMA (WCDMA) phone, an MBS ( It may be a Mobile Broadband System phone, a Smart phone, or a Multi Mode Multi Band (MM-MB) terminal.
  • PDA Personal Digital Assistant
  • PCS Personal Communication Service
  • GSM Global System for Mobile
  • WCDMA Wideband CDMA
  • MBS It may be a Mobile Broadband System phone, a Smart phone, or a Multi Mode Multi Band (MM-MB) terminal.
  • MBS Multi Mode Multi Band
  • a smart phone is a terminal that combines the advantages of a mobile communication terminal and a personal portable terminal, and may mean a terminal incorporating data communication functions such as schedule management, fax transmission and reception, etc. which are functions of a personal portable terminal.
  • a multimode multiband terminal can be equipped with a multi-modem chip to operate in both portable Internet systems and other mobile communication systems (e.g., code division multiple access (CDMA) 2000 systems, wideband CDMA (WCDMA) systems, etc.). Speak the terminal.
  • CDMA code division multiple access
  • WCDMA wideband CDMA
  • the terminal may be a notebook PC, a hand-held PC, a tablet PC, an ultrabook, a slate PC, a digital broadcasting terminal, a portable multimedia player (PMP), navigation,
  • a wearable device may be, for example, a smartwatch, a glass glass, a head mounted display, etc.
  • a drone may be burned by a radio control signal without a human being.
  • the HMD may be a display device in a form worn on the head, for example, the HMD may be used to implement VR or AR.
  • Various embodiments of the present disclosure may be implemented through various means.
  • various embodiments of the present disclosure may be implemented by hardware, firmware, software, or a combination thereof.
  • a method may include one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs). ), Field programmable gate arrays (FPGAs), processors, controllers, microcontrollers, microprocessors, and the like.
  • ASICs application specific integrated circuits
  • DSPs digital signal processors
  • DSPDs digital signal processing devices
  • PLDs programmable logic devices
  • FPGAs Field programmable gate arrays
  • processors controllers, microcontrollers, microprocessors, and the like.
  • the method according to various embodiments of the present disclosure may be implemented in the form of a module, procedure, or function that performs the functions or operations described above.
  • software code may be stored in the memory units 50 and 150 and driven by the processors 40 and 140.
  • the memory unit may be located inside or outside the processor, and may exchange data with the processor by various known means.
  • Various embodiments of the present disclosure can be applied to various radio access systems.
  • Examples of various radio access systems include 3rd Generation Partnership Project (3GPP) or 3GPP2 systems.
  • 3GPP 3rd Generation Partnership Project
  • Various embodiments of the present disclosure may be applied to all technical fields that apply the various radio access systems as well as the various radio access systems.
  • the proposed method can be applied to mmWave communication system using ultra high frequency band.

Landscapes

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

Abstract

Dans ses divers modes de réalisation, la présente invention concerne un procédé d'émission et de réception de signaux dans un système de communication radio, et un appareil prenant en charge ledit procédé. De façon plus spécifique, dans ses divers modes de réalisation, la présente invention concerne un procédé d'émission et de réception de signaux basé sur une pluralité de blocs de transmission dans un système comprenant l'application répétée d'une transmission de signal/canal physique, et un appareil prenant en charge ledit procédé.
PCT/KR2019/010070 2018-08-09 2019-08-09 Procédé d'émission et de réception de signaux dans un système de communication radio, et appareil prenant en charge ledit procédé WO2020032681A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201862716940P 2018-08-09 2018-08-09
US62/716,940 2018-08-09

Publications (1)

Publication Number Publication Date
WO2020032681A1 true WO2020032681A1 (fr) 2020-02-13

Family

ID=69415059

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2019/010070 WO2020032681A1 (fr) 2018-08-09 2019-08-09 Procédé d'émission et de réception de signaux dans un système de communication radio, et appareil prenant en charge ledit procédé

Country Status (1)

Country Link
WO (1) WO2020032681A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20210219330A1 (en) * 2018-08-13 2021-07-15 Nokia Technologies Oy Apparatus, method and computer program
US11729790B2 (en) 2020-08-06 2023-08-15 Samsung Electronics Co., Ltd. Mobile communications methods for monitoring and scheduling

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150189624A1 (en) * 2012-08-22 2015-07-02 Nokia Solutions And Networks Oy Deciding transmission parameters
US20170026297A1 (en) * 2015-07-24 2017-01-26 Qualcomm Incorporated Code block segmentation and rate matching for multiple transport block transmissions
US20170117992A1 (en) * 2014-04-04 2017-04-27 Nokia Solutions And Networks Oy Hybrid automatic repeat request timing in communications
KR20180045070A (ko) * 2010-12-21 2018-05-03 엘지전자 주식회사 무선 통신 시스템에서 신호를 송수신하는 방법 및 이를 위한 장치
KR20180059758A (ko) * 2015-08-25 2018-06-05 아이디에이씨 홀딩스, 인크. 무선 시스템의 프레이밍, 스케줄링, 및 동기화

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20180045070A (ko) * 2010-12-21 2018-05-03 엘지전자 주식회사 무선 통신 시스템에서 신호를 송수신하는 방법 및 이를 위한 장치
US20150189624A1 (en) * 2012-08-22 2015-07-02 Nokia Solutions And Networks Oy Deciding transmission parameters
US20170117992A1 (en) * 2014-04-04 2017-04-27 Nokia Solutions And Networks Oy Hybrid automatic repeat request timing in communications
US20170026297A1 (en) * 2015-07-24 2017-01-26 Qualcomm Incorporated Code block segmentation and rate matching for multiple transport block transmissions
KR20180059758A (ko) * 2015-08-25 2018-06-05 아이디에이씨 홀딩스, 인크. 무선 시스템의 프레이밍, 스케줄링, 및 동기화

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20210219330A1 (en) * 2018-08-13 2021-07-15 Nokia Technologies Oy Apparatus, method and computer program
US11968683B2 (en) * 2018-08-13 2024-04-23 Nokia Technologies Oy Apparatus, method and computer program
US11729790B2 (en) 2020-08-06 2023-08-15 Samsung Electronics Co., Ltd. Mobile communications methods for monitoring and scheduling

Similar Documents

Publication Publication Date Title
WO2020032740A1 (fr) Procédé d'émission/réception de signal dans un système de communication sans fil et dispositif correspondant
WO2020032750A1 (fr) Procédé d'émission et de réception de signaux dans un système de communication sans fil et dispositif associé
WO2020204322A1 (fr) Procédé de gestion de faisceaux par un terminal dans un système de communication sans fil, ainsi que terminal et station de base le prenant en charge
WO2019212224A1 (fr) Procédé d'émission et de réception d'informations d'état de canal entre un terminal et une station de base dans un système de communication sans fil et appareil le prenant en charge
WO2020130755A1 (fr) Procédé de fonctionnement d'un terminal et d'une station de base dans un système de communication sans fil et dispositif pour prendre en charge ledit procédé
WO2020145773A1 (fr) Procédé, équipement utilisateur, dispositif et support de stockage pour transmettre une liaison montante, et procédé et station de base pour recevoir une liaison montante
WO2020032726A1 (fr) Procédé et dispositif pour permettre à un dispositif de communication de détecter ou de transmettre un signal wus dans un système de communication sans fil
WO2020184836A1 (fr) Procédé de transmission d'informations de faisceau par un équipement utilisateur dans un système de communication sans fil, et équipement d'utilisateur et station de base le prenant en charge
WO2020050682A1 (fr) Procédé de fonctionnement d'un terminal dans un système de communication sans fil et terminal prenant en charge celui-ci
WO2020190117A1 (fr) Procédé d'émission et de réception de signal dans un système de communication sans fil et dispositif le prenant en charge
WO2020032751A1 (fr) Procédé d'émission de wus dans un système de communication sans fil et dispositif correspondant
WO2020166844A1 (fr) Procédé par lequel un équipement utilisateur reçoit un signal de données dans un système de communication sans fil, et équipement utilisateur et station de base qui le prennent en charge
WO2020171405A1 (fr) Procédé de gestion de faisceau par ue dans un systѐme de communication sans fil, et ue et station de base le prenant en charge
WO2020032756A1 (fr) Procédé d'émission et de réception de signaux dans un système de communication sans fil et dispositif associé
WO2020032643A1 (fr) Procédé d'émission et de réception d'un signal dans un système de communication sans fil, et appareil associé
WO2020166848A1 (fr) Procédé de transmission d'informations de retour de liaison montante relatives à un faisceau d'équipement utilisateur dans un système de communication sans fil, et équipement utilisateur et station de base pour le prendre en charge
WO2020159172A1 (fr) Procédé de rapport de défaillance de faisceau d'un terminal dans un système de communication sans fil, terminal et station de base pour prendre en charge celui-ci
WO2020159189A1 (fr) Procédé par lequel un terminal rapporte des informations d'état dans un système de communication sans fil, et terminal et station de base le mettant en œuvre
WO2020204497A1 (fr) Procédé et dispositif pour la transmission ou la réception d'un signal pour une planification de blocs de transport multiples
WO2021066602A1 (fr) Procédé d'émission et de réception de signaux dans un système de communication sans fil, et dispositif le prenant en charge
WO2021066606A1 (fr) Procédé permettant de transmettre et de recevoir un signal dans un système de communication sans fil, et dispositif prenant en charge celui-ci
WO2020145609A1 (fr) Procédé de transmission et de réception d'informations de commande de liaison descendante entre un terminal et une station de base dans un système de communications sans fil, et dispositif prenant en charge ce procédé
WO2020032717A1 (fr) Procédé et appareil pour la réception de signaux dans un système de communication sans fil
WO2020091498A1 (fr) Procédé de fonctionnement d'un terminal et d'une station de base dans un système de communication sans fil et appareil permettant de prendre en charge ledit procédé
WO2020091557A1 (fr) Procédé d'émission et de réception de signal dans un système de communication sans fil, et appareil associé

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

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

Country of ref document: EP

Kind code of ref document: A1