Terminal, wireless communication method, base station and system

Abstract

The present disclosure appropriately performs beam fault detection or beam fault recovery even when a plurality of transmission / reception points are used. A terminal according to one embodiment of the present disclosure has: a reception unit for receiving information that pertains to settings for beam fault detection for each transmission / reception point (TRP) and information that pertains to settings for an uplink control channel resource corresponding to a scheduling request; and, a control unit that, when a beam fault is detected in a first TRP, controls transmission of the scheduling request by using either an uplink control channel resource that corresponds to the first TRP or an uplink control channel resource that corresponds to a second TRP different from the first TRP.

Description

Terminal, wireless communication method and base station

[0001] The present disclosure relates to a terminal, a wireless communication method, and a base station in a next-generation mobile communication system.

[0002] Long Term Evolution (LTE) has been specified for the Universal Mobile Telecommunications System (UMTS) network with the aim of achieving higher data rates and lower latency (Non-Patent Document 1). Also, LTE-Advanced (3GPP Rel. 10-14) has been specified with the aim of achieving higher capacity and more advanced features than LTE (Third Generation Partnership Project (3GPP) Release (Rel.) 8, 9).

[0003] Successor systems to LTE (e.g., 5th generation mobile communication system (5G), 5G+ (plus), 6th generation mobile communication system (6G), New Radio (NR), 3GPP Rel. 15 or later, etc.) are also being considered.

[0004] In existing LTE systems (LTE Rel. 8-15), radio link quality is monitored (Radio Link Monitoring (RLM)). When a Radio Link Failure (RLF) is detected by RLM, a request is made to a user equipment (UE) to re-establish a Radio Resource Control (RRC) connection.

[0005] 3GPP TS 36.300 V8.12.0 “Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 (Release 8)”, April 2010

[0006] In future wireless communication systems (e.g., NR), it is being considered to implement a procedure for detecting beam failure and switching to another beam (which may also be called a Beam Failure Recovery (BFR) procedure, BFR, link recovery procedure, etc.).

[0007] In NR Rel. 17 and later, it is also assumed that a terminal (UE) will communicate using multiple transmission / reception points (TRPs) / UE panels. In this case, it is possible to perform beam management (e.g., beam failure detection) in multiple TRPs / multiple UE panels, but the problem is how to control beam failure detection (BFD) or beam failure recovery (BFR) in each TRP / UE panel. If beam failure detection or beam failure recovery in each TRP / UE panel cannot be properly controlled, there is a risk of a decrease in communication throughput or a deterioration in communication quality.

[0008] The present disclosure has been made in consideration of these points, and one of its objectives is to provide a terminal, a wireless communication method, and a base station that are capable of appropriately detecting beam faults or recovering from beam faults even when multiple transmission and reception points are used.

[0009] A terminal according to one aspect of the present disclosure has a receiving unit that receives information regarding the setting of beam failure detection for each transmitting / receiving point (TRP) and information regarding the setting of an uplink control channel resource corresponding to a scheduling request, and a control unit that, when a beam failure is detected in a first TRP, controls the transmission of a scheduling request using either the uplink control channel resource corresponding to the first TRP or the uplink control channel resource corresponding to a second TRP different from the first TRP.

[0010] According to one aspect of the present disclosure, beam failure detection or beam failure recovery can be performed appropriately even when multiple transmission and reception points are used.

[0011] Fig. 1 is a diagram showing an example of a beam recovery procedure in Rel. 15 NR. Figs. 2A to 2C are diagrams showing an example of setting PUCCH resources and spatial relationships in response to a scheduling request. Figs. 3A to 3C are diagrams showing an example of BFR types applied to each cell in a cell group according to the first aspect. Fig. 4 is a diagram showing an example of SR transmission control according to the first aspect. Figs. 5A and 5B are diagrams showing other examples of BFR types applied to each cell in a cell group according to the first embodiment. Fig. 6 is a diagram showing an example of SR transmission control according to the first aspect. Figs. 7A and 7B are diagrams showing an example of setting multiple SRs according to the second aspect. Fig. 8 is a diagram showing an example of association between TRP indexes and SR PUCCH resource indexes according to the third aspect. Figs. 9A and 9B are diagrams showing an example of association between TRP indexes and SR settings / SR PUCCH resource spatial relationships according to the fourth aspect. Fig. 10 is a diagram showing an example of a schematic configuration of a wireless communication system according to an embodiment. Fig. 11 is a diagram illustrating an example of a configuration of a base station according to an embodiment. Fig. 12 is a diagram illustrating an example of a configuration of a user terminal according to an embodiment. Fig. 13 is a diagram illustrating an example of a hardware configuration of a base station and a user terminal according to an embodiment.

[0012] (Beam Obstacle Detection) In NR, communication is performed using beamforming. For example, a UE and a base station (e.g., a gNB (gNodeB)) may use a beam used to transmit a signal (also referred to as a transmit beam, Tx beam, etc.) and a beam used to receive a signal (also referred to as a receive beam, Rx beam, etc.).

[0013] When beamforming is used, it is expected that radio link quality will deteriorate due to increased susceptibility to interference from obstacles. This deterioration in radio link quality may lead to frequent radio link failures (RLFs). Since RLFs require cell reconnection, frequent RLFs will result in degradation of system throughput.

[0014] In NR, in order to suppress the occurrence of RLF, when the quality of a specific beam deteriorates, a procedure for switching to another beam (which may be called Beam Recovery (BR), Beam Failure Recovery (BFR), L1 / L2 (Layer 1 / Layer 2) beam recovery, etc.) is performed. Note that the BFR procedure may also be simply called BFR.

[0015] Note that the beam failure (BF) in this disclosure may also be referred to as a link failure.

[0016] Figure 1 shows an example of a beam recovery procedure in Rel. 15 NR. The number of beams is merely an example and is not limited to this. In the initial state (step S101) of Figure 1, the UE performs measurements based on reference signal (RS) resources transmitted using two beams.

[0017] The RS may be at least one of a synchronization signal block (SSB) and a channel state measurement RS (Channel State Information RS (CSI-RS)). The SSB may also be called an SS / PBCH (Physical Broadcast Channel) block.

[0018] The RS may be at least one of a Primary Synchronization Signal (PSS), a Secondary Synchronization Signal (SSS), a Mobility Reference Signal (MRS), a signal included in an SSB, an SSB, a CSI-RS, a Demodulation Reference Signal (DMRS), a beam-specific signal, etc., or a signal configured by extending or modifying any of these. The RS measured in step S101 may also be called an RS for beam failure detection (Beam Failure Detection RS (BFD-RS)), an RS for use in a beam recovery procedure (BFR-RS), etc.

[0019] In step S102, the UE cannot detect the BFD-RS (or the reception quality of the RS deteriorates) due to interference with the radio waves from the base station. Such interference can occur due to, for example, obstacles, fading, interference, etc. between the UE and the base station.

[0020] The UE detects a beam failure when a predetermined condition is satisfied. For example, the UE may detect the occurrence of a beam failure when the block error rate (BLER) is less than a threshold for all configured BFD-RSs (BFD-RS resource configurations). When the occurrence of a beam failure is detected, a lower layer (physical (PHY) layer) of the UE may notify (indicate) a beam failure instance to an upper layer (MAC layer).

[0021] The criteria for the determination are not limited to BLER, but may be Layer 1 Reference Signal Received Power (L1-RSRP) in the physical layer. Also, instead of or in addition to RS measurement, beam failure detection may be performed based on a downlink control channel (Physical Downlink Control Channel (PDCCH)). The BFD-RS may be expected to be quasi-co-located (QCL) with the DMRS of the PDCCH monitored by the UE.

[0022] Here, the QCL is an index indicating the statistical properties of a channel. For example, if a signal / channel has a QCL relationship with another signal / channel, it may mean that it can be assumed that at least one of a Doppler shift, a Doppler spread, an average delay, a delay spread, and a spatial parameter (e.g., a spatial Rx parameter) is the same between these different signals / channels (i.e., the QCL is true for at least one of these).

[0023] The spatial reception parameters may correspond to a reception beam (e.g., a reception analog beam) of the UE, and the beam may be identified based on a spatial QCL. The QCL (or at least one element of the QCL) in the present disclosure may be replaced with sQCL (spatial QCL).

[0024] Information about BFD-RS (e.g., RS index, resource, number, number of ports, precoding, etc.), information about beam failure detection (BFD) (e.g., the above-mentioned threshold), etc. may be configured (notified) to the UE using higher layer signaling, etc. The information about BFD-RS may also be referred to as information about BFR resources, etc.

[0025] In the present disclosure, higher layer signaling may be, for example, any one of Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information, and the like, or a combination thereof.

[0026] The MAC signaling may use, for example, a Media Access Control Control Element (MAC CE), a MAC Protocol Data Unit (PDU), etc. The broadcast information may be, for example, a Master Information Block (MIB), a System Information Block (SIB), Remaining Minimum System Information (RMSI), Other System Information (OSI), etc.

[0027] When a beam failure instance notification is received from the UE's PHY layer, the UE's upper layer (e.g., MAC layer) may start a predetermined timer (which may be called a beam failure detection timer). If the UE's MAC layer receives a certain number of beam failure instance notifications (e.g., beamFailureInstanceMaxCount configured in RRC) before the timer expires, the UE's MAC layer may trigger a BFR (e.g., start one of the random access procedures described below).

[0028] The base station may determine that the UE has detected a beam failure if there is no notification from the UE or if it receives a predetermined signal (beam recovery request in step S104) from the UE.

[0029] In step S103, the UE starts searching for a new candidate beam to be used for new communication in order to recover the beam. The UE may select a new candidate beam corresponding to a predetermined RS by measuring the RS. The RS measured in step S103 may be called a new candidate RS, an RS for identifying a new candidate beam (New Candidate Beam Identification RS (NCBI-RS)), a CBI-RS, or a CB-RS (Candidate Beam RS). The NCBI-RS may be the same as or different from the BFD-RS. Note that the new candidate beam may simply be called a candidate beam or candidate RS.

[0030] The UE may determine a beam corresponding to an RS that satisfies a predetermined condition as a new candidate beam. The UE may determine a new candidate beam, for example, based on an RS among the configured NCBI-RSs whose L1-RSRP exceeds a threshold. Note that the criteria for determination are not limited to L1-RSRP. The L1-RSRP related to SSB may be referred to as SS-RSRP. The L1-RSRP related to CSI-RS may be referred to as CSI-RSRP.

[0031] Information about the NCBI-RS (e.g., RS resources, number of ports, precoding, etc.), information about the new candidate beam identification (NCBI) (e.g., the above-mentioned threshold), etc. may be configured (notified) to the UE using higher layer signaling, etc. Information about the new candidate RS (or NCBI-RS) may be acquired based on information about the BFD-RS. Information about the NCBI-RS may be referred to as information about NBCI resources, etc.

[0032] Note that BFD-RS, NCBI-RS, etc. may be read as Radio Link Monitoring RS (RLM-RS).

[0033] In step S104, the UE that has identified the new candidate beam transmits a beam failure recovery request (BFRQ). The beam recovery request may be referred to as a beam recovery request signal, a beam failure recovery request signal, or the like.

[0034] The BFRQ may be transmitted using, for example, at least one of an uplink control channel (Physical Uplink Control Channel (PUCCH)), a random access channel (Physical Random Access Channel (PRACH)), an uplink shared channel (Physical Uplink Shared Channel (PUSCH)), and a configured grant (CG) PUSCH.

[0035] The BFRQ may include information of the new candidate beam / new candidate RS identified in step S103. Resources for the BFRQ may be associated with the new candidate beam. The beam information may be notified using a beam index (BI), a port index of a predetermined reference signal, an RS index, a resource index (e.g., a CSI-RS Resource Indicator (CRI) or an SSB Resource Indicator (SSBRI)), etc.

[0036] In Rel. 15 NR, CB-BFR (Contention-Based BFR), which is a BFR based on a contention-based random access (RA) procedure, and CF-BFR (Contention-Free BFR), which is a BFR based on a contention-free random access procedure, are being considered. In CB-BFR and CF-BFR, the UE may use the PRACH resource to transmit a preamble (also referred to as an RA preamble, a random access channel (Physical Random Access Channel (PRACH)), a RACH preamble, etc.) as a BFRQ.

[0037] In CB-BFR, a UE may transmit a preamble randomly selected from one or more preambles. On the other hand, in CF-BFR, a UE may transmit a preamble assigned specifically to the UE by the base station. In CB-BFR, a base station may assign the same preamble to multiple UEs. In CF-BFR, a base station may assign a preamble individually to each UE.

