KR102592454B1 - Method and apparatus for transmitting and receiving uplink control information - Google Patents

Abstract

These embodiments relate to a method and device for transmitting and receiving uplink control information. One embodiment is a method for a terminal to transmit uplink control information, and a slot-based uplink control channel (PUCCH) from a base station. ) Receiving configuration information about a resource set and a subslot-based uplink control channel resource set, receiving information indicating a subslot-based uplink control channel resource set from a base station, and subslot-based uplink A method is provided including repeatedly transmitting uplink control information within one slot using uplink control channel resources of a link control channel resource set.

Description

Method and device for transmitting and receiving uplink control information {METHOD AND APPARATUS FOR TRANSMITTING AND RECEIVING UPLINK CONTROL INFORMATION}

These embodiments propose a method and device for transmitting and receiving uplink control information in a next-generation radio access network (hereinafter referred to as “NR [New Radio]”).

3GPP recently approved "Study on New Radio Access Technology", a study item for research on next-generation radio access technology (in other words, 5G radio access technology), and based on this, RAN WG1 each developed a study item for NR (New Radio). Design of frame structure, channel coding & modulation, waveform & multiple access scheme, etc. is in progress. NR is required to be designed to satisfy not only an improved data transmission rate compared to LTE, but also various QoS requirements required for each detailed and specific usage scenario.

As representative usage scenarios of NR, eMBB (enhancement Mobile BroadBand), mMTC (massive Machine Type Communication), and URLLC (Ultra Reliable and Low Latency Communications) have been defined, and a flexible frame structure compared to LTE is used to meet the needs of each usage scenario. A design is required.

Since each service requirement (usage scenario) has different requirements for data rates, latency, reliability, coverage, etc., it can be used through the frequency band that makes up an arbitrary NR system. Based on different numerologies (e.g., subcarrier spacing, subframe, TTI (Transmission Time Interval), etc.) as a method to efficiently satisfy the needs of each usage scenario. There is a need for a method of efficiently multiplexing radio resource units.

As part of this aspect, a design is needed to configure an uplink control channel resource set used to transmit uplink control information in NR and to allocate uplink control channel resources from the uplink control channel resource set.

Embodiments of the present disclosure can provide a specific method and device that can improve reliability of an uplink control channel according to repeated transmission of uplink control information.

In one aspect, the present embodiments provide a method for a terminal to transmit uplink control information, a slot-based uplink control channel (PUCCH) resource set and subslot-based uplink control from a base station. Receiving configuration information about a channel resource set, receiving information indicating a subslot-based uplink control channel resource set from a base station, and using the uplink control channel resources of the subslot-based uplink control channel resource set. A method including repeatedly transmitting uplink control information within one slot may be provided.

In another aspect, the present embodiments include a slot-based uplink control channel (PUCCH) resource set and a subslot-based uplink control channel resource in a method for a base station to receive uplink control information. Transmitting configuration information about the set to the terminal, transmitting information indicating a subslot-based uplink control channel resource set to the terminal, and using the uplink control channel resources of the subslot-based uplink control channel resource set. A method including the step of repeatedly receiving uplink control information within one slot may be provided.

In another aspect, these embodiments provide a slot-based uplink control channel (PUCCH) resource set and a subslot-based uplink control channel from the base station in the terminal transmitting uplink control information. Uplink using the uplink control channel resources of the receiving unit and subslot-based uplink control channel resource set that receives configuration information about the resource set and information indicating the subslot-based uplink control channel resource set from the base station. A terminal including a transmitter that repeatedly transmits control information within one slot can be provided.

In another aspect, the present embodiments include a slot-based uplink control channel (PUCCH) resource set and a subslot-based uplink control channel resource set in a base station receiving uplink control information. Uplink using a transmitter that transmits configuration information to the terminal and information indicating a subslot-based uplink control channel resource set to the terminal, and the uplink control channel resources of the subslot-based uplink control channel resource set. A base station including a receiving unit that repeatedly receives control information within one slot can be provided.

According to the present embodiments, a specific method and device that can improve reliability of the uplink control channel according to repeated transmission of uplink control information can be provided.

Figure 1 is a diagram briefly illustrating the structure of an NR wireless communication system to which this embodiment can be applied.
Figure 2 is a diagram for explaining the frame structure in an NR system to which this embodiment can be applied.
FIG. 3 is a diagram illustrating a resource grid supported by wireless access technology to which this embodiment can be applied.
Figure 4 is a diagram for explaining the bandwidth part supported by the wireless access technology to which this embodiment can be applied.
Figure 5 is a diagram illustrating a synchronization signal block in a wireless access technology to which this embodiment can be applied.
Figure 6 is a diagram for explaining a random access procedure in wireless access technology to which this embodiment can be applied.
Figure 7 is a diagram to explain CORESET.
FIG. 8 is a diagram illustrating an example of symbol level alignment among different SCSs to which this embodiment can be applied.
Figure 9 is a diagram showing a conceptual example of a bandwidth part to which this embodiment can be applied.
Figure 10 is a diagram illustrating a procedure for a terminal to transmit uplink control information according to an embodiment.
Figure 11 is a diagram illustrating a procedure for a base station to receive uplink control information according to an embodiment.
Figure 12 is a diagram showing the configuration of a user terminal according to another embodiment.
Figure 13 is a diagram showing the configuration of a base station according to another embodiment.

Hereinafter, some embodiments of the present disclosure will be described in detail with reference to illustrative drawings. In adding reference numerals to components in each drawing, the same components may have the same reference numerals as much as possible even if they are shown in different drawings. Additionally, in describing the present embodiments, if it is determined that a detailed description of a related known configuration or function may obscure the gist of the present technical idea, the detailed description may be omitted. When “comprises,” “has,” “consists of,” etc. mentioned in the specification are used, other parts may be added unless “only” is used. When a component is expressed in the singular, it can also include the plural, unless specifically stated otherwise.

Additionally, in describing the components of the present disclosure, terms such as first, second, A, B, (a), and (b) may be used. These terms are only used to distinguish the component from other components, and the nature, sequence, order, or number of the components are not limited by the term.

In the description of the positional relationship of components, when two or more components are described as being “connected,” “coupled,” or “connected,” the two or more components are directly “connected,” “coupled,” or “connected.” However, it should be understood that two or more components and other components may be further “interposed” and “connected,” “combined,” or “connected.” Here, other components may be included in one or more of two or more components that are “connected,” “coupled,” or “connected” to each other.

In the description of temporal flow relationships related to components, operation methods, production methods, etc., for example, temporal precedence relationships such as “after”, “after”, “after”, “before”, etc. Or, when a sequential relationship is described, non-continuous cases may be included unless “immediately” or “directly” is used.

On the other hand, when a numerical value or corresponding information (e.g., level, etc.) for a component is mentioned, even if there is no separate explicit description, the numerical value or corresponding information is related to various factors (e.g., process factors, internal or external shocks, It can be interpreted as including the error range that may occur due to noise, etc.).

The wireless communication system in this specification refers to a system for providing various communication services such as voice and data packets using wireless resources, and may include a terminal, a base station, or a core network.

The present embodiments disclosed below can be applied to wireless communication systems using various wireless access technologies. For example, the present embodiments include code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), orthogonal frequency division multiple access (OFDMA), and single carrier frequency division multiple access (SC-FDMA). Alternatively, it can be applied to various wireless access technologies such as NOMA (non-orthogonal multiple access). In addition, wireless access technology not only refers to a specific access technology, but also refers to communication technology for each generation established by various communication consultative organizations such as 3GPP, 3GPP2, WiFi, Bluetooth, IEEE, and ITU. For example, CDMA can be implemented as a wireless 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). OFDMA can be implemented with wireless technologies such as IEEE (institute of electrical and electronics engineers) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802-20, E-UTRA (evolved UTRA), etc. IEEE 802.16m is an evolution of IEEE 802.16e and provides backward compatibility with systems based on IEEE 802.16e. UTRA is part of the universal mobile telecommunications system (UMTS). 3GPP (3rd generation partnership project) LTE (long term evolution) is a part of E-UMTS (evolved UMTS) that uses E-UTRA (evolved-UMTS terrestrial radio access), employing OFDMA in the downlink and SC- in the uplink. FDMA is adopted. In this way, the present embodiments can be applied to wireless access technologies currently disclosed or commercialized, and can also be applied to wireless access technologies currently under development or to be developed in the future.

Meanwhile, the terminal in this specification is a comprehensive concept meaning a device including a wireless communication module that communicates with a base station in a wireless communication system, and is used in WCDMA, LTE, NR, HSPA, and IMT-2020 (5G or New Radio), etc. It should be interpreted as a concept that includes not only UE (User Equipment), but also MS (Mobile Station), UT (User Terminal), SS (Subscriber Station), and wireless devices in GSM. In addition, a terminal may be a user portable device such as a smart phone depending on the type of use, and in a V2X communication system, it may mean a vehicle, a device including a wireless communication module within the vehicle, etc. Additionally, in the case of a machine type communication system, it may mean an MTC terminal, M2M terminal, URLLC terminal, etc. equipped with a communication module to perform machine type communication.

