Method and apparatus for transmitting signal in wireless communication system

Abstract

The present invention relates to a wireless communication system and, specifically, to a method and a wireless device therefor, the method comprising: receiving a configuration for an SBFD symbol set and a non-SBFD symbol set in a wireless frame, the SBFD symbol set including a DL symbol or a flexible symbol in which a UL subband is configured; and receiving a DL signal in a slot including an SBFD symbol, wherein, when an SSB is configured on symbols in the slot, the DL signal is permitted to also be received in the UL subband in the slot, and, when the SSB is not configured on the symbols in the slot, the DL signal is received only outside the UL subband in the slot.

Description

Method and device for transmitting a signal 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 have been made to develop new 5G (5th generation) communication systems to meet the increasing demand for wireless data traffic. 5G communication systems are referred to as beyond 4G network communication systems, post-LTE systems, or NR (new radio) systems. To achieve high data transmission rates, 5G communication systems include systems operating in the mmWave band above 6 GHz, and implementations at base stations and terminals are being considered to include communication systems operating in the frequency band below 6 GHz in order to secure coverage.

[0003] 3GPP (3rd generation partnership project) NR systems improve network spectrum efficiency, enabling telecommunications operators to provide more data and voice services within a given bandwidth. Therefore, 3GPP NR systems are designed to meet the demands for high-speed data and media transmission in addition to supporting high-volume voice. The advantages of NR systems include high throughput, low latency, support for FDD (frequency division duplex) and TDD (time division duplex), an enhanced end-user experience, and low operating costs due to a simple architecture, all within the same platform.

[0004] For more efficient data processing, dynamic TDD in NR systems may use a method that varies the number of Orthogonal Frequency Division Multiplexing (OFDM) symbols available for uplink and downlink based on the direction of data traffic from cell users. For example, when a cell's downlink traffic is greater than its uplink traffic, the base station may allocate multiple downlink OFDM symbols to a slot (or subframe). Information regarding the slot configuration must be transmitted to the terminals.

[0005] In order to mitigate path loss of radio waves in the ultra-high frequency band and increase the transmission distance of radio waves, beamforming, massive array multiple input / output (massive MIMO), full-dimensional multiple input / output (full-dimensional MIMO, FD-MIMO), array antenna, analog beamforming, hybrid beamforming combining analog beamforming and digital beamforming, and large-scale antenna technologies are being discussed in 5G communication systems. In addition, to improve the network of the system, technology development is underway in 5G communication systems regarding 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, CoMP (coordinated multi-points), and interference cancellation.In addition, advanced coding modulation (ACM) methods such as FQAM (hybrid FSK and QAM modulation) and SWSC (sliding window superposition coding), as well as advanced access technologies such as FBMC (filter bank multi-carrier), NOMA (non-orthogonal multiple access), and SCMA (sparse code multiple access) are being developed in 5G systems.

[0006] Meanwhile, the Internet is evolving from a human-centric network where humans generate and consume information into an IoT (Internet of Things) network where distributed components, such as objects, exchange and process information. IoE (Internet of Everything) technology, which combines IoT with big data processing techniques via connections with cloud servers, is also emerging. To implement IoT, technological elements such as sensing technology, wired and wireless communication and network infrastructure, service interface technology, and security technology are required; consequently, technologies such as sensor networks for connecting objects, machine-to-machine (M2M) communication, and machine-type communication (MTC) are currently being researched. In an IoT environment, intelligent IT services that create new value for human life by collecting and analyzing data generated from connected objects can be provided. Through the convergence and integration of existing IT technologies with various industries, IoT can be applied to fields such as smart homes, smart buildings, smart cities, smart or connected cars, smart grids, healthcare, smart home appliances, and advanced medical services.

[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) communication, and machine-type communication (MTC) are being implemented using 5G communication techniques such as beamforming, MIMO, and array antennas. The application of cloud radio access networks (cloud RAN) as the big data processing technology described earlier can also be considered an example of the convergence of 5G and IoT technologies. Generally, mobile communication systems were developed to provide voice services while ensuring user mobility.

[0008] However, mobile communication systems are gradually expanding their scope to include not only voice but also data services, and have now advanced to the point where they can provide high-speed data services. Nevertheless, due to resource shortages in currently operating mobile communication systems and users' demands for high-speed services, more advanced mobile communication systems are required.

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

[0010] In one aspect of the present invention, a terminal configured to operate in a wireless communication system comprises: a communication module; and a processor for controlling the communication module, wherein the processor receives a configuration of a non-overlapping subband full duplex (SBFD) symbol set and a non-SBFD symbol set within a wireless frame, wherein the SBFD symbol set includes a downlink (DL) symbol or a flexible symbol configured with an uplink (UL) subband, and is configured to receive a DL signal in a slot containing the SBFD symbol, wherein if a synchronization signal / physical broadcast channel block (SSB) is configured on the symbols within the slot, the DL signal is allowed to be received in the UL subband within the slot, and if the SSB is not configured on the symbols within the slot, the DL signal is received only outside the UL subband within the slot.

[0011] In one aspect of the present invention, a method performed by a terminal in a wireless communication system comprises: receiving a configuration of a non-overlapping subband full duplex (SBFD) symbol set and a non-SBFD symbol set within a wireless frame, wherein the SBFD symbol set includes a downlink (DL) symbol or a flexible symbol configured with an uplink (UL) subband; and receiving a DL signal in a slot containing the SBFD symbol, wherein if a synchronization signal / physical broadcast channel block (SSB) is configured on the symbols within the slot, the DL signal is allowed to be received in the UL subband within the slot, and if the SSB is not configured on the symbols within the slot, the DL signal is received only outside the UL subband within the slot.

[0012] Preferably, the SSB may include a cell-specific SSB. Here, the cell-specific SSB may include an SSB set by SIB1 (system information block 1) or ServingCellConfigCommon.

[0013] Preferably, terminal-specific SSBs may be excluded from the above SSBs. Here, the terminal-specific SSBs may include SSBs set by ssb-ToMeasure or SSB-MTCAdditionalPCI.

[0014] Preferably, the DL signal may include a DL signal or a DL channel set semi-static by a base station.

[0015] The present invention provides a method for efficiently transmitting a signal in a wireless communication system and an apparatus utilizing the same. Furthermore, the present invention provides a method for configuring an RO in a wireless communication system and an apparatus utilizing the same. Additionally, the objective of the present invention is to provide a method for transmitting and receiving signals based on an RO and an apparatus utilizing the same.

[0016] The effects obtainable from the present invention are not limited to those mentioned above, and other unmentioned effects will be clearly understood by those skilled in the art from the description below.

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

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

[0019] Figure 3 is a diagram illustrating a physical channel used in a 3GPP system and a general signal transmission method using said physical channel.

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

[0021] Figures 5a and 5b illustrate the procedure for transmitting control information and control channels in a 3GPP NR system.

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

[0023] Figure 7 is a diagram illustrating a method for setting up a PDCCH search space in a 3GPP NR system.

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

[0025] Figure 9 is a diagram illustrating single-carrier communication and multi-carrier communication.

[0026] Figure 10 is a diagram illustrating an example where a cross-carrier scheduling technique is applied.

[0027] FIG. 11 is a block diagram showing the configuration of a terminal and a base station, respectively, according to an embodiment of the present invention.

[0028] Figures 12 and 13 illustrate a subband setting method.

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

[0030] FIGS. 15a and FIGS. 15b illustrate legacy RACH configuration information.

[0031] Figure 16 illustrates an RO (RACH occasion) within a slot.

[0032] Figure 17 illustrates a legacy RO validity determination method.

[0033] FIG. 18 illustrates a signal reception operation according to an example of the present invention.

[0034] FIGS. 19–22 illustrate a method for configuring RO according to an example of the present invention.

[0035] FIGS. 23–27 illustrate a method for determining RO configuration and RO validity according to an example of the present invention.

[0036] FIGS. 28–29 illustrate a PRACH (physical random access channel) transmission according to an example of the present invention.

[0037] The terms used in this specification have been selected to be as widely used as possible, taking into account their functions in the present invention; however, these may vary depending on the intent, convention, or emergence of new technologies of those skilled in the art. In addition, in certain cases, terms have been arbitrarily selected by the applicant, and in such cases, their meanings will be described in the relevant description of the invention. Therefore, it should be noted that the terms used in this specification should be interpreted based on their actual meanings and the overall content of this specification, rather than merely their names.

[0038] Throughout the specification, when a configuration is described as being "connected" to another configuration, this includes not only cases where they are "directly connected," but also cases where they are "electrically connected" with other components interposed between them. Furthermore, when a configuration is described as "including" a specific component, this means that, unless specifically stated otherwise, it does not exclude other components but may include additional components. In addition, the limitation "greater than or equal to" or "less than or equal to" based on a specific threshold value may be appropriately replaced with "greater than" or "less than," respectively, depending on the embodiment.

[0039] 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 using radio technologies such as UTRA (Universal Terrestrial Radio Access) or CDMA2000. TDMA can be implemented using radio technologies such as GSM (Global System for Mobile Communications), GPRS (General Packet Radio Service), and EDGE (Enhanced Data Rates for GSM Evolution). OFDMA can be implemented using radio technologies such as IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802-20, and E-UTRA (Evolved UTRA). UTRA is part of the UMTS (Universal Mobile Telecommunications System). 3GPP (3rd Generation Partnership Project) LTE (long term evolution) is part of E-UMTS (Evolved UMTS) using 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 eMBB (enhanced Mobile BroadBand), URLLC (Ultra-Reliable and Low Latency Communication), and mMTC (massive Machine Type Communication) services, which are requirements of IMT-2020. For clarity, the description focuses on 3GPP NR, but the technical concept of the present invention is not limited thereto.

[0040] Unless otherwise specified in this specification, a base station may include a gNB (next generation node B) as defined in 3GPP NR. Additionally, unless otherwise specified, a terminal may include UE (user equipment). Hereinafter, to aid in understanding the description, each content is described separately as an example, but each example may be used in combination with one another. In this 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 value of a parameter used in the operation of the terminal or in a wireless communication system.

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

[0042] Referring to Fig. 1, the radio frame (or radio frame) used in a 3GPP NR system is 10ms (Δf max N f / 100) * T c It can have a length of ). In addition, the wireless frame consists of 10 subframes (SF) of equal size. 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. Ten subframes within a single radio frame can each be numbered from 0 to 9. Each subframe has a length of 1ms and can consist of one or more slots depending on the subcarrier spacing. More specifically, the available subcarrier spacing in 3GPP NR systems is 15*2 μ It is kHz. μ is the subcarrier spacing configuration, and μ can have values ​​from 0 to 4. That is, 15kHz, 30kHz, 60kHz, 120kHz, or 240kHz can be used as the subcarrier spacing. A 1ms subframe is 2 μ It can be composed of slots. In this case, the length of each slot is 2 -μ It is ms. 2 within one subframe μ The slots are each from 0 to 2 μ Numbers from 0 to 1 can be assigned. Additionally, the slots within a single wireless frame can be assigned from 0 to 10*2 respectively. μ - Numbers up to 1 may be assigned. Time resources may be distinguished by at least one of a wireless frame number (also called a wireless frame index), a subframe number (also called a subframe index), and a slot number (or slot index).

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

[0044] There is one resource grid per antenna port. Referring to FIG. 2, a slot contains multiple orthogonal frequency division multiplexing (OFDM) symbols in the time domain and multiple resource blocks (RBs) in the frequency domain. An OFDM symbol also refers to a single symbol interval. Unless otherwise specified, an OFDM symbol may simply be referred to as a symbol. One RB contains 12 consecutive subcarriers in the frequency domain. Referring to FIG. 2, the signal transmitted in each slot is N size,μ grid,x * N RB sc N subcarriers and N slot symb It can be represented as a resource grid composed of OFDM symbols. Here, x=DL for the downlink resource grid and x=UL for the uplink resource grid. N size,μ grid,x represents the number of resource blocks (RB) according to the subcarrier spacing factor μ (where x is DL or UL), and N slot symb represents the number of OFDM symbols in the slot. N RB sc is the number of subcarriers constituting a single RB, N RB sc = 12. Depending on the multiple access method, OFDM symbols can be referred to as CP-OFDM (cyclic prefix OFDM) symbols or DFT-S-OFDM (discrete Fourier transform spread OFDM) symbols.

[0045] The number of OFDM symbols included in a single slot may vary depending on the length of the cyclic prefix (CP). For example, in the case of a normal CP, a single slot may contain 14 OFDM symbols, whereas in the case of an extended CP, a single slot may contain 12 OFDM symbols. In a specific embodiment, the extended CP may be used only at a 60 kHz subcarrier interval. Although FIG. 2 illustrates a case where a single slot consists of 14 OFDM symbols for convenience of explanation, embodiments of the present invention can 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 includes several subcarriers. The types of subcarriers can be divided into data subcarriers for data transmission, reference signal subcarriers for the transmission of reference signals, and guard bands. The carrier frequency is also called the center frequency (fc).

[0046] One RB is N in the frequency domain RB sc It can be defined by (e.g., 12) consecutive subcarriers. 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 a single slot. k ranges from 0 to N in the frequency domain. size,μ grid, x * N RBsc It is an index assigned up to 1, where l ranges from 0 to N in the time domain. slot symb - It can be an index assigned up to 1.

[0047] In order for a terminal to receive a signal from a base station or transmit a signal to a base station, the terminal's time / frequency synchronization may need to be aligned with the base station's time / frequency synchronization. This is because only when the base station and the terminal are synchronized can the terminal determine the time and frequency parameters necessary to perform the demodulation of the DL signal and the transmission of the UL signal at the correct time.

