Terminal, radio communication method, and base station

Abstract

A terminal according to one aspect of the present disclosure comprises a receiving unit that receives a configuration relating to a channel state information (CSI) trigger state, and downlink control information (DCI) including a CSI request field indicating the CSI trigger state, and a control unit that, on the basis of the CSI trigger state, controls aperiodic CSI reporting or beam reporting (UEIBR) initiated by the terminal, wherein the control unit determines the CSI trigger state on the basis of a correspondence relationship between the configuration and the CSI trigger state.

Description

Terminal, wireless communication method, and base station

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

[0002] In the Universal Mobile Telecommunications System (UMTS) network, Long Term Evolution (LTE) was specified with the aim of achieving even higher data rates and lower latency (Non-Patent Literature 1). Furthermore, LTE-Advanced (3GPP Rel. 10-14) was specified with the aim of further increasing the capacity and sophistication of LTE (Third Generation Partnership Project (3GPP®) Release (Rel.) 8, 9).

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

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

[0005] In future wireless communication systems (e.g., NR, Rel. 19 and later), support for event-based beam reporting (UE-initiated Beam Report (UEIBR)) initiated by a terminal (user terminal, User Equipment (UE)) is being considered.

[0006] Such beam reporting (CSI measurement / reporting) is being considered for support in MIMO / mobility systems from Rel. 19 onwards.

[0007] However, there are cases where CSI measurement / reporting (UEIBR) for MIMO has not been adequately considered. If this consideration is insufficient, it may not be possible to achieve lower latency communication, potentially hindering improvements in communication quality and throughput.

[0008] Therefore, one of the objectives of this disclosure is to provide a terminal, a wireless communication method, and a base station that can improve communication quality / throughput.

[0009] A terminal according to one aspect of the present disclosure includes a receiving unit that receives a setting relating to a channel status information (CSI) trigger state and downlink control information (DCI) including a CSI request field indicating the CSI trigger state, and a control unit that controls aperiodic CSI reporting or beam reporting (UEIBR) initiated by the terminal based on the CSI trigger state, wherein the control unit determines the CSI trigger state based on the correspondence between the setting and the CSI trigger state.

[0010] According to one aspect of this disclosure, communication quality / throughput can be improved.

[0011] Figure 1A shows an example of UE movement in Rel. 17. Figure 1B shows an example of UE movement in Rel. 18. Figure 2 shows an example of trigger state indication. Figure 3 shows an example of the correspondence between the reporting settings for Alt1 in Embodiment 1-0 and the CSI trigger state. Figure 4 shows an example of the correspondence between the reporting settings for Alt2 in Embodiment 1-0 and the CSI trigger state. Figure 5 shows an example of the correspondence between the reporting settings for Alt3 in Embodiment 1-0 and the CSI trigger state. Figure 6 shows an example of the correspondence between the reporting settings for Alt4 in Embodiment 1-0 and the CSI trigger state. Figures 7A and 7B show examples of assumed cases (Alt1-1 / 1-2) for the UEIBR in Embodiment 1-1, respectively. Figures 8A and 8B show examples of assumed cases (Alt2-1 / 2-2) for the UEIBR in Embodiment 1-1, respectively. Figures 9A and 9B show an example of a case where the UE cannot correctly receive the first DL signal. Figures 10A and 10B show an example of a case where the NW cannot correctly receive the second UL channel. Figures 11A and 11B show a modified UEIBR. Figures 12A and 12B show a modified UEIBR. Figures 13A and 13B show a modified UEIBR. Figure 14 shows an example of a schematic configuration of a wireless communication system according to one embodiment. Figure 15 shows an example of a base station configuration according to one embodiment. Figure 16 shows an example of a user terminal configuration according to one embodiment. Figure 17 shows an example of the hardware configuration of a base station and user terminal according to one embodiment. Figure 18 shows an example of a vehicle according to one embodiment.

[0012] (L1 / L2 Inter-Cell Mobility) A UE may perform UL transmissions to one or more cells / TRPs. In this case, the following Scenario 1 or Scenario 2 procedures are possible. In this disclosure, a serving cell may be interpreted as a TRP within a serving cell. Layer 1 / layer 2 (L1 / L2) and DCI / Medium Access Control Control Element (MAC CE) may be interpreted as mutually exclusive. In this disclosure, a PCI different from the Physical Cell Identity (PCI) of the current serving cell may be simply referred to as a "different PCI". Non-serving cells, cells with different PCIs, and additional cells may be interpreted as mutually exclusive.

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

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