The base station or cell in this specification refers to an end point that communicates with a terminal in terms of a network, and includes Node-B (Node-B), evolved Node-B (eNB), gNode-B (gNB), Low Power Node (LPN), Sector, site, various types of antennas, BTS (Base Transceiver System), access point, point (e.g. transmission point, reception point, transmission/reception point), relay node ), mega cell, macro cell, micro cell, pico cell, femto cell, RRH (Remote Radio Head), RU (Radio Unit), and small cell. Additionally, a cell may mean including a bandwidth part (BWP) in the frequency domain. For example, a serving cell may mean the UE's Activation BWP.

Since the various cells listed above have a base station that controls one or more cells, base station can be interpreted in two ways. 1) It may be the device itself that provides mega cells, macro cells, micro cells, pico cells, femto cells, and small cells in relation to the wireless area, or 2) it may indicate the wireless area itself. In 1), all devices providing a predetermined wireless area are controlled by the same entity or all devices that interact to collaboratively configure the wireless area are directed to the base station. Depending on how the wireless area is configured, a point, transmission/reception point, transmission point, reception point, etc. become an example of a base station. In 2), the wireless area itself where signals are received or transmitted from the user terminal's perspective or the neighboring base station's perspective may be indicated to the base station.

In this specification, a cell refers to the coverage of a signal transmitted from a transmission/reception point, a component carrier having coverage of a signal transmitted from a transmission point or transmission/reception point, or the transmission/reception point itself. You can.

Uplink (UL, or uplink) refers to a method of transmitting and receiving data from a terminal to a base station, and downlink (Downlink, DL, or downlink) refers to a method of transmitting and receiving data from a base station to a terminal. do. Downlink may refer to communication or a communication path from multiple transmission/reception points to a terminal, and uplink may refer to communication or a communication path from a terminal to multiple transmission/reception points. At this time, in the downlink, the transmitter may be part of a multiple transmission/reception point, and the receiver may be part of the terminal. Additionally, in the uplink, a transmitter may be part of a terminal, and a receiver may be part of a multiple transmission/reception point.

Uplink and downlink transmit and receive control information through control channels such as PDCCH (Physical Downlink Control CHannel) and PUCCH (Physical Uplink Control CHannel), and PDSCH (Physical Downlink Shared CHannel), PUSCH (Physical Uplink Shared CHannel), etc. Data is transmitted and received by configuring the same data channel. Hereinafter, the situation in which signals are transmitted and received through channels such as PUCCH, PUSCH, PDCCH, and PDSCH is sometimes expressed as 'transmitting and receiving PUCCH, PUSCH, PDCCH, and PDSCH.'

For clarity of explanation, the technical idea below is mainly described in the 3GPP LTE/LTE-A/NR (New RAT) communication system, but the technical features are not limited to the corresponding communication system.

Following research on 4G (4th-Generation) communication technology, 3GPP develops 5G (5th-Generation) communication technology to meet the requirements of ITU-R's next-generation wireless access technology. Specifically, 3GPP develops LTE-A pro, which is a 5G communication technology that improves LTE-Advanced technology to meet the requirements of ITU-R, and a new NR communication technology that is separate from 4G communication technology. Both LTE-A pro and NR refer to 5G communication technology, and hereinafter, 5G communication technology will be explained focusing on NR in cases where a specific communication technology is not specified.

The operating scenario in NR defines a variety of operating scenarios by adding consideration of satellites, automobiles, and new verticals to the existing 4G LTE scenario, and in terms of service, the eMBB (Enhanced Mobile Broadband) scenario has a high terminal density but is wide. It is deployed in a wide range of applications, supporting mMTC (Massive Machine Communication) scenarios that require low data rates and asynchronous connections, and URLLC (Ultra Reliability and Low Latency) scenarios that require high responsiveness and reliability and can support high-speed mobility. .

To satisfy this scenario, NR is launching a wireless communication system with new waveform and frame structure technology, low latency technology, ultra-high frequency band (mmWave) support technology, and forward compatible technology. In particular, the NR system proposes various technical changes in terms of flexibility to provide forward compatibility. The main technical features of NR are explained below with reference to the drawings.

<NR system general>

Figure 1 is a diagram briefly illustrating the structure of an NR system to which this embodiment can be applied.

Referring to Figure 1, the NR system is divided into 5GC (5G Core Network) and NR-RAN parts, and NG-RAN controls the user plane (SDAP/PDCP/RLC/MAC/PHY) and UE (User Equipment). It consists of gNBs and ng-eNBs that provide planar (RRC) protocol termination. gNB interconnection or gNB and ng-eNB are interconnected through the Xn interface. gNB and ng-eNB are each connected to 5GC through the NG interface. 5GC may be composed of an Access and Mobility Management Function (AMF), which is responsible for the control plane such as terminal access and mobility control functions, and a User Plane Function (UPF), which is responsible for controlling user data. NR includes support for both the frequency band below 6 GHz (FR1, Frequency Range 1) and the frequency band above 6 GHz (FR2, Frequency Range 2).

gNB refers to a base station that provides NR user plane and control plane protocol termination to the terminal, and ng-eNB refers to a base station that provides E-UTRA user plane and control plane protocol termination to the terminal. The base station described in this specification should be understood to encompass gNB and ng-eNB, and may be used to refer to gNB or ng-eNB separately, if necessary.

<NR wave form, numerology and frame structure>

In NR, the CP-OFDM wave form using a cyclic prefix is used for downlink transmission, and CP-OFDM or DFT-s-OFDM is used for uplink transmission. OFDM technology is easy to combine with MIMO (Multiple Input Multiple Output) and has the advantage of being able to use a low-complexity receiver with high frequency efficiency.

Meanwhile, in NR, the requirements for data rate, delay rate, coverage, etc. are different for each of the three scenarios described above, so it is necessary to efficiently satisfy the requirements for each scenario through the frequency band that constitutes an arbitrary NR system. . To this end, a technology for efficiently multiplexing wireless resources based on a plurality of different numerologies has been proposed.

Specifically, the NR transmission numerology is determined based on sub-carrier spacing and CP (Cyclic prefix), and as shown in Table 1 below, the μ value is used as an exponent value of 2 based on 15 kHz to obtain the exponent. changes into an enemy.

μ Subcarrier spacing Cyclic prefix Supported for data Supported for synchronization 0 15 Normal Yes Yes One 30 Normal Yes Yes 2 60 Normal, Extended Yes No 3 120 Normal Yes Yes 4 240 Normal No Yes

As shown in Table 1 above, NR's numerology can be divided into five types depending on the subcarrier spacing. This is different from the subcarrier spacing of LTE, one of the 4G communication technologies, which is fixed at 15 kHz. Specifically, the subcarrier intervals used for data transmission in NR are 15, 30, 60, and 120 kHz, and the subcarrier intervals used for synchronization signal transmission are 15, 30, 12, and 240 kHz. Additionally, the extended CP applies only to the 60 kHz subcarrier spacing. Meanwhile, the frame structure in NR is defined as a frame with a length of 10ms consisting of 10 subframes with the same length of 1ms. One frame can be divided into half-frames of 5ms, and each half-frame contains 5 subframes. In the case of 15 kHz subcarrier spacing, one subframe consists of one slot, and each slot consists of 14 OFDM symbols. Figure 2 is a diagram for explaining the frame structure in an NR system to which this embodiment can be applied.

Referring to FIG. 2, a slot is fixedly composed of 14 OFDM symbols in the case of normal CP, but the length of the slot in the time domain may vary depending on the subcarrier spacing. For example, in the case of numerology with a 15 kHz subcarrier spacing, a slot is 1ms long and has the same length as a subframe. In contrast, in the case of numerology with a 30 kHz subcarrier spacing, a slot consists of 14 OFDM symbols, but two slots can be included in one subframe with a length of 0.5 ms. That is, subframes and frames are defined with a fixed time length, and slots are defined by the number of symbols, so the time length may vary depending on the subcarrier interval.

Meanwhile, NR defines the basic unit of scheduling as a slot, and also introduces a mini-slot (or sub-slot or non-slot based schedule) to reduce transmission delay in the wireless section. When a wide subcarrier spacing is used, the length of one slot is shortened in inverse proportion, so transmission delay in the wireless section can be reduced. Mini-slots (or sub-slots) are designed to efficiently support URLLC scenarios and can be scheduled in units of 2, 4, or 7 symbols.

Additionally, unlike LTE, NR defines uplink and downlink resource allocation at the symbol level within one slot. In order to reduce HARQ delay, a slot structure that can transmit HARQ ACK/NACK directly within the transmission slot has been defined, and this slot structure is described as a self-contained structure.

NR is designed to support a total of 256 slot formats, of which 62 slot formats are used in 3GPP Rel-15. In addition, it supports a common frame structure that forms an FDD or TDD frame through a combination of various slots. For example, a slot structure in which all slot symbols are set to downlink, a slot structure in which all symbols are set to uplink, and a slot structure in which downlink symbols and uplink symbols are combined are supported. Additionally, NR supports scheduling data transmission distributed over one or more slots. Therefore, the base station can use a slot format indicator (SFI) to inform the terminal whether the slot is a downlink slot, an uplink slot, or a flexible slot. The base station can indicate the slot format by indicating the index of the table configured through UE-specific RRC signaling using SFI, and can indicate it dynamically through DCI (Downlink Control Information) or statically or through RRC. It can also be indicated semi-statically.

