Method and device for transmitting signals in wireless communication system

Abstract

The present invention relates to a wireless communication system and, particularly, to a method and a wireless device therefor, the method comprising the steps of: receiving RACH configuration information, the RACH configuration information including RB offset information used to determine an RO start position in a frequency domain; identifying an RO set in a PRACH slot on the basis of the RB offset information, the PRACH slot including an SBFD symbol set and / or a non-SBFD symbol set; and transmitting a PRACH in the RO set, wherein a reference RB to which the RB offset information is applied in the PRACH slot is differently interpreted according to whether the type of symbol in which the RO set is positioned is an SBFD symbol.

Description

Method and device for transmitting signals in a wireless communication system

[0001] The present invention relates to a wireless communication system. Specifically, the present invention relates to a method for transmitting a signal in a wireless communication system and a device utilizing the same.

[0002] Since the commercialization of 4G (4th generation) communication systems, efforts are being made to develop new 5G (5th generation) communication systems to meet the growing demand for wireless data traffic. 5G communication systems are also referred to as "beyond 4G network" communication systems, "post-LTE" systems, or "new radio" (NR) systems. To achieve high data rates, 5G communication systems include systems operating in the ultra-high frequency (mmWave) band above 6 GHz. Furthermore, for coverage purposes, systems operating in frequency bands below 6 GHz are being considered for implementation at base stations and terminals.

[0003] The 3rd Generation Partnership Project (3GPP) NR system improves network spectral efficiency, enabling carriers to offer more data and voice services within a given bandwidth. Therefore, the 3GPP NR system is designed to meet the demands for high-speed data and media transmission in addition to high-capacity voice support. The advantages of the NR system include high throughput, low latency, support for frequency division duplex (FDD) and time division duplex (TDD) on the same platform, an improved end-user experience, and lower operating costs due to its simple architecture.

[0004] For more efficient data processing, dynamic TDD in NR systems can vary the number of orthogonal frequency division multiplexing (OFDM) symbols available for uplink and downlink transmissions depending on the data traffic direction of users in the cell. For example, when a cell's downlink traffic exceeds its uplink traffic, the base station can allocate multiple downlink OFDM symbols to a slot (or subframe). Information about the slot configuration must be transmitted to terminals.

[0005] To mitigate the path loss of radio waves in ultra-high frequency bands and increase the transmission distance of radio waves, beamforming, massive MIMO (massive MIMO), full dimensional MIMO (FD-MIMO), array antenna, analog beamforming, hybrid beamforming that combines analog beamforming and digital beamforming, and large scale antenna technologies are being discussed in 5G communication systems. Additionally, to improve the network of the system, 5G communication systems are developing technologies for advanced small cells, advanced small cells, cloud radio access networks (cloud RAN), ultra-dense networks, device to device communication (D2D), vehicle to everything communication (V2X), wireless backhaul, non-terrestrial network communication (NTN), moving networks, cooperative communication, coordinated multi-points (CoMP), and interference cancellation.In addition, advanced coding modulation (ACM) methods such as hybrid FSK and QAM modulation (FQAM) and sliding window superposition coding (SWSC), as well as advanced access technologies such as filter bank multi-carrier (FBMC), non-orthogonal multiple access (NOMA), and sparse code multiple access (SCMA), are being developed in 5G systems.

[0006] Meanwhile, the Internet is evolving from a human-centric network where humans create and consume information to the Internet of Things (IoT), where information is exchanged and processed between distributed components such as objects. The Internet of Everything (IoE), which combines IoT technologies with big data processing technologies through connections to cloud servers, is also emerging. To implement the IoT, technological elements such as sensing technology, wired and wireless communication and network infrastructure, service interface technology, and security technology are required. Recently, research is being conducted on technologies such as sensor networks, machine-to-machine (M2M) communication, and machine-type communication (MTC) for connecting objects. In the IoT environment, intelligent IT (Internet technology) services can be provided that collect and analyze data generated from connected objects to create new value for human life. IoT can be applied to areas such as smart homes, smart buildings, smart cities, smart or connected cars, smart grids, healthcare, smart appliances, and advanced medical services through the convergence and integration of existing IT (information technology) technologies with various industries.

[0007] Accordingly, various attempts are being made to apply 5G communication systems to IoT networks. For example, technologies such as sensor networks, machine-to-machine (M2M), and machine-type communication (MTC) are being implemented using 5G communication techniques such as beamforming, MIMO, and array antennas. Cloud RAN, a big data processing technology described above, can also be considered an example of the convergence of 5G and IoT technologies. Mobile communication systems have traditionally been developed to provide voice services while ensuring user activity.

[0008] However, mobile communication systems are gradually expanding beyond voice to include data services, and have now evolved to the point where they can provide high-speed data services. However, resource shortages and user demand for high-speed services in existing mobile communication systems are driving the need for more advanced systems.

[0009] The purpose of the present invention is to provide a method for efficiently transmitting signals in a wireless communication system and a device utilizing the same. Specifically, the purpose of the present invention is to provide a method for configuring an RO (RACH occasion) in a wireless communication system and a device utilizing the same. In addition, the purpose of the present invention is to provide a method for transmitting and receiving signals based on the RO and a device utilizing the same.

[0010] In one aspect of the present invention, a terminal configured to operate in a wireless communication system is provided, comprising: a communication module; and a processor controlling the communication module, wherein the processor receives RACH (random access channel) configuration information, wherein the RACH configuration information includes resource block (RB) offset information used to determine a RO (RACH occasion) start position in a frequency domain; identifies an RO set in a PRACH (physical random access channel) slot based on the RB offset information, wherein the PRACH slot includes at least one of a subband non-overlapping full duplex (SBFD) symbol set or a non-SBFD symbol set; and transmits a PRACH within the RO set, wherein the SBFD symbol set includes an uplink (UL) subband in a frequency domain, and a reference RB to which the RB offset information is applied within the PRACH slot is set differently depending on whether a type of a symbol in which the RO set is located is an SBFD symbol.

[0011] In another aspect of the present invention, a base station configured to operate in a wireless communication system is provided, comprising: a communication module; and a processor controlling the communication module, wherein the processor transmits RACH (random access channel) configuration information, wherein the RACH configuration information includes resource block (RB) offset information used to determine a RO (RACH occasion) start position in a frequency domain; and identifies an RO set in a PRACH (physical random access channel) slot based on the RB offset information, wherein the PRACH slot includes at least one of a subband non-overlapping full duplex (SBFD) symbol set or a non-SBFD symbol set; and is configured to receive a PRACH within the RO set, wherein the SBFD symbol set includes an uplink (UL) subband in a frequency domain, and a base station to which the RB offset information is applied within the PRACH slot is set differently depending on whether a type of a symbol in which the RO set is located is an SBFD symbol.

[0012] In another aspect of the present invention, a method used by a terminal in a wireless communication system is provided, comprising: receiving RACH (random access channel) configuration information, wherein the RACH configuration information includes RB (resource block) offset information used to determine a RO (RACH occasion) start position in a frequency domain; identifying an RO set in a PRACH (physical random access channel) slot based on the RB offset information, wherein the PRACH slot includes at least one of a SBFD (subband non-overlapping full duplex) symbol set or a non-SBFD symbol set; and transmitting a PRACH within the RO set, wherein the SBFD symbol set includes an UL (uplink) subband in a frequency domain, and a reference RB to which the RB offset information is applied within the PRACH slot is set differently depending on whether a type of a symbol in which the RO set is located is an SBFD symbol.

[0013] In another aspect of the present invention, a method used by a base station in a wireless communication system is provided, comprising: transmitting RACH (random access channel) configuration information, wherein the RACH configuration information includes RB (resource block) offset information used to determine a RO (RACH occasion) start position in a frequency domain; identifying an RO set in a PRACH (physical random access channel) slot based on the RB offset information, wherein the PRACH slot includes at least one of a SBFD (subband non-overlapping full duplex) symbol set or a non-SBFD symbol set; and receiving a PRACH within the RO set, wherein the SBFD symbol set includes an UL (uplink) subband in a frequency domain, and a reference RB to which the RB offset information is applied within the PRACH slot is set differently depending on whether a type of a symbol in which the RO set is located is an SBFD symbol.

[0014] Preferably, when the RO set is located in the SBFD symbol set, the reference RB may be set to the lowest RB among UL usable RBs on the SBFD symbol set, and when the RO set is located in the non-SBFD symbol set, the reference RB may be set to the lowest RB in the UL BWP (bandwidth part) on the non-SBFD symbol set.

[0015] Preferably, the SBFD symbol set further includes DL (downlink) usable RBs outside the UL subband in the frequency domain, and the UL usable RBs may include RBs within the UL subband.

[0016] Preferably, the RACH configuration information may include Rach-ConfigGeneric information, and the RB offset information may include msg-1-FrequencyStart.

[0017] Preferably, the UL subband can be configured based on a higher layer signal.

[0018] The present invention provides a method for efficiently transmitting signals in a wireless communication system and a device utilizing the same. Furthermore, the present invention provides a method for configuring an RO in a wireless communication system and a device utilizing the same. Furthermore, the present invention provides a method for transmitting and receiving signals based on an RO and a device utilizing the same.

[0019] The effects that can be obtained from the present invention are not limited to the effects mentioned above, and other effects not mentioned can be clearly understood by a person having ordinary skill in the art to which the present invention belongs from the description below.

[0020] Figure 1 shows an example of a radio frame structure used in a wireless communication system.

[0021] Figure 2 shows an example of a downlink (DL) / uplink (UL) slot structure in a wireless communication system.

[0022] Figure 3 is a drawing for explaining a physical channel used in a 3GPP system and a general signal transmission method using the physical channel.

[0023] Figures 4a and 4b illustrate SS / PBCH blocks for initial cell access in a 3GPP NR system.

[0024] Figures 5a and 5b illustrate procedures for transmitting control information and control channels in a 3GPP NR system.

[0025] Figure 6 is a diagram showing a CORESET (control resource set) in which a PDCCH (physical downlink control channel) can be transmitted in a 3GPP NR system.

[0026] FIG. 7 is a diagram illustrating a method for setting a PDCCH search space in a 3GPP NR system.

[0027] Figure 8 is a conceptual diagram explaining carrier aggregation.

[0028] Figure 9 is a diagram for explaining single carrier communication and multi-carrier communication.

[0029] Figure 10 is a diagram illustrating an example in which a cross-carrier scheduling technique is applied.

[0030] Figure 11 is a block diagram showing the configuration of a terminal and a base station according to one embodiment of the present invention.

[0031] Figures 12 and 13 illustrate a method for setting subbands.

[0032] Figure 14 illustrates a RACH (random access channel) procedure.

[0033] Figures 15 and 16 illustrate legacy RACH configuration information.

[0034] Figure 17 illustrates an RO (RACH occasion) within a slot.

[0035] Figures 18 to 20 illustrate a method for configuring an RO according to an example of the present invention.

[0036] Figures 21 to 24 illustrate RO-SSB (synchronization / physical broadcast channel) mapping according to an example of the present invention.

[0037] Figures 25 to 29 illustrate a method for determining a valid RO according to an example of the present invention.

[0038] Figures 30 to 33 illustrate signal transmission and reception according to an example of the present invention.

[0039] The terms used in this specification have been selected from widely used and current terms, taking into account the functions of the present invention. However, these terms may vary depending on the intentions of those skilled in the art, customs, or the emergence of new technologies. Furthermore, in certain cases, the applicant may arbitrarily select terms, in which case their meanings will be described in the description of the relevant invention. Therefore, it should be noted that the terms used in this specification should be interpreted based on their substantive meaning and the overall content of this specification, rather than simply their names.

[0040] Throughout the specification, when a component is said to be "connected" to another component, this includes not only the case where the component is "directly connected," but also the case where the component is "electrically connected" with another component intervening therebetween. Furthermore, when a component is said to "include" a particular component, this does not exclude the other component, but rather allows the inclusion of other components, unless specifically stated otherwise. Furthermore, the terms "more than" or "less than" based on a specific threshold may be appropriately replaced with "more than" or "less than", respectively, depending on the embodiment.

[0041] The following technologies can be used in various wireless access systems, such as CDMA (code division multiple access), FDMA (frequency division multiple access), TDMA (time division multiple access), OFDMA (orthogonal frequency division multiple access), and SC-FDMA (single carrier frequency division multiple access). CDMA can be implemented with radio technologies such as UTRA (Universal Terrestrial Radio Access) or CDMA2000. TDMA can be implemented with radio technologies such as GSM (Global System for Mobile communications) / GPRS (General Packet Radio Service) / EDGE (Enhanced Data Rates for GSM Evolution). OFDMA can be implemented with radio technologies such as IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802-20, and E-UTRA (Evolved UTRA). UTRA is a part of UMTS (Universal Mobile Telecommunications System). 3GPP (3rd Generation Partnership Project) LTE (long term evolution) is a part of E-UMTS (Evolved UMTS) that uses E-UTRA, and LTE-A (Advanced) is an evolved version of 3GPP LTE.3GPP NR (New Radio) is a system designed separately from LTE / LTE-A to support enhanced Mobile Broadband (eMBB), Ultra-Reliable and Low Latency Communication (URLLC), and massive Machine Type Communication (mMTC) services, which are requirements of IMT-2020. For clarity, the following description focuses on 3GPP NR, but the technical concepts of the present invention are not limited thereto.

[0042] Unless otherwise specified herein, a base station may include a gNB (next generation node B) defined in 3GPP NR. In addition, unless otherwise specified, a terminal may include a UE (user equipment). Hereinafter, to facilitate understanding of the description, each content is described separately as an embodiment, but each embodiment may be used in combination with each other. In the present disclosure, the configuration of a terminal may refer to a configuration by a base station. Specifically, the base station may transmit a channel or signal to the terminal to set the values ​​of parameters used in the operation of the terminal or in a wireless communication system.

[0043] Figure 1 shows an example of a radio frame structure used in a wireless communication system.

