Terminal, radio communication method, and base station

WO2026204885A1PCT designated stage Publication Date: 2026-10-01NTT DOCOMO INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
PCT/JP2026/011371
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2025-03-27
Filing Date
2026-03-23
Publication Date
2026-10-01

Smart Images

  • Figure JP2026011371_01102026_PF_FP_ABST
    Figure JP2026011371_01102026_PF_FP_ABST
Patent Text Reader

Abstract

A terminal according to one aspect of the present disclosure has: a receiver unit that receives information relating to a transmission condition for a scheduling request and information indicating a unified transmission configuration indication (TCI) state; and a control unit that, in the case of updating the TCI state to be applied to the uplink on the basis of the information indicating the unified TCI state, controls the transmission of the scheduling request on the basis of the information relating to the transmission condition and also of a time domain offset.
Need to check novelty before this filing date? Find Prior Art

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] In a Universal Mobile Telecommunications System (UMTS) network, Long Term Evolution (LTE) was specified for the purposes of higher data rates, lower latency and the like (Non-Patent Document 1). Furthermore, LTE-Advanced (3GPP Rel. 10-14) was specified for the purposes of further increasing capacity and advancing functionality of LTE (Third Generation Partnership Project (3GPP (registered trademark)) Release (Rel.) 8, 9).

[0003] Successor systems to LTE (also referred to as, for example, 5th generation mobile communication system (5G), 5G+ (plus), 6th generation mobile communication system (6G), New Radio (NR), 3GPP Rel. 15 and later) are also under study.

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

[0005] In future wireless communication systems (e.g., NR), it is under study that a user terminal (terminal, user terminal, User Equipment (UE)) controls transmission and reception processing based on information related to Quasi-Co-Location (QCL) (QCL assumption / Transmission Configuration Indication (TCI) state / spatial relation).

[0006] Furthermore, in Rel. 17 and later, a TCI state (unified TCI state) applicable to multiple types of signals (channel / reference signal) will be used. It is also envisioned that this unified TCI state will be dynamically updated for each UE.

[0007] However, there are cases where the consideration of supporting dynamic updates of beam / TCI states is unclear. If this consideration is insufficient, communication may not be performed properly, and communication quality may deteriorate.

[0008] Therefore, one of the objectives of this disclosure is to provide a terminal, a wireless communication method, and a base station that can suppress the deterioration of communication quality even when the beam / TCI state is updated.

[0009] A terminal according to one aspect of the present disclosure includes a receiving unit that receives information regarding the transmission conditions for a scheduling request and information indicating a Unified Transmission Configuration Indication (TCI) state, and a control unit that, when updating the TCI state to be applied to the uplink based on the information indicating the Unified TCI state, controls the transmission of the scheduling request based on the information regarding the transmission conditions and a time-domain offset.

[0010] According to one aspect of this disclosure, it is possible to suppress the deterioration of communication quality even when the beam / TCI state is updated.

[0011] Figures 1A and 1B show an example of a unified / common TCI framework. Figures 2A and 2B show an example of DCI-based TCI state indication. Figure 3 shows an example where multiple UEs have SR transmission opportunities set up for the same set of OFDM symbols. Figure 4 shows an example where the TCI state of some UEs is updated when multiple UEs have SR transmission opportunities set up for the same set of OFDM symbols. Figure 5 shows an example of SR transmission control according to the first embodiment. Figure 6 shows another example of SR transmission control according to the first embodiment. Figure 7 shows an example of RRC parameters related to time-domain offset according to the second embodiment. Figure 8 shows another example of RRC parameters related to time-domain offset according to the second embodiment. Figure 9 shows an example of a schematic configuration of a wireless communication system according to one embodiment. Figure 10 shows an example of a base station configuration according to one embodiment. Figure 11 shows an example of a user terminal configuration according to one embodiment. Figure 12 shows an example of the hardware configuration of a base station and user terminal according to one embodiment. Figure 13 shows an example of a vehicle according to one embodiment.

[0012] (Scheduling Request (SR)) A scheduling request (SR) is used by a UE to request resources for UL data (e.g., UL-SCH (Uplink Shared Channel)). For example, a UE will trigger / send an SR if it has UL data to send but does not have a UL grant (allocation of UL resources).

[0013] SR may be triggered by a predetermined event. Examples of predetermined events include, but are not limited to, BSR (Buffer Status Report), SCell Beam Failure Recovery, UE-led Beam Report (LTM), or LBT (Listen Before Talk).

[0014] When an SR is triggered, the UE controls the transmission of the SR using a predetermined UL channel (e.g., PUCCH). The SR may be transmitted using the PUCCH resource (which may also be called the SR resource). The SR resource may be a predetermined time / frequency resource allocated on the PUCCH for use in transmitting the SR.

[0015] The transmission conditions / parameters for SR (for example, parameters of the SR resource used for SR transmission, such as period) may be set by the base station to the UE using RRC parameters. The base station may also set for each UE, using RRC parameters, which PUCCH resource to use to transmit SR.

[0016] (TCI, Spatial Relations, QCL) In NR, it is being considered to control the receive processing (e.g., at least one of receive, demapping, demodulation, and decoding) and transmit processing (e.g., transmit, mapping, precoding, modulation, and encoding) of at least one of the signal and channel (referred to as signal / channel) in the UE based on the Transmission Configuration Indication state (TCI state).

[0017] TCI status refers to information about signal / channel quasi-co-location (QCL), and may also be called spatial reception parameters or spatial relation information. TCI status may be set in the UE for each channel or signal.

[0018] QCL is an index that indicates the statistical properties of a signal / channel. For example, if one signal / channel and another signal / channel have a QCL relationship, it may mean that we can assume that at least one of the following is identical between these different signals / channels: Doppler shift, Doppler spread, average delay, delay spread, and spatial parameter (e.g., spatial Rx parameter).

[0019] The spatial reception parameters may correspond to the received beam of the UE (e.g., the received analog beam), or the beam may be identified based on the spatial QCL. In this disclosure, QCL (or at least one element of QCL) may be interpreted as sQCL (spatial QCL).

[0020] Multiple types of QCLs (QCL types) may be defined. For example, four QCL types A-D may be provided, each with different parameters (or parameter sets) that can be assumed to be identical.

[0021] The assumption by a User Engineer (UE) that one control resource set (CORESET), channel, or reference signal is in a specific QCL (e.g., QCL type D) relationship with another CORESET, channel, or reference signal may be called a QCL assumption.

[0022] The UE may determine at least one of the transmit beam (Tx beam) and receive beam (Rx beam) of a signal / channel based on the TCI status or QCL assumption of the signal / channel.

[0023] The TCI state may, for example, be information regarding the QCL between the channel in question (in other words, the reference signal (RS) for that channel) and another signal (e.g., another RS). The TCI state may be set (indicated) by upper-layer signaling, physical layer signaling, or a combination thereof.

[0024] Physical layer signaling may include, for example, Downlink Control Information (DCI).

[0025] The channel on which the TCI state or spatial relationship is set (specified) may be, for example, at least one of the following: Physical Downlink Shared Channel (PDSCH), Physical Downlink Control Channel (PDCCH), Physical Uplink Shared Channel (PUSCH), or Physical Uplink Control Channel (PUCCH).

[0026] Furthermore, the RS that has a QCL relationship with the channel may be at least one of the following: a Synchronization Signal Block (SSB), a Channel State Information Reference Signal (CSI-RS), a Sounding Reference Signal (SRS), a Tracking CSI-RS (also called a Tracking Reference Signal (TRS)), or a QCL detection reference signal (also called a QRS).

[0027] An SSB is a signal block that includes at least one of a Primary Synchronization Signal (PSS), a Secondary Synchronization Signal (SSS), and a Physical Broadcast Channel (PBCH). An SSB may also be called an SS / PBCH block.

[0028] The RS of a QCL type X in a TCI state may also mean the RS in the relationship between a channel / signal (and its DMRS) and a QCL type X, and this RS may be called the QCL source of the QCL type X in that TCI state.

[0029] (Unified / Common TCI Framework) According to the Unified TCI Framework, multiple types of channels / RS (UL / DL) can be controlled by a common framework. The Unified TCI Framework does not define TCI states or spatial relationships for each channel, as in Rel. 15, but may specify a common beam (common TCI state) and apply it to all UL and DL channels, or a common beam for UL may be applied to all UL channels, and a common beam for DL ​​may be applied to all DL channels.

[0030] UE may assume the same TCI state (joint TCI state, joint TCI pool, joint common TCI pool, joint TCI state set) for UL and DL. Alternatively, UE may assume different TCI states for UL and DL respectively (separate TCI state, separate TCI pool, UL separate TCI pool and DL separate TCI pool, separate common TCI pool, UL common TCI pool and DL common TCI pool).

[0031] The default beams for UL and DL may be aligned by beam management based on MAC CE (MAC CE level beam instruction). Alternatively, the default TCI status of PDSCH may be updated to match the default UL beam (spatial relationship).

[0032] DCI-based beam management (DCI level beam indication) may indicate a common beam / unified TCI state from the same TCI pool (joint common TCI pool, joint TCI pool, set) for both UL and DL. X (>1) TCI states may be activated by MAC CE. UL / DL DCI may select one from the X active TCI states. The selected TCI state may be applied to both UL and DL channels / RS.

[0033] A TCI pool (set) may be a set of multiple TCI states configured by the RRC parameter, or it may be a set of multiple TCI states (active TCI states, active TCI pool, set) activated by MAC CE from among the multiple TCI states configured by the RRC parameter. Each TCI state may be a QCL type A / D RS. SSB, CSI-RS, or SRS may be set as the QCL type A / D RS.

[0034] In the example in Figure 1A, the RRC parameter (information element) sets up multiple TCI states for both DL and UL. MAC CE may activate multiple TCI states from the set up TCI states. DCI may indicate one of the activated TCI states. DCI may be a UL / DL DCI. The indicated TCI state may be applied to at least one (or all) of the UL / DL channels / RS. One DCI may indicate both UL TCI and DL TCI.

[0035] In the example shown in this figure, one point may represent a single TCI state that applies to both UL and DL, or it may represent two TCI states that apply to UL and DL respectively.

[0036] At least one of the multiple TCI states set by the RRC parameters and the multiple TCI states activated by MAC CE may be called a TCI pool (common TCI pool, joint TCI pool, TCI state pool). The multiple TCI states activated by MAC CE may be called an active TCI pool (active common TCI pool).

[0037] In this disclosure, the higher-layer parameters (RRC parameters) that set up multiple TCI states may also be referred to as setting information that sets up multiple TCI states, or simply as "setting information." Furthermore, in this disclosure, being instructed to select one of multiple TCI states using DCI may mean receiving instruction information that instructs one of the multiple TCI states included in DCI, or simply receiving "instruction information."

[0038] In the example in Figure 1B, the RRC parameter sets up multiple TCI states (joint common TCI pool) for both DL and UL. MAC CE may activate multiple TCI states (active TCI pool) from the set up multiple TCI states. Separate active TCI pools for UL and DL may be set up / activated.

