Terminal, wireless communication method, and base station

Abstract

A terminal according to one aspect of the present disclosure is characterized by comprising: a reception unit that receives a setting related to at least one of a plurality of offsets related to timing advance (TA) and a plurality of timing advance groups (TAGs); and a control unit that, on the basis of a specific method, determines, from among the plurality of offsets and / or the plurality of TAGs, at least one of a specific offset and a specific TAG to be applied to a specific uplink transmission. The terminal is characterized in that the specific uplink transmission is an uplink transmission after the reception of an upper layer parameter related to a unified transmission configuration indication (TCI) state and before the application of the indicated TCI state. According to the one aspect of the present disclosure, UL transmission can be appropriately controlled.

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 (e.g., wireless communication systems after Rel. 16 / 5G), it is expected that communications will be controlled based on inter-cell mobility including non-serving cells, or inter-cell mobility using multiple transmission / reception points (e.g., Multi-TRP (MTRP)). In inter-cell mobility, it is also expected that candidate cells will be set separately from the serving cell, and that switching between the serving cell and the candidate cell will be performed.

[0006] However, when inter-cell mobility (for example, switching between a serving cell and a candidate cell) is applied, how to control UL transmission (for example, control of timing advance, etc.) becomes an issue.

[0007] In addition to the multi-TRP approach, the introduction of a unified TCI framework is also being considered. However, the rules supporting the application of both approaches are not yet fully defined. Without a clear relationship between these two approaches, the UE may not be able to properly determine the TA corresponding to the cell / TRP, which may increase communication throughput and hinder the improvement of communication quality.

[0008] The present disclosure has been made in consideration of the above points, and one of its objects is to provide a terminal, a wireless communication method, and a base station that are capable of appropriately controlling UL transmission.

[0009] A terminal according to one aspect of the present disclosure includes: a receiving unit that receives settings for at least one of a plurality of offsets related to a timing advance (TA) and a plurality of timing advance groups (TAGs); and a control unit that determines, based on a specific method, a specific offset and / or a specific TAG to be applied to a specific uplink transmission from among the plurality of offsets and / or the plurality of TAGs, wherein the specific uplink transmission is an uplink transmission after receiving higher layer parameters related to a unified Transmission Configuration Indication (TCI) state and before applying the indicated TCI state.

[0010] According to one aspect of the present disclosure, UL transmission can be appropriately controlled.

[0011] 1A to 1D are diagrams illustrating an example of a multi-TRP. FIG. 2 is a diagram illustrating an example of a timing advance group (TAG) to which cells included in a cell group belong. FIGS. 3A and 3B are diagrams illustrating an example of a MAC CE for a timing advance command. FIG. 4 is a diagram illustrating an example of TAG configuration when TAG ID association is supported for candidate cells. FIGS. 5A and 5B illustrate an example of a unified / common TCI framework. FIGS. 6A and 6B illustrate an example of a DCI-based TCI status indication. FIG. 7 is a diagram illustrating an example of selection / application of an offset / TAG for a TA. FIG. 8 is a diagram illustrating an example of a schematic configuration of a wireless communication system according to an embodiment. FIG. 9 is a diagram illustrating an example of a configuration of a base station according to an embodiment. FIG. 10 is a diagram illustrating an example of a configuration of a user terminal according to an embodiment. FIG. 11 is a diagram illustrating an example of hardware configurations of a base station and a user terminal according to an embodiment. FIG. 12 is a diagram illustrating an example of a vehicle according to an embodiment.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0026] (Multi-TRP) In NR, one or more transmission / reception points (Transmission / Reception Points (TRP)) (multi-TRP) are considered to perform DL transmission to a UE using one or more panels (multi-panels). Also, it is considered that a UE performs UL transmission to one or more TRPs.

[0027] Note that multiple TRPs may correspond to the same cell identifier (ID), or different cell IDs, which may be physical cell IDs (e.g., PCIs) or virtual cell IDs.

[0028] 1A-1D illustrate an example of a multi-TRP scenario, assuming, but not limited to, that each TRP is capable of transmitting four different beams.

[0029] 1A shows an example of a case where only one TRP (TRP1 in this example) of multiple TRPs transmits to the UE (this may be referred to as single mode, single TRP, etc.). In this case, TRP1 transmits both control signals (PDCCH) and data signals (PDSCH) to the UE.

[0030] In this disclosure, single-TRP mode may refer to a mode in which multi-TRP (mode) is not set.

[0031] 1B shows an example of a case where only one TRP (TRP1 in this example) transmits control signals to the UE, and the multi-TRP transmits data signals (also called single master mode). The UE receives each PDSCH transmitted from the multi-TRP based on a single Downlink Control Information (DCI).

[0032] Figure 1C shows an example of a case where each of the multi-TRPs transmits a part of the control signal to the UE, and the multi-TRPs transmit data signals (this may be called a master-slave mode). Part 1 of the control signal (DCI) may be transmitted in TRP1, and Part 2 of the control signal (DCI) may be transmitted in TRP2. Part 2 of the control signal may depend on Part 1. The UE receives each PDSCH transmitted from the multi-TRP based on these parts of the DCI.

[0033] 1D shows an example of a multi-TRP mode in which each TRP transmits a separate control signal to the UE, and the multi-TRP transmits a data signal (also referred to as a multi-master mode). A first control signal (DCI) may be transmitted on TRP1, and a second control signal (DCI) may be transmitted on TRP2. The UE receives each PDSCH transmitted from the multi-TRP based on these DCIs.

[0034] When multiple PDSCHs from multiple TRPs as shown in Figure 1B (which may also be referred to as multiple PDSCHs) are scheduled using one DCI, the DCI may be referred to as a single DCI (S-DCI, single PDCCH). Also, when multiple PDSCHs from multiple TRPs as shown in Figure 1D are scheduled using multiple DCIs, these multiple DCIs may be referred to as multiple DCIs (M-DCI, multiple PDCCHs).

[0035] Each TRP in a multi-TRP may transmit a different transport block (TB) / code word (CW) / different layer, or each TRP in a multi-TRP may transmit the same TB / CW / layer.

[0036] Non-Coherent Joint Transmission (NCJT) is being considered as one form of multi-TRP transmission. In NCJT, for example, TRP1 modulates and layer-maps a first codeword to transmit a first PDSCH using a first number of layers (e.g., two layers) with a first precoding. TRP2 modulates and layer-maps a second codeword to transmit a second PDSCH using a second number of layers (e.g., two layers) with a second precoding.

[0037] Note that multiple PDSCHs (multi-PDSCHs) that are non-coherent may be defined as partially or completely overlapping in time and / or frequency domains, i.e., a first PDSCH from a first TRP and a second PDSCH from a second TRP may overlap in time and / or frequency resources.

[0038] The first PDSCH and the second PDSCH may be assumed to be not quasi-co-located (QCL). Reception of multiple PDSCHs may be interpreted as simultaneous reception of PDSCHs that are not of a certain QCL type (e.g., QCL type D).

[0039] In URLLC for multi-TRP, it is considered that PDSCH (transport block (TB) or codeword (CW)) repetition across multi-TRP is supported. Repetition schemes (URLLC schemes, e.g., Schemes 1, 2a, 2b, 3, and 4) across multi-TRP in the frequency domain, layer (spatial) domain, or time domain are supported. In Scheme 1, multiple PDSCHs from multi-TRP are space division multiplexed (SDM). In Schemes 2a and 2b, PDSCHs from multi-TRP are frequency division multiplexed (FDM). In Scheme 2a, the redundancy version (RV) is the same for multi-TRP. In Scheme 2b, the RVs for multi-TRP may be the same or different. In schemes 3 and 4, multiple PDSCHs from multiple TRPs are time division multiplexed (TDM). In scheme 3, multiple PDSCHs from multiple TRPs are transmitted in one slot. In scheme 4, multiple PDSCHs from multiple TRPs are transmitted in different slots.

