Terminal, radio communication method, and base station
The terminal and base station system addresses communication quality issues by aligning scheduling request transmissions with unified TCI state updates using a time domain offset, enhancing communication stability.
Patent Information
- Application Number
- JP2025053900
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2025-03-27
- Publication Date
- 2025-10-14
AI Technical Summary
In future wireless communication systems, the dynamic update of beam/TCI states is not adequately considered, leading to potential communication quality deterioration.
A terminal and base station system that controls scheduling request transmission based on unified TCI state information, incorporating a time domain offset to align transmission opportunities, thereby managing beam/TCI state updates efficiently.
This approach suppresses communication quality degradation by aligning transmission conditions with TCI state updates, reducing the need for RRC reconfiguration and network overhead.
Smart Images

Figure 2025156204000001_ABST
Abstract
Description
[Technical Field]
[0001] The present disclosure relates to a terminal, a wireless communication method, and a base station in a next-generation mobile communication system. [Background technology]
[0002] In Universal Mobile Telecommunications System (UMTS) networks, Long Term Evolution (LTE) has been specified with the aim of achieving higher data rates and lower latency (Non-Patent Document 1). Also, LTE-Advanced (3GPP Rel. 10-14) has been specified with the aim of achieving higher capacity and more advanced features than LTE (Third Generation Partnership Project (3GPP (registered trademark)) Release (Rel.) 8, 9).
[0003] Successor systems to LTE (e.g., 5th generation mobile communication system (5G), 5G+ (plus), 6th generation mobile communication system (6G), New Radio (NR), 3GPP Rel. 15 or later) are also being considered. [Prior art documents] [Non-patent literature]
[0004] [Non-Patent Document 1] 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 Summary of the Invention [Problem to be solved by the invention]
[0005] In future wireless communication systems (e.g., NR), it is being considered that user terminals (UEs) will control transmission and reception processing based on information about quasi-co-location (QCL) (QCL assumptions / Transmission Configuration Indication (TCI) states / spatial relationships).
[0006] In addition, in Rel. 17 and later, a TCI state (unified TCI state) that can be applied to multiple types of signals (channels / reference signals) will be used. It is expected that the unified TCI state will be dynamically updated for each UE.
[0007] However, there are cases where the consideration of dynamic update of beam / TCI status is not clear. If this consideration is insufficient, communication may not be performed properly and communication quality may deteriorate.
[0008] Therefore, one of the objects of the present disclosure is to provide a terminal, a wireless communication method, and a base station that can suppress deterioration of communication quality even when the beam / TCI state is updated. [Means for solving the problem]
[0009] A terminal according to one embodiment of the present disclosure includes a receiving unit that receives information regarding transmission conditions of a scheduling request and information indicating a unified transmission configuration indication (TCI) state, and a control unit that controls transmission of a scheduling request based on the information regarding the transmission conditions and a time domain offset when updating a TCI state to be applied to an uplink based on the information indicating the unified TCI state. [Effects of the Invention]
[0010] According to one aspect of the present disclosure, degradation of communication quality can be suppressed even when the beam / TCI state is updated. [Brief explanation of the drawings]
[0011] [Figure 1] 1A and 1B show an example of a unified / common TCI framework. [Figure 2] 2A and 2B show an example of DCI-based TCI status indication. [Figure 3] FIG. 3 shows an example in which SR transmission opportunities for multiple UEs are set in the same set of OFDM symbols. [Figure 4] FIG. 4 shows an example of a case where the TCI status of some UEs is updated when SR transmission opportunities for multiple UEs are set in the same set of OFDM symbols. [Figure 5] FIG. 5 shows an example of SR transmission control according to the first embodiment. [Figure 6] FIG. 6 shows another example of SR transmission control according to the first embodiment. [Figure 7] FIG. 7 shows an example of RRC parameters related to the time domain offset according to the second embodiment. [Figure 8] FIG. 8 shows another example of RRC parameters related to the time domain offset according to the second embodiment. [Figure 9] FIG. 9 is a diagram illustrating an example of a schematic configuration of a wireless communication system according to an embodiment. [Figure 10] FIG. 10 is a diagram illustrating an example of the configuration of a base station according to an embodiment. [Figure 11] FIG. 11 is a diagram illustrating an example of the configuration of a user terminal according to an embodiment. [Figure 12] FIG. 12 is a diagram illustrating an example of the hardware configuration of a base station and a user terminal according to an embodiment. [Figure 13] FIG. 13 is a diagram illustrating an example of a vehicle according to an embodiment. DETAILED DESCRIPTION OF THE INVENTION
[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 triggers / sends an SR when it has UL data to transmit but does not have an UL grant (allocation of UL resources).
[0013] The SR may be triggered by a predetermined event, such as, but not limited to, a Buffer Status Report (BSR), a beam failure recovery of an SCell, a UE initiated beam report (LTM), or a listen before talk (LBT).
[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 a PUCCH resource (which may also be referred to as an SR resource). The SR resource may be a predetermined time / frequency resource allocated on the PUCCH to be used for transmitting the SR.
[0015] The transmission conditions / transmission parameters of the SR (for example, parameters of the SR resource used for SR transmission (for example, periodicity, etc.)) may be set to the UE by the base station using RRC parameters, etc. The base station may set to each UE, using RRC parameters, which PUCCH resource to use to transmit the SR.
[0016] (TCI, spatial relations, QCL) In NR, it is being considered to control the reception processing (e.g., at least one of reception, demapping, demodulation, and decoding) and transmission processing (e.g., at least one of transmission, mapping, precoding, modulation, and encoding) in the UE of at least one of a signal and a channel (referred to as signal / channel) based on the transmission configuration indication state (TCI state).
[0017] The TCI state is information about the quasi-co-location (QCL) of signals / channels, and may also be called spatial reception parameters, spatial relation information, etc. The TCI state may be configured in the UE for each channel or signal.
[0018] A QCL is an index that indicates the statistical properties of a signal / channel. For example, if a signal / channel has a QCL relationship with another signal / channel, it may mean that it can be assumed that at least one of the Doppler shift, Doppler spread, average delay, delay spread, and spatial parameter (e.g., spatial Rx parameter) is the same between these different signals / channels (i.e., they are QCLs with respect to at least one of these).
[0019] The spatial reception parameters may correspond to a reception beam (e.g., a reception analog beam) of the UE, and the beam may be determined based on a spatial QCL. A QCL (or at least one element of a QCL) in the present disclosure may be replaced with an sQCL (spatial QCL).
[0020] A plurality of types (QCL types) of QCLs may be defined. For example, four QCL types A and B may be provided, each having different parameters (or parameter sets) that can be assumed to be the same.
[0021] The assumption by a UE that a Control Resource Set (CORESET), channel, or reference signal has a specific QCL (e.g., QCL type D) relationship with another CORESET, channel, or reference signal may be referred to as a QCL assumption.
[0022] The UE may determine at least one of a transmit beam (Tx beam) and a receive beam (Rx beam) for a signal / channel based on the TCI condition or QCL assumption of the signal / channel.
[0023] The TCI state may be, for example, information about the QCL between the target channel (in other words, the Reference Signal (RS) for the channel) and another signal (e.g., another RS). The TCI state may be set (indicated) by higher layer signaling, physical layer signaling, or a combination thereof.
[0024] The physical layer signaling may be, for example, Downlink Control Information (DCI).
[0025] The channel for which the TCI state or spatial relationship is set (specified) may be, for example, at least one of a downlink shared channel (Physical Downlink Shared Channel (PDSCH)), a downlink control channel (Physical Downlink Control Channel (PDCCH)), an uplink shared channel (Physical Uplink Shared Channel (PUSCH)), and an uplink control channel (Physical Uplink Control Channel (PUCCH)).
[0026] Furthermore, the RS that has a QCL relationship with the channel may be, for example, at least one of a Synchronization Signal Block (SSB), a Channel State Information Reference Signal (CSI-RS), a Sounding Reference Signal (SRS), a CSI-RS for tracking (also called a Tracking Reference Signal (TRS)), and 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 referred to as an SS / PBCH block.
[0028] An RS of QCL type X in a TCI state may refer to an RS that has a relationship of QCL type X with (the DMRS of) a certain channel / signal, and this RS may be called a QCL source of QCL type X in the TCI state.
[0029] (Unified / Common TCI Framework) The unified TCI framework allows multiple types of channels / RSs (UL / DL) to be controlled by a common framework. The unified TCI framework does not specify the TCI state or spatial relationship for each channel as in Rel. 15. Instead, it specifies a common beam (common TCI state) and applies it to all UL and DL channels. Alternatively, 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] The UE may assume the same TCI state for UL and DL (joint TCI state, joint TCI pool, joint common TCI pool, joint TCI state set). The UE may assume different TCI states for UL and DL (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 via MAC CE based beam management (MAC CE level beam direction). The default TCI state of the PDSCH may be updated to align with 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 the MAC CE. The UL / DL DCI may select one from the X active TCI states. The selected TCI state may apply to both UL and DL channels / RS.
[0033] The TCI pool (set) may be multiple TCI states configured by RRC parameters, or multiple TCI states (active TCI states, active TCI pools, sets) activated by the MAC CE among the multiple TCI states configured by RRC parameters. Each TCI state may be a QCL type A / D RS. SSB, CSI-RS, or SRS may be configured as the QCL type A / D RS.
[0034] In the example of Figure 1A, RRC parameters (information elements) configure multiple TCI states for both DL and UL. The MAC CE may activate multiple TCI states from the configured multiple TCI states. The DCI may indicate one of the activated multiple TCI states. The DCI may be a UL / DL DCI. The indicated TCI state may apply 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 of this figure, one point may be one TCI state that applies to both UL and DL, or two TCI states that apply to UL and DL respectively.
[0036] At least one of the multiple TCI states configured by the RRC parameters and the multiple TCI states activated by the MAC CE may be referred to as a TCI pool (common TCI pool, joint TCI pool, TCI state pool). The multiple TCI states activated by the MAC CE may be referred to as an active TCI pool (active common TCI pool).
[0037] In the present disclosure, higher layer parameters (RRC parameters) for setting multiple TCI states may be referred to as configuration information for setting multiple TCI states, or simply as "configuration information." Also, in the present disclosure, being instructed to set one of multiple TCI states using DCI may mean receiving indication information instructing one of the multiple TCI states included in DCI, or simply receiving "instruction information."
[0038] In the example of Figure 1B, the RRC parameters configure multiple TCI states (joint common TCI pools) for both DL and UL. The MAC CE may activate multiple TCI states (active TCI pools) from the configured multiple TCI states. Separate active TCI pools for UL and DL may be configured / activated.
[0039] The DL DCI or a new DCI format may select (indicate) one or more (e.g., one) TCI states. The selected TCI state may be applied to one or more (or all) DL channels / RSs. The 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. The UL DCI or a new DCI format may select (indicate) one or more (e.g., one) TCI states. The selected TCI state may be applied to one or more (or all) UL channels / RSs. The UL channels may be PUSCH / SRS / PUCCH. In this way, different DCIs may indicate the UL TCI and the DL DCI separately.
[0040] (TCI status indication) The Rel.17 Unified TCI Framework supports modes 1 to 3 below. <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 configured and activated with a Rel.17 TCI State ID (e.g., tci-StateId_r17) receives DCI format 1_1 / 1_2 providing an indicated TCI state with the Rel.17 TCI State ID for one CC, or receives DCI format 1_1 / 1_2 providing an indicated TCI state with the Rel.17 TCI State ID for all CCs in the same CC list as the CC list configured by simultaneous TCI update list 1 or simultaneous TCI update list 2 (e.g., simultaneousTCI-UpdateList1 or simultaneousTCI-UpdateList2). DCI format 1_1 / 1_2 may or may not be accompanied by a DL assignment if one is available.
[0042] If DCI format 1_1 / 1_2 is not accompanied by a DL assignment, the UE can assume (verify) the following for that DCI: - The CS-RNTI is used to scramble the CRC for the DCI. - The following DCI fields (special fields) are set to the following values: - 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 Dynamic Switch (similar to PDCCH validation for release of DL semi-persistent scheduling (SPS) or UL grant type 2 scheduling).
[0043] The DCI in the above-mentioned mode 2 / mode 3 may be called a beam instruction DCI.
[0044] In Rel.15 / 16, if the UE does not support active BWP change via DCI, the UE ignores the BWP indicator field. A similar behavior is considered for the relationship between Rel.17 TCI state support and the interpretation of the TCI field. If the UE is configured with Rel.17 TCI state, the TCI field will always be present in DCI format 1_1 / 1_2; if the UE does not support TCI update via DCI, the UE will ignore the TCI field.
[0045] In Rel.15 / 16, whether or not a TCI field is present (TCI presence information in DCI, tci-PresentInDCI) is set for each CORESET.
[0046] The TCI field in DCI format 1_1 is 0 bit if the higher 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 shall follow the following actions: <Operation> If the higher layer parameter tci-PresentInDCI is not enabled for the CORESET used for the PDCCH carrying that DCI format 1_1, the UE shall assume that tci-PresentInDCI is not enabled for all CORESETs within the indicated BWP; otherwise, the UE shall assume that tci-PresentInDCI is enabled for all CORESETs within the indicated BWP.
[0047] The TCI field in DCI format 1_2 is 0 bit if the higher layer parameter tci-PresentInDCI-1-2 is not set, otherwise it is 1, 2 or 3 bits determined by the higher layer parameter tci-PresentInDCI-1-2. If the BWP indicator field indicates a BWP other than the active BWP, the UE shall follow the following actions: <Operation> If the upper layer parameter tci-PresentInDCI-1-2 is not set for the CORESET used for the PDCCH carrying that DCI format 1_2, the UE shall assume that tci-PresentInDCI is not enabled for all CORESETs within the indicated BWP; otherwise, the UE shall assume that tci-PresentInDCI-1-2 is set for all CORESETs within the indicated BWP with the same value as tci-PresentInDCI-1-2 set for the CORESET used for the PDCCH carrying that DCI format 1_2.
[0048] 2A shows an example of DCI-based joint DL / UL TCI status indication, where a TCI status ID indicating the joint DL / UL TCI status is associated with the value of the TCI field for joint DL / UL TCI status indication.
[0049] 2B shows an example of a DCI-based separate DL / UL TCI status indication. At least one TCI status ID, indicating a DL-only TCI status or a UL-only TCI status, is associated with a value of the TCI field for the separate DL / UL TCI status indication. In this example, TCI field values 000 to 001 are associated with only one TCI status ID for DL, TCI field values 010 to 011 are associated with only one TCI status ID for UL, and TCI field values 100 to 111 are associated with both one TCI status ID for DL and one TCI status ID for UL.
[0050] (Channel / RS to which the indicated TCI state applies) The indicated TCI state by the MAC CE / DCI may apply to the following channels / RS:
[0051] <pdcch> If followUnifiedTCIState is set for CORESET0, the indicated TCI state applies. Otherwise, the Rel.15 specification applies for that CORESET. That is, CORESET0 follows the TCI state activated by the MAC CE or is QCL'd with SSB. · For CORESETs with index other than 0 with USS / CSS type 3, the indicated TCI state always applies. If a CORESET with index other than 0, with at least a CSS other than CSS type 3, is configured to follow the unified TCI state, the indicated TCI state applies. Otherwise, the configured TCI state for that CORESET applies to that CORESET.
[0052] <pdsch> · The indication TCI state always applies to all UE-dedicated PDSCHs. For a non-UE-dedicated PDSCH (a PDSCH scheduled by a DCI in a CSS), if followUnifiedTCIState is configured (for the CORESET of the PDCCH that schedules that PDSCH), the indicated TCI state may apply. Otherwise, the configured TCI state for that PDSCH applies to that PDSCH. If followUnifiedTCIState is not configured for a PDSCH, whether a non-UE-dedicated PDSCH follows the indicated TCI state may depend on whether followUnifiedTCIState is configured for the CORESET used to schedule that PDSCH.
[0053] <csi-rs> For an A-CSI-RS for CSI acquisition or beam management, if followUnifiedTCIState is set (for the CORESET of the PDCCH that triggers that A-CSI-RS), the indicated TCI state applies. For other CSI-RSs, the configured TCI state for that CSI-RS applies.
[0054] <pucch> · For all dedicated PUCCH resources, the indicated TCI state always applies.
[0055] <pusch> For dynamic / configured grant PUSCH, the indicated TCI state is always applied.
[0056] <srs> - When the SRS resource set for A-SRS for beam management and A / SP / P-SRS for codebook (CB) / non-codebook (NCB) / antenna switching is configured to follow the unified TCI state, the indicated TCI state applies. For other SRS, the configured TCI state in the SRS resource set applies.
[0057] (analysis) Scheduling requests (SRs) or SR resources (hereinafter simply referred to as SRs) are code division multiplexed (CDM) between UEs. For example, SRs between multiple UEs are CDM multiplexed in the same resource (e.g., PRB). In this case, the SR transmission occasions corresponding to the multiple UEs may be set to be the same.
[0058] The network (or base station) configures periodic SR transmission opportunities (e.g., every 40 ms) to reduce the delay when the UE requests resources for UL data (e.g., UL-SCH / PUSCH). When an SR is triggered, the UE controls the SR transmission using the configured transmission opportunities (e.g., SR resources / PUCCH resources).
[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 a single beam at a time under typical UL transmission assumptions. 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) for UEs with the same UL TCI state / Rx receive beam. This allows the network to properly receive SRs from multiple UEs simultaneously based on a single receive beam / TCI state.
[0060] In an analog / hybrid beamforming architecture, multiple SR transmission opportunities from different UEs may be aligned to the same base station receive beam / TCI state in the same set of OFDM symbols (see Figure 3).
[0061] 3 shows a case where SR transmission opportunities for UE#1 to UE#3 are set to the same OFDM symbol set, SR transmission opportunities for UE#4 to UE#5 are set to the same OFDM symbol set, and SR transmission opportunities for UE#(n-1) to UE#n are set to the same OFDM symbol set. The base station receives SRs (or PUCCHs) transmitted from UE#1 to UE#3 using UL receiving beam 1, receives SRs (or PUCCHs) transmitted from UE#4 to UE#5 using UL receiving beam 2, and receives SRs (or PUCCHs) transmitted from UE#(n-1) to UE#n using UL receiving beam K.
[0062] In a given SR transmission (or SR transmission opportunity) consisting of multiple UEs (or UE lists), if the beam direction of one SR resource (e.g., the network's UL receiving beam) is changed, the beams will no longer be aligned.
[0063] In current wireless communication systems, the only way to readjust / realign SR resources is to reconfigure SR resources for UEs via RRC. However, the reconfiguration procedure via RRC is slow and increases the overhead of RRC reconfiguration, making it difficult to support frequent beam changes.
[0064] Incidentally, when a unified TCI state (or an instruction TCI state) is set / applied, the transmission beam / TCI state of the SR (or the PUCCH used for SR transmission) is updated / changed individually for each UE by MAC CE / DCI.
[0065] When the transmission beam / TCI state of SR is updated individually for each UE, a case is also assumed in which multiple UEs transmit SR (or PUCCH) using the same resource (e.g., PRB) and each apply a different transmission beam / TCI state. In this case, the base station will not be able to receive the PRB corresponding to the SR (or PUCCH) based on one reception beam / TCI state at a certain transmission opportunity.
[0066] Figure 4 shows an example of a case 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 using the same UL receive beam (or base station beam) by network scheduling. In other words, the same transmit timing (or SR transmission opportunity) is set for one or more UEs that apply the same beam / TCI state to SR, and they are CDM multiplexed.
[0067] In this case, it is possible that the TCI status of only some UEs (e.g., UE#1) may be updated (e.g., updated from reception beam 1 to reception beam 2) due to the movement of the UEs, etc. In this case, the base station may not be able to simultaneously receive all SRs (here, SRs of UE#1 to UE#3) based on a single reception beam.
[0068] For example, when SR transmission is configured by a UE list (e.g., a list of UEs configured to the same OFDM symbol set), if the beam direction of one SR resource in the UE list (e.g., the network's UL reception beam) is changed, the network reception beam for the UE will no longer be aligned. If such beam deviation (or beam misalignment) occurs, SR link failure may occur, resulting in degradation of communication quality.
[0069] Therefore, the present inventors have studied a method for appropriately performing UL transmission even when the beam / TCI state of UL transmission (e.g., SR / PUCCH) is updated for each UE, and have come up with the idea for this embodiment.
[0070] Hereinafter, embodiments according to the present disclosure will be described in detail with reference to the drawings. Wireless communication methods according to the embodiments may be applied independently or in combination.
[0071] In the following embodiment, SR transmission will be described as an example, but the channels / signals to which the embodiment can be applied are not limited to this, and the embodiment may be applied to other channels / signals (for example, HARQ-ACK (or ACK / NACK), PUCCH, PUSCH, SRS). In the present disclosure, SR may be interchangeable with SR resource, SR transmission opportunity, PUCCH, PUCCH resource, and PUCCH transmission opportunity.
[0072] (Various reading changes) In the present disclosure, words enclosed in "()" in a sentence may indicate an explanation of the immediately preceding wording (for example, an explanation of spelling), a paraphrase, a specific example, a supplementary explanation, etc. Also, in the present disclosure, words enclosed in "[ ]" in a sentence may be interpreted including the meaning of the entire sentence, or may be interpreted excluding the meaning of the entire sentence (ignoring the meaning of the entire sentence). Note that "()" and "[ ]" may also be used for purposes / meanings other than those mentioned above.
[0073] In the present disclosure, "A / B" and "at least one of A and B" may be interpreted interchangeably. Also, in the present disclosure, "A / B / C" may mean "at least one of A, B, and C."
[0074] In the present disclosure, terms such as notify, activate, deactivate, indicate (or indicate), select, configure, update, and determine may be interchangeable. In the present disclosure, terms such as support, control, controllable, operate, and operate may be interchangeable.
[0075] In the present disclosure, Radio Resource Control (RRC), RRC parameters, RRC messages, higher layer parameters, fields, information elements (IEs), settings, etc. may be interchangeable. In the present disclosure, Medium Access Control (MAC) control elements (CEs), update commands, activation / deactivation commands, etc. may be interchangeable.
[0076] In the present disclosure, the higher layer signaling may be, for example, any one of Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information, other messages (e.g., messages from the core network such as positioning protocol (e.g., NR Positioning Protocol A (NRPPa) / LTE Positioning Protocol (LPP)) messages), or a combination thereof.
[0077] In the present disclosure, MAC signaling may use, for example, a MAC Control Element (MAC CE), a MAC Protocol Data Unit (PDU), etc. Broadcast information may be, for example, a Master Information Block (MIB), a System Information Block (SIB), Remaining Minimum System Information (RMSI), Other System Information (OSI), etc.
[0078] In the present disclosure, physical layer signaling may be, for example, Downlink Control Information (DCI), Uplink Control Information (UCI), and the like.
[0079] In this disclosure, the terms drop, abort, cancel, puncture, rate match, postpone, do not transmit, etc. may be read interchangeably.
[0080] (Wireless communication method) First Embodiment The first embodiment relates to an example of a method for controlling SR transmission (for example, transmission conditions / parameters) based on an indication / update of a TCI state.
[0081] The UE may receive information about the SR transmission conditions through higher layer parameters. The information about the SR transmission conditions may include, for example, information about a periodicity / transmission opportunity / UL resource (e.g., SR resource / PUCCH resource), etc. When an SR is triggered, the UE controls the SR transmission based on the information about the SR transmission conditions.
[0082] The transmission opportunity of the UL resource (e.g., SR resource / PUCCH resource) reserved or configured for SR may be changed / updated in accordance with the instruction / update of the TCI state. For example, when the TCI state is instructed or when the UE updates the TCI state based on the instructed TCI state, the UE may control to change / update the transmission opportunity corresponding to SR based on a predetermined condition (e.g., a predetermined offset) simultaneously with the update of the TCI state. The instruction of the TCI state may be instructed from the network (or base station) to the UE by MAC CE / DCI.
[0083] By supporting modification / updating of transmission opportunities for SR resources / PUCCH resources in conjunction with TCI state updates (e.g., simultaneously with TCI state updates), it is possible to balance dynamic beam / TCI state updates with network resource overhead.
[0084] The predetermined condition (e.g., the predetermined offset) may be a time-domain offset. For example, a unified TCI state (e.g., a joint / UL TCI state) may be associated with a time-domain offset. In the present disclosure, the time-domain offset may be defined at a slot level (or in units of slots), a system frame number level, a millisecond level, or any combination thereof.
[0085] The time domain offset (e.g., slot-level offset) may be configured by a new RRC parameter (e.g., slotOffset). As an example, the time domain offset may be configured within a predetermined range (e.g., 0 to 639) by an RRC parameter. In this case, it may be configured / supported by a mechanism similar to that of the existing RRC parameter (e.g., periodicityAndOffset) related to a preset periodicity and offset.
[0086] When a certain TCI state is indicated / provided for a PUCCH resource used for transmitting an SR, a time domain offset associated with the 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 certain TCI state is indicated / provided, the UE may control to apply the time domain offset based on the application time of the TCI state.
[0087] In a unified TCI framework (e.g., when a unified TCI state is supported or configured), one 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 SR based on information about the pre-configured SR transmission condition (e.g., periodicity / transmission opportunity / UL resource (e.g., SR resource / PUCCH resource)) and the time domain offset corresponding to the indicated TCI state.
[0088] An example of changing an SR transmission opportunity in accordance with an update of the beam / TCI state is shown in Fig. 5. Fig. 5 shows a case in which a different TCI state (e.g., a second TCI state) is instructed to UE#1, to which a first TCI state / SR transmission opportunity is set, and the TCI state used for SR transmission is updated.
[0089] Before the second TCI state is indicated, UE#1 transmits an SR based on the first TCI state / SR transmission opportunity. After the second TCI state is indicated, UE#1 may control the transmission of an SR using an SR transmission opportunity determined / derived based on the time domain offset associated with the second TCI state.
[0090] This makes it possible to adjust the timing of transmitting an SR (e.g., an SR transmission opportunity, etc.) by adding a time domain offset to the SR transmission timing determined based on the SR resource settings (e.g., a period, etc.) in existing systems.
[0091] 5 shows a case where the time domain offset is set to be changed / shifted to the same transmission opportunity or resource as the transmission opportunity of other UEs that apply the updated second TCI state #2 (or CDM multiplexed with the SR of other UEs #4 and #5). In this way, by setting the time domain offset to be the same SR transmission opportunity or resource as the SR transmission opportunity of other UEs #4 and #5 that apply the same TCI state #2, it is possible to effectively utilize resources.
[0092] Note that the setting of the time domain offset is not limited to this. It may be supported to set the time domain offset so that the transmission opportunity or resource is changed / shifted to a different one from the transmission opportunities of other UEs #4 and #5 to which the updated second TCI state #2 is applied (see FIG. 6). This makes it possible to more flexibly adjust the SR transmission opportunity after the change of the TCI state of UE #1 and to suppress the SR transmission delay of UE #1.
[0093] In this way, when a unified TCI state (e.g., a joint / UL TCI state) is indicated / provided for a PUCCH resource used for SR transmission, a time domain offset associated with the TCI state may be applied to derive an SR transmission opportunity. When a unified TCI state (e.g., a joint / UL TCI state) is indicated / provided, the UE may control SR transmission (e.g., determine an SR transmission opportunity) using the updated TCI state based on the time domain offset associated with the TCI state.
[0094] This allows the SR transmission timing (or transmission opportunity) to be flexibly changed in accordance with the update of the TCI state. By changing the SR transmission opportunity when the TCI state is updated, the base station can properly receive one or more SRs using one receive beam in the same set of OFDM symbols. This also reduces the need for RRC reconfiguration to respond to changes in the beam / TCI state (e.g., changing the SR resource / SR transmission opportunity), thereby suppressing an increase in network overhead.
[0095] When a PUCCH resource is applied to the transmission of an SR, a time offset or a time-domain offset may be provided in a TCI state (e.g., TCI-State or TCI-UL-State) corresponding to the PUCCH resource associated with the SR configuration. 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 (for example, transmission conditions / parameters) based on an indication / update of the TCI state.
[0097] The control of changing the transmission opportunity of the SR resource / PUCCH resource (e.g., applying a time domain offset) in association with updating the TCI state (e.g., simultaneously with updating the TCI state) may be performed only under specific conditions. The specific conditions may be when specific RRC parameters are set, when a unified TCI state is set / applied, or when a time domain offset is set.
[0098] An RRC parameter related to the time domain offset may be added to the RRC parameters / information elements related to the TCI state (for example, TCI-State or TCI-UL-State).
[0099] For example, as shown in FIG. 7, one or both of 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}) may be set in the TCI-State. Although FIG. 7 shows a case where both the time domain slot offset and the time domain symbol offset are included, only one of them may be set. Furthermore, the values of the time domain slot offset and the time domain symbol offset are merely examples, and the present invention is not limited to these. Furthermore, the positions at which the time domain slot offset and the time domain symbol offset are added in the RRC parameters related to the TCI state (here, the TCI-State) are merely examples, and the present invention is not limited to these.
[0100] As shown in FIG. 8, one or both of 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}) may be configured in the TCI-UL-State. Although FIG. 8 shows a case where both the time domain slot offset and the time domain symbol offset are included, only one of them may be configured. Furthermore, the values of the time domain slot offset and the time domain symbol offset are merely examples, and are not limited to these. Furthermore, the positions at which the time domain slot offset and the time domain symbol offset are added in the RRC parameters related to the TCI state (here, TCI-UL-State) are merely examples, and are not limited to these.
[0101] The configuration of the RRC parameters related to the time domain offset may be limited to when the unified TCI state is configured / applied, or may be configured regardless of whether the unified TCI state is configured / applied or not.
[0102] <<Case 2-1>> A case where a time domain offset is configured in an indicated TCI state applied to an SR resource (or a PUCCH resource) may be supported. In this case, the time domain offset may be applied to a slot / symbol determined / derived by a period or the like configured as an SR resource (or a PUCCH resource).
[0103] For example, an SR may be transmitted at a slot / symbol index determined / derived by adding (adding) or subtracting (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 manner as in existing systems. Whether to add (add) or subtract (subtract) the slot / symbol index set by the time domain offset may be defined in the specifications or may be set by RRC, etc.
[0104] <<Case 2-2>> A case in which a time domain offset is not configured in the indicated TCI state applied to the SR resource (or PUCCH resource) may be supported. In this case, at least one of the following options 2-1 and 2-2 may be applied.
[0105] Option 2-1 An SR may be transmitted at a slot / symbol index determined / derived by adding (adding) or subtracting (subtracting) the slot / symbol index of a time domain offset (e.g., time domain offset = 0) to the slot / symbol index determined / derived by the periodicity set as the SR resource. The slot / symbol index determined by the periodicity set as the SR resource may be determined in the same manner as in existing systems. Whether to add (add) or subtract (subtract) the slot / symbol index set by the time domain offset may be defined in the specifications or may be set by RRC, etc.
[0106] Option 2-2 The SR may be transmitted at a slot / symbol index determined / derived by the periodicity configured as the SR resource.
[0107] <<Case 2-3>> A case may be supported in which a time domain offset is configured in a TCI state (e.g., an indicated TCI state) 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). That is, the time domain offset may not be used to determine the transmission / reception resources of the other channel / RS. For example, when a time domain offset is configured in a certain TCI state (a TCI state having a predetermined ID), the UE may control so that the time domain offset is used when the TCI state is used for SR transmission (or PUCCH transmission) and not used when the TCI state is used for other channels / RS.
[0108] <<RRC parameters for time domain offset>> The RRC parameters for the time domain offset may be set in the RRC parameters for the TCI state (eg, TCI-State or TCI-UL-State).
[0109] In this case, the time domain offset may be set by one or more (e.g., a combination of two or more) of a slot index, a symbol index, or an absolute time (e.g., ms). The slot index / symbol index may be a value assuming a predetermined subcarrier spacing (SCS) (or a value based on the predetermined SCS), or may be set for each SCS.
[0110] The predetermined SCS may be an SCS in a bandwidth portion (BWP) in which an RRC parameter related to the TCI state (e.g., TCI-State or TCI-UL-State) is set. Alternatively, it may be an SCS in a BWP in which an SR (or a PUCCH used for SR transmission) is set. By determining an SCS that serves as a 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, the BWP in which the RRC parameters related to the TCI state (e.g., TCI-State or TCI-UL-State) are configured may support the case where it becomes one CC among the multiple CCs (e.g., CC-common TCI state configuration).
[0112] In CC common TCI state configuration, the UE may determine the TCI state (or QCL type) in a BWP / CC in which the RRC parameters related to the TCI state are not configured, based on the RRC parameters related to the TCI state configured in the BWP of the one CC (reference BWP / CC). In this case, a case in which the SCS of the SR to which the unified TCI state applies is different from the SCS of the BWP / CC to which the RRC parameters related to the TCI state are configured may be supported. Therefore, it may be defined / configured as to which SCS the slot index / symbol index indicated by the time domain offset corresponds to.
[0113] <Third embodiment> The third embodiment relates to another example of a method for controlling SR transmission based on indication / update of the TCI state.
[0114] In the first embodiment / second embodiment, a case where a time domain offset is associated with a unified TCI state (or an indicated TCI state) is described, but this is not limiting. SR transmission may be controlled by using an SR resource (or a PUCCH resource) corresponding to a different SR resource ID for each unified TCI state (or indicated TCI state). In the present 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 the present disclosure, the nth SR resource #n may be interpreted as the nth PUCCH resource #n, the nth SR transmission opportunity #n, or the nth PUCCH transmission opportunity #n.
[0116] The UE may be controlled to transmit an SR using the first SR resource #1 when the indicated (or updated) TCI state is the first TCI state #1, and to transmit an SR using the nth SR resource #n when the indicated (or updated) TCI state is the nth TCI state #n.
[0117] The correspondence between each TCI state (for example, a TCI state ID) and an SR resource ID (or a PUCCH resource ID, an SR transmission opportunity ID, or a PUCCH transmission opportunity ID) may be set by an RRC parameter or may be defined in a specification.
[0118] In this way, by associating the TCI state with the SR resource ID, it becomes possible to specify a different SR resource depending on the specified TCI state, which makes it possible to flexibly adjust the SR transmission timing even when the TCI state is changed / updated.
[0119] <Variations> The first embodiment / second embodiment may be applied only when a predetermined RRC parameter (e.g., a time domain offset set in an RRC parameter related to a TCI state) is set. The third embodiment may be applied only when a predetermined RRC parameter (e.g., an association between a TCI state and an SR resource ID) is set.
[0120] The first embodiment / second embodiment / third embodiment may be applied only when a predetermined UE capability is reported.
[0121] The first embodiment, the second embodiment, and the third embodiment may be applied to any or all of predetermined SRs (or SRs for predetermined purposes). The predetermined SRs (or SRs for predetermined purposes) may be a normal SR for requesting resources for UL data (UL-SCH) or an SR for BFR.
[0122] The first embodiment / second embodiment may be configured for each SR resource, or may be switched depending on whether or not a time domain offset is configured in the indication TCI state applied to each SR resource.
[0123] The first embodiment / second embodiment / third embodiment are not limited to SR (or PUCCH for SR transmission) and may be applied to other channels / signals. For example, the first embodiment / second embodiment may be applied to PUCCH transmission in UE-initiated beam reporting (UEIBR). Alternatively, they may be applied to other UL channels / signals.
[0124] In the first embodiment / second embodiment, the offset applied to the SR resource / PUCCH resource / SR transmission opportunity / PUCCH transmission opportunity in response to the indication / update of the TCI state is not limited to the time domain offset, and other offsets (e.g., frequency domain offsets) may be applied instead of or in addition to the time domain offset.
[0125] In the first and second embodiments, the case where the time domain offset is associated with the updated TCI state is described, but this is not limiting. The time domain offset may be explicitly indicated from the base station to the UE. For example, information about the time domain offset may be included in the DCI / MAC CE indicating the TCI state and indicated to the UE. As an example, multiple time domain offsets may be configured in advance using RRC parameters, and the DCI / MAC CE indicating the TCI state may indicate which time domain offset to apply. This enables the base station to dynamically control the SR transmission timing.
[0126] Alternatively, the DCI / MAC CE indicating the TCI state may include information related to the SR transmission opportunity / SR transmission period and indicate it to the UE. Alternatively, the DCI / MAC CE indicating the TCI state may include information indicating whether to apply a time domain offset and indicate it to the UE.
[0127] <Supplementary> <<Notification of Information to UE>> The notification of any information from the [Network (NW) (e.g., Base Station (BS))] to the UE in the above-described embodiment (in other words, the reception of any information from the BS by the UE) may be performed using physical layer signaling (e.g., DCI), upper layer signaling (e.g., RRC signaling, MAC CE), a specific signal / channel (e.g., PDCCH, PDSCH, reference signal), or a combination thereof.
[0128] When the above notification is performed by the MAC CE, the MAC CE may be identified by including a new logical channel ID (LCID) not defined in the existing standard in the MAC sub-header.
[0129] When the above notification is performed by the DCI, the above notification may be performed by a specific field of the DCI, a radio network temporary identifier (RNTI) used for scrambling the cyclic redundancy check (CRC) bits assigned to the DCI, the format of the DCI, etc.
[0130] Also, the notification of any information to the UE in the above-described embodiment may be performed periodically, semi-persistently, or aperiodically.
[0131] <<Notification of Information from UE>> In the above-described embodiments, notification of any information from the UE [to the NW] (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] When the notification is performed by a MAC CE, the MAC CE may be identified by including a new LCID in the MAC subheader that is not defined in existing standards.
[0133] If the notification is performed by UCI, the notification may be transmitted using PUCCH or PUSCH.
[0134] Furthermore, any information in the above-described embodiments may be notified from the UE periodically, semi-persistently, or aperiodically.
[0135] <<Application of each embodiment>> In a UE / BS, the specific process / operation / control / assumption / information(s) of at least one of the above-described embodiments may be applied (used) when one or more of the following conditions are met: Upper layer parameters indicating the above specific processing / operation / control / assumment / information are set. The specific processing / action / control / assumption / information is determined based on relevant upper layer parameters; The above specific processes / actions / controls / assumptions / information are specified / activated / triggered by MAC CE / DCI / UCI / resources / channels / RS, Reporting or supporting specific UE capabilities indicating (or relating to) the above specific processes / actions / controls / assumptions / information; · The application of the above specific processing / action / control / assumption / information is judged based on specific conditions.
[0136] The specific UE capabilities may indicate at least one of the following: Supporting the above specific processes / actions / controls / assumptions / information (e.g., time domain offsets); Support for changing / updating the transmission occasion of SR resources / PUCCH resources; Supports setting time domain offsets; Support for unified TCI state and time domain offset association.
[0137] Furthermore, the above-mentioned specific UE capability may be a capability that is applied across all frequencies (commonly regardless of frequency), or may be a capability for each frequency (e.g., one or a combination of a cell, band, band combination, BWP, component carrier, etc.), or may be a capability for each frequency range (e.g., Frequency Range 1 (FR1), FR2, FR3, FR4, FR5, FR2-1, FR2-2), or may be a capability for each subcarrier spacing (SubCarrier Spacing (SCS)), or may be a capability for each Feature Set (FS) or Feature Set Per Component-carrier (FSPC).
[0138] Furthermore, the specific UE capability may be a capability that is applied across all duplexing methods (commonly regardless of the duplexing method), or may be a capability for each duplexing method (for example, Time Division Duplex (TDD) or Frequency Division Duplex (FDD)).
[0139] If the above conditions are not met, the UE / BS may follow the behavior specified in existing 3GPP releases.
[0140] (Addendum) The following inventions are added regarding one embodiment of the present disclosure. [Appendix 1] a receiver for receiving information regarding transmission conditions of a scheduling request and information indicating a unified transmission configuration indication (TCI) state; A terminal having a control unit that controls transmission of a scheduling request based on information regarding the transmission conditions and a time domain offset when updating a TCI state to be applied to an uplink based on information indicating the unified TCI state. [Appendix 2] The terminal according to Supplementary Note 1, wherein the value of the time domain offset is set in association with the indicated unified TCI state. [Appendix 3] 3. The terminal according to claim 1, wherein the value of the time domain offset is included in higher layer parameters relating to the unified TCI state. [Appendix 4] 4. The terminal according to claim 1, wherein if a time domain offset is not set for a unified TCI state applied to the scheduling request, the control unit controls transmission of the scheduling request based on information about the transmission conditions.
[0141] (wireless communication system) The configuration of a wireless communication system according to an embodiment of the present disclosure will be described below. In this wireless communication system, communication is performed using any one of the wireless communication methods according to the above embodiments of the present disclosure or a combination thereof.
[0142] 9 is a diagram illustrating an example of a schematic configuration of a wireless communication system according to an embodiment. The wireless communication system 1 (which may be simply referred to as system 1) may be a system that realizes communication using Long Term Evolution (LTE), 5th generation mobile communication system New Radio (5G NR), or the like, which are specified by the Third Generation Partnership Project (3GPP).
[0143] The wireless communication system 1 may also support dual connectivity between multiple Radio Access Technologies (RATs) (Multi-RAT Dual Connectivity (MR-DC)). MR-DC may include dual connectivity between LTE (Evolved Universal Terrestrial Radio Access (E-UTRA)) and NR (E-UTRA-NR Dual Connectivity (EN-DC)), dual connectivity between NR and LTE (NR-E-UTRA Dual Connectivity (NE-DC)), etc.
[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 in which both the MN and the SN are NR base stations (gNBs) (NR-NR Dual Connectivity (NN-DC))).
[0146] The wireless communication system 1 may include a base station 11 that forms a macrocell C1 with a relatively wide coverage, and base stations 12 (12a-12c) that are located within the macrocell C1 and form small cells C2 that are smaller than the macrocell C1. A user terminal 20 may be located within at least one of the cells. The location, number, shape, size, etc. of each cell and user terminal 20 are not limited to the embodiment shown in the figure. Hereinafter, when there is no need to distinguish between the base stations 11 and 12, they will be collectively referred to as base station 10.
[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 may be formed by multiple antennas / base stations 10. One [virtual] cell (which may be called, for example, a super cell) may be composed of multiple [virtual] cells (which may be called, for example, sub-cells). A super cell may correspond to a cell whose physical range is fixed, and a sub-cell may correspond to a cell whose physical range varies semi-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 a first frequency band (Frequency Range 1 (FR1)) and a second frequency band (Frequency Range 2 (FR2)). The macro cell C1 may be included in FR1, and the small cell C2 may be included in FR2. For example, FR1 may be a frequency band of 6 GHz or less (sub-6 GHz), and FR2 may be a frequency band above 24 GHz (above-24 GHz). Note that the frequency bands and definitions of FR1 and FR2 are not limited to these, and for example, FR1 may be a frequency band higher than FR2.
[0150] Furthermore, the user terminal 20 may perform communication using at least one of Time Division Duplex (TDD) and Frequency Division Duplex (FDD) in each CC.
[0151] The multiple base stations 10 may be connected by wire (for example, optical fiber conforming to the Common Public Radio Interface (CPRI), an X2 / Xn interface, etc.) or wirelessly (for example, NR communication). For example, when NR communication is used as a backhaul between the base stations 11 and 12, the base station 11 corresponding to the upper station may be called an Integrated Access Backhaul (IAB) donor, and the base station 12 corresponding to the relay station (relay) may be called an IAB node.
[0152] The base station 10 may be connected to the core network 30 directly or via another base station 10. The core network 30 may include, for example, at least one of an Evolved Packet Core (EPC), a 5G Core Network (5GCN), a Next Generation Core (NGC), and the like.
[0153] The core network 30 may include network functions (NFs) such as a User Plane Function (UPF), an Access and Mobility management Function (AMF), a Session Management Function (SMF), a Unified Data Management (UDM), an Application Function (AF), a Data Network (DN), a Location Management Function (LMF), and an Operation, Administration and Maintenance (Management) (OAM). Note that a single network node may provide multiple functions. Furthermore, communication with an external network (e.g., the Internet) may be performed via the DN.
[0154] The user terminal 20 may be a terminal compatible with at least one of communication methods such as LTE, LTE-A, and 5G.
[0155] An Orthogonal Frequency Division Multiplexing (OFDM)-based radio access scheme may be used in the radio communication system 1. For example, Cyclic Prefix OFDM (CP-OFDM), Discrete Fourier Transform Spread OFDM (DFT-s-OFDM), Orthogonal Frequency Division Multiple Access (OFDMA), Single Carrier Frequency Division Multiple Access (SC-FDMA), or the like may be used in at least one of the downlink (DL) and uplink (UL).
[0156] The radio access scheme may also be called a waveform. Note that in the wireless communication system 1, other radio access schemes (for example, other single-carrier transmission schemes, other multi-carrier transmission schemes) may be used as the UL and DL radio access schemes.
[0157] In the wireless communication system 1, a downlink shared channel (Physical Downlink Shared Channel (PDSCH)) shared by each user terminal 20, a broadcast channel (Physical Broadcast Channel (PBCH)), a downlink control channel (Physical Downlink Control Channel (PDCCH)), etc. may be used as the downlink channel.
[0158] Furthermore, in the wireless communication system 1, an uplink shared channel (Physical Uplink Shared Channel (PUSCH)) shared by each user terminal 20, an uplink control channel (Physical Uplink Control Channel (PUCCH)), a random access channel (Physical Random Access Channel (PRACH)), etc. may be used as an uplink channel.
[0159] The PDSCH transmits user data, higher layer control information, System Information Block (SIB), etc. The PUSCH may transmit user data, higher layer control information, etc. Furthermore, the PBCH may transmit Master Information Block (MIB).
[0160] Lower layer control information may be transmitted by the PDCCH. The lower layer control information may include, for example, Downlink Control Information (DCI) including scheduling information for at least one of the PDSCH and the PUSCH.
[0161] Note that the DCI for scheduling the PDSCH may be referred to as a DL assignment, a DL DCI, etc., and the DCI for scheduling the PUSCH may be referred to as an UL grant, a UL DCI, etc. Note that the PDSCH may be interpreted as DL data, and the PUSCH may be interpreted as UL data.
[0162] A control resource set (CORESET) and a search space may be used to detect the PDCCH. The CORESET corresponds to resources to search for DCI. The search space corresponds to a search region and a search method for PDCCH candidates. One CORESET may be associated with one or more search spaces. The UE may monitor a CORESET associated with a certain search space based on the search space configuration.
[0163] One search space may correspond to PDCCH candidates corresponding to one or more aggregation levels. One or more search spaces may be called a search space set. Note that the terms "search space," "search space set," "search space setting," "search space set setting," "CORESET," "CORESET setting," etc. in the present disclosure may be read interchangeably.
[0164] The PUCCH may transmit uplink control information (UCI) including at least one of channel state information (CSI), acknowledgement information (which may be called, for example, Hybrid Automatic Repeat reQuest ACKnowledgement (HARQ-ACK), ACK / NACK, etc.), and scheduling request (SR). The PRACH may transmit a random access preamble for establishing a connection with a cell.
[0165] In the present disclosure, downlink, uplink, etc. may be expressed without adding "link." Also, various channels may be expressed without adding "Physical" to the beginning.
[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, a cell-specific reference signal (CRS), a channel state information reference signal (CSI-RS), a demodulation reference signal (DMRS), a positioning reference signal (PRS), a phase tracking reference signal (PTRS), etc. may be transmitted as DL-RS.
[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 the SS (PSS, SSS) and the PBCH (and DMRS for the PBCH) may be referred to as an SS / PBCH block, an SS Block (SSB), or the like. Note that the SS, SSB, and the like may also be referred to as reference signals.
[0168] Furthermore, in the wireless communication system 1, a sounding reference signal (SRS), a demodulation reference signal (DMRS), etc. may be transmitted as an uplink reference signal (UL-RS). Note that the DMRS may also be called a user equipment-specific reference signal (UE-specific reference signal).
[0169] (base station) 10 is a diagram showing an example of the configuration of a base station according to an embodiment. The base station 10 includes a control unit 110, a transceiver unit 120, a transceiver antenna 130, and a transmission line interface 140. Note that the base station may include one or more of each of the control unit 110, the transceiver unit 120, the transceiver antenna 130, and the transmission line interface 140.
[0170] In this example, the functional blocks of the characteristic parts of the present embodiment are mainly shown, and it may be assumed that the base station 10 also has other functional blocks necessary for wireless communication. Some of the processing of each unit described below may be omitted.
[0171] The control unit 110 performs overall control of the base station 10. The control unit 110 can be configured from a controller, a control circuit, and the like that are explained based on common understanding in the technical field to which the present disclosure relates.
[0172] The control unit 110 may control signal generation, scheduling (e.g., resource allocation, mapping), etc. The control unit 110 may control transmission and reception using the transceiver unit 120, the transceiver antenna 130, and the transmission path interface 140, measurement, etc. The control unit 110 may generate data to be transmitted as signals, control information, sequences, etc., and transfer them to the transceiver unit 120. The control unit 110 may perform call processing (setting up, releasing, etc.) of communication channels, status management of the base station 10, management of radio resources, etc.
[0173] The transceiver unit 120 may include a baseband unit 121, a radio frequency (RF) unit 122, and a measurement unit 123. The baseband unit 121 may include a transmission processing unit 1211 and a reception processing unit 1212. The transceiver unit 120 may be configured with a transmitter / receiver, an RF circuit, a baseband circuit, a filter, a phase shifter, a measurement circuit, a transceiver circuit, etc., which are described based on common understanding in the technical field related to the present disclosure.
[0174] The transmitting / receiving unit 120 may be configured as an integrated transmitting / receiving unit, or may be composed of a transmitting unit and a receiving unit. The transmitting unit may be composed of a transmission processing unit 1211 and an RF unit 122. The receiving unit may be composed of a reception processing unit 1212, an RF unit 122, and a measurement unit 123.
[0175] The transmitting and receiving antenna 130 can be configured from an antenna described based on common understanding in the technical field to which the present disclosure pertains, such as an array antenna.
[0176] The transceiver 120 may transmit the above-mentioned downlink channel, synchronization signal, downlink reference signal, etc. The transceiver 120 may receive the above-mentioned uplink channel, uplink reference signal, etc.
[0177] The transceiver 120 may form at least one of a transmission beam and a reception beam using digital beamforming (for example, precoding), analog beamforming (for example, phase rotation), or the like.
[0178] The transceiver 120 (transmission processing unit 1211) may perform Packet Data Convergence Protocol (PDCP) layer processing, Radio Link Control (RLC) layer processing (e.g., RLC retransmission control), Medium Access Control (MAC) layer processing (e.g., HARQ retransmission control), etc. on data, control information, etc. obtained from the control unit 110, and generate a bit string to be transmitted.
[0179] The transceiver 120 (transmission processor 1211) may perform transmission processing such as channel coding (which may include error correction coding), modulation, mapping, filtering, Discrete Fourier Transform (DFT) processing (if necessary), Inverse Fast Fourier Transform (IFFT) processing, precoding, and digital-to-analog conversion on the bit string to be transmitted, and output a baseband signal.
[0180] The transmitting / receiving unit 120 (RF unit 122) may perform modulation to a radio frequency band, filtering, amplification, etc. on the baseband signal, and transmit the radio frequency band signal via the transmitting / receiving antenna .
[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 .
[0182] The transceiver 120 (reception processing unit 1212) may apply reception processing such as analog-to-digital conversion, Fast Fourier Transform (FFT) processing, Inverse Discrete Fourier Transform (IDFT) processing (if necessary), filtering, demapping, demodulation, decoding (which may include error correction decoding), MAC layer processing, RLC layer processing, and PDCP layer processing to the acquired baseband signal, thereby acquiring user data, etc.
[0183] The transceiver 120 (measurement unit 123) may perform measurements on the received signal. For example, the measurement unit 123 may perform Radio Resource Management (RRM) measurements, Channel State Information (CSI) measurements, etc. based on the received signal. The measurement unit 123 may measure received power (e.g., Reference Signal Received Power (RSRP)), received quality (e.g., Reference Signal Received Quality (RSRQ), Signal to Interference plus Noise Ratio (SINR), Signal to Noise Ratio (SNR)), signal strength (e.g., Received Signal Strength Indicator (RSSI)), propagation path information (e.g., CSI), etc. The measurement results may be output to the control unit 110.
[0184] The transmission path interface 140 may transmit and receive signals (backhaul signaling) between devices included in the core network 30 (e.g., network nodes providing NFs), 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] The transmitting section and receiving section of the base station 10 in the present disclosure may be configured by at least one of the transmitting / receiving section 120, the transmitting / receiving antenna 130, and the transmission path interface 140.
[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 perform RF processing (digital beamforming, digital-to-analog conversion, analog beamforming, etc.) and lower-level functions of the physical layer (precoding, IFFT, FFT, etc.). The DU may perform higher-level functions of the physical layer (coding to resource element mapping, etc.), MAC layer functions, and RLC layer functions. The CU may perform PDCP layer, Service Data Adaptation Protocol (SDAP) layer, and RRC layer functions.
[0187] In the present disclosure, the base station 10 may include a single device that implements all of the functions of the RU, DU, and CU, or may include multiple devices that each implement some of the functions of the RU, DU, and CU and are connected to each other. In the present disclosure, the base station 10 may be interchangeably read as RU / DU / CU.
[0188] The transceiver 120 may transmit information regarding the transmission conditions of the scheduling request and information indicating the unified transmission configuration indication (TCI) status.
[0189] When updating the TCI state to be applied to the uplink based on the information indicating the unified TCI state, the control unit 110 may control reception of a scheduling request based on the information on the transmission condition and the time domain offset.
[0190] (user terminal) 11 is a diagram showing an example of the configuration of a user terminal according to one embodiment. The user terminal 20 includes a control unit 210, a transceiver unit 220, and a transceiver antenna 230. Note that the user terminal 20 may include one or more of each of the control unit 210, the transceiver unit 220, and the transceiver antenna 230.
[0191] Note that this example mainly shows functional blocks of the characteristic parts of the present embodiment, and it may be assumed that the user terminal 20 also has other functional blocks necessary for wireless communication. Some of the processing of each unit described below may be omitted.
[0192] The control unit 210 performs overall control of the user terminal 20. The control unit 210 can be configured from a controller, a control circuit, and the like that are explained based on common understanding in the technical field to which the present disclosure relates.
[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 transceiver unit 220 and the transceiver antenna 230. The control unit 210 may generate data, control information, sequences, etc. to be transmitted as signals, and transfer them to the transceiver unit 220.
[0194] The transceiver unit 220 may include a baseband unit 221, an RF unit 222, and a measurement unit 223. The baseband unit 221 may include a transmission processing unit 2211 and a reception processing unit 2212. The transceiver unit 220 may be configured from a transmitter / receiver, an RF circuit, a baseband circuit, a filter, a phase shifter, a measurement circuit, a transceiver circuit, etc., which are described based on common understanding in the technical field related to the present disclosure.
[0195] The transmitting / receiving unit 220 may be configured as an integrated transmitting / receiving unit, or may be composed of a transmitting unit and a receiving unit. The transmitting unit may be composed of a transmission processing unit 2211 and an RF unit 222. The receiving unit may be composed of a reception processing unit 2212, an RF unit 222, and a measurement unit 223.
[0196] The transmitting / receiving antenna 230 can be configured as an antenna described based on common understanding in the technical field to which the present disclosure pertains, such as an array antenna.
[0197] The transceiver 220 may receive the above-mentioned downlink channel, synchronization signal, downlink reference signal, etc. The transceiver 220 may transmit the above-mentioned uplink channel, uplink reference signal, etc.
[0198] The transceiver 220 may form at least one of a transmission beam and a reception beam using digital beamforming (for example, precoding), analog beamforming (for example, phase rotation), or the like.
[0199] The transceiver 220 (transmission processing unit 2211) may perform PDCP layer processing, RLC layer processing (e.g., RLC retransmission control), MAC layer processing (e.g., HARQ retransmission control), etc. on data, control information, etc. obtained from the control unit 210, and generate a bit string to be transmitted.
[0200] The transceiver 220 (transmission processor 2211) may perform transmission processing such as channel coding (which may include error correction coding), modulation, mapping, filtering, DFT processing (if necessary), IFFT processing, precoding, and digital-to-analog conversion on the bit string to be transmitted, and output a baseband signal.
[0201] Whether or not to apply DFT processing may be based on the setting of transform precoding. When transform precoding is enabled for a certain channel (e.g., PUSCH), the transceiver unit 220 (transmission processing unit 2211) may perform DFT processing as the transmission processing to transmit the channel using a DFT-s-OFDM waveform, and when transform precoding is not enabled, the transceiver unit 220 may not perform DFT processing as the transmission processing.
[0202] The transmitting / receiving unit 220 (RF unit 222) may perform modulation to a radio frequency band, filtering, amplification, etc. on the baseband signal, and transmit the radio frequency band signal 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 transceiver 220 (reception processing unit 2212) may apply reception processing such as analog-to-digital conversion, FFT processing, IDFT processing (if necessary), filtering, demapping, demodulation, decoding (which may include error correction decoding), MAC layer processing, RLC layer processing, and PDCP layer processing to the acquired baseband signal to acquire user data, etc.
[0205] The transceiver 220 (measurement unit 223) may perform measurements on the received signal. For example, the measurement unit 223 may perform RRM measurement, CSI measurement, etc. based on the received signal. The measurement unit 223 may measure received power (e.g., RSRP), received quality (e.g., RSRQ, SINR, SNR), signal strength (e.g., RSSI), propagation path information (e.g., CSI), etc. The measurement results may be output to the control unit 210.
[0206] The measurement unit 223 may derive channel measurements for CSI calculation based on the channel measurement resources. The 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 the interference measurement resources. The interference measurement resources may be at least one of an NZP CSI-RS resource for interference measurement, a CSI-Interference Measurement (IM) resource, etc. Note that CSI-IM may be referred to as CSI-Interference Management (IM) or may be interchangeably read as Zero Power (ZP) CSI-RS. Note that in the present disclosure, CSI-RS, NZP CSI-RS, ZP CSI-RS, CSI-IM, CSI-SSB, etc. may be interchangeably read as interchangeable.
[0207] The transmitting section and receiving section of the user terminal 20 in the present disclosure may be configured by at least one of the transmitting / receiving section 220 and the transmitting / receiving antenna 230.
[0208] The transceiver 220 may receive information regarding transmission conditions of the scheduling request and information indicating a unified transmission configuration indication (TCI) status.
[0209] When updating the TCI state to be applied to the uplink based on the information indicating the unified TCI state, the control unit 210 may control transmission of the scheduling request based on the information on the transmission condition and the time domain offset.
[0210] The value of the time domain offset may be set in association with the indicated unified TCI state, and may be included in higher layer 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 about the transmission conditions.
[0212] (Hardware configuration) The block diagrams used to explain the above embodiments show functional blocks. These functional blocks (components) are realized by any combination of at least one of hardware and software. Furthermore, the method for realizing each functional block is not particularly limited. That is, each functional block may be realized using a single device that is physically or logically coupled, or may be realized using two or more physically or logically separated devices that are directly or indirectly connected (for example, using wires, wirelessly, etc.) and these multiple devices. The functional block may also be realized by combining the single device or multiple devices with software.
[0213] Here, the functions include, but are not limited to, judgment, determination, judgment, calculation, computation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, election, establishment, comparison, assumption, expectation, deeming, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assignment. For example, a functional block (component) that performs transmission may be called a transmitting unit, transmitter, etc. As mentioned above, the implementation method of each is not particularly limited.
[0214] For example, a base station, a user terminal, etc. according to an embodiment of the present disclosure may function as a computer that performs processing of the wireless communication method of the present disclosure. Fig. 12 is a diagram illustrating an example of the hardware configuration of a base station and a user terminal according to an embodiment. The above-described base station 10 and user terminal 20 may be physically configured as a computer device including a processor 1001, a memory 1002, a storage 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, etc.
[0215] In this disclosure, terms such as apparatus, circuit, device, section, unit, etc. may be read interchangeably. The hardware configurations of the base station 10 and the user terminal 20 may be configured to include one or more of the devices shown in the drawings, or may be configured to exclude some of the devices.
[0216] For example, although only one processor 1001 is shown, there may be multiple processors. Furthermore, processing may be performed by one processor, or processing may be performed by two or more processors simultaneously, serially, or in other ways. Furthermore, processor 1001 may be implemented by one or more chips.
[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 a processor 1001 and a memory 1002, causing the processor 1001 to perform calculations, control communication via the communication device 1004, and control at least one of reading and writing data in the memory 1002 and the storage 1003.
[0218] The processor 1001, for example, runs an operating system to control the entire computer. The processor 1001 may be configured as a central processing unit (CPU) including an interface with peripheral devices, a control device, an arithmetic unit, a register, etc. For example, at least a part of the above-mentioned control unit 110 (210), transmission / reception unit 120 (220), etc. may be realized by the processor 1001.
[0219] The processor 1001 also reads programs (program codes), software modules, data, etc. from at least one of the storage 1003 and the communication device 1004 into the memory 1002, and executes various processes in accordance with these. The programs used are those that cause a computer to execute at least some of the operations described in the above-described embodiments. For example, the control unit 110 (210) may be realized by a control program stored in the memory 1002 and running on the processor 1001, and the other functional blocks may be realized in a similar manner.
[0220] The memory 1002 is a computer-readable recording medium and may be configured by at least one of, for example, a read-only memory (ROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a random access memory (RAM), or other suitable storage medium. The memory 1002 may also be referred to as a register, a cache, a main memory, or the like. The memory 1002 may store executable programs (program codes), software modules, and the like for implementing a wireless communication method according to an embodiment of the present disclosure.
[0221] Storage 1003 is a computer-readable recording medium and may be constituted by at least one of, for example, a flexible disk, a floppy disk, a magneto-optical disk (e.g., a compact disc (e.g., a Compact Disc ROM (CD-ROM)), a digital versatile disc, a Blu-ray disc), a removable disk, a hard disk drive, a smart card, a flash memory device (e.g., a card, stick, key drive), a magnetic stripe, a database, a server, or other suitable storage medium. Storage 1003 may also be referred to as a secondary storage device.
[0222] The communication device 1004 is hardware (transmission / reception device) for communicating between computers via at least one of a wired network and a wireless network, and is also referred to as, for example, a network device, a network controller, a network card, or a communication module. The communication device 1004 may be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc. to realize at least one of frequency division duplex (FDD) and time division duplex (TDD). For example, the above-mentioned transmission / reception unit 120 (220), transmission / reception antenna 130 (230), etc. may be realized by the communication device 1004. The transmission / reception unit 120 (220) may be implemented as a transmission unit 120a (220a) and a reception unit 120b (220b) that are physically or logically separated.
[0223] The input device 1005 is an input device (for example, a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.) that receives input from the outside. The output device 1006 is an output device (for example, a display, a speaker, a light emitting diode (LED) lamp, etc.) that outputs to the outside. The input device 1005 and the output device 1006 may be integrated into one device (for example, a touch panel).
[0224] Furthermore, each device, such as the processor 1001 and the memory 1002, is connected by a bus 1007 for communicating information. The bus 1007 may be configured using a single bus, or may be configured using different buses between each device.
[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), or a field programmable gate array (FPGA), and some or all of the functional blocks may be realized using such hardware. For example, the processor 1001 may be implemented using at least one of these pieces of hardware.
[0226] Note that the devices included in the core network 30 (for example, network nodes that provide NFs) may also be realized by the above-described functional block / hardware configuration.
[0227] (Variation) Note that terms explained in the present disclosure and terms necessary for understanding the present disclosure may be replaced with terms having the same or similar meanings. For example, a channel, a symbol, and a signal (signal or signaling) may be interchangeable. A signal may also be a message. A reference signal may be abbreviated as RS, and may also be called a pilot, pilot signal, etc. depending on the applicable standard. A component carrier (CC) may also be called a cell, frequency carrier, carrier frequency, etc.
[0228] A radio frame may be composed of one or more periods (frames) in the time domain. Each of the one or more periods (frames) constituting a radio frame may be called a subframe. Furthermore, a subframe may be composed of one or more slots in the time domain. A subframe may have a fixed time length (e.g., 1 ms) that is independent of numerology.
[0229] Here, the numerology may be a communication parameter applied to at least one of transmission and reception of a signal or channel, and may indicate at least one of, for example, a subcarrier spacing (SCS), a bandwidth, a symbol length, a cyclic prefix length, a transmission time interval (TTI), the number of symbols per TTI, a radio frame structure, a specific filtering process performed by a transceiver in the frequency domain, and a specific windowing process performed by a transceiver in the time domain.
[0230] A slot may be composed of one or more symbols in the time domain (such as an Orthogonal Frequency Division Multiplexing (OFDM) symbol or a Single Carrier Frequency Division Multiple Access (SC-FDMA) symbol), and may be a time unit based on numerology.
[0231] A slot may include multiple minislots. Each minislot may consist of one or multiple symbols in the time domain. A minislot may also be called a subslot. A minislot may consist of fewer symbols than a slot. A PDSCH (or PUSCH) transmitted in a time unit larger than a minislot may be called PDSCH (PUSCH) mapping type A. A PDSCH (or PUSCH) transmitted using a minislot may be called PDSCH (PUSCH) mapping type B.
[0232] A radio frame, a subframe, a slot, a minislot, and a symbol all represent time units for transmitting signals. The radio frame, the subframe, the slot, the minislot, and the symbol may be referred to by other names corresponding to the radio frame, the subframe, the slot, the minislot, and the symbol. Note that the time units such as a frame, a subframe, a slot, a minislot, and a symbol in the present disclosure may be interchangeable.
[0233] For example, one subframe may be referred to as a TTI, or multiple consecutive subframes may be referred to as a TTI, or one slot or one minislot may be referred to as a TTI. That is, at least one of a subframe and a TTI may be a subframe (1 ms) in existing LTE, a period shorter than 1 ms (for example, 1-13 symbols), or a period longer than 1 ms. Note that the unit representing the TTI may be called a slot, minislot, etc., instead of a subframe.
[0234] Here, TTI refers to, for example, the smallest time unit for scheduling in wireless communication. For example, in an LTE system, a base station performs scheduling to allocate radio resources (such as frequency bandwidth and transmission power that can be used by each user terminal) to each user terminal in TTI units. However, the definition of TTI is not limited to this.
[0235] The TTI may be a transmission time unit for a channel-encoded data packet (transport block), a code block, a code word, etc., or may be a processing unit for scheduling, link adaptation, etc. When a TTI is given, the time interval (e.g., the number of symbols) to which a transport block, a code block, a code word, etc. is actually mapped may be shorter than the TTI.
[0236] When one slot or one minislot is called a TTI, one or more TTIs (i.e., one or more slots or one or more minislots) may be the minimum time unit for scheduling. Also, the number of slots (minislots) constituting the minimum time unit for scheduling may be controlled.
[0237] A TTI having a time length of 1 ms may be called a regular TTI (TTI in 3GPP Rel. 8-12), normal TTI, long TTI, regular subframe, normal subframe, long subframe, slot, etc. A TTI shorter than a regular TTI may be called a shortened TTI, short TTI, partial or fractional TTI, shortened subframe, short subframe, minislot, subslot, slot, etc.
[0238] In addition, a long TTI (e.g., a normal TTI, a subframe, etc.) may be interpreted as a TTI having a time length of more than 1 ms, and a short TTI (e.g., a shortened TTI, etc.) may be interpreted as a TTI having a TTI length shorter than the TTI length of a long TTI and equal to or greater than 1 ms.
[0239] A resource block (RB) is a resource allocation unit in the time domain and the frequency domain, and may include one or more consecutive subcarriers in the frequency domain. The number of subcarriers included in an RB may be the same regardless of numerology, for example, 12. The number of subcarriers included in an RB may also be determined based on numerology.
[0240] In addition, an RB may include one or more symbols in the time domain and may have a length of one slot, one minislot, one subframe, or one TTI. One TTI, one subframe, etc. may each be composed of one or more resource blocks.
[0241] Note that one or more RBs may also be called a physical resource block (PRB), a sub-carrier group (SCG), a resource element group (REG), a PRB pair, an RB pair, etc.
[0242] Furthermore, a resource block may be composed of one or more resource elements (REs). For example, one RE may be a radio resource region of one subcarrier and one symbol.
[0243] A Bandwidth Part (BWP), which may also be referred to as a fractional bandwidth, may represent a subset of contiguous common resource blocks (RBs) for a given numerology on a given carrier, where the common RBs may be identified by their index relative to a common reference point of the carrier. PRBs may be defined in a given BWP and numbered within that BWP.
[0244] The BWP may include an UL BWP (a BWP for UL) and a DL BWP (a BWP for DL). One or more BWPs may be configured for a UE within one carrier.
[0245] At least one of the configured BWPs may be active, and the UE may not expect to transmit or receive a given signal / channel outside the active BWP. Note that the terms "cell," "carrier," etc. in this disclosure may be read as "BWP."
[0246] The above-described structures of radio frames, subframes, slots, minislots, symbols, etc. are merely examples. For example, the number of subframes included in a radio frame, the number of slots per subframe or radio frame, the number of minislots included in a slot, the number of symbols and RBs included in a slot or minislot, the number of subcarriers included in an RB, the number of symbols in a TTI, the symbol length, the cyclic prefix (CP) length, etc. may be changed in various ways.
[0247] Furthermore, the information, parameters, etc. described in the present disclosure may be expressed using absolute values, may be expressed using relative values from a predetermined value, or may be expressed using other corresponding information. For example, a radio resource may be indicated by a predetermined index.
[0248] The names used for parameters and the like in this disclosure are not intended to be limiting in any way. Furthermore, the mathematical expressions and the like using these parameters may differ from those explicitly disclosed in this disclosure. The various channels (PUCCH, PDCCH, etc.) and information elements may be identified by any suitable names, and therefore the various names assigned to these various channels and information elements are not intended to be limiting in any way.
[0249] The information, signals, etc. described in this disclosure may be represented using any of a variety of different technologies. For example, data, instructions, commands, information, signals, bits, symbols, chips, etc. that may be referred to throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combination thereof.
[0250] Furthermore, information, signals, etc. may be output from a higher layer to a lower layer and / or from a lower layer to a higher layer. Information, signals, etc. may be input / output via multiple network nodes.
[0251] Input and output information, signals, etc. may be stored in a specific location (for example, memory) or may be managed using a management table. Input and output information, signals, etc. may be overwritten, updated, or added. Output information, signals, etc. may be deleted. Input information, signals, etc. may be transmitted to another device.
[0252] With respect to any information (e.g., variables, constants, parameters) described in the present disclosure, even if not specifically stated in the above embodiments, any first device (e.g., UE / base station) may notify any second device (e.g., base station / UE) of information indicating / identifying (or relating to) the value of the any information.
[0253] Notification of information is not limited to the aspects / embodiments described in the present disclosure, and may be performed using other methods. For example, notification of information in the present disclosure may be performed by physical layer signaling (e.g., Downlink Control Information (DCI) and Uplink Control Information (UCI)), higher layer signaling (e.g., Radio Resource Control (RRC) signaling, broadcast information (Master Information Block (MIB) and System Information Block (SIB)), Medium Access Control (MAC) signaling), other signals, or a combination thereof.
[0254] Note that the physical layer signaling may be called Layer 1 / Layer 2 (L1 / L2) control information (L1 / L2 control signal), L1 control information (L1 control signal), etc. Furthermore, the RRC signaling may be called an RRC message, such as an RRC connection setup message or an RRC connection reconfiguration message. Furthermore, the MAC signaling may be notified using, for example, a MAC Control Element (CE).
[0255] Furthermore, notification of specified information (e.g., notification that "it is X") is not limited to explicit notification, but may be made implicitly (e.g., by not notifying the specified information or by notifying other information).
[0256] The determination may be made by a value represented by one bit (0 or 1), by a Boolean value represented by true or false, or by a comparison of numerical values (e.g., comparison with a predetermined value).
[0257] Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.
[0258] Software, instructions, information, etc. may also be transmitted or received over a transmission medium. For example, if software is transmitted from a website, server, or other remote source using wired technologies (such as coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL)), and / or wireless technologies (such as infrared, microwave), then these wired and / or wireless technologies are included within the definition of transmission media.
[0259] As used in this disclosure, the terms "system" and "network" may be used interchangeably. A "network" may refer to devices included in the network (e.g., base stations).
[0260] In the present disclosure, terms such as "precoding," "precoder," "weight (precoding weight)," "Quasi-Co-Location (QCL)," "Transmission Configuration Indication state (TCI state)," "spatial relation," "spatial domain filter," "transmit power," "phase rotation," "antenna port," "layer," "number of layers," "rank," "resource," "resource set," "beam," "beam width," "beam angle," "antenna," "antenna element," "panel," "UE panel," "transmitting entity," "receiving entity," etc. may be used interchangeably.
[0261] In the present disclosure, the term "antenna port" may be interchangeably read as an antenna port for any signal / channel (e.g., a demodulation reference signal (DMRS) port). In the present disclosure, the term "resource" may be interchangeably read as a resource for any signal / channel (e.g., a reference signal resource, an SRS resource, etc.). The resource may include time / frequency / code / space / power resources. The spatial domain transmission filter may include at least one of a spatial domain transmission filter and a spatial domain reception filter.
[0262] The group may include, for example, at least one of 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, a panel group, and the like.
[0263] In addition, in the present disclosure, beam, SRS Resource Indicator (SRI), CORESET, CORESET pool, PDSCH, PUSCH, codeword (CW), transport block (TB), RS, etc. may be read as interchangeable terms.
[0264] In addition, in the present disclosure, the terms 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 read interchangeably.
[0265] Furthermore, in this disclosure, terms such as "QCL," "QCL assumptions," "QCL relationships," "QCL type information," "QCL properties," "specific QCL type (e.g., Type A, Type D) properties," and "specific QCL type (e.g., Type A, Type D)" may be interchangeable.
[0266] In this disclosure, terms such as index, identifier (ID), indicator, indication, and resource ID may be interchangeable. In this disclosure, terms such as sequence, list, set, group, cluster, and subset may be interchangeable.
[0267] Furthermore, the spatial relationship information identifier (ID) (TCI state ID) and spatial relationship information (TCI state) may be interchangeable. "Spatial relationship information (TCI state)" may be interchangeable with "set of spatial relationship information (TCI state)", "one or more pieces of spatial relationship information", etc. The TCI state and TCI may be interchangeable. The spatial relationship information and spatial relationship may be interchangeable.
[0268] In this disclosure, terms such as "base station (BS)," "radio base station," "fixed station," "NodeB," "eNB (eNodeB)," "gNB (gNodeB)," "access point," "transmission point (TP)," "reception point (RP)," "transmission / reception point (TRP)," "panel," "cell," "sector," "cell group," "carrier," "component carrier," etc. may be used interchangeably. Base stations may also be referred to by terms such as macrocell, small cell, femtocell, picocell, etc.
[0269] A base station can accommodate one or more (e.g., three) cells. When a base station accommodates multiple cells, the overall coverage area of the base station can be divided into multiple smaller areas, and each smaller area can be provided with communication service by a base station subsystem (e.g., a small indoor base station (Remote Radio Head (RRH))). The term "cell" or "sector" refers to a part or the entire coverage area of a base station and / or base station subsystem that provides communication service within this coverage.
[0270] In the present disclosure, a base station transmitting information to a terminal may be interpreted as the base station instructing the terminal to control / operate based on the information.
[0271] In this disclosure, the terms "Mobile Station (MS)," "user terminal," "User Equipment (UE)," "terminal," etc. may be used interchangeably.
[0272] A mobile station may also be referred to as a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or some other suitable terminology.
[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. Note that at least one of the base station and the mobile station may be a device mounted on a moving object, the moving object itself, etc.
[0274] The mobile body is a movable object that can move at any speed and naturally includes cases where the mobile body is stationary. Examples of the mobile body include, but are not limited to, vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, handcars, rickshaws, ships and other watercraft, airplanes, rockets, satellites, drones, multicopters, quadcopters, balloons, and objects mounted thereon. The mobile body may also be a mobile body that moves autonomously based on an operation command.
[0275] The mobile object may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile object (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). Note that at least one of the base station and the mobile station may also include devices that do not necessarily move during communication operations. For example, at least one of the base station and the mobile station may be an Internet of Things (IoT) device such as a sensor.
[0276] 13 is a diagram showing an example of a vehicle according to an embodiment. A 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, axles 48, an electronic control unit 49, various sensors (including a current sensor 50, an RPM sensor 51, an air 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 is configured with at least one of an engine, a motor, and a hybrid of an engine and a motor, for example. 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 is composed of a microprocessor 61, memory (ROM, RAM) 62, and a communication port (e.g., an input / output (IO) port) 63. Signals are input to the electronic control unit 49 from various sensors 50-58 provided in the vehicle. The electronic control unit 49 may also be called an Electronic Control Unit (ECU).
[0279] The signals from the various sensors 50-58 include a current signal from a current sensor 50 that senses the current of the motor, a rotation speed signal of the front wheels 46 / rear wheels 47 obtained by a rotation speed sensor 51, an air pressure signal of the front wheels 46 / rear wheels 47 obtained by an air pressure sensor 52, a vehicle speed signal obtained by a vehicle speed sensor 53, an acceleration signal obtained by an acceleration sensor 54, a depression amount signal of the accelerator pedal 43 obtained by an accelerator pedal sensor 55, a depression amount signal of the brake pedal 44 obtained by a brake pedal sensor 56, an operation signal of the shift lever 45 obtained by a shift lever sensor 57, and a detection signal for detecting obstacles, vehicles, pedestrians, etc. obtained by an object detection sensor 58.
[0280] The information service unit 59 is composed of various devices, such as a car navigation system, an audio system, speakers, a display, a television, and a radio, for providing (outputting) various information such as driving information, traffic information, and entertainment information, and one or more ECUs for controlling these devices. The information service unit 59 uses information acquired from external devices via the communication module 60 or the like to provide various 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 (e.g., keyboards, mice, microphones, switches, buttons, sensors, touch panels, etc.) that accept input from the outside, and may also include output devices (e.g., displays, speakers, LED lamps, touch panels, etc.) that output to the outside.
[0282] The driving assistance system unit 64 is configured with various devices that provide functions for preventing accidents and reducing the driver's driving burden, 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 Units (IMUs), Inertial Navigation Systems (INSs)), Artificial Intelligence (AI) chips, and AI processors, as well as one or more ECUs that control these devices. The driving assistance system unit 64 also transmits and receives various information via the communication module 60 to realize driving 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 transmits and receives data (information) via the communication port 63 to and from 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, axles 48, the microprocessor 61 and memory (ROM, RAM) 62 in the electronic control unit 49, and the various sensors 50-58, which are 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 an external device. For example, it transmits and receives various information to and from the external device 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 above-mentioned base station 10 or user terminal 20. Furthermore, the communication module 60 may be, for example, at least one of the above-mentioned base station 10 and user terminal 20 (or may function as at least one of the base station 10 and user terminal 20).
[0285] The communication module 60 may transmit at least one of signals from the above-mentioned various sensors 50-58 input to the electronic control unit 49, information obtained based on the signals, and information based on input from the outside (user) obtained via the information service unit 59 to an external device via wireless communication. The electronic control unit 49, the various sensors 50-58, the information service unit 59, etc. may be referred to as input units that accept input. For example, the PUSCH transmitted by the communication module 60 may include information based on the above-mentioned input.
[0286] The communication module 60 receives various information (traffic information, traffic signal information, vehicle distance information, etc.) transmitted from external devices and displays it on an information service unit 59 provided in the vehicle. The information service unit 59 may also be called an output unit that outputs information (for example, outputs information to a device such as a display or speaker based on the PDSCH received by the communication module 60 (or data / information decoded from the PDSCH)).
[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, axles 48, various sensors 50-58, and the like provided in the vehicle 40.
[0288] Furthermore, a base station in the present disclosure may be read as a user terminal. For example, the aspects / embodiments of the present disclosure may be applied to a configuration in which communication between a base station and a user terminal is replaced with communication between multiple user terminals (which may be called, for example, Device-to-Device (D2D) or Vehicle-to-Everything (V2X)). In this case, the user terminal 20 may be configured to have the functions of the base station 10 described above. Furthermore, terms such as "uplink" and "downlink" may be read as terms corresponding to terminal-to-terminal communication (for example, "sidelink"). For example, terms such as uplink channel and downlink channel may be read as sidelink channel.
[0289] Similarly, the user terminal in the present disclosure may be read as a base station, in which case the base station 10 may be configured to have the functions of the user terminal 20 described above.
[0290] In the present disclosure, an operation described as being performed by a base station may be performed by its upper node in some cases. It is apparent that in a network including one or more network nodes having a base station, various operations performed for communication with a terminal may be performed by the base station, one or more network nodes other than the base station (such as, but not limited to, a Mobility Management Entity (MME) and a Serving-Gateway (S-GW)), or a combination thereof.
[0291] Each aspect / embodiment described in this disclosure may be used alone, in combination, or switched depending on the implementation. Furthermore, the order of the processing procedures, sequences, flowcharts, etc. of each aspect / embodiment described in this disclosure may be changed unless inconsistent. For example, the methods described in this disclosure present elements of various steps using an example order, and are not limited to the specific order presented.
[0292] Each aspect / embodiment described in the present disclosure may be a technology other than Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 6th generation mobile communication system (6G), xth generation mobile communication system (xG (x is, for example, an integer or decimal number)), Future Radio Access (FRA), New-Radio Access Technology (RAT), New Radio (NR), New radio access (NX), Future generation radio access (FX), Global System for Mobile communications (GSM (registered trademark)), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE The present invention may be applied to systems that use 802.20, Ultra-WideBand (UWB), Bluetooth (registered trademark), or other appropriate wireless communication methods, or to next-generation systems that are expanded, modified, created, or defined based on these. It may also be applied to a combination of multiple systems (e.g., a combination of LTE or LTE-A and 5G).
[0293] As used in this disclosure, the phrase "based on" does not mean "based only on," unless expressly stated otherwise. In other words, the phrase "based on" means both "based only on" and "based at least on."
[0294] As used in this disclosure, any reference to an element using a designation such as "first," "second," etc. does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient method of distinguishing between two or more elements. Thus, a reference to a first and a second element does not imply that only two elements may be employed or that the first element must in some way precede the second element.
[0295] The term "determining," as used in this disclosure, may encompass a wide variety of actions. For example, "determining" may be considered to be judging, calculating, computing, processing, deriving, investigating, looking up, search, inquiry (e.g., looking up in a table, database, or another data structure), ascertaining, etc.
[0296] Additionally, "determining" may be considered to be "determining" receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, accessing (e.g., accessing data in memory), etc.
[0297] Furthermore, "determination" may be considered to be "determining" resolving, selecting, choosing, establishing, comparing, etc. In other words, "determination" may be considered to be "determining" some action. In the present disclosure, "determination" may be read interchangeably with the above-mentioned actions.
[0298] Furthermore, in this disclosure, "determine / determining" may be interchangeably read as "assume / assuming," "expect / expecting," "consider / considering," etc. Furthermore, in this disclosure, "does not expect to do..." may be interchangeably read as "assumes not to do...."
[0299] In the present disclosure, "expect" may be interchangeably read as "be expected." For example, "expect(s) ..." ("..." may be expressed, for example, as a that clause, a to-infinitive, etc.) may be interchangeably read as "be expected ...," "do ... (if the above "..." is a to-infinitive, a verb with "to")," etc. "does not expect ..." may be interchangeably read as "be not expected ...," "does not ... (if the above "..." is a to-infinitive, a verb with "to")," etc. Furthermore, "An apparatus A is not expected ..." may be interchangeably read 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 "maximum transmit power" in this disclosure may mean the maximum value of 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," or any variation thereof, refer to any direct or indirect connection or coupling between two or more elements, and may include the presence of one or more intermediate elements between two elements that are "connected" or "coupled" to each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, "connected" may be read as "access."
[0302] In this disclosure, when two elements are connected, they may be considered to be "connected" or "coupled" to one another using one or more wires, cables, printed electrical connections, etc., as well as using electromagnetic energy having wavelengths in the radio frequency range, microwave range, light (both visible and invisible) range, etc., as some non-limiting and non-exhaustive examples.
[0303] In the present disclosure, the term "A and B are different" may mean "A and B are different from each other." The term may also mean "A and B are each different from C." Terms such as "separate" and "coupled" may also be interpreted in the same way as "different."
[0304] When used in this disclosure, the terms "include," "including," and variations thereof are intended to be inclusive, similar to the term "comprising." Furthermore, when used in this disclosure, the term "or" is not intended to be an exclusive or.
[0305] In this disclosure, where articles are added by translation, such as a, an, and the in English, the disclosure may include that the nouns following these articles are in the plural form.
[0306] In the present disclosure, terms such as "less than or equal to," "less than," "greater than," "more than," "equal to," etc. may be interchangeable. Furthermore, in the present disclosure, terms meaning "good," "bad," "big," "small," "high," "low," "fast," "slow," "wide," "narrow," etc. may be interchangeable, not limited to the positive, comparative, and superlative. Furthermore, in the present disclosure, terms meaning "good," "bad," "big," "small," "high," "low," "fast," "slow," "wide," "narrow," etc. may be interchangeable, not limited to the positive, comparative, and superlative, as expressions with the prefix "i-th" (i is any integer) (for example, "highest" may be interchangeable as "i-th highest").
[0307] In this disclosure, the terms "of," "for," "regarding," "related to," "associated with," etc. may be read interchangeably.
[0308] In the present disclosure, terms 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. Note that A, B, and the like herein may be replaced with appropriate expressions, such as nouns, gerunds, and regular sentences, depending on the context. Note that the time difference between A and B may be nearly zero (immediately after or immediately before). A time offset may be applied to the time at which A occurs. For example, "A" may be interchangeable with "before / after the time offset at which A occurs." The time offset (eg, one or more symbols / slots) may be predefined or may be specified by the UE based on signaled information.
[0309] In the present disclosure, timing, time, duration, time instance, any time unit (e.g., slot, subslot, symbol, subframe), period, occasion, resource, etc. may be read interchangeably.
[0310] Although the invention according to the present disclosure has been described in detail above, it is clear to those skilled in the art that the invention according to the present disclosure is not limited to the embodiments described in the present disclosure. The description of the present disclosure is for illustrative purposes only and does not impose any limiting meaning on the invention according to the present disclosure.< / srs> < / pusch> < / pucch> < / pdsch> < / pdcch>
Claims
1. a receiver for receiving information relating to transmission conditions of a scheduling request and information indicating a unified transmission configuration indication (TCI) state; A terminal having a control unit that controls transmission of a scheduling request based on information regarding the transmission conditions and a time domain offset when updating a TCI state to be applied to an uplink based on information indicating the unified TCI state.
2. The terminal of claim 1 , wherein the value of the time domain offset is set in association with a designated unified TCI state.
3. The terminal of claim 1 , wherein the value of the time domain offset is included in higher layer parameters for the unified TCI state.
4. The terminal of claim 1 , wherein, when a time domain offset is not set for a unified TCI state applied to the scheduling request, the controller controls transmission of the scheduling request based on information about the transmission condition.
5. receiving information regarding transmission conditions for a scheduling request and information indicating a unified transmission configuration indication (TCI) state; When updating the TCI state to be applied to the uplink based on the information indicating the unified TCI state, controlling transmission of a scheduling request based on the information regarding the transmission conditions and a time domain offset.
6. a transmitter for transmitting information regarding transmission conditions of a scheduling request and information indicating a unified transmission configuration indication (TCI) state; A base station having a control unit that controls reception of a scheduling request based on information regarding the transmission conditions and a time domain offset when updating a TCI state to be applied to an uplink based on information indicating the unified TCI state.