[0038] Note that CB-BFR and CF-BFR may be referred to as CB PRACH-based BFR (contention-based PRACH-based BFR (CBRA-BFR)) and CF PRACH-based BFR (contention-free PRACH-based BFR (CFRA-BFR)), respectively. CBRA-BFR may be referred to as CBRA for BFR. CFRA-BFR may be referred to as CFRA for BFR.

[0039] Regardless of whether CB-BFR or CF-BFR is used, information about the PRACH resource (RA preamble) may be notified, for example, by higher layer signaling (such as RRC signaling). For example, the information may include information indicating a correspondence relationship between the detected DL-RS (beam) and the PRACH resource, and a different PRACH resource may be associated with each DL-RS.

[0040] In step S105, the base station that detected the BFRQ transmits a response signal (which may be referred to as a gNB response, etc.) to the BFRQ from the UE. The response signal may include reconfiguration information (e.g., DL-RS resource configuration information) for one or more beams.

[0041] The response signal may be transmitted, for example, in a UE common search space of the PDCCH. The response signal may be signaled using a PDCCH (DCI) scrambled with a cyclic redundancy check (CRC) by a UE identifier (e.g., a Cell-Radio RNTI (C-RNTI)). The UE may determine at least one of a transmit beam and a receive beam to use based on the beam reconfiguration information.

[0042] The UE may monitor the response signal based on at least one of a control resource set (CORESET) for BFR and a search space set for BFR.

[0043] For CB-BFR, contention resolution may be determined to be successful if the UE receives a PDCCH corresponding to its own C-RNTI.

[0044] Regarding the processing of step S105, a period for the UE to monitor a response from a base station (e.g., a gNB) to the BFRQ may be set. This period may be referred to as, for example, a gNB response window, a gNB window, a beam recovery request response window, etc. If no gNB response is detected within this window period, the UE may retransmit the BFRQ.

[0045] In step S106, the UE may transmit a message indicating that the beam reconfiguration is complete to the base station. The message may be transmitted, for example, via the PUCCH or the PUSCH.

[0046] A beam recovery success (BR success) may indicate, for example, that step S106 has been reached, whereas a beam recovery failure (BR failure) may indicate, for example, that a predetermined number of BFRQ transmissions have been made or that a beam-failure-recovery-timer has expired.

[0047] Rel. 15 supports the use of a random access procedure to perform a beam recovery procedure (e.g., BFRQ notification) in response to a beam failure detected in an SpCell (PCell / PSCell).

[0048] On the other hand, Rel. 16 supports a beam recovery procedure (e.g., BFRQ notification (step S104 in FIG. 1)) for a beam failure detected in an SCell, using at least one of a PUCCH (e.g., a scheduling request (SR)) transmission for BFR and a MAC CE (e.g., an UL-SCH) transmission for BFR. For example, the UE may transmit information about the beam failure using two MAC CE-based steps. The information about the beam failure may include information about the cell in which the beam failure was detected and information about a new candidate beam (or a new candidate RS index).

[0049] [Step 1] If BFR is detected, the UE may transmit a PUCCH-BFR (Scheduling Request (SR)) to the SpCell (e.g., PCell / PSCell). The PUCCH-BFR may also be referred to as PUCCH-SR, PUCCH-SR for BFR, or PUCCH for SR.

[0050] Next, the PCell / PSCell may transmit an UL grant (e.g., DCI) to the UE for the following step 2. When a beam failure is detected and a MAC CE (or UL-SCH) for transmitting information about a new candidate beam exists, step 1 (e.g., PUCCH transmission) may be omitted and step 2 (e.g., MAC CE transmission) may be performed.

[0051] [Step 2] The UE may transmit information about the cell where beam failure has been detected (failed) (e.g., cell index) and information about the new candidate beam to the base station (PCell / PSCell) via an uplink channel (e.g., PUSCH) using a MAC CE. After that, through the BFR procedure, the QCL of the PDCCH / PUCCH / PDSCH / PUSCH may be updated to the new beam after a predetermined period (e.g., 28 symbols) after receiving a response signal from the base station.

[0052] Note that the numbers of these steps are for illustrative purposes only, and multiple steps may be combined or the order may be reversed. Furthermore, whether to perform BFR may be configured in the UE using higher layer signaling.

[0053] Incidentally, in future wireless communication systems (e.g., Rel. 17 and later), beam management for UEs with multiple panels (multi-panels) or extension of beam management using multiple transmission / reception points (multi-Transmission / Reception Points (TRP)) is being considered.

[0054] In beam failure detection / recovery in Rel. 17 and later, it is assumed that a BFRQ framework based on the SCell BFR BFRQ of Rel. 16 will be supported. In this case, up to X PUCCH-SR resources (e.g., dedicated PUCCH-SR resources) may be configured in a cell group. X may be 1, 2, or greater than 1.

[0055] In the present disclosure, the cell group may be, for example, at least one of a master cell group (MCG), a secondary cell group (SCG), and a PUCCH cell group. The MCG and the SCG may be groups configured in dual connectivity (DC). The PUCCH cell group may be a group configured in PUCCH transmission.

[0056] In addition, in Rel. 17 and later, it is possible to perform beam failure detection / beam failure recovery for multiple TRPs / multiple UE panels in a cell (e.g., per-TRP BFR). For example, it is possible to support the transmission of a scheduling request (SR) for BFR per TRP / TRP unit.

[0057] In this case, the problem is how to control the configuration of scheduling requests (e.g., SR configuration, SR configuration). For example, the problem is how to control the configuration of SRs (e.g., SR index / SchedulingRequestID / SR ID) for a cell group (or cell / TRP), the configuration of PUCCH resources (e.g., PUCCH-SR resources), and the configuration of spatial relationships (e.g., spatial relations) corresponding to PUCCH resources. Alternatively, the problem is how to control the transmission of SRs (or PUCCH-SRs) for BFR based on the BFR type configured / applied to each cell included in the cell group (e.g., whether or not BFR per TRP is configured / applied).

[0058] The inventors focused on cases where beam failure recovery procedures (beam failure detection / beam failure recovery request / UE operation based on beam failure recovery) are applied in units of one or more TRPs / panels, and considered methods for setting SR / transmitting SR in such cases, and came up with the present embodiment.

[0059] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the drawings. Each aspect may be applied alone or in combination.

[0060] In the present disclosure, a UE may be a UE that uses multiple panels to transmit and receive data to and from a TRP, where each panel may correspond to a different TRP, one panel may correspond to multiple TRPs, or multiple panels may correspond to one TRP.

[0061] In this disclosure, a panel (or panel index) of a UE may correspond to a particular group. In this case, the UE may assume that beams / RSs of each group are measured on each panel of the UE. The UE may assume that it receives beams of multiple groups simultaneously (using different panels).

[0062] In the present disclosure, a TRP may be interchangeably referred to as a panel of TRPs (or base stations), an RS group, an antenna port group, a spatial relationship group, a QCL group, a TCI state, a TCI state group, a CORESET group, a CORESET pool, etc. Also, a TRP index may be interchangeably referred to as an RS group index, an antenna port group index, a QCL group index, a TCI state index, a TCI state group index, a CORESET group index, a CORESET pool index, etc.

[0063] In the present disclosure, a panel of a UE may be interchangeably read as an RS group, an antenna port group, a spatial relationship group, a QCL group, a TCI state group, a CORESET group, and the like.

[0064] In the present disclosure, a panel may be associated with a group index of an SSB / CSI-RS group. Also, in the present disclosure, a panel may be associated with a TRP. Also, in the present disclosure, multiple panels may be associated with a group index for group beam-based reporting. Also, in the present disclosure, a panel may be associated with a group index of an SSB / CSI-RS group for group beam-based reporting.

[0065] In the present disclosure, the serving cell / cell may be replaced with a PCell, a PSCell, an SpCell, or an SCell. In the following description, a case where two TRPs correspond to a serving cell is taken as an example, but three or more TRPs may correspond to a serving cell.

[0066] In the present disclosure, a BFD RS in which a beam failure has been detected, a failed BFD RS, a TRP in which a beam failure has been detected, a failed TRP, a UE panel in which a beam failure has been detected, and a failed UE panel may be read as interchangeable.

[0067] In the present disclosure, A / B may be read as at least one of A and B, or A and B. In the present disclosure, A / B / C may be read as at least one of A, B, and C.

[0068] (SR Setting Example) For SR setting, at least one of the following options 0, 1, and 2 may be supported.

[0069] <Option 0> SR in the cell group (e.g., SR index / SchedulingRequestID) ０ PUCCH resources (or PUCCH for SR) are configured, and Y ０ In the following description, X ０ = 1, Y ０ = 1 (see Figure 2A).