[0048] Each symbol of a radio frame operating in TDD (time division duplex) or unpaired spectrum may consist 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 FDD (frequency division duplex) or paired spectrum may consist of a downlink symbol or a flexible symbol, and a radio frame operating as an uplink carrier may consist of an uplink symbol or a flexible symbol. Downlink transmission is possible but uplink transmission is not possible with downlink symbols, and uplink transmission is possible but downlink transmission is not possible with uplink symbols. Depending on the signal, it may be determined whether a flexible symbol will be used for downlink or uplink.

[0049] Information regarding the type of each symbol, that is, information indicating one of downlink symbols, uplink symbols, or flexible symbols, may be composed of a cell-specific (or common) radio resource control (RRC) signal. Additionally, information regarding the type of each symbol may be further composed of a terminal-specific (or dedicated) RRC signal. The base station uses the cell-specific RRC signal to provide 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 uplink symbols or downlink symbols is a flexible symbol.

[0050] When information regarding 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. In this case, the terminal-specific RRC signal cannot change the downlink symbol or uplink symbol configured by the cell-specific RRC signal to another symbol type. The terminal-specific RRC signal is for each slot, N of the corresponding slot slot symb Number of downlink symbols among the symbols, N of the corresponding slot slot symbThe number of uplink symbols among the symbols can be signaled. In this case, the downlink symbols of the slot can be configured consecutively from the first symbol to the i-th symbol of the slot. Additionally, the uplink symbols of the slot can be configured consecutively from the j-th symbol to the last symbol of the slot (where i <j). 슬롯에서 상향링크 심볼과 하향링크 심볼 어느 것으로도 구성되지 않은 심볼은 플랙서블 심볼이다.

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

[0052] When the terminal's power is turned on or the terminal newly enters a 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. Afterward, the terminal receives a physical broadcast channel from the base station to obtain broadcast information within the cell.

[0053] 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 the information carried in the PDCCH (S102). Here, the system information received by the terminal is cell-common system information for the terminal to operate correctly at the physical layer in the Radio Resource Control (RRC), and is referred to as remaining system information or system information block (SIB) 1.

[0054] When the terminal first connects to the base station or when there are no wireless resources available for signal transmission (when the terminal is in RRC_IDLE mode), the terminal may perform a random access process with respect to 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 for the preamble from the base station through a PDCCH and a corresponding PDSCH (S104). If a valid random access response message is received by the terminal, the terminal transmits data including its identifier, etc., to the base station through a physical uplink shared channel (PUSCH) as instructed by an uplink grant transmitted from the base station via the PDCCH (S105). Next, the terminal waits for the reception of a PDCCH as instructed by the base station to resolve collisions. If the terminal successfully receives a PDCCH with its identifier (S106), the random access process is terminated. During the random access process, the terminal can obtain terminal-specific system information from the RRC layer that is necessary for the terminal to operate correctly at the physical layer. When the terminal obtains terminal-specific system information from the RRC layer, the terminal enters RRC connected mode.

[0055] The RRC layer is used for generating and managing messages for control between a terminal and a Radio Access Network (RAN). More specifically, the base station and the terminal can perform broadcasting of cell system information required by all terminals within the cell, management of paging message delivery, mobility management and handover, terminal measurement reporting and control thereof, terminal capability management, and storage management including device management at the RRC layer. Generally, since the update of a signal transmitted at the RRC layer (hereinafter referred to as an RRC signal) is longer than the transmission time interval (TTI) at the physical layer, the RRC signal can be maintained without changing for a long period.

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

[0057] FIGS. 4a and FIGS. 4b illustrate an SS / PBCH block for initial cell connection in a 3GPP NR system.

[0058] When the terminal is powered on or intends 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 cell's physical cell identity N cell IDIt can detect [this]. To do this, the terminal can synchronize with the base station by receiving synchronization signals, for example, a main 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 (identity, ID).

[0059] Referring to Fig. 4a, the synchronization signal (SS) is described in more detail. The synchronization signal can be divided into PSS and SSS. PSS can be used to obtain time-domain synchronization and / or frequency-domain synchronization, such as OFDM symbol synchronization and slot synchronization. SSS can be used to obtain frame synchronization and cell group ID. Referring to Fig. 4a and Table 1, the SS / PBCH block can be composed of 20 RBs (= 240 subcarriers) consecutive in the frequency axis and 4 OFDM symbols consecutive in the time axis. In this case, within 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 assigned starting from 0. In the first OFDM symbol where the PSS is transmitted, the base station does not transmit signals through the remaining subcarriers, namely subcarriers 0 through 55 and 183 through 239. Also, in the third OFDM symbol where the SSS is transmitted, the base station does not transmit signals through subcarriers 48 through 55 and 183 through 191. In the SS / PBCH block, the base station transmits the PBCH (physical broadcast channel) through the remaining REs excluding the above signals.

[0060]

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

[0062]

[0063] Here, And,

[0064] It is given as.

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

[0066]

[0067] Here, And,

[0068] It is given as.

[0069] A wireless frame of length 10 ms can be divided into two half frames of length 5 ms. Referring to FIG. 4b, the slot in which the SS / PBCH block is transmitted within each half frame is described. The slot in which the SS / PBCH block is transmitted can be any one of cases A, B, C, D, or E. In case A, the subcarrier interval is 15 kHz, and the start time of the SS / PBCH block is {2, 8} + 14*n-th symbol. At this time, n can be 0 or 1 at a carrier frequency of 3 GHz or less. Also, at a carrier frequency between 3 GHz and 6 GHz or less, n can be 0, 1, 2, or 3. In case B, the subcarrier interval is 30 kHz, and the start time of the SS / PBCH block is {4, 8, 16, 20} + 28*n-th symbol. At this time, n can be 0 at a carrier frequency of 3 GHz or less. Additionally, at carrier frequencies greater than 3 GHz and less than or equal to 6 GHz, n can be 0 or 1. In case C, the subcarrier interval is 30 kHz, and the start time of the SS / PBCH block is {2, 8} + 14*n-th symbol. At this time, at carrier frequencies less than or equal to 3 GHz, n can be 0 or 1. Additionally, at carrier frequencies greater than 3 GHz and less than or equal to 6 GHz, n can be 0, 1, 2, or 3. In case D, the subcarrier interval is 120 kHz, and the start time of the SS / PBCH block is {4, 8, 16, 20} + 28*n-th symbol. At this time, at carrier frequencies greater than or equal to 6 GHz, n can be 0, 1, 2, 3, 5, 6, 7, 8, 10, 11, 12, 13, 15, 16, 17, or 18. In case E, the subcarrier interval is 240 kHz, and the start time of the SS / PBCH block is {8, 12, 16, 20, 32, 36, 40, 44} + 56*n-th symbol. At this time, at a carrier frequency of 6 GHz or higher, n can be 0, 1, 2, 3, 5, 6, 7, 8.

[0070] FIGS. 5A and 5B illustrate a procedure for transmitting control information and a control channel in a 3GPP NR system. Referring to FIG. 5A, a base station may add a cyclic redundancy check (CRC) 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 SI-RNTI (system information RNTI), P-RNTI (paging RNTI), RA-RNTI (random access RNTI), and TPC-RNTI (transmit power control RNTI). Additionally, a terminal-specific RNTI may include at least one of C-RNTI (cell temporary RNTI) and CS-RNTI. Subsequently, 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) (S206). Subsequently, the base station can multiplex DCI(s) based on a CCE (control channel element)-based PDCCH structure (S208). In addition, the base station can apply additional processes (S210), such as scrambling, modulation (e.g., QPSK), and interleaving, to the multiplexed DCI(s) and then map them to the resources to be transmitted. A 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 the aggregation level. In 3GPP NR systems, 1, 2, 4, 8, or 16 aggregation levels can be used. FIG. 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 area accordingly.

[0071] 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.

[0072] A CORESET is a time-frequency resource through which a PDCCH, a control signal for a terminal, is transmitted. Additionally, the search space described below can be mapped to a single CORESET. Therefore, instead of monitoring all frequency bands to receive a PDCCH, the terminal can decode the PDCCH mapped to the CORESET by monitoring the time-frequency area designated as the CORESET. The base station can configure one or multiple CORESETs per cell for the terminal. A CORESET can be composed of up to three consecutive symbols along the time axis. Additionally, a CORESET can be composed of six consecutive PRBs along the frequency axis. In the embodiment of FIG. 6, CORESET#1 is composed of consecutive PRBs, while CORESET#2 and CORESET#3 are composed of discontinuous 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.

[0073] Figure 7 is a diagram illustrating a method for setting up a PDCCH search space in a 3GPP NR system.

[0074] 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 referred to as PDCCH candidates) where the terminal's PDCCH can be transmitted. The search space may include a common search space that 3GPP NR terminals must search in common, and a terminal-specific or UE-specific search space that a specific terminal must search. In the common search space, PDCCHs configured to be searched in common by all terminals in a cell belonging to the same base station can be monitored. Additionally, the terminal-specific search space may be configured per terminal so that PDCCHs assigned to each terminal can be monitored at different search space locations depending on the terminal. In the case of a terminal-specific search space, search spaces between terminals may partially overlap due to the limited control area where PDCCHs can be assigned. Monitoring a PDCCH includes blind decoding PDCCH candidates within the search space. When blind decoding is successful, it can be expressed that PDCCH is (successfully) detected / received, and when blind decoding fails, it can be expressed that PDCCH is not detected / received or is not successfully detected / received.

[0075] For convenience of explanation, a PDCCH scrambled with a group common (GC) RNTI already known to one or more terminals to transmit downlink control information to one or more terminals is referred to as a group common (GC) PDCCH or a common PDCCH. Additionally, a PDCCH scrambled with a terminal-specific RNTI already known to a specific terminal to transmit uplink scheduling information or downlink scheduling information to one 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 a common search space or a terminal-specific PDCCH.

[0076] The base station can notify each terminal or group of terminals via PDCCH of information related to resource allocation for the transmission channels PCH (paging channel) and DL-SCH (downlink-shared channel) (i.e., DL Grant) or information related to resource allocation for UL-SCH (uplink-shared channel) and HARQ (hybrid automatic repeat request) (i.e., UL Grant). The base station can transmit PCH transmission blocks and DL-SCH transmission blocks via PDSCH. The base station can transmit data excluding specific control information or specific service data via PDSCH. Additionally, the terminal can receive data excluding specific control information or specific service data via PDSCH.

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

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

[0079]

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

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

[0082] - HARQ-ACK: A response to a PDCCH (indicating a DL SPS release) and / or a response to a downlink transport block (TB) on the PDSCH. HARQ-ACK indicates the successful reception of information transmitted via the PDCCH or PDSCH. HARQ-ACK responses include a positive ACK (simply ACK), a negative ACK (hereinafter NACK), a DTX (Discontinuous Transmission), or a NACK / DTX. Here, the term HARQ-ACK is used interchangeably with HARQ-ACK / NACK and ACK / NACK. Generally, ACK is represented by a bit value of 1 and NACK can be represented by a bit value of 0.

[0083] - CSI (Channel State Information): This is feedback information regarding 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 RI (Rank Indicator) and PMI (Precoding Matrix Indicator). CSI can be divided into CSI Part 1 and CSI Part 2 depending on the information represented by the CSI.

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

[0085] PUCCH Format 0 is a format capable of transmitting 1-bit or 2-bit HARQ-ACK information or SR. PUCCH Format 0 can be transmitted via one or two OFDM symbols in the time axis and one PRB in the frequency axis. When PUCCH Format 0 is transmitted via two OFDM symbols, the same sequence can be transmitted via different RBs for both symbols. In this case, the sequence may 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 M bit Bit UCI (M bit Cyclic shift (CS) value m depending on = 1 or 2) cs It can determine. In addition, a base sequence of length 12 with a fixed CS value m cs Based on this, a cyclically shifted sequence 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 When = 1, 1-bit UCI 0 and 1 can each be mapped to two cyclically shifted sequences with a difference of 6 in their cyclic shift values. Also, M bit In the case where = 2, 2-bit UCI 00, 01, 11, 10 can each be mapped to four cyclically shifted sequences with a difference of 3 in the cyclic shift values.

[0086] PUCCH Format 1 can transmit 1-bit or 2-bit HARQ-ACK information or SR. PUCCH Format 1 can be transmitted via consecutive OFDM symbols in the time axis and a single 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= A single UCI can be modulated with BPSK. The terminal is M bit A UCI with =2 can be modulated using QPSK (quadrature phase shift keying). A signal is obtained by multiplying the modulated complex valued symbol d(0) by a sequence of length 12. In this case, the sequence may be the base sequence used in PUCCH format 0. The terminal transmits the obtained signal by spreading it as a time-axis orthogonal cover code (OCC) onto the even-numbered OFDM symbols assigned to PUCCH format 1. In PUCCH format 1, the maximum number of different terminals multiplexed to the same RB is determined by the length of the OCC used. A demodulation reference signal (DMRS) can be spread as an OCC and mapped to the odd-numbered OFDM symbols of PUCCH format 1.

[0087] PUCCH Format 2 can transmit UCIs exceeding 2 bits. PUCCH Format 2 can be transmitted via one or two OFDM symbols in the time axis and one or multiple RBs in the frequency axis. When PUCCH Format 2 is transmitted via two OFDM symbols, the same sequence can be transmitted via two OFDM symbols to different RBs. Here, the sequence consists of multiple modulated complex symbols d(0), …, d(M symbol -1) can be. Here, M symbol is M bit It can be / 2. Through this, the terminal can obtain frequency diversity gain. More specifically, M bit Bit UCI (M bit >2) is bit-level scrambled and QPSK modulated and mapped to RB(s) of one or two OFDM symbols. Here, the number of RBs can be one of 1 to 16.