<NR physical resources>

Regarding physical resources in NR, antenna port, resource grid, resource element, resource block, bandwidth part, etc. are considered. do.

An antenna port is defined so that a channel carrying a symbol on the antenna port can be inferred from a channel carrying another symbol on the same antenna port. If the large-scale properties of the channel carrying the symbols on one antenna port can be inferred from the channel carrying the symbols on the other antenna port, then the two antenna ports are quasi co-located or QC/QCL. It can be said that they are in a quasi co-location relationship. Here, the wide range characteristics include one or more of delay spread, Doppler spread, frequency shift, average received power, and received timing.

FIG. 3 is a diagram illustrating a resource grid supported by wireless access technology to which this embodiment can be applied.

Referring to FIG. 3, since NR supports multiple numerology on the same carrier, a resource grid may exist for each numerology. Additionally, resource grids may exist depending on antenna ports, subcarrier spacing, and transmission direction.

A resource block consists of 12 subcarriers and is defined only in the frequency domain. Additionally, a resource element consists of one OFDM symbol and one subcarrier. Therefore, as shown in FIG. 3, the size of one resource block may vary depending on the subcarrier spacing. Additionally, NR defines "Point A", which serves as a common reference point for the resource block grid, common resource blocks, virtual resource blocks, etc.

Figure 4 is a diagram for explaining the bandwidth part supported by the wireless access technology to which this embodiment can be applied.

In NR, unlike LTE, where the carrier bandwidth is fixed at 20Mhz, the maximum carrier bandwidth is set from 50Mhz to 400Mhz for each subcarrier interval. Therefore, it is not assumed that all terminals use all of these carrier bandwidths. Accordingly, in NR, the terminal can use a designated bandwidth part (BWP) within the carrier bandwidth as shown in FIG. 4. Additionally, the bandwidth part is linked to one numerology and consists of a subset of consecutive common resource blocks, and can be activated dynamically over time. The terminal is configured with up to four bandwidth parts for each uplink and downlink, and data is transmitted and received using the bandwidth parts activated at a given time.

In the case of a paired spectrum, the uplink and downlink bandwidth parts are set independently, and in the case of an unpaired spectrum, to prevent unnecessary frequency re-tunning between downlink and uplink operations. For this purpose, the bandwidth parts of the downlink and uplink are set in pairs so that they can share the center frequency.

<NR initial access>

In NR, the terminal performs cell search and random access procedures to connect to the base station and perform communication.

Cell search is a procedure in which the terminal synchronizes to the cell of the base station, obtains a physical layer cell ID, and obtains system information using a synchronization signal block (SSB) transmitted by the base station.

Figure 5 is a diagram illustrating a synchronization signal block in a wireless access technology to which this embodiment can be applied.

Referring to FIG. 5, the SSB is composed of a primary synchronization signal (PSS) and a secondary synchronization signal (SSS), each occupying 1 symbol and 127 subcarriers, and a PBCH spanning 3 OFDM symbols and 240 subcarriers.

The terminal monitors the SSB in the time and frequency domains and receives the SSB.

SSB can be transmitted up to 64 times in 5ms. Multiple SSBs are transmitted through different transmission beams within 5ms, and the terminal performs detection assuming that SSBs are transmitted every 20ms period based on one specific beam used for transmission. The number of beams that can be used for SSB transmission within 5ms time can increase as the frequency band becomes higher. For example, up to 4 different SSB beams can be transmitted under 3 GHz, up to 8 different beams can be used in the frequency band from 3 to 6 GHz, and up to 64 different beams can be used in the frequency band above 6 GHz.

Two SSBs are included in one slot, and the start symbol and number of repetitions within the slot are determined according to the subcarrier spacing as follows.

Meanwhile, unlike SS in conventional LTE, SSB is not transmitted at the center frequency of the carrier bandwidth. In other words, SSBs can be transmitted even in places other than the center of the system band, and when broadband operation is supported, multiple SSBs can be transmitted in the frequency domain. Accordingly, the terminal monitors the SSB using a synchronization raster, which is a candidate frequency location for monitoring the SSB. The carrier raster and synchronization raster, which are the center frequency location information of the channel for initial access, have been newly defined in NR, and the synchronization raster has a wider frequency interval than the carrier raster, supporting fast SSB search of the terminal. You can.

The UE can obtain the MIB through the PBCH of the SSB. MIB (Master Information Block) contains the minimum information for the terminal to receive the remaining system information (RMSI, Remaining Minimum System Information) broadcast by the network. In addition, the PBCH includes information about the location of the first DM-RS symbol in the time domain, information for the terminal to monitor SIB1 (e.g., SIB1 numerology information, information related to SIB1 CORESET, search space information, PDCCH (related parameter information, etc.), offset information between the common resource block and the SSB (the position of the absolute SSB within the carrier is transmitted through SIB1), etc. Here, the SIB1 numerology information is equally applied to some messages used in the random access procedure for accessing the base station after the terminal completes the cell search procedure. For example, numerology information of SIB1 may be applied to at least one of messages 1 to 4 for the random access procedure.

The above-mentioned RMSI may mean SIB1 (System Information Block 1), and SIB1 is broadcast periodically (ex, 160ms) in the cell. SIB1 contains information necessary for the terminal to perform the initial random access procedure and is transmitted periodically through PDSCH. In order for the terminal to receive SIB1, it must receive numerology information used for SIB1 transmission and CORESET (Control Resource Set) information used for scheduling SIB1 through the PBCH. The UE uses SI-RNTI in CORESET to check scheduling information for SIB1 and acquires SIB1 on the PDSCH according to the scheduling information. Except for SIB1, the remaining SIBs may be transmitted periodically or according to the request of the terminal.

Figure 6 is a diagram for explaining a random access procedure in wireless access technology to which this embodiment can be applied.

Referring to FIG. 6, when cell search is completed, the terminal transmits a random access preamble for random access to the base station. The random access preamble is transmitted through PRACH. Specifically, the random access preamble is transmitted to the base station through PRACH, which consists of continuous radio resources in a specific slot that is repeated periodically. Generally, when a UE initially accesses a cell, a contention-based random access procedure is performed, and when random access is performed for beam failure recovery (BFR), a non-contention-based random access procedure is performed.

The terminal receives a random access response to the transmitted random access preamble. The random access response may include a random access preamble identifier (ID), UL Grant (uplink radio resource), temporary C-RNTI (Temporary Cell - Radio Network Temporary Identifier), and TAC (Time Alignment Command). Since one random access response may include random access response information for one or more terminals, the random access preamble identifier may be included to indicate to which terminal the included UL Grant, temporary C-RNTI, and TAC are valid. The random access preamble identifier may be an identifier for the random access preamble received by the base station. TAC may be included as information for the terminal to adjust uplink synchronization. The random access response may be indicated by a random access identifier on the PDCCH, that is, RA-RNTI (Random Access - Radio Network Temporary Identifier).

The terminal that has received a valid random access response processes the information included in the random access response and performs scheduled transmission to the base station. For example, the terminal applies TAC and stores temporary C-RNTI. Additionally, using the UL Grant, data stored in the terminal's buffer or newly generated data is transmitted to the base station. In this case, information that can identify the terminal must be included.

Finally, the terminal receives a downlink message to resolve contention.

<NR CORESET>

The downlink control channel in NR is transmitted in CORESET (Control Resource Set) with a length of 1 to 3 symbols, and transmits uplink/downlink scheduling information, SFI (Slot format Index), and TPC (Transmit Power Control) information. .

In this way, in order to secure the flexibility of the system, NR introduced the CORESET concept. CORESET (Control Resource Set) refers to time-frequency resources for downlink control signals. The terminal may decode the control channel candidate using one or more search spaces in the CORESET time-frequency resource. QCL (Quasi CoLocation) assumptions were set for each CORESET, and this is used for the purpose of informing the characteristics of the analog beam direction in addition to the delay spread, Doppler spread, Doppler shift, and average delay, which are the characteristics assumed by the conventional QCL.

Figure 7 is a diagram to explain CORESET.

Referring to FIG. 7, CORESET may exist in various forms within one slot and within the carrier bandwidth, and in the time domain, CORESET may be composed of up to three OFDM symbols. Additionally, CORESET is defined as a multiple of 6 resource blocks from the frequency domain to the carrier bandwidth.

The first CORESET is directed through the MIB as part of the initial bandwidth part configuration to enable it to receive additional configuration and system information from the network. After establishing a connection with the base station, the terminal can receive and configure one or more CORESET information through RRC signaling.

In this specification, frequencies, frames, subframes, resources, resource blocks, regions, bands, subbands, control channels, data channels, synchronization signals, various reference signals, various signals, or various messages related to NR (New Radio) can be interpreted in a variety of meanings that may be used in the past or present, or may be used in the future.

NR(New Radio)

NR, which was recently developed in 3GPP, was designed to not only provide improved data transmission rates compared to LTE, but also to satisfy various QoS requirements for each segmented and specific service requirement (usage scenario). In particular, eMBB (enhancement Mobile BroadBand), mMTC (massive Machine Type Communication), and URLLC (Ultra Reliable and Low Latency Communications) were defined as representative service requirements (usage scenarios) of NR, and the requirements for each service requirement (usage scenario) were defined. As a way to satisfy this, a flexible frame structure design compared to LTE/LTE-Advanced is required.

Since each service requirement (usage scenario) has different requirements for data rates, latency, reliability, coverage, etc., the frequencies that make up an arbitrary NR system Radio resource units based on different numerologies (e.g., subcarrier spacing, subframe, TTI, etc.) as a method to efficiently satisfy the needs of each service requirement (usage scenario) through the band. It is designed for efficient multiplexing.

As a method for this, TDM, FDM or TDM/FDM based on one or multiple NR component carrier(s) for numerology with different subcarrier spacing values. There was discussion on how to support multiplexing and how to support more than one time unit when configuring a scheduling unit in the time domain. In this regard, in NR, a subframe has been defined as a type of time domain structure, and reference numerology is used to define the subframe duration. It was decided to define a single subframe duration consisting of 14 OFDM symbols of normal CP overhead based on 15kHz Sub-Carrier Spacing (SCS), which is the same as LTE. Accordingly, in NR, a subframe has a time duration of 1ms. However, unlike LTE, the subframe of NR is an absolute reference time duration, and is a time unit based on actual uplink/downlink data scheduling, using slots and mini-slots. ) can be defined. In this case, the number and y value of OFDM symbols constituting the corresponding slot were determined to have a value of y=14 regardless of the SCS value in the case of normal CP.

