Method and apparatus for performing beam failure recovery in wireless mobile communication system

Abstract

The present embodiments provide a method by which a terminal performs beam failure recovery (BFR), the method comprising the steps of: receiving configuration information related to beam failure detection (BFD) and configuration information related to beam failure recovery; performing a beam failure detection operation on the basis of the configuration information related to the beam failure detection; and, if the beam failure recovery is triggered on the basis of the beam failure detection, performing a beam failure recovery operation on the basis of the configuration information related to the beam failure recovery, wherein, if a subband full duplex (SBFD) symbol for supporting an SBFD operation is configured by a base station, the beam failure detection operation and / or the beam failure recovery operation is performed separately with respect to each of the SBFD symbol and non-SBFD symbol.

Description

Method and device for performing beam failure recovery in a wireless mobile communication system

[0001] The present embodiments propose a method and apparatus for performing beam failure recovery in a wireless mobile communication system in a next generation wireless access network (in this disclosure, “5G”, “NR [New Radio]”, “5G-Advanced”, “6G” or a subsequent 3GPP wireless access network).

[0002] TDD (Time Division Duplex) is a duplexing method widely used in commercial New Radio (NR) and 5G mobile communication systems. In TDD, time-slot radio resources are divided into downlink and uplink slots. Typically, downlink slots are distributed at a higher rate than uplink slots, depending on the distribution ratio of uplink to downlink traffic. However, this limitation of uplink slots negatively impacts coverage and latency. Full duplex communication has recently attracted attention as a technology to address these issues.

[0003] Additionally, as the number of terminals within a cell increases, beam-based communication technologies are being studied to provide efficient communication. Beam-based communication, which forms beams for specific terminals or groups of terminals, can provide efficient communication while reducing interference.

[0004] Beam-based communication can be implemented even in full-duplex environments, particularly when full-duplex communication is configured on a symbol or slot basis based on subbands. In this context, a specific design is needed to perform beam failure recovery following beam failure detection in situations where various types of full-duplex communication are configured on a symbol or slot basis.

[0005] Embodiments of the present disclosure can provide a method and device for performing beam failure recovery in a wireless mobile communication system.

[0006] In one aspect, the present embodiments provide a method for a terminal to perform beam failure recovery (BFR), the method comprising: receiving configuration information related to beam failure detection (BFD) and configuration information related to beam failure recovery; performing a beam failure detection operation based on the configuration information related to beam failure detection; and performing a beam failure recovery operation based on the configuration information related to beam failure recovery when beam failure recovery is triggered based on beam failure detection, wherein when a SBFD symbol for supporting a subband full duplex (SBFD) operation is configured by a base station, at least one of the beam failure detection operation and the beam failure recovery operation may be separately performed for each of an SBFD symbol and a non-SBFD symbol.

[0007] In another aspect, the present embodiments provide a method for a base station to perform beam failure recovery (BFR), the method comprising: transmitting configuration information related to beam failure detection (BFD) and configuration information related to beam failure recovery; performing a beam failure detection operation based on the configuration information related to beam failure detection; and performing a beam failure recovery operation based on the configuration information related to beam failure recovery when beam failure recovery is triggered based on the beam failure detection, wherein when a subband full duplex (SBFD) symbol for supporting an SBFD operation is configured by the base station, at least one of the beam failure detection operation and the beam failure recovery operation may be performed separately for each of an SBFD symbol and a non-SBFD symbol.

[0008] In another aspect, the present embodiments provide a terminal that performs beam failure recovery (BFR), comprising a transmitter, a receiver, and a control unit that controls operations of the transmitter and the receiver, wherein the control unit receives configuration information related to beam failure detection (BFD) and configuration information related to beam failure recovery, performs a beam failure detection operation based on the configuration information related to beam failure detection, and when beam failure recovery is triggered based on beam failure detection, performs a beam failure recovery operation based on the configuration information related to beam failure recovery, and when a SBFD symbol for supporting a subband full duplex (SBFD) operation is configured by a base station, the terminal can provide a terminal in which at least one of the beam failure detection operation and the beam failure recovery operation is performed separately for each of an SBFD symbol and a non-SBFD symbol.

[0009] In another aspect, the present embodiments provide a base station that performs beam failure recovery (BFR), comprising a transmitter, a receiver, and a control unit that controls operations of the transmitter and the receiver, wherein the control unit transmits configuration information related to beam failure detection (BFD) and configuration information related to beam failure recovery, performs a beam failure detection operation based on the configuration information related to beam failure detection, and performs a beam failure recovery operation based on the configuration information related to beam failure recovery when beam failure recovery is triggered based on beam failure detection, and when a SBFD symbol for supporting a subband full duplex (SBFD) operation is configured by the base station, at least one of the beam failure detection operation and the beam failure recovery operation is performed separately for each of an SBFD symbol and a non-SBFD symbol.

[0010] According to the present embodiments, a method and device for performing beam failure recovery in an environment where full-duplex communication is applied can be provided.

[0011] FIG. 1 is a schematic diagram illustrating the structure of an NR wireless communication system to which the present embodiment can be applied.

[0012] FIG. 2 is a drawing for explaining a frame structure in an NR system to which the present embodiment can be applied.

[0013] FIG. 3 is a diagram for explaining a resource grid supported by a wireless access technology to which the present embodiment can be applied.

[0014] FIG. 4 is a diagram for explaining a bandwidth part supported by a wireless access technology to which the present embodiment can be applied.

[0015] FIG. 5 is a diagram illustrating an example of a synchronization signal block in a wireless access technology to which the present embodiment can be applied.

[0016] FIG. 6 is a diagram for explaining a random access procedure in a wireless access technology to which the present embodiment can be applied.

[0017] Figure 7 is a drawing for explaining CORESET.

[0018] FIG. 8 is a diagram illustrating an example in which an uplink subband is set in an arbitrary downlink slot according to one embodiment.

[0019] FIG. 9 is a diagram illustrating another example in which an uplink subband is set in an arbitrary downlink slot according to one embodiment.

[0020] FIG. 10 is a diagram illustrating a procedure for a terminal to perform beam failure recovery according to one embodiment.

[0021] FIG. 11 is a diagram illustrating a procedure for a base station to perform beam failure recovery according to one embodiment.

[0022] FIG. 12 is a diagram for explaining configuration information related to beam failure detection according to one embodiment.

[0023] FIG. 13 is a diagram for explaining configuration information related to beam failure recovery according to one embodiment.

[0024] Fig. 14 is a drawing showing the configuration of a terminal according to another embodiment.

[0025] Fig. 15 is a drawing showing the configuration of a base station according to another embodiment.

[0026] Hereinafter, some embodiments of the present disclosure will be described in detail with reference to exemplary drawings. When adding reference numerals to components in each drawing, identical components may have the same numerals as much as possible even if they are shown in different drawings. In addition, when describing the present embodiments, if it is determined that a detailed description of a related known configuration or function may obscure the gist of the technical idea of ​​the present invention, the detailed description may be omitted. When "includes," "has," "consists of," etc. are used in this specification, other parts may be added unless "only" is used. When a component is expressed in the singular, it may include a case in which the plural is included unless specifically stated otherwise.

[0027] Additionally, terms such as first, second, A, B, (a), (b), etc. may be used to describe components of the present disclosure. These terms are only intended to distinguish the components from other components, and the nature, order, sequence, or number of the components are not limited by the terms.

[0028] In a description of the positional relationship of components, when it is described that two or more components are "connected," "combined," or "connected," it should be understood that the two or more components may be directly "connected," "combined," or "connected," but that the two or more components may also be further "interposed" with another component to be "connected," "combined," or "connected." Here, the other component may be included in one or more of the two or more components that are "connected," "combined," or "connected" to each other.

[0029] In the description of the temporal flow relationship related to components, operation methods, or manufacturing methods, for example, when the temporal or flow relationship is described as “after”, “following”, “next to”, “before”, etc., it may also include cases where it is not continuous, unless “immediately” or “directly” is used.

[0030] Meanwhile, when numerical values ​​or corresponding information (e.g., levels, etc.) for components are mentioned, even without separate explicit description, the numerical values ​​or corresponding information may be interpreted as including an error range that may occur due to various factors (e.g., process factors, internal or external impact, noise, etc.).

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

[0032] The embodiments disclosed below can be applied to wireless communication systems using various wireless access technologies. For example, the embodiments can be applied to various wireless access technologies such as CDMA (code division multiple access), FDMA (frequency division multiple access), TDMA (time division multiple access), OFDMA (orthogonal frequency division multiple access), SC-FDMA (single carrier frequency division multiple access), or NOMA (non-orthogonal multiple access). In addition, the wireless access technology may not only refer to a specific access technology, but also to each generation of communication technology established by various communication agreement organizations such as 3GPP, 3GPP2, WiFi, Bluetooth, IEEE, and ITU. For example, CDMA can be implemented with wireless technologies such as UTRA (universal terrestrial radio access) or CDMA2000. TDMA can be implemented with wireless technologies such as GSM (global system for mobile communications) / GPRS (general packet radio service) / EDGE (enhanced data rates for GSM evolution). OFDMA can be implemented in wireless technologies such as IEEE (Institute of Electrical and Electronics Engineers) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802-20, and E-UTRA (evolved UTRA). IEEE 802.16m is an evolution of IEEE 802.16e and provides backward compatibility with systems based on IEEE 802.16e.UTRA is part of UMTS (universal mobile telecommunications system). 3GPP (3rd generation partnership project) LTE (long term evolution) is part of E-UMTS (evolved UMTS) that uses E-UTRA (evolved-UMTSterrestrial radio access), employing OFDMA in the downlink and SC-FDMA in the uplink. Thus, the present embodiments can be applied to currently disclosed or commercialized wireless access technologies, as well as wireless access technologies currently under development or to be developed in the future.

[0033] Meanwhile, the term "terminal" in this specification is a comprehensive concept that refers to a device that includes a wireless communication module that performs communication with a base station in a wireless communication system, and should be interpreted as a concept that includes not only UE (User Equipment) in WCDMA, LTE, NR, HSPA, and IMT-2020 (5G or New Radio), but also MS (Mobile Station), UT (User Terminal), SS (Subscriber Station), and wireless device in GSM. In addition, the terminal may be a user portable device such as a smartphone depending on the usage type, and in a V2X communication system, it may mean a vehicle, a device including a wireless communication module in the vehicle, etc. In addition, in the case of a Machine Type Communication system, it may mean an MTC terminal, M2M terminal, URLLC terminal, etc. that is equipped with a communication module to perform machine type communication.