[0039] A DL DCI, or a new DCI format, may select (instruct) one or more (e.g., one) TCI states. The selected TCI state may be applied to one or more (or all) DL channels / RSs. DL channels may be PDCCH / PDSCH / CSI-RS. The UE may determine the TCI state of each DL channel / RS using the TCI state behavior (TCI framework) of Rel. 16. A UL DCI, or a new DCI format, may select (instruct) one or more (e.g., one) TCI states. The selected TCI state may be applied to one or more (or all) UL channels / RSs. UL channels may be PUSCH / SRS / PUCCH. Thus, different DCIs may instruct UL TCI and DL DCI separately.

[0040] (TCI State Indication) The Rel. 17 Unified TCI Framework supports the following modes 1 to 3: <Mode 1> MAC CE based TCI state indication <Mode 2> DCI based TCI state indication by DCI format 1_1 / 1_2 with DL assignment <Mode 3> DCI based TCI state indication by DCI format 1_1 / 1_2 without DL assignment

[0041] A UE with a TCI state set and activated with a Rel. 17 TCI state ID (e.g., tci-StateId_r17) receives a DCI format 1_1 / 1_2 that provides an indicated TCI state with the Rel. 17 TCI state ID for one CC, or receives a DCI format 1_1 / 1_2 that provides an indicated TCI state with the Rel. 17 TCI state ID for all CCs in the same CC list as the CC list set by simultaneous TCI update list 1 or simultaneous TCI update list 2 (e.g., simultaneousTCI-UpdateList1 or simultaneousTCI-UpdateList2). The DCI format 1_1 / 1_2 may or may not include a DL assignment if one is available.

[0042] If DCI format 1_1 / 1_2 does not carry a DL assignment, the UE can assume (verify) the following for the DCI: - CS-RNTI is used to scramble the CRC for DCI. - The values of the following DCI fields (special fields) are set as follows: - The redundancy version (RV) field is all '1's. - The modulation and coding scheme (MCS) field is all '1's. - The new data indicator (NDI) field is 0. - The frequency domain resource assignment (FDRA) field is all '0's for FDRA type 0, or all '1's for FDRA type 1, or all '0's for DynamicSwitch (same as the validation of PDCCH for DL semi-persistent scheduling (SPS) or release of UL grant type 2 scheduling).

[0043] It should be noted that the DCI in the above mode 2 / mode 3 may also be referred to as beam indication DCI.

[0044] In Rel. 15 / 16, if the UE does not support active BWP switching via DCI, the UE ignores the BWP indicator field. A similar operation is also under consideration for the relationship between the support of Rel. 17 TCI states and the interpretation of TCI fields. It is under consideration that if the UE is configured with Rel. 17 TCI states, a TCI field always exists in DCI format 1_1 / 1_2, and if the UE does not support TCI updating via DCI, the UE ignores the TCI field.

[0045] In Rel. 15 / 16, whether a TCI field exists (TCI presence information in DCI, tci-PresentInDCI) is configured per CORESET.

[0046] In DCI format 1_1, the TCI field is 0 bits if the upper layer parameter tci-PresentInDCI is not enabled, and 3 bits otherwise. If the BWP indicator field indicates a BWP other than the active BWP, the UE follows the following behavior: <Behavior> If the upper layer parameter tci-PresentInDCI is not enabled for the CORESET used in the PDCCH that transmits that DCI format 1_1, the UE assumes that tci-PresentInDCI is not enabled for all CORESETs within the indicated BWP; otherwise, the UE assumes that tci-PresentInDCI is enabled for all CORESETs within the indicated BWP.

[0047] In DCI format 1_2, the TCI field is 0 bits if the upper layer parameter tci-PresentInDCI-1-2 is not set, and otherwise is 1, 2, or 3 bits determined by the upper layer parameter tci-PresentInDCI-1-2. If the BWP indicator field indicates a BWP other than the active BWP, the UE follows the following behavior: <Operation> If the higher-layer parameter tci-PresentInDCI-1-2 is not set for the CORESET used in the PDCCH that transmits the DCI format 1_2, the UE assumes that tci-PresentInDCI is not enabled for all CORESETs in the specified BWP. Otherwise, the UE assumes that tci-PresentInDCI-1-2 is set for all CORESETs in the specified BWP with the same value as tci-PresentInDCI-1-2 set for the CORESET used in the PDCCH that transmits the DCI format 1_2.

[0048] Figure 2A shows an example of a DCI-based joint DL / UL TCI status indication. A TCI status ID indicating the joint DL / UL TCI status is associated with the value of the TCI field used for joint DL / UL TCI status indication.

[0049] Figure 2B shows an example of a DCI-based separate DL / UL TCI state indication. For a value of the TCI field for separate DL / UL TCI state indication, at least one TCI state ID is associated with: a TCI state ID indicating a DL-only TCI state, and a TCI state ID indicating a UL-only TCI state. In this example, values 000 to 001 of the TCI field are associated with only one TCI state ID for DL, values 010 to 011 of the TCI field are associated with only one TCI state ID for UL, and values 100 to 111 of the TCI field are associated with both one TCI state ID for DL and one TCI state ID for UL.

[0050] (Channel / RS to which the indicated TCI state applies) A TCI state indicated by MAC CE / DCI ("indicated TCI state") may be applied to the following channels / RS.

[0051] <PDCCH> ・For CORESET0, when followUnifiedTCIState (compliance with a unified TCI state) is configured, the indicated TCI state is applied. Otherwise, the Rel. 15 specification applies to the CORESET. That is, CORESET0 follows the TCI state activated by the MAC CE, or is QCLed with an SSB. ・For CORESETs other than index 0 that are associated with USS / CSS type 3, the indicated TCI state is always applied. ・For at least CORESETs other than index 0 that are associated with CSS other than CSS type 3, when compliance with a unified TCI state is configured, the indicated TCI state is applied. Otherwise, the configured TCI state ("configured TCI state") for the CORESET is applied to the CORESET.

[0052] <PDSCH> - The directive TCI state is always applied to all UE-dedicated PDSCHs. - For non-UE-dedicated PDSCHs (PDSCHs scheduled by DCI in CSS), the directive TCI state may be applied if followUnifiedTCIState is set (for the CORESET of the PDCCH that schedules the PDSCH). Otherwise, the set TCI state for that PDSCH is applied to that PDSCH. If followUnifiedTCIState is not set for a PDSCH, whether a non-UE-dedicated PDSCH follows the directive TCI state may be determined by whether followUnifiedTCIState is set for the CORESET used to schedule that PDSCH.

[0053] <CSI-RS> - For A-CSI-RS for CSI acquisition or beam management, if followUnifiedTCIState is set (for the PDCCH CORESET that triggers that A-CSI-RS), the indicated TCI state is applied. For other CSI-RS, the configured TCI state for that CSI-RS is applied.

[0054] <PUCCH> - The instructed TCI state is always applied to all dedicated PUCCH resources.

[0055] <PUCH> - For dynamic / configured grant pushes, the instructed TCI state is always applied.

[0056] <SRS> For A-SRS used for beam management and A / SP / P-SRS used for codebook (CB) / non-codebook (NCB) / antenna switching, the indicative TCI state is applied when the SRS resource set is configured to follow a unified TCI state. For other SRSs, the configured TCI state within that SRS resource set is applied.

[0057] (Analysis) Scheduling requests (SRs) or SR resources (hereinafter simply referred to as SRs) are code-divisibility multiplexed (CDM) between UEs. For example, multiple SRs between UEs are CDM multiplexed on the same resource (e.g., PRB). In this case, the same SR transmission occasion may be set for each of the multiple UEs.

[0058] The network (or base station) sets up periodic transmission opportunities for SRs (e.g., every 40 milliseconds) to reduce the delay when a UE requests resources for UL data (e.g., UL-SCH / PUSCH). When an SR is triggered, the UE controls the transmission of the SR using the set transmission opportunities (e.g., SR resource / PUCCH resource).

[0059] In analog / hybrid beamforming architectures (e.g., U6G (unlicensed 6G) ​​in the first frequency range (FR1) or the second frequency range (FR2)), the network can only receive one beam at a time, which is a common assumption for UL transmission. In such situations, it is desirable for the network to group pre-configured periodic SR resources from different UEs into the same UL transmission opportunity (e.g., the same set of OFDM symbols) with UEs that have the same UL TCI state / Rx received beam. This allows the network to simultaneously and appropriately receive SR from multiple UEs based on a single received beam / TCI state.

[0060] In analog / hybrid beamforming architectures, it is conceivable that multiple SR transmission opportunities from different UEs within the same set of OFDM symbols can be aligned to the same base station received beam / TCI state (see Figure 3).

[0061] Figure 3 shows the case where the SR transmission opportunities for UE#1 to UE#3 are set to the same OFDM symbol set, the SR transmission opportunities for UE#4 to UE#5 are set to the same OFDM symbol set, and the SR transmission opportunities for UE#(n-1) to UE#n are set to the same OFDM symbol set. The base station receives the SR (or PUCCH) transmitted from UE#1 to UE#3 using UL receive beam 1, the SR (or PUCCH) transmitted from UE#4 to UE#5 using UL receive beam 2, and the SR (or PUCCH) transmitted from UE#(n-1) to UE#n using UL receive beam K.

[0062] In an SR transmission (or SR transmission opportunity) consisting of multiple UEs (or a list of UEs), if the beam direction of one SR resource (e.g., the UL receive beam of a network) is changed, the beams will become misaligned.

[0063] In current wireless communication systems, the only way to readjust / realign SR resources is to reset the SR resources to the UE via the RRC. However, the readjustment procedure via the RRC is slow, and the overhead of resetting the RRC increases, making it difficult to cope with frequent beam changes.

[0064] Incidentally, when a unified TCI state (or instructional TCI state) is set / applied, the transmit beam / TCI state of the SR (or PUCCH used for SR transmission) is updated / modified individually for each UE by MAC CE / DCI.

[0065] If the transmit beam / TCI state of an SR is updated individually for each UE, it is conceivable that multiple UEs may use the same resource (e.g., PRB) to transmit SR (or PUCCH) with different transmit beam / TCI states. In this case, the base station may not be able to receive the PRB corresponding to the SR (or PUCCH) based on one of the receive beam / TCI states during a given transmission opportunity.

[0066] Figure 4 shows an example where the transmit beam / TCI state is updated separately for each UE. In Figure 4, initially, SR resources from different UEs are received by the base station on the same set of OFDM symbols with the same UL receive beam (or base station beam) due to network scheduling. In other words, the same transmit timing (or SR transmit opportunity) is set for one or more UEs to which the same beam / TCI state is applied to the SR, and CDM multiplexing occurs.