Accordingly, any slot consists of 14 symbols, and depending on the transmission direction of the slot, all symbols are used for downlink transmission (DL transmission), or all symbols are used for uplink transmission (UL). It can be used for transmission, or in the form of a downlink portion (DL portion) + gap + uplink portion (UL portion).

In addition, in any numerology (or SCS), a mini-slot consisting of fewer symbols than the slot is defined, and based on this, a short time-domain scheduling interval (time-domain) for transmitting and receiving uplink/downlink data is defined. A scheduling interval may be set, or a long time-domain scheduling interval may be configured for up/downlink data transmission and reception through slot aggregation.

In particular, in the case of transmission and reception of latency critical data such as URLLC, a 1ms (14 symbols) based frame structure defined in numerology with a small SCS value such as 15kHz is used. If scheduling is done on a slot-by-slot basis, it may be difficult to satisfy the latency requirement. Therefore, for this purpose, a mini-slot consisting of fewer OFDM symbols than the corresponding slot is defined and based on this, a critical delay rate such as the URLLC is defined. It can be defined so that scheduling is performed for (latency critical) data.

Or, as described above, by multiplexing and supporting numerology with different SCS values within one NR carrier using the TDM and/or FDM method, each numerology A method of scheduling data according to latency requirements based on defined slot (or mini-slot) length is also being considered. For example, as shown in Figure 8 below, when the SCS is 60kHz, the symbol length is reduced to about 1/4 compared to the SCS 15kHz, so when one slot is configured with the same 14 OFDM symbols, the 15kHz-based The slot length is 1ms, while the 60kHz-based slot length is reduced to about 0.25ms.

As such, in NR, discussions are underway on how to satisfy the requirements of URLLC and eMBB by defining different SCS or different TTI lengths.

Wider bandwidth operations

In the case of the existing LTE system, scalable bandwidth operation for any LTC CC (Component Carrier) was supported. In other words, depending on the frequency deployment scenario, any LTE operator could configure a bandwidth from a minimum of 1.4 MHz to a maximum of 20 MHz when configuring one LTE CC, and a normal LTE terminal can configure one LTE CC. For CC, transmission and reception capabilities of 20 MHz bandwidth were supported.

However, in the case of NR, the design is made to enable support for NR terminals with different transmission and reception bandwidth capabilities through one wideband NR CC, and accordingly, Figure 9 below and Likewise, one or more bandwidth parts (BWP, bandwidth part(s)) consisting of segmented bandwidths are configured for any NR CC, and flexible (bandwidth part(s)) is configured through different bandwidth part configuration and activation for each terminal. It is required to support flexible wider bandwidth operation.

Specifically, in NR, one or more bandwidth parts can be configured through one serving cell configured from the terminal's perspective, and the terminal can configure one downlink bandwidth part ( It is defined to be used for uplink/downlink data transmission and reception by activating a DL bandwidth part) and one uplink bandwidth part (UL bandwidth part). In addition, when multiple serving cells are configured in the corresponding terminal, that is, for terminals to which CA is applied, one downlink bandwidth part and/or uplink bandwidth part is activated for each serving cell. Therefore, it was defined to be used for up/downlink data transmission and reception using the radio resources of the corresponding serving cell.

Specifically, the initial bandwidth part for the initial access procedure of the terminal is defined in any serving cell, and for each terminal, one or more terminal-specific (UE) signals are provided through dedicated RRC signaling. -specific) bandwidth part(s) may be configured, and a default bandwidth part for fallback operation may be defined for each terminal.

However, in any serving cell, multiple downlink and/or uplink bandwidth parts can be activated and used simultaneously depending on the terminal's capability and bandwidth part(s) configuration. However, in NR rel-15, it is defined to activate and use only one downlink bandwidth part (DL bandwidth part) and one uplink bandwidth part (UL bandwidth part) at any time in any terminal. .

HARQ ACK/NACK feedback resource allocation method

According to the PUCCH resource allocation method for UE's HARQ ACK/NACK feedback defined in NR, the base station configures a PUCCH resource set consisting of one or more PUCCH resources for any UE, and provides HARQ ACK/NACK for any PDSCH transmission. It is defined to indicate the PUCCH resource information to be used for NACK feedback through the ARI (ACK Resource Indicator) information area of the DCI. However, the PUCCH resource set is configured for each UL BWP configured for the corresponding terminal, and separate PUCCH resource sets are configured according to the payload size of HARQ ACK/NACK for any UL BWP.

Hereinafter, a method for transmitting and receiving uplink control information will be described in detail with reference to the related drawings.

Figure 10 is a diagram illustrating a procedure for a terminal to transmit uplink control information according to an embodiment.

Referring to FIG. 10, the terminal may receive configuration information about a slot-based uplink control channel (PUCCH) resource set and a subslot-based uplink control channel resource set from the base station ( S1000).

An uplink control channel resource set to be used to transmit uplink control information to the terminal may be configured. For example, in order to transmit HARQ ACK/NACK feedback information for the PDSCH received from the base station, a PUCCH resource set consisting of one or more PUCCH resources may be configured for the terminal.

According to one example, separately from this PUCCH resource set setting, a PUCCH resource set for intra-slot PUCCH repetition may be additionally configured. In other words, the base station uses upper layer signaling to additionally apply intra-slot PUCCH repetition in addition to the existing PUCCH resource set (hereinafter, 'slot-based PUCCH resource set' or 'type-1 PUCCH resource set') to the terminal. A PUCCH resource set (hereinafter referred to as 'subslot-based PUCCH resource set' or 'type-2 PUCCH resource set') can be set.

The terminal may receive configuration information for the slot-based PUCCH resource set and configuration information for the subslot-based PUCCH resource set from the base station, respectively. According to one example, the base station configures a separate subslot-based PUCCH resource set depending on whether the UE's PUCCH transmission type is a conventional slot-based PUCCH transmission or subslot-based PUCCH repetition transmission (or multiple PUCCH transmission) to transmit the upper layer It can be transmitted to the terminal through signaling.

In this case, the configuration information for the subslot-based PUCCH resource set may additionally include repetition number setting information for transmission of uplink control information in addition to the PUCCH resource setting information constituting the slot-based PUCCH resource set. there is.

Alternatively, configuration information for the subslot-based PUCCH resource set may include information on the number of subslots configured in one slot. That is, for a UE, the number or length of uplink subslots in one slot may be configured UE-specifically semi-statically. For one intra-slot PUCCH repetition resource setting, separate time section or frequency section allocation information may be included for each intra-slot PUCCH repetition. That is, for intra-slot PUCCH repetition, each slot can be divided into subslots, and PUCCH resource allocation information can be configured for each subslot.

According to one example, when the uplink control information is HARQ feedback information, the slot-based uplink control channel resource set and the subslot-based uplink control channel resource set may be configured based on different HARQ-ACK codebooks. there is. That is, in order to support different service types of the terminal, at least two HARQ-ACK codebooks can be configured simultaneously. In this case, parameters in the PUCCH configuration related to HARQ-ACK feedback for different HARQ-ACK codebooks may be configured separately. Identification of the HARQ-ACK codebook can be distinguished by DCI format, by the RNTI of the terminal, by explicit instructions in the DCI, or by core set/search space.

Referring again to FIG. 10, the terminal may receive information indicating a subslot-based uplink control channel resource set from the base station (S1010).

When providing HARQ ACK/NACK feedback for the UE's PDSCH reception, whether to apply intra-slot PUCCH repetition to improve reliability may be explicitly or implicitly signaled by the base station.