[0034] The base station or cell in this specification refers to an end that communicates with a terminal in terms of a network, and includes various coverage areas such as Node-B, eNB (evolved Node-B), gNB (gNode-B), LPN (Low Power Node), Sector, Site, various types of antennas, BTS (Base Transceiver System), Access Point, Point (e.g., Transmission Point, Reception Point, Transmission / Reception Point), Relay Node, Mega Cell, Macro Cell, Micro Cell, Pico Cell, Femto Cell, RRH (Remote Radio Head), RU (Radio Unit), and Small Cell. In addition, a cell may mean including a BWP (Bandwidth Part) in the frequency domain. For example, a serving cell may mean an Activation BWP of a terminal.

[0035] Since the various cells listed above have a base station that controls one or more cells, the base station can be interpreted in two meanings. 1) It can be a device itself that provides a mega cell, macro cell, micro cell, pico cell, femto cell, or small cell in relation to a wireless area, or 2) it can indicate the wireless area itself. In 1), all devices that provide a given wireless area are controlled by the same entity or that interact to cooperatively configure the wireless area are all indicated as a base station. Depending on how the wireless area is configured, a point, a transceiver point, a transmission point, a reception point, etc. can be an embodiment of a base station. In 2), the wireless area itself that receives or transmits a signal from the perspective of a user terminal or a neighboring base station can also be indicated as a base station.

[0036] In this specification, a cell may mean a component carrier having coverage of a signal transmitted from a transmission / reception point or a transmission / reception point itself.

[0037] Uplink (UL, or uplink) refers to a method of transmitting and receiving data from a terminal to a base station, and downlink (DL, or downlink) refers to a method of transmitting and receiving data from a base station to a terminal. Downlink may refer to communication or a communication path from multiple transmission / reception points to a terminal, and uplink may refer to communication or a communication path from a terminal to multiple transmission / reception points. In this case, in the downlink, the transmitter may be part of the multiple transmission / reception points, and the receiver may be part of the terminal. In addition, in the uplink, the transmitter may be part of the terminal, and the receiver may be part of the multiple transmission / reception points.

[0038] Uplink and downlink transmit and receive control information through control channels such as PDCCH (Physical Downlink Control CHannel) and PUCCH (Physical Uplink Control CHannel), and transmit and receive data by configuring data channels such as PDSCH (Physical Downlink Shared CHannel) and PUSCH (Physical Uplink Shared CHannel). Hereinafter, the situation in which signals are transmitted and received through channels such as PUCCH, PUSCH, PDCCH, and PDSCH is also expressed in the form of 'transmitting and receiving PUCCH, PUSCH, PDCCH, and PDSCH'.

[0039] For clarity of explanation, the technical idea of ​​this invention is described below mainly with reference to the 3GPP LTE / LTE-A / NR (New RAT) communication system, but the technical features of this invention are not limited to the communication system.

[0040] After researching 4G (4th-Generation) communication technology, 3GPP develops 5G (5th-Generation) communication technology to meet the requirements of the next-generation wireless access technology of the ITU-R. Specifically, 3GPP develops LTE-A pro, which enhances LTE-Advanced technology to meet the requirements of the ITU-R, and NR, a new communication technology separate from 4G communication technology. Both LTE-A pro and NR refer to 5G communication technology, and in the following, 5G communication technology will be explained with NR as the focus, unless a specific communication technology is specifically mentioned.

[0041] The operating scenario in NR defines various operation scenarios by adding considerations for satellites, automobiles, and new verticals to the existing 4G LTE scenario, and in terms of service, it supports the eMBB (Enhanced Mobile Broadband) scenario, the mMTC (Massive Machine Communication) scenario that has high terminal density but is deployed over a wide area and requires low data rate and asynchronous access, and the URLLC (Ultra Reliability and Low Latency) scenario that requires high responsiveness and reliability and can support high-speed mobility.

[0042] To meet these scenarios, NR introduces a wireless communication system that incorporates new waveform and frame structure technologies, low latency technologies, support for ultra-high frequency bands (mmWave), and forward compatibility technologies. In particular, NR systems offer various technological changes in terms of flexibility to ensure forward compatibility. The key technical features of NR are described below with reference to the drawings.

[0043]

[0044] <NR 시스템 일반>

[0045] Figure 1 is a schematic diagram illustrating the structure of an NR system to which the present embodiment can be applied.

[0046] Referring to Fig. 1, the NR system is divided into 5GC (5G Core Network) and NR-RAN parts, and the NG-RAN is composed of gNBs and ng-eNBs that provide user plane (SDAP / PDCP / RLC / MAC / PHY) and control plane (RRC) protocol termination for UE (User Equipment). gNBs or gNBs and ng-eNBs are interconnected via the Xn interface. gNBs and ng-eNBs are each connected to the 5GC via the NG interface. The 5GC can be configured to include an AMF (Access and Mobility Management Function) that is responsible for the control plane such as terminal access and mobility control functions, and an UPF (User Plane Function) that is responsible for the control function for user data. NR includes support for both frequency bands below 6 GHz (FR1, Frequency Range 1) and frequency bands above 6 GHz (FR2, Frequency Range 2).

[0047] gNB refers to a base station that provides NR user plane and control plane protocol termination to terminals, and ng-eNB refers to a base station that provides E-UTRA user plane and control plane protocol termination to terminals. The base station described in this specification should be understood to encompass both gNB and ng-eNB, and may also be used to refer to gNB or ng-eNB separately as needed.

[0048] <NR 웨이브 폼, 뉴머롤러지 및 프레임 구조>

[0049]

[0050] *NR uses the CP-OFDM waveform with a cyclic prefix for downlink transmission, and CP-OFDM or DFT-s-OFDM for uplink transmission. OFDM technology is easily combined with MIMO (Multiple Input Multiple Output) and has the advantage of enabling the use of low-complexity receivers with high frequency efficiency.

[0051] Meanwhile, in NR, the requirements for data rates, latency, and coverage differ across the three scenarios mentioned above. Therefore, it is necessary to efficiently satisfy these requirements across the frequency bands that comprise any NR system. To this end, technologies have been proposed to efficiently multiplex radio resources based on multiple different numerologies.

[0052] Specifically, the NR transmission numerator is determined based on the sub-carrier spacing and the cyclic prefix (CP), and is changed exponentially with the μ value being an exponent value of 2 based on 15 kHz, as shown in Table 1 below.

[0053] μ서브캐리어 간격Cyclic prefixSupported for dataSupported for synch015NormalYesYes130NormalYesYes260Normal, ExtendedYesNo3120NormalYesYes4240NormalNoYes

[0054] As shown in Table 1 above, the numerology of NR can be divided into five types according to the subcarrier spacing. This is different from the fixed subcarrier spacing of LTE, one of the 4G communication technologies, at 15 kHz. Specifically, the subcarrier spacing used for data transmission in NR is 15, 30, 60, and 120 kHz, and the subcarrier spacing used for synchronization signal transmission is 15, 30, 12, and 240 kHz. In addition, the extended CP is applied only to the 60 kHz subcarrier spacing. Meanwhile, the frame structure in NR is defined as a 10 ms frame consisting of 10 subframes with the same length of 1 ms. One frame can be divided into half frames of 5 ms, and each half frame contains 5 subframes. In the case of a 15 kHz subcarrier spacing, one subframe consists of one slot, and each slot consists of 14 OFDM symbols. FIG. 2 is a diagram for explaining the frame structure in an NR system to which the present embodiment can be applied. Referring to FIG. 2, a slot is fixedly composed of 14 OFDM symbols in the case of a normal CP, but the length of the slot in the time domain may vary depending on the subcarrier spacing. For example, in the case of a numerology with a 15 kHz subcarrier spacing, a slot is composed of 1 ms, which is the same length as a subframe. In contrast, in the case of a numerology with a 30 kHz subcarrier spacing, a slot is composed of 14 OFDM symbols, but two slots may be included in one subframe with a length of 0.5 ms. That is, a subframe and a frame are defined with a fixed time length, and a slot is defined by the number of symbols, so the time length may vary depending on the subcarrier spacing.

[0055] Meanwhile, NR defines slots as the basic scheduling unit and also introduces mini-slots (or sub-slots, or non-slot-based scheduling) to reduce transmission delay in the wireless section. Using wider subcarrier spacing reduces transmission delay in the wireless section by shortening the length of each slot inversely. Mini-slots (or sub-slots) are designed to efficiently support URLLC scenarios and allow scheduling in units of 2, 4, or 7 symbols.

[0056] Furthermore, unlike LTE, NR defines uplink and downlink resource allocation at the symbol level within a single slot. To reduce HARQ delay, a slot structure was defined that allows HARQ ACK / NACKs to be transmitted directly within the transmission slot. This slot structure is referred to as a self-contained structure and will be described in detail.

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

[0058] <NR 물리 자원 >

[0059] In relation to physical resources in NR, antenna ports, resource grids, resource elements, resource blocks, and bandwidth parts are considered.

[0060] Antenna ports are defined such that the channel through which a symbol on an antenna port is carried can be inferred from the channel through which another symbol on the same antenna port is carried. Two antenna ports are said to be quasi co-located (or quasi co-located) if the large-scale properties of the channel through which a symbol on one antenna port is carried can be inferred from the channel through which a symbol on the other antenna port is carried. Here, the large-scale properties include one or more of delay spread, Doppler spread, frequency shift, average received power, and received timing.

[0061] FIG. 3 is a diagram for explaining a resource grid supported by a wireless access technology to which the present embodiment can be applied.

[0062] Referring to Figure 3, a resource grid may exist for each numeral, as NR supports multiple numerals on the same carrier. Furthermore, resource grids may exist based on antenna ports, subcarrier spacing, and transmission direction.

[0063] A resource block (RB) consists of 12 subcarriers and is defined solely in the frequency domain. Furthermore, a resource element (RE) consists of one OFDM symbol and one subcarrier. Therefore, as shown in Figure 3, the size of a single RB can vary depending on the subcarrier spacing. NR also defines "Point A," which serves as a common reference point for the RB grid, as well as common RBs and virtual RBs.

