Terminal, wireless communication method, base station and system

Abstract

The present invention performs transmission of a scheduling request (SR) appropriately even when an SR configuration is extended. A terminal according to one aspect of the present disclosure comprises: a receiving unit for receiving information regarding the configuration of a scheduling request (SR) for detecting beam failure; and a control unit which, if there are a plurality of configurations of the SR, if a plurality of uplink control channel resources are configured for the SR, or if a plurality of spatial relationships correspond to an uplink control channel resource configured for the SR, controls the SR to be applied with respect to a plurality of purposes.

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 a beam failure and switching to another beam (which may also be called a Beam Failure Recovery (BFR) procedure, BFR, link recovery procedure, etc.). In NR from Rel. 17 onwards (or beyond 5G, 6G and later), it is also expected that a terminal (UE) will communicate using multiple transmission / reception points (TRPs) / UE panels. In this case, it is considered that beam management (e.g., beam failure detection) will be performed in multiple TRPs / multiple UE panels.

[0007] In existing systems (e.g., Rel. 16 and earlier), a UE is supported to transmit a scheduling request (e.g., SR) using uplink control channel (e.g., PUCCH) resources when it detects a beam failure. It is also assumed that the SR / SR setting used for BFR may also be used for other purposes (or other communication control / applications) (SR sharing).

[0008] On the other hand, in future wireless communication systems (Rel. 17 and later), it is expected that the SR / SR settings used for BFR will be expanded.

[0009] However, when the configuration of the SR for BFR (for example, the configuration of the PUCCH resource for SR) is extended, how to control the configuration / application of the SR for other purposes (for example, SR sharing) becomes an issue. If the SR transmission is not performed appropriately for each purpose, there is a risk of a decrease in communication throughput or a deterioration in communication quality.

[0010] The present disclosure has been made in consideration of such points, and one of its objectives is to provide a terminal, a wireless communication method, and a base station that are capable of appropriately transmitting a scheduling request (SR) even when the SR setting is extended.

[0011] A terminal according to one aspect of the present disclosure is characterized by having a receiving unit that receives information regarding the setting of a scheduling request (SR) for beam failure detection, and a control unit that controls the SR to be applied to multiple purposes when multiple SRs are set, when multiple uplink control channel resources are set for the SR, or when multiple spatial relationships correspond to the uplink control channel resources set for the SR.

[0012] According to one aspect of the present disclosure, it is possible to appropriately transmit a scheduling request (SR) even when the SR configuration is extended.

[0013] 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 and 3B are diagrams showing an example of SR sharing control according to the first aspect. Fig. 4 is a diagram showing another example of SR sharing control according to the first aspect. Figs. 5A and 5B are diagrams showing an example of SR transmission control when SR sharing according to the second aspect is performed. Figs. 6A and 6B are diagrams showing another example of SR transmission control when SR sharing according to the second aspect is performed. Figs. 7A and 7B are diagrams showing another example of SR transmission control when SR sharing according to the second aspect is performed. Fig. 8 is a diagram showing an example of a schematic configuration of a wireless communication system according to an embodiment. Fig. 9 is a diagram showing an example of the configuration of a base station according to an embodiment. Fig. 10 is a diagram illustrating an example of the configuration of a user terminal according to an embodiment. Fig. 11 is a diagram illustrating an example of the hardware configuration of a base station and a user terminal according to an embodiment.

[0014] (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.).

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

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

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

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

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

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

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

[0022] 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).

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

[0024] 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).

[0025] 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).

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

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

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

[0029] 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).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0049] 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).

[0050] 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).

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

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

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

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

[0055] 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)), are being considered.

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

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

[0058] 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, TRP-specific BFR). For example, it is possible that SR transmission / SR setting / SR ID / PUCCH resource for SR is supported for each TRP / TRP unit / TRP-specific BFR.

[0059] By performing BFR on a TRP basis, it becomes possible to more flexibly control the beam fault detection / beam recovery procedure when a cell contains multiple TRPs.

[0060] (Unlicensed band) In an unlicensed band (e.g., the 2.4 GHz band, the 5 GHz band, the 6 GHz band, etc., which may also be referred to as an unlicensed spectrum), it is expected that multiple systems, such as a Wi-Fi system and a system supporting Licensed-Assisted Access (LAA) (LAA system), will coexist, and therefore collision avoidance and / or interference control of transmissions between the multiple systems will be required.