According to one example, the terminal may receive intra-slot PUCCH repetition indication information as information indicating a subslot-based uplink control channel resource set from the base station through explicit higher layer signaling. For example, intra-slot PUCCH repetition indication information may be set semi-statically through UE-specific RRC signaling, or may be activated or deactivated through MAC CE signaling.

Alternatively, the terminal may receive intra-slot PUCCH repetition indication information as information indicating a subslot-based uplink control channel resource set through a DCI format for transmitting PDSCH resource allocation information. That is, the DL assignment DCI format for transmitting PDSCH resource allocation information may include an information area for indicating whether intra-slot PUCCH repetition is applied. The base station can dynamically indicate whether to apply intra-slot PUCCH repetition through the corresponding information area.

According to one example, information indicating a subslot-based uplink control channel resource set is configured based on a downlink control channel search space or a terminal RNTI (Radio Network Temporary Identifier) and is implicitly indicated. You can. That is, the terminal can receive information indicating a subslot-based uplink control channel resource set, such as CORESET or search space, or information about the terminal RNTI.

Specifically, when configuring a CORESET or search space, setting information about the PUCCH transmission type for PDSCH allocation through the CORESET or search space may be included. Here, the PUCCH transmission type can be divided into slot-based PUCCH transmission or subslot-based PUCCH transmission. In this case, whether to apply the corresponding intra-slot PUCCH repetition can be determined by the CORESET or search space through which the DCI format including arbitrary PDSCH resource allocation information is transmitted.

Alternatively, if the RNTI applied to CRC scrambling in DCI format containing resource allocation information for PDSCH is MCS-C-RNTI, intra-slot PUCCH repetition is applied, otherwise, intra-slot PUCCH repetition is not applied. You can. Alternatively, by allocating a separate new RNTI for intra-slot PUCCH repetition application, PDSCH transmission resource allocation requiring intra-slot PUCCH repetition application can be configured to transmit by performing CRC scrambling based on the new RNTI.

Referring again to FIG. 10, the terminal can repeatedly transmit uplink control information within one slot using the uplink control channel resources of the subslot-based uplink control channel resource set (S1020).

According to one example, when the base station indicates PUCCH resource allocation information through a PUCCH resource indicator in DCI format, the terminal may interpret the PUCCH resource allocation information based on whether intra-slot PUCCH repetition is applied. . That is, when instructed/configured not to apply intra-slot PUCCH repetition, the base station may indicate PUCCH resource allocation information based on the type-1 PUCCH resource set. The terminal can transmit uplink control information using the corresponding PUCCH resources.

In contrast, when instructed/configured to apply intra-slot PUCCH repetition, the base station may indicate PUCCH resource allocation information based on a new type-2 PUCCH resource set. The terminal can repeatedly transmit uplink control information for each subslot constituting one slot using the corresponding PUCCH resources.

According to this, it is possible to provide a specific method and device that can improve reliability of the uplink control channel according to repeated transmission of uplink control information.

Figure 11 is a diagram illustrating a procedure for a base station to receive uplink control information according to an embodiment.

Referring to FIG. 11, the base station may transmit configuration information about the slot-based uplink control channel (PUCCH) resource set and the subslot-based uplink control channel resource set to the terminal (S1100) ).

The base station can configure an uplink control channel resource set to be used to transmit uplink control information to the terminal. For example, in order to transmit HARQ ACK/NACK feedback information for the PDSCH received from the base station, a PUCCH resource set consisting of one or more PUCCH resources may be configured for the terminal.

According to one example, separately from this PUCCH resource set setting, a PUCCH resource set for intra-slot PUCCH repetition may be additionally configured. That is, the base station can set a PUCCH resource set for applying intra-slot PUCCH repetition in addition to the existing PUCCH resource set for the terminal through higher layer signaling.

The base station may transmit configuration information for the slot-based PUCCH resource set and configuration information for the subslot-based PUCCH resource set to the terminal, respectively. According to one example, the base station can configure a separate subslot-based PUCCH resource set and transmit it to the terminal through higher layer signaling, depending on whether the PUCCH transmission type of the terminal is a conventional slot-based PUCCH transmission or subslot-based PUCCH repeated transmission. there is.

In this case, the configuration information for the subslot-based PUCCH resource set may additionally include repetition number setting information for transmission of uplink control information in addition to the PUCCH resource setting information constituting the slot-based PUCCH resource set.

Alternatively, configuration information for the subslot-based PUCCH resource set may include information on the number of subslots configured in one slot. That is, for a UE, the number or length of uplink subslots in one slot may be configured UE-specifically semi-statically. For one intra-slot PUCCH repetition resource setting, separate time section or frequency section allocation information may be included for each intra-slot PUCCH repetition. That is, for intra-slot PUCCH repetition, each slot can be divided into subslots, and PUCCH resource allocation information can be configured for each subslot.

According to one example, when the uplink control information is HARQ feedback information, the slot-based uplink control channel resource set and the subslot-based uplink control channel resource set may be configured based on different HARQ-ACK codebooks. there is. That is, in order to support different service types of the terminal, at least two HARQ-ACK codebooks can be configured simultaneously. In this case, parameters in the PUCCH configuration related to HARQ-ACK feedback for different HARQ-ACK codebooks may be configured separately. Identification of the HARQ-ACK codebook can be distinguished by DCI format, by the RNTI of the terminal, by explicit instructions in the DCI, or by core set/search space.

Referring again to FIG. 11, the base station may transmit information indicating a subslot-based uplink control channel resource set to the terminal (S1110).

According to one example, the base station may transmit intra-slot PUCCH repetition indication information as information indicating a subslot-based uplink control channel resource set to the terminal through explicit higher layer signaling. For example, the base station can semi-statically set intra-slot PUCCH repetition indication information through UE-specific RRC signaling, or activate or deactivate it through MAC CE signaling.

Alternatively, the base station may transmit intra-slot PUCCH repetition indication information as information indicating a subslot-based uplink control channel resource set through a DCI format for transmitting PDSCH resource allocation information. That is, the DL assignment DCI format for transmitting PDSCH resource allocation information may include an information area for indicating whether intra-slot PUCCH repetition is applied. The base station can dynamically indicate whether to apply intra-slot PUCCH repetition through the corresponding information area.

According to one example, information indicating a subslot-based uplink control channel resource set is configured based on a downlink control channel search space or a terminal RNTI (Radio Network Temporary Identifier) and is implicitly indicated. You can. That is, the base station can transmit information indicating a subslot-based uplink control channel resource set, such as CORESET or search space, or information about the terminal RNTI.

Specifically, when configuring a CORESET or search space, setting information about the PUCCH transmission type for PDSCH allocation through the CORESET or search space may be included. Here, the PUCCH transmission type can be divided into slot-based PUCCH transmission or subslot-based PUCCH transmission. In this case, whether to apply the corresponding intra-slot PUCCH repetition can be determined by the CORESET or search space through which the DCI format including arbitrary PDSCH resource allocation information is transmitted.

Alternatively, if the RNTI applied to CRC scrambling in DCI format containing resource allocation information for PDSCH is MCS-C-RNTI, intra-slot PUCCH repetition is applied, otherwise, intra-slot PUCCH repetition is not applied. You can. Alternatively, by allocating a separate new RNTI for intra-slot PUCCH repetition application, PDSCH transmission resource allocation requiring intra-slot PUCCH repetition application can be configured to transmit by performing CRC scrambling based on the new RNTI.

Referring again to FIG. 11, the base station can repeatedly receive uplink control information within one slot using the uplink control channel resources of the subslot-based uplink control channel resource set (S1120).

According to one example, when the base station indicates PUCCH resource allocation information through a PUCCH resource indicator in DCI format, the terminal may interpret the PUCCH resource allocation information based on whether intra-slot PUCCH repetition is applied. . That is, when instructed/configured not to apply intra-slot PUCCH repetition, the base station may indicate PUCCH resource allocation information based on the type-1 PUCCH resource set. Accordingly, the base station can receive uplink control information transmitted by the terminal using PUCCH resources.

In contrast, when instructed/configured to apply intra-slot PUCCH repetition, the base station may indicate PUCCH resource allocation information based on a new type-2 PUCCH resource set. Accordingly, the base station can repeatedly receive uplink control information that the terminal repeatedly transmits for each subslot within one slot using PUCCH resources.

According to this, it is possible to provide a specific method and device that can improve reliability of the uplink control channel according to repeated transmission of uplink control information.

Hereinafter, with reference to the related drawings, each embodiment related to the configuration and allocation of radio resources for repeated transmission of subslot-based uplink control information within one slot will be described in detail.

This disclosure proposes a PUCCH resource allocation method for repeatedly transmitting UCI through one slot in an NR system.

As described above, the PUCCH resource for transmitting HARQ ACK/NACK feedback information for PDSCH reception of any UE in NR is a PUCCH resource indicator information area in DCI format including the corresponding PDSCH resource allocation information. It is directed through. Specifically, up to 4 PUCCH resource sets for any UE can be configured by the base station, and each PUCCH resource set can consist of up to 16 PUCCH resources. In addition, PUCCH resources for HARQ ACK/NACK feedback for PDSCH reception of any UE are allocated through implicit mapping with the PUCCH resource indicator.