[0064] FIG. 4 is a diagram for explaining a bandwidth part supported by a wireless access technology to which the present embodiment can be applied.

[0065] Unlike LTE, where the carrier bandwidth is fixed at 20 MHz, NR sets the maximum carrier bandwidth from 50 MHz to 400 MHz for each subcarrier interval. Therefore, it is not assumed that all terminals will use the entire carrier bandwidth. Accordingly, NR allows terminals to designate bandwidth parts (BWPs) within the carrier bandwidth, as illustrated in Figure 4. Furthermore, bandwidth parts are associated with a single numerology, consist of a subset of consecutive common resource blocks, and can be dynamically activated over time. Each terminal is configured with up to four bandwidth parts for both the uplink and downlink, and data is transmitted and received using the bandwidth parts activated at a given time.

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

[0067] <NR 초기 접속>

[0068] In NR, a terminal performs cell search and random access procedures to connect to a base station and perform communication.

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

[0070] FIG. 5 is a diagram illustrating an example of a synchronization signal block in a wireless access technology to which the present embodiment can be applied.

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

[0072] The terminal receives SSB by monitoring SSB in the time and frequency domain.

[0073] SSB can be transmitted up to 64 times in 5ms. Multiple SSBs are transmitted in different transmission beams within 5ms, and the terminal performs detection assuming that SSBs are transmitted every 20ms based on a specific beam used for transmission. The number of beams that can be used for SSB transmission within 5ms can increase as the frequency band increases. For example, up to 4 SSB beams can be transmitted below 3GHz, up to 8 in the frequency band between 3GHz and 6GHz, and up to 64 different beams can be used for SSB transmission in the frequency band above 6GHz.

[0074] SSB contains two symbols in one slot, and the starting symbol and number of repetitions within the slot are determined as follows depending on the subcarrier spacing.

[0075] Meanwhile, unlike SS in conventional LTE, SSB is not transmitted at the center frequency of the carrier bandwidth. This means that SSB can be transmitted even in locations other than the center of the system bandwidth, and when supporting wideband operation, multiple SSBs can be transmitted in the frequency domain. Accordingly, the terminal monitors SSB using the synchronization raster, which is a candidate frequency location for monitoring SSB. The carrier raster, which is the center frequency location information of the channel for initial access, and the synchronization raster are newly defined in NR. The synchronization raster has a wider frequency interval than the carrier raster, which can support the terminal's fast SSB search.

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

[0077] The aforementioned RMSI may refer to SIB1 (System Information Block 1), and SIB1 is broadcast periodically (e.g., every 160 ms) in the cell. SIB1 contains information necessary for the UE to perform the initial random access procedure and is periodically transmitted via PDSCH. In order for the UE to receive SIB1, it must receive numerology information used for SIB1 transmission and CORESET (Control Resource Set) information used for SIB1 scheduling via PBCH. The UE checks scheduling information for SIB1 using SI-RNTI in CORESET and acquires SIB1 on PDSCH according to the scheduling information. The remaining SIBs, excluding SIB1, may be transmitted periodically or upon request of the UE.

[0078] FIG. 6 is a diagram for explaining a random access procedure in a wireless access technology to which the present embodiment can be applied.

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

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

[0081] Upon receiving a valid random access response, the terminal processes the information contained in the random access response and performs scheduled transmission to the base station. For example, the terminal applies TAC and stores a temporary C-RNTI. Furthermore, using the UL Grant, the terminal transmits data stored in its buffer or newly generated data to the base station. In this case, information that identifies the terminal must be included.

[0082] Finally, the terminal receives a downlink message for contention resolution.

[0083] <NR CORESET>

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

[0085] To ensure system flexibility, NR introduced the CORESET concept. CORESET (Control Resource Set) refers to time-frequency resources for downlink control signals. A terminal can decode control channel candidates using one or more search spaces within the CORESET time-frequency resources. A QCL (Quasi CoLocation) assumption is established for each CORESET, which is used to inform the characteristics of analog beam direction in addition to the delay spread, Doppler spread, Doppler shift, and average delay assumed by the conventional QCL.

[0086] Figure 7 is a drawing for explaining CORESET.

[0087] Referring to Figure 7, a CORESET can exist in various forms within the carrier bandwidth within a single slot, and in the time domain, a CORESET can consist of up to three OFDM symbols. In addition, a CORESET is defined as a multiple of six resource blocks up to the carrier bandwidth in the frequency domain.

[0088] The first CORESET is indicated via the MIB as part of the initial bandwidth part configuration, allowing the terminal to receive additional configuration and system information from the network. After establishing a connection with the base station, the terminal can receive and configure one or more CORESET information via RRC signaling.

[0089] Wider bandwidth operations

[0090] Existing LTE systems supported scalable bandwidth operation for any LTE Component Carrier (CC). That is, depending on the deployment scenario, any LTE operator could configure a single LTE CC with a bandwidth ranging from a minimum of 1.4 MHz to a maximum of 20 MHz, and a normal LTE terminal supported transmission and reception capabilities of 20 MHz bandwidth for a single LTE CC.

[0091] However, in the case of NR, the design is made to support NR terminals with different transmission and reception bandwidth capabilities through a single wideband NR CC, and accordingly, it is required to configure one or more bandwidth parts (BWP, bandwidth part(s)) consisting of segmented bandwidths for any NR CC, and to support flexible wider bandwidth operation through different bandwidth part configurations and activations for each terminal.

[0092] Specifically, in NR, one or more bandwidth parts can be configured through one serving cell configured from the terminal's perspective, and the terminal is defined to activate one downlink bandwidth part (DL bandwidth part) and one uplink bandwidth part (UL bandwidth part) in the serving cell to use them for uplink / downlink data transmission and reception. In addition, when multiple serving cells are configured in the terminal, that is, for the terminal to which CA is applied, it is defined to activate one downlink bandwidth part and / or uplink bandwidth part for each serving cell to use the radio resources of the serving cell to use them for uplink / downlink data transmission and reception.

[0093] Specifically, an initial bandwidth part for an initial access procedure of a terminal in an arbitrary serving cell is defined, one or more UE-specific bandwidth part(s) are configured for each terminal through dedicated RRC signaling, and a default bandwidth part for a fallback operation can also be defined for each terminal.

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

[0095] In this specification, the terms frequency, frame, subframe, resource, resource block, region, band, subband, control channel, data channel, synchronization signal, various reference signals, various signals or various messages related to NR (New Radio) may be interpreted in the past or present meaning or in various meanings used in the future.

[0096]

[0097] The present disclosure proposes a beam failure recovery method between a base station and a terminal to support full-duplex communication.

[0098] TDD (Time Division Duplex) is a duplexing method widely used in commercial New Radio (NR) and 5G mobile communication systems. In TDD, time-slot radio resources are divided into downlink and uplink slots. Typically, downlink slots are distributed at a higher rate than uplink slots, depending on the distribution ratio of uplink to downlink traffic. However, this limitation on uplink slots negatively impacts coverage and latency. Full-duplex communication can be applied as a technology to address these issues.

[0099] Full-duplex communication is a technology that performs DL transmission and UL reception simultaneously on the same radio resources, specifically at the gNB, or base station. Simultaneous DL reception and UL transmission can also be performed at the terminal side. In other words, both the base station and the terminal can support full duplex. However, unlike the base station, which is structurally easy to cancel self-interference, the DL reception performance of the terminal is easily affected by self-interference of the UL transmission signal. Therefore, it is generally considered that the base station operates in full-duplex communication, and the terminal operates in half-duplex communication. Additionally, to reduce the influence of self-interference at the base station, a subband non-overlapping full-duplex (subband non-overlapping full-duplex, also referred to as SBFD or subband full-duplex in this disclosure) method can be primarily considered, in which DL transmission and UL reception are performed simultaneously, but the DL / UL are transmitted and received by distinguishing frequency resources rather than using the same resources.

[0100] FIG. 8 is a diagram illustrating an example in which an uplink subband is set in an arbitrary downlink slot according to one embodiment. FIG. 9 is a diagram illustrating another example in which an uplink subband is set in an arbitrary downlink slot according to one embodiment.

[0101] That is, FIGS. 8 and 9 illustrate examples in which DL slots and UL slots are configured in a ratio of 4:1 in an arbitrary NR frequency band. However, some symbols of the last DL slot may be special slots including flexible symbols for DL / UL transition. In this way, when a TDD (Time Division Duplex) configuration is made, an uplink subband (UL subband) may be set to support UL transmission of a terminal in some (or all) of the DL slots. When a UL subband is set in an arbitrary DL slot, the UL subband may be set at the center of the frequency band, as shown in FIG. 8, or at the edge of the frequency band, as shown in FIG. 9. In this case, a guard band may be set between the UL subband and the downlink subband (DL subband) in the slot.

[0102] In addition, for frequency resources other than the UL subband and guard band, they can be utilized as DL subbands for DL ​​transmission and reception according to the existing slot / symbol configuration information. That is, as in FIG. 8, if the UL subband is configured around the center of the frequency band, two guard bands, one each above and below the UL subband, can be configured, and then similarly, two DL subbands, one each above and below the UL subband, can be configured. Alternatively, as in FIG. 9, if the UL subband is configured at the edge of the frequency band, one guard band and one DL subband can be configured following the UL subband.

[0103] The UL-DL slot configuration defined in NR is defined to be done on a cell-by-cell basis through cell-specific RRC signaling. That is, a pattern of DL symbols, UL symbols, and flexible symbols for a certain period is set through the RRC message 'tdd-UL-DL-ConfigurationCommon' for the corresponding UL-DL slot configuration. Additionally, through the UE-specific RRC signaling 'tdd-UL-DL-ConfigurationDedicated', only the flexible symbols set through the 'tdd-UL-DL-ConfigurationCommon' can be reallocated to UL symbols, DL symbols, or flexible symbols for each UE. Alternatively, a method for indicating a dynamic slot format through a UE-group common PDCCH is also defined. For this purpose, NR also supports a dynamic slot format indication method through DCI format 2_0.

