Terminal, wireless communication method, and base station

Abstract

A terminal according to one embodiment of the present disclosure is provided with: a reception unit that receives a cell handover command including information relating to a target cell that is a handover candidate for a serving cell; and a control unit that controls the path loss calculation on the basis of the measurement result of the reference signal before or after the reception of the cell handover command.

Description

Technical Field

[0001] This disclosure relates to terminals, wireless communication methods, and base stations in next-generation mobile communication systems. Background Technology

[0002] In Universal Mobile Telecommunication System (UMTS) networks, Long Term Evolution (LTE) was standardized with the aim of achieving higher data rates and lower latency (Non-Patent Document 1). Furthermore, LTE-Advanced (3GPP Rel. 10-14) was standardized with the aim of further increasing capacity and improving the height of LTE (3rd Generation Partnership Project (3GPP) Release (Rel.) 8, 9).

[0003] The development of successor systems to LTE is also underway (e.g., also known as the 5th generation mobile communication system (5G), 5G+ (plus), the 6th generation mobile communication system (6G), New Radio (NR), 3GPP Rel.15 and later, etc.).

[0004] Existing technical documents

[0005] Non-patent literature

[0006] Non-patent document 1: 3GPP TS 36.300 V8.12.0 “Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 (Release 8)”, April 2010 Summary of the Invention

[0007] The problem that the invention aims to solve

[0008] In future wireless communication systems (e.g., wireless communication systems after Rel.17 / 5G), it is envisioned that communication will be controlled based on multiple inter-cell mobility, including non-serving cells, or by utilizing multiple transmit / receive points (e.g., multi-TRP (MTRP)). It is also envisioned that, within inter-cell mobility, candidate cells will be designated, and handover / reception between serving cells and candidate cells will be performed using L1 / L2 signaling.

[0009] For example, in LTM of Rel.18, candidate cells support RACH based on PDCCH commands without RAR (PDCCH command RACH). On the other hand, the serving cell can also be set as a candidate cell.

[0010] In this situation, the method for path loss calculation / power control is unclear. If the method for path loss calculation / power control is unclear, an appropriate random access procedure cannot be performed, resulting in concerns about reduced communication throughput.

[0011] This disclosure was made in view of this purpose, one of which is to make the method of path loss calculation / power control clear, and to provide a terminal, wireless communication method and base station capable of appropriately controlling communication.

[0012] Methods for solving problems

[0013] One aspect of this disclosure relates to a terminal comprising: a receiving unit for receiving a cell handover command, the cell handover command including information relating to a target cell that is a handover candidate to become a serving cell; and a control unit for controlling path loss calculation based on measurement results of reference signals before or after receiving the cell handover command.

[0014] Invention Effects

[0015] According to one aspect of this disclosure, the method for path loss calculation / power control is made explicit, enabling appropriate control of communication. Attached Figure Description

[0016] Figure 1A This is a diagram illustrating an example of UE movement in Rel.17. Figure 1B This is a diagram illustrating an example of UE movement in Rel.18.

[0017] Figure 2 This is a diagram illustrating an example of the LTM process.

[0018] Figure 3 This is a diagram illustrating an example of comparing L3 switching with LTM in Rel.18.

[0019] Figure 4 This is a diagram illustrating an example of the association between a serving cell and a candidate cell.

[0020] Figure 5A This is a diagram representing the first example of option 2 for candidate cell settings. Figure 5B This is a diagram representing the second example of option 2 for candidate cell settings.

[0021] Figure 6 This is a diagram illustrating example 1 of serving cell handover.

[0022] Figure 7 This is a diagram representing Example 2 of a serving cell handover.

[0023] Figure 8 This is a diagram representing example 3 of a serving cell handover.

[0024] Figure 9 This is a diagram that represents an overview of L1L2-triggered mobility (LTM).

[0025] Figure 10 This is a diagram representing a RACH (PDCCH ordered RACH) based on PDCCH indications used for serving cells, with random access response (RAR) monitoring.

[0026] Figure 11 It is a diagram representing a RACH (PDCCH ordered RACH) based on PDCCH indications used for candidate cells without Random Access Response (RAR) monitoring.

[0027] Figure 12 This is a diagram representing DCI format 1_0 scrambled by CRC via C-RNTI.

[0028] Figure 13 This is a diagram representing an example of a timing advance group (TAG) to which a cell belongs within a cell group.

[0029] Figure 14 This is a diagram illustrating an example of a MAC CE used to execute timed advance commands.

[0030] Figure 15 This is a diagram illustrating other examples of MAC CE used for timed advance commands.

[0031] Figure 16 This diagram illustrates an example of how TAG settings are supported when a candidate cell is associated with a TAG ID.

[0032] Figure 17 This is a diagram illustrating an example of path loss calculation according to the first embodiment.

[0033] Figure 18 This is a diagram illustrating an example of path loss calculation involved in the second embodiment.

[0034] Figure 19 This is a diagram illustrating an example of path loss calculation involved in the third embodiment.

[0035] Figure 20 This is a diagram illustrating an example of the calculations related to power gradual increase involved in the fifth embodiment.

[0036] Figure 21 This is a diagram illustrating an example of the schematic structure of a wireless communication system according to one embodiment.

[0037] Figure 22 This is a diagram illustrating an example of the structure of a base station according to one embodiment.

[0038] Figure 23 This is a diagram illustrating an example of the structure of a user terminal according to one embodiment.

[0039] Figure 24 This is a diagram illustrating an example of the hardware structure of a base station and a user terminal according to one embodiment.

[0040] Figure 25 This is a diagram illustrating an example of a vehicle according to one embodiment. Detailed Implementation

[0041] (TCI, Spatial Relations, QCL)

[0042] In NR, research is being conducted on the reception processing (e.g., at least one of receiving, demapping, demodulation, and decoding) and transmission processing (e.g., at least one of transmitting, mapping, precoding, modulation, and encoding) of at least one of control signals and channels (referred to as signal / channel) in the UE based on the Transmission Configuration Indication state (TCI state).

[0043] TCI states can also represent the TCI states of signals / channels applied to the downlink. The equivalent TCI states of signals / channels applied to the uplink can also be described as spatial relations.

[0044] The so-called TCI status is information related to the quasi-co-location (QCL) of a signal / channel, and can also be referred to as spatial reception parameters, spatial relation information, etc. The TCI status can also be set for the UE on a per-channel or per-signal basis.

[0045] QCL is an indicator of the statistical properties of a signal / channel. For example, it can also mean that when a signal / channel has a QCL relationship with other signals / channels, it can be assumed that at least one of the following is the same among these different signals / channels: Doppler shift, Doppler spread, average delay, delay spread, and spatial parameter (e.g., spatial Rx parameter) (with regard to at least one of them being the QCL).

[0046] Additionally, the spatial reception parameters may also correspond to the UE's receive beam (e.g., receive analog beam), and the beam may also be determined based on the spatial QCL. The QCL (or at least one element of the QCL) in this disclosure may also be rewritten as sQCL (spatial QCL).

[0047] A QCL can also be defined with multiple types (QCL types). For example, four QCL types, or types AD, can be set, where the parameters (or parameter sets) that can be assumed to be the same are different. These parameters (also called QCL parameters) are represented as follows:

[0048] • QCL Type A (QCL-A): Doppler shift, Doppler spread, average delay, and delay spread.

[0049] • QCL Type B (QCL-B): Doppler shift and Doppler extension,

[0050] • QCL Type C (QCL-C): Doppler shift and average delay,

[0051] • QCL Type D (QCL-D): Spatial reception parameters.

[0052] The UE envisions a relationship between a certain Control Resource Set (CORESET), channel, or reference signal and other CORESETs, channels, or reference signals in a specific QCL (e.g., QCL type D), which can also be called a QCL assumption.

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

[0054] The TCI state can also be, for example, information related to the QCL between the target channel (in other words, the reference signal (RS) used by the channel) and other signals (e.g., other RSs). The TCI state can also be set (indicated) by higher-layer signaling, physical-layer signaling, or a combination thereof.

[0055] In addition, the channel / signal that becomes the application object in the TCI state can also be called the target channel / reference signal (target channel / RS), or simply the target, etc. The other signals mentioned above can also be called reference RS, source RS, or simply reference, etc.

[0056] The channel that is set (specified) to TCI state or spatial relationship can be, for example, at least one of the following: downlink shared channel (Physical Downlink Shared Channel (PDSCH))), downlink control channel (Physical Downlink Control Channel (PDCCH))), uplink shared channel (Physical Uplink Shared Channel (PUSCH))), and uplink control channel (Physical Uplink Control Channel (PUCCH))).

[0057] Furthermore, the RS that is related to the channel as QCL can be at least one of the following: a Synchronization Signal Block (SSB), a Channel State Information Reference Signal (CSI-RS), a Measurement Reference Signal (Sounding Reference Signal (SRS)), a Tracking CSI-RS (also known as a Tracking Reference Signal (TRS)), a QCL Detection Reference Signal (also known as a QRS), or a DeModulation Reference Signal (DMRS).

[0058] An SSB is a block of signals that includes at least one Primary Synchronization Signal (PSS), a Secondary Synchronization Signal (SSS), and a broadcast channel (Physical Broadcast Channel (PBCH)). An SSB can also be referred to as an SS / PBCH block.

[0059] The RS of QCL type X in TCI state can also refer to the RS that is in a relationship of QCL type X with a certain channel / signal (DMRS), and the RS can also be called the QCL source of QCL type X in TCI state.

[0060] (L1 / L2 inter-cell mobility)

[0061] As described above, the study investigates UL transmission of a UE to one or more cells / TRPs. As a procedure in this case, consider scenario 1 or scenario 2 below. Additionally, in this disclosure, the serving cell can also be rewritten as the TRP within the serving cell. Layer 1 / Layer 2 (L1 / L2) and the DCI / Medium Access Control Element (MAC CE) can also be rewritten. In this disclosure, a PCI that differs from the physical cell ID (Physical Cell Identity (PCI)) of the current serving cell is sometimes abbreviated as "different PCI". Non-serving cells, cells with different PCIs, and additional cells can also be rewritten.

[0062] <Scenario 1>

[0063] Scenario 1 could be a scenario that corresponds to inter-cell mobility in multi-TRP, but it could also be a scenario that does not correspond to inter-cell mobility in multi-TRP.

[0064] (1) The UE receives from the serving cell: the setting of the SSB for beam measurement of the TRP corresponding to a different PCI from the serving cell, and the settings required for using radio resources for data transmission and reception, which include resources of different PCIs.

[0065] (2) The UE performs beam measurement for the TRP corresponding to different PCIs and reports the beam measurement results to the serving cell.

[0066] (3) Based on the above report, the Transmission Configuration Indication (TCI) status associated with the TRP corresponding to different PCIs is activated by L1 / L2 signaling from the serving cell.

[0067] (4) The UE uses the dedicated channel on the TRP corresponding to different PCIs for transmission and reception.

[0068] (5) The UE needs to always cover the serving cell, including in the case of multiple TRPs. Similar to previous systems, the UE needs to use common channels from the serving cell (Broadcast Control Channel (BCCH), Paging Channel (PCH)), etc.

[0069] In Scenario 1, when the UE transmits and receives signals with the additional cell / TRP (the TRP corresponding to the PCI of the additional cell), the serving cell (the assumption of the serving cell in the UE) is not changed. The UE can also have higher-layer parameters associated with the PCI of a non-serving cell set from the serving cell. Scenario 1 can also be applied in Rel. 17, for example.

[0070] Figure 1A This diagram illustrates an example of UE movement in Rel.17. Imagine the UE moving from PCI#1 cell (serving cell) to PCI#3 cell (additional cell) (overlapping with the serving cell). In this scenario, L1 / L2-based handover to the serving cell is not supported in Rel.17.

[0071] An additional cell is a cell that holds an additional PCI different from that of the serving cell. The UE can receive / transmit UE-dedicated channels from the additional cell. For the UE to receive UE-common channels (e.g., system information / paging / SMS), it needs to be within the coverage area of ​​the serving cell. If the UE moves outside the coverage area of ​​the serving cell, a handover (also known as L3 mobility) is required.

[0072] <Scenario 2>

[0073] In Scenario 2, L1 / L2 inter-cell mobility is applied. With L1 / L2 inter-cell mobility, serving cell changes can be performed using functions such as beam control without RRC reset. In other words, transmission and reception with the additional cell can be performed without handover. Handover requires RRC reconnection, creating periods where data communication is impossible. Therefore, by applying L1 / L2 inter-cell mobility that does not require handover, data communication can continue even during serving cell changes. Scenario 2 can also be applied, for example, in Rel. 18. In Scenario 2, for example, the following process is performed.

[0074] (1) In order to change the beam measurement / serving cell, the UE receives the SSB settings of the cell (additional cell) holding a different PCI from the serving cell.

[0075] (2) The UE performs beam measurements for cells using different PCIs and reports the measurement results to the serving cell.

[0076] (3) The UE can also receive the settings (serving cell settings) of cells with different PCIs through higher-layer signaling (e.g., RRC). That is, it can also make advance settings related to serving cell changes. This setting can be made together with the setting in (1) or separately.

[0077] (4) Based on the above report, the TCI status of cells with different PCIs can also be activated via L1 / L2 signaling according to the change of the serving cell. The activation of the TCI status and the change of the serving cell can also be carried out separately.

[0078] (5) The UE changes its serving cell (the concept of the serving cell) and uses a pre-set UE-specific channel and TCI state to start receiving / transmitting.

[0079] That is, in Scenario 2, the serving cell (the assumption of the serving cell in the UE) is updated via L1 / L2 signaling. Scenario 2 can also be applied in Rel.18.

[0080] Figure 1BThis is a diagram showing an example of the movement of a UE in Rel. 18. In Rel. 18, the serving cell is switched via L1 / L2 (e.g., DCI / MAC CE). The UE can receive / send UE-specific channels / common channels with the new serving cell (or, target serving cell). The UE can also move out of the coverage area of the current serving cell (e.g., Current serving cell).

[0081] <L1L2-triggered mobility (LTM) process>

[0082] Figure 2 This is a diagram showing an example of the LTM process. In addition, L1 / L2 inter-cell mobility and L1L2-triggered mobility (LTM) can also be rewritten with each other. In addition, Figure 2 The process is the process corresponding to Scenario 2 above. The following will explain each process of Figure 2 in detail.

[0083] 1: After RRC connection, the UE sends a MeasurementReport message to the base station (gNB). The gNB determines the use of LTM based on the MeasurementReport and starts preparing candidate cells.

[0084] 2: The gNB sends an RRCReconfiguration message containing the LTM candidate cell setting of one or more candidate cells to the UE.

[0085] 3: The UE saves the received LTM candidate cell setting and sends an RRCReconfigurationComplete message to the gNB.

[0086] 4a / 4b: Before receiving the cell switch command, the UE performs DL / UL synchronization with the candidate cell and obtains the timing advance (TA). CMAX, f, c（i） 7>

[0087] 5: The UE performs L1 measurements on the set candidate cells and sends a measurement report of the lower layer (physical layer, L1) to the gNB. In addition, the UE can also send a measurement report to the gNB before UL synchronization with the candidate cell. The step 5 can also be implemented between the above 4a / 4b. In addition, activation of the TCI state can also be implemented between the UE and the current serving cell between step 4b and step 5.

[0088] 6: The gNB decides to execute the cell switch to the target cell and sends a MAC CE triggering the cell switch containing the candidate setting index of the target cell to the UE. Thereby, the cell setting of the UE is switched to the setting of the target cell.

[0089] 7. When the random access procedure needs to be included in cell handover, the UE performs the random access procedure towards the target cell. Alternatively, the UE can also perform the random access procedure based on a RACH procedure request from the gNB.