[0015] In Scenario 1, when the UE sends and receives signals with the additional cell / TRP (the TRP corresponding to the PCI of the additional cell), the serving cell (the UE's assumption of the serving cell) remains unchanged. The UE sets higher-layer parameters related to the PCI of the non-serving cell from the serving cell. Scenario 1 may be applied, for example, in Rel. 17.

[0016] Figure 1A shows an example of UE movement in Rel. 17. It assumes a UE moving from a PCI#1 cell (serving cell) to a PCI#3 cell (additional cell) (overlapping with the serving cell). In this case, Rel. 17 does not support L1 / L2 switching of serving cells.

[0017] An additional cell is a cell with an additional PCI that is different from the PCI of the serving cell. UEs can receive and transmit UE-dedicated channels from additional cells. UEs need to be within the coverage of the serving cell to receive UE common channels (e.g., system information / paging / short messages). If a UE moves outside the coverage of the serving cell, a cell switch is required, such as through a handover (also called L3 mobility).

[0018] <Scenario 2> In Scenario 2, L1 / L2 cell mobility is applied. With L1 / L2 cell mobility, serving cell changes can be made using functions such as beam control without RRC reconfiguration. In other words, transmission and reception with additional cells are possible without handover. Since handover requires RRC reconnection and other factors, resulting in a period of no data communication, applying L1 / L2 cell mobility that does not require handover allows data communication to continue even when the serving cell is changed. Scenario 2 may be applied, for example, in Rel. 18. In Scenario 2, for example, the following procedure is performed.

[0019] (1) The UE receives the SSB configuration of a cell with a different PCI (additional cell) from the serving cell for beam measurement / serving cell change. (2) The UE performs beam measurement on the cell using the different PCI and reports the measurement results to the serving cell. (3) The UE may receive the configuration of the cell with the different PCI (serving cell configuration) by upper layer signaling (e.g., RRC). In other words, a pre-configuration regarding the serving cell change may be performed. This configuration may be performed together with the configuration in (1) or separately. (4) Based on the above report, the TCI state of the cell with the different PCI may be activated by L1 / L2 signaling in accordance with the serving cell change. The activation of the TCI state and the serving cell change may be performed separately. (5) The UE changes the serving cell (assumed serving cell) and starts receiving / transmitting using the pre-configured UE-specific channel and TCI state.

[0020] In other words, in Scenario 2, the serving cell (the assumed serving cell in the UE) is updated by L1 / L2 signaling. Scenario 2 may also be applied in Rel. 18.

[0021] Figure 1B shows an example of UE movement in Rel. 18. In Rel. 18, serving cells are switched by L1 / L2 (e.g., DCI / MAC CE). UEs can receive / transmit UE-dedicated / common channels to and from the new serving cell (or target serving cell). UEs may leave the coverage of the current serving cell (e.g., Current serving cell).

[0022] (Beam reporting type) <Intra-cell beam reporting in Rel. 15 / 16> Intra-cell beam reporting is supported in Rel. 15 / 16. For example, L1-RSRP / SINR reporting can be configured by upper-layer signaling (RRC).

[0023] For example, in the calculation of L1-RSRP, the UE may configure either or both a CSI-RS resource and / or an SS / PBCH block resource if the resource is associated with QCL type C / type D.

[0024] Furthermore, the UE may configure up to 16 CSI-RS resource sets, each containing up to 64 resources. In all resource sets, the total number of different CSI-RS resources is 128 or less.

[0025] In L1-RSRP reporting, if the upper layer parameter nrofReportedRS (for example, in CSI-ReportConfig) is set to 1, the reported L1-RSRP value is defined as a 7-bit value in the range of [-140 to -44] dBm with a step size of 1 dB.

[0026] Here, the maximum measurement of L1-RSRP is quantized to a 7-bit value in the range of [-140 to -44] dBm with a step size of 1 dB. The difference value of L1-RSRP is quantized to a 4-bit value.

[0027] The difference value is calculated with a step size of 2 dB, referencing the largest measurement that is part of the same L1-RSRP reporting instance.

[0028] For example, in L1-SINR calculation and channel measurement, the UE may configure either an NZP CSI-RS resource and / or an SS / PBCH block resource. Furthermore, for interference measurement, the UE may configure either an NZP CSI-RS resource or a CSI-IM resource.

[0029] For channel measurement, the UE can configure CSI resource settings for up to 64 CSI resources or up to 16 CSI-RS resource sets having SS / PBCH block resources.

[0030] In L1-SINR reporting, if the upper layer parameter nrofReportedRS is set to 1, the reported L1-SINR value is defined as a 7-bit value in the range of [-23 to 40] dBm with a step size of 0.5 dB.

[0031] If the upper layer parameter nrofReportedRS is set to a value greater than 1, or if the upper layer parameter groupBasedBeamReporting is set to "enabled", the UE will use the difference-based L1-SINR value for reporting.

[0032] The difference value is calculated with a step size of 1 dB, referencing the largest measurement that is part of the same L1-SINR reporting instance.

[0033] In this disclosure, the intra-cell beam report of Rel. 15 / 16 (which may also be simply called the intra-cell beam report) may be called a type 1 beam report (beam report type 1), or a beam report for intra-cell beam switching.

[0034] <Inter-cell beam report for Rel. 17> As mentioned above, L1 / L2 inter-cell mobility is supported in Rel. 17. For example, a UE can send and receive UL / DL channels / signals to and from a PCI of a different cell than the PCI of the serving cell. For example, if a non-serving cell has a larger RSRP than the serving cell, the UE can send and receive UL / DL channels / signals to and from the non-serving cell without performing a handover.

[0035] In the L1-RSRP report, the absolute value / difference value of L1-RSRP may be used, as in Rel. 15 / 16. In the inter-cell beam report of Rel. 17 (Type 2-1 beam report described later), each L1-RSRP value is associated with a PCI ID (for the serving cell / additional cell / candidate cell). The association between the L1-RSRP value and the PCI ID may be set / instructed by upper-layer signaling / physical-layer signaling.

[0036] The configuration by upper layer signaling supports up to seven additional cells. Note that ID = 0 means the PCI of the serving cell.

[0037] In the present disclosure, inter-cell beam reporting (in Rel. 17 / 18) may be referred to as type 2 beam reporting (beam reporting type 2). Type 2 beam reporting can be further classified into type 2-1 and type 2-2, which will be described later.

[0038] In the present disclosure, the beam reporting of Rel. 17 may be referred to as type 2-1 beam reporting, or beam reporting for inter-cell beam switching.

[0039] <Inter-cell beam reporting in Rel. 18> Also, for the beam reporting in Rel. 18, only SSB-based L1-RSRP reporting (beam reporting) is supported. Here, the number of candidate cells L can be any one of 1 to 4, and the number of beams M per cell (per hit) can be any one of 1 to 4. For example, in beam reporting, a 7-bit absolute value (the largest L1-RSRP value among all cells) is reported for one cell, and all the remaining L1-RSRP values are reported as difference values.

[0040] Regarding beam selection in SSB-based L1-RSRP reporting, the maximum value of M*L that can be set by RRC for the above-mentioned M and L, and the combination of M and L may vary depending on the UE capabilities.

[0041] In L1-RSRP reporting, the absolute value / difference value of L1-RSRP may be used as in Rel. 15 / 16 / 17.

[0042] In L1-RSRP reporting, the reported L1-RSRP value is defined as a 7-bit value in the range of [-140 to -44] dBm with a step size of 1 dB.

[0043] Here, the maximum measured value of L1-RSRP is quantized to a 7-bit value in the range of [-140 to -44] dBm with a step size of 1 dB. Also, the difference value of L1-RSRP is quantized to a 4-bit value.

[0044] The difference value is calculated with a step size of 2 dB, referencing the largest measurement that is part of the same L1-RSRP reporting instance.

[0045] The L1-RSRP report includes the SSBRI between the configured candidate cells. In other words, the L1-RSRP report includes the SSBRI of the configured candidate cells and the corresponding L1-RSRP. The format may be the same as the existing specification.

[0046] In this disclosure, the beam report of Rel. 18 may also be referred to as a type 2-2 beam report or a beam report for cell switching. Note that the type 2-2 beam report does not include PCI information (PCI ID). Instead, the SSBRI may include PCI information. For example, if four cells have 64 SSBs, the SSBRI will be one of {0, 1, ..., 255}.

[0047] (UE-initiated Beam Report (UEIBR)) In future wireless communication systems (e.g., Rel. 19 and beyond), support for event-based beam reporting is being considered. Event-based beam reporting may also be called event-triggered beam reporting, or UE-initiated beam reporting (UEIBR).

[0048] Beam management (UEIBM) initiated by UEIBR / UE can be used for measurement reporting, beam switching, cell switching, etc.

[0049] At UEIBR, the report content is being considered to include at least one of the following pieces of information in the beam report: • Beam / reference signal index (e.g., CSI-RS / SSB resource index / indicator). • Measurement result (e.g., L1-RSRP / SINR (absolute / relative)). • Number of beams / RSs reported. • Whether or not serving beams are included in the beam report.

[0050] Regarding the reported beam / RS number information, the base station / network and the UE need to have a common understanding of the size of the beam report (e.g., UCI), so it is preferable that this information is included in the beam report reported by the UE.

[0051] In this case, the UCI may be reported in two parts. For example, the size of the UCI transmitted in the second part (step), which may be a fixed size, may indicate the size of the UCI transmitted in the second part (step).

[0052] In this case, the UCI may be encoded in two parts. For example, the size of the second part of the UCI may be indicated by the first part of the UCI (which may have a fixed size).

[0053] Events related to UEIBR (the events mentioned above) may be broadly categorized into the following event types: • Event 1: The quality of the current beam falls below a certain threshold. • Event 2: The quality of at least one new beam (e.g., L1-RSRP) is better than a certain threshold compared to the quality of the current beam. • Event 3: The quality of a new beam is better than a certain threshold. • Event 4: The quality of the current beam falls below a first threshold, and the quality of at least one new beam is better than a second threshold. • Event 5: The absolute difference between the quality of the current beam and the quality of at least one new beam falls below a certain threshold. • Event 6: The current beam is no longer included in the best K beams (more than 1: K > 1) (of the beams set up for measurement / reporting). - Event 7: The quality of at least one new beam (e.g., L1-RSRP) is above the threshold of the RS derived from the best quality activated TCI state up to the Mth (M is 1 or greater, and M may be set by RRC). - Event 8: The quality of M (more than 1: M > 1) new beams (e.g., L1-RSRP) is above the threshold of the current beam. - Event 9: The quality of at least one new beam (e.g., L1-RSRP) is above the threshold of the set reference RS (which may be SSB / CSI-RS).

[0054] Note that this type of event does not exclude the events described above. For example, this type of event may be interpreted as equivalent to the events described above as appropriate.

[0055] Furthermore, at least two of the above events may be combined and defined.

[0056] (UCI-based UEIBR) In UCI-based UEIBR procedures, the following modes may be supported:

[0057] <<Mode A>> Mode A relates to the dynamic scheduling of UCI by NW (gNB). That is, in Mode A, resources for UCI are scheduled by gNB. Mode A may be a basic function of the UE (a UE that supports UEIBR may naturally support this function).

[0058] Step 1: The UE transmits a first UL channel (e.g., PUCCH). The first UL channel is a UL channel that pre-notifies / requests a second UL channel (e.g., PUCCH) for transmitting beam reports, and may consist of one or more bits.

[0059] Step 2: The UE detects the DCI format indicating the second UL channel resource.

[0060] Step 3: The UE transmits the beam report using the resource (UCI) on the second UL channel.

[0061] In mode A, a 1-bit instruction in at least the first UL channel (PUCCH) may be supported to request resources on the second UL channel for transmitting beam reports.

[0062] In this case, periodic PUCCH resources (PUCCH format 0 / 1) can be set up by dedicated upper-layer signaling.

[0063] <<Mode B>> Mode B relates to the UCI in the pre-configured resources for the second UL channel.

[0064] Step 1: The UE transmits a first UL channel (e.g., PUCCH). The first UL channel is a UL channel that notifies a second UL channel for transmitting beam reports, and may consist of one or more bits.

[0065] Step 2: The UE transmits a beam report on the second UL channel (for example, using a specific resource (UCI) within the channel).

[0066] Note that the notification in Step 1 may be included in a separate reporting instance from the beam report in Step 2.

[0067] In mode B, a one-bit instruction on at least the first UL channel (PUCCH) may be supported to indicate that the second UL channel will transmit a beam report.

[0068] In this case, periodic PUCCH resources (PUCCH format 0 / 1) can be set up by dedicated upper-layer signaling.

[0069] In either mode A or B as described above, cross-CC (component carrier) beam reporting may be supported.

[0070] The pre-configured resource for the second UL channel in step 2 of mode B may be at least a CG PUSCH (e.g., type 1 CG PUSCH).

[0071] The CG PUSCH may transmit UL data (UL-SCH) and beam reports.

[0072] Furthermore, the CG PUSCH may be a dedicated CG PUSCH for transmitting beam reports (it does not need to transmit UL data / other UCI).

[0073] Furthermore, the use of PUCCH and PUSCH with / without UL data is being considered as the second UL channel.

[0074] (CSI Trigger State) Figure 2 is a diagram showing an example of a trigger state indication. In this disclosure, the terms trigger state, CSI trigger state, and CSI report trigger state may be interpreted interchangeably.

[0075] The trigger state (the trigger for CSI reporting) is initiated using the CSI request field in the DCI. If all bits [values] of the CSI request field in the DCI are set to 0, it may mean that no CSI is requested.

[0076] The number of CSI trigger states set in the upper layer parameter CSI-AperiodicTriggerStateList is 2 Ｎ ＴＳIf it is greater than -1, the UE may receive a sub-selection instruction. The sub-selection instruction (e.g., MAC CE) may be used to map up to 2 Ｎ ＴＳ -1 trigger states to the code point of the CSI request field in the DCI.

[0077] That is, when the number of configured trigger states is greater than 2 Ｎ ＴＳ -1, it may be used to activate up to 2 Ｎ ＴＳ trigger states for further DCI indication by the CSI request field.

[0078] Here, N ＴＳ may represent the number of bits of the CSI request field. The CSI request field is variably configured with 0 to 6 bits and is determined by the upper layer parameter reportTriggerSize.

[0079] The number of trigger states is at most 2 Ｎ ＴＳ -1, and each trigger state may correspond to the code point of the CSI request field in the DCI.

[0080] Each trigger state may include a plurality (e.g., at most 16) of reporting configurations (CSI-ReportConfig).

[0081] (Analysis) By the way, in the UE-initiated / event-driven beam reporting (i.e., UEIBR), at least one of the following options may be supported as an extension of the L1-RSRP reporting format in response to event 2.

[0082] ((Option 1)) For each of the reported CRI / SSBRI, an additional indication field indicating whether the CRI / SSBRI satisfies the condition of event 2 may be introduced.

[0083] The presence of the field may be enabled by RRC according to the UE capabilities.

[0084] Alternatively, the field may only exist if a value of N greater than 1, a time window, and a value of M are set.

[0085] ((Option 2)) For each reported CRI / SSBRI, an additional instruction field may be introduced indicating the number of Event 2 instances for the CRI / SSBRI within a given time window.

[0086] The existence of the field may be activated by RRC in accordance with UE capabilities.

[0087] Alternatively, the field may only exist if a value of N greater than 1, a time window, and a value of M are set.

[0088] ((Option 3)) No further extensions apply.

[0089] For example, in a Mode A UEIB, there is room for further consideration of the processing behavior / method when the UE is not transmitting on the first UL channel (PUCCH).

[0090] Furthermore, the UEIBR reporting procedure considers at least one of the following cases regarding the 1-bit multiplexing / dropping rule for the first UL channel.

[0091] (Case 1) When one bit of the first UL channel collides with / overlaps with the PUCCH carrying the normal SR / LRR.

[0092] (Case 2) When one bit of the first UL channel collides with / overlaps with PUSCH.

[0093] (Case 3) When one bit of [multiple] first UL channels corresponding to different UEIB reporting settings collide / overlap in a certain time domain.

[0094] Furthermore, in the UEIBR reporting procedure, at least one of the following options has been considered regarding the trigger procedure for step 2 of mode A:

[0095] (Option 1) The CSI trigger state is a trigger state (setting) exclusive to the UEIBR and is not associated with existing reporting settings (aperiodic).

[0096] (Option 2) The CSI trigger state is associated with one of the following reporting settings: - Reporting settings for UEIBR only. - Existing aperiodic [CSI] reporting settings only. - Both UEIBR and existing aperiodic [CSI] reporting settings.

[0097] As mentioned above, if option 1 is supported, the CSI trigger status can be set to "UEIBR only" and "Report".

[0098] This CSI trigger state can only trigger the corresponding UEIBR.

[0099] If Option 2 is supported, the CSI trigger state may be associated with the UEIBR reporting settings and existing non-periodic [CSI] reporting settings.

[0100] The following issues may arise here: • It is unclear how reporting settings for UEIBR and existing [aperiodic] reporting settings relate to CSI trigger states. • It is unclear how to handle cases where a single CSI trigger state is associated with multiple reporting settings (reporting settings for UEIBR and existing [aperiodic] reporting settings).

[0101] Thus, there is room for further investigation into the correspondence between CSI trigger states and reporting settings. If these are not clearly defined, it may be impossible to achieve lower latency communication, potentially hindering improvements in communication quality and throughput.

[0102] Therefore, the inventors of this invention conceived a way to solve these problems.

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

[0104] (Various substitutions) In this disclosure, words enclosed in parentheses () may indicate an explanation of the preceding word (e.g., an explanation of spelling), a paraphrase, a specific example, or supplementary explanation. Also, in this disclosure, words enclosed in square brackets [] may be interpreted as part of the overall meaning of the text, or they may be interpreted as being excluded (ignored). Note that parentheses () and square brackets [] may be used for purposes / meanings other than those described above.

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

[0106] In this disclosure, terms such as notice, activate, deactivate, indicate (or specify), select, configure, update, and determine may be interpreted interchangeably. In this disclosure, terms such as support, control, controllable, operate, and capable of operating may be interpreted interchangeably.

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

[0108] In this disclosure, the upper layer signaling may be any or a combination thereof, such as Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information, and other messages (e.g., messages from the core network, such as positioning protocol messages (e.g., NR Positioning Protocol A (NRPPPa) / LTE Positioning Protocol (LPP)) messages).

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

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

[0111] In this disclosure, terms such as drop, suspend, cancel, puncture, rate match, postpone, and not send may be interpreted interchangeably.

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

[0113] In this disclosure, the terms used include: panel, UE panel, panel group, beam, beam group, precoder, Uplink (UL) transmit entity, Transmission / Reception Point (TRP), base station, Spatial Relation Information (SRI), spatial relationship, SRS Resource Indicator (SRI), Control Resource Set (CORESET), Physical Downlink Shared Channel (PDSCH), Codeword (CW), Transport Block (TB), Reference Signal (RS), Antenna port (e.g., Demodulation Reference Signal (DMRS) port), Antenna port group (e.g., DMRS port group), Group (e.g., Spatial relationship group, Code Division Multiplexing (CDM) group, Reference Signal group, CORESET group, Physical Uplink Control The following terms may be interchangeable: Channel (PUCCH) group, PUCCH resource group), resource (e.g., reference signal resource, SRS resource), resource set (e.g., reference signal resource set), CORESET pool, downlink Transmission Configuration Indication state (TCI state) (DL TCI state), uplink TCI state (UL TCI state), unified TCI state, common TCI state, quasi-co-location (QCL), QCL assumption, etc.

[0114] In this disclosure, base station, gNB, and network (NW) may be interpreted as interchangeable.

[0115] In this disclosure, cell group, serving cell group, master cell group (MCG), and secondary cell group (SCG) may be interpreted interchangeably. L1 / L2, L1 / L2 signaling, and DCI / MAC CE may be interpreted interchangeably. A serving cell may be replaced with a cell that transmits PDSCH. A candidate cell may mean a candidate cell that becomes a serving cell through L1 / L2 inter-cell mobility. L1 / L2-triggered mobility (LTM) and L1 / L2 inter-cell mobility may be interpreted interchangeably.

[0116] In this disclosure, cell, PCI, serving cell, source serving cell, source cell, CC, BWP, BWP within CC, and band may be interpreted interchangeably. In this disclosure, cell, PCI, cell with additional PCI, additional cell, other cell, non-serving cell, cell with a different PCI, candidate cell, candidate serving cell, cell with a PCI different from the current serving cell's PCI, another serving cell, and target cell may be interpreted interchangeably. A target cell may be a cell selected from among several candidate cells. In this disclosure, switch, change, and update may be interpreted interchangeably. A serving cell may be interpreted as a serving cell before a switch or a serving cell after a switch.

[0117] In this disclosure, event-based beam reporting, event-triggered beam reporting, event-driven beam reporting, UE-triggered beam reporting, UE-initiated beam reporting, event-triggered reporting / measurement, and UE-initiated beam management (UEIBM) are interchangeable.

[0118] In this disclosure, event-triggered [beam] reports may be interpreted interchangeably with beam reports, CSI reports, L1-RSRP beam reports, and L1-SINR beam reports. These reports may also be simply referred to as reports.

[0119] In this disclosure, the CSI report and the CSI report for LTMs Rel. 18 may be interpreted as mutually interchangeable.

[0120] In this disclosure, beam report, UEIBR, UEIBR report, and simply report may be interpreted interchangeably.

[0121] In this disclosure, the Type 1 beam report and the beam report for in-cell beam switching may be interpreted as interchangeable.

[0122] In this disclosure, Type 2 beam reporting and inter-cell beam reporting may be interpreted interchangeably.

[0123] In this disclosure, the type 2-1 beam report and the beam report for inter-cell beam switching may be interpreted as interchangeable.

[0124] In this disclosure, the Type 2-2 beam report and the beam report for cell switching may be interpreted as interchangeable.

[0125] In this disclosure, tables, mappings, associations, lists, formats, content, reports, etc., may be interpreted interchangeably.

[0126] In this disclosure, the (new) MAC CE, UCI, cell switching command, beam switching command, MAC CE for beam reporting, and MAC CE for cell switching may be interpreted as interchangeable.

[0127] In this disclosure, event-based beam reporting may be reported using PUSCH (e.g., config-grant PUSCH, grant-based PUSCH). That is, the reporting content in this disclosure may be transmitted using at least one of MAC CE / UCI / PUCCH / PUSCH.

[0128] In this disclosure, "report," "reporting resources," and "resources" may be interpreted interchangeably. For example, the first resource and the first report may be interpreted interchangeably, and the second resource and the second report may be interpreted interchangeably.

[0129] In this disclosure, the number of beams and the number of resources may be interpreted interchangeably.

[0130] In this disclosure, ACK may be referred to as an affirmative response and NACK as a negative response. In this disclosure, NACK may be information indicating a first value (e.g., 0 (or 1)), and ACK may be information indicating a second value (e.g., 1 (or 0)).

[0131] In this disclosure, "Serving" may be interpreted as "Serving beam," "Serving cell," or "SpCell."

[0132] In this disclosure, "Neighbor" may be interpreted as any beam or cell other than a serving beam / serving cell / SpCell / SCell.

[0133] In this disclosure, the RS index and the L1-RSRP / SINR pair may be referred to as the L1 measurement report. That is, the L1 measurement report may include the RS index and the L1-RSRP / SINR pair.

[0134] In this disclosure, candidate cells, target cells, adjacent cells, cells, etc., may be interpreted interchangeably.

[0135] In this disclosure, the phrases "an event occurred" and "the conditions for the event were met" may be interpreted interchangeably.

[0136] In this disclosure, the beam, RS, and [L1 / L3] measurement results may be interpreted interchangeably.

[0137] In this disclosure, the measured RS may be the QCL source RS in an active TCI state / indicated TCI state.

[0138] In this disclosure, spatial domain filters, temporal domain filters, and domain filters may be interpreted as interchangeable.

[0139] In this disclosure, NW / BS / gNB may be interpreted as interchangeable.

[0140] In this disclosure, the current beam / new beam may correspond to at least one of the following: indicated TCI state, indicated TCI state, active TCI state, activated TCI state, set TCI state, and RS set in RRC.

[0141] In this disclosure, indicated TCI state, active TCI state, activated TCI state, set TCI state, configured TCI state, and RS configured in RRC may be interpreted interchangeably.

[0142] In this disclosure, the number of current beams / new beams may be one or more.

[0143] In this disclosure, the terms "new beam / RS," "candidate beam / RS," "measurement beam / RS," "beam for measurement / RS," etc., may be interpreted interchangeably.

[0144] In this disclosure, a novel type of UCI (novel UCI) may mean a UCI that is transmitted in multiple bits (and multiple steps / parts).

[0145] Each embodiment of this disclosure is applicable to any event.

[0146] In this disclosure, L1-RSRP may be interpreted as L1-SINR.

[0147] In this disclosure, conditions and thresholds may be interpreted interchangeably.

[0148] In this disclosure, the filtered value (measured value: L1-RSRP), the filtered value, and the L1-RSRP to which filtering by NW settings has been applied (NW-filtered L1-RSRP) may be interpreted interchangeably.

[0149] In this disclosure, Mode A and Mode B may be interpreted as interchangeable.

[0150] In this disclosure, CC, carrier, cell, serving cell, frequency, frequency carrier, carrier frequency, etc., may be interpreted interchangeably. In this disclosure, reporting of multiple CCs may be interpreted interchangeably with reporting of multiple events.

[0151] In this disclosure, UCI and MAC CE may be interpreted as containers used in UEIBR interchangeably.

[0152] In this disclosure, reporting of a (current / measured) beam may mean reporting of the RS index (e.g., CSI-RS resource indicator (CRI) / SSB resource indicator (SSBRI)) and measurement results (e.g., L1-RSRP / RSRQ / SINR) corresponding to the (current / measured) beam. In this disclosure, information about a beam may mean the RS index / measurement results corresponding to the beam.

[0153] In this disclosure, “current beam” may mean “current beam of the current serving cell” in mobility.

[0154] In this disclosure, beam, RS, RS resource, RS resource set, RS index, RS indicator, RS ID, etc. may be interpreted interchangeably. In this disclosure, RS resource set, subset of RS resource, subset of RS, etc. may be interpreted interchangeably.

[0155] In this disclosure, the type of CSI reporting may be periodic, semi-persistent, or aperiodic. In other words, this disclosure is applicable to any type of CSI reporting.

[0156] In this disclosure, multiplexing (to multiplex / to be multiplexed) and mapping (to map / to be mapped) may be interpreted interchangeably.

[0157] In this disclosure, the UL channel for transmitting UEIBR-CSI, CG PUSCH, type 1 CG PUSCH, type 2 CG PUSCH, DG PUSCH, and PUSCH may be interpreted as being interchangeable.

[0158] In this disclosure, other UL channels, PUCCH, and PUSCH [for transmitting other UCIs] may be interpreted as interchangeable.

[0159] In this disclosure, steps 2 and 3 in mode A may be collectively referred to as step 2. That is, steps 2 and 3 in mode A may be interpreted as interchangeable.

[0160] In this disclosure, the multiple events may be any of the events described above (or a combination of multiple events).

[0161] In this disclosure, Mode A and Mode B may be interpreted as interchangeable. Step 1 in Mode A / Mode B may be interpreted as interchangeable. Step 3 in Mode A and Step 2 in Mode B may be interpreted as interchangeable.

[0162] A specific channel may be PUSCH / PUCCH, and a specific signal may be SRS. However, the specific channel / signal may be any other channel / signal.

[0163] In this disclosure, the first UL channel may be a PUCCH that notifies / requests the second UL channel, and the second UL channel may be, for example, a DG / CG PUCCH.

[0164] In this disclosure, the DCI, the first DL signal, and the ACK for the first UL channel in step 2 may be interpreted as being interchangeable.

[0165] In this disclosure, [New] UCI, UCI for UEIBR, Second UL Channel, and PUSCH may be interpreted interchangeably.

[0166] (Wireless communication method) The UE may perform / control measurements / reports by applying the provisions described herein (the various provisions described above and the embodiments described below). The NW / BS / gNB may provide / transmit to the UE settings / instructions etc. for the UE to implement such control. Furthermore, the NW / BS / gNB may perform various controls necessary to receive such reports (beam reports / CSI reports) from the UE.

[0167] This disclosure is applicable to various MIMO / mobility use cases.

[0168] In this disclosure, each embodiment / option may be applied individually or in combination with others.

[0169] In this disclosure, CSI-RS and SSB may be interpreted interchangeably.

[0170] In this disclosure, the terms resource, resource set, and resource list may be interpreted interchangeably.

[0171] In this disclosure, the channel measurement resource, the interference measurement resource, and the resource may be interpreted as interchangeable.

[0172] In this disclosure, the terms "criteria" and "condition / requirement" may be interpreted interchangeably.

[0173] In this disclosure, CSI acquisition, CSI measurement, and CSI reporting may be interpreted interchangeably.

[0174] This disclosure clarifies the correspondence between the CSI trigger state for the UEIBR and the reporting settings. Based on this correspondence, the UE can appropriately control the UEIBR. As a result, lower latency communication can be achieved, and communication quality / throughput can be improved.

[0175] <First Embodiment> The first embodiment relates to the correspondence between reporting settings and CSI trigger states.

[0176] <<Aspect 1-0>> Aspect 1-0 relates to an example in which reporting settings for UEIBR and existing aperiodic CSI reporting settings are associated within a single CSI trigger state.

[0177] As mentioned above, the UE can be configured with settings related to the CSI trigger state (e.g., CSI-AperiodicTriggerStateList).

[0178] Additionally, the trigger state (the trigger for CSI reporting) may be initiated (instructed) using the CSI request field within the DCI.

[0179] In addition, the UE may receive sub-selection instructions (e.g., MAC CE) depending on the number of CSI trigger states that are set.

[0180] The following explains the correspondence between reporting settings and CSI trigger states, using Alt1 to Alt4 as examples. The UE may determine / decide the CSI trigger state based on at least one of the following options.

[0181] (Alt1) Figure 3 is a diagram showing an example of the correspondence between the reporting settings and the CSI trigger state related to Alt1 in Embodiment 1-0.

[0182] A single CSI trigger state may be associated with both a periodic CSI reporting setting and a reporting setting for the UEIBR.

[0183] As shown in Figure 3, the higher-layer parameter (CSI-AperiodicTriggerStateList) for a list of aperiodic CSI trigger states may include multiple (e.g., up to 128) aperiodic CSI trigger states (CSI-AperiodicTriggerState).

[0184] Each CSI trigger state may include an associated report configuration information list (associatedReportConfigInfoList).

[0185] Each report configuration information list (which may also be called an associated report configuration information list) may contain multiple (e.g., up to 16) reports configurations [information] (CSI-AssociatedReportConfigInfo). Multiple reports configurations (which may also be called CSI-associated report configuration information) may contain existing reports configuration [ID] and reports configuration [ID] for UEIBR.

[0186] For example, a list of related reporting configuration information may include one or more existing reporting configuration IDs and one or more reporting configuration IDs for UEIBR. Reporting configuration IDs may be denoted as reportConfigId, CSI-ReportConfigId, etc.

[0187] Furthermore, the list of reporting settings may include multiple reporting settings (for example, up to 48). Each reporting setting may include parameters such as a reporting setting ID (reportConfigId), carrier, resources for channel measurement (resourcesForChannelMeasurement), CSI-IM resources for interference (csi-IM-ResourcesForInterference), NZP-CSI-RS resources for interference (nzp-CSI-RS-ResourcesForInterference), and reporting setting type (reportConfigType).

[0188] The reporting setting type may be selectable from options such as periodic / semi-persistent / aperiodic / UEIBR, etc.

[0189] Furthermore, the settings for UEIBR may include event-related settings and other parameters.

[0190] As shown in Figure 3, the related reporting setting information list (CSI trigger status) and the CSI reporting setting list may be associated. Furthermore, the CSI related reporting setting information in the related reporting setting information list and the CSI reporting settings in the CSI reporting setting list may be associated according to the type of reporting setting.

[0191] In other words, reporting settings for UEIBR may be associated with an existing list of aperiodic trigger states. Furthermore, both an existing aperiodic reporting setting and a reporting setting for UEIBR may be associated with a single trigger state simultaneously.

[0192] (Alt2) Figure 4 shows an example of the correspondence between the reporting settings and the CSI trigger state related to Alt2 in Embodiment 1-0.

[0193] A single CSI trigger state may be associated only with a non-periodic CSI reporting setting, or only with a reporting setting for the UEIBR.

[0194] As shown in Figure 4, the higher-layer parameter (CSI-AperiodicTriggerStateList) for a list of aperiodic CSI trigger states may include multiple (e.g., up to 128) aperiodic CSI trigger states (CSI-AperiodicTriggerState).

[0195] Each CSI trigger state may include an associated report configuration information list (associatedReportConfigInfoList).

[0196] Each report configuration information list (which may also be called an associated report configuration information list) may contain multiple (e.g., up to 16) reports configurations [information] (CSI-AssociatedReportConfigInfo). Multiple reports configurations (which may also be called CSI-associated report configuration information) may contain existing reports configuration [ID] and reports configuration [ID] for UEIBR.

[0197] For example, a single related reporting settings list may contain only one of either existing reporting settings IDs or reporting settings IDs for UEIBR. More specifically, a single related reporting settings list may contain only one or more existing reporting settings IDs. Another related reporting settings list may contain only one or more reporting settings IDs for UEIBR.

[0198] Furthermore, the list of reporting settings may include multiple reporting settings (for example, up to 48). Each reporting setting may include parameters such as a reporting setting ID (reportConfigId), carrier, resources for channel measurement (resourcesForChannelMeasurement), CSI-IM resources for interference (csi-IM-ResourcesForInterference), NZP-CSI-RS resources for interference (nzp-CSI-RS-ResourcesForInterference), and reporting setting type (reportConfigType).

[0199] The reporting setting type may be selectable from options such as periodic / semi-persistent / aperiodic / UEIBR, etc.

[0200] Furthermore, the settings for UEIBR may include event-related settings and other parameters.

[0201] As shown in Figure 4, the related reporting setting information list (CSI trigger status) and the CSI reporting setting list may be associated. Furthermore, the CSI related reporting setting information in the related reporting setting information list and the CSI reporting settings in the CSI reporting setting list may be associated according to the type of reporting setting.

[0202] In other words, reporting settings for UEIBR may be associated with an existing list of aperiodic trigger states. Furthermore, only existing aperiodic reporting settings or only reporting settings for UEIBR may be associated with a single trigger state.

[0203] ((Variation)) The related reporting settings information list may not be in list format, but may consist of (or be replaced by) specialized parameters specifically designed to instruct the UEIBR. This allows the UE to determine which reporting settings to use without associating trigger conditions with reporting settings.

[0204] Reporting settings for UEIBR may be included in an existing reporting settings list or in a new reporting settings list specifically for UEIBR.

[0205] (Alt3) Figure 5 is a diagram showing an example of the correspondence between the reporting settings and the CSI trigger state related to Alt3 in Embodiment 1-0.

[0206] One trigger state may be associated with a non-periodic CSI reporting setting / reporting setting for UEIBR.

[0207] As shown in Figure 5, the higher-layer parameter (CSI-AperiodicTriggerStateList) for a list of aperiodic CSI trigger states may include multiple (e.g., up to 128) aperiodic CSI trigger states (CSI-AperiodicTriggerState).

[0208] The CSI trigger state may include an associated report configuration information list (associatedReportConfigInfoList).

[0209] Each report configuration information list (which may also be called an associated report configuration information list) may contain multiple (for example, up to 16) report configurations [information] (CSI-AssociatedReportConfigInfo). Multiple report configurations (which may also be called CSI-associated report configuration information) may contain existing report configuration [IDs].

[0210] For example, a list of related reporting configuration information may contain one or more existing reporting configuration IDs. Reporting configuration IDs may be denoted as reportConfigId, CSI-ReportConfigId, etc.

[0211] Additionally, a certain CSI trigger state may include a report setting [ID] for the UEIBR as related report setting information for the UEIBR (UEI-AssociatedReportConfigInfo-r19), separate from the related report setting information list.

[0212] A single CSI trigger state may include associated reporting configuration information (UEI-AssociatedReportConfigInfo-r19) for one or more UEIBRs.

[0213] In other words, the reporting settings for UEIBR (UEI-AssociatedReportConfigInfo-r19 / UEI-CSI-ReportConfigId-r19) may be included directly in the CSI trigger state rather than being included in the related reporting settings information list.

[0214] Furthermore, existing reporting settings and reporting settings for UEIBR may be defined / configured separately. For example, an existing reporting settings list may contain multiple reporting settings (e.g., up to 48). Each reporting setting may include parameters such as a reporting setting ID (reportConfigId), carrier, resources for channel measurement (resourcesForChannelMeasurement), CSI-IM resources for interference (csi-IM-ResourcesForInterference), NZP-CSI-RS resources for interference (nzp-CSI-RS-ResourcesForInterference), and reporting setting type (reportConfigType).

[0215] The reporting setting type may be selectable from options such as periodic, semi-persistent, or aperiodic.

[0216] A reporting settings list for UEIBR may contain multiple (e.g., up to N) reporting settings for UEIBR.

[0217] Each reporting configuration may include parameters such as a reporting configuration ID (reportConfigId), carrier, resources for channel measurement (resourcesForChannelMeasurement), reporting configuration type (reportConfigType), event-related settings, and other parameters.

[0218] As shown in Figure 5, the related reporting setting information list (CSI trigger state) and the CSI reporting setting list may be associated. Furthermore, in existing non-periodic CSI reporting settings, the CSI related reporting setting information in the related reporting setting information list and the CSI reporting settings in the CSI reporting setting list may be associated.

[0219] Furthermore, in the reporting settings for UEIBR, the CSI trigger state and the UEIBR reporting settings list may be associated. More specifically, the UEIBR reporting settings within the CSI trigger state and the UEIBR reporting settings within the UEIBR reporting settings list may be associated.

[0220] In other words, reporting settings for UEIBR may be associated with an existing list of aperiodic trigger states. Furthermore, existing aperiodic reporting settings and reporting settings for UEIBR may be associated with a single trigger state simultaneously or individually.

[0221] (Alt4) Figure 6 shows an example of the correspondence between the reporting settings and CSI trigger status related to Alt4 in Embodiment 1-0.

[0222] One trigger state may be associated with a non-periodic CSI reporting setting / reporting setting for UEIBR.

[0223] For example, the list of trigger states may be configured separately in the non-periodic CSI reporting settings / UEIBR reporting settings.

[0224] As shown in Figure 6, the higher-layer parameter (CSI-AperiodicTriggerStateList) for a list of aperiodic CSI trigger states may include multiple (e.g., up to 128) aperiodic CSI trigger states (CSI-AperiodicTriggerState).

[0225] Similarly, a higher-layer parameter (CSI-UEIBRTriggerStateList) relating to a list of CSI trigger states for a UEIBR may include multiple (e.g., up to N) CSI trigger states (CSI-UEIBRTriggerState) for a UEIBR.

[0226] Each non-periodic CSI trigger state may include an associated report configuration information list (associatedReportConfigInfoList).

[0227] Each report configuration information list (which may also be called an associated report configuration information list) may contain multiple (for example, up to 16) report configurations [information] (CSI-AssociatedReportConfigInfo). Multiple report configurations (which may also be called CSI-associated report configuration information) may contain existing report configuration [IDs].

[0228] For example, a list of related reporting configuration information may contain one or more existing reporting configuration IDs. Reporting configuration IDs may be denoted as reportConfigId, CSI-ReportConfigId, etc.

[0229] Each CSI trigger state for a UEIBR may include one or more reporting configurations [IDs] for the UEIBR. The reporting configuration ID may be denoted as reportConfigId, CSI-ReportConfigId, etc.

[0230] Furthermore, the list of reporting settings may include multiple reporting settings (for example, up to 48). Each reporting setting may include parameters such as a reporting setting ID (reportConfigId), carrier, resources for channel measurement (resourcesForChannelMeasurement), CSI-IM resources for interference (csi-IM-ResourcesForInterference), NZP-CSI-RS resources for interference (nzp-CSI-RS-ResourcesForInterference), and reporting setting type (reportConfigType).

[0231] The reporting setting type may be selectable from options such as periodic / semi-persistent / aperiodic / UEIBR, etc.

[0232] Furthermore, the settings for UEIBR may include event-related settings and other parameters.

[0233] As shown in Figure 6, the CSI trigger status list for UEIBR and the CSI reporting settings [list] may be associated. Furthermore, the CSI-related reporting setting information in the CSI trigger status list for UEIBR and the CSI reporting settings for UEIBR in the CSI reporting settings list may be associated.

[0234] In other words, reporting settings for UEIBR may be associated with an existing list of aperiodic trigger states. Furthermore, both an existing aperiodic reporting setting and a reporting setting for UEIBR may be associated with a single trigger state simultaneously.

[0235] In Alt4, at least one of the following options may be applied:

[0236] ((Opt1)) An existing CSI request field may trigger either an existing aperiodic CSI report or a UEIBR.

[0237] Whether an existing CSI request field indicates an existing aperiodic trigger state or a trigger state for the UEIBR may depend on whether a first UL channel (PUCCH) is transmitted.

[0238] In other words, the content (list) indicated by the CSI request field may be switched depending on whether or not the first UL channel is transmitted.

[0239] For example, when a first UL channel is transmitted, the CSI request field may indicate one or more CSI trigger states in the CSI-UEIBRTriggerStateList.

[0240] Otherwise (if the first UL channel is not transmitted), the CSI request field may indicate one or more CSI trigger states in the CSI-AperiodicTriggerStateList.

[0241] The CSI request field value [for UEIBR] may consist of a code point indicating a single trigger state, or a bitmap indicating one trigger state / multiple trigger states simultaneously.

[0242] ((Opt2)) In DCI / MAC CE, a new CSI request field for UEIBR may be introduced / defined.

[0243] A new CSI request field [value] may trigger a UEIBR. That is, the CSI trigger state for a UEIBR may be indicated by a new CSI request field.

[0244] For example, DCI may include an existing CSI request field that indicates an existing non-periodic trigger state and a new CSI request field (a field dedicated to UEIBR) that indicates a trigger state for UEIBR. MAC CE may also include a sub-selection instruction [field] for the CSI trigger state for UEIBR.

[0245] ((Opt3)) Existing CSI request fields and CSI request fields for UEIBR may be combined. For example, the same fields may be used for CSI request fields in DCI for both existing CSI reporting and UEIBR.

[0246] The CSI trigger state for UEIBR may be indicated by a combination of existing CSI request fields, CSI request fields for UEIBR, and special fields. For example, the same CSI request field may be used for both existing CSI reporting and UEIBR in the DCI. In this case, the CSI trigger state for UEIBR may be indicated by a combination of existing CSI request fields and special fields. This makes it possible to indicate the CSI trigger state for UEIBR by simply adding special fields while utilizing existing CSI request fields.

[0247] For example, the content (list) indicated by the CSI request field may be switched based on the content of a special field within the DCI.

[0248] When a certain CSI trigger condition is indicated, either a non-periodic CSI report or a UEIBR may be triggered.

[0249] More specifically, if DCI includes a special field indicating a request for the UEIBR, the CSI request field may indicate an element (one or more trigger states) in the trigger state list for the UEIBR (CSI-UEIBRTriggerStateList).

[0250] <<Aspect 1-1>> Aspect 1-1 relates to the content of the CSI report.

[0251] As mentioned above, the handling of cases where a single CSI trigger state is associated with multiple reporting settings (reporting settings for UEIBR and existing [aperiodic] reporting settings) is unclear.

[0252] For example, in this case, depending on the implementation, the CSI trigger state can simultaneously trigger both the UEIBR and existing aperiodic CSI reporting.

[0253] Furthermore, if an existing CSI request field is reused for UEIBR (i.e., if an existing CSI request field triggers UEIBR), the DCI containing that CSI request field can simultaneously trigger both UEIBR and the existing aperiodic CSI reporting.

[0254] On the other hand, in the specific case of the above-described embodiment 1-0, even if the UE triggers both reports, there may be cases where the NW does not necessarily need both reports. In such cases, sending unnecessary report content can become a source of overhead.

[0255] Therefore, I propose the following:

[0256] With respect to the reporting content included in the second UL channel (PUSCH), if: • A single CSI trigger state is associated with multiple reporting settings (reporting settings for UEIBR and existing [non-periodic] reporting settings), or • An existing CSI request field is reused for UEIBR (if an existing CSI request field triggers UEIBR), then at least one of the following options may apply. That is, if at least one of the above conditions is satisfied, the UE may control / determine / generate reporting content according to at least one of the following options.

[0257] (Alt1) The UE may send only reports intended for the UEIBR to the second UL channel. That is, the UE may drop aperiodic CSI reports. Content intended for the UEIBR can be further classified as follows: (Alt1-a): May include all reports for the UEIBR. (Alt1-b): May include only one report for the UEIBR. (Alt1-c): May include X reports for the UEIBR.

[0258] The value of X may be predefined by the specification, set / instructed by upper-layer signaling / physical-layer signaling, or determined according to UE capabilities. Furthermore, if X = 0, it may mean that the corresponding report (UEIBR) is not triggered.

[0259] (Alt2) The UE may transmit only existing non-periodic CSI reports to the second UL channel. In other words, the UE may drop the UEIBR report.

[0260] (Alt3) UE may transmit both reports for UEIBR and existing aperiodic CSI reports to the second UL channel.

[0261] (Alt4) Whether the second UL channel includes reports for the UEIBR / existing aperiodic CSI reports may be determined / switched by signaling from the NW (upper layer signaling RRC / MAC CE) / physical layer signaling (DCI)). For example, at least one of the following options may be applied.

