Terminal, wireless communication method, and base station

Abstract

A terminal according to one aspect of the present disclosure comprises: a reception unit that receives a PRACH-related indicator field in a physical downlink control channel order which triggers a physical random access channel (PRACH); and a control unit that determines the bit size of the PRACH-related indicator field on the basis of a specific condition when two timing advances (TA) are supported at an in-cell multi-transmission / reception point (TRP) of a signal downlink control information (DCI) base.

Description

Terminal, wireless communication method and base station

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

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

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

[0004] 3GPP TS 36.300 V8.12.0 “Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 (Release 8)”, April 2010

[0005] It is being considered that a Downlink single transmission / reception point (DL sTRP) / Uplink multi transmission / reception point (UL mTRP) scenario will be applied to future wireless communication systems. In this case, it is being considered that two Timing Advances (TAs) / Timing Advance Groups (TAGs) will be indicated.

[0006] However, the control of UL transmission when two TAs / TAGs are indicated is not clear, so the UE may not be able to appropriately control the timing of UL transmission.

[0007] Therefore, one of the objects 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.

[0008] A terminal according to one aspect of the present disclosure includes a receiving unit that receives a PRACH-related indicator field in a physical downlink control channel order that triggers a physical random access channel (PRACH), and a control unit that determines a bit size of the PRACH-related indicator field based on specific conditions when supporting two timing advances (TAs) in a single downlink control information (DCI)-based intra-cell multiple transmission / reception point (TRP).

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

[0010] FIG. 1A is a diagram showing an example of a typical arrangement of transmission and reception points. FIG. 1B is a diagram showing an example of a high-density UL arrangement. FIG. 2 is a diagram showing an example of DL / UL coverage of a Heterogeneous Network (HetNet). FIG. 3 is a diagram showing an example of TAG settings for a cell. FIGS. 4A and 4B are diagrams showing examples of MAC CEs for timing advance commands. FIG. 5 is a diagram showing an example of a schematic configuration of a wireless communication system according to an embodiment. FIG. 6 is a diagram showing an example of a configuration of a base station according to an embodiment. FIG. 7 is a diagram showing an example of a configuration of a user terminal according to an embodiment. FIG. 8 is a diagram showing an example of hardware configurations of a base station and a user terminal according to an embodiment. FIG. 9 is a diagram showing an example of a vehicle according to an embodiment.

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

[0012] In order to expand UL coverage, the installation of UL reception points in addition to general transmission and reception points is being considered. Therefore, an example of the arrangement of general transmission and reception points and an example of an arrangement with UL reception points (UL high-density arrangement) will be described.

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

[0014] Figure 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 Figure 1B in addition to the TRPs (DL transmission points) shown in Figure 1A. In Figure 1B, a UE receives DL signals from a DL transmission point (TRP / Central TRP / DL 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 can also perform UL transmission to a DL transmission point.

[0015] By using a high-density UL configuration such as that shown in Figure 1B, it is possible to improve both coverage and UL data rates by reducing path loss, improving UL signaling quality, and obtaining a higher coding rate compared to a general configuration such as that shown in Figure 1A. Furthermore, since the UL reception point mainly performs reception, it requires fewer functions (e.g., power amplifiers) and is therefore less costly than a transmission / reception point corresponding to a general small cell, making deployment management much easier.

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

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

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

[0019] 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 ＴＡ ) before

[0020] 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 NTN (non-terrestrial network).

[0021] 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 Ｃ may respectively indicate the Basic time unit for NR.

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

[0023] (Timing Advance Group) When multiple TRPs are used, the distances between the UE and each TRP may be different. The multiple TRPs may be included in the same cell (e.g., serving cell). Alternatively, one TRP among the multiple TRPs may correspond to the serving cell and the other TRPs may correspond to non-serving cells. The multiple TRPs may include DL transmission points and UL reception points. In this case, it is assumed that the distances between each TRP and the UE may be different.

[0024] In existing systems, the transmission timing of an uplink (UL) channel and / or an UL signal (UL channel / signal) is adjusted by a timing advance (TA). The reception timing of the UL channel / signal from different user terminals (UE) is adjusted by a radio base station (TRP: Transmission and Reception Point, also referred to as gNodeB: gNB) side.

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

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

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

[0028] TAGs (e.g., serving cells belonging to the same TAG) may be configured by higher layer parameters. The same timing advance value may be applied to serving cells (e.g., serving cells for which UL is configured) belonging to the same TAG. A timing advance group including the SpCell of a MAC entity may be called a Primary Timing Advance Group (PTAG), and other TAGs may be called Secondary Timing Advance Groups (STAGs). In addition, the maximum number of TAGs may be X (e.g., X=4) per cell group (e.g., MCG / SCG).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0043] (PRACH-related indicator in Rel. 18) The PRACH-related indicator consists of 0 or 1 bit.

[0044] The PRACH related indicator is 1 bit if the following conditions are met: - the UE is provided with specific parameters (tag-Id2 and SSB-MTC-AdditionalPCI), - the UE is not provided with coresetPoolIndex or is provided with coresetPoolIndex (value = 0) for the first CORESET, - the UE is provided with coresetPoolIndex (value = 1) for the second CORESET.

[0045] If the UE is provided with a specific parameter SSB-MTC-AdditionalPCI, the corresponding PRACH related indicator field (hereinafter simply referred to as the field) consisting of one bit indicates the PCI associated with the PRACH transmission.

[0046] Specifically, index 0 of this field is mapped (associated) with the PCI of the serving cell, and index 1 of this field is mapped with the PCI of the active additional cell.

[0047] On the other hand, if the UE has not been provided with the specific parameter SSB-MTC-AdditionalPCI, this field indicates the PL-RS (Path Loss Reference Signal) for PRACH transmission.

[0048] Specifically, index 0 of this field is mapped to the DL RS where the PDCCH-ordered DM-RS is quasi-collocated, and index 1 of this field is mapped to the SS / PBCH indicated by the SS / PBCH index field in this DCI format (1_0).

[0049] Otherwise, if none of the above conditions are met, the PRACH-related indicator is a 0 bit.

[0050] (Reference Signal Power in PRACH Transmission in Rel. 18) If at least one of the following conditions is met, the UE is provided with a parameter referenceSignalPower related to the reference signal power via a corresponding parameter ss-PBCH-BlockPower:

[0051] If the PRACH transmission from the UE is a response to the detection of a PDCCH order by the UE that triggers a contention-free random access procedure, and the DM-RS in the PDCCH order depends on the QCL'ed DL RS, and at least one of the following conditions is met: - there is no PRACH related indicator in the PDCCH order; - there is no cell indicator field in the PDCCH order or the value of this field is 0; - the value of the PRACH related indicator field in the PDCCH order is 0 if the UE is not provided with SSB-MTC-AdditionalPCI; - the PRACH related indicator field in the PDCCH order indicates a physical cell ID (physCellId) associated with the cell receiving the PDCCH order or depends on the indicated SS / PBCH block; - the PRACH transmission is transmitted in a non-serving cell indicated by the cell indicator field in the PDCCH order. - If the UE is not provided with SSB-MTC-AdditionalPCI, and the value of the PRACH related indicator field in the PDCCH order is 1, or - If the PRACH related indicator field in the PDCCH order indicates a physical cell ID (physCellId) that is different from the physical cell ID (physCellId) associated with the cell receiving the PDCCH order.

[0052] (Analysis) It is considered that a DL sTRP / UL mTRP scenario will be applied to future wireless communication systems. In this case, it is considered that two TAs / TAGs will be indicated.

[0053] For example, a further extension of the asymmetric DL sTRP / UL mTRP deployment scenario envisions intra-band / intra-cell non-co-located multi-TRP and further assumes a unified TCI framework for multi-TRP targeting FR1 and FR2, which may not require changes to existing cell definitions or definitions for new cells (e.g., UL-only cells).

[0054] In this extension, for example, when a path loss RS is transmitted from a DL sTRP, it is necessary to clarify the setting of two closed-loop power control adjustment states for the SRS (both of which are independent of the PUSCH) or the path loss offset for the UL TRP in order to calculate the path loss towards the UL TRP.

[0055] The two TAs in asymmetric DL sTRP / UL mTRP deployment scenarios need to be supported, for example, in the following frameworks: - Multi-DCI based intra-cell / inter-cell multi-TRP framework - Single DCI based intra-cell multi-TRP framework - Single DCI based inter-cell beam management (ICBM) framework

[0056] <Problem 1> For example, when supporting two TAs in a single DCI-based intra-cell multi-TRP, it is necessary to extend the PRACH-related indicator field of the DCI (e.g., DCI format 1_0).

[0057] For example, in existing specifications, for a PRACH triggered by a PDCCH order, the PRACH related indicator field in the PDCCH order indicates that the PL-RS of the corresponding PRACH transmission is the QCL-RS of the PDCCH order or the SSB indicated in the PDCCH order.

[0058] Specifically, if the UE is provided with a specific parameter SSB-MTC-AdditionalPCI, the PRACH-related indicator field indicates the PCI associated with the PRACH transmission, whereas if the UE is not provided with a specific parameter SSB-MTC-AdditionalPCI, the PRACH-related indicator field indicates the PL-RS for the PRACH transmission.