[0088] PUCCH Format 3 or PUCCH Format 4 can transmit a UCI exceeding 2 bits. PUCCH Format 3 or PUCCH Format 4 can be transmitted via consecutive OFDM symbols in the time axis and a single 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 is M bit Bit UCI (M bit Modulate >2) with π / 2-BPSK (Binary Phase Shift Keying) or QPSK to obtain complex number symbols d(0)~d(M symb -1) can be generated. Here, if π / 2-BPSK is used, M symb =M bit And, if you use QPSK, M symb =M bit / 2. The terminal may not apply block-unit spreading to PUCCH format 3. However, the terminal may apply block-unit spreading to one RB (i.e., 12 subcarriers) using a PreDFT-OCC of length 12 so that PUCCH format 4 can have two or four multiplexing capacities. The terminal may transmit the spread signal by transmitting precoding (or DFT-precoding) the spread signal and mapping it to each RE.

[0089] At this time, the number of RBs occupied by PUCCH format 2, PUCCH format 3, or PUCCH format 4 can be determined by the length of the UCI transmitted by the terminal and the maximum code rate. When 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 may transmit only the remaining UCI information without transmitting some UCI information according to the priority of the UCI information.

[0090] PUCCH format 1, PUCCH format 3, or PUCCH format 4 can be configured via an RRC signal 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 an RRC signal. When PUCCH format 1, PUCCH format 3, or PUCCH format 4 is transmitted over N OFDM symbols in the time axis, the first hop may have floor (N / 2) OFDM symbols and the second hop may have ceil (N / 2) OFDM symbols.

[0091] PUCCH format 1, PUCCH format 3, or PUCCH format 4 may be configured to be transmitted repeatedly across multiple slots. In this case, the number of slots K in which PUCCH is transmitted repeatedly may be configured by an RRC signal. The PUCCH transmitted repeatedly must start at the same position of the OFDM symbol within each slot and have the same length. If any of the OFDM symbols in the slot in which the terminal is to transmit the PUCCH is indicated as a DL symbol by the RRC signal, the terminal may not transmit the PUCCH in that slot but may defer transmission to the next slot.

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

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

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

[0095] Carrier aggregation refers to a method by which a terminal utilizes multiple frequency blocks or (in a logical sense) cells, composed of uplink resources (or component carriers) and / or downlink resources (or component carriers), to form a single large logical frequency band, thereby enabling a wireless communication system to use 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 the sake of convenience of explanation, the term "component carrier" will be used consistently below.

[0096] Referring to FIG. 8, as an example of a 3GPP NR system, the entire system band 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 depicts each component carrier as having the same bandwidth, this is merely an example, and each component carrier may have different bandwidths. Additionally, although each component carrier is depicted as being adjacent to each other in the frequency axis, the figure is illustrated in a logical sense, and each component carrier may be physically adjacent to each other or separated.

[0097] Different center frequencies may be used in each component carrier. Additionally, a single common center frequency may be used in physically adjacent component carriers. Assuming that all component carriers are physically adjacent in the embodiment of FIG. 8, center frequency A may be used in all component carriers. Additionally, assuming that each component carrier is not physically adjacent, center frequency A and center frequency B may be used in each component carrier.

[0098] When the total system bandwidth is expanded through carrier aggregation, the frequency band used for communication with each terminal can be defined in terms of component carriers. Terminal A can use the total system bandwidth of 100 MHz and performs communication using all five component carriers. Terminals B1 through B5 can use only a 20 MHz bandwidth and perform communication using a single component carrier. Terminals C1 and C2 can use a 40 MHz bandwidth and each perform communication using two component carriers. The two component carriers may or may not be logically or 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.

[0099] FIG. 9 is a diagram illustrating single-carrier communication and multi-carrier communication. In particular, FIG. 9(a) illustrates a subframe structure of a single carrier, and FIG. 9(b) illustrates a subframe structure of a multi-carrier.

[0100] Referring to FIG. 9(a), a typical wireless communication system can perform data transmission or reception through one DL band and a corresponding UL band in FDD mode. In another specific embodiment, in TDD mode, the wireless communication system can divide the wireless frame into uplink time units and downlink time units in the time domain and perform data transmission or reception through the uplink and downlink time units. Referring to FIG. 9(b), three 20MHz component carriers (CCs) can be aggregated in the UL and DL, respectively, to support a bandwidth of 60MHz. Each CC can be adjacent or non-adjacent to one another in the frequency domain. FIG. 9(b) illustrates a case where the bandwidths of the UL CC and the DL CC are both identical and symmetrical for convenience, but the bandwidths of each CC can be determined independently. Additionally, asymmetric carrier aggregation is possible where the number of UL CCs and the number of DL CCs are different. A DL / UL CC assigned / configured to a specific terminal via RRC can be referred to as the serving DL / UL CC of the specific terminal.

[0101] A base station can communicate with a terminal by activating some or all of the terminal's serving CCs or by deactivating some of the CCs. The base station may change the CCs that are activated / deactivated and may change the number of CCs that are activated / deactivated. If the base station allocates available CCs to the terminal in a cell-specific or terminal-specific manner, at least one of the CCs once allocated may not be deactivated unless the CC allocation to the terminal is completely reconfigured or the terminal undergoes a handover. One CC that is not deactivated to the terminal is referred to as the primary CC (PCC) or PCell (primary cell), and the CC that the base station can freely activate / deactivate is referred to as the secondary CC (SCC) or SCell (secondary cell).

[0102] 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, that is, a combination of a DL CC and an UL CC. A cell can consist of a DL resource alone or a combination of a DL resource and an UL resource. Where carrier aggregation is supported, the linkage between the carrier frequency of a DL resource (or DL ​​CC) and the carrier frequency of a UL resource (or UL CC) can be indicated by system information. The carrier frequency refers to the center frequency of each cell or CC. A cell corresponding to a PCC is referred to as a PCell, and a cell corresponding to an SCC is referred to as a SCell. In the downlink, the carrier corresponding to a PCell is a DL PCC, and in the uplink, the carrier corresponding to a PCell is an UL PCC. Similarly, in the downlink, the carrier corresponding to a SCell is a DL SCC, and in the uplink, the carrier corresponding to a SCell is an UL SCC. Depending on the terminal capability, the serving cell(s) may consist of one PCell and zero or more SCells. For a UE in the RRC_CONNECTED state but where carrier aggregation is not enabled or does not support carrier aggregation, there is only one serving cell consisting only of PCells.

[0103] As previously mentioned, the term "cell" used in carrier aggregation is distinguished from the term "cell" which refers to a specific geographical area where communication services are provided by a single base station or a single antenna group. That is, a 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 specific geographical area and a cell in carrier aggregation, the present invention refers to a cell in carrier aggregation as CC, and a cell in a geographical area as a cell.

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

[0105] 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 SCell). Additionally, it is assumed that the DL PCC is configured as a PDCCH monitoring CC. If cross-carrier scheduling is not configured by terminal-specific (or terminal-group-specific or cell-specific) upper-layer signaling, CIF is disabled, and each DL CC can transmit only the PDCCH that schedules its own PDSCH without 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 use CIF to transmit not only the PDCCH that schedules the PDSCH of DL CC A but also the PDCCH that schedules the PDSCH of another CC (cross-carrier scheduling). On the other hand, no PDCCH is transmitted from other DL CCs. Therefore, depending on whether cross-carrier scheduling is configured for the terminal, the terminal monitors the PDCCH that does not contain CIF to receive the self-carrier scheduled PDSCH, or monitors the PDCCH that contains CIF to receive the cross-carrier scheduled PDSCH.

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

[0107] FIG. 11 is a block diagram showing the configuration of a terminal and a base station, respectively, according to an embodiment of the present invention.

[0108] In an embodiment of the present invention, the 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 User Equipment (UE), Station (STA), Mobile Subscriber (MS), etc. Additionally, in an embodiment of the present invention, the 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 assignment, channel monitoring, self-diagnosis, and relay. The base station may be referred to as a Next Generation Node (gNB) or Access Point (AP), etc.

[0109] As described above, 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).

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

[0111] 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), such as cellular communication interface cards (121, 122) and unlicensed band communication interface cards (123), either internally or externally. Although the communication module (120) is depicted as an integrated module in the drawing, each network interface card may be arranged independently according to circuit configuration or purpose, unlike in the drawing.

[0112] A 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 cellular communication services in a first frequency band based on instructions from a processor (110). According to one embodiment, the cellular communication interface card (121) may include at least one NIC module using a frequency band of less 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 a base station (200), an external device, and a server according to a cellular communication standard or protocol of a frequency band of less than 6 GHz supported by the NIC module.

[0113] A cellular communication interface card (122) 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 cellular communication services in a second frequency band based on instructions from a processor (110). According to one embodiment, the cellular communication interface card (122) 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 (122) can independently perform cellular communication with at least one of a 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 NIC module.

[0114] 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 a third frequency band which is an unlicensed band, and provides unlicensed band communication services based on instructions from a processor (110). The unlicensed band communication interface card (123) may include at least one NIC module that uses the 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 perform wireless communication with at least one of a base station (200), an external device, and a server independently or dependently according to the unlicensed band communication standard or protocol of the frequency band supported by the NIC module.

[0115] Next, the memory (130) stores a control program used in the terminal (100) and various data associated therewith. This control program may include a specific 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.

[0116] 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 the command of the processor (110) using various output means.

[0117] Next, the display unit (150) outputs various images to 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 control commands of the processor (110).

[0118] In addition, 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).

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

[0120] 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 a plurality of network interface cards, such as cellular communication interface cards (221, 222) and unlicensed band communication interface cards (223), in an internal or external form. Although the communication module (220) is shown as an integrated module in the drawing, each network interface card may be arranged independently according to circuit configuration or purpose, unlike in the drawing.

[0121] A cellular communication interface card (221) can transmit and receive wireless signals with at least one of the above-described terminal (100), external device, and server using a mobile communication network, and can provide cellular communication services in a first frequency band based on instructions from a processor (210). According to one embodiment, the cellular communication interface card (221) may include at least one NIC module using a frequency band of less 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 of less than 6 GHz supported by the NIC module.

[0122] A cellular communication interface card (222) can 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 can provide cellular communication services in a second frequency band based on instructions from a 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) can independently perform cellular communication with at least one of a 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 NIC module.

[0123] 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 a third frequency band which is an unlicensed band, and provides unlicensed band communication services based on instructions from a processor (210). The unlicensed band communication interface card (223) may include at least one NIC module that uses the 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 perform wireless communication with at least one of a terminal (100), an external device, and a server independently or dependently according to the unlicensed band communication standard or protocol of the frequency band supported by the NIC module.

[0124] The terminal (100) and base station (200) illustrated in FIG. 11 are block diagrams according to an embodiment of the present invention, wherein the separated blocks represent logically distinguished elements of the device. Accordingly, the elements of the device described above may be mounted as a single chip or as a plurality of chips depending on the design of the device. In addition, some components of the terminal (100), such as a user interface (140) and a display unit (150), may be optionally provided in the terminal (100). Furthermore, the user interface (140) and the display unit (150), etc., may be additionally provided in the base station (200) as needed.

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

[0126] The terminal can receive information regarding each symbol type within a slot from the base station via a cell-specific (or cell-common) RRC (radio resource control) signal and set the information for each symbol type semi-statically. Here, the cell-specific (in other words, cell-common or terminal-common) RRC signal includes tdd-UL-DL-ConfigurationCommon. Alternatively, the terminal can receive information regarding each symbol type within a slot via SIB1 and set the information for each symbol type semi-statically. Additionally, the terminal can receive information regarding each symbol type within a slot semi-statically from the base station via a terminal-specific (UE-specific) or terminal-dedicated RRC signal. The base station can configure / set each symbol type within the slot for the terminal using the information regarding each symbol type within the slot.

[0127] When a terminal receives information regarding each symbol type within a slot from a base station as a cell-specific RRC signal, the information formed by the cell-specific RRC signal may include at least one of: 1) the period of the cell-specific slot configuration; 2) the number of slots consisting only of downlink symbols starting from the starting slot of the period; 3) the number of downlink symbols starting from the first symbol of the slot immediately following the last slot consisting only of downlink symbols; 4) the number of slots consisting only of uplink symbols starting from the last slot of the period; and 5) the number of uplink symbols immediately preceding the last slot among the slots consisting only of uplink symbols (starting from the end of the period and moving forward). Here, a symbol that is not composed of a downlink symbol or an uplink symbol is a flexible symbol. Additionally, when a terminal receives information regarding each symbol type within a slot from a base station as a cell-specific RRC signal, the information regarding each symbol type may include up to two slot patterns. In this case, each of the two patterns may be applied consecutively to the 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.

[0128] When a terminal receives information regarding each symbol type within a slot from a base station as a terminal-specific RRC signal, a cell-specific flexible symbol may 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 may include at least one of 1) an index for a slot within the 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. Additionally, the terminal may be configured such that all symbols within the slot are downlink symbols or all symbols within the slot are uplink symbols. 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.

[0129] As another method of providing slot format information to a terminal, the base station may transmit slot format information to the terminal via a slot format indicator (SFI) of DCI format 2_0 included in the group common (GC)-PDCCH. The GC-PDCCH may be CRC scrambled into SFI-RNTI for terminals receiving slot format information. In the following description, the SFI transmitted via the GC-PDCCH may be referred to as a dynamic SFI.

