Terminals, wireless communication methods, base stations and systems

Abstract

A terminal according to one aspect of the present disclosure comprises: a reception unit that receives at least one timing advance command included in a MAC control element (MAC CE) for random access response; and a control unit that, when application of a timing advance to each transmission / reception point is supported, determines timing advances to be applied to a plurality of transmission / reception points on the basis of the at least one timing advance command, or on the basis of the at least one timing advance command and information indicated through another MAC CE.

Description

Technical Field

[0001] This disclosure relates to a terminal, a wireless communication method in a next-generation mobile communication system 、 base station and system and is related to a base station.

Background Art

[0002] In a Universal Mobile Telecommunications System (UMTS) network, Long Term Evolution (LTE) was specified for the purpose of further high data rates, low latency, etc. (Non-Patent Document 1). Also, for the purpose of further large capacity and sophistication of LTE (Third Generation Partnership Project (3GPP) Release (Rel.) 8, 9), LTE-Advanced (3GPP Rel. 10-14) was specified.

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

Prior Art Documents

Non-Patent Documents

[0004]

Non-Patent Document 1

Summary of the Invention

[0005] Future wireless communication systems (for example, wireless communication systems beyond Rel.17 / 5G) are expected to control communication using multiple transmit / receive points (e.g., Multi-TRP (MTRP)) within a serving cell, or to control communication based on inter-cell mobility including non-serving cells.

[0006] However, when a terminal (user terminal, User Equipment (UE)) performs UL transmission to multiple transmission / reception points, the question arises as to how to control the UL transmission (e.g., timing advance control). If UL transmission to each transmission / reception point is not properly controlled, the quality of communication using multiple transmission / reception points may deteriorate.

[0007] This disclosure is made in view of the above, and describes a terminal and wireless communication method that can properly perform communication even when using multiple transmission and reception points. 、 base station and system One of the objectives is to provide it. [Means for solving the problem]

[0008] A terminal relating to one aspect of this disclosure has a serving cell in which multiple transmit and receive points are configured, Includes a 1-bit field indicating a single transmit / receive point. Medium Access Control Control Element (MAC CE) related to Timing Advance Commands )of If the receiving unit and the setting of timing advance for each transmission / reception point are supported, the MAC CE is included The aforementioned Based on a 1-bit field ,before Note 1 Applies to the send / receive points. , Timing Advance Commands included in the MAC CEIt has a control unit that determines the following. [Effects of the Invention]

[0009] According to one aspect of this disclosure, communication can be performed appropriately even when using multiple transmission points. [Brief explanation of the drawing]

[0010] [Figure 1] Figures 1A-1D show an example of a multi-TRP. [Figure 2] Figures 2A and 2B show an example of inter-cell mobility. [Figure 3] Figure 3 shows an example of a Timing Advance Group (TAG) to which cells included in a cell group belong. [Figure 4] Figure 4 shows an example of a MAC CE for timing advance commands. [Figure 5] Figures 5A and 5B show examples of events / conditions that trigger the random access procedure according to the first embodiment. [Figure 6] Figures 6A and 6B show an example of how to apply the TAC included in the RAR according to the second embodiment. [Figure 7] Figures 7A and 7B show an example of a RAR (e.g., MAC CE for RAR) that indicates the TAC according to the second embodiment. [Figure 8] Figures 8A and 8B show other examples of RARs (e.g., MAC CE for RAR) that indicate the TAC according to the second embodiment. [Figure 9] Figures 9A and 9B show other examples of how the TAC included in the RAR according to the second embodiment is applied. [Figure 10] Figure 10 shows an example of another MAC CE used to notify information about TA according to the second embodiment. [Figure 11]FIG. 11A and FIG. 11B are diagrams showing an example of a RAR (e.g., MAC CE for RAR) that instructs a TAC according to the second embodiment. [Figure 12] FIG. 12 is a diagram showing an example of a schematic configuration of a wireless communication system according to an embodiment. [Figure 13] FIG. 13 is a diagram showing an example of a configuration of a base station according to an embodiment. [Figure 14] FIG. 14 is a diagram showing an example of a configuration of a user terminal according to an embodiment. [Figure 15] FIG. 15 is a diagram showing an example of a hardware configuration of a base station and a user terminal according to an embodiment. [Figure 16] FIG. 16 is a diagram showing an example of a vehicle according to an embodiment.

MODE FOR CARRYING OUT THE INVENTION

[0011] (TCI, Spatial Relationship, QCL) In NR, based on the Transmission Configuration Indication state (TCI state), reception processing (e.g., at least one of reception, demapping, demodulation, decoding) and transmission processing (e.g., at least one of transmission, mapping, precoding, modulation, encoding) of at least one of a signal and a channel (expressed as a signal / channel) in a UE are considered to be controlled.

[0012] The TCI state may represent what is applied to a downlink signal / channel. What corresponds to the TCI state applied to an uplink signal / channel may be expressed as a spatial relation.

[0013] TCI status refers to information about signal / channel quasi-co-location (QCL), and may also be called spatial reception parameters or spatial relation information. TCI status may be set for each channel or signal in the UE.

[0014] QCL is an index that indicates the statistical properties of a signal / channel. For example, if two signals / channels have a QCL relationship, it may mean that we can assume that at least one of the following is identical between these different signals / channels: Doppler shift, Doppler spread, average delay, delay spread, and spatial parameter (e.g., spatial Rx parameter).

[0015] The spatial reception parameters may correspond to the UE's received beam (e.g., the received analog beam), and the beam may be identified based on the spatial QCL. In this disclosure, QCL (or at least one element of QCL) may be interpreted as sQCL (spatial QCL).

[0016] QCL may have multiple types (QCL types). For example, there may be four QCL types A and D that differ in the parameters (or parameter sets) that can be assumed to be the same, and these parameters (which may also be called QCL parameters) are shown below: • QCL Type A (QCL-A): Doppler shift, Doppler spread, mean delay and delay spread, • QCL Type B (QCL-B): Doppler shift and Doppler spread, • QCL Type C (QCL-C): Doppler shift and mean delay, • QCL Type D (QCL-D): Spatial reception parameters.

[0017] The assumption by the UE that one control resource set (CORESET), channel, or reference signal is in a specific QCL (e.g., QCL type D) relationship with another CORESET, channel, or reference signal may be called a QCL assumption.

[0018] The UE may determine at least one of the transmit beam (Tx beam) and receive beam (Rx beam) of a signal / channel based on the TCI state or QCL assumption of the signal / channel.

[0019] The TCI state may, for example, be information regarding the QCL between the target channel (in other words, the reference signal (RS) for that channel) and another signal (e.g., another RS). The TCI state may be set (indicated) by upper-layer signaling, physical layer signaling, or a combination thereof.

[0020] In this disclosure, the upper-layer signaling may be, for example, Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information, or a combination thereof.

[0021] MAC signaling may use, for example, MAC Control Elements (MAC CEs) or MAC Protocol Data Units (PDUs). Broadcast information may also include, for example, Master Information Blocks (MIBs), System Information Blocks (SIBs), Remaining Minimum System Information (RMSIs), or Other System Information (OSIs).

[0022] Physical layer signaling may include, for example, Downlink Control Information (DCI).

[0023] The channel / signal to which the TCI status applies may also be called the target channel / reference signal (target channel / RS), or simply the target, while the other signal mentioned above may be called the reference signal (reference RS), source RS, or simply the reference.

[0024] The channel on which the TCI state or spatial relationship is set (specified) may be, for example, at least one of the following: Physical Downlink Shared Channel (PDSCH), Physical Downlink Control Channel (PDCCH), Physical Uplink Shared Channel (PUSCH), or Physical Uplink Control Channel (PUCCH).

[0025] Furthermore, the RS that has a QCL relationship with the channel may be at least one of the following: a Synchronization Signal Block (SSB), a Channel State Information Reference Signal (CSI-RS), a Sounding Reference Signal (SRS), a Tracking CSI-RS (also called a Tracking Reference Signal (TRS)), a QCL detection reference signal (also called a QRS), or a Demodulation Reference Signal (DMRS)).

[0026] An SSB is a signal block that includes at least one of a Primary Synchronization Signal (PSS), a Secondary Synchronization Signal (SSS), and a Physical Broadcast Channel (PBCH). An SSB may also be called an SS / PBCH block.

[0027] The RS of a QCL type X in a TCI state may also mean the RS in the relationship between a channel / signal (or its DMRS) and a QCL type X, and this RS may also be called the QCL source of the QCL type X in that TCI state.

[0028] (Multi-TRP) In NR, it is being considered that one or more transmission / reception points (TRPs) (multi-TRPs) will use one or more panels (multi-panels) to perform DL transmissions to the UE. Furthermore, it is being considered that the UE will perform UL transmissions to one or more TRPs.

[0029] Multiple TRPs may correspond to the same cell identifier (Cell Identifier (ID)) or to different cell IDs. This cell ID may be a physical cell ID (e.g., PCI) or a virtual cell ID.

[0030] Figures 1A-1D show examples of multi-TRP scenarios. In these examples, it is assumed, but not limited to, that each TRP can transmit four different beams.

[0031] Figure 1A shows an example of a case where only one TRP (TRP1 in this example) among the multi-TRPs transmits to the UE (this may also be called single-mode or single-TRP). In this case, TRP1 transmits both control signals (PDCCH) and data signals (PDSCH) to the UE.

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

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

[0034] Figure 1D shows an example of a multi-TRP where each of the multi-TRPs transmits a separate control signal to the UE, and the multi-TRP transmits data signals (this may also be called multi-master mode). TRP1 may transmit a first control signal (DCI), and TRP2 may transmit a second control signal (DCI). The UE receives each PDSCH transmitted from the multi-TRP based on these DCIs.

[0035] When scheduling multiple PDSCHs from a multi-TRP (which may also be called multiple PDSCHs) as shown in Figure 1B using a single DCI, that DCI may be called a single DCI (S-DCI, single PDCCH). Similarly, when scheduling multiple PDSCHs from a multi-TRP (as shown in Figure 1D) using multiple DCIs, these multiple DCIs may be called multiple DCIs (M-DCI, multi-PDCCH (multiple PDCCH)).

[0036] Each TRP in a multi-TRP system may transmit different transport blocks (TBs), code words (CWs), and layers. Alternatively, each TRP in a multi-TRP system may transmit the same TB, CW, and layer.

[0037] Non-Coherent Joint Transmission (NCJT) is being considered as one form of multi-TRP transmission. In NCJT, for example, TRP1 modulates and layers a first codeword and transmits a first PDSCH using a first precode with a first number of layers (e.g., 2 layers). TRP2 modulates and layers a second codeword and transmits a second PDSCH using a second precode with a second number of layers (e.g., 2 layers).

[0038] Furthermore, multiple PDSCHs (Multi-PDSCHs) that are NCJTed may be defined as partially or completely overlapping with respect to at least one of the time and frequency domains. In other words, a first PDSCH from a first TRP and a second PDSCH from a second TRP may overlap in at least one of the time and frequency resources.

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

[0040] In URLLC for multiple TRPs, support for PDSCH (Transport Block (TB) or Codeword (CW)) repetition spanning multiple TRPs is being considered. Support for repetition schemes (URLLC schemes, e.g., schemes 1, 2a, 2b, 3, 4) spanning multiple TRPs on the frequency domain, layer (spatial) domain, or time domain is being considered. In scheme 1, multiple PDSCHs from multiple TRPs are performed using space division multiplexing (SDM). In schemes 2a and 2b, PDSCHs from multiple TRPs are performed using frequency division multiplexing (FDM). In scheme 2a, the redundant version (RV) is the same for multiple TRPs. In scheme 2b, the RV may be the same or different for multiple TRPs. In schemes 3 and 4, multiple PDSCHs from multiple TRPs are performed using time division multiplexing (TDM). In Scheme 3, multi-PDSCH signals from multi-TRPs are transmitted within a single slot. In Scheme 4, multi-PDSCH signals from multi-TRPs are transmitted within different slots.

[0041] Such multi-TRP scenarios allow for more flexible transmission control using high-quality channels.