[0044] Referring to Figure 1, the radio frame (or radio frame) used in the 3GPP NR system is 10ms (Δf max N f / 100) * T c ) can have a length of . In addition, a radio frame consists of 10 equally sized subframes (SF). Here, Δf max =480*10 3 Hz, N f =4096, T c =1 / (Δfref *N f,ref ), Δf ref =15*10 3 Hz, N f,ref =2048. Each of the 10 subframes within a radio frame can be numbered from 0 to 9. Each subframe has a length of 1ms and can be composed of one or more slots depending on the subcarrier spacing. More specifically, the subcarrier spacing that can be used in the 3GPP NR system is 15*2. μ kHz. μ is the subcarrier spacing configuration, and μ can have a value of 0 to 4. That is, 15 kHz, 30 kHz, 60 kHz, 120 kHz, or 240 kHz can be used as the subcarrier spacing. A 1 ms long subframe is 2 μ It can be composed of slots, where the length of each slot is 2 -μ ms. 2 within one subframe μ The slots of each dog are numbered from 0 to 2 μ - Numbers from 1 to 1 can be assigned. Also, slots within a radio frame are numbered from 0 to 10*2. μ - A number up to 1 may be assigned. Time resources may be distinguished by at least one of a radio frame number (also called a radio frame index), a subframe number (also called a subframe index), and a slot number (or slot index).

[0045] Figure 2 illustrates an example of a downlink (DL) / uplink (UL) slot structure in a wireless communication system. In particular, Figure 2 illustrates the structure of a resource grid of a 3GPP NR system.

[0046] There is one resource grid per antenna port. Referring to Fig. 2, a slot includes multiple OFDM (orthogonal frequency division multiplexing) symbols in the time domain and multiple resource blocks (RBs) in the frequency domain. An OFDM symbol also means one symbol period. Unless otherwise specified, an OFDM symbol may be simply referred to as a symbol. One RB includes 12 consecutive subcarriers in the frequency domain. Referring to Fig. 2, a signal transmitted in each slot is N size,μ grid,x * N RB sc N subcarriers and slot symb It can be expressed as a resource grid consisting of OFDM symbols. Here, when it is a downlink resource grid, x = DL, and when it is an uplink resource grid, x = UL. N size,μ grid,x represents the number of resource blocks (RBs) according to the subcarrier spacing configuration factor μ (x is DL or UL), and N slot symb represents the number of OFDM symbols in a slot. N RB sc N is the number of subcarriers that constitute one RB. RB sc =12. Depending on the multiple access method, an OFDM symbol may be referred to as a CP-OFDM (cyclic prefix OFDM) symbol or a DFT-S-OFDM (discrete Fourier transform spread OFDM) symbol.

[0047] The number of OFDM symbols included in one slot may vary depending on the length of the CP (cyclic prefix). For example, in the case of a normal CP, one slot may include 14 OFDM symbols, but in the case of an extended CP, one slot may include 12 OFDM symbols. In a specific embodiment, the extended CP may be used only at a 60 kHz subcarrier interval. In Fig. 2, for convenience of explanation, a case in which one slot consists of 14 OFDM symbols is exemplified, but embodiments of the present invention may be applied in the same manner to slots having a different number of OFDM symbols. Referring to Fig. 2, each OFDM symbol is, in the frequency domain, N size,μ grid,x * N RB sc It contains subcarriers. The types of subcarriers can be divided into data subcarriers for data transmission, reference signal subcarriers for reference signal transmission, and guard bands. The carrier frequency is also called the center frequency (fc).

[0048] One RB is N in the frequency domain. RB sc can be defined by a number of consecutive subcarriers (e.g., 12). For reference, a resource consisting of one OFDM symbol and one subcarrier can be referred to as a resource element (RE) or tone. Therefore, one RB is N slot symb * N RB sc It can be composed of resource elements. Each resource element within the resource grid can be uniquely defined by an index pair (k, l) within one slot. k is from 0 to N in the frequency domain. size,μ grid, x * N RBsc - An index is given from 1, and l is from 0 to N in the time domain. slot symb - It can be an index assigned up to 1.

[0049] For a terminal to receive signals from or transmit signals to a base station, its time / frequency synchronization may need to be aligned with that of the base station. Only when the base station and terminal are synchronized can the terminal determine the time and frequency parameters necessary to accurately demodulate DL signals and transmit UL signals.

[0050] Each symbol of a radio frame operating in time division duplex (TDD) or an unpaired spectrum can be composed of at least one of a downlink symbol (DL symbol), an uplink symbol (UL symbol), or a flexible symbol. A radio frame operating as a downlink carrier in frequency division duplex (FDD) or a paired spectrum can be composed of downlink symbols or flexible symbols, and a radio frame operating as an uplink carrier can be composed of uplink symbols or flexible symbols. Downlink transmission is possible in a downlink symbol but uplink transmission is not possible, and uplink transmission is possible in an uplink symbol but downlink transmission is not possible. A flexible symbol can be determined to be used for downlink or uplink depending on a signal.

[0051] Information about the type of each symbol, i.e., information indicating either a downlink symbol, an uplink symbol, or a flexible symbol, may be configured as a cell-specific (or common) radio resource control (RRC) signal. In addition, information about the type of each symbol may be additionally configured as a UE-specific (or dedicated) RRC signal. The base station uses the cell-specific RRC signal to indicate i) the period of the cell-specific slot configuration, ii) the number of slots containing only downlink symbols from the beginning of the period of the cell-specific slot configuration, iii) the number of downlink symbols from the first symbol of the slot immediately following the slot containing only downlink symbols, iv) the number of slots containing only uplink symbols from the end of the period of the cell-specific slot configuration, and v) the number of uplink symbols from the last symbol of the slot immediately preceding the slot containing only uplink symbols. Here, a symbol that is not composed of either an uplink symbol or a downlink symbol is a flexible symbol.

[0052] When information about the symbol type is configured as a terminal-specific RRC signal, the base station can signal whether the flexible symbol is a downlink symbol or an uplink symbol using a cell-specific RRC signal. At this time, the terminal-specific RRC signal cannot change the downlink symbol or uplink symbol configured as the cell-specific RRC signal to a different symbol type. The terminal-specific RRC signal is configured for each slot, and N of the corresponding slot slot symb Number of downlink symbols in the symbol slot, N slot symbThe number of uplink symbols in the symbol can be signaled. At this time, the downlink symbols of the slot can be configured continuously from the first symbol of the slot to the i-th symbol. In addition, the uplink symbols of the slot can be configured continuously from the j-th symbol of the slot to the last symbol (where, i <j). 슬롯에서 상향링크 심볼과 하향링크 심볼 어느 것으로도 구성되지 않은 심볼은 플랙서블 심볼이다.

[0053] FIG. 3 is a diagram illustrating a physical channel used in a 3GPP system (e.g., NR) and a general signal transmission method using the physical channel.

[0054] When the terminal powers up or enters a new cell, the terminal performs an initial cell search operation (S101). Specifically, the terminal can synchronize with the base station during the initial cell search. To this end, the terminal receives a primary synchronization signal (PSS) and a secondary synchronization signal (SSS) from the base station to synchronize with the base station and obtain information such as a cell index. Thereafter, the terminal can receive a physical broadcast channel from the base station to obtain broadcast information within the cell.

[0055] A terminal that has completed initial cell search can obtain more specific system information than the system information obtained through initial cell search by receiving a physical downlink control channel (PDCCH) and a physical downlink shared channel (PDSCH) according to information carried in the PDCCH (S102). The system information received by the terminal here is cell-common system information for the terminal to operate properly in the physical layer of the RRC (Radio Resource Control, RRC), and is referred to as remaining system information or system information block (SIB) 1.

[0056] When a terminal accesses a base station for the first time or there are no radio resources for signal transmission (when the terminal is in RRC_IDLE mode), the terminal may perform a random access procedure for the base station (steps S103 to S106). First, the terminal transmits a preamble through a physical random access channel (PRACH) (S103) and may receive a response message to the preamble from the base station through a PDCCH and a corresponding PDSCH (S104). When a valid random access response message is received by the terminal, the terminal transmits data, including its identifier, to the base station through a physical uplink shared channel (PUSCH) indicated in an uplink grant transmitted from the base station through the PDCCH (S105). Next, the terminal waits for reception of the PDCCH as an instruction from the base station to resolve collisions. When the terminal successfully receives the PDCCH through its identifier (S106), the random access procedure is terminated. During the random access process, the terminal can obtain terminal-specific system information required for proper operation from the RRC layer to the physical layer. Once the terminal obtains terminal-specific system information from the RRC layer, the terminal enters RRC connected mode (RRC_CONNECTED mode).

[0057] The RRC layer is used to generate and manage messages for control between terminals and the Radio Access Network (RAN). More specifically, the base station and terminals can perform broadcasting of cell system information required for all terminals in the cell, management of delivery of paging messages, mobility management and handover, terminal measurement reporting and control thereof, terminal capability management, and storage management including base station management in the RRC layer. In general, since the update of a signal transmitted in the RRC layer (hereinafter, “RRC signal”) is longer than the transmission / reception cycle (i.e., transmission time interval, TTI) in the physical layer, the RRC signal can be maintained without change for a long period.

[0058] After the procedure described above, the terminal can perform the general uplink / downlink signal transmission procedure of receiving PDCCH / PDSCH (S107) and transmitting physical uplink shared channel (PUSCH) / physical uplink control channel (PUCCH) (S108). In particular, the terminal can receive downlink control information (DCI) through the PDCCH. The DCI can include control information such as resource allocation information for the terminal. In addition, the format of the DCI can vary depending on the purpose of use. The uplink control information (UCI) that the terminal transmits to the base station through the uplink can include downlink / uplink ACK / NACK signals, channel quality indicator (CQI), precoding matrix index (PMI), rank indicator (RI), etc. Here, the CQI, PMI, and RI can be included in channel state information (CSI). In the case of a 3GPP NR system, the terminal can transmit control information such as the HARQ-ACK and CSI described above through PUSCH and / or PUCCH.

[0059] Figures 4a and 4b illustrate SS / PBCH blocks for initial cell access in a 3GPP NR system.

[0060] When a terminal is powered on or attempts to connect to a new cell, it can acquire time and frequency synchronization with the cell and perform an initial cell search process. During the cell search process, the terminal obtains the physical cell identity N of the cell. cell IDcan be detected. To this end, the terminal can synchronize with the base station by receiving synchronization signals, such as a primary synchronization signal (PSS) and a secondary synchronization signal (SSS), from the base station. At this time, the terminal can obtain information such as a cell identifier (ID).

[0061] Referring to Fig. 4a, the synchronization signal (SS) will be described in more detail. The synchronization signal can be divided into PSS and SSS. PSS can be used to obtain time-domain synchronization such as OFDM symbol synchronization and slot synchronization and / or frequency-domain synchronization. SSS can be used to obtain frame synchronization and cell group ID. Referring to Fig. 4a and Table 1, an SS / PBCH block can be composed of 20 consecutive RBs (= 240 subcarriers) in the frequency axis and 4 consecutive OFDM symbols in the time axis. At this time, in the SS / PBCH block, the PSS is transmitted through the 56th to 182nd subcarriers in the first OFDM symbol, and the SSS is transmitted through the 56th to 182nd subcarriers in the third OFDM symbol. Here, the lowest subcarrier index of the SS / PBCH block is numbered from 0. In the first OFDM symbol where PSS is transmitted, the base station does not transmit signals through the remaining subcarriers, i.e., subcarriers 0 to 55 and 183 to 239. Furthermore, in the third OFDM symbol where SSS is transmitted, the base station does not transmit signals through subcarriers 48 to 55 and 183 to 191. The base station transmits the PBCH (physical broadcast channel) through the remaining REs in the SS / PBCH block, excluding the above signals.

[0062] [Correction pursuant to Rule 91 06.03.2025] [Table 1]

[0063] The SS can be grouped into 336 physical-layer cell-identifier groups, each group containing three unique identifiers, such that each physical-layer cell ID is part of only one physical-layer cell-identifier group, for a total of 1008 unique physical-layer cell IDs through a combination of three PSSs and SSSs. Therefore, the physical-layer cell ID N cell ID = 3N (1) ID + N (2) ID An index N in the range 0 to 335 representing a group of physical-layer cell identifiers. (1) ID and an index N from 0 to 2 representing the physical-layer identifier within the physical-layer cell-identifier group. (2) ID can be uniquely defined by. The terminal can detect the PSS to identify one of three unique physical-layer identifiers. In addition, the terminal can detect the SSS to identify one of 336 physical-layer cell IDs associated with the physical-layer identifier. At this time, the sequence d of the PSS PSS (n) is as follows.

[0064]

[0065] Here, And,

[0066] is given as

[0067] Also, the sequence d of SSS SSS (n) is as follows.

[0068]

[0069] Here, And,

[0070] is given as

[0071] A 10ms long radio frame can be divided into two half frames each of 5ms long. Referring to Fig. 4b, the slots in which SS / PBCH blocks are transmitted within each half frame are described. The slots in which SS / PBCH blocks are transmitted can be any one of Cases A, B, C, D, and E. In Case A, the subcarrier spacing is 15kHz, and the starting point of the SS / PBCH block is the {2, 8} + 14*nth symbol. At this time, n can be 0 or 1 for carrier frequencies below 3GHz. In addition, n can be 0, 1, 2, or 3 for carrier frequencies exceeding 3GHz and below 6GHz. In Case B, the subcarrier spacing is 30kHz, and the starting point of the SS / PBCH block is the {4, 8, 16, 20} + 28*nth symbol. At this time, n can be 0 for carrier frequencies below 3GHz. Also, n can be 0, 1 at a carrier frequency exceeding 3 GHz and below 6 GHz. In case C, the subcarrier spacing is 30 kHz, and the starting point of the SS / PBCH block is the {2, 8} + 14*nth symbol. At this time, n can be 0, 1 at a carrier frequency below 3 GHz. Also, n can be 0, 1, 2, 3 at a carrier frequency exceeding 3 GHz and below 6 GHz. In case D, the subcarrier spacing is 120 kHz, and the starting point of the SS / PBCH block is the {4, 8, 16, 20} + 28*nth symbol. At this time, n can be 0, 1, 2, 3, 5, 6, 7, 8, 10, 11, 12, 13, 15, 16, 17, 18 at a carrier frequency above 6 GHz. In Case E, the subcarrier spacing is 240 kHz, and the starting point of the SS / PBCH block is {8, 12, 16, 20, 32, 36, 40, 44} + 56*nth symbol. At this time, n can be 0, 1, 2, 3, 5, 6, 7, or 8 for carrier frequencies above 6 GHz.