[0090] 8: The UE notifies the gNB that the cell handover to the target cell has ended normally.

[0091] In addition, in order to perform the next LTM cell handover, the UE can also execute steps 4 to 8 above multiple times based on the LTM candidate cell settings received in step 2.

[0092] <Shortening interruption time>

[0093] In Rel.18 L1 / L2 inter-cell mobility (e.g., scenario 2 above), the UE can reduce the time without data transmission (interruption time). When applying Rel.18 LTM, compared to the method of handover based on L3 measurement results (L3 handover), the time without data transmission (interruption time) can be reduced. The following describes each specific process.

[0094] Figure 3 This diagram illustrates an example comparing L3 handover with LTM in Rel.18. In the L3 handover scenario, firstly, the UE performs L3 measurements and decides to handover based on the results. Then, the UE and the current serving cell perform RRC reset. Next, the UE performs DL synchronization and UL synchronization with the target serving cell. The UE performs L1 measurements / reports for the target serving cell and, upon receiving beam indication, sends initial UL data to the target serving cell. In this case, the UE does not send UL data during the period from the handover decision until the initial UL data is sent (an interruption).

[0095] In the LTM scenario of Rel.18, firstly, the UE performs L3 measurements. Then, the UE, the current serving cell, and the target serving cell perform RRC resets. Next, the UE performs DL synchronization with the target serving cell. Then, the UE performs L1 measurements / reports for both the current and target serving cells and performs UL synchronization. Then, the current serving cell sends a cell handover command (including beam indication) based on L1 / L2 (DCI / MAC CE) to the UE. Finally, the UE sends the initial UL data to the target serving cell. In this case, although the period from the receipt of the cell handover command to the transmission of the initial UL data is an interruption time for UL transmission, it is shorter compared to the L3 handover scenario.

[0096] (Setting up multiple candidate cells)

[0097] Figure 4 This diagram illustrates an example of the association between a serving cell and candidate cells. Let SpCell#0, SCell#1, or SCell#2 be the serving cell. SpCell refers to a special cell (including the primary cell (PCell) and the primary / secondary cell (PSCell)). SCell refers to the secondary cell. SpCell#0 is associated with candidate cells #0-1, #0-2, and #0-3. SCell#1 is associated with candidate cell #1-1. SCell#2 is associated with candidate cells #2-1 and #2-2. Thus, a serving cell can also be associated with more than one candidate cell (candidate serving cell).

[0098] Regarding the setting of the candidate cell (candidate cell) in the case of changing the serving cell, consider options 1 and 2 as follows.

[0099] <Option 1>

[0100] As with inter-cell mobility in Rel.17, the information in the ServingCellConfig can also include information related to multiple candidate cells. In this case, multiple candidate cells need to share the same PDCCH / PDSCH / UL settings with the serving cell.

[0101] For example, in Rel.17 inter-cell mobility, "mimoParam-r17" is appended under ServingCellConfig to add PCI configuration information. mimoParam-r17 can also contain additionalPCI-ToAddModList-r17, which is a list of additional SSBs with PCIs different from the serving cell's PCI. In candidate cells (additional cells, cells with additional PCIs), the same settings as the serving cell can be applied, except for some information.

[0102] <Option 2>

[0103] Multiple candidate cells can also be assigned complete settings corresponding to each cell (e.g., ServingCellConfig), or the carrier aggregation (CA) configuration framework can be reused to associate them with each serving cell. That is, candidate cells can also be assigned different settings instead of sharing configuration information with the serving cell. Because the UE is provided with complete settings for each candidate cell, it is able to communicate appropriately with the candidate cells.

[0104] Within the CA (Cell Controller) configuration framework, SpCells can be configured for each cell group, and multiple SCells can be added. Alternatively, by reusing the CA framework, serving cells can be configured for each cell group based on L1 / L2 inter-cell mobility, and multiple candidate cells can be configured. Candidate cells can also be activated / deactivated via MAC CE (Machine-Assisted Cell Execution). Alternatively, the TCI (Tracking Control Information) information corresponding to the candidate cells can be activated / deactivated via MAC CE, thereby activating / deactivating the candidate cells. This method is considered beneficial for reducing the complexity of UE (User Equipment) operations.

[0105] Figure 5A This is a diagram representing the first example of option 2 for candidate cell settings. Figure 5A In the example, the common candidate cell pool used for cell handover in the MCG / SCG is applied to the candidate cells. That is, the candidate cells are treated as a pool (group) regardless of the frequency band.

[0106] Figure 5B This is a diagram representing the second example of option 2 for candidate cell settings. Figure 5B In this example, multiple cell groups are configured, enabling cell group handover via L1 / L2 signaling. Candidate cells are configured for each cell group, and the configuration for each group includes the indexes of the corresponding SpCell and SCell.

[0107] (Signaling used for service cell change instructions)

[0108] This section describes the implicit or explicit signaling used for serving cell change indications.

[0109] [Method 1]

[0110] In Method 1, the implicit signaling used for service cell change indication is described.

[0111] [[Option 1-1]]