[0059] Since the above-mentioned existing specifications are for multi-TRP within a cell based on multi-DCI, the content needs to be extended to single DCI.

[0060] <Issue 2> Furthermore, even when two TAs are supported in single DCI-based inter-cell beam management (ICBM), further enhancements such as UL timing adjustment are required.

[0061] <Problem 3> In addition, in Rel.18, with two TAs for multi-DCI-based intra-cell / inter-cell multi-TRP, the UE does not expect that the TCI state (UL TCI state) associated with one coresetPoolIndex corresponds to two TAGs.

[0062] The above constraints require further extension to support single DCI (ICBM).

[0063] <Problem 4> As described above, in the Rel. 18 multi-DCI-based intra-cell multi-TRP, the PRACH association indicator indicates whether a PRACH (transmission) is associated with the PCI of the serving cell or with an active additional cell (additional PCI).

[0064] Here, in the multi-DCI based intra-cell multi-TRP, only one additional active cell (additional PCI) can be associated with the PRACH (transmission).

[0065] On the other hand, with single DCI-based inter-cell beam management (ICBM) in Rel. 19 and later, it is expected that a maximum of seven additional active cells (additional PCIs) can be associated with a PRACH (transmission).

[0066] In this case, the PRACH-related indicators need to be further extended for single DCI-based ICBM.

[0067] As described above, in order to support two TAs in single DCI-based intra-cell / inter-cell multi-TRP, the existing specifications (i.e., the control of UL transmission when two TAs / TAGs are indicated) need to be further extended.

[0068] If these are not clear, the UE may not be able to properly control the timing of its UL transmissions.

[0069] Therefore, the present inventors have conceived a method for appropriately controlling the timing of UL transmission.

[0070] (Various Replacements, etc.) Hereinafter, embodiments according to the present disclosure will be described in detail with reference to the drawings. Wireless communication methods according to the embodiments may be applied independently or in combination.

[0071] In the 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."

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

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

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

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

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

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

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

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

[0080] In the present disclosure, the terms panel, UE panel, panel group, beam, beam group, precoder, Uplink (UL) transmitting entity, Transmission / Reception Point (TRP), base station, Spatial Relation Information (SRI), spatial relation, SRS resource set, SRS Resource Indicator (SRI), Control Resource Set (CORESET), Physical Downlink Shared Channel (PDSCH), Codeword (CW), Transport Block (TB), Reference Signal (RS), antenna port (e.g., Demodulation Reference Signal (DMRS) port), antenna port group (e.g., DMRS port group), group (e.g., spatial relation group, Code Division Multiplexing (CDM) group, reference signal group, CORESET group, Physical Uplink Control Channel (PUCCH) group, PUCCH resource group), resource (e.g., reference signal resource, SRS resource), resource set (e.g., reference signal resource set), CORESET pool, downlink Transmission Configuration Indication state (TCI state) (DL TCI state), uplink TCI state (UL TCI state), unified TCI state, common TCI state, Quasi-Co-Location (QCL), QCL assumption, etc. may be read as interchangeable.

[0081] In the present disclosure, the terms sTRP, single TRP, channel / signal using single TRP, one SRS resource set indicated by DCI, channel using one TCI state / spatial relationship, multi-TRP not enabled by RRC / DCI, multiple TCI states / spatial relationships not enabled by RRC / DCI, a CORESET pool index (CORESETPoolIndex) value of 1 not set for any CORESET, and no code point in the TCI field mapped to two TCI states may be read interchangeably.

[0082] In the present disclosure, mTRP, multi-TRP, two SRS resource sets indicated by DCI, 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.

[0083] In the present disclosure, single DCI, sDCI, single PDCCH, multi-TRP based on single DCI, sDCI-based mTRP, 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 interchangeably.

[0084] In the present disclosure, multi-DCI, mDCI, multi-PDCCH, multi-TRP based on multi-DCI, mDCI-based mTRP, setting two CORESET pool indices or CORESET pool index = 1 (or a value greater than or equal to 1), and setting multiple specific indexes (e.g., TRP index, CORESET pool index, or index corresponding to TRP) for a specific channel / CORESET may be read interchangeably.

[0085] In the present disclosure, TRP #1 (first TRP) may correspond to a CORESET pool index = 0 or may correspond to the first of two TCI states corresponding to one code point in the TCI field. TRP #2 (second TRP) TRP #1 (first TRP) may correspond to a CORESET pool index = 1 or may correspond to the second 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.

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

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

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

[0089] 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 interchangeable. In the present disclosure, the path loss (PL), the path loss value, and the path loss parameter may be interchangeable.

[0090] In the present 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 conditions are met.

[0091] In the present 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.

[0092] In the present disclosure, TA, TAG, and TA offset value may be interchangeable. DL reference timing and DL reception timing may be interchangeable. Two TAs / TAGs may be interchangeable with more than two TAs / TAGs.

[0093] In the present disclosure, coresetPoolIndex, CORESET pool index, and RRC parameters indicating the CORESET pool index may be interchanged. n-TimingAdvanceOffset and TA offset may be interchanged. TCI-UL-State, UL TCI state, and RRC parameters indicating the UL TCI state may be interchanged. dl-OrJointTCI-StateList, a list of DL or joint TCI states, and RRC parameters indicating a list of DL or joint TCI states may be interchanged. ul-TCI-StateList, a list of UL TCI states, and RRC parameters indicating a list of UL TCI states may be interchanged. n-TimingAdvanceOffset and n-TimingAdvanceOffset2 may be interchanged with a TA offset and an RRC parameter indicating a TA offset.

[0094] DL sTRP / UL mTRP may refer to, for example, the scenario applied in Rel. 19. DL sTRP / UL mTRP may refer to, for example, Scenario 1 ( FIG. 1B ) or Scenario 2 ( FIG. 2 ). Asymmetric DL sTRP / UL mTRP and DL sTRP / UL mTRP may be interchangeable.

[0095] (Wireless communication method) The embodiments of the present disclosure can be broadly categorized as follows: First embodiment: Extension of PRACH-related indicators in single DCI-based intra-cell multi-TRP. Second embodiment: Extension for two TAs in single DCI-based inter-cell beam management (ICBM). Third embodiment: Restrictions when two TAs are supported in single DCI-based ICBM. Fourth embodiment: Extension of PRACH-related indicators in single DCI-based ICBM. Each embodiment will be described below based on these.

[0096] In the present disclosure, each embodiment / option may be applied alone or in combination with other embodiments / options.

[0097] <First embodiment> The first embodiment addresses the above-mentioned problem 1 and relates to an extension of PRACH-related indicators in single DCI-based intra-cell multi-TRP.

[0098] The PRACH-related indicator may indicate the PCI (serving cell / additional cell) associated with the PRACH transmission or the PL-RS for the PRACH transmission.

[0099] The UE may determine the cell (PCI) associated with the PRACH transmission or the PL-RS for the PRACH transmission based on the PRACH-related indicator.

[0100] More specifically, the UE may control the determination depending on whether a specific parameter (SSB-MTC-AdditionalPCI) is provided. The UE may apply the above-mentioned existing specifications regarding the determination.

[0101] For example, the UE may apply the same (common) behavior regarding the above decision in single DCI-based and multi-DCI-based scenarios.

[0102] Alternatively, the UE may apply different behaviors regarding the above determination in the single-DCI-based and multi-DCI-based scenarios, i.e., the UE may apply the above determination in either the single-DCI-based or multi-DCI-based scenario.

[0103] [Aspect 1-1] To support two TAs in a single DCI-based intra-cell multi-TRP framework, the PRACH-related indicator in DCI format 1_0 may be 1 bit if at least one of the following conditions is met:

[0104] That is, the UE may determine / assume the number of bits of the PRACH-related indicator based on conditions 1 to 7 below.

[0105] (Condition 1) When a UE is provided with a specific parameter (tag-Id2), the specific parameter may be a parameter indicating a timing advance group.

[0106] (Condition 2) When a UE is provided with a specific parameter (new higher layer parameter), the new higher layer parameter may be a parameter that enables multiple (two) TAs in a specific scenario (single DCI-based intra-cell multi-TRP framework / single DCI-based inter-cell beam management framework), for example.

[0107] (Condition 3) When the UE is provided with a specific parameter (new higher layer parameter), the new higher layer parameter may be, for example, a parameter that provides a path loss offset setting for a specific scenario (DL sTRP / UL mTRP deployment scenario).

[0108] (Condition 4) When a UE indicates / reports a specific capability (new UE capability), the UE capability may indicate support for multiple (two) TAs in a DL sTRP / UL mTRP deployment scenario or multiple (two) TAs in a single DCI-based intra-cell multi-TRP framework.

[0109] (Condition 5) If the UE is provided with at least one TCI codepoint indicating two TCI states.

[0110] (Condition 6) When the UE is configured with dl-OrJointTCI-StateList or ul-TCI-StateList and has two indicated TCI states. Condition 6 may be a condition for single DCI-based multi-TRP in a unified TCI state. For example, condition 6 may be read as "When the UE is provided with dl-OrJointTCI-StateList or TCI-UL-State and a first TCI-State or TCI-UL-State and a second TCI-State or TCI-UL-State are indicated."

[0111] (Condition 7) When the UE is configured with dl-OrJointTCI-StateList or ul-TCI-StateList.