[0072] Figures 5a and 5b illustrate a procedure for transmitting control information and a control channel in a 3GPP NR system. Referring to Figure 5a, a base station may add a CRC (cyclic redundancy check) masked (e.g., XOR operation) with a radio network temporary identifier (RNTI) to control information (e.g., downlink control information, DCI) (S202). The base station may scramble the CRC with an RNTI value determined according to the purpose / target of each control information. A common RNTI used by one or more terminals may include at least one of a system information RNTI (SI-RNTI), a paging RNTI (P-RNTI), a random access RNTI (RA-RNTI), and a transmit power control RNTI (TPC-RNTI). In addition, a terminal-specific RNTI may include at least one of a cell temporary RNTI (C-RNTI) and a CS-RNTI. Afterwards, the base station can perform rate matching according to the amount of resource(s) used for PDCCH transmission after performing channel encoding (e.g., polar coding) (S204). Afterwards, the base station can multiplex DCI(s) based on a PDCCH structure based on CCE (control channel element) (S208). In addition, the base station can apply additional processes such as scrambling, modulation (e.g., QPSK), and interleaving (S210) to the multiplexed DCI(s) and then map them to resources to be transmitted. CCE is a basic resource unit for PDCCH, and one CCE can be composed of multiple (e.g., 6) REGs (resource element groups). One REG can be composed of multiple (e.g., 12) REs.The number of CCEs used for a single PDCCH can be defined as an aggregation level. In a 3GPP NR system, aggregation levels of 1, 2, 4, 8, or 16 can be used. Figure 5b is a diagram regarding CCE aggregation levels and PDCCH multiplexing, showing the types of CCE aggregation levels used for a single PDCCH and the CCE(s) transmitted in the control domain accordingly.

[0073] Figure 6 is a diagram showing a CORESET (control resource set) in which a PDCCH (physical downlink control channel) can be transmitted in a 3GPP NR system.

[0074] A CORESET is a time-frequency resource where the PDCCH, a control signal for a terminal, is transmitted. Furthermore, a search space, described below, can be mapped to a single CORESET. Therefore, rather than monitoring the entire frequency band for PDCCH reception, a terminal can monitor the time-frequency domain designated by the CORESET and decode the PDCCH mapped to the CORESET. A base station can configure one or more CORESETs for each cell for the terminal. A CORESET can consist of up to three consecutive symbols along the time axis. Furthermore, a CORESET can be configured in units of six consecutive PRBs along the frequency axis. In the embodiment of FIG. 6, CORESET#1 consists of consecutive PRBs, and CORESET#2 and CORESET#3 consist of non-consecutive PRBs. A CORESET can be located in any symbol within a slot. For example, in the embodiment of FIG. 6, CORESET#1 starts at the first symbol of the slot, CORESET#2 starts at the fifth symbol of the slot, and CORESET#9 starts at the ninth symbol of the slot.

[0075] FIG. 7 is a diagram illustrating a method for setting a PDCCH search space in a 3GPP NR system.

[0076] In order to transmit a PDCCH to a terminal, each CORESET may have at least one search space. In an embodiment of the present invention, the search space is a set of all time-frequency resources (hereinafter, PDCCH candidates) on which the PDCCH of the terminal can be transmitted. The search space may include a common search space that 3GPP NR terminals must commonly search and a terminal-specific or UE-specific search space that a specific terminal must search. In the common search space, a PDCCH that is commonly set for all terminals in a cell belonging to the same base station can be monitored. In addition, a terminal-specific search space may be set for each terminal so that the PDCCH allocated to each terminal can be monitored at different search space locations depending on the terminal. In the case of a terminal-specific search space, the search spaces between terminals may be allocated to partially overlap due to the limited control region to which the PDCCH can be allocated. Monitoring PDCCHs involves blindly decoding PDCCH candidates within the search space. Successful blind decoding is referred to as "successful detection / reception of the PDCCH." Failure to do so is referred to as "non-detection / non-reception of the PDCCH," or "non-successful detection / reception."

[0077] For convenience of explanation, a PDCCH scrambled with a group common (GC) RNTI that one or more terminals already know in order to transmit downlink control information to one or more terminals is referred to as a group common (GC) PDCCH or common PDCCH. In addition, a PDCCH scrambled with a terminal-specific RNTI that a specific terminal already knows in order to transmit uplink scheduling information or downlink scheduling information to a specific terminal is referred to as a terminal-specific PDCCH. The common PDCCH may be included in a common search space, and the terminal-specific PDCCH may be included in either the common search space or the terminal-specific PDCCH.

[0078] The base station can inform each terminal or terminal group of information related to resource allocation of the transmission channel, PCH (paging channel) and DL-SCH (downlink-shared channel) (i.e., DL Grant) or information related to resource allocation of UL-SCH (uplink-shared channel) and HARQ (hybrid automatic repeat request) (i.e., UL Grant) through PDCCH. The base station can transmit PCH transport blocks and DL-SCH transport blocks through PDSCH. The base station can transmit data excluding specific control information or specific service data through PDSCH. In addition, the terminal can receive data excluding specific control information or specific service data through PDSCH.

[0079] The base station can transmit information on the PDCCH, including information about which terminal (one or more terminals) the PDSCH data is transmitted to and how the corresponding terminal should receive and decode the PDSCH data. For example, assume that the DCI transmitted through a specific PDCCH is CRC-masked with an RNTI called "A", and that the DCI indicates that the PDSCH is allocated to a radio resource (e.g., frequency location) called "B", and indicates transmission format information (e.g., transmission block size, modulation method, coding information, etc.) called "C". The terminal monitors the PDCCH using the RNTI information it has. In this case, if there is a terminal that blindly decodes the PDCCH using the "A" RNTI, the terminal receives the PDCCH and, based on the information in the received PDCCH, receives the PDSCH indicated by "B" and "C".

[0080] Table 2 shows an example of a physical uplink control channel (PUCCH) used in a wireless communication system.

[0081] [Correction pursuant to Rule 91 06.03.2025] [Table 2]

[0082] PUCCH can be used to transmit the following uplink control information (UCI):

[0083] - SR (Scheduling Request): Information used to request uplink UL-SCH resources.

[0084] - HARQ-ACK: This is a response to the PDCCH (indicating DL SPS release) and / or a response to a downlink transport block (TB) on the PDSCH. HARQ-ACK indicates whether the information transmitted through the PDCCH or PDSCH was successfully received. The HARQ-ACK response includes positive ACK (simply, ACK), negative ACK (hereinafter, NACK), Discontinuous Transmission (DTX), or NACK / DTX. Here, the term HARQ-ACK is used interchangeably with HARQ-ACK / NACK and ACK / NACK. In general, ACK can be expressed with bit value 1, and NACK can be expressed with bit value 0.

[0085] - CSI (Channel State Information): This is feedback information for the downlink channel. It is generated by the terminal based on the CSI-RS (Reference Signal) transmitted by the base station. MIMO (Multiple Input Multiple Output)-related feedback information includes the RI (Rank Indicator) and PMI (Precoding Matrix Indicator). CSI can be divided into CSI Part 1 and CSI Part 2, depending on the information it represents.

[0086] In 3GPP NR systems, five PUCCH formats can be used to support various service scenarios, channel environments, and frame structures.

[0087] PUCCH format 0 is a format that can transmit 1-bit or 2-bit HARQ-ACK information or SR. PUCCH format 0 can be transmitted through 1 or 2 OFDM symbols in the time axis and 1 PRB in the frequency axis. When PUCCH format 0 is transmitted through two OFDM symbols, the same sequence can be transmitted in different RBs in the two symbols. At this time, the sequence can be a sequence cyclically shifted (CS) from the base sequence used in PUCCH format 0. Through this, the terminal can obtain frequency diversity gain. Specifically, the terminal can receive M bit Beat UCI (M bit = 1 or 2) depending on the cyclic shift (CS) value m cs can be determined. In addition, a base sequence of length 12 is given with a CS value m cs A cyclically shifted sequence based on M can be transmitted by mapping it to 12 REs of 1 OFDM symbol and 1 RB. The number of cyclic shifts available to the terminal is 12, and M bit = 1, 1-bit UCI 0 and 1 can be mapped to two cyclically shifted sequences, each with a cyclic shift value difference of 6. In addition, M bit = 2, 2-bit UCI 00, 01, 11, 10 can be mapped to four cyclically shifted sequences, each with a cyclic shift value difference of 3.

[0088] PUCCH format 1 can carry 1-bit or 2-bit HARQ-ACK information or SR. PUCCH format 1 can be transmitted through consecutive OFDM symbols in the time axis and 1 PRB in the frequency axis. Here, the number of OFDM symbols occupied by PUCCH format 1 can be one of 4 to 14. More specifically, M bit= 1 UCI can be modulated with BPSK. The terminal is M bit =2 UCI can be modulated with QPSK (quadrature phase shift keying). A signal is obtained by multiplying a modulated complex valued symbol d(0) by a sequence of length 12. At this time, the sequence may be a base sequence used in PUCCH format 0. The terminal transmits the obtained signal by spreading it with a time-domain OCC (orthogonal cover code) in the even-numbered OFDM symbols to which PUCCH format 1 is assigned. In PUCCH format 1, the maximum number of different terminals multiplexed into the same RB is determined according to the length of the OCC used. A demodulation reference signal (DMRS) can be mapped by spreading it with the OCC in the odd-numbered OFDM symbols of PUCCH format 1.

[0089] PUCCH format 2 can carry UCI exceeding 2 bits. PUCCH format 2 can be transmitted through 1 or 2 OFDM symbols in the time axis and 1 or multiple RBs in the frequency axis. When PUCCH format 2 is transmitted through 2 OFDM symbols, the same sequence can be transmitted through different RBs through the 2 OFDM symbols. Here, the sequence is a plurality of modulated complex symbols d(0), … , d(M symbol -1) can be. Here, M symbol Silver M bit / 2 can be used. This allows the terminal to obtain frequency diversity gain. More specifically, M bit Beat UCI (M bit >2) is bit-level scrambled, QPSK modulated and mapped to RB(s) of one or two OFDM symbol(s), where the number of RB(s) can be between 1 and 16.

[0090] PUCCH format 3 or PUCCH format 4 can carry UCI exceeding 2 bits. PUCCH format 3 or PUCCH format 4 can be transmitted through consecutive OFDM symbols in the time axis and one PRB in the frequency axis. The number of OFDM symbols occupied by PUCCH format 3 or PUCCH format 4 can be one of 4 to 14. Specifically, the terminal can transmit M bit Beat UCI (M bit >2) is modulated with π / 2-BPSK (Binary Phase Shift Keying) or QPSK to produce complex symbols d(0)~d(M symb -1) can be generated. Here, using π / 2-BPSK, M symb =M bit And, if QPSK is used, M symb =M bit / 2. The terminal may not apply block-wise spreading to PUCCH format 3. However, the terminal may apply block-wise spreading to one RB (i.e., 12 subcarriers) using PreDFT-OCC of length 12 so that PUCCH format 4 can have a multiplexing capacity of 2 or 4. The terminal may transmit the spread signal by transmitting precoding (or DFT-precoding) the spread signal and mapping it to each RE.

[0091] At this time, the number of RBs occupied by PUCCH format 2, PUCCH format 3, or PUCCH format 4 can be determined according to the length of UCI transmitted by the terminal and the maximum code rate. If the terminal uses PUCCH format 2, the terminal can transmit HARQ-ACK information and CSI information together through PUCCH. If the number of RBs that the terminal can transmit is greater than the maximum number of RBs available for PUCCH format 2, PUCCH format 3, or PUCCH format 4, the terminal can transmit only the remaining UCI information without transmitting some UCI information according to the priority of the UCI information.

[0092] PUCCH format 1, PUCCH format 3, or PUCCH format 4 can be configured via RRC signaling to indicate frequency hopping within a slot. When frequency hopping is configured, the index of the RB to be frequency hopped can be configured via RRC signaling. When PUCCH format 1, PUCCH format 3, or PUCCH format 4 is transmitted over N OFDM symbols in the time axis, the first hop can have floor(N / 2) OFDM symbols and the second hop can have ceil(N / 2) OFDM symbols.

[0093] PUCCH format 1, PUCCH format 3, or PUCCH format 4 can be configured to be repeatedly transmitted in multiple slots. In this case, the number K of slots in which the PUCCH is repeatedly transmitted can be configured by an RRC signal. The repeatedly transmitted PUCCH must start from the same OFDM symbol in each slot and have the same length. If any OFDM symbol in the slot in which the UE must transmit the PUCCH is indicated as a DL symbol by an RRC signal, the UE may not transmit the PUCCH in that slot and postpone transmission to the next slot.

[0094] Meanwhile, in the 3GPP NR system, a terminal can perform transmission and reception using a bandwidth that is smaller than or equal to the bandwidth of a carrier (or cell). To this end, the terminal can be configured with a bandwidth part (BWP) consisting of a continuous bandwidth of a portion of the carrier's bandwidth. A terminal operating in TDD or an unpaired spectrum can be configured with up to four DL / UL BWP pairs per carrier (or cell). In addition, the terminal can activate one DL / UL BWP pair. A terminal operating in FDD or a paired spectrum can be configured with up to four DL BWPs per downlink carrier (or cell) and up to four UL BWPs per uplink carrier (or cell). The terminal can activate one DL BWP and one UL BWP per carrier (or cell). A terminal may not receive or transmit on time-frequency resources other than the activated BWP. The activated BWP may be referred to as an active BWP.

[0095] A base station can indicate an activated BWP among the configured BWPs of a terminal through downlink control information (DCI). The BWP indicated through the DCI is activated, and other configured BWP(s) are deactivated. In a carrier (or cell) operating in TDD, the base station can include a bandwidth part indicator (BPI) indicating an activated BWP in the DCI scheduling PDSCH or PUSCH to change the DL / UL BWP pair of the terminal. The terminal can receive the DCI scheduling PDSCH or PUSCH and identify the activated DL / UL BWP pair based on the BPI. In a downlink carrier (or cell) operating in FDD, the base station can include a BPI indicating an activated BWP in the DCI scheduling PDSCH to change the DL BWP of the terminal. For an uplink carrier (or cell) operating in FDD, the base station may include a BPI indicating the BWP to be activated in the DCI scheduling the PUSCH to change the UL BWP of the terminal.