[0262] ((Opt1)) The UE may send only reports for the UEIBR to the second UL channel. That is, the UE may drop aperiodic CSI reports. Content for the UEIBR can be further classified as follows: (Opt1-a): All reports for the UEIBR may be included. (Opt1-b): Only one report for the UEIBR may be included. (Opt1-c): X reports for the UEIBR may be included.

[0263] The value of X may be predefined by the specification, set / instructed by upper-layer signaling / physical-layer signaling, or determined according to UE capabilities. Furthermore, if X = 0, it may mean that the corresponding report (UEIBR) is not triggered.

[0264] ((Opt2)) The UE may transmit only existing non-periodic CSI reports to the second UL channel. In other words, the UE may drop the UEIBR reports.

[0265] ((Opt3)) UE may transmit both reports for UEIBR and existing aperiodic CSI reports to the second UL channel.

[0266] In Alt4, the signaling from the network for the UE to determine the reported content may follow at least the following options:

[0267] ((Alt4-1)) A new indicator (single-bit / multi-bit) within DCI.

[0268] ((Alt4-2)) Special bit allocation within DCI.

[0269] ((Alt4-3)) A new MAC CE. In this case, a new MAC CE for UEIBR may include at least one of the following pieces of information: - An indicator (single bit / multi-bit) that points to the reporting content (for UEIBR / existing aperiodic CSI reporting / both). - Serving cell ID. - BWP ID.