[0112] The UE can determine / assume the number of bits of the PRACH-related indicator based on conditions 1-7.

[0113] <Modification of Aspect 1-1> To support two TAs in a single DCI-based intra-cell / inter-cell multi-TRP framework, a new field having a function similar to the PRACH-related indicator field described above may be introduced. The new field may be referred to as a field for supporting two TAs in a single DCI-based intra-cell / inter-cell multi-TRP framework.

[0114] (Specification Description Example 1) The new field is composed of 0 or 1 bit. The new field may be 1 bit if it satisfies at least one of the above conditions 1 to 7.

[0115] The new field consists of 0 or 1 bits.

[0116] A new field indicates the PL-RS for PRACH transmission. Index 0 of this field is mapped to the DL RS with which the PDCCH-ordered DM-RS is quasi-collocated. Index 1 of this field is mapped to the SS / PBCH indicated by the SS / PBCH index field in this DCI format (1_0).

[0117] Otherwise, if none of the above conditions are met, the new field is 0 bits.

[0118] (Specification Description Example 2) When at least one of the following conditions is met, the UE is provided with a parameter referenceSignalPower related to reference signal power by a corresponding parameter ss-PBCH-BlockPower.

[0119] If the PRACH transmission from the UE is a response to the detection of a PDCCH order by the UE that triggers a contention-free random access procedure and the DM-RS in the PDCCH order depends on the QCL'ed DL RS, and at least one of the following conditions is met: - the PRACH related indicator is not present in the PDCCH order; - the cell indicator field in the PDCCH order is not present or has a value of 0; - the PRACH related indicator field in the PDCCH order has a value of 0 if the UE is not provided with SSB-MTC-AdditionalPCI; - the PRACH related indicator field in the PDCCH order indicates a physical cell ID (physCellId) associated with the cell receiving the PDCCH order; - the value of the new field in the PDCCH order is 0; - depends on the indicated SS / PBCH block; - if the PRACH transmission is sent in a non-serving cell indicated by the cell indicator field of the PDCCH order; - if the UE is not provided with SSB-MTC-AdditionalPCI and the value of the PRACH related indicator field of the PDCCH order is 1; - if the PRACH related indicator field of the PDCCH order indicates a physical cell ID (physCellId) that is different from the physical cell ID (physCellId) associated with the cell receiving the PDCCH order; - if the value of the new field of the PDCCH order is 1.

[0120] [Aspect 1-2] In a single DCI-based intra-cell multi-TRP framework or a DL sTRP / UL mTRP deployment scenario, two TAs may not be supported.

[0121] When a single DCI-based intra-cell multi-TRP framework or a DL sTRP / UL mTRP deployment scenario is configured, the UE may not expect at least one of the following configurations / indications / behaviors:

[0122] - Multiple (may be two, three or more) TAGs are configured for one serving cell. - Multiple (may be two, three or more) DL reference timings are configured for one serving cell, where each DL reference timing may be associated with a TAG. - Multiple (may be two, three or more) timing advance offset values ​​(n-TimingAdvanceOffset values) are configured for each serving cell, where each timing advance offset value may be associated with a TAG. - A correspondence (mapping / association) between TAG IDs and TCI states is configured. - TAG IDs are indicated in absolute timing advance MAC CEs (absolute TAC MAC CEs). - TAG IDs are indicated in MAC random access responses (MAC RARs). A PDCCH order for one TRP / cell / PCI / TCI state triggers a PRACH for a TRP / cell / PCI / TCI state different from the PDCCH order. A PRACH-related indicator in the PDCCH order that triggers the PRACH (the PRACH-related indicator must be included in the PDCCH order). A TAG ID must be indicated in the PDCCH order. A TAG must be associated with SSB / CSI-RS.

[0123] In aspect 1-2, "when a single DCI-based intra-cell multi-TRP framework or a DL sTRP / UL mTRP deployment scenario is configured" may mean that at least one of the following conditions is met:

[0124] - When the UE is provided with new higher layer parameters enabling the DL sTRP / UL mTRP deployment scenario. - When the UE is provided with new higher layer parameters for configuring the path loss offset for the DL sTRP / UL mTRP deployment scenario. - When the UE is provided with at least one TCI codepoint indicating two TCI states and the UE is not provided with two different CORESETPoolIndexes (i.e., single DCI based). - When the UE is configured with dl-OrJointTCI-StateList or ul-TCI-StateList and has two indicated TCI states and the UE is not provided with two different CORESETPoolIndexes. - When the UE is configured with dl-OrJointTCI-StateList or ul-TCI-StateList and the UE is not provided with two different CORESETPoolIndexes.

[0125] According to this embodiment, the UE can support two TAs in a single DCI-based intra-cell multi-TRP framework or a DL sTRP / UL mTRP deployment scenario, and even if the UE does not support the two TAs, it can appropriately control the corresponding operation according to a specific scenario.

[0126] Second Embodiment The second embodiment addresses the above-mentioned problem 2 and relates to an extension for two TAs in single DCI-based inter-cell beam management (ICBM).

[0127] [Aspect 2-1] In single DCI-based inter-cell beam management, the following extensions may be applied to support two TAs: That is, when supporting two TAs in single DCI-based inter-cell beam management, the UE may expect / assume at least one of the following:

[0128] - Multiple (may be two, three or more) TAGs are configured for one serving cell. - Multiple (may be two, three or more) DL reference timings are configured for one serving cell, where each DL reference timing may be associated with a TAG. - Multiple (may be two, three or more) timing advance offset values ​​(n-TimingAdvanceOffset values) are configured for each serving cell, where each timing advance offset value may be associated with a TAG. - Mapping / association between TAG IDs and TCI states is configured. In UL transmissions, TAG IDs associated with UL / joint TCI states may be used. - TAG IDs are indicated in absolute timing advance MAC CEs (absolute TAC MAC CEs). - TAG IDs are indicated in MAC random access responses (MAC RARs). The TAC (Timing Advance Command) in the MAC RAR may be applied to the indicated TAG ID. Receive (configure) a PRACH configuration for each additional cell / PCI (where the PCI is different from the PCI of the serving cell). Include a PRACH association indicator in the PDCCH order that triggers the PRACH. As described above, the PRACH association indicator indicates the PCI (serving cell / additional cell) associated with the PRACH transmission. That is, the PRACH association indicator indicates whether the PRACH transmission is associated with the serving cell or with which additional cell. A PDCCH order for a certain TRP / cell / PCI / TCI state triggers a PRACH for a TRP / cell / PCI / TCI state different from the PDCCH order. - TAG ID is indicated in the PDCCH order. - TAG and SSB / CSI-RS are associated with each other.

[0129] [Aspect 2-2] The UE may apply the content of aspect 2-1 if at least one of the following conditions is satisfied: That is, the UE may determine / assume support for two TAs in single DCI-based ICBM based on conditions 1 to 4 below.

[0130] (Condition 1) When the UE is provided with specific parameters (new higher layer parameters), the new higher layer parameters may be, for example, parameters for enabling multiple (two) TAs in a DL sTRP / UL mTRP deployment scenario or a single DCI-based ICBM.

[0131] (Condition 2) When a UE is provided with a specific parameter (new higher layer parameter), the new higher layer parameter may be, for example, a parameter related to setting a path loss offset for a DL sTRP / UL mTRP deployment scenario.

[0132] (Condition 3) When a UE indicates / reports a specific capability (new UE capability), the UE capability may indicate support for multiple (two) TAs in a DL sTRP / UL mTRP deployment scenario or multiple (two) TAs in a single DCI-based ICBM.

[0133] (Condition 4) When the UE is provided with a specific parameter (SSB-MTC-AdditionalPCI) and is not provided with two different CORESETPoolIndexes (i.e., it supports single DCI-based ICBM).

[0134] The UE may determine / assume support for two TAs in single DCI-based ICBM based on conditions 1-4.

[0135] [Aspect 2-3] In a single DCI-based ICBM framework or a DL sTRP / UL mTRP deployment scenario, two TAs may not be supported.

[0136] When a single DCI-based ICBM framework or a DL sTRP / UL mTRP deployment scenario is configured, the UE may not expect at least one of the contents (configuration / instruction / behavior) of aspect 2-1.

[0137] In aspect 2-3, "when a single DCI-based ICBM framework or a DL sTRP / UL mTRP deployment scenario is configured" may mean that at least one of the following conditions is met:

[0138] - when the UE is provided with a specific parameter (SSB-MTC-AdditionalPCI) but not with two different CORESETPoolIndex (meaning it supports single DCI based ICBM); - when the UE is provided with new higher layer parameters enabling the DL sTRP / UL mTRP deployment scenario; - when the UE is provided with new higher layer parameters for configuring the path loss offset for the DL sTRP / UL mTRP deployment scenario.

[0139] According to this embodiment, the UE can support two TAs in a single DCI-based ICBM framework or a DL sTRP / UL mTRP deployment scenario, and even if the UE does not support the two TAs, it can appropriately control the corresponding behavior according to a specific scenario.

[0140] <Third Embodiment> The third embodiment addresses the above-mentioned problem 3 and relates to constraints when two TAs are supported in a single DCI-based ICBM.

