Terminal, radio communication method, and base station

Abstract

To appropriately control the timing of UL transmission.SOLUTION: A terminal according to an aspect of the present disclosure has: a receiving section that receives a parameter related to timing advance offset and settings related to a specific scenario in which two timing advances (TA) are supported; and a control section that determines whether to support UL transmission to which the two TAs are applied, on the basis of whether the specific scenario in which two timing advances (TA) are supported is set. The specific scenario is an inter-cell scenario involving path-loss (PL) offset, or an inter-cell scenario not involving the PL offset.SELECTED DRAWING: Figure 11

Description

[Technical Field]

[0001] The present disclosure relates to a terminal, a wireless communication method, and a base station in a next-generation mobile communication system. [Background technology]

[0002] In Universal Mobile Telecommunications System (UMTS) networks, Long Term Evolution (LTE) has been specified with the aim of achieving higher data rates and lower latency (Non-Patent Document 1). Also, LTE-Advanced (3GPP Rel. 10-14) has been specified with the aim of achieving higher capacity and more advanced features than LTE (Third Generation Partnership Project (3GPP (registered trademark)) Release (Rel.) 8, 9).

[0003] Successor systems to LTE (e.g., 5th generation mobile communication system (5G), 5G+ (plus), 6th generation mobile communication system (6G), New Radio (NR), 3GPP Rel. 15 or later) are also being considered. [Prior art documents] [Non-patent literature]

[0004] [Non-Patent Document 1] 3GPP TS 36.300 V8.12.0 “Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 (Release 8)”, April 2010 Summary of the Invention [Problem to be solved by the invention]

[0005] In future wireless communication systems (e.g., NR), in order to expand UL coverage, it is being considered to install UL receiving points in addition to general transmitting and receiving points. Also, Heterogeneous Networks (HetNets) using macro Base Stations (BSs) and micro BSs are being considered.

[0006] However, it is not clear how to determine the timing advance (TA) for the UL reception point (or micro BS) when a terminal (user terminal, User Equipment (UE)) performs UL transmission. If the TA cannot be determined correctly, there is a risk that the timing of UL transmission cannot be controlled appropriately.

[0007] Therefore, one object of the present disclosure is to provide a terminal, a wireless communication method, and a base station that can appropriately control the timing of UL transmission. [Means for solving the problem]

[0008] A terminal according to one embodiment of the present disclosure has a receiving unit that receives parameters related to timing advance offsets and settings related to a specific scenario in which two timing advances (TAs) are supported, and a control unit that determines whether to support UL transmission applying the two timing advances (TAs) based on whether a specific scenario in which two timing advances (TAs) are supported is configured, and is characterized in that the specific scenario is an intra-cell scenario with a path loss (PL) offset or an inter-cell scenario without a PL offset. [Effects of the Invention]

[0009] According to one aspect of the present disclosure, the timing of UL transmission can be appropriately controlled. [Brief explanation of the drawings]

[0010] [Figure 1] Fig. 1A is a diagram showing an example of a typical arrangement of transmission and reception points, and Fig. 1B is a diagram showing an example of a high-density UL arrangement. [Figure 2] FIG. 2 is a diagram illustrating an example of DL / UL coverage of a Heterogeneous Network (HetNet). [Figure 3] 3A and 3B are diagrams showing examples of associations between RS indexes and PL values, respectively, and FIG. 3B is a diagram showing examples of associations between RS indexes and delta PL values. [Figure 4] FIG. 4 shows an example of Option 1 in a high density UL deployment. [Figure 5] FIG. 5 shows an example of Option 2 in a high density UL deployment. [Figure 6] FIG. 6 is a diagram showing an example of setting a tag for a cell. [Figure 7] 7A and 7B are diagrams illustrating an example of a MAC CE for a timing advance command. [Figure 8] FIG. 8 illustrates an example in which only a DL TRP transmits a DL signal in an asymmetric multi-TRP scenario in which 2TA is supported. [Figure 9] 9A and 9B are diagrams illustrating an example of a case where a PL offset is set and a case where a PL offset is not set in an asymmetric multi-TRP scenario in which 2TA is supported. [Figure 10] 10A and 10B are diagrams showing an example of UL transmission control in the case where a PL offset is set and in the case where a PL offset is not set. [Figure 11] FIG. 11 is a diagram illustrating an example of UE operation when supporting two TAs according to the first embodiment. [Figure 12] FIG. 12 is a diagram illustrating an example of a schematic configuration of a wireless communication system according to an embodiment of the present disclosure. [Figure 13] FIG. 13 is a diagram illustrating an example of a configuration of a base station according to an embodiment of the present disclosure. [Figure 14] FIG. 14 is a diagram illustrating an example of a configuration of a terminal according to an embodiment of the present disclosure. [Figure 15] FIG. 15 is a diagram illustrating an example of a hardware configuration of a base station and a terminal according to an embodiment of the present disclosure. DETAILED DESCRIPTION OF THE INVENTION

[0011] (Scenario 1: High-density UL deployment (TRP with only UL)) In Rel. 15 NR, the coverage (reaching distance) of PUSCH, PUCCH, PRACH, PDSCH, PDCCH, and PBCH is uneven. The coverage of PUSCH is limited, especially at higher frequencies. Future wireless communication systems (e.g., Rel. 18, Rel. 19, or later) are expected to improve at least one of UL coverage and UL throughput.

[0012] In order to expand UL coverage, the installation of UL receiving points in addition to general transmitting and receiving points is being considered. Here, we will explain examples of the layout of general transmitting and receiving points and an example of a layout with UL receiving points (UL dense deployment).

[0013] Figure 1A shows an example of a typical arrangement of transmission / reception points. In Figure 1A, a UE receives a DL signal from a transmission / reception point (TRP) and transmits a UL signal to the TRP. For example, if the UE and the TRP are far apart, the path loss may be large, resulting in a deterioration in communication quality.

[0014] FIG. 1B is a diagram showing an example of a high-density UL deployment. To expand UL coverage, it is being considered to provide UL reception points as shown in FIG. 1B in addition to DL transmission points. In FIG. 1B, a UE receives DL signals from a DL transmission point (TRP / Central TRP / DL TRP / Macro TRP) corresponding to a macro cell and transmits UL signals to a UL reception point (e.g., a reception point with a smaller path loss / reception power). However, the UE may also be capable of UL transmission to a DL transmission point.

[0015] By using a high-density UL deployment like that shown in Figure 1B, both coverage and UL data rates can be improved by reducing path loss, improving UL signaling quality, and obtaining higher coding rates compared to the general deployment like that shown in Figure 1A. Also, since the UL receiving point mainly performs reception, it requires fewer functions (e.g., power amplifiers) and is therefore less costly than the transmitting / receiving points corresponding to typical small cells, making deployment management much easier.

[0016] In scenario 1, UL transmission of multiple TRPs may not be supported. For example, even if there are two TCIs to be indicated, UL TCI (UL single TRP) may always be indicated to one UE.

[0017] Alternatively, in Scenario 1, multi-TRP UL transmission (e.g., TDM / FDM repetition, SDM / SFN multi-panel simultaneous transmission, or all of them) may be supported. It may be specified that one of the two UL TRPs must be a DL TRP, or one of the two UL TRPs may be a DL TRP.

[0018] (Scenario 2: Decoupling of DL TRP and UL TRP in Heterogeneous Networks) In this disclosure, a Heterogeneous Network (HetNet) using a macro Base Station (BS) (DL TRP) and a micro BS (UL TRP) may be applied (Figure 2). In a typical HetNet, the transmission power of the macro BS and the micro BS is different. Also, the optimal DL coverage and the optimal UL coverage are different. For example, DL coverage is determined by RSRP, and UL coverage is determined by path loss (PL).

[0019] In the example shown in Figure 2, the UE is included in the optimal DL coverage of the macro BS and the optimal UL coverage of the micro BS. In this case, the UE can receive DL signals from the macro BS and transmit UL signals to the micro BS. However, the UE may transmit some reference signals / channels (e.g., an SRS with an antenna switching (AS) usage, used for DL ​​CSI acquisition) to the macro BS. Therefore, the UE may require two timing advances (TAs) in this scenario. Note that the AS SRS is transmitted to the macro BS because it is used by the base station (macro BS) to measure DL CSI (e.g., to determine the DL MIMO precoder) based on the reception of the SRS using channel reciprocity. On the other hand, the codebook / non-codebook SRS is transmitted to the micro BS because it is used for PUSCH precoder / beam determination.

[0020] In a HetNet, even if a micro BS has DL transmission capability, it can save energy by turning off DL most of the time. In this case, the function of the micro BS is similar to a UL-only TRP (UL Receiving Point).

[0021] (Path loss (PL) reception) The UE may receive first information indicating a path loss (PL) used for transmission power control (TPC), which is estimated and notified (transmitted) by the network, via DL signaling. The DL signaling may be at least one of higher layer signaling (e.g., RRC or MAC CE) and physical layer signaling (e.g., Downlink Control Information (DCI)).