[0042] NCJT using multiple TRPs / panels may utilize high ranks. To support ideal and non-ideal backhauls between multiple TRPs, both single DCI (single PDCCH, e.g., Figure 1B) and multi-DCI (multi-PDCCH, e.g., Figure 1D) may be supported. For both single and multi-DCI, the maximum number of TRPs may be 2.

[0043] An extension of the TCI is being considered for single PDCCH designs (primarily for ideal backhaul). Each TCI code point within the DCI may correspond to one or two TCI states. The TCI field size may be the same as that of Rel. 15.

[0044] For PDCCH / CORESET as defined in Rel.15, one TCI state without a CORESET Pool Index (CORESETPoolIndex) (also known as TRP Info) is set for one CORESET.

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

[0046] (Inter-cell mobility) In NR, it is being considered that one or more transmission / reception points (TRPs) (multi-TRPs (MTRPs)) will perform DL transmissions to the UE. It is also being considered that the UE will perform UL transmissions to one or more TRPs.

[0047] In inter-cell mobility (e.g., L1 / L2 inter-cell mobility), the UE may receive channels / signals from multiple cells / TRPs (see Figures 2A and 2B).

[0048] Figure 2A shows an example of inter-cell mobility including a non-serving cell (e.g., Single-TRP inter-cell mobility). The UE may configure one TRP (or single TRP) in each cell. Here, the UE receives channels / signals from the base station / TRP of cell #1, which is the serving cell, and from the base station / TRP of cell #3, which is not the serving cell (it becomes a non-serving cell). This corresponds, for example, to the UE switching from cell #1 to cell #3 (e.g., a fast cell switch). The TRP of the serving cell may be called the primary TRP (e.g., pTRP). The TRP of the non-serving cell may be called an additional TRP (aTRP).

[0049] In this case, the selection of a port (e.g., an antenna port) / TRP may be performed dynamically. The selection of a port (e.g., an antenna port) / TRP may be performed based on the TCI status indicated or updated by the DCI / MAC CE. Here, we show a case where different physical cell IDs (e.g., PCI) are supported for cell #1 and cell #3.

[0050] Figure 2B shows an example of a multi-TRP scenario (e.g., multi-TRP inter-cell mobility). The UE may have multiple (e.g., two) TRPs (or different CORESET pool indices) configured in each cell. Here, the UE receives channels / signals from TRP#1 and TRP2. Here, TRP#1 corresponds to physical cell ID (PCI)#1 and TRP#2 corresponds to PCI#2.

[0051] Multiple TRPs (TRP#1, #2) may be connected by an ideal / non-ideal backhaul, and information, data, etc., may be exchanged. Each TRP in a multi-TRP may transmit the same or different codewords (CW) and the same or different layers. As one form of multi-TRP transmission, Non-Coherent Joint Transmission (NCJT) may be used, as shown in Figure 2B. Here, we show the case where NCJT is performed between TPRs corresponding to different PCIs. Note that the same serving cell settings may be applied / configured for TRP#1 and TRP#2.

[0052] Multiple PDSCHs (Multi-PDSCHs) that are NCJTed may be defined as partially or completely overlapping with respect to at least one of the time and frequency domains. That is, a first PDSCH from TRP#1 and a second PDSCH from TRP#2 may overlap in at least one of the time and frequency resources. The first and second PDSCHs may be used for transmitting the same TB or for transmitting different TBs.

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

[0054] Multiple PDSCHs from a multi-TRP (which may also be called multiple PDSCHs) may be scheduled using a single DCI (single DCI (S-DCI), single PDCCH) (single master mode). A single DCI may be transmitted from one TRP in the multi-TRP. A configuration using a single DCI in a multi-TRP may be called a single-DCI-based multi-TRP (mTRP / MTRP).

[0055] Multiple PDSCHs from a multi-TRP may be scheduled using multiple DCIs (multi-DCI (M-DCI), multi-PDCCH (multiple PDCCH)) (multi-master mode). Multiple DCIs may be transmitted from each of the multi-TRPs. A configuration that utilizes multiple DCIs in a multi-TRP may be called a multi-DCI-based multi-TRP (mTRP / MTRP).

[0056] A UE may assume that it sends separate CSI reports (CSI reports) for different TRPs, each for each TRP. Such CSI feedback may be called separate feedback, separate CSI feedback, etc. In this disclosure, “separate” may be interpreted as “independent.”

[0057] From Rel.17 NR onward, MAC CE / DCI is expected to support beam instruction to TCI states associated with different PCIs. Furthermore, from Rel.18 NR onward, MAC CE / DCI is expected to support instruction to change serving cells to cells with different PCIs.

[0058] (Timing Advance Group) When using multiple TRPs, the distance between the UE and each TRP may differ. Multiple TRPs may be contained within the same cell (e.g., a serving cell). Alternatively, some TRPs may correspond to a serving cell, while others correspond to non-serving cells. In this case, it is conceivable that the distance between each TRP and the UE will differ.

[0059] In existing systems, the transmission timing of UL (Uplink) channels and / or UL signals (UL channels / signals) is adjusted by Timing Advance (TA). The reception timing of UL channels / signals from different user terminals (UEs) is adjusted at the base station (TRP: Transmission and Reception Point, also known as gNB: gNodeB, etc.).

[0060] The UE may control the timing of UL transmission by applying a timing advance (multiple timing advance) for each pre-configured Timing Advance Group (TAG).

[0061] When applying multiple timing advances, Timing Advance Groups (TAGs) are supported, categorized by transmission timing. 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.

[0062] When applying Multiple Timing Advance, the UE can independently adjust the transmission timing of the cells belonging to each TAG, allowing the radio base station to synchronize the uplink signal reception timing from the UE, even when using multiple cells.

[0063] TAGs (for example, serving cells belonging to the same TAG) may be defined by higher-level parameters. The same timing advance value may be applied to serving cells belonging to the same TAG. The timing advance group containing a MAC entity's SpCell may be called the primary timing advance group (PTAG), and the other TAGs may be called secondary timing advance groups (STAG).

[0064] In existing systems (e.g., Rel.16 NR), a maximum of four TAG settings are supported per cell group (e.g., MCG / SCG) (see Figure 3). Figure 3 shows a case where three TAGs are set for a cell group containing SpCell and SCell#1~#4. Here, 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 belong to the third TAG (TAG#2).

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

[0066] A MAC CE for timing advance commands (TAC MAC CE) may be configured to include a field for the timing advance group index (e.g., TAG ID) and a field for the timing advance command (see Figure 4).

[0067] On the other hand, in future wireless communication systems, it is conceivable that different TAGs (or TAG-IDs) may be set for one or more TRPs corresponding to a given cell (or CC). Alternatively, it is conceivable that different TRPs corresponding to a given cell may share a common TAG. Furthermore, it is conceivable that a MAC CE for TA commands may apply to only one TRP, or that a MAC CE for TA commands may apply to multiple TRPs.

[0068] Alternatively, different TRPs (Traffic Rate Programs) may use different TAGs for different cells, or they may share a common TAG. For example, in intercell mobility, it is conceivable that UL transmissions could be controlled based on common / different timing advances for serving cells (or serving cell TRPs) and non-serving cells (or non-serving cell TRPs).

[0069] Thus, MIMO versions Rel.18 and later are expected to support two timing advances (TAs) for two TRPs in multi-TRP operation using multiple DCIs.

[0070] If TAGs are set / controlled on a TRP basis, a time alignment timer (e.g., timeAlignmentTimer) may be set for each TRP. The time alignment timer may control the time at which a MAC entity considers a serving cell belonging to an associated TAG to be uplink time aligned. For example, a time alignment timer may be set by the RRC to maintain UL time alignment.

[0071] A time alignment timer (e.g., timeAlignmentTimer) may be maintained for UL time alignment. In Rel.17, a time alignment timer (e.g., timeAlignmentTimer) corresponds to each 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 each indicated timing advance group (e.g., TAG).

[0072] The MAC entity receives the TAC MAC CE and a predetermined value (N) between it and the indicated TAG. TA If the specified value (N) is maintained, apply the timing advance command to the specified TAG, or start or restart the time alignment timer associated with the specified TAG. TA ) may also be a timing advance between DL and UL.

[0073] The behavior when the time alignment timer expires may be defined separately for PTAG and STAG. Furthermore, the timing advance group (TAG) containing the MAC entity's SpCell may be called the primary timing advance group (PTAG), and the other TAGs may be called secondary timing advance groups (STAG).

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

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

[0076] [Operation for specified PTAG] If the time alignment timer is associated with the PTAG, • Flushes all HARQ buffers in all serving cells. • If configured, notify RRC to release PUCCH for all serving cells. • If configured, notify RRC to release the SRS. • Clear all configured DL (Download) and UL (Ultimate Load) allocations. Clear the PUSCH resources for semi-persistent CSI reporting. • Complete all time alignment timers during your run. • All TAGs N TA Maintain.

[0077] [Operation for specified STAG] If a time alignment timer is associated with a STAG, then for all serving cells belonging to that TAG, • Flushes all HARQ buffers. • If configured, notify RRC to release PUCCH. • If configured, notify RRC to release the SRS. • Clear all configured DL and UL assignments. Clear the PUSCH resources for semi-persistent CSI reporting. • N of the relevant TAG TA Maintain.

[0078] (TA control per TRP / panel) As mentioned above, when communicating using multiple transmit / receive points (e.g., TRPs) / panels, it is also conceivable that timing advances may need to be controlled for each TRP / panel.

[0079] For example, a TA may be applied to each TRP (or instructions may be given on a TRP TA basis). For example, at least one of the following options may be applied.

[0080] [Option 1] A different TAG-ID may be set for each TRP, and a different MAC CE for TA commands may be set for each TRP. Each TAG may maintain a time alignment timer for UL time alignment.