[0061] In LAA in existing LTE systems (e.g., Rel. 13), a data transmitting device listens to determine whether or not other devices (e.g., base stations, user terminals, Wi-Fi devices, etc.) are transmitting data in unlicensed bands before transmitting data. This listening may also be called Listen Before Talk (LBT), Clear Channel Assessment (CCA), carrier sense, channel sensing, sensing, channel access procedure, shared spectrum channel access procedure, energy detection (ED), etc.

[0062] The transmitting device may be, for example, a base station (which may be called, for example, a gNodeB (gNB) or a network (NW)) in the downlink (DL) and a user terminal (UE) in the uplink (UL). Also, a receiving device that receives data from the transmitting device may be, for example, a user terminal in the DL and a base station (NW) in the UL.

[0063] In the LAA of existing LTE systems, the transmitting device starts transmitting data a predetermined period (e.g., immediately after or during a backoff period) after detecting that no other devices are transmitting (idle state) in the LBT.

[0064] The use of unlicensed bands is also being considered for future wireless communication systems (e.g., 5G, 5G+, New Radio (NR), 3GPP Rel. 15 and later, etc.). NR systems that use unlicensed bands may also be called NR-Unlicensed (U) systems, NR LAA systems, etc.

[0065] NR-U may also include dual connectivity (DC) between licensed bands and unlicensed bands, and stand-alone (SA) of unlicensed bands.

[0066] In order to coexist with other systems or other operators, nodes in NR-U (e.g., base stations, UEs) confirm that the channel is idle using LBT before starting transmission.

[0067] In NR-U, a base station (e.g., a gNB) or a UE acquires a transmission opportunity (Transmission Opportunity (TxOP)) and transmits when the LBT result is idle. The base station or UE does not transmit when the LBT result is busy (LBT-busy). The time of the transmission opportunity may be called the channel occupancy time (COT).

[0068] Note that LBT-idle may be interpreted as LBT success, and LBT-busy may be interpreted as LBT failure.

[0069] (LBT Failure) LBT failure (eg, consistent LBT failure) may be detected per UL BWP by counting LBT failure indications of all UL transmissions from lower layers to the MAC entity.

[0070] The RRC may use predetermined upper layer parameters (e.g., lbt-FailureRecoveryConfig) to configure parameters for LBT failure detection (e.g., maximum count for LBT failure detection, timer for LBT detection).

[0071] When an LBT failure is triggered, the MAC entity transmits the MAC CE for the LBT failure if UL-SCH resources for transmitting the MAC CE for the LBT failure are available, while in other cases (e.g., when UL-SCH resources for transmitting the MAC CE for the LBT failure are not available), the MAC entity triggers a scheduling request (SR) for transmitting the MAC CE for the LBT failure.

[0072] In this way, the transmission of SR is supported in the LBT failure (LBT detection / recovery) procedure as well as the mechanism of the BFR procedure.

[0073] (SR Sharing) Sharing the SR for the TRP-specific BFR (e.g., SR for BFR) with other purposes / uses (or using it for other purposes / uses) is under consideration. SR may be read as SR configuration or SR ID.

[0074] The other purposes / uses may be, for example, one or more logical channels and / or LBT failure recovery (e.g., consistent LBT failure recovery).

[0075] An SR resource (or an SR PUCCH resource) may be configured for each SR configuration / ID. In existing systems (e.g., Rel. 16), it is supported that an SR for BFR corresponds to a maximum of one PUCCH resource.

[0076] For example, up to one PUCCH resource for SR may be configured for each BWP for a logical channel, an SCell beam failure recovery, and an LBT failure recovery (consistent LBT failure recovery). Each SR configuration may correspond to at least one of one or more logical channels, an SCell beam failure recovery, and an LBT failure recovery.

[0077] On the other hand, in future wireless communication systems (e.g., Rel. 17 and later), it is expected that the SR / SR configuration used for BFR will be extended. For example, consideration is being given to supporting a case in which multiple (e.g., two) PUCCH resources for SR are configured / corresponding to an SR for BFR, or a case in which multiple (e.g., two) PUCCH resources for SR having a spatial relationship are configured / corresponding to an SR for BFR. Alternatively, consideration is being given to supporting a case in which multiple (e.g., two) SRs for BFR are configured, and one or more PUCCH resources are configured / corresponding to each SR for BFR.