[0130] The terminal can receive a dynamic SFI via the GC-PDCCH to be indicated whether the symbols within the slot are cell-specific flexible symbols or terminal-specific flexible symbols, or whether they are downlink symbols, uplink symbols, or flexible symbols. In other words, only the flexible symbols semi-statically configured by the terminal can be indicated as any one of downlink symbols, uplink symbols, or flexible symbols via the dynamic SFI. The terminal may not expect that the semi-statically configured downlink symbols or uplink symbols will be indicated as other types of symbols by the dynamic SFI. To receive a GC-PDCCH transmitting DCI format 2_0 containing a dynamic SFI, the terminal may perform blind decoding at set monitoring cycles from the base station. If the terminal successfully receives the GC-PDCCH by performing blind decoding, the terminal may apply the information regarding the slot format indicated by the dynamic SFI starting from the slot in which the GC-PDCCH was received.

[0131] The terminal may receive a combination of slot formats that can be indicated from the base station via a dynamic SFI. The slot format combinations are for each of the 1 to 256 slots, and the terminal may receive a slot format combination for any one of the 1 to 256 slots via a dynamic SFI, and the dynamic SFI may include an index indicating which slot the slot format combination applies to. Table 3 is a table showing the slot format combinations for each slot (see 3GPP TS38.213).

[0132]

[0133] In Table 3, D represents the downlink symbol, U represents the uplink symbol, and F represents the flexible symbol. As shown in Table 3, up to two DL / UL switching operations may be allowed within one slot.

[0134] In this specification, configuration, setting, and instruction may be used interchangeably. That is, being configured, being set, and being directed may have the same meaning, and likewise being configured, being set, and being directed may have the same meaning.

[0135] Subband-based full duplex: Spectrum partitioning

[0136] Figures 12 and 13 illustrate a subband setting method and signal transmission.

[0137] In TDD or unpaired spectrum systems, when a terminal is configured or instructed to set a slot format, problems such as reduced uplink coverage, increased latency, and reduced capacity may occur because only limited time-domain resources are allocated as uplink resources. To address these issues, a method is being discussed to divide specific time-domain resources within a cell into multiple subbands in the frequency domain for use in both downlink reception and uplink transmission.

[0138] Referring to FIG. 12, the terminal may receive TDD configuration information to configure the slot format semi-statically, or receive SFI to dynamically instruct the slot format. Here, the TDD configuration information may 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 the downlink, U (or UL) represents the uplink, and F represents the flexible, and D / F (or DL / F) represents D (or DL) or F. Subsequently, the terminal may configure one or more subbands in the frequency domain for specific time domain resources (e.g., at least one slot / symbol) (n2~n3) through subband configuration / instruction from the base station. Subband configuration / indication information may include information regarding a consecutive set of RBs constituting the subband (e.g., starting RB, number of RBs, etc.). If multiple subbands are configured within a time domain resource, the 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. The D (or DL) subband may consist of one or more downlink RB(s), and the U (or UL) subband may consist of one or more uplink RB(s). Downlink RB(s) may refer to resources available for downlink reception (i.e., DL usable RBs), and uplink RB(s) may refer to resources available for uplink transmission (i.e., UL usable RBs).

[0139] Referring to FIG. 13, a terminal may be (dynamically) instructed to multiple subbands in the frequency domain for a downlink (D or DL) slot or symbol(s) that is semi-statically configured (e.g., TDD configuration) or dynamically instructed (e.g., SFI) by a base station. In the figure, the multiple subbands include two D (or DL) subbands and one U (or UL) subband. In this case, resources configured or instructed to receive a downlink signal or channel and resources configured or instructed to transmit an uplink signal or channel 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, there may be overlap in at least one symbol (5th to 6th symbols). Meanwhile, when a subband is configured, the base station can perform both downlink transmission and uplink reception on the same subband symbol (full duplex), whereas a terminal supporting only half duplex can only perform one of the operations: downlink reception or uplink transmission on the same subband symbol. Here, a subband symbol refers to a symbol in which a subband is configured. Therefore, when downlink reception and uplink transmission overlap on the same subband symbol (refer to the circled part in the diagram), the terminal and the base station may operate as follows.

[0140] 1) Where downlink reception and uplink transmission belong to different terminals,

[0141] - Each terminal can perform downlink reception or uplink transmission without restriction.

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

[0143] 2) Where downlink reception and uplink transmission belong to the same terminal,

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

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

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

[0147] In addition, the collision situation may not be limited to cases where the terminal receives multiple subbands in the frequency domain for flexible slots or symbol(s) that are semi-statically configured or dynamically instructed by the base station. That is, the collision situation may also include cases where the terminal receives multiple subbands in the frequency domain for flexible slots or symbol(s) that are semi-statically configured or dynamically instructed by the base station.

[0148] Random Access Channel Procedure (RACH)

[0149] FIG. 14 illustrates a random access procedure. FIG. 15a and 15b illustrate RACH configuration information. FIG. 16 illustrates a RACH resource.

