Terminal, wireless communication method, and base station

Abstract

A terminal according to one aspect of the present disclosure comprises: a reception unit that receives a downlink control channel order including information related to a candidate cell; and a control unit that controls, on the basis of information related to the candidate cell, physical random access channel (PDCCH order RACH) transmission that is triggered by the downlink control channel order. The control unit determines, on the basis of the value of a candidate cell indicator field, application of a PDCCH order RACH having a random access response (RAR) or a PDCCH order RACH not having the RAR.

Description

Terminal, wireless communication method and base station

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

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

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

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

[0005] In future wireless communication systems (e.g., wireless communication systems after Rel. 17 / 5G), it is expected that communications will be controlled based on inter-cell mobility including a non-serving cell, or inter-cell mobility using multiple transmission / reception points (e.g., Multi-TRP (MTRP)). In inter-cell mobility, it is also expected that candidate cells will be set and switching between the serving cell and candidate cells will be performed using L1 / L2 signaling.

[0006] For example, in the LTM of Rel. 18, RACH by a PDCCH order without RAR (PDCCH order RACH) is supported for a candidate cell. Meanwhile, a serving cell can also be configured as a candidate cell.

[0007] In this case, there may be cases where the UE does not know whether the serving cell (e.g., SCell) configured as a candidate cell performs an existing PDCCH order RACH or a PDCCH order RACH without RAR.

[0008] In this way, if the RACH procedure to be applied cannot be appropriately selected depending on the candidate cell to be set, cell switching may not be performed appropriately, which may result in a decrease in throughput / deterioration in communication quality.

[0009] The present disclosure has been made in consideration of such points, and one of its objectives is to provide a terminal, a wireless communication method, and a base station that can clearly distinguish between RACH procedures depending on the candidate cell to be set and appropriately control communications.

[0010] A terminal according to one aspect of the present disclosure includes a receiving unit that receives a downlink control channel order including information about a candidate cell, and a control unit that controls a physical random access channel transmission (PDCCH order RACH) triggered by the downlink control channel order based on the information about the candidate cell, and the control unit determines whether to apply a PDCCH order RACH with a random access response (RAR) or a PDCCH order RACH without an RAR based on the value of the candidate cell indicator field.

[0011] According to one aspect of the present disclosure, it is possible to clearly distinguish between RACH procedures depending on the candidate cells to be set, and to appropriately control communications.

[0012] Figure 1A illustrates an example of UE mobility in Rel. 17. Figure 1B illustrates an example of UE mobility in Rel. 18. Figure 2 illustrates an example of an LTM procedure. Figure 3 illustrates an example of a comparison between L3 handover and Rel. 18 LTM. Figure 4 illustrates an example of serving cell and candidate cell association. Figure 5A illustrates a first example of candidate cell configuration option 2. Figure 5B illustrates a second example of candidate cell configuration option 2. Figure 6 illustrates serving cell switch example 1. Figure 7 illustrates serving cell switch example 2. Figure 8 illustrates serving cell switch example 3. Figure 9 illustrates an overview of L1L2-triggered mobility (LTM). Figure 10 illustrates PDCCH-ordered RACH with random access response (RAR) monitoring for a serving cell. FIG. 11 is a diagram illustrating a PDCCH-instructed RACH (PDCCH-ordered RACH) without random access response (RAR) monitoring for a candidate cell. FIG. 12 is a diagram illustrating DCI format 1_0 CRC-scrambled by C-RNTI. FIG. 13 is a diagram illustrating an example of RACH procedure distinction according to the first embodiment. FIG. 14 is a diagram illustrating an example of DCI format 1_0 (DCI field) according to the second embodiment. FIGS. 15A and 15B are diagrams illustrating examples of RACH specifications according to the second embodiment. FIG. 16 is a diagram illustrating an example of a schematic configuration of a wireless communication system according to an embodiment. FIG. 17 is a diagram illustrating an example of a base station configuration according to an embodiment. FIG. 18 is a diagram illustrating an example of a user terminal configuration according to an embodiment. FIG. 19 is a diagram illustrating an example of hardware configurations of a base station and a user terminal according to an embodiment. FIG. 20 is a diagram illustrating an example of a vehicle according to an embodiment.

[0013] (TCI, spatial relationship, QCL) In NR, it is considered to control the reception processing (e.g., at least one of reception, demapping, demodulation, and decoding) and transmission processing (e.g., at least one of transmission, mapping, precoding, modulation, and encoding) in a UE of at least one of a signal and a channel (referred to as a signal / channel) based on a transmission configuration indication state (TCI state).

[0014] The TCI state may represent that which is applied to a downlink signal / channel, and the equivalent of the TCI state that is applied to an uplink signal / channel may be expressed as a spatial relation.

[0015] The TCI state is information about the Quasi-Co-Location (QCL) of signals / channels, and may also be called spatial reception parameters, spatial relation information, etc. The TCI state may be configured in the UE for each channel or signal.

[0016] The QCL is an index indicating the statistical properties of signals / channels. For example, if a signal / channel has a QCL relationship with another signal / channel, it may mean that it can be assumed that at least one of a Doppler shift, a Doppler spread, an average delay, a delay spread, and a spatial parameter (e.g., a spatial Rx parameter) is the same between these different signals / channels (i.e., the signals / channels have a QCL with respect to at least one of these).

[0017] The spatial reception parameters may correspond to a reception beam (e.g., a reception analog beam) of the UE, and the beam may be identified based on a spatial QCL. The QCL (or at least one element of the QCL) in the present disclosure may be replaced with sQCL (spatial QCL).

[0018] A plurality of types (QCL types) of QCL may be defined. For example, four QCL types A to D may be provided, each having different parameters (or parameter sets) that can be assumed to be the same. The parameters (which may be referred to as QCL parameters) are as follows: QCL type A (QCL-A): Doppler shift, Doppler spread, mean delay, and delay spread QCL type B (QCL-B): Doppler shift and Doppler spread QCL type C (QCL-C): Doppler shift and mean delay QCL type D (QCL-D): Spatial reception parameters.

[0019] The UE's assumption that a Control Resource Set (CORESET), channel, or reference signal has a specific QCL (e.g., QCL type D) relationship with another CORESET, channel, or reference signal may be referred to as a QCL assumption.

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

[0021] The TCI state may be, for example, information about the QCL between the channel of interest (in other words, the Reference Signal (RS) for that channel) and another signal (e.g., another RS). The TCI state may be set (indicated) by higher layer signaling, physical layer signaling, or a combination thereof.

[0022] The channel / signal to which the TCI state is applied may be called a target channel / reference signal (target channel / RS), or simply a target, and the other signal may be called a reference reference signal (reference RS), a source RS, or simply a reference.

[0023] The channel for which the TCI state or spatial relationship is set (specified) may be, for example, at least one of a physical downlink shared channel (PDSCH), a physical downlink control channel (PDCCH), a physical uplink shared channel (PUSCH), and a physical uplink control channel (PUCCH).

[0024] Furthermore, the RS that has a QCL relationship with the channel may be at least one of, for example, a synchronization signal block (SSB), a channel state information reference signal (CSI-RS), a sounding reference signal (SRS), a tracking CSI-RS (also called a tracking reference signal (TRS)), a QCL detection reference signal (also called a QRS), a demodulation reference signal (DMRS), etc.

[0025] An SSB is a signal block including at least one of a Primary Synchronization Signal (PSS), a Secondary Synchronization Signal (SSS), and a Physical Broadcast Channel (PBCH). An SSB may also be referred to as an SS / PBCH block.

[0026] An RS of QCL type X in a TCI state may refer to an RS that has a QCL type X relationship with a certain channel / signal (DMRS), and this RS may be called a QCL source of QCL type X in the TCI state.