[0270] ((Alt4-4)) No signaling (UE / NW may implicitly decide which option to apply).

[0271] In this way, by determining / switching the reporting content according to the reporting type, it is possible to reduce the overhead associated with the second UL channel.

[0272] (Specific Example #1) The specific example of Alt4-4 mentioned above will be explained as follows.

[0273] <<Possible Cases>> The following cases can be exemplified regarding the retransmission process of UEIBR.

[0274] (Alt1) Alt1 relates to the case in which the UE cannot correctly receive the first DL signal (DCI). In this case, it can be further classified into the following cases. Figures 7A and 7B show examples of assumed cases (Alt1-1 / 1-2) for the UEIBR in embodiment 1-1, respectively.

[0275] ((Alt1-1)) Case where the UE retransmits the first UL channel (PUCCH) (see Figure 7A).

[0276] ((Alt1-2)) Case where the UE does not retransmit the first UL channel (PUCCH) (see Figure 7B).

[0277] Furthermore, when transmitting the first UL channel, the UE may start a timer / window for detecting the first DL signal (DCI). If the UE fails to correctly decode the DCI within that timer / window, the UE may detect that it failed to correctly receive the first DL signal.

[0278] Furthermore, if DCI retransmission is applied due to the gNB implementation, the UEIBR procedure corresponding to the same event may be continued.

[0279] (Alt2) Alt2 concerns the case in which the UE cannot correctly receive the second UL channel (PUSCH). In this case, it can be further classified into the following cases. Figures 8A and 8B show examples of assumed cases (Alt2-1 / 2-2) for the UEIBR of embodiment 1-1, respectively.

[0280] ((Alt2-1)) Case where the UE retransmits the first UL channel (PUCCH) (see Figure 8A).

[0281] ((Alt2-2)) Case where the UE retransmits the second UL channel (PUSCH) (see Figure 8B). In this case, the retransmission of the second UL channel may be scheduled by the retransmitted first DL signal.

[0282] Furthermore, if the UE does not receive an ACK from the NW (is not transmitted from the NW) within a predetermined period (timer / window), it may detect that it failed to properly receive the second UL channel.

[0283] <<Implicit derivation method for conditions (which option to apply)>> For example, if the UE transmits the first UL channel before receiving the first DL signal, the UE may transmit the report content for the UEIBR on the second UL channel (CSI report).

[0284] Alternatively, in this case, UE may send the reporting content for both the UEIBR and the existing non-periodic CSI reports to the second UL channel (CSI reporting).

[0285] Otherwise (if the UE has not transmitted the first UL channel before receiving the first DL signal), the UE may transmit only the content intended for existing aperiodic CSI reports on the scheduled second UL channel.

[0286] At least one of the following options may be applied as a process to determine whether the UE transmitted the first UL channel before receiving the first DL signal. Figures 9 to 10 show examples of determining whether the first UL channel was transmitted in response to channel / signal retransmission according to embodiment 1-1. Figures 9A and 9B show an example of a case in which the UE cannot correctly receive the first DL signal, and Figures 10A and 10B show an example of a case in which the NW cannot correctly receive the second UL channel.

[0287] ((Alt1)) When a UE transmits the first UL channel, the UE may start a timer / window for that determination. In this case, the UE may consider (determine) that the first UL channel has been transmitted until the timer / window expires.

[0288] ((Alt2)) The UE may perform a check [for determining whether to transmit the first UL channel] for a predetermined period (X slots / subframes / milliseconds) before receiving the first DL signal. If the first UL channel is transmitted within that predetermined period, the UE may consider (determine) that it transmitted the first UL channel before receiving the first DL signal.

[0289] ((Alt3)) After transmitting the first UL channel, the UE may maintain the state that "the UE has transmitted the first UL channel" (which may also be called a specific state). Furthermore, the UE may release the specific state if at least one of the following conditions (which may also be called cancellation conditions) is satisfied.

[0290] <Condition #1> When a specific timer / window expires. This timer / window may be instructed / specified as the period for maintaining the specific state described above.

[0291] <Condition #2> When the UE receives the first DL signal. Even if a specific state is canceled, if the UE receives a first DL signal (DCI) in which the NDI (new data indicator) field is set to "No" and the HARQ process ID associated with the previous (past) first UL channel is set, the UE may consider (determine) that it transmitted the first UL channel before receiving the first DL signal.

[0292] <Condition #3> When the UE transmits on the second UL channel.

[0293] <Condition #4> When the UE receives an ACK (or any information equivalent to an ACK) for the second UL channel.

[0294] Furthermore, if the network misidentifies the first UL channel, further consideration is needed regarding error detection. For example, if the network expects a UEIB to be transmitted, but the UE transmits an existing aperiodic CSI report, the network may determine that it has misidentified the first UL channel based on the received report content.

[0295] In other words, if the report includes content that differs from what the network expects, the network may conclude that it has misidentified the first UL channel.

[0296] The above-mentioned options may be combined in any way. Figures 11 to 13 show the UEIBR related to the modified version.

[0297] (Specific example #2) The following can be given as an example of Alt4 signaling.

[0298] ((Alt4-1)) A new indicator (single-bit / multi-bit) within DCI.

[0299] In the case of a single bit, the new indicator may instruct the inclusion of a UEIBR in the second UL channel, or to include a periodic CSI report within the scheduled PUSCH.

[0300] In the case of multi-bit, the new indicator may instruct the second UL channel to include the UEIBR / existing aperiodic CSI report. Specifically, the new indicator may instruct at least one of the following:

[0301] - Include only UEIBR in the second UL channel (in this case, existing aperiodic CSI reports will be dropped). - Include only existing aperiodic CSI reports in the second UL channel (in this case, UEIBR will be dropped). - Include both UEIBR and existing aperiodic CSI reports in the second UL channel.

[0302] Furthermore, the new indicator may include a field indicating the number of UEIBR / existing CSI reports included in the second UL channel (X = 0, 1, 2..., or any integer).

[0303] ((Another example of Alt4-1)) The new indicators described above may indicate that the CSI request field is associated with a specific CSI trigger state (for UEIBR / for existing aperiodic CSI reporting).

[0304] In the case of a single bit, the new indicator may indicate that the CSI request field is associated with a CSI trigger state for UEIBR, or that the CSI request field is associated with a CSI trigger state for an existing aperiodic CSI report.

[0305] In the case of multi-bit, the new indicator may indicate that the CSI request field is associated with a specific CSI trigger state (for UEIBR / for existing aperiodic CSI reporting). Specifically, the new indicator may indicate at least one of the following:

[0306] - The CSI request field is associated with the CSI trigger state for UEIBR (in this case, the existing CSI trigger state for aperiodic CSI reporting is ignored). - The CSI request field is associated with the existing CSI trigger state for aperiodic CSI reporting (in this case, the CSI trigger state for UEIBR is ignored). - The CSI request field is associated with the CSI trigger state for UEIBR / the existing CSI trigger state for aperiodic CSI reporting.

[0307] Furthermore, the new indicator may include a field indicating the number of UEIBR / existing CSI reports included in the second UL channel (X = 0, 1, 2..., or any integer).

[0308] ((Alt4-2)) The new indicators described above can be applied to Alt4-2 by interpreting them as special fields.

[0309] ((Alt4-3)) The new indicators mentioned above can be applied to Alt4-3 by substituting the new MAC CE.

[0310] ((Alt4-4)) If the first UL channel is transmitted, the UE may include only content for the UEIBR in the second UL channel, or it may include both content for the UEIBR and content for existing aperiodic CSI reports.

[0311] Otherwise (if the first UL channel is not being transmitted), the UE may include only content for existing aperiodic CSI reports in the scheduled PUSCH.

[0312] ((Another example of Alt4-4)) When the first UL channel is transmitted, the CSI request field may be associated only with the CSI trigger state for the UEIBR, or it may be associated with the CSI trigger state for both the UEIBR and existing aperiodic CSI reports.

[0313] Otherwise (if the first UL channel is not being transmitted), the CSI request field may only be associated with the CSI trigger state for existing aperiodic CSI reports.

[0314] According to this embodiment, the correspondence between reporting settings and CSI trigger states becomes clear, and the UE can appropriately determine, judge, and control the reporting content to be included in the second UL channel.

[0315] <Supplement> <<Notification of Information to UE>> In the embodiments described above, notification of any information from the Network (NW) (e.g., Base Station (BS)) to the UE (in other words, reception of any information from the BS at the UE) may 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 signal), or a combination thereof.

[0316] If the above notification is made by a MAC CE, the MAC CE may be identified by the inclusion of a new Logical Channel ID (LCID) not defined in existing standards in the MAC subheader.

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

[0318] Furthermore, the notification of arbitrary information to the UE in the above-described embodiment may be periodic, semi-persistent, or aperiodic.

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

[0320] If the above notification is made by a MAC CE, the MAC CE may be identified by the inclusion of a new LCID not specified in existing standards in the MAC subheader.

[0321] If the above notice is made by the UCI, the notice may be transmitted using PUCCH or PUSCH.

[0322] Furthermore, the notification of any information from the UE in the above-described embodiment may be periodic, semi-persistent, or aperiodic.

[0323] <<Regarding the Application of Each Embodiment>> In UE / BS, specific (one or more) processes / operations / controls / assumptions / information for at least one of the embodiments described above may be applied (or used) if any or more of the following conditions are met: - A higher-layer parameter indicating the specific process / operation / control / assumption / information is set. - The specific process / operation / control / assumption / information is determined based on the relevant higher-layer parameter. - The specific process / operation / control / assumption / information is designated / activated / triggered by MAC CE / DCI / UCI / Resource / Channel / RS. - A specific UE capability indicating (or related to) the specific process / operation / control / assumption / information is reported or supported. - The application of the specific process / operation / control / assumption / information is determined based on specific conditions.

[0324] The above-mentioned specific UE capabilities may include at least one of the following: - Supporting specific processing / operations / controls / information for at least one of the above embodiments; - Supporting MIMO / mobility Rel. 19 or later; - Supporting UEIBR Rel. 19 or later, and related settings / operations.

[0325] Furthermore, the above-mentioned specific UE capability may be a capability that applies across all frequencies (commonly regardless of frequency), a capability per frequency (e.g., one or a combination thereof, such as cell, band, band combination, BWP, component carrier, etc.), a capability per frequency range (e.g., Frequency Range 1 (FR1), FR2, FR3, FR4, FR5, FR2-1, FR2-2), a capability per subcarrier spacing (SCS), or a capability per feature set (FS) or feature set per component-carrier (FSPC).

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

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

[0328] (Note) The following inventions are added with respect to one embodiment of the present disclosure. [Note 1] A terminal having: a receiving unit that receives a setting relating to a channel status information (CSI) trigger state and downlink control information (DCI) including a CSI request field indicating the CSI trigger state; and a control unit that controls a periodic CSI report or a beam report (UEIBR) initiated by a terminal based on the CSI trigger state, wherein the control unit determines the CSI trigger state based on the correspondence between the setting and the CSI trigger state. [Note 2] The terminal according to Note 1, wherein the CSI trigger state is associated with a periodic CSI report setting or a report setting for the UEIBR. [Note 3] The terminal according to Note 1 or Note 2, wherein, if one CSI trigger state is associated with multiple reporting settings and the CSI request field is used for the UEIBR, the control unit determines, based on specific conditions, the reporting content to be included in the uplink shared channel (PUSCH) scheduled by the DCI. [Note 4] The terminal according to any one of Notes 1 to 3, wherein the control unit includes either aperiodic CSI reporting or reporting for the UEIBR, or both, the aperiodic CSI reporting and reporting for the UEIBR in the PUSCH.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0343] In the wireless communication system 1, an orthogonal frequency division multiplexing (OFDM)-based wireless access scheme may be used. For example, Cyclic Prefix OFDM (CP-OFDM), Discrete Fourier Transform Spread OFDM (DFT-s-OFDM), Orthogonal Frequency Division Multiple Access (OFDMA), Single Carrier Frequency Division Multiple Access (SC-OFDM), etc., may be used in at least one of the downlink (DL) and uplink (UL).

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

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

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

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

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