[0112] When a specific Control Resource Set (CORESET) (e.g., at least one of CORESET#0, CH5Type0-CSS, or CH6 / CH7 / CH8 CSS) and one or more TCI states associated with a cell with a PCI different from the serving cell's PCI are indicated (activated) via MAC CE (for a specific CORESET, when one or more TCI states associated with a cell with a PCI different from the serving cell's PCI are indicated / activated via MAC CE), the UE can also determine to change the serving cell to another cell (cell x, a cell with a different PCI). That is, this activation can also implicitly indicate changing the serving cell to another cell.

[0113] In this case, the UE can also update the beam 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 mentioned above.

[0114] [[Options 1-2]]

[0115] When MAC CE activates / deactivates the TCI state of PDSCH, if all of the TCI states activated by MAC CE are associated with the same cell x with a PCI different from the serving cell, the UE can also determine that the serving cell has been changed to another cell (cell x). That is, this association can also implicitly indicate that the serving cell has been changed to another cell.

[0116] When this option is applied, if the NW (base station) does not change the serving cell, the MAC CE needs to include the TCI state associated with other cells (e.g., the current serving cell or a cell with a second different PCI) when activating the TCI state of the PDSCH associated with a cell with a different PCI.

[0117] [[Options 1-3]]

[0118] When MAC CE activates / deactivates a unified TCI state (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 can also determine that it will change the serving cell to another cell (cell x). That is, this association can also implicitly indicate that the serving cell will be changed to another cell.

[0119] [Method 2]

[0120] In Method 2, the explicit signaling used for serving cell change indication is described. Method 2 is, for example, applied to Scenario 2 described above.

[0121] [[Option 2-1]]

[0122] The following is an example of a serving cell change instruction. Additionally, the activation / deactivation of a non-serving cell, changes to the serving cell, and sending / receiving data with other cells (non-serving cells) that have a physical cell ID different from the serving cell can also be mutually modified.

[0123] The UE may also receive a new MAC CE for the activation / deactivation of a non-serving cell, which includes at least one of the fields (information) corresponding to the non-serving cell as shown in (1) to (3) below. Upon receiving this MAC CE, the UE may also determine that the serving cell has been changed to another cell (non-serving cell). Furthermore, the UE may also control the transmission and reception of DL / UL signals with the non-serving cell based on this information. In addition, there may be one or more non-serving cells. In the example shown below, a MAC CE containing multiple fields representing multiple non-serving cell indices is applied.

[0124] (1) Service cell ID.

[0125] (2) BWP ID.

[0126] (3) The non-serving cell ID used for activation. The non-serving cell ID can also be replaced with any information corresponding to the non-serving cell (that can identify the non-serving cell).

[0127] As an example of (3), any of (3-1) to (3-5) can also be applied.

[0128] (3-1) PCI (PCI that is used directly). For example, 10 bits are used.

[0129] (3-2) Recreated index (new ID) for non-serving cells. The new ID can also be associated with a portion of the PCI and is set only for the serving and non-serving cells used by the UE (and that it can use). The new ID reduces the number of bits compared to the PCI.

[0130] (3-3) CSI report setting ID (CSI-ReportConfigId) (the case where CSI-ReportConfig corresponds to one or more non-serving cells).

[0131] (3-4) CSI Resource Configuration ID (CSI-ResourceConfigId) (CSI-ResourceConfigId corresponds to one or more non-serving cells).

[0132] (3-5) shows the bitmap for the activation / deactivation of each non-serving cell. The size (number of bits) of the bitmap can also be the same as the number of non-serving cells set on the CC. For example, in the case of activating the second of three non-serving cells, it is set to "010".

[0133] At least one of the information contained in the MAC CE can also be included in the DCI. Alternatively, at least one of the serving cells activated via the MAC CE can also be indicated via the DCI. The MAC CE / DCI can also include a field indicating the TCI status / SSB / CSI-RS from a cell with a different PCI, enabling the identification of the DL beam monitored by the UE on the target cell (the changed serving cell). The UE can also use the TCI status / SSB / CSI-RS to generate and send a beam report (CSI report).

[0134] [[Option 2-2]]

[0135] The UE can also receive a MAC CE with a new 1-bit field "C" appended to the existing MAC CE. This field indicates whether a change of serving cell is being performed. The UE can also receive this MAC CE and determine whether to change the serving cell to another cell based on this field.

[0136] [[Options 2-3]]

[0137] For MAC CE in option 2-2, the fields representing the serving cell index / PCI / other ID (such as the new ID in option 2-1 above) and the TCI status / SSB / CSI-RS of the target cell (the changed serving cell) can also be included in MAC CE.

[0138] In this way, the indication for serving cell change is indicated via MAC CE / DCI, so the UE can make appropriate changes to the serving cell.

[0139] [Serving Cell Handover Example 1]

[0140] Figure 6This diagram illustrates Example 1 of serving cell handover. For example, in the serving cell SpCell#0 of the MCG / SCG, if the serving cell is instructed to be changed to candidate cell#0-2 via L1 / L2 signaling, candidate cell#0-2 becomes the new serving cell SpCell#0. Similarly, for example, in the serving cell SCell#2 of the MCG / SCG, if the serving cell is instructed to be changed to candidate cell#2-1 via L1 / L2 signaling, candidate cell#2-1 becomes the new serving cell SCell#2.

[0141] [Serving Cell Handover Example 2]

[0142] The RRC / MAC CE can also set global candidate cell IDs (cell#3,...,8) for each cell group, each band, each FR, and each UE. The UE can also be instructed to hand over the serving cell through this global candidate cell ID.

[0143] Figure 7 This is a diagram illustrating example 2 of a serving cell handover. (Compared to...) Figure 5A Similarly, a pool of multiple candidate cells can be configured, and the serving cell can be switched to any (activated) candidate cell within the pool via L1 / L2 signaling. In this case, the configured candidate cell can become either a SpCell or an SCell based on L1 / L2 signaling.

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

[0145] [Serving Cell Handover Example 3]

[0146] The RRC / MAC CE can also configure cell groups. The UE can also perform serving cell handover based on cell group handover.

[0147] Figure 8 This diagram illustrates Example 3 of serving cell handover. The UE receives an indication of a change in the cell group with the serving cell (a change to candidate cell group #1) via the 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. That is, the serving cell group is switched.

[0148] (An overview of L1L2-triggered mobility (LTM))

[0149] In L1L2-triggered mobility (LTM) supported after Rel.18, L1 inter-frequency measurement (e.g., L1 inter-frequency measurement) can also be supported. Furthermore, at least SSB-based candidate cell DL synchronization / UL synchronization can be supported before cell handover commands.

[0150] Figure 9 This is a diagram illustrating the general concept of L1L2-triggered mobility (LTM). LTM and L1 / L2 inter-cell mobility can also be rewritten interchangeably.

[0151] During UE reconfiguration, the UE receives candidate cell configurations from the NW. UE reconfiguration includes T... RRC T proccesing1 / T proccesing2 T RRC (For example, a maximum of 10ms) is the processing time for RRC reconfiguration (RRC reconfiguration) to carry candidate cell settings (candidate configurations). proccesing1 / T proccesing2 (For example, a maximum of 20ms for the same FR and a maximum of 40ms for different FRs) refers to the time allotted for UE processing before and after the cell handover command. This includes processes such as L2 / 3 reconfiguration, RF retuning, baseband retuning, and, where necessary, security updates.

[0152] DL synchronization includes T search T Δ T margin T search (For example, 0ms when the cell is known, and a maximum of 60ms when the cell is unknown) is the time required to search for the target cell. Δ This is the time used for fine-grained tracking and acquisition of all timing information. T margin (For example, a maximum of 2ms) is the time used for post-processing of SSB and CSI-RS.

[0153] L1 measurement includes T meas (SMTC cycle (e.g., 20ms)). T meas It is the measurement delay from the appearance of the target to the cell handover command.

[0154] UL synchronization includes T IU T RAR T cmd T IU (For example, a maximum of 15ms) is the indeterminate interruption time when an initial PRACH opportunity (occasion) is obtained in a new cell. T RAR (For example, 4ms) is the RAR latency. T cmd (For example, a maximum of 5ms) is the processing time for L1 / L2 commands (HARQ and paging).

[0155] T cmd The T after that first-data It is the time when the UE performs its initial DL reception / UL transmission on the indicator beam of the target cell after RAR.

[0156] Figure 10 This diagram illustrates an example of a PDCCH-ordered RACH with RAR monitoring. Furthermore, in this disclosure, source cell and source cell group can be interchanged. Additionally, candidate cell and candidate cell group can also be interchanged.

[0157] The source cell can also send information related to the configuration of candidate cells (e.g., candidate cell configuration information) to the UE. Furthermore, the source cell can also send PDCCH commands (e.g., DCI format 1_0) used in PRACH triggering to the UE. Candidate cells (e.g., a candidate cell) / Random Access Hours (ROs) that can be indicated as the target of PRACH triggering / transmission can also be identified via PDCCH commands (order) (or DCI). For TAG / TA acquisition, the UE sends PRACH during the RACH process to the candidate cell based on the PDCCH commands.

[0158] Next, the source cell sends a Responding Message (RAR) to the UE for the PRACH. The RAR may also contain information related to the TA (e.g., a TA indication). The RAR (e.g., the PDSCH containing the RAR / the PDCCH that schedules the PDSCH) may also be monitored in a specific search space (e.g., the Common Search Space (CSS)) of a specific cell (e.g., SpCell) within the current serving cell (only within the Distributed Unit (DU)). Furthermore, TA maintenance is performed in the source cell.

[0159] Next, the source cell can also send a cell handover command to the UE. Furthermore, TA information can be moved from the source cell to / notified to the target cell. The UE can also control UL transmission based on the acquired TA after a cell handover. For example, if UL synchronization of all candidate cells is not completed after the initial cell handover, the UE can use the initial TA to perform the initial UL transmission.

[0160] Figure 11 This is a diagram illustrating an example of a PDCCH-ordered RACH (RACH based on PDCCH commands) without RAR monitoring. About Figure 11 This is only to explain the relationship with Figure 10 The differences.

[0161] exist Figure 11 In this example, the UE may be designated as the target of PRACH triggering / transmission from one or more candidate cells (e.g., multiple candidate cells) / random access opportunities through the PDCCH command used in PRAH triggering. For multiple TAG / TA acquisitions, the UE may also send PRACH during the RACH process to the candidate cells based on the PDCCH command. The source cell does not send a PRACH acknowledgment signal (e.g., RAR). The source cell may also use cell handover commands to indicate TA-related information to the UE (e.g., TA indication).

[0162] In this disclosure, RACH without RAR and RACH without RAR monitoring (e.g., RACH without RAR monitoring) can also be rewritten to each other. RACH can also be rewritten as PRACH transmission triggered by a PDCCH command. RACH / PRACH transmission without RAR monitoring can also be rewritten as RACH / PRACH transmission that does not require RAR monitoring, or RACH / PRACH transmission that does not request RAR monitoring.

[0163] [PDCCH command]

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

[0165] In the case of PRACH transmission triggered by the PDCCH command, if the value of the random access preamble index field is not zero, the PRACH mask index field indicates the PRACH timing associated with the SS / PBCH block index represented by the SS / PBCH block index field of the PDCCH command.

[0166] Figure 12 This is a diagram representing DCI format 1_0 scrambled by CRC via C-RNTI. Frequency domain resource assignment can also be used, for example, for RACH (PDCCH order) based on PDCCH indication. For example, if all frequency domain resource assignments are represented as 1, it can also mean that DCI format 1_0 is used as a PDCCH order.

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

[0168] In L1 / L2-based mobility (e.g., LTM) supported after Rel.18, candidate cell TA acquisition can also be supported before the cell handover command. The candidate cell TA acquisition mechanism can also at least support RACH of the PDCCH command. The PDCCH command can also be triggered solely by the source cell (e.g., the serving cell). The candidate cell / candidate cell RACH timing (RO) can also be indicated by the DCI sent in the PDCCH command. The setting of the candidate cell's RACH resources can also be provided to the UE before the PDCCH command.

[0169] In the RACH of the PDCCH command, at least one method with RAR monitoring and one without RAR monitoring can be applied. When the method with RAR monitoring is applied, information related to the timing advance of the candidate cell (e.g., TA information / TAC) can also be included in the RAR and indicated to the UE. When the method without RAR monitoring is applied, information related to the timing advance of the candidate cell (e.g., TA information / TAC) can also be included in the cell handover command and indicated to the UE.

[0170] (Pre-scheduled group)

[0171] When using multiple TRPs, situations arise where the distance between the UE and each TRP differs. Multiple TRPs can also be contained within the same cell (e.g., a serving cell). Alternatively, one of the multiple TRPs can be equivalent to the serving cell, while the others can be equivalent to non-serving cells. In this case, it is also assumed that the distance between each TRP and the UE will differ.

[0172] In existing systems, the transmission timing of UL (Uplink) channels and / or UL signals (UL channels / signals) is adjusted through Timing Advance (TA). The reception timing of UL channels / signals from different User Terminals (UEs) is adjusted at the radio base station (also known as the Transmission and Reception Point (TRP), gNB, etc.).

[0173] The UE can also apply timing advance (multiple timing advance) to control the timing of UL transmission according to each pre-set Timing Advance Group (TAG).

[0174] When applying multiple timing advances, Timing Advance Groups (TAGs) are supported, categorized by transmission timing. The UE can also be designed to control the UL transmission timing in each TAG by applying the same TA offset (or TA value) to each TAG. That is, the TA offset can also be set independently for each TAG.

[0175] When multiple timing advances are applied, the UE independently adjusts the transmission timing of cells belonging to each TAG, so that the uplink signal reception timing from the UE can be aligned in the radio base station even when multiple cells are used.

[0176] TAGs (e.g., serving cells belonging to the same TAG) can also be set via higher-layer parameters. The same timing advance value can also be applied to serving cells belonging to the same TAG (e.g., serving cells with a set UL). Alternatively, the timing advance group of the SpCell containing the MAC entity can be called the primary timing advance group (PTAG), and other TAGs can be called secondary timing advance groups (STAG). Furthermore, the maximum number of TAGs can also be X per cell group (e.g., MCG / SCG) (e.g., X=4).

[0177] In existing systems (e.g., Rel.16 NR), it is supported to set a maximum of 4 tags per cell group (e.g., MCG / SCG) (see reference). Figure 13 ).exist Figure 13 The diagram illustrates the case where three tags are set for a cell group containing SpCell and SCell#1~#4. Here, the following scenario is shown: SpCell and SCell#1 belong to the first tag (PTAG or TAG#0), SCell#2 and SCell#3 belong to the second tag (TAG#1), and SCell#4 belongs to the third tag (TAG#2).

[0178] Timing advance command (TA command) can also be notified to the UE via MAC control elements (e.g., MAC CE). A TA command is a command representing the transmission timing value of the uplink channel and is contained within the MAC control element. The TA command (TAC) is signaled from the radio base station to the UE at the MAC layer. The UE controls specific timers (e.g., TA timers) based on the receipt of the TA command.

[0179] The MAC CE used for the advance timing command can also be a structure that includes fields for the advance timing group index (e.g., TAG ID) and fields for the advance timing command (see reference). Figure 14 The MAC CE can also be composed of an octet (=8 bits).

[0180] The TAG ID field can also consist of 2 bits, for example. The TAG ID field can also be used to indicate the TAG ID of a TAG at a specified address. The timing advance command field (TAC field) can also consist of 6 bits, for example. The TAC field can also represent: the index value T used in controlling the amount / value (relative amount / relative value) of timing adjustments that must be applied by the MAC entity. A (0, 1, 2…63). Figure 14 The MAC CE used for the timing advance command shown can also be called TACMAC CE.

[0181] Figure 15 This is a diagram illustrating other examples of MAC CE used for timed advance commands. Figure 15 The MAC CE shown can also be called an absolute TAC MAC CE. A MAC CE can also consist of two octets (16 bits). Specifically, the MAC CE can also include a field for reserved bits (R bit field) and a field for timing advance commands (TAC field). The R bit field (R=0) can, for example, consist of 4 bits. The TAC field can also span two octets and, for example, consist of 12 bits. Figure 15 The TAC field can also be used with Figure 14 Similarly, this indicates the index value used in the control of the actual amount / value (absolute amount / absolute value) of the TA that the MAC entity must apply. Furthermore, absolute TAC MAC CE may not include... Figure 14 The TAG ID field is shown in the image.

[0182] Figure 14 The MAC CE shown can also be used after the initial access is established. On the other hand, Figure 15 The MACCE shown can also be used only during initial access, included in RAR, etc. The fields included in the MACCE used for the aforementioned timing advance command can also be referred to as fields related to TA. Among them, Figure 14 The TAC field shown can also be called the TA adjustment field / field used to indicate TA adjustment / field related to TA adjustment. Figure 15 The TAC field shown can also be called an absolute TAC field / a field used to indicate an absolute TAC.

[0183] (Control based on UL transmission in advance at a set time)

[0184] In future wireless communication systems, it is also envisioned that, in inter-cell mobility, UL transmission will be controlled based on timing advance for both the serving cell (or the serving cell's TRP) and non-serving / additional cells (or the non-serving / additional cell's TRP). Alternatively, in future wireless communication systems, it is envisioned that different TAGs (or TAG-IDs) will be assigned to more than one TRP corresponding to a certain cell (or CC) (e.g., multiple TRPs with different PCIs). Furthermore, it is also envisioned that different TRPs corresponding to a certain cell will share a common TAG.

[0185] Figure 16 This is a diagram illustrating an example of TAG settings for different cells (or TRPs) within a PCI.

[0186] It is also envisioned that each CC can be configured with a maximum of M PCIs (e.g., serving cell + candidate cells associated with the serving cell), and for the maximum of M PCIs, a maximum of N (e.g., N≤M) TAGs can be configured. In this case, one or more PCIs can also be associated with a TAG.

[0187] Furthermore, for a maximum of S serving cells within a cell group (or, for a maximum of S serving cells), one or more PCIs can be associated with a TAG. In this case, a maximum of T TAGs can also be assigned, considering one PCI per CC (Case 1). That is, a maximum of T×N TAGs can also be assigned to a maximum of M×S cells. Alternatively, a maximum of U TAGs can also be assigned to a maximum of M×S cells (Case 2).

[0188] Thus, when candidate cells are set / applied / supported, it is envisioned that different serving cells / different candidate cells are associated with the same TAG. The TAG of a candidate cell can be indicated by the base station or determined based on the TAG of the candidate cell obtained by the UE.

[0189] Furthermore, for UL transmission of candidate cells, the UE considers the TA corresponding to that candidate cell when performing UL transmission. When considering the TA of candidate cells, the UE needs to acquire the TA of the candidate cells (e.g., TA acquisition of candidate cells).

[0190] For candidate cell TA acquisition, multiple TA acquisition methods are considered, including TA acquisition utilizing RACH (e.g., RACH-based solutions) and TA acquisition without RACH (RACH-less solutions). In TA acquisition utilizing RACH, methods with and without RAR monitoring can also be supported. The TA acquisition method can also be rewritten as a TA acquisition scheme, TA acquisition type, or TA acquisition process. In this disclosure, TA acquisition, TA measurement, TA calculation, TA derivation, and TA determination can also be mutually rewritten.

[0191] For example, a UE can also send a RACH (e.g., a PDCCH order RACH) to a candidate cell, which is indicated / triggered via the PDCCH, to obtain the candidate cell's TA. Information related to the candidate cell's TA (e.g., the TA value) can also be included in the RACH's response signal (e.g., a RAR). The RAR can be sent from either the serving cell or the candidate cell. Alternatively, the candidate cell's TA can be obtained using a RACH triggered by the UE or a RACH triggered by the network via higher layers. The PDCCH order can also be triggered only by the source cell (or the serving cell).

[0192] Alternatively, the UE can also send signals other than RACH to the candidate cell to obtain the TA of the candidate cell. Information related to the TA of the candidate cell (e.g., TA value) can also be indicated to the UE from the base station. As a signal other than RACH, SRS (SRS-based TA measurement) can also be applied, for example.

[0193] Alternatively, the UE may measure / calculate / obtain the TA for a candidate cell based on DL signals (e.g., downlink reference signals) transmitted from each cell (e.g., candidate cell / serving cell). The method by which the UE obtains the TA for a candidate cell based on DL signals transmitted from more than one cell can also be referred to as UE-based TA measurement (e.g., UE-based TA measurement).

[0194] In UE-based TA measurements, the downlink reference signal can also be a specific DL signal (e.g., a synchronization signal block (e.g., SSB) / CSI-RS, etc.). For example, the UE can also measure the timing difference / difference of the received DL signals from multiple cells (or two cells) to obtain the TA of a candidate cell.

[0195] Multiple cells may include a reference cell (e.g., the serving cell). In this case, the UE can also calculate the required TA for the candidate cell based on the reception timing (and TA value) of the reference cell and the timing difference (e.g., T) between the reference cell and the candidate cell. The UE can also use a timing advance command (TAC) sent from the serving cell to obtain the TA of the candidate cell.

[0196] (Uplink time alignment maintenance)

[0197] To maintain uplink time alignment (UL), parameters such as time alignment timers (e.g., timeAlignmentTimer) can be configured. The time alignment timer (per TAG) can also control the time during which a MAC entity considers a serving cell belonging to an associated TAG to be UL time aligned.

[0198] Parameters corresponding to each TAG ID can also be set via higher-level parameters. For example, parameters such as the time alignment timer (e.g., timeAlignmentTimer) corresponding to each TAG ID can also be set. Alternatively, for each serving cell, the TAG ID can also be set via higher-level parameters (e.g., the tag-ID contained in ServingCellConfig). Furthermore, after being set via higher-level parameters, the TAG ID / parameters can be updated via MAC CE.

[0199] The time alignment timer can also be maintained for UL time alignment. In Rel.17, the time alignment timer can also be set / associated per TAG. Upon receiving a MAC CE (e.g., TACMAC CE) for a timing advance command, the UE starts or restarts the time alignment timer associated with the indicated timing advance group (e.g., TAG).

[0200] The MAC entity receives the MAC CE used for the timing advance command and maintains a specific value (N) between it and the indicated TAG. TA In the case of ), apply a timing advance command for the indicated TAG and start or restart the time alignment timer associated with the indicated TAG. Specific value (N) TA It can also be a timing advance between DL and UL.

[0201] If a timing advance command is received in a RAR message for a serving cell belonging to a TAG (e.g., a TAG of SpCell) or in a message B (e.g., MSGB) for SpCell, and the MAC entity does not select a random access preamble from among contention-based random access preambles, the timing advance command for that TAG is applied, and the time alignment timer associated with that TAG is started or restarted.

[0202] The timing advance command of PTAG can also be applied in the case where an absolute timing advance command (e.g., Absolute Timing Advance Command) is received in response to the sending of a message A (e.g., MSGA) containing a specific RNTI MAC CE (e.g., C-RNTI MAC CE).

[0203] Operations when the time alignment timer expires can also be defined separately in PTAG and STAG. Alternatively, the timing advance group (TAG) of the SpCell containing the MAC entity can be called the primary timing advance group (PTAG), and other TAGs can be called secondary timing advance groups (STAG).

[0204] For example, in Rel.17, it is supported to apply specific PTAG operations when the timer corresponding to PTAG expires, and to apply specific STAG operations when the timer corresponding to STAG expires.

[0205] For example, when the time alignment timer expires, the following operations can also be performed (e.g., specific PTAG operation / specific STAG operation).

[0206] [Specific PTAG operations]

[0207] When the time alignment timer is associated with the PTAG

[0208] • Flush all HARQ buffers for all serving cells.

[0209] • If configured, notify the RRC to release the PUCCH for all serving cells.

[0210] • If configured, notify the RRC to release the SRS.

[0211] • Clear all set DL assignments and set UL assignments.

[0212] • Clear the PUSCH resource used for semi-persistent CSI reporting.

[0213] • Make the running time align with all timers until they expire.

[0214] • Maintain N for all tags TA .

[0215] [Specific STAG operations]

[0216] When a time alignment timer is associated with a STAG, for all serving cells belonging to that TAG...

[0217] • Refresh all HARQ buffers.

[0218] • If configured, notify the RRC to release the PUCCH.

[0219] • If configured, notify the RRC to release the SRS.

[0220] • Clear all assigned DL and UL values.

[0221] • Clear the PUSCH resource used for semi-persistent CSI reporting.

[0222] • Maintain the N of this TAG TA .

[0223] (PRACH uses power control process)

[0224] The transmit power of the preamble (PRACH) is calculated by the UE. The transmit power of PRACH is determined by open-loop power control and a power ramping / ramping mechanism. The UE calculates the transmit power based on the received power set from the network and the value of the preamble power ramping counter.

[0225] In PDCCH-ordered RACH, research is underway on whether the UE should perform power ramping (also known as power ramping) based on PDCCH commands in certain situations (e.g., when RAR reception is not configured).

[0226] For example, when power ramping is executed, the PDCCH command can be used to explicitly indicate whether PRACH is an initial transmission or a retransmission. Furthermore, when power ramping is executed, a power ramping-up value can also be set.

[0227] In addition, in the case where that is not the case (where power ramping is not performed), the transmission power of the PRACH can be determined by open-loop power control.

[0228] <PUSCH Transmission Power Control>

[0229] In NR, the transmission power of the PUSCH is controlled based on the TPC command (also referred to as a value, increment / decrement value, correction value, etc.) indicated by the value of a field within the DCI (also referred to as the TPC command field, etc.).

[0230] For example, when the UE uses a parameter set with index j (open-loop parameter set), an index l of the power control adjustment state (PUSCH power control adjustment state), and transmits a PUSCH on the active UL BWP b of carrier f in serving cell c, the transmission power (P PUSCH, b, f, c (i, j, q d , l)) [dBm] of the PUSCH in transmission occasion (transmission opportunity) i (also referred to as the transmission period, etc.) of the PUSCH can also be as shown in the following (Equation 1), based on P CMAX, f, c（i） , P O_PUSCH, b, f, c (j), M PUSCH RB, b, f, c (i), α b, f, c (j), PL b, f, c (q d ), Δ TF, b, f, c (i), f b, f, c (i, l), at least one of them.

[0231] (Equation 1)

[0232]

[0233] The power control adjustment state can also be referred to as the closed-loop (CL)-power control (PC) state, the value of the TPC command based on the power control adjustment state index l, the cumulative value of the TPC command, and the value based on the closed loop. l can also be referred to as the closed-loop index.

[0234] In addition, the PUSCH transmission occasion i is the period during which the PUSCH is transmitted and can be composed of, for example, more than one symbol, more than one time slot, etc.

[0235] P CMAX, f, c(i) For example, the maximum transmit power of the user terminal set for the carrier f of the serving cell c in transmission opportunity i (configured maximum output power, UE set maximum output power).

[0236] P O_PUSCH, b, f, c (j) For example, parameters related to the target receive power set for the activation ULBWP b of carrier f in serving cell c in transmission opportunity i (e.g., also referred to as parameters related to transmit power offset, transmit power offset P0, target receive power parameter, etc.). P O_UE_PUSCH, b, f, c (j) can also be P O_NOMINAL_PUSCH, f, c (j) and P O_UE_PUSCH, b, f, c The total of (j).

[0237] M PUSCH RB, b, f, c (i) For example, the number of resource blocks (bandwidth) allocated to the PUSCH for transmission opportunities i in the active ULBWP b of the serving cell c and the carrier f with subcarrier spacing μ. α b, f, c (j) is the value provided by higher-level parameters (e.g., also known as msg3-Alpha, p0-PUSCH-Alpha, fractional factor, etc.).

[0238] PL b, f, c (q) d For example, the index q of the reference signal (RS), path loss reference RS, path loss (PL)-RS, path loss reference RS, path loss measurement DL-RS, PUSCH-PathlossReferenceRS, used for the downlink BWP associated with the active UL BWP b of the carrier f of the serving cell c. d The path loss (path loss estimate [dB], path loss compensation) is calculated through the user terminal.

[0239] If the UE is not provided with a path loss reference RS (e.g., PUSCH-PathlossReferenceRS), or if the UE is not provided with dedicated higher-layer parameters, the UE can also utilize RS resources from the synchronization signal (SS) / physical broadcast channel (PBCH) block (SSB) used to obtain the Master Information Block (MIB) to calculate PL. b, f, c (q) d ).

[0240] When the UE is configured with a number of RS resource indices that is at most the maximum number of path loss reference RSs (e.g., maxNrofPUSCH-PathlossReferenceRSs), and a set of RS settings for each RS resource index is configured according to the path loss reference RSs, the set of RS resource indices may also include one or both of the set of SS / PBCH block indices and the set of Channel State Information (CSI)-Reference Signal (RS) resource indices. The UE may also identify RS resource index q within the set of RS resource indices. d .

[0241] When PUSCH transmission is scheduled via Random Access Response (RAR) UL permission, the UE can also use the same RS resource index q as the corresponding PRACH transmission. d .

[0242] When the UE is provided with a power control setting for the PUSCH based on a sounding reference signal (SRS) resource indicator (SRI) (e.g., SRI-PUSCH-PowerControl) and is provided with more than one value for the path loss reference RS ID, a mapping between the set of SRI field values ​​in DCI format 0_1 ​​and the set of path loss reference RS ID values ​​can be obtained according to higher-layer signaling (e.g., sri-PUSCH-PowerControl-Id within SRI-PUSCH-PowerControl). The UE can also determine the RS resource index q based on the path loss reference RS ID mapped to the SRI field values ​​in DCI format 0_1 ​​of the scheduling PUSCH. d .

[0243] When PUSCH transmission is scheduled via DCI format 0_0, and the UE is not provided with PUCCH spatial relationship information for the PUCCH resource with the lowest index for each carrier f and serving cell c active UL BWP b, the UE may also use the same RS resource index q as the PUCCH transmission within that PUCCH resource. d .

[0244] When PUSCH transmission is scheduled via DCI format 0_0 and the UE is not provided with PUSCH transmission spatial settings, or when PUSCH transmission is scheduled via DCI format 0_1 ​​without an SRI field, or when SRI-based PUSCH power control settings are not provided to the UE, the UE can also use an RS resource index q with path loss reference RS ID zero. d .

[0245] When sending a PUSCH that is configured by setting a permission setting (e.g., ConfiguredGrantConfig), where the permission setting includes specific parameters (e.g., rrc-ConfiguredUplinkGrant), the RS resource index q d It can also be provided to the UE via a path loss reference index (e.g., pathlossReferenceIndex) within specific parameters.

[0246] For PUSCH transmissions configured through permission settings, where the permission settings do not include specific parameters, the UE can also determine the RS resource index q based on the value of the path loss reference RS ID mapped to the SRI field in the DCI format used to activate PUSCH transmissions. d Even when the DCI format does not include an SRI field, the UE can still determine the RS resource index q with an ID of the path loss reference RS that has zero. d .

[0247] Δ TF, b, f, c (i) is the transmission power adjustment component (offset, transmission format compensation) used by the UL BWP b of the carrier f of the serving cell c.

[0248] f b, f, c (i, l) represents the PUSCH power control adjustment state of the active UL BWP b for carrier f of serving cell c in transmission opportunity i. b, f, c (i, l) can also be based on δ PUSCH, b, f, c (i, l).

[0249] In the case of TPC cumulative validity, f b, f, c (i, l) can also be based on δ PUSCH, b, f, c The cumulative value of (m, l).

[0250] In the case of TPC cumulative invalidity, f b, f, c (i, l) can also be δ PUSCH, b, f, c(i, l) (absolute value).

[0251] In the absence of a disabled TPC accumulation setting (where no disabled TPC accumulation setting is provided, or where TPC accumulation is enabled), the UE accumulates the TPC command value and determines the transmission power based on the accumulation result (power control state) (the TPC command value is applied after accumulation).

[0252] When invalid information (TPC-Accumulation) is set to indicate TPC accumulation (when invalid information indicating TPC accumulation is provided, or when TPC accumulation is set to invalid), the UE does not accumulate the TPC command value and determines the transmission power based on the TPC command value (power control state) (applying the TPC command value without using accumulation).

[0253] δ PUSCH, b, f, c (i, l) can also be the following TPC command values: TPC command values ​​contained in DCI format 0_0 or DCI format 0_1 ​​that schedule PUSCH transmission opportunities i on the active ULBWP b of carrier f of serving cell c, or TPC command values ​​that are combined with other TPC commands in DCI format 2_2 that have a CRC scrambled by a specific RNTI (Radio Network Temporary Identifier) ​​(e.g., TPC-PUSCH-RNTI).

[0254] Σ m=0 C（Di）-1 δ PUCCH, b, f, c (m, l) can also be a group / concentration (cardinality) C(D) i The set D of TPC command values i The total of TPC command values ​​within. D i It could also be the UE adjusting the PUSCH power control state l, on the active UL BWP b of carrier f in serving cell c, with PUSCH transmission opportunities i-i0. PUSCH (i-i0)-1 codeword before and PUSCH transmission opportunity i of K PUSCH (i) The set of TPC command values ​​received between symbolic points. i0 can also be K that enables PUSCH transmission opportunity i-i0. PUSCH (i-i0) symbol precedes PUSCH transmission opportunity i by K PUSCH(i) The smallest positive integer preceding the symbol.

[0255] When PUSCH transmissions are scheduled via DCI format 0_0 or DCI format 0_1, K PUSCH (i) can also be the number of symbols in the active UL BWP b of the carrier f of the serving cell c, after the last symbol received by the corresponding PDCCH and before the first symbol transmitted by the PUSCH. When the PUSCH transmission is configured through the configured grant structure information (ConfiguredGrantConfig), K PUSCH (i) could also be the number of symbols N per slot in the active UL BWP b of the carrier f of the serving cell c. symb slot K is equal to the product of the minimum value provided by k2 within the PUSCH common structure information (PUSCH-ConfigCommon). PUSCH, min The number of code elements.

[0256] The power control adjustment state can also be set via higher-level parameters to have multiple states (e.g., two states) or a single state. Furthermore, if multiple power control adjustment states are set, one of the multiple power control adjustment states can be identified by an index l (e.g., 1∈{0, 1}).

[0257] (analyze)

[0258] As mentioned above, in LTM of Rel.18, when the TA for the target cell is not included in the cell handover command, the UE does not perform the RACH procedure for the target cell after receiving the cell handover command, thus supporting so-called RACH-less handover. RACH-less handover can be rewritten with the aforementioned PDCCH command RACH without RAR.

[0259] In this scenario, the UE performs a UL transmission to the target cell using the configuration permission information element (IE) set via higher-layer signaling (RRC). Consequently, the gNB of the target cell can receive this UL transmission at a specified power within the specified time / frequency resources.

[0260] However, when determining the power of UL transmission (signal / channel), existing specifications require PL-RS measurement to determine path loss. On the other hand, in LTM of Rel.18, from the perspective of delay and reliability, it is necessary to study how the power should be set for the target cell. For example, consider the following issues.

[0261] [Analysis 1]

[0262] Interruption time may be longer if path loss is measured after the UE receives the cell handover command.

[0263] [Analysis 2]

[0264] On the other hand, if the measurement results are used before the UE receives the cell handover command, the UL transmission may not reach the target cell (gNB) due to potentially inaccurate measurement results. This becomes a major cause of handover failure.

[0265] [Analysis 3]

[0266] Furthermore, after a cell handover is performed using LTM, the UE performs a MAC reset. However, in this case, the RRC reset used for LTM is not performed.

[0267] Furthermore, in the case of LTM without RACH, the RACH procedure after handover to the new target cell is not executed; only UL transmissions (e.g., PUSCH) scheduled based on dynamic grant or configured grant are executed.

[0268] In the initial UL transmission following such a cell handover, it is necessary to clarify how to define the power control f for PUSCH. b,f,c (k,l). Here, f b,f,c (k,l) (k=0,1,···,i) can represent the PUSCH power control adjustment state of the active UL BWP b for the carrier f of the serving cell c in the transmission opportunity k.

[0269] [Analysis 4]

[0270] As described above, in the case of RACH-less handover, since no RACH is performed for the target cell, the UE performs UL transmission for the target cell without adjusting the PUSCH power control. Furthermore, the PRACH power increment is considered for PUSCH power control, but in existing specifications, this power increment is limited to the case of a 2-step RACH. That is, it is envisioned that these power controls are also applied to LTM.

[0271] As explained in analyses 1-4, in Rel.18 LTM, if the method for path loss calculation / power control in the case of RACH-less handover is not clear, an appropriate random access procedure cannot be performed, resulting in concerns about reduced communication throughput.

[0272] Therefore, the inventors of this invention studied path loss calculation / power control in the case of RACH-less switching in LTM of Rel.18 and came up with a way of this embodiment.

[0273] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. Furthermore, the following embodiments / methods (e.g., various situations) can be used individually or in combination of at least two.

[0274] (Various rewrites, etc.)

[0275] In this disclosure, "A / B" and "at least one of A and B" may be rewritten as each other. In addition, in this disclosure, "A / B / C" may also mean "at least one of A, B and C".

[0276] In this disclosure, terms such as notification, activation, deactivation, indication (or indication), selection, configuration, update, and determination can be overridden. Similarly, terms such as support, control, ability to control, operation, and ability to operate can also be overridden.

[0277] In this disclosure, Radio Resource Control (RRC), RRC parameters, RRC messages, higher-level parameters, fields, Information Elements (IE), settings, etc., can also be modified interchangeably. In this disclosure, Medium Access Control (MAC) control elements (CE), update commands, activation / deactivation commands, etc., can also be modified interchangeably.

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

[0279] In this disclosure, MAC signaling may also use, for example, a MAC Control Element (MACCE) or a MAC Protocol Data Unit (PDU). Broadcast information may also be, for example, a Master Information Block (MIB), a System Information Block (SIB), a Minimum System Information (Remaining Minimum System Information (RMSI)), or Other System Information (OSI).

[0280] In this disclosure, physical layer signaling may also be, for example, downlink control information (DCI), uplink control information (UCI), etc.

[0281] In this disclosure, the terms cell, PCI, serving cell, SpCell, source serving cell, reference / base cell, CC, BWP, BWP within CC, and band domain can be mutually modified. In this disclosure, additional cells, other cells, non-serving cells, cells with different PCIs, candidate cells, candidate serving cells, cells with PCIs different from the current serving cell, other serving cells, target cells, target serving cells, and neighboring cells can also be mutually modified. In this disclosure, handover, change, and update can also be mutually modified. The serving cell can also be modified to the serving cell before or after the handover. LTM applications, cell applications, cell handover, and handover can also be mutually modified. LTM applications, beam applications, and beam switching can also be mutually modified.

[0282] In this disclosure, RACH resources, RA resources, PRACH preamble, timing, RACH timing (RO), PRACH timing, repetition resources, repetition setting resources, resources set for RO / repetition, time instances and frequency instances, time resources and frequency resources, RO / preamble resources, repetition, PRACH resources, time / frequency resources used for PRACH, preamble setting / index, mask setting / index, and PRACH setting can also be overridden.

[0283] In this disclosure, candidate cells and candidate cell groups can be interchanged. The candidate cells in this disclosure can also be candidate cells indicated in the PDCCH command. The PDCCH command and DCI (e.g., DCI format 1_0) can also be interchanged. In this disclosure, RO, RO index, and RO# can also be interchanged.

[0284] In this disclosure, RACH (procedure), PRACH transmission triggered by PDCCH command, PDCCH command RACH, and RACH-less switching can be rewritten interchangeably. RACH without RAR, RACH without RAR monitoring (e.g., RACH without RAR monitoring), PDCCH command RACH without RAR, and PDCCH command RACH for LTM can also be rewritten interchangeably. RACH procedure / PRACH transmission without RAR monitoring can also be rewritten with RACH procedure / PRACH transmission that does not require RAR monitoring, or RACH procedure / PRACH transmission that is not required to be RAR monitored.

[0285] In this disclosure, RACH-free, RAR-free, RAR-monitor-free, RAR-free, RAR-free, and LTM-free can be interchanged.

[0286] In this disclosure, RAR, RAR monitoring, RAR application, and RAR can be overridden with each other.

[0287] In this disclosure, LTM, cell handover, and handover can be rewritten interchangeably.

[0288] In this disclosure, the measurement result may be, for example, L1 / L3-RSRP.

[0289] The following description can be applied to inter-cell mobility (e.g., L1 / L2 inter-cell mobility) as well as to communication control outside of inter-cell mobility. L1 / L2 inter-cell mobility can also be rewritten as at least one of cell handover, cell switching, and cell change.

[0290] (Wireless communication method)

[0291] <First Implementation Method>

[0292] The first implementation method corresponds to the analyses 1 to 2 above, and explains the path loss calculation. Figure 17 This is a diagram illustrating an example of path loss calculation according to the first embodiment.

[0293] The SSB associated with the TCI status index (indicating TCI status) indicated by the cell handover command (MAC CE) can be measured after the cell handover command is received and used for path loss calculation.

[0294] That is, after receiving the cell handover command, the UE can measure the SSB associated with the TCI state index indicated by the cell handover command (MAC CE). Furthermore, the UE can use the measured SSB to calculate the corresponding path loss.

[0295] More specifically, such as Figure 17 As shown, the UE can calculate the path loss using the SSB (Measurement Result) corresponding to one or more reference signals (RS) received in the initial time slot after a specific time has elapsed following receiving the cell handover command. Here, as mentioned above, the SSB is associated with the TCI state index represented by the cell handover command.

[0296] Based on these structures, the UE can perform accurate path loss calculations without needing to store or measure the parameters used for path loss calculations in advance.

[0297] Furthermore, the measurement result can be either a single measurement result (corresponding to one RS) or the average of multiple measurement results (corresponding to multiple RS).

[0298] The number of measurements used in path loss calculation can be set / indicated by higher-layer signaling / physical layer signaling, determined based on UE capabilities, or predefined by specifications.

[0299] Furthermore, the specific time (specific period) after receiving the aforementioned cell handover command can be set / indicated by higher-layer signaling / physical layer signaling, determined based on UE capabilities, or predefined by specifications.

[0300] According to the first embodiment described above, the UE can appropriately calculate the path loss based on the SSB measured after receiving the cell handover command.

[0301] <Second Implementation Method>

[0302] The second implementation method corresponds to the analyses 1 to 2 above, and explains the path loss calculation. Figure 18 This is a diagram illustrating an example of path loss calculation involved in the second embodiment.

[0303] When using UE-based TA measurements to obtain the TA of a target cell, the path loss can be calculated using the measurement results of the RS of the target cell used in the TA calculation.

[0304] That is, when UE-based TA measurement is applied in order to obtain the TA of the target cell, the UE can use the measurement results of the RS of the target cell used in the TA calculation to calculate the corresponding path loss.

[0305] More specifically, such as Figure 18 As shown, the RS for the target cell received before receiving the cell handover command is used for UE-based TA measurements. The results of these RS measurements can then be used for path loss measurements.

[0306] Based on these structures, measurements from other targets (TAs) can be used to calculate path loss, thus reducing downtime.

[0307] The UE can calculate the corresponding path loss by using the measurement results obtained from UE-based TA measurements through the SSB associated with the TCI status index / target cell index indicated according to the cell handover command.

[0308] In this case, the UE can save / store the measurement results of the RS used in the measurement / path loss calculation.

[0309] The maximum number of measurement results that can be saved / stored can be set / indicated by higher-layer signaling / physical layer signaling, determined based on UE capabilities, or defined in advance by specifications.

[0310] In addition, measurement results can be saved / stored per candidate cell / per RS ​​index.

[0311] Furthermore, the first implementation described above can also be applied when using UE-based TA measurements.

[0312] According to the second embodiment described above, the UE can appropriately calculate the path loss based on the TA measurement results measured before receiving the cell handover command.

[0313] <Third Implementation Method>

[0314] The third implementation method corresponds to the analyses 1 to 2 above and explains the path loss calculation. Figure 19 This is a diagram illustrating an example of path loss calculation involved in the third embodiment.

[0315] Measurements taken before receiving a cell handover command for an RS associated with the target cell index / TCI status index indicated by the cell handover command can be used for path loss calculation.

[0316] That is, the UE can measure the RS associated with the target cell index / TCI status index indicated by the cell handover command before receiving the cell handover command.

[0317] More specifically, such as Figure 19 As shown, the UE can calculate the path loss using the measurement results corresponding to one or more received reference signals (RS) within a specific time period (within) before receiving the cell handover command.

[0318] Based on these structures, path loss can be calculated based on measurements taken before receiving cell handover commands, thus reducing downtime.

[0319] Furthermore, the UE can use the latest SSB measurement received before receiving the cell handover command to calculate the corresponding path loss. This SSB can be associated with the TCI state index represented by the cell handover command.

[0320] Furthermore, the measurement result can be either a single measurement result (corresponding to one RS) or the average of multiple measurement results (corresponding to multiple RS).

[0321] The number of (SSB) measurements used in path loss calculation can be set / indicated by higher-layer signaling / physical layer signaling, determined based on UE capabilities, or predefined by specifications.

[0322] Furthermore, the measurement results (of the SSB) can also be limited to the results within a specific time period prior to receiving the cell handover command. That is, the specific time (specific period) prior to receiving the aforementioned cell handover command can be set / indicated by higher-layer signaling / physical layer signaling, determined based on UE capabilities, or predefined by specifications.

[0323] The UE can save / store the measurement results of RS used in path loss calculation.

[0324] The maximum number of measurement results that can be saved / stored can be set / indicated by higher-layer signaling / physical layer signaling, determined based on UE capabilities, or defined in advance by specifications.

[0325] In addition, measurement results can be saved / stored per candidate cell / per RS ​​index.

[0326] According to the third embodiment described above, the UE can appropriately calculate the path loss based on the measurement results before receiving the cell handover command.

[0327] <Fourth Implementation Method>

[0328] The fourth embodiment corresponds to analysis 3 above, and explains the power control adjustment state.

[0329] In LTM, after a successful cell handover, the PUSCH power control adjustment state (f) is...b,f,c (k,l) can be reset to 0.

[0330] After a successful cell handover, the UE can adjust the PUSCH power control state (f) for the new target cell indicated by the cell handover command. b,f,c (k,l) is reset to 0. The conditions for resetting are explained below.

[0331] The UE may adjust the PUSCH power control state (f) of the active UL BWP b for carrier f of serving cell c in transmission opportunity k to a state where at least one of the following conditions is met. b,f,c (k,l) is reset to 0.

[0332] <Condition 1>

[0333] Provided with P from a high level O_PUSCH,b,f,c (j), or P O_UE_PUSCH,b,f,c The value of (j) corresponds to the setting.

[0334] <Condition 2>

[0335] Provided with α from the higher levels b,f,c The value of (j) corresponds to the setting.

[0336] <Condition 3>

[0337] After the UE receives the LTM cell handover command (MAC CE), it performs a cell handover through the LTM procedure (if successful).

[0338] <Changes in conditions>

[0339] You can also add / replace the following conditions to conditions 1 to 3 above.

[0340] • When the UE receives a cell handover command (MAC CE) for LTM.

[0341] • When a MAC reset is performed (for LTM)

[0342] • When the UE determines that the LTM process has ended normally.

[0343] According to the fourth implementation method described above, the UE can appropriately reset the power control adjustment state based on specific conditions when the cell handover is successful.

[0344] <Fifth Implementation Method>

[0345] The fifth embodiment corresponds to analysis 4 above and explains the gradual increase in power. Figure 20This is a diagram illustrating an example of the calculations related to power gradual increase involved in the fifth embodiment.

[0346] When the PDCCH command RACH is applied in order to obtain the TA of the target cell, the UE can consider the power ramp-up number of PRACH for the power control of PUSCH.

[0347] This architecture can shorten downtime. Furthermore, it allows for the application of normal transmit power to the gNB without requiring additional parameters to be set via higher-layer signaling (RRC).

[0348] In this case, the UE can save / store the power.

[0349] Furthermore, this implementation can also be applied to the initial PUSCH transmission of the target cell after the cell handover command has been received.

[0350] The total power increment can also be used for the PDCCH command RACH, which indicates the SSB associated with the TCI status index / candidate cell index (target cell index) indicated by the cell handover command (MAC CE).

[0351] like Figure 20 As shown, when the UE transmits PUSCH on the active UL BWP b of carrier f in serving cell c during PUSCH transmission opportunity i, f b,f,c (0,l)=ΔP rampup,b,f,c .

[0352] Here, ΔP rampup,b,f,c Provided by higher levels, corresponding to a gradual increase in the total power requested by the higher levels. M RB,b,f,c PUSCH (i) is the bandwidth allocated to PUSCH resources, expressed as the number of resource blocks. Δ TF,b,f,c It is the power adjustment of PUSCH transmission in PUSCH transmission opportunity i.

[0353] According to the fifth embodiment described above, the UE can appropriately control the power ramp-up in LTM.

[0354] <Supplement>

[0355] [Information notification to UE]

[0356] The notification of any information from the Network (NW) (e.g., Base Station (BS)) to the UE in the above-described embodiments (in other words, the reception of any information from the BS in the UE) can also be performed using physical layer signaling (e.g., DCI), higher layer signaling (e.g., RRC signaling, MAC CE), specific signals / channels (e.g., PDCCH, PDSCH, reference signals), or combinations thereof.

[0357] In the case where the above notification is made via MAC CE, the MAC CE can also be identified by including a new Logical Channel ID (LCID) that is not specified in the existing standard in the MAC subheader.

[0358] When the above notification is made through a DCI, the notification can also be made through specific fields of the DCI, the Radio Network Temporary Identifier (RNTI) used in the scrambling of the Cyclic Redundancy Check (CRC) bits assigned to the DCI, the format of the DCI, etc.

[0359] Furthermore, the notification of any information to the UE in the above embodiments can also be carried out periodically, semi-persistently, or non-periodically.

[0360] [Notification from UE]

[0361] The notification of any information from the UE (to the NW) in the above embodiments (in other words, the transmission / reporting of any information from the UE to the BS) can also be performed using physical layer signaling (e.g., UCI), higher layer signaling (e.g., RRC signaling, MACCE), specific signals / channels (e.g., PUCCH, PUSCH, PRACH, reference signals), or combinations thereof.

[0362] In the case where the above notification is made via MAC CE, the MAC CE can also be identified by including a new LCID in the MAC subheader that is not specified in the existing standard.

[0363] In cases where the above notification is sent via UCI, the above notification may also be sent using PUCCH or PUSCH.

[0364] Furthermore, the notification of any information from the UE in the above embodiments can also be carried out periodically, semi-persistently, or non-periodically.

[0365] [Regarding the application of each implementation method]

[0366] At least one of the above-described implementation methods can also be applied under certain conditions. These specific conditions can be specified in the standard or communicated to the UE / BS using higher-layer signaling / physical layer signaling.

[0367] At least one of the above implementation methods can also be applied only to UEs that have reported a specific UE capability or support that specific UE capability. In addition, "support" and "whether to support" can be rewritten interchangeably.

[0368] This specific UE capability can also represent at least one of the following:

[0369] • Supports specific processing / operation / control / information for at least one of the above embodiments;

[0370] • Supports two TAs for multiple TRPs;

[0371] • Supports two TAs for multiple TRPs within a cell (e.g., intra-cell M-TRP);

[0372] • Supports two TAs for multiple TRPs within a small interval (e.g., inter-cell M-TRP);

[0373] • Supports L1 / L2 inter-cell mobility (e.g., L1 / L2 inter-cell mobility).

[0374] • Supports PDCCH monitoring of candidate cells / deactivated candidate cells / deactivated Scells;

[0375] • The maximum number of cells / TAGs / reference CCs that can be monitored by the PDCCH;

[0376] • Supports PDCCH commands across carriers (across CCs);

[0377] • Supports existing PDCCH command RACH and LTM-used PDCCH command RACH;

[0378] • Supports the PDCCH command RACH with / without RAR;

[0379] • Supports RACH-free switching;

[0380] • Supports path loss calculation for LTM;

[0381] • Supports UE-based TA measurements;

[0382] • Supports power ramping for LTM.

[0383] Furthermore, the aforementioned specific UE capabilities can be applied across the entire frequency (commonly regardless of frequency), or per frequency (e.g., one or a combination of cells, bands, band combinations, BWPs, component carriers, etc.), or per frequency range (e.g., Frequency Range 1 (FR1), FR2, FR3, FR4, FR5, FR2-1, FR2-2), or per subcarrier spacing (SCS), or per feature set (FS) or per component carrier feature set (FSPC).

[0384] Furthermore, the aforementioned specific UE capabilities can be either the ability to apply across all duplex modes (commonly independent of duplex mode) or the capability for each duplex mode (e.g., Time Division Duplex (TDD) and Frequency Division Duplex (FDD)).

[0385] Furthermore, at least one of the above-described embodiments can also be applied when the UE is set / activated / triggered by specific information associated with the above-described embodiments (or performs the operations of the above-described embodiments) via higher-layer signaling / physical layer signaling. For example, this specific information may be information indicating LTM activation, arbitrary RRC parameters for a specific version (e.g., Rel.18 / 19), etc.

[0386] The UE may also apply operations such as Rel.15 / 16 / 17 if it does not support at least one of the specific UE capabilities mentioned above, or if the specific information mentioned above is not set.

[0387] (Postscript)

[0388] Regarding one embodiment of this disclosure (first to third embodiments), the invention is described below.

[0389] [Postscript 1]

[0390] A terminal having:

[0391] The receiving unit receives a cell handover command containing information about a target cell that is a handover candidate to become the serving cell; and

[0392] The control unit calculates the path loss based on the measurement results of the reference signal before or after receiving the cell handover command.

[0393] [Postscript 2]

[0394] As described in Appendix 1, the control unit uses the result of a timing advance measurement before receiving the cell handover command to control the path loss calculation.

[0395] [Postscript 3]

[0396] As described in Appendix 1 or Appendix 2, the control unit controls the path loss calculation based on the measurement results of a reference signal associated with a target cell index or transmission setting indication state (TCI) index indicated by the cell handover command.

[0397] [Postscript 4]

[0398] The terminal as described in any one of Annexes 1 to 3, wherein the control unit controls the path loss calculation using measurement results from a specific time before or after receiving the cell handover command.

[0399] (Postscript)

[0400] Regarding one embodiment of this disclosure (the fourth to fifth embodiments), the invention is described below.

[0401] [Postscript 1]

[0402] A terminal having:

[0403] The receiving unit receives a cell handover command containing information about a target cell that is a handover candidate to become the serving cell; and

[0404] The control unit controls the power control adjustment state or power gradual increase for the target cell indicated by the cell handover command.

[0405] [Postscript 2]

[0406] As described in Appendix 1, in the terminal, after a successful cell handover, the control unit resets the power control adjustment state for the target cell based on specific conditions.

[0407] [Postscript 3]

[0408] As described in Appendix 1 or Appendix 2, after a successful cell handover, the control unit resets the power control adjustment state for the target cell based on whether the cell handover command has been received or whether the MAC reset has been executed.

[0409] [Postscript 4]

[0410] The terminal as described in any of Annexes 1 to 3, wherein, in the case of applying random access triggered by a downlink control channel command in order to obtain the timing advance of the target cell, the control unit considers the power ramp-up number to control the power ramp-up.

[0411] (Wireless communication system)

[0412] The structure of a wireless communication system according to one embodiment of this disclosure will now be described. In this wireless communication system, communication is performed using any one or a combination of the wireless communication methods according to the above embodiments of this disclosure.

[0413] Figure 21 This is a diagram illustrating an example of the schematic structure of a wireless communication system according to one embodiment. The wireless communication system 1 (also referred to simply as System 1) may also be a system that uses Long Term Evolution (LTE) or 5th generation mobile communication system New Radio (5GNR) as standardized by the Third Generation Partnership Project (3GPP).

[0414] Furthermore, the wireless communication system 1 can also support dual connectivity between multiple radio access technologies (RATs) (Multi-RAT Dual Connectivity (MR-DC)). MR-DC can also 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.

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

[0416] Wireless communication system 1 can also support dual connectivity between multiple base stations within the same RAT (e.g., MN and SN are dual connectivity between NR base stations (gNB) (NR-NR Dual Connectivity (NN-DC))).

[0417] The wireless communication system 1 may also include a base station 11 forming a macro cell C1 with a relatively wide coverage area, and a base station 12 (12a-12c) configured within the macro cell C1 and forming a small cell C2 narrower than the macro cell C1. The user terminal 20 may also be located within at least one cell. The configuration and number of each cell and the user terminal 20 are not limited to the arrangement shown in the figure. Hereinafter, without distinguishing between base stations 11 and 12, they will be collectively referred to as base station 10.

[0418] User terminal 20 may also connect to at least one of multiple base stations 10. User terminal 20 may also utilize at least one of carrier aggregation (CA) using multiple component carriers (CC) and dual connectivity (DC).

[0419] Each CC can also be included in at least one of the first frequency band (Frequency Range 1 (FR1)) and the second frequency band (Frequency Range 2 (FR2)). Macro cell C1 can also be included in FR1, and small cell C2 can also be included in FR2. For example, FR1 can also be a frequency band below 6 GHz (sub-6 GHz), and FR2 can also be a frequency band above 24 GHz (above-24 GHz). In addition, the frequency bands, definitions, etc. of FR1 and FR2 are not limited to these; for example, FR1 can also correspond to a frequency band higher than FR2.

[0420] In addition, in each CC, the user terminal 20 may also use at least one of Time Division Duplex (TDD) and Frequency Division Duplex (FDD) for communication.

[0421] Multiple base stations 10 can also be connected via wired (e.g., fiber optic, X2 interface, etc. based on Common Public Radio Interface (CPRI)) or wireless (e.g., NR communication). For example, when NR communication between base stations 11 and 12 is used as a backhaul, base station 11, which is equivalent to a host station, can also be referred to as an Integrated Access Backhaul (IAB) donor, and base station 12, which is equivalent to a relay station, can also be referred to as an IAB node.

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

[0423] The core network 30 may also include, for example, user plane functions (UPF), access and mobility management functions (AMF), session management functions (SMF), unified data management (UDM), application functions (AF), data network (DN), location management functions (LMF), and network functions (NF) such as operation, administration and maintenance (OAM). Alternatively, a single network node may provide multiple functions. Furthermore, communication with external networks (e.g., the Internet) may also be conducted via the DN.

[0424] User terminal 20 can also be a terminal that supports at least one of the following communication methods: LTE, LTE-A, 5G, etc.

[0425] In wireless communication system 1, wireless access methods based on Orthogonal Frequency Division Multiplexing (OFDM) can also be used. For example, in at least one of the downlink (DL) and uplink (UL) links, Cyclic Prefix OFDM (CP-OFDM), Discrete Fourier Transform Spread OFDM (DFT-s-OFDM), Orthogonal Frequency Division Multiple Access (OFDMA), and Single Carrier Frequency Division Multiple Access (SC-FDMA) can also be used.

[0426] The wireless access method can also be referred to as a waveform. In addition, in the wireless communication system 1, other wireless access methods (e.g., other single-carrier transmission methods, other multi-carrier transmission methods) can also be used in the wireless access methods of UL and DL.

[0427] As a downlink channel, the wireless communication system 1 can also use downlink shared channels (Physical Downlink Shared Channel (PDSCH)), broadcast channels (Physical Broadcast Channel (PBCH)), downlink control channels (Physical Downlink Control Channel (PDCCH)) and so on, which are shared among the user terminals 20.

[0428] In addition, as uplink channels, the wireless communication system 1 may also use uplink shared channels (Physical Uplink Shared Channel (PUSCH)), uplink control channels (Physical Uplink Control Channel (PUCCH)), random access channels (Physical Random Access Channel (PRACH)) and so on, which are shared by each user terminal 20.

[0429] User data, high-level control information, and System Information Blocks (SIBs) are transmitted via the PDSCH. User data and high-level control information can also be transmitted via the PUSCH. In addition, Master Information Blocks (MIBs) can also be transmitted via the PBCH.

[0430] Lower-layer control information can also be transmitted via PDCCH. This lower-layer control information may include, for example, downlink control information (DCI), which includes scheduling information for at least one of PDSCH and PUSCH.

[0431] Additionally, the DCI that schedules PDSCH can also be called DL allocation, DL DCI, etc., and the DCI that schedules PUSCH can also be called UL authorization, UL DCI, etc. Furthermore, PDSCH can be rewritten as DL data, and PUSCH can be rewritten as UL data.

[0432] In PDCCH detection, a Control Resource Set (CORESET) and a search space can also be utilized. A CORESET corresponds to the resources used to search for DCIs. The search space corresponds to the search area and search method for PDCCH candidates. A CORESET can also be associated with one or more search spaces. The UE can also monitor CORESETs associated with a specific search space based on search space settings.

[0433] A search space can also correspond to a PDCCH candidate corresponding to one or more aggregation levels. One or more search spaces can also be referred to as a search space set. In addition, the terms "search space", "search space set", "search space setting", "search space set setting", "CORESET", "CORESET setting" etc. disclosed herein can be rewritten interchangeably.

[0434] The PUCCH can also transmit uplink control information (uplink control information (UCI)) that includes at least one of the following: Channel State Information (CSI), delivery confirmation information (e.g., also known as Hybrid Automatic Repeat Request ACK Knowledge (HARQ-ACK), ACK / NACK, etc.), and Scheduling Request (SR). The PRACH can also transmit random access preambles used for establishing connections with the cell.

[0435] Additionally, in this disclosure, downlink, uplink, etc., may be described without the word "link". Furthermore, it may be stated that the word "physical" is not included at the beginning of various channels.

[0436] In wireless communication system 1, synchronization signals (SS) and downlink reference signals (DL-RS) can also be transmitted. In wireless communication system 1, DL-RS can also transmit cell-specific reference signals (CRS), channel state information reference signals (CSI-RS), demodulation reference signals (DMRS), positioning reference signals (PRS), and phase tracking reference signals (PTRS).

[0437] Synchronization signals can be, for example, at least one of a primary synchronization signal (PSS) and a secondary synchronization signal (SSS). A signal block containing SS (PSS, SSS) and PBCH (and DMRS for PBCH) can also be called an SS / PBCH block, SS block (SSB), etc. In addition, SS, SSB, etc. can also be called reference signals.

[0438] Furthermore, as an uplink reference signal (UL-RS), measurement reference signals (sounding reference signals (SRS)) and demodulation reference signals (DMRS) can also be transmitted in the wireless communication system 1. Additionally, DMRS can also be referred to as a user terminal-specific reference signal (UE-specific reference signal).

[0439] (Base station)

[0440] Figure 22 This diagram illustrates an example of the structure of a base station according to one embodiment. The base station 10 includes a control unit 110, a transmit / receive unit 120, a transmit / receive antenna 130, and a transmission path interface (transmission line interface) 140. Alternatively, the control unit 110, the transmit / receive unit 120, the transmit / receive antenna 130, and the transmission path interface 140 may each be provided in more than one manner.

[0441] Furthermore, while this example primarily illustrates the functional blocks of the characteristic portions of this embodiment, it is also conceivable that the base station 10 may have other functional blocks required for wireless communication. Some of the processing of each unit described below may also be omitted.

[0442] The control unit 110 performs overall control of the base station 10. The control unit 110 can be composed of a controller, control circuit, etc., which are described based on common knowledge in the art to which this disclosure pertains.

[0443] The control unit 110 can also control signal generation and scheduling (e.g., resource allocation, mapping). The control unit 110 can also control transmission, reception, and measurement using the transmit / receive unit 120, transmit / receive antenna 130, and transmission path interface 140. The control unit 110 can also generate data, control information, sequences, etc., to be transmitted as signals and forward them to the transmit / receive unit 120. The control unit 110 can also perform call processing (setting, releasing, etc.) of the communication channel, status management of the base station 10, and management of wireless resources.

[0444] The transmitting / receiving unit 120 may also include a baseband unit 121, a radio frequency (RF) unit 122, and a measurement unit 123. The baseband unit 121 may also include a transmitting processing unit 1211 and a receiving processing unit 1212. The transmitting / receiving unit 120 can be composed of transmitters / receivers, RF circuits, baseband circuits, filters, phase shifters, measurement circuits, transmitting / receiving circuits, etc., as described based on common knowledge in the art to which this disclosure pertains.

[0445] The transmitting and receiving unit 120 can be configured as a single integrated transmitting and receiving unit, or it can be composed of a transmitting unit and a receiving unit. The transmitting unit can also be composed of a transmitting processing unit 1211 and an RF unit 122. The receiving unit can also be composed of a receiving processing unit 1212, an RF unit 122, and a measurement unit 123.

[0446] The transmitting and receiving antenna 130 can be constructed from an antenna, such as an array antenna, as described based on common knowledge in the art to which this disclosure pertains.

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

[0448] The transmitting and receiving unit 120 may also use digital beamforming (e.g., precoding), analog beamforming (e.g., phase rotation), etc. to form at least one of the transmitting beam and the receiving beam.

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

[0450] The transmitting and receiving unit 120 (transmitting processing unit 1211) can also perform transmission processing such as channel coding (which may also include error correction coding), modulation, mapping, filter processing (filtering processing), Discrete Fourier Transform (DFT) processing (as needed), Inverse Fast Fourier Transform (IFFT) processing, precoding, and digital-to-analog conversion on the bit string to be transmitted, and output the baseband signal.

[0451] The transmitting and receiving unit 120 (RF unit 122) can also perform modulation, filtering, amplification, etc. on the baseband signal to the wireless frequency band, and transmit the wireless frequency band signal through the transmitting and receiving antenna 130.

[0452] On the other hand, the transmitting and receiving unit 120 (RF unit 122) can also amplify, filter, and demodulate the signals of the wireless frequency band received through the transmitting and receiving antenna 130 into the baseband signal.

[0453] The transmitting and receiving unit 120 (receiving and processing unit 1212) can also perform receiving and processing on the acquired baseband signal, including analog-to-digital conversion, Fast Fourier Transform (FFT) processing, Inverse Discrete Fourier Transform (IDFT) processing (as needed), filter processing, demapping, demodulation, decoding (which may also include error correction decoding), MAC layer processing, RLC layer processing, and PDCP layer processing, to acquire user data, etc.

[0454] The transmitting / receiving unit 120 (measurement unit 123) can also perform measurements related to the received signal. For example, the measurement unit 123 can also perform radio resource management (RRM) measurements, channel state information (CSI) measurements, etc., based on the received signal. The measurement unit 123 can also 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 can also be output to the control unit 110.

[0455] The transmission path interface 140 can also transmit and receive signals (backhaul signaling) between the device included in the core network 30 (e.g., the network node providing the NF), other base stations 10, etc., and can also acquire and transmit user data (user plane data), control plane data, etc. for the user terminal 20.

[0456] In addition, the transmitting unit and receiving unit of the base station 10 in this disclosure may also be composed of at least one of a transmitting / receiving unit 120, a transmitting / receiving antenna 130, and a transmission path interface 140.

[0457] The transmitting / receiving unit 120 can transmit a cell handover command containing information about a target cell that is a handover candidate to become the serving cell. The control unit 110 can control path loss calculation based on the measurement results of the reference signal before or after receiving the cell handover command. The control unit 110 can control the power control adjustment state or power escalation for the target cell indicated by the cell handover command.

[0458] (User terminal)

[0459] Figure 23This diagram illustrates an example of the structure of a user terminal according to one embodiment. The user terminal 20 includes a control unit 210, a transmitting / receiving unit 220, and a transmitting / receiving antenna 230. Alternatively, the control unit 210, the transmitting / receiving unit 220, and the transmitting / receiving antenna 230 may each be provided as one or more.

[0460] Furthermore, while this example primarily illustrates the functional blocks of the characteristic portions of this embodiment, it is also conceivable that the user terminal 20 may also have other functional blocks required for wireless communication. Some of the processing of each unit described below may also be omitted.

[0461] The control unit 210 performs overall control of the user terminal 20. The control unit 210 can be composed of a controller, control circuit, etc., which are described based on common knowledge in the technical field to which this disclosure pertains.

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

[0463] The transmitting / receiving unit 220 may also include a baseband unit 221, an RF unit 222, and a measurement unit 223. The baseband unit 221 may also include a transmitting processing unit 2211 and a receiving processing unit 2212. The transmitting / receiving unit 220 may be composed of a transmitter / receiver, RF circuit, baseband circuit, filter, phase shifter, measurement circuit, transmitting / receiving circuit, etc., as described based on common knowledge in the art to which this disclosure pertains.

[0464] The transmitting and receiving unit 220 can be configured as a single integrated transmitting and receiving unit, or it can be composed of a transmitting unit and a receiving unit. The transmitting unit can also be composed of a transmitting processing unit 2211 and an RF unit 222. The receiving unit can also be composed of a receiving processing unit 2212, an RF unit 222, and a measurement unit 223.

[0465] The transmitting and receiving antenna 230 can be constructed from an antenna, such as an array antenna, as described based on common knowledge in the art to which this disclosure pertains.

[0466] The transmitting / receiving unit 220 can also receive the downlink channel, synchronization signal, downlink reference signal, etc., mentioned above. The transmitting / receiving unit 220 can also transmit the uplink channel, uplink reference signal, etc., mentioned above.

[0467] The transmitting and receiving unit 220 may also use digital beamforming (e.g., precoding), analog beamforming (e.g., phase rotation), etc., to form at least one of the transmitting beam and the receiving beam.

[0468] The transmitting and receiving unit 220 (transmitting processing unit 2211) may, for example, perform PDCP layer processing, RLC layer processing (e.g., RLC retransmission control), MAC layer processing (e.g., HARQ retransmission control) on the data and control information obtained from the control unit 210, and generate the bit string to be transmitted.

[0469] The transmitting and receiving unit 220 (transmitting processing unit 2211) can also perform channel coding (which may include error correction coding), modulation, mapping, filter processing, DFT processing (as needed), IFFT processing, precoding, digital-to-analog conversion and other transmission processing on the bit string to be transmitted, and output the baseband signal.

[0470] Furthermore, whether or not to apply DFT processing can be based on the settings of transform precoding. For a certain channel (e.g., PUSCH), if transform precoding is enabled, the transmit / receive unit 220 (transmit processing unit 2211) can perform DFT processing as described above in order to transmit the channel using the DFT-s-OFDM waveform. If not, the transmit / receive unit 220 (transmit processing unit 2211) can perform the above transmission processing without performing DFT processing.

[0471] The transmitting and receiving unit 220 (RF unit 222) can also perform modulation, filtering, amplification, etc. on the baseband signal to the wireless frequency band, and transmit the wireless frequency band signal through the transmitting and receiving antenna 230.

[0472] On the other hand, the transmitting and receiving unit 220 (RF unit 222) can also amplify, filter, demodulate, etc., the signals of the wireless frequency band received by the transmitting and receiving antenna 230.

[0473] The transmitting and receiving unit 220 (receiving and processing unit 2212) can also perform receiving and processing on the acquired baseband signal, such as analog-to-digital conversion, FFT processing, IDFT processing (as needed), filter processing, demapping, demodulation, decoding (which may also include error correction decoding), MAC layer processing, RLC layer processing, and PDCP layer processing, to acquire user data.

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

[0475] Additionally, the measurement unit 223 can also derive channel measurements for CSI calculation based on channel measurement resources. Channel measurement resources can be, for example, non-zero power (NZP) CSI-RS resources. Furthermore, the measurement unit 223 can also derive interference measurements for CSI calculation based on interference measurement resources. Interference measurement resources can be at least one of NZP CSI-RS resources for interference measurement, CSI-Interference Measurement (IM) resources, etc. Additionally, CSI-IM can also be referred to as CSI-Interference Management (IM), and can be interchanged with zero power (ZP) CSI-RS. Furthermore, in this disclosure, CSI-RS, NZP CSI-RS, ZP CSI-RS, CSI-IM, CSI-SSB, etc., can also be interchanged.

[0476] Alternatively, the transmitting and receiving units of the user terminal 20 in this disclosure may also be composed of at least one transmitting / receiving unit 220 and transmitting / receiving antenna 230.

[0477] The transmit / receive unit 220 can receive information related to a target cell that is a handover candidate for serving cell. The control unit 210 can, based on this information, control the transmission of a Physical Random Access Channel (PDCCH command RACH) triggered by a downlink control channel command. If the information contains an indication related to the application of a PDCCH command RACH without a Random Access Acknowledgment (RAR), the control unit 210 can apply the PDCCH command RACH without RAR.

[0478] The transmitting / receiving unit 220 can receive a cell handover command containing information about a target cell that is a handover candidate to become the serving cell. The control unit 210 can control path loss calculation based on measurement results of reference signals before or after receiving the cell handover command. The control unit 210 can also control the path loss calculation using the results of timing advance measurements before receiving the cell handover command. The control unit 210 can control the path loss calculation based on measurement results of reference signals associated with the target cell index or Transmission Setting Indication Status (TCI) index indicated by the cell handover command. The control unit 210 can also control the path loss calculation using measurement results at a specific time before or after receiving the cell handover command.

[0479] Control unit 210 can control the power control adjustment state or power escalation for the target cell indicated by the cell handover command. After a successful cell handover, control unit 210 can reset the power control adjustment state for the target cell based on specific conditions. After a successful cell handover, control unit 210 can reset the power control adjustment state for the target cell based on whether the cell handover command was received or whether a MAC reset was executed. In the case of random access triggered by a downlink control channel command to obtain the timing advance of the target cell, control unit 210 can consider the power escalation number to control the power escalation.

[0480] (Hardware structure)

[0481] Furthermore, the block diagrams used in the description of the above embodiments illustrate functional units. These functional blocks (structural units) are implemented through any combination of at least one of hardware and software. Moreover, the implementation method of each functional block is not particularly limited. That is, each functional block can be implemented using a single device that is physically or logically combined, or it can be implemented by directly or indirectly (e.g., using wired, wireless, etc.) connecting two or more physically or logically separate devices. A functional block can also be implemented by combining the aforementioned single device or multiple devices with software.

[0482] Here, the functions include judgment, decision, determination, calculation, calculation, processing, export, investigation, search, confirmation, receiving, sending, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, regard as, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assigning, but are not limited to these. For example, a functional block (structural unit) that implements the sending function can also be called a transmitting unit, transmitter, etc. Each of these, as described above, is not particularly limited in its implementation method.

[0483] For example, in one embodiment of this disclosure, the base station, user terminal, etc., can also function as a computer for processing the wireless communication method of this disclosure. Figure 24 This diagram illustrates an example of the hardware structure of a base station and a user terminal according to one embodiment. The base station 10 and the user terminal 20 described above can also be physically configured as a computer device including a processor 1001, a memory 1002, a storage device 1003, a communication device 1004, an input device 1005, an output device 1006, and a bus 1007.

[0484] Furthermore, in this disclosure, terms such as apparatus, circuit, device, section, and unit can be interchanged. The hardware structure of base station 10 and user terminal 20 can be configured to include one or more of the apparatuses shown in the figures, or it can be configured not to include any of the apparatuses.

[0485] For example, only one processor 1001 is shown, but there can be multiple processors. Furthermore, processing can be performed by one processor, or simultaneously, sequentially, or by two or more processors using other methods. Additionally, processor 1001 can be implemented using more than one chip.

[0486] Regarding the functions in base station 10 and user terminal 20, for example, by reading specific software (programs) into hardware such as processor 1001 and memory 1002, so that processor 1001 performs calculations and controls communication via communication device 1004, or by controlling at least one of reading and writing data in memory 1002 and storage device 1003.

[0487] The processor 1001 enables the operating system to operate and control the computer as a whole. The processor 1001 may also be a central processing unit (CPU) that includes interfaces with peripheral devices, control devices, arithmetic devices, registers, etc. For example, at least a portion of the control unit 110 (210), the transmit / receive unit 120 (220), etc., described above may also be implemented by the processor 1001.

[0488] Furthermore, the processor 1001 reads programs (program code), software modules, data, etc., from at least one of the storage 1003 and the communication device 1004 into the memory 1002, and performs various processes accordingly. As a program, a program that causes the computer to perform at least a portion of the operations described in the above embodiments can be used. For example, the control unit 110 (210) can also be implemented by a control program stored in the memory 1002 and operated in the processor 1001; similar implementations can be made for other functional blocks.

[0489] The memory 1002 may also be a computer-readable recording medium, such as being composed of at least one of a read-only memory (ROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a random access memory (RAM), or other suitable storage media. The memory 1002 may also be referred to as a register, cache, main memory (main storage device), etc. The memory 1002 is capable of storing executable programs (program code), software modules, etc., for implementing the wireless communication method according to an embodiment of this disclosure.

[0490] Storage device 1003 may also be a computer-readable recording medium, such as a flexible disc, floppy disk, optical disk (e.g., a compact disc ROM), digital multifunction disk, Blu-ray disc, removable disk, hard disk drive, smart card, flash memory device (e.g., a card, stick, key drive), magnetic stripe, database, server, or at least one other suitable storage medium. Storage device 1003 may also be referred to as an auxiliary storage device.

[0491] The communication device 1004 is hardware (transmitting and receiving device) used for communication between computers via at least one of a wired network and a wireless network. It is also referred to as a network device, network controller, network interface card (NIC), communication module, etc. To implement at least one of, for example, Frequency Division Duplex (FDD) and Time Division Duplex (TDD), the communication device 1004 may be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc. For example, the aforementioned transmit / receive unit 120 (220) and transmit / receive antenna 130 (230) may also be implemented by the communication device 1004. The transmit / receive unit 120 (220) may also be implemented by physically or logically separating the transmit unit 120a (220a) and the receive unit 120b (220b).

[0492] Input device 1005 is an input device that receives input from external sources (e.g., keyboard, mouse, microphone, switch, button, sensor, etc.). Output device 1006 is an output device that performs output to external sources (e.g., display, speaker, light-emitting diode (LED) lamp, etc.). Alternatively, input device 1005 and output device 1006 can also be an integrated structure (e.g., a touch panel).

[0493] Furthermore, the processor 1001, memory 1002, and other devices are connected via a bus 1007 for communicating information. The bus 1007 can be configured as a single bus or as different buses between the devices.

[0494] Furthermore, the base station 10 and the user terminal 20 can also 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 can also use this hardware to implement part or all of the functional blocks. For example, the processor 1001 can also be implemented using at least one of these hardware components.

[0495] (Modified example)

[0496] Furthermore, the terms described in this disclosure, as well as those necessary for understanding this disclosure, may be replaced with terms that have the same or similar meanings. For example, channel, symbol, and signal (signal or signaling) may be interchanged. Additionally, a signal may also be a message. A reference signal can also be abbreviated as RS, and may be referred to as pilot, pilot signal, etc., depending on the applied standard. Furthermore, a component carrier (CC) may also be referred to as cell, frequency carrier, carrier frequency, etc.

[0497] A radio frame can also be composed of one or more periods (frames) in the time domain. Each of these periods (frames) that constitute a radio frame can also be called a subframe. Furthermore, a subframe can also be composed of one or more time slots in the time domain. A subframe can also be a fixed time length (e.g., 1 ms) independent of the parameter set (numerology).

[0498] Here, the parameter set can also be communication parameters applied in at least one of the transmission and reception of a signal or channel. For example, the parameter set can also represent at least one of the following: subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, radio frame structure, specific filtering processing performed by the transmitter and receiver in the frequency domain, and specific windowing processing performed by the transmitter and receiver in the time domain.

[0499] In the time domain, a time slot can also be composed of one or more symbols (Orthogonal Frequency Division Multiplexing (OFDM) symbols, Single Carrier Frequency Division Multiple Access (SC-FDMA) symbols, etc.). In addition, a time slot can also be a time unit based on a set of parameters.

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

[0501] Radio frames, subframes, time slots, mini-time slots, and symbols all represent time units for transmitting signals. Radio frames, subframes, time slots, mini-time slots, and symbols can also use their respective other names. Furthermore, the time units such as frames, subframes, time slots, mini-time slots, and symbols in this disclosure can be interchanged.

[0502] For example, a subframe can also be called a TTI, multiple consecutive subframes can also be called a TTI, and a time slot or a mini-time slot can also be called a TTI. That is, at least one of a subframe and a TTI can be a subframe in existing LTE (1ms), a period shorter than 1ms (e.g., 1-13 symbols), or a period longer than 1ms. In addition, the unit representing TTI may not be called a subframe, but rather a time slot, mini-time slot, etc.

[0503] Here, TTI refers, for example, to the smallest unit of time for scheduling in wireless communication. For instance, in an LTE system, the base station schedules radio resources (frequency bandwidth, transmit power, etc., available to each user terminal) in TTI units. However, the definition of TTI is not limited to this.

[0504] TTI can also be a unit of time for transmitting channel-coded data packets (transmission blocks), code blocks, codewords, etc., and can also be a unit of processing such as scheduling and link adaptation. In addition, when a TTI is given, the actual time interval (e.g., the number of symbols) mapped to transmission blocks, code blocks, codewords, etc. can be shorter than the TTI.

[0505] Additionally, where a time slot or a mini-time slot is referred to as a TTI, more than one TTI (i.e., more than one time slot or more than one mini-time slot) can also serve as the minimum time unit for scheduling. Furthermore, the number of time slots (mini-time slots) constituting the minimum time unit of the schedule can also be controlled.

[0506] A TTI with a duration of 1ms can also be referred to as a normal TTI (TTI in 3GPPRel.8-12), a standard TTI, a long TTI, a normal subframe, a standard subframe, a long subframe, a time slot, etc. A TTI shorter than a normal TTI can also be referred to as a shortened TTI, a short TTI, a partial TTI (partial or fractional TTI), a shortened subframe, a short subframe, a mini time slot, a sub-time slot, a time slot, etc.

[0507] In addition, a long TTI (e.g., a normal TTI, a subframe, etc.) can also be rewritten as a TTI with a duration of more than 1 ms, and a short TTI (e.g., a shortened TTI, etc.) can also be rewritten as a TTI with a duration of less than a long TTI but more than 1 ms.

[0508] A resource block (RB) is a unit of resource allocation in both the time and frequency domains. In the frequency domain, it can also contain one or more consecutive subcarriers. The number of subcarriers in an RB can be the same regardless of the parameter set, for example, it can be 12. The number of subcarriers in an RB can also be determined based on the parameter set.

[0509] Furthermore, an RB can contain one or more symbols in the time domain, and can also be a time slot, a mini-time slot, a subframe, or the length of a TTI. A TTI, a subframe, etc., can also be composed of one or more resource blocks.

[0510] In addition, one or more RBs can also be referred to as Physical Resource Blocks (PRBs), Sub-Carrier Groups (SCGs), Resource Element Groups (REGs), PRB pairs, RB pairs, etc.

[0511] In addition, a resource block can also consist of one or more resource elements (REs). For example, an RE can also be a radio resource area consisting of a subcarrier and a symbol.

[0512] The Bandwidth Part (BWP) (also referred to as partial bandwidth, etc.) can also represent a subset of consecutive common resource blocks (RBs) used for a certain parameter set in a certain carrier. Here, common RBs can also be determined by the index of RBs based on the common reference point of the carrier. PRBs can also be defined in a BWP and appended with numbers within that BWP.

[0513] A BWP can also include a UL BWP (the BWP used by UL) and a DL BWP (the BWP used by DL). For a UE, one or more BWPs can also be set within a single carrier.

[0514] At least one of the configured BWPs can be active, and the UE may not intend to transmit or receive specific signals / channels outside of the active BWPs. Additionally, terms such as "cell" and "carrier" in this disclosure may be replaced with "BWP".

[0515] Furthermore, the structures described above, such as radio frames, subframes, time slots, mini-time slots, and symbols, are merely illustrative. For example, the number of subframes contained in a radio frame, the number of time slots in each subframe or radio frame, the number of mini-time slots contained within a time slot, the number of symbols and RBs contained in a time slot or mini-time slot, the number of subcarriers contained in an RB, and the number of symbols in a TTI, symbol length, and cyclic prefix (CP) length can be varied in many ways.

[0516] Furthermore, the information, parameters, etc., described in this disclosure can be represented by absolute values, relative values ​​with respect to a specific value, or other corresponding information. For example, wireless resources can also be indicated by a specific index.

[0517] In this disclosure, the names used for parameters, etc., are not limiting names in any respect. Furthermore, the mathematical expressions, etc., using these parameters may differ from those explicitly disclosed in this disclosure. Various channels (PUCCH, PDCCH, etc.) and information elements can be identified by any suitable name; therefore, the various names assigned to these various channels and information elements are not limiting names in any respect.

[0518] The information, signals, etc., described in this disclosure can also be represented using any of a variety of different technologies. For example, data, instructions, commands, information, signals, bits, symbols, chips, etc., which may be mentioned throughout the above description, can also be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or photons, or any combination thereof.

[0519] Furthermore, information, signals, etc., can be output in at least one of the following directions: from higher level (upper layer) to lower level (lower layer), and from lower layer to higher level. Information, signals, etc., can also be input and output via multiple network nodes.

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

[0521] The notification of information is not limited to the methods / implementations described in this disclosure, and may also be carried out by other methods. For example, the notification of information in this disclosure may also be implemented by physical layer signaling (e.g., downlink control information (DCI), uplink control information (UCI), etc.), higher layer signaling (e.g., radio resource control (RRC) signaling, broadcast information (Master Information Block (MIB), System Information Block (SIB) etc.), medium access control (MAC) signaling), other signals, or combinations thereof.

[0522] In addition, physical layer signaling can also be referred to as Layer 1 / Layer 2 (L1 / L2) control information (L1 / L2 control signals), L1 control information (L1 control signals), etc. Furthermore, RRC signaling can also be referred to as RRC messages, such as RRC connection setup messages, RRC connection reconfiguration messages, etc. Additionally, MAC signaling can also be notified using, for example, the MAC control element (CE).

[0523] Furthermore, notification of specific information (e.g., a notification of “is X”) is not limited to explicit notification, but can also be implicit (e.g., by not providing that specific information, or by providing other information).

[0524] The determination can be made by a value represented by a single bit (0 or 1), by a true or false value (boolean), or by a numerical comparison (e.g., a comparison with a specific value).

[0525] Whether software is called software, firmware, middleware, microcode, hardware description language, or any other name, it should be broadly interpreted to refer to instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, functions, etc.

[0526] Furthermore, software, instructions, and information can also be sent and received via a transmission medium. For example, when software is sent from a website, server, or other remote source using at least one of wired technologies (coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL) etc.) and wireless technologies (infrared, microwave, etc.), at least one of these wired and wireless technologies is included within the definition of a transmission medium.

[0527] The terms “system” and “network” as used in this disclosure are interchangeable. “Network” may also mean devices included in a network (e.g., base stations).

[0528] In this disclosure, the terms “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”, “beamwidth”, “beam angle”, “antenna”, “antenna element”, “panel”, “UE panel”, “transmitting entity”, and “receiving entity” are used interchangeably.

[0529] Furthermore, in this disclosure, the antenna port can also be rewritten with an antenna port used for any signal / channel (e.g., a DeModulation Reference Signal (DMRS) port). In this disclosure, resources can also be rewritten with resources used for any signal / channel (e.g., reference signal resources, SRS resources, etc.). Additionally, resources can also include time / frequency / code / space / power resources. Moreover, the spatial domain transmission filter can also include at least one of a spatial domain transmission filter and a spatial domain reception filter.

[0530] The aforementioned groups may include, for example, at least one of the following: spatial relation group, code division multiplexing (CDM) group, reference signal (RS) group, control resource set (CORESET) group, PUCCH group, antenna port group (e.g., DMRS port group), layer group, resource group, beam group, antenna group, panel group, etc.

[0531] Furthermore, in this disclosure, beam, SRS Resource Indicator (SRI), CORESET, CORESET pool, PDSCH, PUSCH, Codeword (CW), Transport Block (TB), RS, etc., can also be rewritten to each other.

[0532] Furthermore, in this disclosure, the TCI state, downlink TCI state (DL TCI state), uplink TCI state (UL TCI state), unified TCI state, common TCI state, and joint TCI state can also be rewritten to each other.

[0533] Furthermore, in this disclosure, terms such as "QCL", "QCL concept", "QCL relationship", "QCL type information", "QCL property (QCLproperty / properties)", "specific QCL type (e.g., type A, type D) property", and "specific QCL type (e.g., type A, type D)" can be rewritten interchangeably.

[0534] In this disclosure, indexes, identifiers (IDs), indicators, indications, resource IDs, etc., can be interchanged. Sequences, lists, sets, groups, clusters, subsets, etc., can also be interchanged.

[0535] Furthermore, the spatial relationship information identifier (ID) (TCI state ID) and the spatial relationship information (TCI state) can be interchanged. "Spatial relationship information (TCI state)" can also be interchanged with "a set of spatial relationship information (TCI states)," "one or more spatial relationship information," etc. TCI state and TCI can also be interchanged. Spatial relationship information and spatial relationship can also be interchanged.

[0536] In this disclosure, the terms "Base Station (BS)", "Wireless Base Station", "Fixed Station", "NodeB", "eNB (eNodeB)", "gNB (gNodeB)", "Access Point", "Transmission Point (TP)", "Reception Point (RP)", "Transmission / Reception Point (TRP)", "Panel", "Cell", "Sector", "Cell Group", "Carrier", and "Component Carrier" are used interchangeably. There are also instances where the terms macro cell, small cell, femtocell, and picocell are used to refer to a base station.

[0537] A base station can accommodate one or more (e.g., three) cells. When a base station accommodates multiple cells, its overall coverage area can be divided into several smaller areas, each of which can also provide communication services through a base station subsystem (e.g., a small indoor base station (Remote Radio Head (RRH))). Terms such as "cell" or "sector" refer to a portion or all of the coverage area of ​​at least one of the base station and base station subsystem providing communication services within that coverage area.

[0538] In this disclosure, the act of a base station sending information to a terminal can also be rewritten in relation to the act of the base station instructing the terminal to perform control / operation based on that information.

[0539] In this disclosure, the terms “Mobile Station (MS)”, “user terminal”, “user equipment (UE)”, and “terminal” are used interchangeably.

[0540] There are also instances where mobile stations are referred to as subscriber stations, mobile units, subscriber units, wireless units, remote units, mobile devices, wireless devices, wireless communication devices, remote devices, mobile subscriber stations, access terminals, mobile terminals, wireless terminals, remote terminals, handsets, user agents, mobile clients, clients, or several other appropriate terms.

[0541] At least one of the base station and the mobile station can also be referred to as a transmitting device, a receiving device, a wireless communication device, etc. Additionally, at least one of the base station and the mobile station can also be a device mounted on a moving object, the moving object itself, etc.

[0542] The term "mobile body" refers to a movable object whose speed is arbitrary, including situations where the body is stationary. Examples of such mobile bodies include vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, handcarts, rickshaws, ships (ships and other watercraft), airplanes, rockets, artificial satellites, drones, multicopters, quadcopters, hot air balloons, and objects carried on them, but are not limited to these. Furthermore, the mobile body can also be a mobile body that moves autonomously based on operational commands.

[0543] The mobile entity can be a means of transportation (e.g., a vehicle, an airplane, etc.), a mobile entity moving in an unmanned manner (e.g., a drone, an autonomous vehicle, etc.), or a robot (humanized or unmanned). Additionally, at least one of the base station and the mobile station also includes a device that does not necessarily move during communication operations. For example, at least one of the base station and the mobile station can also be an Internet of Things (IoT) device such as a sensor.

[0544] Figure 25This is a diagram illustrating an example of a vehicle according to one embodiment. The vehicle 40 includes a drive unit 41, a steering unit 42, an accelerator pedal 43, a brake pedal 44, a shift lever 45, left and right front wheels 46, left and right rear wheels 47, an axle 48, an electronic control unit 49, various sensors (including a current sensor 50, a speed sensor 51, a 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.

[0545] The drive unit 41 is comprised of at least one of an engine, a motor, or a combination of an engine and a motor. The steering unit 42 is configured to include at least a steering wheel (also called a steering handle) that steers at least one of the front wheels 46 and the rear wheels 47 based on operation of the steering wheel by the user.

[0546] The electronic control unit 49 consists of a microprocessor 61, a memory (ROM, RAM) 62, and a communication port (e.g., an input / output (IO) port) 63). Signals from various sensors 50-58 present in the vehicle are input to the electronic control unit 49. The electronic control unit 49 can also be referred to as an electronic control unit (ECU).

[0547] The signals from various sensors 50-58 include the following: current signal from current sensor 50 sensing the current of the motor; rotational speed signal of front wheel 46 / rear wheel 47 obtained by speed sensor 51; air pressure signal of front wheel 46 / rear wheel 47 obtained by air pressure sensor 52; vehicle speed signal obtained by vehicle speed sensor 53; acceleration signal obtained by acceleration sensor 54; accelerator pedal 43 depress amount signal obtained by accelerator pedal sensor 55; brake pedal 44 depress amount signal obtained by brake pedal sensor 56; shift lever 45 operation signal obtained by shift lever sensor 57; and detection signal obtained by object detection sensor 58 for detecting obstacles, vehicles, pedestrians, etc.

[0548] The information service unit 59 comprises various devices such as a navigation system, audio system, speakers, display, television, and radio, used to provide (output) various information such as driving information, traffic information, and entertainment information, and one or more ECUs that control these devices. The information service unit 59 uses information obtained from external devices via the communication module 60, etc., to provide various information / services (e.g., multimedia information / multimedia services) to the occupants of the vehicle 40.

[0549] The information service unit 59 may include input devices (e.g., keyboard, mouse, microphone, switch, button, sensor, touch panel, etc.) that accept input from the outside, and output devices (e.g., display, speaker, LED light, touch panel, etc.) that implement output to the outside.

[0550] The driver assistance system unit 64 comprises various devices used to provide functions for preventing accidents or reducing the driver's workload, such as millimeter-wave radar, light detection and ranging (LiDAR), cameras, positioning detectors (e.g., Global Navigation Satellite System (GNSS), map information (e.g., High Definition (HD) maps, Autonomous Vehicle (AV) maps), gyroscope systems (e.g., Inertial Measurement Unit (IMU), Inertial Navigation System (INS), etc.), artificial intelligence (AI) chips, and AI processors, and one or more ECUs that control these devices. Furthermore, the driver assistance system unit 64 sends and receives various information via communication module 60 to realize driver assistance functions or autonomous driving functions.

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

[0552] The communication module 60 can be controlled by the microprocessor 61 of the electronic control unit 49 and is a communication device capable of communicating with external devices. For example, it can transmit and receive various types of information with external devices via wireless communication. The communication module 60 can be located both inside and outside the electronic control unit 49. The external device can be, for example, the aforementioned base station 10, user terminal 20, etc. Furthermore, the communication module 60 can be, for example, at least one of the aforementioned base station 10 and user terminal 20 (or it can function as at least one of the base station 10 and user terminal 20).

[0553] The communication module 60 can also wirelessly transmit at least one of the signals input to the electronic control unit 49 from the various sensors 50-58 described above, the information obtained based on these signals, and the information based on input from an external (user) source obtained via the information service unit 59 to an external device. The electronic control unit 49, the various sensors 50-58, the information service unit 59, etc., can also be referred to as input units that receive input. For example, the PUSCH transmitted via the communication module 60 can also contain information based on the aforementioned inputs.

[0554] The communication module 60 receives various information (traffic information, signal information, workshop information, etc.) sent from external devices and displays it on the vehicle's information service unit 59. The information service unit 59 can also be referred to as an output unit that outputs information (for example, outputs information to devices such as displays and speakers based on the PDSCH received by the communication module 60 (or the data / information decoded from the PDSCH).

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

[0556] Furthermore, the base station in this disclosure can also be rewritten as a user terminal. For example, various methods / implementations of this disclosure can be applied to structures where communication between the base station and the user terminal is replaced by communication between multiple user terminals (e.g., also referred to as device-to-device (D2D) or vehicle-to-everything (V2X)). In this case, it can also be configured such that the user terminal 20 has the functions of the base station 10 described above. In addition, terms such as "uplink" and "downlink" can be rewritten as terms corresponding to inter-terminal communication (e.g., "sidelink"). For example, uplink channel, downlink channel, etc., can also be rewritten as sidelink channel.

[0557] Similarly, the user terminal in this disclosure can also be rewritten as a base station. In this case, it can also be configured such that the base station 10 has the functions of the user terminal 20 described above.

[0558] In this disclosure, operations are assumed to be performed by the base station, and sometimes, depending on the circumstances, by its upper node. In a network containing one or more network nodes having a base station, the various operations performed for communication with a terminal can obviously be performed by the base station, one or more network nodes other than the base station (e.g., considering a Mobility Management Entity (MME), a Serving-Gateway (S-GW), etc., but not limited to these), or combinations thereof.

[0559] The various methods / implementations described in this disclosure can be used individually or in combination, and can be switched as needed during execution. Furthermore, the processing procedures, timing sequences, flowcharts, etc., of the various methods / implementations described in this disclosure can be rearranged as long as they do not contradict each other. For example, for the method described in this disclosure, the illustrated order is used to indicate various steps, but the order in which they are indicated is not limited.

[0560] The various methods / implementations described in this disclosure can also be applied to Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 6th generation mobile communication system (6G), xth generation mobile communication system (xG, where x is, for example, an integer or a decimal)), Future Radio Access (FRA), New-Radio Access Technology (RAT), New Radio (NR), New Radio Access (NX), Futuregeneration Radio Access (FX), Global System for Mobile Communications (GSM (registered trademark)), CDMA2000, Ultra Mobile Broadband (UMB), IEEE This includes 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, Ultra-Wideband (UWB)), Bluetooth (registered trademark), systems utilizing other suitable wireless communication methods, and next-generation systems derived from, modified, generated, or specified based on these methods. Furthermore, multiple systems can be combined (e.g., LTE or LTE-A, combinations with 5G, etc.) for application.