[0027] (L1 / L2 Inter-Cell Mobility) As described above, it is being considered that a UE performs UL transmission to one or more cells / TRPs. The following scenario 1 or scenario 2 can be considered as a procedure in this case. In the present disclosure, the term "serving cell" may be replaced with the TRP in the serving cell. The terms "layer 1 / layer 2" (L1 / L2) and "DCI / Medium Access Control Control Element (MAC CE)" may be interchangeable. In the present disclosure, a physical cell identity (PCI) different from the physical cell identity (PCI) of the current serving cell may be simply referred to as a "different PCI." The terms "non-serving cell," "cell having a different PCI," and "additional cell" may be interchangeable.

[0028] <Scenario 1> Scenario 1 corresponds to, for example, multi-TRP inter-cell mobility, but may be a scenario that does not correspond to multi-TRP inter-cell mobility.

[0029] (1) The UE receives from the serving cell the configuration necessary for using radio resources for data transmission and reception, including the SSB configuration for beam measurement of the TRP corresponding to a PCI different from that of the serving cell and the resources of the different PCI. (2) The UE performs beam measurement of the TRP corresponding to the different PCI and reports the beam measurement results to the serving cell. (3) Based on the above report, the Transmission Configuration Indication (TCI) state associated with the TRP corresponding to the different PCI is activated by L1 / L2 signaling from the serving cell. (4) The UE transmits and receives using UE-dedicated channels on the TRP corresponding to the different PCI. (5) The UE must always cover the serving cell, including in the case of multiple TRPs. As in conventional systems, the UE must use common channels from the serving cell, such as the Broadcast Control Channel (BCCH) and the Paging Channel (PCH).

[0030] In Scenario 1, when the UE transmits and receives signals to and from an additional cell / TRP (a TRP corresponding to the PCI of the additional cell), the serving cell (the serving cell assumption in the UE) is not changed. The UE is configured with higher layer parameters related to the PCI of non-serving cells from the serving cell. Scenario 1 may be applied, for example, in Rel. 17.

[0031] Figure 1A shows an example of UE movement in Rel. 17. Assume that the UE moves from a cell (serving cell) with PCI #1 to a cell (additional cell) with PCI #3 (which overlaps with the serving cell). In this case, Rel. 17 does not support switching of serving cells via L1 / L2.

[0032] An additional cell is a cell with an additional PCI that is different from the PCI of the serving cell. The UE can receive / transmit UE-dedicated channels from the additional cell. The UE needs to be within the coverage of the serving cell to receive UE common channels (e.g., system information / paging / short messages). When the UE moves out of the coverage of the serving cell, a cell change is required, such as by handover (also called L3 mobility).

[0033] <Scenario 2> In scenario 2, L1 / L2 inter-cell mobility is applied. With L1 / L2 inter-cell mobility, the serving cell can be changed using functions such as beam control without RRC reconfiguration. In other words, transmission and reception with an additional cell is possible without handover. Since handover requires RRC reconnection, which results in a period when data communication is unavailable, by applying L1 / L2 inter-cell mobility that does not require handover, data communication can be continued even when the serving cell is changed. Scenario 2 may be applied, for example, in Rel. 18. In scenario 2, for example, the following procedure is performed.

[0034] (1) The UE receives SSB configuration for a cell with a different PCI (additional cell) from the serving cell for beam measurement / serving cell change. (2) The UE performs beam measurement for the cell using the different PCI and reports the measurement results to the serving cell. (3) The UE may receive the configuration for the cell with a different PCI (serving cell configuration) via higher layer signaling (e.g., RRC). That is, pre-configuration for the serving cell change may be performed. This configuration may be performed together with or separately from the configuration in (1). (4) Based on the above report, the TCI state of the cell with a different PCI may be activated via L1 / L2 signaling in accordance with the serving cell change. The activation of the TCI state and the serving cell change may be performed separately. (5) The UE changes the serving cell (assumed serving cell) and starts reception / transmission using the pre-configured UE-dedicated channel and TCI state.

[0035] That is, in Scenario 2, the serving cell (the serving cell assumed by the UE) is updated by L1 / L2 signaling. Scenario 2 may be applied in Rel. 18.

[0036] Figure 1B shows an example of UE mobility in Rel. 18. In Rel. 18, the serving cell is switched by L1 / L2 (e.g., DCI / MAC CE). The UE can receive / transmit UE-dedicated channels / common channels to / from the new serving cell (or target serving cell). The UE may move out of the coverage of the current serving cell (e.g., current serving cell).

[0037] <L1L2-triggered mobility (LTM) procedure> Fig. 2 is a diagram showing an example of an LTM procedure. Note that L1 / L2 inter-cell mobility and L1L2-triggered mobility (LTM) may be interpreted as interchangeable. Note that the procedure in Fig. 2 may be a procedure corresponding to the above-mentioned scenario 2. Each procedure in Fig. 2 will be described below.