[0096] Figure 8 is a conceptual diagram explaining carrier aggregation.

[0097] Carrier aggregation refers to a method in which a wireless communication system utilizes multiple frequency blocks or (logically speaking) cells composed of uplink resources (or component carriers) and / or downlink resources (or component carriers) as a single large logical frequency band, so that the terminal can utilize a wider frequency band. A single component carrier may also be referred to as a PCell (Primary cell), SCell (Secondary Cell), or PScell ​​(Primary SCell). However, for convenience of explanation, the term "component carrier" will be used hereafter.

[0098] Referring to FIG. 8, as an example of a 3GPP NR system, the entire system bandwidth may include up to 16 component carriers, and each component carrier may have a bandwidth of up to 400 MHz. A component carrier may include one or more physically contiguous subcarriers. Although FIG. 8 illustrates that each component carrier has the same bandwidth, this is merely an example, and each component carrier may have a different bandwidth. In addition, although each component carrier is illustrated as being adjacent to each other on the frequency axis, the drawing is illustrated in a logical concept, and each component carrier may be physically adjacent to each other or may be spaced apart from each other.

[0099] Each component carrier may use a different center frequency. Furthermore, a common center frequency may be used for physically adjacent component carriers. In the embodiment of FIG. 8, assuming that all component carriers are physically adjacent, center frequency A may be used for all component carriers. Furthermore, assuming that each component carrier is not physically adjacent, center frequency A and center frequency B may be used for each component carrier.

[0100] When the overall system bandwidth is expanded by carrier aggregation, the frequency band used for communication with each terminal can be defined in component carrier units. Terminal A can use the entire system bandwidth of 100 MHz and performs communication using all five component carriers. Terminals B1 to B5 can use only a 20 MHz bandwidth and perform communication using one component carrier. Terminals C1 and C2 can use a 40 MHz bandwidth and perform communication using two component carriers each. The two component carriers may or may not be logically / physically adjacent. The embodiment of FIG. 8 illustrates a case where terminal C1 uses two non-adjacent component carriers and terminal C2 uses two adjacent component carriers.

[0101] Figure 9 is a diagram for explaining single-carrier communication and multi-carrier communication. In particular, Figure 9 (a) illustrates the subframe structure of a single carrier, and Figure 9 (b) illustrates the subframe structure of a multi-carrier.

[0102] Referring to (a) of Fig. 9, a typical wireless communication system can perform data transmission or reception through one DL band and one corresponding UL band in the case of FDD mode. In another specific embodiment, the wireless communication system can divide a radio frame into an uplink time unit and a downlink time unit in the time domain in the case of TDD mode, and perform data transmission or reception through the uplink / downlink time units. Referring to (b) of Fig. 9, three 20MHz component carriers (CCs) each in the UL and DL can be aggregated to support a bandwidth of 60MHz. Each CC can be adjacent or non-adjacent in the frequency domain. For convenience, Fig. 9 (b) illustrates a case where the bandwidth of the UL CC and the bandwidth of the DL CC are both equal and symmetrical, but the bandwidth of each CC can be determined independently. In addition, asymmetric carrier aggregation is also possible, where the number of UL CCs and the number of DL CCs are different. A DL / UL CC allocated / configured to a specific terminal through RRC can be called the serving DL / UL CC of the specific terminal.

[0103] A base station can communicate with a terminal by activating some or all of the serving CCs of the terminal or deactivating some CCs. The base station can change the CCs to be activated / deactivated and the number of CCs to be activated / deactivated. When the base station allocates available CCs to the terminal in a cell-specific or terminal-specific manner, at least one of the assigned CCs may not be deactivated unless the CC allocation to the terminal is completely reconfigured or the terminal performs a handover. A CC that is not deactivated for the terminal is called a primary CC (PCC) or PCell (primary cell), and a CC that the base station can freely activate / deactivate is called a secondary CC (SCC) or SCell (secondary cell).

[0104] Meanwhile, 3GPP NR uses the concept of a cell to manage radio resources. A cell is defined as a combination of downlink and uplink resources, i.e., a combination of a DL CC and an UL CC. A cell can consist of only DL resources or a combination of DL and UL resources. When carrier aggregation is supported, the linkage between the carrier frequency of the DL resources (or DL ​​CC) and the carrier frequency of the UL resources (or UL CC) can be indicated by system information. The carrier frequency refers to the center frequency of each cell or CC. The cell corresponding to the PCC is referred to as a PCell, and the cell corresponding to the SCC is referred to as an SCell. The carrier corresponding to the PCell in the downlink is a DL PCC, and the carrier corresponding to the PCell in the uplink is a UL PCC. Similarly, the carrier corresponding to the SCell in the downlink is a DL SCC, and the carrier corresponding to the SCell in the uplink is a UL SCC. Depending on the UE's capabilities, the serving cell(s) may consist of one PCell and zero or more SCells. For UEs in RRC_CONNECTED state but without carrier aggregation configured or supporting carrier aggregation, there is only one serving cell consisting of only PCells.

[0105] As mentioned above, the term "cell" used in carrier aggregation is distinct from the term "cell" which refers to a certain geographic area where communication services are provided by a single base station or a single antenna group. That is, a single component carrier may also be referred to as a scheduling cell, a scheduled cell, a PCell (Primary cell), a SCell (Secondary Cell), or a PScell ​​(Primary SCell). However, in order to distinguish between a cell referring to a certain geographic area and a cell of carrier aggregation, the present invention refers to a cell of carrier aggregation as a CC, and a cell of a geographic area as a cell.

[0106] FIG. 10 is a diagram illustrating an example of a cross-carrier scheduling technique. When cross-carrier scheduling is configured, a control channel transmitted through a first CC can schedule a data channel transmitted through the first or second CC using a carrier indicator field (CIF). The CIF is included in the DCI. In other words, a scheduling cell is configured, and a DL grant / UL grant transmitted in the PDCCH region of the scheduling cell schedules the PDSCH / PUSCH of the scheduled cell. In other words, a search region for multiple component carriers exists in the PDCCH region of the scheduling cell. The PCell is basically a scheduling cell, and a specific SCell can be designated as a scheduling cell by a higher layer.

[0107] In the embodiment of FIG. 10, it is assumed that three DL CCs are merged. Here, DL component carrier #0 is assumed to be a DL PCC (or PCell), and DL component carrier #1 and DL component carrier #2 are assumed to be DL SCCs (or SCells). In addition, it is assumed that the DL PCC is configured as a PDCCH monitoring CC. If cross-carrier scheduling is not configured by UE-specific (or UE-group-specific or cell-specific) upper layer signaling, CIF is disabled, and each DL CC can transmit only a PDCCH that schedules its own PDSCH without a CIF according to the NR PDCCH rule (non-cross-carrier scheduling, self-carrier scheduling). On the other hand, when cross-carrier scheduling is configured by terminal-specific (or terminal-group-specific or cell-specific) upper layer signaling, CIF is enabled, and a specific CC (e.g., DL PCC) can transmit not only the PDCCH scheduling the PDSCH of DL CC A but also the PDCCH scheduling the PDSCH of other CCs using CIF (cross-carrier scheduling). On the other hand, PDCCH is not transmitted in other DL CCs. Therefore, depending on whether cross-carrier scheduling is configured for the terminal, the terminal monitors the PDCCH that does not include CIF to receive a self-carrier scheduled PDSCH, or monitors the PDCCH that includes CIF to receive a cross-carrier scheduled PDSCH.

[0108] Meanwhile, although FIGS. 9 and 10 illustrate the subframe structure of a 3GPP LTE-A system, the same or similar configuration can also be applied to a 3GPP NR system. However, in a 3GPP NR system, the subframes of FIGS. 9 and 10 can be replaced with slots.

[0109] Figure 11 is a block diagram showing the configuration of a terminal and a base station according to one embodiment of the present invention.

[0110] In embodiments of the present invention, a terminal may be implemented as various types of wireless communication devices or computing devices that ensure portability and mobility. The terminal may be referred to as a UE (User Equipment), STA (Station), MS (Mobile Subscriber), etc. In addition, in embodiments of the present invention, a base station may control and manage cells (e.g., macro cells, femto cells, pico cells, etc.) corresponding to a service area, and perform functions such as signal transmission, channel designation, channel monitoring, self-diagnosis, and relay. The base station may be referred to as a gNB (next generation NodeB) or an AP (access point).

[0111] As illustrated, a terminal (100) according to one embodiment of the present invention may include a processor (110), a communication module (120), a memory (130), a user interface unit (140), and a display unit (150).

[0112] First, the processor (110) can execute various commands or programs and process data within the terminal (100). In addition, the processor (110) can control the overall operation of the terminal (100), including each unit, and control data transmission and reception between the units. Here, the processor (110) can be configured to perform operations according to the embodiments described in the present invention. For example, the processor (110) can receive slot configuration information, determine the slot configuration based on the information, and perform communication according to the determined slot configuration.

[0113] Next, the communication module (120) may be an integrated module that performs wireless communication using a wireless communication network and wireless LAN access using a wireless LAN. To this end, the communication module (120) may be equipped with a plurality of network interface cards (NICs) in built-in or external form, such as a cellular communication interface card (121, 122) and an unlicensed band communication interface card (123). Although the communication module (120) is illustrated as an integrated module in the drawing, each network interface card may be independently arranged depending on the circuit configuration or purpose, unlike the drawing.

[0114] The cellular communication interface card (121) can transmit and receive wireless signals with at least one of a base station (200), an external device, and a server using a mobile communication network, and can provide a cellular communication service by a first frequency band based on a command of the processor (110). According to one embodiment, the cellular communication interface card (121) can include at least one NIC module that uses a frequency band lower than 6 GHz. At least one NIC module of the cellular communication interface card (121) can independently perform cellular communication with at least one of the base station (200), an external device, and a server according to a cellular communication standard or protocol of a frequency band lower than 6 GHz supported by the corresponding NIC module.

[0115] The cellular communication interface card (122) may transmit and receive wireless signals with at least one of a base station (200), an external device, and a server using a mobile communication network, and may provide a cellular communication service by a second frequency band based on a command of the processor (110). According to one embodiment, the cellular communication interface card (122) may include at least one NIC module that uses a frequency band of 6 GHz or higher. At least one NIC module of the cellular communication interface card (122) may independently perform cellular communication with at least one of the base station (200), an external device, and a server according to a cellular communication standard or protocol of a frequency band of 6 GHz or higher supported by the corresponding NIC module.

[0116] The unlicensed band communication interface card (123) transmits and receives wireless signals with at least one of a base station (200), an external device, and a server using the third frequency band, which is an unlicensed band, and provides an unlicensed band communication service based on a command of the processor (110). The unlicensed band communication interface card (123) may include at least one NIC module that uses an unlicensed band. For example, the unlicensed band may be a band of 2.4 GHz, 5 GHz, 6 GHz, 7 GHz, or 52.6 GHz or higher. At least one NIC module of the unlicensed band communication interface card (123) may independently or dependently perform wireless communication with at least one of the base station (200), an external device, and a server according to an unlicensed band communication standard or protocol of a frequency band supported by the corresponding NIC module.

[0117] Next, the memory (130) stores a control program used in the terminal (100) and various data corresponding thereto. This control program may include a predetermined program required for the terminal (100) to perform wireless communication with at least one of a base station (200), an external device, and a server.

[0118] Next, the user interface (140) includes various types of input / output means provided in the terminal (100). That is, the user interface (140) can receive user input using various input means, and the processor (110) can control the terminal (100) based on the received user input. In addition, the user interface (140) can perform output based on a command of the processor (110) using various output means.

[0119] Next, the display unit (150) outputs various images on the display screen. The display unit (150) can output various display objects, such as content executed by the processor (110) or a user interface based on the control commands of the processor (110).

[0120] Additionally, a base station (200) according to one embodiment of the present invention may include a processor (210), a communication module (220), and a memory (230).

[0121] First, the processor (210) can execute various commands or programs and process data within the base station (200). In addition, the processor (210) can control the overall operation of the base station (200), including each unit, and control data transmission and reception between the units. Here, the processor (210) can be configured to perform operations according to the embodiments described in the present invention. For example, the processor (210) can signal slot configuration information and perform communication according to the signaled slot configuration.

[0122] Next, the communication module (220) may be an integrated module that performs wireless communication using a wireless communication network and wireless LAN access using a wireless LAN. To this end, the communication module (220) may be equipped with multiple network interface cards, such as cellular communication interface cards (221, 222) and unlicensed band communication interface cards (223), in built-in or external form. Although the communication module (220) is depicted as an integrated module in the drawing, each network interface card may be independently arranged depending on the circuit configuration or purpose, unlike the drawing.

[0123] The cellular communication interface card (221) can transmit and receive wireless signals with at least one of the terminal (100), external device, and server described above using a mobile communication network, and can provide a cellular communication service using a first frequency band based on a command of the processor (210). According to one embodiment, the cellular communication interface card (221) can include at least one NIC module using a frequency band lower than 6 GHz. At least one NIC module of the cellular communication interface card (221) can independently perform cellular communication with at least one of the terminal (100), external device, and server according to a cellular communication standard or protocol of a frequency band lower than 6 GHz supported by the corresponding NIC module.

[0124] The cellular communication interface card (222) may transmit and receive wireless signals with at least one of a terminal (100), an external device, and a server using a mobile communication network, and may provide a cellular communication service using a second frequency band based on a command of the processor (210). According to one embodiment, the cellular communication interface card (222) may include at least one NIC module using a frequency band of 6 GHz or higher. At least one NIC module of the cellular communication interface card (222) may independently perform cellular communication with at least one of the terminal (100), an external device, and a server according to a cellular communication standard or protocol of a frequency band of 6 GHz or higher supported by the corresponding NIC module.

[0125] The unlicensed band communication interface card (223) transmits and receives wireless signals with at least one of a terminal (100), an external device, and a server using the third frequency band, which is an unlicensed band, and provides an unlicensed band communication service based on a command of the processor (210). The unlicensed band communication interface card (223) may include at least one NIC module that uses an unlicensed band. For example, the unlicensed band may be a band of 2.4 GHz, 5 GHz, 6 GHz, 7 GHz, or 52.6 GHz or higher. At least one NIC module of the unlicensed band communication interface card (223) may independently or dependently perform wireless communication with at least one of the terminal (100), an external device, and a server according to an unlicensed band communication standard or protocol of a frequency band supported by the corresponding NIC module.