[0078] However, when the configuration of the SR for BFR (or the PUCCH resource / spatial relationship for SR) is extended, a problem arises as to how to control the configuration / application of the SR for other purposes (e.g., SR sharing). Alternatively, when the SR for BFR is shared for other purposes / applications, a problem arises as to how to control the selection of the PUCCH resource / spatial relationship for SR when the SR for BFR is applied / triggered for the other purposes / applications. If SR transmission is not performed appropriately for each purpose, a decrease in communication throughput or degradation of communication quality may occur.

[0079] The present inventors focused on the case where the SR for BFR is extended, and studied SR sharing for multiple purposes / uses in such a case, and came up with an idea for one aspect of this embodiment.

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

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

[0082] 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).

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

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

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

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

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

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

[0089] In the present disclosure, BFR may include SCell BFR in Rel. 16 / per-TRP BFR in Rel. 17 and later. In the following description, PUCCH may be read as PUCCH for SR, and PUCCH resources may be read as PUCCH-SR resources or PUCCH resources for SR. Also, PUCCH for SR and PUCCH resources for SR may be read interchangeably. BFR for per-TRP may be read as BFR per TRP. Cell-specific BFR may be read as BFR per cell.

[0090] (SR Configuration Example) For SR configuration, at least one of the following options A, B, and C may be supported. Of course, other configurations may also be supported.

[0091] <Option A> 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).

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

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

[0094] <Option B> 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).

[0095] 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 B may be read as first SR / first SR setting.

[0096] <Option C> In the SR (e.g., SR index / SchedulingRequestID) for each cell group, 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).

[0097] 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 C may be interpreted as second SR / second SR setting.

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

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

[0100] 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).

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

[0102] The following description illustrates a case where the spatial relationship corresponding to the SR for BFR, the PUCCH resource for SR set in the SR for BFR, or the PUCCH resource for SR set in the SR for BFR is set / applied to another purpose / use (hereinafter simply referred to as purpose), but is not limited to this. A common SR / PUCCH resource for SR / spatial relationship may be set / applied to multiple purposes including the SR for BFR. Alternatively, a configuration may be adopted in which the SR / PUCCH for SR / spatial relationship set for a purpose other than BFR is set / applied to BFR.

[0103] (First Aspect) In the first aspect, an example of SR sharing control will be described in a case where a plurality of PUCCH resources for SR are configured in an SR for BFR, a case where a plurality of PUCCH resources having a spatial relationship are configured, or a case where a plurality of SRs for BFR are configured.

[0104] For example, at least one of the following options 1-1 to 1-2 may be used to set / control SR sharing.

[0105] <Option 1-1> When multiple PUCCH resources for SR are configured in an SR for BFR (for example, an SR configuration for BFR of a predetermined index), or when one PUCCH resource for SR having multiple spatial relationships is configured in an SR for BFR, at least one of Option 1-1-1 to Option 1-1-2 below may be applied. Note that in this embodiment, an example is given in which two PUCCH resources for SR are configured as multiple PUCCH resources for SR, but the number of PUCCH resources for SR configured may be three or more. Also, an example is given in which two resources are configured as multiple spatial relationships, but the number of spatial relationships configured may be two or more.

[0106] <<Option 1-1-1>> The SR for BFR may be configured to support being configured / applied for another purpose (or multiple purposes) (SR sharing is supported). In this case, information about the SR configured / applied for another purpose may be notified / configured from the base station to the UE using higher layer parameters / MAC CE, etc.

[0107] For example, an SR in which multiple PUCCH resources for SR are configured (see Case 1-1-1A in FIG. 3A ), or an SR in which multiple PUCCH resources for SR having spatial relationships are configured (see Case 1-1-1B in FIG. 3B ) may be configured / applied corresponding to one or multiple logical channels (e.g., logical channels). Alternatively, the SR may be configured / applied corresponding to LBT failure recovery (consistent LBT failure recovery). LBT failure recovery may be interpreted as LBT detection / recovery.

[0108] <<Option 1-1-2>> The SR for BFR may be configured so that it is not supported to be set / applied for other purposes (or multiple purposes) (SR sharing is not supported).

