Terminal, radio communication method, and base station
The terminal and base station system addresses the challenge of uplink power control in future wireless systems by using path loss offsets and MAC control elements, enhancing coverage and throughput through precise power management.
Patent Information
- Application Number
- PCT/JP2024/005571
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2024-02-16
- Publication Date
- 2025-08-21
AI Technical Summary
In future wireless communication systems, the appropriate control of uplink transmission power is unclear, leading to a risk of decreased throughput due to path loss uncertainties when additional uplink reception points are introduced.
A terminal and base station system that includes a receiving unit for path loss offsets and MAC control elements to control uplink transmission power based on downlink control information, utilizing TCI states and spatial relationships for precise power management.
Enables effective control of uplink transmission power, improving coverage and throughput by reducing path loss and enhancing signaling quality in heterogeneous networks.
Smart Images

Figure JP2024005571_21082025_PF_FP_ABST
Abstract
Description
Terminal, wireless communication method and base station
[0001] The present disclosure relates to a terminal, a wireless communication method, and a base station in a next-generation mobile communication system.
[0002] Long Term Evolution (LTE) has been specified for the Universal Mobile Telecommunications System (UMTS) network with the aim of achieving higher data rates and lower latency (Non-Patent Document 1). Also, LTE-Advanced (3GPP Rel. 10-14) has been specified with the aim of achieving higher capacity and more advanced features than LTE (Third Generation Partnership Project (3GPP (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, etc.) are also being considered.
[0004] 3GPP TS 36.300 V8.12.0 “Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 (Release 8)”, April 2010
[0005] In future wireless communication systems, in order to expand UL coverage, it is being considered to install UL receiving points in addition to general transmitting and receiving points. Also, UL high-density deployment using DL transmitting points / macro Base Stations (BSs) and UL receiving points / micro BSs / Heterogeneous Networks (HetNets) are being considered.
[0006] However, when an RS (path loss RS) for path loss (PL) calculation is transmitted from a DL transmission point, it is not clear how a terminal (user terminal, User Equipment (UE)) determines the transmission power when transmitting an UL signal to an UL reception point. If the UL transmission power cannot be controlled appropriately, there is a risk that the throughput will decrease.
[0007] Therefore, one object of the present disclosure is to provide a terminal, a wireless communication method, and a base station that can appropriately control UL transmission power.
[0008] A terminal according to one aspect of the present disclosure includes a receiving unit that receives settings for a specific number of path loss (PL) offsets corresponding to uplink (UL) reception points, and receives Medium Access Control (MAC) control elements or downlink control information that instruct updating of the PL offsets, and a control unit that controls the transmission power of UL signals for the UL reception points based on the MAC control elements or the downlink control information.
[0009] According to one aspect of the present disclosure, UL transmission power can be appropriately controlled.
[0010] Figure 1A is a diagram showing an example of a typical arrangement of transmission / reception points. Figure 1B is a diagram showing an example of an UL high-density arrangement. Figure 2 is a diagram showing an example of DL / UL coverage in a Heterogeneous Network (HetNet). Figure 3A is a diagram showing an example of association between RS indexes and PL values. Figure 3B is a diagram showing an example of association between RS indexes and delta PL values. Figure 4 is a diagram showing an example of Option 1 in an UL high-density arrangement. Figure 5 is a diagram showing an example of Option 2 in an UL high-density arrangement. Figure 6 is a diagram showing an example of power control parameters related to TCI states. Figure 7 is a diagram showing an example of a TCI-State information element in Rel. 17. Figures 8A and 8B show an example of a unified / common TCI framework. Figures 9A and 9B are diagrams showing an example of UL power control parameters in Rel. 17. Figures 10A and 10B are diagrams showing an example of setting / application of PL offsets in the 0th embodiment. 11A and 11B are diagrams illustrating an example of PL offset setting according to the first embodiment. FIG. 12A is a diagram illustrating an example of PL offset updating according to embodiment 3-1. FIG. 12B is a diagram illustrating an example of PL offset updating according to embodiment 3-2. FIG. 13 is a diagram illustrating an example of a MAC CE according to embodiment 4-4-A. FIGS. 14A and 14B are diagrams illustrating an example of a MAC CE according to embodiment 4-4-B. FIG. 15 is a diagram illustrating another example of a MAC CE according to embodiment 4-4-B. FIG. 16A is a diagram illustrating an example of a MAC CE according to embodiment 4-4-C-1. FIG. 16B is a diagram illustrating an example of a MAC CE according to embodiment 4-4-C-2. FIGS. 17A to 17C are diagrams illustrating an example of PL offset association according to embodiment 4-5. FIG. 18A is a diagram illustrating an example of PL offset updating according to embodiment 4-6-1. FIG. 18B is a diagram illustrating an example of PL offset updating according to embodiment 4-6-2. Fig. 19 is a diagram showing an example of a PL offset value instruction according to embodiment 5-1. Fig. 20 is a diagram showing another example of a PL offset value instruction according to embodiment 5-1. Fig. 21 is a diagram showing an example of a PL offset value update according to embodiment 5-2.Fig. 22 is a diagram showing another example of updating a PL offset value according to embodiment 5-2. Fig. 23 is a diagram showing an example of a schematic configuration of a wireless communication system according to an embodiment. Fig. 24 is a diagram showing an example of a configuration of a base station according to an embodiment. Fig. 25 is a diagram showing an example of a configuration of a user terminal according to an embodiment. Fig. 26 is a diagram showing an example of the hardware configuration of a base station and a user terminal according to an embodiment. Fig. 27 is a diagram showing an example of a vehicle according to an embodiment.
[0011] (TCI, spatial relationship, QCL) In NR, it is 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 a UE of at least one of a signal and a channel (referred to as a signal / channel) based on a transmission configuration indication state (TCI state).
[0012] The TCI state may represent that which is applied to a downlink signal / channel, and the equivalent of the TCI state that is applied to an uplink signal / channel may be expressed as a spatial relation.
[0013] 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.
[0014] The QCL is an index indicating the statistical properties of signals / channels. For example, if a signal / channel has a QCL relationship with another signal / channel, it may mean that it can be assumed that at least one of a Doppler shift, a Doppler spread, an average delay, a delay spread, and a spatial parameter (e.g., a spatial Rx parameter) is the same between these different signals / channels (i.e., the signals / channels have a QCL with respect to at least one of these).
[0015] The spatial reception parameters may correspond to a reception beam (e.g., a reception analog beam) of the UE, and the beam may be identified based on a spatial QCL. The QCL (or at least one element of the QCL) in the present disclosure may be replaced with sQCL (spatial QCL).
[0016] A plurality of types (QCL types) of QCL may be defined. For example, four QCL types A to D may be provided, each having different parameters (or parameter sets) that can be assumed to be the same. The parameters (which may be referred to as QCL parameters) are as follows: QCL type A (QCL-A): Doppler shift, Doppler spread, mean delay, and delay spread QCL type B (QCL-B): Doppler shift and Doppler spread QCL type C (QCL-C): Doppler shift and mean delay QCL type D (QCL-D): Spatial reception parameters.
[0017] The UE's assumption 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.
[0018] 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.
[0019] The TCI state may be, for example, information about the QCL between the channel of interest (in other words, the Reference Signal (RS) for that channel) and another signal (e.g., another RS). The TCI state may be set (indicated) by higher layer signaling, physical layer signaling, or a combination thereof.
[0020] The channel / signal to which the TCI state is applied may be called a target channel / reference signal (target channel / RS), or simply a target, and the other signal may be called a reference reference signal (reference RS), a source RS, or simply a reference.
[0021] The channel for which the TCI state or spatial relationship is set (specified) may be, for example, at least one of a physical downlink shared channel (PDSCH), a physical downlink control channel (PDCCH), a physical uplink shared channel (PUSCH), and a physical uplink control channel (PUCCH).
[0022] Furthermore, the RS that has a QCL relationship with the channel may be at least one of, for example, a synchronization signal block (SSB), a channel state information reference signal (CSI-RS), a sounding reference signal (SRS), a tracking CSI-RS (also called a tracking reference signal (TRS)), a QCL detection reference signal (also called a QRS), a demodulation reference signal (DMRS), etc.
[0023] An SSB is a signal block including 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.
[0024] An RS of QCL type X in a TCI state may refer to an RS that has a QCL type X relationship with a certain channel / signal (DMRS), and this RS may be called a QCL source of QCL type X in the TCI state.
[0025] (Scenario 1: UL Dense Deployment (UL-Only TRP)) In Rel. 15 NR, the coverage (reaching distance) of PUSCH, PUCCH, PRACH, PDSCH, PDCCH, and PBCH is uneven. PUSCH coverage is limited, especially at high frequencies. Future wireless communication systems (e.g., Rel. 18, Rel. 19, or later) are expected to improve at least one of UL coverage and UL throughput.
[0026] In order to expand UL coverage, the installation of UL reception points in addition to general transmission and reception points is being considered. Therefore, an example of the arrangement of general transmission and reception points and an example of an arrangement with UL reception points (UL high-density arrangement) will be described.
[0027] 1A is a diagram showing an example of a typical arrangement of transmission / reception points. In FIG. 1A, a UE receives a DL signal from a transmission / reception point (TRP) and transmits a UL signal to the TRP. For example, if the UE and the TRP are far apart, the path loss may be large, resulting in a deterioration in communication quality.
[0028] Figure 1B is a diagram showing an example of a high-density UL deployment. To expand UL coverage, it is considered to provide UL reception points as shown in Figure 1B in addition to the DL transmission points as shown in Figure 1A. In Figure 1B, a UE receives DL signals from a DL transmission point (TRP / Central TRP / DL TRP / Macro TRP) corresponding to a macro cell and transmits UL signals to a UL reception point (e.g., a reception point with a smaller path loss / reception power). However, the UE may also be capable of UL transmission to a DL transmission point.
[0029] By using a high-density UL configuration such as that shown in Figure 1B, it is possible to improve both coverage and UL data rates by reducing path loss, improving UL signaling quality, and obtaining a higher coding rate compared to a general configuration such as that shown in Figure 1A. Furthermore, since the UL reception point mainly performs reception, it requires fewer functions (e.g., power amplifiers) and is therefore less costly than a transmission / reception point corresponding to a general small cell, making deployment management much easier.
[0030] (Scenario 2: Decoupling of DL TRP and UL TRP in HetNet) In the present disclosure, a Heterogeneous Network (HetNet) using a macro Base Station (BS) (DL TRP) and a micro BS (UL TRP) may be applied (FIG. 2). In a typical HetNet, the transmission power of the macro BS and the micro BS is different. Also, the optimal DL coverage and the optimal UL coverage are different. For example, the DL coverage is determined by the RSRP, and the UL coverage is determined by the path loss (PL).
[0031] In the example of FIG. 2, the UE is included in the optimal DL coverage of the macro BS and the optimal UL coverage of the micro BS. In this case, the UE can receive DL from the macro BS and transmit UL to the micro BS. However, the UE may transmit some reference signals / channels (e.g., SRS with Antenna Switching (AS) usage, used to acquire DL CSI) to the macro BS. Therefore, the UE may require two timing advances (TAs) in this scenario. Note that the AS SRS is transmitted to the macro BS because it is intended for the base station (macro BS) to measure DL CSI (e.g., determine the DL MIMO precoder) based on the reception of the SRS using channel reciprocity. On the other hand, the codebook / non-codebook SRS is transmitted to the micro BS because it is used for determining the precoder / beam of the PUSCH.
[0032] In a HetNet, even if a micro BS has DL transmission capability, it can save energy by turning off DL most of the time, in which case the function of the micro BS is similar to a UL-only TRP (UL Reception Point).
[0033] (Receiving Path Loss (PL)) The UE may receive first information indicating a path loss (PL) used for transmission power control (TPC), which is estimated and notified (transmitted) by the network, via DL signaling. The DL signaling may be at least one of higher layer signaling (e.g., RRC or MAC CE) and physical layer signaling (e.g., Downlink Control Information (DCI)).
[0034] The UE receives the path loss (PL b,f,c (q d ), P.L. b,f,c ) (index q d The active UL BWP of carrier f of serving cell c (path loss for b) may be used to calculate the UL signal transmission power (for example, the transmission power of PUSCH / PUCCH / SRS / PRACH) for a reception point that does not transmit downlink data.
[0035] [Option 1] The absolute path loss (PL) value [dB] for each RS index may be reported (transmitted) from the network to the UE, and the UE may use the reported absolute path loss value directly in calculating the transmit power.
[0036] [Option 2] The network may notify (transmit) a relative path loss (Delta PL) value [dB] for each RS index to the UE. The UE may use the path loss value obtained by applying (adding or subtracting) the received Delta PL value to the conventional path loss value estimated from the DL RS transmitted from the macro cell (macro BS / central TRP) for calculating the transmission power.
[0037] The PL value / delta PL value in options 1 and 2 is q dThe PL value / delta PL value may be notified / configured for each index of the RS / SSB / CSI-RS / SRS resource / SRS resource set. One or more RS indices and the PL value / delta PL value corresponding to each RS index may be notified by DL signaling. The PL value / delta PL value may be interpreted as a PL parameter / delta PL parameter.
[0038] FIG. 3A is a diagram showing an example of the association between RS indexes and PL values. FIG. 3B is a diagram showing an example of the association between RS indexes and delta PL values. The association (correspondence) between RS indexes and PL values / delta PL values is not limited to that shown in FIGS. 3A and 3B. For example, one RS index may correspond to multiple PL values / delta PL values. Note that a quantization table (range and step) for PL values / delta PL values may be predefined in the specifications. The notified PL values / delta PL values may be quantized values or indices of quantized values.
[0039] Figure 4 shows an example of Option 1 in UL dense deployment. The UL reception point receives / measures the UL signal. If the DL transmission point (macro TRP / gNB) knows the transmission power of this UL signal, the DL transmission point can know the exact PL value of the UL reception point. In this case, the DL transmission point can notify the UE of the absolute PL value (X [dB]) of the UL reception point.
[0040] Figure 5 shows an example of Option 2 in a UL dense deployment. When both the DL transmission point (macro TRP / gNB) and the UL reception point measure the same resource, the DL transmission point can recognize the difference between the PL between the DL transmission point and the UE and the PL between the UL reception point and the UE. In this case, the DL transmission point may notify the UE of this difference (relative PL / delta PL). The relative PL / delta PL may also be referred to as PL offset.
[0041] As described above, even if the UE is not notified of the DL RS (RS index) used for path loss estimation, the UE can calculate the transmission power using the notified PL value / delta PL value.
[0042] (TCI, spatial relationship, QCL) In NR, it is 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 a UE of at least one of a signal and a channel (referred to as a signal / channel) based on a transmission configuration indication state (TCI state).
[0043] The TCI state may represent that which is applied to a downlink signal / channel, and the equivalent of the TCI state that is applied to an uplink signal / channel may be expressed as a spatial relation.
[0044] 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.
[0045] The QCL is an index indicating the statistical properties of signals / channels. For example, if a signal / channel has a QCL relationship with another signal / channel, it may mean that it can be assumed that at least one of a Doppler shift, a Doppler spread, an average delay, a delay spread, and a spatial parameter (e.g., a spatial Rx parameter) is the same between these different signals / channels (i.e., the signals / channels have a QCL with respect to at least one of these).
[0046] The spatial reception parameters may correspond to a reception beam (e.g., a reception analog beam) of the UE, and the beam may be identified based on a spatial QCL. The QCL (or at least one element of the QCL) in the present disclosure may be replaced with sQCL (spatial QCL).
[0047] A plurality of types of QCLs (QCL types) may be defined. For example, four QCL types A to D may be provided, each having different parameters (or parameter sets) that can be assumed to be the same.
[0048] The UE's assumption 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.
[0049] 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.
[0050] The TCI state may be, for example, information about the QCL between the channel of interest (in other words, the Reference Signal (RS) for that channel) and another signal (e.g., another RS). The TCI state may be set (indicated) by higher layer signaling, physical layer signaling, or a combination thereof.
[0051] The physical layer signaling may be, for example, Downlink Control Information (DCI).
[0052] 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)).
[0053] 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 tracking CSI-RS (also called a tracking reference signal (TRS)), and a QCL detection reference signal (also called a QRS).
[0054] An SSB is a signal block including 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.
[0055] An RS of QCL type X in a TCI state may refer to an RS that has a QCL type X relationship with a certain channel / signal (DMRS), and this RS may be called a QCL source of QCL type X in the TCI state.
[0056] (UL Power Control Parameters for TCI States) Fig. 6 is a diagram showing examples of power control parameters related to TCI states. As shown in Fig. 6, the power control parameters of the path loss RS and the PUSCH / PUCCH / SRS are associated with the TCI states.
[0057] When the Rel. 17 TCI state is set, the Rel. 15 / 16 TCI state and spatial relationship information (except positioning) cannot be set in the same band. For channels / RSs that do not apply the indicated TCI state, the Rel. 17 TCI state may be set instead of the Rel. 15 / 16 TCI state and spatial relationship information.
[0058] The UE may transmit UE capability information indicating that different power control parameters are associated with each TCI state. If the UE does not support this UE capability, default power control parameters may be used. Figure 7 shows an example of the TCI-State information element in Rel. 17. The default power control parameter is, for example, the pathlossReferenceRS-Id (pathlossReferenceRS-Id-r17) in Figure 7.
[0059] (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 TCI states or spatial relationships for each channel as in Rel. 15. Instead, it may specify a common beam (common TCI state) and apply it to all UL and DL channels, or it may apply a common beam for UL to all UL channels and a common beam for DL to all DL channels.
[0060] One common beam for both DL and UL, or one common beam for DL and one common beam for UL (two common beams overall) are considered.
[0061] 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).
[0062] The default beams for UL and DL may be aligned via MAC CE based beam management (MAC CE level beam indication). The default TCI state of the PDSCH may be updated to align with the default UL beam (spatial relationship).
[0063] DCI-based beam management (DCI-level beam indication) may indicate a common beam / unified TCI state from the same TCI pool for both UL and DL (joint common TCI pool, joint TCI pool, set). 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.
[0064] 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 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.
[0065] The number of TCI states corresponding to each of one or more TRPs may be specified. For example, the number N (≧1) of TCI states applied to UL channels / RSs (UL TCI states) and the number M (≧1) of TCI states applied to DL channels / RSs (DL TCI states) may be specified. At least one of N and M may be notified / configured / instructed to the UE via higher layer signaling / physical layer signaling.
[0066] In the present disclosure, when N=M=X (X is any integer), it may mean that X TCI states (joint TCI states) common to UL and DL (corresponding to X TRPs) are notified / configured / indicated to the UE. Also, when N=X (X is any integer) and M=Y (Y may be any integer, Y=X), it may mean that X UL TCI states (corresponding to X TRPs) and Y DL TCI states (i.e., separate TCI states) (corresponding to Y TRPs) are notified / configured / indicated to the UE.
[0067] For example, when N=M=1 is written, this may mean that a TCI state common to one UL and DL for a single TRP is notified / configured / indicated to the UE (joint TCI state for a single TRP).
[0068] Also, for example, when N=1 and M=1 are written, this may mean that one UL TCI state and one DL TCI state for a single TRP are separately notified / configured / instructed to the UE (separate TCI states for a single TRP).
[0069] Also, for example, when N=M=2 is written, this may mean that a TCI state common to multiple (two) ULs and DLs for multiple (two) TRPs is notified / configured / instructed to the UE (joint TCI state for multi-TRP).
[0070] Also, for example, when N=2 and M=2 are written, this may mean that the UE is notified / configured / instructed of multiple (two) UL TCI states and multiple (two) DL TCI states for multiple (two) TRPs (separate TCI states for multi-TRP).
[0071] In the above example, the values of N and M are 1 or 2, but the values of N and M may be 3 or more, and N and M may be different.
[0072] It is being considered that N=M=1 will be supported in Rel. 17. It is being considered that other cases will be supported in Rel. 18 and later.
[0073] In the example of Figure 8A, an RRC parameter (information element) configures multiple TCI states for both DL and UL. A MAC CE may activate multiple TCI states from the configured multiple TCI states. A 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.
[0074] In the example of this figure, a point may be one TCI state that applies to both UL and DL, or two TCI states that apply to UL and DL respectively.
[0075] 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).
[0076] 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 may simply mean receiving "instruction information."
[0077] In the example of Figure 8B, 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 each of the UL and DL may be configured / activated.
[0078] The DL DCI or a new DCI format may select (indicate) one or more (e.g., one) TCI states. The selected TCI state may apply 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 apply to one or more (or all) UL channels / RSs. The UL channels may be PUSCH / SRS / PUCCH. In this way, different DCIs may indicate UL TCI and DL DCI separately.
[0079] It is assumed that in Rel. 17 NR and later, the MAC CE / DCI supports beam activation / indication to a TCI state associated with a different physical cell identifier (PCI), and in Rel. 18 NR and later, the MAC CE / DCI supports indicating a serving cell change to a cell with a different PCI.
[0080] <Channels / RSs to which the indicated TCI state in Rel. 17 applies> The indicated TCI state by the MAC CE / DCI may apply to the following channels / RSs:
[0081] <<PDCCH>> - If followUnifiedTCIState is configured for CORESET0, the indicated TCI state applies. Otherwise, the Rel. 15 specifications apply for that CORESET. That is, CORESET0 follows the TCI state activated by the MAC CE or is QCL'd with SSB. - For CORESETs with USS / CSS type 3 and index other than 0, the indicated TCI state always applies. - For CORESETs with index other than 0 and at least CSS type other than 3, if followUnifiedTCIState is configured, the indicated TCI state applies. Otherwise, the configured TCI state for that CORESET applies to that CORESET.
[0082] <<PDSCH>> - The indicated TCI state always applies to all UE-dedicated PDSCHs. - For non-UE-dedicated PDSCHs (PDSCHs scheduled by DCI in the CSS), the indicated TCI state may apply if followUnifiedTCIState is set (for the CORESET of the PDCCH that schedules that PDSCH). Otherwise, the configured TCI state for that PDSCH applies to that PDSCH. If followUnifiedTCIState is not set for a PDSCH, whether a non-UE-dedicated PDSCH follows the indicated TCI state may depend on whether followUnifiedTCIState is set for the CORESET used to schedule that PDSCH.
[0083] <<CSI-RS>> For an A-CSI-RS for CSI acquisition or beam management, if followUnifiedTCIState is set (for 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.
[0084] <<PUCCH>> - For all dedicated PUCCH resources, the indication TCI state always applies.
[0085] <<PUSCH>> - For dynamic / configured grant PUSCH, the indication TCI state always applies.
[0086] <<SRS>> When the SRS resource set for the A-SRS used for beam management and the A / SP / P-SRS used for codebook (CB) / non-codebook (NCB) / antenna switching is configured to follow the unified TCI state, the indicated TCI state applies. For other SRSs, the configured TCI state in the SRS resource set applies.
[0087] <Channels / RSs to which the indicated TCI state applies in Rel. 18> When single DCI multi-TRP is applied, the indicated TCI state may be applied to the following channels / RSs: Note that applyIndicatedTCIState={1st, 2nd, both} in the following description is a parameter indicating that the first TCI state, the second TCI state, or both the first TCI state and the second TCI state are applied.
[0088] <<PDCCH>> - For CORESET 0, followUnifiedTCIState is set and applyIndicatedTCIState={1st,2nd,both} is set to indicate that the indicated TCI state applies. Otherwise, the Rel. 15 specifications apply for that CORESET. That is, CORESET 0 follows the TCI state activated by the MAC CE or is QCL'd with SSB. - For CORESETs other than index 0 with USS / CSS type 3, applyIndicatedTCIState={1st,2nd,both} is set for each CORESET to indicate that the indicated TCI state applies. For CORESETs other than index 0 with at least a CSS other than CSS type 3, if the Unified TCI state is configured to be followed, applyIndicatedTCIState={1st,2nd,both} is set for each CORESET to indicate that the indicated TCI state applies. Otherwise, the configured TCI state for that CORESET applies to that CORESET.
[0089] <<PDSCH>> - For all UE-dedicated PDSCHs, one or both of the indicated TCI states always apply. - For PDSCHs scheduled / activated by DCI1_1 / 1_2, the 2-bit TCI state selection field of that DCI1_1 / 1_2 can indicate {1st, 2nd, both}. If the TCI state selection field is not set, both indicated TCI states apply. - For PDSCHs scheduled / activated by DCI1_0, {1st, 2nd, both} are configured by RRC. - "both" can only be configured if PDSCH-CJT or PDSCH-SFN is configured.
[0090] <<CSI-RS>> If followUnifiedTCIState is set for an A-CSI-RS for CSI acquisition or beam management (for the CORESET of the PDCCH that triggers that A-CSI-RS), applyIndicatedTCIState={1st,2nd,both} is set for each CSI-RS resource or CSI-RS resource set to indicate that the indicated TCI state applies. For other CSI-RSs, the configured TCI state for that CSI-RS resource applies.
[0091] <<PUCCH>> - applyIndicatedTCIState={1st, 2nd, both} is set for each PUCCH resource / PUCCH resource group.
[0092] <<PUSCH>> - For dynamic / configured grant PUSCH, the indicated TCI state is always applied. - For PUSCH scheduled / activated by DCI0_0, the first indicated TCI state is always applied. - For Type 1 CG PUSCH, applyIndicatedTCIState={1st,2nd,both} is set. - The SRS resource set indication field indicates one / both of the SRS resource sets used.
[0093] <<SRS>> When the SRS resource set for A-SRS used for beam management and A / SP / P-SRS used for codebook (CB) / non-codebook (NCB) / antenna switching is configured to follow the unified TCI state, applyIndicatedTCIState={1st,2nd,both} is set for each SRS resource set to indicate that the indicated TCI state applies. For other SRSs, the configured TCI state in that SRS resource set applies.
[0094] In the present disclosure, the terms "indicated TCI state," "unified TCI state," "TCI state applied to channels / signals configured to follow the unified TCI state," "TCI state applied to a UE-specific PDSCH and a CORESET / PDCCH associated with a USS," and "TCI state applied to a PUCCH and a PUSCH" may be interchangeable.
[0095] (UL Power Control Parameters for Unified TCI State in Rel. 17) In the unified TCI state in Rel. 17, the UE is provided with UL power control parameters (RRC information element "ul-powerControl-r17") included in the UE-specific UL BWP configuration (RRC information element "BWP-UplinkDedicated") (see Fig. 9A). If the UE is not configured with UL power control (ul-powerControl) for the UL TCI state / joint TCI state of the serving cell, these parameters are used for transmit power control of UL transmissions.
[0096] The UL power control parameter (RRC information element "ul-powerControl-r17") corresponds to a UL power control parameter ID (Uplink-powerControlId-r17), and the UL power control parameter is identified by this ID.
[0097] The UL power control parameters (RRC information element "uplink-powerControl-r17") corresponding to "ul-powerControl-r17" include at least one of a set of P0 and α for PUSCH (p0AlphaSetforPUSCH-r17), a set of P0 and α for PUCCH (p0AlphaSetforPUCCH-r17), and a set of P0 and α for SRS (p0AlphaSetforSRS-r17), and are used for transmission power control of each channel / signal (see FIG. 9B).
[0098] Also, in the Rel. 17 unified TCI framework, the RRC / MAC CE / DCI indicates one joint TCI or one set of {DL TCI, UL TCI} (separate TCI), where the indicated TCI applies to multiple UL / DL channels / RSs.
[0099] (Unified TCI Status for Multi-TRP in Rel. 18) In Rel. 18, the specification for unified TCI for multi-TRP has been extended. For example, in the case of multi-TRP with a single DCI, the UE may be indicated up to two joint TCIs or up to two sets of {DL TCI, UL TCI} by the RRC / MAC CE / DCI. In the case of multi-TRP with multi-DCI, the UE may be indicated one joint TCI or one set of {DL TCI, UL TCI} per coresetPoolIndex by the RRC / MAC CE / DCI. The indicated TCI applies to multiple UL / DL channels / RSs. The association of the first and second indicated TCIs with each UL / DL channel / RS may be predefined in the specification, configured by RRC signaling, or indicated by DCI.
[0100] (TCI State Switching) Rel. 15 / 16 specifies a delay time (switching delay) for switching the active TCI state for a UE configured with one or more TCI states in the serving cell.
[0101] Even if the UE measures / stores / holds the QCL characteristics, unless the UE makes an L1-RSRP report / beam report to the network (NW, for example, a base station), the NW cannot recognize whether the UE measures / stores / holds the QCL characteristics. For this reason, the UE measures and reports the beam / RS, and the UE and the NW need to have a common understanding of whether the TCI state is known or unknown.
[0102] In Rel. 16, a TCI state is known if the following conditions 0 to 5 are satisfied: (Condition 0): From the last transmission of RS resources used for reporting L1-RSRP measurements in the target TCI state until the switching of the active TCI state is completed, the RS resources for L1-RSRP measurements are RSs in the target TCI state or RSs that have a QCL relationship with the target TCI state. (Condition 1): A TCI state switch command is received within 1280 ms from the last transmission of RS resources for beam reporting or measurements. (Condition 2): The UE has transmitted at least one L1-RSRP report for the target TCI state before the TCI state switch command. (Condition 3): During the TCI state switching period, detection of the TCI state remains possible. (Condition 4): During the TCI state switching period, detection of the SSB associated with the TCI state remains possible. (Condition 5) The signal to noise ratio (SNR) in a TCI state is −3 dB or more.
[0103] The TCI state being unknown means that the TCI state is not known.
[0104] In addition, in the present disclosure, a known TCI state may be referred to as a "known TCI state," and an unknown TCI state may be referred to as an "unknown TCI state."
[0105] In the case where MAC CE is used for switching the TCI state (MAC-CE based TCI state switch), when the target TCI state (the TCI state to which switching is made) is a known TCI state, when the UE receives a physical downlink shared channel (PDSCH) including a TCI state activation command (TCI state indication) in slot n, the UE activates the TCI state in slot n+T. HARQ +3N subframe,μ slot +TO k *(T first-SSB+T SSB-proc In the first slot after slot n+T, the UE receives the physical downlink control channel (PDCCH) of the target TCI state of the serving cell where the TCI state switching occurred. HARQ +3N subframe,μ slot The PDCCH in the old (pre-switching) TCI state can be received until slot n+T. HARQ +3N subframe,μ slot From slot n+T HARQ +3N subframe,μ slot +TO k *(T first-SSB +T SSB-proc ) / (NR slot length), the TCI state that the UE applies is undefined.
[0106] Here, T HARQ indicates the timing from the transmission of a downlink data signal (for example, PDSCH) to the transmission of acknowledgement information (for example, HARQ-ACK information). subframe,μ slot represents the number of slots per subframe for the subcarrier setting μ. first-SSB T is the time from when the UE decodes the MAC CE command used to activate the TCI state until it transmits the first SSB. SSB-proc is 2 ms. k is 1 if the target TCI state is not included in the list of active TCI states for the PDSCH, otherwise it is 0. NR slot length indicates the length of the slot.
[0107] When MAC CE is used for TCI state switching and the target TCI state is unknown TCI state, if the UE receives a PDSCH containing a TCI state activation command in slot n, it will HARQ +3N subframe,μ slot +T L1-RSRP +TO uk *(Tfirst-SSB +T SSB-proc ) / (NR slot length), the UE receives the PDCCH of the target TCI state of the serving cell where the TCI state switching occurred. HARQ +3N subframe,μ slot Until then, the PDCCH in the old (pre-switching) TCI state can be received.
[0108] Here, TO uk is 1 for L1-RSRP measurements using CSI-RS or for switching of the TCI state in which a QCL type other than QCL type D is configured. uk is 0 for TCI state switching with at least QCL type D configured and for L1-RSRP measurements using SSB.
[0109] Also, T first-SSB is the time from the L1-RSRP measurement to the first SSB transmission when switching the TCI state with at least QCL type D set. first-SSB is the time until the UE first transmits an SSB after decoding a MAC CE command used to activate a TCI state other than QCL type D.
[0110] Compared to when the target TCI state is a known TCI state, when the target TCI state is an unknown TCI state, the TCI state switching L1-RSRP This requires additional time. L1-RSRP is the time associated with the received power measurement. L1-RSRP is 0 in frequency range (FR) 1 or in FR2 where QCL type D is not set. Otherwise, it is the time required to determine / refine the receive beam in FR2.
[0111] Furthermore, in the case where downlink control information (DCI) is used for TCI state switching (DCI-based TCI state switch), if the target TCI state is a known TCI state, and if the higher layer parameter tci-PresentInDCI for CORESET scheduling PDSCH in slot n is set to enabled, the UE receives the PDSCH in the target TCI state of the serving cell where the TCI state switching occurred in the first slot after slot n+timeDurationForDCI, where timeDurationForDCI is the time required for receiving the PDCCH and applying spatial relationship / QCL information (spatial QCL information) to receiving the DCI for the PDSCH.
[0112] Furthermore, when RRC signaling is used for switching the TCI state (RRC based TCI state switch), if the target TCI state is a known TCI state, when the UE receives a PDSCH carrying an RRC activation command for the TCI state in slot n, the UE RRC_processing +TO k *(T first-SSB +T SSB-proc ))) / (NR slot length), the PDCCH of the target TCI state of the serving cell where the TCI state switching occurred is received.
[0113] Here, T RRC_processing is the RRC processing delay. first-SSB is the time to the first SSB transmission after the UE RRC process. SSB-proc , T.O. k and (NR slot length) are the same as in the case of known TCI state in TCI state switching using MAC CE.
[0114] In addition, when RRC signaling is used for switching the TCI state (RRC based TCI state switch), if the target TCI state is an unknown TCI state, when the UE receives a PDSCH carrying an RRC activation command for the TCI state in slot n, the UE RRC_processing +T L1-RSRP +TO uk *(T first-SSB +T SSB-proc ))) / (NR slot length), the PDCCH of the target TCI state of the serving cell where the TCI state switching occurred is received.
[0115] Here, T RRC_processing is the RRC processing delay. SSB-proc , T.O. uk and (NR slot length) are the same as in the case of unknown TCI state in TCI state switching using MAC CE.
[0116] Also, T first-SSB is the time from the L1-RSRP measurement to the first SSB transmission when switching the TCI state with at least QCL type D set. first-SSB is the time until the UE first transmits an SSB after decoding a MAC CE command used to activate a TCI state other than QCL type D.
[0117] Rel. 17 defines a delay time (switching delay) for switching between unified TCI states.
[0118] For example, when an RRC parameter (DLorJoint-TCIState) related to the unified TCI state for the DL channel of the serving cell is configured for the UE, the specified delay time may be applied.
[0119] In MR-DC or standalone NR, this delay time also applies to all lists of multiple serving cells in simultaneous TCI update lists for multiple CCs / cells (e.g., simultaneousU-TCI-UpdateList1, simultaneousU-TCI-UpdateList2, simultaneousU-TCI-UpdateList3, simultaneousU-TCI-UpdateList4).
[0120] If the target DL TCI state refers to an additional PCI that is different from the Physical Cell ID (PCI) of the serving cell for which this DL TCI state is configured, this delay may be applied provided that the following conditions are met: the active BWP of the serving cell and the cell of the additional PCI are the same, the center frequency, subcarrier spacing (SCS) and system frame number (SFN) offset of the cell of the additional PCI are the same as those of the serving cell, and the cell of the additional PCI is known to the UE.
[0121] Also, a cell of an additional PCI may be known if the following conditions are met: The UE has sent a valid L3 measurement report for the cell of the additional PCI in the last 5 seconds before the L1-RSRP measurement is configured. The timing offset between the serving cell and the cell of the additional PCI is within the CP of the corresponding SCS.
[0122] If this condition is not met, the cells of the additional PCI may be unknown.
[0123] A DL TCI state in a unified TCI state may be known if it satisfies the following conditions: - The RS resources for L1-RSRP measurements are the RSs of the target DL TCI state or the RSs that have a QCL relationship with the target DL TCI state from the last transmission of the RS resources used for reporting L1-RSRP measurements of the target DL TCI state until the switching of the active DL TCI state is completed. - A DL TCI state switch indication (downlink TCI state switch command) is received within 1280 ms from the last transmission of the RS resources for beam reporting or measurements. - The UE has sent at least one L1-RSRP report for the target DL TCI state before the DL TCI state switch indication. - Detection of the DL TCI state remains possible during the DL TCI state switching period. During the DL TCI state switching period, detection of the SSB associated with the DL TCI state remains possible. The Signal to Noise Ratio (SNR) in the DL TCI state is -3 dB or greater.
[0124] The SSB may be associated with the PCI of the serving cell or a PCI different from the serving cell PCI.
[0125] If the above conditions are not met, the DL TCI status may be unknown.
[0126] In the case of joint TCI state switching, if the target PL-RS is not maintained, the UE may not be expected to receive in the DL based on the target TCI state before completing the switch of DL and UL TCI states.
[0127] When MAC CE is used for switching the DL TCI state (MAC-CE based downlink TCI state switch), if the target TCI state (the TCI state to which switching is made) is a known TCI state, when the UE receives a PDSCH including a TCI state activation command (TCI state indication) in slot n, the UE activates the TCI state in slot n+T. HARQ +3N subframe,μ slot +TO k *(T first-SSB +T SSB-proc In the first slot after slot n+T, the UE receives a physical downlink control channel (PDCCH) in the target TCI state of the serving cell where the TCI state switching occurred. HARQ +3N subframe,μ slot The UE can receive the UE-specific PDSCH / PDCCH using the old (pre-switching) TCI state until slot n+T. HARQ +3N subframe,μ slot From slot n+T HARQ +3N subframe,μ slot +TO k *(T first-SSB +T SSB-proc ) / (NR slot length), the TCI state that the UE applies is not specified.
[0128] Here, T HARQ indicates the timing from the transmission of a downlink data signal (for example, PDSCH) to the transmission of acknowledgement information (for example, HARQ-ACK information). subframe,μ slot represents the number of slots per subframe for the subcarrier setting μ. first-SSB T is the time from when the UE decodes the MAC CE command used to activate the TCI state until it transmits the first SSB. SSB-proc is 2 ms. kis 1 if the target TCI state is not included in the list of active TCI states for the PDSCH, otherwise it is 0. NR slot length indicates the length of the slot.
[0129] When using MAC CE for DL TCI state switching and the target TCI state is unknown TCI state, if the UE receives a PDSCH containing a TCI state activation command in slot n, it will HARQ +3N subframe,μ slot +T L1-RSRP +TO uk *(T first-SSB +T SSB-proc ) / (NR slot length), the UE receives the PDCCH of the target TCI state of the serving cell where the TCI state switching occurred. HARQ +3N subframe,μ slot Until then, the UE can receive the UE-specific PDSCH / PDCCH using the old (pre-switching) TCI state.
[0130] Here, TO uk is 1 for L1-RSRP measurements using CSI-RS or for switching of the TCI state in which a QCL type other than QCL type D is configured. uk is 0 for TCI state switching with at least QCL type D configured and for L1-RSRP measurements using SSB.
[0131] Also, T first-SSB is the time from the L1-RSRP measurement to the first SSB transmission when switching the TCI state with at least QCL type D set. first-SSB is the time until the UE first transmits an SSB after decoding a MAC CE command used to activate a TCI state other than QCL type D.
[0132] Compared to when the target TCI state is a known TCI state, when the target TCI state is an unknown TCI state, the TCI state switching L1-RSRP This requires additional time. L1-RSRP is the time associated with the received power measurement. L1-RSRP is 0 in frequency range (FR) 1 or in FR2 where QCL type D is not set. Otherwise, it is the time required to determine / refine the receive beam in FR2.
[0133] Also, for example, when an RRC parameter related to the unified TCI state (DLorJoint-TCIState (when unifiedTCI-StateType indicates Joint) or UL-TCIState) is configured for the UE for the UL channel / signal of the serving cell, the specified delay time may be applied.
[0134] In MR-DC or standalone NR, this delay time also applies to all lists of multiple serving cells in simultaneous TCI update lists for multiple CCs / cells (e.g., simultaneousU-TCI-UpdateList1, simultaneousU-TCI-UpdateList2, simultaneousU-TCI-UpdateList3, simultaneousU-TCI-UpdateList4).
[0135] Regarding the UL TCI state (or the joint TCI state), the known / unknown status of the cell of the additional PCI and the known / unknown status of the UL TCI state are the same as those obtained by replacing the "DL TCI state" of the known / unknown status of the cell of the additional PCI and the TCI state for the above DL TCI state with "UL TCI state (or the joint TCI state)."
[0136] In the case of a joint TCI state switch, the UE may not be expected to transmit on the UL before the switch of DL and UL TCI states is complete.
[0137] When MAC CE is used for switching between separate UL TCI states and joint TCI states for UL channels / signals (MAC-CE based uplink TCI state switch), if the target TCI state (the TCI state to which the UE is switched) is a known TCI state, when the UE receives a PDSCH including a TCI state activation command (TCI state indication) in slot n, the UE activates the TCI state in slot n+T. HARQ +3N subframe,μ slot + NM * (T first-target-PL-RS +4*T target-PL-RS +2 ms) / (NR slot length), the UL signal in the target TCI state can be transmitted, where the UL channel / signal can be PUCCH, PUSCH, or semi-persistent / periodic / aperiodic SRS (when beamCorrespondenceWithoutUL-BeamSweeping is set to 1).
[0138] Also, when MAC CE is used for switching between separate UL TCI state and joint TCI state for UL channels / signals, and the target TCI state is unknown TCI state, when the UE receives a PDSCH including a TCI state activation command (TCI state indication) in slot n, the UE activates the TCI state in slot n+T. HARQ +3N subframe,μ slot + (T L1-RSRP +T first-target-PL-RS +4*T target-PL-RS +2 ms) / (NR slot length), a UL signal in the target TCI state can be transmitted.
[0139] Here, T HARQ indicates the timing from the transmission of a downlink data signal (for example, PDSCH) to the transmission of acknowledgement information (for example, HARQ-ACK information). subframe,μ slot represents the number of slots per subframe for the subcarrier setting μ. NR slot length indicates the length of the slot.
[0140] NM is 1 if the target PL-RS is maintained, and 0 otherwise.
[0141] T target-PL-RS is the time until the first path loss RS is transmitted after the L1-RSRP measurement when the target TCI state is unknown. target-PL-RS is the time to the first pathloss RS transmission after the MAC CE command is decoded by the UE when the target TCI state is known.
[0142] T target-PL-RS is the period of the target PL-RS, which is an SSB or NZP CSI-RS, if the PL-RS is associated with the serving cell. target-PL-RS is the period of the PL-RS that becomes the SSB when the PL-RS is associated with a PCI different from the serving cell.
[0143] Compared to when the target TCI state is a known TCI state, when the target TCI state is an unknown TCI state, the TCI state switching L1-RSRP This requires additional time. L1-RSRP is the time associated with the received power measurement. L1-RSRP is 0 in frequency range (FR) 1 or in FR2 where QCL type D is not set. Otherwise, it is the time required to determine / refine the receive beam in FR2.
[0144] (Timing Advance) Timing Advance (TA) is used for UL timing adjustment. In the existing specification (Rel. 17), the UL frame number i for transmission from the UE is set to a specific time (e.g., T TA ) before
[0145] The specific time is, for example, T TA =(N TA +N TA,offset +N common TA,adj +N UE TA,adj )TC N common TA,adj and N UE TA,adj may be 0 regardless of the examples of this disclosure when used in NTN (non-terrestrial network).
[0146] where N TA is the timing advance between DL and UL, TA,offset defines a fixed offset used in calculating the timing advance, N common TA,adj is the network-controlled timing correction, N UE TA,adj is the UE-derived timing correction, T C may respectively indicate the Basic time unit for NR.
[0147] For example, in the random access preamble transmission and the message A PUSCH transmission, N TA is 0 and N TA,offset applies.
[0148] (Timing Advance Group) When multiple TRPs are used, the distances between the UE and each TRP may be different. The multiple TRPs may be included in the same cell (e.g., serving cell). Alternatively, one TRP among the multiple TRPs may correspond to the serving cell and the other TRPs may correspond to non-serving cells. The multiple TRPs may include DL transmission points and UL reception points. In this case, it is assumed that the distances between each TRP and the UE may be different.
[0149] In existing systems, the transmission timing of an uplink (UL) channel and / or an UL signal (UL channel / signal) is adjusted by timing advance. The reception timing of the UL channel / signal from different user terminals (UE) is adjusted by a radio base station (TRP: Transmission and Reception Point, also referred to as gNodeB: gNB) side.
[0150] The UE may control the timing of UL transmission by applying timing advance (multiple timing advances) for each pre-configured timing advance group (TAG).
[0151] When multiple timing advances are applied, Timing Advance Groups (TAGs) classified by transmission timing are supported. The UE may control the UL transmission timing for each TAG assuming that the same TA offset (or TA value) is applied to each TAG. In other words, the TA offset may be set independently for each TAG.
[0152] When multiple timing advance is applied, the UE independently adjusts the transmission timing of cells belonging to each TAG, so that even when multiple cells are used, the radio base station can synchronize the reception timing of uplink signals from the UE.
[0153] TAGs (e.g., serving cells belonging to the same TAG) may be configured by higher layer parameters. The same timing advance value may be applied to serving cells (e.g., serving cells for which UL is configured) belonging to the same TAG. A timing advance group including the SpCell of a MAC entity may be called a Primary Timing Advance Group (PTAG), and other TAGs may be called Secondary Timing Advance Groups (STAGs). In addition, the maximum number of TAGs may be X (e.g., X=4) per cell group (e.g., MCG / SCG).
[0154] (Analysis) As mentioned above, in order to expand UL coverage, the installation of UL receiving points in addition to general transmitting and receiving points is being considered. Also, UL high-density deployment / Heterogeneous Network (HetNet) using DL transmitting points / macro Base Stations (BS) and UL receiving points / micro BSs is being considered.
[0155] However, when an RS (path loss RS) for path loss (PL) calculation is transmitted from a DL transmission point, it is not clear how to determine the transmission power when a terminal performs UL transmission to an UL reception point.
[0156] As an example, it is being considered to set a PL offset for a UL channel / signal for each UL channel, but a specific method for setting the PL offset is not clear.
[0157] If the method for determining the transmission power is not clear, the UL transmission power cannot be controlled appropriately, which may hinder improvement in communication throughput.
[0158] Therefore, the present inventors have conceived a method for appropriately controlling UL transmission power.
[0159] 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.
[0160] (Various Reinterpretations) In the present disclosure, a word enclosed in "( )" in a sentence may indicate an explanation of the word immediately preceding it (for example, an explanation of spelling), a paraphrase, a specific example, a supplementary explanation, etc. Furthermore, in the present disclosure, a word enclosed in "[ ]" in a sentence may be interpreted including the word in the meaning of the entire sentence, or may be interpreted excluding (ignoring) the word in the meaning of the entire sentence. Note that "( )" and "[ ]" may also be used for purposes / meanings other than those mentioned above.
[0161] 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."
[0162] In the present disclosure, terms such as notify, activate, deactivate, indicate (or indicate), select, configure, update, and determine may be read interchangeably. In the present disclosure, terms such as support, control, controllable, operate, and operate may be read interchangeably.
[0163] 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.
[0164] 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.
[0165] 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.
[0166] In the present disclosure, physical layer signaling may be, for example, Downlink Control Information (DCI), Uplink Control Information (UCI), and the like.
[0167] In the present disclosure, the terms drop, abort, cancel, puncture, rate match, postpone, do not transmit, etc. may be read interchangeably.
[0168] In the present disclosure, the terms panel, UE panel, panel group, beam, beam group, precoder, Uplink (UL) transmitting entity, Transmission / Reception Point (TRP), base station, Spatial Relation Information (SRI), spatial relation, SRS Resource Indicator (SRI), Control Resource Set (CORESET), Physical Downlink Shared Channel (PDSCH), Codeword (CW), Transport Block (TB), Reference Signal (RS), antenna port (e.g., Demodulation Reference Signal (DMRS) port), antenna port group (e.g., DMRS port group), group (e.g., spatial relation group, Code Division Multiplexing (CDM) group, reference signal group, CORESET group, Physical Uplink Control Channel (PUCCH) group, PUCCH resource group), resource (e.g., reference signal resource, SRS resource), resource set (e.g., reference signal resource set), CORESET pool, downlink Transmission Configuration Indication state (TCI state) (DL TCI state), uplink TCI state (UL TCI state), unified TCI state, common TCI state, Quasi-Co-Location (QCL), QCL assumption, etc. may be read as interchangeable.
[0169] In the present disclosure, the terms single TRP, channel / signal using single TRP, channel using one TCI state / spatial relationship, multi-TRP not enabled by RRC / DCI, multiple TCI states / spatial relationships not enabled by RRC / DCI, a CORESETPoolIndex value of 1 not set for any CORESET, and no code point in the TCI field mapped to two TCI states may be read interchangeably.
[0170] In the present disclosure, multi-TRP, channel / signal using multi-TRP, channel using multiple TCI states / spatial relationships, multi-TRP enabled by RRC / DCI, multiple TCI states / spatial relationships enabled by RRC / DCI, and at least one of multi-TRP based on a single DCI and multi-TRP based on multiple DCI may be read interchangeably.
[0171] In the present disclosure, single DCI (sDCI), single PDCCH, multi-TRP system based on single DCI, sDCI-based MTRP, and activation of two TCI states on at least one TCI codepoint may be read interchangeably.
[0172] In the present disclosure, multi-DCI (mDCI), multi-PDCCH, multi-TRP system based on multi-DCI, mDCI-based MTRP, and setting two CORESET pool indices or CORESET pool index = 1 (or a value greater than or equal to 1) may be read interchangeably.
[0173] In the present disclosure, the terms cell, PCI, serving cell, source serving cell, source cell, CC, BWP, BWP within a CC, and band may be interchangeable. In the present disclosure, the terms cell, PCI, cell with an additional PCI, additional cell, other cell, non-serving cell, cell with a different PCI, candidate cell, candidate serving cell, cell with a PCI different from the PCI of the current serving cell, another serving cell, target cell, neighbor cell, and inter-RAT neighbor cell may be interchangeable. The target cell may be a cell selected from multiple candidate cells. In the present disclosure, the terms switch, change, and update may be interchangeable. The term serving cell may be interchangeable with the serving cell before the switch or the serving cell after the switch.
[0174] The UL reception point may be connected to a TRP (e.g., a base station) or a core network via wired or wireless. The UL reception point may be treated as a network (NW) or a base station. The UL reception point may be capable of transmitting downlink (DL) signals (e.g., PL values) and may be applied to base stations forming a macrocell. For example, the UL reception point may not transmit downlink data but may transmit control signals / channels.
[0175] In the present disclosure, the terms base station, TRP, UL receiving point, UL TRP, UL only TRP, micro cell, micro BS, and micro TRP may be interchangeable. An UL receiving point primarily performs UL reception. An UL receiving point may perform only UL reception, or may perform UL reception and DL transmission.
[0176] In the present disclosure, the terms base station, TRP, DL transmission point, DL TRP, DL only TRP, UL / DL TRP, macro cell, macro BS, macro TRP, and central TRP may be interchangeable. A DL transmission point primarily performs DL transmission. A DL transmission point may perform only DL transmission, or may perform UL reception and DL transmission.
[0177] In the present disclosure, UL high density deployment, distributed TRP mode, separated location mode of transmitting / receiving points, distributed transmitting / receiving mode, separated TRP mode, TRP type 1, TRP type 2, TRP type A, and TRP type B may be read interchangeably.
[0178] The present disclosure may assume at least one of single TRP, multi-TRP with multi-DCI, multi-TRP with single DCI, scenario 1 or scenario 2 above.
[0179] In the present disclosure, being set and receiving a setting (setting information) may be read interchangeably.
[0180] In the present disclosure, TCI, TCI state, TCI state ID, TCI state list / set / pool / group, and TCI state list / set / pool / group ID may be read interchangeably.
[0181] In the present disclosure, a set of TCI states (separate TCI states) may refer to a set of UL TCI states and DL TCI states. The TCI state may refer to a TCI-State information element, which is an RRC information element.
[0182] In the present disclosure, the terms "indicated TCI state," "unified TCI state," "unified TCI state in which multi-TRP is not configured / used / applied," "unified TCI state defined in Rel. 17," "Rel. 17 unified TCI state," and "first unified TCI state" may be interchangeable.
[0183] In the present disclosure, the terms "indication TCI state," "unified TCI state," "unified TCI state in which multi-TRP is configured / used / applied," "unified TCI state in which multi-TRP can be configured / used / applied," "indication TCI state in which multi-TRP is configured / used / applied," "indication TCI state in which multi-TRP can be configured / used / applied," "unified TCI state specified in Rel. 18," "Rel. 18 unified TCI state," "unified TCI state for multi-TRP," and "second unified TCI state" may be interpreted interchangeably.
[0184] In the present disclosure, the terms "DCI-indicated TCI state," "indicated TCI state," "indicated TCI state," "unified TCI state," "TCI state applied to multiple types of channels / signals," "joint TCI state (for DL and UL)," "DL TCI state," "UL TCI state," "Rel. 17 TCI state," "common TCI state," "single unified TCI state configured," and "single unified TCI state activated" may be read interchangeably.
[0185] In the present disclosure, the terms TCI state set by RRC parameters, configured TCI state, set TCI state, TCI state that does not conform to the unified TCI state, TCI state other than the unified TCI state, TCI state / spatial relationship set for a specific channel / signal, and individual TCI state may be read interchangeably.
[0186] The unified / common TCI state may refer to the indicated TCI state indicated using DCI / MAC CE / RRC (in Rel. 17).
[0187] The indicated TCI state may be shared with at least one of the UE-specific reception of PDSCH / PDCCH (updated using Rel. 17 DCI / MAC CE / RRC), PUSCH of dynamic grant (DCI) / configured grant, and multiple (e.g., all) dedicated PUCCH resources. The TCI state indicated by DCI / MAC CE / RRC may be referred to as the indicated TCI state.
[0188] If the indicated TCI state is supported (in Rel. 17), a TCI state other than the unified TCI state may refer to the TCI state configured using MAC CE / RRC (in Rel. 17) (configured TCI state).
[0189] The configured TCI state may not be shared with at least one of the UE-specific reception of PDSCH / PDCCH (updated using DCI / MAC CE / RRC in Rel. 17), PUSCH of dynamic grant (DCI) / configured grant, and multiple (e.g., all) dedicated PUCCH resources. The configured TCI state may be configured by RRC / MAC CE per CORESET / per resource / per resource set, and may not be updated even if the indicated TCI state is updated.
[0190] In the present disclosure, a first TRP may correspond to a first TCI state. In the present disclosure, a second TRP may correspond to a second TCI state. In the present disclosure, an n-th TRP may correspond to an n-th TCI state.
[0191] In the present disclosure, a first CORESET pool index value (e.g., 0), a first TRP index value (e.g., 1), and a first TCI state (first DL / UL (joint / separate) TCI state) may correspond to each other. In the present disclosure, a second CORESET pool index value (e.g., 1), a second TRP index value (e.g., 2), and a second TCI state (second DL / UL (joint / separate) TCI state) may correspond to each other.
[0192] In the present disclosure, TA, TAG, and TA offset value may be interchangeable. DL reference timing and DL reception timing may be interchangeable. Two TAs / TAGs may be interchangeable with more than two TAs / TAGs.
[0193] In the present disclosure, the terms absolute PL, path loss (PL), PL value, and PL parameter may be interchangeable. O The offset of α, the offset of power / power density [x dBm], the path loss (PL), the PL value, and the PL parameter may be interchangeable. In the present disclosure, the PL, the PL value, the PL RS, and the PL RSID may be interchangeable.
[0194] In the present disclosure, using a relative PL (PL offset) value may mean using a PL value obtained by applying (adding or subtracting) a received (set) relative PL (PL offset) value to a PL value estimated based on a DL RS transmitted from a macro TRP to calculate the transmission power of an UL signal to be transmitted to a UL reception point.
[0195] In the present disclosure, the terms UL channel, UL signal, UL RS, UL channel / signal, etc. may be interchangeable. The UL channel / signal in the present disclosure may be interchangeable with any UL channel / signal (e.g., PRACH / PUSCH / PUCCH / SRS).
[0196] In this disclosure, the PL offset corresponding to the UL TRP / UL reception point may be simply referred to as the "PL offset."
[0197] (Wireless Communication Method) <Tenth Embodiment> The tenth embodiment relates to application / setting of a PL offset.
[0198] The PL offset setting may apply (may be applicable) to UL TCI conditions [only].
[0199] The setting of the PL offset may not apply (may not be applicable) to the joint / DL TCI state.
[0200] The PL offset setting (parameter) may be included in the UL TCI state setting (parameter).
[0201] The setting (parameter) of the PL offset may be set outside the setting (parameter) of the UL TCI state. In this case, the setting (parameter) of the PL offset may be associated with the setting (parameter) of the UL TCI state.
[0202] In the joint / DL TCI state, the QCL source is only CSI-RS or SSB, and SRS cannot be configured as the QCL source RS. However, (especially when PL RS is transmitted from a non-collocated DL TRP and when PL offset setting is used for transmit power control (TPC)) DL RS may not be transmitted from the UL TRP. Therefore, it is considered inappropriate to use the joint / DL TCI state for PL offset setting. In the case of the UL TRP, it is preferable that the NW (base station) configures SRS as the QCL source RS in the UL TCI state and uses SRS-based beam sweeping for UL beam direction.
[0203] For DL / UL TCI states, different QCL source RSs may be configured as the QCL source RSs for the TCI states.
[0204] The UE may determine the QCL source RS of the UL TCI state corresponding to each TRP and the QCL source RS of the DL TCI state corresponding to each TRP based on the TRP in which the UE transmits the UL signal.
[0205] If the UE transmits an UL signal for a DL TRP, the QCL source RS of a particular UL TCI state (e.g., the UL TCI for the DL TRP (e.g., UL TCI#0)) may be the same as the QCL source RS of a particular DL TCI state (e.g., the DL TCI for the DL TRP (e.g., DL TCI#0 (e.g., CSI-RS / SSB#0 from the DL TRP))).
[0206] If a UE transmits an UL signal for a DL TRP, the QCL source RS for a particular UL TCI state (e.g., UL TCI #0) may be a different QCL source RS (e.g., QCL source RS (e.g., SRS #1) for a UL TCI (e.g., UL TCI #1) for the UL TRP) from the QCL source RS for a particular DL TCI state (e.g., QCL source RS for DL TCI #0 (e.g., CSI-RS / SSB #0 from the DL TRP)).
[0207] If the UE transmits an UL signal for a UL TRP, the QCL source RS for a particular UL TCI state (e.g., the QCL source RS for UL TCI #1 (e.g., SRS #1)) may be a different QCL source RS from the QCL source RS for a particular DL TCI state (e.g., DL TCI #0 (e.g., CSI-RS / SSB #0 from the DL TRP)). In this case, the PL offset may be configured in the UL TCI state #1.
[0208] If a PL offset is applied / configured in the UL TCI state, the QCL source RS in the UL TCI state may be different from the QCL source RS in the corresponding (paired) DL TCI state.
[0209] If a PL offset is applied / configured in the UL TCI state, the QCL source RS in the UL TCI state may be (or may correspond to) the SRS [resource].
[0210] 10A is a diagram showing an example of setting / application of a PL offset in the 0th embodiment. In the example shown in FIG. 10A, a UE transmits a UL signal for a DL TRP. The PL-RS for the DL TRP is SSB#0, and the DL TCI state and UL TCI state corresponding to the DL TRP are DL TCI#0 and UL TCI#1, respectively.
[0211] At this time, the PL offset is not configured (absent) in the UL TCI#0 configuration for the UE.
[0212] 10B is a diagram showing another example of setting / applying a PL offset in the 0th embodiment. In the example shown in FIG. 10B, the UE transmits a UL signal for UL TRP #1. The PL-RS for the DL TRP is SSB #0, the DL TCI state corresponding to the DL TRP is DL TCI #0, and the UL TCI state corresponding to UL TRP #1 is UL TCI #1.
[0213] At this time, a PL offset (for example, X1 [dB]) is set for the UE in the UL TCI#1 configuration.
[0214] The 0th embodiment may be applied only to settings in a specific frequency range (for example, FR2 / 2-1 / 2-2).
[0215] Also, the TCI state ID of the UL TCI state for the DL TRP may be different from the TCI state ID of the UL TCI state for the UL TRP. The UE may determine which UL UCI state to use based on the configuration / instruction by the RRC / MAC CE / DCI.
[0216] According to the above-described 0th embodiment, it is possible to appropriately set a PL offset for a UL TRP.
[0217] First Embodiment The first embodiment relates to a method for setting a PL offset.
[0218] Different PL offset settings may be used based / dependent / according to the target channel / signal (RS).
[0219] The target channel / signal (RS) may be, for example, any UL channel / signal (eg, PUSCH / PUCCH / SRS / PRACH).
[0220] For example, different PL offset settings may be used based / depending / according to the target channel / signal.
[0221] For example, for the first UL channel / signal (eg, PUSCH / PUCCH / SRS( / PRACH)), the PL offset value may be configured per UL TCI state.
[0222] Also, for example, for a second UL channel (e.g., PRACH ( / PUSCH / PUCCH / SRS)), the PL offset value may be configured as a set / list of PL offset values in the configuration of the second UL channel. For example, one PL offset value for the PDCCH order PRACH may be indicated by the PDCCH.
[0223] For example, a common PL offset setting may be used based / dependent / according to the target channel / signal.
[0224] For example, for [all] UL channels / signals (e.g., PUSCH / PUCCH / SRS / PRACH), the PL offset value may be configured per UL TCI state or may be configured as a set / list of PL offset values in the configuration of that UL channel / signal.
[0225] 11A is a diagram illustrating an example of a configuration of a PL offset according to the first embodiment. In the example illustrated in FIG. 11A, a serving cell configuration (ServingCellConfig) includes configurations for each channel / RS (PRACH / PUSCH / PUCCH / SRS).
[0226] In the example shown in FIG. 11A, a PL offset [value] list is set only for the PRACH, and for the PUSCH / PUCCH / SRS, a PL offset [value] is set for each TCI state.
[0227] 11B is a diagram illustrating another example of the configuration of the PL offset according to the first embodiment. In the example illustrated in FIG. 11B, the serving cell configuration (ServingCellConfig) includes configuration for each channel / RS (PRACH / PUSCH / PUCCH / SRS).
[0228] In the example shown in FIG. 11B, a PL offset [value] list is set for each TCI state for PRACH / PUSCH / PUCCH / SRS.
[0229] As described above, according to the first embodiment, it is possible to appropriately set the PL offset for each channel / RS.
[0230] Second Embodiment The second embodiment relates to restrictions on the indicative TCI state.
[0231] <<Embodiment 2-1>> In the existing specifications, whether or not to apply the SRS indication TCI state for SRS is specified by UE capability information that is separate from other UL channels.
[0232] Whether to apply a PL offset for each indicated TCI state (UL TCI state) may be based on support of specific (Rel. 17) UE capability information.
[0233] The UE may report UE capability information regarding the application of the indicated TCI state for SRS.
[0234] If the UE supports the unified TCI state for SRS, the PL offset in the indicated TCI state may be applied.
[0235] When the UE reports UE capability information regarding the application of an indicated TCI state for SRS, the UE may assume that the PL offset in the indicated TCI state is applied.
[0236] If the UE does not support the unified TCI state for SRS, the PL offset in the indicated TCI state may not be applied.
[0237] The PL offset may not be applied to an SRS that does not apply the indicated TCI state.
[0238] In this case, the SRS may be transmitted [only] for the DL TRP.
[0239] In this case, a PL offset may be indicated / applied to other UL channels (e.g., PRACH / PUSCH / PUCCH).
[0240] Furthermore, the PL offset set in the configured TCI state for the SRS may be applied to the SRS.
[0241] In addition, for a specific UL channel (e.g., PUSCH / PUCCH), the indicated TCI state (e.g., in the case of a single DCI multi-TRP, either / both of the indicated TCI states) may be applied, and the configured TCI state may not be applied.
[0242] <<Embodiment 2-2>> In the existing specifications, in the case of the Rel. 17 / 18 unified TCI state, for basic UE capabilities, the UE assumes that the PL-RS is the same as (is QCLed to) the QCL source RS.
[0243] If the PL offset configuration is applied to a joint TCI state, the characteristics on which the PL offset configuration is based may be based on the UE capabilities.
[0244] It should be noted that if the PL offset is applied only to the UL TCI state, the characteristics on which the PL offset is configured may not be based on the UE capabilities.
[0245] <<Embodiment 2-3>> In the existing specifications, the application of different TPC parameters for PUSCH / PUCCH / SRS for each TCI state is specified by different UE capability information.
[0246] The PL RS may be configured in the joint / DL TCI state as defined in Rel. 17 / 18.
[0247] The UE may assume that a PL offset is configured for each UL TCI state, regardless of any additional configuration / association of TPC parameters for UL channels / RS (e.g., PUSCH / PUCCH / SRS) in the TCI state.
[0248] Also, if no additional configuration / association of TPC parameters for UL channels / RS (e.g., PUSCH / PUCCH / SRS) in the TCI state is configured, the UE may assume that no PL offset applies / is not configured for the TCI state.
[0249] According to the second embodiment, it is possible to appropriately define the PL offset for the indicated TCI state.
[0250] Third Embodiment In Rel. 17 / 18, the application timing (Beam Application Timing (BAT)) of the unified TCI state (indicated TCI state) was specified.
[0251] For DCI-based TCI indication, the BAT starts applying the indication TCI state after the period set by the RRC parameter BeamAppTime_r17 (e.g., {1, 2, 4, 7, 14, 28, 42, 56, 70, 84, 98, 112, 224, 336} symbols) has elapsed since the transmission of HARQ-ACK for the beam indication DCI or the PDSCH scheduled by the beam indication DCI.
[0252] In the BAT for MAC CE-based TCI indication, the indication TCI state is updated 3 ms after the transmission of a positive HARQ-ACK for a PDSCH carrying a MAC CE, similar to the application timing of MAC CE.
[0253] Also, as mentioned above, the switching delay of the active TCI state with respect to the unified TCI state is specified.
[0254] Therefore, in this embodiment, the timing of applying the PL offset will be described.
[0255] The UE may determine the timing of applying / updating the PL offset set / associated with the TCI state (indicated TCI state) based on the timing of applying / updating the TCI state (indicated TCI state).
[0256] <<Embodiment 3-1>> For example, when a PL offset is configured / associated with a TCI state (indicated TCI state), the UE may determine to apply / update the PL offset at the same timing as the update / application timing / switching delay of the indicated TCI state.
[0257] 12A is a diagram showing an example of updating a PL offset according to embodiment 3-1. In the example shown in FIG. 12A, a UE receives a beam instruction DCI and a PDSCH scheduled by the beam instruction DCI, and transmits a HARQ-ACK corresponding to the PDSCH. After transmitting the HARQ-ACK, the UE determines to apply / update the indicated TCI state and apply a PL offset corresponding to the indicated TCI state after a period (BAT) indicated by a specific RRC parameter (e.g., BeamAppTime_r17) has elapsed.
[0258] Although FIG. 12A has been described taking DCI-based TCI state indication as an example, the present embodiment can also be applied to MAC CE-based TCI state indication and TCI state switching delay.
[0259] According to embodiment 3-1, the implementation of the UE can be facilitated.
[0260] <<Embodiment 3-2>> Furthermore, for example, when a PL offset is set / associated with a TCI state (indicated TCI state), the UE may determine to apply / update the PL offset at a timing based on a timing related to an update / application timing / switching delay of the indicated TCI state and a specific offset (e.g., Y symbols / ms).
[0261] The value Y may be specified in advance in a specification, may be configured / instructed to the UE using RRC / MAC CE / DCI, may be determined based on a report of UE capability information, or may be determined based on a combination of at least two of these.
[0262] For example, when a PL offset is set / associated with a TCI state (indicated TCI state), the UE may determine to apply / update the PL offset at a timing obtained by adding (or subtracting) a specific offset to the timing related to the update / application timing / switching delay of the indicated TCI state.
[0263] 12B is a diagram showing an example of updating a PL offset according to embodiment 3-2. In the example shown in FIG. 12B, a UE receives a beam instruction DCI and a PDSCH scheduled by the beam instruction DCI, and transmits a HARQ-ACK corresponding to the PDSCH. After transmitting the HARQ-ACK, the UE applies / updates the indication TCI state after a period (BAT) indicated by a specific RRC parameter (e.g., BeamAppTime_r17) has elapsed.
[0264] In the example shown in FIG. 12B, the UE further determines to apply the PL offset corresponding to the indicated TCI state after Y symbols have elapsed since the timing of updating / applying the indicated TCI state.
[0265] Although FIG. 12B has been described taking DCI-based TCI state indication as an example, application of this embodiment is also applicable to MAC CE-based TCI state indication and TCI state switching delay.
[0266] According to embodiment 3-2, it is possible to set a rule that appropriately takes into account the timing required to update the transmission power of the UE.
[0267] According to the third embodiment, the PL offset can be applied / updated at an appropriate timing.
[0268] <Fourth Embodiment> The fourth embodiment relates to MAC CE-based PL offset updating.
[0269] The UE may update the PL offset using the MAC CE.
[0270] <<Embodiment 4-1>> For a UE, a set of PL offsets may be configured for each BWP / serving cell / UE / CORESET pool index.
[0271] The MAC CE for PL offset update may include fields for at least one of the following: Serving cell ID, BWP ID, PL offset (PLO) ID, PL offset value [corresponding to PLO ID], and reserved bits.
[0272] If a set of PL offsets is configured for each serving cell, the field related to the BWP ID may be ignored or replaced with a reserved bit.
[0273] If a set of PL offsets is configured per UE, the field related to the serving cell ID / BWP ID may be ignored or replaced with a reserved bit.
[0274] When a set of PL offsets is configured for each CORESET pool index, a specific field in the MAC CE (e.g., one reserved bit field) may be replaced with a field indicating the value (0 or 1) of the CORESET pool index.
[0275] <<Embodiment 4-2>> The number of PL offset values may be set / defined.
[0276] The size of the PLO ID field may be expressed as log2(number of PL offset values) (or Ceil(log2(number of PL offset values))). In this disclosure, CeilA may refer to the output of the ceiling function of A.
[0277] For example, if a maximum of four PL offset values are set, the PLO ID field may be defined as two bits.
[0278] <<Embodiment 4-3>> A range (for example, maximum value / minimum value / step size) of the PL offset value field may be set / defined.
[0279] The size of this field may be expressed in log2(number of different values of PL offset) (or Ceil(log2(number of different values of PL offset))).
[0280] For example, if the range of PL offset values is specified as {0, 1, ..., 31} dB (i.e., minimum value = 1, maximum value = 31, 1 dB step size), the size of this field may be 5 bits.
[0281] <<Embodiment 4-4>> The number of PL offset values indicated by one MAC CE may be set / defined.
[0282] <<<Embodiment 4-4-A>>> For example, one MAC CE may indicate one PL offset value corresponding to one PLO ID.
[0283] In this case, the MAC CE may include a field indicating a serving cell ID, a field indicating a BWP ID, a field indicating one PLO ID, a field indicating one PL offset value, and a reserved bit field (see FIG. 13).
[0284] <<<Embodiment 4-4-B>>> For example, one MAC CE may indicate multiple PL offset values, each of which may correspond to one (different) PLO ID.
[0285] For example, as shown in Figure 14A, one MAC CE may include a field indicating four PL offset values, each of which may correspond to a different PLO ID (e.g., PLO ID 1-4).
[0286] For example, as shown in Fig. 14B, one MAC CE may have a configuration that does not include some of the reserved bit fields included in the MAC CE described in the above-mentioned Fig. 14A. Note that the positions of the reserved bits in the MAC CE shown in Fig. 14B are not limited to this example.
[0287] Also, for example, one MAC CE may include a PLO ID and a PL offset value corresponding to the PLO ID, as shown in Fig. 15. The PLO ID field and the corresponding PL offset value field may be located in the same octet.
[0288] 15, the Cn field located in the same octet as the nth PLO ID / PL offset value may be a field indicating the presence of a field related to the (n+1)th PLO ID / PL offset value. When the Cn field indicates a first value (e.g., 0 (or 1)), it may indicate the presence of a field related to the (n+1)th PLO ID / PL offset value, and when the Cn field indicates a second value (e.g., 1 (or 0)), it may indicate the absence of a field related to the (n+1)th PLO ID / PL offset value.
[0289] <<<Embodiment 4-4-C>>> For example, one MAC CE may indicate one or more PL offset values for each TCI state (TCI state ID).
[0290] <<<<<Embodiment 4-4-C-1>>>> One MAC CE may be used to indicate one set of PL offset values for each TCI state [ID].
[0291] For example, as shown in FIG. 16A, one MAC CE includes a TCI state ID and one PL offset value corresponding to the TCI state ID (i.e., one set of a TCI state ID and a PL offset value).
[0292] In addition, in embodiment 4-4-C-1, multiple TCI states may be associated with the same PL offset value / PLO ID.
[0293] In this case, only the PL offset of the TCI state ID indicated by one MAC CE may be updated.
[0294] In this case, the PL offsets corresponding to a plurality of (for example, all) TCI state IDs associated with the PL offset value corresponding to one MAC CE may be updated.
[0295] <<<<<Embodiment 4-4-C-2>>>> One MAC CE may be used to indicate multiple sets of PL offset values for each TCI state [ID].
[0296] For example, as shown in Fig. 16B, one MAC CE includes multiple sets of TCI state IDs and PL offset values corresponding to the TCI state IDs. Note that the Cn field included in the MAC CE shown in Fig. 16B may be a field indicating the same meaning as the Cn field included in the MAC CE shown in Fig. 15 described above.
[0297] <<Embodiments 4-5>> The association between the value of the field indicating the PL offset value and the PL offset value may be defined.
[0298] The association may be defined, for example, based on the step size / range (eg, maximum / minimum) of the PL offset values.
[0299] For example, at least one of a table in which the PL offset value corresponds to a 1 dB step size / {0, 1, ..., 31} dB (see Figure 17A) and a table in which the PL offset value corresponds to a 0.5 dB step size / {0, 1, ..., 31} dB (see Figure 17B) may be defined.
[0300] Note that the step size / range of the PL offset value are merely examples and are not limited to these examples. For example, the step size may be a value other than 1 dB / 0.5 dB (e.g., 0.25 dB / 2 dB), and the range may be a range other than {0, 1, ..., 31} dB (e.g., {0, 1, ..., 64} dB / {0, 1, ..., 128} dB).
[0301] A plurality of associations / tables may be defined, and in this case, the UE may select / determine one of the plurality of associations / tables based on at least one of a rule predefined in a specification (e.g., a rule based on band / subcarrier spacing, etc.), a configuration of higher layer signaling (e.g., RRC), and a report of UE capability information.
[0302] Furthermore, the PL offset value in the association / table may be updated based on the setting / instruction of higher layer signaling (e.g., RRC) / MAC CE / DCI. As shown in Fig. 17C, the PL offset value (Value #0-#31) corresponding to the value of each field may be updated based on the setting / instruction of higher layer signaling (e.g., RRC) / MAC CE / DCI.
[0303] For example, the UE may be notified of the updated PL offset value using an RRC parameter with a number of field values.
[0304] Alternatively, for example, the updated PL offset value may be notified to the UE using a minimum value (start value), a maximum value (end value), and a step size. This configuration can reduce signaling overhead compared to directly notifying the updated value.
[0305] <<Embodiment 4-6>> The timing of updating the PL offset using MAC CE will be described below.
[0306] The IE may use the updated value of the PL offset for TPC calculation / determination based on the timing of updating / applying the PL offset.
[0307] For example, the UE may determine the timing of applying / updating the PL offset based on the timing of applying / updating the TCI state (indicated TCI state) by the MAC CE.
[0308] <<<<Embodiment 4-6-1>>> For example, the UE may determine to apply / update the PL offset at the same timing as the timing of updating / applying the indicated TCI state.
[0309] For example, the UE may receive a PDSCH carrying a MAC CE and determine to apply / update the PL offset after a certain period of time (e.g., 3 ms) has elapsed since the transmission of a positive HARQ-ACK corresponding to the PDSCH.
[0310] 18A is a diagram showing an example of updating a PL offset according to embodiment 4-6-1. In the example shown in FIG. 18A, a UE receives a PDSCH that transmits a MAC CE for updating a PL offset and transmits a positive HARQ-ACK corresponding to the PDSCH. The UE determines to update the PL offset 3 ms after transmitting the HARQ-ACK.
[0311] According to embodiment 4-6-1, the implementation of the UE can be facilitated.
[0312] <<<Embodiment 4-6-2>>> Furthermore, for example, the UE may determine to apply / update the PL offset at a timing based on the timing related to the update / application timing of the indicated TCI state and a specific offset (e.g., Y symbols / ms).
[0313] The value Y may be specified in advance in a specification, may be configured / instructed to the UE using RRC / MAC CE / DCI, may be determined based on a report of UE capability information, or may be determined based on a combination of at least two of these.
[0314] For example, the UE may determine to apply / update the PL offset at a timing obtained by adding (or subtracting) a specific offset to the timing related to the update / application timing of the indicated TCI state.
[0315] For example, the UE may receive a PDSCH carrying a MAC CE, and determine to apply / update the PL offset after a specific period (e.g., 3 ms) plus (or minus) a specific offset has elapsed since the transmission of a positive HARQ-ACK corresponding to the PDSCH.
[0316] 18B is a diagram showing an example of updating a PL offset according to embodiment 4-6-2. In the example shown in FIG. 18B, a UE receives a PDSCH that transmits a MAC CE for updating a PL offset and transmits a positive HARQ-ACK corresponding to the PDSCH. The UE determines to update the PL offset after (3+Y) ms have elapsed since the transmission of the HARQ-ACK.
[0317] According to embodiment 4-6-2, it is possible to set a rule that appropriately takes into account the timing required to update the transmission power of the UE.
[0318] According to the fourth to sixth embodiments, the PL offset can be applied / updated at an appropriate timing.
[0319] <<Embodiments 4-7>> In the fourth embodiment, updating of the PL offset using mainly the MAC CE has been described, but the "MAC CE" in the present disclosure may be read as "DCI."
[0320] For example, a specific DCI field may be used to update the PL offset value.
[0321] For example, an existing DCI field may be reused as the specific DCI field, in which case fields other than the specific DCI field may be set to special values.
[0322] Furthermore, the particular DCI field may be, for example, a new field.
[0323] The specific DCI field may be included in a specific DCI format (e.g., DCI format 0_0 / 0_1 / 0_2 / 0_3 / 1_0 / 1_1 / 1_2 / 1_3), for example. The specific DCI field may be included in a unicast DCI format or a multicast DCI format, for example.
[0324] The PLO ID may be indicated to the UE using the DCI. For example, if the number of PLO IDs is 4, the PLO ID indication field may be 2 bits.
[0325] The DCI may be used to indicate to the UE the value of the PL offset. For example, if the PL offset value has a 1 dB step size / range of {0, 1, ..., 31} dB, the PL offset value indication field may be 5 bits.
[0326] According to the fourth embodiment, the PL offset can be updated appropriately.
[0327] Fifth Embodiment The fifth embodiment relates to the association of a PL offset and a PLO ID.
[0328] A TCI State [ID] group containing one or more TCI State [ID]s may be configured for a UE.
[0329] <<Embodiment 5-1>> The number of PL offset values to be set (for example, a specific number X (X is 1, 2, 4, . . . , 2 n (n may be any number)) may be defined / limited.
[0330] For example, each PL offset value may be set in association with at least one of a TCI state [ID] group, an RS (e.g., SSB / CSI-RS / SRS) group, a physical cell ID (PCI), and a TAG ID.
[0331] For example, the TCI State [ID] / RS Group ID may be the same as the UL TRP ID.
[0332] For example, for PL offset, a 1 dB step size and range {0, 1, ..., 31} requires a 5-bit field / parameter per TCI state. For 64 UL TCI states, a 5 x 64 = 320-bit field / parameter is required.
[0333] On the other hand, if the maximum number of PL offsets per serving cell is specified as 4, a field / parameter of 5 x 4 = 20 bits is required per serving cell. Furthermore, if the PLO ID for each TCI state is 2 bits and 64 UL TCI states are configured, 2 x 64 = 128 bits are required to indicate all PLO IDs. Therefore, the total bit size can be 20 + 128 = 148 bits, and the signaling overhead required for field notification can be reduced.
[0334] For example, a set of PL offset values may be configured in a serving cell / BWP / component carrier (CC) (or across multiple (e.g., all) BWPs / CCs), and a PL ID may be configured in the UL TCI state.
[0335] For example, a set of PL offset values may be configured in a serving cell (or across multiple (e.g., all) component carriers (CCs)), and a PLO ID may be configured outside of the UL TCI state configuration. In this case, an association between the UL TCI state ID and the PLO ID may be defined.
[0336] Fig. 19 is a diagram showing an example of specifying a PL offset value according to embodiment 5-1. In the example shown in Fig. 19, an association between a PLO ID and a PL offset is set for each BWP / CC or for all CCs. Also, as shown in Fig. 19, a PL offset ID is set for each TCI status ID (one PLO ID is associated with one TCI status ID).
[0337]
[0073] Fig. 20 is a diagram showing another example of a PL offset value indication according to embodiment 5-1. In the example shown in Fig. 20, an association between a PLO ID and a PL offset is set for each BWP / CC or for all CCs. Also, as shown in Fig. 20, a PL offset ID is set for each group of UL TCI states (multiple TCI state IDs). In the example shown in Fig. 20, TCI state IDs 0-15 correspond to group #1, TCI state IDs 16-31 correspond to group #2, TCI state IDs 32-47 correspond to group #3, and TCI state IDs 48-63 correspond to group #4.
[0338] <<Embodiment 5-2>> The PL offset may be updated using MAC CE / DCI.
[0339] The UE may update the PL offset value for one TCI state [ID] group / RS group / PCI / TAG ID via MAC CE / DCI.
[0340] The UE may update the PL offset values for multiple TCI state [ID] groups / RS groups / PCI / TAG IDs via MAC CE / DCI.
[0341] A PL offset may be associated with a PLO ID / TCI state [ID] group / RS group / PCI / TAG ID.
[0342] For example, the TCI State [ID] / RS Group ID may be the same as the UL TRP ID.
[0343] For example, if a PL offset value associated with a PLO ID / TCI state [ID] group / RS group / PCI / TAG ID is updated by a MAC CE / DCI, the (other) PL offset values associated with that PLO ID / TCI state [ID] group / RS group / PCI / TAG ID may also be updated.
[0344] For example, the UE may use one MAC CE (eg, a MAC CE associated with one LCID) to update one or more PL offset values corresponding to one or more PLO IDs.
[0345] Fig. 21 is a diagram showing an example of updating a PL offset value according to embodiment 5-2. In the example shown in Fig. 21, an association between a PLO ID and a PL offset is set for each BWP / CC or for all CCs. Also, as shown in Fig. 21, a PL offset ID is set for each TCI status ID.
[0346] In the example shown in Figure 21, the UE is instructed to update the PL offset value for PLO ID 3 using a MAC CE, in which case the UE applies the PL offset value update for all TCI state IDs (TCI states) associated with PLO ID 3.
[0347]
[0073] Fig. 22 is a diagram showing another example of updating the PL offset value according to embodiment 5-2. In the example shown in Fig. 22, an association between a PLO ID and a PL offset is set for each BWP / CC or for all CCs. Also, as shown in Fig. 22, a PL offset ID is set for each group of UL TCI states (multiple TCI state IDs). In the example shown in Fig. 22, TCI state IDs 0-15 correspond to group #1, TCI state IDs 16-31 correspond to group #2, TCI state IDs 32-47 correspond to group #3, and TCI state IDs 48-63 correspond to group #4.
[0348] In the example shown in Fig. 22, the UE is instructed to update the PL offset value for PLO ID 3 using a MAC CE. In this case, the UE applies the PL offset value update to the TCI states in the TCI state ID group (group #4) associated with PLO ID 3.
[0349] According to the fifth embodiment, the PL offset can be updated appropriately.
[0350] <Supplementary Information> <<Notification of Information to UE>> In the above-described embodiments, notification of any information to the UE [from a Network (NW) (e.g., a Base Station (BS))] (in other words, reception of any information from the BS by the UE) may be performed using physical layer signaling (e.g., DCI), higher layer signaling (e.g., RRC signaling, MAC CE), a specific signal / channel (e.g., PDCCH, PDSCH, reference signal), or a combination thereof.
[0351] When the notification is performed by a MAC CE, the MAC CE may be identified by including a new Logical Channel ID (LCID) in the MAC subheader, which is not defined in existing standards.
[0352] When the notification is made by DCI, the notification may be made by a specific field of the DCI, a Radio Network Temporary Identifier (RNTI) used to scramble Cyclic Redundancy Check (CRC) bits assigned to the DCI, the format of the DCI, etc.
[0353] Furthermore, notification of any information to the UE in the above embodiments may be performed periodically, semi-persistently, or aperiodically.
[0354] <<Notification of Information from UE>> In the above-described embodiments, notification of any information from the UE [to the NW] (in other words, transmission / report 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), a specific signal / channel (e.g., PUCCH, PUSCH, PRACH, reference signal), or a combination thereof.
[0355] When the notification is performed by a MAC CE, the MAC CE may be identified by including a new LCID, which is not defined in existing standards, in the MAC subheader.
[0356] If the notification is made by UCI, the notification may be transmitted using PUCCH or PUSCH.
[0357] Furthermore, any information in the above-described embodiments may be notified from the UE periodically, semi-persistently, or aperiodically.
[0358] <<Application of Each Embodiment>> In a UE / BS, specific (one or more) processes / operations / controls / assumptions / information for at least one of the above-described embodiments may be applied (used) when one or more of the following conditions are met: - A higher layer parameter indicating the specific processes / operations / controls / assumptions / information is configured. - The specific processes / operations / controls / assumptions / information is determined based on related higher layer parameters. - The specific processes / operations / controls / assumptions / information is specified / activated / triggered by a MAC CE / DCI / UCI / resource / channel / RS. - A specific UE capability indicating (or related to) the specific processes / operations / controls / assumptions / information is reported or supported. - The application of the specific processes / operations / controls / assumptions / information is determined based on specific conditions.
[0359] The specific UE capability may indicate at least one of the following: Supporting the specific process / operation / control / assumption / information Supporting multiple TRP scenarios with a single DCI Supporting scenario 1 (UL dense deployment) Supporting scenario 2 (HetNet) Supporting UL transmission (SRS / PUSCH / PUCCH / PRACH) to UL reception points Number of supported UL reception points / DL transmission points.
[0360] 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, a band, a band combination, a BWP, a 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).
[0361] Furthermore, the specific UE capability may be a capability that is applied to all duplexing methods (commonly regardless of the duplexing method), or may be a capability for each duplexing method (e.g., Time Division Duplex (TDD) or Frequency Division Duplex (FDD)).
[0362] If the above conditions are not met, the UE / BS may follow the behavior specified in existing 3GPP releases.
[0363] (Supplementary Notes) The following inventions are supplementary notes with respect to each embodiment of the present disclosure. [Supplementary Note 1-1] A terminal having a receiving unit that receives a path loss (PL) offset configuration that is included in or associated with a UL Transmission Configuration Indication (TCI) state configuration corresponding to an uplink (UL) reception point, and a control unit that controls transmission power of an UL signal for the UL reception point based on the PL offset configuration. [Supplementary Note 1-2] The terminal according to Supplementary Note 1-1, wherein the PL offset configuration is not included in a joint or downlink TCI state configuration. [Supplementary Note 1-3] The terminal according to Supplementary Note 1-1 or Supplementary Note 1-2, wherein the UL signal includes at least one of a first UL signal in which a PL offset value is configured for each of the UL TCI states, and a second UL signal in which a list of PL offset values is configured in the UL signal configuration. [Supplementary Note 1-4] The terminal according to any one of Supplements 1-1 to 1-3, wherein the control unit assumes that the PL offset setting for each instruction TCI state for a sounding reference signal (SRS) is configured when capability information related to the application of an instruction TCI state for an SRS is reported. [Supplementary Note 2-1] A terminal including: a control unit that determines update of the PL offset based on at least one of update timing of an instruction Transmission Configuration Indication (TCI) state and an offset related to update timing of a path loss (PL) offset corresponding to an uplink (UL) reception point; and a transmission unit that transmits an UL signal in accordance with transmit power determined based on the update of the PL offset. [Supplementary Note 2-2] The terminal according to Supplementary Note 2-1, wherein the update timing of the instruction TCI state is update timing of the instruction TCI state by beam instruction using downlink control information. [Supplementary Note 2-3] The terminal according to Supplementary Note 2-1 or Supplementary Note 2-2, wherein the update timing of the instruction TCI state is update timing of the instruction TCI state by beam instruction using a Medium Access Control control element. [Supplementary Note 2-4] The terminal according to any one of Supplementary Note 2-1 to Supplementary Note 2-3, wherein the update timing of the indicated TCI state is a timing related to a switching delay of the active TCI state.[Supplementary Note 3-1] A terminal having a receiving unit that receives a Medium Access Control (MAC) control element that instructs updating of a path loss (PL) offset corresponding to an uplink (UL) reception point, and a control unit that controls transmission power of an UL signal directed to the UL reception point based on the MAC control element. [Supplementary Note 3-2] The terminal according to Supplementary Note 3-1, wherein one MAC control element includes an indication field for one or more PL offset values and an indication field for one or more PL offset identifiers corresponding to the PL offset values. [Supplementary Note 3-3] The terminal according to Supplementary Note 3-1 or Supplementary Note 3-2, wherein the control unit determines a PL offset value to be used in calculating the transmission power based on an association between a value of the PL offset value indication field in the MAC control element and the PL offset value. [Supplementary Note 3-4] The terminal according to any one of Supplementary Note 3-1 to Supplementary Note 3-3, wherein the control unit determines to update the PL offset after a specific period has elapsed since the end of transmission of a positive Hybrid Automatic Repeat reQuest ACKnowledgement (HARQ-ACK) for the MAC control element. [Supplementary Note 4-1] A terminal comprising: a receiving unit that receives configurations related to a specific number of path loss (PL) offsets corresponding to uplink (UL) reception points, and receives Medium Access Control (MAC) control elements or downlink control information that instructs updating the PL offsets; and a control unit that controls transmit power of UL signals for the UL reception points based on the MAC control elements or the downlink control information. [Supplementary Note 4-2] The terminal according to Supplementary Note 4-1, wherein the PL offset value is associated with at least one of a Transmission Configuration Indication (TCI) state group, a reference signal group, a physical cell identifier, and a timing advance group. [Supplementary Note 4-3] The terminal according to Supplementary Note 4-1 or Supplementary Note 4-2, wherein the control unit determines to update a value of the PL offset associated with one Transmission Configuration Indication (TCI) state group based on the MAC control element or the downlink control information.[Supplementary Note 4-4] The terminal according to any one of Supplementary Note 4-1 to Supplementary Note 4-3, wherein the control unit determines to update values of the PL offsets associated with a plurality of Transmission Configuration Indication (TCI) state groups based on the MAC control element or the downlink control information.
[0364] (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.
[0365] 23 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) or 5th generation mobile communication system New Radio (5G NR) specified by the Third Generation Partnership Project (3GPP).
[0366] 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.
[0367] In EN-DC, the LTE (E-UTRA) base station (eNB) is the master node (Master Node (MN)), and the NR base station (gNB) is the secondary node (Secondary Node (SN)). In NE-DC, the NR base station (gNB) is the MN, and the LTE (E-UTRA) base station (eNB) is the SN.
[0368] The wireless communication system 1 may support dual connectivity between multiple base stations within the same RAT (for example, dual connectivity in which both the MN and SN are NR base stations (gNBs) (NR-NR Dual Connectivity (NN-DC))).
[0369] 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 the base station 10.
[0370] 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 supercell) may be composed of multiple [virtual] cells (which may be called, for example, subcells). A supercell may correspond to a cell with a fixed physical range, and a subcell may correspond to a cell with a quasi-static / dynamically variable physical range. In this case, the wireless communication system 1 may be called a cell-free system.
[0371] The user terminal 20 may be connected to at least one of the multiple base stations 10. The user terminal 20 may utilize at least one of carrier aggregation (CA) using multiple component carriers (CCs) and dual connectivity (DC).
[0372] Each CC may be included in at least one of a first frequency band (Frequency Range 1 (FR1)) and a second frequency band (Frequency Range 2 (FR2)). The macro cell C1 may be included in FR1, and the small cell C2 may be included in FR2. For example, FR1 may be a frequency band of 6 GHz or less (sub-6 GHz), and FR2 may be a frequency band higher than 24 GHz (above-24 GHz). Note that the frequency bands and definitions of FR1 and FR2 are not limited to these, and for example, FR1 may correspond to a higher frequency band than FR2.
[0373] 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.
[0374] The multiple base stations 10 may be connected by wire (e.g., optical fiber compliant with the Common Public Radio Interface (CPRI), an X2 / Xn interface, etc.) or wirelessly (e.g., NR communication). For example, when NR communication is used as a backhaul between the base stations 11 and 12, the base station 11 corresponding to the upper station may be called an Integrated Access Backhaul (IAB) donor, and the base station 12 corresponding to the relay station (relay) may be called an IAB node.
[0375] 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.
[0376] The core network 30 may include network functions (Network Functions (NF)) 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 Operation, Administration and Maintenance (Management) (OAM). A single network node may provide multiple functions. Communication with an external network (e.g., the Internet) may also be performed via the DN.
[0377] The user terminal 20 may be a terminal that supports at least one of communication methods such as LTE, LTE-A, and 5G.
[0378] An Orthogonal Frequency Division Multiplexing (OFDM)-based radio access scheme may be used in the wireless communication system 1. For example, Cyclic Prefix OFDM (CP-OFDM), Discrete Fourier Transform Spread OFDM (DFT-s-OFDM), Orthogonal Frequency Division Multiple Access (OFDMA), Single Carrier Frequency Division Multiple Access (SC-FDMA), or the like may be used in at least one of the downlink (DL) and uplink (UL).
[0379] The radio access scheme may also be called a waveform. Note that in the wireless communication system 1, other radio access schemes (e.g., other single-carrier transmission schemes, other multi-carrier transmission schemes) may be used as the UL and DL radio access schemes.
[0380] 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.
[0381] Furthermore, in the wireless communication system 1, an uplink shared channel (Physical Uplink Shared Channel (PUSCH)) shared by each user terminal 20, an uplink control channel (Physical Uplink Control Channel (PUCCH)), a random access channel (Physical Random Access Channel (PRACH)), or the like may be used as an uplink channel.
[0382] The PDSCH transmits user data, higher layer control information, a System Information Block (SIB), etc. The PUSCH may transmit user data, higher layer control information, etc. Furthermore, the PBCH may transmit a Master Information Block (MIB).
[0383] 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.
[0384] Note that the DCI for scheduling the PDSCH may be referred to as a DL assignment, a DL DCI, etc., and the DCI for scheduling the PUSCH may be referred to as a UL grant, a UL DCI, etc. Note that the PDSCH may be replaced with DL data, and the PUSCH may be replaced with UL data.
[0385] A control resource set (CORESET) and a search space may be used to detect the PDCCH. The CORESET corresponds to resources for searching for DCI. The search space corresponds to a search region and a search method for PDCCH candidates. One CORESET may be associated with one or more search spaces. The UE may monitor the CORESET associated with a certain search space based on the search space configuration.
[0386] One search space may correspond to PDCCH candidates corresponding to one or more aggregation levels. One or more search spaces may be referred to as a search space set. Note that the terms "search space," "search space set," "search space configuration," "search space set configuration," "CORESET," "CORESET configuration," and the like in the present disclosure may be read interchangeably.
[0387] The PUCCH may transmit uplink control information (UCI) including at least one of channel state information (CSI), delivery confirmation information (which may be called, for example, Hybrid Automatic Repeat reQuest ACKnowledgement (HARQ-ACK), ACK / NACK, etc.), and scheduling request (SR). The PRACH may transmit a random access preamble for establishing a connection with a cell.
[0388] 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.
[0389] In the wireless communication system 1, a synchronization signal (SS), a downlink reference signal (DL-RS), etc. may be transmitted. In the wireless communication system 1, as the DL-RS, a cell-specific reference signal (CRS), a channel state information reference signal (CSI-RS), a demodulation reference signal (DMRS), a positioning reference signal (PRS), a phase tracking reference signal (PTRS), etc. may be transmitted.
[0390] The synchronization signal may be, for example, at least one of a Primary Synchronization Signal (PSS) and a Secondary Synchronization Signal (SSS). A signal block including an SS (PSS, SSS) and a PBCH (and a DMRS for the PBCH) may be referred to as an SS / PBCH block, an SS Block (SSB), or the like. Note that the SS, SSB, and the like may also be referred to as a reference signal.
[0391] Furthermore, in the wireless communication system 1, a sounding reference signal (SRS), a demodulation reference signal (DMRS), or the like may be transmitted as an uplink reference signal (UL-RS). Note that the DMRS may also be called a user equipment-specific reference signal (UE-specific reference signal).
[0392] 24 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.
[0393] 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.
[0394] 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.
[0395] The control unit 110 may control signal generation, scheduling (e.g., resource allocation, mapping), etc. The control unit 110 may control transmission and reception using the transceiver unit 120, the transceiver antenna 130, and the transmission path interface 140, measurement, etc. The control unit 110 may generate data, control information, sequences, etc. to be transmitted as signals, and transfer them to the transceiver unit 120. The control unit 110 may perform call processing (setting up, releasing, etc.) of communication channels, status management of the base station 10, management of radio resources, etc.
[0396] 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.
[0397] The transmitting / receiving unit 120 may be configured as an integrated transmitting / receiving unit, or may be configured from a transmitting unit and a receiving unit. The transmitting unit may be configured from a transmission processing unit 1211 and an RF unit 122. The receiving unit may be configured from a reception processing unit 1212, the RF unit 122, and a measurement unit 123.
[0398] The transmitting and receiving antenna 130 can be configured from an antenna described based on common understanding in the technical field to which the present disclosure relates, such as an array antenna.
[0399] 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.
[0400] The transceiver 120 may form at least one of the transmit beam and the receive beam using digital beamforming (e.g., precoding), analog beamforming (e.g., phase rotation), or the like.
[0401] The transmitter / receiver unit 120 (transmission processing unit 1211) may perform Packet Data Convergence Protocol (PDCP) layer processing, Radio Link Control (RLC) layer processing (e.g., RLC retransmission control), Medium Access Control (MAC) layer processing (e.g., HARQ retransmission control), etc. on data, control information, etc. obtained from the control unit 110, and generate a bit string to be transmitted.
[0402] The transmitter / receiver unit 120 (transmission processing unit 1211) may perform transmission processing such as channel coding (which may include error correction coding), modulation, mapping, filtering, Discrete Fourier Transform (DFT) processing (if necessary), Inverse Fast Fourier Transform (IFFT) processing, precoding, and digital-to-analog conversion on the bit string to be transmitted, and output a baseband signal.
[0403] The transceiver unit 120 (RF unit 122) may perform modulation, filtering, amplification, etc. on the baseband signal to a radio frequency band, and transmit the radio frequency band signal via the transceiver antenna 130.
[0404] On the other hand, the transceiver unit 120 (RF unit 122) may perform amplification, filtering, demodulation to a baseband signal, etc. on the radio frequency band signal received by the transceiver antenna 130.
[0405] 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.
[0406] 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.
[0407] The transmission path interface 140 may transmit and receive signals (backhaul signaling) between devices included in the core network 30 (e.g., network nodes that provide NF), other base stations 10, etc., and may acquire and transmit user data (user plane data), control plane data, etc. for the user terminal 20.
[0408] 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.
[0409] The base station 10 may be separated into three elements: a radio unit (RU), a distributed unit (DU), and a central unit (CU). For example, the RU may implement RF processing (digital beamforming, digital-to-analog conversion, analog beamforming, etc.) and lower-level functions of the physical layer (precoding, IFFT, FFT, etc.). The DU may implement higher-level functions of the physical layer (coding to resource element mapping, etc.), MAC layer functions, and RLC layer functions. The CU may implement the functions of the PDCP layer, Service Data Adaptation Protocol (SDAP) layer, and RRC layer.
[0410] In the present disclosure, the base station 10 may include a single device that realizes all of the functions of the RU, DU, and CU, or may include multiple devices that each realize 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.
[0411] The transceiver 120 may transmit a path loss (PL) offset configuration included in or associated with an uplink (UL) Transmission Configuration Indication (TCI) state configuration corresponding to an uplink (UL) reception point, and the controller 110 may use the PL offset configuration to indicate the transmission power of an UL signal for the UL reception point (a zeroth embodiment).
[0412] The control unit 110 may determine whether to update the path loss (PL) offset based on at least one of an update timing of a Transmission Configuration Indication (TCI) state and an offset related to an update timing of a path loss (PL) offset corresponding to an uplink (UL) reception point. The transceiver unit 120 may receive an UL signal transmitted according to a transmission power based on the update of the PL offset (third embodiment).
[0413] The transceiver 120 may transmit a Medium Access Control (MAC) control element instructing updating of a path loss (PL) offset corresponding to an uplink (UL) reception point, and the controller 110 may use the MAC control element to instruct transmission power of an UL signal for the UL reception point (fourth embodiment).
[0414] The transceiver 120 may transmit a configuration for a specific number of path loss (PL) offsets corresponding to uplink (UL) reception points, or may transmit a Medium Access Control (MAC) control element or downlink control information instructing updating of the PL offsets. The controller 220 may use the MAC control element or the downlink control information to instruct transmission power of an UL signal for the UL reception points (fifth embodiment).
[0415] (User terminal) Fig. 25 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.
[0416] In this example, the functional blocks of the characteristic parts of the present embodiment are mainly shown, and it may be assumed that the user terminal 20 also has other functional blocks necessary for wireless communication. Some of the processing of each unit described below may be omitted.
[0417] The control unit 210 performs overall control of the user terminal 20. The control unit 210 can be configured from a controller, a control circuit, etc., which are described based on common understanding in the technical field to which the present disclosure relates.
[0418] The control unit 210 may control signal generation, mapping, etc. The control unit 210 may control transmission and reception, measurement, etc. using the transceiver unit 220 and the transceiver antenna 230. The control unit 210 may generate data, control information, sequences, etc. to be transmitted as signals and transfer them to the transceiver unit 220.
[0419] The transceiver unit 220 may include a baseband unit 221, an RF unit 222, and a measurement unit 223. The baseband unit 221 may include a transmission processing unit 2211 and a reception processing unit 2212. The transceiver unit 220 may be configured with a transmitter / receiver, an RF circuit, a baseband circuit, a filter, a phase shifter, a measurement circuit, a transceiver circuit, etc., which are described based on common understanding in the technical field related to the present disclosure.
[0420] 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.
[0421] The transmitting / receiving antenna 230 can be configured from an antenna described based on common understanding in the technical field to which the present disclosure relates, such as an array antenna.
[0422] 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.
[0423] The transceiver unit 220 may form at least one of the transmit beam and the receive beam using digital beamforming (e.g., precoding), analog beamforming (e.g., phase rotation), or the like.
[0424] The transceiver unit 220 (transmission processing unit 2211) may perform PDCP layer processing, RLC layer processing (e.g., RLC retransmission control), MAC layer processing (e.g., HARQ retransmission control), etc. on data, control information, etc. obtained from the control unit 210, and generate a bit string to be transmitted.
[0425] The transmitter / receiver unit 220 (transmission processing unit 2211) may perform transmission processing such as channel coding (which may include error correction coding), modulation, mapping, filtering, DFT processing (if necessary), IFFT processing, precoding, and digital-to-analog conversion on the bit string to be transmitted, and output a baseband signal.
[0426] Whether or not to apply DFT processing may be based on the setting of transform precoding. When transform precoding is enabled for a certain channel (e.g., PUSCH), the transceiver unit 220 (transmission processing unit 2211) may perform DFT processing as the transmission processing to transmit the channel using a DFT-s-OFDM waveform, and if not, it may not be necessary to perform DFT processing as the transmission processing.
[0427] The transceiver unit 220 (RF unit 222) may perform modulation, filtering, amplification, etc. on the baseband signal to a radio frequency band, and transmit the radio frequency band signal via the transceiver antenna 230.
[0428] On the other hand, the transceiver unit 220 (RF unit 222) may perform amplification, filtering, demodulation to a baseband signal, etc. on the radio frequency band signal received by the transceiver antenna 230.
[0429] The transceiver unit 220 (reception processing unit 2212) may apply reception processing such as analog-to-digital conversion, FFT processing, IDFT processing (if necessary), filtering, demapping, demodulation, decoding (which may include error correction decoding), MAC layer processing, RLC layer processing, and PDCP layer processing to the acquired baseband signal, and acquire user data, etc.
[0430] The transceiver 220 (measurement unit 223) may perform measurements on the received signal. For example, the measurement unit 223 may perform RRM measurements, CSI measurements, etc. based on the received signal. The measurement unit 223 may measure received power (e.g., RSRP), received quality (e.g., RSRQ, SINR, SNR), signal strength (e.g., RSSI), propagation path information (e.g., CSI), etc. The measurement results may be output to the control unit 210.
[0431] 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.
[0432] Note that the transmitting unit and receiving unit of the user terminal 20 in the present disclosure may be configured by at least one of the transmitting / receiving unit 220 and the transmitting / receiving antenna 230.
[0433] The transceiver 220 may receive a path loss (PL) offset configuration included in or associated with an uplink (UL) Transmission Configuration Indication (TCI) state configuration corresponding to an uplink (UL) reception point, and the controller 210 may control the transmission power of an UL signal for the UL reception point based on the PL offset configuration (zeroth embodiment).
[0434] The PL offset configuration may not be included in the joint or downlink TCI state configuration (0th embodiment).
[0435] The UL signal may include at least one of a first UL signal in which a PL offset value is set for each of the UL TCI states, and a second UL signal in which a list of PL offset values is set within the setting of the UL signal (first embodiment).
[0436] When capability information regarding the application of an indicated TCI state for a sounding reference signal (SRS) is reported, the control unit 210 may assume that the PL offset setting for each indicated TCI state for SRS is set (second embodiment).
[0437] The control unit 210 may determine whether to update the path loss (PL) offset based on at least one of an update timing of a Transmission Configuration Indication (TCI) state and an offset related to an update timing of a path loss (PL) offset corresponding to an uplink (UL) reception point. The transceiver unit 220 may transmit an UL signal according to a transmission power determined based on the update of the PL offset (third embodiment).
[0438] The timing of updating the indicated TCI state may be the timing of updating the indicated TCI state by a beam instruction using downlink control information (third embodiment).
[0439] The timing for updating the indicated TCI state may be the timing for updating the indicated TCI state by beam instruction using a Medium Access Control control element (third embodiment).
[0440] The timing of updating the indicated TCI state may be a timing related to the switching delay of the active TCI state (third embodiment).
[0441] The transceiver 220 may receive a Medium Access Control (MAC) control element instructing updating of a path loss (PL) offset corresponding to an uplink (UL) reception point, and the controller 210 may control the transmission power of an UL signal directed to the UL reception point based on the MAC control element (fourth embodiment).
[0442] One of the MAC control elements may include an indication field for one or more PL offset values and an indication field for one or more PL offset identifiers corresponding to the PL offset values (fourth embodiment).
[0443] The control unit 210 may determine the PL offset value to be used in calculating the transmission power based on the association between the value of the PL offset value indication field in the MAC control element and the PL offset value (fourth embodiment).
[0444] The control unit 210 may determine to update the PL offset after a specific period has elapsed since the end of transmission of a positive Hybrid Automatic Repeat reQuest Acknowledgement (HARQ-ACK) for the MAC control element (fourth embodiment).
[0445] The transceiver 220 may receive configurations for a specific number of path loss (PL) offsets corresponding to uplink (UL) reception points, and may receive Medium Access Control (MAC) control elements or downlink control information instructing updating of the PL offsets. The controller 210 may control transmission power of UL signals for the UL reception points based on the MAC control elements or the downlink control information (fifth embodiment).
[0446] The value of the PL offset may be associated with at least one of a Transmission Configuration Indication (TCI) state group, a reference signal group, a physical cell identifier, and a timing advance group (fifth embodiment).
[0447] The control unit 210 may determine whether to update the value of the PL offset associated with one Transmission Configuration Indication (TCI) state group based on the MAC control element or the downlink control information (fifth embodiment).
[0448] The control unit 210 may determine whether to update the value of the PL offset associated with a plurality of Transmission Configuration Indication (TCI) state groups based on the MAC control element or the downlink control information (fifth embodiment).
[0449] (Hardware Configuration) Note that the block diagrams used to explain the above embodiments show functional blocks. These functional blocks (components) are realized by any combination of at least one of hardware and software. Furthermore, the method for realizing each functional block is not particularly limited. That is, each functional block may be realized using a single device that is physically or logically coupled, or may be realized using two or more physically or logically separated devices that are directly or indirectly connected (for example, using wires, wirelessly, etc.) and these multiple devices. The functional block may be realized by combining software with the single device or the multiple devices.
[0450] Here, the functions include, but are not limited to, judgment, determination, judgment, calculation, computation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, election, establishment, comparison, assumption, expectation, deeming, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assignment. For example, a functional block (component) that performs transmission may be called a transmitting unit, transmitter, etc. As described above, the implementation method of each is not particularly limited.
[0451] 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. Figure 26 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.
[0452] In the present disclosure, the terms apparatus, circuit, device, section, unit, etc. may be used interchangeably. The hardware configurations of the base station 10 and the user terminal 20 may be configured to include one or more of the devices shown in the drawings, or may be configured to exclude some of the devices.
[0453] 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.
[0454] Each function in the base station 10 and the user terminal 20 is realized, for example, by loading specified software (programs) onto hardware such as a processor 1001 and a memory 1002, causing the processor 1001 to perform calculations, control communication via the communication device 1004, and control at least one of reading and writing data in the memory 1002 and the storage 1003.
[0455] The processor 1001, for example, runs an operating system to control the entire computer. The processor 1001 may be configured as a central processing unit (CPU) including an interface with peripheral devices, a control device, an arithmetic unit, a register, etc. For example, at least a part of the above-mentioned control unit 110 (210), transceiver unit 120 (220), etc. may be realized by the processor 1001.
[0456] The processor 1001 also reads programs (program codes), software modules, data, etc. from at least one of the storage 1003 and the communication device 1004 into the memory 1002 and executes various processes in accordance with these. The programs used are those that cause a computer to execute at least some of the operations described in the above-described embodiments. For example, the control unit 110 (210) may be implemented by a control program stored in the memory 1002 and running on the processor 1001, and the other functional blocks may be implemented in a similar manner.
[0457] The memory 1002 is a computer-readable recording medium and may be configured by at least one of, for example, Read Only Memory (ROM), Erasable Programmable ROM (EPROM), Electrically EEPROM (EEPROM), Random Access Memory (RAM), or other suitable storage medium. The memory 1002 may also be referred to as a register, cache, main memory, etc. The memory 1002 may store executable programs (program codes), software modules, etc. for implementing a wireless communication method according to an embodiment of the present disclosure.
[0458] Storage 1003 is a computer-readable recording medium and may be composed of at least one of, for example, a flexible disk, a floppy disk, a magneto-optical disk (e.g., a compact disc (e.g., a Compact Disc ROM (CD-ROM)), a digital versatile disc, a Blu-ray disc), a removable disk, a hard disk drive, a smart card, a flash memory device (e.g., a card, a stick, a key drive), a magnetic stripe, a database, a server, or other suitable storage medium. Storage 1003 may also be referred to as an auxiliary storage device.
[0459] 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.
[0460] The input device 1005 is an input device (e.g., a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.) that accepts input from the outside. The output device 1006 is an output device (e.g., a display, a speaker, a light emitting diode (LED) lamp, etc.) that outputs to the outside. Note that the input device 1005 and the output device 1006 may be integrated into one device (e.g., a touch panel).
[0461] 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.
[0462] Furthermore, the base station 10 and the user terminal 20 may be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a programmable logic device (PLD), or a field programmable gate array (FPGA), and some or all of the functional blocks may be realized using this hardware. For example, the processor 1001 may be implemented using at least one of these pieces of hardware.
[0463] In addition, the devices included in the core network 30 (for example, network nodes that provide NF) may also be realized by the above-mentioned functional block / hardware configuration.
[0464] (Modifications) Note that terms described in the present disclosure and terms necessary for understanding the present disclosure may be replaced with terms having the same or similar meanings. For example, a channel, a symbol, and a signal (signal or signaling) may be interchangeable. A signal may also be a message. A reference signal may be abbreviated as RS, and may also be called a pilot, pilot signal, etc. depending on the applicable standard. A component carrier (CC) may also be called a cell, frequency carrier, carrier frequency, etc.
[0465] 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.
[0466] Here, the numerology may be a communication parameter applied to at least one of transmission and reception of a signal or channel, and may indicate at least one of, for example, Subcarrier Spacing (SCS), bandwidth, symbol length, cyclic prefix length, Transmission Time Interval (TTI), number of symbols per TTI, radio frame structure, specific filtering performed by a transceiver in the frequency domain, and specific windowing performed by a transceiver in the time domain.
[0467] A slot may be composed of one or more symbols (such as an Orthogonal Frequency Division Multiplexing (OFDM) symbol or a Single Carrier Frequency Division Multiple Access (SC-FDMA) symbol) in the time domain. A slot may also be a time unit based on numerology.
[0468] 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.
[0469] 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.
[0470] For example, one subframe may be referred to as a TTI, or multiple consecutive subframes may be referred to as a TTI, or one slot or one minislot may be referred to as a TTI. That is, at least one of the subframe and the TTI may be a subframe (1 ms) in existing LTE, a period shorter than 1 ms (for example, 1-13 symbols), or a period longer than 1 ms. Note that the unit representing the TTI may be called a slot, minislot, etc. instead of a subframe.
[0471] Here, TTI refers to, for example, the smallest time unit for scheduling in wireless communication. For example, in an LTE system, a base station performs scheduling to allocate radio resources (such as frequency bandwidth and transmission power that can be used by each user terminal) to each user terminal in TTI units. Note that the definition of TTI is not limited to this.
[0472] 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.
[0473] 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.
[0474] 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.
[0475] In addition, a long TTI (e.g., a normal TTI, a subframe, etc.) may be interpreted as a TTI having a time length of more than 1 ms, and a short TTI (e.g., a shortened TTI, etc.) may be interpreted as a TTI having a TTI length shorter than the TTI length of a long TTI and greater than or equal to 1 ms.
[0476] A resource block (RB) is a resource allocation unit in the time domain and the frequency domain, and may include one or more consecutive subcarriers in the frequency domain. The number of subcarriers included in an RB may be the same regardless of numerology, for example, 12. The number of subcarriers included in an RB may be determined based on numerology.
[0477] In addition, an RB may include one or more symbols in the time domain and may have a length of one slot, one minislot, one subframe, or one TTI, each of which may be composed of one or more resource blocks.
[0478] In addition, one or more RBs may be referred to as a physical resource block (PRB), a sub-carrier group (SCG), a resource element group (REG), a PRB pair, an RB pair, etc.
[0479] 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.
[0480] A Bandwidth Part (BWP), which may also be referred to as a partial bandwidth, may represent a subset of contiguous common resource blocks (RBs) for a given numerology on a given carrier, where the common RBs may be identified by their index relative to a Common Reference Point of the carrier. PRBs may be defined in a BWP and numbered within the BWP.
[0481] The BWP may include a UL BWP (BWP for UL) and a DL BWP (BWP for DL). One or more BWPs may be configured for a UE within one carrier.
[0482] 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."
[0483] 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.
[0484] 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.
[0485] 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.
[0486] 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.
[0487] 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.
[0488] 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.
[0489] 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 / specifying (or relating to) the value of the any information.
[0490] The notification of information is not limited to the aspects / embodiments described in the present disclosure, and may be performed using other methods. For example, the notification of information in the present disclosure may be performed by physical layer signaling (e.g., Downlink Control Information (DCI) and Uplink Control Information (UCI)), higher layer signaling (e.g., Radio Resource Control (RRC) signaling, broadcast information (Master Information Block (MIB) and System Information Block (SIB)), Medium Access Control (MAC) signaling), other signals, or a combination thereof.
[0491] Note that the physical layer signaling may be referred to as Layer 1 / Layer 2 (L1 / L2) control information (L1 / L2 control signal), L1 control information (L1 control signal), etc. Furthermore, the RRC signaling may be referred to as an RRC message, such as an RRC Connection Setup message or an RRC Connection Reconfiguration message. Furthermore, the MAC signaling may be notified using, for example, a MAC Control Element (CE).
[0492] 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).
[0493] 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).
[0494] 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.
[0495] Software, instructions, information, etc. may also be transmitted or received over a transmission medium. For example, if software is transmitted from a website, server, or other remote source using wired technologies (such as coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL)), and / or wireless technologies (such as infrared, microwave), these wired and / or wireless technologies are included within the definition of transmission media.
[0496] 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).
[0497] In this disclosure, terms such as "precoding," "precoder," "weight (precoding weight)," "Quasi-Co-Location (QCL)," "Transmission Configuration Indication state (TCI state)," "spatial relation," "spatial domain filter," "transmit power," "phase rotation," "antenna port," "layer," "number of layers," "rank," "resource," "resource set," "beam," "beam width," "beam angle," "antenna," "antenna element," "panel," "UE panel," "transmitting entity," "receiving entity," etc. may be used interchangeably.
[0498] 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. Furthermore, the spatial domain transmission filter may include at least one of a spatial domain transmission filter and a spatial domain reception filter.
[0499] 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.
[0500] 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.
[0501] 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.
[0502] Furthermore, in the present disclosure, terms such as "QCL," "QCL assumption," "QCL relationship," "QCL type information," "QCL property / properties," "specific QCL type (e.g., Type A, Type D) property," and "specific QCL type (e.g., Type A, Type D)" may be interchangeable.
[0503] In the present disclosure, terms such as index, identifier (ID), indicator, indication, and resource ID may be interchangeable. In the present disclosure, terms such as sequence, list, set, group, cluster, and subset may be interchangeable.
[0504] Furthermore, the spatial relationship information identifier (ID) (TCI state ID) and the spatial relationship information (TCI state) may be interchangeable. The "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 the TCI may be interchangeable. The spatial relationship information and the spatial relationship may be interchangeable.
[0505] In the present disclosure, terms such as "base station (BS)," "radio base station," "fixed station," "NodeB," "eNB (eNodeB)," "gNB (gNodeB)," "access point," "transmission point (TP)," "reception point (RP)," "transmission / reception point (TRP)," "panel," "cell," "sector," "cell group," "carrier," "component carrier," etc. may be used interchangeably. Base stations may also be referred to by terms such as macrocell, small cell, femtocell, picocell, etc.
[0506] A base station can accommodate one or more (e.g., three) cells. When a base station accommodates multiple cells, the overall coverage area of the base station can be partitioned into multiple smaller areas, and each smaller area can be provided with communication service by a base station subsystem (e.g., a small indoor base station (Remote Radio Head (RRH))). The terms "cell" or "sector" refer to part or all of the coverage area of a base station and / or base station subsystem that provides communication service within that coverage.
[0507] 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.
[0508] In this disclosure, the terms "Mobile Station (MS)," "user terminal," "User Equipment (UE)," "terminal," etc. may be used interchangeably.
[0509] 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.
[0510] 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.
[0511] 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.
[0512] 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.
[0513] 27 is a diagram showing an example of a vehicle according to an embodiment. The vehicle 40 includes a drive unit 41, a steering unit 42, an accelerator pedal 43, a brake pedal 44, a shift lever 45, left and right front wheels 46, left and right rear wheels 47, 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.
[0514] 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 a user.
[0515] The electronic control unit 49 is composed of a microprocessor 61, memory (ROM, RAM) 62, and a communication port (for example, 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).
[0516] 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.
[0517] 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 (e.g., multimedia information / multimedia services) to the occupants of the vehicle 40.
[0518] 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.
[0519] The driving assistance system unit 64 includes various devices for providing functions to prevent accidents and reduce 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.
[0520] 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.
[0521] 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 base station 10 or the user terminal 20 described above. Furthermore, the communication module 60 may be, for example, at least one of the base station 10 and the user terminal 20 described above (or may function as at least one of the base station 10 and the user terminal 20).
[0522] 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.
[0523] The communication module 60 receives various information (traffic information, traffic signal information, vehicle distance information, etc.) transmitted from an external device 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)).
[0524] 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.
[0525] 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 an uplink channel and a downlink channel may be read as a sidelink channel.
[0526] 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.
[0527] In the present disclosure, an operation described as being performed by a base station may be performed by its upper node in some cases. It is apparent that in a network including one or more network nodes having a base station, various operations performed for communication with a terminal may be performed by the base station, one or more network nodes other than the base station (such as, but not limited to, a Mobility Management Entity (MME), a Serving-Gateway (S-GW), etc.), or a combination thereof.
[0528] Each aspect / embodiment described in this disclosure may be used alone, in combination, or switched depending on the implementation. Furthermore, the order of the processing procedures, sequences, flowcharts, etc. of each aspect / embodiment described in this disclosure may be changed unless inconsistent. For example, the methods described in this disclosure present elements of various steps using an example order, and are not limited to the particular order presented.
[0529] 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 802.17 (WiMAX (registered trademark)), IEEE 802.19 (WiMAX (registered trademark)), IEEE 802.20 (WiMAX (registered trademark)), IEEE 802.21 (Wi-Fi (registered trademark)), IEEE 802.22 (WiMAX (registered trademark)), IEEE 802.23 (WiMAX (registered trademark)), IEEE 802.24 (WiMAX (registered trademark)), IEEE 802.25 (WiMAX (registered trademark)), IEEE 802.26 (WiMAX (registered trademark)), IEEE 802.27 (WiMAX (registered trademark)), IEEE 802.28 (WiMAX (registered trademark)), IEEE 802.29 (WiMAX (registered trademark)), IEEE 802.30 (WiMAX (registered trademark)), IEEE 802.31 (Wi-Fi (registered trademark)), IEEE 802.32 (WiMAX (registered trademark)), IEEE 802.33 (WiMAX (registered trademark)), IEEE 802. The present invention may be applied to systems that use IEEE 802.20, Ultra-WideBand (UWB), Bluetooth (registered trademark), or other suitable wireless communication methods, or to next-generation systems that are expanded, modified, created, or defined based on these. Furthermore, the present invention may be applied to a combination of multiple systems (e.g., a combination of LTE or LTE-A and 5G).
[0530] 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."
[0531] 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.
[0532] 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.
[0533] 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.
[0534] 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 kind of action. In the present disclosure, "determination" may be read interchangeably with the above-mentioned actions.
[0535] 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...."
[0536] 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 ..." or "do ... (if the above "..." is a to-infinitive, a verb with "to")," etc. "does not expect ..." may be interchangeably read as "be not expected ..." or "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).
[0537] 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.
[0538] 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."
[0539] 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.
[0540] 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."
[0541] When the terms "include," "including," and variations thereof are used in this disclosure, these terms are intended to be inclusive, similar to the term "comprising." Furthermore, when the term "or" is used in this disclosure, it is not intended to be an exclusive or.
[0542] 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.
[0543] 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 "i-th" (i is an arbitrary integer) attached (for example, "highest" may be interchangeable with "i-th highest").
[0544] In this disclosure, the terms "of," "for," "regarding," "related to," "associated with," etc. may be read interchangeably.
[0545] 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 approximately zero (immediately after or immediately before). A time offset may also be applied to the time at which A occurs. For example, "A" may be interchangeable with "before / after a 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.
[0546] 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.
[0547] 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.
Claims
1. A terminal having: a receiving unit that receives settings for a specific number of path loss (PL) offsets corresponding to uplink (UL) reception points, and receives Medium Access Control (MAC) control elements or downlink control information that instruct updating of the PL offsets; and a control unit that controls the transmission power of UL signals for the UL reception points based on the MAC control elements or the downlink control information.
2. The terminal of claim 1, wherein the value of the PL offset is associated with at least one of a Transmission Configuration Indication (TCI) state group, a reference signal group, a physical cell identifier, and a timing advance group.
3. The terminal according to claim 1, wherein the control unit determines whether to update the value of the PL offset associated with one Transmission Configuration Indication (TCI) state group based on the MAC control element or the downlink control information.
4. The terminal according to claim 1, wherein the control unit determines whether to update the value of the PL offset associated with a plurality of Transmission Configuration Indication (TCI) state groups based on the MAC control element or the downlink control information.
5. A wireless communication method for a terminal, comprising the steps of: receiving settings for a specific number of path loss (PL) offsets corresponding to uplink (UL) reception points, and receiving a Medium Access Control (MAC) control element or downlink control information instructing updating of the PL offsets; and controlling the transmission power of an UL signal for the UL reception points based on the MAC control element or the downlink control information.
6. A base station having: a transmitter that transmits settings for a specific number of path loss (PL) offsets corresponding to uplink (UL) reception points and transmits Medium Access Control (MAC) control elements or downlink control information that instruct updating of the PL offsets; and a controller that uses the MAC control elements or the downlink control information to instruct the transmission power of UL signals for the UL reception points.
Citation Information
Patent Citations
Terminal, wireless communication method, and base station
WO2021176724A1