[0561] As used in this disclosure, the term "based on" does not mean "based on only" unless otherwise specified. In other words, the term "based on" means both "based on only" and "based on at least".

[0562] Any reference to an element using the designations "first," "second," etc., as used in this disclosure does not comprehensively limit the quantity or order of these elements. These designations may be used in this disclosure as a convenient method of distinguishing between two or more elements. Therefore, reference to the first and second elements does not imply that only two elements may be used, or that the first element must take precedence over the second element in some form.

[0563] The term "determining" as used in this disclosure can encompass a wide variety of operations. For example, "determining" can also refer to judging, calculating, computing, processing, deriving, investigating, looking up (search, inquiry) (e.g., searching in a table, database or other data structure), and ascertaining.

[0564] In addition, "judgment (decision)" can also refer to receiving (e.g., receiving information), transmitting (e.g., sending information), inputting, outputting, accessing (e.g., accessing data in memory), etc., as situations where "judgment (decision)" is performed.

[0565] Furthermore, "judgment (decision)" can also refer to situations where resolving, selecting, choosing, establishing, or comparing are considered as making a "judgment (decision)". That is, "judgment (decision)" can also refer to certain operations as making a "judgment (decision)". In this disclosure, "judgment (decision)" can also be rewritten in relation to the operations described above.