[0081] [Option 2] Different TRPs may share a TAG. A MAC CE for a TA command may be applied to only one TRP. The UE applies different TAs to other TRPs. For example, the UE may adjust the TA value for other TRPs (e.g., TRP#1) by a TA offset (TA_TRP_offset) based on the TA for TRP#0 (TA_TRP#0).

[0082] In this case, only one time alignment timer may exist for the UL time alignment of multiple TRPs. This may mean that the UL time alignment of multiple TRPs may be maintained or lost simultaneously.

[0083] [Option 3] There may be only one TAG. The MAC CE for the TA command may be applied to multiple serving TRPs for the UE.

[0084] [Option 4] There may be only one TAG. MAC CEs for TA commands received on a TRP / CW / PDSCH / DMRS port group may be applied to the same TRP / CW / PDSCH / DMRS port group of the TAG. Each TRP / CW / PDSCH / DMRS port group of the TAG maintains a time alignment timer for UL time alignment.

[0085] Thus, in Rel.18 and later, it is anticipated that multiple timing advances will be supported in multi-TRP (e.g., multi-TRP using multi-DCI). For example, multiple (e.g., two) timing advances may be supported for multi-TRP using multi-DCI (e.g., two TRPs). Furthermore, the application of multiple timing advances to multi-TRP may be supported in intra-cell / inter-cell multi-DCI multi-TRP scenarios, or in multiple frequency ranges (e.g., FR1 and FR2).

[0086] If the application / configuration of timing advances per TRP is supported, the question arises as to how to control the timing advance. For example, the question becomes how to control the events / conditions that trigger random access channel procedures (Case 1).

[0087] Alternatively, if TRP-based timing advance application / setting is supported, the question arises as to how to control the application of timing advance commands instructed by a given MAC CE (e.g., MAC RAR) (Case 2 / 3). Alternatively, if TRP-based timing advance application / setting is supported, the question arises as to how to control the application of time alignment timers (Case 4).

[0088] Alternatively, if the application / setting of timing advances on a TRP basis is supported, the issue becomes how to control the selection of random access resources in the random access procedure used to control the timing advance (Case 5).

[0089] The inventors focused on cases 1 to 5 when the application / setting of timing advance in TRP units is supported, and considered timing advance control for at least one of cases 1 to 5, thereby conceiving this embodiment.

[0090] The embodiments of this disclosure will be described in detail below with reference to the drawings. Each wireless communication method according to the embodiments may be applied individually or in combination.

[0091] In this disclosure, "A / B" and "at least one of A and B" may be interpreted as mutually exclusive. In this disclosure, "A / B / C" may mean "at least one of A, B, and C".

[0092] In this disclosure, terms such as activate, deactivate, indicate, select, configure, update, and determine may be interpreted interchangeably. In this disclosure, terms such as support, control, controllable, operate, and operable may be interpreted interchangeably.

[0093] In this disclosure, Radio Resource Control (RRC), RRC parameters, RRC messages, higher-layer parameters, fields, Information Elements (IE), settings, etc., may be interpreted interchangeably. In this disclosure, Medium Access Control elements (MAC Control Element (CE)), update commands, activation / deactivation commands, etc., may be interpreted interchangeably.

[0094] In this disclosure, the upper-layer signaling may be, for example, Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information, or a combination thereof.

[0095] In this disclosure, MAC signaling may include, for example, MAC Control Elements (MAC CEs) and MAC Protocol Data Units (PDUs). Broadcast information may include, for example, Master Information Blocks (MIBs), System Information Blocks (SIBs), Remaining Minimum System Information (RMSIs), and Other System Information (OSIs).

[0096] In this disclosure, physical layer signaling may include, for example, Downlink Control Information (DCI) and Uplink Control Information (UCI).

[0097] In this disclosure, terms such as index, identifier (ID), indicator, and resource ID may be interpreted interchangeably. In this disclosure, terms such as sequence, list, set, group, cluster, and subset may be interpreted interchangeably.

[0098] In this disclosure, the terms used include: panel, UE panel, panel group, beam, beam group, precoder, Uplink (UL) transmit entity, Transmission / Reception Point (TRP), base station, Spatial Relation Information (SRI), spatial relationship, 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 relationship group, Code Division Multiplexing (CDM) group, reference signal group, CORESET group, Physical Uplink Control Channel (PUCCH) groups, PUCCH resource groups, resources (e.g., reference signal resources, SRS resources), resource sets (e.g., reference signal resource sets), CORESET pools, 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 assumptions, etc., may be interpreted interchangeably.

[0099] Furthermore, the spatial relationship information Identifier (ID) (TCI state ID) and spatial relationship information (TCI state) may be interpreted as mutually exclusive. "Spatial relationship information" may be interpreted as mutually exclusive as "a set of spatial relationship information," "one or more spatial relationship information," etc. TCI state and TCI may be interpreted as mutually exclusive.

[0100] (Wireless communication method) If timing advances can be applied / configured for each TRP (or per TRP), the UE controls UL transmissions in each TRP based on the timing advance corresponding to each TRP (or the timing advance group to which each TRP belongs).

[0101] Information regarding the TRP corresponding to each serving cell (e.g., TRP index / TRP ID) may be set / instructed to the UE by the base station using RRC / MAC CE / downlink control information. The UE may also receive relevant information regarding the timing advance corresponding to each TRP (e.g., information regarding TA value / timing advance command / time alignment timer, etc.) from the base station.

[0102] In this disclosure, information relating to a TRP (e.g., TRP index / TRP ID) may be interpreted as a control resource set pool index (e.g., CORESETPoolIndex) or a new ID / predetermined ID. The new ID / predetermined ID may be a new ID to which different TAs are applied to UL transmissions associated with different IDs. For example, setting multiple (e.g., two) TRPs for a serving cell may mean setting multiple (e.g., two) CORESET pool indexes, predetermined IDs, or predetermined parameters (e.g., higher-layer parameters) for a serving cell.

[0103] This embodiment may be applied to both intra-cell multi-TRP and inter-cell multi-TRP.

[0104] In a multi-TRP within a cell, multiple TRPs (or the activated TCI states of multiple TRPs) may be associated with the same cell ID. The cell ID may be the physical cell ID (PCI).

[0105] In inter-cell multi-TRP, multiple TRPs (or the activated TCI states of multiple TRPs) may be associated with different cell IDs (e.g., PCIs). For example, in inter-cell multi-TRP, two TRPs may be interpreted as two TRPs each associated with two PCIs.

[0106] If the application / setting of timing advance is supported for each TRP (or per TRP), each TRP may belong to a different TAG. Multiple TRPs in a serving cell (e.g., two TRPs) may each belong to two TAGs. A TAG may contain multiple TRPs from multiple serving cells. All TRPs / serving cells within a TAG apply / maintain the same timing advance (TA) / same time alignment timer.

[0107] In this disclosure, a TAG may contain one or more sub-TAGs. For example, two TRPs of a serving cell may each belong to two sub-TAGs and also to one TAG. A sub-TAG may contain multiple TRPs from multiple serving cells. All TRPs / serving cells within a sub-TAG apply / maintain the same timing advance (TA) / same time alignment timer.

[0108] <First Embodiment> The first embodiment describes events / conditions that trigger random access channel operation when timing advance application / setting is supported for each TRP (or on a per-TRP basis).

[0109] When the UE applies / controls timing advances on a TRP basis, it may determine that a random access procedure is triggered based on predetermined conditions. These predetermined conditions may be called events.

[0110] A random access procedure (e.g., Random access procedure) may be interpreted as a RACH procedure (e.g., RACH procedure), RACH transmission, or PRACH transmission. An event that triggers a random access channel procedure may be interpreted as a trigger event, trigger condition, or condition.

[0111] The UE may initiate a random access procedure (or send a PRACH) if it determines that a random access procedure is triggered according to a predetermined event (or condition). The predetermined event may be a new event not supported in existing systems (e.g., Rel. 17 or earlier). For example, a random access procedure may be triggered based on at least one of the following options 1-1 to 1-2.

[0112] [Option 1-1] Assume that multiple TRPs are configured for a serving cell, and that multiple timing advances are supported / configured / applied to the multiple TRPs. In such a case, the triggering of a random access procedure may be controlled based on the UL synchronization status (e.g., UL synchronized status) of at least one TRP / specified TRP.

[0113] In this disclosure, a multi-TRP may, for example, consist of two TRPs. In this case, two timing advances may be set separately for the two TRPs. The number of configurable / supportable TRPs and timing advances is not limited to this. The number of configurable / supported TRPs and timing advances may be the same or different.

[0114] The UE may determine that a random access procedure (e.g., RACH) is triggered if multiple timing advances are supported / configured / applied to a multi-TRP and the UL synchronization status of the cell's TRP is asynchronous (e.g., non-synchronized).

[0115] The UL synchronization status of a TRP being asynchronous (e.g., non-synchronized) may mean that the time alignment timer (e.g., time alignment timer) of the TRP (or the TAG to which the TRP belongs) has expired.

[0116] 《Alt.1-1-1》 A RACH may be triggered if the UL synchronization status of any one of the cell's multiple TRPs becomes asynchronous (see Figure 5A). For example, if TRP#1 and TRP#2 are configured for a serving cell, the UE may determine that a RACH will be triggered if the UL synchronization status of at least one of TRP#1 and TRP#2 becomes asynchronous, and send a PRACH.

[0117] In the case of inter-cell multi-TRP (e.g., inter-cell M-TRP), RACH may be triggered when the UL synchronization status of at least one TRP, such as TRP#1 corresponding to a serving cell and TRP#2 corresponding to a non-serving cell, becomes asynchronous.

[0118] 《Alt.1-1-2》 A RACH may be triggered if the UL synchronization status of a specific TRP among several TRPs in a cell is asynchronous (see Figure 5B). The specific TRP may be, for example, a TRP with a specific ID (e.g., TRP ID=0 (or TRP ID=1)). In Figure 5B, TRP#1 corresponds to the specific TRP, and the UE may determine that a RACH is triggered when the UL synchronization status of TRP#1 becomes asynchronous. On the other hand, the UE does not have to determine that a RACH is triggered when the UL synchronization status of TRP#2 becomes asynchronous (or does not have to request the sending of a PRACH).

[0119] Alternatively, in the case of inter-cell multi-TRPs (e.g., inter-cell M-TRPs), a particular TRP may be a TRP associated with the PCI (Physical Cell ID) of the serving cell.

[0120] [Options 1-2] If multiple TRPs are configured for a serving cell and multiple timing advances are supported / configured / applied to the multiple TRPs, RACH may be triggered to establish the cell's TRP time alignment. In other words, the UE / base station may control the establishment of the cell's TRP time alignment by triggering a random access procedure.

[0121] 《Alt.1-2-1》 RACH may be triggered to establish time alignment for any one of the cell's multiple TRPs. In other words, a UE / base station may trigger RACH to establish time alignment for any one of the cell's TRPs.

[0122] 《Alt.1-2-2》 RACH may be triggered to establish time alignment for a specific TRP among several TRPs in a cell. In other words, a UE / base station may trigger RACH to establish time alignment for a specific TRP in a cell. The specific TRP may be, for example, a TRP with a specific ID (e.g., TRP ID=0 (or TRP ID=1)).

[0123] In the case of inter-cell multi-TRP (e.g., inter-cell M-TRP), a particular TRP may be a TRP associated with the PCI (Physical Cell ID) of a serving cell, or a TRP associated with the PCI (Physical Cell ID) of a non-serving cell.

[0124] Thus, even when timing advance application / setting is supported for each TRP, the UL synchronization state or the establishment of time alignment for each TRP can be properly achieved by controlling the events / conditions for triggering random access procedures on a TRP-by-TRP basis.

[0125] <Second Embodiment> A second embodiment describes the instruction / application of a timing advance command (e.g., TAC) when the application / setting of timing advance is supported for each TRP (or on a per-TRP basis). The second embodiment may be applied in combination with the first embodiment. For example, the RAR in the second embodiment may be a response signal corresponding to a RACH transmission triggered in the first embodiment, or a response signal corresponding to other RACH transmissions transmitted under other conditions.

[0126] The UE may receive a TAC in a random access response message (e.g., a RAR message) for a serving cell belonging to the TAG, or in a message B (e.g., an MSGB) for a special cell (e.g., a SpCell). If the MAC entity does not select a random access preamble from among collision-based random access preambles (e.g., a contention-based Random Access Preamble), the TAC for that TAG may be applied. Otherwise, if the time alignment timer associated with that TAG is not running, the TAC for that TAG may be applied.

[0127] Assume that the UE receives a TA command in the RAR for a serving cell where multiple TRPs are configured, and that multiple (e.g., two) timing advances are supported / configured / applied to the multiple TRPs. In such a case, at least one of the following options 2-1 to 2-3 may apply.

[0128] [Option 2-1] In a Random Access Response (RAR), one TAC may be indicated and applied to multiple TRPs (e.g., two TRPs) in the serving cell. If a TAC is indicated by a response signal to a PRACH transmission triggered based on a predetermined event / condition, the UE may apply that TAC to multiple TRPs in common (see Figure 6A).

[0129] For example, if TRP#1 and TRP#2 are set for a serving cell and one TAC is specified by RAR, the TAC specified by RAR may be applied to both TRP#1 and TRP#2.

[0130] In this case, a single TAC may be applied to the Timing Advance Group (TAG) / Sub-TAG to which multiple TRPs (TRP#1 / TRP#2) of the serving cell belong. For example, if the UE has a first TRP#1 belonging to a first TAG#1 and a second TRP#2 belonging to a second TAG#2, it applies the TAC specified in the RAR to the first TAG#1 and the second TAG#2.

[0131] Alternatively, if the first TRP#1 belongs to the first sub-TAG#1 and the second TRP#2 belongs to the second sub-TAG#2, the UE applies the TAC specified in the RAR to the first sub-TAG#1 and the second sub-TAG#2. Note that the first sub-TAG#1 and the second sub-TAG#2 may belong to the same TAG.

[0132] [Option 2-2] In a RAR, multiple (e.g., two) TACs may be indicated, and these multiple TACs may be applied to multiple TRPs (e.g., two TRPs) in the serving cell, respectively. If two TACs (TAC#1 and TAC#2) are indicated by a response signal to a PRACH transmission triggered based on a predetermined event / condition, the UE may apply these two TACs to the two TRPs, respectively (see Figure 6B).

[0133] For example, if TRP#1 and TRP#2 are set for a serving cell, and RAR indicates two TAC#1 and TAC#2, the UE may apply TAC#1 to TRP#1 and TAC#2 to TRP#2.

[0134] In this case, the two TACs may be applied to the TAGs / sub-TAGs of multiple TRPs in the serving cell, respectively. For example, if the first TRP#1 belongs to the first TAG#1 and the second TRP#2 belongs to the second TAG#2, the UE will apply the first TAC#1, as instructed in the RAR, to the first TAG#1 and the second TAC#2 to the second TAG#2.

[0135] Alternatively, if the first TRP#1 belongs to the first sub-TAG#1 and the second TRP#2 belongs to the second sub-TAG#2, the UE applies TAC#1, as instructed in the RAR, to the first sub-TAG#1 and TAC#2 to the second sub-TAG#2. Note that the first sub-TAG#1 and the second sub-TAG#2 may belong to the same TAG.

[0136] In the case of inter-cell multi-TRP, for example, TRP#1 may be set for a serving cell and TRP#2 for a non-serving cell, and RAR may instruct two TAC#1 and TAC#2. In this case, the UE may apply TAC#1 to TRP#1 and TAC#2 to TRP#2.

[0137] Figure 7A shows an example of a RAR (e.g., MAC RAR) used to direct two TACs. A MAC RAR may also be called a MAC payload for RAR (e.g., MAC payload for RAR).

[0138] The MAC RAR shown in Figure 7A is an example that includes TAC#1 corresponding to TRP#1 and TAC#2 corresponding to TAR#2. Note that the MAC CE configuration shown in Figure 7A is just one example, and the number of bits in the TAC field, the position / order of the TAC field, or the position / order of the reserved bits (R) are not limited to this.

[0139] The MAC CE (MAC RAR) shown in Figure 7A and the MAC CE supported by existing systems (e.g., Rel. 17 or earlier) (see Figure 7B) may be switched between and applied. The UE may determine which MAC CE to receive based on the settings of higher layer parameters, etc. Alternatively, the UE may determine which MAC CE to receive based on the MAC header, etc.

[0140] It may be indicated whether two TA values ​​are valid, or whether only one TA value (for example, a TA value for a specific TRP) is valid.

[0141] Figures 8A and 8B illustrate other examples of RARs (e.g., MAC RARs) used to indicate two TACs. Specifically, Figures 8A and 8B show cases where a field (P field) indicating whether or not two TAC fields exist is included in the MAC RAR.

[0142] Figure 8A shows that the P field consists of 1 bit, and this P field indicates either the presence of two TAC fields (e.g., P=0) or the presence of only one TAC field (e.g., P=1). Alternatively, P=1 may indicate the presence of two TAC fields, and P=0 may indicate the presence of only one TAC field.

[0143] Figure 8B shows a case where the P field indicates the presence (or absence) of two TAC fields and the TRP index. The P field may be set with multiple bits (e.g., 2 bits). For example, P=00 may mean that two TAC fields exist. P=01 may mean that one TAC field exists and is applied to the first TRP (e.g., TRP ID=0). P=10 may mean that one TAC field exists and is applied to the second TRP (e.g., TRP ID=1). P=11 may be reserved. Note that the meaning of each code point in the P field (P=00 / 01 / 10 / 11) may be changed as appropriate.

[0144] [Options 2-3] In RAR, one TAC may be indicated and applied to one of several TRPs (e.g., two TRPs) in the serving cell. If one TAC is indicated by a response signal to a PRACH transmission triggered based on a predetermined event / condition, the UE may apply that one TAC to one of two TRPs (see Figure 9A).

[0145] For example, if TRP#1 and TRP#2 are set for a serving cell and one TAC is specified by RAR, the TAC specified by RAR may be applied to either TRP#1 or TRP#2.

[0146] In this case, one TAC may be applied to the TAG / sub-TAG to which one of the serving cell's multiple TRPs belongs. For example, if the first TRP#1 belongs to the first TAG#1 (or sub-TAG#1) and the second TRP#2 belongs to the second TAG#2 (or sub-TAG#2), the UE applies the TAC indicated in the RAR to either the first TAG#1 (or sub-TAG#1) or the second TAG#2 (or sub-TAG#2).

[0147] When applying one TAC specified in RAR (e.g., MAC RAR) to one of two TRPs, the TA (or TA value) to be applied to the other TRP may be determined based on a predetermined rule. For example, at least one of the following options 2-3-1 to 2-3-2 may be applied.

[0148] 《Option 2-3-1》 The TAs of other TRPs may be indicated by TACs included in other MAC RARs. For example, a UE may receive information about a first TAC#1 applicable to a first TRP#1 (or a first TAG#1 to which the first TRP#1 belongs) and information about a second TAC#2 applicable to a second TRP#2 (or a second TAG#1 to which the second TRP#2 belongs) in different MAC RARs (see Figure 9B).

[0149] 《Option 2-3-2》 The timing advances of other TRPs may be indicated by other MAC CEs (e.g., MAC CEs other than MAC RAR). For example, one TAC indicated by RAR (e.g., MAC RAR) may be applied to TRP#1, and information indicated by other MAC CEs may be applied to TRP#2 to control the timing advance of each TRP.

[0150] [[Option 2-3-2-1]] Other MAC CEs of TRP TA This may be indicated. For example, another MAC CE may be reused, such as a MAC CE for a timing advance command (e.g., an Absolute Timing Advance Command MAC CE). In this case, the TRP index may be indicated using the reserve bits (at least one reserve bit) included in the MAC CE for the timing advance command (see Figure 10).

[0151] [[Option 2-3-2-2]] TAC (for example, N) is specified in RAR. TA The offset for ) may be indicated by other MAC CEs. In this case, the TA determined based on the TAC included in the RAR and other MAC CEs may be applied to the TAG / sub-TAG to which the serving cell's TRP (e.g., other TRPs) belongs.

[0152] The UE determines the TAC (or TA) to apply to the first TRP#1 based on the TAC indicated by the MAC RAR. The UE may also determine the TAC (or TA) to apply to the second TRP#2 based on the TAC indicated by the MAC RAR and information indicated by other MAC CEs (e.g., offsets).

[0153] <Third Embodiment> A third embodiment describes how to determine which TAC (e.g., one TAC) is applied to a TRP of a serving cell when a TAC indicated by the RAR is applied to that TRP. For example, the third embodiment may be applied in combination with option 2-3 of the second embodiment.

[0154] The UE receives a TAC via RAR for a serving cell configured with multiple TRPs, and if two TAs are supported for that multiple TRP, it applies the TAC indicated in RAR to one of the TRPs in the serving cell. The TRP to which the TAC indicated in RAR is applied (e.g., one TRP) may be determined based on at least one of the following options 3-1 to 3-5.

[0155] [Option 3-1] A TRP (e.g., a specific TRP) to which a single TAC indicated by RAR applies may be defined in advance in the specification. A specific TRP may be, for example, a TRP with a specific ID (e.g., TRP ID=0 or TRP ID=1).

[0156] If inter-cell multi-TRP is supported / configured, a specific TRP may be a TRP associated with a specific cell ID (or a specific physical cell ID). The specific cell ID may be the cell ID of the serving cell (e.g., serving cell PCI).

[0157] [Option 3-2] A specific TRP to which a single TAC indicated by a RAR applies may also be indicated by a MAC RAR. For example, a specific TRP (e.g., a TRP index) may be indicated using the reserved bits of a MAC RAR supported by an existing system (e.g., Rel. 17 or earlier) (see Figure 11A).

[0158] Figure 11A shows an example of a RAR (e.g., MAC RAR) used for TAC instructions and TRP instructions to which said TAC applies.

[0159] The MAC RAR shown in Figure 11A is an example that includes one TAC field and a field (in this case, the X field) that indicates the TRP to which the TAC field applies. Note that the MAC CE configuration shown in Figure 11A is just one example, and the number of bits in the TAC field, the position / order of the TAC field, or the position / order of the field used to indicate the TRP (the X field) are not limited to this.

[0160] The X field may indicate the TRP index. For example, X=0 may indicate that TAC is applied to the TRP with TRP ID=0, and X=1 may indicate that TAC is applied to the TRP with TRP ID=1. Alternatively, X=1 may indicate that TAC is applied to the TRP with TRP ID=0, and X=0 may indicate that TAC is applied to the TRP with TRP ID=1.

[0161] The MAC CE (MAC RAR) shown in Figure 11A and the MAC CE supported by existing systems (e.g., Rel. 17 or earlier) (see Figure 11B) may be switched between and applied. The UE may determine which MAC CE to receive based on the settings of higher layer parameters, etc. Alternatively, the UE may determine which MAC CE to receive based on the MAC header, etc.

[0162] [Option 3-3] In a RACH (e.g., PDCCH ordered RACH) indicated by a PDCCH (or PDCCH order), a specific TRP may be indicated by the PDCCH order. For example, a specific TRP (e.g., TRP index) may be indicated using reserve bits within the PDCCH order. The UE applies the TAC indicated by the response signal to the PRACH transmitted based on the PDCCH order to the TRP indicated by the PDCCH.

[0163] For inter-cell multi-TRPs (e.g., inter-cell M-TRPs), reserve bits in PDCCH order may be used to indicate serving or non-serving cells. A RACH indicated by PDCCH (e.g., PDCCH ordered RACH) and the corresponding RAR may be applied to the TRP of the serving or non-serving cell indicated in PDCCH.

[0164] [Options 3-4] In a RACH indicated by a PDCCH (or PDCCH order), the TRP index may be associated with the CORESET / TCI state of the PDCCH. The RACH indicated by the PDCCH and the corresponding RAR may be applied to the TRP associated with the CORESET / TCI state of the PDCCH.

[0165] For example, if DCI#1 (PDCCH#1) associated with CORESET pool index #0 triggers RACH (e.g., PDCCH ordered RACH), the specific TRP may be the TRP corresponding to CORESET pool index #0 (e.g., TRP#0). If DCI#2 (PDCCH#2) associated with CORESET pool index #1 triggers RACH (e.g., PDCCH ordered RACH), the specific TRP may be the TRP corresponding to CORESET pool index #1 (e.g., TRP#1).

[0166] For inter-cell multi-TRPs (e.g., inter-cell M-TRPs), serving cells or non-serving cells may be associated with the CORESET / TCI state of the PDCCH. A RACH (e.g., PDCCH ordered RACH), the corresponding RAR, and the TRP of the serving or non-serving cell associated with the CORESET / TCI state of the PDCCH may be applied.

[0167] [Options 3-5] A specific TRP index may be associated with an SSB / CSI-RS / RACH preamble index (e.g., ra-PreambleIndex) / PRACH occasion. The TAC indicated in the RAR may be applied to the TRP associated with the SSB / CSI-RS / ra-PreambleIndex / PRACH occasion selected in the Random Access Resource Selection procedure (e.g., Random Access Resource selection procedure).

[0168] The association between the TRP index and the SSB / CSI-RS / ra-PreambleIndex / PRACH occasion may be defined in the specification beforehand, or it may be set from the base station to the UE by higher-layer parameters.

[0169] For inter-cell multi-TRPs (e.g., inter-cell M-TRPs), serving cells or non-serving cells may be associated with SSB / CSI-RS / ra-PreambleIndex / PRACH occasions. The TACs indicated in the RAR may be applied to the TRPs of serving cells or non-serving cells associated with SSB / CSI-RS / ra-PreambleIndex / PRACH occasions selected in a random access resource selection procedure (e.g., a random access resource selection procedure).

[0170] <Fourth Embodiment> A fourth embodiment describes the UE behavior when one or more (e.g., two) time alignment timers are maintained / applied / configured for multiple (e.g., two) TRPs. For example, the fourth embodiment may be applied in combination with each of the options of the second embodiment.

[0171] [Case 4-1] This assumes that RAR specifies one TAC and that TAC is applied to multiple (e.g., two) TRPs (e.g., Option 2-1), or that RAR specifies two TACs and that two TACs are each applied to multiple (e.g., two) TRPs (Option 2-2). It also assumes that one time alignment timer is maintained (e.g., maintained) for two TRPs in a serving cell. Note that "maintain" may be interpreted as "apply" or "set". In inter-cell multi-TRP, the two TRPs in a serving cell may be interpreted as the TRP of the serving cell and the TRP of the non-serving cell.

[0172] In this case, the UE may control the serving cell's time alignment timer to start or restart when it receives a TAC via RAR. The serving cell's time alignment timer may be interpreted as the time alignment timer of the TAG to which the serving cell belongs.

[0173] In other words, if the UE receives a TAC via RAR, it may start or restart the time alignment timers for multiple TRPs.

[0174] [Case 4-2] Assume that RAR specifies one TAC and that TAC is applied to multiple (e.g., two) TRPs (e.g., Option 2-1), or that RAR specifies two TACs and those two TACs are each applied to multiple (e.g., two) TRPs (Option 2-2). Also assume that two time alignment timers are maintained (e.g., maintained) for two TRPs in a serving cell.

[0175] In this case, when the UE receives a TAC via RAR, it may control the two time alignment timers corresponding to the two TRPs of the serving cell to start or restart them. The time alignment timers corresponding to the TRPs of the serving cell may be interpreted as the time alignment timers corresponding to the TAG / sub-TAG to which the TRPs of the serving cell belong.

[0176] [Case 4-3] Assume that one TAC is indicated by a RAR and that TAC is applied to one of several (e.g., two) TRPs, and the TAs of the other TRPs are indicated by the TACs of other MAC RARs (e.g., Option 2-3-1). Also assume that one time alignment timer is maintained for two TRPs in a serving cell.

[0177] In this case, if the UE receives the TAC via RAR, it may apply at least one of the following options 4-3-1 to 4-3-2.

[0178] 《Option 4-3-1》 If the RAR receives a TAC for one of the two TRPs of a serving cell, the UE may control the time alignment timers of the serving cell (or the two TRPs) to start or restart.

[0179] 《Option 4-3-2》 If the RAR receives a TAC for a specific TRP among the two TRPs of a serving cell, the UE may control the time alignment timer of the serving cell (or the two TRPs) to start or restart.

[0180] A specific TRP may be, for example, a TRP with a specific ID (e.g., TRP ID=0 (or TRP ID=1)). Alternatively, in the case of inter-cell multi-TRPs (e.g., inter-cell M-TRPs), a specific TRP may be a TRP associated with the PCI (Physical Cell ID) of the serving cell.

[0181] [Case 4-4] Assume that one TAC is indicated by a RAR and that TAC is applied to one of several (e.g., two) TRPs, and the TAs of the other TRPs are indicated by the TACs of other MAC RARs (e.g., Option 2-3-1). Also assume that two time alignment timers are maintained for the two TRPs of the serving cell.

[0182] In this case, when the UE receives the TAC of a TRP via RAR, it may control the time alignment timer of that TRP (the time alignment timer of the TAG / sub-TAG to which the TRP belongs) to start or restart. The UE may also control the start or restart of the time alignment timer separately for each TRP.

[0183] [Case 4-5] Assume that RAR directs one TAC and that TAC is applied to one of several (e.g., two) TRPs, and that the TAs of the other TRPs are directed / determined by other MAC CEs (e.g., Option 2-3-2). Also assume that one time alignment timer is maintained for the two TRPs of the serving cell.

[0184] In this case, the UE may control the time alignment timers of the serving cell (or two TRPs) to start or restart when it receives the TAC of the TRP via RAR.

[0185] The UE may control the time alignment timers of the serving cell (or two TRPs) to start or restart when it receives a TAC (or acquires a TA) from another MAC CE. Alternatively, the UE may control the time alignment timers not to take any action when it receives a TAC (or acquires a TA) from another MAC CE (or the UE may not be required to start or restart the time alignment timers).

[0186] [Cases 4-6] Assume that RAR directs one TAC and that TAC is applied to one of several (e.g., two) TRPs, and that the TAs of the other TRPs are directed / determined by other MAC CEs (e.g., Option 2-3-2). Also assume that two time alignment timers are maintained for the two TRPs of the serving cell.

[0187] In this case, the UE may, upon receiving the TAC of a TRP (for example, a specific TRP) via RAR, control the time alignment timer for that TRP (or the time alignment timer of the TAG / sub-TAG to which the TRP belongs) to start or restart. The UE may also control the start or restart of the time alignment timer separately for each TRP.

[0188] If the UE receives a TAC (or acquires a TA) from another MAC CE, it may control the time alignment timer of the other TRP (or the time alignment timer of the TAG / sub-TAG to which the other TRP belongs) to start or restart.

[0189] <Fifth Embodiment> The fifth embodiment describes a random access resource selection rule (e.g., a random access resource selection rule) when RACH is triggered for each TRP (or on a per-TRP basis) and acquisition of TAs for each TRP is supported.

[0190] In collision-based random access (CBRA), SSB / CSI-RS / ra-PreambleIndex / PRACH occasions are selected according to predetermined rules for random access resource selection. These predetermined rules may also be called random access resource selection (e.g., Random Access Resource selection).

[0191] In existing systems, in collision-based random access preamble selection (e.g., contention-based Random Access preamble selection), if at least one SSB exceeds a predetermined threshold (e.g., rsrp-ThresholdSSB), the SSB exceeding that threshold is selected. Otherwise, any SSB is selected.

[0192] A random access preamble is randomly selected with equal probability from the random access preambles associated with the selected SSB and the selected random access preamble group. Additionally, the preamble index (e.g., PREAMBLE_INDEX) is set for the selected random access preamble.

[0193] Furthermore, if SSB is selected, the next available PRACH occasion is determined from the PRACH occasion corresponding to the selected SSB. Alternatively, if CSI-RS is selected, the next available PRACH occasion may be determined from the PRACH occasion according to the selected CSI-RS.

[0194] If RACH is triggered per TRP (or per TRP) and TRP-specific TA acquisition is supported, the SSB / CSI-RS / ra-PreambleIndex / PRACH occasion may be associated with the TRP index. In the case of inter-cell multi-TRP (e.g., inter-cell M-TRP), the SSB / CSI-RS / RACH settings (e.g., RACH configurations) for multiple additional PCI cells may be configured in the UE.

[0195] [Option 5-1] For CBRAs triggered by a PDCCH (or PDCCH order), the TRP index may be indicated by the PDCCH. Alternatively, the TRP index may be associated with the CORESET / TCI state of the PDCCH.

[0196] Random access resources may be determined based on SSB / CSI-RS / ra-PreambleIndex / PRACH occasions associated with a TRP index (or selected from among SSB / CSI-RS / ra-PreambleIndex / PRACH occasions). The TRP index may be indicated by PDCCH or may be a TRP index associated with PDCCH.

[0197] The method for selecting random access resources from SSB / CSI-RS / ra-PreambleIndex / PRACH occasions may be governed by the rules of existing systems (e.g., Rel. 17 or earlier).

[0198] [Option 5-2] For CBRAs triggered by predetermined events / conditions, random access resources may be determined based on the SSB / CSI-RS / ra-PreambleIndex / PRACH occasion associated with the TRP (or selected from among the SSB / CSI-RS / ra-PreambleIndex / PRACH occasions).

[0199] The specified event / condition may be the event / condition shown in the first embodiment. In the first embodiment, the RACH procedure is triggered either because the serving cell's TRP is out of sync or to establish a time alignment with the serving cell's TRP. In such a case, the UE may select a random access resource from among the SSB / CSI-RS / ra-PreambleIndex / PRACH occasions associated with the TRP.

[0200] The method for selecting random access resources from SSB / CSI-RS / ra-PreambleIndex / PRACH occasions may be governed by the rules of existing systems (e.g., Rel. 17 or earlier).

[0201] [Option 5-3] For CBRAs triggered by unsuccessful contention resolution, the random access resource may be determined based on the same TRP applied in the previous random access resource selection.

[0202] For example, consider a scenario where the random access resource in a previous preamble transmission (e.g., a preceding preamble transmission) was selected from among the SSB / CSI-RS / ra-PreambleIndex / PRACH occasions associated with a given TRP. In this case, the random access resource in the CBRA triggered by unsuccessful contention resolution may be determined based on (or selected from) the SSB / CSI-RS / ra-PreambleIndex / PRACH occasions associated with the same TRP as the previous preamble transmission.

[0203] <Supplement> At least one of the embodiments described above may apply only to a UE that has reported or supports a particular UE capability.

[0204] The specific UE capability may represent at least one of the following: • Support for multiple (e.g., two) timing advances for multi-TRPs. • Multiple (e.g., two) timing advances are supported for multi-TRPs within a cell. • Support for multiple (e.g., two) timing advances for inter-cell multi-TRP.

[0205] Furthermore, the specific UE capabilities described above may be capabilities that apply across all frequencies (commonly regardless of frequency), capabilities per frequency (e.g., cell, band, BWP), capabilities per frequency range (e.g., Frequency Range 1 (FR1), FR2, FR3, FR4, FR5, FR2-1, FR2-2), or capabilities per subcarrier spacing (SCS).

[0206] Furthermore, the specific UE capabilities described above may be capabilities that apply across all duplexing schemes (common to all duplexing schemes), or they may be capabilities specific to each duplexing scheme (e.g., Time Division Duplex (TDD), Frequency Division Duplex (FDD)).

[0207] Furthermore, at least one of the embodiments described above may be applied when the UE is configured by upper-layer signaling to provide specific information or specific UE capabilities related to the embodiments described above.

[0208] If the UE does not support at least one of the above-mentioned specific UE capabilities or does not have the above-mentioned specific information configured, the behavior of, for example, Rel.15 / 16 may be applied.

[0209] (Note) The following invention is added with respect to one embodiment of this disclosure.

[0210] [Note 1-1] A terminal having a receiving unit that receives information regarding the timing advance used for the transmitting and receiving points, and a control unit that, if the setting of the timing advance for each transmitting and receiving point is supported, determines the trigger for a random access procedure based on at least one of the uplink synchronization status for each transmitting and receiving point and the establishment of the time alignment for each transmitting and receiving point. [Appendix 1-2] In the case where multiple transmit / receive points are configured for a serving cell, the control unit determines that the random access procedure is triggered when the uplink synchronization status of a particular transmit / receive point becomes asynchronous, as described in Appendix 1-1 of the terminal. [Appendix 1-3] In the case where multiple transmit / receive points are set for a serving cell, the control unit determines that the random access procedure is triggered when establishing a time alignment for a specific transmit / receive point, as described in Appendix 1-1 or Appendix 1-2 of the terminal. [Appendix 1-4] The control unit, when the random access procedure is triggered, selects the random access resources to be used in the random access procedure, taking into consideration the transmit / receive point where the uplink synchronization status becomes asynchronous, or the transmit / receive point where the time alignment timer is established, as described in any of the terminals in Appendix 1-1 to Appendix 1-3.

[0211] [Note 2-1] A terminal comprising: a receiving unit that receives one or more timing advance commands included in a MAC control element (MAC CE) for random access response; and a control unit that, when the application of timing advance on a per-transmit / receive point basis is supported, determines a timing advance to apply to multiple transmit / receive points based on the one or more timing advance commands, or based on the one or more timing advance commands and information indicated by other MAC CEs. [Note 2-2] If the MAC CE for the random access response includes one timing advance command, the control unit applies the one timing advance command to a specific transmit / receive point as described in Appendix 2-1. [Appendix 2-3] The terminal described in Appendix 2-1 or Appendix 2-2, wherein the control unit receives one or more timing advance commands included in the MAC CE for the random access response, and applies one timing advance timer to multiple transmission and reception points. [Appendix 2-4] The terminal described in any of Appendix 2-1 to 2-3, wherein the control unit receives one or more timing advance commands included in the MAC CE for the random access response, and applies different timing advance timers to multiple transmit / receive points.

[0212] (Wireless communication system) The configuration of a wireless communication system according to one embodiment of this disclosure will be described below. In this wireless communication system, communication is performed using any or a combination thereof of the wireless communication methods according to the above embodiments of this disclosure.

[0213] Figure 12 shows an example of a schematic configuration of a wireless communication system according to one embodiment. The wireless communication system 1 (which may also be simply called system 1) may be a system that realizes communication using Long Term Evolution (LTE), 5th generation mobile communication system New Radio (5G NR), etc., as specified by the Third Generation Partnership Project (3GPP).

[0214] Furthermore, the wireless communication system 1 may 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)), and so on.

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

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