[0022] The UE receives the path loss (PL b,f,c (q d ), P.L. b,f,c )(index q d The UL signal transmit power (e.g., transmit power of PUSCH / PUCCH / SRS / PRACH) for a reception point that does not transmit downlink data may be calculated using the active UL BWP b of carrier f of serving cell c using the path loss for b.

[0023] <Option 1> The absolute path loss (PL) value [dB] for each RS index may be notified (transmitted) from the network to the UE. The UE may directly use the notified absolute path loss value to calculate the transmission power.

[0024] <Option 2> The network may notify (transmit) the relative path loss (delta PL, PL offset) value [dB] for each RS index to the UE. The UE may use the path loss value obtained by applying (adding or subtracting) the received delta PL value to the conventional path loss value estimated from the DL RS transmitted from the macro cell (macro BS / central TRP) for transmission power calculation.

[0025] The PL value / delta PL value in options 1 and 2 is q dThe PL value / delta PL value may be signaled / configured for each index of the RS / SSB / CSI-RS / SRS resource / SRS resource set. One or more RS indices and the PL value / delta PL value corresponding to each RS index may be signaled by DL signaling. The PL value / delta PL value may be interpreted as a PL parameter / delta PL parameter.

[0026] FIG. 3A is a diagram showing an example of the association between RS indexes and PL values. FIG. 3B is a diagram showing an example of the association between RS indexes and delta PL values. The association (correspondence) between RS indexes and PL values / delta PL values ​​is not limited to that shown in FIGS. 3A and 3B. For example, one RS index may correspond to multiple PL values / delta PL values. Note that a quantization table (range and step) for PL values / delta PL values ​​may be predefined in the specifications. The notified PL value / delta PL value may be a quantized value or an index of a quantized value.

[0027] Figure 4 shows an example of Option 1 in a high-density UL deployment. The UL reception point receives / measures the UL signal. If the DL transmission point (macro TRP / gNB) knows the transmit power of this UL signal, the DL transmission point can know the exact PL value of the UL reception point. In this case, the DL transmission point can notify the UE of the absolute PL value (X [dB]) of the UL reception point.

[0028] Figure 5 shows an example of Option 2 in a dense UL deployment. When both the DL transmission point (macro TRP / gNB) and the UL reception point measure the same resource, the DL transmission point can recognize the difference between the PL between the DL transmission point and the UE and the PL between the UL reception point and the UE. In this case, the DL transmission point may notify the UE of the difference (relative PL / delta PL). The relative PL / delta PL may also be referred to as a PL offset.

[0029] As described above, even if the UE is not notified of the DL RS (RS index) used for path loss estimation, the UE can calculate the transmission power using the notified PL value / delta PL value.

[0030] (Timing Advance) Timing Advance (TA) is used for UL timing adjustment. In the existing specification (Rel. 17), the UL frame number i for transmission from the UE is a specific time (e.g., T TA ) before

[0031] The specific time is, for example, T TA =(N TA +N TA,offset +N common TA,adj +N UE TA,adj )T C N common TA,adj and N UE TA,adj may be 0 regardless of the examples of this disclosure when used in an NTN (non-terrestrial network).

[0032] where N TA is the timing advance between DL and UL, TA,offset defines a fixed offset used in calculating the timing advance, N common TA,adj is the network-controlled timing correction, N UE TA,adj is the UE-derived timing correction, T C may denote the Basic time unit for NR, respectively.

[0033] For example, in the random access preamble transmission and the message A PUSCH transmission, N TAis 0 and N TA,offset applies.

[0034] (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. The multiple TRPs may include DL transmission points and UL reception points. In this case, it is assumed that the distances between each TRP and the UE may be different.

[0035] 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 an UL channel / signal from different user terminals (UE) is adjusted by a radio base station (TRP: Transmission and Reception Point, also known as gNodeB (gNB)).

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

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

[0038] When multiple timing advance is applied, the UE independently adjusts the transmission timing of cells belonging to each TAG, allowing the radio base station to synchronize the reception timing of uplink signals from the UE even when multiple cells are used.

[0039] 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 an 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). The maximum number of TAGs may be X (e.g., X=4) per cell group (e.g., MCG / SCG).

[0040] Existing systems (e.g., Rel. 16 NR) support the configuration of up to four TAGs per cell group (e.g., MCG / SCG) (see Figure 6). Figure 6 shows a case where three TAGs are configured for a cell group including SpCell and SCells #1 to #4. Here, the case is shown where 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).

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

[0042] 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. 7A). The MAC CE may be configured by one octet (=8 bits).

[0043] The TAG ID field may consist of, 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 consist of, 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. A (0, 1, 2, . . . 63). The MAC CE for the timing advance command shown in FIG. 7A may be called a TAC MAC CE.

[0044] FIG. 7B is a diagram showing another example of a MAC CE for a timing advance command. The MAC CE shown in FIG. 7B may be called 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. 7B may indicate an index value used to control the amount / value (absolute amount / value) of the actual TA that the MAC entity must apply, as in FIG. 7A. Furthermore, the absolute TAC MAC CE may not include the TAG ID field shown in FIG. 7A.

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

[0046] The parameters corresponding to each TAG ID may be set by a higher layer parameter. 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 a higher layer parameter (e.g., tag-ID included in ServingCellConfig). Note that after being set by the higher layer parameter, the TAG ID / parameter may be updated by the MAC CE.

[0047] A time alignment timer may be maintained for UL time alignment. In Rel. 17, a 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.

[0048] The MAC entity receives the TAC MAC CE and determines whether the TAG is equal to or smaller than the predetermined value (N TA ) is maintained, apply a timing advance command for the indicated TAG or start or restart the time alignment timer associated with the indicated TAG. TA) may be the timing advance between DL and UL.

[0049] The behavior when the time alignment timer expires may be defined separately for PTAG and STAG. Note that the timing advance group (TAG) that includes 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 (STAG).

[0050] For example, in Rel. 17, it is supported that when the timing advance timer corresponding to a PTAG expires, a specified PTAG operation is applied, and when the timing advance timer corresponding to a STAG expires, a specified STAG operation is applied.

[0051] For example, when the time alignment timer expires, the following operations (for example, a predetermined PTAG operation / a predetermined STAG operation) may be performed.

[0052] [Prescribed PTAG Action] If a time alignment timer is associated with the PTAG, ·Flush all HARQ buffers in all serving cells. If configured, notify RRC to release PUCCH for all serving cells. If configured, notify RRC to release SRS. Clear all configured DL allocations and configured UL allocations. Clear PUSCH resources for semi-persistent CSI reporting. - Complete all time alignment timers while running. All TAG N TA Maintain.

[0053] [Prescribed STAG Action] If a time alignment timer is associated with a STAG, for all serving cells belonging to that STAG: Flush all HARQ buffers. If configured, notify RRC to release PUCCH. If configured, notify RRC to release SRS. Clear all configured DL and UL allocations. Clear PUSCH resources for semi-persistent CSI reporting. N of the TAG TA Maintain.

[0054] (analysis) ((Analysis 0)) As mentioned above, in order to expand UL coverage, the installation of UL receiving points in addition to general transmitting and receiving points is being considered. Also, heterogeneous networks (HetNets) using macro base stations (BSs) (DL TRPs) and micro BSs (UL TRPs) are being considered.

[0055] For example, in asymmetric HetNets in Rel. 19 and later, it is possible to support separate (independent) configuration of a path loss offset configuration (PL-offset configuration), multiple (e.g., two) CL-PCs for SRS, and multiple (e.g., two) timing advances (TAs). In this case, the issue is how to configure / control the relationship between these parameters (e.g., the relationship between the path loss offset configuration and the timing advance (e.g., the timing advance offset (n-TimingAdvanceoffset))).

[0056] ((Analysis 1)) In addition, even if the UE supports two TAs, it is not clear in what cases two TAs are supported, i.e., it is necessary to clarify the use cases / scenarios in which two TAs are supported.

[0057] As such, it is unclear how to determine the timing advance (TA) for the UL reception point (or micro BS) when the UE performs UL transmission, or what the use cases are. If the TA cannot be determined correctly, the UE may not be able to properly control the timing of UL transmission depending on the use case.

[0058] As a result, the base station may not be able to receive the UL transmission in a timely manner, which may affect communication quality / throughput.

[0059] Therefore, the present inventors have studied a method for appropriately controlling the timing of UL transmission and have come up with the idea for this embodiment.

[0060] Hereinafter, embodiments according to the present disclosure will be described in detail with reference to the drawings. Wireless communication methods according to the respective embodiments may be applied independently or in combination. The present disclosure also provides embodiments in which part or all of one embodiment is combined with part or all of another embodiment.

[0061] (Various reading changes) In this disclosure, words enclosed in "()" in a sentence may indicate an explanation of the immediately preceding wording (for example, an explanation of spelling), a paraphrase, a specific example, a supplementary explanation, etc. Also, in this disclosure, words enclosed in "[ ]" in a sentence may be interpreted including the meaning of the entire sentence, or may be interpreted excluding the meaning of the entire sentence (ignoring the meaning of the entire sentence). Note that "()" and "[ ]" may also be used for purposes / meanings other than those mentioned above.

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

[0063] In the present disclosure, terms such as notify, activate, deactivate, indicate (or indicate), select, configure, update, and determine may be interchangeable. In the present disclosure, terms such as support, control, controllable, operate, and operate may be interchangeable.

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

[0065] In the present disclosure, signaling, message, field, parameter, information, payload, etc. may be read interchangeably.

[0066] In the present disclosure, higher layer signaling may be, for example, any one of Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information, Non-Access Stratum (NAS) signaling (of the control plane), other messages (e.g., messages communicated to and from the core network, such as positioning protocol (e.g., NR Positioning Protocol A (NRPPa) / LTE Positioning Protocol (LPP)) messages), or a combination thereof.

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

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

[0069] In this disclosure, the terms index, identifier (ID), indicator, resource ID, etc. may be interchangeable. In this disclosure, the terms sequence, list, set, group, cluster, subset, etc. may be interchangeable.

[0070] In the present disclosure, a single DCI, a single PDCCH, multiple TRPs based on a single DCI, activating two TCI states on at least one TCI code point, mapping at least one code point of a TCI field to two TCI states, and setting a specific index (e.g., a TRP index, a CORESET pool index, or an index corresponding to a TRP) for a specific channel / CORESET may be read as interchangeable.

[0071] In the present disclosure, multi-TRP, channel / signal using multi-TRP, channel using multiple TCI states / spatial relationships, multi-TRP enabled by RRC / DCI, multiple TCI states / spatial relationships enabled by RRC / DCI, and at least one of multi-TRP based on a single DCI and multi-TRP based on multiple DCI may be read as interchangeable.

[0072] In the present disclosure, multiple TRPs based on multiple DCIs, setting one CORESET pool index (CORESETPoolIndex) value for a CORESET, and setting multiple specific indexes (e.g., TRP indexes, CORESET pool indexes, or indexes corresponding to TRPs) for a specific channel / CORESET may be read interchangeably.

[0073] In the present disclosure, TRP#1 (first TRP) may correspond to CORESET pool index=0 (first CORESET) or may correspond to the first TCI state of two TCI states corresponding to one code point in the TCI field. TRP#2 (second TRP) may correspond to CORESET pool index=1 (second CORESET) or may correspond to the second TCI state of two TCI states corresponding to one code point in the TCI field. The first TRP or second TRP may be a DL transmission point or a UL reception point.

[0074] In the present disclosure, single DCI (sDCI), single PDCCH, multi-TRP system based on single DCI, sDCI-based MTRP, and activation of two TCI states on at least one TCI codepoint may be read interchangeably.

[0075] In the present disclosure, multi-DCI (mDCI), multi-PDCCH, multi-TRP system based on multi-DCI, mDCI-based MTRP, and setting two CORESET pool indices or CORESET pool index=1 (or a value greater than or equal to 1) may be read interchangeably.

[0076] In the present disclosure, the terms TRP, base station, gNB, and network (NW) may be interchangeable. In the present disclosure, the terms TRP, RS group, antenna port group, and control resource set (CORESET) group may be interchangeable.

[0077] The UL reception point may be connected to a TRP (e.g., a base station) or a core network via wired or wireless connections. The UL reception point may be treated as a network (NW) or a base station. The UL reception point may be capable of transmitting downlink (DL) signals and may be applied to a base station forming a macrocell. For example, the UL reception point may not transmit downlink data but may transmit control signals / channels.