[0349] Furthermore, the DCI that schedules PDSCH may be called DL assignment, DL DCI, etc., and the DCI that schedules PUSCH may be called UL grant, UL DCI, etc. Furthermore, PDSCH may be read as DL data, and PUSCH may be read as UL data.

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

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

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

[0353] In this disclosure, downlinks, uplinks, etc., may be expressed without the prefix "link." Also, the prefix "physical" may be omitted from the names of various channels.

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

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

[0356] Furthermore, in the wireless communication system 1, the uplink reference signal (UL-RS) may include a sounding reference signal (SRS), a demodulation reference signal (DMRS), etc. The DMRS may also be called a user-specific reference signal (UE-specific Reference Signal).

[0357] (Base Station) Figure 15 shows an example of the configuration of a base station according to one embodiment. The base station 10 includes a control unit 110, a transmitting / receiving unit 120, a transmitting / receiving antenna 130, and a transmission line interface 140. Note that one or more of the control unit 110, the transmitting / receiving unit 120, the transmitting / receiving antenna 130, and the transmission line interface 140 may be provided.

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

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

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

[0361] The transmitting / receiving unit 120 may include a baseband unit 121, a radio frequency (RF) unit 122, and a measurement unit 123. The baseband unit 121 may include a transmission processing unit 1211 and a reception processing unit 1212. The transmitting / receiving unit 120 can be composed of a transmitter / receiver, RF circuit, baseband circuit, filter, phase shifter, measurement circuit, transmitting / receiving circuit, etc., as described based on common understanding in the art relating to this disclosure.

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

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

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

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

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