[0040] Such a multi-TRP scenario allows for more flexible transmission control using good quality channels.

[0041] NCJT using multiple TRPs / panels may use high rank. To support ideal and non-ideal backhaul between multiple TRPs, both single DCI (single PDCCH, e.g., FIG. 1B) and multiple DCI (multiple PDCCH, e.g., FIG. 1D) may be supported. For both single DCI and multiple DCI, the maximum number of TRPs may be two.

[0042] For single PDCCH design (mainly for ideal backhaul), TCI extension is being considered. Each TCI codepoint in the DCI may correspond to one or two TCI states. The TCI field size may be the same as that of Rel. 15.

[0043] For PDCCH / CORESET specified in Rel. 15, one TCI state without CORESETPoolIndex (also referred to as TRP Info) is set to one CORESET.

[0044] Regarding the PDCCH / CORESET enhancements specified in Rel. 16, in multi-TRP based on multi-DCI, a CORESET pool index is configured for each CORESET.

[0045] (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 may correspond to the serving cell and the other TRPs may correspond to non-serving cells. In this case, the distances between each TRP and the UE may be different.

[0046] In existing systems, the transmission timing of an uplink (UL) channel and / or an UL signal (UL channel / signal) is adjusted by a timing advance (TA). 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.

[0047] The UE may control the timing of UL transmission by applying timing advance (multiple timing advances) for each pre-configured timing advance group (TAG).

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

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

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

[0051] In existing systems (e.g., Rel. 16 NR), the configuration of up to four TAGs per cell group (e.g., MCG / SCG) is supported (see Figure 2). Figure 2 shows a case where three TAGs are configured for a cell group including SpCell and SCell #1 to #4. Here, the SpCell and SCell #1 belong to the first TAG (PTAG or TAG #0), SCell #2 and SCell #3 belong to the second TAG (TAG #1), and SCell #4 belongs to the third TAG (TAG #2).

[0052] A timing advance command (TA command) may be notified to the UE using a MAC control element (e.g., MAC CE). The TA command indicates a transmission timing value of an uplink channel and is included in the MAC control element. The TA command (TAC) is signaled from the radio base station to the UE at the MAC layer. The UE controls a predetermined timer (e.g., a TA timer) based on the reception of the TA command.

[0053] The MAC CE for the timing advance command may include a field for a timing advance group index (e.g., TAG ID) and a field for the timing advance command (see FIG. 3A). The MAC CE may be configured by one octet (=8 bits).

[0054] The TAG ID field (TAG ID field) may be configured with, for example, 2 bits. The TAG ID field may be used to indicate the TAG ID of the addressed TAG. The Timing Advance Command field (TAC field) may be configured with, for example, 6 bits. The TAC field contains an index value T that is used to control the amount / value (relative amount / relative value) of timing adjustment that the MAC entity must apply. Ａ (0, 1, 2...63). The MAC CE for the timing advance command shown in Figure 3A may be called a TAC MAC CE.

[0055] FIG. 3B illustrates another example of a MAC CE for a timing advance command. The MAC CE illustrated in FIG. 3B may be referred to as an absolute TAC MAC CE. The MAC CE may be configured with two octets (16 bits). Specifically, the MAC CE may include a field for reserved bits (R-bit field) and a field for a timing advance command (TAC field). The R-bit field (R=0) may be configured with, for example, 4 bits. The TAC field may be configured with, for example, 12 bits across two octets. The TAC field in FIG. 3B may indicate an index value used to control the actual amount / value (absolute amount / value) of TA that a MAC entity must apply, as in FIG. 3A. Furthermore, the absolute TAC MAC CE may not include the TAG ID field illustrated in FIG. 3A.

[0056] The MAC CE shown in Fig. 3A may be used after initial access is established. On the other hand, the MAC CE shown in Fig. 3B is used only during initial access and may be included in the RAR, etc. Each field included in the MAC CE for the timing advance command described above may be called a TA-related field. Among them, the TAC field shown in Fig. 3A may be called a TA adjustment field / field for instructing TA adjustment / field related to TA adjustment, and the TAC field shown in Fig. 3B may be called an absolute TAC field / field for instructing absolute TAC.

[0057] Parameters corresponding to each TAG ID may be set by higher layer parameters. For example, a parameter such as a time alignment timer (e.g., timeAlignmentTimer) corresponding to each TAG ID may be set. Alternatively, the TAG ID for each serving cell may be set by higher layer parameters (e.g., tag-ID included in ServingCellConfig). Note that after being set by higher layer parameters, the TAG ID / parameter may be updated by MAC CE.

[0058] A time alignment timer may be maintained for UL time alignment. In Rel. 17, the time alignment timer may be configured / associated per TAG. When the UE receives a MAC CE for a timing advance command (e.g., TAC MAC CE), it starts or restarts the time alignment timer associated with the indicated timing advance group (e.g., TAG), respectively.

[0059] The MAC entity receives the TAC MAC CE and performs a predetermined value (N ＴＡ ) is maintained, apply a timing advance command for the indicated TAG or start or restart the time alignment timer associated with the indicated TAG. ＴＡ ) may be the timing advance between DL and UL.

[0060] The behavior when the time alignment timer expires may be defined separately for the PTAG and the STAG. Note that the timing advance group (TAG) including the SpCell of the MAC entity may be called the primary timing advance group (PTAG), and the other TAGs may be called secondary timing advance groups (STAGs).

[0061] For example, Rel. 17 supports that when a timing advance timer corresponding to a PTAG expires, a predetermined PTAG action is applied, and when a timing advance timer corresponding to a STAG expires, a predetermined STAG action is applied.

[0062] For example, when the time alignment timer expires, the following actions (e.g., predetermined PTAG action / predetermined STAG action) may be performed.

[0063] Actions for a given PTAG If a time alignment timer is associated with a PTAG: Flush all HARQ buffers for all serving cells. Inform RRC to release PUCCH for all serving cells, if configured. Inform RRC to release SRS, if configured. Clear all configured DL allocations and configured UL allocations. Clear PUSCH resources for semi-persistent CSI reporting. Allow all running time alignment timers to expire. Clear N for all TAGs. ＴＡ Maintain.

[0064] Actions for a given STAG: If a time alignment timer is associated with a STAG, then for all serving cells belonging to that TAG: Flush all HARQ buffers. Inform RRC to release PUCCH, if configured. Inform RRC to release SRS, if configured. Clear all configured DL and UL allocations. Clear PUSCH resources for semi-persistent CSI reporting. Clear N for that TAG. ＴＡ Maintain.

[0065] (Control of UL Transmission Based on Timing Advance) In future wireless communication systems, it is also assumed that in inter-cell mobility, UL transmission will be controlled based on timing advance for a serving cell (or a TRP of a serving cell) and a non-serving cell / additional cell (or a TRP of a non-serving cell / additional cell). Alternatively, in future wireless communication systems, it is also assumed that different TAGs (or TAG-IDs) will be set for one or more TRPs (e.g., multiple TRPs having different PCIs) corresponding to a certain cell (or CC). Alternatively, it is also assumed that different TRPs corresponding to a certain cell will share a common TAG.

[0066] FIG. 4 is a diagram showing an example of TAG settings for multiple cells (or TRPs) with different PCIs.

[0067] It is also assumed that up to M PCIs (e.g., a serving cell plus candidate cells associated with the serving cell) can be configured for each CC, and that up to N TAGs (e.g., N≦M) can be configured for the M PCIs. In this case, one or more PCIs may be associated with one TAG.