[0067] In this case, it is conceivable that the TCI status of only some UEs (e.g., UE#1) may be updated due to the movement of UEs (e.g., updated from received beam 1 to received beam 2). In this case, the base station may not be able to simultaneously receive all SRs (in this case, the SRs of UE#1 to UE#3) based on a single received beam.

[0068] For example, if SR transmission is configured by a UE list (e.g., a list of UEs set to the same OFDM symbol set), if the beam direction of one SR resource in that UE list (e.g., the UL receive beam of the network) is changed, the network receive beams to the UE will no longer be aligned. Such beam misalignment can cause SR link failures and degrade communication quality.

[0069] Therefore, the inventors investigated a method for properly performing UL transmission (e.g., SR / PUCCH) even when the beam / TCI state for UL transmission is updated for each UE, and conceived this embodiment.

[0070] The embodiments of this disclosure will be described in detail below with reference to the drawings. Each wireless communication method according to the embodiments may be applied individually or in combination.

[0071] In the following embodiment, the transmission of SR is used as an example, but the channels / signals to which this embodiment can be applied are not limited to this, and it may also be applied to other channels / signals (e.g., HARQ-ACK (or ACK / NACK), PUCCH, PUSCH, SRS). In this disclosure, SR, SR resource, SR transmission opportunity, PUCCH, PUCCH resource, and PUCCH transmission opportunity may be read interchangeably.

[0072] (Various substitutions) In this disclosure, words enclosed in parentheses () may indicate an explanation of the preceding word (e.g., an explanation of spelling), a paraphrase, a specific example, or supplementary explanation. Also, in this disclosure, words enclosed in square brackets ([]) may be interpreted as part of the overall meaning of the text, or they may be interpreted as being excluded (ignored). Note that parentheses () and square brackets ([]) may be used for purposes / meanings other than those described above.

[0073] In this disclosure, "A / B" and "at least one of A and B" may be interpreted as mutually exclusive. In this disclosure, "A / B / C" may mean "at least one of A, B, and C".

[0074] In this disclosure, terms such as notice, activate, deactivate, indicate (or specify), select, configure, update, and determine may be interpreted interchangeably. In this disclosure, terms such as support, control, controllable, operate, and capable of operating may be interpreted interchangeably.

[0075] In this disclosure, Radio Resource Control (RRC), RRC parameters, RRC messages, higher-layer parameters, fields, Information Elements (IE), settings, etc., may be interpreted interchangeably. In this disclosure, Medium Access Control elements (MAC Control Elements (CE)), update commands, activation / deactivation commands, etc., may be interpreted interchangeably.

[0076] In this disclosure, the upper layer signaling may be any or a combination thereof, such as Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information, and other messages (e.g., messages from the core network, such as positioning protocol messages (e.g., NR Positioning Protocol A (NRPPPa) / LTE Positioning Protocol (LPP)) messages).

[0077] In this disclosure, MAC signaling may include, for example, MAC Control Elements (MAC CEs) and MAC Protocol Data Units (PDUs). Broadcast information may include, for example, Master Information Blocks (MIBs), System Information Blocks (SIBs), Remaining Minimum System Information (RMSIs), and Other System Information (OSIs).

[0078] In this disclosure, physical layer signaling may include, for example, Downlink Control Information (DCI) and Uplink Control Information (UCI).

[0079] In this disclosure, terms such as drop, suspend, cancel, puncture, rate match, postpone, and not send may be interpreted interchangeably.

[0080] (Wireless Communication Method) <First Embodiment> The first embodiment relates to an example of a method for controlling SR transmission (e.g., transmission conditions / parameters) based on TCI status instruction / update.

[0081] The UE may receive information regarding the transmission conditions of an SR via higher-layer parameters. This information may include, for example, information regarding the period, transmission opportunities, and UL resources (e.g., SR resources and PUCCH resources). When an SR is triggered, the UE controls the transmission of the SR based on the information regarding its transmission conditions.

[0082] The transmission opportunities for UL resources reserved or configured for SR (e.g., SR resources / PUCCH resources) may be changed / updated in conjunction with the indication / update of the TCI status. For example, when a TCI status is indicated or when the TCI status is updated based on the indicated TCI status, the UE may control the system to change / update the transmission opportunities corresponding to SR based on predetermined conditions (e.g., predetermined offset) at the same time as the TCI status update. The indication of the TCI status may be given to the UE from the network (or base station) via MAC CE / DCI.

[0083] By supporting changes / updates to the transmission opportunities of SR resources / PUCCH resources in conjunction with TCI state updates (for example, simultaneously with TCI state updates), it is possible to balance dynamic updates of beam / TCI states with network resource overhead.

[0084] The predetermined condition (e.g., predetermined offset) may be a time-domain offset. For example, a unified TCI state (e.g., joint / UL TCI state) may be associated with a time-domain offset. In this disclosure, a time-domain offset may be defined at the slot level (or per slot), the system frame number level, the millisecond level, or any combination thereof.

[0085] The time-domain offset (e.g., slot-level offset) may be set by a new RRC parameter (e.g., slotOffset). For example, the time-domain offset may be set by an RRC parameter within a predetermined range (e.g., 0 to 639). In this case, it may be set / supported by a mechanism similar to that of existing RRC parameters for pre-set period and offset (e.g., periodicityAndOffset).

[0086] If a TCI state is instructed / provided for a PUCCH resource used for SR transmission, a time-domain offset associated with that TCI state may be applied. The application time of the time-domain offset may be the same as the application time of the TCI state. For example, when a TCI state is instructed / provided, the UE may control the application of the time-domain offset based on the application time of that TCI state.

[0087] In a unified TCI framework (for example, where unified TCI states are supported or configured), a single joint / UL TCI state (or each joint / UL TCI state) may be associated with a time-domain offset. When a TCI state is indicated / updated, the UE may control the transmission of an SR based on pre-configured information regarding the SR transmission conditions (e.g., period / transmission opportunity / UL resource (e.g., SR resource / PUCCH resource)) and the time-domain offset corresponding to the indicated TCI state.

[0088] Figure 5 shows an example of how SR transmission opportunities are changed in accordance with beam / TCI state updates. In Figure 5, a different TCI state (for example, a second TCI state) is instructed for UE#1, which has a first TCI state / SR transmission opportunity set, and the TCI state used for SR transmission is updated.

[0089] Before a second TCI state is indicated, UE#1 transmits an SR based on the first TCI state / SR transmission opportunity. After a second TCI state is indicated, UE#1 may control the transmission of an SR by utilizing an SR transmission opportunity determined / derived based on the time-domain offset associated with the second TCI state.

[0090] This allows for adjustment of the timing of SR transmission (e.g., SR transmission opportunities) by adding a time-domain offset to the SR transmission timing, which is determined based on the settings of SR resources in the existing system (e.g., period).

[0091] Figure 5 shows a case where the time-domain offset is set to change / shift (or CDM multiplex with the SR of other UEs #4 and #5) to the same transmission opportunity or resource as the transmission opportunity of other UEs to which the updated second TCI state #2 applies. In this way, by setting the time-domain offset to be the same SR transmission opportunity or resource as the SR transmission opportunities of other UEs #4 and #5 to which the same TCI state #2 applies, resources can be used effectively.

[0092] However, the setting of the time domain offset is not limited to this. It may be supported to set the time domain offset so that it changes / shifts to a different transmission opportunity or resource than the transmission opportunities of other UEs #4 and #5 to which the updated second TCI state #2 applies (see Figure 6). This makes it possible to adjust the changed SR transmission opportunity of UE #1 to which the TCI state is updated more flexibly, and to suppress the transmission delay of SR for UE #1.

[0093] Thus, when a unified TCI state (e.g., a joint / UL TCI state) is specified / provided to a PUCCH resource used for SR transmission, a time-domain offset associated with that TCI state may be applied to derive an opportunity to transmit an SR. When a unified TCI state (e.g., a joint / UL TCI state) is specified / provided, the UE may control the transmission of an SR using the updated TCI state (e.g., determine an opportunity to transmit an SR) based on the time-domain offset associated with that TCI state.

[0094] This allows for flexible modification of the SR transmission timing (or transmission opportunity) in accordance with TCI state updates. By changing the transmission opportunity of SRs for which the TCI state is updated, the base station can appropriately receive one or more SRs using a single receive beam within the same set of OFDM symbols. Furthermore, it reduces the need to reconfigure the RRC to respond to changes in beam / TCI state (e.g., by changing SR resources / SR transmission opportunities), thereby suppressing the increase in network overhead.

[0095] When a PUCCH resource is applied to the transmission of an SR, a time offset or time-domain offset may be provided in the TCI state (e.g., TCI-State or TCI-UL-State) corresponding to the PUCCH resource associated with the SR setting. In this case, the transmission opportunity for transmitting the SR (SR transmission opportunity / PUCCH transmission opportunity) may be updated according to the time offset corresponding to the TCI state.

[0096] <Second Embodiment> The second embodiment relates to another example of a method for controlling SR transmission (e.g., transmission conditions / parameters) based on TCI status instruction / update.

[0097] Control over the transmission opportunities of SR resources / PUCCH resources (e.g., application of a time-domain offset) in conjunction with (e.g., simultaneously with) the update of the TCI state may be implemented only under specific conditions. These specific conditions may include the setting of specific RRC parameters, the setting / application of a unified TCI state, or the setting of a time-domain offset.

[0098] An RRC parameter relating to the time-domain offset may be added to the RRC parameters / information elements relating to the TCI state (e.g., TCI-State or TCI-UL-State).

[0099] For example, as shown in Figure 7, a TCI-State may contain either or both a time-domain slot offset (e.g., Time domain slot offset={1,2,3,4}) and a time-domain symbol offset (e.g., Time domain symbol offset={1,2,3,4,5,6,7,8,9,10,11,12,13}). Figure 7 shows a case where both a time-domain slot offset and a time-domain symbol offset are included, but only one of them may be set. Also, the values ​​of the time-domain slot offset and time-domain symbol offset are examples only and are not limited to these. Furthermore, the positions where the time-domain slot offset and time-domain symbol offset are added to the RRC parameter related to the TCI state (in this case, TCI-State) are examples only and are not limited to these.

[0100] As shown in Figure 8, either or both of the following may be set in TCI-UL-State: a time-domain slot offset (e.g., Time domain slot offset={1,2,3,4}) and a time-domain symbol offset (e.g., Time domain symbol offset={1,2,3,4,5,6,7,8,9,10,11,12,13}). Figure 8 shows the case where both the time-domain slot offset and the time-domain symbol offset are included, but only one of them may be set. Also, the values ​​of the time-domain slot offset and time-domain symbol offset are examples only and are not limited to these. Furthermore, the positions where the time-domain slot offset and time-domain symbol offset are added in the RRC parameter related to the TCI state (in this case, TCI-UL-State) are examples only and are not limited to these.

[0101] The setting of RRC parameters related to time-domain offsets may be limited to cases where a unified TCI state is set / applied, or it may be set regardless of whether a unified TCI state is set / applied or not.

[0102] <<Case 2-1>> A case may be supported in which a time-domain offset is set for the indicated TCI state applied to the SR resource (or PUCCH resource). In this case, the time-domain offset may be applied to the slot / symbol determined / derived by the period, etc., set as the SR resource (or PUCCH resource).

[0103] For example, an SR may be transmitted with a slot / symbol index determined / derived by adding or subtracting the slot / symbol index set by the time domain offset to the slot / symbol index determined / derived by the period set as the SR resource. The slot / symbol index determined by the period set as the SR resource may be determined in the same way as in existing systems. Whether to add or subtract the slot / symbol index set by the time domain offset may be defined in the specification or set by RRC, etc.

[0104] <<Case 2-2>> A case may be supported in which no time-domain offset is set for the indicated TCI state applied to the SR resource (or PUCCH resource). In this case, at least one of the following options 2-1 and 2-2 may be applied.

[0105] 《Option 2-1》 The SR may be transmitted with a slot / symbol index determined / derived by adding or subtracting the slot / symbol index of a time-domain offset (for example, time-domain offset = 0) to the slot / symbol index determined / derived by the period set as the SR resource. The slot / symbol index determined by the period set as the SR resource may be determined in the same way as in existing systems. Whether to add or subtract the slot / symbol index set by the time-domain offset may be defined in the specification or set by RRC, etc.

[0106] 《Option 2-2》 The SR may be transmitted with a slot / symbol index determined / derived by the period set as the SR resource.

[0107] <<Case 2-3>> A case may be supported in which a time-domain offset is set for a TCI state (e.g., an indicated TCI state) that is applied to a channel / RS other than an SR resource (or a PUCCH resource used for SR transmission). In this case, the time-domain offset may be ignored / dropped (or not applied). In other words, the time-domain offset does not have to be used to determine the transmit / receive resources of other channels / RS. For example, if a time-domain offset is set for a certain TCI state (a TCI state with a predetermined ID), the UE may control the system to use the time-domain offset when that TCI state is used for SR transmission (or PUCCH transmission), but not when it is used for other channels / RS.

[0108] <<RRC Parameters for Time Domain Offset>> RRC parameters for time domain offset may be set within the RRC parameters for TCI states (e.g., TCI-State or TCI-UL-State).

[0109] In this case, the time domain offset may be set by a slot index, a symbol index, or absolute time (e.g., ms), or by a combination of two or more (e.g., two or more combinations). The slot index / symbol index may be a value that assumes a predetermined subcarrier interval (SCS) (or a value based on a predetermined SCS), or it may be set for each SCS.

[0110] The specified SCS may be the SCS in the bandwidth portion (BWP) where RRC parameters related to the TCI state (e.g., TCI-State or TCI-UL-State) are set. Alternatively, it may be the SCS in the BWP where SR (or PUCCH used for SR transmission) is set. By determining the SCS that serves as the basis for the time-domain offset in this way, it becomes possible to appropriately apply the time-domain offset even when multiple SCSs are supported.

[0111] When multiple CCs (or cells) are configured, a BWP (Basework Program) for which RRC parameters related to the TCI state (e.g., TCI-State or TCI-UL-State) are set may support the case where the multiple CCs become a single CC (e.g., CC-common TCI state configuration).

[0112] In CC common TCI state setting, the UE may determine the TCI state (or QCL type) in a BWP / CC for which no RRC parameter is set, based on the RRC parameter for the TCI state set in the BWP (reference BWP / CC) of that one CC. In this case, it may be supported that the SCS of the SR to which the unified TCI state is applied is different from the SCS of the BWP / CC for which the RRC parameter for the TCI state is set. Therefore, it may be defined / set which SCS corresponds to the slot index / symbol index indicated by the time domain offset.

[0113] <Third Embodiment> The third embodiment relates to another example of a method for controlling SR transmission based on TCI status instruction / update.

[0114] The first and second embodiments describe a case in which a time-domain offset is associated with a unified TCI state (or instructed TCI state), but are not limited thereto. For each unified TCI state (or instructed TCI state), SR transmission may be controlled using an SR resource (or PUCCH resource) corresponding to a different SR resource ID. In this disclosure, the SR resource ID may be read as a PUCCH resource ID, an SR transmission opportunity ID, or a PUCCH transmission opportunity ID.

[0115] For example, a first SR resource #1 may be associated with or mapped to a first TCI state #1, a first SR resource #2 may be associated with or mapped to a second TCI state #1, and an nth SR resource #n may be associated with or mapped to an nth TCI state #n. In this disclosure, the nth SR resource #n may be read as the nth PUCCH resource #n, the nth SR transmission opportunity #n, or the nth PUCCH transmission opportunity #n.

[0116] The UE may control the system to send an SR using the first SR resource #1 if the instructed (or updated) TCI state is the first TCI state #1, and to send an SR using the nth SR resource #n if the instructed (or updated) TCI state is the nth TCI state #n.

[0117] The correspondence between each TCI state (e.g., TCI state ID) and the SR resource ID (or PUCCH resource ID, SR transmission opportunity ID, PUCCH transmission opportunity ID) may be set by RRC parameters or defined in the specifications.

[0118] By associating the TCI state with the SR resource ID in this way, it becomes possible to specify a different SR resource depending on the specified TCI state. This allows for flexible adjustment of the SR transmission timing even when the TCI state is changed or updated.

[0119] <Variations> The first and second embodiments may be applied only when a predetermined RRC parameter (for example, a time-domain offset set in the RRC parameters relating to the TCI state) is set. The third embodiment may be applied only when a predetermined RRC parameter (for example, the association between the TCI state and the SR resource ID) is set.

[0120] The first, second, and third embodiments may be applied only when a predetermined UE capability is reported.

[0121] The first, second, and third embodiments may be applied to any or all of the predetermined SRs (or SRs for predetermined purposes). The predetermined SRs (or SRs for predetermined purposes) may be ordinary SRs for requesting resources for UL data (UL-SCH), or SRs for BFRs.

[0122] The first embodiment and the second embodiment may be set for each SR resource, or they may be switched depending on whether or not a time-domain offset is set in the instruction TCI state applied to each SR resource.

[0123] The first, second, and third embodiments are not limited to SR (or PUCCH for SR transmission) but may be applied to other channels / signals. For example, the first and second embodiments may be applied to PUCCH transmission in UE-led beam reporting (UEIBR). Alternatively, they may be applied to other UL channels / signals.

[0124] In the first and second embodiments, the offset applied to the SR resource / PUCCH resource / SR transmission opportunity / PUCCH transmission opportunity in conjunction with the instruction / update of the TCI state is not limited to the time-domain offset. Other offsets (e.g., frequency-domain offsets) may be applied in place of or in addition to the time-domain offset.

[0125] The first and second embodiments show, but are not limited to, a case in which the time-domain offset is associated with the TCI state being updated. The time-domain offset may also be explicitly instructed from the base station to the UE. For example, the DCI / MAC CE that instructs the TCI state may include information about the time-domain offset in its instruction to the UE. As an example, multiple time-domain offsets may be pre-set using RRC parameters, and the DCI / MAC CE that instructs the TCI state may instruct which time-domain offset to apply. This allows the base station to dynamically control the transmission timing of the SR.

[0126] Alternatively, the DCI / MAC CE indicating the TCI status may include information regarding the SR transmission opportunity / SR transmission period when instructing the UE. Alternatively, the DCI / MAC CE indicating the TCI status may include information indicating whether or not to apply a time-domain offset when instructing the UE.

[0127] <Supplement> <<Notification of Information to UE>> In the embodiments described above, notification of any information from the Network (NW) (e.g., Base Station (BS)) to the UE (in other words, reception of any information from the BS at the UE) may be performed using physical layer signaling (e.g., DCI), higher layer signaling (e.g., RRC signaling, MAC CE), specific signals / channels (e.g., PDCCH, PDSCH, reference signal), or a combination thereof.

[0128] If the above notification is made by a MAC CE, the MAC CE may be identified by the inclusion of a new Logical Channel ID (LCID) not defined in existing standards in the MAC subheader.

[0129] If the above notification is made by DCI, the notification may be made by a specific field of the DCI, a Radio Network Temporary Identifier (RNTI) used to scramble the Cyclic Redundancy Check (CRC) bits assigned to the DCI, or the format of the DCI.

[0130] Furthermore, the notification of arbitrary information to the UE in the above-described embodiment may be periodic, semi-persistent, or aperiodic.

[0131] <<Notification of Information from UE>> Notification of any information from the UE to the NW in the embodiments described above (in other words, transmission / reporting of any information from the UE to the BS) may be performed using physical layer signaling (e.g., UCI), higher layer signaling (e.g., RRC signaling, MAC CE), specific signals / channels (e.g., PUCCH, PUSCH, PRACH, reference signals), or a combination thereof.

[0132] If the above notification is made by a MAC CE, the MAC CE may be identified by the inclusion of a new LCID not specified in existing standards in the MAC subheader.

[0133] If the above notice is made by the UCI, the notice may be transmitted using PUCCH or PUSCH.

[0134] Furthermore, the notification of any information from the UE in the above-described embodiment may be periodic, semi-persistent, or aperiodic.

[0135] <<Regarding the application of each embodiment>> In UE / BS, specific (one or more) processes / operations / controls / assumptions / information for at least one of the embodiments described above may be applied (or used) if any or more of the following conditions are met: - A higher-layer parameter indicating the specific process / operation / control / assumption / information is set; - The specific process / operation / control / assumption / information is determined based on the relevant higher-layer parameter; - The specific process / operation / control / assumption / information is designated / activated / triggered by MAC CE / DCI / UCI / Resource / Channel / RS; - A specific UE capability indicating (or related to) the specific process / operation / control / assumption / information is reported or supported; - The application of the specific process / operation / control / assumption / information is determined based on specific conditions.

[0136] The above-mentioned specific UE capabilities may include at least one of the following: supporting the above-mentioned specific processing / operation / control / assumption / information (e.g., time-domain offset); supporting the modification / update of the transmission occasion of SR resources / PUCCH resources; supporting the setting of time-domain offsets; and supporting the association of unified TCI states with time-domain offsets.

[0137] Furthermore, the above-mentioned specific UE capability may be a capability that applies across all frequencies (commonly regardless of frequency), a capability per frequency (e.g., one or a combination thereof, such as cell, band, band combination, BWP, component carrier, etc.), a capability per frequency range (e.g., Frequency Range 1 (FR1), FR2, FR3, FR4, FR5, FR2-1, FR2-2), a capability per subcarrier spacing (SCS), or a capability per feature set (FS) or feature set per component-carrier (FSPC).

[0138] Furthermore, the specific UE capabilities described above may be capabilities that apply across all duplexing schemes (common to all duplexing schemes regardless of the duplexing scheme), or they may be capabilities specific to each duplexing scheme (e.g., Time Division Duplex (TDD), Frequency Division Duplex (FDD)).

[0139] If the above conditions are not met, UE / BS may follow the behavior specified in existing 3GPP releases.

[0140] (Note) The following inventions are added with respect to one embodiment of the present disclosure. [Note 1] A terminal having: a receiving unit that receives information regarding the transmission conditions of a scheduling request and information indicating a unified transmission configuration indication (TCI) state; and a control unit that, when updating the TCI state to be applied to the uplink based on the information indicating the unified TCI state, controls the transmission of the scheduling request based on the information regarding the transmission conditions and a time-domain offset. [Note 2] The terminal according to Note 1, wherein the value of the time-domain offset is set in association with the indicated unified TCI state. [Note 3] The terminal according to Note 1 or Note 2, wherein the value of the time-domain offset is included in the higher-layer parameters relating to the unified TCI state. [Note 4] The terminal according to any one of Notes 1 to 3, wherein if no time-domain offset is set for the unified TCI state applied to the scheduling request, the control unit controls the transmission of the scheduling request based on the information regarding the transmission conditions.

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

[0142] Figure 9 shows an example of a schematic configuration of a wireless communication system according to one embodiment. The wireless communication system 1 (which may also be simply called system 1) may be a system that realizes communication using Long Term Evolution (LTE), 5th generation mobile communication system New Radio (5G NR), etc., as specified by the Third Generation Partnership Project (3GPP).

[0143] Furthermore, the wireless communication system 1 may 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)), and the like.