[0141] In the case of a single DCI based ICBM or DL ​​sTRP / UL mTRP deployment scenario where multiple (two) TAs are enabled, the UE does not expect the TCI-states / UL TCI-states associated with a cell / PCI to correspond to two / multiple TAGs.

[0142] Alternatively, according to UE capabilities, the TCI-states / UL TCI-states associated with a cell / PCI may correspond to two / multiple TAGs.

[0143] In the third embodiment, "when multiple (two) TAs are enabled in a single DCI-based ICBM or DL ​​sTRP / UL mTRP deployment scenario" may mean that at least one of the following conditions 1 to 7 is satisfied:

[0144] (Condition 1) When the UE is provided with a specific parameter (tag-Id2) (i.e., when the UE is provided with multiple (two) TAGs in the serving cell).

[0145] (Condition 2) When the UE is provided with the second n-TimingAdvanceOffset value (i.e., when the UE is provided with multiple (two) timing advance offset values ​​in the serving cell).

[0146] (Condition 3) The UE is provided with a correspondence (mapping / association) between TAG IDs and TCI states.

[0147] (Condition 4) When new upper layer parameters are provided to the UE to enable multiple (two) TAs in a single DCI-based ICBM or DL ​​sTRP / UL mTRP deployment scenario.

[0148] (Condition 5) For DL ​​sTRP / UL mTRP deployment scenarios, new higher layer parameters for setting path loss offset are provided to the UE.

[0149] (Condition 6) When a UE indicates / reports a specific capability (new UE capability), the UE capability may indicate support for multiple (two) TAs in a DL sTRP / UL mTRP deployment scenario or multiple (two) TAs in a single DCI-based ICBM.

[0150] (Condition 7) The UE is provided with a specific parameter (SSB-MTC-AdditionalPCI) and is not provided with two different CORESETPoolIndex (meaning that it supports single DCI-based ICBM).

[0151] [Variation] In a single DCI-based ICBM or DL ​​sTRP / UL mTRP deployment scenario where multiple (two) TAs are enabled, the UE does not expect a TAG with the same index to be associated with the indexes of multiple indicated TCI states. That is, in this case, the UE does not expect the index of the same TAG to be associated with the index of each indicated TCI state. In other words, the UE does not expect a common TAG to be associated with multiple indicated TCI states.

