Signal transmission and reception method for wireless communication and apparatus therefor

Abstract

According to various embodiments, an apparatus in a wireless communication system: receives a physical downlink control channel (PDCCH) including downlink control information (DCI) from a base station through a control link; and transmitting a hybrid automatic repeat request (HARQ) feedback signal for the PDCCH through the backhaul link, in which a transmission resource of the HARQ feedback signal is determined based on K0 for a slot interval between the PDCCH and a physical downlink shared channel (PDSCH) and K1 for an interval between the PDSCH and the HARQ feedback signal, and side control information (SCI) for the backhaul link is included based on the DCI, at least one of K0 and K1 may be determined based on a predefined rule.

Description

Technical Field

[0001] The present disclosure relates to wireless communication, and more particularly, to a method and an apparatus for transmitting or receiving uplink / downlink signals in a wireless communication system. Background Art

[0002] Wireless communication systems are being widely deployed to provide various types of communication services such as voice and data. Generally, a wireless communication system is a multi-access system capable of supporting communication with multiple users by sharing available system resources (e.g., bandwidth, transmission power, etc.). Examples of multi-access systems include code division multiple access (CDMA) systems, frequency division multiple access (FDMA) systems, time division multiple access (TDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single carrier frequency division multiple access (SC-FDMA) systems, and multi-carrier frequency division multiple access (MC-FDMA) systems.

[0003] As more and more communication devices require greater communication capacity when transmitting and receiving signals, there is a need for improved mobile broadband communication relative to traditional radio access technologies. Therefore, communication systems considering services / UEs sensitive to reliability and latency are being discussed. Next-generation radio access technologies considering enhanced mobile broadband communication, massive machine type communication (MTC), and ultra-reliable and low-latency communication (URLLC) may be referred to as new radio access technologies (RATs) or new radio (NR). Summary of the Invention

[0004] Technical Problem

[0005] An object of the present disclosure is to provide a method for transmitting and receiving signals more accurately and more efficiently.

[0006] Those skilled in the art will understand that the objects that can be achieved by various embodiments of the present disclosure are not limited to those specifically described above, and the above and other objects that can be achieved by various embodiments of the present disclosure will be more clearly understood from the following detailed description.

[0007] Technical Solution

[0008] In one aspect of the present disclosure, there is provided a method of performing communication by a device having a control link and a backhaul link formed with a base station (BS) in a wireless communication system. The method includes: receiving, via the control link, a physical downlink control channel (PDCCH) including downlink control information (DCI) from the BS; and transmitting a hybrid automatic repeat request (HARQ) feedback signal for the PDCCH. Transmission resources for the HARQ feedback signal may be determined based on K0 and K1, where K0 represents a slot interval between the PDCCH and a physical downlink shared channel (PDSCH), and K1 represents an interval between the PDSCH and the HARQ feedback signal. Based on the fact that the DCI includes side control information (SCI) for the backhaul link, at least one of K0 and K1 may be determined based on a predefined rule.

[0009] Alternatively, based on a predefined rule, K0 may be determined as a value corresponding to the lowest or highest index in a time domain resource allocation (TDRA) table configured by radio resource control (RRC) signaling.

[0010] Alternatively, based on a predefined rule, K0 may always be determined as 0.

[0011] Alternatively, based on a predefined rule, K1 may be determined as the maximum or minimum value among K1 values configured by RRC signaling from the BS.

[0012] Alternatively, the method may further include reporting to the BS capability information of a minimum processing time related to transmission of the HARQ feedback signal. The device may determine K1 using the minimum processing time based on a predefined rule, regardless of the indication of K1 in the DCI.

[0013] Alternatively, the device may determine HARQ feedback transmission resources by also considering a physical uplink control channel (PUCCH) resource indicator (PRI). Based on the fact that the DCI does not include a field for the PRI, the PRI may always be determined as 1, regardless of the control channel element (CCE) index of the received PDCCH.

[0014] Alternatively, the DCI may not include fields for K0 and a start and length indicator value (SLIV), a field for K1, and a field for the PRI.

[0015] Alternatively, the HARQ feedback signal may include HARQ feedback information obtained by codebook combination only for the PDCCH including the SCI.

[0016] Alternatively, the device may be a network control repeater (NCR).

[0017] In another aspect of the present disclosure, there is provided an apparatus configured to perform communication in a wireless communication system based on a control link and a backhaul link formed with a BS. The apparatus may include: a radio frequency (RF) transceiver; and a processor configured to control the RF transceiver. The processor is configured to control the RF transceiver to: receive a PDCCH including DCI from the BS via the control link; and transmit a HARQ feedback signal for the PDCCH. The transmission resource for the HARQ feedback signal may be determined based on K0 and K1, where K0 represents the slot interval between the PDCCH and the PDSCH, and K1 represents the interval between the PDSCH and the HARQ feedback signal. Based on the SCI for the backhaul link included in the DCI, at least one of K0 and K1 may be determined based on a predefined rule.

[0018] In another aspect of the present disclosure, there is provided a processing apparatus configured to control an apparatus having a control link and a backhaul link formed with a BS to perform operations in a wireless communication system. The processing apparatus includes: at least one processor; and at least one memory connected to the at least one processor and storing instructions, which, when executed by the at least one processor, cause a user equipment (UE) to: receive a PDCCH including DCI from the BS via the control link; and transmit a HARQ feedback signal for the PDCCH. The transmission resource for the HARQ feedback signal may be determined based on K0 and K1, where K0 represents the slot interval between the PDCCH and the PDSCH, and K1 represents the interval between the PDSCH and the HARQ feedback signal. Based on the SCI for the backhaul link included in the DCI, at least one of K0 and K1 may be determined based on a predefined rule.

[0019] In yet another aspect of the present disclosure, there is provided a method for a BS having a control link and a backhaul link formed with an apparatus to perform communication in a wireless communication system. The method includes: transmitting a PDCCH including DCI to the apparatus via the control link; and receiving a HARQ feedback signal for the PDCCH. The reception resource for the HARQ feedback signal may be determined based on K0 and K1, where K0 represents the slot interval between the PDCCH and the PDSCH, and K1 represents the interval between the PDSCH and the HARQ feedback signal. Based on the SCI for the backhaul link included in the DCI, at least one of K0 and K1 may be determined based on a predefined rule.

[0020] Beneficial effects

[0021] According to an embodiment of the present disclosure, signal transmission and reception can be performed more accurately and efficiently in a wireless communication system.

[0022] The effects to be achieved by the embodiments are not limited to those specifically described above, and those skilled in the art in the field of the embodiments will more clearly understand other effects not mentioned herein according to the following detailed description. BRIEF DESCRIPTION OF THE DRAWINGS

[0023] The accompanying drawings, which are incorporated in and constitute a part of this application, are included to provide a further understanding of the present disclosure, and illustrate embodiments of the present disclosure and, together with the description, serve to explain the principles of the present disclosure.

[0024] Figure 1 Illustrates the structure of an LTE system to which applicable embodiments are applied.

[0025] Figure 2 Illustrates the structure of an NR system to which applicable embodiments are applied.

[0026] Figure 3 Illustrates the structure of an NR radio frame to which applicable embodiments are applied.

[0027] Figure 4 Illustrates the time slot structure of an NR frame to which applicable embodiments are applied.

[0028] Figure 5 Illustrates an example of mapping physical channels in a time slot.

[0029] Figure 6 Illustrates an exemplary PDCCH transmission / reception process.

[0030] Figure 7 Illustrates a process for transmitting hybrid automatic repeat request (HARQ) acknowledgement / negative acknowledgement (ACK / NACK).

[0031] Figure 8 Schematically illustrates an example of a parent link and a child link in IAB.

[0032] Figure 9 Is a diagram illustrating an example of a topology in which a network control repeater (NCR) performs transmission and reception between a gNB and a UE.

[0033] Figure 10 Is a diagram illustrating a radio frequency (RF) repeater and an NCR.

[0034] Figure 11 Is a diagram for explaining a method of a device having a backhaul link and a control link formed with a base station (BS) to perform communication.

[0035] Figure 12 Is a diagram for explaining a method of a BS having a control link and a backhaul link formed with a device to perform communication.

[0036] Figure 13An example of a communication system to which the present disclosure is applied is illustrated.

[0037] Figure 14 An example of a wireless device applicable to the present disclosure is illustrated.

[0038] Figure 15 Another example of a wireless device to which the present disclosure is applied is illustrated. Detailed implementation manners

[0039] A wireless communication system is a multiple access system that supports communication with multiple users by sharing available system resources (e.g., bandwidth, transmission power, etc.). Examples of multiple access systems include code division multiple access (CDMA) systems, frequency division multiple access (FDMA) systems, time division multiple access (TDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single carrier frequency division multiple access (SC-FDMA) systems, multi-carrier frequency division multiple access (MC-FDMA) systems, etc.

[0040] A sidelink refers to a communication scheme in which a direct link is established between user equipment (UEs) without the assistance of a base station (BS) to directly exchange voice or data between the UEs. The sidelink is regarded as a way to solve the burden on the BS caused by the rapidly increasing data traffic.

[0041] Vehicle-to-everything (V2X) refers to a communication technology for exchanging information with other vehicles, pedestrians, and infrastructure objects through wired / wireless communication. V2X can be divided into four types: vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), vehicle-to-network (V2N), and vehicle-to-pedestrian (V2P). V2X communication can be provided through the PC5 interface and / or the Uu interface.

[0042] As more and more communication devices require greater communication capacity when sending and receiving signals, improved mobile broadband communication relative to traditional radio access technologies is needed. Therefore, communication systems considering services / UEs sensitive to reliability and latency are being discussed. Next-generation radio access technologies considering enhanced mobile broadband communication, massive MTC, and ultra-reliable and low-latency communication (URLLC) can be referred to as new radio access technologies (RATs) or new radio (NR). Even in NR, V2X communication can be supported.

[0043] The technologies described herein can be used in various wireless access systems such as Code Division Multiple Access (CDMA), Frequency Division Multiple Access (FDMA), Time Division Multiple Access (TDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-Carrier Frequency Division Multiple Access (SC-FDMA), etc. CDMA can be implemented as radio technologies such as Universal Terrestrial Radio Access (UTRA) or CDMA2000. TDMA can be implemented as radio 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 as radio technologies such as IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Evolved UTRA (E-UTRA), etc. UTRA is part of the Universal Mobile Telecommunications System (UMTS). The 3rd Generation Partnership Project (3GPP) Long-Term Evolution (LTE) is part of the Evolved UMTS (E-UMTS) that uses Evolved UTRA (E-UTRA). 3GPP LTE adopts OFDMA for the downlink and SC-FDMA for the uplink. LTE-A is the evolution of 3GPP LTE. 3GPP New Radio (NR) (New Radio or New Radio Access Technology) is an evolved version of 3GPP LTE / LTE-A / LTE-A pro.

[0044] 5G NR is a successor technology to LTE-A and is a new clean-state mobile communication system characterized by high performance, low latency, and high availability. 5G NR can use all available spectrum resources, including low-frequency bands below 1 GHz, intermediate-frequency bands between 1 GHz and 10 GHz, and high-frequency (millimeter) bands of 24 GHz or above.

[0045] For the sake of clarity, LTE-A or 5G NR is mainly described, but the technical spirit of the embodiments is not limited thereto.

[0046] Figure 1 The structure of an LTE system to which the present disclosure is applicable is illustrated. This can also be referred to as the Evolved UMTS Terrestrial Radio Access Network (E-UTRAN) or the LTE / LTE-A system.

[0047] Referring to Figure 1 , the E-UTRAN includes an evolved Node B (eNB) 20 that provides a control plane and a user plane to the UE 10. The UE 10 can be fixed or mobile and can also be referred to as a Mobile Station (MS), User UE (UT), Subscriber Station (SS), Mobile UE (MT), or wireless device. The eNB 20 is a fixed station that communicates with the UE 10 and can also be referred to as a Base Station (BS), Base Transceiver System (BTS), or Access Point.

[0048] The eNBs 20 can be connected to each other via the X2 interface. The eNBs 20 are connected to the evolved packet core (EPC) 39 via the S1 interface. More specifically, the eNBs 20 are connected to the mobility management entity (MME) via the S1-MME interface and to the serving gateway (S-GW) via the S1-U interface.

[0049] The EPC 30 includes the MME, the S-GW, and the packet data network gateway (P-GW). The MME has access information or capability information about the UE, which is mainly used for the mobility management of the UE. The S-GW is a gateway with the E-UTRAN as an endpoint, and the P-GW is a gateway with the packet data network (PDN) as an endpoint.

[0050] Based on the lowest three layers of the well-known open systems interconnection (OSI) reference model in the communication system, the radio protocol stack between the UE and the network can be divided into layer 1 (L1), layer 2 (L2), and layer 3 (L3). These layers are defined in pairs between the UE and the evolved UTRAN (E-UTRAN) for data transmission via the Uu interface. The physical (PHY) layer at L1 provides an information transfer service on the physical channel. The radio resource control (RRC) layer at L3 is used to control the radio resources between the UE and the network. For this purpose, the RRC layer exchanges RRC messages between the UE and the eNB.

[0051] Figure 2 Illustrated is the structure of the NR system to which the present disclosure is applicable.

[0052] Refer to Figure 2 , the next-generation radio access network (NG-RAN) may include next-generation Node Bs (gNBs) and / or eNBs that provide user plane and control plane protocol termination to the UE. In Figure 7 , for example, the NG-RAN is shown as including only gNBs. The gNBs and eNBs are connected to each other via the Xn interface. The gNBs and eNBs are connected to the 5G core network (5GC) via the NG interface. More specifically, the gNBs and eNBs are connected to the access and mobility management function (AMF) via the NG-C interface and to the user plane function (UPF) via the NG-U interface.

[0053] Figure 3 Illustrated is the structure of the NR radio frame to which the present disclosure is applicable.

[0054] Refer to Figure 3, A radio frame can be used for UL transmission and DL transmission in NR. The length of the radio frame is 10 ms and can be defined by two 5 - ms half - frames. A half - frame (HF) can include five 1 - ms sub - frames. A sub - frame can be divided into one or more time slots, and the number of time slots in the sub - frame (SF) can be determined according to the sub - carrier spacing (SCS). Each time slot can include 12 or 14 OFDM(A) symbols according to the cyclic prefix (CP).

[0055] In the case of normal CP (NCP), each time slot can include 14 symbols, while in the case of extended CP (ECP), each time slot can include 12 symbols. In this document, a symbol can be an OFDM symbol (or CP - OFDM symbol) or an SC - FDMA symbol (or DFT - s - OFDM symbol).

[0056] Table 1 below lists the number of symbols N per time slot, the number of time slots N per frame slot symb and the number of time slots N per sub - frame frame,u slot in the case of NCP according to the SCS configuration μ. subframe,u slot .

[0057] [Table 1]

[0058] <![CDATA[SCS(15*2 u )]]> <![CDATA[N slot symb > <![CDATA[N frame,u slot > <![CDATA[N subframe,u slot > 15 KHz (u = 0) 14 10 1 30 KHz (u = 1) 14 20 2 60 KHz (u = 2) 14 40 4 120 KHz (u = 3) 14 80 8 240 KHz (u = 4) 14 160 16

[0059] Table 2 below lists the number of symbols per time slot, the number of time slots per frame, and the number of time slots per sub - frame according to the SCS in the case of ECP.

[0060] [Table 2]

[0061] <![CDATA[SCS(15*2 u )]]> <![CDATA[N slot symb > <![CDATA[N frame,u slot > <![CDATA[N subframe,u slot > 60 KHz (u = 2) 12 40 4

[0062] In the NR system, different OFDM(A) parameter sets (e.g., SCS, CP length, etc.) can be configured for multiple cells aggregated for one UE. Therefore, the (absolute - time) duration of a time resource (e.g., sub - frame, time slot, or TTI) that includes the same number of symbols (collectively referred to as time unit (TU) for convenience) can be configured to be different for the aggregated cells.

[0063] In NR, various parameter sets or SCSs can be supported to support various 5G services. For example, with an SCS of 15 kHz, a wide area in the traditional cellular band can be supported, while with an SCS of 30 kHz / 60 kHz, dense urban areas, lower latency, and wide carrier bandwidth can be supported. When the SCS is 60 kHz or higher, a bandwidth wider than 24.25 GHz can be supported to overcome phase noise.

[0064] The NR frequency band can be defined by two types of frequency ranges, FR1 and FR2. The two types of frequency ranges can be FR1 and FR2. The numerical values of the frequency ranges can be changed. For example, the two types of frequency ranges can be configured as shown in Table 3 below. Among the frequency ranges used in the NR system, FR1 can represent "the range below 6 GHz", and FR2 can represent "the range above 6 GHz", and can be referred to as millimeter wave (mmW).

[0065] [Table 3]

[0066] Frequency range designation Corresponding frequency range Subcarrier spacing (SCS) FR1 450 MHz - 6000 MHz 15 kHz, 30 kHz, 60 kHz FR2 24250 MHz - 52600 MHz 60 kHz, 120 kHz, 240 kHz

[0067] As mentioned above, the numerical values of the frequency ranges of the NR system can be changed. For example, FR1 can include the frequency band from 410 MHz to 7125 MHz as shown in Table 4 below. That is, FR1 can include the frequency band of 6 GHz (or 5850 MHz, 5900 MHz, 5925 MHz, etc.) or higher. For example, the frequency band of 6 GHz (or 5850 MHz, 5900 MHz, 5925 MHz, etc.) or higher included in FR1 can include an unlicensed frequency band. The unlicensed frequency band can be used for various purposes, for example, for vehicle communication (such as autonomous driving).

[0068] [Table 4]

[0069] Frequency range designation Corresponding frequency range Subcarrier spacing (SCS) FR1 410 MHz - 7125 MHz 15 kHz, 30 kHz, 60 kHz FR2 24250 MHz - 52600 MHz 60 kHz, 120 kHz, 240 kHz

[0070] Figure 4 Illustrated is the time slot structure of the NR frame to which the present disclosure is applicable.

[0071] Refer to Figure 4 , one time slot includes a plurality of symbols in the time domain. For example, one time slot can include 14 symbols in the case of normal CP, and can include 12 symbols in the case of extended CP. Alternatively, one time slot includes 7 symbols in the case of normal CP, and can include 6 symbols in the case of extended CP.

[0072] A carrier can include a plurality of subcarriers in the frequency domain. A resource block (RB) is defined as a plurality of consecutive subcarriers in the frequency domain (for example, 12 subcarriers). A bandwidth part (BWP) can be defined as a plurality of consecutive (P) RBs in the frequency domain, and the BWP can correspond to a parameter set (such as SCS, CP length, etc.). A carrier can include up to N (for example, 5) BWPs. Data communication can be performed in the activated BWP. In the resource grid, each element can be called a resource element (RE), and can be mapped to a complex symbol.

[0073] The radio interface between UEs or between a UE and the network may include L1 layer, L2 layer, and L3 layer. In various embodiments of the present disclosure, the L1 layer may represent the physical layer. The L2 layer may represent, for example, at least one of the MAC layer, RLC layer, PDCH layer, or SDAP layer. The L3 layer may represent, for example, the RRC layer.

[0074] Bandwidth part (BWP)

[0075] In the NR system, each component carrier (CC) may support up to 400 MHz. If the UE operating on a wideband CC always utilizes RF operation for all enabled CCs, the battery power consumption of the UE may increase. Alternatively, considering various use cases (e.g., eMBB, URLLC, Mmtc, V2X, etc.) operating within a wideband CC, different parameter sets (e.g., subcarrier spacing) may be supported for different frequency bands within a specific CC. Alternatively, the capabilities for the maximum bandwidth may be different among UEs. Considering this, the BS may indicate to the UE to operate only in a partial bandwidth instead of the entire bandwidth of the wideband CC. For simplicity, the partial bandwidth is defined as the bandwidth part (BWP). Here, the BWP may be composed of resource blocks (RBs) that are continuous on the frequency axis and may correspond to a parameter set (e.g., subcarrier spacing, CP length, slot / sub-slot duration).

[0076] The BS may configure multiple BWPs in one CC configured for the UE. For example, a BWP occupying a relatively small frequency domain may be configured in the PDCCH monitoring slot, and the PDSCH indicated by the PDCCH in a larger BWP may be scheduled. Alternatively, when the UE is concentrated in a specific BWP, some of the UEs may be configured in another BWP to achieve load balancing. Alternatively, considering the frequency-domain inter-cell interference cancellation between neighboring cells, the spectrum in the middle of the entire bandwidth may be punctured and two BWPs on both sides may be configured in the same slot. That is, the BS may configure at least one DL / UL BWP for the UE associated with the wideband CC (e.g., via L1 signaling, MAC CE, or RRC signaling, etc.) and activate at least one of the configured DL / UL BWPs at a specific time. The BS may (e.g., via L1 signaling, MAC CE, or RRC signaling, etc.) instruct the UE to switch to another configured DL / UL BWP. Alternatively, when the timer expires, the UE may switch to a predetermined DL / UL BWP. The activated DL / UL BWP is defined as the active DL / UL BWP. During the initial access procedure or before establishing the RRC connection, the UE may not be able to receive the DL / UL BWP configuration. The DL / UL BWP assumed by the UE in this case is defined as the initially active DL / UL BWP.

[0077] Figure 5 Illustrates an example of mapping physical channels in a time slot.

[0078] The time slot may include a DL control channel, DL or UL data, a UL control channel, etc., all of which are included. For example, the first N symbols in the time slot can be used to transmit the DL control channel (hereinafter referred to as the DL control region), and the last M symbols in the time slot can be used to transmit the UL control channel (hereinafter referred to as the UL control region). N and M are each integers greater than or equal to 0. The resource region (hereinafter referred to as the data region) between the DL control region and the UL control region can be used for DL data transmission or UL data transmission. A time gap for DL to UL or UL to DL switching may exist between the control region and the data region. The PDCCH can be transmitted in the DL control region, and the PDSCH can be transmitted in the DL data region. Some symbols at the time of switching from DL to UL in the time slot can be used as the time gap.

[0079] In the NR system, a frame is characterized by a self - contained structure in which a DL control channel, DL or UL data, and a UL channel can all be included in one time slot. For example, the first N symbols of the time slot can be used to carry the DL channel (e.g., PDCCH) (hereinafter referred to as the DL control region), and the last M symbols of the time slot can be used to carry the UL channel (e.g., PUCCH) (hereinafter referred to as the UL control region). Each of N and M is an integer equal to or greater than 0. The resource region (hereinafter referred to as the data region) between the DL control region and the UL control region can be used to transmit DL data (e.g., PDSCH) or UL data (e.g., PUSCH). The guard period (GP) provides a time gap for switching from the transmission mode to the reception mode or from the reception mode to the transmission mode. Some symbols at the time of DL to UL switching in the sub - frame can be configured as the GP.

[0080] The PDCCH transmits DCI. For example, the PDCCH (i.e., DCI) may carry information on the transmission format and resource allocation of the DL shared channel (DL-SCH), resource allocation information for the uplink shared channel (UL-SCH), paging information regarding the paging channel (PCH), system information regarding the DL-SCH, information on the resource allocation of high-layer control messages (e.g., RAR sent on the PDSCH), transmit power control commands, information on the enabling / release of configured scheduling, etc. The DCI includes a cyclic redundancy check (CRC). The CRC is masked using various identifiers (IDs) (e.g., radio network temporary identifier (RNTI)) according to the owner or use of the PDCCH. For example, if the PDCCH is for a specific UE, the CRC is masked by the UE ID (e.g., cell-RNTI (C-RNTI)). If the PDCCH is for a paging message, the CRC is masked by the paging-RNTI (P-RNTI). If the PDCCH is for system information (e.g., system information block (SIB)), the CRC is masked by the system information RNTI (SI-RNTI). When the PDCCH is for the RAR, the CRC is masked by the random access-RNTI (RA-RNTI).

[0081] Figure 6 An exemplary PDCCH transmission / reception process is illustrated.

[0082] Refer to Figure 6, the BS may send a Control Resource Set (CORESET) configuration to the UE (S502). A CORESET is defined as a set of Resource Element Groups (REGs) with a given parameter set (e.g., subcarrier spacing (SCS), cyclic prefix (CP) length, etc.). A REG is defined as one OFDM symbol by one (physical) resource block (P)RB. Multiple CORESETs for one UE may overlap with each other in the time domain / frequency domain. A CORESET may be configured by system information (e.g., Master Information Block (MIB)) or higher layer signaling (e.g., Radio Resource Control (RRC) signaling). For example, configuration information about a specific common CORESET (e.g., CORESET#0) may be sent in the MIB. For example, the PDSCH carrying System Information Block 1 (SIB1) may be scheduled by a specific PDCCH, and CORESET#0 may be used to send the specific PDCCH. The system information (SIB1) broadcast in the cell includes cell-specific PDSCH configuration information, PDSCH-ConfigCommon. PDSCH-ConfigCommon includes a list (or look-up table) of parameters related to time domain resource allocation, pdsch-TimeDomainAllocationList. Each pdsch-TimeDomainAllocationList may include up to 16 entries (or rows), and each entry is jointly encoded {K0, PDSCH mapping type, PDSCH start symbol and length (SLIV)}. In addition to the pdsch-TimeDomainAllocationList configured through PDSCH-ConfigCommon, a pdsch-TimeDomainAllocationList, PDSCH-Config, may also be provided through UE-specific PDSCH configuration. The structure of the pdsch-TimeDomainAllocationList configured for the UE is the same as that of the pdsch-TimeDomainAllocationList provided publicly for the UE. For K0 and SLIV of the pdsch-TimeDomainAllocationList, refer to the following description.

[0083] In addition, configuration information about CORESET#N (e.g., N>0) may be sent through RRC signaling (e.g., cell-common RRC signaling, UE-specific RRC signaling, etc.). For example, UE-specific RRC signaling carrying CORESET configuration information may include (but is not limited to) various types of signaling, such as RRC establishment messages, RRC reconfiguration messages, and / or BWP configuration information. Specifically, the CORESET configuration may include the following information / fields.

[0084] - controlResourceSetId: Indicates the ID of the CORESET.

[0085] - frequencyDomainResources: Indicates the frequency-domain resources of the CORESET. The resources are indicated by a bitmap where each bit corresponds to an RB group (= 6 (consecutive) RBs). For example, the most significant bit (MSB) of the bitmap corresponds to the first RB group in the BWP. The RB groups corresponding to the bits with a value of 1 are allocated as the frequency-domain resources of the CORESET.

[0086] - duration: Indicates the time-domain resources of the CORESET. It indicates the number of consecutive OFDM symbols included in the CORESET. duration has a value between 1 and 3.

[0087] - cce-REG-MappingType: Indicates the control channel element (CCE) to REG mapping type. Interleaved and non-interleaved types are supported.

[0088] - interleaverSize: Indicates the interleaver size.

[0089] - pdcch-DMRS-ScramblingID: Indicates the value used for PDCCH DMRS initialization. When pdcch-DMRS-ScramblingID is not included, the physical cell ID of the serving cell is used.

[0090] - precoderGranularity: Indicates the precoder granularity in the frequency domain.

[0091] - reg-BundleSize: Indicates the REG bundle size.

[0092] - tci-PresentInDCI: Indicates whether the transmission configuration index (TCI) field is included in the DL-related DCI.

[0093] - tci-StatesPDCCH-ToAddList: Indicates a subset of the TCI states configured in pdcch-Config that provides the quasi-co-location (QCL) relationship between the DL RS in the RS set (TCI state) and the PDCCH DMRS ports.

[0094] In addition, the BS may send a PDCCH search space (SS) configuration (S504) to the UE. The PDCCH SS configuration may be sent via higher layer signaling (e.g., RRC signaling). For example, the RRC signaling may include (but is not limited to) various types of signaling such as RRC establishment messages, RRC reconfiguration messages, and / or BWP configuration information. Although for ease of description, in Figure 5 the CORESET configuration and the PDCCH SS configuration are shown as being signaled separately, the present disclosure is not limited thereto. For example, the CORESET configuration and the PDCCH SS configuration may be sent in one message (e.g., via one RRC signaling) or separately in different messages.

[0095] The PDCCH SS configuration may include information about the configuration of a PDCCH SS set. A PDCCH SS set may be defined as a set of PDCCH candidates to be monitored (e.g., blindly detected) by the UE. One or more SS sets may be configured for the UE. Each SS set may be a UE-specific search space (USS) set or a common search space (CSS) set. For ease of description, the PDCCH SS set may be referred to as "SS" or "PDCCH SS".

[0096] The PDCCH SS set includes PDCCH candidates. A PDCCH candidate is a CCE that the UE monitors to receive / detect a PDCCH. Monitoring includes blind decoding (BD) of the PDCCH candidates. One PDCCH (candidate) includes 1, 2, 4, 8, or 16 CCEs according to the aggregation level (AL). One CCE includes 6 REGs. Each CORESET configuration is associated with one or more SSs, and each SS is associated with one CORESET configuration. One SS is defined based on the SS configuration, and the SS configuration may include the following information / fields.

[0097] - searchSpaceId: Indicates the ID of the SS.

[0098] - controlResourceSetId: Indicates the CORESET associated with the SS.

[0099] - monitoringSlotPeriodicityAndOffset: Indicates the periodicity (in time slots) and offset (in time slots) of PDCCH monitoring.

[0100] -monitoringSymbolsWithinSlot: Indicates the first OFDM symbol for PDCCH monitoring in a slot configured for PDCCH monitoring. The first OFDM symbol for PDCCH monitoring is indicated by a bitmap where each bit corresponds to an OFDM symbol in the slot. The MSB of the bitmap corresponds to the first OFDM symbol of the slot. The OFDM symbol corresponding to a bit set to 1 corresponds to the first symbol of the CORESET in the slot.

[0101] -nrofCandidates: Indicates the number of PDCCH candidates per AL (one of the values 0, 1, 2, 3, 4, 5, 6, and 8), where AL = {1, 2, 4, 8, 16}.

[0102] -searchSpaceType: Indicates CSS or USS and the DCI format used in the corresponding SS type.

[0103] Subsequently, the BS may generate a PDCCH and send the PDCCH to the UE (S506), and the UE may monitor PDCCH candidates in one or more SSs to receive / detect the PDCCH (S508). The occasion (e.g., time / frequency resource) for the UE to monitor PDCCH candidates is defined as the PDCCH (monitoring) occasion. One or more PDCCH (monitoring) occasions may be configured in a slot.

[0104] Table 5 shows the characteristics of each SS.

[0105] [Table 5]

[0106]

[0107] Table 6 shows the DCI formats sent on the PDCCH.

[0108] [Table 6]

[0109]

[0110] DCI format 0_0 can be used to schedule TB (or TB-level) based PUSCH, and DCI format 0_1 can be used to schedule TB (or TB-level) based PUSCH or codeblock group (CBG) (or CBG-level) based PUSCH. DCI format 1_0 can be used to schedule TB (or TB-level) based PDSCH, and DCI format 1_1 can be used to schedule TB (or TB-level) based PDSCH or CBG (or CBG-level) based PDSCH (or DL grant DCI). DCI formats 0_0 / 0_1 can be referred to as UL grant DCI or UL scheduling information, and DCI formats 1_0 / 1_1 can be referred to as DL grant DCI or DL scheduling information. DCI format 2_0 is used to transmit dynamic time slot format information (e.g., dynamic time slot format indicator (SFI)) to the UE, and DCI format 2_1 is used to transmit DL preemption information to the UE. DCI format 2_0 and / or DCI format 2_1 can be transmitted to a corresponding group of UEs on the group common PDCCH (PDCCH pointing to a group of UEs).

[0111] DCI format 0_0 and DCI format 1_0 can be referred to as fallback DCI formats, while DCI format 0_1 and DCI format 1_1 can be referred to as non-fallback DCI formats. In the fallback DCI format, regardless of the UE configuration, the DCI size / field configuration remains the same. In contrast, in the non-fallback DCI format, the DCI size / field configuration varies according to the UE configuration.

[0112] The CCE-to-REG mapping type is configured as one of the interleaved CCE-to-REG type and the non-interleaved CCE-to-REG type.

[0113] - Non-interleaved CCE-to-REG mapping (or local CCE-to-REG mapping)( Figure 5 ): The 6 REGs for a given CCE are grouped into a REG bundle, and all the REGs for a given CCE are adjacent. One REG bundle corresponds to one CCE.

[0114] - Interleaved CCE-to-REG mapping (or distributed CCE-to-REG mapping)( Figure 6 ): The 2, 3, or 6 REGs for a given CCE are grouped into a REG bundle, and the REG bundles are interleaved within the CORESET. In a CORESET including one or two OFDM symbols, the REG bundle includes 2 or 6 REGs, and in a CORESET including three OFDM symbols, the REG bundle includes 3 or 6 REGs. The REG bundle size is set based on the CORESET.

[0115] Figure 7 An exemplary ACK / NACK transmission procedure is illustrated.

[0116] Reference Figure 7 The UE can detect the PDCCH in time slot #n. The PDCCH includes DL scheduling information (e.g., DCI format 1_0 or DCI format 1_1). The PDCCH indicates the DL assignment to the PDSCH offset K0 and the PDSCH to HARQ-ACK report offset K1. For example, DCI format 1_0 or DCI format 1_1 may include the following information.

[0117] - Frequency domain resource assignment: Indicates the set of RBs assigned to the PDSCH.

[0118] - Time domain resource assignment: Indicates K0 (e.g., time slot offset), the start position of the PDSCH in time slot #n+K0 (e.g., OFDM symbol index), and the length of the PDSCH (e.g., the number of OFDM symbols)

[0119] - PDSCH to HARQ feedback timing indicator: Indicates K1

[0120] - HARQ process number (4 bits): Indicates the HARQ process identification (ID) of the data (e.g., PDSCH or TB)

[0121] - PUCCH resource indicator (PRI): Indicates the PUCCH resource to be used for UCI transmission among multiple PUCCH resources in the PUCCH resource set

[0122] Subsequently, the UE can receive the PDSCH from time slot #(n+K0) according to the scheduling information in time slot #n. When the reception of the PDSCH in time slot #n1 (where n+K0≤n1) is completed, the UE can send UCI through the PUCCH in time slot #(n1+K1). The UCI may include a HARQ-ACK response to the PDSCH. In Figure 7 For convenience, it is assumed that the SCS of the PDSCH and the SCS of the PUCCH are the same and time slot #n1 = time slot #n+K0, but the present disclosure is not limited thereto. When the SCSs are different, K1 can be indicated / interpreted based on the SCS of the PUCCH.

[0123] When the PDSCH is configured to transmit at most one TB, the HARQ-ACK response may include one bit. When the PDSCH is configured to transmit at most two TBs, in the case where spatial bundling is not configured, the HARQ-ACK response may include two bits, and in the case where spatial bundling is configured, it includes one bit. When the HARQ-ACK transmission time of multiple PDSCHs is specified as time slot #(n+K1), the UCI transmitted in time slot #(n+K1) includes the HARQ-ACK responses to the multiple PDSCHs.

[0124] It is possible to configure whether the UE should perform spatial bundling for HARQ-ACK responses for each cell group (e.g., via RRC / higher layer signaling). For example, spatial bundling can be configured separately for each HARQ-ACK response sent via PUCCH and / or for each HARQ-ACK response sent via PUSCH.

[0125] Spatial bundling can be supported when the maximum number of TBs (or codewords) that can be received at once (or scheduled by one DCI) in the corresponding serving cell is 2 (or greater) (e.g., when the higher layer parameter maxNrofCodeWordsScheduledByDCI corresponds to 2 TBs). In addition, more than four layers can be used for 2 TB transmissions, and at most four layers can be used for 1 TB transmissions. As a result, when spatial bundling is configured for a corresponding cell group, spatial bundling can be performed for serving cells in the cell group's serving cells that can be scheduled for more than four layers. On a serving cell, a UE that wants to send a HARQ-ACK response via spatial bundling can generate the HARQ-ACK response by performing a bitwise logical AND operation on the A / N bits of multiple TBs.

[0126] For example, assume that the UE receives a DCI scheduling two TBs and receives two TBs via PDSCH based on the DCI. The UE performing spatial bundling can generate a single A / N bit by performing a logical AND operation on the first A / N bit of the first TB and the second A / N bit of the second TB. As a result, when both the first TB and the second TB are ACK, the UE reports the ACK bit value to the BS, and when either TB is NACK, the UE reports the NACK bit value to the BS.

[0127] For example, when only one TB is actually scheduled in a serving cell configured to receive two TBs, the UE can generate a single A / N bit by performing a logical AND operation on the A / N bit of one TB and the bit value 1. As a result, the UE reports the A / N bit of one TB to the BS as it is.

[0128] There are multiple parallel DL HARQ processes in the BS / UE for DL transmissions. While the BS waits for HARQ feedback on the successful or unsuccessful reception of a previous DL transmission, the multiple parallel HARQ processes allow DL transmissions to be performed continuously. Each HARQ process is associated with a HARQ buffer in the medium access control (MAC) layer. Each DL HARQ process manages state variables such as the number of transmissions of the MAC protocol data unit (PDU) in the buffer, the HARQ feedback for the MAC PDU in the buffer, and the current redundancy version. Each HARQ process is identified by a HARQ process ID.

[0129] Hereinafter, the PUSCH transmission procedure is described.

[0130] The UE can detect the PDCCH in slot #n. The PDCCH can include UL scheduling information (e.g., DCI format 0_0 or DCI format 0_1). DCI format 0_0 or DCI format 0_1 can include the following information.

[0131] - Frequency domain resource allocation: Indicates the set of RBs allocated to the PUSCH.

[0132] - Time domain resource allocation: Specifies the slot offset K2 indicating the starting position (e.g., symbol index) and the length of the PUSCH in the slot (e.g., the number of OFDM symbols). The starting symbol and length of the PUSCH can be indicated by the start and length indicator value (SLIV) or indicated separately.

[0133] Then, the UE can send the PUSCH in slot #(n + K2) according to the scheduling information in slot #n. The PUSCH includes the UL-SCH TB.

[0134] Method for configuring HARQ-ACK timing

[0135] The HARQ timing is defined by two parameters: K0 and K1. K0 and K1 represent the DL authorized PDCCH to the corresponding PDSCH transmission and the PDSCH to the slot with the corresponding HARQ-ACK transmission at the slot granularity. These values are configured considering the processing time of the UE according to its capabilities. The K0 value and the K1 value are indicated by the DCI. Specifically, the K0 value is indicated as follows. The row index of the PDSCH-TimeDomainResourceAllocationList configured by RRC is indicated by the time domain resource allocation field of the PDSCH in the DL authorization DCI. The corresponding IE specifies the K0 value, which is the slot offset between the DCI and the PDSCH it schedules. If this field does not exist, the UE applies the value 0 for K0. The time domain resource allocation is 4 bits, and the maximum number of entries in the PDSCH-TimeDomainResourceAllocationList (i.e., maxNrofDL-Allocations) is 16. To specify the K1 value, the dl-DataToUL-ACK or dl-DataToUL-ACKForDCIFormat1_2 is indicated by the PDSCH to HARQ feedback timing indicator field in the DL authorization DCI, and this PDSCH to HARQ feedback timing indicator field is at most 3 bits. That is, both the K0 value and the K1 value are indicated by the IE values configured by RRC for the DCI. If reusing the current configuration as it is, at least 5 bits and at most 7 bits are required.

[0136] The key parameters related to HARQ-ACK timing (see TS 38.331) can include the following parameters.

[0137] - k0: k0 can be the slot offset between the DCI and the scheduled PDSCH (see Section 5.1.2.1 of TS 38.214). For k0 up to r17, only the values {0..32} can be applicable to the 120 kHz PDSCH SCS. If the k0 field does not exist, the UE may apply the value 0 for k0.

[0138] - dl-DataToUL-ACK and dl-DataToUL-ACK-DCI-1-2: dl-DataToUL-ACK and dl-DataToUL-ACK-DCI-1-2 can be the timing lists for the PDSCH given for DL ACK (see Section 9.1.2 of TS 38.213). The dl-DataToUL-ACK field is applied to DCI format 1_1, and the dl-DataToUL-ACK-DCI-1-2 field is applied to DCI format 1_2. If dl-DataToUL-ACK-r16 or dl-DataToUL-ACK-r17 is signaled, the UE needs to ignore dl-DataToUL-ACK (without suffix). The value -1 can correspond to the "not applicable value" when the A / N feedback timing is not explicitly included in the PDSCH scheduling. The dl-DataToUL-ACK-r17 and dl-DataToUL-ACK-DCI-1-2-r17 fields can only be applied to the SCS of 480 kHz or 960 kHz.

[0139] Method for configuring PUCCH resources and HARQ-ACK codebook

[0140] The PUCCH resources are specified based on a combination of the PRI, CCE index, and UCI payload size. First, the PUCCH resource set to be used is determined by the UCI payload size (select one of PUCCH resource sets 0 to 3). If the PUCCH resource set is not PUCCH resource set 0, i.e., if the UCI payload size is greater than 2, the specific PUCCH resource within the resource set is determined by the PRI. In the case of PUCCH resource set 0, i.e., if the UCI payload size is 2 or less, the PUCCH resource is determined by both the CCE index and the PRI. Among them, the part that needs to be indicated by DCI is the 3-bit PRI.

[0141] The HARQ-ACK codebook includes a semi-static (Type 1) HARQ-ACK codebook and a dynamic (Type 2) HARQ-ACK codebook. The codebook type to be used is determined according to whether the RRC parameter HARQ_ACK-codebook is semi-static or dynamic. The representative feature of the semi-static codebook is that the PDSCH-to-HARQ-ACK timing (i.e., the set of K1) and the PDSCH reception occasion (i.e., the set of {K0, SLIV}) can be configured. Therefore, the number of bits to be sent in the ACK / NACK report is fixed and may be large. Thus, in specific cases, HARQ-ACK fallback to the semi-static codebook can be supported. Additionally, since multiple PDSCHs can be scheduled in a single time slot, for the semi-static HARQ-ACK codebook, pruning is used to determine which PDSCH each HARQ-ACK bit corresponds to. In other words, if the PDSCHs are in the same time slot, pruning based on SLIV is supported to determine which PDSCH each HARQ-ACK bit corresponds to. Here, pruning refers to the process of determining which PDSCH each bit for overlapping SLIVs within the same time slot corresponds to. This process is performed through the following steps.

[0142] - Determine the SLIV with the earliest ending symbol (e.g., SLIV A)

[0143] - Determine the set of SLIVs that overlap with SLIV A (e.g., set X)

[0144] - Assign the same HARQ-ACK bit to SLIV A and set X (then, remove them)

[0145] - Find the new SLIV A and its set X in the remaining SLIVs

[0146] The type 2 codebook is characterized in that the type 2 codebook supports ACK / NACK reporting for the scheduled PDSCH. Therefore, the number of bits to be sent in the ACK / NACK report can be variable. In this case, there may be an ambiguity between the UE and the gNB regarding the number of bits to be sent in the ACK / NACK report. To prevent this, the counter downlink assignment index (C-DAI) and the total downlink assignment index (T-DAI) are indicated by the DL grant DCI. Specifically, the C-DAI is signaled in both fallback and non-fallback DCI, while the T-DAI is signaled only in non-fallback DCI. In addition, when the CBG configuration is used together, the first sub-codebook assignment is based on the TB's PDSCH, and the second sub-codebook assignment is based on the CBG's PDSCH. When there is PDSCH reception, the C-DAI represents the cumulative number of {CC, m} pairs. In this case, for the {CC, M} pair, CC is mapped first, and then m. CC represents the component carrier, and m represents the downlink assignment index (DAI) number. Similarly, when there is PDSCH reception, the T-DAI represents the total number of {CC, m} pairs. For the {CC, M} pair, CC is mapped first, and then m. CC represents the component carrier, and m represents the DAI number.

[0147] In NR, for the following PDCCHs, the UE's operation of sending ACK for the PDCCH can be supported.

[0148] (1) SPS PDSCH release PDCCH

[0149] - DCI format 1_0 / 1_1 / 1_2

[0150] - CS-RNTI

[0151] - If the field value is a specific combination, it is determined as an SPS PDSCH release.

[0152] (2) TCI state update PDCCH

[0153] - DCI format 1_1 or DCI format 1_2

[0154] (3) SCell dormancy PDCCH

[0155] - DCI format 0_1 / 1_1 / 2_6

[0156] - SCell dormancy indication field

[0157] - The UE generates HARQ-ACK information bits as described in Clause 9.1.3 for the DCI format 1_1 indicating SCell dormancy, and the HARQ-ACK information bit value is ACK.

[0158] (4) Unified TCI indication (R17) PDCCH

[0159] However, for all the above cases, the mechanism for the UE to send ACK for the PDSCH is borrowed and supported. In other words, the aim is to refer to the PDSCH configuration or PUCCH configuration for configuring the HARQ-ACK timing and HARQ-ACK codebook, and to avoid introducing new DCI formats.

[0160] IAB (Integrated Access / Backhaul)

[0161] Examples where the network has such integrated access and backhaul links are where an IAB node or a relay node (rTRP) can multiplex the access and backhaul links in time, frequency, or space (e.g., beam-based operation).

[0162] The operations of different links can be at the same or different frequencies (also known as "in-band" and "out-of-band" relaying). Efficient support for out-of-band relaying is important in some NR deployment scenarios, but it is very important to understand the in-band operation requirements to accept the duplex constraints and avoid / mitigate interference, which means close interaction with the access link operating at the same frequency.

[0163] In addition, operating an NR system in the millimeter-wave spectrum may pose several unique challenges, including experiencing severe short-term blockages. Compared with short-term blockages, due to the larger time scale required for the completion process, the current RRC-based handover mechanism may not easily mitigate such severe short-term blockages.

[0164] To overcome short-term blockages in mmWave systems, a fast RAN-based mechanism (which may not necessarily require the intervention of the core network) may be needed for inter-rTRP handover.

[0165] In cases where it is necessary to more easily deploy self-backhauled NR cells, the need to mitigate short-term blockages in NR operations in the mmWave spectrum may lead to the need to develop an integrated framework that enables fast switching between access links and backhaul links.

[0166] In addition, over-the-air (OTA) coordination between rTRPs can be considered to mitigate interference and support end-to-end routing and optimization.

[0167] The following requirements and aspects may need to be addressed through integrated access and wireless backhaul (IAB) for NR.

[0168] - Efficient and flexible operation of in-band and out-of-band broadcasting in indoor and outdoor scenarios

[0169] - Multi-hop and redundant connections

[0170] - End-to-end routing and optimization

[0171] - Backhaul link support with high spectral efficiency

[0172] - Legacy NR UE support

[0173] Legacy NR (new RAT) is designed to support half-duplex devices. Additionally, half-duplex for the IAB scenario is supported and is worthy of being targeted. Furthermore, full-duplex IAB devices can be studied.

[0174] In the IAB scenario, if each IAB node or relay node (RN) does not have scheduling capabilities, the donor gNB (DgNB) must schedule all the links between the DgNB-related RN and the UE. In other words, the DgNB can collect traffic information from all relevant RNs, make scheduling decisions for all links, and then notify each RN of the scheduling information.

[0175] Figure 8 Examples of the parent link and the child link are schematically illustrated.

[0176] As Figure 8 shown, the link between the IAB node and the parent node is called the parent link, and the link between the IAB node and the child node / UE is called the child link. That is, the link between the MT and the parent DU is called the parent link, and the link between the DU and the child MT / UE is called the child link.

[0177] However, depending on the interpretation or perspective, the link between the IAB node and the parent node can be called the backhaul link, and the link between the IAB node and the child node / UE can be called the access link.

[0178] The IAB node can receive the slot format configuration for communicating with the parent node and the slot format configuration for communicating with the child node / access UE.

[0179] In existing IAB nodes, TDM operations in which the DU and the MT operate through different time resources have been performed. On the other hand, for efficient resource operation, resource multiplexing such as SDM / FDM, FC, etc. is required between the DU and the MT. As Figure 7 shown, the link between the IAB node (IAB MT) and the parent node is called the parent link, and the link between the IAB node (IAB DU) and the child node (child MT) is called the child link. At this time, TDM operations between the parent link and the child link have been discussed, and SDM / FDM and FD operations are being discussed.

[0180] The DU and MT that exist in the same IAB node (or are co-located) cannot operate simultaneously due to in-node interference, misalignment of time slot / symbol boundaries, power sharing, etc., but can operate in TDM. On the other hand, multiplexing of SDM / FDM can be used between the DU and MT. This multiplexing is applicable to example cases where since the DU and MT use different panels, there is little interference between the panels. In such cases, the DU and MT that exist in the same IAB node (or are co-located) can send or receive data or information simultaneously, but it is not possible for each of the DU and MT to perform transmission and reception simultaneously or perform reception and transmission simultaneously.

[0181] Alternatively, FD can be used between the DU and MT. This is applicable to cases where there is little interference between the DU and MT (for example, when the frequency domain in which the DU operates is far from the frequency domain in which the MT operates). In such cases, the DU and MT that exist in the same IAB node (or are co-located) can freely send and receive data simultaneously. The DU and MT can send or receive data simultaneously, and each of the DU and MT can also perform transmission and reception simultaneously or perform reception and transmission simultaneously.

[0182] There can be N MT-CCs and M DU-cells within an IAB node. The MT-CCs that exist in the IAB node can operate through the same or different frequency resources, and one MT-CC can be connected to one or more parent DU-cells. The DU-cells that exist in the IAB node can operate through the same or different frequency resources.

[0183] For a specific MT-CC / DU-cell pair within an IAB node, the MT-CC and DU-cell can adopt a TDM relationship or a non-TDM relationship for the following four Tx / Rx direction combinations, and for each Tx / Rx combination, TDM or non-TDM can vary.

[0184] - DU-Tx / MT-Tx

[0185] - DU-Rx / MT-Rx

[0186] - DU-Tx / MT-Rx

[0187] - DU-Rx / MT-Tx

[0188] For example, for a specific MT-CC / DU-cell pair, all four Tx / Rx combinations can operate in the case of TDM. In this case, the corresponding DU-cell and the corresponding MT-CC should always operate in the case of TDM regardless of the Tx / Rx directions of the DU-cell and the MT-CC. In another example, for a specific MT-CC / DU-cell pair, all four Tx / Rx combinations can operate in the case of non-TDM. In this case, the corresponding DU-cell and MT-CC can operate simultaneously in the case of non-TDM regardless of the Tx / Rx directions of the DU-cell and the MT-CC. In another example, for a specific MT-CC / DU-cell pair, DU-Tx / MT-Tx and DU-Rx / MT-Rx can operate in the case of non-TDM, and DU-Tx / MT-Rx and DU-Rx / MT-Tx can operate in the case of TDM. The above operations involve methods (e.g., SDM / FDM) for allowing simultaneous operation when the Tx / Rx directions of the DU-cell and the MT-CC are the same, and the method can operate simultaneously when the Tx / Rx directions of the DU-cell and the MT-CC are the same. For each specific MT-CC / DU-cell pair within the IAB node, the TDM / non-TDM information for each Tx / Rx combination can be configured / determined differently or independently.

[0189] At this time, the IAB MT can connect to two parent DUs using, for example, a dual connectivity method or a DAPS-HO method.

[0190] Network Control Repeater (NCR) in NR

[0191] Coverage is a fundamental aspect of cellular network deployments. Mobile operators rely on different types of network nodes to provide comprehensive coverage in their deployments. Deployment of conventional full-stack cells is an option, but it may not always be possible (e.g., without the availability of backhaul) or economically viable. As a result, new types of network nodes are considered to increase the flexibility of mobile operators' network deployments. For example, integrated access and backhaul (IAB), as a new type of network node that does not require a wired backhaul, was introduced in Rel-16 and enhanced in Rel-17. Another type of network node is the RF repeater, which simply amplifies and forwards any signal it receives. RF repeaters have been widely deployed in 2G, 3G, and 4G to supplement the coverage provided by conventional full-stack cells. In Rel-17, RAN4 specified the RF and EMC requirements for such RF repeaters targeting NR for both FR1 and FR2. While RF repeaters provide a cost-effective means of extending network coverage, they have their limitations. RF repeaters simply perform amplification and forwarding operations without being able to consider various factors that can improve performance. These factors can include information about semi-static and / or dynamic downlink / uplink configurations, adaptive transmitter / receiver spatial beamforming, on-off states, etc.

[0192] A network-controlled repeater is an enhancement to the conventional RF repeater that has the ability to receive and process side control information from the network. The side control information can allow the network-controlled repeater to perform its amplification and forwarding operations in a more efficient manner. Potential benefits can include reduced unnecessary noise amplification, transmission and reception with better spatial directivity, and simplified network integration.

[0193] Figure 9 is a diagram illustrating an example of a topology in which a network-controlled repeater (NCR) performs transmission and reception between a gNB and a UE.

[0194] Referring to Figure 9 ,the NCR can include a radio unit (RU) and a mobile terminal (MT).

[0195] The gNB can include a central unit (CU) and / or a distributed unit (DU), and the NCR can be connected to the gNB. In the NCR, the MT can form a control link with the gNB, and the RU can form a forwarding link for the backhaul with the gNB and a forwarding link for the access with the UE.

[0196] The RU of the NCR can consist only of the RF layer. The RU can receive, at the RF side, the signals sent by the gNB via the forwarding link and can forward the received signals to the UE. As a result, the signals received from the UE can be received by the RF side and the received signals can be forwarded to the gNB. The RU can only send signals between the gNB and the UE and can not generate signals / channels by itself and send the generated signals / channels to the gNB / UE. Alternatively, the RU receives signals / channels from the gNB / UE but does not detect the received signals / channels. To forward the received signals, the RU can control, at the RF side, the direction of the Tx / Rx beam, the DL / UL direction, the on / off information, the transmit (Tx) power, etc. However, this RU operation cannot be determined by the NCR itself but can be completely controlled by the gNB.

[0197] The MT of the NCR described above can include the RF layer and the L1, L2, and / or L3 layers. For example, the MT can include only the RF layer and the L1 layer, or can include the L1 and L2 layers. Alternatively, the MT can include the RF layer and the L1 / L2 / L3 layers. The MT can detect / receive the signals / channels sent by the gNB and can generate the signals / channels to be sent to the gNB. In addition, the MT can receive the information (e.g., side control information) required to control the operation of the RU from the gNB. Furthermore, the MT can not perform the transmission and reception with the UE.

[0198] Figure 10 is a diagram illustrating a radio frequency (RF) repeater and an NCR.

[0199] Referring to Figure 10 (a) of, the existing RF repeater can perform beamforming with an omnidirectional or fixed direction applied. In contrast, referring to Figure 10 (b) of, the NCR can adaptively adjust the transmit / receive beam direction of the NCR according to the UE position and the UE channel condition, thereby obtaining a beamforming gain.

[0200] In addition, in the case of the existing RF repeater, since the DL / UL directions are not distinguishable from each other in the TDD system, the transmission and reception in the DL and UL directions are always performed simultaneously. Alternatively, only a fixed TDD configuration is applied to the existing RF repeater, so that the switching between the DL direction and the UL direction is performed using a fixed time pattern. In contrast, the NCR can perform DL / UL switching considering the TDD configuration. As a result, considering the switching. The NCR can enable adaptive DL / UL operation, can minimize the power consumption caused by forwarding unnecessary signals, and can also minimize interference.

[0201] In addition, in the case of an existing RF repeater, the power of the received signal is always amplified and transmitted regardless of whether the gNB and the UE are transmitting signals. As a result, unnecessary power consumption and interference to the surrounding environment are inevitably increased. In contrast, the NCR performs an on / off operation, and when there is no signal to be transmitted to the gNB and the UE, the operation of the RU is turned off, so that unnecessary signals are not transmitted.

[0202] In addition, in the case of an existing RF repeater, the power of the received signal at a fixed ratio is amplified and transmitted. When the signal is transmitted at an unnecessary high power, the interference affecting the surrounding environment can be reduced by reducing the transmission (Tx) power of the NCR. When the signal is transmitted at a low power, the transmission (Tx) power of the NCR is increased so that the signal can be stably transmitted to the receiver.

[0203] In addition, existing RF repeaters have operated without recognizing the DL / UL time slot boundary. On the other hand, in order for the NCR to adaptively adjust beamforming, on / off, DL / UL direction, transmission power, etc. as described above, the NCR must know the transmission / reception (Tx / Rx) boundary of the downlink (DL). As a result, the RU operation can be applied differently for each unit of time (e.g., time slot / symbol).

[0204] Side control information for NCR

[0205] Hereinafter, for ease of description, the operation in the NCR will be assumed. However, the content described below can be applied to devices other than the NCR. Specifically, the content described below can be applied to the operation of the RIS. For this purpose, the NCR mentioned in the present disclosure can be replaced with "RIS" and extended / interpreted. In this case, the RU can be used to forward signals from the gNB to the UE in the RIS and to forward signals from the UE to the gNB in the RIS, and the MT can be used to receive side control information required for transmitting signals for controlling the RU from the gNB. At this time, the term "network" can be interpreted as "gNB" or "CU / DU" hereinafter. In addition, the term "gNB" can be interpreted as "network", "CU" or "DU" hereinafter.

[0206] In order for the NCR to forward the signal received by the RU, it is possible to consider adjusting the direction of the transmission / reception (Tx / Rx) beam, DL / UL direction, on / off state, transmission (Tx) power, etc. at the RF side. However, the RU operation cannot be determined by the NCR itself, but can be completely controlled by the gNB. For this purpose, the MT can receive information required for controlling the RU operation (i.e., side control information) from the gNB. This side control information can be transmitted by L1 / L2 signaling such as MAC-CE and DCI.

[0207] The above side control information may include all or part of the following information.

[0208] - Beamforming information: Information about the transmit / receive (Tx / Rx) beam directions of the RU

[0209] Here, the beamforming information may include the beam direction for UL transmission to the gNB, the beam direction for DL reception from the gNB, the beam direction for DL transmission to the UE, and / or the beam direction for UL reception from the UE.

[0210] - Timing information for aligning the transmit / receive boundaries of the Network Control Repeater (NCR): Information for the RU to align the transmit / receive (Tx / Rx) slot symbol boundaries

[0211] - Information about the UL-DL TDD configuration: Information about the DL / UL directions of the RU

[0212] - On-off information for efficient interference management and improved energy efficiency: Information about the on-off operation of the RU

[0213] - Power control information for efficient interference management: Information about the transmit (Tx) power of the RU, and such information may include the UL transmit (Tx) power to the gNB and / or the DL transmit (Tx) power to the UE.

[0214] The NCR may consist of two parts: the Network Control Repeater Mobile Terminal (NCR-MT), which receives side control information from the gNB and sends reports to the gNB; and the Network Control Repeater Forwarder (NCR-Fwd), which receives transmit signals from the gNB and forwards the signals to the UE, or receives transmit signals from the UE and forwards the signals to the gNB.

[0215] In this regard, the following scenarios may be considered.

[0216] - The Network Control Repeater Mobile Terminal (NCR-MT) may be defined as a functional entity that realizes the exchange of control information (e.g., side control information) by communicating with the gNB via a control link (C-link). The C-link is based on the NR Uu interface. As a reference, the side control information is at least used to control the NCR-Forwarder.

[0217] - The Network Control Repeater Forwarder (NCR-Fwd) is defined as a functional entity that amplifies and forwards UL / DL RF signals between the gNB and the UE via a backhaul link and an access link. The operation of the NCR-Fwd can be controlled based on the side control information received from the gNB.

[0218] In NR, since cost - effectiveness is important for NCR, it is assumed that NCR uses AF (amplify - and - forward) relays instead of DF (decode - and - forward) relays. Therefore, the signal received by NCR - Fwd from the UE and sent to the gNB is only amplified and forwarded without being decoded. As a result, there may be limitations in transmitting the transmission signal from NCR - MT together on these transmission resources. For example, in order to multiplex the signal received from the UE and the transmission signal from NCR - MT, NCR - Fwd needs to know in advance the time - domain / frequency - domain or resources where the received signal from the UE exists. Additionally, the synchronization between the received signal and the transmission signal should be perfectly aligned. However, such identification of the time / frequency resources of the received signal and synchronization alignment may not be allowed in AF relays. Due to the regulatory limitations on the transmission signal power of NCR, it may be difficult for the uplink transmission of NCR - Fwd and the uplink transmission of NCR - MT to occur on the same time resource. Against this background, it can be assumed that the uplink transmissions of NCR - MT and NCR - Fwd are based on TDM operation.

[0219] HARQ-ACK transmission for PDCCH at NCR and its configuration method

[0220] In the present disclosure, when sending side control information (SCI) for NCR on the PDCCH, it can be assumed that NCR performs HARQ - ACK transmission for this PDCCH through the PUCCH. In this case, a new DCI format can be introduced / defined for the transmission of the SCI. Hereinafter, for the case where a new DCI format for the SCI is defined, the content of designing this DCI format and the method of configuring the information for HARQ - ACK transmission are described in detail.

[0221] For the definition of the DCI format, three aspects can be considered. For example, the determination of the PUCCH transmission time slot, the configuration of PUCCH resources within the PUCCH transmission time slot, and the configuration of the HARQ - ACK codebook can be considered. Considering these three aspects, the content to be included in the DCI format for sending the SCI and the operation perspective of NCR will be described in detail.

[0222] First, the PUCCH transmission time slot will be described. The PUCCH transmission time slot can be the time slot for transmitting HARQ-ACK information. To allow the NCR to transmit HARQ-ACK for the PDCCH containing / carrying the SCI received from the gNB via the PUCCH, existing methods for specifying the PUCCH transmission time slot can be considered. That is, the position of the relative PUCCH transmission time slot (defined below as the K1' offset) can be determined at the time slot level starting from the time slot in which the DCI is received by the NCR. For example, when the HARQ-ACK codebook is semi-static, the existing K1 value and SLIV need to be trimmed, that is, to determine which HARQ-ACK bit corresponds to which PDSCH or PDCCH bit (for multiple HARQ-ACK bits reported by the UE via the PUCCH). In the case of a dynamic HARQ-ACK codebook, since the T-DAI (and / or C-DAI) is indicated in the DCI and no trimming is required, the existing K1 value may still be needed. The existing K1 value and SLIV value on the PDSCH can be indicated via the DCI to indicate which row of the PDSCH-TimeDomainResourceAllocation in the multiple PDSCH-TimeDomainResourceAllocation entries pre-configured by the RRC for the UE. However, when the gNB transmits the SCI via the PDSCH (i.e., when the DL grant is included in the DCI), the existing DL grant DCI format (e.g., DCI format 1_0, 1_1, 1_2, etc.) can be used. On the contrary, when the gNB transmits the SCI via the PDCCH instead of the PDSCH, the PDCCH may not need to schedule the PDSCH, so the DL grant may not be included in the PDCCH. In other words, it may not be necessary to indirectly indicate the K0 value through the PDSCH time domain resource allocation (TDRA) as in the existing mechanism. On the other hand, the DCI field for indicating the K0 value through the TDRA can be 4 bits. Additionally, the maxNrofDL-Allocations that can be configured for the UE can be 16.

[0223] The existing HARQ-ACK timing will be explained again. As referred to Figure 7As explained, the HARQ-ACK timing can be defined based on two parameters K0 and K1. These two parameters can respectively represent the DL grant PDCCH to the corresponding PDSCH transmission and the PDSCH to the slot with the corresponding HARQ-ACK transmission at the slot granularity. In other words, the HARQ-ACK transmission slot can be determined as the slot K0+K1 slots after the slot where the DL grant PDCCH is transmitted. Here, the K0 value and the K1 value can be determined / configured based on the processing time of the UE according to its capabilities. The K0 value and the K1 value can be indicated by DCI. Specifically, the K0 value is indicated as follows. The row index of the PDSCH-TimeDomainResourceAllocationList configured by RRC is indicated by the time domain resource assignment field of the PDSCH in the DL grant DCI. The IE corresponding to this row index specifies the K0 value (i.e., the slot offset between the DCI and the PDSCH it schedules). If the field related to the K0 value does not exist, the UE can apply the value 0 for K0. The time domain resource assignment is 4 bits, and the maximum number of entries in the PDSCH-TimeDomainResourceAllocationList (i.e., maxNrofDL-Allocations) can be 16. To specify the K1 value, the dl-DataToUL-ACK or dl-DataToUL-ACKForDCIFormat1_2 is indicated by the PDSCH to HARQ feedback timing indicator field in the DL authorization DCI, and this PDSCH to HARQ feedback timing indicator field is at most 3 bits. In other words, the K0 value and the K1 value can be determined / configured by the IE values configured by RRC indicated in the DCI. According to a specific scenario (3GPP), the range of the K0 value and the K1 value may range from at least 5 bits to at most 7 bits.

[0224] The K1 value needs to be configured considering the processing time. The capabilities related to the UE processing time can include N1 and / or N2. Specifically, as the capabilities related to the symbol granularity of the processing time expected to be reported by the NCR to the gNB, N1 and N2 can be defined as follows:

[0225] - N1: From the UE's perspective, the number of OFDM symbols required from the end of PDSCH reception to the earliest possible start of the corresponding HARQ-ACK transmission

[0226] - N2: From the UE's perspective, the number of OFDM symbols required from the end of the PDCCH reception containing the UL grant to the earliest possible start of the corresponding PUSCH transmission

[0227] As a capability report, for each SCS (and / or for the case of only preamble DMRS and for the case of preamble DMRS + additional DMRS), N1 can be reported as capability 1 (baseline UE processing time capability) or capability 2 (aggressive UE processing time capability).

[0228] In this context, when determining the transmission position of the ACK bit based on K1 in the semi-static codebook, various factors such as DCI overhead reduction and existing framework maintenance can be considered to determine / configure the K1 offset value.

[0229] Additionally, regarding the configuration method of PUCCH resources within the PUCCH transmission time slot, the PUCCH resources can be specified based on the PRI, CCE index, and UCI payload. Specifically, the indication method can be divided into two stages: before and after the dedicated PUCCH resource configuration. For example, before the dedicated PUCCH resource configuration, a 4-bit RMSI indicates the resource set, and a 3-bit PRI indicates which subset within the indicated resource set to use. Subsequently, the specific PUCCH resource to be used within the indicated subset can be indicated by the CCE index. Conversely, after the dedicated PUCCH resource configuration, 32 PUCCH resources can be configured in the first PUCCH resource set, and up to 8 PUCCH resources can be configured in each of the second to fourth PUCCH resource sets. Among the PUCCH resource sets, if the UCI payload is less than 2, the first PUCCH resource set is used. If the UCI payload is greater than 2, the PUCCH resource set to be used is determined based on a predetermined value according to the UCI payload size. When using the first PUCCH resource set, a 3-bit PRI indicates which subset within the PUCCH resource set to use, and the specific PUCCH resource to be selected / used within the indicated subset can be determined based on the CCE index. On the other hand, when using / indicating the second to fourth PUCCH resource sets, the PUCCH resource to be used within the PUCCH resource set can be indicated by the PRI without considering the CCE index.

[0230] In summary, when using the existing mechanism for transmitting HARQ-ACK for the PDSCH to transmit HARQ-ACK information for the received PDCCH, the following information may be required:

[0231] - HARQ-ACK transmission time slot: It is necessary to determine the time slot position for transmitting the HARQ-ACK. Existing UEs receive information about K0 and K1 via DCI and can determine the HARQ-ACK transmission time slot as the time slot K0 + K1 time slots after the time slot when the PDCCH is received.

[0232] - PUCCH Resource: The PUCCH resource for transmitting HARQ-ACK information can be determined from multiple PUCCH resources. To this end, the existing UE can receive PRI information via DCI.

[0233] - HARQ-ACK Codebook: Information about the number of bits constituting the entire HARQ-ACK information and the bit positions for transmitting the HARQ-ACK information may be required. To this end, when using a semi-static HARQ codebook, the UE can receive the following information from the gNB:

[0234] -- K1: The K1 value is indicated by the PDSCH-to-HARQ feedback timing indicator field in DCI.

[0235] -- SLIV: Information about which SLIV among the SLIVs configured by each row index (i.e., TDRA index) in the TDRA table is used to transmit the HARQ-ACK for the PDSCH is required. The bit positions of the HARQ-ACK information to be transmitted are determined based on the symbol resources constituting the indicated SLIV. The UE can receive the SLIV through the TDRA field in DCI.

[0236] Alternatively, when using a dynamic HARQ codebook, DAI may be required. In this case, to indicate DAI, C-DAI value and T-DAI value may be required. The UE can receive the C-DAI value and T-DAI value through the DAI field in DCI.

[0237] Based on the above methods and the methods described later, the BS can set some parameters for the UE through RRC: {K0, SLIV, K1, PRI, C-DAI, T-DAI}, and the specific values of these parameters can be indicated / specified through DCI. Based on the parameters (or parameter values) indicated / configured through RRC, the UE or NCR-MT can calculate / determine / select the candidate resources for A / N feedback. Among these candidate resources, the UE can transmit the PUCCH including A / N on the PUCCH resource indicated / specified based on the parameters for A / N feedback indicated through DCI.

[0238] Based on the foregoing, the method by which the NCR transmits the HARQ-ACK for the PDCCH carrying the SCI received from the gNB through the PUCCH can consider the following Scenario 1 and Scenario 2.

[0239] 1. Scenario 1

[0240] In Scenario 1, the NCR can configure the HARQ-ACK codebook according to the existing codebook configuration method. The HARQ-ACK for the PDCCH carrying / sending the SCI can be combined with other HARQ-ACKs.

[0241] In scenario 1, when the NCR-MT sends a HARQ-ACK for a new DCI format related to the PDCCH carrying the SCI, the HARQ-ACK can be combined with the HARQ-ACK for another PDCCH or PDSCH. For this purpose, it is necessary to maintain the existing HARQ-ACK transmission method. However, the DCI included in the PDCCH carrying / sending the SCI (hereinafter referred to as the DCI for SCI) may not schedule the PDSCH, and it may not be used for multiple purposes like the existing HARQ-ACK PDCCH (e.g., the PDCCH for Scell dormancy, SPS PDSCH release, TCI state update). In this case, if the DCI for SCI is based on the existing DCI format, it may include unnecessary information. Therefore, the present disclosure proposes a method that can reduce the overhead of the DCI format for SCI while ensuring coexistence with the existing HARQ-ACK. For example, to coexist with the existing HARQ-ACK, the DCI for SCI needs to reuse the existing PUCCH resource indication method. That is, the DCI for SCI should include the aforementioned PRI and can reuse the existing method of selecting / indicating the PUCCH resource set and PUCCH resources.

[0242] Scenario 1 can be explained in three main cases. First, regarding NCR, the following cases can be considered: Case 1 where only the semi-static (type 1) HARQ-ACK codebook is applicable (i.e., NCR only supports the semi-static (type 1) HARQ-ACK codebook); and Case 2 where only the dynamic (type 2) HARQ-ACK codebook is applicable (i.e., NCR only supports the dynamic (type 2) HARQ-ACK codebook). Both of these cases have the advantage of reducing the complexity of NCR, but the disadvantage of these methods is that they cannot inherit the existing configuration. To address this disadvantage, Case 3 is considered, that is, supporting both the semi-static (type 1) HARQ-ACK codebook and the dynamic (type 2) HARQ-ACK codebook. The existing method of selecting / indicating the PUCCH resource set and PUCCH resources will be explained for each of Case 1, Case 2, and Case 3 below.

[0243] (1) Case 1-1: The case where only the semi-static (type 1) HARQ-ACK codebook is applicable

[0244] In Case 1-1, it is considered that NCR only supports semi-static (Type 1) HARQ-ACK codebooks. That is, NCR can only support Type 1 HARQ-ACK codebooks through capability reporting or previous protocols (consensus). In this case, it is assumed that NCR does not support HARQ-ACK fallback for existing semi-static codebooks. In other words, even if NCR supports existing HARQ-ACK fallback, NCR can still send HARQ-ACK based on the semi-static HARQ-ACK codebook.

[0245] - Receive only a single PDCCH / PDSCH in the Pcell

[0246] - The PDCCH / PDSCH is scheduled by fallback DCI

[0247] - The DCI includes a C-DAI with a value of 1

[0248] NCR can be configured not to send HARQ-ACK for operations such as UL TDM frequently. In this case, NCR may include many bits in a single HARQ-ACK report. For the purpose of reducing NCR complexity and facilitating configuration, it is considered that NCR only supports semi-static HARQ-ACK codebooks. Since the transmission position of (HARQ) ACK bits in the semi-static HARQ-ACK codebook is determined according to K1, it may not be appropriate to set the K1' offset (PDCCH to HARQ-ACK timing) to an arbitrary value.

[0249] In this case, the DCI for SCI (or the DCI for the PDCCH carrying SCI) needs to include information about the SLIV, K0, and K1 of the PDSCH. On the other hand, the DCI for SCI (or the DCI for the PDCCH carrying SCI) may not require fields for C-DAI and T-DAI. Therefore, when NCR only applies semi-static HARQ-ACK codebooks, it can be assumed that the DCI for SCI may not include the T-DAI and C-DAI fields. In this case, the gNB can provide the HARQ ACK transmission timing to NCR via the DCI for SCI (which includes information about the SLIV, K0, and K1 of the PDSCH) based on at least one of the following alternative options:

[0250] 1) Alternative 1-1

[0251] In Alternative 1-1, the DCI for SCI can indicate {SLIV of the PDSCH, K0} and K1 in a similar or identical manner to the existing DL grant DCI.

[0252] Specifically, the DCI for SCI may include a field indicating a specific row index in the PDSCH-TimeDomainResourceAllocation configured by RRC (a field for indicating the SLIV and K0 of the PDSCH) and a field indicating the index of dl-DataToUL-ACK or dl-DataToUL-ACK-DCI-1-2 in the PUCCH-Config configured by RRC (a field for indicating K1). That is, in alternative 1-1, the DCI for SCI may define the existence of a dedicated field for the content of the existing DCI format and a method for indicating that content, as shown in Table 7 below.

[0253] [Table 7]

[0254]

[0255] 2) Alternative 1-2

[0256] In alternative 1-2, the DCI for SCI indicates K1 in the same way as the existing DL grant DCI, but the DCI for SCI may not indicate {the SLIV of the PDSCH, K0} in the same way as the existing DL grant DCI.

[0257] Specifically, the DCI for SCI includes a field indicating the index of dl-DataToUL-ACK or dl-DataToUL-ACK-DCI-1-2 in the PUCCH-Config configured by RRC (a field for indicating K1), but the DCI for SCI may not include a field indicating a specific row index in the PDSCH-TimeDomainResourceAllocation configured by RRC (a field for indicating the SLIV and K0 of the PDSCH).

[0258] Alternatively, the DCI for SCI may have a dedicated field for the SLIV and K0 of the PDSCH, but compared with the existing DCI, this dedicated field may only indicate the K0 value. This dedicated field may directly indicate the K0 value based on a specified bit width, or this dedicated field may indicate one of the candidate K0 values based on a previous protocol. For example, if N bits are allocated to the dedicated field, it may be pre-agreed that 2 NA candidate K0 value. In this case, one of the candidate K0 values can be indicated based on the value indicated by a dedicated field. The SLIV can be configured based on a predefined rule. According to the predefined rule, the SLIV can be preset as a specific SLIV, the SLIV corresponding to the entire time slot, the SLIV existing only in the first time slot symbol, or the SLIV existing only in the last time slot symbol. Alternatively, based on the predefined rule, the SLIV can be set as the SLIV value including the most symbols among the candidate SLIV values of the PDSCH configured by RRC.

[0259] Alternatively, the DCI for the SCI can include a dedicated field for the SLIV and K0 of the PDSCH, but compared with the existing DCI, this dedicated field may only indicate the SLIV value. This dedicated field can directly indicate the SLIV value based on the specified bit width, or this dedicated field can indicate one of the candidate SLIV values based on the previous protocol. For example, if N bits are allocated to the dedicated field, it can be pre-agreed that there are 2 N candidate SLIV values. In this case, one of the candidate SLIV values can be indicated based on the value indicated by the dedicated field. At the same time, K0 can be configured based on a predefined rule. In this case, in order to indicate the SLIV value according to the specified bit width, it can be considered that this dedicated field indicates one of the candidate SLIV values based on the previous protocol. For example, if N bits are allocated to the field, it can be pre-agreed that there are 2 N candidate SLIV values, and one of the candidate SLIV values is selected based on the value indicated by the field. The K0 value can be defined / configured according to the predefined rule. For example, according to the predefined rule, K0 can always be set to 0, and in this case, the K1 indicated by the DCI for the SCI can be the PDCCH-to-HARQ-ACK timing (K1' offset). Alternatively, according to the predefined rule, K0 can be fixed to a specific value other than 0.

[0260] Alternatively, the DCI for SCI may not include dedicated fields for SLIV and K0 for PDSCH, and both the SLIV value and the K0 value may be configured / defined based on predefined rules. For example, according to the predefined rules, the SLIV may be configured / defined as a specific SLIV, a value corresponding to the entire time slot, an SLIV value that exists only in the first time slot symbol, or an SLIV value that exists only in the last time slot symbol. Alternatively, based on the predefined rules, the SLIV may be set to the SLIV value that includes the most symbols among the candidate SLIV values of the PDSCH configured by RRC. In addition, according to the predefined rules, K0 may always be configured / defined as 0, and in this case, the K1 indicated by the DCI for SCI may be the PDCCH-to-HARQ-ACK timing (K1’ offset). Alternatively, according to the predefined rules, K0 may be fixed to a specific value other than 0. Alternatively, {K0, SLIV} may be set / determined to the {K0, SLIV} defined for the lowest or highest row index in the TDRA table without even being separately indicated.

[0261] In this way, in alternative 1-2, the DCI for SCI may define the presence of dedicated fields of the existing DCI format content and the method of indicating that content, as shown in Table 8 below.

[0262] [Table 8]

[0263]

[0264] 3) Alternative 1-3

[0265] In alternative 1-3, the DCI for SCI indicates {SLIV of PDSCH, K0} in the same way as the existing DL grant DCI, but the DCI for SCI may indicate K1 in a different way from the existing DL grant DCI.

[0266] Specifically, the DCI for SCI includes a field indicating a specific row index in the PDSCH-TimeDomainResourceAllocation configured by RRC (the field for indicating the SLIV and K0 of the PDSCH), but the DCI for SCI may not include a field indicating the index of dl-DataToUL-ACK or dl-DataToUL-ACK-DCI-1-2 in the PUCCH-Config configured by RRC (see TS.38.331) (the field for indicating K1). In this case, K1 can be configured / determined based on pre-agreed or pre-specified values. For example, K1 can be derived from the N1 value reported by NCR (the number of OFDM symbols required from the end of PDSCH reception to the earliest possible start of the corresponding HARQ-ACK transmission from the UE's perspective). Since the N1 value is at the symbol granularity, K1 can be set / determined to the value obtained by converting the N1 value into time slots. For example, if N1 is 17 (symbols), when N1 is converted into time slot units, N1 may be 1 time slot (14 symbols) + 3 symbols. By rounding up the converted value to the time slot unit (or applying ceil(N1)), the N1 converted into time slot units can be regarded as 2 time slots. In this case, K1 can be set / determined to 3 (or 2). Alternatively, the K1 value and the K0 value (and / or the SLIV of the PDSCH) can be pre-mapped to each other, and based on this mapping, K1 can be determined / set to a value corresponding to the K0 value (and / or the SLIV of the PDSCH) indicated in the DCI for SCI. The mapping relationship between the K1 value and the K0 value (and / or the SLIV of the PDSCH) can be configured by the BS (gNB) through RRC or DCI, etc. Alternatively, K1 can be determined / set to the maximum (or minimum) value within the pre-configured K1 range (or among the K1 values configured by RRC signaling).

[0267] Alternatively, the DCI for SCI can have a dedicated field for K1, but compared with the existing method, this dedicated field may only indicate the K1 value. In this case, the dedicated field can directly indicate the K1 value according to the specified bit width. Alternatively, one of the K0 candidate values can be indicated based on a previous protocol. For example, if N bits are allocated to the dedicated field, 2 N candidate K1 values can be pre-agreed, and one of the candidate K1 values is selected based on the value indicated by the dedicated field.

[0268] In this way, in alternative scenarios 1-3, the DCI for SCI can define the existence of a dedicated field for the content of the existing DCI format and the method for indicating this content, as shown in Table 9 below.

[0269] [Table 9]

[0270]

[0271] 4) Alternative 1-4

[0272] In alternative 1 - 4, the DCI for SCI may not indicate {SLIV of PDSCH, K0} and K1 in the same way as the existing DL grant DCI.

[0273] Specifically, the DCI for SCI may not include a field indicating a specific row index in PDSCH - TimeDomainResourceAllocation configured by RRC (the field for indicating SLIV and K0 of PDSCH) and a field indicating the index of dl - DataToUL - ACK or dl - DataToUL - ACK - DCI - 1 - 2 in PUCCH - Config configured by RRC (the field for indicating K1).

[0274] Specifically, the DCI for SCI does not have dedicated fields for SLIV and K0 of PDSCH, and both the SLIV and K0 values can be determined based on predefined rules. For example, the SLIV value can be determined as / assumed to be a specific SLIV value based on predefined rules. Alternatively, the SLIV value can be set as / defined as a value corresponding to the entire time slot, an SLIV value that only exists in the first time - slot symbol, or an SLIV value that only exists in the last time - slot symbol. Alternatively, based on predefined rules, the SLIV can be set as the SLIV value among the candidate SLIV values of PDSCH configured by RRC that includes the most symbols. Additionally, according to predefined rules, K0 can always be set as / defined as 0, and in this case, the K1 indicated by the DCI for SCI can be the PDCCH - to - HARQ - ACK timing (K1’ offset). Alternatively, according to predefined rules, K0 can be fixed to a specific value other than 0. Alternatively, {K0, SLIV} can be set as / determined as the {K0, SLIV} defined for the lowest or highest row index in the TDRA table, even without separate indication.

[0275] Alternatively, the DCI for SCI can have dedicated fields for SLIV and K0 of PDSCH. However, compared with the existing method, this dedicated field may only indicate the K0 value, and the SLIV can be configured / determined based on predefined rules. In this case, the dedicated field can directly indicate the K0 value based on a specified bit width, or can indicate one of the candidate K0 values based on a previous protocol. For example, if N bits are allocated to the dedicated field, 2 N candidate K0 values can be pre - agreed / defined, and based on the value indicated in the dedicated field, 2 NOne of the candidate K0 values. At the same time, the SLIV value can be determined / assumed to be a specific SLIV value based on a predefined rule. Alternatively, the SLIV value can be set / defined as the value corresponding to the entire time slot, the SLIV value existing only in the first time slot symbol, or the SLIV value existing only in the last time slot symbol. Alternatively, based on a predefined rule, the SLIV can be set as the SLIV value including the most symbols among the candidate SLIV values of the PDSCH configured by RRC.

[0276] Alternatively, the DCI for the SCI can include a dedicated field for the SLIV and K0 of the PDSCH, but compared with the existing method, this dedicated field may only indicate the SLIV value. For example, the dedicated field can directly indicate the SLIV value based on a specified bit width, or can indicate one of the candidate SLIV values based on a previous protocol. For example, if N bits are allocated to the dedicated field, 2 N candidate SLIV values can be pre-agreed / defined, and based on the value indicated in the dedicated field, one of the 2 N candidate SLIV values can be selected / configured. At the same time, according to a predefined rule, K0 can always be set / defined as 0, and in this case, the K1 indicated by the DCI for the SCI can be the PDCCH-to-HARQ-ACK timing (K1' offset). Alternatively, according to a predefined rule, K0 can be fixed to a specific value other than 0.

[0277] In addition, the DCI for the SCI can include a dedicated field for K1, but compared with the existing method, this dedicated field may only indicate the K1 value. In this case, the dedicated field can directly indicate the K1 value based on a specified bit width. Alternatively, based on a previous protocol, one of the candidate K0 values can be indicated. For example, if N bits are allocated to the dedicated field, 2 N candidate K1 values can be pre-agreed / defined, and based on the value indicated in the dedicated field, one of the 2 N candidate K1 values can be selected / configured.

[0278] Alternatively, the DCI for SCI may not include a dedicated field for K1. In this case, the K1 value may be determined / configured based on a previous protocol or consensus. For example, K1 may be derived from the N1 value reported by the NCR (the number of OFDM symbols required from the end of PDSCH reception to the earliest possible start of the corresponding HARQ-ACK transmission from the UE perspective). In this case, since the N1 value is at the symbol granularity, K1 may be set / determined to the value converted to a time slot from the N1 value. For example, if N1 is 17 (symbols), when converted to a time slot unit, it may be 1 time slot (14 symbols) + 3 symbols. By rounding up the converted value to a time slot unit (or applying ceil(N1)), the N1 converted to a time slot can be regarded as 2 time slots. In this case, K1 may be set / determined to 3 (or 2). The K1 value and the K0 value (and / or the SLIV of the PDSCH) may be pre-mapped to each other. Based on this mapping, K1 may be determined / set to a value corresponding to the K0 value (and / or the SLIV of the PDSCH) indicated in the DCI for SCI. The mapping relationship between the K1 value and the K0 value (and / or the SLIV of the PDSCH) may be configured by the gNB via RRC or DCI. Alternatively, K1 may be determined / set to a specific value, i.e., the maximum or minimum value within the pre-configured K1 range (or among the K1 values).

[0279] In this way, in alternative scenarios 1-4, the DCI for SCI may define the presence of dedicated fields of the existing DCI format content and the method of indicating this content, as shown in Table 10 below.

[0280] [Table 10]

[0281]

[0282] (2) Case 1-2: The case where NCR only applies the dynamic (Type 2) HARQ-ACK codebook

[0283] In cases 1-2, the NCR may support only the dynamic (type 2) HARQ-ACK codebook. That is, the NCR that may support only the type 2 HARQ-ACK codebook may be considered based on the capability report. Alternatively, it may be assumed that the NCR supports only the type 2 HARQ-ACK codebook based on a previous protocol or consensus.

[0284] According to the content indicated to the NCR via SCI, since the NCR is a network device, the NCR may not need to be frequently indicated via SCI. Therefore, the NCR may be configured not to send HARQ-ACK frequently. This means that the variability of HARQ-ACK bits may be necessary. Additionally, to reduce the NCR complexity and facilitate configuration, it may be necessary for the NCR to support only the type 2 HARQ-ACK codebook.

[0285] In this case, the DCI for SCI does not require the SLIV of PDSCH, but the DCI for SCI needs to include information about K0 and K1 and T-DAI and / or C-DAI. Therefore, when NCR only applies the dynamic (type 2) HARQ-ACK codebook, it can be assumed that the DCI for SCI does not have a dedicated field directly indicating the SLIV of PDSCH.

[0286] The value of K0 can be configured by at least one of the methods listed in alternative 1-1, alternative 1-2, alternative 1-3, and alternative 1-4 of case 1-1. That is, according to the existing DL grant method, the value of K0 can be indicated by a dedicated field for indicating the specific row index in the TDRA table configured by PDSCH-TimeDomainResourceAllocationList configured by RRC. Alternatively, a predetermined value can be applied according to a predefined rule without a dedicated field, or the existence of a dedicated field can be considered, but the value of K0 is indicated differently from the existing method.

[0287] The value of K1 can be configured by at least one of the methods listed in alternative 1-1, alternative 1-2, alternative 1-3, and alternative 1-4 of case 1-1. That is, according to the existing DL grant method, the value of K1 can be indicated by a dedicated field for indicating the index of dl-DataToUL-ACK or dl-DataToUL-ACK-DCI-1-2 in PUCCH-Config. Alternatively, a predetermined value can be applied according to a predefined rule without a dedicated field, or the existence of a dedicated field can be considered, but the value of K1 is indicated differently from the existing method.

[0288] It can be considered to indicate T-DAI and / or C-DAI differently from case 1-1. That is, it can be considered to indicate C-DAI and / or {T-DAI, C-DAI} in the same way as the dedicated field for indicating T-DAI and / or C-DAI in the existing fallback / non-fallback DCI. In other words, the DCI format for SCI can indicate C-DAI by a dedicated field in the same way as indicated in the fallback DCI, or the DCI format for SCI can indicate {T-DAI, C-DAI} by a dedicated field in the same way as indicated in the non-fallback DCI. Alternatively, the existence of a dedicated field can be considered, but only T-DAI is indicated differently from the existing method.

[0289] In case 1-2, the DCI for SCI can define the existence of dedicated fields for each content and the method of indicating that content, as shown in Table 11. It can be considered that the options in each column are applied independently.

[0290] [Table 11]

[0291]

[0292] (3) Case 1-3: The case where NCR can apply both the semi-static (Type 1) HARQ-ACK codebook and the dynamic (Type 2) HARQ-ACK Codebook

[0293] The case where NCR supports both semi-static (Type 1) HARQ-ACK codebooks and dynamic (Type 2) HARQ-ACK codebooks can be considered. In this case, to support combinations with other HARQ-ACKs (and to support both Type 1 HARQ-ACK codebooks and Type 2 HARQ-ACK codebooks), the DCI for the SCI needs to indicate the SLIV, K0, K1, and C-DAI (and / or T-DAI) of the PDSCH.

[0294] The SLIV (or the PDSCH for the SLIV) can be configured by at least one of the methods listed in Alternative 1-1, Alternative 1-2, Alternative 1-3, and Alternative 1-4 of Case 1-1. That is, according to the existing DL grant method, the SLIV (or the PDSCH for the SLIV) value can be indicated by a dedicated field for the row index used to indicate PDSCH-TimeDomainResourceAllocation. Alternatively, a predetermined value can be applied according to predefined rules without a dedicated field, or it can be considered that there is a dedicated field, but the SLIV (or the PDSCH for the SLIV) value is indicated differently from the existing method.

[0295] The K0 value can be configured by at least one of the methods listed in Alternative 1-1, Alternative 1-2, Alternative 1-3, and Alternative 1-4 of Case 1-1. That is, according to the existing DL grant method, the K0 value can be indicated by a dedicated field for the row index used to indicate PDSCH-TimeDomainResourceAllocation. Alternatively, a predetermined value can be applied according to predefined rules without a dedicated field, or it can be considered that there is a dedicated field, but the K0 value is indicated differently from the existing method.

[0296] The K1 value can be configured by at least one of the methods listed in Alternative 1-1, Alternative 1-2, Alternative 1-3, and Alternative 1-4 of Case 1-1. That is, according to the existing DL grant method, the K1 value can be indicated by a dedicated field for the index used to indicate dl-DataToUL-ACK or dl-DataToUL-ACK-DCI-1-2 in PUCCH-Config. Alternatively, a determined value can be applied according to predefined rules without a dedicated field, or it can be considered that there is a dedicated field, but the K1 value is indicated differently from the existing method.

[0297] T-DAI and / or C-DAI can be indicated according to the method mentioned in Scenario 1-2. It can be considered to indicate C-DAI and / or {T-DAI, C-DAI} in the same way as the dedicated fields used to indicate T-DAI and / or C-DAI in the existing fallback / non-fallback DCI. That is, the DCI format for SCI can indicate C-DAI through a dedicated field in the same way as indicated in the fallback DCI, or can indicate {T-DAI, C-DAI} through a dedicated field in the same way as indicated in the non-fallback DCI. Alternatively, there can be a dedicated field, but only T-DAI is indicated differently from the existing method.

[0298] In Scenario 1-3, the DCI for SCI can define the existence of dedicated fields for each content and the method of indicating that content, as shown in Table 12. It can be considered that the options in each column are applied independently.

[0299] [Table 12]

[0300]

[0301] 2. Scenario 2

[0302] In Scenario 2, the NCR can configure the HARQ-ACK codebook according to the existing codebook configuration method, but the HARQ-ACK for the DCI used for SCI (or the PDCCH carrying SCI) is not combined with other HARQ-ACKs.

[0303] In Scenario 2, a specific codebook (e.g., Type 1 HARQ-ACK codebook or Type 2 HARQ-ACK codebook) may always be used. However, considering the case of only using the Type 1 HARQ-ACK codebook, the PDCCH carrying SCI for the NCR may not be received frequently. In this case, compared with the HARQ-ACK codebook size, only a small number of HARQ-ACK bits may be included, and scheduling the PDCCH carrying SCI to match the HARQ-ACK codebook size may be redundant and impose scheduling constraints. Therefore, in Scenario 2, when sending the HARQ-ACK for the DCI used for SCI (or the PDCCH carrying SCI), it is necessary to configure the NCR to only apply / use the Type 2 HARQ-ACK codebook.

[0304] Compared with Case 1-2 of Scenario 1, even if NCR supports both Type 1 HARQ-ACK codebook and Type 2 HARQ-ACK codebook or has a semi-static (Type 1) HARQ-ACK codebook configured by RRC, it can be assumed that NCR (or NCR-MT) will perform HARQ-ACK fallback transmission to send HARQ-ACK for the DCI used for SCI. In this case, NCR (or NCR-MT) can assume / expect that the network or gNB will perform appropriate scheduling so that the HARQ-ACK for the DCI used for SCI will not conflict with other HARQ-ACK transmissions.

[0305] (1) Case 2-1: The case where the HARQ-ACK for DCI used for SCI never performs codebook combination

[0306] In Case 2-1, the HARQ-ACK for the DCI used for SCI (or the HARQ-ACK of the PDCCH carrying SCI) is essentially a dedicated HARQ-ACK with a 1-bit payload, and thus may not require indicating at least one pre-protocol specific PUCCH resource via PRI. In other words, the PUCCH resource can be specified according to predefined rules. In this case, even without a PRI indication, NCR can always assume that the HARQ-ACK for the DCI used for SCI indicates a specific PRI. For example, even if the PRI field is not included / defined in the DCI used for SCI, NCR can always assume or determine that the PRI is 1. In addition, regarding the implicit PUCCH resource selection due to the CCE index, NCR can assume or determine that a specific PUCCH resource indicated or already indicated via RRC (in advance) is used, regardless of the CCE index of the DCI used for SCI. Alternatively, NCR can determine that the PUCCH resource indication based on the CCE index is valid. That is, NCR can decide / select the PRI for the DCI used for SCI and select / determine the PUCCH resource based on predefined rules, or NCR can select / determine the PUCCH resource based on the CCE index of the DCI.

[0307] In addition, since the HARQ-ACK for the DCI used for SCI always has a 1-bit payload, a dedicated field for indicating C-DAI and / or T-DAI may not be required in the DCI. For example, the DCI used for SCI may not have an indication / configuration for SLIV, K0, K1, C-DAI, T-DAI, or PRI for the PDSCH. In this case, NCR-MT can use the PUCCH resource determined based on the previous protocol and send a HARQ-ACK with a 1-bit payload based on the Type 2 HARQ-ACK codebook in a time slot after a specific time slot offset based on the previous protocol starting from the DCI reception time.

[0308] Alternatively, for scheduling flexibility, in Scenario 2, K0 and / or K1 can be determined / configured based on predefined rules (or based on dedicated fields), similar to the method applied in Case 1-2 of Scenario 1. That is, in Case 2-1 of Scenario 2, the DCI for SCI can define the existence of dedicated fields for each content and the method of indicating the content, as shown in Table 13. The options in each column of Table 13 can be applied independently.

[0309] [Table 13]

[0310]

[0311] (2) Case 2-2

[0312] In Case 2-2, the HARQ-ACK for the DCI for SCI is not combined with other HARQ-ACK combinations through a codebook, but codebook combination can be applied to multiple HARQ-ACKs for the DCI for SCI.

[0313] Specifically, the HARQ-ACK for the DCI for SCI (or the PDCCH carrying SCI) has a variable payload, so the HARQ-ACK may not be combined with other HARQ-ACKs. In this case, since the specific PUCCH resource for the HARQ-ACK for the DCI for SCI is specified based on a previous protocol, the DCI for SCI may not need to indicate the PUCCH resource through the PRI. That is, since the PUCCH resource is specified by a predefined rule, the NCR can always assume that the HARQ-ACK for the DCI for SCI (or the HARQ-ACK for the PDCCH carrying SCI) indicates a specific PRI even without explicitly indicating the PRI. For example, even if there is no PRI field in the DCI for SCI, the NCR can always assume that the PRI of the HARQ-ACK for the DCI for SCI (or the HARQ-ACK for the PDCCH carrying SCI) is 1. In addition, regarding the implicit PUCCH resource selection based on the CCE index (i.e., the CCE index of the PDCCH carrying SCI), the NCR can determine to select a specific PUCCH resource preconfigured via RRC for the DCI for SCI regardless of the CCE index, or the NCR can determine that the PUCCH resource indication based on the CCE index is valid. That is, the NCR can determine the PRI of the DCI for SCI based on a predefined rule, or the NCR can select the PUCCH resource based on the CCE index of the DCI.

[0314] Alternatively, since the payload of the DCI for SCI is variable, the existing method of indicating the PUCCH resource by PRI for the DCI for SCI can be reused. In addition, compared with Case 2-1, since the DCI for SCI has a variable payload, it is not necessary to include both C-DAI and T-DAI in the DCI for SCI. In this case, the DCI for SCI can include only C-DAI or only T-DAI. However, similar to the existing HARQ-ACK operation, both {C-DAI, T-DAI} can also be indicated. In addition, compared with Case 2-1, since codebook combination can be performed between the HARQ-ACKs for the PDCCH carrying SCI, it may be necessary to indicate the K1 value by the DCI for SCI. The SLIV and K0 of the PDSCH do not need to be configured / indicated by the DCI for SCI.

[0315] Alternatively, for scheduling flexibility, K0 can be determined / configured according to a predefined rule, similar to Case 1-2 of Scenario 1, or K0 can be indicated based on a dedicated field in the DCI for SCI. K1 can also be indicated similar to Case 1-2 of Scenario 1. That is, in Case 2-2 of Scenario 2, the DCI for SCI can define the presence of dedicated fields for each content and the method of indicating the content, as shown in Table 14. The options in each column of Table 14 can be applied independently.

[0316] [Table 14]

[0317]

[0318] In summary, NCR-MT may require the following information to send HARQ-ACK for the PDCCH carrying SCI:

[0319] -> HARQ-ACK transmission time slot

[0320] - Method 1: The HARQ-ACK transmission time slot can be configured / determined based on the K0 value and the K1 value. In this case, NCR-MT can regard the time slot after K0 + K1 time slots starting from the time slot of transmitting the PDCCH carrying SCI as the time slot for transmitting HARQ-ACK.

[0321] --Regarding Method 1, the DCI for SCI can independently indicate the K0 value and the K1 value. In this case, the K0 value can be indicated by the TDRA index. For this purpose, the DCI carrying SCI can include a TDRA field. Alternatively, the DCI can include a dedicated field that independently indicates the K0 value. In this case, the K1 value can be indicated by the PDSCH-to-HARQ feedback timing indicator field included in the DCI for SCI. Alternatively, the K0 value can be configured by RRC, and the K1 value can be indicated by the DCI for SCI. In this case, the K1 value can be indicated by the PDSCH-to-HARQ feedback timing indicator field included in the DCI for SCI. Alternatively, the K0 value can be fixed to a specific value, and the K1 value can be indicated by the DCI for SCI. The specific value of K0 can correspond to the K0 value corresponding to a specific TDRA index. For example, the specific value of K0 can be determined based on the value of a specific TDRA index configured by RRC, or the specific value of K0 can always be determined based on a predefined value (e.g., 0, the lowest index, the highest index). In this case, the K1 value can be indicated by the PDSCH-to-HARQ feedback timing indicator field included in the DCI for SCI.

[0322] -Method 2: The HARQ-ACK transmission time slot can be determined / set based on the K1 value. In this case, the NCR-MT can consider the time slot K1 time slots after the time slot when the PDCCH carrying SCI is transmitted as the time slot for transmitting HARQ-ACK. For this purpose, the K1 value can be indicated by the PDSCH-to-HARQ feedback timing indicator field in the DCI for SCI. At the same time, Method 2 may be similar to Method 1, that is, the K0 value is always considered as 0.

[0323] -Method 3: The K1' value can be directly indicated to determine the HARQ-ACK transmission time slot. In this case, the NCR-MT can consider the time slot K1' time slots after the time slot when the PDCCH carrying SCI is transmitted as the time slot for transmitting HARQ-ACK. In this case, the DCI for SCI can indicate the K1' value.

[0324] ->PUCCH Resource

[0325] -Method 1: The PUCCH resource for transmitting HARQ-ACK can be determined based on the index value of the PUCCH resource indicated in the DCI for SCI. For example, the DCI can include a PRI field, and the index of the PUCCH resource can be indicated by the value included in the PRI field.

[0326] - Method 2: Compared with the method described in Method 1, in Method 2, the index of the PUCCH resource may not be indicated by DCI. In this case, even if the PRI is not included in the DCI, the NCR can determine that a specific PRI value has been indicated based on the received DCI. For example, if the UCI payload size is less than or equal to 2 (i.e., when determining the PUCCH resource from Resource Set 0), it can be assumed that the implicit indication via the CCE index is valid. In this case, the NCR can determine the PUCCH resource based on the CCE index in the DCI.

[0327] - Method 3: Even if the DCI does not indicate the PRI, the NCR can determine that a specific PRI value has been indicated based on the received DCI. In addition, when determining the PUCCH resource information, the CCE index of the DCI used to indicate the SCI can be regarded as a specific value based on the previous protocol, regardless of the actual CCE index of the DCI used to indicate the SCI.

[0328] -> Type 1 HARQ-ACK codebook

[0329] - When using the Type 1 HARQ-ACK codebook, information about the bit position used to send the HARQ-ACK information within the total number of bits constituting the HARQ-ACK information may be required. For this purpose, information about either or both of the SLIV and K1 may be required.

[0330] - The K1 value for determining the bit position used to send the HARQ-ACK information can be determined based on one of the following methods.

[0331] -- Method 1: The K1 value can be indicated by the PDSCH to HARQ feedback timing indicator field included in the DCI for the SCI.

[0332] -- Method 2: K1 can be pre-configured by RRC configuration.

[0333] -- Method 3: The K1 value can always be determined as a specific value. For example, when the value of the PDSCH to HARQ feedback timing indicator is a specific value (e.g., 0), the K1 value can be determined as the value corresponding to this value.

[0334] - The SLIV value for determining the bit position used to send the HARQ-ACK information can be determined based on one of the following methods.

[0335] -- Method 1: The SLIV information can be indicated by the DCI for the SCI. For example, the SLIV value can be determined as the value corresponding to / mapped to the row index included in the TDRA field of the DCI.

[0336] -- Method 2: SLIV can be indicated / configured through RRC configuration. For this purpose, the SLIV value can be directly configured. For example, the RRC configuration can indicate the row index of the TDRA, and the SLIV can be determined as the value mapped to the row index of the TDRA indicated by the RRC configuration.

[0337] -- Method 3: The row index value in the TDRA table used to determine the SLIV can be fixed to a specific value. For example, the SLIV can be determined as a specific value corresponding to / mapped to the lowest or highest row index (TDRA index 0) in the TDRA table.

[0338] -- Method 4: The SLIV can be determined as the SLIV value among the SLIV values corresponding to the TDRA table (among the SLIV values configured by PDSCH-TimeDomainResourceAllocationList) that has the earliest starting symbol.

[0339] - The following methods can be considered to determine the bit position for sending HARQ-ACK information.

[0340] -- Method 1: NCR-MT can always send the HARQ-ACK information for the PDCCH carrying the SCI in the first bit among the bits constituting the HARQ-ACK information.

[0341] -- Method 2: NCR-MT can always send the HARQ-ACK information for the PDCCH carrying the SCI in the last bit among the bits constituting the HARQ-ACK information.

[0342] -- Method 3: NCR-MT can always send the HARQ-ACK information for the PDCCH carrying the SCI in the specific B-th bit among the bits constituting the HARQ-ACK information. In this case, the value corresponding to B can be indicated by the K1 value of the DCI for the SCI, or this value can be indicated / configured through RRC configuration.

[0343] - Alternatively, NCR-MT can determine that the HARQ-ACK information for the PDCCH carrying the SCI is sent separately (as a single bit) without being combined with other HARQ-ACK information. That is, when NCR-MT sends the HARQ-ACK for the PDCCH carrying the SCI, the entire HARQ-ACK information consists of 1 bit, and the HARQ-ACK information for the PDCCH carrying the SCI can be sent through this 1 bit. In this case, it can be assumed that HARQ-ACK fallback is always applied when NCR-MT sends the HARQ-ACK information for the PDCCH carrying the SCI.

[0344] ->Type 2 HARQ-ACK Codebook

[0345] - When using the Type 1 HARQ-ACK codebook, the NCR-MT can determine the number of bits constituting the HARQ-ACK information and the bit positions for transmitting the HARQ-ACK information based on all or part of the C-DAI and T-DAI information. Specifically, the NCR-MT can determine the number of bits constituting the HARQ-ACK information and the bit positions for transmitting the HARQ-ACK information based on at least one of the following methods.

[0346] -- Method 1: The C-DAI and T-DAI information can be indicated by the DAI field of the DCI for the SCI.

[0347] -- Method 2: The NCR-MT can obtain / determine only the T-DAI information from the C-DAI and T-DAI fields in the DAI field of the DCI for the SCI. It can be assumed that the C-DAI value is always 0. This means that the HARQ-ACK information for the PDCCH carrying the SCI is always sent in the first bit among the bits constituting the HARQ-ACK information.

[0348] -- Method 3: The NCR-MT can assume that both T-DAI and C-DAI are 0. This means that the HARQ-ACK information for the PDCCH carrying the SCI is sent separately (as a single bit) without being combined with other HARQ-ACK information. That is, when the NCR-MT sends the HARQ-ACK for the PDCCH carrying the SCI, the entire HARQ-ACK information may consist of 1 bit, and only the HARQ-ACK information for the PDCCH carrying the SCI is sent through this 1 bit.

[0349] To send HARQ-ACK feedback in response to receiving the DCI for the SCI, the NCR can determine the HARQ-ACK transmission time slot based on the K0, K1, and / or SLIV information determined by the above methods. Determine the HARQ-ACK bits corresponding to the SCI reception within the HARQ-ACK payload. Based on the determined transmission time slot and HARQ-ACK bits, the NCR can map / transmit the HARQ-ACK bits for the SCI reception.

[0350] NCR's ability report for HARQ-ACK transmission from PDCCH

[0351] For the existing UE processing time, N1 and N2 are indicated at the symbol granularity. N1 refers to the number of OFDM symbols required for the earliest possible start of the corresponding HARQ-ACK transmission from the end of PDSCH reception from the UE's perspective. N2 refers to the number of OFDM symbols required for the earliest possible start of the corresponding PUSCH transmission from the end of PDCCH reception containing the UL grant from the UE's perspective. Since there is no ability report indicating the PDCCH to HARQ-ACK timing, the NCR may consider sending information about the time interval from the end of PDCCH reception to the start of the corresponding HARQ-ACK transmission from the NCR's perspective to the gNB through a specific ability report (e.g., processing ability report). This ability report can be directly reported at the symbol / slot level through UCI / MAC-CE / RRC, or reported as one of the pre-protocol candidates. The gNB needs to consider such an ability report when indicating the transmission timing of the PDCCH carrying the SCI and the HARQ-ACK. On the contrary, if the transmission timing of the PDCCH carrying the SCI and the HARQ-ACK is indicated with a shorter time interval than the reported ability, even if the NCR successfully receives the PDCCH carrying the SCI, the NCR may not send the HARQ-ACK for the PDCCH carrying the SCI and may not apply the SCI.

[0352] The methods proposed according to Scenario 1 and Scenario 2 can be summarized as follows.

[0353] 1. HARQ-ACK for PDCCH carrying SCI

[0354] During the discussion of a specific scenario, the following agreement was reached regarding the HARQ-ACK feedback for the SCI (see Table 15). It was decided to support the HARQ-ACK feedback for the PDSCH carrying the SCI. The support for the HARQ-ACK feedback for the PDCCH carrying the SCI was discussed, but this remains an open issue (FFS) to be further discussed.

[0355] [Table 15]

[0356]

[0357] In this section, the advantages and disadvantages of the HARQ-ACK for the PDCCH, the parameters required for HARQ-ACK transmission, and the operations required to support the HARQ-ACK will be described.

[0358] To determine whether to support HARQ-ACK for the PDCCH carrying the SCI, the advantages and disadvantages of transmission need to be considered. As described above, the SCI can include all or part of the (NCR-Fwd) on / off information and beam indication for the access link and the backhaul link. Since this is critical information directly affecting the NCR performance, it is necessary to clearly report whether the reception is successful. Through this report, it can help resolve the ambiguity between the NCR and the gNB regarding the transmission and reception of the SCI. However, if the NCR transmits HARQ-ACK for the PDCCH carrying the SCI, the SCI needs to be applied after the HARQ-ACK is transmitted via the PUCCH. For the gNB to expect specific operations from the NCR, the gNB needs to pre-indicate (via the SCI) these operations to the NCR, which can introduce the disadvantage of causing latency. Considering that the NCR does not have the ability to simultaneously transmit on the uplink for the backhaul link and the C link, the PUCCH transmission on the C link and the transmission on the backhaul link can be time-division multiplexed (TDMed). In this case, if more transmission opportunities are given to the C link to transmit HARQ-ACK for the PDCCH carrying the SCI, the uplink transmission on the backhaul link can be delayed. On the other hand, if the uplink transmission on the backhaul link is prioritized for the UE served by the NCR, the latency problem of transmitting HARQ-ACK for the PDCCH carrying the SCI may become more serious. In addition, when HARQ-ACK for the PDCCH is supported, if the UE fails to receive the corresponding DCI, it aims to alleviate the potential misunderstanding of the HARQ-ACK codebook configuration between the gNB and the UE, and such an inconsistency can occur subsequently. However, even if the DCI carrying the SCI from the NCR is not received, there may be no ambiguity regarding the HARQ-ACK codebook subsequently transmitted by the NCR. Nevertheless, if there is a misunderstanding between the NCR and the gNB regarding the reception and application of the NCR's on / off indication and beam indication information, link reliability problems may occur from the perspective of the UE served by the NCR. In addition, from the perspective of the gNB, the measurement reliability of the UE served by the NCR may be problematic.

[0359] - Observation 0: HARQ-ACK for the PDCCH carrying the SCI can help resolve the ambiguity between the NCR and the gNB regarding the transmission and reception of the SCI, but may increase latency. When considering that the NCR does not have the ability to simultaneously transmit on the uplink for the C link and the backhaul link, the latency problem can become more serious.

[0360] Whether to introduce HARQ-ACK for the PDCCH carrying SCI needs to be determined not only by considering the above advantages and disadvantages but also by considering the characteristics of the existing HARQ-ACK for PDCCH. Existing UEs support HARQ-ACK feedback operations for PDCCH. For example, the DCI for SPS PDSCH release, the DCI for TCI state update, and the indication of SCell dormancy can be sent via DL grants (e.g., DCI format 1_0, 1_1, 1_2). In this case, the UE can send HARQ-ACK for the PDCCH. In all cases, the existing HARQ-ACK transmission mechanism for PDSCH can be reused to send HARQ-ACK for the PDCCH. In other words, the method of sending HARQ-ACK for PDSCH based on DL grants can be reused to specify and indicate the parameters for HARQ-ACK transmission. To this end, even if the PDSCH is not actually scheduled by DCI, the DCI indicates information about the PDSCH transmission resource. Therefore, the HARQ-ACK for PDSCH can be sent instead on the resource specified for HARQ-ACK for the PDCCH. Therefore, to support HARQ-ACK for the PDCCH carrying SCI by reusing the existing mechanism, it is necessary to send SCI using the existing DL grant, or the DCI carrying SCI needs to include the fields required for HARQ-ACK transmission.

[0361] For sending HARQ-ACK for the PDCCH carrying SCI, the following determinations regarding HARQ-ACK feedback timing, PUCCH resources, and HARQ-ACK codebook may be required.

[0362] - To determine the timing for sending HARQ-ACK, two parameters are required: K0 and K1. K0 and K1 can represent the DL grant PDCCH to the corresponding PDSCH transmission and the PDSCH to the time slot with the corresponding HARQ-ACK transmission at the time slot granularity. The K0 value is indicated by the 4-bit TDRA field (which is 4 bits) of the DCI. The TDRA field can indicate a specific row index in the TDRA table configured via RRC's PDSCH-TimeDomainResourceAllocationList. The K1 value is indicated by the PDSCH to HARQ feedback timing indicator field of the DCI, which consists of at most 3 bits. The PDSCH to HARQ feedback timing indicator field can indicate the index of dl-DataToUL-ACK or dl-DataToUL-ACKForDCIFormat1_2 configured via RRC. In other words, both the K0 value and the K1 value can indicate specific values of the IE configured via RRC through the DCI. Therefore, when reusing the current configuration as it is, determining these two values requires at least 5 bits and at most 7 bits of the DCI field in total.

[0363] - The PUCCH resource can be indicated based on the PRI (or a combination of CCE index and UCI payload size) from the PUCCH resource set pre-configured via RRC. Therefore, a 3-bit PRI field may be required to determine the PUCCH resource.

[0364] - The HARQ-ACK codebook includes a semi-static (type 1) HARQ-ACK codebook and a dynamic (type 2) HARQ-ACK codebook. The type of codebook to be used can be configured via RRC. To determine the bit position for sending HARQ-ACK using the semi-static codebook, information about the PDSCH to HARQ-ACK timing (i.e., K1) and SLIV may be required. For this purpose, a 4-bit TDRA field and a PDSCH to HARQ feedback timing indicator field of at most 3 bits may be required. On the other hand, the type 2 codebook is characterized by its ability to support ACK / NACK reporting for the scheduled PDSCH. Therefore, the number of bits to be sent in the ACK / NACK report can be variable. In this case, there may be an ambiguity regarding the number of bits in the HARQ ACK / NACK report between the UE and the gNB. To prevent this ambiguity, the C-DAI and T-DAI can be indicated by a dedicated bit field of at most 4 bits in the DCI. In other words, to send HARQ-ACK using the dynamic HARQ-ACK codebook, DAI information may be required.

[0365] As described above, if HARQ-ACK transmission for DCI of SCI carrying NCR is supported (to inherit the existing HARQ-ACK structure), DCI fields may be required to indicate K0, K1, SLIV, PRI, C-DAI, and T-DAI. This may lead to an increase in DCI overhead. In addition, since the existing DCI format is used not only for HARQ-ACK transmission for DCI formats but also for DL authorization (i.e., scheduling PDSCH), the above fields may be necessary. However, since the DCI format for SCI does not support DL authorization, some of the above fields may be unnecessary. Therefore, in order to reduce the DCI overhead in the DCI format for SCI, only a dedicated bit field including the minimum information required for HARQ-ACK transmission needs to be included in the DCI format. In this case, it may be necessary to discuss which specific information is required for the DCI to indicate the HARQ-ACK feedback for the DCI carrying SCI.

[0366] - Observation 1: To support HARQ-ACK feedback for the PDCCH carrying SCI while reusing the existing mechanism, the following fields need to be included in the DCI for SCI.

[0367] -- When using a semi-static HARQ-ACK codebook, at least one of the following fields needs to be included: time-domain resource assignment field, PDSCH-to-HARQ feedback timing indicator field, or PUCCH resource indicator field.

[0368] -- When using a dynamic HARQ-ACK codebook, the DAI field needs to be included.

[0369] - Proposal 0: Methods for reducing the DCI fields required for HARQ-ACK feedback for the PDCCH carrying SCI need to be considered.

[0370] 2. DCI Design for SCI

[0371] Two types of DCI may be required for SCI. One type can be the DCI carrying / including the non-periodic SCI. The other type can be the DCI for activating / deactivating the semi-persistent SCI configuration.

[0372] (1) DCI for SCI

[0373] According to the discussion results in the companion proposal, the fields required for transmitting the non-periodic SCI are as follows.

[0374] - Beam / Off Indicator Field

[0375] Non-periodic SCI can support beam indication and shutdown status indication. As proposed in the companion proposal, beam indication and shutdown status indication are not indicated separately, but can be indicated by using a combination of beam / shutdown indication fields. For example, as shown in Table 16, if the value of the field is "0", it can indicate the shutdown status, and if it is other values, it can represent a specific beam index.

[0376] [Table 16]

[0377]

[0378] - Time resource indication field

[0379] To indicate the time resource for applying beam / shutdown indication, a time resource indication field may be required. By indicating the starting symbol position and symbol length with this field, the time resource composed of consecutive symbols can be indicated.

[0380] - HARQ-ACK related fields for DCI

[0381] As mentioned above, fields may be required to support HARQ-ACK feedback for the PDCCH carrying SCI. When reusing existing mechanisms as much as possible, at least one of the following fields should be included in DCI:

[0382] -- Time domain resource allocation

[0383] -- PDSCH to HARQ feedback timing indicator

[0384] -- PUCCH resource indicator

[0385] -- Downlink allocation index

[0386] In addition, methods to reduce DCI overhead and the required fields can be considered. In this case, the configuration related to the HARQ-ACK related fields for DCI may be different.

[0387] On the other hand, since an explicit turn-on indication is not required and the shutdown indication can be combined with the beam indication, an explicit field for indicating turn-on and / or shutdown may not be required. For backhaul link beam indication, since semi-static configuration is sufficient, a separate DCI field may not need to be defined.

[0388] Recommendation 1: For DCI used for SCI, the following fields are required -> beam / shutdown indication field, time resource indication field, HARQ-ACK related fields for DCI

[0389] In addition, to support beam and inactive state indication for multiple timing resources, multiple beam / inactive indication fields and timing resource indication fields may be required (in DCI). In this case, each beam / inactive indication may correspond to a specific timing resource indication. For example, the number of beam / inactive indication fields and timing resource indication fields may be equal. Beam / inactive indication 1 may be applied to the timing resource indicated by timing resource indication 1, and beam / inactive indication 2 may be applied to the timing resource indicated by timing resource indication 2. In this case, the size of DCI may vary according to the number of fields. To monitor DCI, NCR-MT needs to know the DCI size. For this purpose, the DCI length or the number of beam / inactive indication or timing resource indication fields may be configured via RRC.

[0390] Recommendation 2: The number of beam / inactive indication fields may be configured to determine the DCI size for SCI.

[0391] When designing the DCI format for carrying SCI, it should be determined whether the DCI is NCR-MT specific or NCR-MT group specific. Generally, when the amount of information to be sent to one UE is small and DCI needs to be sent to multiple UEs simultaneously (or the same information needs to be indicated to multiple UEs), the UE group specific DCI format may be appropriately used. However, SCI may need to include beam / inactive indication, corresponding timing resources, and HARQ-ACK related fields. In this case, the amount of content to be included in the DCI fields may be relatively large. In addition, since SCI is NCR-MT specific information, it is expected that the same SCI will not be sent to multiple NCR-MTs. In this regard, the DCI carrying SCI based on the NCR-MT specific DCI format may be more suitable than the NCR-MT group specific DCI format.

[0392] Recommendation 3: Support NCR-MT specific DCI to indicate aperiodic SCI.

[0393] Reusing the existing DCI format for DL / UL data scheduling for the DCI of SCI may not be appropriate. SCI is not information for data scheduling. That is, the use of SCI is completely different from the existing DL / UL grants. In addition, DL / UL grants include many redundant fields that are unnecessary for sending SCI. Therefore, a new DCI format needs to be introduced / defined for SCI.

[0394] Recommendation 4: Introduce a new DCI format for the DCI of SCI.

[0395] (2) DCI for activating / deactivating semi-persistent SCI

[0396] The configuration of semi-persistent SCI can be performed by RRC. In this case, DCI can indicate activation / deactivation on a per-configuration basis. For this purpose, DCI needs to include the following information:

[0397] - Configuration index field: To perform activation / deactivation of semi-persistent SCI on a per-configuration basis, the configuration index for which the activation / deactivation indication is to be applied can be indicated.

[0398] - Activation / deactivation indication field: A field indicating whether the configuration index indicated by the configuration index field is activated or deactivated.

[0399] - HARQ-ACK related fields for DCI: For the stable forwarding operation of NCR-Fwd, NCR-Fwd needs to perform HARQ-ACK feedback for DCI reception so that the gNB can determine whether the NCR-MT has received the DCI for activating / deactivating the semi-persistent SCI. For this purpose, similar to the DCI for SCI, at least one of the following fields may be required:

[0400] -- Time domain resource assignment

[0401] -- PDSCH to HARQ feedback timing indicator

[0402] -- PUCCH resource indicator

[0403] -- Downlink assignment index

[0404] On the other hand, if a method for reducing the DCI overhead and reducing the number of required fields is considered, the configuration of the HARQ-ACK related fields for DCI can be varied.

[0405] Recommendation 5: The DCI for activating / deactivating the semi-persistent SCI needs the following fields:

[0406] - Configuration index field

[0407] - Activation / deactivation indication field

[0408] - HARQ-ACK related fields for DCI

[0409] For the DCI for activating / deactivating the semi-persistent SCI, a separate DCI format can be created, or the same DCI format as that for the DCI for SCI can be used, but with different interpretations for the fields used for activating / deactivating the semi-persistent SCI.

[0410] To distinguish between the DCI for activating / deactivating the semi-persistent SCI and the DCI for SCI, the DCI for activating / deactivating the semi-persistent SCI can be scrambled using a different RNTI from that for the DCI for SCI.

[0411] Suggestion 6: It may be necessary to discuss whether to use the same DCI format as that used for SCI in the DCI, or to create a separate DCI format for activating / deactivating semi-persistent SCI.

[0412] Figure 11 It is a schematic diagram for explaining a method for a device having a backhaul link and a control link formed with a base station to perform communication.

[0413] The device may include an NCR-MT that forms a control link with the BS, and an NCR-fwd (NCR-RU) that forms a backhaul link with the BS and a forwarding link with the UE. In other words, the device may be the aforementioned NCR device. The device may receive control information related to the NCR through the control link and send its signal to the BS. In addition, the device may forward the signal received from the UE through the forwarding link to the BS through the backhaul link, or forward the signal received from the BS through the backhaul link to the UE through the forwarding link.

[0414] Refer to Figure 11 , the device may receive a PDCCH (S111) including a DCI (related to the control of the backhaul link) through the control link. In this case, the device may receive a DCI including control information for at least one of the control link and the backhaul link, and the control information for the backhaul link may be received through a DCI including an SCI.

[0415] Next, the device may determine the transmission resource of the HARQ feedback signal for the PDCCH (S113). Regarding the determination of the transmission resource, the device may differently determine the transmission resource based on whether the PDCCH includes a DCI for the control link or a DCI for the backhaul link. For example, if the PDCCH includes a DCI for the control link, the device may determine the transmission resource of the HARQ feedback signal based on values such as K0 / K1 indicated in the DCI. Alternatively, as described above, when the PDCCH includes a DCI including an SCI (which is control information for the backhaul link), the device may determine the transmission resource for the HARQ feedback signal based on the K0 / K1 values determined according to a predefined rule, regardless of the values indicated for K0 / K1 in the DCI.

[0416] Specifically, regarding the transmission of HARQ feedback signals / HARQ information, the device may transmit a HARQ feedback signal including HARQ information for DCI / PDCCH at or on a HARQ transmission timing / transmission resource determined based on at least one of the following indicated in the DCI: K0, K1, SLIV, PRI, C-DAI, and T-DAI. As described above, K0 includes information about the slot interval between the PDCCH and the PDSCH scheduled by the PDCCH, and K1 includes information about the interval between the PDSCH and the HARQ feedback signal.

[0417] As described above, when the DCI is used to transmit SCI (which is control information for the backhaul link) (existing DCI format or new DCI format), the device may determine at least one of the K0 value and the K1 value (and / or SLIV, PRI, C-DAI, and T-DAI) based on a predefined rule, regardless of the DCI (even when the HARQ-ACK codebook is configured to be determined based on the DCI, such as a type 2 HARQ-ACK codebook). For example, even if the DCI does not include a dedicated field indicating K0 / K1 (or even if such a dedicated field for K0 / K1 is included in the DCI), the device may determine the K0 / K1 value according to the predefined rule. For example, as described in alternative 1-1, alternative 1-2, alternative 1-3, and / or alternative 1-4 of case 1-1 in scenario 1, even if the HARQ-ACK codebook configuration and / or HARQ-ACK timing determination is based on the DCI configuration (even if a dynamic (type 2) HARQ-ACK codebook is configured), the device may determine the K0 / K1 value for the HARQ feedback signal transmission for the DCI / PDCCH including SCI according to the predefined rule, regardless of the DCI. On the other hand, in case 2-1 of scenario 2, where the HARQ-ACK feedback signal is transmitted without being combined with the HARQ-ACK codebook, the device may determine the transmission resource of the HARQ feedback signal without determining SLIV.

[0418] As described in alternative 1-1, alternative 1-2, alternative 1-3, and / or alternative 1-4 of scenario 1 (or scenario 2), according to predefined rules, K0 can always be determined to be 0, or K0 can be determined to be a value corresponding to the lowest or highest index in the TDRA table configured by RRC signaling. Alternatively, according to predefined rules, K1 can be determined to be the maximum or minimum value among the K1 values configured by RRC signaling from the BS. Alternatively, if the device reports to the BS the capability information regarding the minimum processing time related to the transmission of HARQ feedback signals, the device can determine K1 based on the predefined rules using the minimum processing time, regardless of the K1 indication in the DCI. Here, the minimum processing time can be based on the values of N1 and / or N2 (or a specific capability report of NCR).

[0419] In other words, the DCI including the SCI can be a new DCI format that does not include fields for the following items: K0, SLIV, K1, and PRI. Alternatively, even if these fields are included in the DCI, if the DCI contains the SCI, the device can determine the values of K0 / K1 according to predefined rules, regardless of the values included in the DCI or the values indicated by the DCI.

[0420] On the other hand, if the SCI is not included in the DCI, the device can determine the transmission resources of the HARQ feedback signal for the DCI / PDCCH based on the K0 / K1 values included in the DCI in the absence of the SCI. For example, if the DCI contains control information for the control link rather than the backhaul link, the device can determine the transmission resources of the HARQ feedback signal for the DCI / PDCCH based on the K0 / K1 values indicated in the DCI rather than the predefined rules. In other words, according to whether the SCI is included in the DCI, the device can determine whether to use the values indicated in the DCI or the predefined rules to determine the values of K1 / K0 for determining the transmission resources of the HARQ feedback signal.

[0421] Alternatively, as described in case 2-2 of scenario 2, the device can transmit a HARQ feedback signal containing HARQ feedback information obtained through codebook combination only for the PDCCH including the SCI.

[0422] Alternatively, the device can determine only K0 based on predefined rules while determining K1 based on the value indicated by the field in the DCI carrying the SCI. For example, when the DCI indicates both K0 and K1, the device can ignore the value indicated for K0 and determine K0 according to predefined rules, but the device can determine K1 based on the value indicated by the DCI (see scenario 1). Alternatively, when the DCI indicates both K0 and K1, the device can ignore the value indicated for K1 and determine K1 according to predefined rules, but the device can determine K0 based on the value indicated by the DCI.

[0423] Among the fields / parameters related to determining the transmission resources of HARQ feedback signals, fields / parameters that do not follow predefined rules can apply the existing indication method explained with reference to Figure 7 the existing indication method explained.

[0424] Next, the device can send a HARQ feedback signal for the PDCCH (S115) on the determined transmission resources (via the backhaul link).

[0425] Figure 12 is a schematic diagram explaining a method for a base station having a control link and a backhaul link formed with a device to perform communication.

[0426] With reference to Figure 12 , the BS can send a PDCCH (S121) containing DCI related to the control of the backhaul link of the device to the device via the control link. Here, the DCI can include the SCI for controlling the backhaul link as described above.

[0427] Next, the BS can receive a HARQ feedback signal for the PDCCH from the device via the backhaul link (S123). As described above, regarding the transmission of the HARQ feedback signal / HARQ information, the BS can indicate the following by DCI to determine the HARQ transmission timing / resources of the HARQ feedback signal (for example, in the case of dynamic type 2 HARQ-ACK): K0, K1, SLIV, PRI, C-DAI, and T-DAI.

[0428] As described above, if the DCI is a DCI (existing DCI format or new DCI format) for carrying an SCI (which is control information for a backhaul link), the BS can expect / predict that the device will determine at least one of the K0 value and the K1 value (and / or SLIV, PRI, C-DAI, and T-DAI) based on predefined rules, regardless of the DCI. Even if the BS sends a DCI that does not include a dedicated field for indicating K0 / K1, the BS can still expect / predict that the device will determine the values of K0 / K1 based on predefined rules. For example, as described in alternative 1-1, alternative 1-2, alternative 1-3, and / or alternative 1-4 of scenario 1, even if the BS configures the device to determine the HARQ-ACK codebook configuration and / or HARQ-ACK timing based on the DCI (e.g., dynamic (type 2) HARQ-ACK codebook configuration), when the BS sends a DCI / PDCCH including an SCI, the BS can expect / predict that the device will send a HARQ feedback signal for the DCI / PDCCH based on the predefined K0 / K1 values. In case 2-1 of scenario 2, where the HARQ-ACK feedback signal is sent without being combined with the HARQ-ACK codebook, the BS can send a DCI to the device that does not include the SLIV field (i.e., a DCI that does not include K0 / K1 / SLIV).

[0429] As described in alternative 1-1, alternative 1-2, alternative 1-3, and / or alternative 1-4 of scenario 1 (or scenario 2), according to the predefined rules, K0 can always be determined to be 0, or K0 can be determined to be a value corresponding to the lowest or highest index in the TDRA table configured by RRC signaling. Alternatively, according to the predefined rules, K1 can be determined to be the maximum or minimum value among the K1 values configured by RRC signaling from the BS. Alternatively, if the device reports to the BS the capability information regarding the minimum processing time related to the transmission of the HARQ feedback signal, the device will determine K1 based on the predefined rules using the minimum processing time, regardless of the K1 indication in the DCI. Here, the minimum processing time can be based on the values of N1 and / or N2 (or a specific capability report of NCR).

[0430] Alternatively, as described in case 2-2 of scenario 2, the BS can receive a HARQ feedback signal containing HARQ feedback information obtained through codebook combination only for the PDCCH carrying the SCI.

[0431] By pre - defining values related to the HARQ feedback timing of the DCI carrying the SCI, the DCI overhead can be minimized by excluding at least one of the fields related to the HARQ feedback for the DCI carrying the SCI. Additionally, among the DCI fields required to determine the transmission timing / resource of the HARQ feedback signal, unnecessary fields (such as K0 / K1) can be determined according to pre - defined rules based on the characteristics of the DCI carrying the SCI (considering that these fields are not used for PDSCH scheduling). For the remaining fields, the existing indication methods can be maintained / reused, thus minimizing the changes to the existing DCI framework.

[0432] Example of a communication system applying the present disclosure

[0433] Although not limited thereto, the various descriptions, functions, processes, proposals, methods, and / or operation flowcharts of the present disclosure disclosed in this document can be applied to various fields that require wireless communication / connection (5G) between devices.

[0434] Hereinafter, it will be illustrated in more detail with reference to the accompanying drawings. In the following drawings / descriptions, unless otherwise specified, the same reference numerals may denote the same or corresponding hardware blocks, software blocks, or functional blocks.

[0435] Figure 13 A communication system to which the present disclosure is applied is illustrated.

[0436] Refer to Figure 13, the communication system 1 applied to the present disclosure includes a wireless device, a base station (BS), and a network. Herein, the wireless device refers to a device that performs communication using a radio access technology (RAT) (e.g., 5G new RAT (NR) or Long-Term Evolution (LTE)), and may be referred to as a communication / radio / 5G device. The wireless device may include (but is not limited to) a robot 100a, vehicles 100b-1 and 100b-2, an extended reality (XR) device 100c, a handheld device 100d, a household appliance 100e, an Internet of Things (IoT) device 100f, and an artificial intelligence (AI) device / server 400. For example, the vehicle may include a vehicle with a wireless communication function, an autonomous driving vehicle, and a vehicle capable of performing communication between vehicles. Herein, the vehicle may include an unmanned aerial vehicle (UAV) (e.g., a drone). The XR device may include an augmented reality (AR) / virtual reality (VR) / mixed reality (MR) device, and may be implemented in the form of a head-mounted device (HMD), a head-up display (HUD) installed in a vehicle, a television, a smartphone, a computer, a wearable device, a household appliance device, a digital sign, a vehicle, a robot, etc. The handheld device may include a smartphone, a smart board, a wearable device (e.g., a smartwatch or smart glasses), and a computer (e.g., a notebook). The household appliance may include a TV, a refrigerator, and a washing machine. The IoT device may include sensors and smart meters. For example, the BS and the network may be implemented as wireless devices, and a specific wireless device 200a may operate as a BS / network node with respect to other wireless devices.

[0437] The wireless devices 100a to 100f may be connected to the network 300 via the BS 200. AI technology may be applied to the wireless devices 100a to 100f, and the wireless devices 100a to 100f may be connected to the AI server 400 via the network 300. The network 300 may be configured using a 3G network, a 4G (e.g., LTE) network, or a 5G (e.g., NR) network. Although the wireless devices 100a to 100f may communicate with each other via the BS 200 / network 300, the wireless devices 100a to 100f may perform direct communication (e.g., sidelink communication) with each other without passing through the BS / network. For example, the vehicles 100b-1 and 100b-2 may perform direct communication (e.g., vehicle-to-vehicle (V2V) / vehicle-to-everything (V2X) communication). The IoT device (e.g., a sensor) may perform direct communication with other IoT devices (e.g., sensors) or other wireless devices 100a to 100f.

[0438] A wireless communication / connection 150a, 150b, or 150c can be established between wireless devices 100a to 100f / BS200 or BS200 / BS200. In this document, the wireless communication / connection can be established through various RATs (e.g., 5G NR) such as uplink / downlink communication 150a, sidelink communication 150b (or D2D communication), or inter-BS communication (e.g., relay, integrated access backhaul (IAB)). The wireless device and the BS / wireless device can send / receive radio signals to / from each other through the wireless communication / connections 150a and 150b. For example, the wireless communication / connections 150a and 150b can send / receive signals through various physical channels. To this end, at least a part of the various configuration information configuring processes for sending / receiving radio signals, various signal processing processes (e.g., channel encoding / decoding, modulation / demodulation, and resource mapping / demapping), and resource allocation processes can be executed based on various proposals of the present disclosure.

[0439] Example of a wireless device applying the present disclosure

[0440] Figure 14 A wireless device applicable to the present disclosure is illustrated.

[0441] Referring to Figure 14 , the first wireless device 100 and the second wireless device 200 can send radio signals through various RATs (e.g., LTE and NR). In this document, {the first wireless device 100 and the second wireless device 200} can correspond to Figure 13 {the wireless device 100x and BS200} and / or {the wireless device 100x and the wireless device 100x}.

[0442] The first wireless device 100 may include one or more processors 102 and one or more memories 104, and may additionally include one or more transceivers 106 and / or one or more antennas 108. The processor 102 may control the memory 104 and / or the transceiver 106, and may be configured to implement the descriptions, functions, processes, proposals, methods, and / or operation flowcharts disclosed in this document. For example, the processor 102 may process the information in the memory 104 to generate first information / signals, and then send radio signals including the first information / signals through the transceiver 106. The processor 102 may receive radio signals including second information / signals through the transceiver 106, and then store the information obtained by processing the second information / signals in the memory 104. The memory 104 may be connected to the processor 102 and may store various information related to the operation of the processor 102. For example, the memory 104 may store software codes including commands for executing part or all of the processes controlled by the processor 102 or for implementing the descriptions, functions, processes, proposals, methods, and / or operation flowcharts disclosed in this document. Herein, the processor 102 and the memory 104 may be part of a communication modem / circuit / chip designed to implement a RAT (e.g., LTE or NR). The transceiver 106 may be connected to the processor 102 and send and / or receive radio signals through one or more antennas 108. Each transceiver 106 may include a transmitter and / or a receiver. The transceiver 106 may be used interchangeably with the radio frequency (RF) unit. In this disclosure, the wireless device may represent a communication modem / circuit / chip.

[0443] For example, the first wireless device 100 or the device may include a processor 102 connected to the RF transceiver 106 and the memory 104. The memory 104 may include at least one program capable of performing operations related to the Figures 9 to 12 embodiments described therein.

[0444] Specifically, the processor 102 may control the RF transceiver 106 to receive a PDCCH including DCI from the BS through a control link; and send a HARQ feedback signal for the PDCCH through a backhaul link. In this case, the transmission resources for the HARQ feedback signal may be determined based on K0 and K1, where K0 represents the time slot interval between the PDCCH and the PDSCH, and K1 represents the interval between the PDSCH and the HARQ feedback signal. Based on the SCI included in the DCI, at least one of K0 and K1 may be determined based on a predefined rule.

[0445] Alternatively, a processing device is provided that is configured to control a device having a control link and a backhaul link formed with a BS having a processor 102 and a memory 104. In this case, the processing device includes: at least one processor; and at least one memory connected to the at least one processor and storing instructions that, when executed by the at least one processor, cause the UE to: receive a PDCCH including DCI from the BS via the control link; and transmit a HARQ feedback signal for the PDCCH via the backhaul link. In this case, the transmission resources for the HARQ feedback signal can be determined based on K0 and K1, where K0 represents the slot interval between the PDCCH and the PDSCH, and K1 represents the interval between the PDSCH and the HARQ feedback signal. Based on the SCI included in the DCI, at least one of K0 and K1 can be determined based on a predefined rule.

[0446] Alternatively, a non-transitory computer-readable storage medium can be configured with instructions recorded thereon for performing the proposed method described with reference to Figures 9 to 12 the description.

[0447] The second wireless device 200 may include one or more processors 202 and one or more memories 204, and may additionally include one or more transceivers 206 and / or one or more antennas 208. The processor 202 may control the memory 204 and / or the transceiver 206 and may be configured to implement the descriptions, functions, processes, proposals, methods, and / or operation flowcharts disclosed in this document. For example, the processor 202 may process the information within the memory 204 to generate third information / signals, and then transmit a radio signal including the third information / signals via the transceiver 206. The processor 202 may receive a radio signal including fourth information / signals via the transceiver 206, and then store the information obtained by processing the fourth information / signals in the memory 204. The memory 204 may be connected to the processor 202 and may store various information related to the operation of the processor 202. For example, the memory 204 may store software codes including commands for performing part or all of the processes controlled by the processor 202 or for performing the descriptions, functions, processes, proposals, methods, and / or operation flowcharts disclosed in this document. Herein, the processor 202 and the memory 204 may be part of a communication modem / circuit / chip designed to implement a RAT (e.g., LTE or NR). The transceiver 206 may be connected to the processor 202 and transmit and / or receive radio signals via one or more antennas 208. Each transceiver 206 may include a transmitter and / or a receiver. The transceiver 206 may be used interchangeably with the RF unit. In the present disclosure, the wireless device may represent a communication modem / circuit / chip.

[0448] In the following, the hardware components of wireless devices 100 and 200 will be described more specifically. One or more protocol layers may be implemented by (but not limited to) one or more processors 102 and 202. For example, one or more processors 102 and 202 may implement one or more layers (such as functional layers such as PHY, MAC, RLC, PDCP, RRC, and SDAP). One or more processors 102 and 202 may generate one or more protocol data units (PDUs) and / or one or more service data units (SDUs) according to the descriptions, functions, processes, proposals, methods, and / or operation flowcharts disclosed in this document. One or more processors 102 and 202 may generate messages, control information, data, or information according to the descriptions, functions, processes, proposals, methods, and / or operation flowcharts disclosed in this document. One or more processors 102 and 202 may generate signals (such as baseband signals) including PDUs, SDUs, messages, control information, data, or information according to the descriptions, functions, processes, proposals, methods, and / or operation flowcharts disclosed in this document, and provide the generated signals to one or more transceivers 106 and 206. One or more processors 102 and 202 may receive signals (such as baseband signals) from one or more transceivers 106 and 206 and obtain PDUs, SDUs, messages, control information, data, or information according to the descriptions, functions, processes, proposals, methods, and / or operation flowcharts disclosed in this document.

[0449] One or more processors 102 and 202 may be referred to as controllers, microcontrollers, microprocessors, or microcomputers. One or more processors 102 and 202 may be implemented by hardware, firmware, software, or a combination thereof. As an example, one or more application-specific integrated circuits (ASICs), one or more digital signal processors (DSPs), one or more digital signal processor devices (DSPDs), one or more programmable logic devices (PLDs), or one or more field-programmable gate arrays (FPGAs) may be included in one or more processors 102 and 202. The descriptions, functions, processes, proposals, methods, and / or operation flowcharts disclosed in this document may be implemented using firmware or software, and the firmware or software may be configured to include modules, processes, or functions. The firmware or software configured to execute the descriptions, functions, processes, proposals, methods, and / or operation flowcharts disclosed in this document may be included in one or more processors 102 and 202 or stored in one or more memories 104 and 204 to be driven by one or more processors 102 and 202. The descriptions, functions, processes, proposals, methods, and / or operation flowcharts disclosed in this document may be implemented using firmware or software in the form of code, commands, and / or command sets.

[0450] One or more memories 104 and 204 may be connected to one or more processors 102 and 202 and store various types of data, signals, messages, information, programs, code, instructions, and / or commands. One or more memories 104 and 204 may be configured by read-only memory (ROM), random access memory (RAM), electrically erasable programmable read-only memory (EPROM), flash memory, hard disk drive, register, cache memory, computer-readable storage medium, and / or combinations thereof. One or more memories 104 and 204 may be located inside and / or outside one or more processors 102 and 202. One or more memories 104 and 204 may be connected to one or more processors 102 and 202 by various techniques such as wired or wireless connections.

[0451] One or more transceivers 106 and 206 may send user data, control information, and / or radio signals / channels mentioned in the methods and / or flowcharts of operations of this document to one or more other devices. One or more transceivers 106 and 206 may receive descriptions, functions, processes, proposals, methods, and / or user data, control information, and / or radio signals / channels mentioned in the flowcharts of operations disclosed in this document from one or more other devices. For example, one or more transceivers 106 and 206 may be connected to one or more processors 102 and 202 and send and receive radio signals. For example, one or more processors 102 and 202 may execute control so that one or more transceivers 106 and 206 may send user data, control information, or wireless signals to one or more other devices. One or more processors 102 and 202 may execute control so that one or more transceivers 106 and 206 may receive user data, control information, or radio signals from one or more other devices. One or more transceivers 106 and 206 may be connected to one or more antennas 108 and 208, and one or more transceivers 106 and 206 may be configured to send and receive user data, control information, and / or radio signals / channels mentioned in the descriptions, functions, processes, proposals, methods, and / or flowcharts of operations disclosed in this document through one or more antennas 108 and 208. In this document, one or more antennas may be multiple physical antennas or multiple logical antennas (e.g., antenna ports). One or more transceivers 106 and 206 may convert the received radio signals / channels, etc. from RF band signals to baseband signals in order to process the received user data, control information, radio signals / channels, etc. using one or more processors 102 and 202. One or more transceivers 106 and 206 may convert the user data, control information, radio signals / channels, etc. processed using one or more processors 102 and 202 from baseband signals to RF band signals. To this end, one or more transceivers 106 and 206 may include (analog) oscillators and / or filters.

[0452] Application example of a wireless device applying the present disclosure

[0453] Figure 15 Another example of a wireless device to which the present disclosure is applied is shown.

[0454] Referring to Figure 15 , the wireless devices 100 and 200 may correspond to Figure 14Wireless devices 100 and 200, and can be configured by various elements, components, units / parts, and / or modules. For example, each of wireless devices 100 and 200 may include a communication unit 110, a control unit 120, a memory unit 130, and additional components 140. The communication unit may include a communication circuit 112 and a transceiver 114. For example, communication circuit 112 may include Figure 14 one or more processors 102 and 202 and / or one or more memories 104 and 204. For example, transceiver 114 may include Figure 14 one or more transceivers 106 and 206 and / or one or more antennas 108 and 208. Control unit 120 is electrically connected to communication unit 110, memory 130, and additional components 140, and controls the overall operation of the wireless device. For example, control unit 120 may control the electrical / mechanical operations of the wireless device based on programs / codes / commands / information stored in memory unit 130. Control unit 120 may send information stored in memory unit 130 to the outside (e.g., other communication devices) via communication unit 110 through a wireless / wired interface, or store information received from the outside (e.g., other communication devices) via communication unit 110 in memory unit 130 through a wireless / wired interface.

[0455] Additional components 140 may be configured differently according to the type of wireless device. For example, additional components 140 may include at least one of a power unit / battery, an input / output (I / O) unit, a drive unit, and a computing unit. The wireless device may be implemented as (but not limited to) a robot ( Figure 13 100a), a vehicle ( Figure 13 100b-1 and 100b-2), an XR device ( Figure 13 100c), a handheld device ( Figure 13 100d), a household appliance ( Figure 13 100e), an IoT device ( Figure 13 100f), a digital broadcast terminal, a holographic device, a public safety device, an MTC device, a medical device, a fintech device (or financial device), a security device, a climate / environment device, an AI server / device ( Figure 13 400), a BS ( Figure 13 200), a network node, etc. The wireless device may be used in a mobile or fixed location according to usage examples / services.

[0456] In Figure 15Among them, various components, assemblies, units / parts, and / or modules in the wireless devices 100 and 200 can all be connected to each other through wired interfaces, or at least a part of them can be wirelessly connected through the communication unit 110. For example, in each of the wireless devices 100 and 200, the control unit 120 and the communication unit 110 can be wired-connected, and the control unit 120 and the first units (e.g., 130 and 140) can be wirelessly connected through the communication unit 110. Each component, assembly, unit / part, and / or module within the wireless devices 100 and 200 may also include one or more elements. For example, the control unit 120 can be configured by a set of one or more processors. As an example, the control unit 120 can be configured by a set of a communication control processor, an application processor, an electronic control unit (ECU), a graphics processing unit, and a memory control processor. In another example, the memory 130 can be configured by a random access memory (RAM), a dynamic RAM (DRAM), a read-only memory (ROM), a flash memory, a volatile memory, a non-volatile memory, and / or a combination thereof.

[0457] Here, the wireless communication technology implemented in the wireless devices (XXX, YYY) in this specification may include, in addition to the narrowband Internet of Things for low-power communication, LTE, NR, and 6G. At this time, for example, the NB-IoT technology can be an example of a low-power wide area network (LPWAN) technology and can be implemented according to standards such as LTE Cat NB1 and / or LTE Cat NB2, and is not limited to the above names. Additionally or alternatively, the wireless communication technology implemented in the wireless devices (XXX, YYY) in this specification can perform communication based on the LTE-M technology. In this case, as an example, the LTE-M technology can be an example of an LPWAN technology and can be called various names such as eMTC (enhanced machine type communication). For example, the LTE-M technology can be implemented according to at least one of various standards such as 1) LTE CAT 0, 2) LTE Cat M1, 3) LTE Cat M2, 4) LTE non-BL (non-bandwidth limited), 5) LTE-MTC, 6) LTE machine type communication, and / or 7) LTE M, and is not limited to the above names. Additionally or alternatively, considering low-power communication, the wireless communication technology implemented in the wireless devices (XXX, YYY) in this specification is at least one of ZigBee, Bluetooth, and low-power wide area network (LPWAN), and is not limited to the above names. As an example, the ZigBee technology can generate a personal area network (PAN) related to small / low-power digital communication based on various standards such as IEEE 802.15.4 and can be called various names.

[0458] The above-described embodiments are embodiments in which the components and features of the present disclosure are combined in a predetermined form. Unless otherwise clearly stated, each component or feature should be regarded as optional. Each component or feature can be implemented in a form that is not combined with other components or features. Additionally, embodiments of the present disclosure can also be constructed by combining some components and / or features. The order of operations described in the embodiments of the present disclosure can be changed. Some configurations or features of one embodiment can be included in other embodiments, or can be replaced with corresponding configurations or features of other embodiments. Obviously, embodiments can be constructed by combining claims that do not have an explicit citation relationship in the claims, or can be constructed by modifying and including them as new claims after filing.

[0459] In this document, embodiments of the present disclosure are mainly described based on the signal transmission / reception relationship between a terminal and a base station. Such a transmission / reception relationship is extended to the signal transmission / reception between a terminal and a repeater or between a base station and a repeater in the same / similar manner. In some cases, specific operations described in this document as being performed by a base station can be performed by its upper node. That is, obviously, various operations performed for communicating with a terminal in a network including multiple network nodes containing a base station can be performed by the base station or by a network node other than the base station. The base station can be replaced with terms such as a fixed station, Node B, eNode B (eNB), access point, etc. Additionally, the terminal can be replaced with terms such as a user equipment (UE), mobile station (MS), mobile subscriber station (MSS).

[0460] In a hardware configuration, embodiments of the present disclosure can be implemented by one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), processors, controllers, microcontrollers, microprocessors, etc.

[0461] In a firmware or software configuration, the method according to embodiments of the present disclosure can be implemented in the form of modules, procedures, functions, etc. The software code can be stored in a storage unit and executed by a processor. The memory is located inside or outside the processor and can send data to and receive data from the processor via various known means.

[0462] As described above, a detailed description of the preferred embodiments of the present disclosure has been given so that those skilled in the art can implement and execute the present disclosure. Although the above has referred to the preferred embodiments of the present disclosure, those skilled in the art will understand that various modifications and changes can be made to the present disclosure within the scope of the present disclosure.

[0463] Industrial Applicability

[0464] The above embodiments of the present disclosure are applicable to various mobile communication systems.

Claims

1. A method for performing communication by a device having a control link and a backhaul link formed with a base station BS in a wireless communication system, the method comprising the steps of: Receiving, via the control link, a physical downlink control channel PDCCH including downlink control information DCI from the BS; and Transmitting a hybrid automatic repeat request HARQ feedback signal for the PDCCH, Wherein, the transmission resource for the HARQ feedback signal is determined based on K0 and K1, where K0 represents the time slot interval between the PDCCH and the physical downlink shared channel PDSCH, and K1 represents the interval between the PDSCH and the HARQ feedback signal, and Wherein, based on the DCI including side control information SCI for the backhaul link, at least one of K0 and K1 is determined based on a predefined rule.

2. The method according to claim 1, wherein Based on the predefined rule, K0 is determined to be a value corresponding to the lowest or highest index in a time domain resource allocation TDRA table configured by radio resource control RRC signaling.

3. The method according to claim 1, wherein Based on the predefined rule, K0 is always determined to be 0.

4. The method according to claim 1, wherein Based on the predefined rule, K1 is determined to be the maximum or minimum value among the K1 values configured by radio resource control RRC signaling from the BS.

5. The method according to claim 1, wherein the method further comprises the following steps: Reporting to the BS capability information regarding the minimum processing time related to the transmission of the HARQ feedback signal, Wherein, the device determines K1 using the minimum processing time based on the predefined rule, regardless of the indication of K1 in the DCI.

6. The method according to claim 1, wherein, The device determines the HARQ feedback transmission resource by further considering a physical uplink control channel PUCCH resource indicator PRI, and Wherein, based on the DCI not including a field for the PRI, the PRI is always determined to be 1, regardless of the control channel element CCE index for receiving the PDCCH.

7. The method according to claim 1, wherein The DCI does not include fields for K0 and start and length indicator value SLIV, a field for K1, and a field for a physical uplink control channel PUCCH resource indicator PRI.

8. The method according to claim 1, wherein The HARQ feedback signal includes HARQ feedback information obtained by codebook combination only for the PDCCH including the SCI.

9. The method according to claim 1, wherein The device is a network control repeater NCR.

10. A non-transitory computer-readable storage medium having recorded thereon instructions for performing the method according to claim 1.

11. A device configured to perform communication based on a control link and a backhaul link formed with a base station BS in a wireless communication system, the device comprising: A radio frequency RF transceiver; And A processor connected to the RF transceiver, Wherein, the processor is configured to control the RF transceiver to: Receive, via the control link, a physical downlink control channel PDCCH including downlink control information DCI from the BS; and Transmit a hybrid automatic repeat request HARQ feedback signal for the PDCCH, Among them, the transmission resource for the HARQ feedback signal is determined based on K0 and K1, where K0 represents the time slot interval between the PDCCH and the physical downlink shared channel PDSCH, and K1 represents the interval between the PDSCH and the HARQ feedback signal, and Among them, based on that the DCI includes side control information SCI for the backhaul link, at least one of K0 and K1 is determined based on a predefined rule.

12. A processing device configured to control a device having a control link and a backhaul link formed with a base station BS in a wireless communication system, the processing device comprising: At least one processor; And At least one memory, the at least one memory being connected to the at least one processor and storing instructions, the instructions, when executed by the at least one processor, cause the device to: Receive, via the control link, a physical downlink control channel PDCCH including downlink control information DCI from the BS; and Transmit a hybrid automatic repeat request HARQ feedback signal for the PDCCH, Among them, the transmission resource for the HARQ feedback signal is determined based on K0 and K1, where K0 represents the time slot interval between the PDCCH and the physical downlink shared channel PDSCH, and K1 represents the interval between the PDSCH and the HARQ feedback signal, and Among them, based on that the DCI includes side control information SCI for the backhaul link, at least one of K0 and K1 is determined based on a predefined rule.

13. A method for a base station BS to perform communication in a wireless communication system via a control link and a backhaul link formed with a device, the method comprising the following steps: Transmit, via the control link, a physical downlink control channel PDCCH including downlink control information DCI to the device; And Receive a hybrid automatic repeat request HARQ feedback signal for the PDCCH, Among them, the reception resource for the HARQ feedback signal is determined based on K0 and K1, where K0 represents the time slot interval between the PDCCH and the physical downlink shared channel PDSCH, and K1 represents the interval between the PDSCH and the HARQ feedback signal, and Among them, based on that the DCI includes side control information SCI for the backhaul link, at least one of K0 and K1 is determined based on a predefined rule.

14. A base station BS configured to perform communication based on a control link and a backhaul link formed with a device in a wireless communication system, the device comprising: A radio frequency RF transceiver; And A processor, the processor being connected to the RF transceiver, Wherein, the processor is configured to control the RF transceiver to: Transmit, via the control link, a physical downlink control channel PDCCH including downlink control information DCI to the device; and Receive a hybrid automatic repeat request HARQ feedback signal for the PDCCH, Among them, the receiving resources for the HARQ feedback signal are determined based on K0 and K1, where K0 represents the slot interval between the PDCCH and the physical downlink shared channel PDSCH, and K1 represents the interval between the PDSCH and the HARQ feedback signal, and Among them, based on that the DCI includes side control information SCI for the backhaul link, at least one of K0 and K1 is determined based on a predefined rule.

Images