In NR, there is a need to improve the reliability of uplink data and control channels and downlink data and control channels to provide URLLC services. Accordingly, a method of repeatedly transmitting arbitrary uplink control information through one slot can be applied as a method of improving reliability for PUCCH, an uplink control channel. In this disclosure, we propose a PUCCH resource allocation method for applying intra-slot PUCCH repetition, in which the same UCI is repeatedly transmitted through a single slot to improve reliability of the uplink control channel.

Example 1. Definition of intra-slot PUCCH repetition indication

When providing HARQ ACK/NACK feedback for PDSCH reception at any terminal, it can be defined to explicitly or implicitly signal the application of intra-slot PUCCH repetition to improve reliability by the base station. You can.

Specifically, the corresponding intra-slot PUCCH repetition indication information may be explicitly signaled. According to one example, the corresponding intra-slot PUCCH repetition indication information may be set to semi-static through UE-specific RRC signaling.

According to another example, intra-slot PUCCH repetition indication information may be activated or deactivated by intra-slot PUCCH repetition through MAC control element (CE) signaling.

According to another example, intra-slot PUCCH repetition indication information may be transmitted through a DCI format for transmitting PDSCH resource allocation information. That is, through the DL assignment DCI format for transmitting PDSCH resource allocation information, an information area for indicating whether to apply the intra-slot PUCCH repetition, for example, an intra-slot PUCCH repetition indicator, is defined to include , through this, the base station can define whether to dynamically apply intra-slot PUCCH repetition.

Alternatively, intra-slot PUCCH repetition indication information may be signaled implicitly. According to one example, whether to apply the intra-slot PUCCH repetition may be determined according to an arbitrary PDSCH transmission duration. For example, if the PDSCH transmission is slot-based transmission or aggregated slot-based transmission, the intra-slot PUCCH repetition may not be applied. On the other hand, if the PDSCH transmission is a non-slot based transmission such as a minislot of 2, 4, or 7 symbols, which are units smaller than one slot, the intra-slot PUCCH repetition is applied. It can be defined as:

Or, according to another example, when configuring a core set or search space, setting information on the PUCCH transmission type for PDSCH allocation through the corresponding CORESET or search space is provided. It can be included. Here, the PUCCH transmission type can be divided into existing slot-based PUCCH transmission or subslot-based PUCCH transmission for intra-slot PUCCH repetition application. In this case, it can be defined that whether or not the intra-slot PUCCH repetition is applied is determined by the CORESET or search space in which the DCI format including arbitrary PDSCH resource allocation information is transmitted.

According to another example, if the RNTI (Radio Network Temporary Identifier) applied to CRC scrambling in DCI format including resource allocation information for PDSCH is MCS-C-RNTI, intra-slot PUCCH repetition is applied and , otherwise, it can be defined not to apply intra-slot PUCCH repetition. Alternatively, by allocating a separate new RNTI (new RNTI) for intra-slot PUCCH repetition application, PDSCH transmission resource allocation requiring intra-slot PUCCH repetition can be defined to be transmitted by CRC scrambling based on the new RNTI. there is.

Additionally, among the above-described intra-slot PUCCH repetition application methods, except for the example through UE-specific higher layer signaling, the remaining examples can be applied in a hybrid form with the higher layer signaling configuration method. there is. That is, whether to apply intra-slot PUCCH repetition is preferentially set by the base station for each terminal or on a cell basis through UE-specific or cell-specific higher layer signaling, and accordingly, the above-mentioned It can be defined to secondarily indicate whether to apply intra-slot PUCCH repetition by using methods.

For example, in the case of an indication method using an intra-slot PUCCH repetition indicator in the DCI format, the setting of whether to apply intra-slot PUCCH repetition is primarily made through UE-specific or cell-specific upper layer signaling, and accordingly, within the DCI format Whether or not to include the intra-slot PUCCH repetition indicator information area may be determined. In this case, when the inclusion of the intra-slot PUCCH repetition indicator information area in the DCI format is set through the corresponding upper layer signaling, the base station secondarily determines whether to apply intra-slot PUCCH repetition dynamically through the corresponding intra-slot PUCCH repetition indicator. It can be defined to signal. Likewise, the same can be applied to the MAC CE signaling method or implicit signaling method.

Example 2. Intra-slot PUCCH repetition method

When intra-slot PUCCH repetition is applied according to the above-described Embodiment 1, it is necessary to define a method for allocating PUCCH resources that are repeatedly transmitted through a single slot. However, the following description can be applied substantially the same even when intra-slot PUCCH repetition is applied by a method other than Example 1.

According to one example, a PUCCH resource set for intra-slot PUCCH repetition may be defined to be set separately from the existing PUCCH resource set setting. In other words, the base station provides additional intra-slot PUCCH repetition in addition to the existing PUCCH resource set (e.g., type-1 PUCCH resource set) to which intra-slot PUCCH repetition is not applied to any UE through upper layer signaling. It can be defined to set a PUCCH resource set (for example, type-2 PUCCH resource set) to apply.

In this case, the base station indicates PUCCH resource allocation information through the PUCCH resource indicator in DCI format, and when the terminal interprets this, intra-slot PUCCH repetition is not applied depending on whether intra-slot PUCCH repetition is applied. If instructed/configured not to do so, the base station may indicate PUCCH resource allocation information based on the type-1 PUCCH resource set, and the terminal may interpret it. Conversely, when instructed/configured to apply intra-slot PUCCH repetition, PUCCH resource allocation information can be instructed by the base station and interpreted by the terminal based on the new type-2 PUCCH resource set.

In addition, the setting information of the PUCCH resources constituting the type-2 PUCCH resource set includes additional repetition number setting information in addition to the PUCCH resource setting information constituting the type-1 PUCCH resource set, or one intra-slot PUCCH Repletion resource settings can be defined to include separate time or frequency section allocation information for each intra-slot PUCCH repetition. That is, for intra-slot PUCCH repetition, each slot can be divided into subslots, and PUCCH resource allocation information can be configured for each subslot.

According to another example, intra-slot PUCCH repetition can be defined to be applied based on PUCCH resources constituting an existing allocated PUCCH resource set. In this case, the number of corresponding PUCCH repetitions and the symbol resource in which each repetition is performed are a function of the time interval resource allocation information of the PUCCH resource indicated through the PUCCH resource indicator and the number of uplink symbols constituting the slot in which the corresponding PUCCH is transmitted. It can be defined to be determined.

Alternatively, it can be defined that the base station signals intra-slot repetition number information in addition to the PUCCH resource indicator through DCI. In this case, the symbol resource in which each repetition is performed according to the time interval resource allocation information of the PUCCH resource indicated through the PUCCH resource indicator, the number of uplink symbols constituting the slot in which the PUCCH is transmitted, and the indicated intra-slot repetition number information. This can be defined to be determined. However, whether or not to include the information area indicating the number of intra-slot repetitions through the corresponding DCI format is determined depending on whether intra-slot PUCCH repetition is set according to the above-described embodiment 1, or is determined by a terminal-specific or cell-specific upper layer by the base station. It can be set through signaling.

Hereinafter, a method of applying PUCCH resource allocation for HARQ ACK/NACK feedback transmission for PDSCH reception of the terminal will be described in detail based on the contents proposed in the above-described embodiments 1 and 2.

First, according to the specific PUCCH resource set configuration method presented in Example 2, the base station/network can configure different types of PUCCH resource sets for any UE. That is, when configuring a PUCCH resource set for an arbitrary terminal in a base station/network, the service type or the corresponding PDSCH group and the corresponding PUCCH transmission type, that is, the existing slot-based PUCCH transmission, are intra -slot PUCCH repetition/multiple A separate PUCCH resource set can be configured depending on whether it is a subslot-based PUCCH transmission for PUCCH transmission and transmitted to each terminal through higher layer signaling.

Here, a specific example of distinguishing the service type is to distinguish whether any PDSCH transmission is a PDSCH transmission for providing eMBB service or a PDSCH transmission for providing URLLC service. The PDSCH group is a service type for arbitrary PDSCH transmission at the upper layer level such as the physical layer, MAC layer, RLC, or PDCP/RRC depending on the service type in the air interface that constitutes the RAN (Radio Access Network). As a method for classification, it means dividing each PDSCH transmission into a group according to the service type to which the corresponding PDSCH transmission belongs (i.e., provided by the corresponding PDSCH transmission). Accordingly, a PDSCH group ID can be defined for any PDSCH transmission, and according to the corresponding PDSCH group ID value, the service type to which any PDSCH transmission belongs and the corresponding requirement, or the corresponding PDSCH transmission as described above. The PUCCH transmission type for HARQ ACK/NACK feedback and the type of the PUCCH resource set of Embodiment 2, which is the PUCCH resource set configuration accordingly, can be distinguished.