[0217] The wireless communication system 1 may include a base station 11 that forms a macrocell C1 with relatively wide coverage, and base stations 12 (12a-12c) located within the macrocell C1 that form a small cell C2 that is narrower than the macrocell C1. User terminals 20 may be located within at least one cell. The arrangement and number of each cell and user terminal 20 are not limited to the configuration shown in the figure. Hereinafter, when base stations 11 and 12 are not distinguished, they will be collectively referred to as base station 10.

[0218] The user terminal 20 may be connected to at least one of the multiple base stations 10. The user terminal 20 may utilize at least one of Carrier Aggregation (CA) using multiple Component Carriers (CC) and Dual Connectivity (DC).

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

[0220] Furthermore, the user terminal 20 may communicate using at least one of the following methods at each CC: Time Division Duplex (TDD) and Frequency Division Duplex (FDD).

[0221] Multiple base stations 10 may be connected by wire (e.g., optical fiber compliant with Common Public Radio Interface (CPRI), X2 interface, etc.) or wireless (e.g., NR communication). For example, if NR communication is used as a backhaul between base stations 11 and 12, base station 11, which is the upstream station, may be called an Integrated Access Backhaul (IAB) donor, and base station 12, which is the relay station, may be called an IAB node.

[0222] Base station 10 may be connected to the core network 30 via other base stations 10 or directly. The core network 30 may include at least one of the following: Evolved Packet Core (EPC), 5G Core Network (5GCN), Next Generation Core (NGC), etc.