[0078] In the present disclosure, UL high density deployment, distributed TRP mode, separated location mode of transmitting / receiving points, distributed transmitting / receiving mode, separated TRP mode, TRP type 1, TRP type 2, TRP type A, and TRP type B may be read as interchangeable.

[0079] In the present disclosure, the SRS may be at least one of an aperiodic (A)-SRS, a periodic (P)-SRS, and a semi-persistent (SP)-SRS.

[0080] In the present disclosure, the path loss reference RS, the path loss reference RS for PUSCH, the path loss reference RS for PUCCH, the path loss reference RS for SRS, SSB, CSI-RS, and RS may be interpreted as interchangeable.

[0081] In the present disclosure, the terms path loss (PL), path loss value, and path loss parameter may be interpreted as interchangeable.

[0082] In this disclosure, the terms base station, UL receiving point, UL TRP, UL only TRP, and micro BS may be interchangeable. An UL receiving point may perform only UL reception, or may perform DL transmission if certain conditions are met.

[0083] In this disclosure, the terms base station, DL transmission point, DL TRP, DL only TRP, macro BS, and central TRP may be interchangeable. A DL transmission point may only perform DL transmission, or may perform UL reception if certain conditions are met.

[0084] In the present disclosure, TA and TAG may be interchangeable, and DL reference timing and DL reception timing may be interchangeable.

[0085] In the present disclosure, at least one of M-TRP of M-DCI, multi-TRP of S-DCI, and the above scenario 1 or scenario 2 may be assumed.

[0086] (Wireless communication method) The embodiments of the present disclosure relate to UL transmissions in which two TAs are supported and can be broadly categorized as follows: · 0th embodiment: Provisions for supporting two TAs. First embodiment: Use case / scenario where two TAs are supported.

[0087] Each embodiment will be described below based on these. Each embodiment / option may be applied alone or in combination.

[0088] The UE / NW (gNB) may perform UL transmission (UL reception) applying one / two TAs and various related operations (measurement / prediction / reporting / transmission / reception) by applying the various provisions described above and the embodiments described below.

[0089] The UE may receive various settings / responses (from the NW) for the UL transmission, and may also transmit various requests / reports for the UL transmission to the NW.

[0090] The NW (gNB) may transmit various settings for the UL transmission to the UE, receive corresponding requests / reports from the terminal, and transmit responses to the requests / reports to the UE.

[0091] The UE / NW may control various operations related to the UL transmission (transmission and reception of related information) by applying the embodiments of the present disclosure and the various provisions described above. Furthermore, the UE / NW may execute information exchange among multiple entities to realize these various operations.

[0092] According to the embodiments of the present disclosure, various rules for supporting two TAs and use cases / scenarios in which two TAs are supported are clarified. Based on the rules, the UE is able to appropriately control the timing of UL transmission according to a specific use case. The NW is able to receive the UL transmission at an appropriate timing. As a result, Improved communication throughput and quality can be expected.

[0093] <0th embodiment> The 0th embodiment relates to the provisions for supporting two TAs.

[0094] In an asymmetric TRP (e.g., asymmetric DL sTRP / UL mTRP) scenario, scenario A (see Figure 8) is assumed in which two timing advances (2TA) are supported. In scenario A, the following configurations may be applied / supported: 2TA may be two TA without coresetPoolIndex. Without coresetPoolIndex may mean that no coresetPoolIndex is provided or no coresetPoolIndex with value 1 is provided for the second CORESETs.

[0095] <Scenario A Settings> The requirement to set coresetPoolIndex may be removed. One DL reference timing may be supported and applied to both Timing Advance Groups (TAGs). One timing advance offset (e.g., one single n-TimingAdvanceoffset) may be configured and applied to both TAGs. Any TCI state may be associated with either of two TAGs.

[0096] In the scenario shown in Figure 8 (Scenario A), if it is assumed (or assumed) that only the DL TRP can transmit DL signals, a single timing advance offset (single n-TimingAdvanceOffset) may be assumed, in which case a single timing advance offset may be applied to both TAGs.

[0097] In the above-mentioned scenario A (or in addition to / instead of scenario A), at least one of scenario B1 and scenario B2 may be considered. Scenario B1 / Scenario B2 may be classified according to whether a PL offset is configured (or whether the UL TRP can transmit a DL signal (e.g., SSB)) (see FIGS. 9A and 9B). Scenarios B1 / B2 may be referred to as conditions B1 / B2 or cases B1 / B2.

[0098] In the present disclosure, the PL offset setting may be set in at least one TCI state (eg, joint / UL TCI state) in a certain BWP / CC.

[0099] When a PL offset is configured (Scenario B1), the UL TRP may be configured not to transmit SSB (see Figure 9A). This is because if the UL TRP transmits SSB, there will be no use case for the PL offset. The UE may assume / expect that no DL signal (e.g., SSB) will be transmitted from the UL TRP.

[0100] If no PL offset is configured (Scenario B2), the UL TRP may or may not transmit SSB (see FIG. 9B), since the UL TRP functions as a normal UL TRP. The UE may assume / expect that a DL signal (e.g., SSB) may be transmitted from the UL TRP.

[0101] From the UE perspective, the UE may not expect to receive SSB from the UL TRP if the PL offset is configured in the joint / UL TCI state, and may expect to receive SSB from the UL TRP otherwise.

[0102] In an asymmetric HetNet (e.g., the above-mentioned scenarios A / B1 / B2), the PL-offset configuration, multiple (e.g., two) CL-PCs for SRS, and multiple (e.g., two) timing advances (TAs) may be configured separately (or independently). In an asymmetric HetNet, the configuration / application of a single timing advance offset (TA offset) may be controlled based on the PL offset configuration (or whether or not it is configured). For example, if a PL offset is not configured, the restriction / configuration of a single timing advance offset (single n-TimingAdvanceoffset) may not be necessary. This makes it possible to configure / apply a (suitable) timing advance offset (or the number of timing advance offsets) corresponding to the applied scenario.

[0103] [Case 1-1] If the PL offset is configured in any of the TCI states in the BWP / CC (e.g., when scenario B1 / condition B1 applies), the configuration of scenario A may be applied. For example, if the PL offset is configured (e.g., when the UL TRP does not transmit SSB), a single timing advance offset (single n-TimingAdvanceoffset) may be configured / applied (see FIG. 10A).

[0104] In this case, a single configured timing advance offset may be applied to multiple / all (e.g., two) timing advance groups (TAGs), and one DL reference timing may be supported and applied to multiple / all (e.g., two) timing advance groups (TAGs).

[0105] When Case 1-1 is applied (a PL offset is configured), the UE may assume / expect that no DL signal (e.g., SSB) will be transmitted from the UL TRP. In this case, the UE may control UL transmission (e.g., determine UL transmit power based on the PL offset and determine timing advance based on the TA offset) based on configuration information transmitted from the DL TRP. The configuration information transmitted from the DL TRP may include at least one of information on the PL offset and information on the TA offset. This allows the UE to set / apply a (suitable) timing advance offset (or timing advance offset number) corresponding to the applicable scenario.

[0106] [Case 1-2] In other cases (for example, when the PL offset is not set (for example, when scenario B2 / condition B2 applies)), either or both of the following settings 1-1 and 1-2 may be applied (see Figure 10B).

[0107] Setting 1-1: Multiple (e.g., two) timing advance offsets may be set and applied to each timing advance group (TAG). · Configuration 1-2: Multiple DL reference timings are supported and may be applied to each Timing Advance Group (TAG).

[0108] When Case 1-2 is applied (PL offset is not configured), the UE may assume / expect that DL signals (e.g., SSB) can be transmitted from the UL TRP. In this case, the UE may control UL transmission based on multiple (e.g., two) TA offsets / DL reference timings. This allows the UE to configure / apply a (suitable) timing advance offset (or number of timing advance offsets) corresponding to the applied scenario.

[0109] [Variation 1] In other cases (Case 1-2), at least one of two TAs without coresetPoolIndex and two closed-loop power controls for SRS (two CL-PC for SRS) may be configured. For example, even if a PL offset is configured, at least one of Configuration 1-1 and Configuration 1-2 may be applied if at least one of two TAs without coresetPoolIndex and two closed-loop power controls for SRS are configured.

[0110] In this case, case 1-1 may be a case where two TAs without coresetPoolIndex and two closed-loop power controls for SRS are not set and a PL offset is set.

[0111] [Variation 2] Up to two (or a maximum of two) TA offsets (n-TimingAdvanceoffset) (or up to two TA offsets / DL reference timings) may be configured, and up to two (or a maximum of two) DL reference timings may be applied. In this case, whether to configure one or more (e.g., two) TA timing offsets for the UE depends on the network (e.g., base station), and whether to apply one or more (e.g., two) DL reference timings depends on the network, and may be configurable for the UE by the network.

[0112] For example, in a scenario where multiple (e.g., two) TAs are supported, multiple (e.g., two) TA offsets may be configured only for inter-cell mTRPs, and a single TA offset may be configured only for intra-cell mTRPs.

[0113] [Variation 3] Multiple (e.g., two) TA offsets (n-TimingAdvanceoffset without coresetPoolIndex) may be configured only for inter-cell mTRPs. A single TA offset may be configured for intra-cell mTRPs.

[0114] Note that the inter-cell multi-TRP may correspond to a case where an additional PCI is set, and the intra-cell multi-TRP may correspond to a case where an additional PCI is not set.

[0115] [UE ability] As UE capabilities, separate UE capabilities and common UE capabilities may be introduced.

[0116] Separate UE Ability Separate UE capabilities may be defined to report UE capabilities regarding the number of supported (or applicable) TA offsets, for example, whether a UE supports one TA offset, multiple (e.g., two) TA offsets, or both (e.g., {"single n-TimingAdvanceoffset", "two n-TimingAdvanceoffset", "both"}).

[0117] Separate UE capabilities may be defined to report UE capabilities regarding the number of supported (or applicable) DL reference timings, for example, whether a UE supports one DL reference timing, multiple (e.g., two) DL reference timings, or both (e.g., {"one downlink reference timing", "two downlink reference timing", "both"}).

[0118] The UE capability for TA offset and the UE capability for DL ​​reference timing may be reported by common or different UE capabilities.

[0119] Common UE Ability A common UE capability may be defined to report common UE capabilities regarding the number of supported (or applicable) TA offsets, for example, a report may indicate support for one TA offset, multiple (e.g., two) TA offsets, or both (e.g., {"single n-TimingAdvanceoffset", "two n-TimingAdvanceoffset", "both"}).