[0104] According to the slot configuration method described above, any one symbol can be set or indicated as one of DL, UL, or Flexible. FIG. 8 is an example in which an arbitrary slot format is set to DDDSU through the existing slot configuration. D refers to a downlink slot, meaning that all OFDM symbols constituting the slot are set to DL. U refers to an uplink slot, meaning that all OFDM symbols constituting the slot are set to UL. S refers to a special slot, meaning that a slot includes a flexible symbol for DL / UL transition. Typically, in the case of a normal CP, the special slot can be configured with 12 DL symbols and 2 flexible symbols out of a total of 14 symbols. Alternatively, it can be configured with 10 DL symbols, 2 flexible symbols, and 2 UL symbols. That is, within any one TDD carrier, one symbol is configured or indicated as only one of DL, UL, or flexible.

[0105] However, as shown in FIGS. 8 and 9, if a UL subband is configured in any DL slot, DL transmission or UL transmission can occur simultaneously for each frequency resource in the symbol. In this way, a DL slot or symbol including a UL subband, or a UL slot or symbol including a DL subband, is referred to as an SBFD (subband full duplex) slot or SBFD symbol in the present disclosure.

[0106] In addition, in the present disclosure, a slot composed only of the SBFD symbols is referred to as an SBFD slot, and a slot composed only of symbols according to existing symbol settings (i.e., a slot composed only of symbols that do not include a UL subband, a DL subband, and a guardband) is referred to as a non-SBFD slot. Alternatively, a slot including at least one SBFD symbol may be referred to as an SBFD slot. As mentioned above, this is for convenience of explanation and is not limited to the terminology.

[0107]

[0108] Below, a method for performing beam failure recovery in a wireless mobile communication system will be specifically described with reference to related drawings.

[0109] FIG. 10 is a diagram illustrating a procedure (1000) for a terminal to perform beam failure recovery according to one embodiment.

[0110] Referring to FIG. 10, the terminal can receive configuration information related to beam failure detection (BFD) and configuration information related to beam failure recovery (S1010).

[0111] In this disclosure, we assume that a terminal and a base station support full-duplex communication based on subband non-overlapping. In this case, certain frequency resources within the same symbol in a TDD carrier can be used for downlink transmission, while other frequency resources can be used for uplink reception. That is, within a TDD carrier, some frequency resources in any downlink symbol can be configured to be utilized for uplink transmission by a terminal, or as flexible symbols for downlink / uplink transitions.

[0112] A terminal may configure a downlink subband in an uplink slot, or receive information about a time domain and a frequency domain for configuring an uplink subband in a downlink slot. According to an example, the SBFD configuration information may include configuration information about at least one uplink subband and at least one downlink subband. In addition, the SBFD configuration information may include configuration information about an SBFD symbol in which an uplink subband and a downlink subband are configured in the frequency domain. Alternatively, the SBFD configuration information may include information about a frequency domain in which a guard band is configured and information about a time domain. Here, the frequency resource information may include resource block allocation information, and the time resource information may include SBFD symbol allocation information.

[0113] In addition, for configuring SBFD subbands, time resource information for uplink subbands can be set based on reference subcarrier spacing (SCS) information and pattern setting information. In this case, the time resource information can be set based on the reference subcarrier spacing (SCS) included in the TDD configuration information. That is, the reference subcarrier spacing (SCS) setting included in the TDD configuration information can be used as a reference SCS for setting time resources for configuring uplink subbands.

[0114] Additionally, time resource information can be set based on the number of TDD patterns and the period of the patterns included in the TDD configuration information. That is, the settings for Pattern 1 and Pattern 2 included in the TDD configuration information can be used as pattern setting information for setting time resources for configuring an uplink subband.

[0115] In this case, the SBFD symbol allocation information may be set to consecutive SBFD symbols within the cycle of a TDD pattern set to one or two. Each pattern setting information may include cycle setting information, offset information, and duration information of the corresponding pattern. At this time, the duration information may be set to the number of consecutive SBFD symbols from the offset, or may be set to a combination of the number of consecutive SBFD slots and the number of consecutive SBFD symbols. Alternatively, according to an example, the offset may be set to an end point instead of a start point. That is, offset information corresponding to the end point and duration information from the end point may be set.

[0116] For configuring SBFD subbands, frequency resource configuration information for uplink subbands may be configured in units of common resource blocks (CRBs). In this case, frequency resource configuration for uplink subbands may be accompanied by guardband configuration or downlink subband configuration within the same symbol / slot. That is, frequency resource configuration information for uplink subbands may include at least one of guardbands accompanying an SBFD slot or SBFD symbol in which the uplink subband is configured, or frequency resource configuration information for downlink subbands. In this case, time resource configuration information for the guardband or downlink subbands may be configured according to the time resource configuration information of the uplink subband.

[0117] For example, for configuring SBFD subbands, frequency resource information for an uplink subband may include configuration information for one uplink subband and one or two guard bands based on a CRB. In this case, if the uplink subband is located in the center of the frequency band, two guard bands may be configured above and below the uplink subband. Alternatively, if the uplink subband is located at the upper boundary of the frequency band, one guard band may be configured below the uplink subband. Alternatively, if the uplink subband is located at the lower boundary of the frequency band, one guard band may be configured above the uplink subband. Accordingly, configuration information for one or two guard bands may be included in the frequency resource information. In this case, a downlink subband may be configured with a guard band in between, and the downlink subband may be inferred from the frequency resource information for the uplink subband and the guard band.

[0118] In another example, for configuring SBFD subbands, frequency resource information for an uplink subband may include configuration information for one uplink subband and one or two downlink subbands based on a CRB. In this case, if the uplink subband is located in the center of the frequency band, two downlink subbands may be configured above and below the uplink subband. Alternatively, if the uplink subband is located at the upper boundary of the frequency band, one downlink subband may be configured below the uplink subband. Alternatively, if the uplink subband is located at the lower boundary of the frequency band, one downlink subband may be configured above the uplink subband. Accordingly, configuration information for one or two downlink subbands may be included in the frequency resource information. In this case, a guard band may be configured between the uplink subband and the downlink subband, and the guard band may be inferred from the frequency resource information for the uplink subband and the downlink subband.

[0119] For example, SBFD configuration information can be received via cell-specific upper layer signaling. That is, the terminal can receive SBFD subband configuration information from the base station via cell-specific RRC signaling. The terminal can receive the TDD configuration information and SBFD subband configuration information to configure a format for each slot.

[0120] A terminal may receive configuration information related to beam failure detection and configuration information related to beam failure recovery from a base station for radio link monitoring. In one example, the configuration information related to beam failure detection and configuration information related to beam failure recovery may be received as an RRC message. For example, the configuration information related to beam failure detection may be received via RadioLinkMonitoringConfig. Additionally, the configuration information related to beam failure recovery may be received via BeamFailureRecoveryConfig, which includes RACH resource configuration information and candidate beam configuration information.

[0121] When a base station configures a subband full duplex (SBFD) symbol to support subband-based full duplex operation, at least one of a beam failure detection operation and a beam failure recovery operation can be performed separately for each of the SBFD symbol and the non-SBFD symbol. That is, when an SBFD symbol is configured for a terminal, the terminal can perform independent beam failure detection and beam failure recovery procedures for the SBFD symbol and the non-SBFD symbol.

[0122] For example, whether separate beam failure detection and beam failure recovery procedures are configured for SBFD symbols may be determined based on the capabilities of the terminal. In this case, the terminal may report its capability information to the base station through capability signaling. The base station may additionally set whether to separately configure beam failure detection and beam failure recovery procedures for SBFD symbols and non-SBFD symbols based on the capabilities of the terminal. A terminal for which beam failure detection and beam failure recovery procedures are separately configured by the base station for each symbol type may independently perform beam failure detection and beam failure recovery procedures with the base station for SBFD symbols and non-SBFD symbols.

[0123] Alternatively, the terminal may be configured to perform the beam failure detection procedure separately according to the symbol type, i.e., for non-SBFD symbols and SBFD symbols, while performing the beam failure recovery procedure based on common configuration information. Alternatively, the terminal may be configured to perform the beam failure recovery procedure separately according to the symbol type, while performing the beam failure detection procedure based on common configuration information.

[0124] Whether to configure beam failure detection and beam failure recovery procedures separately in SBFD symbols and non-SBFD symbols can be explicitly set by the base station via RRC signaling.

[0125] Alternatively, whether beam failure detection and beam failure recovery procedures are configured separately in BFD symbols and non-SBFD symbols can be implicitly configured. According to the implicit configuration method, configuration information related to beam failure detection and / or configuration information related to beam failure recovery can be configured through separate RRC message settings for beam failure detection and recovery in SBFD symbols. That is, at least one of the configuration information related to beam failure detection and the configuration information related to beam failure recovery can be separately configured and received for each of the SBFD symbol and the non-SBFD symbol.

[0126] In this case, configuration information related to beam failure detection for the SBFD symbol can be received through a separate RRC message, such as RadioLinkMonitoringConfig_SBFD, in addition to the existing RadioLinkMonitoringConfig. In addition, configuration information related to beam failure recovery for the SBFD symbol can be received through a separate RRC message, such as BeamFailureRecoveryConfig_SBFD, in addition to the existing BeamFailureRecoveryConfig.

[0127] Accordingly, as described above, when the beam failure detection and beam failure recovery procedures are configured separately for each symbol type, configuration information related to beam failure detection and / or configuration information related to beam failure recovery may be configured separately for each SBFD symbol and non-SBFD symbol, respectively. Alternatively, when only the beam failure detection procedure is configured separately for each symbol type, configuration information related to beam failure detection may be configured separately for each SBFD symbol and non-SBFD symbol, respectively. Alternatively, when only the beam failure recovery procedure is configured separately for each symbol type, configuration information related to beam failure recovery may be configured separately for each SBFD symbol and non-SBFD symbol, respectively.

[0128] For example, each of the configuration information related to beam failure detection and the configuration information related to beam failure recovery configured for an SBFD symbol may be configured to include at least a portion of all parameters included in each of the configuration information related to beam failure detection and the configuration information related to beam failure recovery configured for a non-SBFD symbol. That is, the configuration information related to beam failure detection and the configuration information related to beam failure recovery configured separately for an SBFD symbol may include all or a portion of the parameters included in existing configuration information, i.e., the configuration information related to beam failure detection and the configuration information related to beam failure recovery configured for a non-SBFD symbol. If only a portion of the parameters is included, the values ​​of the existing configuration information may be used for the parameters that are not included.