[0109] For example, an SR configured with multiple PUCCH resources for SR (see Case 1-1-2A in FIG. 3A) or an SR configured with multiple PUCCH resources for SR having spatial relationships (see Case 1-1-2B in FIG. 3B) may be controlled not to be configured / applied in correspondence with one or multiple logical channels. Alternatively, the SR may be controlled not to be configured / applied in correspondence with LBT failure recovery.

[0110] Alternatively, the SR for BFR may be set (or shared) for only some purposes.

[0111] Furthermore, among a plurality of PUCCH resources for SR configured for SR, only some of the PUCCH resources for SR (for example, one PUCCH resource for SR) may be configured / applied for another purpose. Alternatively, among the PUCCH resources for SR having a plurality of spatial relationships, only some of the spatial relationships (for example, one spatial relationship) may be configured / applied for another purpose.

[0112] <Option 1-2> When multiple (e.g., two) SRs for BFR are configured and one or more (e.g., one) PUCCH resources for SR are configured for each SR, at least one of the following options 1-2-1 to 1-2-3 may be applied: A separate PUCCH resource for SR (e.g., a different PUCCH resource for SR) may be configured for each SR for BFR.

[0113] <<Option 1-2-1>> Each BFR SR may be configured to support being configured / applied for other purposes (or multiple purposes) (SR sharing supported) (see Case 1-2-1 in Figure 4).