[0120] Separate UE capabilities may be defined to report UE capabilities regarding the number of supported (or applicable) DL reference timings, for example, a report may indicate support for one DL reference timing, multiple (e.g., two) DL reference timings, or both (e.g., {"one downlink reference timing", "two downlink reference timing", "both"}).

[0121] The UE capability for TA offset and the UE capability for DL ​​reference timing may be reported by common or different UE capabilities.

[0122] [RRC parameters] <<Separate Settings>> An RRC parameter may be introduced to set (or separately set) one TA offset, multiple (e.g., two) TA offsets, or both (e.g., {"single n-TimingAdvanceoffset", "two n-TimingAdvanceoffset", "both"}).

[0123] An RRC parameter may be introduced to set (or separately set) one DL reference timing, multiple (e.g., two) DL reference timings, or both (e.g., {"one downlink reference timing", "two downlink reference timing", "both"}).

[0124] The RRC parameter related to the TA offset and the RRC parameter related to the DL reference timing may be configured by common or different RRC parameters.

[0125] <<Non-separate setting>> An RRC parameter for configuring any one of the TA offsets / an RRC parameter for configuring any one of the DL reference timings may not be introduced (is unnecessary). One or more (e.g., two) TA offsets (n-TimingAdvanceoffset) / DL reference timings may be distinguished by a combination of other RRC parameters (e.g., RRC parameters related to the PL offset) and the RRC parameters related to the TA offset / RRC parameters related to the DL reference timing. As an example, when the UE receives an RRC parameter related to the PL offset (e.g., an RRC parameter for setting the PL offset) and the RRC parameters related to the TA offset / RRC parameters related to the DL reference timing, the UE may be controlled to apply one TA offset / DL reference timing.

[0126] In an embodiment, when a PL offset is set in any of the TCI states in the BWP / CC (e.g., in case 1-1), the UL reception point (UL Rx point) may refer to a UL reception-only point that does not transmit DL signals (e.g., SSB). In other cases (e.g., in case 1-2), the UL reception point (UL Rx point) may refer to a UL reception point that is also capable / supports transmission of DL signals (e.g., SSB).

[0127] According to this embodiment, the regulations for supporting two TAs are clarified. As a result, the UE can appropriately control UL transmissions applying two TAs.

[0128] <First Embodiment> The first embodiment relates to use cases / scenarios where two TAs are supported.

[0129] The UE may adjust the timing of [UL] transmissions according to the following regulations (Embodiments 1-1 to 1-3, etc.).

[0130] <<Embodiment 1-0>> The UE may be provided with the value (N TA,offset ) of the timing advance offset of the serving cell by a specific parameter (related to the timing advance offset) for one serving cell (n-TimingAdvanceOffset).

[0131] <<<Case where two CORESETs are configured (two N TA,offset values are configured)>>> In the serving cell, when the UE is provided with two CORESET pool index values 0, 1 for the first CORESET and the second CORESET, or when no CORESET pool index value is provided for the first CORESET and the CORESET pool index value 1 is provided for the second CORESET, for transmissions using the first spatial filter associated with the first TCI state corresponding to the first CORESET and the second spatial filter associated with the second TCI state corresponding to the second CORESET, the first N TA,offset value and the second N TA,offset value may be provided by specific parameters (related to the timing advance offset) (n-TimingAdvanceOffset, n-TimingAdvanceOffset2).