[0129] Alternatively, according to an example, each of the configuration information related to beam failure detection configured for the SBFD symbol and the configuration information related to beam failure recovery may be configured in a form that is included in each of the configuration information related to beam failure detection configured for the non-SBFD symbol and the configuration information related to beam failure recovery. That is, the configuration information related to beam failure detection and the configuration information related to beam failure recovery configured separately for the SBFD symbol may be configured as part of the existing configuration information.

[0130] For example, if at least one of a beam failure detection operation and a beam failure recovery operation is performed separately for each of an SBFD symbol and a non-SBFD symbol, the reference signal and radio resources used for the beam failure detection operation and the beam failure recovery operation may be configured only for symbols of the same type. For example, when the terminal sets a monitoring reference signal for beam failure detection, the monitoring reference signal for beam failure detection of an SBFD symbol may be configured to be limited to a reference signal transmitted through the SBFD symbol. If the monitoring reference signal includes transmissions in both an SBFD symbol and a non-SBFD symbol, the terminal may be configured to be limited to transmission instances in the SBFD symbol.

[0131] Similarly, the terminal may be configured to restrict the monitoring reference signal for beam failure detection of non-SBFD symbols to reference signals transmitted via non-SBFD symbols. If the monitoring reference signal includes transmissions in both SBFD and non-SBFD symbols, the terminal may be configured to restrict the transmission instances to those in non-SBFD symbols.

[0132] As another example, the terminal may be configured to limit the candidate beam lists for beam failure recovery to symbols of the same type. That is, the terminal may be configured to limit SBFD symbol target recovery to reference signals transmitted via SBFD symbols, and to limit non-SBFD symbol target recovery to reference signals transmitted via non-SBFD symbols.

[0133] As another example, the terminal may be configured to limit the RACH resource settings for beam failure recovery of the terminal to RACH resource settings belonging to the same symbol type.

[0134] The above description assumes that beam failure detection and beam failure recovery procedures are configured separately depending on the symbol type. However, as another example, the base station can configure the integrated procedure without distinguishing between non-SBFD and SBFD symbols. In this case, the terminal can perform beam failure detection and beam failure recovery procedures by integrating SBFD and non-SBFD symbols without distinguishing between them.

[0135] Referring again to FIG. 10, the terminal performs a beam failure detection operation based on configuration information related to beam failure detection (S1020), and when beam failure recovery is triggered based on beam failure detection, the terminal may perform a beam failure recovery operation based on configuration information related to beam failure recovery (S1030).

[0136] The terminal can perform beam failure detection procedures and beam failure recovery procedures based on configuration information related to beam failure detection and configuration information related to beam failure recovery. In this case, as described above, the following procedures can be performed depending on whether the configuration information related to beam failure detection and configuration information related to beam failure recovery are separately configured for the SBFD symbol.

[0137] The MAC sublayer of the terminal can detect beam failure based on periodic Beam Failure Instance (BFI) reporting results from the physical layer (PHY). The downlink reference signal that the terminal should monitor for beam failure detection is determined by the CSI-RS or SSB, which are CORESET beam reference signals for PDCCH monitoring, and the reference signal for beam failure detection can be explicitly set by the base station. Alternatively, if not set, the terminal can determine BFI by monitoring all CORESET beam reference signals.

[0138] Additionally, the MAC sublayer of the terminal may declare a beam failure and perform a beam failure recovery procedure according to configuration information regarding beam failure recovery when N BFIs, determined by the beamFailureInstanceMaxCount setting value, are received from the PHY during M reporting intervals, determined by the beamFailureDetectionTimer setting value.

[0139] Accordingly, a method and device for performing beam failure recovery in an environment where full-duplex communication is applied can be provided.

[0140] FIG. 11 is a diagram illustrating a procedure (1100) for a base station to perform beam failure recovery according to one embodiment. The description given above in FIG. 10 may be omitted to avoid redundant description, and in this case, the omitted content may be substantially equally applied to the base station as long as it does not conflict with the technical spirit of the invention.

[0141] Referring to FIG. 11, the base station can transmit configuration information related to beam failure detection (BFD) and configuration information related to beam failure recovery (S1110).

[0142] In this disclosure, we assume that a terminal and a base station support full-duplex communication based on subband non-overlapping. In this case, certain frequency resources within the same symbol in a TDD carrier can be used for downlink transmission, while other frequency resources can be used for uplink reception. That is, within a TDD carrier, some frequency resources in any downlink symbol can be configured to be utilized for uplink transmission by a terminal, or as flexible symbols for downlink / uplink transitions.

[0143] For example, SBFD configuration information can be received via cell-specific upper layer signaling. That is, the terminal can receive SBFD subband configuration information from the base station via cell-specific RRC signaling. The terminal can receive the TDD configuration information and SBFD subband configuration information to configure a format for each slot.

[0144] The base station may transmit configuration information related to beam failure detection and configuration information related to beam failure recovery to the terminal for radio link monitoring. In one example, the configuration information related to beam failure detection and configuration information related to beam failure recovery may be transmitted as an RRC message. For example, the configuration information related to beam failure detection may be transmitted via RadioLinkMonitoringConfig. Additionally, the configuration information related to beam failure recovery may be transmitted via BeamFailureRecoveryConfig, which includes RACH resource configuration information and candidate beam configuration information.

[0145] When a base station configures a subband full duplex (SBFD) symbol to support subband-based full duplex operation, at least one of a beam failure detection operation and a beam failure recovery operation can be performed separately for each of the SBFD symbol and the non-SBFD symbol. That is, when an SBFD symbol is configured for a terminal, the base station can perform independent beam failure detection and beam failure recovery procedures for the SBFD symbol and the non-SBFD symbol.

[0146] For example, whether separate beam failure detection and beam failure recovery procedures are configured for SBFD symbols may be determined based on the capabilities of the terminal. In this case, the base station may receive capability information of the terminal from the terminal to the base station through capability signaling. The base station may additionally set whether to separately configure beam failure detection and beam failure recovery procedures for SBFD symbols and non-SBFD symbols based on the capabilities of the terminal. If the beam failure detection and beam failure recovery procedures are separately configured by symbol type by the base station, the base station may independently perform the beam failure detection and beam failure recovery procedures with the terminal for SBFD symbols and non-SBFD symbols.

[0147] Alternatively, the base station may be configured to perform the beam failure detection procedure separately depending on the type of symbol, i.e., depending on non-SBFD symbols and SBFD symbols, while performing the beam failure recovery procedure based on common configuration information. Alternatively, the base station may be configured to perform the beam failure recovery procedure separately depending on the type of symbol, while performing the beam failure detection procedure based on common configuration information.

[0148] Whether to configure beam failure detection and beam failure recovery procedures separately in SBFD symbols and non-SBFD symbols can be explicitly set by the base station via RRC signaling.

[0149] Alternatively, whether beam failure detection and beam failure recovery procedures are configured separately in BFD symbols and non-SBFD symbols can be implicitly configured. According to the implicit configuration method, configuration information related to beam failure detection and / or configuration information related to beam failure recovery can be configured through separate RRC message settings for beam failure detection and recovery in SBFD symbols. That is, at least one of the configuration information related to beam failure detection and the configuration information related to beam failure recovery can be configured separately for each of the SBFD symbol and the non-SBFD symbol and transmitted to the terminal.

[0150] In this case, configuration information related to beam failure detection for the SBFD symbol can be transmitted to the terminal through a separate RRC message, such as RadioLinkMonitoringConfig_SBFD, in addition to the existing RadioLinkMonitoringConfig. In addition, configuration information related to beam failure recovery for the SBFD symbol can be transmitted through a separate RRC message, such as BeamFailureRecoveryConfig_SBFD, in addition to the existing BeamFailureRecoveryConfig.

[0151] Accordingly, as described above, when the beam failure detection and beam failure recovery procedures are configured separately for each symbol type, configuration information related to beam failure detection and / or configuration information related to beam failure recovery may be configured separately for each SBFD symbol and non-SBFD symbol, respectively. Alternatively, when only the beam failure detection procedure is configured separately for each symbol type, configuration information related to beam failure detection may be configured separately for each SBFD symbol and non-SBFD symbol, respectively. Alternatively, when only the beam failure recovery procedure is configured separately for each symbol type, configuration information related to beam failure recovery may be configured separately for each SBFD symbol and non-SBFD symbol, respectively.

[0152] For example, each of the configuration information related to beam failure detection and the configuration information related to beam failure recovery configured for an SBFD symbol may be configured to include at least a portion of all parameters included in each of the configuration information related to beam failure detection and the configuration information related to beam failure recovery configured for a non-SBFD symbol. That is, the configuration information related to beam failure detection and the configuration information related to beam failure recovery configured separately for an SBFD symbol may include all or a portion of the parameters included in existing configuration information, i.e., the configuration information related to beam failure detection and the configuration information related to beam failure recovery configured for a non-SBFD symbol. If only a portion of the parameters is included, the values ​​of the existing configuration information may be used for the parameters that are not included.

[0153] Alternatively, according to an example, each of the configuration information related to beam failure detection configured for the SBFD symbol and the configuration information related to beam failure recovery may be configured in a form that is included in each of the configuration information related to beam failure detection configured for the non-SBFD symbol and the configuration information related to beam failure recovery. That is, the configuration information related to beam failure detection and the configuration information related to beam failure recovery configured separately for the SBFD symbol may be configured as part of the existing configuration information.

[0154] For example, if at least one of a beam failure detection operation and a beam failure recovery operation is performed separately for each of an SBFD symbol and a non-SBFD symbol, the reference signal and radio resources used for the beam failure detection operation and the beam failure recovery operation may be configured only for symbols of the same type. For example, when the base station sets a monitoring reference signal for beam failure detection of the terminal, the monitoring reference signal for beam failure detection of the SBFD symbol may be configured to be limited to a reference signal transmitted through the SBFD symbol. If the monitoring reference signal includes transmissions in both the SBFD symbol and the non-SBFD symbol, the base station may configure the terminal to be limited to transmission instances in the SBFD symbol.

[0155] Similarly, the base station may configure the terminal to limit the monitoring reference signal for beam failure detection of non-SBFD symbols to reference signals transmitted via non-SBFD symbols. If the monitoring reference signal includes transmissions in both SBFD and non-SBFD symbols, the base station may configure the terminal to limit the transmission instances to those in non-SBFD symbols.