[0223] The core network 30 may include network functions (NF) such as User Plane Function (UPF), Access and Mobility Management Function (AMF), Session Management Function (SMF), Unified Data Management (UDM), Application Function (AF), Data Network (DN), Location Management Function (LMF), and Operation, Administration and Maintenance (Management) (OAM). Multiple functions may be provided by a single network node. Furthermore, communication with an external network (e.g., the Internet) may occur via the DN.

[0224] The user terminal 20 may be a terminal that supports at least one of the following communication methods: LTE, LTE-A, 5G, etc.

[0225] In the wireless communication system 1, an orthogonal frequency division multiplexing (OFDM)-based wireless access scheme may be used. 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), etc., may be used in at least one of the downlink (DL) and uplink (UL).

[0226] The wireless access method may also be called a waveform. In wireless communication system 1, other wireless access methods (for example, other single-carrier transmission methods, other multi-carrier transmission methods) may be used for the UL and DL wireless access methods.

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

[0228] Furthermore, in the wireless communication system 1, the uplink channel may include a Physical Uplink Shared Channel (PUSCH), a Physical Uplink Control Channel (PUCCH), a Physical Random Access Channel (PRACH), or the like, all of which are shared by each user terminal 20.

[0229] User data, higher-layer control information, and System Information Blocks (SIBs) are transmitted via PDSCH. User data and higher-layer control information may also be transmitted via PUSCH. Furthermore, Master Information Blocks (MIBs) may be transmitted via PBCH.