[0132] <<<Case where no CORESET is configured (one NTA,offset Case where a value is set >>> When the UE performs an operation with two tags in one serving cell and no CORESET pool index is provided, for transmission using the first spatial filter associated with the first TCI state and the second spatial filter associated with the second TCI state corresponding to the second CORESET, the UE uses a specific (parameter regarding timing advance offset) parameter (n-TimingAdvanceOffset) to obtain one N TA,offset value may be provided.

[0133] The two TCI states (joint / ULTCI state) may be provided by a parameter (dl-OrJointTCI-StateList or ul-TCI-State-List) regarding the TCI state list.

[0134] <<<Case where no TCI state is set for SRS>>> When the UE performs an operation with two tags in one serving cell and no parameter (followUnifiedTCI-StateSRS) regarding the unified TCI state is provided for one SRS resource set, the TAG may be provided by a parameter (tag-Id-ptr) regarding the TAG.

[0135] The parameter (tag-Id-ptr) regarding the TAG may be associated with the TCI state (TCI-State) or UL TCI state (TCI-UL-State) of the SRS resource having the lowest SRS resource ID within one SRS resource set.

[0136] <<<Case where two N TA,offset values are set >>> For transmission using the first spatial filter corresponding to the first TCI state associated with the PCI of the serving cell or the first SS / PBCH block reception, the UE uses the first N TA,offsetIn addition to being provided with a second N value, a second N value may be provided for transmission using a second spatial filter corresponding to a second TCI state or second SS / PBCH block reception associated with a PCI (physCellId) different from the PCI of the serving cell. TA,offset A value may be provided.

[0137] 1st / 2nd N TA,offset The values ​​correspond to the 1st / 2nd TAG indicated in the MAC RAR / Absolute TAC MAC CE respectively and have an association indicated by tag-Id-ptr corresponding to the 1st / 2nd joint TCI state provided by dl-OrJointTCI-StateList or the 1st / 2nd UL TCI state provided by ul-TCI-State-List.

[0138] <<<Others>>> If the UE is not provided with n-TimingAdvanceOffset for one serving cell, the UE shall use the default value N of the timing advance offset of the serving cell. TA,offset Determine.

[0139] If a UE is configured with two UL carriers for one serving cell, then for transmissions in serving cells associated with the same TAG, the same timing advance offset value N shall be used for both carriers. TA,offset The UE uses two N TA,offset It does not expect values ​​to be applied.

[0140] <<<Scenarios in which two TAs are supported>>> Two TAs are supported (e.g., two N TA,offset The cases in which the value is set / provided may be limited to, for example, at least one of the following. That is, the UE may support UL transmission with two TAs in at least one of the following use cases / scenarios. Fig. 11 is a diagram showing an example of UE operation when supporting two TAs according to the first embodiment.

[0141] (Scenario A) Intra-cell scenario with PL offset. In this scenario, the UL TRP does not need to transmit the SSB.

[0142] (Scenario B) Inter-cell scenario without PL offset. In this scenario, the UL TRP may transmit the SSB.

[0143] The UE may execute / support the control of UL transmission applying two TAs only when provided with the settings related to the above-described Scenario A / B or when reporting the corresponding capability information (see Figure 11).

[0144] In other words, the UE does not need to execute / support the control of UL transmission applying two TAs when not provided with the settings related to the above-described Scenario A / B or when not reporting / supporting the corresponding capability information.

[0145] That is, the UE may determine whether to support UL transmission applying two TAs based on whether the above-described Scenario A / B is set / supported.

[0146] In the following Embodiments 1-1 to 1-3, specific examples where Scenario A / B is set / supported are listed. Each embodiment can be arbitrarily combined.

[0147] <<Embodiment 1-1>> <<<Case where CORESET is not set (one N TA,offset value is set)>>> When a UE operates with two TAGs in a serving cell, and a CORESET pool index is not provided, and a PL offset (pl-Offset) is provided in any TCI state (TCI-State or TCI-UL-State) in the serving cell, the UE shall select one N spatial filter (pl-Offset) for transmission using a first spatial filter associated with a first TCI state and a second spatial filter associated with a second TCI state corresponding to a second CORESET, using a specific parameter (n-TimingAdvanceOffset) (related to the timing advance offset). TA,offset A value may be provided.

[0148] That is, in embodiment 1-1, providing a PL offset in the serving cell may mean that two TAs are not supported.

[0149] <<<Two N TA,offset Cases where values ​​are set>>> If no PL offset is provided in any TCI state (TCI-State or TCI-UL-State) in the serving cell, the UE may select the first N spatial filters for transmission using the first TCI state associated with the PCI of the serving cell or the first SS / PBCH block reception. TA,offset In addition to being provided with a second N value, a second N value may be provided for transmission using a second spatial filter corresponding to a second TCI state or second SS / PBCH block reception associated with a PCI (physCellId) different from the PCI of the serving cell. TA,offset A value may be provided.

[0150] 1st / 2nd N TA,offset The values ​​correspond to the 1st / 2nd TAG indicated in the MAC RAR / Absolute TAC MAC CE respectively and have an association indicated by tag-Id-ptr corresponding to the 1st / 2nd joint TCI state provided by dl-OrJointTCI-StateList or the 1st / 2nd UL TCI state provided by ul-TCI-State-List.

[0151] That is, in Embodiment 1-1, the fact that no PL offset is provided in the serving cell may mean that two TAs are supported.

[0152] Thus, in Embodiment 1-1, the UE may determine the number of TAs to be applied based on whether the PL offset is set in any transmission configuration indication (TCI) state within the serving cell.

[0153] <<Embodiment 1-2>> <<<Case where no CORESET is set (two N TA,offset values are set)>>> When the UE performs operations with two TAGs in one serving cell, and no CORESET pool index is provided, and no PL offset is provided in any TCI state (TCI-State or TCI-UL-State) within the serving cell, the UE may use specific (parameters related to timing advance offset) parameters (n-TimingAdvanceOffset, n-TimingAdvanceOffset2) to provide the first N TA,offset value and the second N TA,offset value.

[0154] In Embodiment 1-2, the fact that no CORESET index and no PL offset are provided in the serving cell may mean that two TAs are supported.

[0155] <<Embodiment 1-3>> <<<Case where two CORESETs are set (two N TA,offset values are set)>>> In the serving cell, when the UE is provided with two CORESET pool index values ​​of 0 and 1 for the first CORESET and the second CORESET, or when no CORESET pool index value is provided for the first CORESET and a CORESET pool index value of 1 is provided for the second CORESET, the UE may select a first N spatial filter for transmission using a first TCI state or a first SS / PBCH block reception associated with the PCI of the serving cell. TA,offset In addition to being provided with a second N value, a second N value may be provided for transmission using a second spatial filter corresponding to a second TCI state or second SS / PBCH block reception associated with a PCI (physCellId) different from the PCI of the serving cell. TA,offset A value may be provided.

[0156] That is, in embodiments 1-3, providing a CORESET pool index value of 1 for the second CORESET may mean that two TAs are supported.

[0157] <<<One N TA,offset Cases where values ​​are set>>> If no PL offset is provided in an inter-cell scenario, one N TA,offset A value may be provided.

[0158] For example, when a UE operates with two TAGs in a serving cell and no PL offset (pl-Offset) is provided in any TCI state (TCI-State or TCI-UL-State) in the serving cell, the UE may use a specific parameter (related to timing advance offset) (n-TimingAdvanceOffset) to provide one N spatial filter for transmission using a first spatial filter associated with a first TCI state and a second spatial filter associated with a second TCI state corresponding to a second CORESET. TA,offset A value may be provided.

[0159] <<Others>> In the present disclosure, not supporting two TAs may mean supporting only one TA.

[0160] In the present disclosure, supporting two TAs may mean that the above-described scenario A / B is set / supported.

[0161] In the present disclosure, providing a PL offset in any TCI state within a serving cell may mean that no additional cell is set or that two TAs are not supported.

[0162] In the present disclosure, not providing a PL offset in any TCI state within a serving cell may mean that an additional cell is set or that two TAs are supported.

[0163] According to this embodiment, the use cases / scenarios in which two TAs are supported are clarified. As a result, the UE can appropriately control UL transmissions applying two TAs according to the use case / scenario.

[0164] <Supplementary> <<Notification of Information to UE / BS>> Notification of any information from a [Network (NW) (e.g., Base Station (BS)) / NW node] to the UE / BS in the above-described embodiment (in other words, reception of any information from the BS / NW node at the UE / BS) may be performed using physical layer signaling (e.g., DCI), upper layer signaling (e.g., RRC signaling, MAC CE, NAS signaling, LPP message, NRPPa message), a specific signal / channel (e.g., PDCCH, PDSCH, reference signal), or a combination thereof.

[0165] When the above notification is performed by a MAC CE, the MAC CE may be identified by including a new logical channel ID (LCID) not defined in the existing standard in the MAC sub-header.

[0166] When the above notification is performed by DCI, the above notification may be performed by a specific field of the DCI, a radio network temporary identifier (RNTI) used for scrambling cyclic redundancy check (CRC) bits assigned to the DCI, the format of the DCI, etc.

[0167] Also, the notification of any information to the UE / BS in the above embodiments may be performed periodically, semi-persistently, or aperiodically. The notification of semi-persistent or aperiodic information may be triggered by an instruction from the UE / BS / NW.

[0168] In the above embodiments, the information from the NW may be set / instructed by any one or a combination of the following methods: · Common to multiple UEs or individual to each UE, · Common to multiple BSs or individual to each BS, · Common to a plurality of frequencies (for example, one or a combination of a cell, a band, a band combination, a bandwidth part (BWP), a component carrier, etc.) (for example, cell common) or frequency specific (for each frequency, for example, for each cell).

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

[0170] When the notification is performed by a MAC CE, the MAC CE may be identified by including a new LCID in the MAC subheader that is not defined in existing standards.

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

[0172] In addition, any information notification from the UE / BS in the above-mentioned embodiments may be performed periodically, semi-persistently, or aperiodically. Notification of semi-persistent or aperiodic information may be triggered by an instruction from the UE / BS / NW.

[0173] <<Application of each embodiment>> In a UE / BS, a specific (e.g., one or more, or part of) process / operation / control / assumption / information of at least one of the above-described embodiments may be applied (used) when one or more of the following conditions are met: Upper layer parameters indicating the above specific processing / operation / control / assumment / information are set in the UE / BS; The specific processing / operation / control / assumption / information is determined in the UE / BS based on relevant higher layer parameters; The above specific process / operation / control / assumption / information is specified / activated / triggered for the UE / BS by the MAC CE / DCI / UCI / resource / channel / RS, The UE / BS reports or supports specific capabilities (e.g., UE capabilities) that indicate (or relate to) the specific processing / action / control / assumptions / information. The application of the above specific processing / operation / control / assumption / information is determined in the UE / BS based on specific conditions.

[0174] The specified capabilities may indicate at least one of the following: Supporting the above specific processes / actions / controls / assumptions / information; Supporting two TAs, Support scenarios A / B.

[0175] In the present disclosure, "supporting" and "whether to support" may be read interchangeably.

[0176] Furthermore, the above-mentioned specific capabilities may be capabilities that are applied across all frequencies (commonly regardless of frequency), capabilities for each frequency (e.g., one or a combination of a cell, band, band combination, BWP, component carrier, etc.), capabilities for each frequency range (e.g., Frequency Range 1 (FR1), FR2, FR3, FR4, FR5, FR2-1, FR2-2), capabilities for each subcarrier spacing (SubCarrier Spacing (SCS)), or capabilities for each Feature Set (FS) or Feature Set Per Component-carrier (FSPC).

[0177] Furthermore, the above-mentioned specific capabilities may be capabilities that are applied across all duplexing methods (commonly regardless of the duplexing method), or may be capabilities for each duplexing method (for example, Time Division Duplex (TDD) or Frequency Division Duplex (FDD)).

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

[0179] (Addendum) The following inventions are added regarding one embodiment of the present disclosure. [Appendix 1] a receiver for receiving parameters relating to a timing advance offset and a configuration relating to a particular scenario in which two timing advances (TAs) are supported; a control unit that determines whether to support UL transmission applying two timing advances (TAs) based on whether a specific scenario in which the two TAs are supported is configured; The terminal, wherein the specific scenario is an intra-cell scenario with a path loss (PL) offset or an inter-cell scenario without a PL offset. [Appendix 2] The terminal according to Supplementary Note 1, wherein the control unit determines the number of TAs to apply based on whether the PL offset is configured in any transmission configuration indication (TCI) state in a serving cell. [Appendix 3] The terminal according to claim 1 or 2, wherein if a control resource set (CORESET) pool index is not provided and the PL offset is not provided in any transmission configuration indication (TCI) in a serving cell, the receiving unit receives two timing advance offset values. [Appendix 4] 4. The terminal of claim 1, wherein when a CORESET pool index value of 1 is provided for a second control resource set (CORESET), the receiving unit receives two timing advance offset values. [Appendix 5] receiving parameters for a timing advance offset and a configuration for a particular scenario in which two timing advances (TAs) are supported; determining whether to support UL transmission with two timing advances (TAs) based on whether a specific scenario in which two TAs are supported is configured; The wireless communication method for a terminal, wherein the specific scenario is an intra-cell scenario with a path loss (PL) offset or an inter-cell scenario without a PL offset. [Appendix 6] a transmitter for transmitting parameters relating to timing advance offsets and configurations relating to specific scenarios in which two timing advances (TAs) are supported; a control unit configured to control reception of an UL transmission to which two timing advances (TAs) are applied by a terminal based on whether a specific scenario in which the two TAs are supported is configured; The base station, wherein the particular scenario is an intra-cell scenario with a path loss (PL) offset or an inter-cell scenario without a PL offset.

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

[0181] 12 is a diagram illustrating an example of a schematic configuration of a wireless communication system according to an embodiment of the present disclosure. The wireless communication system 1 (which may be simply referred to as system 1) may be a system that realizes communication using Long Term Evolution (LTE), 5th generation mobile communication system New Radio (5G NR), or the like, which are specified by the Third Generation Partnership Project (3GPP).

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

[0183] In EN-DC, the LTE (E-UTRA) base station (eNB) is the master node (MN), and the NR base station (gNB) is the secondary node (SN). In NE-DC, the NR base station (gNB) is the MN, and the LTE (E-UTRA) base station (eNB) is the SN.

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

[0185] 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 arranged within the macrocell C1 and form small cells C2 that are smaller than the macrocell C1. A terminal 20 may be located within at least one of the cells. The arrangement, number, shape, size, etc. of each cell and terminal 20 are not limited to the embodiment shown in the figure. Hereinafter, when there is no need to distinguish between the base stations 11 and 12, they will be collectively referred to as base station 10.

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

[0187] The terminal 20 may be connected to at least one of the multiple base stations 10. The terminal 20 may use at least one of carrier aggregation (CA) using multiple component carriers (CC) and dual connectivity (DC).

[0188] Each CC may be included in at least one of a first frequency band (Frequency Range 1 (FR1)) and a second frequency band (Frequency Range 2 (FR2)). The macro cell C1 may be included in FR1, and the small cell C2 may be included in FR2. For example, FR1 may be a frequency band of 6 GHz or less (sub-6 GHz), and FR2 may be a frequency band above 24 GHz (above-24 GHz). Note that the frequency bands and definitions of FR1 and FR2 are not limited to these, and for example, FR1 may be a frequency band higher than FR2.

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

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

[0191] 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, 5GC), a Next Generation Core (NGC), and the like.

[0192] The core network 30 may include network functions (Network Functions (NFs)) such as a User Plane Function (UPF), an Access and Mobility management Function (AMF), a Session Management Function (SMF), a Unified Data Management (UDM), an Application Function (AF), a Data Network (DN), a Location Management Function (LMF), and Operation, Administration and Maintenance (Management) (OAM). Note that a single network node (which may simply be referred to as a node) may provide multiple functions. Furthermore, communication with an external network (e.g., the Internet) may be performed via the DN.

[0193] The terminal 20 may be a terminal compatible with at least one of communication methods such as LTE, LTE-A, and 5G.

[0194] An Orthogonal Frequency Division Multiplexing (OFDM)-based radio access scheme may be used in the radio communication system 1. For example, Cyclic Prefix OFDM (CP-OFDM), Discrete Fourier Transform Spread OFDM (DFT-s-OFDM), Orthogonal Frequency Division Multiple Access (OFDMA), Single Carrier Frequency Division Multiple Access (SC-FDMA), or the like may be used in at least one of the downlink (DL) and uplink (UL).

[0195] The radio access scheme may also be called a waveform. Note that in the wireless communication system 1, other radio access schemes (for example, other single-carrier transmission schemes, other multi-carrier transmission schemes) may be used as the UL and DL radio access schemes.

[0196] In the wireless communication system 1, a downlink shared channel (Physical Downlink Shared Channel (PDSCH)) shared by each 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.

[0197] In addition, in the wireless communication system 1, an uplink shared channel (Physical Uplink Shared Channel (PUSCH)) shared by each terminal 20, an uplink control channel (Physical Uplink Control Channel (PUCCH)), a random access channel (Physical Random Access Channel (PRACH)), etc. may be used as an uplink channel.

[0198] The PDSCH transmits user data, higher layer control information, System Information Block (SIB), etc. The PUSCH may transmit user data, higher layer control information, etc. Furthermore, the PBCH may transmit Master Information Block (MIB).

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

[0200] Note that the DCI for scheduling the PDSCH may be referred to as a DL assignment, a DL DCI, etc., and the DCI for scheduling the PUSCH may be referred to as an UL grant, a UL DCI, etc. Note that the PDSCH may be interpreted as DL data, and the PUSCH may be interpreted as UL data.

[0201] A control resource set (CORESET) and a search space may be used to detect the PDCCH. The CORESET corresponds to resources to search for DCI. The search space corresponds to a search region and a search method for PDCCH candidates. One CORESET may be associated with one or more search spaces. The UE may monitor a CORESET associated with a certain search space based on the search space configuration.

[0202] One search space may correspond to PDCCH candidates corresponding to one or more aggregation levels. One or more search spaces may be called a search space set. Note that the terms "search space," "search space set," "search space setting," "search space set setting," "CORESET," "CORESET setting," etc. in the present disclosure may be read interchangeably.

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

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

[0205] In the wireless communication system 1, a synchronization signal (SS), a downlink reference signal (DL-RS), etc. may be transmitted. In the wireless communication system 1, a cell-specific reference signal (CRS), a channel state information reference signal (CSI-RS), a demodulation reference signal (DMRS), a positioning reference signal (PRS), a phase tracking reference signal (PTRS), etc. may be transmitted as DL-RS.

[0206] The synchronization signal may be, for example, at least one of a Primary Synchronization Signal (PSS) and a Secondary Synchronization Signal (SSS). A signal block including the SS (PSS, SSS) and the PBCH (and DMRS for the PBCH) may be referred to as an SS / PBCH block, an SS Block (SSB), or the like. Note that the SS, SSB, and the like may also be referred to as reference signals.

[0207] Furthermore, in the wireless communication system 1, a sounding reference signal (SRS), a demodulation reference signal (DMRS), etc. may be transmitted as an uplink reference signal (UL-RS). Note that the DMRS may also be called a user equipment-specific reference signal (UE-specific reference signal).

[0208] (base station) 13 is a diagram illustrating an example of the configuration of a base station according to an embodiment of the present disclosure. 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.

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

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

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

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

[0213] The transmitting / receiving unit 120 may be configured as an integrated transmitting / receiving unit, or may be composed of a transmitting unit and a receiving unit. The transmitting unit may be composed of a transmission processing unit 1211 and an RF unit 122. The receiving unit may be composed of a reception processing unit 1212, an RF unit 122, and a measurement unit 123.

[0214] The transmitting and receiving antenna 130 can be configured from an antenna described based on common understanding in the technical field to which the present disclosure pertains, such as an array antenna.

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

[0216] The transceiver 120 may form at least one of a transmission beam and a reception beam using digital beamforming (for example, precoding), analog beamforming (for example, phase rotation), or the like.

[0217] The transceiver 120 (transmission processing unit 1211) may perform Packet Data Convergence Protocol (PDCP) layer processing, Radio Link Control (RLC) layer processing (e.g., RLC retransmission control), Medium Access Control (MAC) layer processing (e.g., HARQ retransmission control), etc. on data, control information, etc. obtained from the control unit 110, and generate a bit string to be transmitted.

[0218] The transceiver 120 (transmission processor 1211) may perform transmission processing such as channel coding (which may include error correction coding), modulation, mapping, filtering, Discrete Fourier Transform (DFT) processing (if necessary), Inverse Fast Fourier Transform (IFFT) processing, precoding, and digital-to-analog conversion on the bit string to be transmitted, and output a baseband signal.

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

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

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

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

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

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

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

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

[0227] The transmitting / receiving unit 120 and the control unit 110 may perform the operations described in the appendix.

[0228] Furthermore, in the present disclosure, a network device (for example, an LMF node) having the functionality of any of the above-described NFs may be a device having the configuration (for example, the control unit 110 and the transceiver unit 120) of the base station 10 in the same manner as in Fig. 13. In other words, in the description of Fig. 13, by replacing the base station with the network device, the configuration of the network device according to an embodiment of the present disclosure may be covered.

[0229] (Terminal) 14 is a diagram illustrating an example of the configuration of a terminal according to an embodiment of the present disclosure. The terminal 20 includes a control unit 210, a transceiver unit 220, and a transceiver antenna 230. Note that the terminal may include one or more of each of the control unit 210, the transceiver unit 220, and the transceiver antenna 230.

[0230] In this example, functional blocks of the characteristic parts of the present embodiment are mainly shown, and it may be assumed that the terminal 20 also has other functional blocks necessary for wireless communication. Some of the processing of each unit described below may be omitted.

[0231] The control unit 210 performs overall control of the terminal 20. The control unit 210 can be configured from a controller, a control circuit, and the like that are explained based on common understanding in the technical field to which the present disclosure relates.

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

[0233] The transceiver unit 220 may include a baseband unit 221, an RF unit 222, and a measurement unit 223. The baseband unit 221 may include a transmission processing unit 2211 and a reception processing unit 2212. The transceiver unit 220 may be configured from a transmitter / receiver, an RF circuit, a baseband circuit, a filter, a phase shifter, a measurement circuit, a transceiver circuit, etc., which are described based on common understanding in the technical field related to the present disclosure.

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

[0235] The transmitting / receiving antenna 230 can be configured as an antenna described based on common understanding in the technical field to which the present disclosure pertains, such as an array antenna.

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

[0237] The transceiver 220 may form at least one of a transmission beam and a reception beam using digital beamforming (for example, precoding), analog beamforming (for example, phase rotation), or the like.

[0238] The transceiver 220 (transmission processing unit 2211) may perform PDCP layer processing, RLC layer processing (e.g., RLC retransmission control), MAC layer processing (e.g., HARQ retransmission control), etc. on data, control information, etc. obtained from the control unit 210, and generate a bit string to be transmitted.

[0239] The transceiver 220 (transmission processor 2211) may perform transmission processing such as channel coding (which may include error correction coding), modulation, mapping, filtering, DFT processing (if necessary), IFFT processing, precoding, and digital-to-analog conversion on the bit string to be transmitted, and output a baseband signal.

[0240] Whether or not to apply DFT processing may be based on the setting of transform precoding. When transform precoding is enabled for a certain channel (e.g., PUSCH), the transceiver unit 220 (transmission processing unit 2211) may perform DFT processing as the transmission processing to transmit the channel using a DFT-s-OFDM waveform, and when transform precoding is not enabled, the transceiver unit 220 may not perform DFT processing as the transmission processing.

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

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

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

[0244] The transceiver 220 (measurement unit 223) may perform measurements on the received signal. For example, the measurement unit 223 may perform RRM measurement, CSI measurement, etc. based on the received signal. The measurement unit 223 may measure received power (e.g., RSRP), received quality (e.g., RSRQ, SINR, SNR), signal strength (e.g., RSSI), propagation path information (e.g., CSI), etc. The measurement results may be output to the control unit 210.

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

[0246] The transmitting section and receiving section of the terminal 20 in the present disclosure may be configured by at least one of the transmitting / receiving section 220 and the transmitting / receiving antenna 230.

[0247] The transmitting / receiving unit 220 and the control unit 210 may perform the operations described in the appendix.

[0248] (Hardware configuration) The block diagrams used to explain the above embodiments show functional blocks. These functional blocks (components) are realized by hardware, software, or a combination of these. Furthermore, the method of realizing each functional block is not particularly limited. That is, each functional block may be realized by using a single device that is physically or logically coupled, or may be realized by using two or more physically or logically separated devices that are connected directly or indirectly (for example, by wire, wirelessly, etc.) and these multiple devices. The functional block may also be realized by combining the single device or the multiple devices with software.

[0249] For example, a base station, a terminal, a network node, 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. 15 is a diagram illustrating an example of the hardware configuration of a base station and a terminal according to an embodiment of the present disclosure. The above-described base station 10 and 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.

[0250] In the present disclosure, any two terms selected from a set of terms such as apparatus, circuit, device, section, unit, module, chip, means, etc. may be read as interchangeable. The hardware configurations of the base station 10 and the 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.

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

[0252] 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. Although only one processor 1001 is shown in the figure, there may be multiple processors.

[0253] The processor 1001 also reads programs (program codes), software modules, data, etc. from the storage 1003, the communication device 1004, or both the storage 1003 and the communication device 1004 into the memory 1002, and executes various processes in accordance with these. The programs used are those that cause a computer to execute at least some of the operations described in the above-described embodiments. For example, the control unit 110 (210) may be realized by a control program stored in the memory 1002 and running on the processor 1001, and the other functional blocks may be realized in a similar manner.

[0254] The various processes described above may be performed by one processor 1001, or may be performed by two or more processors 1001 simultaneously, sequentially, or using other techniques. The processor 1001 may be implemented by one or more chips. The program may be transmitted from a network via a telecommunications line, or may be provided to the computer device via, for example, the communication device 1004.

[0255] The present disclosure also provides a computer program product including a computer program, which may implement the steps of the methods described in the above embodiments when the computer program is executed by a computer (e.g., the processor 1001).

[0256] The memory 1002 is a non-transitory computer-readable recording medium and may be configured, for example, by a read-only memory (ROM), an erasable programmable ROM (EPROM), an electrically EEPROM (EEPROM), a random access memory (RAM), or a combination of at least two of these. The memory 1002 may also be referred to as a register, a cache, a main memory, or the like. The memory 1002 may store executable programs (program codes), software modules, and the like for implementing a wireless communication method according to one embodiment of the present disclosure.

[0257] Storage 1003 is a non-transitory computer-readable recording medium, and may be, for example, a flexible disk, a floppy disk, an optical disk (e.g., a compact disc (e.g., a Compact Disc ROM (CD-ROM)), a digital versatile disc, a Blu-ray disc), a magneto-optical disk, a removable disk, a hard disk drive, a smart card, a flash memory (e.g., a card, stick, key drive), a magnetic stripe, or the like, or a combination of at least two of these. Storage 1003 may also be referred to as a secondary storage device.

[0258] The above-mentioned recording medium may be, for example, the memory 1002, the storage 1003, or a database including both the memory 1002 and the storage 1003, a server, or other suitable medium.

[0259] The communication device 1004 is hardware (transmission / reception device) for communicating between computers via a wired network, a wireless network, or both a wired network and a wireless network, and is also referred to as a network device, a network controller, a network card, a communication module, etc. The communication device 1004 may be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc., or a combination of at least two of these. 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.

[0260] The input device 1005 is an input device that accepts input from the outside (for example, a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc., or a combination of at least two of these). The output device 1006 is an output device that performs output to the outside (for example, a display, a speaker, a Light Emitting Diode (LED) lamp, etc., or a combination of at least two of these). Note that the input device 1005 and the output device 1006 may be integrated into one device (for example, a touch panel).

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

[0262] Furthermore, base station 10 and 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), a field programmable gate array (FPGA), a graphics processing unit (GPU), a neural processing unit (NPU), or a combination of at least two of these, and some or all of the functional blocks may be realized using such hardware. For example, processor 1001 may be implemented using at least one of these hardware elements.