[0114] For example, multiple SRs (e.g., SRs #1 and #2 for BFR) each having a PUCCH resource for SR configured therein may be configured / applied corresponding to one or multiple logical channels. Alternatively, each SR may be configured / applied corresponding to a failure recovery of LBT.

[0115] <<Option 1-2-2>> Each BFR SR may be configured such that it is not supported to be configured / applied for other purposes (or multiple purposes) (SR sharing is not supported) (see Case 1-2-2 in Figure 4).

[0116] For example, multiple SRs each having a PUCCH resource for SR configured therein may be controlled not to be configured / applied in correspondence with one or multiple logical channels, or each SR may be controlled not to be configured / applied in correspondence with LBT failure recovery.

[0117] <<Option 1-2-3>> Some of the multiple BFR SRs (e.g., one BFR SR#1) may be configured to support being set / applied for another purpose (or multiple purposes) (see Case 1-2-3 in FIG. 4 ), while another BFR SR#2 may be configured not to support being set / applied for another purpose (or multiple purposes).

[0118] For example, one SR (e.g., a first SR) of two SRs each having a PUCCH resource for SR configured therein may be configured / applied in response to failure recovery of one or more logical channels / LBTs, and the other SR (e.g., a second SR) may be controlled so as not to be configured / applied in response to failure recovery of one or more logical channels / LBTs.

[0119] This makes it possible to suppress an increase in the overhead of SR setting by sharing some SRs for other purposes, even when the SRs for BFR are expanded.

[0120] When the configuration described in the first aspect is applied / implemented, a predetermined UE capability may be defined / configured / supported. The configuration described in the first aspect may be applied when the UE reports / supports the predetermined UE capability and / or when a predetermined upper layer parameter is configured by the base station. The predetermined UE capability may be a UE capability regarding whether or not to support SR sharing in different cases.

[0121] In this way, by applying the first aspect, SR transmission can be performed appropriately even when the SR setting for BFR is extended.

[0122] (Second Aspect) In the second aspect, an example of SR transmission control in a case where the SR for BFR is set / applied for another purpose (or multiple purposes) is supported. The second aspect may be applied, for example, to a case where the SR for BFR is set / applied for another purpose (or multiple purposes) in the first aspect.

[0123] When the SR for BFR is configured for another purpose (or multiple purposes) and the SR for BFR is applied / triggered for another purpose, at least one of the following options 2-1 to 2-4 may be applied. Here, it is assumed that multiple (e.g., two) PUCCH resources for SR are configured for the SR for BFR (or one PUCCH resource for SR having multiple (e.g., two) spatial relationships is configured for the SR for BFR), and the SR for BFR is configured in response to failure recovery of one or multiple logical channels / LBTs.

[0124] <Option 2-1> Among the multiple PUCCH resources for SR configured for BFR SR, a predetermined PUCCH resource for SR (e.g., one PUCCH resource for SR) may be selected / applied for transmission for another purpose (see FIG. 5A ). The predetermined PUCCH resource for SR may be selected / determined autonomously by the UE (UE implementation).

[0125] For example, as shown in FIG. 5A, when PUCCH resources #1 and #2 for SR are configured for SR for BFR, the UE may determine one PUCCH resource for SR (one of #1 and #2) to be used for another purpose.

[0126] Alternatively, when one PUCCH resource for SR with multiple spatial relationships is configured for SR for BFR, a predetermined spatial relationship (e.g., one spatial relationship) from the multiple spatial relationships may be selected / applied for transmission for another purpose (see FIG. 5B ). The predetermined spatial relationship may be autonomously selected / determined by the UE (UE implementation).

[0127] For example, as shown in FIG. 5B, when multiple spatial relationships #1 and #2 correspond to the SR PUCCH resource #1 configured for BFR SR, the UE may determine one spatial relationship (one of #1 and #2) to be applied for another purpose.

[0128] <Option 2-2> Among multiple PUCCH resources for SR configured for BFR SR, a default / fixed PUCCH resource for SR (e.g., one default / fixed PUCCH resource for SR) may be selected / applied for transmission for another purpose (see FIG. 6A ). The default / fixed PUCCH resource for SR may be defined in the specifications or configured / activated in the UE by higher layer signaling / MAC CE.

[0129] For example, as shown in FIG. 6A , when PUCCH resources #1 and #2 for SR are configured for SR for BFR and PUCCH resource #1 for SR is the default, the default PUCCH resource #1 for SR may be configured / applied for another purpose.

[0130] Alternatively, when one PUCCH resource for SR with multiple spatial relationships is configured for SR for BFR, a default / fixed spatial relationship (e.g., one default / fixed spatial relationship) among the multiple spatial relationships may be selected / applied for transmissions for other purposes (see FIG. 6B ). The default / fixed spatial relationship may be defined in a specification or configured / activated in the UE by higher layer signaling / MAC CE.

[0131] For example, as shown in Figure 6B, if spatial relationships #1 and #2 correspond to the SR PUCCH resources set in the BFR SR and spatial relationship #1 is the default, the default spatial relationship #1 may be set / applied for other purposes.

[0132] <Option 2-3> When there is an association between SR PUCCH resources and TRP information (e.g., TRP info) (see FIG. 7A), a predetermined SR PUCCH resource (e.g., one SR PUCCH resource) associated with the TRP information for each purpose may be selected / applied for transmission of the respective purpose (see FIG. 7B).

[0133] For example, assume a case where PUCCH resource #1 for SR is configured in association with TRP #1 and another purpose corresponds to (or is supported by) TRP #1 as shown in Figure 7A. When PUCCH resources #1 and #2 for SR are configured for SR for BFR as shown in Figure 7A, PUCCH resource #1 for SR associated with TRP #1 corresponding to another purpose may be configured / applied for the other purpose.

[0134] Alternatively, if there is an association between spatial relationships corresponding to PUCCH resources for SR and TRP information (e.g., TRP info), a predetermined spatial relationship (e.g., one spatial relationship) associated with the TRP information for each purpose may be selected / applied to the transmission for that purpose.

[0135] The association between the PUCCH resource for SR and the TRP information (or the association between the spatial relationship of the PUCCH resource for SR and the TRP information) may be configured in the UE using higher layer signaling / MAC CE, etc.

[0136] The TRP information for each purpose may be information about the TRP corresponding to each purpose. For example, the TRP information for each purpose may be set when there is an association between the TRP and a logical channel, or when there is an association between the TRP and LBT detection / recovery (when there is panel-specific LBT detection / recovery for each UL TRP). The association between the TRP and a logical channel, or the association between the TRP and LBT detection / recovery may be configured in the UE using higher layer signaling, MAC CE, etc.

[0137] <Option 2-4> Multiple PUCCH resources for SR configured for SR for BFR may be selected / applied for transmission for another purpose.

[0138] Alternatively, when one PUCCH resource for SR having multiple spatial relationships is configured for SR for BFR, the multiple spatial relationships may be selected / applied to transmissions for other purposes.

[0139] When the configuration shown in Option 2-4 (or Option 2-1 to Option 2-3) is applied / introduced, a predetermined UE capability may be defined / configured / supported. The configuration shown in Option 2-4 (or Option 2-1 to Option 2-3) may be applied in at least one of the cases where the UE reports / supports a predetermined UE capability and where a predetermined upper layer parameter is configured by the base station.

[0140] The predetermined UE capability may be a UE capability regarding whether application of multiple PUCCH resources for SR (or multiple spatial relationships corresponding to PUCCH resources for SR) for other purposes is supported.

[0141] In this way, by applying the second aspect, it is possible to appropriately control the transmission of SR / PUCCH resources for SR (or SR sharing) even when the extended SR for BFR is configured / applied for another purpose.

[0142] (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.

[0143] 8 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).

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

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

[0146] 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))).

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