[0230] Lower-layer control information may be transmitted by PDCCH. The lower-layer control information may include, for example, Downlink Control Information (DCI) which includes scheduling information for at least one of PDSCH and PUSCH.

[0231] Furthermore, the DCI that schedules PDSCH may be called a DL assignment or DL ​​DCI, and the DCI that schedules PUSCH may be called a UL grant or UL DCI. Furthermore, PDSCH may be interpreted as DL data, and PUSCH may be interpreted as UL data.

[0232] PDCCH detection may utilize a Control Resource Set (CORESET) and a search space. A CORESET corresponds to the resources used to search for DCIs. A search space corresponds to the search area and search method for PDCCH candidates. A single CORESET may be associated with one or more search spaces. The UE may monitor CORESETs associated with a particular search space based on the search space configuration.

[0233] A single search space may correspond to one or more PDCCH candidates corresponding to aggregation levels. One or more search spaces may be referred to as a search space set. In this disclosure, "search space," "search space set," "search space configuration," "search space set configuration," "CORESET," and "CORESET configuration" may be interpreted interchangeably.

[0234] PUCCH may transmit uplink control information (UCI) which includes at least one of the following: channel state information (CSI), delivery acknowledgment (e.g., Hybrid Automatic Repeat reQuest ACKnowledgement (HARQ-ACK), ACK / NACK, etc.), and scheduling request (SR). PRACH may transmit a random access preamble for establishing a connection with the cell.

[0235] In this disclosure, downlinks, uplinks, etc., may be expressed without the prefix "link." Also, the prefix "physical" may be omitted when describing various channels.

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

[0237] 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 SS (PSS, SSS) and PBCH (and DMRS for PBCH) may be called an SS / PBCH block, SS Block (SSB), etc. SS, SSB, etc., may also be called reference signals.

[0238] Furthermore, in the wireless communication system 1, the Uplink Reference Signal (UL-RS) may transmit the Sounding Reference Signal (SRS), Demodulation Reference Signal (DMRS), etc. The DMRS may also be called the User-Specific Reference Signal (UE-specific Reference Signal).

[0239] (base station) Figure 13 shows an example of the configuration of a base station according to one 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 one or more of the control unit 110, transceiver unit 120, transceiver antenna 130, and transmission line interface 140 may be provided.

[0240] In this example, the functional blocks of the characteristic parts of this 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 part described below may be omitted.

[0241] The control unit 110 controls the entire base station 10. The control unit 110 can be composed of a controller, control circuit, etc., as described based on common understanding in the art relating to this disclosure.

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

[0243] The transmitting / receiving 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 transmitting / receiving unit 120 can be composed of a transmitter / receiver, RF circuit, baseband circuit, filter, phase shifter, measurement circuit, transmitting / receiving circuit, etc., as described based on common understanding in the art relating to this disclosure.

[0244] The transmitting / receiving unit 120 may be configured as an integrated transmitting / receiving unit, or it may be composed of a transmitting unit and a receiving unit. The transmitting unit may consist of a transmitting processing unit 1211 and an RF unit 122. The receiving unit may consist of a receiving processing unit 1212, an RF unit 122 and a measuring unit 123.

[0245] The transmitting and receiving antenna 130 can be composed of an antenna described based on common understanding in the art relating to this disclosure, such as an array antenna.

[0246] The transmitting / receiving unit 120 may transmit the downlink channel, synchronization signal, downlink reference signal, etc. The transmitting / receiving unit 120 may also receive the uplink channel, uplink reference signal, etc.

[0247] The transmission / reception unit 120 may form at least one of a transmission beam and a reception beam by using digital beamforming (e.g., precoding), analog beamforming (e.g., phase rotation), or the like.

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

[0249] The transmission / reception 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, digital-to-analog conversion, etc. on the bit string to be transmitted, and output a baseband signal.

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

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

[0252] The transmitting / receiving unit 120 (receiving processing unit 1212) may apply reception processing to the acquired baseband signal, such as analog-to-digital conversion, Fast Fourier Transform (FFT) processing, Inverse Discrete Fourier Transform (IDFT) processing (if necessary), filtering, demapping, demodulation, decoding (may include error correction decoding), MAC layer processing, RLC layer processing, and PDCP layer processing, to acquire user data, etc.

[0253] The transmitting / receiving unit 120 (measurement unit 123) may perform measurements related to 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 also measure received power (e.g., Reference Signal Received Power (RSRP)), reception 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.