[0070] FIG. 2A shows a case where one PUCCH resource for SR (here, PUCCH resource for SR #1) is configured for an SR configured in a cell group (or SpCell), and one spatial relationship (here, spatial relationship #1) is configured for the PUCCH resource for SR. ０ , Y ０ The number is not limited to this.

[0071] Option 0 may be applied to the SR configuration method for SCell BFR in Rel. 16. Option 0 may be read as 0th SR / 0th SR configuration.

[0072] <Option 1> In the SR (e.g., SR index / SchedulingRequestID) for each cell group, specify the maximum X １PUCCH resources (e.g., dedicated PUCCH-SR resources) are configured, and Y PUCCH resources are allocated to the PUCCH resources. １ In the following description, X １ = 1, Y １ = 2 (see Figure 2B).

[0073] FIG. 2B shows a case where one PUCCH resource for SR (here, PUCCH resource for SR #1) is configured for an SR configured in a cell group (or SpCell), and two spatial relationships (here, spatial relationships #1 and #2) are configured for the PUCCH resource for SR. １ , Y １ The number of SRs is not limited to this. Option 1 may be read as first SR / first SR setting.

[0074] <Option 2> In the SR for each cell group (for example, SR index / SchedulingRequestID), specify the maximum X ２ Y PUCCH resources (e.g., dedicated PUCCH-SR resources) are configured, and Y PUCCH resources are assigned to each PUCCH resource. ２ In the following description, X ２ = 2 (or 2 or more), Y ２ = 1 (see Figure 2C).

[0075] FIG. 2C shows a case where two PUCCH resources for SR (here, PUCCH resources for SR #1 and #2) are configured for an SR configured in a cell group (or SpCell), and one spatial relationship (here, spatial relationship #1 and #2) is configured for each PUCCH resource for SR. FIG. 2C shows a case where different spatial relationships are configured for PUCCH resource for SR #1 and PUCCH resource for SR #2, but the same spatial relationship may also be configured. Note that X ２ , Y ２ The number of SRs is not limited to this. Option 2 may be interpreted as second SR / second SR setting.

[0076] The UE may receive at least one of the following information from the network (e.g., base station) using higher layer signaling / DCI: information on SRs in a cell group (e.g., SR index / SchedulingRequestID), information on PUCCH resources in a cell group (e.g., PUCCH-SR resources), and information on spatial relations (e.g., spatial relations) set for PUCCH resources.

[0077] The information about SR may be at least one of information indicating a configured SR index (or SchedulingRequestID) and information indicating the number of configured SRs. The information about PUCCH resources in a cell group may be at least one of information indicating PUCCH resources and information indicating the number of configured PUCCH resources. The information about spatial relations may be at least one of information indicating spatial relations and information indicating the number of configured spatial relations. In the present disclosure, spatial relations (e.g., spatial relation), beam, spatial filter, spatial domain filter, TCI state, and QCL may be interchangeable.

[0078] Furthermore, the UE may receive information regarding the BFR configuration for each BFR / BFR unit for each cell (e.g., a cell included in a cell group) from a network (e.g., a base station) using higher layer signaling / DCI. The information regarding the BFR configuration for each BFR / BFR unit may be information indicating whether the BFR is configured / applied for each BFR / BFR unit. Alternatively, the information regarding the BFR configuration for each BFR / BFR unit may be information indicating a BFR type (BFR for each BFR / BFR unit, or cell-specific BFR).

[0079] The UE may control the transmission of the SR or the PUCCH-SR based on at least one of the number of SRs (or the number of SR indices) configured for each cell group and the BFR type configured / applied to a specific cell included in the cell group (e.g., BFR per TRP / BFR per cell). In this case, the UE may control the transmission of the SR or the PUCCH-SR based on at least one of the number of PUCCH resources configured and the number of spatial relations configured (or corresponding) to the PUCCH resources.

[0080] (First Aspect) In the first aspect, a case where up to one SR (or SR index) can be configured for each cell group in BFR (or where only one is configured) will be described as an example. The BFR may include the SCell BFR in Rel. 16 / the BFR for each TRP in Rel. 17. In the following description, the PUCCH may be read as the PUCCH for SR, and the PUCCH resource may be read as the PUCCH-SR resource or the PUCCH resource for SR. Furthermore, the PUCCH for SR and the PUCCH resource for SR may be read as interchangeable. The BFR for each TRP may be read as the BFR for each TRP. The cell-specific BFR may be read as the BFR for each cell.

[0081] <Case A> Assume that in a cell group, per-TRP BFR is configured for at least a specific cell, or a specific cell that supports per-TRP BFR is configured. In this case, the per-TRP BFR (e.g., per-TRP BFR) procedure may be applied to the specific cell.

[0082] The specific cell may be an SpCell (e.g., PCell / PSCell). In this case, the cell group including the SpCell may include, for example, the SpCell and one or more SCells (see Figures 3A to 3C). In Case A, at least the SpCell supports BFR per TRP, and some or all of the other SCells may be configured to support BFR per TRP, or may not support BFR per TRP.

[0083] For example, as shown in Figure 3A, a BFR per TRP may be configured / applied to the SpCell, and a cell-specific BFR may be configured / applied to other SCells (here, SCell #1-#3). Alternatively, as shown in Figure 3B, a BFR per TRP may be configured / applied to the SpCell, a BFR per TRP may be configured / applied to some SCells (here, SCell #2), and a cell-specific BFR may be configured / applied to the remaining SCells (here, SCell #1, #3). Alternatively, as shown in Figure 3C, a BFR itself may not be configured to some SCells (here, SCell #1).

[0084] Furthermore, as the configuration of SR for BFR for the cell group, at least one of the above Option 1 and Option 2 may be applied. That is, two beam / spatial relationships may be configured for one PUCCH (or PUCCH resource) (see above Option 1 / FIG. 2B), or two beam / spatial relationships may be configured for two PUCCHs (or PUCCH resources) (see above Option 2 / FIG. 2C).

[0085] <<Beam Failure in SpCell>> If an SpCell includes multiple TRPs (e.g., TRP#0 and TRP#1) and a beam failure (e.g., TRP failure) is detected in some of the TRPs (e.g., TRP#0), an SR may be triggered.

[0086] Case A1: Assume that one PUCCH resource is configured for a cell group / SR, two spatial relationships are configured for the PUCCH resource (Option 1 above), and a beam failure is detected on TRP #0 (or an SR is triggered based on a beam failure on TRP #0). In this case, the UE may transmit an SR using the spatial relationship (here, spatial relationship #2) associated with another TRP (e.g., TRP #1) (see Case A1 / Option 1 in Fig. 4).

[0087] This allows the UE to transmit SR by utilizing spatial relationships where no beam obstruction is detected (or where the quality is high).

[0088] Alternatively, assume that two PUCCH resources are configured for a cell group / SR, and one spatial relationship is configured for each PUCCH resource (option 2 above), and a beam failure is detected at TRP#0 (or an SR is triggered based on a beam failure at TRP#0).

[0089] In this case, the UE may transmit the SR using the PUCCH for SR / PUCCH resource for SR (PUCCH resource for SR #2 in this case) associated with another TRP (e.g., TRP #1) (see Case A1 / Option 2 in Fig. 4 ). This allows the UE to transmit the SR using a PUCCH resource where no beam obstruction is detected (or where the quality is high).

[0090] The UE may also use the PUCCH for SR / PUCCH for SR resource associated with a TRP other than another TRP (e.g., TRP #1). For example, the UE may transmit an SR using the PUCCH for SR / PUCCH for SR resource (here, PUCCH resource #1 for SR) associated with the TRP (e.g., TRP #0) in which a beam failure is detected.

[0091] <<Beam Failure in SCell>> [No BFR Configuration Per TRP] If BFR operation per TRP is not configured for the SCell, a cell-specific BFR (e.g., cell-specific BFR) may be applied to the SCell. When a beam failure (e.g., TRP failure) is detected in the SCell, an SR may be triggered. The SR may be transmitted via the PUCCH (e.g., PUCCH-SR) of an SpCell included in the cell group to which the SCell belongs.

[0092] Case A2: Assume that one PUCCH resource is configured for a cell group / SR, two spatial relationships are configured for the PUCCH resource (Option 1 above), and a beam failure is detected in the SCell (or an SR is triggered based on a beam failure in the SCell). In this case, the UE may transmit the default beam / default spatial relationship for SR (or transmit the SR using the default beam / default spatial relationship) (see Case A2 / Option 1 in Figure 4).

[0093] Alternatively, assume that two PUCCH resources are configured for a cell group / SR, and one spatial relationship is configured for each PUCCH resource (Option 2 above), and if a beam failure is detected in the SCell (or if an SR is triggered based on a beam failure in the SCell), the UE may transmit the default PUCCH / default PUCCH resource for SR (or transmit the SR using the default PUCCH / default PUCCH resource) (see Case A2 / Option 2 in FIG. 4 ).

[0094] In this way, when a beam failure is detected in the SCell, the UE may control the transmission of the SR by using the default spatial relationship (option 1) or the default PUCCH resource (option 2). This allows the UE to appropriately control the transmission of the SR even when multiple spatial relationships / PUCCH resources for SR transmission are configured.

[0095] In option 1, the default beam / default spatial relationship for SR may be predefined in a specification, may be determined based on a predetermined rule (e.g., the index order of spatial relationships, etc.), or may be set from the base station to the UE by higher layer signaling, etc. For example, the default beam / default spatial relationship for SR may be the spatial relationship of SR associated with the first spatial relationship (e.g., 1st spatial relation), the lowest spatial relationship index (e.g., lowest spatial relation ID), or the lowest control resource set index (e.g., lowest CORESETPoolIndex) of SR.

[0096] In Option 2, the default PUCCH / default PUCCH resource for SR may be predefined in a specification, may be determined based on a predetermined rule (e.g., the index order of PUCCH resources, etc.), or may be configured from the base station to the UE by higher layer signaling, etc. For example, the default PUCCH / default PUCCH resource for SR may be the first PUCCH resource for SR (e.g., 1st PUCCH resource), the lowest PUCCH resource for SR (e.g., lowest PUCCH resource ID), or the PUCCH resource for SR associated with the lowest control resource set index (e.g., lowest CORESETPoolIndex).

[0097] [BFR configured per TRP] When BFR operation per TRP is configured for an SCell, a BFR procedure per TRP (e.g., per-TRP BFR) may be applied to the SCell.

[0098] If an SCell includes multiple TRPs (e.g., TRP #0 and TRP #1) and a beam failure (e.g., TRP failure) is detected in at least some of the TRPs (e.g., TRP #0), SR may be triggered.

[0099] Case A3: Assume that one PUCCH resource is configured for a cell group / SR, two spatial relationships are configured for the PUCCH resource (Option 1 above), and beam failure is detected in all TRPs (e.g., TRP #0 and TRP #1) (or SR is triggered based on beam failure in two TRPs). In this case, the UE may transmit the default beam / default spatial relationship for SR (or transmit SR using the default beam / default spatial relationship) (see Case A3 / Option 1 in Figure 4).

[0100] Alternatively, assume that two PUCCH resources are configured for a cell group / SR, each with one spatial relationship (Option 2 above), and beam failure is detected in all TRPs (e.g., TRP #0 and TRP #1) (or SR is triggered based on beam failure in two TRPs). In this case, the UE may transmit the default PUCCH / default PUCCH resource for SR (or transmit the SR using the default PUCCH / default PUCCH resource) (Case A3 / Option 2 in FIG. 4).

[0101] In this way, when the UE detects beam failures in multiple TRPs (e.g., all TRPs) of the SCell, the UE may control the transmission of the SR using the default spatial relationship (Option 1) or the default PUCCH resource (Option 2). This allows the UE to appropriately control the transmission of the SR even when multiple spatial relationships / PUCCH resources for SR transmission are configured.

[0102] Case A4: Alternatively, assume that one PUCCH resource is configured for a cell group / SR, two spatial relationships are configured for the PUCCH resource (Option 1 above), and a beam failure is detected in TRP #0 (or an SR is triggered based on a beam failure in TRP #0). In this case, the UE may transmit the default beam / default spatial relationship for the SR (or transmit the SR using the default beam / default spatial relationship) (see Case A4 / Option 1 in Figure 4). Alternatively, the UE may transmit the SR using a spatial relationship (Non-failed) associated with another TRP (e.g., TRP #1) (see Case A4 / Option 1 in Figure 4).

[0103] Alternatively, assume that two PUCCH resources are configured for a cell group / SR, and one spatial relationship is configured for each PUCCH resource (Option 2 above), and a beam failure is detected on TRP#0 (or an SR is triggered based on a beam failure on TRP#0). In this case, the UE may transmit the default PUCCH / default PUCCH resource for the SR (or transmit the SR using the default PUCCH / default PUCCH resource) (see Case A4 / Option 2 in Figure 4).

[0104] Alternatively, the UE may transmit the SR using the SR PUCCH / SR PUCCH resource (Non-failed) associated with another TRP (e.g., TRP #1) (see Case A4 / Option 2 in Figure 4).

[0105] The UE may also use the PUCCH for SR / PUCCH for SR resource associated with a TRP other than another TRP (e.g., TRP #1). For example, the UE may transmit the SR using the PUCCH for SR / PUCCH for SR resource associated with the TRP (e.g., TRP #0) in which the beam failure is detected.

[0106] In this embodiment, the SR PUCCH / SR PUCCH resource corresponding to the TRP to be used may be determined based on a predetermined condition. For example, the predetermined condition may be a cell (or a cell index) in which a beam failure is detected in the TRP.

[0107] For example, if a beam failure is detected in a TRP of a cell (e.g., SpCell) that transmits SR using the PUCCH resource for SR, the PUCCH resource for SR corresponding to the TRP in which the beam failure is not detected may be used. Also, if a beam failure is detected in a TRP of another cell (e.g., SCell) different from the cell (e.g., SpCell) that transmits SR using the PUCCH resource for SR, the PUCCH resource for SR corresponding to the TRP in which the beam failure is detected may be used. Alternatively, the reverse configuration may be applied.

[0108] <Case B> Assume that in a cell group, a specific cell (e.g., an SpCell) is not configured with per-TRP BFR operation (or BFR itself is not configured), and at least one other cell (e.g., an SCell) is configured with per-TRP BFR operation (see Figures 5A and 5B). In this case, the SCell applies per-TRP BFR (e.g., per-TRP BFR) procedures, and the SpCell applies cell-specific BFR (e.g., cell-specific BFR).

[0109] For example, as shown in Figure 5A, a cell-specific BFR may be set / applied to the SpCell, a BFR per TRP may be set / applied to some SCells (here, SCells #1 and #3), and a cell-specific BFR may be set / applied to the remaining SCells (here, SCell #2). Alternatively, as shown in Figure 5B, the BFR itself may not be set to the SpCell.

[0110] Furthermore, the above-mentioned Option 0 (see FIG. 2A ) may be applied as the configuration of the SR for BFR for the cell group (Alt. 1). Specifically, one PUCCH resource may be configured for the SR of the cell group, and one spatial relationship may be configured for the PUCCH resource (i.e., one beam / spatial relationship may be configured for one PUCCH / PUCCH resource).

[0111] Since BFR per TRP is not configured / supported in the SpCell, if a beam failure is detected in the SCell and an SR is triggered, the SR can be transmitted properly in the SpCell as long as the SpCell is not detected as a beam failure.

[0112] Alternatively, at least one of Option 1 and Option 2 may be applied as the configuration of SR for BFR for the cell group (Alt. 2). That is, two beam / spatial relationships may be configured for one PUCCH (or PUCCH resource) (Option 1), or two beam / spatial relationships may be configured for two PUCCHs (or PUCCH resources) (Option 2).

[0113] <<Beam Failure in SpCell>> If per-TRP BFR operation is not configured for the SpCell, a cell-specific BFR (e.g., cell-specific BFR) may be applied in the SpCell. If a beam failure (e.g., TRP failure) is detected in the SpCell, SR may be triggered.

[0114] Assume that one PUCCH resource is configured for a cell group / SR, two spatial relationships are configured for the PUCCH resource (Option 1 above), and a beam failure is detected in the SpCell (or an SR is triggered based on a beam failure in the SpCell). In this case, the UE may transmit a default beam / default spatial relationship for the SR (or transmit an SR using the default beam / default spatial relationship).

[0115] Alternatively, assume that two PUCCH resources are configured for a cell group / SR, and one spatial relationship is configured for each PUCCH resource (Option 2 above), and a beam failure is detected in the SpCell (or an SR is triggered based on a beam failure in the SpCell). In this case, the UE may transmit the default PUCCH / default PUCCH resource for the SR (or transmit the SR using the default PUCCH / default PUCCH resource).

[0116] In this way, when a UE detects a beam failure in an SpCell in which per-TRP BFR operation is not configured, the UE may control the transmission of the SR using the default spatial relationship (Option 1) or the default PUCCH resource (Option 2). This allows the UE to appropriately control the transmission of the SR even when multiple spatial relationships / PUCCH resources for SR transmission are configured.

[0117] Alternatively, if BFR operation per TRP is not configured in the SpCell, when a beam failure is detected in the SpCell, a BFR procedure using PRACH (e.g., the BFR procedure of Rel. 15) may be applied.

[0118] <<Beam Failure in SCell>> [No BFR Configuration Per TRP] If BFR operation per TRP is not configured for the SCell, a cell-specific BFR (e.g., cell-specific BFR) may be applied to the SCell. When a beam failure (e.g., TRP failure) is detected in the SCell, an SR may be triggered. The SR may be transmitted via the PUCCH (e.g., PUCCH-SR) of an SpCell included in the cell group to which the SCell belongs.

[0119] Case B1: Assume that one PUCCH resource is configured for a cell group / SR, two spatial relationships are configured for the PUCCH resource (Option 1 above), and a beam failure is detected in the SCell (or an SR is triggered based on a beam failure in the SCell). In this case, the UE may transmit the default beam / default spatial relationship for SR (or transmit the SR using the default beam / default spatial relationship) (see Case B1 / Option 1 in Figure 6).

[0120] Alternatively, assume that two PUCCH resources are configured for a cell group / SR, and one spatial relationship is configured for each PUCCH resource (Option 2 above), and if a beam failure is detected in the SCell (or if an SR is triggered based on a beam failure in the SCell), the UE may transmit the default PUCCH / default PUCCH resource for SR (or transmit the SR using the default PUCCH / default PUCCH resource) (see Case B1 / Option 2 in FIG. 6 ).

[0121] In this way, when a beam failure is detected in the SCell, the UE may control the transmission of the SR by using the default spatial relationship (option 1) or the default PUCCH resource (option 2). This allows the UE to appropriately control the transmission of the SR even when multiple spatial relationships / PUCCH resources for SR transmission are configured.

[0122] In option 1, the default beam / default spatial relationship for SR may be predefined in a specification, may be determined based on a predetermined rule (e.g., the index order of spatial relationships, etc.), or may be set from the base station to the UE by higher layer signaling, etc. For example, the default beam / default spatial relationship for SR may be the spatial relationship of SR associated with the first spatial relationship (e.g., 1st spatial relation), the lowest spatial relationship index (e.g., lowest spatial relation ID), or the lowest control resource set index (e.g., lowest CORESETPoolIndex) of SR.

[0123] In Option 2, the default PUCCH / default PUCCH resource for SR may be predefined in a specification, may be determined based on a predetermined rule (e.g., the index order of PUCCH resources, etc.), or may be configured from the base station to the UE by higher layer signaling, etc. For example, the default PUCCH / default PUCCH resource for SR may be the first PUCCH resource for SR (e.g., 1st PUCCH resource), the lowest PUCCH resource for SR (e.g., lowest PUCCH resource ID), or the PUCCH resource for SR associated with the lowest control resource set index (e.g., lowest CORESETPoolIndex).

[0124] [BFR configured per TRP] When BFR operation per TRP is configured for an SCell, a BFR procedure per TRP (e.g., per-TRP BFR) may be applied to the SCell.

[0125] If an SCell includes multiple TRPs (e.g., TRP #0 and TRP #1) and a beam failure (e.g., TRP failure) is detected in at least some of the TRPs (e.g., TRP #0), SR may be triggered.

[0126] Case B2: Assume that one PUCCH resource is configured for a cell group / SR, two spatial relationships are configured for the PUCCH resource (Option 1 above), and beam failure is detected in all TRPs (e.g., TRP #0 and TRP #1) (or SR is triggered based on beam failure in two TRPs). In this case, the UE may transmit the default beam / default spatial relationship for SR (or transmit SR using the default beam / default spatial relationship) (see Case B2 / Option 1 in Figure 6).

[0127] Alternatively, assume that two PUCCH resources are configured for a cell group / SR, each with one spatial relationship (Option 2 above), and beam failure is detected in all TRPs (e.g., TRP #0 and TRP #1) (or SR is triggered based on beam failure in two TRPs). In this case, the UE may transmit the default PUCCH / default PUCCH resource for SR (or transmit SR using the default PUCCH / default PUCCH resource) (see Case B2 / Option 2 in Figure 6).

[0128] In this way, when the UE detects beam failures in multiple TRPs (e.g., all TRPs) of the SCell, the UE may control the transmission of the SR using the default spatial relationship (Option 1) or the default PUCCH resource (Option 2). This allows the UE to appropriately control the transmission of the SR even when multiple spatial relationships / PUCCH resources for SR transmission are configured.

[0129] Case B3: Alternatively, assume that one PUCCH resource is configured for a cell group / SR, two spatial relationships are configured for the PUCCH resource (Option 1 above), and a beam failure is detected in TRP #0 (or an SR is triggered based on a beam failure in TRP #0). In this case, the UE may transmit the default beam / default spatial relationship for the SR (or transmit the SR using the default beam / default spatial relationship) (see Case B3 / Option 1 in Figure 6). Alternatively, the UE may transmit the SR using a spatial relationship (Non-failed) associated with another TRP (e.g., TRP #1) (see Case B3 / Option 1 in Figure 6).

[0130] Alternatively, assume that two PUCCH resources are configured for a cell group / SR, each with one spatial relationship (Option 2 above), and a beam failure is detected in TRP#0 (or an SR is triggered based on a beam failure in TRP#0). In this case, the UE may transmit the SR using the default PUCCH / default PUCCH resource (or transmit the SR using the default PUCCH / default PUCCH resource) (see Case B3 / Option 2 in FIG. 6). Alternatively, the UE may transmit the SR using the SR / PUCCH resource (non-failed) associated with another TRP (e.g., TRP#1) (see Case B3 / Option 2 in FIG. 6).

[0131] (Second Aspect) In the second aspect, a case where multiple SRs or up to N SRs (for example, N = 2) can be set for each cell group in BFR will be described. In the following description, N = 2 is used as an example, but the number of SRs that can be set for a cell group is not limited to 2.

[0132] For example, two SR configurations may be set taking into consideration different conditions for each cell group. As the two SRs (or SR configurations corresponding to two SRs), an SR corresponding to the above option 0 (e.g., a first SR) and an SR corresponding to the above option 1 / 2 (e.g., a second SR) may be set (see FIGS. 7A and 7B).

[0133] 7A shows a case where a first SR configuration corresponding to option 0 and a second SR configuration corresponding to option 1 are configured for a certain cell group. FIG. 7B shows a case where a first SR configuration corresponding to option 0 and a second SR configuration corresponding to option 2 are configured for a certain cell group.

[0134] For example, one SR (e.g., a first SR) may be configured for SCell BFR in Rel. 16, and one SR (e.g., a second SR) may be configured for per-TRP BFR in Rel. 17.

[0135] The setting conditions of the two SRs may be in accordance with at least one of the following Alt. 2-1 to Alt. 2-3.

[0136] <Alt. 2-1> The configuration of two SRs may be controlled based on whether or not a BFR per TRP is configured for at least one serving cell included in a cell group (for example, whether or not it is configured).

[0137] When BFR per TRP is configured in at least one serving cell (e.g., SpCell or SCell) in a cell group, two SRs may be configured (or two SR configurations may be supported). The first SR (or SR configuration) may be the SR corresponding to the Option 0, and the second SR (or SR configuration) may be the SR corresponding to the Option 1 / 2.

[0138] The UE may be controlled to transmit a first SR (e.g., an SR corresponding to Option 0) under a first condition. The first condition may be when the SR is triggered due to beam failure of two TRPs of an SCell (where per-TRP BFR is configured) or when the SR is triggered due to beam failure of an SCell (where cell-specific BFR is applied).

[0139] The UE may be controlled to transmit a second SR (e.g., an SR corresponding to option 1 / 2) under a second condition. The second condition may be when the SR is triggered by a beam failure of one TRP of the SpCell / SCell (the SpCell / SCell in which per-TRP BFR is configured). This allows the UE to control the SR transmission taking into account the TRP (or spatial relationship / PUCCH resource) in which the beam failure is detected.

[0140] <Alt. 2-2> The configuration of the first SR and the configuration of the second SR may be separately controlled based on different conditions. The different conditions may be a cell type (SpCell / SCell) or a configured / applied BFR type (cell-specific BFR / per-TRP BFR). For example, the configuration of one SR may be controlled based on whether a cell-specific BFR is applied to at least one SCell (e.g., whether configured), and the configuration of another SR may be controlled based on whether a per-TRP BFR is configured to at least one serving cell (SpCell / SCell) (e.g., whether configured).

[0141] If at least one SCell in a cell group does not have a per-TRP BFR configured (or a cell-specific BFR is applied), one SR (e.g., a first SR corresponding to option 0) may be configured. Also, if at least one serving cell (e.g., an SpCell or an SCell) in a cell group has a per-TRP BFR configured, another SR (e.g., a second SR corresponding to option 1 / 2) may be configured.

[0142] If SR is triggered due to beam failure of an SCell (an SCell to which cell-specific BFR is applied), the UE may be controlled to transmit a first SR (an SR corresponding to option 0).

[0143] On the other hand, if SR is triggered by beam failure detection of an SpCell / SCell (where BFR per TRP is configured), the UE may control to transmit a second SR (SR corresponding to Option 1 / 2), thereby controlling SR transmission taking into account the TRP (or spatial relationship / PUCCH resource) where beam failure is detected.

[0144] <Alt. 2-3> The configuration of the first SR and the configuration of the second SR may be separately controlled based on different conditions. The different conditions may be the cell type (SpCell / SCell) or the configured / applied BFR type (cell-specific BFR / per-TRP BFR). For example, the configuration of one SR may be controlled based on whether or not a BFR (e.g., cell-specific BFR / per-TRP BFR) is applied to at least one SCell (e.g., whether or not it is configured), and the configuration of the other SR may be controlled based on whether or not a per-TRP BFR is configured to the SpCell (e.g., whether or not it is configured).

[0145] One SR (e.g., a first SR corresponding to option 0) may be configured if BFR (e.g., per-TRP BFR or cell-specific / per-cell BFR) is configured for at least one SCell in a cell group. Also, another SR (e.g., a second SR corresponding to option 1 / 2) may be configured only if per-TRP BFR is configured for an SpCell.

[0146] Only when a beam failure in one TRP (e.g., TRP#0) of the SpCell is detected, the UE may control to transmit a second SR (e.g., an SR corresponding to Option 1 / 2). When transmitting the second SR, the UE may use the spatial relationship associated with another TRP (e.g., TRP#1) (Option 1) or the PUCCH for SR / PUCCH for SR resource associated with another TRP (e.g., TRP#1) (Option 2).

[0147] Otherwise (e.g., other than when a beam failure in one TRP of the SpCell is detected), the UE may be controlled to transmit a first SR (e.g., an SR corresponding to option 0).

[0148] (Third Aspect) In the third aspect, an example of association between a TRP index and a PUCCH resource index for SR will be described.

[0149] The third aspect may be applied to the first aspect, the second aspect, or the fourth aspect. The third aspect may also be applied when at least one of the following rules 1 to 3 is used as a selection rule for the PUCCH resource for SR.

[0150] Rule 1: A PUCCH resource for SR associated with another TRP (e.g., a non-failed BFD-RS set) is selected. Rule 2: A PUCCH resource for SR associated with a TRP in which a beam failure is detected (e.g., a failed BFD-RS set) is selected. Rule 3: A PUCCH resource for SR is selected by the UE implementation (UE implementation).

[0151] The UE may be configured with an association between the PUCCH resource index for SR and the TRP index for each BWP / cell. For example, the base station may configure / notify the UE of the association between the PUCCH resource index for SR and the TRP index for each BWP / cell using a predetermined higher layer parameter (e.g., BFR-Config) via RRC / MAC CE (see FIG. 8).

[0152] 8 shows a case where TRP #1 corresponds to PUCCH resource #1 for SR, and TRP #2 corresponds to PUCCH resource #2 for SR. The number of TRPs and the number of PUCCH resources for SR are not limited to this.

[0153] The TRP index may not be specified (or defined / introduced). In this case, the TRP index may be indicated by at least one of a CORESET pool index (e.g., {0, 1}), an index of an enhanced TCI state for a PDSCH MAC CE (e.g., {first TCI state, second TCI state}), and an index of a BFD / NBI RS set (e.g., {first BFD / NBI RS set, second BFD / NBI RS set}).

[0154] Rule 1 or Rule 2 may indicate that there is an association between the PUCCH resource for SR and the TRP. Also, which PUCCH resource for SR is to be transmitted may be selected based on a predetermined condition (e.g., association).

[0155] (Fourth Aspect) In the fourth aspect, an example of association between a TRP index and an SR configuration / ID, or an example of association between a TRP index and a spatial relationship of a PUCCH for SR will be described.

[0156] A configuration in which two SR PUCCH resources correspond to one SR setting / ID for each TRP, or a configuration in which two SR settings / IDs correspond to each TRP may be supported.

[0157] In the current specifications (for example, Rel. 16 and earlier), it is defined that one SR resource (or one PUCCH resource for SR) is associated with one SR configuration / ID. Therefore, when two or more PUCCH resources for SR correspond to one SR configuration / ID, the UE operation in the fourth aspect (for example, the trigger condition for the SR configuration / ID (or the PUCCH for SR)) may be applied.

[0158] When multiple (e.g., two) SR PUCCH resources (or one or more SR PUCCH resources having multiple spatial relationships) correspond to one SR setting / ID, the UE / base station may control the UE operation / base station operation based on at least one of the following options 4-1 to 4-2.

[0159] <Option 4-1> Assume that two SR IDs (e.g., SR setting / ID) are configured for BFR. In this case, the association between the SR setting / ID and the TRP may be supported. The association between the SR setting / ID and the TRP may be configured from the base station to the UE using RRC / MAC CE, etc. (see FIG. 9A).

[0160] 9A shows a case where TRP#1 is associated with SR ID#1, and TRP#2 is associated with SR ID#2. The number of TRPs and the number of SR IDs are not limited to this.

[0161] Furthermore, SR ID #1 may correspond to SR PUCCH resource #1, and SR ID #2 may correspond to SR PUCCH resource #2. The association between the SR ID and the SR PUCCH resource may be configured / instructed to the UE by the base station using RRC / MAC CE / DCI.

[0162] Separate (eg, different) spatial relationships may be set for different SR PUCCH resources.

[0163] The UE may determine / decide which PUCCH resource for SR to transmit for different cases (or for each case) based on the association.

[0164] For example, if a beam failure is detected in a certain TRP, a PUCCH for SR corresponding to (or related to) the SR setting / ID associated with the TRP in which the beam failure was detected (e.g., a failed TRP) may be transmitted.

[0165] Alternatively, when a beam failure is detected in a certain TRP, a PUCCH for SR corresponding to an SR setting / ID associated with a TRP different from the TRP in which the beam failure was detected (for example, a TRP in which no beam failure was detected (non-failed TRP)) may be transmitted.

[0166] <Option 4-2> Assume that one SR ID (e.g., SR configuration / ID) is configured for BFR, and two spatial relations correspond to one PUCCH resource for SR. In this case, the configuration of an association between the spatial relation and the TRP may be supported. The association between the spatial relation and the TRP may be configured from the base station to the UE using RRC / MAC CE, etc. (see FIG. 9B ).

[0167] 9B shows a case where TRP #1 is associated with spatial relationship #1, and TRP #2 is associated with spatial relationship #2. The number of TRPs and the number of spatial relationships are not limited to this.

[0168] The UE may determine which spatial relationship to select / apply for transmitting the PUCCH for SR for different cases (or for each case) based on the association.

[0169] For example, if a beam failure is detected in a certain TRP, the SR PUCCH may be transmitted by applying the spatial relationship associated with the TRP in which the beam failure was detected (e.g., the failed TRP).

[0170] Alternatively, if a beam failure is detected in a certain TRP, the SR PUCCH may be transmitted by applying a spatial relationship associated with a TRP different from the TRP in which the beam failure was detected (e.g., a TRP in which no beam failure was detected (non-failed TRP)).

[0171] The different case may be at least one of the following cases 4-1 to 4-4.

[0172] Case 4-1 corresponds to a case where a beam failure / TRP failure occurs in a TRP (e.g., one TRP) of at least one SpCell / SCell when a TRP-specific BFR (e.g., a TRP-specific BFR) is configured.

[0173] Case 4-2 corresponds to a case where beam failure / SCell failure occurs in at least one SCell when a TRP-specific BFR (e.g., a TRP-specific BFR) is configured.

[0174] Case 4-3 corresponds to a case where a TRP-specific BFR (e.g., a TRP-specific BFR) is configured in a cell, and beam failure or different TRP failure occurs in one or more (or more than one) of the cells (e.g., SpCell / SCell) at different TRPs.

[0175] Case 4-4 corresponds to a case where a beam failure (or TRP failure) occurs in the TRP of a cell in one or more (or more than one) SpCell / SCell when a TRP-specific BFR (e.g., a TRP-specific BFR) is configured, and a beam failure occurs in another SCell when a cell-specific BFR is configured.

[0176] In this way, by establishing an association between a TRP index and an SR configuration / ID, or an association between a TRP index and a spatial relationship of a PUCCH for SR, and controlling SR (or PUCCH for SR) transmission based on the association, it is possible to appropriately control UE operation in BFR.

[0177] (UE Capability Information) In the above-described first to fourth aspects, the following UE capabilities may be configured. Note that the following UE capabilities may be interpreted as parameters (e.g., higher layer parameters) configured in the UE from a network (e.g., a base station).

[0178] UE capability information regarding whether SR is supported for BFR in which two PUCCH resources are configured (e.g., BFR per TRP) may be defined.

[0179] UE capability information regarding whether or not to support default PUCCH resources for SR for BFR may be defined.

[0180] UE capability information regarding whether SR is supported for BFR (e.g., BFR per TRP) in which one PUCCH resource having two spatial relationships is configured may be defined.

[0181] UE capability information regarding whether or not to support the default spatial relationship for SR for BFR may be defined.

[0182] UE capability information regarding whether or not the SpCell with BFR per TRP is supported may be defined.

[0183] UE capability information regarding whether or not the SCell supports BFR per TRP may be defined.

[0184] For each cell group, UE capability information regarding the maximum number of SCells / serving cells for which BFR per TRP can be configured may be defined.

[0185] The first to fourth aspects may be applied to a UE that supports / reports at least one of the above-mentioned UE capabilities, or may be applied to a UE configured by the network.

[0186] (Wireless Communication System) The configuration of a wireless communication system according to an embodiment of the present disclosure will be described below. In this wireless communication system, communication is performed using any one of the wireless communication methods according to the above embodiments of the present disclosure or a combination thereof.

[0187] 10 is a diagram illustrating an example of a schematic configuration of a wireless communication system according to an embodiment. The wireless communication system 1 may be a system that realizes communication using Long Term Evolution (LTE) or 5th generation mobile communication system New Radio (5G NR) specified by the Third Generation Partnership Project (3GPP).

[0188] The wireless communication system 1 may also support dual connectivity between multiple Radio Access Technologies (RATs) (Multi-RAT Dual Connectivity (MR-DC)). MR-DC may include dual connectivity between LTE (Evolved Universal Terrestrial Radio Access (E-UTRA)) and NR (E-UTRA-NR Dual Connectivity (EN-DC)), dual connectivity between NR and LTE (NR-E-UTRA Dual Connectivity (NE-DC)), etc.

[0189] In EN-DC, the LTE (E-UTRA) base station (eNB) is the master node (Master Node (MN)), and the NR base station (gNB) is the secondary node (Secondary Node (SN)). In NE-DC, the NR base station (gNB) is the MN, and the LTE (E-UTRA) base station (eNB) is the SN.

[0190] The wireless communication system 1 may support dual connectivity between multiple base stations within the same RAT (for example, dual connectivity in which both the MN and SN are NR base stations (gNBs) (NR-NR Dual Connectivity (NN-DC))).

[0191] The wireless communication system 1 may include a base station 11 that forms a macrocell C1 with a relatively wide coverage, and base stations 12 (12a-12c) that are located within the macrocell C1 and form small cells C2 that are smaller than the macrocell C1. A user terminal 20 may be located within at least one of the cells. The locations and numbers of the cells and user terminals 20 are not limited to the embodiment shown in the figure. Hereinafter, when there is no need to distinguish between the base stations 11 and 12, they will be collectively referred to as base station 10.

[0192] The user terminal 20 may be connected to at least one of the multiple base stations 10. The user terminal 20 may utilize at least one of carrier aggregation (CA) using multiple component carriers (CCs) and dual connectivity (DC).

[0193] Each CC may be included in at least one of a first frequency band (Frequency Range 1 (FR1)) and a second frequency band (Frequency Range 2 (FR2)). The macro cell C1 may be included in FR1, and the small cell C2 may be included in FR2. For example, FR1 may be a frequency band of 6 GHz or less (sub-6 GHz), and FR2 may be a frequency band higher than 24 GHz (above-24 GHz). Note that the frequency bands and definitions of FR1 and FR2 are not limited to these, and for example, FR1 may correspond to a higher frequency band than FR2.

[0194] Furthermore, the user terminal 20 may perform communication using at least one of time division duplex (TDD) and frequency division duplex (FDD) in each CC.

[0195] The multiple base stations 10 may be connected by wire (e.g., optical fiber compliant with the Common Public Radio Interface (CPRI), an X2 interface, etc.) or wirelessly (e.g., NR communication). For example, when NR communication is used as a backhaul between the base stations 11 and 12, the base station 11 corresponding to the upper station may be called an Integrated Access Backhaul (IAB) donor, and the base station 12 corresponding to the relay station (relay) may be called an IAB node.

[0196] The base station 10 may be connected to the core network 30 directly or via another base station 10. The core network 30 may include, for example, at least one of an Evolved Packet Core (EPC), a 5G Core Network (5GCN), a Next Generation Core (NGC), and the like.

[0197] The user terminal 20 may be a terminal that supports at least one of communication methods such as LTE, LTE-A, and 5G.

[0198] An Orthogonal Frequency Division Multiplexing (OFDM)-based radio access scheme may be used in the wireless communication system 1. For example, Cyclic Prefix OFDM (CP-OFDM), Discrete Fourier Transform Spread OFDM (DFT-s-OFDM), Orthogonal Frequency Division Multiple Access (OFDMA), Single Carrier Frequency Division Multiple Access (SC-FDMA), or the like may be used in at least one of the downlink (DL) and uplink (UL).

[0199] The radio access scheme may also be called a waveform. Note that in the wireless communication system 1, other radio access schemes (e.g., other single-carrier transmission schemes, other multi-carrier transmission schemes) may be used as the UL and DL radio access schemes.

[0200] In the wireless communication system 1, a downlink shared channel (Physical Downlink Shared Channel (PDSCH)) shared by each user terminal 20, a broadcast channel (Physical Broadcast Channel (PBCH)), a downlink control channel (Physical Downlink Control Channel (PDCCH)), etc. may be used as the downlink channel.

[0201] Furthermore, in the wireless communication system 1, an uplink shared channel (Physical Uplink Shared Channel (PUSCH)) shared by each user terminal 20, an uplink control channel (Physical Uplink Control Channel (PUCCH)), a random access channel (Physical Random Access Channel (PRACH)), or the like may be used as an uplink channel.

[0202] The PDSCH transmits user data, higher layer control information, a System Information Block (SIB), etc. The PUSCH may transmit user data, higher layer control information, etc. Furthermore, the PBCH may transmit a Master Information Block (MIB).

[0203] Lower layer control information may be transmitted by the PDCCH. The lower layer control information may include, for example, Downlink Control Information (DCI) including scheduling information for at least one of the PDSCH and the PUSCH.

[0204] Note that the DCI for scheduling the PDSCH may be referred to as a DL assignment, a DL DCI, etc., and the DCI for scheduling the PUSCH may be referred to as a UL grant, a UL DCI, etc. Note that the PDSCH may be replaced with DL data, and the PUSCH may be replaced with UL data.

[0205] A control resource set (CORESET) and a search space may be used to detect the PDCCH. The CORESET corresponds to resources for searching for DCI. The search space corresponds to a search region and a search method for PDCCH candidates. One CORESET may be associated with one or more search spaces. The UE may monitor the CORESET associated with a certain search space based on the search space configuration.

[0206] One search space may correspond to PDCCH candidates corresponding to one or more aggregation levels. One or more search spaces may be referred to as a search space set. Note that the terms "search space," "search space set," "search space configuration," "search space set configuration," "CORESET," "CORESET configuration," and the like in the present disclosure may be read interchangeably.

[0207] The PUCCH may transmit uplink control information (UCI) including at least one of channel state information (CSI), delivery confirmation information (which may be called, for example, Hybrid Automatic Repeat reQuest ACKnowledgement (HARQ-ACK), ACK / NACK, etc.), and scheduling request (SR). The PRACH may transmit a random access preamble for establishing a connection with a cell.

[0208] In the present disclosure, downlink, uplink, etc. may be expressed without adding "link." Also, various channels may be expressed without adding "Physical" to the beginning.

[0209] In the wireless communication system 1, a synchronization signal (SS), a downlink reference signal (DL-RS), etc. may be transmitted. In the wireless communication system 1, as the DL-RS, a cell-specific reference signal (CRS), a channel state information reference signal (CSI-RS), a demodulation reference signal (DMRS), a positioning reference signal (PRS), a phase tracking reference signal (PTRS), etc. may be transmitted.

[0210] The synchronization signal may be, for example, at least one of a Primary Synchronization Signal (PSS) and a Secondary Synchronization Signal (SSS). A signal block including an SS (PSS, SSS) and a PBCH (and a DMRS for the PBCH) may be referred to as an SS / PBCH block, an SS Block (SSB), or the like. Note that the SS, SSB, and the like may also be referred to as a reference signal.

[0211] Furthermore, in the wireless communication system 1, a sounding reference signal (SRS), a demodulation reference signal (DMRS), or the like may be transmitted as an uplink reference signal (UL-RS). Note that the DMRS may also be called a user equipment-specific reference signal (UE-specific reference signal).

[0212] 11 is a diagram showing an example of the configuration of a base station according to an embodiment. The base station 10 includes a control unit 110, a transceiver unit 120, a transceiver antenna 130, and a transmission line interface 140. Note that the base station may include one or more of each of the control unit 110, the transceiver unit 120, the transceiver antenna 130, and the transmission line interface 140.

[0213] In this example, the functional blocks of the characteristic parts of the present embodiment are mainly shown, and it may be assumed that the base station 10 also has other functional blocks necessary for wireless communication. Some of the processing of each unit described below may be omitted.

[0214] The control unit 110 performs overall control of the base station 10. The control unit 110 can be configured from a controller, a control circuit, and the like that are explained based on common understanding in the technical field to which the present disclosure relates.

[0215] The control unit 110 may control signal generation, scheduling (e.g., resource allocation, mapping), etc. The control unit 110 may control transmission and reception using the transceiver unit 120, the transceiver antenna 130, and the transmission path interface 140, measurement, etc. The control unit 110 may generate data, control information, sequences, etc. to be transmitted as signals, and transfer them to the transceiver unit 120. The control unit 110 may perform call processing (setting up, releasing, etc.) of communication channels, status management of the base station 10, management of radio resources, etc.

[0216] The transceiver unit 120 may include a baseband unit 121, a radio frequency (RF) unit 122, and a measurement unit 123. The baseband unit 121 may include a transmission processing unit 1211 and a reception processing unit 1212. The transceiver unit 120 may be configured with a transmitter / receiver, an RF circuit, a baseband circuit, a filter, a phase shifter, a measurement circuit, a transceiver circuit, etc., which are described based on common understanding in the technical field related to the present disclosure.

[0217] The transmitting / receiving unit 120 may be configured as an integrated transmitting / receiving unit, or may be configured from a transmitting unit and a receiving unit. The transmitting unit may be configured from a transmission processing unit 1211 and an RF unit 122. The receiving unit may be configured from a reception processing unit 1212, the RF unit 122, and a measurement unit 123.

[0218] The transmitting and receiving antenna 130 can be configured from an antenna described based on common understanding in the technical field to which the present disclosure relates, such as an array antenna.

[0219] The transceiver 120 may transmit the above-mentioned downlink channel, synchronization signal, downlink reference signal, etc. The transceiver 120 may receive the above-mentioned uplink channel, uplink reference signal, etc.

[0220] The transceiver 120 may form at least one of the transmit beam and the receive beam using digital beamforming (e.g., precoding), analog beamforming (e.g., phase rotation), or the like.

[0221] The transmitter / receiver unit 120 (transmission processing unit 1211) may perform Packet Data Convergence Protocol (PDCP) layer processing, Radio Link Control (RLC) layer processing (e.g., RLC retransmission control), Medium Access Control (MAC) layer processing (e.g., HARQ retransmission control), etc. on data, control information, etc. obtained from the control unit 110, and generate a bit string to be transmitted.

[0222] The transmitter / receiver unit 120 (transmission processing unit 1211) may perform transmission processing such as channel coding (which may include error correction coding), modulation, mapping, filtering, Discrete Fourier Transform (DFT) processing (if necessary), Inverse Fast Fourier Transform (IFFT) processing, precoding, and digital-to-analog conversion on the bit string to be transmitted, and output a baseband signal.

[0223] The transceiver unit 120 (RF unit 122) may perform modulation, filtering, amplification, etc. on the baseband signal to a radio frequency band, and transmit the radio frequency band signal via the transceiver antenna 130.

[0224] On the other hand, the transmitting / receiving unit 120 (RF unit 122) may perform amplification, filtering, demodulation to a baseband signal, etc. on the radio frequency band signal received by the transmitting / receiving antenna 130.

[0225] The transceiver 120 (reception processing unit 1212) may apply reception processing such as analog-to-digital conversion, Fast Fourier Transform (FFT) processing, Inverse Discrete Fourier Transform (IDFT) processing (if necessary), filtering, demapping, demodulation, decoding (which may include error correction decoding), MAC layer processing, RLC layer processing, and PDCP layer processing to the acquired baseband signal, thereby acquiring user data, etc.

[0226] The transceiver 120 (measurement unit 123) may perform measurements on the received signal. For example, the measurement unit 123 may perform Radio Resource Management (RRM) measurements, Channel State Information (CSI) measurements, etc. based on the received signal. The measurement unit 123 may measure received power (e.g., Reference Signal Received Power (RSRP)), received quality (e.g., Reference Signal Received Quality (RSRQ), Signal to Interference plus Noise Ratio (SINR), Signal to Noise Ratio (SNR)), signal strength (e.g., Received Signal Strength Indicator (RSSI)), propagation path information (e.g., CSI), etc. The measurement results may be output to the control unit 110.

[0227] The transmission path interface 140 may transmit and receive signals (backhaul signaling) between devices included in the core network 30, other base stations 10, etc., and may acquire and transmit user data (user plane data), control plane data, etc. for the user terminal 20.

[0228] The transmitting section and receiving section of the base station 10 in the present disclosure may be configured by at least one of the transmitting / receiving section 120, the transmitting / receiving antenna 130, and the transmission path interface 140.

[0229] The transceiver unit 120 may transmit information regarding the configuration of beam failure detection for each transceiver point (TRP) and information regarding the configuration of uplink control channel resources corresponding to the scheduling request.

[0230] When a terminal detects a beam failure in a first TRP, the control unit 110 may control the reception of a scheduling request transmitted from the terminal using either an uplink control channel resource corresponding to the first TRP or an uplink control channel resource corresponding to a second TRP different from the first TRP.

[0231] (User Terminal) Fig. 12 is a diagram showing an example of the configuration of a user terminal according to one embodiment. The user terminal 20 includes a control unit 210, a transceiver unit 220, and a transceiver antenna 230. Note that the user terminal 20 may include one or more of each of the control unit 210, the transceiver unit 220, and the transceiver antenna 230.

[0232] In this example, the functional blocks of the characteristic parts of the present embodiment are mainly shown, and it may be assumed that the user terminal 20 also has other functional blocks necessary for wireless communication. Some of the processing of each unit described below may be omitted.

[0233] The control unit 210 performs overall control of the user terminal 20. The control unit 210 can be configured from a controller, a control circuit, etc., which are described based on common understanding in the technical field to which the present disclosure relates.

[0234] The control unit 210 may control signal generation, mapping, etc. The control unit 210 may control transmission and reception, measurement, etc. using the transceiver unit 220 and the transceiver antenna 230. The control unit 210 may generate data, control information, sequences, etc. to be transmitted as signals and transfer them to the transceiver unit 220.

[0235] The transceiver unit 220 may include a baseband unit 221, an RF unit 222, and a measurement unit 223. The baseband unit 221 may include a transmission processing unit 2211 and a reception processing unit 2212. The transceiver unit 220 may be configured with a transmitter / receiver, an RF circuit, a baseband circuit, a filter, a phase shifter, a measurement circuit, a transceiver circuit, etc., which are described based on common understanding in the technical field related to the present disclosure.

[0236] The transmitting / receiving unit 220 may be configured as an integrated transmitting / receiving unit, or may be composed of a transmitting unit and a receiving unit. The transmitting unit may be composed of a transmission processing unit 2211 and an RF unit 222. The receiving unit may be composed of a reception processing unit 2212, an RF unit 222, and a measurement unit 223.

[0237] The transmitting / receiving antenna 230 can be configured from an antenna described based on common understanding in the technical field to which the present disclosure relates, such as an array antenna.

[0238] The transceiver 220 may receive the above-mentioned downlink channel, synchronization signal, downlink reference signal, etc. The transceiver 220 may transmit the above-mentioned uplink channel, uplink reference signal, etc.

[0239] The transceiver unit 220 may form at least one of the transmit beam and the receive beam using digital beamforming (e.g., precoding), analog beamforming (e.g., phase rotation), or the like.

[0240] The transceiver unit 220 (transmission processing unit 2211) may perform PDCP layer processing, RLC layer processing (e.g., RLC retransmission control), MAC layer processing (e.g., HARQ retransmission control), etc. on data, control information, etc. obtained from the control unit 210, and generate a bit string to be transmitted.

[0241] The transmitter / receiver unit 220 (transmission processing unit 2211) may perform transmission processing such as channel coding (which may include error correction coding), modulation, mapping, filtering, DFT processing (if necessary), IFFT processing, precoding, and digital-to-analog conversion on the bit string to be transmitted, and output a baseband signal.

[0242] Whether or not to apply DFT processing may be based on the setting of transform precoding. When transform precoding is enabled for a certain channel (e.g., PUSCH), the transceiver unit 220 (transmission processing unit 2211) may perform DFT processing as the transmission processing to transmit the channel using a DFT-s-OFDM waveform, and if not, it may not be necessary to perform DFT processing as the transmission processing.

[0243] The transceiver unit 220 (RF unit 222) may perform modulation, filtering, amplification, etc. on the baseband signal to a radio frequency band, and transmit the radio frequency band signal via the transceiver antenna 230.

[0244] On the other hand, the transceiver unit 220 (RF unit 222) may perform amplification, filtering, demodulation to a baseband signal, etc. on the radio frequency band signal received by the transceiver antenna 230.

[0245] The transceiver unit 220 (reception processing unit 2212) may apply reception processing such as analog-to-digital conversion, FFT processing, IDFT processing (if necessary), filtering, demapping, demodulation, decoding (which may include error correction decoding), MAC layer processing, RLC layer processing, and PDCP layer processing to the acquired baseband signal, and acquire user data, etc.

[0246] The transceiver 220 (measurement unit 223) may perform measurements on the received signal. For example, the measurement unit 223 may perform RRM measurements, CSI measurements, etc. based on the received signal. The measurement unit 223 may measure received power (e.g., RSRP), received quality (e.g., RSRQ, SINR, SNR), signal strength (e.g., RSSI), propagation path information (e.g., CSI), etc. The measurement results may be output to the control unit 210.

[0247] The transmitting unit and receiving unit of the user terminal 20 in the present disclosure may be configured by at least one of the transmitting / receiving unit 220 and the transmitting / receiving antenna 230.

[0248] The transceiver unit 220 may receive information regarding the configuration of beam failure detection for each transceiver point (TRP) and information regarding the configuration of uplink control channel resources corresponding to the scheduling request.

[0249] The transceiver 220 may receive information relating to the association between a TRP index and an index of an uplink control channel resource corresponding to the scheduling request. The transceiver 220 may receive information relating to the association between a TRP index and an index of configuration information of the scheduling request. The transceiver 220 may receive information relating to the association between a TRP index and an index of a spatial relationship of an uplink control channel resource corresponding to the scheduling request.

[0250] When a beam failure is detected in a first TRP, the control unit 210 may control the transmission of a scheduling request using either an uplink control channel resource corresponding to the first TRP or an uplink control channel resource corresponding to a second TRP different from the first TRP.

[0251] (Hardware Configuration) Note that the block diagrams used to explain the above embodiments show functional blocks. These functional blocks (components) are realized by any combination of at least one of hardware and software. Furthermore, the method for realizing each functional block is not particularly limited. That is, each functional block may be realized using a single device that is physically or logically coupled, or may be realized using two or more physically or logically separated devices that are directly or indirectly connected (for example, using wires, wirelessly, etc.) and these multiple devices. The functional block may be realized by combining software with the single device or the multiple devices.

[0252] Here, the functions include, but are not limited to, judgment, determination, judgment, calculation, computation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, election, establishment, comparison, assumption, expectation, deeming, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assignment. For example, a functional block (component) that performs transmission may be called a transmitting unit, transmitter, etc. As described above, the implementation method of each is not particularly limited.

[0253] For example, a base station, a user terminal, or the like according to an embodiment of the present disclosure may function as a computer that performs processing of the wireless communication method of the present disclosure. Fig. 13 is a diagram illustrating an example of the hardware configuration of a base station and a user terminal according to an embodiment. The above-described base station 10 and user terminal 20 may be physically configured as a computer device including a processor 1001, a memory 1002, a storage 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, and the like.

[0254] In the present disclosure, the terms apparatus, circuit, device, section, unit, etc. may be used interchangeably. The hardware configurations of the base station 10 and the user terminal 20 may be configured to include one or more of the devices shown in the drawings, or may be configured to exclude some of the devices.

[0255] For example, although only one processor 1001 is shown, there may be multiple processors. Furthermore, processing may be performed by one processor, or processing may be performed by two or more processors simultaneously, serially, or in other ways. Furthermore, processor 1001 may be implemented by one or more chips.

[0256] Each function in the base station 10 and the user terminal 20 is realized, for example, by loading specified software (programs) onto hardware such as a processor 1001 and a memory 1002, causing the processor 1001 to perform calculations, control communication via the communication device 1004, and control at least one of reading and writing data in the memory 1002 and the storage 1003.

[0257] The processor 1001, for example, runs an operating system to control the entire computer. The processor 1001 may be configured as a central processing unit (CPU) including an interface with peripheral devices, a control device, an arithmetic unit, a register, etc. For example, at least a part of the above-mentioned control unit 110 (210), transceiver unit 120 (220), etc. may be realized by the processor 1001.

[0258] The processor 1001 also reads programs (program codes), software modules, data, etc. from at least one of the storage 1003 and the communication device 1004 into the memory 1002 and executes various processes in accordance with these. The programs used are those that cause a computer to execute at least some of the operations described in the above-described embodiments. For example, the control unit 110 (210) may be implemented by a control program stored in the memory 1002 and running on the processor 1001, and the other functional blocks may be implemented in a similar manner.

[0259] The memory 1002 is a computer-readable recording medium and may be configured by at least one of, for example, Read Only Memory (ROM), Erasable Programmable ROM (EPROM), Electrically EEPROM (EEPROM), Random Access Memory (RAM), or other suitable storage medium. The memory 1002 may also be referred to as a register, cache, main memory, etc. The memory 1002 may store executable programs (program codes), software modules, etc. for implementing a wireless communication method according to an embodiment of the present disclosure.

[0260] Storage 1003 is a computer-readable recording medium and may be composed of at least one of, for example, a flexible disk, a floppy disk, a magneto-optical disk (e.g., a compact disc (e.g., a Compact Disc ROM (CD-ROM)), a digital versatile disc, a Blu-ray disc), a removable disk, a hard disk drive, a smart card, a flash memory device (e.g., a card, a stick, a key drive), a magnetic stripe, a database, a server, or other suitable storage medium. Storage 1003 may also be referred to as an auxiliary storage device.

[0261] The communication device 1004 is hardware (transmission / reception device) for communicating between computers via at least one of a wired network and a wireless network, and is also referred to as, for example, a network device, a network controller, a network card, or a communication module. The communication device 1004 may be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc. to realize at least one of frequency division duplex (FDD) and time division duplex (TDD). For example, the above-mentioned transmission / reception unit 120 (220), transmission / reception antenna 130 (230), etc. may be realized by the communication device 1004. The transmission / reception unit 120 (220) may be implemented as a transmission unit 120a (220a) and a reception unit 120b (220b) that are physically or logically separated.

[0262] The input device 1005 is an input device (e.g., a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.) that accepts input from the outside. The output device 1006 is an output device (e.g., a display, a speaker, a light emitting diode (LED) lamp, etc.) that outputs to the outside. Note that the input device 1005 and the output device 1006 may be integrated into one device (e.g., a touch panel).

[0263] Furthermore, each device, such as the processor 1001 and the memory 1002, is connected by a bus 1007 for communicating information. The bus 1007 may be configured using a single bus, or may be configured using different buses between each device.

[0264] Furthermore, the base station 10 and the user terminal 20 may be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a programmable logic device (PLD), or a field programmable gate array (FPGA), and some or all of the functional blocks may be realized using this hardware. For example, the processor 1001 may be implemented using at least one of these pieces of hardware.

[0265] (Modifications) Note that terms described in the present disclosure and terms necessary for understanding the present disclosure may be replaced with terms having the same or similar meanings. For example, a channel, a symbol, and a signal (signal or signaling) may be interchangeable. A signal may also be a message. A reference signal may be abbreviated as RS, and may also be called a pilot, pilot signal, etc. depending on the applicable standard. A component carrier (CC) may also be called a cell, frequency carrier, carrier frequency, etc.

[0266] A radio frame may be composed of one or more periods (frames) in the time domain. Each of the one or more periods (frames) constituting a radio frame may be called a subframe. Furthermore, a subframe may be composed of one or more slots in the time domain. A subframe may have a fixed time length (e.g., 1 ms) that is independent of numerology.

[0267] Here, the numerology may be a communication parameter applied to at least one of transmission and reception of a signal or channel, and may indicate at least one of, for example, Subcarrier Spacing (SCS), bandwidth, symbol length, cyclic prefix length, Transmission Time Interval (TTI), number of symbols per TTI, radio frame structure, specific filtering performed by a transceiver in the frequency domain, and specific windowing performed by a transceiver in the time domain.

[0268] A slot may be composed of one or more symbols (such as an Orthogonal Frequency Division Multiplexing (OFDM) symbol or a Single Carrier Frequency Division Multiple Access (SC-FDMA) symbol) in the time domain. A slot may also be a time unit based on numerology.

[0269] A slot may include multiple minislots. Each minislot may consist of one or multiple symbols in the time domain. A minislot may also be called a subslot. A minislot may consist of fewer symbols than a slot. A PDSCH (or PUSCH) transmitted in a time unit larger than a minislot may be called PDSCH (PUSCH) mapping type A. A PDSCH (or PUSCH) transmitted using a minislot may be called PDSCH (PUSCH) mapping type B.

[0270] A radio frame, a subframe, a slot, a minislot, and a symbol all represent time units for transmitting signals. The radio frame, the subframe, the slot, the minislot, and the symbol may be referred to by other names corresponding to the radio frame, the subframe, the slot, the minislot, and the symbol. Note that the time units such as a frame, a subframe, a slot, a minislot, and a symbol in the present disclosure may be interchangeable.

[0271] For example, one subframe may be referred to as a TTI, or multiple consecutive subframes may be referred to as a TTI, or one slot or one minislot may be referred to as a TTI. That is, at least one of the subframe and the TTI may be a subframe (1 ms) in existing LTE, a period shorter than 1 ms (for example, 1-13 symbols), or a period longer than 1 ms. Note that the unit representing the TTI may be called a slot, minislot, etc. instead of a subframe.

[0272] Here, TTI refers to, for example, the smallest time unit for scheduling in wireless communication. For example, in an LTE system, a base station performs scheduling to allocate radio resources (such as frequency bandwidth and transmission power that can be used by each user terminal) to each user terminal in TTI units. Note that the definition of TTI is not limited to this.

[0273] The TTI may be a transmission time unit for a channel-encoded data packet (transport block), a code block, a code word, etc., or may be a processing unit for scheduling, link adaptation, etc. When a TTI is given, the time interval (e.g., the number of symbols) to which a transport block, a code block, a code word, etc. is actually mapped may be shorter than the TTI.

[0274] When one slot or one minislot is called a TTI, one or more TTIs (i.e., one or more slots or one or more minislots) may be the minimum time unit for scheduling. Also, the number of slots (minislots) constituting the minimum time unit for scheduling may be controlled.

[0275] A TTI having a time length of 1 ms may be called a regular TTI (TTI in 3GPP Rel. 8-12), normal TTI, long TTI, regular subframe, normal subframe, long subframe, slot, etc. A TTI shorter than a regular TTI may be called a shortened TTI, short TTI, partial or fractional TTI, shortened subframe, short subframe, minislot, subslot, slot, etc.

[0276] In addition, a long TTI (e.g., a normal TTI, a subframe, etc.) may be interpreted as a TTI having a time length of more than 1 ms, and a short TTI (e.g., a shortened TTI, etc.) may be interpreted as a TTI having a TTI length shorter than the TTI length of a long TTI and greater than or equal to 1 ms.

[0277] A resource block (RB) is a resource allocation unit in the time domain and the frequency domain, and may include one or more consecutive subcarriers in the frequency domain. The number of subcarriers included in an RB may be the same regardless of numerology, for example, 12. The number of subcarriers included in an RB may be determined based on numerology.

[0278] In addition, an RB may include one or more symbols in the time domain and may have a length of one slot, one minislot, one subframe, or one TTI, each of which may be composed of one or more resource blocks.

[0279] In addition, one or more RBs may be referred to as a physical resource block (PRB), a sub-carrier group (SCG), a resource element group (REG), a PRB pair, an RB pair, etc.

[0280] Furthermore, a resource block may be composed of one or more resource elements (REs). For example, one RE may be a radio resource region of one subcarrier and one symbol.

[0281] A Bandwidth Part (BWP), which may also be referred to as a partial bandwidth, may represent a subset of contiguous common resource blocks (RBs) for a given numerology on a given carrier, where the common RBs may be identified by their index relative to a Common Reference Point of the carrier. PRBs may be defined in a BWP and numbered within the BWP.

[0282] The BWP may include a UL BWP (BWP for UL) and a DL BWP (BWP for DL). One or more BWPs may be configured for a UE within one carrier.

[0283] At least one of the configured BWPs may be active, and the UE may not expect to transmit or receive a given signal / channel outside the active BWP. Note that the terms "cell," "carrier," etc. in this disclosure may be read as "BWP."

[0284] The above-described structures of radio frames, subframes, slots, minislots, symbols, etc. are merely examples. For example, the number of subframes included in a radio frame, the number of slots per subframe or radio frame, the number of minislots included in a slot, the number of symbols and RBs included in a slot or minislot, the number of subcarriers included in an RB, the number of symbols in a TTI, the symbol length, the cyclic prefix (CP) length, etc. may be changed in various ways.

[0285] Furthermore, the information, parameters, etc. described in the present disclosure may be expressed using absolute values, may be expressed using relative values ​​from a predetermined value, or may be expressed using other corresponding information. For example, a radio resource may be indicated by a predetermined index.

[0286] The names used for parameters and the like in this disclosure are not intended to be limiting in any way. Furthermore, the mathematical expressions and the like using these parameters may differ from those explicitly disclosed in this disclosure. The various channels (PUCCH, PDCCH, etc.) and information elements may be identified by any suitable names, and therefore the various names assigned to these various channels and information elements are not intended to be limiting in any way.

[0287] The information, signals, etc. described in this disclosure may be represented using any of a variety of different technologies. For example, data, instructions, commands, information, signals, bits, symbols, chips, etc. that may be referred to throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combination thereof.

[0288] Furthermore, information, signals, etc. may be output from a higher layer to a lower layer and / or from a lower layer to a higher layer. Information, signals, etc. may be input / output via multiple network nodes.

[0289] Input and output information, signals, etc. may be stored in a specific location (for example, memory) or may be managed using a management table. Input and output information, signals, etc. may be overwritten, updated, or added. Output information, signals, etc. may be deleted. Input information, signals, etc. may be transmitted to another device.

[0290] The notification of information is not limited to the aspects / embodiments described in the present disclosure, and may be performed using other methods. For example, the notification of information in the present disclosure may be performed by physical layer signaling (e.g., Downlink Control Information (DCI) and Uplink Control Information (UCI)), higher layer signaling (e.g., Radio Resource Control (RRC) signaling, broadcast information (Master Information Block (MIB) and System Information Block (SIB)), Medium Access Control (MAC) signaling), other signals, or a combination thereof.

[0291] Note that the physical layer signaling may be referred to as Layer 1 / Layer 2 (L1 / L2) control information (L1 / L2 control signal), L1 control information (L1 control signal), etc. Furthermore, the RRC signaling may be referred to as an RRC message, such as an RRC Connection Setup message or an RRC Connection Reconfiguration message. Furthermore, the MAC signaling may be notified using, for example, a media access control control element (MAC Control Element (CE)).

[0292] Furthermore, notification of specified information (e.g., notification that "it is X") is not limited to explicit notification, but may be made implicitly (e.g., by not notifying the specified information or by notifying other information).

[0293] The determination may be made by a value represented by one bit (0 or 1), by a Boolean value represented by true or false, or by a comparison of numerical values ​​(e.g., comparison with a predetermined value).

[0294] Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.

[0295] Software, instructions, information, etc. may also be transmitted or received over a transmission medium. For example, if software is transmitted from a website, server, or other remote source using wired technologies (such as coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL)), and / or wireless technologies (such as infrared, microwave), these wired and / or wireless technologies are included within the definition of transmission media.

[0296] As used in this disclosure, the terms "system" and "network" may be used interchangeably. A "network" may refer to devices included in the network (e.g., base stations).

[0297] In the present disclosure, terms such as "precoding," "precoder," "weight (precoding weight)," "Quasi-Co-Location (QCL)," "Transmission Configuration Indication state (TCI state)," "spatial relation," "spatial domain filter," "transmit power," "phase rotation," "antenna port," "antenna port group," "Reference Signal (RS) port group," "layer," "number of layers," "rank," "resource," "resource set," "resource group," "beam," "beam width," "beam angle," "antenna," "antenna element," "panel," "transmitting and receiving point," etc. may be used interchangeably.

[0298] In the present disclosure, terms such as "base station (BS)," "radio base station," "fixed station," "NodeB," "eNB (eNodeB)," "gNB (gNodeB)," "access point," "transmission point (TP)," "reception point (RP)," "transmission / reception point (TRP)," "panel," "cell," "sector," "cell group," "carrier," "component carrier," etc. may be used interchangeably. Base stations may also be referred to by terms such as macrocell, small cell, femtocell, picocell, etc.

[0299] A base station can accommodate one or more (e.g., three) cells. When a base station accommodates multiple cells, the overall coverage area of ​​the base station can be partitioned into multiple smaller areas, and each smaller area can be provided with communication service by a base station subsystem (e.g., a small indoor base station (Remote Radio Head (RRH))). The terms "cell" or "sector" refer to part or all of the coverage area of ​​a base station and / or base station subsystem that provides communication service within that coverage.

[0300] In this disclosure, the terms "Mobile Station (MS)," "user terminal," "User Equipment (UE)," "terminal," etc. may be used interchangeably.

[0301] A mobile station may also be referred to as a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or some other suitable terminology.

[0302] At least one of the base station and the mobile station may be referred to as a transmitting device, a receiving device, a wireless communication device, etc. At least one of the base station and the mobile station may be a device mounted on a mobile body, the mobile body itself, etc. The mobile body may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile body (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). At least one of the base station and the mobile station may also include devices that do not necessarily move during communication operations. For example, at least one of the base station and the mobile station may be an Internet of Things (IoT) device such as a sensor.

[0303] Furthermore, a base station in the present disclosure may be read as a user terminal. For example, the aspects / embodiments of the present disclosure may be applied to a configuration in which communication between a base station and a user terminal is replaced with communication between multiple user terminals (which may be called, for example, Device-to-Device (D2D) or Vehicle-to-Everything (V2X)). In this case, the user terminal 20 may be configured to have the functions of the base station 10 described above. Furthermore, terms such as "uplink" and "downlink" may be read as terms corresponding to terminal-to-terminal communication (for example, "side"). For example, terms such as an uplink channel and a downlink channel may be read as a side channel.

[0304] Similarly, the user terminal in the present disclosure may be read as a base station, in which case the base station 10 may be configured to have the functions of the user terminal 20 described above.

[0305] In the present disclosure, an operation described as being performed by a base station may be performed by its upper node in some cases. It is apparent that in a network including one or more network nodes having a base station, various operations performed for communication with a terminal may be performed by the base station, one or more network nodes other than the base station (such as, but not limited to, a Mobility Management Entity (MME), a Serving-Gateway (S-GW), etc.), or a combination thereof.

[0306] Each aspect / embodiment described in this disclosure may be used alone, in combination, or switched depending on the implementation. Furthermore, the order of the processing procedures, sequences, flowcharts, etc. of each aspect / embodiment described in this disclosure may be changed unless inconsistent. For example, the methods described in this disclosure present elements of various steps using an example order, and are not limited to the particular order presented.

[0307] Each aspect / embodiment described in the present disclosure may be a technology other than Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 6th generation mobile communication system (6G), xth generation mobile communication system (xG) (xG (x is, for example, an integer or decimal number)), Future Radio Access (FRA), New-Radio Access Technology (RAT), New Radio (NR), New radio access (NX), Future generation radio access (FX), Global System for Mobile communications (GSM (registered trademark)), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.17 (WiMAX (registered trademark)), IEEE 802.19 (WiMAX (registered trademark)), IEEE 802.20 (WiMAX (registered trademark)), IEEE 802.21 (Wi-Fi (registered trademark)), IEEE 802.22 (WiMAX (registered trademark)), IEEE 802.23 (WiMAX (registered trademark)), IEEE 802.24 (WiMAX (registered trademark)), IEEE 802.25 (WiMAX (registered trademark)), IEEE 802.26 (WiMAX (registered trademark)), IEEE 802.27 (WiMAX (registered trademark)), IEEE 802.28 (WiMAX (registered trademark)), IEEE 802.29 (WiMAX (registered trademark)), IEEE 802.30 (WiMAX (registered trademark)), IEEE 802.31 (Wi-Fi (registered trademark)), IEEE 802.32 (WiMAX (registered trademark)), IEEE 802.33 (WiMAX (registered trademark)), IEEE The present invention may be applied to systems that use IEEE 802.20, Ultra-WideBand (UWB), Bluetooth (registered trademark), or other appropriate wireless communication methods, or to next-generation systems that are based on these and are extended thereto. In addition, the present invention may be applied to a combination of multiple systems (for example, a combination of LTE or LTE-A and 5G).

[0308] As used in this disclosure, the phrase "based on" does not mean "based only on," unless expressly stated otherwise. In other words, the phrase "based on" means both "based only on" and "based at least on."

[0309] As used in this disclosure, any reference to an element using a designation such as "first," "second," etc. does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient method of distinguishing between two or more elements. Thus, a reference to a first and a second element does not imply that only two elements may be employed or that the first element must in some way precede the second element.

[0310] The term "determining" as used in this disclosure may encompass a wide variety of actions. For example, "determining" may be considered to be judging, calculating, computing, processing, deriving, investigating, looking up, search, inquiry (e.g., looking up in a table, database, or another data structure), ascertaining, etc.

[0311] Additionally, "determining" may be considered to be "determining" receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, accessing (e.g., accessing data in memory), etc.

[0312] Also, "determination" may be considered to be "deciding" resolving, selecting, choosing, establishing, comparing, etc. In other words, "determination" may be considered to be "deciding" some action.

[0313] Furthermore, "judgment (decision)" may be read as "assuming," "expecting," "considering," or the like.

[0314] As used in this disclosure, the terms "connected," "coupled," or any variation thereof, refer to any direct or indirect connection or coupling between two or more elements, and may include the presence of one or more intermediate elements between two elements that are "connected" or "coupled" to each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, "connected" may be read as "access."

[0315] In this disclosure, when two elements are connected, they may be considered to be "connected" or "coupled" to one another using one or more wires, cables, printed electrical connections, etc., as well as using electromagnetic energy having wavelengths in the radio frequency range, microwave range, light (both visible and invisible) range, etc., as some non-limiting and non-exhaustive examples.

[0316] In the present disclosure, the term "A and B are different" may mean "A and B are different from each other." The term may also mean "A and B are each different from C." Terms such as "separate" and "coupled" may also be interpreted in the same way as "different."

[0317] When the terms "include," "including," and variations thereof are used in this disclosure, these terms are intended to be inclusive, similar to the term "comprising." Furthermore, when the term "or" is used in this disclosure, it is not intended to be an exclusive or.

[0318] In this disclosure, where articles are added by translation, such as a, an, and the in English, the disclosure may include that the nouns following these articles are in the plural form.

[0319] Although the invention according to the present disclosure has been described in detail above, it is clear to those skilled in the art that the invention according to the present disclosure is not limited to the embodiments described in the present disclosure. The invention according to the present disclosure can be implemented in modified and altered forms without departing from the spirit and scope of the invention as defined by the description of the claims. Therefore, the description of the present disclosure is intended to be illustrative and explanatory and does not impose any limiting meaning on the invention according to the present disclosure.

[0320] This application is based on Japanese Patent Application No. 2021-088742, filed on May 26, 2021, the contents of which are incorporated herein in their entirety.

Claims

1. a receiving unit that receives first information regarding a setting of beam fault detection for each transmitting / receiving point (TRP) and second information regarding a setting of an uplink control channel resource corresponding to a scheduling request; A control unit is provided which, when a beam failure is detected in a first TRP, controls transmission of the scheduling request using a first uplink control channel resource corresponding to the first TRP and a second uplink control channel resource corresponding to a second TRP different from the first TRP, A terminal in which, after a beam failure recovery procedure, the quasi-colocation of the physical downlink control channel (PDCCH) is updated to a new beam, wherein the new beam is determined from a reference signal (RS) set for identifying a first new candidate beam associated with the first TRP and an RS set for identifying a second new candidate beam associated with the second TRP.

2. The terminal according to claim 1 , wherein the receiving unit receives third information regarding an association between an RS set for beam failure detection of each TRP and an index of the configuration information of the scheduling request.

3. receiving first information on beam failure detection configuration for each transmission / reception point (TRP) and second information on uplink control channel resource configuration corresponding to the scheduling request; When a beam failure is detected in a first TRP, the method includes controlling the transmission of the scheduling request by using a first uplink control channel resource corresponding to the first TRP and a second uplink control channel resource corresponding to a second TRP different from the first TRP; A wireless communication method for a terminal, in which after a beam failure recovery procedure, the quasi-colocation of a physical downlink control channel (PDCCH) is updated to a new beam, wherein the new beam is determined from a reference signal (RS) set for identifying a first new candidate beam associated with the first TRP and an RS set for identifying a second new candidate beam associated with the second TRP.

4. a transmitter that transmits, to a terminal, first information regarding a setting of beam fault detection for each transmission / reception point (TRP) and second information regarding a setting of an uplink control channel resource corresponding to a scheduling request; When the terminal detects a beam failure in a first TRP, a control unit controls reception of a scheduling request transmitted from the terminal using a first uplink control channel resource among a first uplink control channel resource corresponding to the first TRP and a second uplink control channel resource corresponding to a second TRP different from the first TRP, A base station, wherein after a beam failure recovery procedure, the quasi-colocation of the physical downlink control channel (PDCCH) is updated to a new beam, wherein the new beam is determined from a reference signal (RS) set for identifying a first new candidate beam associated with the first TRP and an RS set for identifying a second new candidate beam associated with the second TRP.

5. A system including a terminal and a base station, The terminal a receiving unit that receives first information regarding a setting of beam fault detection for each transmitting / receiving point (TRP) and second information regarding a setting of an uplink control channel resource corresponding to a scheduling request; A control unit is provided which, when a beam failure is detected in a first TRP, controls transmission of the scheduling request using a first uplink control channel resource corresponding to the first TRP and a second uplink control channel resource corresponding to a second TRP different from the first TRP, After the beam failure recovery procedure, the quasi-co-location of the physical downlink control channel (PDCCH) is updated to a new beam, where the new beam is determined from a reference signal (RS) set for identifying a first new candidate beam associated with the first TRP and a RS set for identifying a second new candidate beam associated with the second TRP; The base station A system comprising a transmitter that transmits the first information and the second information.