[0144] In EN-DC, the LTE (E-UTRA) base station (eNB) is the Master Node (MN), and the NR base station (gNB) is the 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.

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

[0146] The wireless communication system 1 may include a base station 11 that forms a macrocell C1 with relatively wide coverage, and base stations 12 (12a-12c) located within the macrocell C1 that form a small cell C2 that is narrower than the macrocell C1. User terminals 20 may be located within at least one cell. The arrangement, number, shape, size, etc., of each cell and user terminal 20 are not limited to the configuration shown in the figure. Hereinafter, when base stations 11 and 12 are not distinguished, they will be collectively referred to as base station 10.

[0147] The wireless communication system 1 may utilize Multi Input Multi Output (MIMO). For example, one cell may be formed by one antenna / base station 10, or by multiple antennas / base stations 10. One [virtual] cell (which may be called a supercell, for example) may be composed of multiple [virtual] cells (which may be called subcells, for example). A supercell may correspond to a cell with a fixed physical range, and a subcell may correspond to a cell whose physical range fluctuates quasi-statically / dynamically. In this case, the wireless communication system 1 may be called a cell-free system.

[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 (CC) and Dual Connectivity (DC).

[0149] Each CC may be included in at least one of the first frequency band (Frequency Range 1 (FR1)) and the second frequency band (Frequency Range 2 (FR2)). A macrocell C1 may be included in FR1, and a 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 above 24 GHz. Note that the frequency bands and definitions of FR1 and FR2 are not limited to these, and for example, FR1 may be in a frequency band higher than FR2.

[0150] Furthermore, the user terminal 20 may communicate in each CC using at least one of Time Division Duplex (TDD) and Frequency Division Duplex (FDD).

[0151] Multiple base stations 10 may be connected by wire (e.g., optical fiber compliant with Common Public Radio Interface (CPRI), X2 / Xn interface, etc.) or wireless (e.g., NR communication). For example, when NR communication is used as a backhaul between base stations 11 and 12, base station 11, which is the upstream station, may be called an Integrated Access Backhaul (IAB) donor, and base station 12, which is the relay station, may be called an IAB node.

[0152] Base station 10 may be connected to the core network 30 via other base stations 10 or directly. The core network 30 may include at least one of the following: Evolved Packet Core (EPC), 5G Core Network (5GCN), Next Generation Core (NGC), etc.

[0153] The core network 30 may include network functions (NF) such as User Plane Function (UPF), Access and Mobility Management Function (AMF), Session Management Function (SMF), Unified Data Management (UDM), Application Function (AF), Data Network (DN), Location Management Function (LMF), and Operation, Administration and Maintenance (Management) (OAM). Multiple functions may be provided by a single network node. Furthermore, communication with an external network (e.g., the Internet) may occur via the DN.

[0154] The user terminal 20 may be a terminal that supports at least one of the following communication methods: LTE, LTE-A, 5G, etc.

[0155] In the wireless communication system 1, an orthogonal frequency division multiplexing (OFDM)-based wireless access scheme may be used. 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-OFDM), etc., may be used in at least one of the downlink (DL) and uplink (UL).