[0152] For example, the UE does not expect the first indicated TCI state to be associated with the first TAG (TAG#1) and the second indicated TCI state to be associated with the second TAG (TAG#1).

[0153] According to this embodiment, the UE can appropriately control its behavior when supporting two TAs in a single DCI-based ICBM framework or in a DL sTRP / UL mTRP deployment scenario based on certain constraints.

[0154] <Fourth Embodiment> The fourth embodiment addresses the above-mentioned problem 4 and relates to an extension of the PRACH-related indicator in single DCI-based ICBM.

[0155] [Aspect 4-1] When multiple (two) TAs are enabled in a single DCI-based ICBM or DL ​​sTRP / UL mTRP deployment scenario, the UE determines which cells (additional cells / serving cells) are to trigger PRACH according to Options 1 and 2 below.

[0156] More specifically, in the above case, the UE determines whether it can trigger PRACH only for the active additional cell (PCI) / serving cell, or whether it can trigger PRACH for the configured additional cells (either the active additional cells or the inactive additional cells) based on the following options 1 and 2.

[0157] (Option 1) PRACH may be triggered only for active additional cells or serving cells, i.e., the UE may trigger PRACH only for active additional cells or serving cells.

[0158] (Option 2) PRACH may be triggered for configured added cells (either active added cells or inactive added cells), i.e., the UE may trigger PRACH for configured added cells (either active added cells or inactive added cells).

[0159] In this disclosure, an active PCI (additional cell) may refer to a PCI (additional cell) that is associated with an active TCI state.

[0160] According to this aspect, the UE can appropriately determine the cell (additional cell / serving cell) that is to trigger the PRACH.

[0161] [Aspect 4-2] When multiple (two) TAs are enabled in a single DCI-based ICBM or DL ​​sTRP / UL mTRP deployment scenario, at least one of the following options 1 and 2 may be applied to indicate which cell (PCI) a PRACH transmission is associated with.

[0162] That is, the UE may determine the cell (additional cell / serving cell) associated with the PRACH transmission according to options 1-2 below.

[0163] (Option 1) Use the PRACH association indicator field in the PDCCH order (DCI format 1_0) that triggers the PRACH transmission, i.e., the UE may use the PRACH association indicator field to determine the cell (additional cell / serving cell) associated with the PRACH transmission.

[0164] (Option 2) Use a new field added in the PDCCH order (DCI format 1_0) that triggers the PRACH transmission, i.e., the UE may use the new field (assuming that the new field is added) to determine the cell (additional cell / serving cell) associated with the PRACH transmission.

[0165] According to this aspect, the UE can appropriately determine the cell (additional cell / serving cell) associated with the PRACH transmission.

[0166] [Aspect 4-3] The number of bits (size) of the PRACH-related indicator field / new field in aspect 4-2 may be in accordance with Alt1 to Alt3 below. The UE may determine / assume the number of bits of the PRACH-related indicator / new field in accordance with Alt1 to Alt3 below.

[0167] (Alt1) The number of bits may be 3. With this number of bits, up to 8 PCIs (including 1 serving cell and 7 additional cells) can be configured / enabled. That is, the number of bits may be determined based on the number of cells (serving cell and additional cells).

[0168] (Alt2) The number of bits may be determined based on the number of additional cells. More specifically, number of bits = ceil(log ２ (NrofadditionalPCI+1)). In the present disclosure, ceil(X) may mean multiplying X by a ceiling function. NrofadditionalPCI may represent the number of additional cells (or active additional cells).

[0169] NrofadditionalPCI represents the number of additional cells and may be set by higher layer signaling (RRC) (Alt2-1).

[0170] NrofadditionalPCI may represent the number of active additional cells (ie, the number of additional cells associated with an active TCI state) (Alt2-2).

[0171] Alt2 allows for flexible control of the number of bits depending on the number of additional cells (or active additional cells).

[0172] [Aspect 4-4] The code point mapping (association) of the PRACH-related indicator field / new field in aspect 4-2 may follow Alt1 to Alt2 below. The UE may determine / assume the code point mapping (association with cells (PCIs)) of the PRACH-related indicator / new field according to Alt1 to Alt2 below.

[0173] (Alt1) One code point (e.g., indicated by bit field index 0) may be mapped to the PCI of the serving cell. The other NrfadditionalPCI code points (e.g., indicated by bit field indexes 1 to NrfadditionalPCI) may be mapped to the PCIs of additional cells, which may be configured by higher layer signaling (RRC) according to the descending / ascending order of the additional cell indices.

[0174] (Alt2) One code point (e.g., indicated by bit field index 0) may be mapped to the PCI of the serving cell. The (other) NrofadditionalPCI code points (e.g., indicated by bit field indexes 1 to NrofadditionalPCI) may be mapped to the PCIs of active additional cells (PCIs of additional cells associated with active TCI states) in descending / ascending order of the additional cell index.

[0175] According to this aspect, the UE can appropriately recognize / determine the correspondence between the code points of the PRACH-related indicators / new fields and the cells (PCIs) according to Alt1 to Alt2.

[0176] In the fourth embodiment, "when multiple (two) TAs are enabled in a single DCI-based ICBM or DL ​​sTRP / UL mTRP deployment scenario" may mean that the same conditions (conditions 1 to 7) as in the third embodiment described above are met.

[0177] <Modification> In the multi-DCI-based inter-cell multi-TRP of Rel. 18, when the PRACH-related indicator field in a PDCCH order indicates the same PCI as that of the cell receiving the PDCCH order, the PL-RS of the PRACH transmission is (corresponds to) the DL RS with which the DM-RS of the PDCCH order is quasi-collocated (QCLed).

[0178] On the other hand, if the PRACH related indicator field in the PDCCH order indicates a PCI different from the cell receiving the PDCCH order, the PL-RS of the PRACH transmission is (corresponds to) the SSB indicated in the PDCCH order.

[0179] These correspondences may also be applied in the case where multiple (two) TAs are enabled in a single DCI-based ICBM.

[0180] Furthermore, the "PRACH-related indicator (field)" in the existing specifications may be read interchangeably with the "new field" in the present disclosure.

[0181] For example, some of the conditions under which the UE uses the parameter referenceSignalPower related to the reference signal power provided by the corresponding parameter ss-PBCH-BlockPower may be interpreted as at least one of the following: - when a new field in the PDCCH order indicates a physical cell ID (physCellId) associated with the cell receiving the PDCCH order; - when a new field in the PDCCH order indicates a physical cell ID (physCellId) that is different from the physical cell ID (physCellId) associated with the cell receiving the PDCCH order.

[0182] According to the modified example, it is possible to effectively utilize existing specifications and simplify UE implementation.

[0183] <Supplementary Information> [Notification of Information to UE] In the above-described embodiments, any information may be notified to the UE (from a network (NW) (e.g., a base station (BS))) (in other words, reception of any information from the BS by the UE) using physical layer signaling (e.g., DCI), higher layer signaling (e.g., RRC signaling, MAC CE), a specific signal / channel (e.g., PDCCH, PDSCH, reference signal), or a combination thereof.

[0184] When the notification is performed by a MAC CE, the MAC CE may be identified by including a new Logical Channel ID (LCID) in the MAC subheader, which is not defined in existing standards.

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

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

[0187] [Notification of Information from UE] In the above-described embodiments, notification of any information from the UE (to the NW) (in other words, transmission / report of any information from the UE to the BS) may be performed using physical layer signaling (e.g., UCI), higher layer signaling (e.g., RRC signaling, MAC CE), a specific signal / channel (e.g., PUCCH, PUSCH, PRACH, reference signal), or a combination thereof.

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

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

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

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

[0192] At least one of the above-described embodiments may be applied only to UEs that have reported a specific UE capability or that support the specific UE capability. Note that "supporting" and "whether to support" may be read interchangeably.

[0193] The specific UE capabilities may indicate at least one of the following: - Supporting specific processing / operation / control / information for at least one of the above embodiments; - Supporting DL sTRP / UL mTRP; - Supporting multi-DCI based intra-cell / inter-cell multi-TRP; - Supporting single DCI based intra-cell multi-TRP; - Supporting single DCI based inter-cell beam management (ICBM); - Supporting two TA / TAGs; - Number of supported TA / TAGs.

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

[0195] Furthermore, the specific UE capability may be a capability that is applied to all duplexing methods (commonly regardless of the duplexing method), or may be a capability for each duplexing method (e.g., Time Division Duplex (TDD) or Frequency Division Duplex (FDD)).

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

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

[0198] (Supplementary Notes) The following inventions are supplemented with respect to one embodiment (first embodiment) of the present disclosure. [Supplementary Note 1] A terminal comprising: a receiving unit that receives a PRACH-related indicator field in a physical downlink control channel order that triggers a physical random access channel (PRACH); and a control unit that determines a bit size of the PRACH-related indicator field based on a specific condition when two timing advances (TAs) are supported in a single downlink control information (DCI)-based intra-cell multiple transmission / reception point (TRP). [Supplementary Note 2] The terminal according to Supplementary Note 1, wherein the specific condition is that the terminal is provided with at least one of a parameter indicating a timing advance group, a parameter enabling multiple TAs in a specific scenario, and a path loss offset configuration for the specific scenario. [Supplementary Note 3] The terminal according to Supplementary Note 1 or Supplementary Note 2, wherein the specific condition is at least one of receiving a transmission configuration indication (TCI) code point indicating two TCI states, having two indicated TCI states, and receiving a configuration related to a unified TCI state. [Supplementary Note 4] The terminal according to any one of Supplementary Notes 1 to 3, wherein, if the single downlink control information (DCI)-based intra-cell multiple transmission / reception point (TRP) does not support two timing advances (TAGs), the control unit does not expect at least one of multiple timing advance groups (TAGs), multiple downlink (DL) reference timings, and timing advance offset values ​​to be configured for the serving cell.

[0199] (Supplementary Note) The following inventions are supplementary notes regarding one embodiment (second embodiment) of the present disclosure. [Supplementary Note 1] A terminal having: a receiving unit that receives specific parameters related to support of two timing advances (TAs) in single downlink control information (DCI)-based inter-cell beam management (ICBM); and a control unit that determines support of two TAs in the DCI-based ICBM based on the specific parameters. [Supplementary Note 2] The terminal according to Supplementary Note 1, wherein the specific parameters are at least one of a parameter that enables support of two TAs in the DCI-based ICBM, a parameter related to setting a path loss offset for a specific scenario, and a parameter related to an additional cell. [Supplementary Note 3] The terminal according to Supplementary Note 1 or Supplementary Note 2, wherein, when supporting two TAs in the DCI-based ICBM, the control unit expects at least one of a plurality of timing advance groups (TAGs), a plurality of downlink (DL) reference timings, and a timing advance offset value to be configured for a serving cell. [Supplementary Note 4] The terminal according to any one of Supplementary Notes 1 to 3, wherein when two TAs are supported in the DCI-based ICBM, the control unit does not expect at least one of multiple timing advance groups (TAGs), multiple downlink (DL) reference timings, and timing advance offset values ​​to be configured for the serving cell.

[0200] (Supplementary Notes) The following inventions are supplemented with respect to one embodiment (third embodiment) of the present disclosure. [Supplementary Note 1] A terminal comprising: a receiving unit that receives parameters for enabling two timing advances (TAs) in single downlink control information (DCI)-based inter-cell beam management (ICBM); and a control unit that determines enabling two TAs in the DCI-based ICBM based on the parameters, wherein, when the two TAs are enabled, the control unit does not expect a transmission configuration indication (TCI) state associated with a cell to correspond to two timing advance groups (TAGs). [Supplementary Note 2] The terminal according to Supplementary Note 1, wherein enabling the two TAs means being provided with two TAGs or two timing advance offset values ​​in a serving cell. [Supplementary Note 3] The terminal according to Supplementary Note 1 or Supplementary Note 2, wherein enabling the two TAs means being provided with a correspondence relationship between TAGs and TCI states. [Supplementary Note 4] The terminal according to any one of Supplementary Note 1 to Supplementary Note 3, wherein enabling the two TAs means providing a parameter related to setting a path loss offset or a parameter related to an additional cell.

[0201] (Supplementary Notes) The following inventions are supplementary notes regarding one embodiment (fourth embodiment) of the present disclosure. [Supplementary Note 1] A terminal comprising: a receiver unit that receives parameters for enabling two timing advances (TAs) in single downlink control information (DCI)-based inter-cell beam management (ICBM) and a PRACH-associated indicator field in a physical downlink control channel order that triggers a physical random access channel (PRACH); and a controller that determines enabling two TAs in the DCI-based ICBM based on the parameters, wherein if the two TAs are enabled, the controller determines a cell that is to be a trigger target for PRACH based on the PRACH-associated indicator field. [Supplementary Note 2] The terminal according to Supplementary Note 1, wherein the cell that is to be a trigger target for PRACH is at least one of a serving cell, an active additional cell, and an inactive additional cell. [Supplementary Note 3] The terminal according to Supplementary Note 1 or Supplementary Note 2, wherein the number of bits of the PRACH-associated indicator field is determined based on the number of additional cells or active additional cells. [Supplementary Note 4] The terminal according to any one of Supplementary Note 1 to Supplementary Note 3, wherein the code points of the PRACH-related indicator field are mapped according to ascending or descending order of the indexes of the additional cells.

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

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

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

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

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

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

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

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

[0210] Furthermore, the user terminal 20 may perform communication using at least one of time division duplex (TDD) and frequency division duplex (FDD) in each CC.

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

[0212] The base station 10 may be connected to the core network 30 directly or via another base station 10. The core network 30 may include, for example, at least one of an Evolved Packet Core (EPC), a 5G Core Network (5GCN), a Next Generation Core (NGC), and the like.

[0213] The core network 30 may include network functions (Network Functions (NF)) such as a User Plane Function (UPF), an Access and Mobility management Function (AMF), a Session Management Function (SMF), a Unified Data Management (UDM), an Application Function (AF), a Data Network (DN), a Location Management Function (LMF), and Operation, Administration and Maintenance (Management) (OAM). A single network node may provide multiple functions. Communication with an external network (e.g., the Internet) may also be performed via the DN.

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

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

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

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

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

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

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

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

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

[0223] One search space may correspond to PDCCH candidates corresponding to one or more aggregation levels. One or more search spaces may be referred to as a search space set. Note that the terms "search space," "search space set," "search space configuration," "search space set configuration," "CORESET," "CORESET configuration," and the like in the present disclosure may be read interchangeably.

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

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

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

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

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

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

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

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

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

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

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

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

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

[0237] The transceiver 120 may form at least one of the transmit beam and the receive beam using digital beamforming (e.g., precoding), analog beamforming (e.g., phase rotation), or the like.

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

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

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

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

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

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

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

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

[0246] The transceiver 120 may transmit a PRACH-related indicator field in a physical downlink control channel order that triggers a physical random access channel (PRACH). When supporting two timing advances (TAs) in a single downlink control information (DCI)-based intra-cell multi-transmission / reception point (TRP), the controller 110 may determine a bit size of the PRACH-related indicator field based on a specific condition.

[0247] The transceiver unit 120 may transmit specific parameters related to support of two timing advances (TAs) in single downlink control information (DCI)-based inter-cell beam management (ICBM). The control unit 110 may control generation of the specific parameters for a terminal to determine support of two TAs in the DCI-based ICBM.

[0248] The transceiver 120 may transmit parameters for enabling two timing advances (TAs) in single downlink control information (DCI)-based inter-cell beam management (ICBM). The controller 110 may control generation of the parameters for a terminal to determine whether to enable two TAs in the DCI-based ICBM. When the two TAs are enabled, the terminal does not need to expect that a transmission configuration indication (TCI) state associated with a cell corresponds to two timing advance groups (TAGs).

[0249] The transceiver unit 120 may transmit parameters for enabling two timing advances (TAs) in single downlink control information (DCI)-based inter-cell beam management (ICBM) and a PRACH-related indicator field in a physical downlink control channel order for triggering a physical random access channel (PRACH). The control unit 110 may control generation of the parameters for a terminal to determine whether to enable two TAs in the DCI-based ICBM. If the two TAs are enabled, the terminal may determine a cell that is a target for triggering a PRACH based on the PRACH-related indicator field.

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

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

[0252] The control unit 210 performs overall control of the user terminal 20. The control unit 210 can be configured from a controller, a control circuit, etc., which are described based on common understanding in the technical field to which the present disclosure relates.

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

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

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

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

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

[0258] The transceiver unit 220 may form at least one of the transmit beam and the receive beam using digital beamforming (e.g., precoding), analog beamforming (e.g., phase rotation), or the like.

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

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

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

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

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

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

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

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

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

[0268] The transceiver unit 220 may receive a PRACH-related indicator field in a physical downlink control channel order that triggers a physical random access channel (PRACH). When two timing advances (TAs) are supported in a single downlink control information (DCI)-based intra-cell multiple transmission / reception point (TRP), the control unit 210 may determine the bit size of the PRACH-related indicator field based on a specific condition. The specific condition may be provided with at least one of a parameter indicating a timing advance group, a parameter enabling multiple TAs in a specific scenario, and a path loss offset configuration for the specific scenario. The specific condition may be at least one of receiving a transmission configuration indicator (TCI) codepoint indicating two TCI states, having two indicated TCI states, or receiving a configuration for a unified TCI state. If two timing advances (TAs) are not supported in the single downlink control information (DCI)-based intra-cell multi-transmission / reception point (TRP), the control unit 210 does not need to expect at least one of multiple timing advance groups (TAGs), multiple downlink (DL) reference timings, and timing advance offset values ​​to be configured for the serving cell.

[0269] The transceiver 220 may receive specific parameters related to support of two timing advances (TAs) in single downlink control information (DCI)-based inter-cell beam management (ICBM). The controller 210 may determine support of two TAs in the DCI-based ICBM based on the specific parameters. The specific parameters may be at least one of a parameter enabling support of two TAs in the DCI-based ICBM, a parameter related to setting a path loss offset for a specific scenario, and a parameter related to an additional cell. When supporting two TAs in the DCI-based ICBM, the controller 210 may expect at least one of multiple timing advance groups (TAGs), multiple downlink (DL) reference timings, and a timing advance offset value to be configured for the serving cell. When supporting two TAs in the DCI-based ICBM, the control unit 210 does not need to expect at least one of multiple timing advance groups (TAGs), multiple downlink (DL) reference timings, and timing advance offset values ​​to be configured for the serving cell.

[0270] The transceiver unit 220 may receive parameters for enabling two timing advances (TAs) in single downlink control information (DCI)-based inter-cell beam management (ICBM). The control unit 210 may determine whether to enable two TAs in the DCI-based ICBM based on the parameters. When the two TAs are enabled, the control unit 210 may not expect a transmission configuration indication (TCI) state associated with a cell to correspond to two timing advance groups (TAGs). Enabling the two TAs may involve providing two TAGs or two timing advance offset values ​​in a serving cell. Enabling the two TAs may involve providing a correspondence between TAGs and TCI states. Enabling the two TAs may involve providing a parameter related to a path loss offset configuration or a parameter related to an additional cell.

[0271] The transceiver unit 220 may receive parameters enabling two timing advances (TAs) in a single downlink control information (DCI)-based inter-cell beam management (ICBM) and a PRACH-related indicator field in a physical downlink control channel order for triggering a physical random access channel (PRACH). The control unit 210 may determine whether to enable two TAs in the DCI-based ICBM based on the parameters. If the two TAs are enabled, the control unit 210 may determine a cell for which a PRACH is to be triggered based on the PRACH-related indicator field. The cell for which a PRACH is to be triggered may be at least one of a serving cell, an active additional cell, and an inactive additional cell. The number of bits in the PRACH-related indicator field may be determined based on the number of additional cells or active additional cells. The code points in the PRACH-related indicator field may be mapped according to an ascending or descending order of the indexes of the additional cells.

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

[0273] Here, the functions include, but are not limited to, judgment, determination, judgment, calculation, computation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, election, establishment, comparison, assumption, expectation, deeming, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assignment. For example, a functional block (component) that performs transmission may be called a transmitting unit, transmitter, etc. As described above, the implementation method of each is not particularly limited.

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

[0275] In the present disclosure, the terms apparatus, circuit, device, section, unit, etc. may be used interchangeably. The hardware configurations of the base station 10 and the user terminal 20 may be configured to include one or more of the devices shown in the drawings, or may be configured to exclude some of the devices.

[0276] For example, although only one processor 1001 is shown, there may be multiple processors. Furthermore, processing may be performed by one processor, or processing may be performed by two or more processors simultaneously, serially, or in other ways. Furthermore, processor 1001 may be implemented by one or more chips.

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

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

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

[0280] The memory 1002 is a computer-readable recording medium and may be configured by at least one of, for example, Read Only Memory (ROM), Erasable Programmable ROM (EPROM), Electrically EEPROM (EEPROM), Random Access Memory (RAM), or other suitable storage medium. The memory 1002 may also be referred to as a register, cache, main memory, etc. The memory 1002 may store executable programs (program codes), software modules, etc. for implementing a wireless communication method according to an embodiment of the present disclosure.

[0281] Storage 1003 is a computer-readable recording medium and may be composed of at least one of, for example, a flexible disk, a floppy disk, a magneto-optical disk (e.g., a compact disc (e.g., a Compact Disc ROM (CD-ROM)), a digital versatile disc, a Blu-ray disc), a removable disk, a hard disk drive, a smart card, a flash memory device (e.g., a card, a stick, a key drive), a magnetic stripe, a database, a server, or other suitable storage medium. Storage 1003 may also be referred to as an auxiliary storage device.

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

[0283] The input device 1005 is an input device (e.g., a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.) that accepts input from the outside. The output device 1006 is an output device (e.g., a display, a speaker, a light emitting diode (LED) lamp, etc.) that outputs to the outside. Note that the input device 1005 and the output device 1006 may be integrated into one device (e.g., a touch panel).

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

[0285] Furthermore, the base station 10 and the user terminal 20 may be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a programmable logic device (PLD), or a field programmable gate array (FPGA), and some or all of the functional blocks may be realized using this hardware. For example, the processor 1001 may be implemented using at least one of these pieces of hardware.

[0286] (Modifications) Note that terms described in the present disclosure and terms necessary for understanding the present disclosure may be replaced with terms having the same or similar meanings. For example, a channel, a symbol, and a signal (signal or signaling) may be interchangeable. A signal may also be a message. A reference signal may be abbreviated as RS, and may also be called a pilot, pilot signal, etc. depending on the applicable standard. A component carrier (CC) may also be called a cell, frequency carrier, carrier frequency, etc.

[0287] A radio frame may be composed of one or more periods (frames) in the time domain. Each of the one or more periods (frames) constituting a radio frame may be called a subframe. Furthermore, a subframe may be composed of one or more slots in the time domain. A subframe may have a fixed time length (e.g., 1 ms) that is independent of numerology.

[0288] Here, the numerology may be a communication parameter applied to at least one of transmission and reception of a signal or channel, and may indicate at least one of, for example, Subcarrier Spacing (SCS), bandwidth, symbol length, cyclic prefix length, Transmission Time Interval (TTI), number of symbols per TTI, radio frame structure, specific filtering performed by a transceiver in the frequency domain, and specific windowing performed by a transceiver in the time domain.

[0289] A slot may be composed of one or more symbols (such as an Orthogonal Frequency Division Multiplexing (OFDM) symbol or a Single Carrier Frequency Division Multiple Access (SC-FDMA) symbol) in the time domain. A slot may also be a time unit based on numerology.

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

[0291] A radio frame, a subframe, a slot, a minislot, and a symbol all represent time units for transmitting signals. The radio frame, the subframe, the slot, the minislot, and the symbol may be referred to by other names corresponding to the radio frame, the subframe, the slot, the minislot, and the symbol. Note that the time units such as a frame, a subframe, a slot, a minislot, and a symbol in the present disclosure may be interchangeable.

[0292] For example, one subframe may be referred to as a TTI, or multiple consecutive subframes may be referred to as a TTI, or one slot or one minislot may be referred to as a TTI. That is, at least one of the subframe and the TTI may be a subframe (1 ms) in existing LTE, a period shorter than 1 ms (for example, 1-13 symbols), or a period longer than 1 ms. Note that the unit representing the TTI may be called a slot, minislot, etc. instead of a subframe.

[0293] Here, TTI refers to, for example, the smallest time unit for scheduling in wireless communication. For example, in an LTE system, a base station performs scheduling to allocate radio resources (such as frequency bandwidth and transmission power that can be used by each user terminal) to each user terminal in TTI units. Note that the definition of TTI is not limited to this.

[0294] The TTI may be a transmission time unit for a channel-encoded data packet (transport block), a code block, a code word, etc., or may be a processing unit for scheduling, link adaptation, etc. When a TTI is given, the time interval (e.g., the number of symbols) to which a transport block, a code block, a code word, etc. is actually mapped may be shorter than the TTI.

[0295] When one slot or one minislot is called a TTI, one or more TTIs (i.e., one or more slots or one or more minislots) may be the minimum time unit for scheduling. Also, the number of slots (minislots) constituting the minimum time unit for scheduling may be controlled.

[0296] A TTI having a time length of 1 ms may be called a regular TTI (TTI in 3GPP Rel. 8-12), normal TTI, long TTI, regular subframe, normal subframe, long subframe, slot, etc. A TTI shorter than a regular TTI may be called a shortened TTI, short TTI, partial or fractional TTI, shortened subframe, short subframe, minislot, subslot, slot, etc.

[0297] In addition, a long TTI (e.g., a normal TTI, a subframe, etc.) may be interpreted as a TTI having a time length of more than 1 ms, and a short TTI (e.g., a shortened TTI, etc.) may be interpreted as a TTI having a TTI length shorter than the TTI length of a long TTI and greater than or equal to 1 ms.

[0298] A resource block (RB) is a resource allocation unit in the time domain and the frequency domain, and may include one or more consecutive subcarriers in the frequency domain. The number of subcarriers included in an RB may be the same regardless of numerology, for example, 12. The number of subcarriers included in an RB may be determined based on numerology.

[0299] In addition, an RB may include one or more symbols in the time domain and may have a length of one slot, one minislot, one subframe, or one TTI, each of which may be composed of one or more resource blocks.

[0300] In addition, one or more RBs may be referred to as a physical resource block (PRB), a sub-carrier group (SCG), a resource element group (REG), a PRB pair, an RB pair, etc.

[0301] Furthermore, a resource block may be composed of one or more resource elements (REs). For example, one RE may be a radio resource region of one subcarrier and one symbol.

[0302] A Bandwidth Part (BWP), which may also be referred to as a partial bandwidth, may represent a subset of contiguous common resource blocks (RBs) for a given numerology on a given carrier, where the common RBs may be identified by their index relative to a Common Reference Point of the carrier. PRBs may be defined in a BWP and numbered within the BWP.

[0303] The BWP may include a UL BWP (BWP for UL) and a DL BWP (BWP for DL). One or more BWPs may be configured for a UE within one carrier.

[0304] At least one of the configured BWPs may be active, and the UE may not expect to transmit or receive a given signal / channel outside the active BWP. Note that the terms "cell," "carrier," etc. in this disclosure may be read as "BWP."

[0305] The above-described structures of radio frames, subframes, slots, minislots, symbols, etc. are merely examples. For example, the number of subframes included in a radio frame, the number of slots per subframe or radio frame, the number of minislots included in a slot, the number of symbols and RBs included in a slot or minislot, the number of subcarriers included in an RB, the number of symbols in a TTI, the symbol length, the cyclic prefix (CP) length, etc. may be changed in various ways.

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

[0307] The names used for parameters and the like in this disclosure are not intended to be limiting in any way. Furthermore, the mathematical expressions and the like using these parameters may differ from those explicitly disclosed in this disclosure. The various channels (PUCCH, PDCCH, etc.) and information elements may be identified by any suitable names, and therefore the various names assigned to these various channels and information elements are not intended to be limiting in any way.

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

[0309] Furthermore, information, signals, etc. may be output from a higher layer to a lower layer and / or from a lower layer to a higher layer. Information, signals, etc. may be input / output via multiple network nodes.

[0310] Input and output information, signals, etc. may be stored in a specific location (for example, memory) or may be managed using a management table. Input and output information, signals, etc. may be overwritten, updated, or added. Output information, signals, etc. may be deleted. Input information, signals, etc. may be transmitted to another device.

[0311] The notification of information is not limited to the aspects / embodiments described in the present disclosure, and may be performed using other methods. For example, the notification of information in the present disclosure may be performed by physical layer signaling (e.g., Downlink Control Information (DCI) and Uplink Control Information (UCI)), higher layer signaling (e.g., Radio Resource Control (RRC) signaling, broadcast information (Master Information Block (MIB) and System Information Block (SIB)), Medium Access Control (MAC) signaling), other signals, or a combination thereof.

[0312] Note that the physical layer signaling may be referred to as Layer 1 / Layer 2 (L1 / L2) control information (L1 / L2 control signal), L1 control information (L1 control signal), etc. Furthermore, the RRC signaling may be referred to as an RRC message, such as an RRC Connection Setup message or an RRC Connection Reconfiguration message. Furthermore, the MAC signaling may be notified using, for example, a MAC Control Element (CE).

[0313] Furthermore, notification of specified information (e.g., notification that "it is X") is not limited to explicit notification, but may be made implicitly (e.g., by not notifying the specified information or by notifying other information).

[0314] The determination may be made by a value represented by one bit (0 or 1), by a Boolean value represented by true or false, or by a comparison of numerical values ​​(e.g., comparison with a predetermined value).

[0315] Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.

[0316] Software, instructions, information, etc. may also be transmitted or received over a transmission medium. For example, if software is transmitted from a website, server, or other remote source using wired technologies (such as coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL)), and / or wireless technologies (such as infrared, microwave), these wired and / or wireless technologies are included within the definition of transmission media.