[0156] As another example, the base station can configure the terminal to limit the candidate beam lists for beam failure recovery to symbols of the same type. That is, the base station can configure the terminal to limit SBFD symbol target recovery to reference signals transmitted via SBFD symbols, and non-SBFD symbol target recovery to reference signals transmitted via non-SBFD symbols.

[0157] As another example, the base station may configure the terminal to limit the RACH resource settings for beam failure recovery of the terminal to RACH resource settings belonging to the same symbol type.

[0158] The above description assumes that beam failure detection and beam failure recovery procedures are configured separately depending on the symbol type. However, according to another example, the integrated procedure can be set by the base station without distinguishing between non-SBFD and SBFD symbols. In this case, the base station can perform beam failure detection and beam failure recovery procedures with the terminal by integrating SBFD and non-SBFD symbols without distinguishing between them.

[0159] Referring again to FIG. 11, the base station performs a beam failure detection operation based on configuration information related to beam failure detection (S1120), and when beam failure recovery is triggered based on beam failure detection, the base station may perform a beam failure recovery operation based on configuration information related to beam failure recovery (S1130).

[0160] The base station can perform beam failure detection procedures and beam failure recovery procedures with the terminal based on configuration information related to beam failure detection and configuration information related to beam failure recovery. In this case, as described above, the following procedures can be performed depending on whether the configuration information related to beam failure detection and configuration information related to beam failure recovery are separately configured for the SBFD symbol.

[0161] The MAC sublayer of the terminal can detect beam failure based on periodic Beam Failure Instance (BFI) reporting results from the physical layer (PHY). The downlink reference signal that the terminal should monitor for beam failure detection is determined by the CSI-RS or SSB, which are CORESET beam reference signals for PDCCH monitoring, and the reference signal for beam failure detection can be explicitly set by the base station. Alternatively, if not set, the terminal can determine BFI by monitoring all CORESET beam reference signals.

[0162] Additionally, the MAC sublayer of the terminal may declare a beam failure and perform a beam failure recovery procedure according to configuration information regarding beam failure recovery when N BFIs, determined by the beamFailureInstanceMaxCount setting value, are received from the PHY during M reporting intervals, determined by the beamFailureDetectionTimer setting value.

[0163] Accordingly, a method and device for performing beam failure recovery in an environment where full-duplex communication is applied can be provided.

[0164]

[0165] Hereinafter, each embodiment related to a method for performing beam failure recovery in a wireless mobile communication system will be specifically described with reference to related drawings.

[0166] According to the beam failure detection and recovery procedure of the existing terminal, the terminal receives configuration information for beam failure detection through RadioLinkMonitoringConfig, which is configuration information for radio link monitoring, from the base station. In addition, based on the radio link monitoring configuration, the terminal receives BeamFailureRecoveryConfig information, which includes RACH (Random Access Channel) resource configuration information and candidate beam configuration information for beam failure recovery, from the base station when beam failure is detected. The information areas included in the RadioLinkMonitoringConfig and BeamFailureRecoveryConfig information are as shown in FIGS. 12 and 13.

[0167] The MAC (Medium Access Control) sublayer of the terminal can detect beam failure based on the periodic BFI (Beam Failure Instance) reporting results from the PHY (Physical layer). The downlink reference signal that the terminal should monitor for beam failure detection can be determined by the CORESET beam RS (reference signal) (CSI-RS or SSB) for PDCCH monitoring. In this case, if the RS for beam failure detection is explicitly set by the base station or the RS is not set, the terminal monitors all CORESET beam RSs to determine the BFI. The MAC sublayer of the terminal declares a beam failure when N BFIs, determined by the beamFailureInstanceMaxCount setting value, are received from the PHY during M reporting intervals, determined by the beamFailureDetectionTimer setting value, and performs a beam failure recovery procedure according to the BeamFailureRecoveryConfig.

[0168] In the present disclosure, as described above, we propose a beam failure recovery method for a terminal in an arbitrary NR cell including an SBFD symbol configured with UL and DL subbands for SBFD operation. In particular, we propose a method for performing independent beam failure detection and recovery in the SBFD symbol and non-SBFD symbol at the terminal.

[0169] According to one example of the present disclosure, a terminal may perform independent beam failure detection and recovery procedures in SBFD symbols and non-SBFD symbols. When a base station configures UL / DL subbands for SBFD support and configures SBFD slots / symbols accordingly, the terminal may independently perform separate beam failure detection and recovery procedures in SBFD symbols and non-SBFD symbols, respectively. This may be determined based on the capability of the terminal, and the corresponding capability may be notified to the base station through capability signaling. The base station may additionally configure whether to perform separate beam failure detection and recovery in SBFD symbols and non-SBFD symbols based on the capability of the terminal. Accordingly, a terminal for which separate beam failure monitoring is configured by the base station can independently perform the above-described beam failure detection and recovery procedures in SBFD symbols and non-SBFD symbols.

[0170] Alternatively, the terminal may perform beam failure detection separately, but recovery based on a common configuration. Alternatively, the terminal may perform beam failure recovery procedures separately for non-SBFD symbols and SBFD symbols, but perform beam failure detection based on a common configuration. Alternatively, the base station may configure joint beam failure monitoring without distinction between non-SBFD symbols and SBFD symbols, in which case the terminal may perform beam failure detection and recovery by integrating SBFD symbols and non-SBFD symbols.

[0171] Whether separate beam failure monitoring is enabled can be explicitly set by the base station or implicitly. The explicit setting is done by the base station via RRC signaling.

[0172] The implicit configuration method can be achieved by configuring separate RRC messages for beam failure detection and recovery in SBFD symbols such as separate RadioLinkMonitoringConfig_SBFD or / and BeamFailureRecoveryConfig_SBFD.

[0173] A terminal configured with separate beam failure monitoring can receive separate RRC messages for beam failure monitoring and recovery in SBFD symbols, along with beamfailure monitoring configuration information and recovery configuration information for non-SBFD symbols, from the base station. That is, the terminal can receive separate RadioLinkMonitoringConfig_SBFD and / or BeamFailureRecoveryConfig_SBFD information from the base station, along with existing RadioLinkMonitoringConfig and BeamFailureRecoveryConfig configuration information. The information fields constituting the RadioLinkMonitoringConfig_SBFD and BeamFailureRecoveryConfig_SBFD can be configured as a subset of the set of information fields constituting the above RadioLinkMonitoringConfig and BeamFailureRecoveryConfig. In this case, information fields not included in RadioLinkMonitoringConfig_SBFD and BeamfailureRecoveryConfig_SBFD can follow the existing RadioLinkMonitoringConfig and BeamFailureRecoveryConfig settings.

[0174] Alternatively, when configuring the information area within a RadioLinkMonitoringConfig and / or BeamfailureRecoveryConfig message, an additional information area for SBFD symbols may be defined in addition to the information area for non-SBFD symbols and configured by the base station.

[0175] As described above, if separate beam failure detection and / or recovery in non-SBFD symbols and SBFD symbols are set by the base station, and separate RadioLinkMonitoringConfig_SBFD and / or BeamFailureRecoveryConfig_SBFD for SBFD symbols are set accordingly, or if existing RadioLinkMonitoringConfig and / or BeamFailureRecoveryConfig messages include separate configuration information for SBFD symbols, certain restrictions may be defined on some configurations and thus beam failure detection and recovery procedures of the terminal.

[0176] For example, when the terminal configures the radiolink monitoring RS for beam failure detection, the monitoring RS for beam failure detection of the SBFD symbol may be configured to be limited to an RS that transmits through the SBFD symbol. Alternatively, in the case of an RS that includes transmissions in both SBFD symbols and non-SBFD symbols, the RS may be limited to transmission instances in the SBFD symbol.

[0177] Similarly, the radiolink monitoring RS for beam failure detection of non-SBFD can also be configured to be limited to RSs that transmit via non-SBFD symbols. Alternatively, for RSs that include transmissions in both SBFD and non-SBFD symbols, the RS can be limited to transmission instances in non-SBFD symbols.

[0178] As another example, the terminal may also limit candidate beam lists for beam failure recovery to symbols of the same type. That is, recovery for SBFD symbols may be limited to RSs that transmit via SBFD symbols, and recovery for non-SBFD symbols may be limited to RSs that transmit via non-SBFD symbols.

[0179] As another example, RACH resource configuration for beam failure recovery of a terminal may also be restricted to RACH resource configuration belonging to the same symbol type.

[0180] With respect to the above-described embodiments, each embodiment is included in the scope of the invention according to the present disclosure not only in an independent case but also in all cases in which the embodiments are combined.

[0181]

[0182] Hereinafter, the configuration of a terminal and a base station capable of performing some or all of the embodiments described with reference to FIGS. 1 to 13 will be described with reference to the drawings. The above description may be omitted to avoid redundant description, and in this case, the omitted content may be substantially equally applied to the following description, as long as it does not contradict the technical spirit of the invention.

[0183] Fig. 14 is a drawing showing the configuration of a terminal (1400) according to another embodiment.

[0184] Referring to FIG. 14, a terminal (1400) according to another embodiment includes a transmitter (1420), a receiver (1430), and a control unit (1410) that controls the operations of the transmitter and receiver.

[0185] The control unit (1410) controls the overall operation of the terminal (1400) according to the method for performing beam failure recovery in a wireless mobile communication system required to perform the present invention described above.

[0186] The control unit (1410) may receive configuration information related to beam failure detection (BFD) and configuration information related to beam failure recovery. The control unit (1410) may receive configuration information related to beam failure detection and configuration information related to beam failure recovery from a base station for radio link monitoring. In one example, the configuration information related to beam failure detection and configuration information related to beam failure recovery may be received as an RRC message. For example, the configuration information related to beam failure detection may be received via RadioLinkMonitoringConfig. In addition, the configuration information related to beam failure recovery may be received via BeamFailureRecoveryConfig, which includes RACH resource configuration information and candidate beam configuration information.

[0187] When a subband full duplex (SBFD) symbol is configured by a base station to support subband-based full duplex operation, at least one of a beam failure detection operation and a beam failure recovery operation may be performed separately for each of the SBFD symbol and the non-SBFD symbol. That is, when an SBFD symbol is configured for a terminal, the control unit (1410) may perform independent beam failure detection and beam failure recovery procedures for the SBFD symbol and the non-SBFD symbol.