[0367] The transmitting / receiving unit 120 (transmission processing unit 1211) may perform transmission processing on the bit sequence to be transmitted, such as channel coding (which may include error correction coding), modulation, mapping, filtering, discrete Fourier transform (DFT) processing (if necessary), inverse fast Fourier transform (IFFT) processing, precoding, and digital-to-analog conversion, and output a baseband signal.

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

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

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

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

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

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

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

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

[0376] The transmitting / receiving unit 120 may transmit settings related to the channel status information (CSI) trigger state and downlink control information (DCI) including a CSI request field indicating the CSI trigger state. The control unit 110 may control the reception of aperiodic CSI reports transmitted from the terminal or beam reports (UEIBR) initiated by the terminal, based on the CSI trigger state. The control unit 110 may control the generation of the settings and the DCI for the terminal to determine the CSI trigger state, based on the correspondence between the settings and the CSI trigger state.

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

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

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

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

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

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

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

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

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

[0386] The transmitting / receiving unit 220 (transmission processing unit 2211) may perform PDCP layer processing, RLC layer processing (e.g., RLC retransmission control), MAC layer processing (e.g., HARQ retransmission control), etc., on data and control information acquired from the control unit 210 to generate a bit sequence to be transmitted.

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

[0388] Whether or not to apply DFT processing may be based on the transform precoding settings. The transmitting / receiving unit 220 (transmission processing unit 2211) may perform DFT processing as part of the transmission process to transmit a channel (for example, PUSCH) using a DFT-s-OFDM waveform if transform precoding is enabled for that channel, or it may not perform DFT processing as part of the transmission process if transform precoding is not enabled for that channel.

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

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

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

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