[0068] Furthermore, one or more PCIs may be associated with one TAG for up to S serving cells in a cell group (or for up to S serving cells). In this case, up to T TAGs may be configured considering one PCI per CC (Case 1). That is, up to T×N TAGs may be configured for up to M×S cells. Alternatively, up to U TAGs may be configured for up to M×S cells (Case 2).

[0069] In this way, when candidate cells are configured / applied / supported, it is assumed that different serving cells / different candidate cells are associated with the same TAG. The TAG of the candidate cell may be indicated by the base station or may be determined based on the TA of the candidate cell acquired by the UE.

[0070] It is also conceivable that the UE performs UL transmission of a candidate cell (for example, a candidate cell for which a switching instruction to the serving cell has been issued) taking into consideration the TA corresponding to the candidate cell. When taking into consideration the TA of the candidate cell, the UE needs to acquire the TA of the candidate cell (for example, TA acquisition of candidate cells).

[0071] As the TA acquisition of a candidate cell, several TA acquisition methods are possible, such as TA acquisition using RACH (e.g., RACH-based solutions) and TA acquisition without using RACH (RACH-less solutions). The TA acquisition method may be interpreted as a TA acquisition scheme, a TA acquisition type, or a TA acquisition procedure. In the present disclosure, TA acquisition, TA measurement, TA calculation, TA computation, and TA determination may be interpreted as interchangeable.

[0072] For example, the UE may acquire the TA of a candidate cell by transmitting a RACH (e.g., a PDCCH ordered RACH) indicated / triggered by the PDCCH to the candidate cell. Information about the TA of the candidate cell (e.g., a TA value) may be included in a response signal (e.g., an RAR) of the RACH. The RAR may be transmitted from the serving cell or the candidate cell. Alternatively, the TA of the candidate cell may be acquired using a RACH triggered by the UE or a RACH triggered by a higher layer from the network. The PDCCH order may be triggered only by the source cell (or the serving cell).

[0073] Alternatively, the UE may acquire the TA of the candidate cell by transmitting a signal other than the RACH to the candidate cell. Information about the TA of the candidate cell (e.g., the TA value) may be indicated to the UE from the base station. As the signal other than the RACH, for example, the SRS may be applied (e.g., SRS-based TA measurement).

[0074] Alternatively, the UE may measure / calculate / obtain the TA for the candidate cell based on DL signals (e.g., downlink reference signals) transmitted from each cell (e.g., candidate cell / serving cell). A method in which the UE obtains the TA for the candidate cell based on DL signals transmitted from one or more cells may be called UE-based TA measurement.

[0075] In the UE-based TA measurement, the downlink reference signal may be a predetermined DL signal (e.g., a synchronization signal block (e.g., SSB) / CSI-RS, etc.). For example, the UE may measure the difference / difference in reception timing of DL signals from multiple cells (or two cells) and obtain the TA of the candidate cell.

[0076] The multiple cells may include a reference cell (e.g., a serving cell). In this case, the UE may calculate the TA required for the candidate cell based on the reception timing of the reference cell (and the TA value of the reference cell) and the timing difference (e.g., T) between the reference cell and the candidate cell. The UE may obtain the TA of the candidate cell using a timing advance command (TAC) transmitted from the serving cell.

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

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

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

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

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

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

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

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

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

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

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

[0088] Also, for example, when N=2 and M=2, it may mean that multiple (two) UL TCI states and multiple (two) DL TCI states for multiple (two) TRPs are notified / configured / instructed to the UE (separate TCI states for multiple TRPs).

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

[0090] Support for N = M = 1 is being considered for Rel. 17. For example, it may be supported to indicate one common beam (e.g., a common beam) using RRC / MAC CE / DCI, and the common beam may be applied to multiple DL / UL channels / reference signals. Other cases may also be supported in Rel. 18 and later.

[0091] 5A and 5B illustrate an example of a unified TCI framework, where FIG. 5A illustrates an example of a joint DL / UL TCI state, and FIG. 5B illustrates an example of a separate TCI state.

[0092] In the example of Figure 5A, RRC parameters (information elements) configure multiple TCI states for both DL and UL. In this disclosure, the TCI states configured by the RRC parameters may be referred to as configured TCI states or configured TCI states (e.g., configured TCI states). The MAC CE may activate multiple TCI states from the configured TCI states. The DCI may indicate one of the activated TCI states. In this disclosure, the TCI state indicated by the DCI may be referred to as indicated TCI state or indicated TCI state (e.g., indicated TCI state).

[0093] The DCI may be a UL DCI (e.g., a DCI used to schedule a PUSCH) or a DL DCI (e.g., a DCI used to schedule a PDSCH). The indicated TCI state may apply to at least one (or all) of the UL / DL channels / RS. One DCI may indicate both a UL TCI and a DL TCI.

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

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

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

[0097] In the example of Figure 5B, 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.

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

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

[0100] The method of setting / indicating the TCI state (e.g., joint DL / UL TCI state) in Fig. 5A and the method of setting / indicating the application of the TCI state (e.g., separate TCI state) in Fig. 5B may be switched and applied. Whether the joint DL / UL TCI state or the separate TCI state is applied may be configured by a base station to the UE by a higher layer parameter.

[0101] [Physical Layer Procedures for Data / Antenna Port QCL] In PDSCH-Config, the UE can configure a list of up to 128 DLorJointTCIState configurations to provide reference signals for PDSCH DMRS and PDCCH DMRS and CSI-RS within a CC, and also to provide a reference for determining the UL TX (Transmit) spatial filter for PUSCH and PUCCH resources and SRS within a CC based on dynamic and configuration grants, if available.

[0102] If there is no DLorJointTCIState or UL-TCIState (UL TCI state) configuration in the BWP in that CC, the UE may apply the DLorJointTCIState or UL-TCIState configuration from the reference BWP of the reference CC. If the UE has DLorJointTCIState or UL-TCIState configured in any CC in the same band, it does not assume that TCI-State, SpatialRelationInfo (spatial relation information), or PUCCH-SpatialRelationInfo (PUCCH spatial relation information) in that band are configured, except for SpatialRelationInfoPos (spatial relation information for position). The UE assumes that if the UE has TCI-State in any CC in the CC list configured by simultaneousTCI-UpdateList1-r16 (simultaneous TCI update list 1), simultaneousTCI-UpdateList2-r16 (simultaneous TCI update list 2), simultaneousSpatial-UpdatedList1-r16 (simultaneous spatial update list 1), or simultaneousSpatial-UpdatedList2-r16 (simultaneous spatial update list 2), the UE does not have DLorJointTCIState or UL-TCIState configured in any CC in that CC list.

[0103] The UE receives an activation command used to map up to eight TCI states and / or TCI state pairs, with one TCI state for DL ​​channels / signals and one TCI state for UL channels / signals, to codepoints in the DCI field 'Transmission Configuration Indication' (TCI) for one CC / DL BWP or set of CC / DL BWPs, if available. If a set of TCI state IDs is activated for a set of CC / DL BWPs, and also for one CC / DL BWP, if available, the same set of TCI state IDs applies to all DL and / or UL BWPs within the indicated CC, where the applicable list of CCs is determined by the CC indicated in the activation command. If the activation command maps DLorJointTCIState and / or UL-TCIState to only one TCI codepoint, the UE applies the indicated DLorJointTCIState and / or UL-TCIState to one or a set of CC / DL BWPs, and if the indicated mapping to one single TCI codepoint applies, the UE applies the indicated DLorJointTCIState and / or UL-TCIState to one or a set of CC / DL BWPs.