[0263] In this disclosure, the term "processor" may encompass a single processor or a group of multiple processors, including, for example, a single-core processor, a multi-core processor, multiple processors in a single device, multiple processors in wired or wireless communication with each other, etc. Similarly, the term "(non-transitory) computer-readable storage medium" may encompass a single storage medium or a group of multiple storage media, including multiple storage media in wired or wireless communication with each other.

[0264] Devices such as processors and storage media in the present disclosure may be distributed locally or remotely, and may perform the processing of the devices by operating cooperatively or independently using a bus, network, the Internet, the cloud, etc.

[0265] Note that the devices included in the core network 30 (for example, network nodes that provide NFs) may also be realized by the above-described functional block / hardware configuration.

[0266] (Variation) Each aspect / embodiment described in the present disclosure may be a mobile communication system other than Long Term Evolution (LTE), LTE-Advanced (LTE-A), International Mobile Telecommunications-Advanced (IMT-Advanced), 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 5G-Advanced (5G-A), 6th generation mobile communication system (6G), xth generation mobile communication system (xG (x is, for example, an integer or a decimal number)), Future Radio Access (FRA), New Radio (NR), New radio access (NX), Future generation radio access (FX), Open Radio Access Network (Open RAN (O-RAN)), Wideband Code Division Multiple Access (W-CDMA (registered trademark)), Global System for Mobile communications (GSM (registered trademark)), CDMA2000, Ultra Mobile Broadband (UMB), Institute of Electrical and Electronics Engineers (IEEE) 802.11, IEEE 802.11x (where x is any character string such as b, a, g, n, ac, ax, be, or bn, and when x = n, it is called Wi-Fi 4, when x = ac, it is called Wi-Fi 5, when x = ax, it is called Wi-Fi 6 or Wi-Fi 6E, when x = be, it is called Wi-Fi 7, and when x = bn, it is called Wi-Fi 8.Note that the present disclosure may be applied to systems based on technologies such as Wi-Fi (a registered trademark), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, Ultra-WideBand (UWB), Bluetooth (registered trademark), network virtualization technologies (e.g., Network Function Virtualization (NFV), Service Function Chaining (SFC), Software Defined Networking (SDN)), or Low Power Wide Area (LPWA). Furthermore, each aspect / embodiment described in the present disclosure may be applied to a system based on a combination of at least two of these technologies. Here, "based on" naturally refers not only to a system that uses the technology in question, but also to a system that uses an extension or modification of the technology.

[0267] In the present disclosure, any two terms selected from a set of terms such as "Base Station (BS)", "Radio Base Station", "Fixed Station", "NodeB", "eNodeB (eNB)", "gNodeB (gNB)", "Access Point (AP)", "Transmission Point (TP)", "Reception Point (RP)", "Transmission / Reception Point (TRP)", "Radio Unit (RU)", "Remote Unit (RU)", "Control Unit (CU)", "Distributed Unit (DU)", "Remote Radio Head (RRH)", "node", "gateway", "terrestrial base station", "stratospheric base station", "unmanned aerial vehicle", "High Altitude Platform Station (HAPS)", "airborne platform", "panel", "cell", "Radio Access Network (RAN)", "network", etc. may be used interchangeably. Each cell accommodated by a base station may be referred to by terms such as a macro cell, a small cell, a femto cell, a pico cell, a serving cell, a super cell, etc. In the present disclosure, any two terms selected from a set of terms such as "cell," "sector," "cell group," "carrier," "component carrier," "cluster," "bandwidth part (BWP)," and "carrier bandwidth" may be used interchangeably.

[0268] In the present disclosure, any two terms selected from the set of terms such as "Mobile Station (MS)", "user terminal", "User Equipment (UE)", "Device", "Module", "Terminal", etc. may be used interchangeably.

[0269] A terminal may 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, router (e.g., home router, mobile router, etc.), Telematics Control Unit (TCU), or some other suitable terminology.

[0270] The base station and the terminal may each be composed of one or more devices. The devices constituting at least a part of the base station and the terminal may be called a transmitting device, a receiving device, a [wireless] communication device, etc. In addition, the devices constituting at least a portion of each of the base stations and terminals may be objects themselves, such as 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, unmanned aerial vehicles, stratospheric base stations (e.g., High Altitude Platform Stations (HAPS)), artificial satellites (e.g., Low Earth Orbit (LEO) satellites, Middle Earth Orbit (MEO) satellites, Geostationary Earth Orbit (GEO) satellites), drones (registered trademark), multicopters, quadcopters, balloons, Internet of Things (IoT) equipment (e.g., smart meters, sensors), etc., or may include, but are not limited to, objects or devices mounted on such objects. Furthermore, the object may be a moving object (hereinafter referred to as a "moving object"; this does not exclude the case where the moving object is stationary and not moving), or may be a fixedly positioned object (hereinafter referred to as a "non-moving object").

[0271] Furthermore, a base station in the present disclosure may be read as a 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 terminal is replaced with communication between multiple terminals (which may be called, for example, Device-to-Device (D2D) or Vehicle-to-Everything (V2X)) or communication in a non-terrestrial network (Non-Terrestrial Network (NTN)). In this case, the 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 communication between terminals (for example, "sidelink") or terms corresponding to NTN (for example, feeder link, service link). For example, terms such as uplink channel and downlink channel may be read as sidelink channel.

[0272] The present disclosure is also applicable to cases where at least some of the devices constituting the base station and the terminal operate outside the earth (for example, in the atmosphere or outer space).

[0273] Similarly, the term "terminal" in the present disclosure may be read as "base station." In this case, the base station 10 may be configured to have the functions of the terminal 20 described above.

[0274] In the present disclosure, an operation described as being performed by a base station may be performed by its upper node or by some of its upper nodes (e.g., CU, RU, DU, etc.) in some cases. It is clear that various operations performed for communication with a terminal in a RAN or core network may be performed by at least some of the base station and other network nodes other than the base station. The other network node may be one node or a combination of multiple nodes. The network node is, for example, a node provided in various core networks such as an Evolved Packet Core (EPC) or a 5G Core Network (5GCN, 5GC), and provides one or more network functions (Network Functions (NFs)), but is not limited to these.

[0275] Furthermore, in the present disclosure, the operation of "a terminal receives information from a base station" accompanies the operation of "the base station transmits the information to the terminal," "the base station generates the information," or both. Similarly, the operation of "a terminal transmits information to a base station" accompanies the operation of "the base station receives the information from the terminal." Furthermore, operations such as "a terminal is configured to ..." or "configure UE to ..." may include the operation of "a base station transmits configuration information regarding the configuration of the terminal" or "a terminal configures a predetermined operation based on the configuration information."

[0276] 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 of at least two of them.

[0277] The physical layer signaling may be referred to as Layer 1 (L1) control information. The MAC signaling may be referred to as, for example, a MAC Control Element (CE) or a MAC Protocol Data Unit (PDU). The RRC signaling may be referred to as an RRC message or an information element (IE) in the RRC message. The RRC signaling may be, for example, a message used for controlling an RRC connection (e.g., setup, reconfiguration, establishment, reestablishment, release, or resume), mobility, a measurement report, notification of terminal capabilities, or an information element in the message.

[0278] Furthermore, notification of information may be either explicit or implicit. Note that an explicit notification of certain information means notification of the certain information itself, and an implicit notification of certain information may mean notification of information other than the certain information, or the certain information being deemed to have been notified when a certain condition is met.

[0279] Furthermore, notification of information may include not only notification between the same layers of different devices (for example, between a lower layer or an upper layer of the base station 10 and the terminal 20) but also notification between different layers in the same or different devices (for example, between a lower layer and an upper layer in the base station 10 or the terminal 20). Furthermore, notification of information from one device to another device may be performed via one or more devices.

[0280] With respect to any information (e.g., variables, constants, parameters, settings) described in the present disclosure, even if not specifically stated in the above embodiments, any first device (e.g., terminal / base station) may notify any second device (e.g., base station / terminal) of information indicating / identifying (or relating to) the value of the any information.

[0281] Each aspect / embodiment described in this disclosure may be used alone, in combination, or switched depending on the implementation. Furthermore, the order of the procedures, sequences, flowcharts, etc. of each aspect / embodiment described in this disclosure may be changed as long as it is consistent. For example, the methods described in this disclosure present various step elements using an exemplary order and are not limited to the particular order presented. Furthermore, at least one step may be omitted in the procedures, sequences, flowcharts, etc. of each aspect / embodiment described in this disclosure.

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

[0283] In the present disclosure, a radio resource may be defined by a combination of resource units in one or more domains, such as the time domain, the frequency domain, the spatial domain, the code domain, and the power domain.

[0284] For example, a resource in the time domain (which may be referred to as a time resource) may be defined by one or more time units. The one or more time units may include, but are not limited to, a radio frame, a subframe, a slot, a symbol, a transmission time interval (TTI), or a combination of at least two of these. Furthermore, the time unit may be a fixed-length time unit that is independent of numerology, a variable-length time unit that is dependent on numerology, or both.

[0285] Examples of fixed-length time units include, but are not limited to, subframes each consisting of one or more slots and radio frames each including multiple subframes. Examples of variable-length time units include, but are not limited to, symbols and slots each including a fixed number of symbols. A certain time unit may be divided into time units shorter than the certain time unit. Examples of such shorter time units include, but are not limited to, minislots each consisting of fewer symbols than the number of symbols that make up a slot. The above-described time units may include time units used as units for scheduling, link adaptation, and the like. Any time unit in the present disclosure may be interchangeable with another time unit.

[0286] Numerology is a parameter that defines the physical layer structure, and may be a parameter based on at least one of the subcarrier spacing (SCS), the symbol length, the cyclic prefix length, and the sampling time, for example.

[0287] A resource in the frequency domain (which may also be referred to as a frequency resource) may be defined by, for example, one or more frequency units. The one or more frequency units may include, for example, a subcarrier, a resource block (RB), a bandwidth part (BWP), a carrier bandwidth, or a combination of at least two of these, but the name of the frequency unit is not limited to these. Furthermore, the number of subcarriers included in a certain frequency unit may be a fixed number regardless of numerology, or may be a variable number that changes depending on numerology.

[0288] For example, an RB is composed of a predetermined number of consecutive subcarriers in the frequency domain, and the number of subcarriers included in the RB may be the same regardless of numerology, for example, 12, but is not limited to this. Also, a BWP may be composed of, for example, one or more consecutive RBs within a certain carrier bandwidth, but is not limited to this. One or more BWPs may be configured within one carrier for terminal 20, and at least one of the BWPs may be activated. Also, any frequency unit in the present disclosure may be interpreted as another frequency unit.

[0289] Furthermore, resources in both the time domain and the frequency domain may be defined by one or more time / frequency units each consisting of a time unit and a frequency unit, such as, but not limited to, a resource element (RE) consisting of one symbol and one subcarrier, a resource element group (REG) consisting of a predetermined number of REs, or a control resource set (CORESET) consisting of a predetermined number of symbols and a predetermined number of RBs.

[0290] The resources in the spatial domain (which may also be referred to as spatial resources) may be defined, for example, by one or more spatial units, including, but not limited to, beams, layers of Multi-Input Multi-Output (MIMO), antenna ports, etc., or a combination of at least two of them.

[0291] The resource in the code domain (which may also be referred to as a code resource) may be defined by, for example, one or more code units, including, but not limited to, a Cyclic Shift (CS), an Orthogonal Cover Code (OCC), or a combination thereof.

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

[0293] In the present disclosure, terms such as "decide," "determine," "judge," "select," "specify," "compute," "calculate," "process," "derive," "look up / search / inquiry," "confirm," "assume," "expect," and "consider" may be read interchangeably. Also, in the present disclosure, performing a certain process (e.g., sending, receiving) may be read interchangeably as deciding to perform that process. Also, in the present disclosure, "not expected to do..." may be read interchangeably as "assumed not to do...."

[0294] In the present disclosure, "expect" may be interchangeably read as "be expected." For example, "expect(s) ..." ("..." may be expressed, for example, as a that clause, a to-infinitive, etc.) may be interchangeably read as "be expected ...," "do ... (if the above "..." is a to-infinitive, a verb with "to")," etc. "does not expect ..." may be interchangeably read as "be not expected ...," "does not ... (if the above "..." is a to-infinitive, a verb with "to")," etc. Furthermore, "An apparatus A is not expected ..." may be interchangeably read as "an apparatus B other than apparatus A does not expect ... from apparatus A" (for example, if apparatus A is a UE, apparatus B may be a base station).

[0295] In the present disclosure, terms such as "less than or equal to," "less than," "greater than," "more than," "equal to," etc. may be interchangeable. Furthermore, in the present disclosure, terms meaning "good," "bad," "big," "small," "high," "low," "fast," "slow," "wide," "narrow," etc. may be interchangeable, not limited to the positive, comparative, and superlative. Furthermore, in the present disclosure, terms meaning "good," "bad," "big," "small," "high," "low," "fast," "slow," "wide," "narrow," etc. may be interchangeable, not limited to the positive, comparative, and superlative, as expressions with the prefix "i-th" (i is any integer) (for example, "highest" may be interchangeable as "i-th highest").

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

[0297] In the present disclosure, terms such as "when A, B," "if A, (then) B," "B upon A," "B in response to A," "B based on A," "B during / while A," "B before A," "B at (the same time as) / on A," "B after A," "B since A," and "B until A" may be interchangeable. Note that A, B, and the like herein may be replaced with appropriate expressions, such as nouns, gerunds, and regular sentences, depending on the context. Note that the time difference between A and B may be nearly zero (immediately after or immediately before). A time offset may be applied to the time at which A occurs. For example, "A" may be interchangeable with "before / after the time offset at which A occurs." The time offset (eg, one or more symbols / slots) may be predefined or may be specified by the UE based on signaled information.

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

[0299] In the present disclosure, terms such as "precoding," "precoder," "weight (precoding weight)," "Quasi-Co-Location (QCL)," "Transmission Configuration Indication state (TCI state)," "spatial relation," "spatial relation information," "spatial domain filter," "transmit power," "phase rotation," "antenna port," "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.

[0300] In the present disclosure, an 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, a resource may be interchangeably read as a resource for any signal / channel (e.g., a reference signal resource). Furthermore, the spatial domain filter may include at least one of a spatial domain transmission filter and a spatial domain reception filter.

[0301] In the present disclosure, beam, sounding reference signal (SRS) resource indicator (SRS resource indicator (SRI)), control resource set (CONTROLLER RESOLUTION SET (CORESET)), CORESET pool, downlink shared channel (Physical Downlink Shared Channel (PDSCH)), uplink shared channel (Physical Uplink Shared Channel (PUSCH)), codeword (CW), transport block (TB), reference signal (RS), etc. may be interchangeable.

[0302] In the present disclosure, the terms TCI state, TCI, downlink TCI state (Downlink (DL) TCI state), uplink TCI state (Uplink (UL) TCI state), unified TCI state, common TCI state, joint TCI state, etc. may be read interchangeably.

[0303] Furthermore, in this disclosure, terms such as "QCL," "QCL assumptions," "QCL relationships," "QCL type information," "QCL properties," "specific QCL type (e.g., Type A, Type D) properties," and "specific QCL type (e.g., Type A, Type D)" may be interchangeable.

[0304] In this disclosure, terms such as index, identifier (ID), identity (ID), indicator, indication, resource ID, etc. may be interchangeable. In this disclosure, terms such as sequence, list, set, group, cluster, subset, etc. may be interchangeable.

[0305] In the present disclosure, a group may include, for example, at least one of a spatial relationship group, a Code Division Multiplexing (CDM) group, an RS group, a CORESET group, a Physical Uplink Control Channel (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.

[0306] Information in this disclosure (e.g., variables, constants, parameters, settings) may be interchangeably read as the ID of the information. For example, TCI state and TCI state ID may be interchangeably read as the ID of the information. Also, information in this disclosure may be interchangeably read as "a set of the information," "one or more pieces of the information," etc.

[0307] Any signal / channel (e.g., PUCCH) in the present disclosure may be interchangeably read as another signal / channel (e.g., PUSCH, PDSCH, any RS). A signal / channel may be interchangeably read as a signal / channel for the same direction (e.g., UL if the certain signal / channel is in the UL direction, and DL if in the DL direction), or as a signal / channel for another direction (e.g., DL if the certain signal / channel is in the UL direction, and UL if in the DL direction). Also, in the present disclosure, descriptions related to DL communication and descriptions related to UL communication may be interchangeably read. In this case, DL (UL) operation may be interchangeably read as the corresponding UL (DL) operation. For example, reception of a PDSCH in a terminal may be interchangeably read as transmission of a PUSCH in the terminal.

[0308] In the present disclosure, terms such as "X's number," "X number," "the number of X(s)," and "a number of X(s)" may be interchangeable. Note that X here may be replaced with an appropriate expression such as a noun, a gerund, or an ordinary sentence, depending on the context. In the present disclosure, "number" may be interchangeable with terms such as maximum number, minimum number, average number, and total number. In addition, in the present disclosure, terms such as "value," "index," "number," and "quantity" may be interchangeable with each other.

[0309] Values / ranges in this disclosure may be interpreted as approximations, as if the words "about" or "approximately" were preceding the value / range. In this disclosure, "A and B are the same" (A and B are any words) may mean "A and B are identical," "A and B are almost the same," "A and B are partly the same (or partially overlapped)," "There is an error within a certain range between A and B," etc. (i.e., these words may be read interchangeably). Furthermore, in the present disclosure, A and B being the same may mean that at least part of A and at least part of B are the same (or overlapped).

[0310] In this disclosure, the terms "one embodiment," "some embodiments," "another embodiment," etc. may be used interchangeably. The appearances of phrases such as "one embodiment," "some embodiments," "another embodiment," etc. in this disclosure do not necessarily all refer to the same embodiment, nor are they necessarily meant to be mutually exclusive.

[0311] In the present disclosure, expressions such as "at least one of A and B," "at least one of A or B," "A and / or B," and "A / B" may be read interchangeably and may be understood to include "only A," "only B," or "both A and B." Furthermore, in the present disclosure, expressions such as "at least one of A, B, and C," "at least one of A, B, or C," "A, B and / or C," and "A / B / C" may be read interchangeably and may be understood to include "only A," "only B," "only C," "A and B," "B and C," "C and A," or "all of A, B, and C." Note that similar interpretations / readings can be applied to any expression in this disclosure such as "at least X of ..." (where the number of elements in "..." and X are each any number).

[0312] In the present disclosure, expressions such as "A, [and] B, and the like" / "such as A and B"," "A, [or] B, or the like" / "such as A or B"," "A, B, etc." / "A, B, and so on" / "A, B, and so forth"," and "A, B, [and / or] the others" may be read interchangeably.

[0313] In the present disclosure, expressions representing one / single X (e.g., "a X," "one X," "a single X"), expressions representing one or more X (e.g., "one or more X(s)," "at least one of X(s)"), and expressions representing a plurality of X (e.g., "Xs," "more than one X(s)," "multiple X(s)," and "a plurality of X(s)") may be read interchangeably. Note that these expressions may also be read interchangeably with expressions that include specific wording (e.g., when X is an uncountable noun, "pieces of," "amount of," etc.). For example, "a plurality of pieces of spatial relation information" may be read interchangeably as "a plurality of spatial relation information."

[0314] The present disclosure has been described above, but it is for illustrative purposes only, and the present invention is not limited to the aspects / embodiments described in the present disclosure. The present disclosure can be implemented in modified and altered forms without departing from the spirit of the invention. The present disclosure and its modifications and alterations are included in the scope of the present invention and its equivalents.

Claims

1. a receiver for receiving parameters relating to a timing advance offset and a configuration relating to a particular scenario in which two timing advances (TAs) are supported; a control unit that determines whether to support UL transmission applying two timing advances (TAs) based on whether a specific scenario in which the two TAs are supported is configured; The terminal, wherein the specific scenario is an intra-cell scenario with a path loss (PL) offset or an inter-cell scenario without a PL offset.

2. The terminal according to claim 1 , wherein the control unit determines the number of TAs to apply based on whether the PL offset is configured in any transmission configuration indication (TCI) state in a serving cell.

3. 2. The terminal according to claim 1, wherein when a control resource set (CORESET) pool index is not provided and the PL offset is not provided in any transmission configuration indication (TCI) in a serving cell, the receiving unit receives two timing advance offset values.

4. The terminal of claim 1 , wherein when a CORESET pool index value of 1 is provided for a second control resource set (CORESET), the receiver receives two timing advance offset values.

5. receiving parameters for a timing advance offset and a configuration for a particular scenario in which two timing advances (TAs) are supported; determining whether to support UL transmission applying two timing advances (TAs) based on whether a specific scenario in which two TAs are supported is configured; The wireless communication method for a terminal, wherein the specific scenario is an intra-cell scenario with a path loss (PL) offset or an inter-cell scenario without a PL offset.

6. a transmitter for transmitting parameters relating to timing advance offsets and configurations for specific scenarios in which two timing advances (TAs) are supported; a control unit configured to control reception of an UL transmission to which two Timing Advances (TAs) are applied by a terminal based on whether a specific scenario in which the two TAs are supported is configured; The base station, wherein the particular scenario is an intra-cell scenario with a path loss (PL) offset or an inter-cell scenario without a PL offset.

Images