[0156] The wireless access method may also be called a waveform. In wireless communication system 1, other wireless access methods (for example, other single-carrier transmission methods, other multi-carrier transmission methods) may be used for the UL and DL wireless access methods.

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

[0158] Furthermore, in the wireless communication system 1, the uplink channel may include a Physical Uplink Shared Channel (PUSCH), a Physical Uplink Control Channel (PUCCH), a Physical Random Access Channel (PRACH), or the like, all of which are shared by each user terminal 20.

[0159] User data, higher-layer control information, and System Information Blocks (SIBs) are transmitted via PDSCH. User data and higher-layer control information may also be transmitted via PUSCH. Furthermore, Master Information Blocks (MIBs) may be transmitted via PBCH.

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

[0161] Furthermore, the DCI that schedules PDSCH may be called DL assignment, DL DCI, etc., and the DCI that schedules PUSCH may be called UL grant, UL DCI, etc. Furthermore, PDSCH may be read as DL data, and PUSCH may be read as UL data.

[0162] PDCCH detection may utilize a Control Resource Set (CORESET) and a search space. A CORESET corresponds to the resources used to search for DCIs. A search space corresponds to the search area and search method for PDCCH candidates. A single CORESET may be associated with one or more search spaces. A UE may monitor CORESETs associated with a given search space based on the search space configuration.

[0163] A single search space may correspond to one or more PDCCH candidates corresponding to aggregation levels. One or more search spaces may be referred to as a search space set. In this disclosure, "search space," "search space set," "search space configuration," "search space set configuration," "CORESET," and "CORESET configuration" may be interpreted interchangeably.

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

[0165] In this disclosure, downlinks, uplinks, etc., may be expressed without the prefix "link." Also, the prefix "physical" may be omitted from the names of various channels.

[0166] 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, the DL-RS may include 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.

[0167] 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 SS (PSS, SSS) and PBCH (and DMRS for PBCH) may be called an SS / PBCH block, SS Block (SSB), etc. Note that SS, SSB, etc. may also be called reference signals.

[0168] Furthermore, in the wireless communication system 1, the uplink reference signal (UL-RS) may include a sounding reference signal (SRS), a demodulation reference signal (DMRS), etc. The DMRS may also be called a user-specific reference signal (UE-specific Reference Signal).

[0169] (Base Station) Figure 10 shows an example of the configuration of a base station according to one embodiment. The base station 10 includes a control unit 110, a transmitting / receiving unit 120, a transmitting / receiving antenna 130, and a transmission line interface 140. Note that one or more of the control unit 110, the transmitting / receiving unit 120, the transmitting / receiving antenna 130, and the transmission line interface 140 may be provided.

[0170] In this example, the functional blocks of the characteristic parts of this 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 part described below may be omitted.

[0171] The control unit 110 controls the entire base station 10. The control unit 110 can be composed of a controller, control circuit, etc., as described based on common understanding in the technical field related to this disclosure.

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

[0173] The transmitting / receiving 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 transmitting / receiving unit 120 can be composed of a transmitter / receiver, RF circuit, baseband circuit, filter, phase shifter, measurement circuit, transmitting / receiving circuit, etc., as described based on common understanding in the art relating to this disclosure.

[0174] The transmitting / receiving unit 120 may be configured as an integrated transmitting / receiving unit, or it may be composed of a transmitting unit and a receiving unit. The transmitting unit may consist of a transmitting processing unit 1211 and an RF unit 122. The receiving unit may consist of a receiving processing unit 1212, an RF unit 122 and a measuring unit 123.

[0175] The transmitting and receiving antenna 130 can be composed of an antenna described based on common understanding in the art relating to this disclosure, such as an array antenna.

[0176] The transmitting / receiving unit 120 may transmit the downlink channel, synchronization signal, downlink reference signal, etc. The transmitting / receiving unit 120 may also receive the uplink channel, uplink reference signal, etc.

[0177] The transmitting / receiving unit 120 may use digital beamforming (e.g., precoding), analog beamforming (e.g., phase rotation), or the like to form at least one of the transmitting beam and the receiving beam.

[0178] The transmitting / receiving unit 120 (transmission processing unit 1211) may perform processing on data and control information acquired from the control unit 110, for example, at the Packet Data Convergence Protocol (PDCP) layer, the Radio Link Control (RLC) layer (e.g., RLC retransmission control), and the Medium Access Control (MAC) layer (e.g., HARQ retransmission control), to generate a bit sequence to be transmitted.

[0179] The transmitting / receiving unit 120 (transmission processing unit 1211) may perform transmission processing on the bit sequence to be transmitted, 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, and output a baseband signal.

[0180] The transmitting / receiving unit 120 (RF unit 122) may perform modulation, filtering, amplification, etc., of the baseband signal to the radio frequency band and transmit the signal in the radio frequency band via the transmitting / receiving antenna 130.

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