[0254] The transmission path interface 140 may send and receive signals (backhaul signaling) with devices included in the core network 30 (e.g., network nodes providing 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.

[0255] In this disclosure, the transmitting and receiving units of the base station 10 may consist of at least one of a transmitting / receiving unit 120, a transmitting / receiving antenna 130, and a transmission path interface 140.

[0256] The transmitting / receiving unit 120 may transmit information regarding the timing advance used for the transmitting / receiving points. The control unit 110 may control a random access procedure that is triggered based on at least one of the uplink synchronization status for each transmitting / receiving point and the establishment of a time alignment for each transmitting / receiving point, if setting a timing advance for each transmitting / receiving point is supported.

[0257] The transmitting / receiving unit 120 may transmit one or more timing advance commands included in the MAC Control Element (MAC CE) for random access response. The control unit 110 may, if the application of timing advance on a per-transmit / receive point basis is supported, control the system to instruct timing advance to be applied to multiple transmit / receive points by using one or more timing advance commands, or by using one or more timing advance commands and information indicated by other MAC CEs.

[0258] (User terminal) Figure 14 shows an example of the configuration of a user terminal according to one embodiment. The user terminal 20 includes a control unit 210, a transmitting / receiving unit 220, and a transmitting / receiving antenna 230. Note that one or more of the control unit 210, the transmitting / receiving unit 220, and the transmitting / receiving antenna 230 may be provided.

[0259] In this example, the functional blocks of the characteristic parts of this 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 part described below may be omitted.

[0260] The control unit 210 controls the entire user terminal 20. The control unit 210 can be composed of a controller, control circuit, etc., as described based on common understanding in the technical field related to this disclosure.

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

[0262] The transmitting / receiving 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 transmitting / receiving unit 220 can be composed of a transmitter / receiver, RF circuit, baseband circuit, filter, phase shifter, measurement circuit, transmitting / receiving circuit, etc., as described based on common understanding in the art relating to this disclosure.

[0263] The transmitting / receiving unit 220 may be configured as an integrated transmitting / receiving unit, or it may be composed of a transmitting unit and a receiving unit. The transmitting unit may consist of a transmitting processing unit 2211 and an RF unit 222. The receiving unit may consist of a receiving processing unit 2212, an RF unit 222 and a measuring unit 223.

[0264] The transmitting and receiving antenna 230 can be composed of an antenna described based on common understanding in the art relating to this disclosure, such as an array antenna.

[0265] The transmitting / receiving unit 220 may receive the downlink channel, synchronization signal, downlink reference signal, etc. The transmitting / receiving unit 220 may also transmit the uplink channel, uplink reference signal, etc.

[0266] The transmission / reception unit 220 may form at least one of a transmission beam and a reception beam by using digital beamforming (e.g., precoding), analog beamforming (e.g., phase rotation), or the like.

[0267] The transmission / reception unit 220 (transmission processing unit 2211) may perform processing of the PDCP layer, processing of the RLC layer (e.g., RLC retransmission control), processing of the MAC layer (e.g., HARQ retransmission control), etc. on data, control information, etc. obtained from the control unit 210, for example, and generate a bit sequence to be transmitted.

[0268] The transmission / reception 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, digital-to-analog conversion, etc. on the bit sequence to be transmitted, and output a baseband signal.

[0269] Whether to apply DFT processing may be based on the setting of transform precoding. For a certain channel (e.g., PUSCH), when transform precoding is enabled, the transmission / reception unit 220 (transmission processing unit 2211) may perform DFT processing as the above transmission processing in order to transmit the channel using the DFT-s-OFDM waveform, or if not, it may not perform DFT processing as the above transmission processing.

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

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

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

[0273] The transmitting / receiving unit 220 (measuring unit 223) may perform measurements related to the received signal. For example, the measuring unit 223 may perform RRM measurement, CSI measurement, etc., based on the received signal. The measuring unit 223 may also 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.

[0274] In this disclosure, the transmitting and receiving units of the user terminal 20 may consist of at least one of a transmitting / receiving unit 220 and a transmitting / receiving antenna 230.

[0275] The transmitting / receiving unit 220 may receive information regarding the timing advance used for the transmitting / receiving points. The control unit 210 may determine whether to trigger the random access procedure based on at least one of the uplink synchronization status for each transmitting / receiving point and the establishment of the time alignment for each transmitting / receiving point, if setting the timing advance for each transmitting / receiving point is supported.

[0276] If multiple transmit / receive points are configured for a serving cell, the control unit 210 may determine that the random access procedure is triggered when the uplink synchronization status of a particular transmit / receive point becomes asynchronous. If multiple transmit / receive points are configured for a serving cell, the control unit 210 may determine that the random access procedure is triggered when establishing time alignment for a particular transmit / receive point. When the random access procedure is triggered, the control unit 210 may select the random access resources to be used in the random access procedure, taking into consideration the transmit / receive points whose uplink synchronization status becomes asynchronous, or the transmit / receive points that establish the time alignment timer.

[0277] The transmitting / receiving unit 220 may receive one or more timing advance commands included in the MAC Control Element (MAC CE) for random access response. The control unit 210 may determine which timing advances to apply to multiple transmitting / receiving points based on one or more timing advance commands, or based on one or more timing advance commands and information indicated by other MAC CEs, if the application of timing advances on a per-transmitting / receiving point basis is supported.

[0278] If the MAC CE for random access response includes one timing advance command, the control unit 210 may apply that one timing advance command to a specific transmit / receive point. If the control unit 210 receives one or more timing advance commands included in the MAC CE for random access response, it may apply one timing advance timer to multiple transmit / receive points. If the control unit 210 receives one or more timing advance commands included in the MAC CE for random access response, it may apply different timing advance timers to multiple transmit / receive points.

[0279] (Hardware configuration) The block diagrams used in the description of the above embodiments show functional units. These functional blocks (components) are realized by any combination of at least one of hardware and software. Furthermore, the method of realizing each functional block is not particularly limited. That is, each functional block may be realized using one device that is physically or logically coupled, or it may be realized using two or more physically or logically separated devices that are directly or indirectly connected (for example, using wired or wireless connections). A functional block may also be realized by combining the above one device or the above multiple devices with software.

[0280] Here, functions include, but are not limited to, judgment, decision, determination, calculation, calculation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, consideration, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating (mapping), and assigning. For example, a functional block (configuration part) that enables transmission may be called a transmitting unit or transmitter. In all cases, as mentioned above, the method of implementation is not particularly limited.

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

[0282] In this disclosure, terms such as apparatus, circuit, device, section, and unit are interchangeable. The hardware configuration of the base station 10 and the user terminal 20 may include one or more of the devices shown in the figure, or it may be configured to omit some of the devices.

[0283] For example, although only one processor 1001 is shown in the diagram, there may be multiple processors. Furthermore, processing may be performed by one processor, or by two or more processors simultaneously, sequentially, or by other means. Note that processor 1001 may be implemented using one or more chips.

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

[0285] The processor 1001 controls the entire computer, for example, by running an operating system. The processor 1001 may be composed of a central processing unit (CPU) that includes interfaces with peripheral devices, control units, arithmetic units, registers, etc. For example, at least a part of the control unit 110 (210) and the transmitting / receiving unit 120 (220) described above may be implemented by the processor 1001.

[0286] Furthermore, the processor 1001 reads programs (program code), 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 accordingly. The program used is one that causes the computer to execute at least a part of the operations described in the above embodiment. 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 other functional blocks may be implemented similarly.

[0287] Memory 1002 is a computer-readable recording medium and may consist of at least one of the following: Read Only Memory (ROM), Erasable Programmable ROM (EPROM), Electrically EPROM (EEPROM), Random Access Memory (RAM), or other suitable storage medium. Memory 1002 may also be called a register, cache, or main memory. Memory 1002 can store executable programs (program code), software modules, etc., for carrying out a wireless communication method according to one embodiment of this disclosure.

[0288] Storage 1003 is a computer-readable recording medium and may consist of at least one of the following: a flexible disk, a floppy disk, a magneto-optical disk (e.g., a compact disk (Compact Disc ROM (CD-ROM)), a digital multipurpose disk, a Blu-ray disk), a removable disk, a hard disk drive, a smart card, a flash memory device (e.g., a card, stick, key drive), a magnetic stripe, a database, a server, or other suitable storage medium. Storage 1003 may also be called an auxiliary storage device.

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

[0290] The input device 1005 is an input device that accepts input from an external source (e.g., a keyboard, mouse, microphone, switch, button, sensor, etc.). The output device 1006 is an output device that outputs to an external source (e.g., a display, speaker, light-emitting diode (LED) lamp, etc.). The input device 1005 and the output device 1006 may be configured as an integrated unit (e.g., a touch panel).

[0291] Furthermore, each device, such as the processor 1001 and memory 1002, is connected by a bus 1007 for communicating information. The bus 1007 may be configured using a single bus, or different buses may be configured for each device.

[0292] 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), and a field programmable gate array (FPGA), and some or all of each functional block may be implemented using such hardware. For example, the processor 1001 may be implemented using at least one of these hardware components.

[0293] (modified version) In addition, terms used in this disclosure and terms necessary for understanding this disclosure may be replaced with terms having the same or similar meanings. For example, channel, symbol, and signal (signal or signaling) may be used interchangeably. Also, a signal may be a message. A reference signal may be abbreviated as RS and may be called a pilot, pilot signal, etc., depending on the applicable standard. Also, a component carrier (CC) may be called a cell, frequency carrier, carrier frequency, etc.

[0294] A wireless frame may consist of one or more periods (frames) in the time domain. Each of these periods (frames) constituting a wireless frame may be called a subframe. Furthermore, a subframe may consist 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.

[0295] Here, the neuralelogy may be communication parameters applied to at least one of the transmission and reception of a signal or channel. The neuralelogy may be, for example, at least one of the following: subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, radio frame configuration, specific filtering processes performed by the transceiver in the frequency domain, or specific windowing processes performed by the transceiver in the time domain.

[0296] A slot may consist of one or more symbols in the time domain (such as Orthogonal Frequency Division Multiplexing (OFDM) symbols or Single Carrier Frequency Division Multiple Access (SC-FDMA) symbols). Alternatively, a slot may be a time unit based on neurology.

[0297] A slot may include multiple mini-slots. Each mini-slot may consist of one or more symbols in the time domain. Mini-slots may also be called sub-slots. Mini-slots may consist of fewer symbols than a slot. A PDSCH (or PUSCH) transmitted in a time unit larger than a mini-slot may be called a PDSCH (PUSCH) mapping type A. A PDSCH (or PUSCH) transmitted using a mini-slot may be called a PDSCH (PUSCH) mapping type B.

[0298] Wireless frames, subframes, slots, minislots, and symbols all represent units of time when transmitting a signal. Wireless frames, subframes, slots, minislots, and symbols may each be referred to by different names. Furthermore, the units of time such as frames, subframes, slots, minislots, and symbols in this disclosure may be interpreted as interchangeable.

[0299] For example, one subframe may be called TTI, multiple consecutive subframes may be called TTI, or one slot or one mini-slot may be called TTI. In other words, at least one of the subframe and TTI may be a subframe (1ms) in existing LTE, a period shorter than 1ms (e.g., 1-13 symbols), or a period longer than 1ms. Note that the unit representing TTI may be called a slot, mini-slot, etc., instead of a subframe.

[0300] Here, TTI refers to, for example, the smallest unit of time for scheduling in wireless communication. For example, in an LTE system, the base station schedules each user terminal to allocate wireless resources (such as the frequency bandwidth and transmission power available to each user terminal) in TTI units. However, the definition of TTI is not limited to this.

[0301] TTI may be a transmission time unit for channel-encoded data packets (transport blocks), code blocks, code words, etc., or it may be a processing unit for scheduling, link adaptation, etc. Given a TTI, the actual time interval (e.g., number of symbols) to which the transport block, code block, code word, etc. are mapped may be shorter than the given TTI.

[0302] Furthermore, if one slot or one mini-slot is referred to as TTI, then one or more TTIs (i.e., one or more slots or one or more mini-slots) may constitute the minimum time unit of scheduling. In addition, the number of slots (number of mini-slots) that constitute the minimum time unit of scheduling may be controlled.

[0303] A TTI with a time length of 1 ms may also be called a normal TTI (TTI in 3GPP Rel.8-12), a long TTI, a normal subframe, a long subframe, or a slot. A TTI shorter than a normal TTI may also be called a shortened TTI, a short TTI, a partial or fractional TTI, a shortened subframe, a short subframe, a mini slot, a sub slot, or a slot.

[0304] Furthermore, long TTIs (e.g., normal TTIs, subframes, etc.) may be interpreted as TTIs with a time length exceeding 1 ms, and short TTIs (e.g., shortened TTIs, etc.) may be interpreted as TTIs with a TTI length less than that of a long TTI but 1 ms or more.

[0305] A Resource Block (RB) is a resource allocation unit in the time domain and frequency domain, and in the frequency domain, it may contain one or more consecutive subcarriers. The number of subcarriers in an RB may be the same regardless of the neurology, for example, 12. The number of subcarriers in an RB may be determined based on the neurology.

[0306] Furthermore, an RB may contain one or more symbols in the time domain and may have the length of one slot, one minislot, one subframe, or one TTI. Each TTI, subframe, etc., may consist of one or more resource blocks.

[0307] One or more RBs may also be called Physical RBs (PRBs), Sub-Carrier Groups (SCGs), Resource Element Groups (REGs), PRB pairs, RB pairs, etc.

[0308] Furthermore, a resource block may consist of one or more resource elements (REs). For example, one RE may be a radio resource area comprising one subcarrier and one symbol.

[0309] A Bandwidth Part (BWP) (also called a partial bandwidth) may represent a subset of consecutive common resource blocks (RBs) for a given neurology in a given carrier. Here, the common RBs may be identified by an index of the RBs relative to the carrier's common reference point. PRBs may be defined and numbered within a BWP.

[0310] A BWP may include UL BWPs (BWPs for UL) and DL BWPs (BWPs for DL). One or more BWPs may be configured within a single carrier for a UE.

[0311] At least one of the configured BWPs may be active, and the UE does not need to assume that it will send or receive a given signal / channel outside of the active BWP. In this disclosure, terms such as "cell" and "carrier" may be read as "BWP".

[0312] The structures described above, such as wireless frames, subframes, slots, minislots, and symbols, are merely illustrative examples. For instance, the number of subframes included in a wireless frame, the number of slots per subframe or wireless frame, the number of minislots within a slot, the number of symbols and RBs included in a slot or minislot, the number of subcarriers included in an RB, and the number of symbols, symbol length, and cyclic prefix (CP) length within a TTI can be varied in various ways.

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

[0314] The names used for parameters and other elements in this disclosure are not restrictive in any way. Furthermore, mathematical formulas and other elements that use these parameters may differ from those expressly disclosed in this disclosure. Various channels (PUCCH, PDCCH, etc.) and information elements can be identified by any suitable name, and therefore, the various names assigned to these various channels and information elements are not restrictive in any way.

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

[0316] Furthermore, information, signals, etc., can be output from upper layers to lower layers and from lower layers to upper layers, or to at least one of the two. Information, signals, etc., may also be input and output via multiple network nodes.

[0317] Input and output information and signals may be stored in a specific location (e.g., memory) or managed using a management table. Input and output information and signals may be overwritten, updated, or appended to. Output information and signals may be deleted. Input information and signals may be transmitted to other devices.

[0318] Information notification is not limited to the embodiments described herein and may be carried out by other means. For example, information notification in this disclosure may be carried out by physical layer signaling (e.g., Downlink Control Information (DCI), Uplink Control Information (UCI)), higher layer signaling (e.g., Radio Resource Control (RRC) signaling, broadcast information (Master Information Block (MIB), System Information Block (SIB)), Medium Access Control (MAC) signaling), other signals, or a combination thereof).

[0319] Physical layer signaling may also be called Layer 1 / Layer 2 (L1 / L2) control information (L1 / L2 control signals), L1 control information (L1 control signals), etc. RRC signaling may also be called RRC messages, for example, RRC Connection Setup messages, RRC Connection Reconfiguration messages, etc. MAC signaling may also be communicated using, for example, MAC Control Element (CE).