[0150] Referring to FIG. 14, the terminal can receive RACH configuration information from a base station (S1402). The RACH configuration information can be received through RACH-ConfigCommon information within the SIB. RACH-ConfigCommon may include rach-ConfigGeneric information. FIGS. 15a and 15b illustrate RACH-ConfigCommon information and rach-ConfigGeneric information used in legacy NR systems. PRACH slots can be periodically set on a radio frame basis based on the PRACH Configuration Index within 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 the PRACH slot, one or more ROs (RACH occasions or PRACH occasions) may be set in the time domain and one or more ROs may be set in the frequency domain. The number of symbols and RBs occupied by a single RO may be defined differently depending on the PRACH / preamble format. Frequency resource information of the RO(s) configured within the 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 RO start position (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). FIG. 16 illustrates multiple ROs configured within the PRACH slot. The figure illustrates a case where two ROs are configured in the time domain (TDM) and two ROs are configured in the frequency domain (FDM) within the PRACH slot.FIG. 16 illustrates a case where a symbol set constituting a single RO in the time domain consists of 7 symbols. In the frequency domain, the RO start position (e.g., PRB#2) is set based on msg1-FrequencyStart. msg1-FrequencyStart can have a value from 0 to (number of RBs in the frequency band of UL BWP - 1).

[0151] Subsequently, the terminal can transmit PRACH via RO (S1404). Here, the RO can be selected from a set of ROs within the PRACH slot. Specifically, the RO can be selected from among valid RO(s) within the set of ROs within the PRACH slot. For valid ROs, refer to the description of FIG. 17 described later. Subsequently, the terminal can receive a RAR (random access response) (S1406).

[0152] Signal transmission and reception based on RO validity

[0153] Whether an RO is valid can be determined based on the slot format configuration of the PRACH slot. Based on whether the RO is valid, the terminal can perform uplink transmission (e.g., PRACH) or downlink reception (e.g., PDSCH, CSI-RS). Specifically, the terminal can perform PRACH transmission on a valid RO. Additionally, if a valid RO (including gap symbols) and a downlink reception (e.g., PDSCH reception, CSI-RS reception) overlap in the time domain, the terminal can skip the downlink reception. On the other hand, if the RO is invalid, the terminal cannot perform PRACH transmission on that RO. Furthermore, even if the RO (including gap symbols) and a downlink reception overlap in the time domain, if the RO is invalid, the terminal can perform the downlink reception normally. In existing NR systems, the terminal 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 receives or does not receive tdd-UL-DL-ConfigurationCommon, which is information about the symbol type. tdd-UL-DL-ConfigurationCommon can be received via a cell-specific (or cell-common) RRC signal or SIB1 (system information block 1).

[0154] - If the terminal has not received tdd-UL-DL-ConfigurationCommon:

[0155] The RO in the PRACH slot does not precede the SS / PBCH block in the same PRACH slot in the time domain, and at least N after the last SS / PBCH block reception symbol. gap If it starts after a symbol, the corresponding RO may be valid. Here, the last SS / PBCH block received symbol refers to the last received symbol of the last SS / PBCH block prior to the corresponding RO.

[0156] - When the terminal is configured with tdd-UL-DL-ConfigurationCommon (Fig. 17):

[0157] If an RO within a PRACH slot lies on a UL symbol(s), the RO is valid. Additionally, (if at least a portion of the RO is outside the UL symbol(s), the RO within the PRACH slot does not precede the SS / PBCH block within the same PRACH slot in the time domain, and at least N after the last DL symbol. gap It starts after the symbol (Fig. 17(a)) and at least N after the last SS / PBCH block reception symbol. gap If it starts after a symbol (Fig. 17(b)), the corresponding RO may be valid. Here, the last DL symbol refers to the last DL symbol prior to the corresponding RO on the set of DL symbols configured by tdd-UL-DL-ConfigurationCommon. In the figure, the D symbol refers to a cell-common (or cell-specific) DL symbol, the F symbol refers to a cell-common (or cell-specific) flexible symbol, and the U symbol refers to a cell-common (or cell-specific) UL symbol.

[0158] Table 4 is N gap ...is an example. In the case of the PRACH preamble format B4, N gap It can be 0.

[0159] Preamble SCSN gap 1.25 kHz or 5 kHz015 kHz or 30 kHz or 60 kHz or 120 kHz2

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

[0161] First, the terms used in this invention are summarized.

[0162] - Subband-based full duplex: Refers to a method that supports simultaneous transmission and reception operations using subbands within a cell / BWP. It may be referred to as SBFD (subband non-overlapping full duplex). Here, a subband refers to a frequency band configured / instructed for SBFD operation within a cell / BWP. A single subband may consist of a single consecutive set of (P)RBs. For example, a UL subband may consist of a set of (P)RBs capable of UL transmission (i.e., UL usable RBs). Similarly, a DL subband may consist of a set of (P)RBs capable of DL transmission (i.e., DL usable RBs). Examples regarding subband configuration / formats may be referenced in FIGS. 12–13. For example, in the case of unpaired spectrum (i.e., TDD cell / BWP), DL and UL subbands may be configured on a DL slot / symbol, or DL ​​and UL subbands may be configured on a flexible slot / symbol. Here, the DL subband on the DL slot / symbol may be explicitly configured or implicitly configured outside the UL subband. A slot / symbol in which a subband is configured within the frequency domain for SBFD operation may be referred to as an SBFD slot / symbol. If 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. SBFD slots / symbols are limited to DL slots / symbols and flexible slots / symbols, and UL slots / symbols may always be non-SBFD slots / symbols.

[0163] - SBFD Slot / Symbol Interval: Refers to a time interval on a cell / BWP where a subband is configured / indicated. For example, an SBFD slot / symbol interval includes a time interval in the frequency domain where a subband (e.g., DL and / or UL subband) is configured / indicated. Here, the time interval may include slot(s) and / or symbol(s) (or a set of symbols). An SBFD slot / symbol interval may include one or more subbands in the frequency domain. If 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 be non-overlapping in the frequency domain. An SBFD slot / symbol interval may simply be referred to as an SBFD interval. An SBFD slot / symbol interval includes a DL slot / symbol and / or flexible slot / symbol interval where a UL subband is configured.

[0164] - Non-SBFD slot / symbol interval: Refers to a time interval on a cell / BWP where no subband is set / indicated. A non-SBFD slot / symbol interval includes a time interval where no DL or UL subband is set / indicated. Here, the time interval may include slot(s) and / or symbol(s) (or a set of symbols). 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 DL symbols, flexible symbols, and UL symbols depending on the slot format. For example, if no subband is set / indicated on a UL BWP, the non-SBFD slot / symbol interval includes UL slot / symbols. A non-SBFD slot / symbol interval may simply be referred to as a non-SBFD interval. A non-SBFD slot / symbol interval includes UL slot / symbols.

[0165] - Legacy NR System: Refers to a system that operates according to the existing NR method because SBFD operation is not supported or configured.

[0166] - SBFD aware-UE: Refers to a terminal that recognizes SBFD operations. An SBFD aware UE can perform various SBFD operations described in this specification. It may be simply referred to as an SBFD UE.

[0167] - SBFD non-aware-UE: Refers to a terminal that is not aware of SBFD operations. Includes terminals operating on legacy NR systems (e.g., legacy NR terminals). Simply put, it may be referred to as a non-SBFD UE or legacy UE.

[0168] - SBFD-DL symbol: Indicates that a subband is configured to perform SBFD operations on symbols configured as DL by tdd-UL-DL-ConfigurationCommon. The subband may include UL subbands and / or DL ​​subbands.

[0169] - SBFD-FL symbol: Indicates a case where a subband is configured to perform SBFD operations for symbols configured as flexible (F) by tdd-UL-DL-ConfigurationCommon. The subband may include a UL subband and / or a DL subband.

[0170] - SBFD RO: Represents an RO configured for a terminal that supports SBFD operation (i.e., an SBFD aware-UE). An SBFD RO can be configured using a legacy (P)RACH configuration or a new (P)RACH configuration. An SBFD aware-UE can perform PRACH transmissions on a valid SBFD RO. A legacy UE cannot recognize an SBFD RO. Legacy ROs and SBFD ROs coexist within the system. To distinguish it from a legacy RO, an SBFD RO may simply be referred to as a new RO.

[0171] SBFD operation in a slot / symbol where an SS / PBCH block is set

[0172] As an embodiment of the present invention, the SBFD operation in a symbol where reception of an SS / PBCH block (hereinafter SSB) is set is described. FIG. 18 is a diagram for explaining the transmission of an uplink signal and channel by a terminal and the reception of a downlink signal and channel by a terminal in a slot having a symbol where reception of an SSB is set or a symbol where reception of an SSB is set, according to an embodiment of the present invention.

[0173] Referring to FIG. 18, in a slot where SSB symbols are configured cell-specifically based on the cell, the SSB may take precedence over "configured UL transmission" or "dynamic scheduled UL transmission" within the UL subband, so the resources configured for the UL subband may inevitably be wasted. That is, if a slot / symbol configured for the UL subband contains an SSB, the terminal cannot perform a transmission operation in the UL subband. Additionally, the terminal cannot perform a reception operation in the UL subband. As a result, the UL subband resources within the slot / symbol containing the SSB cannot be used for transmission and reception and may be wasted.

[0174] To resolve this issue, if a slot configured with DL symbols by at least TDD-UL-DL-ConfigCommon, and the DL symbols are configured with SBFD symbols according to the SBFD subband configuration, and the reception of SSB symbols is configured on the slot configured with the SBFD symbols so that all UL transmissions have a lower priority (deferralize) compared to SSB transmissions, then the slot configured with the SSB symbols can be considered a DL slot. For example, if an SSB symbol is included within an SBFD slot, the SBFD slot can be considered a DL slot. By considering the slot configured with SSB symbols as a DL slot, the SBFD-aware UE can perform reception of downlink signals and channels configured semi-statically or dynamically scheduled by the base station for the terminal in that slot, regardless of whether a UL subband is configured in that slot. This prevents the waste of resources configured for the UL subband. In addition, since legacy terminals consider the corresponding slot as a DL slot according to TDD-UL-DL-ConfigCommon, no issues arise regarding coexistence with legacy terminals. However, only slots having cell-specifically configured SSBs are considered as slots that can be regarded as DL slots, so that reception of downlink signals and channels semi-statically configured or dynamically scheduled by the base station can be performed in the corresponding slot regardless of whether a UL subband is configured in that slot. Here, the downlink signal includes a CSI-RS (channel state information reference signal) or a PDSCH. For example, a semi-statically configured downlink signal includes a CSI-RS or a SPS (semi-static scheduling) PDSCH.

[0175] Therefore, if a cell-specific SSB is set in the SBFD slot / symbol, the terminal can receive downlink signals / channels within the UL subband (or UL usable PRBs). On the other hand, if a cell-specific SSB is not set in the SBFD slot / symbol, the terminal can receive downlink signals / channels only outside the UL subband (or UL usable PRBs).

[0176] Here, a slot considered as a DL slot may be a slot containing an SBFD symbol (e.g., a DL / flexible symbol configured with a UL subband). However, if a slot with a UE-specific SSB is also considered as a DL slot, cross-link interference (inter-UE CLI) may occur between SBFD-aware UEs; therefore, in a slot with a UE-specific SSB, the terminal may be required to receive downlink signals and channels only within the SBFD DL subband (or DL ​​usable PRBs). Even though conversion from an SBFD symbol or slot to a non-SBFD symbol or slot is not permitted through dynamic signaling "SFI in DCI format 2_0," considering that cell-specific SSB configuration is set as RRC signaling, utilizing a slot with a cell-specific SSB as a DL slot may be desirable in terms of efficient resource usage.

[0177] For example, in the case where a cell-specific SSB is configured in FIG. 18, slots #10 / #12 can both be considered as DL slots regardless of the configuration of the UL subband. In this case, the terminal can receive downlink signals and channels that the base station has semi-statically configured or dynamically scheduled for the terminal in slots #10 / #12, regardless of whether the UL subband is configured in slots #10 / #12. However, in the case where a UE-specific SSB is configured in FIG. 18, the terminal can be configured so that it cannot receive downlink signals and channels in the UL subband, taking into account the UL subband configuration in slots #10 / #12, and can be configured to receive downlink signals and channels only within the DL subband (or DL ​​usable PRBs).

[0178] As an example of a cell-specific SSB in the present invention, an SSB set by ssb-PositionsInBurst of SIB1 or by ssb-PositionsInBurst of ServingCellConfigCommon may be considered as a cell-specific SSB, and all other SSBs may be considered as UE-specific SSBs.

[0179] Additionally, as an example of a UE-specifically set SSB in the present invention, an SSB set by ssb-ToMeasure or an SSB set by ssb-PositionsInBurst within SSB-MTCAdditionalPCI may be considered, and additionally, an SSB set by ssb-PositionsInBurst within SSB-MTCAdditionalPCI that is not associated with a serving cell ID may be considered.

[0180] PRACH transmission power control by SBFD aware-UE

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

[0182] - Method for configuring RO in Idle / inactive mode or RRC connected mode, and method for setting RO on the terminal

[0183] The present invention proposes a method for setting RO for a terminal in idle mode, inactive mode, or RRC connected mode when the terminal receives a plurality of subbands in the frequency domain semi-statically or dynamically for a downlink section and / or flexible section that is semi-statically or dynamically instructed by a base station, or when the uplink subband is semi-statically or dynamically instructed.

[0184] As a first embodiment, when a terminal receives multiple subbands in the frequency domain semi-statically or dynamically for a downlink segment and / or flexible segment that is semi-statically configured or dynamically instructed by a base station, or receives multiple uplink subbands semi-statically or dynamically instructed, a method may be considered to configure the 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. Here, the terminal supporting subband operation may support multiple subband operations in the frequency domain. FIGS. 15 and 16 illustrate upper layer (e.g., RRC) information used to configure RO in a legacy NR system. FIGS. 15 and 16 represent Rach-ConfigCommon information and Rach-ConfigGeneric information, respectively, 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).

[0185] In this case, ROs for terminals supporting subband operation can be configured without additional handling by utilizing the RO configuration set in the flexible section or uplink section of the legacy NR system as is. In this case, any RO that overlaps wholly or partially on the frequency axis with the downlink subband configured in the downlink section may be considered invalid. That is, ROs configured outside the UL subband (i.e., UL usable RBs) in the SBFD symbol may be determined as invalid ROs. However, this may make the configuration of ROs in the uplink subband configured in the downlink section inefficient. To compensate for this, the following measures may be considered.

[0186] In one embodiment, the present invention provides a method for configuring RO from the starting RB index of the uplink subband for a downlink section and / or a flexible section configured with an uplink (U) subband, that is, the starting position of RO on the frequency axis in the downlink section configured with an uplink subband is configured such that, regardless of the setting of msg-1-FrequencyStart configured in legacy Rach-ConfigGeneric, the offset of the lowest PRACH transmission opportunity on the frequency (hereinafter msg-1-FrequencyStart_SBFD) is set from the starting RB index to which the uplink subband is allocated (e.g., lowest RB index, RB#0), thereby allowing the corresponding RACH resources to 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 an SBFD slot / symbol, msg-1-FrequencyStart can be interpreted as an offset value set based on the starting 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, if a guard band is required to account for interference between subbands in the frequency domain between the downlink subband and the uplink subband, 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 that offset so that RACH resources are allocated.

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

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

[0189] 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

[0190] In another embodiment, FIG. 20 illustrates a method for configuring RO that is common to both a terminal that does not recognize SBFD operation (hereinafter, legacy terminal) and a terminal that recognizes SBFD operation (hereinafter, SBFD terminal). FIG. 20 illustrates a method for setting the starting position of the RO on the frequency axis for the SBFD terminal according to the BW ratio of the UL BWP and the UL subband. The starting position of the RO on the frequency axis for the SBFD terminal can be set based on msg-1-FrequencyStart within the Rach-ConfigGeneric of the legacy NR system, the BW size of the UL BWP, and the BW size of the UL subband. For example, the RO offset (RO_offset_SBFD) for the SBFD terminal can be set by the following formula. RO_offset_SBFD is calculated from the starting RB index of the UL subband.

[0191] - RO_offset_SBFD = floor (RO_offset * UL subband_size / UL BWP_size)

[0192] Here, RO_offset represents msg1-FrequencyStart, UL BWP_size represents the BW size of UL BWP, and UL subband_size represents the BW size of UL subband.

[0193] Referring to FIG. 20, an RO with a starting RB index can be set from an RB located at a distance of RO_offset_SBFD from the starting RB index of the uplink subband. For example, assume that the BW size of the UL BWP (UL BWP_size) is 100 RBs and msg1-FrequencyStart (i.e., RO_offset) is 10 RBs. In this case, the offset of the RO for the SBFD terminal (RO_offset_SBFD) can be set to 2 RBs when the BW size of the uplink subband (UL subband_size) is 20 RBs. Accordingly, an RO with a starting RB index can be set from an RB located at a distance of 2 RBs from the starting RB index of the uplink subband. In cases where a guard band is required due to 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 RO can be set starting from the RB index of the uplink subband after the offset so that RACH resources are allocated.

[0194] Referring to FIG. 21, when adjusting the starting position of the RO using the methods above so that the location of the RO for the SBFD terminal can be allocated within the uplink subband, the legacy RO may be set in the flexible slots / symbols and UL slots / symbols. In this case, even if the uplink subband is configured in the flexible slots / symbols, the adjustment of the starting position of the RO for the SBFD terminal may not be performed in the flexible slots / symbols where the legacy RO is set. This is because, as the RO set in the flexible slots / symbols differs between the legacy terminal and the SBFD terminal, when the terminal transmits a PRACH preamble from the valid RO according to the SSB-to-RO mapping (or association), ambiguity may arise in the mapping of the SSB associated with the RO at the base station, which may cause problems during the initial connection or uplink synchronization process.

[0195] Additionally, referring to FIG. 22, when adjusting the starting position of the RO using the above methods so that the position of the RO for the SBFD terminal can be allocated within the uplink subband, the legacy RO may be set only in the UL slot / symbol. If the uplink subband is configured in the flexible slots / symbols, the adjustment of the starting position of the RO for the SBFD terminal may be performed in the flexible slots / symbols. However, the adjustment of the starting position of the RO for the SBFD terminal may be performed under the assumption that the RO according to the PRACH configuration information in the time domain is set in the corresponding slots / symbols. That is, the example in FIG. 22 can be said to be a case where the RO according to the PRACH configuration information is set in all slots. According to this, since the RO set in the flexible slots / symbols between the legacy terminal and the SBFD terminal cannot be different, when the terminal transmits a PRACH preamble from a valid RO according to the SSB-to-RO mapping (or association), no ambiguity occurs in the mapping of the SSB associated with the RO at the base station, so no problem can occur during the initial connection or uplink synchronization process.

[0196] As a second embodiment, when a terminal receives a plurality of subbands in the frequency domain semi-statically or dynamically for a downlink / flexible slot or symbol(s) that is 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 setting an RO within an uplink subband may be considered by independently configuring Rach-ConfigCommon-r19 or Rach-ConfigGeneric-r19 for a terminal that supports subband operation in the frequency domain, in addition to Rach-ConfigCommon or Rach-ConfigGeneric configured for RO configuration in a flexible / uplink slot or symbol(s) in an existing legacy NR system. However, the following method may be considered for the terminal to receive two independent RO configuration information (e.g., legacy Rach-ConfigCommon and Rach-ConfigCommon-r19) to set an RO.

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

[0198] When configuring an RO using a new RACH configuration (e.g., Rach-ConfigCommon-r19, Rach-ConfigGeneric-r19) in a downlink / flexible slot or symbol(s) (i.e., SBFD slot / symbol interval) where an uplink subband is configured as described above, an RO can also be configured by the new RACH configuration in a flexible / uplink slot or symbol(s) (i.e., non-SBFD slot / symbol interval) where an uplink subband is not configured. For convenience, the RO configured by the new RACH configuration is referred to as the new RO (or SBFD RO). In this case, in the flexible / uplink slot or symbol(s) where an uplink subband is not configured, the corresponding RO (new RO) can be set as an invalid RO, and the validity of the RO based only on the legacy RO configuration can be determined (see Fig. 18). The RO configuration based on the new RACH configuration is intended for downlink / flexible slots or symbol(s) where an uplink subband is configured; therefore, for flexible / uplink slots or symbol(s) where an uplink subband is not configured, the legacy RO configuration is used identically for both legacy terminals and SBFD terminals. In summary, an RO for a terminal supporting SBFD operation can be configured in both SBFD and non-SBFD segments in the time domain according to the RACH configuration. In this case, an SBFD RO configured in a non-SBFD segment is determined to be an invalid RO, while the validity of an SBFD RO configured in an SBFD segment can be determined. In the non-SBFD segment, the validity of the RO based on the legacy RO configuration can be determined.

[0199] 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 the uplink subband, and Rach-ConfigCommon-r19 or Rach-ConfigGeneric-r19 may be used for RO configuration in downlink / flexible slots or symbol(s) where the uplink subband is configured.

[0200] When configuring an RO using a new RACH configuration (e.g., Rach-ConfigCommon-r19 or Rach-ConfigGeneric-r19) in a downlink / flexible slot or symbol(s) (i.e., SBFD slot / symbol interval) where an uplink subband is configured as described above, an RO can also be configured by the new RACH configuration in a flexible / uplink slot or symbol(s) (i.e., non-SBFD slot / symbol interval) where an uplink subband is not configured. For convenience, the RO configured by the new RACH configuration is referred to as the new RO (or SBFD RO). In this case, in the flexible / uplink slot or symbol(s) where an uplink subband is not configured, the corresponding RO (new RO) can be set as an invalid RO, and the validity of the RO based only on the legacy RO configuration can be determined (see Fig. 18). The RO configuration based on the new RACH configuration is intended for downlink / flexible slots or symbol(s) where an uplink subband is configured; therefore, for flexible / uplink slots or symbol(s) where an uplink subband is not configured, the legacy RO configuration is used identically for both legacy terminals and SBFD terminals. In summary, an RO for a terminal supporting SBFD operation can be configured in both SBFD and non-SBFD segments in the time domain according to the RACH configuration. In this case, an SBFD RO configured in a non-SBFD segment is determined to be an invalid RO, while the validity of an SBFD RO configured in an SBFD segment can be determined. In the non-SBFD segment, the validity of the RO based on the legacy RO configuration can be determined.

[0201] FIG. 23 illustrates a method of setting an RO as an invalid RO when an RO is configured by the PRACH configuration index of the new RACH configuration in an uplink / flexible slot or symbol(s) where an uplink subband is not configured. FIG. 23(a) illustrates setting an RO according to the new RACH configuration as an invalid RO in an uplink slot or symbol(s) where a subband is not configured (see RO #3). FIG. 23(b) illustrates setting an RO according to the new RACH configuration as an invalid RO in a flexible / uplink slot or symbol(s) where a subband is not configured (see RO #2 / #3). In the figure, D represents a downlink slot / symbol, S represents a flexible slot / symbol, and U represents an uplink slot / symbol.

[0202] Third, Legacy Rach-ConfigCommon or Rach-ConfigGeneric is used for RO configuration in flexible / uplink slots or symbol(s) as in the existing legacy method, regardless of the configuration of the uplink subband, and Rach-ConfigCommon-r19 or Rach-ConfigGeneric-r19 can be used for RO configuration in downlink slots or symbol(s) where the uplink subband is configured. That is, legacy RACH configuration is used for RO configuration in flexible / uplink slots or symbol(s), and new RACH configuration can be used for RO configuration in SBFD time intervals.

[0203] When configuring an RO using a new RACH configuration (e.g., Rach-ConfigCommon-r19, Rach-ConfigGeneric-r19) in a downlink slot or symbol(s) configured with an uplink subband as described above, an RO (i.e., a new RO) can be configured by the new RACH configuration in the flexible / uplink slot or symbol(s) as well, regardless of the uplink subband configuration. In this case, the new RO in the flexible / uplink slot or symbol(s) can be set as an invalid RO to determine only the validity of the RO based on the legacy RO configuration. Since the RO configuration by the new RACH configuration is an RO configuration intended only for downlink slots or symbol(s) configured with an uplink subband, the legacy RO configuration set in the flexible / uplink slot or symbol(s) is intended to be used identically for both legacy terminals and SBFD terminals, regardless of the uplink subband configuration.

[0204] As a third embodiment, a terminal may receive multiple subbands semi-statically or dynamically in the frequency domain for downlink / flexible slots or symbol(s) that are semi-statically configured or dynamically instructed by a base station, or may receive uplink subbands semi-statically or dynamically instructed. In this case, in addition to Rach-ConfigCommon or Rach-ConfigGeneric for configuring RO in flexible / uplink slots or symbol(s) in existing legacy NR systems, a method may be considered to independently configure a new RACH configuration (e.g., Rach-ConfigCommon-r19, Rach-ConfigGeneric-r19) for terminals supporting SBFD operation to configure RO within the uplink subband. The following method may be considered for the terminal to receive two independent configurations to set the configured RO and the valid RO.

[0205] A terminal capable of recognizing SBFD operation (i.e., an SBFD aware UE, simply an SBFD terminal) can configure an RO (i.e., an SBFD RO) by independently receiving a new RACH configuration (e.g., Rach-ConfigCommon-r19, Rach-ConfigGeneric-r19) to configure an RO within a downlink / flexible slot or symbol(s) in which an uplink subband is additionally configured, in addition to legacy ROs. At this time, the RO may be configured within a non-SBFD section (e.g., a flexible / uplink slot or symbol(s)) by the new RACH configuration information (e.g., a PRACH configuration index). If an RO is configured by the new RACH configuration in a flexible / uplink slot or symbol(s) in which a subband is not configured, a method may be considered for the terminal to determine the validity of the RO (i.e., an SBFD RO) according to the legacy method (see FIG. 18). This can be advantageous in that terminals capable of performing SBFD operations can increase PRACH transmission coverage. However, if a new RO is additionally configured by a new RACH configuration in the same slot or symbol(s) as a valid RO configured by a legacy RACH configuration, and the new RO is determined to be valid according to the existing legacy method, when mapping an SSB index to the new valid RO, the same SSB index mapped to the legacy valid RO can be set. This is intended to allow the base station to receive signals by setting an Rx beam corresponding to the same SSB index when setting an Rx beam for valid ROs configured in the same slot or symbol(s). Additionally, it may be possible to distinguish between legacy terminals and SBFD-aware terminals depending on which resource the base station receives PRACH from where the valid RO is configured.

[0206] FIG. 24 illustrates a method of setting a corresponding RO as a valid RO when the RO is configured by the new RACH configuration in an uplink (U) slot or symbol(s) or flexible (S) slot or symbol(s) where the uplink subband is not configured according to the above method. FIG. 24(a) illustrates setting the RO configured by the new RACH configuration in an uplink slot or symbol(s) where the subband is not configured as a valid RO after a validity check (see RO #3). Refer to FIG. 18 for the validity check. FIG. 24(b) illustrates setting the RO configured by the new RACH configuration in a flexible / uplink slot or symbol(s) where the subband is not configured as a valid RO after a validity check (see RO #2 / #3). In the figure, D represents a downlink slot / symbol, S represents a flexible slot / symbol, and U represents an uplink slot / symbol.

[0207] As a fourth embodiment, terminals capable of recognizing SBFD operations (i.e., SBFD aware UEs) may independently receive a new RACH configuration (e.g., Rach-ConfigCommon-r19, Rach-ConfigGeneric-r19) to configure an RO within a downlink slot / symbol(s) or flexible slot / symbol(s) in which an uplink subband is additionally configured, in addition to legacy configured ROs. At this time, the RO may be configured within a non-SBFD section (e.g., flexible / uplink slot or symbol(s)) by the new RACH configuration information (e.g., PRACH configuration index). When an RO (i.e., SBFD RO) is configured by the new RACH configuration in a flexible / uplink slot or symbol(s) in which a subband is not configured, a method may be considered for the terminal to determine the validity of the RO configured in the corresponding slot or symbol(s) (i.e., non-SBFD section) according to the legacy method (see FIG. 18). Additionally, a method may be considered to increase coverage, which is one of the primary purposes of SBFD operations, by transmitting a (long) PRACH format over consecutive slots when performing SBFD operations. To this end, transmission of the (long) PRACH format may be enabled by determining the RO as valid only when the RO is configured (consequently) across SBFD slot / symbol(s) and non-SBFD slot / symbol(s) in the time domain by a new RACH configuration (e.g., PRACH configuration index). That is, if the RO is configured in non-SBFD slot / symbol(s) by a new RACH configuration, the RO may be determined as valid only when it is configured (consequently) across SBFD slot / symbol(s) and non-SBFD slot / symbol(s) in the time domain (in addition to pre-defined RO validity conditions).Here, the predefined RO validity conditions may include gap-based validity conditions, for example, validity conditions based on the gap interval with a specific symbol. The specific symbol may include the last DL symbol and / or the last symbol of the SSB. The predefined RO validity conditions may include legacy RO validity conditions (see FIG. 18). Meanwhile, the validity determination of an RO configured in an SBFD slot / symbol(s) may be performed based on the SBFD RO validity conditions of this specification. For example, the SBFD RO validity conditions may be referenced in FIG. 29–32. Since the gap-based validity conditions are determined based on the starting symbol position of the RO, the validity determination of an RO configured consecutively across an SBFD slot / symbol(s) and a non-SBFD slot / symbol(s) may be performed based on the SBFD RO validity conditions.

[0208] However, when an additional RO (new RO) is configured according to the new RACH configuration and the RO is determined to be valid according to the existing legacy method (new valid RO), the new valid RO may partially or wholly overlap with the slot / symbol(s) occupied by the valid RO (legacy valid RO) configured by the legacy RACH configuration. In this case, when mapping an SSB index to the new valid RO, the SSB index mapped to the legacy RO can be set identically to the new RO. This is intended to allow the base station to receive the Rx beam corresponding to the same SSB index when setting an Rx beam for ROs configured in the same or partially overlapping slot / symbol(s). Additionally, it may be possible to distinguish between legacy terminals and SBFD-aware terminals depending on which resource the base station receives the PRACH from where the RO is configured.

[0209] FIG. 25 illustrates a method of setting a new RO as a valid RO when the RO is configured by a new RACH configuration (e.g., PRACH configuration index) in a flexible / uplink slot or symbol(s) where the uplink subband is not configured according to the above method. In the figure, D represents a downlink slot / symbol, S represents a flexible slot / symbol, and U represents an uplink slot / symbol. FIG. 25(a) illustrates setting the RO as an invalid RO after performing a validity check (e.g., legacy validity check; see FIG. 18) on an RO configured by the new RACH configuration in an uplink slot / symbol(s) where the subband is not configured, and determining whether the RO was configured continuously in the time axis. Specifically, referring to FIG. 25(a), the RO configured by the new RACH configuration can be configured in an uplink slot / symbol (RO #3). At this time, RO #3 is determined to be an invalid RO because it is configured only in a non-SBFD symbol (U). FIG. 25(b) shows that a RO configured by the new RACH configuration in a flexible / uplink slot or symbol(s) where the subband is not configured is set as a valid RO after a validity check and a determination of whether the RO is configured continuously in the time axis. Specifically, referring to FIG. 25(a), the RO configured by the new RACH configuration can be configured in an uplink slot / symbol (RO #3). At this time, since RO #3 is configured continuously across an SBFD symbol (S) and a non-SBFD symbol (U), it can be determined as a valid RO (depending on the RO validity check result).

[0210] FIG. 26 illustrates a case where a PRACH opportunity (i.e., RO) is allocated to a frequency resource different from the SSB and partially overlaps in the time domain in a downlink slot or symbol(s) or a flexible slot or symbol(s) configured with an uplink subband. FIG. 26(a) illustrates a case where an uplink subband is configured in a downlink slot or symbol(s), and the SSB and RO overlap in the time domain on a downlink symbol configured with an uplink subband. FIG. 26(b) illustrates a case where an uplink subband is configured in a downlink slot or symbol(s) or a flexible slot or symbol(s), and the SSB and RO overlap in the time domain on a flexible symbol configured with an uplink subband. Here, the SSB is used in combination with the SS / PBCH block.

[0211] As shown in FIG. 26, a new RO (new RO) can be configured by a new RACH configuration in a downlink slot or symbol(s) or a flexible slot or symbol(s) configured with an uplink subband. In this case, the configured RO and the SSB are allocated from different frequency resources but may partially or entirely overlap in the time domain. At this time, the following method may be considered to check the validity of the configured RO. First, since a terminal performing half-duplex operation cannot simultaneously perform SSB reception and PRACH transmission, the terminal may perform SSB reception and set the RO that partially or entirely overlaps with the SSB reception in the time domain as an invalid RO. Here, SSB reception may be limited to SSB reception that is essential from the perspective of the terminal. For example, the SSB indicated by the cell common signal ServingCellConfigCommonSIB or the RRC parameter ssb-PositionsInBurst within ServingCellConfigCommon must be received by all terminals. Accordingly, for an SSB indicated by ssb-PositionsInBurst, the terminal performs SSB reception and may set an RO that partially or entirely overlaps with the SSB reception in the time domain as an invalid RO. However, in the case of an RO that partially or entirely overlaps with the reception of an SSB set other than the reception position of the SSB indicated by ssb-PositionsInBurst in the time domain, the terminal may set the RO as a valid RO (after checking validity). In this case, the terminal may skip the SSB reception that overlaps with the RO.This is intended to prioritize the reception of an SSB that is commonly configured from a base station for all terminals belonging to a cell, as such reception may be essential for all terminals to perform synchronization via the SSB and RRM (radio resource management) measurements.

[0212] As an example of SSB reception, there may be a symbol for which SSB reception is configured within an SMTC (SSB-based measurement timing configuration) specifically configured for the terminal. In addition to initial cell connection and cell information acquisition, the terminal may be configured to additionally receive SSBs from the base station within a terminal-specific (UE-specific) SMTC window to measure downlink channel conditions received from serving cells and neighboring cells. In this case, the terminal may set a RO that partially or entirely overlaps with the corresponding SSB reception in the time domain as a valid RO.

[0213] As another example of SSB reception, when SSB reception is established from multiple TRPs (transmission and reception points), the terminal may set a RO that partially or entirely overlaps with the reception of the SSB in the time domain as a valid RO.

[0214] As another example of receiving an SSB, when receiving a symbol configured for receiving an SSB from the plurality of TRPs, and when the terminal is configured to receive an SSB from the TRP of a serving cell or a neighboring cell, the terminal may set an RO that partially or entirely overlaps with the reception of the SSB in the time domain as a valid RO.

[0215] As another example regarding the reception of an SSB, when the reception of an SSB is configured by receiving a symbol from the plurality of TRPs mentioned above, if the SSB received by the terminal is identical to the PCI of the serving cell, the terminal may prioritize the reception of the SSB by setting the RO that partially or entirely overlaps with the reception of the said SSB in the time domain as an invalid RO. In other cases, that is, if the reception of an SSB having a PCI different from the PCI of the serving cell is configured from the TRP of the serving / neighboring cell, the terminal may set the RO that partially or entirely overlaps with the reception of the said SSB in the time domain as a valid RO.

[0216] Below, the method for checking the validity of RO is further explained.

[0217] 1. This relates to a method for a terminal to perform a validity check of an RO in a PRACH slot configured for the terminal, considering gap symbols even after the SBFD-DL symbol, in the case of an SBFD-DL symbol (configured as DL by tdd-UL-DL-ConfigurationCommon). When ROs are configured continuously after SBFD-DL symbols, a method for determining the validity of a configured RO is proposed as follows.

[0218] In a first embodiment, a configured RO starting at least after a gap following the SBFD-DL symbols can be determined as a valid RO. This is because when a DL channel / signal is transmitted from a base station to a terminal in the DL subband on the SBFD-DL symbols, the terminal performs a half-duplex operation, and thus a gap may be required to perform UL transmission in the RO after DL reception in the DL subband on the SBFD-DL symbols. Therefore, a configured RO starting at least after a gap following the SBFD-DL symbols can be set as a valid RO.

[0219] In another embodiment, since reception of a DL channel / signal in the DL subband on the SBFD-DL symbols may not always occur from the perspective of a terminal, if the terminal is not scheduled or configured to receive a DL channel / signal in the DL subband on the SBFD-DL symbols prior to the start symbol of the configured RO, the terminal may determine the configured RO as a valid RO regardless of the gap. In other words, if the terminal is scheduled or configured to receive a DL channel / signal in the DL subband on the SBFD-DL symbols prior to the start symbol of the configured RO, the terminal may set the configured RO starting at least after the gap as a valid RO. That is, for a terminal performing a half-duplex operation, a gap may be required to perform UL transmission after the DL reception when there is DL reception, but UL transmission can be performed regardless of the gap when DL reception is not required.

[0220] As another embodiment, from the perspective of a terminal, the terminal may be scheduled or configured to perform transmission of a UL channel / signal to a base station immediately before the start symbol of the configured RO in the UL subband configured in the SBFD-DL symbols. In this case, from the perspective of a terminal performing half-duplex operation, since the terminal performs UL transmission through the configured RO continuously with the UL transmission in the UL subband on the SBFD-DL symbol prior to the start symbol of the RO configured to the terminal, a gap may not be required to perform UL transmission after the DL reception. Therefore, in such cases, the configured RO can be determined as a valid RO regardless of the gap.

[0221] 1-1. This invention relates to a method for a terminal to perform a validity check of an RO in a PRACH slot configured for the terminal, taking into account the gap between DL reception and UL transmission, in the case of SBFD-DL symbols (configured as DL by tdd-UL-DL-ConfigurationCommon) where an additional SSB is configured on the SBFD-DL symbols. A method is proposed to determine the validity of a configured RO when an RO is configured continuously after the SBFD-DL symbols.

[0222] FIG. 27 illustrates a case where the PRACH opportunity (RO) for the SBFD-aware terminal and the SSB are assigned to different frequency resources and do not overlap in the time domain in a downlink slot or symbol(s) or flexible slot or symbol(s) configured with a UL subband.

[0223] In the first embodiment, as shown in FIG. 27(a), a configured RO that starts at least after the last symbol of the SSB configured on the SBFD-DL symbols can be determined as a valid RO. This is because when an SSB transmission from a base station to a terminal occurs in the DL subband on the SBFD-DL symbols, the terminal performs a half-duplex operation, so a gap may be required to perform UL transmission in the RO after receiving the SSB. Therefore, a configured RO that starts at least after the last symbol of the SSB configured on the SBFD-DL symbols can be set as a valid RO.

[0224] As another embodiment, as shown in FIG. 27(a), the reception of an SSB configured on SBFD-DL symbols from the perspective of a terminal may not always be present at that terminal. Therefore, if the SSB configured on SBFD-DL symbols prior to the start symbol of the RO configured for the terminal is not required to be received by the terminal on the DL subband, the terminal may determine the configured RO as a valid RO regardless of the gap. On the other hand, if the terminal receives an SSB configured on the DL subband of SBFD-DL symbols prior to the start symbol of the configured RO, the configured RO starting at least after the gap may be set as a valid RO. That is, for a terminal performing a half-duplex operation, if there is an SSB reception, a gap may be required to perform UL transmission after the SSB reception, but if an SSB reception is not required, UL transmission can be performed regardless of the gap.

[0225] As another embodiment, as shown in FIG. 27(a), a method may be used in which a terminal determines the validity of a subsequently configured RO differently depending on the reception type of the SSB configured on the SBFD-DL symbols from the perspective of a single terminal. For example, a method may be considered in which the validity of the configured RO is determined differently depending on the SSB reception type configured commonly by the cell and the SSB reception type configured specifically by the UE. For SSB reception configured commonly by the cell, a configured RO that starts at least after the gap from the last symbol of the SSB may be determined as a valid RO, as in the first embodiment above. Otherwise, that is, if the gap between the preceding SSB and the configured RO is not guaranteed, the terminal may determine the configured RO as an invalid RO. In the case of SSB reception configured specifically by the UE, the priority of the SSB reception may be considered low, and the configured RO may be determined as a valid RO regardless of the gap between the preceding SSB and the configured RO. SSBs configured for the cell common include SSBs indicated by the RRC parameter ssb-PositionsInBurst configured within ServingCellConfigCommonSIB or ServingCellConfigCommon. SSBs configured for the UE specific may include SSBs indicated by the RRC parameter ssb-PositionsInBurst-r17 configured within SSB-MTC-AdditionalPCI-r17 and the RRC parameter SSB-ToMeasure.

[0226] In another embodiment, as shown in FIG. 27(b), if SSB reception on SBFD-DL symbols is configured after the configured RO, the configured RO can be set as a valid RO if at least the configured RO does not overlap with the SSB in the time and frequency axes. In the case of FIG. 27(b), since a gap for performing UL transmission and DL reception may not typically be required, the terminal can determine the configured RO as a valid RO.

[0227] As another embodiment, as shown in FIG. 27(b), when SSB reception on SBFD-DL symbols is configured after the configured RO, the Tx-Rx transition time defined in legacy NR may be required even if the configured RO does not overlap with the SSB in the time and frequency axes. Accordingly, the validity of the configured RO can be determined by setting a gap to the smallest number of symbols longer than the transition time, and determining whether the last symbol of the configured RO precedes the starting symbol of the SSB in the time domain by at least a gap. For example, if the last symbol of the configured RO precedes the starting symbol of the SSB in the time domain by at least a gap, the terminal can set the configured RO as an invalid RO, and otherwise, the terminal can set the configured RO as a valid RO.

[0228] Table 6 shows the transition times for Tx-Rx as defined in legacy NR. Here, the unit of the transition time is Tc.

[0229] Transition timeFR1FR2N TX-RX 2560013792N RX-TX 2560013792

[0230] As another embodiment, when SSB reception on SBFD-DL symbols is configured after the configured RO as in FIG. 27(b), the SSB to which the method of the above embodiments applies may be limited to an SSB configured commonly by the cell. That is, the method of the above embodiments may not be applied to an SSB configured specifically by the UE. For example, if the SSB in FIG. 27(b) is an SSB configured commonly by the cell, the terminal may determine the validity of the configured RO by considering the gap between the configured RO and the SSB reception. On the other hand, if the SSB in FIG. 27(b) is an SSB configured specifically by the terminal, the terminal may determine the configured RO as a valid RO without considering the gap with the SSB reception.

[0231] 2. This relates to a method for a terminal to perform a validity check of an RO in a PRACH slot configured for the terminal, considering gap symbols even after SBFD-FL symbols, as in the case of SBFD-FL symbols (configured as flexible by tdd-UL-DL-ConfigurationCommon). A method is proposed to determine the validity of a configured RO when ROs are configured consecutively after SBFD-FL symbols.

[0232] In a first embodiment, a configured RO starting at least after a gap following the SBFD-FL symbols can be determined as a valid RO. This is because when a DL channel / signal is transmitted from a base station to a terminal in the DL subband on the SBFD-FL symbols, the terminal performs a half-duplex operation, and thus a gap may be required to perform UL transmission in the RO after receiving the DL in the DL subband on the SBFD-FL symbols from the base station. Therefore, a configured RO starting at least after a gap following the SBFD-FL symbols can be set as a valid RO.

[0233] In another embodiment, since reception of a DL channel / signal in the DL subband on the SBFD-FL symbols may not always occur from the perspective of a terminal, if the terminal is not scheduled or configured to receive a DL channel / signal in the DL subband on the SBFD-FL symbols prior to the start symbol of the configured RO, the terminal may determine the configured RO as a valid RO regardless of the gap. In other words, if the terminal is scheduled or configured to receive a DL channel / signal in the DL subband on the SBFD-FL symbols prior to the start symbol of the configured RO, the terminal may set the configured RO starting at least after the gap as a valid RO. That is, for a terminal performing a half-duplex operation, a gap may be required to perform UL transmission after the DL reception when there is DL reception, but UL transmission can be performed regardless of the gap when DL reception is not required.

[0234] As another embodiment, from the perspective of a terminal, the terminal may be scheduled or configured to perform transmission of a UL channel / signal to a base station immediately before the start symbol of the configured RO in the UL subband configured in the SBFD-FL symbols. In this case, from the perspective of a terminal performing half-duplex operation, since the terminal performs UL transmission through the configured RO continuously with the UL transmission in the UL subband on the SBFD-FL symbol prior to the start symbol of the RO configured to the terminal, a gap may not be required to perform UL transmission after receiving the DL. Therefore, in such cases, the configured RO can be determined as a valid RO regardless of the gap.

[0235] 2-1. This relates to a method for a terminal to perform a validity check of an RO in a PRACH slot configured for the terminal, considering the gap between DL reception and UL transmission, when an additional SSB is configured on SBFD-FL symbols as a case of SBFD-FL symbols (configured as flexible by tdd-UL-DL-ConfigurationCommon). A method is proposed to determine the validity of a configured RO when an RO is configured and received consecutively after SBFD-FL symbols.

[0236] In the first embodiment, as shown in FIG. 27(a), a configured RO that starts at least after a gap following the last symbol of the SSB configured on the SBFD-FL symbols can be determined as a valid RO. This is because when an SSB transmission from a base station to a terminal occurs in the DL subband on the SBFD-FL symbols, the terminal performs a half-duplex operation, so a gap may be required to perform UL transmission in the RO after receiving the SSB. Therefore, a configured RO that starts at least after a gap following the last symbol of the SSB configured on the SBFD-FL symbols can be set as a valid RO.

[0237] In another embodiment, as shown in FIG. 27(a), the reception of an SSB configured on SBFD-FL symbols from the perspective of a terminal may not always be present at that terminal. Therefore, if the SSB configured on SBFD-FL symbols prior to the start symbol of the RO configured for the terminal is not required to be received by the terminal on the DL subband, the terminal may determine the configured RO as a valid RO regardless of the gap. On the other hand, if the terminal receives an SSB configured on the DL subband of SBFD-FL symbols prior to the start symbol of the configured RO, the configured RO starting at least after the gap may be set as a valid RO. That is, for a terminal performing a half-duplex operation, if there is an SSB reception, a gap may be required to perform UL transmission after the SSB reception, but if an SSB reception is not required, UL transmission can be performed regardless of the gap.

[0238] As another embodiment, as shown in FIG. 27(a), a method may be used in which a terminal determines the validity of a subsequently configured RO differently depending on the reception type of the SSB configured on the SBFD-FL symbols from the perspective of a single terminal. For example, a method may be considered in which the validity of the configured RO is determined differently depending on the SSB reception type configured commonly by the cell and the SSB reception type configured specifically by the UE. For SSB reception configured commonly by the cell, a configured RO that starts at least after the gap from the last symbol of the SSB may be determined as a valid RO, as in the first embodiment above. Otherwise, that is, if the gap between the preceding SSB and the configured RO is not guaranteed, the terminal may determine the configured RO as an invalid RO. In the case of SSB reception configured specifically by the UE, the priority of the SSB reception may be considered low, and the configured RO may be determined as a valid RO regardless of the gap between the preceding SSB and the configured RO. SSBs configured for the cell common include SSBs indicated by the RRC parameter ssb-PositionsInBurst configured within ServingCellConfigCommonSIB or ServingCellConfigCommon. SSBs configured for the UE specific may include SSBs indicated by the RRC parameter ssb-PositionsInBurst-r17 configured within SSB-MTC-AdditionalPCI-r17 and the RRC parameter SSB-ToMeasure.

[0239] In another embodiment, as shown in FIG. 27(b), if SSB reception on SBFD-FL symbols is configured after the configured RO, the configured RO can be set as a valid RO if at least the configured RO does not overlap with the SSB in the time and frequency axes. In the case of FIG. 27(b), since a gap for performing UL transmission and DL reception may not typically be required, the terminal can determine the configured RO as a valid RO.

[0240] As another embodiment, as shown in FIG. 27(b), when SSB reception on SBFD-FL symbols is configured after the configured RO, the Tx-Rx transition time defined in legacy NR may be required even if the configured RO does not overlap with the SSB in the time and frequency axes. Refer to Table 6 for the transition time for Tx-Rx defined in legacy NR. Accordingly, the validity of the configured RO can be determined by setting a gap to the smallest number of symbols longer than the transition time, and determining whether the last symbol of the configured RO precedes the starting symbol of the SSB in the time domain by at least a gap. For example, if the last symbol of the configured RO precedes the starting symbol of the SSB in the time domain by at least a gap, the terminal can set the configured RO as an invalid RO, and otherwise, the terminal can set the configured RO as a valid RO.

[0241] As another embodiment, when SSB reception on SBFD-FL symbols is configured after the configured RO as in FIG. 27(b), the SSB to which the method of the above embodiments applies may be limited to an SSB configured commonly by the cell. Meanwhile, the method of the above embodiments may not be applied to an SSB configured specifically by the UE. For example, if the SSB in FIG. 27(b) is an SSB configured commonly by the cell, the terminal may determine the validity of the configured RO by considering the gap between the configured RO and the SSB reception. On the other hand, if the SSB in FIG. 27(b) is an SSB configured specifically by the terminal, the terminal may determine the configured RO as a valid RO without considering the gap with the SSB reception.

[0242] FIG. 28 illustrates power control during PRACH preamble transmission. As described with reference to FIG. 14, the terminal can initiate a random access procedure by transmitting a PRACH preamble (Msg1) from the base station and receive a Random Access Response (RAR) (Msg2) from the base station. Meanwhile, if the terminal does not receive the RAR from the base station within a certain time after transmitting the PRACH preamble, the transmission of the PRACH preamble is considered a failure. In the event of a failure in transmitting the PRACH preamble, the terminal performs a retransmission of the PRACH preamble and can control the number of retransmissions of the PRACH preamble and the transmission power of the PRACH preamble using a ramping counter. When initiating the random access procedure, the terminal can start the ramping counter with a preset initial value (e.g., 1). Subsequently, the terminal can increase the value of the ramping counter by 1 each time it fails to receive the RAR. The terminal can increase the transmission power by a certain amount (step size) during the next PRACH preamble retransmission whenever the value of the ramping counter increases. Meanwhile, when the ramping counter reaches the maximum number of transmissions (e.g., preambleTransMax) (Max), the terminal can determine that the random access procedure has failed and start over from the beginning. Here, preambleTransMax can be set to the terminal through the System Information Block (SIB) of the base station (eNB or gNB).

[0243] Hereinafter, a method for a terminal capable of recognizing SBFD operation (i.e., an SBFD-aware UE) to perform transmission power control of a PRACH preamble is described. In the present invention, two methods were considered for RO configuration for PRACH transmission in a downlink / flexible slot or symbol(s) configured with an UL subband for an SBFD-aware UE. The first is a method of configuring configured RO(s) by setting msg1-FrequencyStart from the start of the uplink subband or from the start of the subband in order to configure msg1-FrequencyStart of the legacy RO configuration method within the uplink subband (see FIGS. 19–22). The second is a method that allows configured RO(s) to be configured within the uplink subband according to an additional RO configuration for RO configuration in a downlink / flexible slot or symbol(s) configured with an uplink subband, separate from the legacy RO configuration method (see FIGS. 23–26).

[0244] However, whether the first method or the second method is used, the SBFD aware UE may receive legacy ROs configured according to the legacy RO configuration and additional ROs configured by the first method or the second method. In performing an initial PRACH transmission or a re-attempt of an initial PRACH transmission in a single random access procedure, the SBFD aware UE may selectively use one of the following types of resources for the PRACH preamble transmission: 1) only legacy ROs, 2) only additional ROs, or 3) legacy ROs and additional ROs. If the SBFD aware UE uses resources configured with only one type of RO (e.g., only legacy ROs or only additional ROs) for the PRACH preamble transmission, the method used in the legacy NR system for setting the transmission power during the PRACH preamble transmission may be used in the same way.

[0245] In one embodiment, when only one type of RO (e.g., only legacy ROs or only additional ROs) is used and the first PRACH transmission fails, the terminal may increase the power ramping counter to increase the transmission power for the next PRACH retransmission and use the next level of higher transmission power for the retransmission of the PRACH preamble. However, if the terminal supports multiple beam operation, the power ramping counter is maintained without change when the terminal performs beam switching, and otherwise, the power ramping counter is increased and the next level of higher transmission power is used for the retransmission of the PRACH preamble.

[0246] In addition, when an SBFD-aware UE selectively uses one type of resource among the legacy ROs and additional ROs for PRACH preamble transmission based on a specific number of times, specific conditions, configured conditions, or priority, the method of setting transmission power during PRACH preamble transmission needs to be applied differently from the legacy method, and the following methods are proposed.

[0247] In one embodiment, since the resources of the legacy ROs and the resources of the additional ROs are configured independently in the time and frequency domains, the SBFD-aware UE may selectively use one type of resource among those configured as legacy ROs and additional ROs for PRACH preamble transmission. In this case, when setting the transmission power of the PRACH preamble, if switching occurs between ROs of different types while performing power ramping, the terminal may maintain the power ramping counter without incrementing it or making changes. For example, a method may be used to increment or reset the power ramping counter when PRACH preamble transmission occurs only within ROs of the same type, whether consecutively or discontinuously. Specifically, assume a case where the SBFD-aware UE configures legacy ROs and additional ROs and transmits a PRACH preamble. In this case, ROs are selected consecutively only from legacy ROs or only from additional ROs, and if PRACH preamble transmission fails at the preceding RO, the terminal may increment the power ramping counter to perform PRACH preamble transmission at the next RO. However, when different types of ROs are selected consecutively (e.g., from a legacy RO to an additional RO, or vice versa), the terminal may maintain the power ramping counter unchanged without incrementing it when transmitting the PRACH preamble. If the power ramping counter is incremented, the PRACH preamble is transmitted using the next higher transmission power. If the power ramping counter is maintained, the PRACH preamble is transmitted using the previous transmission power.

[0248] As another embodiment, at least separate power control parameters may be used for legacy ROs and additional ROs. This is because the resources of the legacy ROs and the resources of the additional ROs will be set as resources that do not overlap in the time and frequency domains independently. Additionally, when the terminal performs multi-beam operation, the transmission power according to each beam may be set differently; therefore, the power control parameters for the legacy ROs and the power control parameters for the additional ROs may be set at least separately according to each time and frequency domain and different beams. Accordingly, when power ramping for the retransmission of the PRACH preamble, the power ramping counter is adjusted only for ROs of the same type, and when switching RO resources to a different type of RO for the retransmission of the PRACH preamble, the terminal can maintain the power ramping counter without increasing it or changing it. When the RO resource selected for PRACH preamble transmission is switched to a different type of RO, if it is the first transmission of PRACH preamble using that type of RO resource within a single random access procedure, the initial PRACH transmission power for that type of RO can be set. Additionally, if the terminal performs multi-beam operation, when the terminal performs beam switching, the power ramping counter can be maintained without being increased or changed when ROs of the same type are continuously selected for PRACH preamble transmission. Otherwise (i.e., when ROs of the same type are continuously selected for PRACH preamble transmission without multi-beam operation), the power ramping counter is increased and the next higher transmission power can be used for the retransmission of the PRACH preamble.

[0249] In addition, when a terminal performs PRACH transmissions alternately according to specific conditions in validated ROs set for different symbol types (e.g., SBFD symbols, non-SBFD symbols) in a single random access procedure, it is necessary to define whether power ramping and the power ramping counter are incremented for the terminal's PRACH retry transmission.

[0250] Separate power control for PRACH transmission can be performed on RO resources configured with different symbol types (e.g., additional RO resources configured with SBFD symbols and legacy RO resources configured with non-SBFD symbols). Depending on specific conditions, when transmitting PRACH from a valid RO with a different symbol type for PRACH retry transmission, it may be desirable not to ramp power and leave the power ramping counter unchanged. On the other hand, when retransmitting PRACH from a valid RO with the same symbol type, power ramping may be performed and the power ramping counter may be incremented.

[0251] However, in determining the maximum number of times a terminal can perform power ramping for PRACH transmission from the perspective of a terminal, or the maximum value of the power ramping counter that a terminal can have, as one embodiment, the maximum value of the power ramping counter that a terminal can have for PRACH transmission from the perspective of a terminal may be integrated into a single value. For example, when PRACH is transmitted from a valid RO with a different symbol type for PRACH retry transmission according to specific conditions, power ramping is not performed and the power ramping counter is maintained without change, but the number of times power ramping can be performed in ROs of different types, namely "legacy ROs in non-SBFD symbol" and "additional ROs in SBFD symbol," may be integrated into a single value and managed. Since terminals that do not support SBFD manage a power ramping counter according to the maximum number of times power ramping is set for the terminal in the legacy RO, terminals that support SBFD can also maintain the same configuration as the legacy terminal, which may be desirable when different types of terminals coexist.

[0252] FIG. 29 illustrates a PRACH transmission according to an example of the present invention. FIG. 29 illustrates a case where the transmission of a PRACH preamble fails and the PRACH preamble is retransmitted.

[0253] Referring to FIG. 29, the terminal can retransmit the PRACH preamble at the RO set on the SBFD symbol (S2902). At this time, the transmission power of the PRACH preamble at the SBFD symbol can be ramped based on a first power control parameter. Additionally, the terminal can retransmit the PRACH preamble at the RO set on the non-SBFD symbol (S2904). At this time, the transmission power of the PRACH preamble at the non-SBFD symbol can be ramped based on a second power control parameter. Meanwhile, power control parameters for transmitting the PRACH preamble at the SBFD symbol and the non-SBFD symbol are set independently, but the maximum number of retransmissions of the PRACH preamble can be managed collectively within the terminal. Accordingly, when the sum of the number of power rampings performed at the RO on the SBFD symbol and the number of power rampings performed at the RO on the non-SBFD symbol reaches the maximum value set in the terminal, the terminal can determine that the random connection procedure has failed and start over from the beginning. Here, the maximum value (e.g., preambleTransMax) can be indicated through the base station's SIB and can be set to up to one for the terminal in relation to whether SBFD is configured.

[0254] As another embodiment, the maximum number of power ramps or the maximum value of the power ramp counter that a terminal can have for PRACH transmission from the perspective of a terminal can be configured independently for each type of RO set in different symbol types, namely "legacy ROs in non-SBFD symbol" and "additional ROs in SBFD symbol". When PRACH is transmitted from a valid RO of a different symbol type for PRACH retry transmission according to specific conditions, power ramping is not performed and the power ramp counter is maintained without change, but the number of times power ramping can be performed in ROs of different types, namely "legacy ROs in non-SBFD symbol" and "additional ROs in SBFD symbol", can be configured and used independently according to the RO set in different symbol types. In ROs configured with a non-SBFD symbol type, PRACH transmissions of legacy terminals, terminals that do not support SBFD, and terminals that support SBFD occur competitively according to a contention-based procedure, so terminals that support SBFD can maintain the same configuration as legacy terminals up to the maximum number of transmissions for power ramping used by legacy terminals, which may be desirable when different types of terminals coexist.

[0255] Although the method and system of the present invention have been described in relation to specific embodiments, some or all of their components or operations may be implemented using a computing system having a general-purpose hardware architecture.

[0256] The foregoing description of the present invention is for illustrative purposes only, and those skilled in the art will understand that other specific forms can be easily modified without altering the technical spirit or essential features 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 unit may be implemented in a distributed manner, and components described as distributed may likewise be implemented in a combined form.

[0257] The scope of the present invention is defined by the claims set forth below rather than by the detailed description above, and all modifications or variations derived from the meaning and scope of the claims and equivalent concepts thereof should be interpreted as being included within the scope of the present invention.

Claims

In a terminal configured to operate in a wireless communication system, Communication module; and It includes a processor that controls the above communication module, and The above processor is, Receive configurations for a non-overlapping subband full duplex (SBFD) symbol set and a non-SBFD symbol set within a wireless frame, wherein the SBFD symbol set includes DL (downlink) symbols or flexible symbols configured with an uplink (UL) subband, and It is configured to receive a DL signal in a slot containing an SBFD symbol, and If an SSB (synchronization signal / physical broadcast channel block) is configured on the symbols within the slot, the DL signal is allowed to be received in the slot and also in the UL subband, and If the SSB is not configured on the symbols within the slot, the DL signal is received only outside the UL subband in the slot. In paragraph 1, The above SSB is a terminal including a cell-specific SSB. In paragraph 2, The above cell-specific SSB is a terminal including an SSB configured by SIB1 (system information block 1) or ServingCellConfigCommon. In paragraph 2, A terminal in the above SSB from which a specific SSB is excluded. In paragraph 4, The above terminal-specific SSB is a terminal that includes an SSB set by ssb-ToMeasure or SSB-MTCAdditionalPCI. In paragraph 1, The above DL signal is a terminal including a DL signal or a DL channel set semi-static by a base station. In a method performed by a terminal in a wireless communication system, Receiving a configuration for a non-overlapping subband full duplex (SBFD) symbol set and a non-SBFD symbol set within a wireless frame, wherein the SBFD symbol set includes DL (downlink) symbols or flexible symbols configured with an uplink (UL) subband; and The method includes the step of receiving a DL signal in a slot containing an SBFD symbol, and If an SSB (synchronization signal / physical broadcast channel block) is configured on the symbols within the slot, the DL signal is allowed to be received in the slot and also in the UL subband, and A method in which, when the SSB is not configured on the symbols within the slot, the DL signal is received only outside the UL subband in the slot. In Paragraph 7, The above SSB is a method including a cell-specific SSB. In paragraph 8, A method in which the cell-specific SSB includes an SSB set by SIB1 (system information block 1) or ServingCellConfigCommon. In paragraph 8, A method for excluding terminal-specific SSBs from the above SSB. In Paragraph 10, A method in which the above terminal-specific SSB includes an SSB set by ssb-ToMeasure or SSB-MTCAdditionalPCI. In Paragraph 7, A method in which the above DL signal includes a DL signal or a DL channel set semi-static by a base station.

Images