[0188] For example, whether separate beam failure detection and beam failure recovery procedures are configured for SBFD symbols may be determined based on the capabilities of the terminal. In this case, the control unit (1410) may report capability information of the terminal to the base station through capability signaling. The base station may additionally set whether to separately configure beam failure detection and beam failure recovery procedures for SBFD symbols and non-SBFD symbols based on the capabilities of the terminal. If the beam failure detection and beam failure recovery procedures are separately configured by symbol type by the base station, the control unit (1410) may independently perform the beam failure detection and beam failure recovery procedures with the base station for SBFD symbols and non-SBFD symbols.

[0189] Alternatively, the control unit (1410) may be configured to separately perform the beam failure detection procedure according to the type of symbol, i.e., according to non-SBFD symbols and SBFD symbols, while performing the beam failure recovery procedure based on common configuration information. Alternatively, the control unit (1410) may be configured to separately perform the beam failure recovery procedure according to the type of symbol, while performing the beam failure detection procedure based on common configuration information.

[0190] Whether to configure beam failure detection and beam failure recovery procedures separately in SBFD symbols and non-SBFD symbols can be explicitly set by the base station via RRC signaling.

[0191] Alternatively, whether beam failure detection and beam failure recovery procedures are configured separately in BFD symbols and non-SBFD symbols can be implicitly configured. According to the implicit configuration method, configuration information related to beam failure detection and / or configuration information related to beam failure recovery can be configured through separate RRC message settings for beam failure detection and recovery in SBFD symbols. That is, at least one of the configuration information related to beam failure detection and the configuration information related to beam failure recovery can be separately configured and received for each of the SBFD symbol and the non-SBFD symbol.

[0192] In this case, configuration information related to beam failure detection for the SBFD symbol can be received through a separate RRC message, such as RadioLinkMonitoringConfig_SBFD, in addition to the existing RadioLinkMonitoringConfig. In addition, configuration information related to beam failure recovery for the SBFD symbol can be received through a separate RRC message, such as BeamFailureRecoveryConfig_SBFD, in addition to the existing BeamFailureRecoveryConfig.

[0193] Accordingly, as described above, when the beam failure detection and beam failure recovery procedures are configured separately for each symbol type, configuration information related to beam failure detection and / or configuration information related to beam failure recovery may be configured separately for each SBFD symbol and non-SBFD symbol, respectively. Alternatively, when only the beam failure detection procedure is configured separately for each symbol type, configuration information related to beam failure detection may be configured separately for each SBFD symbol and non-SBFD symbol, respectively. Alternatively, when only the beam failure recovery procedure is configured separately for each symbol type, configuration information related to beam failure recovery may be configured separately for each SBFD symbol and non-SBFD symbol, respectively.

[0194] For example, each of the configuration information related to beam failure detection and the configuration information related to beam failure recovery configured for an SBFD symbol may be configured to include at least a portion of all parameters included in each of the configuration information related to beam failure detection and the configuration information related to beam failure recovery configured for a non-SBFD symbol. That is, the configuration information related to beam failure detection and the configuration information related to beam failure recovery configured separately for an SBFD symbol may include all or a portion of the parameters included in existing configuration information, i.e., the configuration information related to beam failure detection and the configuration information related to beam failure recovery configured for a non-SBFD symbol. If only a portion of the parameters is included, the values ​​of the existing configuration information may be used for the parameters that are not included.

[0195] Alternatively, according to an example, each of the configuration information related to beam failure detection configured for the SBFD symbol and the configuration information related to beam failure recovery may be configured in a form that is included in each of the configuration information related to beam failure detection configured for the non-SBFD symbol and the configuration information related to beam failure recovery. That is, the configuration information related to beam failure detection and the configuration information related to beam failure recovery configured separately for the SBFD symbol may be configured as part of the existing configuration information.

[0196] For example, if at least one of a beam failure detection operation and a beam failure recovery operation is performed separately for each of an SBFD symbol and a non-SBFD symbol, the reference signal and radio resources used for the beam failure detection operation and the beam failure recovery operation may be configured only for symbols of the same type. For example, the control unit (1410) may be configured to limit the monitoring reference signal for beam failure detection of an SBFD symbol to a reference signal transmitted through the SBFD symbol when setting the monitoring reference signal for beam failure detection. If the monitoring reference signal includes transmissions in both an SBFD symbol and a non-SBFD symbol, the control unit (1410) may be configured to limit it to transmission instances in the SBFD symbol.

[0197] Similarly, the control unit (1410) may be configured to limit the monitoring reference signal for beam failure detection of non-SBFD symbols to reference signals transmitted via non-SBFD symbols. If the monitoring reference signal includes transmissions in both SBFD symbols and non-SBFD symbols, the control unit (1410) may be configured to limit the monitoring reference signal to transmission instances in non-SBFD symbols.

[0198] As another example, the control unit (1410) may be configured to limit candidate beam lists for beam failure recovery to symbols of the same type. That is, the control unit (1410) may be configured to limit SBFD symbol target recovery to reference signals transmitted via SBFD symbols, and to limit non-SBFD symbol target recovery to reference signals transmitted via non-SBFD symbols.

[0199] As another example, the control unit (1410) may be configured to limit the RACH resource settings for beam failure recovery of the terminal to RACH resource settings belonging to the same symbol type.

[0200] The control unit (1410) may perform a beam failure detection operation based on configuration information related to beam failure detection, and when beam failure recovery is triggered based on beam failure detection, may perform a beam failure recovery operation based on configuration information related to beam failure recovery. The control unit (1410) may perform a beam failure detection procedure and a beam failure recovery procedure based on configuration information related to beam failure detection and configuration information related to beam failure recovery. In this case, as described above, each procedure may be performed depending on whether the configuration information related to beam failure detection and the configuration information related to beam failure recovery are separately configured for the SBFD symbol.

[0201] Accordingly, a method and device for performing beam failure recovery in an environment where full-duplex communication is applied can be provided.

[0202] Fig. 15 is a drawing showing the configuration of a base station (1500) according to another embodiment.

[0203] Referring to FIG. 15, a base station (1500) according to another embodiment includes a transmitter (1520), a receiver (1530), and a control unit (1510) that controls the operations of the transmitter and receiver.

[0204] The control unit (1510) controls the overall operation of the base station (1500) according to the method for performing beam failure recovery in a wireless mobile communication system required to perform the aforementioned present invention. The transmitter (1520) transmits downlink control information, data, and messages to the terminal through the corresponding channel. The receiver (1530) receives uplink control information, data, and messages from the terminal through the corresponding channel.

[0205] The control unit (1510) may transmit configuration information related to beam failure detection (BFD) and configuration information related to beam failure recovery. The control unit (1510) may transmit configuration information related to beam failure detection and configuration information related to beam failure recovery to the terminal for radio link monitoring. According to an example, the configuration information related to beam failure detection and configuration information related to beam failure recovery may be transmitted as an RRC message. For example, the configuration information related to beam failure detection may be transmitted via RadioLinkMonitoringConfig. In addition, the configuration information related to beam failure recovery may be transmitted via BeamFailureRecoveryConfig, which includes RACH resource configuration information and candidate beam configuration information.

[0206] When a subband full duplex (SBFD) symbol is configured by the control unit (1510) to support subband-based full duplex operation, at least one of a beam failure detection operation and a beam failure recovery operation may be performed separately for each of the SBFD symbol and the non-SBFD symbol. That is, when an SBFD symbol is configured for a terminal, the control unit (1510) may perform independent beam failure detection and beam failure recovery procedures on the SBFD symbol and the non-SBFD symbol.

[0207] For example, whether separate beam failure detection and beam failure recovery procedures are configured for SBFD symbols may be determined based on the capabilities of the terminal. In this case, the control unit (1510) may receive capability information of the terminal from the terminal to the base station through capability signaling. The control unit (1510) may additionally set whether to separately configure beam failure detection and beam failure recovery procedures for SBFD symbols and non-SBFD symbols based on the capabilities of the terminal. When the beam failure detection and beam failure recovery procedures are separately configured for each symbol type by the control unit (1510), the control unit (1510) may independently perform the beam failure detection and beam failure recovery procedures with the terminal for SBFD symbols and non-SBFD symbols.

[0208] Alternatively, the control unit (1510) may be configured to separately perform the beam failure detection procedure according to the type of symbol, i.e., according to non-SBFD symbols and SBFD symbols, while performing the beam failure recovery procedure based on common configuration information. Alternatively, the control unit (1510) may be configured to separately perform the beam failure recovery procedure according to the type of symbol, while performing the beam failure detection procedure based on common configuration information.

[0209] Whether to configure beam failure detection and beam failure recovery procedures separately in SBFD symbols and non-SBFD symbols can be explicitly set by the base station via RRC signaling.

[0210] Alternatively, whether beam failure detection and beam failure recovery procedures are configured separately in BFD symbols and non-SBFD symbols can be implicitly configured. According to the implicit configuration method, configuration information related to beam failure detection and / or configuration information related to beam failure recovery can be configured through separate RRC message settings for beam failure detection and recovery in SBFD symbols. That is, at least one of the configuration information related to beam failure detection and the configuration information related to beam failure recovery can be configured separately for each of the SBFD symbol and the non-SBFD symbol and transmitted to the terminal.

[0211] In this case, configuration information related to beam failure detection for the SBFD symbol can be transmitted to the terminal through a separate RRC message, such as RadioLinkMonitoringConfig_SBFD, in addition to the existing RadioLinkMonitoringConfig. In addition, configuration information related to beam failure recovery for the SBFD symbol can be transmitted through a separate RRC message, such as BeamFailureRecoveryConfig_SBFD, in addition to the existing BeamFailureRecoveryConfig.

[0212] Accordingly, as described above, when the beam failure detection and beam failure recovery procedures are configured separately for each symbol type, configuration information related to beam failure detection and / or configuration information related to beam failure recovery may be configured separately for each SBFD symbol and non-SBFD symbol, respectively. Alternatively, when only the beam failure detection procedure is configured separately for each symbol type, configuration information related to beam failure detection may be configured separately for each SBFD symbol and non-SBFD symbol, respectively. Alternatively, when only the beam failure recovery procedure is configured separately for each symbol type, configuration information related to beam failure recovery may be configured separately for each SBFD symbol and non-SBFD symbol, respectively.