[0320] Furthermore, notification of the specified information (for example, notification that "X is the case") is not limited to explicit notification, but may also be made implicitly (for example, by not notifying the specified information or by notifying other information).

[0321] The determination may be made by a value represented by 1 bit (0 or 1), by a boolean value represented as true or false, or by a numerical comparison (for example, a comparison with a predetermined value).

[0322] Software should be broadly interpreted to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, functions, and so on, whether they are called software, firmware, middleware, microcode, hardware description languages, or by any other name.

[0323] Furthermore, software, instructions, information, etc., may be transmitted and received via a transmission medium. For example, if software is transmitted from a website, server, or other remote source using at least one of wired technology (such as coaxial cable, fiber optic cable, twisted pair, or Digital Subscriber Line (DSL)) and wireless technology (such as infrared or microwave), then at least one of these wired and wireless technologies is included in the definition of a transmission medium.

[0324] The terms “system” and “network” as used in this disclosure may be used interchangeably. “Network” may also mean the equipment included in the network (e.g., base stations).

[0325] 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," "antenna port group," "layer," "number of layers," "rank," "resource," "resource set," "resource group," "beam," "beam width," "beam angle," "antenna," "antenna element," and "panel" may be used interchangeably.

[0326] In this disclosure, terms such as "Base Station (BS)", "wireless 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", and "component carrier" may be used interchangeably. Base stations may also be referred to by terms such as macrocell, small cell, femtocell, and picocell.

[0327] A base station can house one or more (e.g., three) cells. If a base station houses multiple cells, the entire coverage area of ​​the base station can be divided into several smaller areas, each of which may also be provided with communication services 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 ​​at least one of the base station and / or base station subsystems that provide communication services in that coverage.

[0328] In this disclosure, the transmission of information by a base station to a terminal may be interpreted as the base station instructing the terminal to perform a control / operation based on said information.

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

[0330] A mobile station may also be called 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 appropriate term.

[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. At least one of the base station and the mobile station may also be a device mounted on a moving object, the moving object itself, etc.

[0332] The term "mobile object" refers to any movable object, regardless of its speed, and naturally includes cases where the mobile object is stationary. Examples of such mobile objects include, but are not limited to, vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, handcarts, rickshaws, ships and other watercraft, airplanes, rockets, satellites, drones, multicopters, quadcopters, balloons, and items carried on them. Furthermore, such mobile objects may be autonomously driven objects operating based on operational commands.

[0333] The mobile entity may be a vehicle (e.g., a car, an airplane), an unmanned mobile entity (e.g., a drone, an autonomous vehicle), or a robot (manned or unmanned). At least one of the base station and the mobile station may be a device that does 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] Figure 16 shows an example of a vehicle according to one 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, an axle 48, an electronic control unit 49, various sensors (including a current sensor 50, a rotation speed sensor 51, a pneumatic 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 consists of, for example, at least one of an engine, a motor, or an engine-motor hybrid. The steering unit 42 includes at least a steering wheel (also called a handle) and is configured to steer at least one of the front wheels 46 and the rear wheels 47 based on the operation of the steering wheel operated by the user.

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

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

[0338] The information service unit 59 consists of various devices for providing (outputting) various types of information such as driving information, traffic information, and entertainment information, including a car navigation system, audio system, speakers, displays, television, and radio, and one or more ECUs that control these devices. The information service unit 59 uses information acquired from external devices via a communication module 60 or the like to provide various types of 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 that accept input from the outside (e.g., keyboard, mouse, microphone, switch, button, sensor, touch panel, etc.) and output devices that perform output to the outside (e.g., display, speaker, LED lamp, touch panel, etc.).

[0340] The driver assistance system unit 64 consists of various devices that provide functions to prevent accidents or reduce the driver's workload, 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 Unit (IMU), Inertial Navigation System (INS)), artificial intelligence (AI) chips, and AI processors, as well as one or more ECUs that control these devices. The driver assistance system unit 64 also transmits and receives various information via the communication module 60 to realize driver 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 sends and receives data (information) via the communication port 63 to 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, axle 48, the microprocessor 61 and memory (ROM, RAM) 62 in the electronic control unit 49, and various sensors 50-58 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 external devices. For example, it can send and receive various types of information to and from external devices 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. Alternatively, the communication module 60 may be, for example, at least one of the base station 10 and the user terminal 20 (it 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 the following to an external device via wireless communication: signals from the various sensors 50-58 input to the electronic control unit 49, information obtained based on said signals, and information based on input from an external source (user) obtained via the information service unit 59. The electronic control unit 49, the various sensors 50-58, the information service unit 59, etc., may also be called input units that accept input. For example, the PUSCH transmitted by the communication module 60 may include information based on the above input.

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

[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, axle 48, various sensors 50-58, etc., which are provided in the vehicle 40.

[0346] Furthermore, the term "base station" in this disclosure may be interpreted as "user terminal." For example, the various aspects / embodiments of this 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), Vehicle-to-Everything (V2X)). In this case, the user terminal 20 may have the functions that the base station 10 has. Also, terms such as "uplink" and "downlink" may be interpreted as terms corresponding to terminal-to-terminal communication (for example, "sidelink"). For example, uplink channel and downlink channel may be interpreted as sidelink channel.

[0347] Similarly, the term "user terminal" in this disclosure may be replaced with "base station." In this case, the base station 10 may be configured to have the same functions as the user terminal 20 described above.

[0348] In this disclosure, operations performed by a base station may, in some cases, be performed by its upper node. In a network including one or more network nodes with base stations, it is clear that various operations performed for communication with terminals may be performed by the base station, one or more network nodes other than the base station (for example, a Mobility Management Entity (MME), a Serving Gateway (S-GW), etc., but not limited to these), or a combination thereof.

[0349] Each aspect / embodiment described in this disclosure may be used individually, in combination, or switched between during execution. Furthermore, the processing procedures, sequences, flowcharts, etc., of each aspect / embodiment described in this disclosure may be rearranged in order, provided they are consistent. For example, the methods described in this disclosure present various step elements in an exemplary order and are not limited to that specific order.

[0350] Each aspect / embodiment described in this disclosure includes 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 (where x is, for example, an integer or decimal)), 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®), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi®), IEEE 802.16 (WiMAX®), and IEEE This may apply to systems utilizing 802.20, Ultra-WideBand (UWB), Bluetooth®, or other appropriate wireless communication methods, as well as next-generation systems that are extended, modified, created, or defined based on these. It may also apply to combinations of multiple systems (e.g., a combination of LTE or LTE-A and 5G).

[0351] In this disclosure, the phrase "based on" does not mean "based solely on" unless otherwise specified. In other words, the phrase "based on" means both "based solely on" and "based at least on."

[0352] Any reference to elements using the designations “first,” “second,” etc., as used in this disclosure does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient way to distinguish between two or more elements. Accordingly, the references to the first and second elements do not imply that only two elements may be employed or that the first element must precede the second element in any way.

[0353] The term “determining” as used in this disclosure may encompass a wide variety of actions. For example, “determining” may be considered to include judging, calculating, computing, processing, deriving, investigating, looking up, searching, inquiry (e.g., searching in tables, databases, or other data structures), ascertaining, etc.

[0354] Furthermore, "judgment (decision)" may be considered as "judging (deciding)" things like receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, accessing (e.g., accessing data in memory).

[0355] Furthermore, "judgment (decision)" can be considered as "judging (deciding)" something like resolving, selecting, choosing, establishing, comparing, etc. In other words, "judgment (decision)" can be considered as "judging (deciding)" something about an action.

[0356] Furthermore, "judgment (decision)" can be replaced with "assuming," "expecting," or "considering."

[0357] The term "maximum transmit power" as used in this disclosure may mean the maximum transmit power, the nominal UE maximum transmit power, or the rated UE maximum transmit power.

[0358] As used in this disclosure, the terms “connected,” “coupled,” and any variations thereof mean any direct or indirect connection or coupling between two or more elements, and may include one or more intermediate elements between two elements that are “connected” or “coupled” with each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, “connection” may be replaced with “access.”

[0359] In this disclosure, when two elements are connected, they can be considered to be “connected” or “coupled” to each other using one or more wires, cables, printed electrical connections, etc., and, in some non-exclusive and non-exclusive examples, electromagnetic energy having wavelengths in the radio frequency domain, microwave domain, or optical domain (both visible and invisible).

[0360] In this 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 "combine" may be interpreted similarly to "different."

[0361] Where the terms “include,” “including,” and variations thereof are used in this disclosure, these terms are intended to be inclusive, as is the term “comprising.” Furthermore, the term “or” as used in this disclosure is not intended to mean exclusive OR.

[0362] In this disclosure, if articles are added by translation, such as a, an, and the in English, this disclosure may include the fact that the noun following these articles is plural.

[0363] In this disclosure, terms such as "less than or equal to," "less than," "greater than or equal to," "more than," and "equal to" may be interpreted interchangeably. In addition, in this disclosure, terms meaning "good," "bad," "big," "small," "high," "low," "early," "slow," "wide," and "narrow" may be interpreted interchangeably, not limited to the positive, comparative, and superlative degrees. Furthermore, in this disclosure, terms meaning "good," "bad," "big," "small," "high," "low," "early," "slow," "wide," and "narrow" may be interpreted interchangeably, not limited to the positive, comparative, and superlative degrees, by adding "i-th" (where i is any integer) to the expression (for example, "highest" may be interpreted interchangeably with "i-th highest").

[0364] In this disclosure, "of," "for," "regarding," "related to," and "associated with" may be interpreted as being interchangeable.

[0365] Although the invention described herein has been explained in detail above, it will be clear to those skilled in the art that the invention described herein is not limited to the embodiments described herein. The invention described herein can be implemented in modified and altered forms without departing from the spirit and scope of the invention as defined in the claims. Therefore, the descriptions herein are for illustrative purposes only and do not imply any limitation on the invention described herein.

Claims

1. A receiving unit receives a Medium Access Control Control Element (MAC CE) related to a timing advance command that includes a 1-bit field indicating one of the transmission / reception points for a serving cell with multiple transmission / reception points configured. A terminal having, if setting a timing advance for each of the aforementioned transmission and reception points is supported, a control unit that determines a timing advance command included in the MAC CE to be applied to one of the transmission and reception points based on the one-bit field included in the MAC CE.

2. The terminal according to claim 1, wherein the control unit controls the start or restart of a time alignment timer associated with one of the transmit / receive points to which the timing advance command is applied.

3. For a serving cell with multiple transmit / receive points configured, the process involves receiving a Medium Access Control Control Element (MAC CE) related to a timing advance command that includes a 1-bit field indicating one transmit / receive point, A wireless communication method for a terminal, comprising the step of determining a timing advance command included in the MAC CE to be applied to one of the transmission / reception points, based on the 1-bit field included in the MAC CE, if the setting of a timing advance for each transmission / reception point is supported.

4. A transmitting unit transmits a Medium Access Control Element (MAC CE) related to a timing advance command that includes a 1-bit field indicating one of the transmitting and receiving points for a serving cell with multiple transmit / receive points configured. A base station having, if setting a timing advance for each of the aforementioned transmission and reception points is supported, a control unit that uses the one-bit field contained in the MAC CE to instruct a timing advance command contained in the MAC CE to be applied to one of the transmission and reception points.

5. A system having terminals and base stations, The terminal includes a receiving unit that receives a Medium Access Control Control Element (MAC CE) relating to a timing advance command, which includes a 1-bit field indicating one of the transmission / reception points, for a serving cell in which multiple transmission / reception points are set. If setting a timing advance for each transmission / reception point is supported, the system includes a control unit that determines a timing advance command included in the MAC CE to be applied to one of the transmission / reception points based on the one-bit field included in the MAC CE, The base station includes a transmitting unit that transmits the MAC CE, A system comprising: a control unit that uses the aforementioned one-bit field to issue the timing advance command.

Images