[0182] The transmitting / receiving unit 120 (receiving 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 (may include error correction decoding), MAC layer processing, RLC layer processing, and PDCP layer processing to the acquired baseband signal to acquire user data, etc.

[0183] The transmitting / receiving unit 120 (measurement unit 123) may perform measurements related to 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 also measure received power (e.g., Reference Signal Received Power (RSRP)), reception 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.

[0184] The transmission path interface 140 may send and receive signals (backhaul signaling) with devices included in the core network 30 (e.g., network nodes that provide NF), other base stations 10, etc., and may acquire and transmit user data (user plane data), control plane data, etc. for the user terminal 20.

[0185] In this disclosure, the transmitting and receiving units of the base station 10 may consist of at least one of a transmitting / receiving unit 120, a transmitting / receiving antenna 130, and a transmission path interface 140.

[0186] The base station 10 may be separated into three elements: a Radio Unit (RU), a Distributed Unit (DU), and a Central Unit (CU). For example, the RU may implement RF processing (digital beamforming, digital-to-analog conversion, analog beamforming, etc.) and lower-level physical layer functions (precoding, IFFT, FFT, etc.). The DU may implement higher-level physical layer functions (coding to resource element mapping, etc.), MAC layer functions, and RLC layer functions. The CU may implement PDCP layer, Service Data Adaptation Protocol (SDAP) layer, and RRC layer functions.

[0187] In this disclosure, base station 10 may include a single device that implements all the functions of RU, DU, and CU, or it may include multiple devices that each implement some of the functions of RU, DU, and CU and are connected to each other. In this disclosure, base station 10 may be interpreted as RU / DU / CU.

[0188] The transmitting / receiving unit 120 may transmit information regarding the transmission conditions for scheduling requests and information indicating the Unified Transmission Configuration Indication (TCI) status.

[0189] When the control unit 110 updates the TCI state to be applied to the uplink based on information indicating the unified TCI state, it may control the reception of scheduling requests based on information regarding transmission conditions and time domain offsets.

[0190] (User Terminal) Figure 11 shows an example of the configuration of a user terminal according to one embodiment. The user terminal 20 includes a control unit 210, a transmitting / receiving unit 220, and a transmitting / receiving antenna 230. Note that one or more of the control unit 210, the transmitting / receiving unit 220, and the transmitting / receiving antenna 230 may be provided.

[0191] In this example, the functional blocks of the characteristic parts of this 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 part described below may be omitted.

[0192] The control unit 210 controls the entire user terminal 20. The control unit 210 can be composed of a controller, control circuit, etc., as described based on common understanding in the technical field related to this disclosure.

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

[0194] The transmitting / receiving 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 transmitting / receiving unit 220 can be composed of a transmitter / receiver, RF circuit, baseband circuit, filter, phase shifter, measurement circuit, transmitting / receiving circuit, etc., as described based on common understanding in the art relating to this disclosure.

[0195] The transmitting / receiving unit 220 may be configured as an integrated transmitting / receiving unit, or it may be composed of a transmitting unit and a receiving unit. The transmitting unit may consist of a transmitting processing unit 2211 and an RF unit 222. The receiving unit may consist of a receiving processing unit 2212, an RF unit 222 and a measuring unit 223.

[0196] The transmitting and receiving antenna 230 can be composed of an antenna described based on common understanding in the art relating to this disclosure, such as an array antenna.

[0197] The transmitting / receiving unit 220 may receive the downlink channel, synchronization signal, downlink reference signal, etc. The transmitting / receiving unit 220 may also transmit the uplink channel, uplink reference signal, etc.

[0198] The transmitting / receiving unit 220 may use digital beamforming (e.g., precoding), analog beamforming (e.g., phase rotation), or the like to form at least one of the transmitting beam and the receiving beam.

[0199] The transmitting / receiving 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 and control information acquired from the control unit 210 to generate a bit sequence to be transmitted.

[0200] The transmitting / receiving unit 220 (transmission processing unit 2211) may perform transmission processing on the bit sequence to be transmitted, 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, and output a baseband signal.

[0201] Whether or not to apply DFT processing may be based on the transform precoding settings. The transmitting / receiving unit 220 (transmission processing unit 2211) may perform DFT processing as part of the transmission process to transmit a channel (for example, PUSCH) using a DFT-s-OFDM waveform if transform precoding is enabled for that channel, or it may not perform DFT processing as part of the transmission process if transform precoding is not enabled for that channel.

[0202] The transmitting / receiving unit 220 (RF unit 222) may perform modulation, filtering, amplification, etc., of the baseband signal to the radio frequency band and transmit the signal in the radio frequency band via the transmitting / receiving antenna 230.

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

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

[0205] The transmitting / receiving unit 220 (measuring unit 223) may perform measurements related to the received signal. For example, the measuring unit 223 may perform RRM measurement, CSI measurement, etc., based on the received signal. The measuring unit 223 may also 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.

[0206] The measurement unit 223 may derive channel measurements for CSI calculation based on channel measurement resources. Channel measurement resources may be, for example, Non Zero Power (NZP) CSI-RS resources. The measurement unit 223 may also derive interference measurements for CSI calculation based on interference measurement resources. Interference measurement resources may be at least one of the following: NZP CSI-RS resources for interference measurement, CSI-Interference Measurement (IM) resources, etc. CSI-IM may also be called CSI-Interference Management (IM), and may be interpreted interchangeably with Zero Power (ZP) CSI-RS. In this disclosure, CSI-RS, NZP CSI-RS, ZP CSI-RS, CSI-IM, CSI-SSB, etc., may be interpreted interchangeably.

[0207] In this disclosure, the transmitting unit and receiving unit of the user terminal 20 may be composed of at least one of a transmitting / receiving unit 220 and a transmitting / receiving antenna 230.

[0208] The transmitting / receiving unit 220 may receive information regarding the transmission conditions for scheduling requests and information indicating the Unified Transmission Configuration Indication (TCI) status.

[0209] When the control unit 210 updates the TCI state to be applied to the uplink based on information indicating the unified TCI state, it may control the transmission of scheduling requests based on information regarding transmission conditions and time domain offsets.

[0210] The time-domain offset value may be set in association with the indicated unified TCI state. The time-domain offset value may be included in the higher-level parameters related to the unified TCI state.

[0211] If a time-domain offset is not set for the unified TCI state applied to the scheduling request, the control unit 210 may control the transmission of the scheduling request based on information regarding the transmission conditions.

[0212] (Hardware Configuration) The block diagram used in the description of the above embodiment shows functional units. These functional blocks (components) are realized by any combination of at least one of hardware and software. Furthermore, the method of realizing each functional block is not particularly limited. That is, each functional block may be realized using one device that is physically or logically coupled, or it may be realized using two or more physically or logically separated devices that are directly or indirectly connected (for example, using wired or wireless connections). A functional block may also be realized by combining the above one device or the above multiple devices with software.

[0213] Here, functions include, but are not limited to, judgment, decision, determination, calculation, calculation, processing, derivation, investigation, exploration, confirmation, reception, transmission, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, consideration, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating (mapping), and assigning. For example, a functional block (configuration part) that enables transmission may be called a transmitting unit or transmitter. In all cases, as mentioned above, the method of implementation is not particularly limited.

[0214] For example, a base station, user terminal, etc. in one embodiment of the present disclosure may function as a computer that processes the wireless communication method of the present disclosure. Figure 12 is a diagram showing an example of the hardware configuration of a base station and user terminal according to one embodiment. The base station 10 and user terminal 20 described above may be physically configured as a computer device including a processor 1001, memory 1002, storage 1003, communication device 1004, input device 1005, output device 1006, bus 1007, etc.

[0215] In this disclosure, terms such as apparatus, circuit, device, section, and unit are interchangeable. The hardware configuration of the base station 10 and the user terminal 20 may include one or more of the devices shown in the figure, or it may be configured without some of the devices.

[0216] For example, although only one processor 1001 is shown in the diagram, there may be multiple processors. Furthermore, the processing may be performed by one processor, or it may be performed by two or more processors simultaneously, sequentially, or by other means. Note that the processor 1001 may be implemented using one or more chips.

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

[0218] The processor 1001 controls the entire computer, for example, by running an operating system. The processor 1001 may be composed of a central processing unit (CPU) that includes interfaces with peripheral devices, control devices, arithmetic units, registers, etc. For example, at least a part of the control unit 110 (210) and the transmitting / receiving unit 120 (220) described above may be implemented by the processor 1001.

[0219] Furthermore, the processor 1001 reads programs (program code), 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 accordingly. The program used is one that causes the computer to execute at least a part of the operations described in the above embodiment. 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 other functional blocks may be implemented similarly.

[0220] The memory 1002 is a computer-readable recording medium and may consist of at least one of the following: Read Only Memory (ROM), Erasable Programmable ROM (EPROM), Electrically EPROM (EEPROM), Random Access Memory (RAM), or other suitable storage medium. The memory 1002 may also be called a register, cache, or main memory. The memory 1002 can store executable programs (program code), software modules, etc., for carrying out a wireless communication method according to one embodiment of the present disclosure.

[0221] The storage 1003 is a computer-readable recording medium and may consist of at least one of the following: a flexible disk, a floppy disk, a magneto-optical disk (e.g., a Compact Disk (Compact Disc ROM (CD-ROM)), a Digital Use Disk, a Blu-ray (registered trademark) disk), a removable disk, a hard disk drive, a smart card, a flash memory device (e.g., a card, stick, key drive), a magnetic stripe, a database, a server, or other suitable storage medium. The storage 1003 may also be called an auxiliary storage device.

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

[0223] The input device 1005 is an input device that accepts input from an external source (e.g., a keyboard, mouse, microphone, switch, button, sensor, etc.). The output device 1006 is an output device that outputs to an external source (e.g., a display, speaker, light-emitting diode (LED) lamp, etc.). The input device 1005 and the output device 1006 may be configured as an integrated unit (e.g., a touch panel).

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

[0225] 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), and a field programmable gate array (FPGA), and some or all of each functional block may be implemented using such hardware. For example, the processor 1001 may be implemented using at least one of these hardware components.

[0226] Furthermore, devices included in the core network 30 (for example, network nodes that provide NF) may also be implemented using the functional block / hardware configuration described above.

[0227] (Variations) Terms used in this disclosure and terms necessary for understanding this disclosure may be replaced with terms having the same or similar meanings. For example, channel, symbol and signal (signal or signaling) may be used interchangeably. Also, a signal may be a message. A reference signal may be abbreviated as RS and may be called a pilot, pilot signal, etc., depending on the applicable standard. Also, a component carrier (CC) may be called a cell, frequency carrier, carrier frequency, etc.

[0228] A wireless frame may consist of one or more periods (frames) in the time domain. Each of these periods (frames) constituting a wireless frame may be called a subframe. Furthermore, a subframe may consist 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.

[0229] Here, the neurology may be communication parameters applied to at least one of the transmission and reception of a signal or channel. The neurology may be, for example, at least one of the following: subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, radio frame configuration, specific filtering processes performed by the transceiver in the frequency domain, and specific windowing processes performed by the transceiver in the time domain.

[0230] A slot may consist of one or more symbols in the time domain (such as Orthogonal Frequency Division Multiplexing (OFDM) symbols or Single Carrier Frequency Division Multiple Access (SC-FDMA) symbols). Alternatively, a slot may be a time unit based on neurology.

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

[0232] Wireless frames, subframes, slots, minislots, and symbols all represent units of time when transmitting a signal. Wireless frames, subframes, slots, minislots, and symbols may each be referred to by different names. Furthermore, the units of time such as frames, subframes, slots, minislots, and symbols in this disclosure may be interpreted as interchangeable.

[0233] For example, one subframe may be called a TTI, multiple consecutive subframes may be called a TTI, and one slot or one mini-slot may be called a TTI. In other words, at least one of a subframe and a TTI may be a subframe in existing LTE (1 ms), a period shorter than 1 ms (e.g., 1-13 symbols), or a period longer than 1 ms. Note that the unit representing a TTI may be called a slot, mini-slot, etc., instead of a subframe.

[0234] Here, TTI refers to, for example, the smallest time unit for scheduling in wireless communication. For example, in an LTE system, the base station schedules each user terminal to allocate wireless resources (such as the frequency bandwidth and transmission power available to each user terminal) in TTI units. However, the definition of TTI is not limited to this.

[0235] TTI may be a transmission time unit for channel-encoded data packets (transport blocks), code blocks, code words, etc., or it may be a processing unit for scheduling, link adaptation, etc. When a TTI is given, the actual time interval (e.g., number of symbols) in which the transport block, code block, code word, etc. are mapped may be shorter than the TTI.

[0236] Furthermore, if one slot or one mini-slot is referred to as a TTI, then one or more TTIs (i.e., one or more slots or one or more mini-slots) may constitute the minimum time unit for scheduling. In addition, the number of slots (number of mini-slots) that constitute this minimum time unit for scheduling may be controlled.

[0237] A TTI with a time length of 1 ms may be called a normal TTI, long TTI, normal subframe, long subframe, slot, etc. A TTI shorter than a normal TTI may be called a shortened TTI, short TTI, partial or fractional TTI, shortened subframe, short subframe, mini slot, sub slot, slot, etc.

[0238] Furthermore, long TTIs (e.g., normal TTIs, subframes, etc.) may be interpreted as TTIs with a time length exceeding 1 ms, and short TTIs (e.g., shortened TTIs, etc.) may be interpreted as TTIs with a TTI length less than that of a long TTI but 1 ms or more.