[0393] The measurement unit 223 may derive channel measurements for CSI calculation based on channel measurement resources. Channel measurement resources may be, for example, Non Zero Power (NZP) CSI-RS resources. The measurement unit 223 may also derive interference measurements for CSI calculation based on interference measurement resources. Interference measurement resources may be at least one of the following: NZP CSI-RS resources for interference measurement, CSI-Interference Measurement (IM) resources, etc. CSI-IM may also be called CSI-Interference Management (IM), and may be interpreted interchangeably with Zero Power (ZP) CSI-RS. In this disclosure, CSI-RS, NZP CSI-RS, ZP CSI-RS, CSI-IM, CSI-SSB, etc., may be interpreted interchangeably.

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

[0395] The control unit 210 may perform at least a part of the processing of the control unit as described above.

[0396] The transmitting / receiving unit 220 may perform at least a part of the processing of the transmitting / receiving unit as described above.

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

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

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

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

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

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

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

[0404] Furthermore, the processor 1001 reads programs (program code), software modules, data, etc., from at least one of the storage 1003 and the communication device 1004 into the memory 1002 and executes various processes accordingly. The program used is one that causes the computer to execute at least a part of the operations described in the above embodiment. For example, the control unit 110 (210) may be implemented by a control program stored in the memory 1002 and running on the processor 1001, and other functional blocks may be implemented similarly.

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

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

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

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

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

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

[0411] Furthermore, devices included in the core network 30 (for example, network nodes that provide NF) may also be implemented using the functional block / hardware configuration described above.

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

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

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

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

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

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

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

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

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

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

[0422] A TTI with a time length of 1 ms may be called a normal TTI, long TTI, normal subframe, long subframe, slot, etc. A TTI shorter than a normal TTI may be called a shortened TTI, short TTI, partial or fractional TTI, shortened subframe, short subframe, mini slot, sub slot, slot, etc.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0437] Any information described in this disclosure (e.g., variables, constants, parameters) may be communicated from any first device (e.g., UE / base station) to any second device (e.g., base station / UE) that indicates / specifies (or relates to) the value of such any information, even if not specifically stated in the embodiments described above.

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

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

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

[0441] The determination may be made based on a value represented by 1 bit (either 0 or 1), or may be made based on a boolean value represented by true or false, or may be made by comparing numerical values (for example, comparison with a predetermined value).

[0442] Software should be broadly interpreted to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, functions, etc., regardless of whether it is called software, firmware, middleware, microcode, a hardware description language, or another name.

[0443] Also, software, instructions, information, etc. may be transmitted and received via a transmission medium. For example, when software is transmitted from a website, server, or other remote source using at least one of wired technologies (such as coaxial cables, optical fiber cables, twisted pairs, Digital Subscriber Line (DSL), etc.) and wireless technologies (such as infrared rays, microwaves, etc.), at least one of these wired and wireless technologies is included within the definition of the transmission medium.