[0317] As used in this disclosure, the terms "system" and "network" may be used interchangeably. A "network" may refer to devices included in the network (e.g., base stations).

[0318] In this disclosure, terms such as "precoding," "precoder," "weight (precoding weight)," "Quasi-Co-Location (QCL)," "Transmission Configuration Indication state (TCI state)," "spatial relation," "spatial domain filter," "transmit power," "phase rotation," "antenna port," "layer," "number of layers," "rank," "resource," "resource set," "beam," "beam width," "beam angle," "antenna," "antenna element," "panel," "UE panel," "transmitting entity," "receiving entity," etc. may be used interchangeably.

[0319] In the present disclosure, the term "antenna port" may be interchangeably read as an antenna port for any signal / channel (e.g., a demodulation reference signal (DMRS) port). In the present disclosure, the term "resource" may be interchangeably read as a resource for any signal / channel (e.g., a reference signal resource, an SRS resource, etc.). The resource may include time / frequency / code / space / power resources. Furthermore, the spatial domain transmission filter may include at least one of a spatial domain transmission filter and a spatial domain reception filter.

[0320] The group may include, for example, at least one of a spatial relationship group, a Code Division Multiplexing (CDM) group, a Reference Signal (RS) group, a Control Resource Set (CORESET) group, a PUCCH group, an antenna port group (e.g., a DMRS port group), a layer group, a resource group, a beam group, an antenna group, a panel group, and the like.