[0239] A Resource Block (RB) is a resource allocation unit in the time domain and frequency domain, and in the frequency domain, it may contain one or more consecutive subcarriers. The number of subcarriers in an RB may be the same regardless of the neurology, for example, 12. The number of subcarriers in an RB may be determined based on the neurology.

[0240] Furthermore, an RB may contain one or more symbols in the time domain and may have the length of one slot, one minislot, one subframe, or one TTI. One TTI, one subframe, etc., may each consist of one or more resource blocks.

[0241] One or more RBs may also be called Physical RBs (PRBs), Sub-Carrier Groups (SCGs), Resource Element Groups (REGs), PRB pairs, RB pairs, etc.

[0242] Furthermore, a resource block may consist of one or more resource elements (REs). For example, one RE may be a radio resource area comprising one subcarrier and one symbol.

[0243] A Bandwidth Part (BWP), also known as a partial bandwidth, may represent a subset of consecutive common resource blocks (RBs) for a given neurology in a given carrier. These common RBs may be identified by an index of the RBs relative to a common reference point of the carrier. The PRBs may be defined and numbered within a given BWP.

[0244] A BWP may include UL BWP (BWP for UL) and DL BWP (BWP for DL). One or more BWPs may be configured within a single carrier for a UE.

[0245] At least one of the configured BWPs may be active, and the UE does not need to assume that it will transmit or receive a predetermined signal / channel outside of the active BWP. In this disclosure, terms such as "cell" and "carrier" may be read as "BWP".

[0246] The structures of wireless frames, subframes, slots, minislots, and symbols described above are merely examples. For example, the number of subframes included in a wireless frame, the number of slots per subframe or wireless 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, and the number of symbols, symbol length, and cyclic prefix (CP) length within the TTI can be varied in various ways.

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

[0248] The names used for parameters and other elements in this disclosure are not restrictive in any way. Furthermore, mathematical formulas and other elements using these parameters may differ from those expressly disclosed in this disclosure. Various channels (PUCCH, PDCCH, etc.) and information elements can be identified by any suitable name, and therefore, the various names assigned to these various channels and information elements are not restrictive in any way.

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

[0250] Furthermore, information, signals, etc., can be output from upper layers to lower layers and from lower layers to upper layers, or to at least one of the two. Information, signals, etc., may also be input and output via multiple network nodes.

[0251] Input and output information and signals may be stored in a specific location (e.g., memory) or managed using a management table. Input and output information and signals may be overwritten, updated, or appended to. Output information and signals may be deleted. Input information and signals may be transmitted to other devices.

[0252] Any information described in this disclosure (e.g., variables, constants, parameters) may be communicated from any first device (e.g., UE / base station) to any second device (e.g., base station / UE) that indicates / specifies (or relates to) the value of such any information, even if not specifically stated in the embodiments described above.

[0253] Information notification is not limited to the embodiments described herein and may be carried out by other means. For example, information notification in this disclosure may be carried out by physical layer signaling (e.g., Downlink Control Information (DCI), Uplink Control Information (UCI)), higher layer signaling (e.g., Radio Resource Control (RRC) signaling, broadcast information (Master Information Block (MIB), System Information Block (SIB)), Medium Access Control (MAC) signaling), other signals, or a combination thereof.

[0254] Physical layer signaling may also be called Layer 1 / Layer 2 (L1 / L2) control information (L1 / L2 control signals), L1 control information (L1 control signals), etc. RRC signaling may also be called RRC messages, for example, RRC Connection Setup messages, RRC Connection Reconfiguration messages, etc. MAC signaling may also be communicated using, for example, MAC Control Elements (CEs).

[0255] Furthermore, notification of the specified information (for example, notification that "X is the case") is not limited to explicit notification, but may also be made implicitly (for example, by not notifying the specified information or by notifying other information).

[0256] The determination may be made by a value represented by one bit (0 or 1), by a boolean value represented as true or false, or by a numerical comparison (for example, a comparison with a predetermined value).

[0257] Software should be broadly interpreted to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, functions, and so on, whether they are called software, firmware, middleware, microcode, hardware description languages, or by any other name.

[0258] Furthermore, software, instructions, information, etc., may be transmitted and received via a transmission medium. For example, if software is transmitted from a website, server, or other remote source using at least one of wired technology (such as coaxial cable, fiber optic cable, twisted pair, or Digital Subscriber Line (DSL)) and wireless technology (such as infrared or microwave), then at least one of these wired and wireless technologies is included in the definition of a transmission medium.

[0259] The terms “system” and “network” as used in this disclosure may be used interchangeably. “Network” may also mean the equipment included in the network (e.g., base stations).

[0260] In this 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,” “layer,” “number of layers,” “rank,” “resource,” “resource set,” “beam,” “beam width,” “beam angle,” “antenna,” “antenna element,” “panel,” “UE panel,” “transmitting entity,” and “receiving entity” may be used interchangeably.

[0261] In this disclosure, "antenna port" may be interpreted interchangeably with "antenna port for any signal / channel" (e.g., a Demodulation Reference Signal (DMRS) port). In this disclosure, "resource" may be interpreted interchangeably with "resource for any signal / channel" (e.g., a reference signal resource, an SRS resource, etc.). Resources may include time / frequency / code / spatial / power resources. Furthermore, a spatial domain transmit filter may include at least one of a spatial domain transmit filter and a spatial domain receive filter.

[0262] The above group may include, for example, at least one of the following: a spatial relationship group, a code division multiplexing (CDM) group, a reference signal (RS) group, a control resource set (CORESET) group, a PUCCH group, an antenna port group (e.g., a DMRS port group), a layer group, a resource group, a beam group, an antenna group, or a panel group.

[0263] Furthermore, in this disclosure, terms such as beam, SRS Resource Indicator (SRI), CORESET, CORESET pool, PDSCH, PUSCH, Codeword (CW), Transport Block (TB), and RS may be interpreted interchangeably.

[0264] Furthermore, in this disclosure, TCI state, downlink TCI state (DL TCI state), uplink TCI state (UL TCI state), unified TCI state, common TCI state, joint TCI state, etc., may be interpreted interchangeably.

[0265] Furthermore, in this disclosure, terms such as "QCL," "QCL assumption," "QCL relationship," "QCL type information," "QCL property / properties," "specific QCL type (e.g., Type A, Type D) properties," and "specific QCL type (e.g., Type A, Type D)" may be interpreted interchangeably.

[0266] In this disclosure, terms such as index, identifier (ID), indicator, indication, and resource ID may be interpreted interchangeably. In this disclosure, terms such as sequence, list, set, group, cluster, subset may be interpreted interchangeably.

[0267] Furthermore, the spatial relationship information Identifier (ID) (TCI state ID) and spatial relationship information (TCI state) may be interpreted as mutually exclusive. "Spatial relationship information (TCI state)" may be interpreted as mutually exclusive as "a set of spatial relationship information (TCI state)," "one or more pieces of spatial relationship information," etc. TCI state and TCI may be interpreted as mutually exclusive. Spatial relationship information and spatial relationship may be interpreted as mutually exclusive.

[0268] In this disclosure, terms such as “Base Station (BS),” “wireless 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,” and “component carrier” may be used interchangeably. Base stations may also be referred to by terms such as macrocell, small cell, femtocell, and picocell.

[0269] A base station may house one or more (e.g., three) cells. If a base station houses multiple cells, the entire coverage area of ​​the base station may be divided into several smaller areas, each of which may also be provided with communication services 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 ​​at least one of the base station and / or base station subsystems that provide communication services in that coverage.

[0270] In this disclosure, the transmission of information by a base station to a terminal may be interpreted as the base station instructing the terminal to perform a control / operation based on said information.

[0271] In this disclosure, terms such as "Mobile Station (MS)," "user terminal," "User Equipment (UE)," and "terminal" may be used interchangeably.

[0272] A mobile station may also be called 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 appropriate term.

[0273] At least one of the base station and the mobile station may be called a transmitting device, a receiving device, a wireless communication device, etc. At least one of the base station and the mobile station may also be a device mounted on a moving object, the moving object itself, etc.

[0274] The term "mobile object" refers to any movable object, regardless of its speed, and naturally includes cases where the mobile object is stationary. Examples of such mobile objects include, but are not limited to, vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, handcarts, rickshaws, ships and other watercraft, airplanes, rockets, satellites, drones, multicopters, quadcopters, balloons, and items carried on them. Furthermore, such mobile objects may be autonomously driven objects operating based on operational commands.

[0275] The mobile entity may be a vehicle (e.g., a car, an airplane), an unmanned mobile entity (e.g., a drone, an autonomous vehicle), or a robot (manned or unmanned). At least one of the base station and the mobile station may be a device that does 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.

[0276] Figure 13 shows an example of a vehicle according to one embodiment. The vehicle 40 includes a drive unit 41, a steering unit 42, an accelerator pedal 43, a brake pedal 44, a shift lever 45, left and right front wheels 46, left and right rear wheels 47, an axle 48, an electronic control unit 49, various sensors (including a current sensor 50, a rotation speed sensor 51, a pneumatic pressure sensor 52, a vehicle speed sensor 53, an acceleration sensor 54, an accelerator pedal sensor 55, a brake pedal sensor 56, a shift lever sensor 57, and an object detection sensor 58), an information service unit 59, and a communication module 60.

[0277] The drive unit 41 consists of, for example, at least one of an engine, a motor, or an engine-motor hybrid. The steering unit 42 includes at least a steering wheel (also called a handle) and is configured to steer at least one of the front wheels 46 and the rear wheels 47 based on the operation of the steering wheel operated by the user.

[0278] The electronic control unit 49 consists of a microprocessor 61, memory (ROM, RAM) 62, and communication ports (e.g., input / output (IO) ports) 63. Signals from various sensors 50-58 installed in the vehicle are input to the electronic control unit 49. The electronic control unit 49 may also be called an Electronic Control Unit (ECU).

[0279] Signals from various sensors 50-58 include current signals from current sensor 50 for sensing motor current, rotational speed signals of front wheels 46 / rear wheels 47 acquired by rotational speed sensor 51, air pressure signals of front wheels 46 / rear wheels 47 acquired by air pressure sensor 52, vehicle speed signals acquired by vehicle speed sensor 53, acceleration signals acquired by acceleration sensor 54, accelerator pedal depression amount signals acquired by accelerator pedal sensor 55, brake pedal depression amount signals acquired by brake pedal sensor 56, operation signals of shift lever 45 acquired by shift lever sensor 57, and detection signals acquired by object detection sensor 58 for detecting obstacles, vehicles, pedestrians, etc.

[0280] The information service unit 59 consists of various devices for providing (outputting) various types of information such as driving information, traffic information, and entertainment information, including a car navigation system, audio system, speakers, display, television, and radio, and one or more ECUs that control these devices. The information service unit 59 uses information acquired from external devices via a communication module 60 or the like to provide various types of information / services (for example, multimedia information / multimedia services) to the occupants of the vehicle 40.

[0281] The information service unit 59 may include input devices that accept input from the outside (e.g., keyboard, mouse, microphone, switch, button, sensor, touch panel, etc.) or output devices that perform output to the outside (e.g., display, speaker, LED lamp, touch panel, etc.).