[0566] Furthermore, in this disclosure, "determine / determining" can also be interchanged with "assume / assuming," "expect / expecting," "consider / considering," etc. Additionally, in this disclosure, "not assuming to proceed..." can also be interchanged with "assuming not to proceed..."

[0567] In this disclosure, "expect" can also be interchanged with "be expected." For example, "expect(s) ..." (where "..." can also be expressed using a that clause, to infinitive, etc.) can also be interchanged with "be expected ...." "Does not expect..." can also be interchanged with "be not expected...". Furthermore, "An apparatus A is not expected..." can also be interchanged with "Apparatus B other than apparatus A does not expect..." (for example, if apparatus A is a UE, apparatus B can also be a base station).

[0568] The term "maximum transmit power" as used in this disclosure may refer to the maximum value of the transmit power, the nominal maximum transmit power (the nominal UE maximum transmit power), or the rated maximum transmit power (the rated UE maximum transmit power).

[0569] As used in this disclosure, the terms “connected,” “coupled,” or all variations thereof, refer to all direct or indirect connections or combinations between two or more elements, and can include cases where there is one or more intermediate elements between two mutually “connected” or “coupled” elements. The connections or combinations between elements can be physical, logical, or a combination thereof. For example, “connection” can also be rewritten as “access.”

[0570] In this disclosure, when two elements are connected, it is possible to consider using more than one wire, cable, printed electrical connection, etc. to be "connected" or "combined" with each other, and as several non-limiting and non-exclusive examples, to use electromagnetic energy with wavelengths having wireless frequency domain, microwave region, light (both visible and invisible) region to be "connected" or "combined" with each other.