[0126] The terminal (100) and base station (200) illustrated in FIG. 11 are block diagrams according to one embodiment of the present invention, and the blocks shown separately are logically distinguished elements of the device. Accordingly, the elements of the above-described device may be mounted as one chip or multiple chips depending on the design of the device. In addition, some components of the terminal (100), such as the user interface (140) and the display unit (150), may be selectively provided in the terminal (100). In addition, the user interface (140) and the display unit (150), etc. may be additionally provided in the base station (200) as needed.

[0127] A terminal can receive a slot format configuration from a base station in a TDD or unpaired spectrum system. The slot format may indicate the type of symbols within the slot. The symbol type may be at least one of a downlink symbol (DL symbol), an uplink symbol (UL symbol), or a flexible symbol. The terminal can receive a symbol type configuration for a slot within a radio frame from the base station. A flexible symbol may indicate a symbol that is not composed of a downlink symbol or an uplink symbol.

[0128] The terminal can semi-statically configure information about each symbol type by receiving information about each symbol type within a slot from the base station through a cell-specific (or cell common) RRC (radio resource control) signal. Here, the cell-specific (or cell-common or terminal-common) RRC signal includes tdd-UL-DL-ConfigurationCommon. Alternatively, the terminal can semi-statically configure information about each symbol type by receiving information about each symbol type within a slot through SIB1. In addition, the terminal can semi-statically configure information about each symbol type within a slot from the base station through a UE-specific UE-dedicated RRC signal. The base station can configure / configure each symbol type within a slot for the terminal by using the information about each symbol type within a slot.

[0129] When a terminal receives information about each symbol type within a slot from a base station as a cell-specific RRC signal, the information configured by the cell-specific RRC signal may include at least one of 1) a period of a cell-specific slot configuration, 2) the number of slots consisting of only downlink symbols from the start slot of the period, 3) the number of downlink symbols from the first symbol of the slot immediately following the last slot consisting of only downlink symbols, 4) the number of slots consisting of only uplink symbols from the last slot of the period, 5) the number of uplink symbols immediately preceding the last slot among slots consisting of only uplink symbols (starting from the end of the period and moving forward). Here, a symbol that is not configured as a downlink symbol or an uplink symbol is a flexible symbol. In addition, when a terminal receives information about each symbol type within a slot from a base station as a cell-specific RRC signal, the information about each symbol type may include at most two slot patterns. In this case, each of the two patterns may be applied consecutively to symbols in the time domain. Downlink symbols, uplink symbols, and flexible symbols configured based on cell-specific RRC signals or SIB1 may be referred to as cell-specific downlink symbols, cell-specific uplink symbols, and cell-specific flexible symbols, respectively.

[0130] When a terminal receives information about each symbol type in a slot from a base station as a terminal-specific RRC signal, a cell-specific flexible symbol can be configured as a downlink symbol or an uplink symbol by the terminal-specific RRC signal. Here, the terminal-specific RRC signal includes tdd-UL-DL-ConfigurationDedicated. At this time, the information configured by the terminal-specific RRC signal can include at least one of 1) an index for a slot within a slot configuration period, 2) the number of downlink symbols starting from the first symbol of the slot indicated by the index, and 3) the number of uplink symbols starting from the last symbol of the slot indicated by the index. Here, a symbol that is not configured as a downlink symbol or an uplink symbol is a flexible symbol. In addition, the terminal can be configured so that all symbols in the slot are downlink symbols or all symbols in the slot are configured so that all symbols in the slot are uplink symbols. The downlink symbols, uplink symbols, and flexible symbols configured based on terminal-specific RRC signals may be referred to as terminal-specific downlink symbols, terminal-specific uplink symbols, and terminal-specific flexible symbols, respectively.

[0131] As another method of informing the terminal of slot format information, the base station can transmit slot format information to the terminal through the slot format indicator (SFI) of DCI format 2_0 included in the group common (GC)-PDCCH. The GC-PDCCH can be CRC scrambled with the SFI-RNTI for the terminals receiving the slot format information. Hereinafter, the SFI transmitted through the GC-PDCCH can be described as a dynamic SFI.

[0132] The terminal can receive a dynamic SFI through the GC-PDCCH to be indicated whether the symbols in the slot are downlink symbols, uplink symbols, or flexible symbols, which are cell-specific flexible symbols or terminal-specific flexible symbols. In other words, only the flexible symbols that the terminal has semi-statically configured can be indicated as any of the downlink symbols, uplink symbols, or flexible symbols through the dynamic SFI. The terminal may not expect that the semi-statically configured downlink symbols or uplink symbols will be indicated as a different type of symbol by the dynamic SFI. The terminal can perform blind decoding at every monitoring period set by the base station to receive the GC-PDCCH transmitting the DCI format 2_0 including the dynamic SFI. If the terminal performs blind decoding and successfully receives the GC-PDCCH, the terminal can apply information about the slot format indicated by the dynamic SFI from the slot in which the GC-PDCCH is received.

[0133] A terminal can be configured with a combination of slot formats that can be indicated through a dynamic SFI from a base station. A slot format combination is for each of 1 to 256 slots, and the terminal can be configured with a slot format combination for any one of 1 to 256 slots through a dynamic SFI, and the dynamic SFI can include an index that indicates which slot the slot format combination is applied to. Table 3 is a table showing slot format combinations for each slot (refer to 3GPP TS38.213).

[0134] [Correction pursuant to Rule 91 06.03.2025] [Table 3]

[0135] In Table 3, D represents a downlink symbol, U represents an uplink symbol, and F represents a flexible symbol. As shown in Table 3, up to two DL / UL switchings are allowed within one slot.

[0136] In this specification, the terms "configure," "set," and "instruct" may be used interchangeably. That is, "configure," "set," and "instruct" may have the same meaning, and similarly, "configured," "set," and "instructed" may have the same meaning.

[0137] Subband-based full duplex: Spectrum partitioning

[0138] Figures 12 and 13 illustrate a method for setting subbands and signal transmission.

[0139] In TDD or unpaired spectrum systems, when a terminal is configured or instructed to select a slot format, only limited time-domain resources are allocated as uplink resources, which can lead to reduced uplink coverage, increased latency, and reduced capacity. To address these issues, discussions are underway to divide specific time-domain resources within a cell into multiple subbands in the frequency domain, using them for both downlink reception and uplink transmission.

[0140] Referring to FIG. 12, the terminal can receive TDD configuration information to semi-statically configure a slot format, or receive SFI to dynamically indicate a slot format. Here, the TDD configuration information can include cell-specific (or cell-common) TDD configuration information (e.g., tdd-UL-DL-ConfigurationCommon) or terminal-specific TDD configuration information (e.g., tdd-UL-DL-ConfigurationDedicated). Here, D (or DL) represents downlink, U (or UL) represents uplink, and F represents flexible, and D / F (or DL / F) represents D (or DL) or F. Thereafter, the terminal can receive a subband configuration / indication from the base station to configure multiple subbands in the frequency domain for a specific time domain resource (e.g., at least one slot / symbol) (n2 to n3). The subband configuration / indication information may include information about a set of contiguous RBs constituting a subband (e.g., a start RB, the number of RBs, etc.). Multiple subbands may be subbands of the same or different formats. The subband format may include a downlink (D or DL) subband and an uplink (U or UL) subband. A D (or DL) subband may be composed of one or more downlink RB(s), and a U (or UL) subband may be composed of one or more uplink RB(s). The downlink RB(s) may indicate resources available for downlink reception, and the uplink RB(s) may indicate resources available for uplink transmission.

[0141] Referring to FIG. 13, a terminal may be (dynamically) instructed in the frequency domain of multiple subbands for downlink (D or DL) slots or symbol(s) that are semi-statically configured (e.g., TDD configuration) or dynamically instructed (e.g., SFI) by a base station. In the drawing, the multiple subbands include two D (or DL) subbands and one U (or UL) subband. In this case, resources configured or instructed to receive downlink signals or channels in the same symbol(s) and resources configured or instructed to transmit uplink signals or channels may overlap in the time domain. For example, if downlink reception (e.g., CSI-RS) is scheduled in the D (or DL) subband and uplink transmission (e.g., PUSCH) is scheduled in the U (or UL) subband, they may overlap in at least one symbol (5th to 6th symbol). Meanwhile, when subbands are configured, the base station can perform both downlink transmission and uplink reception in the same subband symbol (full duplex), but a terminal that supports only half duplex can perform only one operation, either downlink reception or uplink transmission, in the same subband symbol. Here, the subband symbol refers to the symbol in which the subband is configured. Therefore, when downlink reception and uplink transmission overlap in the same subband symbol (see the circled part in the drawing), the terminal and the base station can operate as follows.

[0142] 1) When downlink reception and uplink transmission belong to different terminals,

[0143] - Each terminal can perform downlink reception or uplink transmission without limitation.

[0144] - The base station can perform downlink transmission and uplink reception simultaneously.

[0145] 2) When downlink reception and uplink transmission belong to the same terminal,

[0146] - A terminal cannot perform downlink reception and uplink transmission simultaneously. Accordingly, to resolve conflicts between downlink reception and uplink transmission, the terminal's downlink reception and / or uplink transmission may be restricted.

[0147] - A base station can perform downlink transmission and uplink reception simultaneously. However, if downlink reception and / or uplink transmission are restricted at the terminal, the same restrictions may apply to the base station.

[0148] Here, a collision situation may not be limited to a case where the terminal dynamically receives multiple subbands in the frequency domain for a downlink slot or symbol(s) that are semi-statically configured or dynamically indicated by the base station. That is, a collision situation may also include a case where the terminal semi-statically receives multiple subbands in the frequency domain for a downlink slot or symbol(s) that are semi-statically configured or dynamically indicated by the base station.

[0149] Furthermore, a collision situation may not be limited to a case where a terminal is dynamically instructed to multiple subbands in the frequency domain for a flexible slot or symbol(s) that is semi-statically configured or dynamically instructed by the base station. That is, a collision situation may also include a case where a terminal is semi-statically configured to multiple subbands in the frequency domain for a flexible slot or symbol(s) that is semi-statically configured or dynamically instructed by the base station.

[0150] Random Access Channel Procedure (RACH)

[0151] Figure 14 illustrates a random access procedure. Figures 15 and 16 illustrate RACH configuration information. Figure 17 illustrates RACH resources.