[0444] The terms "system" and "network" used in this disclosure may be used interchangeably. "Network" may mean the devices (such as base stations) included in the network.

[0445] In this disclosure, terms such as “precoding,” “precoder,” “weight (precoding weight),” “quasi-co-location (QCL),” “transmission configuration indication state (TCI state),” “spatial relation,” “spatial domain filter,” “transmit power,” “phase rotation,” “antenna port,” “layer,” “number of layers,” “rank,” “resource,” “resource set,” “beam,” “beam width,” “beam angle,” “antenna,” “antenna element,” “panel,” “UE panel,” “transmitting entity,” and “receiving entity” may be used interchangeably.

[0446] In this disclosure, "antenna port" may be interpreted interchangeably with "antenna port for any signal / channel" (e.g., a Demodulation Reference Signal (DMRS) port). In this disclosure, "resource" may be interpreted interchangeably with "resource for any signal / channel" (e.g., a reference signal resource, an SRS resource, etc.). Resources may include time / frequency / code / spatial / power resources. Furthermore, a spatial domain transmit filter may include at least one of a spatial domain transmit filter and a spatial domain receive filter.

[0447] The above group may include, for example, at least one of the following: a spatial relationship group, a code division multiplexing (CDM) group, a reference signal (RS) group, a control resource set (CORESET) group, a PUCCH group, an antenna port group (e.g., a DMRS port group), a layer group, a resource group, a beam group, an antenna group, or a panel group.

[0448] Also, in the present disclosure, a beam, an SRS resource indicator (SRS Resource Indicator (SRI)), a CORESET, a CORESET pool, a PDSCH, a PUSCH, a codeword (Codeword (CW)), a transport block (Transport Block (TB)), an RS, etc. may be read as each other.

[0449] Also, in the present disclosure, a TCI state, a downlink TCI state (DL TCI state), an uplink TCI state (UL TCI state), a unified TCI state, a common TCI state, a joint TCI state, etc. may be read as each other.

[0450] Also, in the present disclosure, "QCL", "QCL assumption", "QCL relationship", "QCL type information", "QCL property / properties", "characteristics of a specific QCL type (e.g., type A, type D)", "a specific QCL type (e.g., type A, type D)", etc. may be read as each other.

[0451] In the present disclosure, an index, an identifier (Identifier (ID)), an indicator, an indication, a resource ID, etc. may be read as each other. In the present disclosure, a sequence, a list, a set, a group, a cluster, a subset, etc. may be read as each other.

[0452] Also, the spatial relationship information Identifier (ID) (TCI state ID) and the spatial relationship information (TCI state) may be read as each other. "Spatial relationship information (TCI state)" may be read as "set of spatial relationship information (TCI state)", "one or more pieces of spatial relationship information", etc. The TCI state and TCI may be read as each other. The spatial relationship information and the spatial relationship may be read as each other.

[0453] In this disclosure, terms such as “Base Station (BS),” “wireless base station,” “fixed station,” “NodeB,” “eNB (eNodeB),” “gNB (gNodeB),” “access point,” “Transmission Point (TP),” “Reception Point (RP),” “Transmission / Reception Point (TRP),” “panel,” “cell,” “sector,” “cell group,” “carrier,” and “component carrier” may be used interchangeably. Base stations may also be referred to by terms such as macrocell, small cell, femtocell, and picocell.

[0454] A base station may house one or more (e.g., three) cells. If a base station houses multiple cells, the entire coverage area of ​​the base station may be divided into several smaller areas, each of which may also be provided with communication services by a base station subsystem (e.g., a small indoor base station (Remote Radio Head (RRH))). The terms “cell” or “sector” refer to part or all of the coverage area of ​​at least one of the base station and / or base station subsystems that provide communication services in that coverage.

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

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

[0457] A mobile station may also be called a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or some other appropriate term.

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

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

[0460] The mobile entity may be a vehicle (e.g., a car, an airplane), an unmanned mobile entity (e.g., a drone, an autonomous vehicle), or a robot (manned or unmanned). At least one of the base station and the mobile station may be a device that does not necessarily move during communication operations. For example, at least one of the base station and the mobile station may be an Internet of Things (IoT) device such as a sensor.

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

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

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

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

[0465] The information service unit 59 consists of various devices for providing (outputting) various types of information such as driving information, traffic information, and entertainment information, including a car navigation system, audio system, speakers, display, television, and radio, and one or more ECUs that control these devices. The information service unit 59 uses information acquired from external devices via a communication module 60 or the like to provide various types of information / services (for example, multimedia information / multimedia services) to the occupants of the vehicle 40.

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

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

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

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

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

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

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

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

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

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

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

[0477] Each aspect / embodiment described in this disclosure is Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 6th generation mobile communication system (6G), xth generation mobile communication system (xG (where x is, for example, an integer or decimal)), Future Radio Access (FRA), New-Radio Access Technology (RAT), New Radio (NR), New radio access (NX), Future generation radio access (FX), Global System for Mobile communications (GSM®), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi®), IEEE 802.16 (WiMAX®), IEEE 802.20, systems utilizing Ultra-WideBand (UWB), Bluetooth®, or other appropriate wireless communication methods, and next-generation systems extended, modified, created, or defined based thereon may also be applied. Furthermore, multiple systems may be applied in combination (for example, a combination of LTE or LTE-A and 5G).

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

[0479] Any reference to an element using designations such as "first", "second", etc. used in this disclosure does not generally limit the quantity or order of those elements. These designations can be used in this disclosure as a convenient way to distinguish between two or more elements. Thus, a reference to a first and a second element does not mean that only two elements can be employed or that the first element must precede the second element in some form.

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

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

[0482] Furthermore, “judgment (decision)” may be considered as “judgment (decision)” of resolving, selecting, choosing, establishing, comparing, etc. In other words, “judgment (decision)” may be considered as “judgment (decision)” of some action. In this disclosure, “judgment (decision)” may be interpreted as mutually interchangeable with the actions described above.

[0483] Furthermore, in this disclosure, “determine / determining” may be interpreted as “assume / assuming,” “expect / expecting,” or “consider / considering.” In addition, in this disclosure, “not expecting to do…” may be interpreted as “expecting not to do….”

[0484] In this disclosure, "expect" may be rephrased as "be expected." For example, "expect(s) ..." (where "..." may be expressed as a that clause, an infinitive, etc.) may be rephrased as "be expected ..." or "do (the verb without "to" if "..." is an infinitive)." Similarly, "does not expect ..." may be rephrased as "be not expected ..." or "do not (the verb without "to" if "..." is an infinitive)." Furthermore, "An apparatus A is not expected ..." may be rephrased as "An apparatus B other than apparatus A does not expect ... from apparatus A" (for example, if apparatus A is a UE, apparatus B may be a base station).

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

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

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

[0488] In this disclosure, the term "A and B are different" may mean "A and B are different from each other." The term may also mean "A and B are each different from C." Terms such as "separate" and "combine" may be interpreted similarly to "different."

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

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

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

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

[0493] In this disclosure, phrases such as "when A, B", "if A, then B", "B upon A", "B in response to A", "B based on A", "B during / while A", "B before A", "B at (the same time as) / on A", "B after A", "B since A", and "B until A" may be interchangeable. Furthermore, A, B, etc., may be replaced with appropriate expressions such as nouns, gerunds, or regular sentences depending on the context. The time difference between A and B may be approximately zero (immediately after or immediately before). Additionally, a time offset may be applied to the time when A occurs. For example, "A" may be interpreted as "before / after the time offset when A occurs". The time offset (e.g., one or more symbols / slots) may be predetermined or determined by the UE based on notified information.

[0494] In this disclosure, timing, time, duration, time instance, any unit of time (e.g., slot, subslot, symbol, subframe), period, occasion, resource, etc., may be interpreted interchangeably.

[0495] Although the invention described herein has been explained in detail above, it will be clear to those skilled in the art that the invention described herein is not limited to the embodiments described herein. The descriptions herein are illustrative and not intended to be restrictive in any way to the invention described herein.

[0496] This application is based on Japanese Patent Application No. 2024-230865, filed on December 26, 2024. All of its contents are included here.

Claims

A receiving unit that receives settings related to the channel status information (CSI) trigger state and downlink control information (DCI) including a CSI request field that indicates the CSI trigger state, The system includes a control unit that controls a non-periodic CSI report or a beam report (UEIBR) initiated by a terminal, based on the CSI trigger state, The control unit is a terminal that determines the CSI trigger state based on the correspondence between the setting and the CSI trigger state. 　 The terminal according to claim 1, wherein the CSI trigger state is associated with a non-periodic CSI reporting setting or a reporting setting for the UEIBR. 　 The terminal according to claim 1, wherein, if one CSI trigger state is associated with multiple reporting settings and the CSI request field is used for the UEIBR, the control unit determines, based on specific conditions, the reporting content to be included in the uplink shared channel (PUSCH) scheduled by the DCI. 　 The terminal according to claim 1, wherein the control unit includes either a periodic CSI report or a report to the UEIBR, or both the periodic CSI report and the report to the UEIBR, to the PUSCH. 　 The steps include receiving a setting related to the channel status information (CSI) trigger state and downlink control information (DCI) including a CSI request field that indicates the CSI trigger state, The process includes the step of controlling a non-periodic CSI report or a beam report (UEIBR) initiated by a terminal based on the CSI trigger state, A wireless communication method for a terminal that determines the CSI trigger state based on the correspondence between the setting and the CSI trigger state. 　 A transmission unit that transmits settings related to the channel status information (CSI) trigger state and downlink control information (DCI) including a CSI request field that indicates the CSI trigger state, The system includes a control unit that controls the reception of non-periodic CSI reports transmitted from a terminal or beam reports (UEIBR) initiated by a terminal, based on the CSI trigger state, The control unit is a base station that controls the setting and the generation of the DCI for the terminal to determine the CSI trigger state, based on the correspondence between the setting and the CSI trigger state.

Images