[0104] If the bwp-id or cell for a QCL type A / D source RS in the QCL-Info of a TCI state with DLorJointTCIState set is not set, the UE shall assume that the QCL type A / D source RS is set in the CC / DL BWP to which the TCI state applies.

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

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

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

[0108] The DCI in the above-mentioned mode 2 / mode 3 may be called a beam instruction DCI.

[0109] In Rel. 15 / 16, if a UE does not support active BWP changes via DCI, the UE ignores the BWP indicator field. A similar behavior is considered for the relationship between support for Rel. 17 TCI states and the interpretation of the TCI field. It is considered that if a UE is configured with Rel. 17 TCI states, the TCI field will always be present in DCI format 1_1 / 1_2, and if the UE does not support TCI updates via DCI, the UE will ignore the TCI field.

[0110] In Rel. 15 / 16, whether or not a TCI field is present (TCI presence information in DCI, tci-PresentInDCI) is set for each CORESET.

[0111] The TCI field in DCI format 1_1 is 0-bit if the higher layer parameter tci-PresentInDCI is not enabled, and 3-bit otherwise. If the BWP indicator field indicates a BWP other than the active BWP, the UE shall follow the following behavior: [Action] If the higher layer parameter tci-PresentInDCI is not enabled for the CORESET used for the PDCCH carrying that DCI format 1_1, the UE shall assume that tci-PresentInDCI is not enabled for all CORESETs in the indicated BWP; otherwise, the UE shall assume that tci-PresentInDCI is enabled for all CORESETs in the indicated BWP.

[0112] The TCI field in DCI format 1_2 is 0 bit if the higher layer parameter tci-PresentInDCI-1-2 is not set, otherwise it is 1, 2 or 3 bits determined by the higher layer parameter tci-PresentInDCI-1-2. If the BWP indicator field indicates a BWP other than the active BWP, the UE shall follow the following actions. [Operation] If the higher layer parameter tci-PresentInDCI-1-2 is not set for the CORESET used for the PDCCH carrying that DCI format 1_2, the UE shall assume that tci-PresentInDCI is not enabled for all CORESETs in the indicated BWP; otherwise, the UE shall assume that tci-PresentInDCI-1-2 for all CORESETs in the indicated BWP is set with the same value as tci-PresentInDCI-1-2 set for the CORESET used for the PDCCH carrying that DCI format 1_2.

[0113] 6A shows an example of a DCI-based joint DL / UL TCI status indication, in which a TCI status ID indicating the joint DL / UL TCI status is associated with a value of the TCI field for the joint DL / UL TCI status indication.

[0114] 6B shows an example of DCI-based separate DL / UL TCI status indication. At least one TCI state ID, indicating a DL-only TCI state or indicating a UL-only TCI state, is associated with a value of the TCI field for the separate DL / UL TCI status indication. In this example, TCI field values ​​000 to 001 are associated with only one TCI state ID for DL, TCI field values ​​010 to 011 are associated with only one TCI state ID for UL, and TCI field values ​​100 to 111 are associated with both one TCI state ID for DL ​​and one TCI state ID for UL.

[0115] (Indicated TCI State / Configured TCI State) For Rel. 17 TCI states, unified / common TCI state may mean the Rel. 17 TCI state indicated using (Rel. 17) DCI / MAC CE / RRC (indicated Rel. 17 TCI state).

[0116] In the present disclosure, the terms indicated Rel. 17 TCI state, indicated TCI state, unified / common TCI state, TCI state applicable to multiple types of signals (channels / RS), and TCI state for multiple types of signals (channels / RS) may be interpreted interchangeably.