[0148] 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).

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

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

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

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

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

[0154] 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).

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

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

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

[0158] 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).

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

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

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

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

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

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

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

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

[0167] 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).

[0168] (Base Station) Fig. 9 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0185] The transceiver 120 may transmit information regarding the setting of a scheduling request (SR) for beam obstruction detection to the terminal.

[0186] The control unit 110 may control the setting of an SR for multiple purposes when multiple SRs are set, when multiple uplink control channel resources are set for an SR, or when multiple spatial relationships correspond to the uplink control channel resources set for an SR.

[0187] (User Terminal) Fig. 10 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0203] Note that 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.

[0204] The transceiver 220 may receive information regarding the setting of a scheduling request (SR) for beam failure detection.

[0205] The control unit 210 may control the SR to be applied to multiple purposes when multiple SRs are set, when multiple uplink control channel resources are set for the SR, or when multiple spatial relationships correspond to the uplink control channel resources set for the SR.

[0206] The control unit 210 may control some of the multiple uplink control channel resources set for the SR, or some of the multiple spatial relationships corresponding to the uplink control channel resources set for the SR, to be applied to multiple purposes.

[0207] Some of the multiple uplink control channel resources applied to multiple purposes or some of the multiple spatial relationships may be predefined or configured.

[0208] A portion of the multiple uplink control channel resources applied for multiple purposes or a portion of the multiple spatial relationships may be associated with a specific transmission / reception point.

[0209] (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.

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

[0211] For example, a base station, a user terminal, etc. 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. 11 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, etc.

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

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

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

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

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

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

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

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

[0220] 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).

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

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

[0223] (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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0241] 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."

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

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

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

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

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

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

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

[0249] 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)).

[0250] 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).

[0251] 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).

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

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

[0254] 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).

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

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

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

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

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

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

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

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

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

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

[0265] 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).

[0266] 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."

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

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

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

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

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

[0272] 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."

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

[0274] 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."

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

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

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

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

Claims

1. A receiver for receiving information for configuring a plurality of physical uplink control channel (PUCCH) resources in response to a scheduling request (SR) for beam fault detection (BFD) specific to a transmission / reception point (TRP); A terminal having a control unit that controls, when the TRP-specific BFD SR is triggered for another purpose, to apply one PUCCH resource among the multiple PUCCH resources to the other purpose.

2. Receiving information for configuring a plurality of physical uplink control channel (PUCCH) resources in response to a scheduling request (SR) for beam fault detection (BFD) specific to a transmission / reception point (TRP); When the TRP-specific BFD SR is triggered for another purpose, controlling one of the plurality of PUCCH resources to be applied to the other purpose.

3. A transmitter that transmits information to a terminal to set multiple physical uplink control channel (PUCCH) resources in response to a scheduling request (SR) for beam fault detection (BFD) specific to a transmission / reception point (TRP); A base station having a control unit that determines that one PUCCH resource among the plurality of PUCCH resources is applied to the other purpose when the TRP-specific BFD SR is triggered for the other purpose.

4. A system having a terminal and a base station, The terminal A receiver for receiving information for configuring a plurality of physical uplink control channel (PUCCH) resources in response to a scheduling request (SR) for beam failure detection (BFD) specific to a transmission / reception point (TRP); A control unit that controls one PUCCH resource among the plurality of PUCCH resources to be used for another purpose when the TRP-specific BFD SR is triggered for the other purpose; The base station A system comprising a transmitter that transmits information for configuring the plurality of PUCCH resources.