[0038] The UE establishes an RRC connection with the current serving cell (PCI #1) and transmits an L3 measurement report. The serving cell (base station) determines whether to perform LTM based on the L3 measurement report and prepares for LTM together with the candidate cell. The UE and the serving cell then perform RRC reconfiguration. Note that the candidate cell may include the target cell (PCI #3).

[0039] The UE, serving cell, target cell, and candidate cell perform DL synchronization. The UE performs and reports L1 (e.g., L1-RSRP / SINR) measurements of the serving / candidate / target cell. The UE, serving cell, target cell, and candidate cell perform UL synchronization.

[0040] The serving cell determines to switch the serving cell to the target cell (PCI #3) based on the L1 measurement report and sends a cell switch command to the UE. After receiving the cell switch command, the UE starts PDCCH monitoring for the target cell.

[0041] In the case of RACH-based LTM, the UE performs a RACH procedure to the target cell. In the case of RACH-less LTM, the UE sends an RRC reconfiguration complete message and transmits the first data to the target cell. This first data transmission is based on a dynamic grant or a configuration grant associated with the beam of the target cell. The target cell sends an ACK for this transmission to the UE.

[0042] <Reduced Interruption Time> In Rel. 18 L1 / L2 inter-cell mobility (e.g., the above-mentioned scenario 2), the UE can reduce the time without data transmission (interruption time). When Rel. 18 LTM is applied, the time without data transmission (interruption time) can be reduced compared to the method of handover based on L3 measurement results (L3 handover). Specific processes for each are described below.

[0043] Figure 3 shows an example comparison between L3 handover and Rel. 18 LTM. In the case of L3 handover, the UE first performs L3 measurements and decides to perform handover based on the measurement results. Then, the UE and the current serving cell perform RRC reconfiguration. The UE then performs DL and UL synchronization with the target serving cell. The UE performs L1 measurements / reports for the target serving cell, receives beam instructions, and then transmits the first UL data to the target serving cell. In this case, the UE does not transmit UL data during the period from the handover decision to the first UL data transmission (interruption time).

[0044] In the Rel. 18 LTM case, the UE first performs L3 measurements. Then, the UE, the current serving cell, and the target serving cell perform RRC reconfiguration. Then, the UE establishes DL synchronization with the target serving cell. Then, the UE performs L1 measurements / reports to the current serving cell and the target serving cell to establish UL synchronization. Then, the current serving cell sends a cell switch command (including beam indication) to the UE via L1 / L2 (DCI / MAC CE). Then, the UE transmits the first UL data to the target serving cell. In this case, the period from receiving the cell switch command to transmitting the first UL data is the UL transmission interruption time, but this interruption time is shorter than in the case of L3 handover.

[0045] (Setting of Multiple Candidate Cells) FIG. 4 is a diagram showing an example of association between a serving cell and a candidate cell. SpCell #0, SCell #1, or SCell #2 is assumed to be a serving cell. Note that SpCell means a special cell (including a primary cell (PCell) and a primary secondary cell (PSCell)). SCell means a secondary cell. SpCell #0 is associated with candidate cell #0-1, candidate cell #0-2, and candidate cell #0-3. SCell #1 is associated with candidate cell #1-1. SCell #2 is associated with candidate cell #2-1 and #2-2. In this way, one or more candidate cells (candidate serving cells) may be associated with a serving cell.

[0046] Regarding the setting of candidate cells (candidate cells) when changing the serving cell, for example, the following options 1 and 2 are possible.

[0047] <Option 1> As with inter-cell mobility in Rel. 17, the information in the serving cell configuration (ServingCellConfig) may include information about multiple candidate cells. In this case, the multiple candidate cells need to share the same configurations of PDCCH / PDSCH / UL, etc. as the serving cell.

[0048] For example, in inter-cell mobility in Rel. 17, "mimoParam-r17" is added under the serving cell configuration (ServingCellConfig), and PCI configuration information is added. mimoParam-r17 may include additionalPCI-ToAddModList-r17, which is an information list of additional SSBs with PCIs different from the PCI of the serving cell. The same configuration as the serving cell may be applied to candidate cells (additional cells, cells with additionalPCI), with the exception of some information.

[0049] <Option 2> Multiple candidate cells may be associated with each serving cell by reusing the carrier aggregation (CA) configuration framework, with a complete configuration (e.g., ServingCellConfig) corresponding to each cell. That is, the candidate cells may not share configuration information with the serving cell and may have a separate configuration. The UE is provided with the complete configuration for each candidate cell, allowing it to communicate properly with the candidate cells.

[0050] In the CA configuration framework, an SpCell can be configured for each cell group, and multiple SCells can be added. By reusing the CA framework, a serving cell can be configured for each cell group for L1 / L2 inter-cell mobility, and multiple candidate cells can be configured. Candidate cells can be activated / deactivated by the MAC CE. Candidate cells can be activated / deactivated by activating / deactivating TCI information corresponding to the candidate cells by the MAC CE. This method is considered to be beneficial for reducing the complexity of UE operations.

[0051] 5A is a diagram showing a first example of Option 2 for candidate cell configuration. In the example of FIG. 5A, a common candidate cell pool for cell switching in the MCG / SCG is applied to the candidate cells. In other words, the candidate cells are treated as one pool (group) regardless of frequency band.

[0052] 5B is a diagram showing a second example of the candidate cell configuration option 2. In the example of FIG. 5B, multiple cell groups are configured, and cell group switching is possible by L1 / L2 signaling. Candidate cells are configured for each cell group, and the configuration for each group includes the indices of the corresponding SpCell and SCell.

[0053] (Signaling for Serving Cell Change Indication) Implicit or explicit signaling for serving cell change indication will now be described.

[0054] [Aspect 1] In aspect 1, implicit signaling for a serving cell change indication is described.

[0055] [[Option 1-1]] When a specific control resource set (CORESET) (e.g., at least one of CORESET#0, CORESET of CH5 Type0-CSS, and CORESET of CH6 / CH7 / CH8 CSS) is indicated (activated) by a MAC CE together with one or more TCI states associated with cells of PCIs different from that of the serving cell (when one or more TCI states associated with cells of PCIs different from that of the serving cell are indicated / activated by a MAC CE for a specific CORESET), the UE may determine to change the serving cell to another cell (cell x, a cell with a different PCI). In other words, this activation may implicitly indicate that the serving cell will be changed to another cell.

[0056] In this case, the UE may update beams of other CORESET IDs, other CORESETs using CH6 / CH7 / CH8, or other CORESETs using CSS to the same TCI state as the activated TCI state.

[0057] [[Option 1-2]] When the MAC CE activates / deactivates the TCI states of the PDSCH, if all such TCI states activated by the MAC CE are associated with the same cell x having a PCI different from that of the serving cell, the UE may determine to change the serving cell to another cell (cell x), i.e., this association may implicitly indicate that the serving cell will be changed to another cell.

[0058] In the case where this option applies, if the NW (base station) does not change the serving cell, when the MAC CE activates the TCI state of a PDSCH associated with a cell with a different PCI, it must also include the TCI state related to another cell (e.g., the current serving cell or a second cell with a different PCI).

[0059] [[Options 1-3]] If the MAC CE activates / deactivates unified TCI states (e.g., corresponding to the unified TCI framework in Rel. 17) and all activated unified TCI states are associated with the same cell x with different PCIs, the UE may determine to change the serving cell to another cell (cell x), i.e., this association may implicitly indicate that the serving cell will be changed to another cell.

[0060] [Aspect 2] In aspect 2, explicit signaling for a serving cell change instruction will be described. In aspect 2, for example, the above-mentioned scenario 2 is applied.

[0061] [Option 2-1] An example of a serving cell change instruction will be described below. Note that activation / deactivation of a non-serving cell, change of a serving cell, and transmission / reception with another cell (non-serving cell) having a physical cell ID different from the physical cell ID of the serving cell may be interpreted as interchangeable.

[0062] The UE may receive a new MAC CE including at least one of the fields (information) indicating the following (1) to (3) corresponding to a non-serving cell, which is used for activating / deactivating the non-serving cell. When the UE receives the MAC CE, the UE may determine to change the serving cell to another cell (non-serving cell). Furthermore, the UE may control transmission and reception of DL signals / UL signals with the non-serving cell based on the information. Note that the non-serving cell may be one or multiple. In the example shown below, a MAC CE including multiple fields indicating multiple non-serving cell indexes is applied.

[0063] (1) Serving cell ID, (2) BWP ID, and (3) Non-serving cell ID used for activation. The non-serving cell ID may be replaced with any information corresponding to the non-serving cell (that can identify the non-serving cell).

[0064] As an example of (3), any of (3-1) to (3-5) may be applied. (3-1) PCI (PCI used directly). For example, 10 bits are used. (3-2) Re-creation index (new ID) of non-serving cells. The new ID may be associated with a part of the PCI and configured only for serving and non-serving cells used (available) by the UE. The new ID can reduce the number of bits compared to the PCI. (3-3) CSI reporting configuration ID (CSI-ReportConfigId) (when CSI-ReportConfig corresponds to one or more non-serving cells). (3-4) CSI resource configuration ID (CSI-ResourceConfigId) (when CSI-ResourceConfigId corresponds to one or more non-serving cells). (3-5) Bitmap indicating activation / deactivation of each non-serving cell. The size (number of bits) of the bitmap may be the same as the number of non-serving cells configured on this CC. For example, when activating the second non-serving cell among three non-serving cells, "010" is set.

[0065] At least one of the pieces of information included in the MAC CE may be included in the DCI. Alternatively, at least one of the serving cells activated by the MAC CE may be indicated by the DCI. The MAC CE / DCI may include a field indicating the TCI status / SSB / CSI-RS from a cell having a different PCI so that the UE can recognize the DL beam to monitor on the target cell (post-change serving cell). The UE may create and transmit a beam report (CSI report) using the TCI status / SSB / CSI-RS.

[0066] [[Option 2-2]] The UE may receive a MAC CE in which a new 1-bit field "C" is added to the existing MAC CE. The field indicates whether to change the serving cell. The UE may receive the MAC CE and determine whether to change the serving cell to another cell based on the field.

[0067] [Option 2-3] In addition to the MAC CE in Option 2-2, the MAC CE may further include a field indicating the serving cell index / PCI / other ID (such as the new ID in Option 2-1 above), and a field indicating the TCI state / SSB / CSI-RS of the target cell (the serving cell after the change).

[0068] In this way, since the instruction for the serving cell change instruction is indicated by the MAC CE / DCI, the UE can appropriately change the serving cell.

[0069] [Serving Cell Switch Example 1] Figure 6 is a diagram showing Serving Cell Switch Example 1. For example, in a serving cell SpCell #0 of an MCG / SCG, if an instruction to change the serving cell to candidate cell #0-2 is given by L1 / L2 signaling, candidate cell #0-2 becomes the new serving cell SpCell #0. Also, for example, in a serving cell SCell #2 of an MCG / SCG, if an instruction to change the serving cell to candidate cell #2-1 is given by L1 / L2 signaling, candidate cell #2-1 becomes the new serving cell SCell #2.

[0070] [Serving Cell Switch Example 2] The RRC / MAC CE may configure a global candidate cell ID (cell #3, ..., 8) for each cell group, band, FR, and UE. The UE may be instructed to switch the serving cell by the global candidate cell ID.

[0071] Figure 7 illustrates a serving cell switch example 2. Similar to Figure 5A, a pool of multiple candidate cells can be configured, and the serving cell can be switched to any (activated) candidate cell in the pool by L1 / L2 signaling. In this case, the configured candidate cell can be either an SpCell or an SCell based on the L1 / L2 signaling.

[0072] The UE may receive an indication of a serving cell change (from cell #2-1 to candidate cell #4) via MAC CE / DCI, and the indicated candidate cell #4 becomes the SpCell of the new cell group (MCG / SCG).

[0073] Serving Cell Switch Example 3 The RRC / MAC CE may configure a cell group, and the UE may perform a serving cell switch based on the cell group switch.

[0074] 8 is a diagram showing a serving cell switch example 3. The UE receives an instruction to change the cell group having the serving cell (change to candidate cell group #1) via MAC CE / DCI. Then, the cells included in the indicated candidate cell group #1 become the new serving cells (SpCell, SCell). For example, candidate cells #0, #1, and #2 included in the indicated candidate cell group #1 become the new SpCell #0, SCell #1, and SCell #2. In other words, the serving cell group is switched.

[0075] (Overview of L1L2-triggered mobility (LTM)) In L1L2-triggered mobility (LTM) supported in Rel. 18 and later, L1 inter-frequency measurements (e.g., L1 inter-frequency measurements) may be supported. Also, DL synchronization / UL synchronization of a candidate cell based on at least SSB before a cell switch command may be supported.

[0076] 9 is a diagram showing an overview of L1L2-triggered mobility (LTM). LTM and L1 / L2 inter-cell mobility may be interpreted as interchangeable.

[0077] The UE receives candidate cell configurations from the NW during UE reconfiguration. RRC , including Tproccesing1 / Tproccesing2. T RRC (e.g., max. 10 ms) is the processing time for RRC Reconfiguration carrying candidate cell configurations. Tproccesing1 / Tproccesing2 (e.g., max. 20 ms for same FR, max. 40 ms for different FR) are the time for UE processing before and after the cell switch command, respectively. This may include L2 / 3 reconfiguration, RF retuning, baseband retuning, security update if required, etc.

[0078] DL synchronization is T search , T Δ , T margin Includes: T search (e.g., 0 ms if the cell is known, up to 60 ms if the cell is unknown) is the time it takes to search for the target cell. Δ is the time for fine tracking and acquisition of all timing information. T margin (e.g., max. 2 ms) is the time for post-processing of SSB and CSI-RS.

[0079] L1 measurement is T meas (including SMTC period (e.g. 20 ms)). T meas is the measured delay from the appearance of the target to the cell switch command.

[0080] UL synchronization is T IU , T RAR , T cmd Includes: T IU (e.g., up to 15 ms) is the time of uncertainty interruption in acquiring the first available PRACH opportunity in the new cell. RAR (e.g., maximum 4 ms) is the RAR delay time. cmd (e.g., maximum 5 ms) is the processing time for L1 / L2 commands (HARQ and paging).

[0081] T cmd T after first-data is the time at which the UE performs its first DL reception / UL transmission on the indicated beam of the target cell after RAR.

[0082] 10 is a diagram showing an example of a PDCCH-ordered RACH with RAR monitoring. In the present disclosure, a source cell and a source cell group may be interchangeable. Also, a candidate cell and a candidate cell group may be interchangeable.

[0083] The source cell may transmit information regarding the configuration of the candidate cell (e.g., candidate cell configuration information) to the UE. The source cell may also transmit a PDCCH order (e.g., DCI format 1_0) used to trigger the PRACH to the UE. The PDCCH order (or DCI) may indicate a candidate cell (e.g., one candidate cell) / Random Access Occasion (RO) that is the target of the PRACH trigger / transmission. The UE transmits the PRACH in the RACH procedure to the candidate cell based on the PDCCH order to acquire the TAG / TA.

[0084] Next, the source cell transmits a response signal (RAR) to the PRACH to the UE. The RAR may include information about the TA (e.g., TA indication). The RAR (e.g., the PDSCH containing the RAR / the PDCCH scheduling the PDSCH) may be monitored in a specific search space (e.g., the common search space (CSS)) of a specific cell (e.g., the SpCell) among the current serving cells (only within the Distributed Unit (DU)). Then, the source cell performs TA adjustment (e.g., TA maintenance).

[0085] Next, the source cell may send a cell switch command to the UE. TA information may also be moved / notified from the source cell to the target cell. The UE may control UL transmission based on the acquired TA after cell switching. For example, the UE may perform the first UL transmission using the initial TA if UL synchronization with all candidate cells has not been completed after the initial cell switch.

[0086] Fig. 11 is a diagram showing an example of a PDCCH ordered RACH without RAR monitoring. Only the differences between Fig. 11 and Fig. 10 will be described.

[0087] In the example of Fig. 11, the PDCCH order used to trigger the PRACH may indicate one or more candidate cells (e.g., multiple candidate cells) / random access occasions that are targets for PRACH trigger / transmission. The UE may transmit PRACH in the RACH procedure to candidate cells based on the PDCCH order to acquire multiple TAGs / TAs. The source cell does not transmit a PRACH response signal (e.g., RAR). The source cell may indicate TA information (e.g., TA indication) to the UE using a cell switch command.

[0088] In the present disclosure, a RACH without RAR and a RACH without RAR monitoring (e.g., a RACH without RAR monitoring) may be interpreted as interchangeable. A RACH may be interpreted as a PRACH transmission triggered by a PDCCH order. A RACH procedure / PRACH transmission without RAR monitoring may be interpreted as a RACH procedure / PRACH transmission in which RAR monitoring is not required, or a RACH procedure / PRACH transmission in which RAR monitoring is not required.

[0089] [PDCCH Order] DCI format 1_0 includes a DCI format identifier field, a bit field that is always set to 1, and a frequency domain resource assignment field. If the cyclic redundancy check (CRC) of DCI format 1_0 is scrambled by the C-RNTI and the frequency domain resource assignment field is all 1, then DCI format 1_0 is for a random access procedure initiated by a PDCCH order, and the remaining fields are a random access preamble, a UL / supplementary uplink (SUL) indicator, a SS / PBCH index (SSB index), a PRACH mask index, and reserved bits (12 bits).

[0090] For a PRACH transmission triggered by a PDCCH order, the PRACH mask index field indicates the PRACH occasion of the PRACH transmission that is associated with the SS / PBCH block index indicated by the SS / PBCH block index field of the PDCCH order if the value of the random access preamble index field is not zero.

[0091] 12 is a diagram showing DCI format 1_0 that is CRC-scrambled by C-RNTI. The frequency domain resource assignment may be used, for example, for a PDCCH order (RACH) according to an instruction of the PDCCH. For example, if the frequency domain resource assignment indicates all 1s, this may mean that the DCI format 1_0 is used as a PDCCH order.

[0092] The random access preamble index may be used for contention-based random access (CBRA). For example, if the random access preamble index is all 0, it may mean that CBRA is used. The reserved bits are 12 bits when operating in a cell with spectrum shared channel access, and 10 bits otherwise.

[0093] Thus, in L1 / L2-based mobility (e.g., LTM) supported in Rel. 18 and later, TA acquisition of a candidate cell before a cell switch command may be supported. The TA acquisition mechanism for a candidate cell may support at least a RACH in a PDCCH order. The PDCCH order may be triggered only by the source cell (e.g., the serving cell). The DCI transmitted in the PDCCH order may indicate the candidate cell / RACH occasion (RO) of the candidate cell. The RACH resource configuration of the candidate cell may be provided to the UE before the PDCCH order.

[0094] In the RACH of the PDCCH order, at least one of a method with RAR monitoring and a method without RAR monitoring may be applied. When the method with RAR monitoring is applied, information on the timing advance of the candidate cell (e.g., TA information / TAC) may be included in the RAR and indicated to the UE. When the method without RAR monitoring is applied, information on the timing advance of the candidate cell (e.g., TA information / TAC) may be included in the cell switch command and indicated to the UE.

[0095] (Initial Access Procedure) In the initial access procedure, a UE (RRC_IDLE mode) receives an SS / PBCH block (SSB), transmits Msg. 1 (PRACH / random access preamble / preamble), receives Msg. 2 (PDCCH, PDSCH including random access response (RAR)), transmits Msg. 3 (PUSCH scheduled by RAR UL grant), and receives Msg. 4 (PDCCH, PDSCH including UE contention resolution identity). After that, when an ACK for Msg. 4 is transmitted from the UE by the base station (network), an RRC connection is established (RRC_CONNECTED mode).

[0096] SSB reception includes PSS detection, SSS detection, PBCH-DMRS detection, and PBCH reception. PSS detection includes detecting part of the physical cell ID (PCI), detecting (synchronizing) OFDM symbol timing, and (coarse) frequency synchronization. SSS detection includes detecting the physical cell ID. PBCH-DMRS detection includes detecting (part of) the SSB index within a half radio frame (5 ms). PBCH reception includes detecting the system frame number (SFN) and radio frame timing (SSB index), receiving configuration information for receiving remaining minimum system information (RMSI, SIB1), and recognizing whether the UE can camp on that cell (carrier).

[0097] SSB has a bandwidth of 20 RBs and a time of 4 symbols. The transmission period of SSB can be set to {5, 10, 20, 40, 80, 160} ms. In a half frame, multiple symbol positions of SSB are defined based on the frequency range (FR1, FR2).

[0098] The PBCH has a payload of 56 bits. N repetitions of the PBCH are transmitted within a period of 80 ms, where N depends on the SSB transmission period.

[0099] The system information consists of the MIB, RMSI (SIB1), and other system information (OSI) carried by the PBCH. SIB1 contains information for RACH setup and RACH procedures. The time / frequency resource relationship between the SSB and the PDCCH monitoring resource for SIB1 is configured by the PBCH.

[0100] A base station using beam correspondence transmits multiple SSBs using multiple beams for each SSB transmission period. The multiple SSBs have multiple SSB indices, respectively. When a UE detects an SSB, it transmits a PRACH in the RACH occasion associated with that SSB index and receives an RAR in the RAR window.

[0101] (RACH Procedure Triggered by a PDCCH Order) In existing systems (e.g., Rel. 17 and earlier), for a RACH procedure for a specific cell (e.g., SpCell), the UE performs the RACH procedure assuming that the PDCCH order and the PDCCH for RAR have the same QCL characteristics for the RACH of the PDCCH order. The PDCCH for RAR may be a PDCCH transmitted by the base station in response to a PRACH triggered by the UE (or transmitted from the UE) by the PDCCH order. The RAR may be included in the PDSCH scheduled by the PDCCH for RAR. The QCL characteristics may be interpreted as DMRS QCL characteristics.

[0102] Specifically, when a UE detects a CRC-scrambled DCI format 1_0 with a corresponding RA-RNTI in response to a PRACH transmission initiated by a PDCCH order that triggers a CFRA procedure for an SpCell, the UE may assume that the PDCCH containing DCI format 1_0 and the PDCCH order have the same DMRS antenna port quasi-co-location property.

[0103] In addition, in existing systems (e.g., Rel. 17 and earlier), there is no restriction such as a specific cell for the RACH procedure for other cells (e.g., SCell), and the UE is supported to use the QCL of a predetermined CORESET for receiving the PDCCH for RAR. The predetermined CORESET may be a CORESET associated with a Type 1 CSS set (e.g., Type 1-PDCCH CSS set).

[0104] Specifically, if the UE performs detection of CRC-scrambled DCI format 1_0 with the corresponding RA-RNTI in response to a PRACH transmission initiated by a PDDCCH order that triggers a CFRA procedure for the SCell, the UE may assume the DMRS antenna port quasi-co-location property of the CORESET associated with the Type 1-PDCCH CSS set for reception of the PDCCH including DCI format 1_0.

[0105] Incidentally, to obtain the TA for each TRP (or the TA for the serving cell and the non-serving cell), a RACH may be triggered for each TRP (or for each serving cell / non-serving cell). Regarding a PDCCH order that triggers a RACH procedure for a TRP (or a serving cell / non-serving cell), a case may be considered in which the PDCCH order and the PDCCH for RAR are transmitted from different TRPs. In such a case, it is necessary to relax / modify the restriction that the PDCCH order and the PDCCH for RAR have the same DMRS QCL characteristics.

[0106] For example, it may be supported that a PDCCH order from TRP #1 triggers a RACH to TRP #2, and an RAR is transmitted from TRP #2. In this case, it becomes possible to trigger a RACH to any TRP via a PDCCH order from any TRP, thereby increasing the flexibility of the RACH procedure.

[0107] As another example, it may be supported that a PDCCH order from TRP #2 triggers a RACH to TRP #2 and an RAR is transmitted from TRP #1. This example may occur in an inter-cell multi-TRP (e.g., inter-cell M-TRP) case when the UE cannot receive a Type 1 CSS set from the TRP of a non-serving cell.

[0108] Random Access Procedure in the MAC Entity The random access procedure is initiated by a PDCCH order, by the MAC entity itself, or by RRC for specification-compliant events. Within a MAC entity, there can only be one random access procedure in progress at any given time. The random access procedure for an SCell is only initiated by a PDCCH order with ra-PreambleIndex different from 0b000000.

[0109] When a random access procedure is initiated on the serving cell, the MAC entity shall: set RA_TYPE to 4-stepRA if the random access procedure is initiated by a PDCCH order and the ra-PreambleIndex explicitly provided by the PDCCH is not 0b000000, or if the random access procedure is initiated due to a reconfiguration with synchronization and a contention-free random access resource of type 4-step RA is explicitly provided by rach-ConfigDedicated for the BWP selected for the random access procedure.

[0110] If the selected RA_TYPE is set to 4-step RA, the MAC entity shall: - If ra-PreambleIndex is explicitly provided by the PDCCH and ra-PreambleIndex is not 0b000000, set PREAMBLE_INDEX to the signaled ra-PreambleIndex and select the SSB signaled by the PDCCH. - If an SSB is selected as above, determine the next available PRACH occasion from the PRACH occasions allowed by the restriction given by ra-ssb-OccasionMaskIndex and corresponding to the selected SSB. (The MAC entity selects a PRACH occasion randomly with equal probability from consecutive PRACH occasions corresponding to the selected SSB according to the specification. The MAC entity may take into account the possibility of measurement gaps when determining the next available PRACH occasion corresponding to the selected SSB.)

[0111] For example, if a new random access procedure is initiated while another random access procedure is already in progress within the MAC entity, it is up to the UE implementation whether to continue the ongoing procedure or initiate a new procedure (e.g., SI request).

[0112] If there is an ongoing random access procedure triggered by a PDCCH order while the UE receives another PDCCH order indicating the same random access preamble, PRACH mask index and UL carrier, it shall be considered as the same ongoing random access procedure and shall not be re-initialized.

[0113] (Analysis) As mentioned above, in the LTM of Rel. 18, RACH by PDCCH order without RAR (PDCCH order RACH) is supported for candidate cells. Meanwhile, the serving cell can also be configured as a candidate cell.

[0114] In this case, there may be cases where the UE does not know whether the serving cell (e.g., SCell) configured as a candidate cell performs an existing PDCCH order RACH or a PDCCH order RACH without RAR.

[0115] In this way, if the RACH procedure to be applied cannot be appropriately selected depending on the candidate cell (type) to be set, cell switching may not be performed appropriately, which may result in a decrease in throughput / deterioration in communication quality.

[0116] Therefore, the present inventors have studied methods for distinguishing RACH procedures according to the candidate cells to be set, and have come up with an example of this embodiment.

[0117] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the drawings. Note that the following embodiments / aspects (e.g., cases) may be used alone or in combination of at least two of them.

[0118] (Various Alternative Readings, etc.) In the present disclosure, "A / B" and "at least one of A and B" may be interchangeable. Also, in the present disclosure, "A / B / C" may mean "at least one of A, B, and C."

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

[0120] In the present disclosure, Radio Resource Control (RRC), RRC parameters, RRC messages, higher layer parameters, fields, information elements (IEs), settings, etc. may be interchangeable. In the present disclosure, Medium Access Control (MAC) control elements (CEs), update commands, activation / deactivation commands, etc. may be interchangeable.

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

[0122] In the present disclosure, MAC signaling may use, for example, a MAC Control Element (MAC CE), a MAC Protocol Data Unit (PDU), etc. Broadcast information may be, for example, a Master Information Block (MIB), a System Information Block (SIB), Remaining Minimum System Information (RMSI), Other System Information (OSI), etc.

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

[0124] In the present disclosure, cell, PCI, serving cell, SpCell, source serving cell (source cell), reference / reference cell, CC, BWP, BWP within CC, and band may be interchangeable. In the present disclosure, additional cell, other cell, non-serving cell, cell with a different PCI, candidate cell, candidate serving cell, cell with a PCI different from the PCI of the current serving cell, another serving cell, target cell, target serving cell, and neighbor cell may be interchangeable. In the present disclosure, switch, change, and update may be interchangeable. Serving cell may be interchangeable with the serving cell before the switch or the serving cell after the switch. LTM application, cell application, and cell switch may be interchangeable. LTM application, beam application, and beam switch may be interchangeable.

[0125] In the present disclosure, RACH resource, RA resource, PRACH preamble, occasion, RACH occasion (RO), PRACH occasion, repetition resource, repetition setting resource, resource configured for RO / repetition, time instance and frequency instance, time resource and frequency resource, RO / preamble resource, repetition, PRACH resource, time / frequency resource for PRACH, preamble setting / index, mask setting / index, PRACH setting may be read as interchangeable.

[0126] In the present disclosure, a candidate cell and a candidate cell group may be interchangeable. A candidate cell in the present disclosure may be a candidate cell indicated in a PDCCH order. A PDCCH order and a DCI (e.g., DCI format 1_0) may be interchangeable. In the present disclosure, an RO, an RO index, and an RO# may be interchangeable.

[0127] In the present disclosure, RACH (procedure), PRACH transmission triggered by a PDCCH order, and PDCCH order RACH may be interchangeable. RACH without RAR, RACH without RAR monitoring (e.g., RACH without RAR monitoring), PDCCH order RACH without RAR, and PDCCH order RACH for LTM may be interchangeable. RACH procedure / PRACH transmission without RAR monitoring may be interchangeable with RACH procedure / PRACH transmission in which RAR monitoring is not required, or RACH procedure / PRACH transmission in which RAR monitoring is not required.

[0128] In the present disclosure, not having an RAR, not requiring RAR monitoring, not applying an RAR, not requiring an RAR, and being for LTM may be read interchangeably.

[0129] In the present disclosure, having an RAR, needing RAR monitoring, applying an RAR, and requiring an RAR may be read interchangeably.

[0130] The following description may be applied to inter-cell mobility (e.g., L1 / L2 inter cell mobility) or to communication control other than inter-cell mobility. L1 / L2 inter-cell mobility may be interpreted as at least one of cell switching, cell switch, and cell change.

[0131] (Wireless Communication Method) First Embodiment In the first embodiment, a method for distinguishing RACH procedures according to the types of candidate cells will be described.

[0132] The UE may determine / judge the type of RACH means to be applied based on the information (higher layer signaling (e.g., RRC / MAC CE) / physical layer signaling (DCI)) shown in the following aspects 1-1 to 1-2.

[0133] [Aspect 1-1] A (current) serving cell may be configured as a candidate cell. For a serving cell configured as a candidate cell, it is assumed that a PDCCH order RACH without RAR is not used (applied).

[0134] Whether to apply the PDCCH order RACH without RAR to the candidate cell may be predefined by a specification or may be determined based on UE capabilities, or may be configured / indicated by higher layer / physical layer signaling.

[0135] In addition, for a serving cell set as a candidate cell, an existing PDCCH order RACH (e.g., a PDCCH with an RAR) or a PDCCH order RACH without an RAR may be set / indicated by higher layer signaling / physical layer signaling.

[0136] Any of the above-mentioned PDCCH orders RACH may be configured / indicated for each cell / CC, or may be configured / indicated for all serving cells.

[0137] The PDCCH order RACH without RAR may be used / applied if a counter for LTM power ramping is configured for a serving cell configured as a candidate cell, in which case the power ramping counter may be configured (or may be assumed / presumed to be configured) for each candidate cell.

[0138] [Aspect 1-2] Whether to execute the existing PDCCH order RACH (e.g., PDCCH with RAR) or the PDCCH order RACH without RAR for a serving cell configured as a candidate cell may be explicitly / implicitly indicated by the PDCCH order (DCI).

[0139] That is, the UE may determine / judge the type of PDCCH order RACH (the RACH procedure to be applied) based on the PDCCH order.

[0140] Explicit Indication: One bit in the DCI may be used to indicate whether to perform a legacy PDCCH order RACH, a PDCCH order RACH without RAR, or whether the PDCCH order is an indication for LTM or a case other than LTM.

[0141] A new bit field or an existing reserved bit field may be used for the one bit.

[0142] Specifically, the one bit may indicate a PDCCH order RACH without an RAR (a PDCCH order RACH for LTM) by "0" and an existing PDCCH order RACH by "1." The correspondence between the bit values ​​is not limited to this and may be reversed.

[0143] <Implicit Instruction> The implicit instruction can apply either of the following options 1 or 2.

[0144] <Option 1> When a candidate cell is indicated by a candidate cell index (candidate cell ID), the type of PDCCH order RACH may be indicated by the candidate cell index, for example, when a specific candidate cell index is indicated, it may be indicated that a PDCCH order RACH without RAR is to be applied.

[0145] As a premise, a candidate cell index is also assigned to a serving cell set as a candidate cell. In this case, the field indicating the candidate cell index in the PDCCH order includes both an index for the serving cell and an index for the candidate cell.

[0146] Fig. 13 is a diagram showing an example of distinction of the RACH procedure according to the first embodiment. As shown in Fig. 12, for example, the following cells may be indicated using a 2-bit field: Serving cell: 00, Candidate cell #1: 01, Candidate cell #2: 10, Candidate cell #3: 11.

[0147] For example, assume that the candidate cell index of the serving cell configured as the candidate cell is #2. Here, when "00" is indicated, this may mean / indicate (may be interpreted as meaning / indicating) that the existing PDCCH order RACH is applied / used. Alternatively, when "10" is indicated, this may mean / indicate (may be interpreted as meaning / indicating) that the PDCCH order RACH without RAR is applied / used.

[0148] That is, the type of PDCCCH order RACH may be indicated (distinguished) based on whether the candidate cell index of the serving cell set as the candidate cell and the candidate index indicated by the PDCCCH order (DCI) are the same or different (serving cell).

[0149] More specifically, if the candidate cell index of the serving cell configured as the candidate cell and the candidate index indicated by the PDCCH order (DCI) are the same, the PDCCH order RACH for LTM may be indicated. On the other hand, if the candidate cell index of the serving cell configured as the candidate cell and the candidate index indicated by the PDCCH order (DCI) are different (if the indication by the PDCCH order is the serving cell), the existing PDCCH order RACH may be indicated.

[0150] <Option 2> The UE may determine / judge the type of PDCCH order RACH (the RACH procedure to be applied) based on the new bit field for LTM.

[0151] For example, if predetermined bits (X bits) of the new bit field for LTM are all 0, it may be indicated that the existing PDCCH order RACH is to be applied. Otherwise (if the X bits of the new bit field for LTM are not all 0), it may be indicated that the PDCCH order RACH without RAR is to be applied.

[0152] The above-mentioned predetermined bits may indicate a candidate cell index and whether the PRACH is a first transmission or a retransmission.

[0153] [Aspect 1-3] The UE may control power ramping according to the type of PDCCH order RACH as follows.

[0154] <Case 1> When a PDCCH order RACH without RAR is used / applied, the UE may perform power ramping using a counter for LTM (power ramping counter) set for each candidate cell or for all candidate cells.

[0155] <Case 2> When the existing PDCCH order RACH is used / applied, the UE may perform power ramping using a counter (power ramping counter) of the serving cell (configured for the serving cell) in the same manner as in the existing operation.

[0156] According to the first embodiment described above, the UE can appropriately determine / judge the RACH to be applied depending on the configured candidate cell.

[0157] Second Embodiment In a second embodiment, a method for distinguishing RACH procedures according to the type of candidate cell will be described.

[0158] <Analysis> In the existing specifications, if a serving cell is configured as a candidate cell and a PDCCH order RACH without RAR is triggered for that cell by a PDCCH order indicating the cell index of that cell, the UE must always monitor the RAR within the RAR window.

[0159] Fig. 14 is a diagram showing an example of DCI format 1_0 (DCI field) according to the second embodiment. Regarding Fig. 14, a description of parts common to Fig. 12 will be omitted, and only differences will be described. As shown in Fig. 14, DCI format 1_0 (PDCCH order) may include a cell indicator field. The number of bits of the cell indicator field may depend on the number of candidate cells.

[0160] More specifically, when a PDCCH order is transmitted to a candidate cell, the bit size N of the cell indicator field may be determined based on the number of candidate cells (e.g., C) configured in the RACH configuration provided for early TA acquisition, as follows:

[0161] Here, the number of candidate cells used in calculating the bit size is the number of candidate cells with RACH configuration provided for early TA acquisition + 1 (+1 corresponds to the serving cell).

[0162] As mentioned above, to obtain the TA of a candidate cell, a PDCCH order RACH without RAR is triggered by a cell indicator field of the PDCCH order indicating the candidate cell.

[0163] Also, to obtain the TA of the serving cell, the existing PDCCH order RACH (i.e., with RAR) is triggered by the cell indicator field of the PDCCH order indicating a specific value of the serving cell (e.g., all 0s).

[0164] However, the current specifications do not clearly define how to distinguish this from the existing behavior. Furthermore, it is unclear which behavior (i.e., with RAR / without RAR) is applied to obtain the TA of a candidate cell configured as the current serving cell (e.g., the current SCell).

[0165] Therefore, in this embodiment, the following Alt1 to Alt2 are proposed as a method of indicating which RACH operation to apply.

[0166] <Alt1> The UE may always use the existing PDCCH order RACH.

[0167] One way to indicate this is to not set the EarlyULSyncConfig for the candidate cell that is configured as the current serving cell, i.e., to obtain the TA of the candidate cell that is configured as the current serving cell, the cell indicator field of the PDCCH order may always indicate all zeros for the serving cell.

[0168] <Alt2> The UE may use both the existing PDCCH order RACH and the PDCCH order RACH without RAR.

[0169] An indication method may be by the cell indicator field of the PDCCH order, for example, if all values ​​are 0, an existing PDCCH order RACH is indicated, and if the value is a candidate cell index, a PDCCH order RACH without RAR may be indicated.

[0170] <Example of description of specifications> An example of description of specifications will be described below with reference to Fig. 15. Fig. 15A and Fig. 15B are diagrams showing an example of description of specifications related to the RACH according to the second embodiment.

[0171] The operation for distinguishing between the existing RACH operation and the RACH operation without RAR may be newly defined by the specification (FIG. 15A). Also, when a PDCCH order RACH without RAR is triggered in a candidate cell configured as the serving cell, the UE operation upon receiving the RAR may be defined by the specification (FIG. 15B).

[0172] As shown in FIG. 15A, the cell indicator (field) is set when the UE is configured with the higher layer parameter EarlyUlSyncConfig. The bit indicates the cell for the corresponding PRACH transmission.

[0173] Here, C is the number of candidate cells set by the upper layer parameter EarlyUlSyncConfig.

[0174] If the value is all zeros, this field indicates the serving cell; otherwise, it is a 0 bit.

[0175] It should be noted that the above-mentioned "if the values ​​are all 0" may be read as "if the values ​​are all 1".

[0176] As shown in Figure 15B, unless the serving cell is indicated as an LTM candidate cell by a PDCCH order, when a random access preamble is transmitted in the serving cell, the MAC entity performs specific actions regarding the reception of the random access response, regardless of the occurrence of a measurement gap.

[0177] Note that the above phrase "except when the serving cell is indicated as an LTM candidate cell by a PDCCH order" may be read as "except when the RACH procedure is triggered by a PDCCH order indicating an LTM candidate cell index" or "except when the RACH procedure is triggered by a PDCCH order indicating a non-zero cell indicator."

[0178] In addition, if the serving cell is indicated as an LTM candidate cell by a PDCCH order, a PDCCH order RACH without RAR may be applied.

[0179] According to the second embodiment described above, the UE can appropriately determine / judge the RACH to be applied depending on the configured candidate cell.

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

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

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

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

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

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

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

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

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

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

[0190] The specific UE capabilities may indicate at least one of the following: - Supporting specific processing / operation / control / information for at least one of the above embodiments; - Supporting two TAs for multi-TRP; - Supporting two TAs for intra-cell multi-TRP (e.g., intra-cell M-TRP); - Supporting two TAs for inter-cell multi-TRP (e.g., inter-cell M-TRP); - Supporting L1 / L2 inter-cell mobility (e.g., L1 / L2 inter-cell mobility); - Supporting PDCCH monitoring of candidate cells / deactive candidate cells / deactive SCells; - Supporting the maximum number of cells / TAGs / reference CCs for PDCCH monitoring; - Supporting cross-carrier (cross-CC) PDCCH orders; - Supporting existing PDCCH order RACH, PDCCH order RACH for LTM; - Supporting PDCCH order RACH with / without RAR.

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

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

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

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

[0195] (Supplementary Notes) The following inventions are supplementary notes regarding one embodiment (second embodiment) of the present disclosure. [Supplementary Note 1] A terminal comprising: a receiving unit that receives a downlink control channel order including information about a candidate cell; and a control unit that controls a physical random access channel transmission (PDCCH order RACH) triggered by the downlink control channel order based on the information about the candidate cell, wherein the control unit determines to apply a PDCCH order RACH with a random access response (RAR) or a PDCCH order RACH without an RAR based on a value of the candidate cell indicator field. [Supplementary Note 2] The terminal according to Supplementary Note 1, wherein the control unit applies a PDCCH order RACH with an RAR if all values ​​of the candidate cell indicator field are 0. [Supplementary Note 3] The terminal according to Supplementary Note 1 or Supplementary Note 2, wherein the control unit applies a PDCCH order RACH without an RAR if the value of the candidate cell indicator field indicates a candidate cell index. [Supplementary Note 4] The terminal according to any one of Supplementary Note 1 to Supplementary Note 3, wherein the control unit applies a PDCCH order RACH without RAR when the serving cell is indicated as an LTM candidate cell by a bona fide PDCCH order.

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

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

[0198] The wireless communication system 1 may also support dual connectivity between multiple Radio Access Technologies (RATs) (Multi-RAT Dual Connectivity (MR-DC)). MR-DC may include dual connectivity between LTE (Evolved Universal Terrestrial Radio Access (E-UTRA)) and NR (E-UTRA-NR Dual Connectivity (EN-DC)), dual connectivity between NR and LTE (NR-E-UTRA Dual Connectivity (NE-DC)), etc.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0219] In the present disclosure, downlink, uplink, etc. may be expressed without adding "link." Also, various channels may be expressed without adding "Physical" to the beginning.

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

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

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

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

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

[0225] The control unit 110 performs overall control of the base station 10. The control unit 110 can be configured from a controller, a control circuit, and the like that are explained based on common understanding in the technical field to which the present disclosure relates.

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

[0227] The transceiver unit 120 may include a baseband unit 121, a radio frequency (RF) unit 122, and a measurement unit 123. The baseband unit 121 may include a transmission processing unit 1211 and a reception processing unit 1212. The transceiver unit 120 may be configured with a transmitter / receiver, an RF circuit, a baseband circuit, a filter, a phase shifter, a measurement circuit, a transceiver circuit, etc., which are described based on common understanding in the technical field related to the present disclosure.

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

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

[0230] The transceiver 120 may transmit the above-mentioned downlink channel, synchronization signal, downlink reference signal, etc. The transceiver 120 may receive the above-mentioned uplink channel, uplink reference signal, etc.

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

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

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

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

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

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

[0237] The transceiver 120 (measurement unit 123) may perform measurements on the received signal. For example, the measurement unit 123 may perform Radio Resource Management (RRM) measurements, Channel State Information (CSI) measurements, etc. based on the received signal. The measurement unit 123 may measure received power (e.g., Reference Signal Received Power (RSRP)), received quality (e.g., Reference Signal Received Quality (RSRQ), Signal to Interference plus Noise Ratio (SINR), Signal to Noise Ratio (SNR)), signal strength (e.g., Received Signal Strength Indicator (RSSI)), propagation path information (e.g., CSI), etc. The measurement results may be output to the control unit 110.

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

[0239] The transmitting section and receiving section of the base station 10 in the present disclosure may be configured by at least one of the transmitting / receiving section 120, the transmitting / receiving antenna 130, and the transmission path interface 140.

[0240] The transceiver 120 may transmit a downlink control channel order including information about the candidate cell. The controller 110 may control reception of a physical random access channel transmission (PDCCH order RACH) triggered by the downlink control channel order controlled by the terminal based on the information about the candidate cell. The value of the candidate cell indicator field may indicate application of a PDCCH order RACH with a random access response (RAR) or a PDCCH order RACH without a RAR.

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

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

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

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

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

[0246] The transmitting / receiving unit 220 may be configured as an integrated transmitting / receiving unit, or may be composed of a transmitting unit and a receiving unit. The transmitting unit may be composed of a transmission processing unit 2211 and an RF unit 222. The receiving unit may be composed of a reception processing unit 2212, an RF unit 222, and a measurement unit 223.

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

[0248] The transceiver 220 may receive the above-mentioned downlink channel, synchronization signal, downlink reference signal, etc. The transceiver 220 may transmit the above-mentioned uplink channel, uplink reference signal, etc.

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

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

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

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

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

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

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

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

[0257] The measurement unit 223 may derive channel measurements for CSI calculation based on the channel measurement resources. The channel measurement resources may be, for example, non-zero power (NZP) CSI-RS resources. The measurement unit 223 may also derive interference measurements for CSI calculation based on the interference measurement resources. The interference measurement resources may be at least one of an NZP CSI-RS resource for interference measurement, a CSI-Interference Measurement (IM) resource, etc. Note that CSI-IM may be referred to as CSI-Interference Management (IM) or may be interchangeably read as Zero Power (ZP) CSI-RS. Note that in the present disclosure, CSI-RS, NZP CSI-RS, ZP CSI-RS, CSI-IM, CSI-SSB, etc. may be interchangeably read as interchangeable.

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

[0259] The transceiver 220 may receive a downlink control channel order including information about a candidate cell. The controller 210 may control a physical random access channel transmission (PDCCH order RACH) triggered by the downlink control channel order based on the information about the candidate cell. The controller 210 may determine whether to apply a PDCCH order RACH with a random access response (RAR) or a PDCCH order RACH without an RAR based on the value of the candidate cell indicator field. The controller 210 may apply a PDCCH order RACH with an RAR if the value of the candidate cell indicator field is all zeros. The controller 210 may apply a PDCCH order RACH without an RAR if the value of the candidate cell indicator field indicates a candidate cell index. The controller 210 may apply a PDCCH order RACH without an RAR if the serving cell is indicated as an LTM candidate cell by a bona fide PDCCH order.

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

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

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

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

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

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

[0266] The processor 1001, for example, runs an operating system to control the entire computer. The processor 1001 may be configured as a central processing unit (CPU) including an interface with peripheral devices, a control device, an arithmetic unit, a register, etc. For example, at least a part of the above-mentioned control unit 110 (210), transceiver unit 120 (220), etc. may be realized by the processor 1001.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0340] As used in this disclosure, any reference to an element using a designation such as "first," "second," etc. does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient method of distinguishing between two or more elements. Thus, a reference to a first and a second element does not imply that only two elements may be employed or that the first element must in some way precede the second element.

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

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

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

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

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

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

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

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

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

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

[0351] In this disclosure, where articles are added by translation, such as a, an, and the in English, the disclosure may include that the nouns following these articles are in the plural form.

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

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

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

[0355] In the present disclosure, timing, time, duration, time instance, any time unit (e.g., slot, subslot, symbol, subframe), period, occasion, resource, etc. may be read interchangeably.

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

Claims

1. A terminal comprising: a receiving unit that receives a downlink control channel order including information regarding a candidate cell; and a control unit that controls a physical random access channel transmission (PDCCH order RACH) triggered by the downlink control channel order based on the information regarding the candidate cell, wherein the control unit determines the application of a PDCCH order RACH with a random access response (RAR) or a PDCCH order RACH without an RAR based on the value of the candidate cell indicator field.

2. The terminal according to claim 1, wherein the control unit applies a PDCCH order RACH with RAR if the values ​​of the candidate cell indicator field are all 0.

3. The terminal according to claim 1, wherein the control unit applies a PDCCH order RACH without an RAR if the value of the candidate cell indicator field indicates a candidate cell index.

4. The terminal according to claim 1, wherein the control unit applies a PDCCH order RACH without RAR when the serving cell is indicated as an LTM candidate cell by a bona fide PDCCH order.

5. A wireless communication method for a terminal, comprising: a step of receiving a downlink control channel order including information regarding a candidate cell; a step of controlling a physical random access channel transmission (PDCCH order RACH) triggered by the downlink control channel order based on the information regarding the candidate cell; and a step of determining the application of a PDCCH order RACH with a random access response (RAR) or a PDCCH order RACH without an RAR based on the value of the candidate cell indicator field.

6. A base station comprising: a transmitting unit that transmits a downlink control channel order including information regarding a candidate cell; and a control unit that controls reception of a physical random access channel transmission (PDCCH order RACH) triggered by a downlink control channel order controlled by a terminal based on the information regarding the candidate cell, wherein the value of the candidate cell indicator field indicates application of a PDCCH order RACH with a random access response (RAR) or a PDCCH order RACH without an RAR.

Images