[0321] In addition, in the present disclosure, beam, SRS Resource Indicator (SRI), CORESET, CORESET pool, PDSCH, PUSCH, codeword (CW), transport block (TB), RS, etc. may be read as interchangeable terms.

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

[0323] Furthermore, in the present disclosure, terms such as "QCL," "QCL assumption," "QCL relationship," "QCL type information," "QCL property / properties," "specific QCL type (e.g., Type A, Type D) property," and "specific QCL type (e.g., Type A, Type D)" may be interchangeable.

[0324] In the present disclosure, terms such as index, identifier (ID), indicator, indication, and resource ID may be interchangeable. In the present disclosure, terms such as sequence, list, set, group, cluster, and subset may be interchangeable.

[0325] Furthermore, the spatial relationship information identifier (ID) (TCI state ID) and the spatial relationship information (TCI state) may be interchangeable. The "spatial relationship information (TCI state)" may be interchangeable with "set of spatial relationship information (TCI state)", "one or more pieces of spatial relationship information", etc. The TCI state and the TCI may be interchangeable. The spatial relationship information and the spatial relationship may be interchangeable.

[0326] In the present disclosure, terms such as "base station (BS)," "radio base station," "fixed station," "NodeB," "eNB (eNodeB)," "gNB (gNodeB)," "access point," "transmission point (TP)," "reception point (RP)," "transmission / reception point (TRP)," "panel," "cell," "sector," "cell group," "carrier," "component carrier," etc. may be used interchangeably. Base stations may also be referred to by terms such as macrocell, small cell, femtocell, picocell, etc.

[0327] A base station can accommodate one or more (e.g., three) cells. When a base station accommodates multiple cells, the overall coverage area of ​​the base station can be partitioned into multiple smaller areas, and each smaller area can be provided with communication service by a base station subsystem (e.g., a small indoor base station (Remote Radio Head (RRH))). The terms "cell" or "sector" refer to part or all of the coverage area of ​​a base station and / or base station subsystem that provides communication service within that coverage.

[0328] In the present disclosure, a base station transmitting information to a terminal may be interpreted as the base station instructing the terminal to control / operate based on the information.

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

[0330] A mobile station may also be referred to as a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or some other suitable terminology.

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

[0332] The mobile body is a movable object that can move at any speed and naturally includes cases where the mobile body is stationary. Examples of the mobile body include, but are not limited to, vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, handcars, rickshaws, ships and other watercraft, airplanes, rockets, satellites, drones, multicopters, quadcopters, balloons, and objects mounted thereon. The mobile body may also be a mobile body that moves autonomously based on an operation command.

[0333] The mobile object may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile object (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). Note that at least one of the base station and the mobile station may also include devices that do not necessarily move during communication operations. For example, at least one of the base station and the mobile station may be an Internet of Things (IoT) device such as a sensor.

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

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

[0336] The electronic control unit 49 is composed of a microprocessor 61, memory (ROM, RAM) 62, and a communication port (for example, an input / output (IO) port) 63. Signals are input to the electronic control unit 49 from various sensors 50-58 provided in the vehicle. The electronic control unit 49 may also be called an Electronic Control Unit (ECU).