Therefore, as presented in Example 2, when different types of PUCCH resource sets are configured for an arbitrary UE, the PUCCH resource set type to be applied for HARQ ACK/NACK feedback in the corresponding UE for arbitrary PDSCH transmission As a method for setting/instructing, when applying the explicit or implicit setting/instructing method through RRC signaling, MAC CE signaling, or L1 control signaling presented in Example 1, the corresponding setting/instructing information is set to Example 1. It may be defined as information that directly sets/instructs the PUCCH resource set type presented in, or information that sets/instructs a PDSCH group or service type, etc. may be defined, and an indirect setting/instruction method through this may also be included.

That is, when configuring the PUCCH resource set in Example 2, setting the PUCCH resource set for one or more types may be in the form of configuring the PUCCH resource set for one or more PDSCH groups, or configuring the PUCCH resource set for each service type, or slot-based or It can be applied as a form of configuring a PUCCH resource set for each subslot-based PUCCH transmission type. In this case, the explicit or implicit indication method through RRC signaling, MAC CE signaling, or L1 control signaling proposed in Example 1, PDSCH group indication, service type indication, or slot/subslot PUCCH transmission type indication, etc. It can be applied as a form.

According to this, it is possible to provide a specific method and device that can improve reliability of the uplink control channel according to repeated transmission of uplink control information.

Hereinafter, the configuration of a user terminal and a base station capable of performing some or all of the embodiments described with reference to FIGS. 1 to 11 will be described with reference to the drawings.

Figure 12 is a diagram showing the configuration of a user equipment (User Equipment, 1200) according to another embodiment.

Referring to FIG. 12, a user terminal 1200 according to another embodiment includes a control unit 1210, a transmitter 1220, and a receiver 1230.

The control unit 1210 controls the overall operation of the user terminal 1200 according to the method by which the user terminal transmits uplink control information necessary to perform the present invention described above. The transmitter 1220 transmits uplink control information, data, and messages to the base station through the corresponding channel. The receiving unit 1230 receives downlink control information, data, messages, etc. from the base station through the corresponding channel.

The receiving unit 1230 may receive configuration information about the slot-based PUCCH resource set and the subslot-based PUCCH resource set from the base station. An uplink control channel resource set to be used to transmit uplink control information to the terminal may be configured. According to one example, separate from this PUCCH resource set configuration, a PUCCH resource set for repeated PUCCH transmission within a slot may be additionally configured. That is, the base station can set a PUCCH resource set for applying intra-slot PUCCH repetition in addition to the existing PUCCH resource set for the terminal through higher layer signaling.

The receiving unit 1230 may receive configuration information about the slot-based PUCCH resource set and configuration information about the subslot-based PUCCH resource set from the base station, respectively. According to one example, the base station can configure a separate subslot-based PUCCH resource set and transmit it to the terminal through higher layer signaling, depending on whether the PUCCH transmission type of the terminal is a conventional slot-based PUCCH transmission or subslot-based PUCCH repeated transmission. there is.

In this case, the configuration information for the subslot-based PUCCH resource set may additionally include repetition number setting information for transmission of uplink control information in addition to the PUCCH resource setting information constituting the slot-based PUCCH resource set.

Alternatively, configuration information for the subslot-based PUCCH resource set may include information on the number of subslots configured in one slot. That is, for a terminal, the number or length of uplink subslots within one slot can be semi-statically configured for the terminal. For one intra-slot PUCCH repetition resource setting, separate time section or frequency section allocation information may be included for each intra-slot PUCCH repetition. That is, for intra-slot PUCCH repetition, each slot can be divided into subslots, and PUCCH resource allocation information can be configured for each subslot.

The receiving unit 1230 may receive information indicating a subslot-based uplink control channel resource set from the base station.

According to one example, the receiver 1230 may receive intra-slot PUCCH repetition indication information, which is information indicating a subslot-based uplink control channel resource set, from the base station through explicit higher layer signaling. For example, intra-slot PUCCH repetition indication information may be set semi-statically through UE-specific RRC signaling, or may be activated or deactivated through MAC CE signaling.

Alternatively, the receiver 1230 may receive intra-slot PUCCH repetition indication information as information indicating a subslot-based uplink control channel resource set through a DCI format for transmitting PDSCH resource allocation information. That is, the DL assignment DCI format for transmitting PDSCH resource allocation information may include an information area for indicating whether intra-slot PUCCH repetition is applied. The base station can dynamically indicate whether to apply intra-slot PUCCH repetition through the corresponding information area.

According to one example, information indicating a subslot-based PUCCH resource set may be configured based on a downlink control channel search space or a terminal RNTI and may be implicitly indicated. That is, the receiver 1230 can receive information indicating a subslot-based uplink control channel resource set, such as CORESET or search space, or information about the terminal RNTI.

Specifically, when configuring a CORESET or search space, setting information about the PUCCH transmission type for PDSCH allocation through the CORESET or search space may be included. Here, the PUCCH transmission type can be divided into slot-based PUCCH transmission or subslot-based PUCCH transmission. In this case, whether to apply the corresponding intra-slot PUCCH repetition can be determined by the CORESET or search space through which the DCI format including arbitrary PDSCH resource allocation information is transmitted.

Alternatively, if the RNTI applied to CRC scrambling in DCI format containing resource allocation information for PDSCH is MCS-C-RNTI, intra-slot PUCCH repetition is applied, otherwise, intra-slot PUCCH repetition is not applied. You can. Alternatively, by allocating a separate new RNTI for intra-slot PUCCH repetition application, PDSCH transmission resource allocation requiring intra-slot PUCCH repetition application can be configured to transmit by performing CRC scrambling based on the new RNTI.

The transmitter 1220 may repeatedly transmit uplink control information within one slot using PUCCH resources of the subslot-based PUCCH resource set.

According to one example, when the base station indicates PUCCH resource allocation information through a PUCCH resource indicator in DCI format, the control unit 1210 may interpret the PUCCH resource allocation information based on whether intra-slot PUCCH repetition is applied. That is, when instructed/configured not to apply intra-slot PUCCH repetition, the base station may indicate PUCCH resource allocation information based on the type-1 PUCCH resource set. The transmitter 1220 can transmit uplink control information using the corresponding PUCCH resources.

In contrast, when instructed/configured to apply intra-slot PUCCH repetition, the base station may indicate PUCCH resource allocation information based on a new type-2 PUCCH resource set. The transmitter 1220 can repeatedly transmit uplink control information for each subslot constituting one slot using PUCCH resources.

According to this, it is possible to provide a specific method and device that can improve reliability of the uplink control channel according to repeated transmission of uplink control information.

FIG. 13 is a diagram showing the configuration of a base station 1300 according to another embodiment.

Referring to FIG. 13, a base station 1300 according to another embodiment includes a control unit 1310, a transmitter 1320, and a receiver 1330.

The control unit 1310 controls the overall operation of the base station 1300 according to the method by which the base station receives uplink control information necessary to perform the present invention described above. The transmitting unit 1320 and the receiving unit 1330 are used to transmit and receive signals, messages, and data necessary to perform the present invention described above with the terminal.

The transmitter 1320 may transmit configuration information about the slot-based PUCCH resource set and the subslot-based PUCCH resource set to the terminal (S1100).

The control unit 1310 can configure a PUCCH resource set to be used to transmit uplink control information to the terminal. For example, in order to transmit HARQ ACK/NACK feedback information for the PDSCH received from the base station, a PUCCH resource set consisting of one or more PUCCH resources may be configured for the terminal.

According to one example, separately from this PUCCH resource set setting, a PUCCH resource set for intra-slot PUCCH repetition may be additionally configured. That is, the control unit 1310 can set a PUCCH resource set for applying intra-slot PUCCH repetition in addition to the existing PUCCH resource set for the terminal through higher layer signaling.

The transmitter 1320 may transmit configuration information about the slot-based PUCCH resource set and configuration information about the subslot-based PUCCH resource set to the terminal, respectively. According to one example, the transmitter 1320 configures a separate subslot-based PUCCH resource set depending on whether the PUCCH transmission type of the terminal is an existing slot-based PUCCH transmission or subslot-based PUCCH repeated transmission, and transmits the terminal to the terminal through higher layer signaling. It can be sent to .

In this case, the configuration information for the subslot-based PUCCH resource set may additionally include repetition number setting information for transmission of uplink control information in addition to the PUCCH resource setting information constituting the slot-based PUCCH resource set.

Alternatively, configuration information for the subslot-based PUCCH resource set may include information on the number of subslots configured in one slot. That is, for a UE, the number or length of uplink subslots in one slot may be configured UE-specifically semi-statically. For one intra-slot PUCCH repetition resource setting, separate time section or frequency section allocation information may be included for each intra-slot PUCCH repetition. That is, for intra-slot PUCCH repetition, each slot can be divided into subslots, and PUCCH resource allocation information can be configured for each subslot.

The transmitter 1320 may transmit information indicating a subslot-based uplink control channel resource set to the terminal.

According to one example, the transmitter 1320 may transmit intra-slot PUCCH repetition indication information as information indicating a subslot-based uplink control channel resource set to the terminal through explicit higher layer signaling. For example, the transmitter 1320 may set the intra-slot PUCCH repetition indication information semi-statically through UE-specific RRC signaling, or activate or deactivate it through MAC CE signaling.