[0213] For example, each of the configuration information related to beam failure detection and the configuration information related to beam failure recovery configured for an SBFD symbol may be configured to include at least a portion of all parameters included in each of the configuration information related to beam failure detection and the configuration information related to beam failure recovery configured for a non-SBFD symbol. That is, the configuration information related to beam failure detection and the configuration information related to beam failure recovery configured separately for an SBFD symbol may include all or a portion of the parameters included in existing configuration information, i.e., the configuration information related to beam failure detection and the configuration information related to beam failure recovery configured for a non-SBFD symbol. If only a portion of the parameters is included, the values ​​of the existing configuration information may be used for the parameters that are not included.

[0214] Alternatively, according to an example, each of the configuration information related to beam failure detection configured for the SBFD symbol and the configuration information related to beam failure recovery may be configured in a form that is included in each of the configuration information related to beam failure detection configured for the non-SBFD symbol and the configuration information related to beam failure recovery. That is, the configuration information related to beam failure detection and the configuration information related to beam failure recovery configured separately for the SBFD symbol may be configured as part of the existing configuration information.

[0215] For example, if at least one of a beam failure detection operation and a beam failure recovery operation is performed separately for each of an SBFD symbol and a non-SBFD symbol, the reference signal and radio resources used for the beam failure detection operation and the beam failure recovery operation may be configured only for symbols of the same type. For example, the control unit (1510) may configure the monitoring reference signal for beam failure detection of the terminal to be limited to a reference signal transmitted through the SBFD symbol when setting the monitoring reference signal for beam failure detection of the SBFD symbol. If the monitoring reference signal includes transmissions in both the SBFD symbol and the non-SBFD symbol, the control unit (1510) may configure the terminal to be limited to transmission instances in the SBFD symbol.

[0216] Similarly, the control unit (1510) may configure the terminal to limit the monitoring reference signal for beam failure detection of non-SBFD symbols to reference signals transmitted via non-SBFD symbols. If the monitoring reference signal includes transmissions in both SBFD symbols and non-SBFD symbols, the control unit (1510) may configure the terminal to limit the transmission instances to those in non-SBFD symbols.

[0217] As another example, the control unit (1510) may configure the terminal to limit the candidate beam lists for beam failure recovery to symbols of the same type. That is, the control unit (1510) may configure the terminal to limit SBFD symbol target recovery to reference signals transmitted via SBFD symbols, and to limit non-SBFD symbol target recovery to reference signals transmitted via non-SBFD symbols.

[0218] As another example, the control unit (1510) may configure the terminal to limit the RACH resource settings for beam failure recovery of the terminal to RACH resource settings belonging to the same symbol type.

[0219] The control unit (1510) may perform a beam failure detection operation based on configuration information related to beam failure detection, and when beam failure recovery is triggered based on beam failure detection, may perform a beam failure recovery operation based on configuration information related to beam failure recovery. The control unit (1510) may perform a beam failure detection procedure and a beam failure recovery procedure with the terminal based on the configuration information related to beam failure detection and the configuration information related to beam failure recovery. In this case, as described above, each procedure may be performed depending on whether the configuration information related to beam failure detection and the configuration information related to beam failure recovery are separately configured for the SBFD symbol.

[0220] Accordingly, a method and device for performing beam failure recovery in an environment where full-duplex communication is applied can be provided.

[0221] The above-described embodiments may be supported by standard documents disclosed in at least one of the wireless access systems, IEEE 802, 3GPP, and 3GPP2. That is, steps, components, and parts not described in the present embodiments to clearly illustrate the technical concepts herein may be supported by the above-described standard documents. Furthermore, all terms disclosed in this specification may be explained by the above-described standard documents.

[0222] The embodiments described above may be implemented through various means. For example, the embodiments may be implemented through hardware, firmware, software, or a combination thereof.

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

[0224] When implemented using firmware or software, the methods according to the present embodiments may be implemented in the form of devices, procedures, or functions that perform the functions or operations described above. The software code may be stored in a memory unit and executed by a processor. The memory unit may be located within or outside the processor and may exchange data with the processor using various known means.

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

[0226] The above description is merely an illustrative example of the technical idea of ​​the present disclosure, and those skilled in the art to which the present disclosure pertains will appreciate that various modifications and variations can be made without departing from the essential characteristics of the technical idea of ​​the present disclosure. In addition, the present embodiments are not intended to limit the technical idea of ​​the present disclosure but rather to explain it, and therefore the scope of the technical idea of ​​the present disclosure is not limited by these embodiments. The scope of protection of the present disclosure should be interpreted by the claims below, and all technical ideas within a scope equivalent thereto should be interpreted as being included within the scope of the rights of the present disclosure.

[0227]

[0228] CROSS-REFERENCE TO RELATED APPLICATION

[0229] This patent application claims priority under 35 USC §119(a) to Korean Patent Application No. 10-2024-0022610, filed in Korea on February 16, 2024, and Korean Patent Application No. 10-2025-0019515, filed in Korea on February 14, 2025, the entire contents of which are incorporated herein by reference. In addition, this patent application claims priority in countries other than the United States for the same reasons, the entire contents of which are incorporated herein by reference.

Claims

1. In a method for a terminal to perform beam failure recovery (BFR), A step of receiving configuration information related to beam failure detection (BFD) and configuration information related to beam failure recovery; A step of performing a beam failure detection operation based on configuration information related to the above beam failure detection; and Including a step of performing a beam failure recovery operation based on configuration information related to the beam failure recovery when beam failure recovery is triggered based on beam failure detection, A method in which, when a SBFD symbol is configured by a base station to support a subband full duplex (SBFD) operation, at least one of the beam failure detection operation and the beam failure recovery operation is performed separately for each of the SBFD symbol and the non-SBFD symbol.

2. In paragraph 1, At least one of the configuration information related to the beam failure detection and the configuration information related to the beam failure recovery, A method in which the SBFD symbol and the non-SBFD symbol are separately configured and received.

3. In paragraph 2, Each of the configuration information related to the beam failure detection configured for the above SBFD symbol and the configuration information related to the beam failure recovery, A method configured to include at least a portion of all parameters included in each of the configuration information related to the beam failure detection configured for the non-SBFD symbol and the configuration information related to the beam failure recovery.

4. In paragraph 2, Each of the configuration information related to the beam failure detection configured for the above SBFD symbol and the configuration information related to the beam failure recovery, A method configured in a form that includes configuration information related to the beam failure detection configured for the non-SBFD symbol and configuration information related to the beam failure recovery, respectively.

5. In paragraph 1, If at least one of the beam failure detection operation and the beam failure recovery operation is performed separately for each of the SBFD symbol and the non-SBFD symbol, the reference signal and radio resource used for the beam failure detection operation and the beam failure recovery operation are, A method that is configured only for symbols of the same type.

6. In a method for a base station to perform beam failure recovery (BFR), A step of transmitting configuration information related to beam failure detection (BFD) and configuration information related to beam failure recovery; A step of performing a beam failure detection operation based on configuration information related to the above beam failure detection; and Including a step of performing a beam failure recovery operation based on configuration information related to the beam failure recovery when beam failure recovery is triggered based on beam failure detection, A method in which, when a subband full duplex (SBFD) symbol is configured by the base station to support subband-based full duplex communication (SBFD) operation, at least one of the beam failure detection operation and the beam failure recovery operation is performed separately for each of the SBFD symbol and the non-SBFD symbol.

7. In paragraph 6, At least one of the configuration information related to the beam failure detection and the configuration information related to the beam failure recovery, A method in which the SBFD symbol and the non-SBFD symbol are separately configured and transmitted.

8. In paragraph 7, Each of the configuration information related to the beam failure detection configured for the above SBFD symbol and the configuration information related to the beam failure recovery, A method configured to include at least a portion of all parameters included in each of the configuration information related to the beam failure detection configured for the non-SBFD symbol and the configuration information related to the beam failure recovery.

9. In paragraph 7, Each of the configuration information related to the beam failure detection configured for the above SBFD symbol and the configuration information related to the beam failure recovery, A method configured in a form that includes configuration information related to the beam failure detection configured for the non-SBFD symbol and configuration information related to the beam failure recovery, respectively.

10. In paragraph 6, If at least one of the beam failure detection operation and the beam failure recovery operation is performed separately for each of the SBFD symbol and the non-SBFD symbol, the reference signal and radio resource used for the beam failure detection operation and the beam failure recovery operation are, A method that is configured only for symbols of the same type.

11. In a terminal performing beam failure recovery (BFR), Transmitter; Receiver; and Including a control unit that controls the operation of the above transmitter and receiver, The control unit receives configuration information related to beam failure detection (BFD) and configuration information related to beam failure recovery, performs a beam failure detection operation based on the configuration information related to beam failure detection, and, when beam failure recovery is triggered based on beam failure detection, performs a beam failure recovery operation based on the configuration information related to beam failure recovery. A terminal in which, when a SBFD symbol is configured by a base station to support subband full duplex (SBFD) operation, at least one of the beam failure detection operation and the beam failure recovery operation is performed separately for each of the SBFD symbol and the non-SBFD symbol.

12. In paragraph 11, At least one of the configuration information related to the beam failure detection and the configuration information related to the beam failure recovery, A terminal configured and received separately for each of the above SBFD symbol and the above non-SBFD symbol.

13. In paragraph 12, Each of the configuration information related to the beam failure detection configured for the above SBFD symbol and the configuration information related to the beam failure recovery, A terminal configured to include at least a portion of all parameters included in each of the configuration information related to the beam failure detection configured for the non-SBFD symbol and the configuration information related to the beam failure recovery.

14. In paragraph 12, Each of the configuration information related to the beam failure detection configured for the above SBFD symbol and the configuration information related to the beam failure recovery, A terminal configured in a form that includes configuration information related to the beam failure detection configured for the non-SBFD symbol and configuration information related to the beam failure recovery, respectively.

15. In paragraph 11, If at least one of the beam failure detection operation and the beam failure recovery operation is performed separately for each of the SBFD symbol and the non-SBFD symbol, the reference signal and radio resource used for the beam failure detection operation and the beam failure recovery operation are, A terminal that is configured only for symbols of the same type.

Images