[0117] The indicated Rel. 17 TCI state may be shared with at least one of the UE-specific reception of PDSCH / PDCC (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 or the unified TCI state.

[0118] Regarding the Rel. 17 TCI state, a TCI state other than the unified TCI state may refer to a Rel. 17 TCI state configured using (Rel. 17) MAC CE / RRC (configured Rel. 17 TCI state). In this disclosure, the terms configured Rel. 17 TCI state, configured TCI state, TCI state other than the unified TCI state, and TCI state applied to a specific type of signal (channel / RS) may be interpreted interchangeably.

[0119] The configured Rel. 17 TCI state may not 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 configured Rel. 17 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 Rel. 17 TCI state (common TCI state) is updated.

[0120] It is being considered that the indicated Rel. 17 TCI state will be applied to UE-specific channels / signals (RS), and that the UE will be notified by higher layer signaling (RRC signaling) whether the indicated Rel. 17 TCI state or the configured Rel. 17 TCI state will be applied to non-UE-specific channels / signals.

[0121] It is being considered that the RRC parameters for the configured Rel. 17 TCI state (TCI state ID) will have the same configuration as the RRC parameters for the TCI state in Rel. 15 / 16. It is also being considered that the configured Rel. 17 TCI state will be configured / instructed per CORESET / per resource / per resource set using RRC / MAC CE. It is also being considered that the UE will determine the configuration / instruction based on specific parameters.

[0122] It is considered that the UE updates the indicated TCI state and the configured TCI state separately. For example, if the unified TCI state for the indicated TCI state is updated, the UE may not update the configured TCI state. It is also considered that the UE may determine whether to update the configured TCI state based on a specific parameter.

[0123] Furthermore, regarding the PDCCH / PDSCH, it is being considered to use higher layer signaling (RRC / MAC CE) to switch whether the indication Rel. 17 TCI state is applied or not (the configured Rel. 17 TCI state is applied, or a TCI state configured separately from the indication Rel. 17 TCI state is applied).

[0124] Regarding intra-cell beam indication (TCI state indication), it is being considered to support Rel. 17 TCI state indication for a UE-specific CORESET and its associated PDSCH, and a non-UE-specific CORESET and its associated PDSCH.

[0125] Also, for inter-cell beam indication (e.g., L1 / L2 inter-cell mobility), it is being considered to support Rel. 17 TCI state indication for a UE-specific CORESET and its associated PDSCH.

[0126] In Rel. 15, whether to indicate the TCI state for CORESET #0 was up to the implementation of the base station. In Rel. 15, for CORESET #0 for which a TCI state is indicated, the indicated TCI state is applied. For CORESET #0 for which a TCI state is not indicated, the SSB and QCL selected at the time of the latest (most recent) PRACH transmission are applied.

[0127] In the unified TCI state framework for Rel. 17 and later, the TCI state for CORESET #0 is being considered.

[0128] For example, in the unified TCI state framework for Rel. 17 and later, whether or not to apply the indicated Rel. 17 TCI state associated with the serving cell for the Rel. 17 TCI state indication in CORESET #0 is configured by RRC for each CORESET, and if not, the legacy MAC CE / RACH signaling mechanism may be used.

[0129] Note that the CSI-RS associated with the Rel. 17 TCI state applied to CORESET #0 may be QCL'd with the SSB associated with the serving cell PCI (physical cell ID) (similar to Rel. 15).

[0130] For CORESET #0, a CORESET with a common search space (CSS), and a CORESET with a CSS and a UE-specific search space (USS), whether to follow the Rel. 17 TCI state may be configured for each CORESET by an RRC parameter. If the Rel. 17 TCI state is not configured to be followed for that CORESET, the configured Rel. 17 TCI state may be applied to that CORESET.

[0131] For non-UE-dedicated channels / RSs (except CORESET), whether to follow the indicated Rel. 17 TCI state may be configured by an RRC parameter for each channel / resource / resource set. If the indicated Rel. 17 TCI state is not configured for that channel / resource / resource set, the configured Rel. 17 TCI state may apply to that channel / resource / resource set.

[0132] (Channels / RSs to which the indicated TCI state applies) The indicated TCI state by the MAC CE / DCI may apply to the following channels / RSs:

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

[0134] [PDSCH] - The indicated TCI state always applies to all UE-dedicated PDSCHs. - For non-UE-dedicated PDSCHs (PDSCHs scheduled by DCI in 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.

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

[0136] [PUCCH] - For all dedicated PUCCH resources, the indicated TCI state always applies.

[0137] [PUSCH] - For dynamic / configured grant PUSCH, the indication TCI state always applies.

[0138] [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 is applied. For other SRSs, the configured TCI state in the SRS resource set is applied.

[0139] (Analysis) Incidentally, in Rel. 18 and later, support for two timing advances (TAs) is being considered in multi-DCI-based multi-TRP operation.

[0140] For example, in Rel. 18 and later, two timing advance groups (TAGs) belonging to one serving cell may be configured.

[0141] It is also being considered to set two timing advance offsets for each serving cell (for example, fixed offsets used to calculate the timing advance indicated by n-TimingAdvanceOffset (n-TimingAdvanceOffset and n-TimingAdvanceOffset2)).

[0142] It is also contemplated that a TAG is associated with a joint TCI state or a UL TCI state, and that for UL transmissions, a TAG ID associated with the joint TCI state or the UL TCI state is utilized.

[0143] However, there is little consideration as to how to determine the TAG before determining the UL / joint TCI state for the UL channel / signal.

[0144] UL transmissions before the application of the unified / indicative TCI state may be, for example, random access preamble transmissions, message A PUSCH transmissions (in a two-step RACH), PUSCH scheduled by a random access response (RAR) UL grant, etc.

[0145] The UL transmission before the application of the unified / indicative TCI state may be, for example, a UL transmission after receiving the initial higher layer parameters (configuration) for the TCI state but before the application of the indicated TCI state, in which case, in Rel. 17, the UL transmit spatial filter for the UL transmission (e.g., PUSCH / PUCCH / SRS) may be the same as the PUSCH transmission scheduled by the RAR UL grant.

[0146] The UL transmission before the application of the unified / indicative TCI state may be, for example, a UL transmission after receiving higher layer parameters (configuration) related to the TCI state but before the application of the indicated TCI state, in which case, in Rel. 17, the UL transmit spatial filter for the UL transmission (e.g., PUSCH / PUCCH / SRS) may be the same as that for the PUSCH transmission scheduled by the RAR UL grant.

[0147] In the existing specification (Rel. 17), for TA, the UL frame number i for transmission from the UE is determined by a specific time (e.g., T ＴＡ ) before the

[0148] The specific time is, for example, expressed by the formula: T ＴＡ = (N ＴＡ +N ＴＡ，ｏｆｆｓｅｔ +N ｃｏｍｍｏｎ ＴＡ，ａｄｊ+N ＵＥ ＴＡ，ａｄｊ ) T Ｃ It may be calculated as follows.

[0149] Here, N ＴＡ is the timing advance between DL and UL, ＴＡ，ｏｆｆｓｅｔ defines a fixed offset used in calculating the timing advance, N ｃｏｍｍｏｎ ＴＡ，ａｄｊ is the network-controlled timing correction, ＵＥ ＴＡ，ａｄｊ is the UE-derived timing correction, T Ｃ may respectively indicate the Basic time unit for NR.

[0150] For example, in the random access preamble transmission and the message A PUSCH transmission, N ＴＡ is 0, and N ＴＡ，ｏｆｆｓｅｔ applies.

[0151] Two TAGs or two Ns for one serving cell ＴＡ，ｏｆｆｓｅｔ If the value of is set, either TAG or N ＴＡ，ｏｆｆｓｅｔ There is insufficient consideration as to whether the value of (1) should be applied to random access preamble transmission and message A PUSCH transmission.

[0152] Similarly, for PUSCH scheduled by RAR UL grant, UL transmissions (e.g. PUSCH / PUCCH / SRS) after receiving initial higher layer parameters for TCI state (dl-OrJoint-TCIStateList with one or more TCI-States or UL-TCI-States) and before applying the indicated TCI state, and for UL transmissions (e.g. PUSCH / PUCCH / SRS) after receiving higher layer parameters for TCI state (dl-OrJoint-TCIStateList with one or more TCI-States or UL-TCI-States) as part of synchronization reconfiguration and before applying the indicated TCI state, two TAGs or two N ＴＡ，ｏｆｆｓｅｔ If the value of is set, either TAG or N ＴＡ，ｏｆｆｓｅｔ There has been insufficient consideration as to whether to apply this value.

[0153] If these considerations are not sufficient, it may not be possible to determine the TA to be applied to UL transmission, which may hinder the realization of appropriate communication and result in a decrease in communication throughput.

[0154] Therefore, the present inventors came up with a method for solving the above problem.

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

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

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

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

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

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

[0161] In the present disclosure, physical layer signaling may be, for example, Downlink Control Information (DCI), Uplink Control Information (UCI), and the like.

[0162] (Wireless communication method) For one serving cell, offsets (N ＴＡ，ｏｆｆｓｅｔ ) or TAG may be provided.

[0163] The UE may configure one serving cell with offsets (e.g., N ＴＡ，ｏｆｆｓｅｔ ) and / or TAG may be set.

[0164] The UE may select / determine one offset / TAG from multiple offsets / TAGs to determine the TA (see FIG. 7).

[0165] The UE may select / determine one offset / TAG for a particular UL transmission based on a particular method (e.g., at least one of a selection of a particular offset / TAG, a configuration by higher layer signaling, a PDCCH order associated with the particular UL transmission, a reference signal associated with the particular UL transmission, a signal scheduling the particular UL transmission, other UL transmissions different from the particular UL transmission, and a CORESET pool index associated with the particular UL transmission).

[0166] First Embodiment The UE determines offsets (N ＴＡ，ｏｆｆｓｅｔ ) or TAG to apply to a particular UL transmission related to the random access operation (e.g., a random access preamble (e.g., PRACH) and / or a PUSCH (e.g., Message A PUSCH) related to the random access operation).

[0167] The UE / base station may follow at least one of options 1-1 to 1-6 below.

[0168] One of options 1-1 to 1-6 may be used alone, or at least two of options 1-1 to 1-6 may be used in combination.

[0169] The application of one of options 1-1 to 1-6 may be specified in advance, or switching between at least two of options 1-1 to 1-6 may be based on reporting of UE capability information and at least one of MIB / SIB / upper layer signaling.

[0170] For options 1-1 to 1-6, different / common options may be applied to at least one of intra-cell multi-TRP, inter-cell multi-TRP, UE-initiated (triggered) random access, and PDCCH order-initiated (triggered) random access.

[0171] Option 1-1: The UE determines the offset (N ＴＡ，ｏｆｆｓｅｔ ) or TAG, it may be assumed / determined to apply a particular offset value / TAG to a particular UL transmission.

[0172] The particular offset value may be, for example, the first offset value.

[0173] The particular TAG may be, for example, the first TAG (eg, the TAG with the lower ID).

[0174] The particular offset value may be, for example, the second offset value.

[0175] The particular TAG may be, for example, a second TAG (eg, a TAG with a higher ID).

[0176] The first / second offset values ​​may be set using, for example, a specific upper layer parameter.

[0177] The first offset value may be set using, for example, a parameter (e.g., n-TimingAdvanceOffset) defined in Rel. 15. The second offset value may be set using, for example, a parameter (e.g., n-TimingAdvanceOffset2) defined in Rel. 18 or later.

[0178] The specific upper layer parameters may be included in a serving cell configuration (e.g., ServingCellConfigCommon / ServingCellConfigCommonSIB) for configuring cell-specific parameters.

[0179] The particular offset value may be, for example, the offset value corresponding to the first CORESET.

[0180] The specific TAG may be, for example, the TAG corresponding to the first CORESET.

[0181] The first CORESET may be, for example, a CORESET of a CORESET pool index (CORESETPoolIndex) having a first value (e.g., 0), or may be a CORESET when a CORESET pool index (CORESETPoolIndex) is not provided.

[0182] The particular offset value may be, for example, an offset value corresponding to the second CORESET.

[0183] The specific TAG may be, for example, a TAG corresponding to the second CORESET.

[0184] The second CORESET may be, for example, a CORESET of a CORESETPoolIndex having a second value (eg, 1).

[0185] The particular offset value may be, for example, an offset value corresponding to a TCI state associated with the first CORESET.

[0186] The particular TAG may be, for example, a TAG corresponding to a TCI state associated with the first CORESET.

[0187] The first CORESET may be, for example, a CORESET of a CORESET pool index (CORESETPoolIndex) having a first value (e.g., 0), or may be a CORESET when a CORESET pool index (CORESETPoolIndex) is not provided.

[0188] The particular offset value may be, for example, an offset value corresponding to a TCI state associated with the second CORESET.

[0189] The particular TAG may be, for example, a TAG corresponding to a TCI state associated with the second CORESET.

[0190] The second CORESET may be, for example, a CORESET of a CORESETPoolIndex having a second value (eg, 1).

[0191] The particular offset value may be, for example, an offset value corresponding to the physical cell ID (PCI) of a particular cell.

[0192] The specific TAG may be, for example, a TAG corresponding to the physical cell ID (PCI) of a specific cell.

[0193] The particular cell may be, for example, a serving cell.

[0194] The specific cell may be, for example, a non-serving cell, and the PCI of the specific cell may be, for example, a PCI different from the PCI of the serving cell, or an additional PCI.

[0195] According to option 1-1, the offset / TAG to be applied to the UL transmission can be determined based on other parameters.

[0196] Option 1-2: The UE may use multiple (e.g., two) TA offsets (N ＴＡ，ｏｆｆｓｅｔ) or TAG, it may be assumed / determined to apply a particular offset value / TAG to a particular UL transmission.

[0197] The particular offset value / TAG may be, for example, a larger offset value / TAG ID.

[0198] The particular offset value / TAG may be, for example, a smaller offset value / TAG ID.

[0199] Other rules for selecting one offset value / TAG from multiple offset values / TAGs may be defined.

[0200] According to option 1-2, the offset / TAG to be applied to the UL transmission can be determined based on a specific rule.

[0201] Option 1-3: The UE may use multiple (e.g., two) TA offsets (N ＴＡ，ｏｆｆｓｅｔ ) or TAG, it may be assumed / determined to apply a particular offset value / TAG for a particular UL transmission based on higher layer signaling (RRC signaling).

[0202] The higher layer signaling may indicate, for example, which of multiple offsets / TAGs to apply.

[0203] According to options 1-3, the offset / TAG to be applied to the UL transmission can be determined based on higher layer signaling.

[0204] Option 1-4: The UE may use multiple (e.g., two) TA offsets (N ＴＡ，ｏｆｆｓｅｔ ) or TAG, it may be assumed / determined to apply a particular offset value / TAG for a particular UL transmission based on the PDCCH order.

[0205] The PDCCH order may indicate, for example, which offset / TAG to apply from among multiple offsets / TAGs.

[0206] This option may be applied, for example, when a random access operation is triggered by a PDCCH order.

[0207] For example, the UE may be instructed by a PDCCH order which RACH configuration to use.

[0208] For example, the RACH configuration may be the RACH configuration of the serving cell or the RACH configuration of a non-serving cell / additional cell.

[0209] For example, when the RACH configuration of the serving cell is used, the UE may assume / determine to apply the offset / TAG corresponding to the serving cell from among multiple offsets / TAGs.

[0210] For example, when a RACH configuration of a non-serving cell / additional cell is used, the UE may assume / determine to apply an offset / TAG corresponding to the non-serving cell / additional cell from among multiple offsets / TAGs.

[0211] According to options 1-4, the offset / TAG to be applied to UL transmission can be determined based on the PDCCH order / RACH configuration.

[0212] Option 1-5: The UE may use multiple (e.g., two) TA offsets (N ＴＡ，ｏｆｆｓｅｔ ) or TAG, it may be assumed / determined to apply a specific offset value / TAG to a specific UL transmission based on a reference signal (e.g., SSB / CSI-RS) associated with the specific UL transmission.

[0213] For example, a first offset value / TAG may be associated with a first reference signal (eg, SSB / CSI-RS) / group of reference signals.

[0214] For example, the second offset value / TAG may be associated with a second reference signal (eg, SSB / CSI-RS) / group of reference signals.

[0215] For example, if a particular UL transmission is associated with a first group of SSB / CSI-RS, the UE may apply a first offset value / TAG to the particular UL transmission.

[0216] According to options 1-5, the offset / TAG to apply to the UL transmission can be determined based on the reference signal / group of reference signals.

[0217] Option 1-6: The UE may use multiple (e.g., two) TA offsets (N ＴＡ，ｏｆｆｓｅｔ ) or TAG, it may be assumed / determined to apply a specific offset value / TAG to a specific UL transmission based on a reference signal (e.g., SSB / CSI-RS) associated with the specific UL transmission.

[0218] For example, a first offset value / TAG may be associated with a first reference signal (eg, SSB / CSI-RS) / group of reference signals.

[0219] For example, the second offset value / TAG may be associated with a second reference signal (eg, SSB / CSI-RS) / group of reference signals.

[0220] For example, if a first group of SSB / CSI-RSs is used as the reference RS for the spatial domain filter of a particular UL transmission, the UE may apply a first offset value / TAG to the particular UL transmission.

[0221] For example, if a second group of SSB / CSI-RS is used as the reference RS for the spatial domain filter of a particular UL transmission, the UE may apply a second offset value / TAG to the particular UL transmission.

[0222] According to options 1-6, the offset / TAG to be applied to a UL transmission may be determined based on the reference signal / group of reference signals used as the reference RS for that UL transmission.

[0223] Second Embodiment The UE determines offsets (N ＴＡ，ｏｆｆｓｅｔ) or TAG to apply to a particular UL transmission for random access operation (e.g., PUSCH scheduled by a RAR UL grant).

[0224] The UE / base station may follow at least one of options 2-1 to 2-9 below.

[0225] One of the options 2-1 to 2-9 may be used alone, or at least two of the options 2-1 to 2-9 may be used in combination.

[0226] The application of one of options 2-1 to 2-9 may be specified in advance, or switching between at least two of options 2-1 to 2-9 may be based on reporting of UE capability information and at least one of MIB / SIB / higher layer signaling.

[0227] For options 2-1 to 2-9, different / common options may be applied to at least one of intra-cell multi-TRP, inter-cell multi-TRP, UE-initiated (triggered) random access, and PDCCH order-initiated (triggered) random access.

[0228] <<Option 2-1>> The above-mentioned option 1-1 may be applied as appropriate to a specific UL transmission of this embodiment.

[0229] <<Option 2-2>> The above-mentioned option 1-2 may be applied as appropriate to a specific UL transmission of this embodiment.

[0230] <<Options 2-3>> The above options 1-3 may be applied as appropriate to specific UL transmissions of this embodiment.

[0231] Options 2-4 The above options 1-4 may be applied as appropriate to specific UL transmissions in this embodiment.

[0232] Options 2-5 The above options 1-5 may be applied as appropriate to specific UL transmissions of this embodiment.

[0233] Options 2-6 The above options 1-6 may be applied as appropriate to specific UL transmissions in this embodiment.

[0234] Option 2-7: The UE may use multiple (e.g., two) TA offsets (N ＴＡ，ｏｆｆｓｅｔ ) or TAG, it may be assumed / determined to apply a particular offset value / TAG to a particular UL transmission based on the RAR (instructions in the RAR).

[0235] The UE may be instructed in the RAR to which TAG the TA command carried in the RAR applies.

[0236] The UE may apply the indicated TAG and corresponding offset value to a particular UL transmission.

[0237] According to option 2-7, the offset / TAG to be applied to the UL transmission can be determined based on the RAR (instructions within the RAR).

[0238] Option 2-8: The UE may specify offsets (N ＴＡ，ｏｆｆｓｅｔ ) or TAG, it may be assumed / determined to apply a specific offset value / TAG to a specific UL transmission based on a UL transmission other than the specific UL transmission.

[0239] The other UL transmission may be, for example, a random access preamble (PRACH).

[0240] For example, the UE may assume / determine to apply, to a specific UL transmission, one of multiple offsets / TAGs that is the same as the offset / TAG applied to a UL transmission other than the specific UL transmission.

[0241] For example, the UE may assume / determine to apply, to a specific UL transmission, an offset / TAG from among multiple offsets / TAGs that is different from the offset / TAG applied to a UL transmission other than the specific UL transmission.

[0242] According to options 2-8, the offset / TAG to apply to a UL transmission can be determined based on other UL transmissions.

[0243] Option 2-9: The UE may use multiple (e.g., two) TA offsets (N ＴＡ，ｏｆｆｓｅｔ ) or TAG, it may be assumed / determined to apply a particular offset value / TAG to a particular UL transmission based on the CORESET pool index.

[0244] For example, an offset value / TAG may be associated with a particular CORESETPoolIndex.

[0245] For example, the UE may assume / decide to apply an offset value / TAG associated with the CORESETPoolIndex corresponding to the scheduling DCI in the RAR for a particular UL transmission.

[0246] According to option 2-9, the offset / TAG to apply to the UL transmission can be determined based on the CORESET pool index.

[0247] Third Embodiment The UE determines offsets (N ＴＡ，ｏｆｆｓｅｔ ) or TAG to apply to a particular UL transmission.

[0248] The particular UL transmission may be, for example, a UL transmission after receiving higher layer parameters relating to the unified TCI state and before applying the indicated TCI state.

[0249] The particular UL transmission may be, for example, at least one of an UL transmission (e.g., PUSCH / PUCCH / SRS) after reception of initial higher layer parameters for the unified TCI state (dl-OrJoint-TCIStateList with one or more TCI-States or UL-TCI-States) and before application of the indicated TCI state, and an UL transmission (e.g., PUSCH / PUCCH / SRS) after reception of higher layer parameters for the unified TCI state (dl-OrJoint-TCIStateList with one or more TCI-States or UL-TCI-States) as part of a reconfiguration for synchronization and before application of the indicated TCI state.

[0250] The UE / base station may follow at least one of options 3-1 to 3-10 below.

[0251] One of Options 3-1 to 3-10 may be used alone, or at least two of Options 3-1 to 3-10 may be used in combination.

[0252] The application of one of options 3-1 to 3-10 may be specified in advance, or switching between at least two of options 3-1 to 3-10 may be based on reporting of UE capability information and at least one of MIB / SIB / higher layer signaling.

[0253] For options 3-1 to 3-10, different / common options may be applied to at least one of intra-cell multi-TRP, inter-cell multi-TRP, random access initiated (triggered) by the UE, and random access initiated (triggered) by a PDCCH order.

[0254] <<Option 3-1>> The above-mentioned option 2-1 (1-1) may be applied as appropriate to a specific UL transmission of this embodiment.

[0255] <<Option 3-2>> The above Option 2-2 (1-2) may be applied as appropriate to a specific UL transmission of this embodiment.

[0256] <<Option 3-3>> The above Option 2-3 (1-3) may be applied as appropriate to a specific UL transmission of this embodiment.

[0257] <<Option 3-4>> The above-mentioned options 2-4 (1-4) may be applied as appropriate to a specific UL transmission of this embodiment.

[0258] <<Option 3-5>> The above options 2-5 (1-5) may be applied as appropriate to specific UL transmissions of this embodiment.

[0259] <<Option 3-6>> The above-mentioned options 2-6 (1-6) may be applied as appropriate to specific UL transmissions of this embodiment.

[0260] <<Options 3-7>> The above options 2-7 may be applied as appropriate to specific UL transmissions of this embodiment.

[0261] <<Options 3-8>> The above options 2-8 may be applied as appropriate to specific UL transmissions of this embodiment.

[0262] Option 3-9: The UE may use multiple (e.g., two) TA offsets (N ＴＡ，ｏｆｆｓｅｔ ) or TAG, it may be assumed / determined to apply a specific offset value / TAG to a specific UL transmission based on a UL transmission other than the specific UL transmission.

[0263] The other UL transmission may be, for example, an UL transmission in an initial access / random access procedure (e.g., a PUSCH scheduled by an RAR UL grant and / or the like).

[0264] For example, the UE may assume / determine to apply, to a specific UL transmission, one of multiple offsets / TAGs that is the same as the offset / TAG applied to a UL transmission other than the specific UL transmission.

[0265] For example, the UE may assume / determine to apply, to a specific UL transmission, an offset / TAG from among multiple offsets / TAGs that is different from the offset / TAG applied to a UL transmission other than the specific UL transmission.

[0266] According to options 3-9, the offset / TAG to apply to a UL transmission can be determined based on other UL transmissions.

[0267] Option 3-10: The UE may specify offsets (N ＴＡ，ｏｆｆｓｅｔ ) or TAG, it may be assumed / determined to apply a particular offset value / TAG to a particular UL transmission based on the CORESET pool index.

[0268] For example, an offset value / TAG may be associated with a particular CORESETPoolIndex.

[0269] For example, the UE may assume / decide to apply to a particular UL transmission an offset value / TAG associated with the CORESET pool index (CORESETPoolIndex) corresponding to the scheduling / triggering DCI of the PUSCH / PUCCH / SRS related to that particular UL transmission.

[0270] According to option 3-10, the offset / TAG to apply to the UL transmission can be determined based on the CORESET pool index.

[0271] <Supplementary Information> [Notification of Information to UE] In the above-described embodiments, any information may be notified 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) 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.

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

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

[0274] Furthermore, notification of any information to the UE in the above embodiments may be performed periodically, semi-persistently, or aperiodically.

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

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

[0277] If the notification is made by UCI, the notification may be transmitted using PUCCH or PUSCH.

[0278] Furthermore, any information in the above-described embodiments may be notified from the UE periodically, semi-persistently, or aperiodically.

[0279] [Application of Each Embodiment] At least one of the above-described embodiments may be applied when a specific condition is met. The specific condition may be defined in a standard or may be notified to a UE / BS using higher layer signaling / physical layer signaling.

[0280] At least one of the above-described embodiments may be applied only to UEs that have reported or support a particular UE capability.

[0281] The specific UE capability may indicate at least one of the following: Supporting specific processing / operation / control / information for at least one of the above embodiments; Supporting multiple (two) TA extensions for multi-DCI intra-cell multi-TRP; Supporting multiple (two) TA extensions for multi-DCI inter-cell multi-TRP; The number of supported (candidate) TAs.

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

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

[0284] Furthermore, at least one of the above-described embodiments may be applied when the UE configures / activates / triggers specific information related to the above-described embodiments (or performs the operations of the above-described embodiments) through higher layer signaling / physical layer signaling. For example, the specific information may be information indicating the enablement of multiple TAs, any RRC parameters for a specific release (e.g., Rel. 18 / 19), etc.

[0285] If the UE does not support at least one of the specific UE capabilities or is not configured with the specific information, the UE may apply, for example, Rel. 15 / 16 behavior.

[0286] (Supplementary Note A) The following inventions are added to one embodiment of the present disclosure. [Supplementary Note A-1] A terminal including: a receiver that receives configurations related to at least one of a plurality of offsets related to a timing advance (TA) and a plurality of timing advance groups (TAGs), and a controller that determines, based on a specific method, at least one of a specific offset and a specific TAG to be applied to uplink transmission related to a random access procedure from among the plurality of offsets and the plurality of TAGs. [Supplementary Note A-2] The terminal described in Supplementary Note A-1, wherein the controller selects, as the specific offset and / or the specific TAG, at least one of a first offset and a first TAG, or at least one of an offset with a larger value and a TAG with a larger value. [Supplementary Note A-3] The terminal described in Supplementary Note A-1 or Supplementary Note A-2, wherein the controller determines the specific offset and / or the specific TAG based on a physical downlink control channel order related to the uplink transmission. [Supplementary Note A-4] The terminal according to any one of Supplementary Note A-1 to Supplementary Note A-3, wherein the control unit determines at least one of the specific offset and the specific TAG based on a reference signal related to the uplink transmission.

[0287] (Supplementary Note B) The following inventions are added to one embodiment of the present disclosure. [Supplementary Note B-1] A terminal, comprising: a receiver unit that receives configurations related to at least one of a plurality of offsets related to a timing advance (TA) and a plurality of timing advance groups (TAGs), and a controller that determines, based on a specific method, at least one of a specific offset and a specific TAG to apply to a specific uplink transmission from the plurality of offsets and the plurality of TAGs, wherein the specific uplink transmission is an uplink transmission after receiving higher layer parameters related to a unified Transmission Configuration Indication (TCI) state and before applying an indicated TCI state. [Supplementary Note B-2] The terminal according to Supplementary Note B-1, wherein the controller selects, as the specific offset and / or the specific TAG, at least one of a first offset and a first TAG, or at least one of an offset with a larger value and a TAG with a larger value. [Supplementary Note B-3] The terminal according to Supplementary Note B-1 or Supplementary Note B-2, wherein the control unit determines at least one of the specific offset and the specific TAG based on a physical downlink control channel order related to the uplink transmission. [Supplementary Note B-4] The terminal according to any one of Supplementary Note B-1 to Supplementary Note B-3, wherein the control unit determines at least one of the specific offset and the specific TAG based on a reference signal related to the uplink transmission.

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

[0289] 8 is a diagram illustrating an example of a schematic configuration of a wireless communication system according to an embodiment. The wireless communication system 1 (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).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0332] The transceiver 120 may transmit a configuration for at least one of a plurality of offsets related to a timing advance (TA) and a plurality of timing advance groups (TAGs). The control unit 110 may use the configuration to indicate at least one of a specific offset and a specific TAG to be applied to uplink transmission related to a random access procedure, among the plurality of offsets and / or the plurality of TAGs, which are determined based on a specific method (first and second embodiments).

[0333] The transceiver 120 may transmit a configuration for at least one of a plurality of offsets and a plurality of timing advance groups (TAGs) related to a timing advance (TA). The control unit 110 may use the configuration to indicate at least one of a specific offset and a specific TAG to be applied to a specific uplink transmission, among the plurality of offsets and / or the plurality of TAGs, determined based on a specific method. The specific uplink transmission may be an uplink transmission after receiving higher layer parameters related to a unified Transmission Configuration Indication (TCI) state but before applying the indicated TCI state.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0352] The transceiver 220 may receive settings for at least one of a plurality of offsets related to timing advances (TAs) and a plurality of timing advance groups (TAGs). The controller 210 may determine, based on a specific method, at least one of a specific offset and a specific TAG to be applied to uplink transmissions related to the random access procedure from among the plurality of offsets and / or the plurality of TAGs (first and second embodiments).