Alternatively, the transmitter 1320 may transmit intra-slot PUCCH repetition indication information as information indicating a subslot-based uplink control channel resource set through a DCI format for transmitting PDSCH resource allocation information. That is, the DL assignment DCI format for transmitting PDSCH resource allocation information may include an information area for indicating whether intra-slot PUCCH repetition is applied. The transmitter 1320 can dynamically indicate whether to apply intra-slot PUCCH repetition through the corresponding information area.

According to one example, information indicating a subslot-based uplink control channel resource set may be configured based on a downlink control channel search space or a terminal RNTI and may be implicitly indicated. That is, the transmitter 1320 may transmit information indicating a subslot-based uplink control channel resource set, such as CORESET or search space, or information about the terminal RNTI.

Specifically, when configuring a CORESET or search space, setting information about the PUCCH transmission type for PDSCH allocation through the corresponding CORESET or search space may be included. Here, the PUCCH transmission type can be divided into slot-based PUCCH transmission or subslot-based PUCCH transmission. In this case, whether to apply the corresponding intra-slot PUCCH repetition can be determined by the CORESET or search space through which the DCI format including arbitrary PDSCH resource allocation information is transmitted.

Alternatively, if the RNTI applied to CRC scrambling in DCI format containing resource allocation information for PDSCH is MCS-C-RNTI, intra-slot PUCCH repetition is applied, otherwise, intra-slot PUCCH repetition is not applied. You can. Alternatively, by allocating a separate new RNTI for intra-slot PUCCH repetition application, PDSCH transmission resource allocation requiring intra-slot PUCCH repetition application can be configured to transmit by performing CRC scrambling based on the new RNTI.

The receiving unit 1330 can repeatedly receive uplink control information within one slot using the uplink control channel resources of the subslot-based uplink control channel resource set.

According to one example, when the transmitter 1320 indicates PUCCH resource allocation information through a PUCCH resource indicator in DCI format, the terminal interprets the PUCCH resource allocation information based on whether intra-slot PUCCH repetition is applied. can do. That is, when instructed/set not to apply intra-slot PUCCH repetition, the transmitter 1320 may indicate PUCCH resource allocation information based on the type-1 PUCCH resource set. Accordingly, the receiving unit 1330 can receive uplink control information transmitted by the terminal using PUCCH resources.

In contrast, when instructed/set to apply intra-slot PUCCH repetition, the transmitter 1320 may indicate PUCCH resource allocation information based on a new type-2 PUCCH resource set. Accordingly, the receiver 1330 can repeatedly receive uplink control information that the terminal repeatedly transmits for each subslot within one slot using PUCCH resources.

According to this, it is possible to provide a specific method and device that can improve reliability of the uplink control channel according to repeated transmission of uplink control information.

The above-described embodiments may be supported by standard documents disclosed in at least one of the wireless access systems IEEE 802, 3GPP, and 3GPP2. That is, steps, configurations, and parts that are not described in the present embodiments to clearly reveal the technical idea may be supported by the above-mentioned standard documents. Additionally, all terms disclosed in this specification can be explained by the standard documents disclosed above.

The above-described embodiments can be implemented through various means. For example, the present embodiments may be implemented by hardware, firmware, software, or a combination thereof.

In the case of hardware implementation, the method according to the present embodiments uses one or more ASICs (Application Specific Integrated Circuits), DSPs (Digital Signal Processors), DSPDs (Digital Signal Processing Devices), PLDs (Programmable Logic Devices), and FPGAs. (Field Programmable Gate Arrays), processors, controllers, microcontrollers, or microprocessors.

In the case of implementation by firmware or software, the method according to the present embodiments may be implemented in the form of a device, procedure, or function that performs the functions or operations described above. Software code can be stored in a memory unit and run by a processor. The memory unit is located inside or outside the processor and can exchange data with the processor through various known means.

Additionally, terms such as "system", "processor", "controller", "component", "module", "interface", "model", or "unit" described above generally refer to computer-related entities hardware, hardware and software. It may refer to a combination of, software, or running software. By way of example, but not limited to, the foregoing components may be a process, processor, controller, control processor, object, thread of execution, program, and/or computer run by a processor. For example, both an application running on a controller or processor and the controller or processor can be a component. One or more components may reside within a process and/or thread of execution, and the components may be located on a single device (e.g., system, computing device, etc.) or distributed across two or more devices.

The above description is merely an illustrative explanation of the technical idea of the present disclosure, and those skilled in the art will be able to make various modifications and variations without departing from the essential characteristics of the present disclosure. In addition, the present embodiments are not intended to limit the technical idea of the present disclosure, but rather to explain it, so the scope of the present technical idea is not limited by these embodiments. The scope of protection of this disclosure should be interpreted in accordance with the claims below, and all technical ideas within the equivalent scope should be interpreted as being included in the scope of rights of this disclosure.

Claims (24)

In a method for a terminal to transmit uplink control information,
Receiving configuration information of two uplink control channel (PUCCH) resource sets from a base station;
Among the two uplink control channel resource sets, determining an uplink control channel resource set used for HARQ-ACK feedback for reception of a downlink data channel; and
Transmitting HARQ-ACK feedback information using a determined uplink control channel resource set among the two uplink control channels,
The configuration information of the two uplink control channel resource sets is,
Configured according to the group ID of the downlink data channel received from the base station through downlink control information (DCI) scrambled with MCS-C-RNTI,
One of the configuration information of the two uplink control channel resource sets is configured on a subslot basis,
Configuration information configured on a subslot basis includes setting information for repeated transmission of subslot-based uplink control information,
A method in which the subslot is configured based on the number of UE specific subslots or subslot length information. According to claim 1,
Two different HARQ-ACK codebooks are configured for the terminal, and the HARQ-ACK codebook to be applied to the uplink control channel resource set used for HARQ-ACK feedback for reception of the downlink data channel is HARQ-ACK feedback. A method for identifying downlink control information by a transmitted core set. delete delete delete delete In a method for a base station to receive uplink control information,
Transmitting configuration information of two uplink control channel (PUCCH) resource sets to the terminal; and
Receiving HARQ-ACK feedback information using an uplink control channel resource set determined by the terminal among the two uplink control channel resource sets,
The configuration information of the two uplink control channel resource sets is,
It is configured according to the group ID of the downlink data channel transmitted to the terminal through downlink control information (DCI) scrambled with MCS-C-RNTI,
One of the configuration information of the two uplink control channel resource sets is configured on a subslot basis,
Configuration information configured on a subslot basis includes setting information for repeated transmission of subslot-based uplink control information,
A method in which the subslot is configured based on the number of UE specific subslots or subslot length information. According to claim 7,
Further comprising transmitting HARQ-ACK codebook information for configuring two different HARQ-ACK codebooks for the terminal,
The HARQ-ACK codebook to be applied to the uplink control channel resource set used for HARQ-ACK feedback for reception of the downlink data channel is identified by the core set (CORESET) to which downlink control information regarding HARQ-ACK feedback is transmitted. How to become. delete delete delete delete In a terminal transmitting uplink control information,
A receiving unit that receives configuration information of two uplink control channel (PUCCH) resource sets from a base station;
A control unit that determines an uplink control channel resource set used for HARQ-ACK feedback for reception of a downlink data channel among the two uplink control channel resource sets; and
A transmitter that transmits HARQ-ACK feedback information using a determined uplink control channel resource set among the two uplink control channels,
The configuration information of the two uplink control channel resource sets is,
Configured according to the group ID of the downlink data channel received from the base station through downlink control information (DCI) scrambled with MCS-C-RNTI,
One of the configuration information of the two uplink control channel resource sets is configured on a subslot basis,
Configuration information configured on a subslot basis includes setting information for repeated transmission of subslot-based uplink control information,
The subslot is configured based on the number of UE specific subslots or subslot length information. According to claim 13,
Two different HARQ-ACK codebooks are configured for the terminal, and the HARQ-ACK codebook to be applied to the uplink control channel resource set used for HARQ-ACK feedback for reception of the downlink data channel is HARQ-ACK feedback. A terminal identified by a core set (CORESET) to which downlink control information is transmitted. delete delete delete delete In the base station receiving uplink control information,
A transmitter that transmits configuration information of two uplink control channel (PUCCH) resource sets to the terminal; and
A receiving unit that receives HARQ-ACK feedback information using an uplink control channel resource set determined by the terminal among the two uplink control channel resource sets,
The configuration information of the two uplink control channel resource sets is,
It is configured according to the group ID of the downlink data channel transmitted to the terminal through downlink control information (DCI) scrambled with MCS-C-RNTI,
One of the configuration information of the two uplink control channel resource sets is configured on a subslot basis,
Configuration information configured on a subslot basis includes setting information for repeated transmission of subslot-based uplink control information,
The subslot is a base station configured based on the number of UE specific subslots or subslot length information. According to claim 19,
The transmitter transmits HARQ-ACK codebook information for configuring two different HARQ-ACK codebooks for the terminal,
The HARQ-ACK codebook to be applied to the uplink control channel resource set used for HARQ-ACK feedback for reception of the downlink data channel is identified by the core set (CORESET) to which downlink control information regarding HARQ-ACK feedback is transmitted. base station. delete delete delete delete

Images