[0571] In this disclosure, the term "A is different from B" can also mean "A and B are different from each other." Additionally, the term can also mean "A and B are each different from C." Terms such as "separate" and "combined" can also be interpreted in the same way as "different."

[0572] When the terms "include," "including," and variations thereof are used in this disclosure, these terms, like the term "comprising," mean inclusive. Furthermore, the term "or" as used in this disclosure does not mean XOR.

[0573] In this disclosure, for example, in cases where articles are added through translation, such as a, an, and the in English, the disclosure may also include cases where the noun following these articles is in a plural form.

[0574] In this disclosure, words such as "below," "less than," "above," "more than," and "equal to" can be interchanged. Furthermore, in this disclosure, words meaning "good," "bad," "large," "small," "high," "low," "early," "slow," "wide," and "narrow," etc., are not limited to the positive, comparative, and superlative degrees, and can be interchanged. Additionally, in this disclosure, words meaning "good," "bad," "large," "small," "high," "low," "early," "slow," "wide," and "narrow," etc., as expressions with "i" appended (i being any integer), are not limited to the positive, comparative, and superlative degrees, and can be interchanged (for example, "highest" can also be interchanged with "i-th highest").

[0575] In this disclosure, "of", "for", "regarding", "related to", "associated with", etc., can also be rewritten interchangeably.