[0353] The control unit 210 may select at least one of a first offset and a first TAG, or at least one of a larger offset and a larger TAG, as the specific offset and / or the specific TAG (first / second embodiment).

[0354] The control unit 210 may determine at least one of the specific offset and the specific TAG based on a physical downlink control channel order associated with the uplink transmission (first / second embodiment).

[0355] The control unit 210 may determine at least one of the specific offset and the specific TAG based on a reference signal related to the uplink transmission (first and second embodiments).

[0356] The transceiver 220 may receive configurations of at least one of a plurality of offsets related to a timing advance (TA) and a plurality of timing advance groups (TAGs). The controller 210 may determine, based on a specific method, at least one of a specific offset and a specific TAG to be applied to a specific uplink transmission from among the plurality of offsets and / or the plurality of TAGs. The specific uplink transmission may be an uplink transmission after receiving higher layer parameters related to a unified Transmission Configuration Indication (TCI) state and before applying the indicated TCI state (third embodiment).

[0357] The control unit 210 may select at least one of a first offset and a first TAG, or at least one of a larger offset and a larger TAG, as the specific offset and / or the specific TAG (third embodiment).

[0358] The control unit 210 may determine at least one of the specific offset and the specific TAG based on a physical downlink control channel order associated with the uplink transmission (third embodiment).