[0282] The driver assistance system unit 64 consists of various devices that provide functions to prevent accidents or reduce the driver's workload, such as millimeter-wave radar, Light Detection and Ranging (LiDAR), cameras, positioning locators (e.g., Global Navigation Satellite System (GNSS)), map information (e.g., High Definition (HD) maps, Autonomous Vehicle (AV) maps), gyro systems (e.g., Inertial Measurement Unit (IMU), Inertial Navigation System (INS)), artificial intelligence (AI) chips, and AI processors, as well as one or more ECUs that control these devices. The driver assistance system unit 64 also transmits and receives various information via the communication module 60 to realize driver assistance functions or autonomous driving functions.

[0283] The communication module 60 can communicate with the microprocessor 61 and components of the vehicle 40 via the communication port 63. For example, the communication module 60 sends and receives data (information) via the communication port 63 to the drive unit 41, steering unit 42, accelerator pedal 43, brake pedal 44, shift lever 45, left and right front wheels 46, left and right rear wheels 47, axle 48, the microprocessor 61 and memory (ROM, RAM) 62 in the electronic control unit 49, and various sensors 50-58 provided in the vehicle 40.

[0284] The communication module 60 is a communication device that can be controlled by the microprocessor 61 of the electronic control unit 49 and can communicate with external devices. For example, it can send and receive various types of information to and from external devices via wireless communication. The communication module 60 may be located either inside or outside the electronic control unit 49. The external device may be, for example, the base station 10 or the user terminal 20 described above. Alternatively, the communication module 60 may be, for example, at least one of the base station 10 and the user terminal 20 (it may function as at least one of the base station 10 and the user terminal 20).

[0285] The communication module 60 may transmit at least one of the following to an external device via wireless communication: signals from the various sensors 50-58 input to the electronic control unit 49, information obtained based on said signals, and information based on input from an external source (user) obtained via the information service unit 59. The electronic control unit 49, the various sensors 50-58, the information service unit 59, etc., may also be called input units that accept input. For example, the PUSCH transmitted by the communication module 60 may include the information based on the above input.

[0286] The communication module 60 receives various information (traffic information, signal information, inter-vehicle information, etc.) transmitted from an external device and displays it on the information service unit 59 installed in the vehicle. The information service unit 59 may also be called an output unit, which outputs information (for example, it outputs information to devices such as displays and speakers based on the PDSCH (or data / information decoded from the PDSCH) received by the communication module 60).

[0287] Furthermore, the communication module 60 stores various information received from external devices in a memory 62 that can be used by the microprocessor 61. Based on the information stored in the memory 62, the microprocessor 61 may control the drive unit 41, steering unit 42, accelerator pedal 43, brake pedal 44, shift lever 45, left and right front wheels 46, left and right rear wheels 47, axle 48, various sensors 50-58, etc., which are provided in the vehicle 40.

[0288] Furthermore, the term "base station" in this disclosure may be interpreted as "user terminal." For example, the various aspects / embodiments of this 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), Vehicle-to-Everything (V2X)). In this case, the user terminal 20 may have the functions of the base station 10 described above. Also, terms such as "uplink" and "downlink" may be interpreted as terms corresponding to terminal-to-terminal communication (for example, "sidelink"). For example, uplink channel, downlink channel, etc., may be interpreted as sidelink channel.

[0289] Similarly, the term "user terminal" in this disclosure may be replaced with "base station." In this case, the base station 10 may be configured to have the same functions as the user terminal 20 described above.

[0290] In this disclosure, operations performed by a base station may, in some cases, be performed by its upper node. In a network including one or more network nodes having base stations, it is clear that various operations performed for communication with terminals may be performed by the base station, one or more network nodes other than the base station (for example, a Mobility Management Entity (MME), a Serving Gateway (S-GW), etc., but not limited to these), or a combination thereof.

[0291] Each aspect / embodiment described in this disclosure may be used individually, in combination, or switched between as needed during execution. Furthermore, the processing procedures, sequences, flowcharts, etc., of each aspect / embodiment described in this disclosure may be rearranged in order, provided they are consistent. For example, the methods described in this disclosure present various step elements using exemplary order and are not limited to the specific order presented.

[0292] Each aspect / embodiment described in this disclosure is 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 (where x is, for example, an integer or decimal)), 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®), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi®), IEEE 802.16 (WiMAX®), IEEE 802.20, systems utilizing Ultra-WideBand (UWB), Bluetooth®, or other appropriate wireless communication methods, and next-generation systems extended, modified, created, or defined based thereon may also be applied. Furthermore, multiple systems may be applied in combination (for example, a combination of LTE or LTE-A and 5G).

[0293] In this disclosure, the phrase "based on" does not mean "based solely on" unless otherwise specified. In other words, the phrase "based on" means both "based solely on" and "based at least on."

[0294] Any reference to elements using the designations “first,” “second,” etc., as used in this disclosure does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient way to distinguish between two or more elements. Accordingly, the references to the first and second elements do not imply that only two elements may be employed or that the first element must precede the second element in any way.

[0295] The term “determining” as used in this disclosure may encompass a wide variety of actions. For example, “determining” may be considered to mean judging, calculating, computing, processing, deriving, investigating, looking up, searching, or inquiring (e.g., searching in tables, databases, or other data structures), ascertaining, etc.

[0296] Furthermore, "judgment (decision)" may be considered as "judging (deciding)" things like receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, accessing (e.g., accessing data in memory).

[0297] Furthermore, “judgment (decision)” may be considered as “judgment (decision)” of resolving, selecting, choosing, establishing, comparing, etc. In other words, “judgment (decision)” may be considered as “judgment (decision)” of some action. In this disclosure, “judgment (decision)” may be interpreted as mutually interchangeable with the actions described above.

[0298] Furthermore, in this disclosure, “determine / determining” may be interpreted as “assume / assuming,” “expect / expecting,” or “consider / considering.” In addition, in this disclosure, “not expecting to do…” may be interpreted as “expecting not to do….”

[0299] In this disclosure, "expect" may be rephrased as "be expected." For example, "expect(s) ..." (where "..." may be expressed as a that clause, an infinitive, etc.) may be rephrased as "be expected ..." or "do (the verb without "to" if "..." is an infinitive)." Similarly, "does not expect ..." may be rephrased as "be not expected ..." or "do not (the verb without "to" if "..." is an infinitive)." Furthermore, "An apparatus A is not expected ..." may be rephrased as "An apparatus B other than apparatus A does not expect ... from apparatus A" (for example, if apparatus A is a UE, apparatus B may be a base station).

[0300] The term "maximum transmit power" as used in this disclosure may mean the maximum transmit power, the nominal UE maximum transmit power, or the rated UE maximum transmit power.

[0301] As used in this disclosure, the terms “connected,” “coupled,” and any variations thereof mean any direct or indirect connection or coupling between two or more elements, and may include one or more intermediate elements between two elements that are “connected” or “coupled” with each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, “connection” may be replaced with “access.”

[0302] In this disclosure, when two elements are connected, they can be considered to be "connected" or "coupled" to each other using one or more wires, cables, printed electrical connections, etc., and, in some non-exclusive and non-exclusive examples, electromagnetic energy having wavelengths in the radio frequency domain, microwave domain, and optical (both visible and invisible) domain.

[0303] In this 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 "combine" may be interpreted similarly to "different."

[0304] Where the terms “include,” “including,” and variations thereof are used in this disclosure, these terms are intended to be inclusive, as is the term “comprising.” Furthermore, the term “or” as used in this disclosure is not intended to mean exclusive OR.

[0305] In this disclosure, if articles are added by translation, such as a, an, and the in English, this disclosure may include the fact that the noun following these articles is plural.

[0306] In this disclosure, "less than or equal to," "less than," "greater than or equal to," "more than," and "equal to" may be interpreted interchangeably. In addition, in this disclosure, words meaning "good," "bad," "big," "small," "high," "low," "early," "slow," "wide," and "narrow" may be interpreted interchangeably, not limited to the positive, comparative, and superlative degrees. In addition, in this disclosure, words meaning "good," "bad," "big," "small," "high," "low," "early," "slow," "wide," and "narrow" may be interpreted interchangeably, not limited to the positive, comparative, and superlative degrees, by adding "i-th" (where i is any integer) to the expression (for example, "highest" may be interpreted interchangeably with "i-th highest").

[0307] In this disclosure, "of," "for," "regarding," "related to," and "associated with" may be interpreted as being interchangeable.

[0308] In this disclosure, phrases such as "when A, B", "if A, then B", "B upon A", "B in response to A", "B based on A", "B during / while A", "B before A", "B at (the same time as) / on A", "B after A", "B since A", and "B until A" may be interchangeable. Furthermore, A, B, etc., may be replaced with appropriate expressions such as nouns, gerunds, or regular sentences depending on the context. The time difference between A and B may be approximately zero (immediately after or immediately before). Additionally, a time offset may be applied to the time when A occurs. For example, "A" may be interpreted as "before / after the time offset when A occurs". The time offset (e.g., one or more symbols / slots) may be predetermined or determined by the UE based on notified information.

[0309] In this disclosure, timing, time, duration, time instance, any unit of time (e.g., slot, subslot, symbol, subframe), period, occasion, resource, etc., may be interpreted interchangeably.

[0310] Although the invention described herein has been explained in detail above, it will be clear to those skilled in the art that the invention described herein is not limited to the embodiments described herein. The descriptions herein are illustrative and not intended to be restrictive in any way to the invention described herein.

[0311] This application is based on Japanese Patent Application No. 2025-053900, filed on March 27, 2025. All of its contents are included herein.

Claims

1. A terminal having a receiving unit that receives information regarding the transmission conditions for a scheduling request and information indicating the Unified Transmission Configuration Indication (TCI) state, and a control unit that, when updating the TCI state to be applied to the uplink based on the information indicating the Unified TCI state, controls the transmission of the scheduling request based on the information regarding the transmission conditions and the time domain offset.

2. The terminal according to claim 1, wherein the value of the time-domain offset is set in association with the indicated unified TCI state.

3. The terminal according to claim 1, wherein the value of the time-domain offset is included in the higher-level parameters relating to the unified TCI state.

4. If no time domain offset is set for the unified TCI state applied to the scheduling request, the control unit controls the transmission of the scheduling request based on the information regarding the transmission conditions, according to claim 1.

5. A wireless communication method for a terminal, comprising the steps of: receiving information regarding the transmission conditions for a scheduling request and information indicating a Unified Transmission Configuration Indication (TCI) state; and, when updating the TCI state to be applied to the uplink based on the information indicating the Unified TCI state, controlling the transmission of the scheduling request based on the information regarding the transmission conditions and a time-domain offset.

6. A base station having a transmission unit that transmits information regarding the transmission conditions for a scheduling request and information indicating a Unified Transmission Configuration Indication (TCI) state, and a control unit that, when updating the TCI state to be applied to the uplink based on the information indicating the Unified TCI state, controls the reception of the scheduling request based on the information regarding the transmission conditions and a time-domain offset.