[0576] In this disclosure, phrases such as "when A, B", "if A, then B", "B upon A", "B in response to A", "based on A", "B during / while A", "before A", "at the same time as / on A", "after A", "since A", and "until A" can be rewritten interchangeably. Furthermore, A and B can be replaced with nouns, gerunds, or ordinary sentences, depending on the context. Additionally, the time difference between A and B can be approximately zero (immediately following or immediately preceding). Moreover, a time offset can be applied to the time A occurs. For example, "A" can be rewritten interchangeably with "before / after the time offset of A". This time offset (e.g., more than one symbol / slot) can be predetermined or determined by the UE based on the information provided.

[0577] In this disclosure, timing, moment, time, time instance, arbitrary time unit (e.g., time slot, sub-time slot, symbol, subframe), period, opportunity, resource, etc., can also be overridden.

[0578] The inventions disclosed herein have been described in detail above. However, it will be apparent to those skilled in the art that the inventions disclosed herein are not limited to the embodiments described herein. The description herein is for illustrative purposes only and is not intended to limit the inventions disclosed herein in any way.

[0579] This application is based on Japan Patent Application No. 2023-137356, filed on August 25, 2023. Its entire contents are contained herein.

Claims

1. A terminal, comprising: The receiving unit receives a cell handover command containing information about a target cell that is a handover candidate to become the serving cell; and The control unit calculates the path loss based on the measurement results of the reference signal before or after receiving the cell handover command.

2. The terminal as described in claim 1, wherein, The control unit uses the results of a timing advance measurement before receiving the cell handover command to control the path loss calculation.

3. The terminal as described in claim 1, wherein, The control unit controls the path loss calculation based on the measurement results of a reference signal associated with the target cell index indicated by the cell handover command or the TCI index for sending a setting indication state.

4. The terminal as described in claim 1, wherein, The control unit uses measurement results from a specific time period before or after receiving the cell handover command to control the path loss calculation.

5. A wireless communication method for a terminal, comprising: The steps of receiving a cell handover command containing information about a target cell that will become a serving cell handover candidate; and The control path loss calculation step is based on the measurement results of the reference signal before or after receiving the cell handover command.

6. A base station, comprising: The transmitting unit transmits a cell handover command containing information about the target cell that is to become a handover candidate serving cell; and The control unit calculates the path loss based on the measurement results of the reference signal before or after receiving the cell handover command.

Images