[0152] Referring to FIG. 14, a terminal may receive RACH configuration information from a base station (S1402). The RACH configuration information may be received through RACH-ConfigCommon information in an SIB. RACH-ConfigCommon may include rach-ConfigGeneric information. FIGS. 15 and 16 illustrate examples of RACH-ConfigCommon information and rach-ConfigGeneric information used in a legacy NR system. A PRACH slot may be periodically configured per radio frame based on a PRACH Configuration Index in the rach-ConfigGeneric information (see 3GPP TS38.211 V16.9.0 (2022-06), Tables 6.3.3.2-2 to 6.3.3.2-4). Within a PRACH slot, one or more ROs (RACH occasion or PRACH occasion) may be configured in the time domain and one or more ROs may be configured in the frequency domain. The number of symbols and RBs occupied by one RO may be defined differently depending on the PRACH / preamble format. Frequency resource information of RO(s) configured within a PRACH slot may be determined based on msg1-FDM and msg1-FrequencyStart within the rach-ConfigGeneric information. msg1-FDM indicates the number of ROs in the frequency domain. msg1-FrequencyStart indicates the starting position of the RO (e.g., PRB index) in the frequency domain. msg1-FrequencyStart indicates the offset (e.g., number of RBs) to the starting RO based on the minimum RB of the UL BWP (e.g., PRB#0). Figure 17 illustrates an example of multiple ROs configured within a PRACH slot. The drawing illustrates a case where two ROs are configured in the time domain (TDM) and two ROs are configured in the frequency domain (FDM) within a PRACH slot.Figure 17 illustrates a case where a symbol set constituting one RO in the time domain consists of seven symbols. In the frequency domain, the starting position of the RO (e.g., PRB#2) is set based on msg1-FrequencyStart. msg1-FrequencyStart can have a value from 0 to (the number of RBs in the frequency band of the UL BWP - 1).

[0153] Thereafter, the terminal can transmit a PRACH via an RO (S1404). Here, the RO can be selected from a set of ROs within a PRACH slot. Specifically, the RO can be selected from valid RO(s) within the set of ROs within the PRACH slot. For details on valid ROs, refer to the description of FIG. 25 described below. Thereafter, the terminal can receive a random access response (RAR) (S1406).

[0154] Example: Subband-based full duplex and signal / channel transmission and reception

[0155] First, let us define the terms used in the present invention.

[0156] - Subband-based full duplex: This refers to a method of supporting simultaneous transmission and reception operations using subbands within a cell / BWP. It may be referred to as SBFD (sub-band non-overlapping full duplex). Here, a subband refers to a frequency band configured / indicated for SBFD operation within a cell / BWP. One subband may be composed of one contiguous (P)RB set. For example, a UL subband may be composed of a (P)RB set capable of UL transmission (i.e., UL usable RBs). Similarly, a DL subband may be composed of a (P)RB set capable of DL transmission (i.e., DL usable RBs). Examples of subband configurations / formats may be referenced to FIGS. 12 and 13. For example, in case of unpaired spectrum (i.e., TDD cell / BWP), DL and UL subbands may be configured on DL slots / symbols, or DL ​​and UL subbands may be configured on flexible slots / symbols. Here, the DL subband may be explicitly configured on the DL slot / symbol, or may be considered as implicitly set outside of the UL subbands. A slot / symbol in which a subband is configured in the frequency domain for SBFD operation may be referred to as an SBFD slot / symbol. When a subband is configured in a cell / BWP, the cell / BWP may include an SBFD slot / symbol interval in which a TDMed subband is configured in the time domain, and a non-SBFD slot / symbol interval in which no subband is configured.

[0157] - SBFD slot / symbol interval: refers to a time interval in which a subband is configured / indicated on a cell / BWP. For example, an SBFD slot / symbol interval includes a time interval in which a subband (e.g., DL and / or UL subband) is configured / indicated in the frequency domain. Here, the time interval may include slot(s) and / or symbol(s) (or, a symbol set). An SBFD slot / symbol interval may include one or more subbands in the frequency domain. When multiple subbands are configured in an SBFD slot / symbol interval, the subbands are FDMed. In an SBFD slot / symbol interval, multiple subbands (DL subbands or UL subbands) may be configured to not overlap each other in the frequency domain. An SBFD slot / symbol interval may be simply referred to as an SBFD interval.

[0158] - Non-SBFD slot / symbol interval: refers to a time interval in which a subband is not configured / indicated on a cell / BWP. A non-SBFD slot / symbol interval includes a time interval in which a DL or UL subband is not configured / indicated. Here, the time interval may include slot(s) and / or symbol(s) (or, a symbol set). A non-SBFD slot / symbol interval refers to a legacy interval or a normal interval. A non-SBFD slot / symbol interval includes at least one of a DL symbol, a flexible symbol, and a UL symbol depending on the slot format. For example, if a subband is not configured / indicated in a UL BWP, a non-SBFD slot / symbol interval includes a UL slot / symbol. A non-SBFD slot / symbol interval may be simply referred to as a non-SBFD interval.

[0159] - Legacy NR system: This refers to a system that operates in the legacy NR manner because SBFD operation is not supported or configured.

[0160] The problem to be solved in the present invention relates to a case where a terminal is semi-statically configured or dynamically instructed by a base station for a plurality of subbands in the frequency domain for downlink slots or symbol(s) (simply, downlink sections) and / or flexible slots or symbol(s) (simply, flexible sections). According to the method of the existing legacy NR system (see Fig. 25), even if uplink subbands are configured in the downlink section, ROs cannot be configured in the downlink section, or even if ROs are configured, the ROs are considered invalid in the downlink section. In addition, according to the method of the existing legacy NR system (see Fig. 25), when configuring ROs in the flexible section, the validity of the ROs is determined in a limited manner, for example, by considering the gap after a DL symbol or by considering the gap after a symbol allocated for an SS / PBCH block. In this case, when following a legacy NR system, if the terminal configures an uplink subband for a downlink section and / or a flexible section that is semi-statically or dynamically configured by the base station, it may be impossible or restricted to transmit a PRACH preamble by setting an RO within the corresponding uplink subband.

[0161] - How to configure RO in idle / inactive mode or RRC connected mode and how to set RO in the terminal

[0162] The present invention proposes a method for setting RO for a terminal in idle mode, inactive mode, or RRC connected mode when the terminal is semi-statically configured or dynamically instructed to configure multiple subbands in the frequency domain for a downlink section and / or a flexible section semi-statically configured or dynamically instructed by a base station, or when the terminal is semi-statically configured or dynamically instructed to configure an uplink subband.

[0163] In a first embodiment, when a terminal is semi-statically configured or dynamically instructed to have multiple subbands in the frequency domain for a downlink section and / or a flexible section semi-statically configured or dynamically instructed by a base station, or when an uplink subband is semi-statically configured or dynamically instructed, a method of configuring an RO configuration for a terminal supporting subband operation to be the same (common) as the RO configuration for a legacy terminal through upper layer (e.g., RRC) parameters configured in an existing legacy NR system may be considered. Here, a terminal supporting subband operation can support multiple subband operations in the frequency domain. Figures 15 and 16 illustrate upper layer (e.g., RRC) information used to configure an RO in a legacy NR system. Figures 15 and 16 respectively represent Rach-ConfigCommon information and Rach-ConfigGeneric information, and for more details, refer to 3GPP TS 38.331 Rel-16. For convenience, the RRC information of the legacy NR system is referred to as legacy RRC information (e.g., legacy Rach-ConfigCommon, legacy Rach-ConfigGeneric).

[0164] In this case, the RO for a terminal supporting subband operation can be configured using the RO configuration configured in the flexible section or uplink section in the legacy NR system without additional handling. In this case, any RO that fully or partially overlaps the downlink subband configured in the downlink section on the frequency axis may be considered invalid. That is, an RO configured outside the UL subband (i.e., UL usable RBs) in the SBFD symbol may be judged as an invalid RO. However, this may make the configuration of the RO in the uplink subband configured in the downlink section inefficient. To compensate for this, the following measures may be considered.

[0165] As one embodiment, the present invention proposes a method for setting an RO from a starting RB index of an uplink subband for a downlink section and / or a flexible section for which an uplink subband is configured. For example, the starting position of an RO on the frequency axis in a downlink section and / or a flexible section for which an uplink subband is configured can be set to the offset of the lowest PRACH transmission occasion on the frequency (for convenience, msg-1-FrequencyStart_SBFD) as the starting RB index (e.g., lowest RB index, RB#0) to which an uplink subband is allocated, regardless of the setting of msg-1-FrequencyStart configured in the legacy Rach-ConfigGeneric. Here, msg-1-FrequencyStart_SBFD is determined based on legacy RO configuration information. Therefore, in the SBFD slot / symbol, msg-1-FrequencyStart can be interpreted as being replaced with the start RB index of the uplink (U) subband. That is, msg-1-FrequencyStart can be interpreted differently depending on the type of symbol in which the RO is configured. Through this, the corresponding RACH resources can be configured to the maximum extent within the BW of the uplink subband. Additionally, in case a guard band is required in consideration of interference between subbands between the downlink subband and the uplink subband in the frequency domain, at least one PRB spaced apart from the downlink subband can be set as an offset, and the RO can be set starting from the RB index of the uplink subband after the offset.

[0166] FIG. 18 illustrates an example of setting RO from the starting RB index of the uplink (U) subband for a downlink section and / or a flexible section configured with an uplink (U) subband according to the above embodiment. In FIG. 18, when a guard band is required between subbands, at least one PRB spaced apart from the downlink (D) subband may be set as an offset, and the RO may be set starting from the RB index of the U subband after the offset. Meanwhile, the starting position on the frequency axis of the RO configured for a legacy UE, i.e., a terminal that does not recognize the SBFD operation, is configured according to msg-1-FrequencyStart in the legacy Rach-ConfigGeneric. That is, in a flexible section and / or a UL section where a subband is not configured, the RO is set after msg-1-FrequencyStart from the starting position of the UL BWP (e.g., PRB#0). In addition, a method of setting PRACH slots and ROs in a downlink / flexible section on the time axis where the U subband is configured can be used by allowing PRACH slots to be configured based on the start time of configuring the U subband on the time axis. In the drawing, PRACH slots can be configured discontinuously within a radio frame according to RACH configuration information.

[0167] As another embodiment, the present invention provides a method for setting an RO from a start RB index of an uplink subband for a downlink section and / or a flexible section configured with an uplink (U) subband, that is, in a downlink section configured with an uplink subband, the starting position of the RO on the frequency axis is set to the offset of the lowest PRACH transmission opportunity on the frequency (hereinafter, msg-1-FrequencyStart_SBFD) from the start RB index to which the uplink subband is allocated (e.g., the lowest RB index, RB#0), regardless of the setting of msg-1-FrequencyStart configured in the legacy Rach-ConfigGeneric, so that the corresponding RACH resource can be configured to the maximum extent within the BW of the uplink subband. Here, msg-1-FrequencyStart_SBFD is determined based on legacy RO configuration information. Therefore, in the SBFD slot / symbol, msg-1-FrequencyStart can be interpreted as an offset value set based on the start RB index of the U subband. That is, msg-1-FrequencyStart can be interpreted differently depending on the type of symbol in which the RO is configured. Additionally, in case a guard band is required in consideration of interference between subbands between a downlink subband and an uplink subband in the frequency domain, at least one PRB spaced apart from the downlink subband can be set as an offset, and the RO can be set starting from the RB index of the uplink subband after the offset so that RACH resources can be allocated.

[0168] FIG. 19 illustrates an example of setting RO after msg-1-FrequencyStart from the starting RB index of the U subband for a downlink section and / or a flexible section configured with an uplink (U) subband according to the above embodiment. The drawing illustrates a case where msg-1-FrequencyStart = 0. In FIG. 19, when a guard band between subbands is required, at least one PRB spaced apart from the downlink (D) subband may be set as an offset, and the RO may be set starting from the RB index of the U subband after the offset. Meanwhile, the starting position on the frequency axis of the RO configured for a legacy UE, i.e., a terminal that does not recognize the SBFD operation, is configured according to msg-1-FrequencyStart in the legacy Rach-ConfigGeneric. That is, in the flexible section and / or UL section where the subband is not configured, the RO is set after msg-1-FrequencyStart from the start position of the UL BWP (e.g., PRB#0). In addition, a method of setting the PRACH slot and RO in the downlink / flexible section on the time axis where the uplink subband is configured can be used by allowing the PRACH slot to be configured based on the start time point at which the uplink subband is configured on the time axis. In the drawing, the PRACH slot can be configured discontinuously within the radio frame according to the RACH configuration information.

[0169] As another embodiment, the present invention proposes a method to configure RO from the starting RB index of an uplink subband for a downlink section and / or a flexible section in which an uplink subband is configured. For example, the starting position of the RO on the frequency axis in a downlink section and / or a flexible section in which an uplink subband is configured can be configured identically using msg-1-FrequencyStart configured in the legacy Rach-ConfigGeneric. For this purpose, the offset of the minimum PRACH transmission opportunity on the frequency (for convenience, msg-1-FrequencyStart_SBFD) can be restricted to have a value after the starting RB index (e.g., lowest RB index, RB#0) to which the uplink subband is allocated. Therefore, msg-1-FrequencyStart can be interpreted as having the same value regardless of the type of symbol in which the RO is configured.

[0170] FIG. 20 illustrates a method for setting an RO that is configured identically (commonly) for both a UE that does not recognize the SBFD operation and a UE that recognizes the SBFD operation according to the above embodiment. Referring to the drawing, an example is shown in which msg-1-FrequencyStart enables the RO to be set after the starting RB index of the U subband for a downlink section and / or a flexible section configured with an uplink (U) subband. The drawing exemplifies a case in which msg-1-FrequencyStart = the starting RB index of the U subband. In FIG. 19, when a guard band between subbands is required, at least one PRB spaced apart from the downlink (D) subband may be set as an offset, and the RO may be set starting from the RB index of the U subband after the offset. Accordingly, the starting position on the frequency axis of the RO configured for a legacy UE, i.e., a UE that does not recognize the SBFD operation, may also be set after the starting RB index of the U subband. Additionally, a method of setting PRACH slots and ROs in a downlink / flexible section on the time axis where uplink subbands are configured can be used by allowing PRACH slots to be configured based on the start time of uplink subband configuration on the time axis. In the drawing, PRACH slots can be configured discontinuously within a radio frame according to RACH configuration information.

[0171] The RO starting position on the frequency axis according to Fig. 18 is as follows.

[0172] Signallegacy Rach-ConfigGeneric> msg-1-FrequencyStart (hereinafter, offset#1)* common for SBFD / non-SBFD UEsnon-SBFD slot / symbol durationStarting RB (eg, RB#0) of a bandwidth + offset#1SBFD slot / symbol duration (opt#1)Starting RB of U subband(eg, Starting RB of a bandwidth + offset#1, where a value of msg-1-FrequencyStart is reinterpreted as being replaced with the starting RB of UL usable RBs)SBFD slot / symbol duration (opt#2)Starting RB of U subband + offset#2

[0173] * offset#2: Can be set by the base station or set to a pre-determined value to mitigate inter-subband interference.

[0174] The RO starting position on the frequency axis according to Fig. 19 is as follows.

[0175] Signallegacy Rach-ConfigGeneric> msg-1-FrequencyStart (hereinafter, offset#1)* common for SBFD / non-SBFD UEsnon-SBFD slot / symbol durationStarting RB (eg, RB#0) of UL BWP (UL usable RBs) + offset#1SBFD slot / symbol duration (opt#1)Starting RB of U subband + offset#1(eg, msg-1-FrequencyStart is reinterpreted as representing an offset from the starting RB of UL usable RBs)SBFD slot / symbol duration (opt#2)Starting RB of U subband + offset#1 + offset#2

[0176] The RO starting position on the frequency axis according to Fig. 20 is as follows.

[0177] Signallegacy Rach-ConfigGeneric> msg-1-FrequencyStart (hereinafter, offset#1)* common for SBFD / non-SBFD UEsnon-SBFD slot / symbol durationStarting RB of UL BWP (UL usable RBs) + offset#1SBFD slot / symbol duration (opt#1)Starting RB of UL BWP + offset#1(e.g., msg-1-FrequencyStart is restricted by a BS to have a value equal to or larger than the starting RB of UL usable RBs)SBFD slot / symbol duration (opt#2)Starting RB of UL BWP (UL usable RBs) + offset#1(e.g., msg-1-FrequencyStart is restricted by a BS to have a value equal to or larger than a sum of the starting RB of UL usable RBs and a guard band)

[0178] As a second embodiment, when a terminal is semi-statically configured or dynamically instructed to have multiple subbands in the frequency domain for downlink / flexible slots or symbol(s) semi-statically configured or dynamically instructed by a base station, or when an uplink subband is semi-statically configured or dynamically instructed, in addition to Rach-ConfigCommon or Rach-ConfigGeneric configured for RO configuration in flexible / uplink slots or symbol(s) in an existing legacy NR system, a method may be considered of independently configuring Rach-ConfigCommon-r19 or Rach-ConfigGeneric-r19 for a terminal supporting subband operation in the frequency domain to configure RO within the uplink subband. However, the following method may be considered in order for a terminal to receive two independent RO configuration information (e.g., legacy Rach-ConfigCommon and Rach-ConfigCommon-r19) and configure RO.

[0179] First, Legacy Rach-ConfigCommon or Rach-ConfigGeneric can be used for RO configuration in flexible / uplink slots or symbol(s) where uplink subbands are not configured, and Rach-ConfigCommon-r19 or Rach-ConfigGeneric-r19 can be used for RO configuration in downlink / flexible slots or symbol(s) where uplink subbands are configured.

[0180] Second, Legacy Rach-ConfigCommon or Rach-ConfigGeneric is used for RO configuration in uplink slots or symbol(s) that are not affected by the configuration of uplink subbands, and RO configuration in downlink / flexible slots or symbol(s) where uplink subbands are configured can use Rach-ConfigCommon-r19 or Rach-ConfigGeneric-r19.

[0181] Third, Legacy Rach-ConfigCommon or Rach-ConfigGeneric is used for RO configuration in flexible / uplink slot or symbol(s) as in the existing legacy method regardless of the configuration of uplink subbands, and RO configuration in downlink slot or symbol(s) where uplink subbands are configured can use Rach-ConfigCommon-r19 or Rach-ConfigGeneric-r19.

[0182] The problem to be solved in the present invention relates to a case where a terminal semi-statically or dynamically configures or instructs multiple subbands in the frequency domain for downlink / flexible slots or symbol(s) semi-statically or dynamically configured by a base station. According to the method of the existing legacy NR system, even if an uplink subband is configured in a downlink slot or symbol, the terminal cannot configure an RO in the corresponding downlink slot or symbol(s), or even if an RO is configured, the RO in the corresponding downlink slot or symbol(s) is considered invalid. Therefore, the legacy mapping of RO and SS / PBCH block (hereinafter referred to as SSB) in the corresponding downlink slot or symbol(s) becomes invalid. Furthermore, in legacy NR, since the RO configuration in flexible slots or symbols and uplink slots or symbols and the RO configuration in uplink subbands differ in terms of resource allocation in the time and frequency axes, the mapping of RO and SSB indices in uplink subbands needs to be additionally defined. Accordingly, in the present invention, when a terminal is semi-statically configured or dynamically instructed to have multiple subbands in the frequency domain for downlink / flexible slots or symbol(s) semi-statically configured or dynamically instructed by a base station, or when an uplink subband is semi-statically configured or dynamically instructed, a mapping method of RO and SSB index according to a method of setting RO configured for a terminal belonging to idle mode, inactive mode, or RRC connected mode is proposed.

[0183] Figures 21 and 22 illustrate one embodiment of configurations for legacy UEs used in a legacy NR system, showing a specific RO configuration and a mapping method of RO and SSB index. In Figure 22, SSB to PRACH opportunity mapping (N) means that 1 / N PRACH opportunities are mapped to one SSB index. Contention-based preambles per SSB (R) means that R contention-based preambles are associated per SSB index. When N is less than 1, one SSB index is mapped to 1 / N consecutive valid PRACH opportunity(s), and R contention-based preambles having consecutive indices associated with the SSB index per valid PRACH opportunity start from preamble index 0. When N is greater than or equal to 1, R contention-based preambles associated with SSB index n (0<=n<=N-1) per valid PRACH opportunity are started from preamble index n*(total number of preambles) / N.

[0184] FIGS. 23 and 24 illustrate an embodiment of the present invention in which a terminal semi-statically configures or dynamically instructs multiple subbands in the frequency domain for downlink / flexible slots or symbol(s) semi-statically or dynamically configured or instructed by a base station, or in which an uplink subband is semi-statically or dynamically configured, and illustrates a mapping method of an RO and an SSB index according to a method of setting an RO configured on an uplink subband.

[0185] The total bandwidth (BW_new) of preamble transmissions set within an uplink subband and the total bandwidth (BW_legacy) of preamble transmissions on flexible slots or symbols and UL slots or symbols set for legacy UEs in a legacy NR system can be configured differently or independently, as shown in FIG. 23. Accordingly, the present invention proposes a method of mapping RO and SSB indexes within an uplink subband based on the total bandwidth of preamble transmissions set within an uplink subband and the total bandwidth of preamble transmissions for legacy UEs.

[0186] The total bandwidth of preamble transmissions for legacy UEs may occupy a BW larger than the total bandwidth of preamble transmissions configured within the uplink subband to perform RO configuration for multiple UEs within the cell. Therefore, the mapping method of RO and SSB indices according to the embodiments below may be used using a scaling factor.

[0187] As one example, the scaling factor (K) = floor(BW_legacy / BW_new), where floor(x) is a natural number less than x.

[0188] As another example, the scaling factor (K) = floor(BW_legacy / BW_new), where floor(x) is a natural number less than x, and K can be limited to values ​​that are powers of 2. That is, if the value is between 1<=floor(x)<2, it can be set to 1, if the value is between 2<=floor(x)<4, it can be set to 2, if the value is between 4<=floor(x)<8, it can be set to 4, and if the value is between 8<=floor(x)<16, it can be set to 8.

[0189] In another embodiment, the scaling factor (K) can be set as a ratio of the BW size for the uplink subband and the UL BWP size. Scaling factor (K) = floor(UL_BWP size / BW size for UL subband), where floor(x) is a natural number smaller than x.

[0190] As another example, the scaling factor (K) = floor(UL_BWP size / BW size for UL subband), where floor(x) is a natural number smaller than x, and K can be set to be limited to a value of an exponentiation of 2. That is, if the value is between 1<=floor(x)<2, it can be set to 1, if the value is between 2<=floor(x)<4, it can be set to 2, if the value is between 4<=floor(x)<8, it can be set to 4, and if the value is between 8<=floor(x)<16, it can be set to 8.

[0191] Another example would be to fix the scaling factor (K) to a specific value or configure it to the terminal according to the configuration.

[0192] In another embodiment, the scaling factor (K) may be fixed to a specific value or configured to be configured to the terminal according to the configuration, and K may be fixed or configured to be limited to values ​​that are powers of 2.

[0193] As an example of the present invention, in FIG. 24, actual SSB to PRACH opportunity mapping (N') for mapping between valid RO and actual SSB within an uplink subband means that 1 / N' PRACH opportunities are mapped to one SSB index. N' can be set to N'=N*K according to the parameter N and the scaling factor K value set in the legacy NR system. In addition, contention-based preambles per SSB (R') set within an uplink subband means that R' contention-based preambles are linked per SSB index, and can be set to R'=R / K ​​according to the parameter R and the scaling factor K value set in the legacy NR system. In addition, the BW occupied by the PRACH opportunity in the frequency domain within the uplink subband can also be set to M'=M / K according to the msg-1 FDM (M) and the scaling factor K value set in the legacy NR. Therefore, mapping between valid RO and actual SSB within an uplink subband can be performed using the RO configuration and parameters for RO and SSB mapping set in the existing legacy NR system.

[0194] FIG. 24 shows a mapping method between RO and SSB index according to a setting method of RO configured on an uplink subband when a terminal is semi-statically configured or dynamically instructed in the frequency domain for a downlink / flexible slot or symbol(s) semi-statically configured or dynamically instructed by a base station by applying a scaling factor K of 2, or when an uplink subband is semi-statically configured or dynamically instructed.

[0195] As another example, a method of applying a scaling factor to only at least one value among N', R', and M' may also be considered.

[0196] The problem to be solved in the present invention is what happens when a signal or channel that a terminal is configured or instructed to receive collides with an RO in the same symbol. The RO is configured within a PRACH slot. The PRACH slot is periodically configured in units of radio frames based on the PRACH Configuration Index, which is higher layer (e.g., RRC) information (see 3GPP TS38.211 V16.9.0 (2022-06), Tables 6.3.3.2-2 to 6.3.3.2-4). Figure 17 illustrates multiple ROs configured within a PRACH slot.

[0197] Whether an RO is valid can be determined based on the slot format configuration of the PRACH slot. The UE can perform uplink transmission (e.g., PRACH) or downlink reception (e.g., PDSCH, CSI-RS) based on whether the RO is valid. Specifically, the UE can perform PRACH transmission in a valid RO. In addition, the UE can skip downlink reception if a valid RO (including gap symbols) and downlink reception (e.g., PDSCH reception, CSI-RS reception) overlap in the time domain. On the other hand, if the RO is invalid, the UE cannot perform PRACH transmission in the corresponding RO. In addition, even if the RO (including gap symbols) and downlink reception overlap in the time domain, the UE can perform downlink reception normally if the RO is invalid. In the existing NR system, the UE can determine a valid RO in TDD or unpaired spectrum as follows. Specifically, a valid RO can be determined as follows depending on whether the terminal is configured with or without tdd-UL-DL-ConfigurationCommon, which is information about the symbol type. tdd-UL-DL-ConfigurationCommon can be received via cell-specific (or cell-common) RRC signaling or SIB1 (system information block 1).

[0198] - If the terminal does not receive tdd-UL-DL-ConfigurationCommon:

[0199] An RO within a PRACH slot does not precede an SS / PBCH block within the same PRACH slot in the time domain and is at least N symbols after the last SS / PBCH block received. gap If the RO starts after the symbol, the RO may be valid. Here, the last SS / PBCH block received symbol means the last received symbol of the last SS / PBCH block before the RO.

[0200] - When the terminal receives tdd-UL-DL-ConfigurationCommon (Fig. 25):

[0201] An RO within a PRACH slot is valid if it is on the UL symbol(s). In addition, an RO within a PRACH slot is valid if it does not precede an SS / PBCH block within the same PRACH slot in the time domain and is at least N blocks after the last DL symbol. gap symbol (Fig. 25(a)) and at least N after the last SS / PBCH block received symbol. gap If the RO starts after a symbol (Fig. 25(b)), the RO may be valid. Here, the last DL symbol means the last DL symbol before the RO in the DL symbol set configured by tdd-UL-DL-ConfigurationCommon. In the figure, the D symbol means a cell-common (or cell-specific) DL symbol, the F symbol means a cell-common (or cell-specific) flexible symbol, and the U symbol means a cell-common (or cell-specific) UL symbol.

[0202] Table 7 shows N gap For example, if the PRACH preamble format is B4, N gap =0 may be.

[0203] Preamble SCSN gap1.25 kHz or 5 kHz015 kHz or 30 kHz or 60 kHz or 120 kHz2

[0204] Meanwhile, according to the disclosure of the present specification, a terminal can be semi-statically configured or dynamically instructed by a base station for a plurality of subbands in the frequency domain for a downlink / flexible slot or symbol(s) that are semi-statically configured or dynamically instructed. Here, the plurality of subbands include at least one UL subband, and as another example, at least one DL subband and at least one UL subband. In this case, in addition to the above method, according to an example of the present invention, the terminal can determine a valid RO in the corresponding slot or symbol(s) as follows.

[0205] - If the terminal does not receive tdd-UL-DL-ConfigurationCommon:

[0206] The RO within a PRACH slot is within an uplink subband, and the RO does not precede an SS / PBCH block within the same PRACH slot in the time domain, and at least N SS / PBCH blocks have been received since the last SS / PBCH block symbol. gap If the RO starts after the symbol, the RO may be valid. Here, the last SS / PBCH block received symbol means the last received symbol of the last SS / PBCH block before the RO.

[0207] - When the terminal receives tdd-UL-DL-ConfigurationCommon (Figs. 26-29):

[0208] If the RO in the PRACH slot is on the UL symbol(s), the RO is valid (Fig. 26). In addition, if the RO in the PRACH slot is in the UL subband (Fig. 26), and the RO does not precede the SS / PBCH block in the same PRACH slot in the time domain and is at least N after the last DL symbol, gapStarting after the symbol (Figs. 27-28) and at least N after the last SS / PBCH block received symbol. gap If it starts after the symbol (Fig. 29), the corresponding RO may be valid. Since UL transmission is allowed in the UL subband, the last DL symbol is limited to a DL symbol for which a UL subband is not configured or indicated (i.e., a non-subband symbol). That is, a subband symbol is not included in the last DL symbol. Referring to Figs. 27 and 28, the last DL symbol means the last DL symbol before the corresponding RO in the DL symbol set configured by tdd-UL-DL-ConfigurationCommon, excluding the symbol(s) for which a UL subband is configured (the last symbol of slot #p-1, the last symbol of slot #m-1).

[0209] In Figures 26 to 29, m, p, and q represent slot indices. m, p, and q are defined according to the PRACH slot configuration and may be configured continuously or discontinuously.

[0210] A terminal can perform UL transmission or DL ​​reception based on a valid RO (or based on whether the RO is valid). For example, the terminal can perform PRACH transmission in a valid RO. In addition, if a valid RO (including a gap symbol) and downlink reception (e.g., PDSCH reception) overlap in the time domain, the terminal may be restricted from either PRACH transmission or DL ​​reception according to the disclosure of the present invention. This is described below with reference to FIGS. 20 to 23. Meanwhile, the terminal cannot perform PRACH transmission in an invalid RO. In addition, the downlink reception of the terminal is not restricted by an invalid RO.

[0211] A terminal may be semi-statically configured or dynamically instructed to receive multiple subbands in the frequency domain for a downlink / flexible slot or symbol(s) that are semi-statically configured or dynamically instructed by a base station. In this case, a resource configured or instructed to receive a DL signal / channel and a valid RO may overlap in the same symbol(s). A terminal that supports only half duplex can only perform one of DL reception or UL transmission in the same symbol, and the terminal may perform (i) a valid RO and (ii) N prior to the valid RO. gap A DL signal / channel (e.g., PDCCH, PDSCH, or CSI-RS) may not be received (e.g., reception may be skipped) in a symbol. On the other hand, if the RO overlapping with the DL signal / channel is invalid, the DL signal / channel may be received normally.

[0212] For example, referring to FIG. 30, the terminal has (i) a valid RO and (ii) N before the valid RO. gap The UE may be configured or instructed to receive PDSCH, including symbols that overlap with the six symbols corresponding to the symbol. In this case, in order to protect the PRACH transmission in the valid RO, the UE may not receive the PDSCH. On the other hand, if there is no actual PRACH transmission in the valid RO, the UE may not receive the PDSCH, which may reduce the downlink coverage by not receiving the PDSCH even though the resources configured or instructed to receive the PDSCH in the corresponding slot are available. Hereinafter, the UE operation to solve this is proposed as follows. In the following, the valid RO is N gap may contain symbols. That is, a valid RO is {N gap It can mean {symbol + RO}. N gap Symbols can be found in Table 4.

[0213] 1) PDSCH (or SPS PDSCH) vs valid RO (Figs. 30-33)

[0214] A terminal may be configured or instructed to configure multiple subbands in the frequency domain for a downlink / flexible slot or symbol(s) that are semi-statically configured or dynamically instructed. In addition, the terminal may be instructed to receive a PDSCH via a DCI format (e.g., DCI format 1_0, 1_1, or 1_2) for DL ​​scheduling in the corresponding slot or symbol(s) (i.e., subband slot / symbol). In addition, the terminal may be configured to receive a semi-persistent scheduling (SPS) PDSCH via a higher layer (e.g., RRC) in the corresponding slot or symbol(s) (i.e., subband slot / symbol). If a PDSCH (or SPS PDSCH) and a valid RO overlap in the same symbol in the corresponding slot or symbol(s), the terminal operation is as follows.

[0215] According to the first embodiment, (a) when there is no actual PRACH transmission, a PDSCH (or SPS PDSCH) may be received, and (b) when there is an actual PRACH transmission, a PRACH may be transmitted but a PDSCH may not be received. The first embodiment can prevent a reduction in downlink coverage by receiving a PDSCH (or SPS PDSCH) at least when there is no actual PRACH transmission to solve the above problem.

[0216] According to the second embodiment, (a) when there is no actual PRACH transmission, the PDSCH (or SPS PDSCH) can be received, and (b) when there is an actual PRACH transmission, the PRACH can be transmitted and the PDSCH (or SPS PDSCH) can be received by rate-matching. For example, referring to FIG. 30, the PDSCH (or SPS PDSCH) is instructed to be received in 14 symbols * 20 RBs, the valid ROs are determined as 6 symbols * 6 RBs, and the resources instructed to receive the PDSCH (or SPS PDSCH) can include all of the valid ROs. In this case, the UE can rate-match 6 symbols * 6 RBs that overlap with the valid ROs among the 14 symbols * 20 RBs instructed for PDSCH (or SPS PDSCH) reception to receive the PDSCH (or SPS PDSCH), and transmit the PRACH in the valid ROs. In the second embodiment, even if actual PRACH transmissions occur in overlapping symbols, the terminal can rate-match and receive the PDSCH (or SPS PDSCH) on resources available for downlink reception. Therefore, a reduction in downlink coverage can be prevented.

[0217] The above first and second embodiments may only be applied to PRACH transmissions configured / initiated from a higher layer (e.g., Medium Access Control MAC). That is, a terminal may not expect to detect a DCI indicating to receive a PDSCH (or SPS PDSCH) and to detect a DCI indicating to transmit a PRACH in the same symbol.

[0218] Referring to FIG. 31, a terminal may be configured or instructed to receive PDSCH from a base station in eight symbols, and may determine six symbols as valid ROs. At this time, valid ROs and PDSCH reception do not overlap in the frequency domain, but may overlap in the time domain (i.e., two symbols). In this case, the terminal may operate differently depending on whether PDSCH reception is configured by a higher layer (e.g., Radio Resource Control, RRC) or instructed by DCI. Here, PDSCH reception configured by a higher layer includes SPS PDSCH reception.

[0219] According to one embodiment, when PDSCH reception is indicated through a DCI format for DL ​​scheduling (e.g., DCI format 1_0, 1_1, or 1_2), the UE may receive the PDSCH (i.e., prioritize PDSCH reception). Referring to FIG. 32, the UE may be instructed to receive the PDSCH in 8 symbols within a downlink subband, and a valid RO may be determined to be 6 symbols. In this case, the UE may receive the PDSCH in the 8 symbols indicated by the DCI, and may not transmit the PRACH in the valid RO. This means that at least when the UE is instructed to receive downlink reception from the base station through DCI, the UE may determine that downlink reception is prioritized for downlink coverage and that PRACH transmission will not be performed. Meanwhile, unlike the UE that supports a half-duplex communication mode on a subband, the base station supports a full-duplex communication mode. Accordingly, as in FIG. 32, even if a PRACH transmission of a terminal in a valid RO within a subband is restricted by the PDSCH reception of the terminal, a base station supporting full duplex operation can receive a PRACH from another terminal while transmitting a PDSCH to the terminal in the valid RO.

[0220] According to another embodiment, when a terminal is set to receive PDSCH from a higher layer (e.g., RRC), the terminal can rate-match and receive PDSCH and perform PRACH transmission in a valid RO. For example, the terminal may set RxTxSwitchingGap, i.e., the gap (N) between downlink reception and uplink transmission, differently depending on the symbol overlapping with the valid RO and the SCS (subcarrier spacing). gap,Rx-Tx ), and / or the gap between uplink transmission and downlink reception (N gap,Tx-Rx ) can be received by rate matching the PDSCH in symbols other than the symbols corresponding to N. Here, N gap,Rx-Tx and N gap,Tx-Rx The values ​​of can be defined independently or as the same value. For convenience, the switching gap is N gap It is generally referred to as N gap Silver N gap,Rx-Tx and / or N gap,Tx-Rx Referring to FIG. 33, the terminal is configured by the upper layer (e.g., RRC) to receive PDSCH in 8 symbols within the downlink subband, and the valid RO can be determined as 6 symbols. In this case, the terminal may receive 2 symbols overlapping with the valid RO and N symbols prior to the valid RO for PDSCH reception. gap =2 (i.e. N gap,Rx-Tx =2, but is not limited thereto) can receive a PDSCH with a length of 4 symbols by rate-matching the PDSCH for the symbol. In addition, the terminal can transmit the PRACH even in a valid RO. This is a method that can prevent a decrease in downlink coverage by rate-matching and receiving the PDSCH at least in resources where downlink reception is possible, and also enables PRACH transmission when the terminal wants to transmit in the RO.

[0221] 2) CSI-RS vs valid RO

[0222] A terminal may be configured or instructed to configure multiple subbands in the frequency domain for a downlink / flexible slot or symbol(s) that are either statically configured or dynamically instructed. Furthermore, the terminal may be instructed to receive a CSI-RS via a DCI format (e.g., DCI format 1_0, 1_1, or 1_2) for DL ​​scheduling in the corresponding slot or symbol(s) (i.e., subband slots / symbols). If a CSI-RS and a valid RO overlap in the same symbol in the corresponding slot or symbol(s), the terminal operates as follows.

[0223] According to the first embodiment, (a) when there is no actual PRACH transmission, a CSI-RS may be received, and (b) when there is an actual PRACH transmission, a PRACH may be transmitted but a CSI-RS may not be received. The first embodiment can prevent a reduction in downlink coverage by receiving a CSI-RS at least when there is no actual PRACH transmission to solve the above problem.

[0224] The above first embodiment can be applied only when CSI-RS reception is indicated in DCI and PRACH transmission is configured from a higher layer (e.g., MAC). That is, the terminal may not expect to receive CSI-RS and transmit PRACH in the same symbol from the higher layer.

[0225] 3) CORESET vs. valid RO

[0226] A terminal may configure or be instructed to configure multiple subbands in the frequency domain for a statically configured or dynamically instructed downlink / flexible slot or symbol(s). Furthermore, the terminal may be configured with a CORESET to monitor the PDCCH in the corresponding slot or symbol(s) (i.e., subband slot / symbol). If the CORESET and the valid RO overlap in the same symbol in the corresponding slot or symbol(s), the terminal will operate as follows.

[0227] According to the first embodiment, (a) if there is no actual PRACH transmission, the PDCCH may be monitored, and (b) if there is an actual PRACH transmission, the PRACH may be transmitted and the PDCCH may not be monitored. The first embodiment can prevent downlink coverage reduction by monitoring the PDCCH at least when there is no actual PRACH transmission to address the above problem. Furthermore, since the PDCCH includes control information, such as resource allocation for a terminal, it can be prioritized.

[0228] The above first embodiment is applicable only when PRACH transmission is configured from a higher layer (e.g., MAC). That is, if a terminal is instructed to transmit a PRACH via DCI in a symbol in which a CORESET is configured, the terminal may not monitor the PDCCH regardless of whether the PRACH is actually transmitted in that symbol.

[0229] The collision situation between a valid RO and a CORESET, PDSCH, or CSI-RS described above may not apply when a UE transmits a PRACH for cell initial access (i.e., prior to RRC connection). That is, a UE prior to RRC connection may not monitor the PDCCH or receive the PDSCH or CSI-RS in the aforementioned collision situation. For example, a UE prior to RRC connection may perform operations according to the legacy NR system.

[0230] Although the methods and systems of the present invention have been described with respect to specific embodiments, some or all of their components or operations may be implemented using a computing system having a general-purpose hardware architecture.

[0231] The foregoing description of the present invention is for illustrative purposes only, and those skilled in the art will readily appreciate that the present invention can be readily modified into other specific forms without altering the technical spirit or essential characteristics of the present invention. Therefore, the embodiments described above should be understood as illustrative in all respects and not restrictive. For example, each component described as a single entity may be implemented in a distributed manner, and similarly, components described as distributed may be implemented in a combined manner.

[0232] The scope of the present invention is indicated by the claims described below rather than the detailed description above, and all changes or modifications derived from the meaning and scope of the claims and their equivalent concepts should be interpreted as being included in the scope of the present invention.

Claims

1. In a terminal configured to operate in a wireless communication system, Communication module; and including a processor that controls the above communication module, The above processor, Receive RACH (random access channel) configuration information, wherein the RACH configuration information includes RB (resource block) offset information used to determine a RO (RACH occasion) start position in a frequency domain; Based on the RB offset information, an RO set is identified in a PRACH (physical random access channel) slot, wherein the PRACH slot includes at least one of a subband non-overlapping full duplex (SBFD) symbol set or a non-SBFD symbol set; and configured to transmit PRACH within the above RO set, The above SBFD symbol set includes an UL (uplink) subband in the frequency domain, A terminal in which the reference RB to which the RB offset information is applied within the PRACH slot is set differently depending on whether the type of symbol in which the RO set is located is an SBFD symbol.

2. In paragraph 1, If the RO set is located in the SBFD symbol set, the reference RB is set to the lowest RB among the UL usable RBs on the SBFD symbol set, A terminal in which the reference RB is set to the minimum RB within the UL BWP (bandwidth part) on the non-SBFD symbol set when the RO set is located in the non-SBFD symbol set.

3. In paragraph 2, The above SBFD symbol set further includes a DL (downlink) usable RB outside the UL subband in the frequency domain, The above UL usable RBs are terminals that include RBs within the above UL subband.

4. In paragraph 1, The above RACH configuration information includes Rach-ConfigGeneric information, The above RB offset information is a terminal including msg-1-FrequencyStart.

5. In paragraph 4, The above UL subband is configured based on a higher layer signal.

6. In a base station configured to operate in a wireless communication system, Communication module; and including a processor that controls the above communication module, The above processor, Transmit RACH (random access channel) configuration information, wherein the RACH configuration information includes RB (resource block) offset information used to determine a RO (RACH occasion) start position in a frequency domain; Based on the RB offset information, an RO set is identified in a PRACH (physical random access channel) slot, wherein the PRACH slot includes at least one of a subband non-overlapping full duplex (SBFD) symbol set or a non-SBFD symbol set; and configured to receive PRACH within the above RO set, The above SBFD symbol set includes an UL (uplink) subband in the frequency domain, A base station in which the reference RB to which the RB offset information is applied within the PRACH slot is set differently depending on whether the type of symbol in which the RO set is located is an SBFD symbol.

7. In paragraph 6, If the RO set is located in the SBFD symbol set, the reference RB is set to the lowest RB among the UL usable RBs on the SBFD symbol set, A base station in which, when the RO set is located in the non-SBFD symbol set, the reference RB is set to the minimum RB within the UL BWP (bandwidth part) on the non-SBFD symbol set.

8. In paragraph 7, The above SBFD symbol set further includes a DL (downlink) usable RB outside the UL subband in the frequency domain, The above UL usable RBs are base stations that include RBs within the above UL subband.

9. In paragraph 6, The above RACH configuration information includes Rach-ConfigGeneric information, The above RB offset information is a base station including msg-1-FrequencyStart.

10. In paragraph 9, The above UL subband is a base station configured based on upper layer signals.

11. In a method used by a terminal in a wireless communication system, A step of receiving RACH (random access channel) configuration information, wherein the RACH configuration information includes RB (resource block) offset information used to determine a RO (RACH occasion) start position in a frequency domain; A step of checking an RO set in a PRACH (physical random access channel) slot based on the RB offset information, wherein the PRACH slot includes at least one of a subband non-overlapping full duplex (SBFD) symbol set or a non-SBFD symbol set; and comprising a step of transmitting a PRACH within the above RO set, The above SBFD symbol set includes an UL (uplink) subband in the frequency domain, A method in which the reference RB to which the RB offset information is applied within the PRACH slot is set differently depending on whether the type of symbol in which the RO set is located is an SBFD symbol.

12. In paragraph 11, If the RO set is located in the SBFD symbol set, the reference RB is set to the lowest RB among the UL usable RBs on the SBFD symbol set, A method in which, when the RO set is located in the non-SBFD symbol set, the reference RB is set to the minimum RB within the UL BWP (bandwidth part) on the non-SBFD symbol set.

13. In paragraph 12, The above SBFD symbol set further includes a DL (downlink) usable RB outside the UL subband in the frequency domain, A method in which the above UL usable RBs include RBs within the above UL subband.

14. In paragraph 11, The above RACH configuration information includes Rach-ConfigGeneric information, The above RB offset information includes msg-1-FrequencyStart.

15. In paragraph 14, A method in which the above UL subband is configured based on a higher layer signal.

16. In a method used by a base station in a wireless communication system, A step of transmitting RACH (random access channel) configuration information, wherein the RACH configuration information includes RB (resource block) offset information used to determine a RO (RACH occasion) start position in a frequency domain; A step of checking an RO set in a PRACH (physical random access channel) slot based on the RB offset information, wherein the PRACH slot includes at least one of a subband non-overlapping full duplex (SBFD) symbol set or a non-SBFD symbol set; and comprising a step of receiving a PRACH within the above RO set, The above SBFD symbol set includes an UL (uplink) subband in the frequency domain, A method in which the reference RB to which the RB offset information is applied within the PRACH slot is set differently depending on whether the type of symbol in which the RO set is located is an SBFD symbol.

17. In paragraph 16, If the RO set is located in the SBFD symbol set, the reference RB is set to the lowest RB among the UL usable RBs on the SBFD symbol set, A method in which, when the RO set is located in the non-SBFD symbol set, the reference RB is set to the minimum RB within the UL BWP (bandwidth part) on the non-SBFD symbol set.

18. In paragraph 17, The above SBFD symbol set further includes a DL (downlink) usable RB outside the UL subband in the frequency domain, A method in which the above UL usable RBs include RBs within the above UL subband.

19. In paragraph 16, The above RACH configuration information includes Rach-ConfigGeneric information, The above RB offset information includes msg-1-FrequencyStart.

20. In paragraph 19, A method in which the above UL subband is configured based on a higher layer signal.

Images