[0337] The signals from the various sensors 50-58 include a current signal from a current sensor 50 that senses the current of the motor, a rotation speed signal of the front wheels 46 / rear wheels 47 obtained by a rotation speed sensor 51, an air pressure signal of the front wheels 46 / rear wheels 47 obtained by an air pressure sensor 52, a vehicle speed signal obtained by a vehicle speed sensor 53, an acceleration signal obtained by an acceleration sensor 54, a depression amount signal of the accelerator pedal 43 obtained by an accelerator pedal sensor 55, a depression amount signal of the brake pedal 44 obtained by a brake pedal sensor 56, an operation signal of the shift lever 45 obtained by a shift lever sensor 57, and a detection signal for detecting obstacles, vehicles, pedestrians, etc. obtained by an object detection sensor 58.

[0338] The information service unit 59 is composed of various devices, such as a car navigation system, an audio system, speakers, a display, a television, and a radio, for providing (outputting) various information such as driving information, traffic information, and entertainment information, and one or more ECUs for controlling these devices. The information service unit 59 uses information acquired from external devices via the communication module 60 or the like to provide various information / services (e.g., multimedia information / multimedia services) to the occupants of the vehicle 40.

[0339] The information service unit 59 may include input devices (e.g., keyboards, mice, microphones, switches, buttons, sensors, touch panels, etc.) that accept input from the outside, and may also include output devices (e.g., displays, speakers, LED lamps, touch panels, etc.) that output to the outside.

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

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

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

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

[0344] The communication module 60 receives various information (traffic information, traffic signal information, vehicle distance information, etc.) transmitted from an external device and displays it on an information service unit 59 provided in the vehicle. The information service unit 59 may also be called an output unit that outputs information (for example, outputs information to a device such as a display or speaker based on the PDSCH received by the communication module 60 (or data / information decoded from the PDSCH)).

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

[0346] Furthermore, a base station in the present disclosure may be read as a user terminal. For example, the aspects / embodiments of the present disclosure may be applied to a configuration in which communication between a base station and a user terminal is replaced with communication between multiple user terminals (which may be called, for example, Device-to-Device (D2D) or Vehicle-to-Everything (V2X)). In this case, the user terminal 20 may be configured to have the functions of the base station 10 described above. Furthermore, terms such as "uplink" and "downlink" may be read as terms corresponding to terminal-to-terminal communication (for example, "sidelink"). For example, terms such as an uplink channel and a downlink channel may be read as a sidelink channel.

[0347] Similarly, the user terminal in the present disclosure may be read as a base station, in which case the base station 10 may be configured to have the functions of the user terminal 20 described above.

[0348] In the present disclosure, an operation described as being performed by a base station may be performed by its upper node in some cases. It is apparent that in a network including one or more network nodes having a base station, various operations performed for communication with a terminal may be performed by the base station, one or more network nodes other than the base station (such as, but not limited to, a Mobility Management Entity (MME), a Serving-Gateway (S-GW), etc.), or a combination thereof.

[0349] Each aspect / embodiment described in this disclosure may be used alone, in combination, or switched depending on the implementation. Furthermore, the order of the processing procedures, sequences, flowcharts, etc. of each aspect / embodiment described in this disclosure may be changed unless inconsistent. For example, the methods described in this disclosure present elements of various steps using an example order, and are not limited to the particular order presented.

[0350] Each aspect / embodiment described in the present disclosure may be a technology other than Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 6th generation mobile communication system (6G), xth generation mobile communication system (xG (x is, for example, an integer or decimal number)), Future Radio Access (FRA), New-Radio Access Technology (RAT), New Radio (NR), New radio access (NX), Future generation radio access (FX), Global System for Mobile communications (GSM (registered trademark)), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.17 (WiMAX (registered trademark)), IEEE 802.19 (WiMAX (registered trademark)), IEEE 802.20 (WiMAX (registered trademark)), IEEE 802.21 (Wi-Fi (registered trademark)), IEEE 802.22 (WiMAX (registered trademark)), IEEE 802.23 (WiMAX (registered trademark)), IEEE 802.24 (WiMAX (registered trademark)), IEEE 802.25 (WiMAX (registered trademark)), IEEE 802.26 (WiMAX (registered trademark)), IEEE 802.27 (WiMAX (registered trademark)), IEEE 802.28 (WiMAX (registered trademark)), IEEE 802.29 (WiMAX (registered trademark)), IEEE 802.30 (WiMAX (registered trademark)), IEEE 802.31 (Wi-Fi (registered trademark)), IEEE 802.32 (WiMAX (registered trademark)), IEEE 802.33 (WiMAX (registered trademark)), IEEE 802. The present invention may be applied to systems that use IEEE 802.20, Ultra-WideBand (UWB), Bluetooth (registered trademark), or other suitable wireless communication methods, or to next-generation systems that are expanded, modified, created, or defined based on these. Furthermore, the present invention may be applied to a combination of multiple systems (e.g., a combination of LTE or LTE-A and 5G).

[0351] As used in this disclosure, the phrase "based on" does not mean "based only on," unless expressly stated otherwise. In other words, the phrase "based on" means both "based only on" and "based at least on."

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

[0353] The term "determining" as used in this disclosure may encompass a wide variety of actions. For example, "determining" may be considered to be judging, calculating, computing, processing, deriving, investigating, looking up, search, inquiry (e.g., looking up in a table, database, or another data structure), ascertaining, etc.

[0354] Additionally, "determining" may be considered to be "determining" receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, accessing (e.g., accessing data in memory), etc.

[0355] Furthermore, "determination" may be considered to be "determining" resolving, selecting, choosing, establishing, comparing, etc. In other words, "determination" may be considered to be "determining" some kind of action. In the present disclosure, "determination" may be read interchangeably with the above-mentioned actions.

[0356] Furthermore, in this disclosure, "determine / determining" may be interchangeably read as "assume / assuming," "expect / expecting," "consider / considering," etc. Furthermore, in this disclosure, "does not expect to do..." may be interchangeably read as "assumes not to do...."

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

[0358] The "maximum transmit power" in this disclosure may mean the maximum value of transmit power, the nominal UE maximum transmit power, or the rated UE maximum transmit power.

[0359] As used in this disclosure, the terms "connected," "coupled," or any variation thereof, refer to any direct or indirect connection or coupling between two or more elements, and may include the presence of one or more intermediate elements between two elements that are "connected" or "coupled" to each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, "connected" may be read as "access."

[0360] In this disclosure, when two elements are connected, they may be considered to be "connected" or "coupled" to one another using one or more wires, cables, printed electrical connections, etc., as well as using electromagnetic energy having wavelengths in the radio frequency range, microwave range, light (both visible and invisible) range, etc., as some non-limiting and non-exhaustive examples.

[0361] In the present disclosure, the term "A and B are different" may mean "A and B are different from each other." The term may also mean "A and B are each different from C." Terms such as "separate" and "coupled" may also be interpreted in the same way as "different."

[0362] When the terms "include," "including," and variations thereof are used in this disclosure, these terms are intended to be inclusive, similar to the term "comprising." Furthermore, when the term "or" is used in this disclosure, it is not intended to be an exclusive or.

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

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

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

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

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

[0368] Although the invention according to the present disclosure has been described in detail above, it is clear to those skilled in the art that the invention according to the present disclosure is not limited to the embodiments described in the present disclosure. The description of the present disclosure is for illustrative purposes only and does not impose any limiting meaning on the invention according to the present disclosure.

Claims

1. A terminal comprising: a receiving unit that receives a Physical Random Access Channel (PRACH) related indicator field in a Physical Downlink Control Channel order for triggering the PRACH; and a control unit that determines the bit size of the PRACH related indicator field based on specific conditions when supporting two Timing Advance (TA) in a single Downlink Control Information (DCI) based multi-Transmission and Reception Point (TRP) within a cell.

2. The terminal according to claim 1, wherein the specific conditions are provided with at least one of a parameter indicating a Timing Advance group, a parameter enabling a plurality of TAs in a specific scenario, and a setting of a path loss offset for the specific scenario.

3. The terminal according to claim 1, wherein the specific conditions are at least one of receiving a TCI code point indicating two Transmission Configuration Indicator (TCI) states, having two indicated TCI states, and receiving a setting regarding a unified TCI state.

4. When not supporting two Timing Advance (TA) in a single Downlink Control Information (DCI) based multi-Transmission and Reception Point (TRP) within a cell, the control unit of the terminal according to claim 1 does not expect at least one of a plurality of Timing Advance Groups (TAG), a plurality of Downlink (DL) reference timings, and a Timing Advance offset value to be set for a serving cell.

5. A wireless communication method of a terminal, comprising: receiving a PRACH related indicator field in a Physical Downlink Control Channel order for triggering the PRACH; and determining the bit size of the PRACH related indicator field based on specific conditions when supporting two Timing Advance (TA) in a single Downlink Control Information (DCI) based multi-Transmission and Reception Point (TRP) within a cell. A base station comprising: a transmission unit that transmits a physical random access channel (PRACH) related indicator field in a physical downlink control channel order for triggering the PRACH; and a control unit that determines a bit size of the PRACH related indicator field based on a specific condition when supporting two timing advances (TAs) in a single downlink control information (DCI) based cell multi-transmission reception point (TRP).

Images