[0359] The control unit 210 may determine at least one of the specific offset and the specific TAG based on a reference signal related to the uplink transmission (third embodiment).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0422] 12 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0445] 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 ...." "does not expect ..." may be interchangeably read as "be not expected ...." 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" (e.g., if apparatus A is a UE, apparatus B may be a base station).

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

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

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

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

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

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

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

[0453] In this disclosure, the terms "of," "for," "regarding," "related to," "associated with," etc. may be read interchangeably.

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

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

[0456] 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 comprising: a receiving unit that receives settings for at least one of a plurality of offsets related to a timing advance (TA) and a plurality of timing advance groups (TAGs); and a control unit that determines, based on a specific method, at least one of a specific offset and a specific TAG to be applied to a specific uplink transmission from among the plurality of offsets and at least one of the plurality of TAGs, wherein the specific uplink transmission is an uplink transmission after receiving upper layer parameters related to a unified Transmission Configuration Indication (TCI) state and before application of an indicated TCI state.

2. The terminal according to claim 1, wherein the control unit selects at least one of a first offset and a first TAG, or at least one of an offset of a larger value and a TAG of a larger value, as the specific offset and / or the specific TAG.

3. The terminal according to claim 1, wherein the control unit determines at least one of the specific offset and the specific TAG based on a physical downlink control channel order associated with the uplink transmission.

4. The terminal according to claim 1, wherein the control unit determines at least one of the specific offset and the specific TAG based on a reference signal associated with the uplink transmission.

5. A wireless communication method for a terminal, comprising: a step of receiving settings for at least one of a plurality of offsets related to a timing advance (TA) and a plurality of timing advance groups (TAGs); and a step of determining, based on a specific method, at least one of a specific offset and a specific TAG to be applied to a specific uplink transmission from among the plurality of offsets and at least one of the plurality of TAGs, wherein the specific uplink transmission is an uplink transmission after receiving upper layer parameters related to a unified Transmission Configuration Indication (TCI) state and before application of the indicated TCI state.

6. A base station comprising: a transmitting unit that transmits settings regarding at least one of a plurality of offsets related to a timing advance (TA) and a plurality of timing advance groups (TAGs); and a control unit that uses the settings to indicate at least one of a specific offset and a specific TAG to be applied to a specific uplink transmission, among the plurality of offsets and at least one of the plurality of TAGs, which are determined based on a specific method, wherein the specific uplink transmission is an uplink transmission after receiving upper layer parameters related to a unified Transmission Configuration Indication (TCI) state and before application of the indicated TCI state.

Images