Terminal, radio communication method, and base station

Abstract

To improve communication quality / throughput.SOLUTION: A terminal according to an aspect of the present disclosure has: a receiving section that receives settings of a beam report started by the terminal; and a control section that determines the time period of occupation of a channel state information (CSI) processing unit for the beam report, on the basis of at least one of a physical uplink control channel (PUCCH) triggering the beam report, a physical uplink shared channel (PUSCH) carrying the beam report, one channel measurement resource in one or more channel measurement resources for measurement of the beam report, and signaling for the beam report.SELECTED DRAWING: Figure 8

Description

[Technical Field]

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

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

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

[0004] [Non-Patent Document 1] 3GPP TS 36.300 V8.12.0 “Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 (Release 8)”, April 2010 Summary of the Invention [Problem to be solved by the invention]

[0005] In existing wireless communication systems (e.g., NR), a terminal (user terminal, User Equipment (UE)) reports channel state information (CSI) to a network (NW, base station), so that the NW can apply appropriate modulation and coding to downlink (DL) data.

[0006] However, the occupancy period of the CSI processing unit (CPU) for UE-initiated beam reporting (UEIBR) has not been sufficiently considered, which may result in a degradation of communication performance / throughput.

[0007] Therefore, one object of the present disclosure is to provide a terminal, a wireless communication method, and a base station that can improve communication performance / throughput. [Means for solving the problem]

[0008] A terminal according to one embodiment of the present disclosure includes a receiving unit that receives a beam report configuration initiated by the terminal, and a control unit that determines a time period for occupancy of a channel state information (CSI) processing unit for the beam report based on at least one of a physical uplink control channel (PUCCH) that triggers the beam report, a physical uplink shared channel (PUSCH) that carries the beam report, one channel measurement resource among one or more channel measurement resources for measuring the beam report, and signaling for the beam report. [Effects of the Invention]

[0009] According to one aspect of the present disclosure, communication quality / throughput can be improved. [Brief explanation of the drawings]

[0010] [Figure 1]FIG. 1 shows an example of a CPU occupation time period. [Figure 2] 2A and 2B show another example of a CPU occupation time period. [Figure 3] 3A and 3B show an example of CSI reference resources and UE CSI calculation times. [Figure 4] FIG. 4 shows an example of UE CSI calculation time for AP CSI reporting. [Figure 5] FIG. 5 shows an example of Table C-1 for CSI calculation delay requirement 1. [Figure 6] FIG. 6 shows an example of Table C-2 for CSI calculation delay requirement 2. [Figure 7] 7A and 7B show an example of a CPU occupancy period for AP CSI reporting. [Figure 8] 8A and 8B show an example of a CPU occupation time period when an event condition is satisfied in the first embodiment. [Figure 9] FIG. 9 shows an example of a CPU occupation time period when the event conditions are not satisfied in the first embodiment. [Figure 10] FIG. 10 shows an example of a CPU occupation time period when an event condition is satisfied in the second embodiment. [Figure 11] FIG. 11 shows an example of a CPU occupation time period according to a variation of the second embodiment. [Figure 12] FIG. 12 shows an example of a CPU occupation time period when an event condition is satisfied in the third embodiment. [Figure 13] FIG. 13 is a diagram illustrating an example of a schematic configuration of a wireless communication system according to an embodiment of the present disclosure. [Figure 14] FIG. 14 is a diagram illustrating an example of a configuration of a base station according to an embodiment of the present disclosure. [Figure 15] FIG. 15 is a diagram illustrating an example of a configuration of a terminal according to an embodiment of the present disclosure. [Figure 16] FIG. 16 is a diagram illustrating an example of a hardware configuration of a base station and a terminal according to an embodiment of the present disclosure.

Embodiments for Implementing the Invention

[0011] (Type of Beam Report) <Intra-Cell Beam Report in Rel.15 / 16> In Rel.15 / 16, intra-cell beam reporting is supported. For example, the L1-RSRP / SINR report can be configured by upper layer signaling (RRC).

[0012] For example, in the calculation of L1-RSRP, if the resource is associated with QCL type C / type D, either or both of the CSI-RS resource and the SS / PBCH block resource can be configured for the UE.

[0013] Also, the UE can be configured with up to 16 CSI-RS resource sets each having up to 64 resources within each set. In all resource sets, the total number of different CSI-RS resources is 128 or less.

[0014] In the L1-RSRP report, when the upper layer parameter nrofReportedRS (e.g., within CSI-ReportConfig) is set to 1, the reported L1-RSRP value is defined as a 7-bit value in the range of [-140~-44] dBm with a step size of 1 dB.

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

[0016] The difference value is calculated with a step size of 2 dB by referring to the maximum measured value that is part of the same L1-RSRP report instance.

[0017] For example, in L1-SINR calculation and channel measurement, the UE may be configured with either or both of the NZP CSI-RS resource and the SS / PBCH block resource. Also, for interference measurement, the UE may be configured with the NZP CSI-RS resource or the CSI-IM resource.

[0018] For channel measurement, the UE may be configured with CSI resource settings related to up to 64 CSI resources or up to 16 CSI-RS resource sets with SS / PBCH block resources.

[0019] In L1-SINR reporting, when 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~40] dBm with a step size of 0.5 dB.

[0020] When the upper layer parameter nrofReportedRS is set greater than 1 or the upper layer parameter groupBasedBeamReporting is set to "enabled", the UE uses the differential value-based L1-SINR value for reporting.

[0021] The differential value is calculated with a step size of 1 dB by referring to the maximum measured value that is part of the same L1-SINR reporting instance.

[0022] In the present disclosure, the in-cell beam reporting of Rel.15 / 16 (which may also be simply referred to as in-cell beam reporting) may be called type 1 beam reporting (beam reporting type 1) or beam reporting for in-cell beam switching.

[0023] <Inter-cell beam reporting in Rel.17> As described above, in Rel.17, mobility between L1 / L2 cells is supported. For example, the UE can transmit and receive UL / DL channels / signals between the PCI of a cell different from that of the serving cell. For example, when a non-serving cell has a larger RSRP than the serving cell, the UE can transmit and receive UL / DL channels / signals with the non-serving cell without performing a handover.

[0024] In L1-RSRP reporting, the absolute value / difference value of L1-RSRP may be used as in Rel.15 / 16. In inter-cell beam reporting in Rel.17 (type 2-1 beam reporting 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 / indicated by upper layer signaling / physical layer signaling.

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

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

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

[0028] <Inter-cell beam reporting in Rel.18> Furthermore, only SSB-based L1-RSRP reporting (beam reporting) is supported for beam reporting in Rel. 18. Here, the number of candidate cells L may be any value between 1 and 4, and the number of beams M per cell may be any value between 1 and 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 remaining L1-RSRP values ​​are reported as differential values.

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

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

[0031] In the L1-RSRP report, 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.

[0032] 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, and the differential value of L1-RSRP is quantized to a 4-bit value.

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

[0034] The L1-RSRP report includes the SSBRI between the configured candidate cells. That is, the L1-RSRP report includes the SSBRI of the configured candidate cells and the corresponding L1-RSRP. The format may be the same as that of the existing specifications.

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

[0036] (Event-triggered Beam Report / UE-initiated Beam Report (UEIBR)) It is being considered that future wireless communication systems (e.g., Rel. 19 and later) will support event-based beam reporting, which may also be called event-triggered beam reporting or UE-initiated beam reporting (UEIBR).

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

[0038] <Applicable cases> The UEIBR may be applied, for example, in at least one of the following cases 1 and 2: Case 1: L1-RSRP / SINR beam reporting with serving cell PCI / additional PCI (e.g., L1-RSRP / SINR beam reporting with serving cell / additional PCI cells for Rel. 18 L1 / L2 mobility with L1 / L2 inter-cell mobility / intra-cell multi-TRP (M-TRP inter-cell) / cell switching). · Case 2: L1-RSRP / SINR beam reporting including only serving cell PCI.

[0039] When a specific event occurs (in the present disclosure, it may be read as when specific conditions are satisfied / not satisfied, when it conforms to a specific event, etc.), the UE may report measurement results (for example, at least L1-RSRP / L1-SINR and corresponding resource indicators / RS indexes) to the NW.

[0040] The specific event may be at least one of, for example, an event related to at least one of the serving cell and additional cells, and an event related to beam reporting including at least one of the PCI of the serving cell and the PCI of the additional cells.

[0041] <Trigger Conditions / Events for UEIBR for Rel.19> UEIBR may be triggered when a certain condition (event) is satisfied. For example, the UE may apply different / same conditions / events for triggering the following beam reports.

[0042] · UE Feature #1: UEIBR for Rel.19 MIMO. · UE Feature #2: UEIBR for Rel.19 Mobility.

[0043] Different UE capabilities may be introduced / defined between UE Feature #1 and #2. Also, different upper layer parameters may be set to enable each UE feature. UE features and UE capabilities may be read as each other.

[0044] The UE does not expect UE Feature #1 and #2 to be set simultaneously in a certain BWP / CC / band / frequency band / frequency (or for each UE).

[0045] The UE may simultaneously set UE features #1 and #2 at a certain BWP / CC / band / frequency band / frequency (or for each UE). For example, if set, the UE may pre-define which event (which UE feature) to prioritize, or it may be set / instructed by upper layer signaling / physical layer signaling.

[0046] This disclosure may be applied in the unified TCI framework.

[0047] This disclosure may be applied only when the corresponding UE capabilities are reported. Alternatively, this disclosure may be applied only when the corresponding upper layer parameters (e.g., RRC) are notified / reported.

[0048] <UE IBR for MIMO> Regarding the UE IBR for MIMO in Rel.19, the following may apply.

[0049] · MAC CE in PUSCH. · UCI in periodic / semi-persistent PUCCH, UCI in dynamic grant (DG) / configured grant (CG) PUSCH. · The relationship between the above MAC CE-based method and UCI-based method. For example, two independent methods may be configurable. Alternatively, the UCI-based method may be applicable in addition to the MAC CE-based method (a combination of two methods (2-step method) may be applied).

[0050] The content of the report may basically be the same as the existing L1 beam measurement report, and may include, for example, at least one of the following. · SSBRI / CRI. · The number of beams X reported. · The selection method of X beams. · L1-RSRP / SINR (absolute value / difference value) for each SSBRI / CRI. When MAC CE is used, An indicator of whether the next octet is included. If MAC CE / UCI is used, Serving cell ID, BWP ID (if the report requires activation of TCI state or beam switching).

[0051] Events related to UEIBR for MIMO may be broadly categorized into the following event types: Event 1: The quality of the current beam becomes worse than a certain threshold. Event 2: The quality of at least one new beam (e.g., L1-RSRP) becomes better than a certain threshold compared to the quality of the current beam. Event 3: The quality of the new beam is better than a certain threshold. Event 4: The quality of the current beam becomes worse than a first threshold and the quality of at least one new beam becomes better than a second threshold. Event 5: The absolute value of the 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 among the best K (more than 1: K>1) beams (among those configured for measurement / reporting). Event 7: The quality of at least one new beam (e.g. L1-RSRP) becomes better than the quality of the Qth (Q may be M, Q or M may be greater than or equal to 1, Q or M may be configured by RRC (based on UE capability reporting)) RS derived from the activated (active) TCI state by more than a threshold. Event 8: The quality (e.g., L1-RSRP) of M (more than 1: M>1) new beams becomes better than the current beam by more than a threshold. Event 9: The quality of at least one new beam (e.g. L1-RSRP) becomes better than the configured reference RS (which may be SSB / CSI-RS) by more than a threshold.

[0052] It should be noted that the events exemplified in this manner do not exclude other events.

[0053] Priorities may be defined for events 1 to 9. For example, among events 1 to 9, a specific event (e.g., event 2) may have the highest priority (e.g., event 2 may be determined to take precedence).

[0054] For example, in event 2, the current beam may be determined / derived based on the QCL RS (e.g., QCL source RS) in the indicated TCI state.

[0055] For example, for the current beam in event 2, at least one of the following beam options 2a to 2c may be supported: Beam Option 2a: The RS corresponding to the current beam is implicitly derived / determined based on the QCL RS of the indicated TCI state. Beam Option 2b: The RS corresponding to the current beam is the QCL RS in the indicated TCI state and the QCL SSB. · Beam Option 2c: The RS corresponding to the current beam is [explicitly] configured / indicated using RRC signaling / MAC CE.

[0056] For example, for the new beam in event 2, at least one of the following beam options 3a to 3c may be supported: Beam Option 3a: The RS corresponding to the new beam is configured [explicitly] using RRC signaling (e.g., reconfiguration of existing RS measurements or TCI state configuration parameters (e.g., TCI-State)) / MAC CE. Beam Option 3b: The RS corresponding to the new beam is implicitly derived / determined based on the QCL RS of the TCI state to be activated (active TCI state). Beam Option 3c: The RS corresponding to the new beam is implicitly derived / determined based on the QCL RS of one or more TCI states in the configured subset of the list of TCI states configured in RRC (configured TCI states).

[0057] For example, for reference signal measurements (RS measurements) of the current beam for Event 2 (and Beam Option 2a), several schemes may be supported: Scheme 1: The RS of the current beam is the QCL RS in the indicated TCI state. Scheme 2: The RS of the current beam is the QCL RS in the indicated TCI state and the QCLed SSB.

[0058] If there are two QCL RSs in the indicated TCI state, the QCL RSs may be QCL type D.

[0059] At least one of CSI-RS and SSB may be supported as the QCL RS configured / applied to the indicated TCI state. When CSI-RS is configured / applied as the QCL RS, at least one of a tracking CSI-RS (TRS) and a measurement CSI-RS may be supported. The measurement CSI-RS may be the CSI-RS used for L1-RSRP / L1-SINR or the CSI-RS used for beam management (BM).

[0060] In scheme 1, only a TRS (for example, one tracking CSI-RS) may be configured as a QCL-RS (for example, type A / D) in the indication TCI state.

[0061] When only a TRS is set as the QCL-RS for the indicated TCI state, a reference signal different from the TRS (e.g., an RS corresponding to the TRS) may be selected for measuring / reporting the RS of the current beam.

[0062] For RS measurements on the current beam in Event 2 / Option 2a, [in addition to Schemes 1 and 2], when only one TRS is set to the indicated TCI state, at least one of the following processing options 1 to 4 may be applied:

[0063] Processing option 1: An additional scheme is introduced. The RS for the current beam can be the CSI-RS for beam management derived from the QCL RS in the indicated TCI state. Processing Option 2: TRS is additionally supported as the measured RS of the current beam to determine the L1-RSRP. Processing option 3: An additional scheme is introduced: the RS for the current beam is explicitly configured / indicated by the RRC or MAC CE. Processing option 4: No further expansion is performed.

[0064] The explicit RS configuration for measurement of the new beam in event 2 may be configured in one RS resource set associated with the CSI reporting configuration.

[0065] In this case, if the existing UE capability cannot be reused, a UE capability indicating the maximum number of RSs configured in the RS resource set may be defined / introduced.

[0066] The RSs in the one RS resource set may be updated by the MAC CE.

[0067] The UE IBR for MIMO may be transmitted using UCI.

[0068] In a UCI-based UEIBR procedure, the following modes may be supported:

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

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

[0071] Step 2: The UE detects a DCI format (which may be referred to as a first DL signal) indicating a second UL channel resource.

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

[0073] For mode A, at least a one-bit indication in the first UL channel (PUCCH) may be supported to request resources in the second UL channel for transmitting a beam report.

[0074] In this case, periodic PUCCH resources (PUCCH format 0 / 1) may be configured by dedicated higher layer signaling.

[0075] An RRC parameter (e.g., reportResourceRequest-UEIBR) corresponding to the one-bit indication (for setting the one-bit indication) may be defined, and the RRC parameter may be identified using a specific ID (e.g., a dedicated SchedulingRequestId).

[0076] Also, an RRC parameter for periodic PUCCH resource configuration (e.g., firstPUCCHResourceConfig-ModeA-UEIBR) corresponding to the one-bit indication may be defined. The RRC parameter may not be associated with an SR ID (e.g., SchedulingRequestId).

[0077] The RRC parameters may include, for example, a periodicity and offset setting parameter (periodicityAndOffset) and a PUCCH resource ID (for example, PUCCH-ResourceID).

[0078] These RRC parameter specifications may be applied to the case where at least one CC (single CC) is used.

[0079] The DCI format in step 2 may be, for example, an UL grant DCI (for example, DCI format 0_1 / 0_2 / 0_3), and the second UL channel in step 3 may utilize at least a PUSCH.

[0080] Furthermore, the DCI format in step 2 may be, for example, DL grant DCI (for example, DCI format 1_1 / 1_2), and the second UL channel in step 3 may be PUCCH.

[0081] A 1-bit field may be newly defined in the DL grant DCI to instruct transmission of the UEIBR.

[0082] The PUCCH resources intended for HARQ-ACK transmission may be (re)used to transmit both HARQ-ACK and UEIBR.

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

[0084] Step 1: The UE transmits a first UL channel (e.g., PUCCH). The first UL channel is an UL channel that indicates a second UL channel for transmitting a beam report, and may be configured with one or more bits. The first UL channel may be configured with one or more bits.

[0085] Step 2: The UE transmits a beam report in the second UL channel (eg, using a specific resource (UCI) within the channel).

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

[0087] For Mode B, at least a one-bit indication in the first UL channel (PUCCH) may be supported to indicate that the second UL channel is used to transmit a beam report.

[0088] In this case, periodic PUCCH resources (PUCCH format 0 / 1) may be configured by dedicated higher layer signaling.

[0089] In either of the above-mentioned modes A / B, cross-CC (component carrier) beam reporting may be supported.

[0090] An RRC parameter (e.g., reportResourceRequest-UEIBR) corresponding to the one-bit indication (for setting the one-bit indication) may be defined, and the RRC parameter may be identified using a specific ID (e.g., a dedicated SchedulingRequestId).

[0091] Also, an RRC parameter for periodic PUCCH resource configuration (e.g., firstPUCCHResourceConfig-ModeB-UEIBR) corresponding to the one-bit indication may be defined. The RRC parameter may not be associated with an SR ID (e.g., SchedulingRequestId).

[0092] The RRC parameters may include, for example, a periodicity and offset setting parameter (periodicityAndOffset) and a PUCCH resource ID (for example, PUCCH-ResourceID).

[0093] These RRC parameter specifications may be applied to the case where at least one CC (single CC) is used.

[0094] The second UL channel in step 2 may be, for example, a Type 1 Configured Grant (CG) PUSCH or a PUCCH.

[0095] <UEIBR for mobility> With respect to UE IBR for Rel. 19 mobility (e.g., lower layer triggered mobility, LTM), the following may apply.

[0096] ·MAC CE on semi-persistent / aperiodic PUSCH. UCI in periodic / semi-persistent PUCCH, UCI in semi-persistent / aperiodic PUSCH.

[0097] The contents of the report may include, for example, at least one of the following: If the measurement report is used for cell switching reporting, in addition to MIMO related information: -Indicator of cell switching or TA related information. Otherwise (measurement reports are not used for cell switch reporting), · The same content as MIMO-related information (only difference is whether it is intra-cell or inter-cell).

[0098] The supported events may be similar to Conditional Hand-Over (CHO).

[0099] For example, since candidate cells are set based on L3 measurement reports, L1-RSRP / SINR may be used as the threshold.

[0100] If reporting is used for cell switch commands, specific domain filters (eg time / frequency / space) may be considered / applied to prevent frequent switches.

[0101] It may also be specified whether flexibility in triggering time (eg, 5 ms, 10 ms, 20 ms) is required.

[0102] In the case of L1 measurements by UEIBR, at least the results of beam level measurements may be used for event evaluation.

[0103] Events related to UEIBR for Mobility may be broadly categorized into the following event types: Event LTM2: The beam quality of the serving cell becomes worse than the (absolute) threshold. · Event LTM3: The beam quality of the candidate cell becomes better than the beam quality of the serving cell by more than a certain offset amount. · Event LTM4: The beam quality of the candidate cell becomes worse than the (absolute) threshold. Event LTM5: The beam quality of the serving cell becomes worse than a first (absolute) threshold and the beam quality of the candidate cell becomes better than a second (absolute) threshold.

[0104] Note that the events exemplified in this way do not exclude other events. Also, the above-mentioned MIMO events may be appropriately used (in this case, the "current beam" may be replaced with the "beam of the serving cell," and the "new beam" may be replaced with the "beam of the candidate cell," respectively). The events that are used / replaced may be called mobility / LTM events corresponding to the MIMO events.

[0105] In the L1 measurement resource configuration in the LTM configuration, both SSB and CSI-RS beam configurations may be supported.

[0106] In events LTM3 and LTM5, the same type of RS (eg, CSI-RS / SSB) may be used in both the serving cell and the candidate cell (neighbor cell).

[0107] Mobility event evaluation may apply at least one of the following: time to trigger (TimeToTrigger (TTT)), hysteresis for entering / leaving, and beam-specific / cell-specific offsets.

[0108] A mobility-oriented UE IBR may be transmitted using the MAC CE.

[0109] <Definition of terms for specific events> In the above-mentioned existing events, the definitions of serving (cell) and neighbor (cell) may be rephrased / updated as follows in the UEIBR for Rel.19:

[0110] For example, the serving [cell], SpCell, and PCell in existing L3 events may be interchangeably read as the current beam (e.g., RS ID associated with the indicated [joint / DL] TCI state) in event-triggered beam reporting for Rel. 19 MIMO.

[0111] In addition, the serving [cell], SpCell, and PCell in existing L3 events may be interchangeably read as the current beam (e.g., the RS ID associated with the indicated [joint / DL] TCI state) or the beam of the serving cell (e.g., the RS ID associated with the TCI state for the PCI of the serving cell) in event-triggered beam reporting for Rel.19 mobility.

[0112] Adjacent [cells] in existing L3 events may be swapped with other beams (e.g., RS IDs associated with RS IDs for L1 beam measurements but not associated with the indicated [joint / DL] TCI state) in event-triggered beam reporting for Rel. 19 MIMO (which may be mobility).

[0113] Also, adjacent [cells] in existing L3 events may be swapped with beams of non-serving cells / target cells / candidate cells (e.g., RS IDs associated with TCI states for the PCI of target cells / candidate cells) in event-triggered beam reporting for Rel. 19 mobility.

[0114] The measured value of each reference signal (RS) may be RSRP / SINR, L3-RSRP / SINR, L1-RSRP / SINR, or the average value of multiple L1-RSRP / SINRs.

[0115] For example, L1-RSRP / SINR can change dynamically. Therefore, by averaging multiple (X number) of L1-RSRP / SINR values (e.g., X = 5), control hunting (frequent switching of trigger states) in beam reporting triggering can be avoided.

[0116] <L1 / L2 Inter-Cell Mobility> The UE may perform UL transmission for one or more cells / TRPs. As procedures in this case, Scenario 1 or Scenario 2 below can be considered. In this disclosure, the serving cell may be read as a TRP within the serving cell. layer1 / layer2 (L1 / L2), DCI / Medium Access Control (MAC) Control Element (CE) may be read as each other. In this disclosure, a PCI different from the physical cell ID (Physical Cell Identity (PCI)) of the current serving cell may simply be described as "different PCI". Non-serving cells, cells with different PCIs, and additional cells may be read as each other.

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

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

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

[0120] Assume that a UE moves from a cell (serving cell) with PCI#1 to a cell (additional cell) with PCI#3 (which overlaps with the serving cell). In this case, Rel. 17 does not support switching of the serving cell via L1 / L2.

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

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

[0123] (1) The UE receives from the serving cell the SSB configuration of a cell (additional cell) with a different PCI for beam measurement / serving cell change. (2) The UE performs beam measurements of cells using different PCIs and reports the measurement results to the serving cell. (3) The UE may receive a configuration of a cell with a different PCI (serving cell configuration) through higher layer signaling (e.g., RRC). That is, a pre-configuration regarding a 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 states of cells with different PCIs may be activated by L1 / L2 signaling according to the change of serving cell. The activation of the TCI states and the change of serving cell 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.

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

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

[0126] <Rel.18 LTM> The main motivation for lower layer triggered mobility (LTM) is to reduce disruption time (in RACH-based cell switches). LTM has several characteristics: ◆Handover can be performed without RACH / RRC reconfiguration / MAC reset. ◆ One or more candidate cells are in the same CU as the serving cell. ◆One or more candidate cells are on the same or different frequencies as the serving cell.

[0127] After the UE receives the LTM configuration (LTM-Config) from the serving cell and before making a cell switch decision for one or more candidate cells, several of the following steps are performed. ◆DL synchronization [between the UE and one or more candidate cells] ◆L1 measurement report ◆UL synchronization [between the UE and one or more candidate cells] ◆TCI state activation [from the serving cell to the UE]

[0128] After that, when the serving cell determines a cell switch and selects one target cell from one or more candidate cells, it transmits a cell switch command (CSC, LTM cell switch command) MAC CE to the UE. The CSC MAC CE contains several of the following information for the target cell of the cell switch [within one or more candidate cells]. ◆Configuration ID [for indicating the target cell] ◆TCI state ID ◆Timing advance (TA) value ◆CFRA resource index (optional)

[0129] <Various settings in the framework of CSI reporting for LTM in Rel.18> In the CSI reporting settings for LTM in Rel.18, the resource settings include a list of candidate IDs that are one-to-one mapped with a list of SSB indices. In Rel.18 LTM, only SSB-based L1-RSRP is supported.

[0130] In Rel.18 LTM, the CSI-RS resource / resource set settings can be provided under the parameters (LTM-TCI-Info) for one LTM candidate ID.

[0131] The configuration of the NZP CSI-RS resource set follows the rules of Rel. 17 and has resource set-specific parameters.

[0132] MAC CE-based event-triggered beam reporting for mobility Regarding L1 measurement reports, the use of MAC CE is being considered.

[0133] For example, an event-triggered L1 measurement may be reported from the UE to the network (NW) via the MAC CE.

[0134] Regarding existing resource allocation, the following is specified:

[0135] The logical channels may be prioritized according to the following order (highest priority may be placed first): ·MAC CE for C-RNTI or data from the Uplink Common Control Channel (UL-CCCH). · [Extended] MAC CE for Beam Failure Recovery (BFR), or MAC CE for Configuration Grant (CG) confirmation, or MAC CE for multiple entry CG confirmation. · MAC CE for checking side link (SL) CG. ·MAC CE for LBT (Listen Before Talk) failure. ·MAC CE for SL LBT failure according to specific provisions. ·MAC CE for timing advance reporting. MAC CE for Buffer Status Report (BSR) included for padding. MAC CE for SL-BSR included for padding.

[0136] Note that prioritization between MAC CEs with the same priority may be up to the UE implementation.

[0137] (CSI report or reporting) In Rel.15 NR, a terminal (also referred to as a user terminal, User Equipment (UE), etc.) generates (also referred to as determining, calculating, estimating, measuring, etc.) channel state information (CSI) based on a reference signal (RS) (or a resource for the RS), and transmits (also referred to as reporting, feeding back, etc.) the generated CSI to a network (e.g., a base station). The CSI may be transmitted to the base station using, for example, an uplink control channel (e.g., a Physical Uplink Control Channel (PUCCH)) or an uplink shared channel (e.g., a Physical Uplink Shared Channel (PUSCH)).

[0138] The RS used to generate the CSI may be, for example, at least one of a Channel State Information Reference Signal (CSI-RS), a Synchronization Signal / Physical Broadcast Channel (SS / PBCH) block, a Synchronization Signal (SS), a Demodulation Reference Signal (DMRS), etc.

[0139] The CSI-RS may include at least one of a Non-Zero Power (NZP) CSI-RS and a CSI-Interference Management (CSI-Interference Measurement, CSI-IM). The SS / PBCH block is a block including an SS and a PBCH (and corresponding DMRS), and may be referred to as an SS block (SSB). The SS may also include at least one of a Primary Synchronization Signal (PSS) and a Secondary Synchronization Signal (SSS).

[0140] The CSI may include at least one of a Channel Quality Indicator (CQI), a Precoding Matrix Indicator (PMI), a CSI-RS Resource Indicator (CRI), a SS / PBCH Block Resource Indicator (SSBRI, SSB index), a Layer Indicator (LI), a Rank Indicator (RI), Layer 1 Reference Signal Received Power (L1-RSRP), Reference Signal Received Quality (L1-RSRQ), Signal to Interference plus Noise Ratio (L1-SINR), and Signal to Noise Ratio (L1-SNR).

[0141] The UE may receive information about CSI reporting (report configuration information) and control CSI reporting based on the report configuration information. The report configuration information may be, for example, "CSI-ReportConfig" of an information element (IE) of Radio Resource Control (RRC).

[0142] The reporting configuration information (for example, the RRC IE "CSI-ReportConfig") may include, for example, at least one of the following: ◆ Information about the type of CSI report (report type information, e.g., RRC IE "reportConfigType") Information about one or more quantities of CSI to be reported (one or more CSI parameters) (report quantity information, e.g., RRC IE "reportQuantity") Information about the RS resources used to generate the quantity (CSI parameter) (resource information, for example, the RRC IE "CSI-ResourceConfigId") Information about the frequency domain to which CSI is reported (frequency domain information, e.g., RRC IE "reportFreqConfiguration")

[0143] For example, the report type information may indicate periodic CSI (P CSI) reporting, aperiodic CSI (A CSI, AP CSI) reporting, or semi-persistent CSI (SP CSI) reporting.

[0144] Furthermore, the reporting amount information may specify a combination of at least one of the above CSI parameters (for example, CRI, RI, PMI, CQI, LI, L1-RSRP, etc.).

[0145] The resource information may also be IDs of resources for RSs, which may include, for example, non-zero power CSI-RS resources or SSBs and CSI-IM resources (e.g., zero power CSI-RS resources).

[0146] The frequency domain information may also indicate frequency granularity of CSI reporting. The frequency granularity may include, for example, a wideband and a subband. The wideband is the entire CSI reporting band. The wideband may be, for example, the entirety of a certain carrier (a component carrier (CC)), a cell, or a serving cell), or the entirety of a bandwidth part (BWP) within a certain carrier. The wideband may also be referred to as a CSI reporting band, the entire CSI reporting band, etc.

[0147] Furthermore, a subband is a part of a wideband and may be configured with one or more resource blocks (RBs or PRBs). The size of the subband may be determined according to the size of the BWP (the number of PRBs).

[0148] The frequency domain information may indicate whether wideband or subband PMI is to be reported (for example, the frequency domain information may include an RRC IE "pmi-FormatIndicator" used to determine whether wideband PMI reporting or subband PMI reporting is to be performed). The UE may determine the frequency granularity of the CSI report (i.e., whether wideband PMI reporting or subband PMI reporting is to be performed) based on at least one of the above-mentioned reporting amount information and frequency domain information.

[0149] When wideband PMI reporting is configured, one wideband PMI may be reported for the entire CSI reporting band, whereas when subband PMI reporting is configured, a single wideband indication i1 may be reported for the entire CSI reporting band, and one subband indication i2 (e.g., one subband indication for each subband) may be reported for each of one or more subbands within the entire CSI reporting band.

[0150] The UE performs channel estimation using the received RS to estimate a channel matrix H. The UE feeds back a performance management index (PMI) determined based on the estimated channel matrix.

[0151] The PMI may indicate a precoder matrix (also simply referred to as a precoder) that the UE considers appropriate for use in downlink (DL) transmissions to the UE. Each value of the PMI may correspond to one precoder matrix. A set of PMI values ​​may correspond to a set of different precoder matrices called a precoder codebook (also simply referred to as a codebook).

[0152] In the space domain, a CSI report may include one or more types of CSI. For example, the CSI may include at least one of a first type (Type 1 CSI) used for single-beam selection and a second type (Type 2 CSI) used for multi-beam selection. The single beam may be rephrased as a single layer, and the multi-beam may be rephrased as multiple beams. Furthermore, Type 1 CSI may not assume multi-user multiple input multiple output (MU-MIMO), while Type 2 CSI may assume multi-user MIMO.

[0153] The codebook may include a codebook for Type-1 CSI (also referred to as a Type-1 codebook, etc.) and a codebook for Type-2 CSI (also referred to as a Type-2 codebook, etc.). Furthermore, Type-1 CSI may include Type-1 single-panel CSI and Type-1 multi-panel CSI, and different codebooks (Type-1 single-panel codebook, Type-1 multi-panel codebook) may be defined for each.

[0154] The uplink control information (UCI) type may include at least one of a Hybrid Automatic Repeat reQuest ACKnowledgement (HARQ-ACK), a scheduling request (SR), and CSI. The UCI may be carried by the PUCCH or the PUSCH.

[0155] In Rel.15 NR, UCI can contain one CSI part for wideband PMI feedback. CSI report #n contains PMI wideband information if reported.

[0156] In Rel.15 NR, UCI can include two CSI parts for subband PMI feedback. CSI Part 1 includes wideband PMI information. CSI Part 2 includes one wideband PMI and several subband PMIs. CSI Part 1 and CSI Part 2 are coded separately.

[0157] In Rel. 15 NR, a UE is configured by higher layers with N (N≧1) CSI reporting configuration report settings and M (M≧1) CSI resource configuration resource settings. For example, the CSI reporting configuration (CSI-ReportConfig) includes a channel measurement resource setting (resourcesForChannelMeasurement), a CSI-IM resource setting for interference (csi-IM-ResourceForInterference), an NZP CSI-RS setting for interference (nzp-CSI-RS-ResourceForInterference), and a report quantity (reportQuantity). The channel measurement resource setting, the interference CSI-IM resource setting, and the interference NZP CSI-RS setting are each associated with a CSI resource configuration (CSI-ResourceConfig, CSI-ResourceConfigId). The CSI resource configuration includes a list of CSI-RS resource sets (csi-RS-ResourceSetList, for example, an NZP CSI-RS resource set or a CSI-IM resource set).

[0158] For both FR1 and FR2, evaluation and provision of CSI reporting for DL ​​multi-TRP and / or multi-panel transmissions is being considered to enable more dynamic channel / interference hypotheses for NCJT.

[0159] In the present disclosure, Type 1 and Type I may be interpreted as interchangeable. In the present disclosure, Type 2 and Type II may be interpreted as interchangeable.

[0160] In the present disclosure, CSI-RS, periodic CSI-RS (P CSI-RS), semi-persistent CSI-RS (SP CSI-RS), aperiodic CSI-RS (AP CSI-RS, A CSI-RS) may be read as each other. In the present disclosure, CSI-RS, periodic CSI report (P CSI report), semi-persistent CSI report (SP CSI report), aperiodic CSI report (AP CSI report, A CSI report) may be read as each other.

[0161] <CSI trigger state> In the present disclosure, trigger state, CSI trigger state, and trigger state of CSI report may be read as each other.

[0162] The trigger state (CSI report trigger) is started using the CSI request field in DCI. When all bits [values] of the CSI request field in DCI are set to 0, it may mean that CSI is not requested.

[0163] When the number of CSI trigger states set in the upper layer parameter CSI-AperiodicTriggerStateList is 2 N TS greater than -1, the UE may receive a sub-selection indication. The sub-selection indication (e.g., MAC CE) may be used to map up to 2 N TS -1 trigger states to the code point of the CSI request field in DCI.

[0164] That is, the MAC CE may be used to activate up to 2 N TS trigger states for further DCI indication by the CSI request field when the number of set trigger states is 2 N TS greater than -1.

[0165] Here, NTS 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.

[0166] The number of trigger states is at most 2 N TS -1, and each trigger state may correspond to a code point of the CSI request field in the DCI.

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

[0168] (Physical layer procedures for data / Procedures related to physical downlink shared channel) <UE procedures for CSI reporting / CSI framework / CSI processing criteria> <<Maximum number of simultaneous CSI calculations (number of CPUs) and occupied CPU number for CSI calculations>> N CPU implies the number of CSI processing units (CPUs). The UE reports / indicates / declares the number of supported simultaneous CSI calculations (maximum number of simultaneous CSI calculations) N using some of the following capability information: CPU to:

[0169] ◆ simultaneousCSI-ReportsPerCC [in csi-ReportFramework in MIMO-ParametersPerBand]. MIMO-ParametersPerBand is used to convey MIMO-related parameters specific to a certain band. csi-ReportFramework indicates whether the UE supports the CSI reporting framework. csi-ReportFramework indicates whether the UE supports the CSI reporting framework. simultaneousCSI-ReportsPerCC indicates the number of CSI reports that the UE can simultaneously measure and process multiple reference signals within one CC of a band for which this capability is provided. CSI reports include periodic, semi-persistent, and aperiodic CSI, and any latency class and codebook type. CSI reports in simultaneousCSI-ReportsPerCC include beam reports and CSI reports.

[0170] ◆ simultaneousCSI-ReportsAllCC [in CA-ParametersNR]. simultaneousCSI-ReportsAllCC indicates whether the UE supports the CSI reporting framework and the number of CSI reports the UE can process simultaneously across all CCs (master cell group (MCG) and secondary cell group (SCG) in the case of NR-DC). CSI reports include periodic, semi-persistent, and aperiodic CSI, and any latency class and codebook type. CSI reports in simultaneousCSI-ReportsAllCC include beam reports and CSI reports. This parameter further constrains simultaneousCSI-ReportsPerCC and Phy-ParametersFRX-Diff in MIMO-ParametersPerBand for each band in a given band combination.

[0171] UE is N CPU If the UE supports N simultaneous CSI calculations, the UE may use NCPU If L CPUs are dedicated to the computation of CSI reports in a given OFDM symbol, the UE is considered to have N CPU -L free CPUs. N CPU On the same OFDM symbol where L CPUs are not occupied, N CSI reports start by occupying each CPU, and O of each CSI report n=0,...,N-1 of the N CSI reports CPU (n) (Number of occupied CPUs for CSI report n, number of consumed CPUs), the UE shall select the lowest priority (highest priority value Pri iCSI (y, k, c, s)), where 0≦M≦N, is not required to update (calculate, process) the NM requested CSI reports from Σ n=0 M-1 O CPU (n) ≦N CPU -L is the maximum value for which it holds.

[0172] UE is N CPU It is not assumed that an AP CSI trigger state containing more than one report setting will be configured. The processing of CSI reports occupies some CPU resources in some symbols, as in the following processes 1, 2, a, and 3. The processing of CSI reports may be performed with 0, 1, or more (O CPU , number of occupied CPUs) (CPU occupancy rule).

[0173] ◆Process 1 In the case where CSI reporting is configured using CSI-ReportConfig with higher layer parameter reportQuantity set to 'none' and CSI-RS-ResourceSet with higher layer parameter trs-Info, CPU =0.

[0174] ◆Process 2 (Beam management) In CSI reporting using ltm-CSI-ReportConfig, or in CSI reporting using CSI-ReportConfig with the higher layer parameter reportQuantity set to 'cri-RSRP', 'ssb-Index-RSRP', 'cri-SINR', 'ssb-Index-SINR', 'cri-RSRP-Capability[Set]Index', 'ssb-Index-RSRP-Capability[Set]Index', 'cri-SINR-Capability[Set]Index', 'ssb-Index-SINR-Capability[Set]Index', or 'none' [if CSI-RS-ResourceSet with the higher layer parameter trs-Info is not configured], CPU =1.

[0175] ◆Process a (TDCP report) For CSI reporting using CSI-ReportConfig with higher layer parameter reportQuantity set to 'tdcp' and the number of delays Y configured by higher layer parameter Y, CPU = (Y+1), where the value of X >= 1 is reported by the UE capabilities.

[0176] ◆Process 3 In CSI reporting using CSI-ReportConfig with higher layer parameter reportQuantity set to 'cri-RI-PMI-CQI', 'cri-RI-i1', 'cri-RI-i1-CQI', 'cri-RI-CQI', or 'cri-RI-LI-PMI-CQI', CPU is based on the following process 3-x:

[0177] - Process 3-1 (case where the UE can use the maximum of its capabilities) max{μ PDCCH ,μ CSI-RS ,μ UL}≦3 and CSI reporting without PUSCH transmission with at least one of transport block and HARQ-ACK is triggered aperiodically when L=0 CPUs are occupied, the CSI corresponds to a single CSI with wideband frequency-granularity and 4 or less CSI-RS ports in a single resource without CRI reporting, the codebookType is set to 'typeI-SinglePanel', and the reportQuantity is set to 'cri-RI-CQI', CPU =N CPU μ PDCCH is the subcarrier spacing (SCS) setting of the PDCCH. CSI-RS is the SCS setting of CSI-RS. μ UL is the SCS setting of the UL BWP where the CSI report is sent.

[0178] - Process 3-2 (NCJT CSI case) If a CSI-ReportConfig with codebookType set to 'typeI-SinglePanel' is configured and the corresponding CSI-RS resource set for channel measurements is configured with 2 resource groups and N resource pairs, then O CPU =X·N+M, where X is the number of CPUs occupied by a pair of CMRs according to the UE capability. The UE capability mTRP-CSI-numCPU-r17 indicates the number of CPUs occupied by a pair of CMRs for the NCJT CSI hypotheses. K s Of the NZP CSI-RS resource sets for channel measurements with K1 resources, M=M1+M2 for M1 and M2 resources associated with CRI values ​​for resource group 1 with K1 resources and resource group 2 with K2 resources.

[0179] - Process 3-3 (CSI reporting subsetting case [for NES]) If CSI-ReportConfig contains a list of L sub-configurations provided by the upper layer parameter csi-ReportSubConfigToAddModList, then CPU is based on the following process 3-3-x: --Process 3-3-1 In the P CSI report, CPU =Σ i=1 L K s i Here, K s i is the number of CSI-RS resources corresponding to the i-th subset. --Process 3-3-2 In the AP CSI report and the SP CSI report, CPU =Σ i=1 N K s i Here, K s i is the number of CSI-RS resources corresponding to the i-th subset, which is the i-th subset from the indicated N subsets out of the L subsets contained in the CSI-ReportConfig, where N≦L and N≧1.

[0180] - Process 3-4 (CJT CSI case) A CSI-ReportConfig is configured with the higher layer parameter reportQuantity set to 'cri-RI-PMI-CQI' and the codebookType set to 'typeII-CJT-r18' or 'typeII-CJT-PortSelection-r18', and the corresponding <N TRP If an NZP-CSI-RS-ResourceSet for channel measurement with ≤ 4 resources is configured, O CPU =X N TRP where the value of X >= 1 is reported by the UE capabilities.

[0181] - Process 3-5 (Doppler CSI case) If CSI-ReportConfig is configured with higher layer parameter reportQuantity set to 'cri-RI-PMI-CQI' and codebookType set to 'typeII-Doppler-r18' or 'typeII-Doppler-PortSelection-r18', then CPU is based on the following procedure 3-5-x: --Processing 3-5-1 If the corresponding CSI-RS resource set for channel measurement is aperiodic (AP) and configured with K CSI-RS resources, then O CPU =8, and for K<12, O CPU = Y1·K, where Y1∈{1,2,3} is reported by the UE capability indication. --Process 3-5-2 If the corresponding CSI-RS resource set for channel measurement is periodic (P) or semi-persistent (SP) and configured with a single CSI-RS resource, then for N4=1, O CPU = 4, and for N4>1, O CPU = Y2·N4 ≥ 4, where N4 is set by the higher layer parameter N4 and Y2 ∈ {2 / 3,1,2,3} is reported by the UE capability indication.

[0182] - Process 3-6 (Other cases) In all other cases, O CPU =K s It is. K s is the number of CSI-RS resources in the CSI-RS resource set for channel measurements.

[0183] As mentioned above, when L CPUs are occupied, the UE n=0 M-1 O CPU (n) ≦N CPU Update CSI report as long as -L.

[0184] <<CPU Occupancy Time Period>> In the CSI reporting using CSI-ReportConfig with a higher layer parameter reportQuantity not set to 'none', or in the CSI reporting using LTM-CSI-ReportConfig, one or more CPUs are occupied during the following multiple OFDM symbols (CPU occupancy time period).

[0185] ◆ Except for [the first SP CSI report on the PUSCH after the PDCCH that triggers the report and the SP CSI report on the PUSCH with the higher layer parameter codebookType set to 'typeII-Doppler-r18' or 'typeII-Doppler-PortSelection-r18'], the P CSI report or the SP CSI report is such that the occasion of each latest CSI-RS / CSI-IM / SSB is before (not later than) the corresponding CSI reference resource and is associated with one or more CSI-RS / CSI-IM resources within the resources of one or more CSI-RS / CSI-IM / SSB for channel or interference measurement, or with one or more CSI-RS / CSI-IM resources associated with all sub-configurations set for the P CSI report corresponding to the CSI-ReportConfig including the list of sub-configurations provided by csi-ReportSubConfigToAddModList, or with one or more CSI-RS / CSI-IM resources associated with all sub-configurations activated / triggered for the SP CSI report corresponding to the CSI-ReportConfig including the list of sub-configurations provided by csi-ReportSubConfigToAddModList. From the first symbol of the earliest resource to the last symbol of the configured PUSCH / PUCCH that carries the report, one or more CPUs are occupied (CPU occupancy time period 1).

[0186] An AP CSI report occupies one or more CPUs from the first symbol after the PDCCH that triggers the CSI report to the last symbol of the scheduled PUSCH that carries the report (CPU occupancy time period, Figure 1). If the PDCCH reception includes two corresponding PDCCH candidates from two search space sets, the PDCCH candidate that ends later is used to determine the CPU occupancy duration.

[0187] The first SP CSI report on the PUSCH after a PDCCH trigger occupies one or more CPUs from the first symbol after the PDCCH to the last symbol of the scheduled PUSCH carrying the report. If the PDCCH reception includes two corresponding PDCCH candidates from two search space sets, the PDCCH candidate that ends later is used to determine the CPU occupancy duration.

[0188] ◆ The CSI-ReportConfig with the upper layer parameter codebookType set to 'typeII-Doppler-r18' or 'typeII-Doppler-PortSelection-r18' is configured, and the SP CSI report on the PUSCH is not later than the CSI reference resource. P occupies one or more CPUs from the first symbol of the th most recent consecutive P / SP CSI-RS occasion to the last symbol of the PUSCH carrying that report, where K P The values ​​∈{1,2,4} are indicated / reported by the UE capabilities.

[0189] For CSI reporting using CSI-ReportConfig with upper layer parameter reportQuantity set to 'none' and CSI-RS-ResourceSet with upper layer parameter trs-info not configured, one or more CPUs are occupied for the following multiple OFDM symbols (CPU occupation time periods):

[0190] ◆ [Excluding the first SP CSI report on the PUSCH after the PDCCH that triggers the report] An SP CSI report occupies one or more CPUs from the first symbol of the earliest transmission occasion among one or more transmission occasions of a P or SP CSI-RS / SSB resource for channel measurement for L1-RSRP calculation to Z'3 symbols after the last symbol of the latest CSI-RS / SSB resource for channel measurement for L1-RSRP calculation within that transmission occasion (CPU occupancy time period, Figure 2A).

[0191] ◆An AP CSI report occupies one or more CPUs from the first symbol after the PDCCH that triggers the CSI report to the last symbol of either Z3 symbols after the first symbol after the PDCCH that triggers the CSI report or Z'3 symbols after the last symbol of the latest CSI-RS / SSB resource for channel measurements for L1-RSRP calculation (CPU occupancy time period, Figure 2B).

[0192] In the present disclosure, the terms CPU occupation time period, CPU occupation time, CPU occupation period, CPU occupation duration, the period from the start of CSI resources for a P CSI report or an SP CSI report to the end of the CSI report, and the period from the end of triggering for an AP CSI report to the end of the CSI report may be read interchangeably.

[0193] <<CSI-RSリソースカウンティング(アクティブリソースカウンティング、ARC)> > In any slot, the UE does not expect to have more active CSI-RS ports or active CSI-RS resources in the active BWP than the number reported as its capabilities. NZP CSI-RS resources are active for a duration of time defined as follows: ◆The duration for an AP CSI-RS starts from the end of the PDCCH containing the request and ends at the end of the scheduled PUSCH containing the report associated with that AP CSI-RS. ◆The duration for an SP CSI-RS starts at the end of the time that the activation command applies and ends at the end of the time that the deactivation command applies. ◆The duration for a P CSI-RS starts when that P CSI-RS is configured by higher layer signaling and ends when that P CSI-RS configuration is released.

[0194] If a CSI-RS resource is referenced N times by one or more CSI reporting settings that are not configured with the higher layer parameter csi-ReportSubConfigToAddModList, then that CSI-RS resource and the CSI-RS ports within that CSI-RS resource are counted N times.

[0195] In a channel measurement CSI-RS resource set configured with two resource groups and N resource pairs, if a CSI-RS resource is referenced X times by one of the M CSI-RS resources and at least one of one or two resource pairs, then that CSI-RS resource and the CSI-RS port within that CSI-RS resource will be counted X times.

[0196] In the CSI-ReportConfig, which contains a list of L subsets provided by the higher layer parameter csi-ReportSubConfigToAddModList, if a CSI-RS resource is referenced by M subsets out of the N subsets triggered for CSI reporting for AP CSI-RS resources or out of the L subsets configured for CSI reporting for P CSI-RS resources or SP CSI-RS resources, then that CSI-RS resource is counted M times and the CSI-RS ports in that CSI-RS resource are counted M times, max(Σs=1 M P s , P) times, where P is the number of ports set by nrofPorts, and if the corresponding antenna port subset indicator [portsubsetIndicator] is set, P s is the number of CSI-RS ports in the subset s derived from that indicator, otherwise, P s =P.

[0197] For a P CSI-RS resource or an SP CSI-RS resource in a CSI-RS resource set for channel measurement that is linked to a CSI-ReportConfig configured with the higher layer parameter codebookType set to 'typeII-Doppler-r18' or 'typeII-Doppler-PortSelection-r18', the CSI-RS resource and the CSI-RS port in the CSI-RS resource are P It is counted K times. P The values ​​∈{1,2,4} are indicated / reported by the UE capabilities.

[0198] A P CSI-RS is always counted as an active CSI-RS, regardless of whether it is received on that OFDM symbol or not.

[0199] The UE reports UE capability information (codebookParameter) related to the codebook of the CSI report for each band.

[0200] The codebookParameter indicates the codebook (type) and corresponding parameters supported by the UE. Reporting of parameters corresponding to Type 1 Single Panel is mandatory. Reporting of parameters corresponding to Type 1 Multi Panel, Type 2, and Type 2 Port Selection is optional. The parameters may include at least one of maxNumberTxPortsPerResource, maxNumberResourcesPerBand, and totalNumberTxPortsPerBand. maxNumberTxPortsPerResource indicates the maximum number of transmit ports in one resource. maxNumberResourcesPerBand indicates the maximum number of resources that can be used simultaneously across all CCs in one band. totalNumberTxPortsPerBand indicates the maximum number of transmit ports that can be used simultaneously across all CCs in one band.

[0201] In this disclosure, CPU occupancy, CPU occupancy rate, CPU occupancy time, number of occupied CPUs, number of CPUs, O CPU , O CPU (n) , Σ n=0 M-1 O CPU (n) The number of occupied CPUs and the number of consumed CPUs may be read interchangeably.

[0202] In the present disclosure, the number of processes / calculations, the number of CSI reports, the number of CSI calculations, the number of simultaneous CSI calculations, the number of CSI reports that can be measured and processed simultaneously, the number of CSI processes, the number of CPUs, and the number (count) of CSI-RS resources / CSI-RS ports calculated / measured / processed for CSI may be read interchangeably.

[0203] In the present disclosure, the CSI-RS resource and the active resource may be interchangeably read. In the present disclosure, the CSI-RS resource counting and the active resource counting (ARC) may be interchangeably read. In the present disclosure, the number of CSI-RS resources and the number of active resources may be interchangeably read.

[0204] <UE Procedures / CSI / CSI Reference Resource Definition for CSI Reporting> The CSI reference resource for a serving cell is defined as follows. ◆ In the frequency domain, the CSI reference resource is defined by a group of multiple DL PRBs corresponding to the band to which the derived CSI is related. ◆ In the time domain, the CSI reference resource for CSI reporting within UL slot n' is a single DL slot n - n CSI_ref -K offset ·2 μ_DL / 2 μ_Koffset and is defined by. Here, K offset is a parameter set by the upper layer, and μ_K_offset is the subcarrier spacing setting for K offset and has a value of 0 in frequency range (FR) 1. ―◆ Here, n is given by the following equation. n = floor(n’·2 μ_DL / 2 μ_UL ) + floor(N slot,offset,UL CA / 2 μ_offset,UL -N slot,offset,DL CA / 2 μ_offset,DL )·2 μ_DL ). μ_DL and μ_UL are the subcarrier spacing settings for DL and UL, respectively. N slot,offset CA and μ_offset are determined by the ca-SlotOffset set by the upper layer for the cell transmitting UL and DL. ―◆ For P / SP CSI reporting, the following procedure is defined. If a single CSI-RS / SSB resource is configured for channel measurement, CSI_ref is 4·2, so that it corresponds to an enabled DL slot. μ_DL This is the minimum value above. If multiple CSI-RS / SSB resources are configured for channel measurement, CSI_ref is 5·2, so that it corresponds to a valid DL slot. μ_DL This is the minimum value above. - In AP CSI reporting, if the UE is instructed by DCI to report CSI in the same slot as the CSI request, n CSI_ref is a value such that the reference resource is in the same valid DL slot as the corresponding CSI request, otherwise, n CSI_ref is slot nn CSI_ref corresponds to a valid DL slot, symb slot ) where Z' corresponds to the CSI calculation delay requirement. N symb slot is the number of symbols in the slot. -◆If CSI-RS / CSI-IM or SSB of P or SP is used for channel / interference measurement, the UE is not expected to measure the channel / interference for the CSI-RS / CSI-IM / SSB whose last OFDM symbol is received less than Z' symbols before the transmission time of the first OFDM symbol of the AP CSI report.

[0205] A slot in the serving cell is considered a valid DL slot if it contains at least a DL or flexible symbol configured by higher layers and the slot is not within a measurement gap configured for the UE.

[0206] As in the example of Figure 3A, the CMR for measurements for AP CSI reporting on PUSCH is before the CSI reference resource (not after the CSI reference resource). The slot of that CSI reference resource is the same slot as the PDCCH (CSI request) that triggers that CSI report (the same slot as the PUSCH that carries that CSI report) (n CSI_ref =0), or before the slot that is floor(Z' / N symb slot ) slots before from the slot of that PUSCH (between the CMR and the PUSCH, n CSI_ref =floor(Z' / N symb slot ) [slots] or more).

[0207] As in the example of Figure 3B, the time between the P / SP CMR for measurements for AP CSI reporting on PUSCH and the start of that PUSCH is greater than the [UE CSI calculation time (CSI calculation delay requirement)] Z' symbols.

[0208] <UE CSI calculation time> [UE] The CSI calculation time is the processing time for AP CSI reporting. The UE reports CSI to the gNB if the following multiple conditions are met. ◆ Condition 1: The time gap #1 (time from indication end to report start) between the last symbol of the PDCCH and the first symbol of the PUSCH is Z symbols or more. ◆ Condition 2: When AP CSI-RS is used for reporting, the time gap #2 (time from measurement end to report start) between the last symbol of the latest AP CSI-RS and the first symbol of the PUSCH is Z' symbols or more.

[0209] (Z, Z') depends on the calculation load of CSI.

[0210] When the CSI request field on the DCI triggers an [AP] CSI report on the PUSCH, the UE provides a valid CSI report for the n-th triggered report if the following condition (Figure 4) holds: ◆ The first uplink symbol carrying one or more corresponding CSI reports and including the effect of timing advance is symbol Z ref (Z symbols from the last symbol of the PDCCH carrying that DCI) ref (starts after the symbol has elapsed), and The first uplink symbol carrying the nth CSI report and including the effect of timing advance is symbol Z' ref (n) (starting no earlier than Z' from the last symbol of the latest AP CMR (AP CSI-RS) for the nth triggered CSI report) ref (n) symbol).

[0211] where Z ref is the end of the last symbol of the PDCCH that triggers one or more CSI reports. proc,CSI =(Z)(2048+144)·κ2 -μ T C +T switch The number of symbols between the last symbol of the PDCCH and the UL symbol is defined as Z ref and the time from the end of the last symbol of the PDCCH to the start of the UL symbol is T proc,CSI (That's all.) Here, Z' ref (n) is the time T' of the end of the last symbol in the latest period among the following multiple resources when the AP CSI-RS is used for channel measurement for the nth triggered CSI report: proc,CSI =(Z')(2048+144)·κ2 -μ T C The number of symbols between the last symbol in the latest period of the resources and the UL symbol is defined as Z'ref (n), and the time from the end of the last symbol in the latest period of the multiple resources to the start of the UL symbol is T' proc,CSI That's it): ◆For a CSI-ReportConfig, or for all triggered sub-configurations if the CSI-ReportConfig includes multiple sub-configurations, the multiple periods are the periods of the AP CSI-RS resources for channel measurement, the AP CSI-IM used for interference measurement, and the AP NZP CSI-RS for interference measurement.

[0212] where T switch is defined in the specification and applies only if Z1 applies.

[0213] If a PDCCH reception includes two corresponding PDCCH candidates from two search space sets, the PDCCH candidate that ends later in time is used to determine the last symbol of the PDCCH that triggers the CSI report.

[0214] Z, Z' and μ are defined as follows:

[0215] Z = max(Z(m)) for m = 0,...,M-1. Z' = max(Z'(m)) for m = 0,...,M-1, where M is the number of updated CSI reports. (Z(m),Z'(m)) corresponds to the mth updated CSI report and is defined as follows: where CSI computation delay requirement 1 denotes (Z1,Z'1) [symbols] for μ∈{0,1,2,3} (Figure 5, Table C-1), and CSI computation delay requirement 2 denotes (Z1,Z'1), (Z2,Z'2), (Z3,Z'3) [symbols] for μ∈{0,1,2,3,4,5,6} (Figure 6, Table C-2).

[0216] ◆max{μ PDCCH ,μ CSI-RS ,μ UL}≦3, and L=0 CPUs are occupied, the CSI to be transmitted is a single CSI, corresponds to wideband frequency granularity, the CSI corresponds to four or less CSI-RS ports in a single resource without CRI reporting, and CodebookType is set to 'typeI-SinglePanel' or reportQuantity is set to 'cri-RI-CQI', and if the CSI is triggered without PUSCH with transport block or HARQ-ACK or both, then (Z(m), Z'(m)) is defined as (Z1, Z'1) in CSI calculation delay requirement 1.

[0217] ◆If the CSI to be transmitted corresponds to wideband frequency granularity, the CSI corresponds to four or fewer CSI-RS ports in a single resource without CRI reporting, and CodebookType is set to 'typeI-SinglePanel' or reportQuantity is set to 'cri-RI-CQI', then (Z(m),Z'(m)) is defined as (Z1,Z'1) in CSI calculation delay requirement 2.

[0218] ◆If the CSI to be transmitted corresponds to wideband frequency granularity and reportQuantity is set to 'ssb-Index-SINR', 'cri-SINR', 'ssb-Index-SINR-Index', or 'cri-SINR-Index', then (Z(m), Z'(m)) is defined as (Z1, Z'1) in CSI calculation delay requirement 2.

[0219] ◆ reportQuantity is set to 'cri-RSRP', 'ssb-Index-RSRP', 'cri-RSRP-Index', or 'ssb-Index-RSRP-Index', and X μ According to the UE reported capability beamReportTiming, KB lIf Z(m), Z'(m) conforms to the capability beamSwitchTiming reported by the UE, then (Z(m), Z'(m)) is defined as (Z3, Z'3) in CSI calculation delay requirement 2.

[0220] ◆ The codebookType is set to 'typeII-CJT-r18' or 'typeII-CJT-PortSelection-r18' and the corresponding NZP-CSI-RS-ResourceSet for channel measurement is 1 <N TRP When configured with ≦4 resources, (Z(m), Z'(m)) is defined as (Z2, Z'2) or (Z2+r, Z'2+r) according to the capabilities reported by the UE, using (Z2, Z'2) in CSI calculation delay requirement 2.

[0221] ◆If CSI reporting is configured with N4=1, and codebookType is set to 'typeII-Doppler-r18' or 'typeII-Doppler-PortSelection-r18', and the corresponding NZP-CSI-RS-ResourceSet for channel measurement is aperiodic (AP) with K CSI-RS resources, then (Z(m), Z'(m)) is defined as (Z2+14(K-1)m, Z'2) using (Z2, Z'2) in CSI calculation delay requirement 2.

[0222] ◆When CSI reporting is configured with N4=1, and codebookType is set to 'typeII-Doppler-r18' or 'typeII-Doppler-PortSelection-r18', and the corresponding NZP-CSI-RS-ResourceSet for channel measurement is periodic or semi-persistent (P or SP) with a single CSI-RS resource, (Z(m),Z'(m)) is defined as (Z2+w,Z'2) using (Z2,Z'2) in CSI calculation delay requirement 2.

[0223] ◆If CSI reporting is configured with N4>1, and codebookType is set to 'typeII-Doppler-r18' or 'typeII-Doppler-PortSelection-r18', and the corresponding NZP-CSI-RS-ResourceSet for channel measurement is aperiodic (AP) with K CSI-RS resources, then (Z(m),Z'(m)) is defined as (Z2+14(K-1)m,Z'2) or (Z2+14(K-1)m+r,Z'2+r) according to the capability reported by the UE using (Z2,Z'2) in CSI calculation delay requirement 2.

[0224] ◆If CSI reporting is configured with N4>1, and codebookType is set to 'typeII-Doppler-r18' or 'typeII-Doppler-PortSelection-r18', and the corresponding NZP-CSI-RS-ResourceSet for channel measurement is periodic or semi-persistent (P or SP) with a single CSI-RS resource, then (Z(m), Z'(m)) is defined as (Z2+w, Z'2) according to the capabilities reported by the UE, using (Z2, Z'2) in CSI computation delay requirement 2. It is also defined as (Z2+14(K-1)m, Z'2) or (Z2+14(K-1)m+r, Z'2+r) according to the capabilities reported by the UE.

[0225] ◆ In other cases, (Z(m),Z'(m)) are given by the specification table.

[0226] ◆μ for CSI calculation delay requirements 1 and 2 is min(μ PDCCH ,μ CSI-RS ,μ UL ) where μ PDCCH corresponds to the subcarrier spacing of the PDCCH on which the DCI is transmitted. UL μ corresponds to the subcarrier spacing of the PUSCH over which the CSI report will be transmitted. CSI-RS corresponds to the minimum subcarrier spacing of the AP CSI-RS triggered by DCI.

[0227] X μ The beamReportTiming field follows the UE reported capability beamReportTiming, which indicates the number of OFDM symbols between the end of the last SSB / CSI-RS symbol and the start of the first symbol of the transmission channel containing the beam report. The UE provides the capability for the band number for which reporting is provided (measurements are made). The UE includes this field for each supported subcarrier spacing.

[0228] KB l follows the UE reported capability beamSwitchTiming. beamSwitchTiming indicates the minimum number of OFDM symbols between the AP CSI-RS DCI triggering and the AP CSI-RS transmission. The number of OFDM symbols is measured from the end of the last symbol containing the indication to the start of the first CSI-RS symbol. The UE includes this field for each supported subcarrier spacing.

[0229] In this disclosure, the number of symbols from the end of the last symbol of the PDCCH that triggers a CSI report to the symbol at which UL transmission of the CSI report can start, the UE CSI calculation time, the CSI calculation time, the CSI processing time, the [CSI processing] timeline, and Z ref , Z' ref At least one of (n), Z, Z', Z(m), Z'(m), Z1, Z'1, Z2, Z'2, Z3, Z'3, (Z,Z'), (Z(m),Z'(m)), (Z1,Z'1), (Z2,Z'2), and (Z3,Z'3) may be read interchangeably.

[0230] (analysis) In conventional AP CSI reporting, the UE starts measuring / calculating CSI after DCI triggering. The CPU occupancy time period includes the time for CMR measurement, CSI calculation, and preparation for reporting.

[0231] As in the example of FIG. 7A, when the reportQuantity in the CSI report configuration is not 'none', the CPU occupancy period for the CSI report is from the end of the PDCCH (DCI) that triggers the CSI report to the end of the PUSCH that carries the CSI report. ref For P / SP CMR, the CSI calculation time from the end of the CMR for that CSI report to the start of the PUSCH for that CSI report (CSI calculation delay requirement from measurement to report) is equal to or greater than Z' [symbols]. For AP CMR, the CSI calculation time from the end of the CMR for that CSI report to the start of the PUSCH for that CSI report (CSI calculation delay requirement from measurement to report) is equal to or greater than Z' ref [Symbol] That's it.

[0232] As in the example of Figure 7B, when reportQuantity in the CSI reporting configuration is 'none', the CPU occupancy time period for the CSI report is from the end of the PDCCH that triggers the CSI report to the latest of either Z3 symbols after the end of the PDCCH (CSI calculation delay requirement from triggering to reporting) or Z'3 symbols after the end of the latest CMR (CSI calculation delay requirement from measurement to reporting).

[0233] Major differences between the UEIBR and existing AP CSI reports include: ◆In the UE IBR, CSI measurements may occur before the report triggering signaling. In existing AP CSI reporting, CSI measurement occurs only after report triggering signaling.

[0234] Other differences include: ◆ In the UEIBR, a measurement window for the UEIBR is defined. ◆In UE IBR, even if an event is triggered, the UE may wait a long time to transmit on the first PUCCH resource depending on the configuration of the first PUCCH. ◆In UEIBR, measurements are based solely on P-CMR.

[0235] It is unclear whether the CPU occupancy time period includes CSI measurements before the reporting triggering signaling for the UE IBR.

[0236] Therefore, the present inventors came up with the idea of ​​a CPU occupation method for UEIBR.

[0237] Hereinafter, embodiments according to the present disclosure will be described in detail with reference to the drawings. Wireless communication methods according to the embodiments may be applied independently or in combination.

[0238] (Various reading changes) In this disclosure, words enclosed in "()" in a sentence may indicate an explanation of the immediately preceding wording (for example, an explanation of spelling), a paraphrase, a specific example, a supplementary explanation, etc. Also, in this disclosure, words enclosed in "[ ]" in a sentence may be interpreted including the meaning of the entire sentence, or may be interpreted excluding the meaning of the entire sentence (ignoring the meaning of the entire sentence). Note that "()" and "[ ]" may also be used for purposes / meanings other than those mentioned above.

[0239] In the present disclosure, "A / B" and "at least one of A and B" may be interpreted interchangeably. Also, in the present disclosure, "A / B / C" may mean "at least one of A, B, and C."

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

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

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

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

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

[0245] In the present disclosure, ceil(x), ceiling function, and ceiling function may be interchangeable. In the present disclosure, floor(x), floor function, and floor function may be interchangeable. In the present disclosure, ceil(x) and floor(x) may be interchangeable. In the present disclosure, sqrt(x), square root of x, and root x may be interchangeable. In the present disclosure, x mod y, mod(x,y), mod function, and modulo operation may be interchangeable. In the present disclosure, Σ i=M M+N-1 f(i),Σ i=M M+N-1 f i , f(i) or f for i=M, M+1,..., M+N-1 i summation of f(M)+f(M+1)+...+f(M+N-1), f M +f M+1 +...+f M+N-1 , may be read interchangeably. C(n,k) is the number of combinations of k values ​​selected from n values ​​(combinatorial coefficient), binomial coefficients, n C k , C n k , may be read as interchangeable. In the present disclosure, x / / y and floor(x / y) may be read as interchangeable.

[0246] In this disclosure, A b , A_b, Ab, and A with b added to the bottom right may be read interchangeably. c , A^c, and the notation of A with c added to the upper right may be read interchangeably. b c, A_b^c, and the notation in which b is added to the bottom right of A and c is added to the top right of A may be read interchangeably. ~ may be expressed by adding 〜 to the x, or may be referred to as x tilde. - may be represented by placing a - on top of the x, or may be referred to as an x-bar. ^ may be represented by placing a ^ above the x, or may be called an x-hat.

[0247] In the present disclosure, FR may be, for example, at least one of FR1, FR2, FR2-1, FR2-2, FR3, sub-terahertz, and terahertz. In the present disclosure, the frequency range corresponding to FR1 may be 410-7125 MHz. In the present disclosure, FR2 may include FR2-1 and FR2-2, and the frequency range corresponding to FR2-1 may be 24250-52600 MHz, and the frequency range corresponding to FR2-1 may be 52600-71000 MHz.

[0248] In this disclosure, the terms event-based beam reporting (for Rel. 19), event-triggered beam reporting, event-driven beam reporting, UE-triggered beam reporting, UE-initiated beam reporting (UEIBR), UE-initiated beam management (UEIBM), beam reporting, CSI reporting, UEIBR, CSI for UEIBR, UEIBR-CSI, UEIBR-UCI, reporting, MAC CE, beam reporting MAC CE, UCI, CSI, PUSCH may be read interchangeably. In this disclosure, CSI / UCI for UEIBR may be referred to as UEIBR-CSI / UCI.

[0249] In the present disclosure, UEIBR, [UE-initiated] beam report / CSI report, and event-based beam report may be read interchangeably.

[0250] In this disclosure, the terms "first UL channel," "first PUCCH [transmission / resource / occasion]," and "PUCCH triggering a UEIBR" may be interchangeable. In this disclosure, the terms "second UL channel," "second PUSCH," and "PUSCH carrying a UEIBR" may be interchangeable.

[0251] In the present disclosure, an event [occurrence] and an [event] [occurrence / trigger] condition may be interpreted as interchangeable. In the present disclosure, an event occurs, an event condition is satisfied, a UEIBR is triggered, a first PUCCH is transmitted, and transmission is performed on a first PUCCH resource may be interpreted as interchangeable.

[0252] In the present disclosure, the terms "time window" and "measurement window" may be read interchangeably.

[0253] In the present disclosure, the report triggering signaling, the first PUCCH, and the DCI / PDCCH that schedules the second PUSCH may be read interchangeably.

[0254] (Wireless communication method) The UE may receive a configuration / instruction for a UEIBR (beam report). The UE / BS may determine a CPU occupancy time period for the UEIBR based on at least one of a first PUCCH triggering the UEIBR, a second PUSCH carrying the UEIBR, one CMR among one or more CMRs for measurement of the UEIBR, and signaling for the UEIBR.

[0255] <Embodiment 1> The first embodiment relates to a CPU occupancy period for the UEIBR.

[0256] The CPU occupation time period for the UEIBR may consider only the time after the report triggering signaling. The CPU occupation time period for the UEIBR may not include the time before the report triggering signaling.

[0257] The start timing of the CPU occupancy period may be the first or last symbol of the first PUCCH transmission that triggers the UEIBR.

[0258] The end timing of the CPU occupancy time period may be the last symbol of the second PUSCH corresponding to the first PUCCH.

[0259] Its start timing and its end timing may apply only to Mode B. The CPU occupation time period for Mode A may follow the CPU occupation time period of the [existing] AP CSI report triggered by DCI.

[0260] As in the example of Figure 8A, if the event condition is met, the CPU occupation time period may be from the start of the first PUCCH transmission to the end of the second PUSCH. As in the example of Figure 8B, if the event condition is met in Mode A, the CPU occupation time period may be from the start of the first PUCCH transmission that schedules the second PUSCH to the end of the second PUSCH. As in the example of Figure 9, if the event condition is not met, the CPU occupation time period may not start.

[0261] According to embodiment 1, the UE / BS can determine, in the UEIBR, an appropriate CPU occupation time period after the triggering of the UEIBR.

[0262] <Embodiment 2> The second embodiment relates to a CPU occupancy period for the UEIBR.

[0263] The CPU occupation time period for a UEIBR may take into account the time before the report triggering signaling. One CPU occupation time period may be defined for one UEIBR.

[0264] The start timing of the CPU occupancy period may be the first or last symbol of the earliest CMR for measurement / evaluation of the UEIBR.

[0265] The start timing of the CPU occupancy time period may be determined by explicit signaling / instruction from the NW to the UE, for example, the signaling may be an RRC configuration of the UE / BR, an activation command of the UE / BR, etc.

[0266] The start timing of the CPU occupation time may be the first symbol (first symbol) of the earliest CMR for UE-IBR measurement / evaluation after receiving at least one of the UE-IBR RRC configuration or UE-IBR activation command, or the first symbol (second symbol) of the earliest CMR for UE-IBR measurement / evaluation after the previous UE-IBR transmission. The first UE-IBR CPU occupation time period after the UE-IBR RRC configuration is applied / received may start at the first symbol (first symbol) of the earliest CMR for UE-IBR measurement / evaluation after receiving at least one of the UE-IBR RRC configuration or UE-IBR activation command. Subsequent UE-IBR CPU occupation time periods may start at the first symbol (second symbol) of the earliest CMR for UE-IBR measurement / evaluation after the previous UE-IBR transmission.

[0267] The end timing of the CPU occupancy period may be the last symbol of the corresponding second PUSCH, which may mean that if the UEIBR is not triggered, the CPU occupancy period continues until the UEIBR is triggered.

[0268] The timing of the end of the CPU occupation time period may be based on at least one of the following variations x:

[0269] ◆ Variation 1: If no transmission is made on the first PUCCH resource (if the UEIBR is not triggered, if the event conditions are not met), the end timing may be one of the following multiple options x: -◆Option 1: The first or last symbol of the first PUCCH resource. -◆Option 2: Z'3 symbols after the last symbol of the last CMR before that first PUCCH resource. -◆Option 3: Z'3 symbols after the last symbol of the last CMR in the measurement window.

[0270] ◆ Variation 2: When transmission is performed on the first PUCCH resource (when a UEIBR is triggered, when the event conditions are met), the end timing may be one of the following multiple options x: -◆Option 1: The last symbol of the corresponding second PUSCH transmission [for that first PUCCH resource]. - ◆ Option 2: In Mode A, the first or last symbol of the first PUCCH resource. In the subsequent procedure of DCI triggering of the UE IBR, another CPU occupation time period in the existing specifications may be used.

[0271] As in the example of Figure 10, a CPU occupation period may start at the start of the earliest CMR for measurement / evaluation of the UEIBR, and if an event condition is met, the CPU occupation period may end at the end of the second PUSCH corresponding to the event.

[0272] According to embodiment 2, the UE / BS can determine, in the UEIBR, an appropriate CPU occupation time period, including the time before the triggering of the UEIBR.

[0273] <Variations of the Second Embodiment> The CPU occupation time period for a UEIBR may take into account the time before the report triggering signaling. One CPU occupation time period may be defined for one UEIBR.

[0274] For multiple CMRs for measuring / evaluating UE IBR and multiple periodic first PUCCH resources (transmission occasions), the start timing of the CPU occupancy time period may be the first or last symbol of the Xth CMR before each first PUCCH resource (transmission occasion), or the first or last symbol of the Xth CMR after each first PUCCH resource (transmission occasion). X may be defined in the specification, may be configured, or may be reported as a UE capability.

[0275] The end timing of the CPU occupation time period may be the same as in the second embodiment.

[0276] As in the example of Figure 11, the first PUCCH resource may be configured / arranged periodically. A CPU occupation time period may start at the start of the Xth CMR before the first PUCCH resource (transmission occasion). If the condition of an event (based on measuring the CMR corresponding to that first PUCCH resource) is met, the CPU occupation time period may end at the end of the second PUSCH corresponding to that event. If the condition of an event (based on measuring the CMR corresponding to that first PUCCH resource) is not met, the CPU occupation time period may end at the end of that first PUCCH resource.

[0277] According to a variation of embodiment 2, the UE / BS can determine, in the UEIBR, an appropriate CPU occupation time period that includes the time before the triggering of the UEIBR.

[0278] <Embodiment 3> Embodiment 3 relates to a CPU occupancy period for the UEIBR.

[0279] The CPU occupation time period for a UEIBR may take into account the time before the report triggering signaling. Two CPU occupation time periods (a first CPU occupation time period and a second CPU occupation time period) may be defined for one UEIBR.

[0280] The start timing of the first CPU occupancy time period may be the first or last symbol of the earliest CMR for measurement / evaluation of the UEIBR.

[0281] The end timing of the first CPU occupation time period and the second CPU occupation time period may be based on at least one of the following multiple definitions x:

[0282] ◆Definition 1: When an event condition is met, the end timing of the first CPU occupancy time period may be Z'3 symbols after the last symbol of the last CMR before the condition is met. [Assuming there is no CSI measurement thereafter while the UE is waiting for the first PUCCH resource,] The second CPU occupancy time period may be based on at least one of the following timings: -◆ The start timing of the second CPU occupied time period may be the first or last symbol of the first PUCCH transmission that triggers the UEIBR. The start timing may apply only to Mode B. For Mode A, the start timing of the second CPU occupied time period may follow the start timing of the CPU occupied time period for the [existing] AP CSI report triggered by the DCI. - The end timing of the second CPU occupancy time period may be the last symbol of the second PUSCH corresponding to the event / first PUCCH resource.

[0283] ◆Definition 2: If the condition of the event is not satisfied, the end timing of the first CPU occupation time period may be the last symbol of the second PUSCH corresponding to the event / first PUCCH resource. This end timing may mean that the first CPU occupation time period continues until the condition of the event is satisfied and the UEIBR is triggered.

[0284] As shown in the example of FIG. 12, the first CPU occupation time period may start at the start of the earliest CMR for measurement / evaluation of the UEIBR. If an event condition is met, the first CPU occupation time period may end Z'3 symbols after the last symbol of the last CMR before the condition is met. Then, the second CPU occupation time period may start at the first symbol of the first PUCCH transmission that triggers the UEIBR. The second CPU occupation time period may end at the last symbol of the second PUSCH corresponding to the event / first PUCCH resource. The UE may not occupy the CPU for the UEIBR between the first and second CPU occupation time periods. The UE may retain information about the measurement result / event from the first to the second CPU occupation time period.

[0285] A CPU occupation time period including [first CPU occupation time period and second CPU occupation time period] may be defined using start and end timings similar to those of embodiment 2, by excluding the time period between Z'3 symbols after the last symbol of the last CMR before the condition is met and the first symbol of the first PUCCH that triggers the UEIBR.

[0286] According to embodiment 3, the UE / BS can determine, in the UEIBR, an appropriate CPU occupation time period, including the time before the triggering of the UEIBR.

[0287] <Variations on Embodiment 2 / Embodiment 3> In the second and third embodiments, the start timing of the CPU occupation time period may be the first or last symbol of the first PUCCH resource, or the first or last symbol of the second PUCCH resource, particularly for Mode B.

[0288] In the second and third embodiments, the timing of the start / end of the CPU occupation time period may be based on at least one of the following multiple variations x. ◆ Variation 1: The start / end timing is the timing (first or last symbol) of reception of MAC CE / DCI for TCI state activation / indication [following a counter reset condition]. ◆Variation 2: The start / end timing is the timing (first or last symbol) of receiving the RRC configuration for updating the CMR / CSI reporting configuration for the UE IBR.

[0289] <Embodiment 4> It is unclear what the CPU occupancy period will be after a UEIBR is sent, and whether the CPU will be released.

[0290] Embodiment 4 may assume one of the following options for the UEIBR: ◆ Option 1: When a UEIBR is RRC configured, the UE performs event evaluation until RRC reconfiguration. After sending a UEIBR for one trigger, the UE may continue event evaluation until RRC reconfiguration without the UEIBR. ◆ Option 2: When a UEIBR is RRC configured, the UE performs event evaluation until the UEIBR is successfully transmitted. The UE may stop event evaluation once the UEIBR is transmitted.

[0291] In option 1, after the UEIBR has been transmitted and the CPU released, the CPU occupancy period may be restarted at the first symbol of the first CMR for measurement and evaluation for the continuing UEIBR.

[0292] In option 2, after RRC reconfiguration for the UEIBR, the CPU occupancy period may start at the start timing of any of embodiments 1 to 3.

[0293] According to the fourth embodiment, the UE / BS can appropriately determine the CPU occupation time period after transmitting the UEIBR.

[0294] <Variations for Embodiment 1 to Embodiment 4> Among the above-described plurality of embodiments, which embodiment / option / choice / variation is applicable may depend on at least one of the following plurality of states x. ◆ State 1: Whether a time window and a counter [for UEIBR] are set. Or, whether the threshold value for the counter is 0, 1, or otherwise. ◆ State 2: Whether a prohibition timer for the first PUCCH resource associated with CMR is running. For example, when the prohibition timer is running, the CPU occupancy time period need not be managed. ◆ State 3: Whether the time gap between the first PUCCH resource and the second PUSCH resource is Z' [symbols] or more [especially for mode B]. For example, when the time gap is Z' [symbols] or more, Embodiment 1 may be applied. Otherwise, Embodiment 2 / Embodiment 3 may be applied.

[0295] <Supplementary> The above-described plurality of embodiments / options / choices / variations may be combined as one embodiment / option / choice / variation.

[0296] In the above embodiments, the measured RS may be the QCL source RS of the active TCI state / indicated (indicated / unified) TCI state.

[0297] <<Notification of Information to UE / BS>> In the above-described embodiments, notification of any information to the UE / BS [from a Network (NW) (e.g., a Base Station (BS)) / NW node] (in other words, reception of any information from the BS / NW node at the UE / BS) may be performed using physical layer signaling (e.g., DCI), higher layer signaling (e.g., RRC signaling, MAC CE, NAS signaling, LPP message, NRPPa message), specific signals / channels (e.g., PDCCH, PDSCH, reference signal), or a combination thereof.

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

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

[0300] In addition, notification of any information to the UE / BS in the above-described embodiments may be performed periodically, semi-persistently, or aperiodically. Notification of semi-persistent or aperiodically may be triggered by an instruction from the UE / BS / NW.

[0301] In the above-described embodiment, the information from the NW may be set / instructed by any one of the following methods or a combination thereof: Common to multiple UEs, or individual to each UE (per UE), Common to multiple BSs, or BS individual (per BS), ·Common to a plurality of frequencies (e.g., one or a combination of these such as a cell, a band, a band combination, a Bandwidth Part (BWP), a component carrier, etc.), or frequency-specific (per frequency, e.g., per cell).

[0302] In the above embodiments, the UE may receive at least one piece of information (QCL information) of some of the following QCL rules / QCL types from the NW. ◆QCL type A (Doppler shift, Doppler spread, average delay, and delay spread) ◆QCL type B (Doppler shift and Doppler spread) ◆QCL type C (Doppler shift and average delay) ◆QCL type D (spatial reception parameters)

[0303] In the above embodiments, the QCL source RS for each QCL type may be at least one of some of the following RSs. ◆SSB ◆CSI-RS with / without repetition ◆TRS ◆DMRS of PDCCH / PDSCH

[0304] In the above embodiments, the information from the NW may be set / instructed by the following methods. ◆Common to multiple UEs, or UE-specific ◆Cell-specific, or common to multiple cells ◆Per UE / CC / BWP / band / cell / cell group (CG)

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

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

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

[0308] In addition, any information notification from the UE / BS in the above-mentioned embodiments may be performed periodically, semi-persistently, or aperiodically. Notification of semi-persistent or aperiodic information may be triggered by an instruction from the UE / BS / NW.

[0309] <<Application of each embodiment>> In a UE / BS, a specific (e.g., one or more, or part of) process / operation / control / assumption / information of at least one of the above-described embodiments may be applied (used) when one or more of the following conditions are met: Upper layer parameters indicating the above specific processing / operation / control / assumment / information are set in the UE / BS; The specific processing / operation / control / assumption / information is determined in the UE / BS based on relevant higher layer parameters; The above specific process / operation / control / assumption / information is specified / activated / triggered to the UE / BS by the MAC CE / DCI / UCI / resource / channel / RS, The UE / BS reports or supports specific capabilities (e.g., UE capabilities) that indicate (or relate to) the specific processing / action / control / assumptions / information. The application of the above specific processing / operation / control / assumption / information is determined in the UE / BS based on specific conditions.

[0310] The specified capabilities may indicate at least one of the following: ◆Supporting the above specific processing / action / control / assuming / information, ◆Supporting CPU occupancy time period / CSI calculation delay requirements for UEIBR; ◆ Number of configurations / resources [sets] supported.

[0311] In the present disclosure, "supporting" and "whether to support" may be read interchangeably.

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

[0313] Furthermore, the above-mentioned specific capabilities may be capabilities that are applied across all duplexing methods (commonly regardless of the duplexing method), or may be capabilities for each duplexing method (for example, Time Division Duplex (TDD) or Frequency Division Duplex (FDD)).

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

[0315] (Addendum) The following inventions are added regarding one embodiment of the present disclosure. <Appendix 1> a receiving unit for receiving a beam report configuration initiated by a terminal; A terminal having a control unit that determines a time period for occupancy of a channel state information (CSI) processing unit for the beam report based on at least one of a physical uplink control channel (PUCCH) that triggers the beam report, a physical uplink shared channel (PUSCH) that carries the beam report, one channel measurement resource among one or more channel measurement resources for measuring the beam report, and signaling for the beam report. <Appendix 2> A terminal as described in Supplementary Note 1, wherein the time period does not include the time before triggering the beam report. <Appendix 3> 3. The terminal of claim 1 or 2, wherein the time period includes a time before triggering the beam report. <Appendix 4> A terminal described in any of Supplementary Note 1 to Supplementary Note 3, wherein the control unit evaluates events for the beam report until it is configured not to use the beam report or until it sends the beam report. <Appendix A> a transmitter for transmitting a beam report configuration initiated by a terminal; A base station having a control unit that determines a time period for occupancy of a channel state information (CSI) processing unit for the beam report based on at least one of a physical uplink control channel (PUCCH) that triggers the beam report, a physical uplink shared channel (PUSCH) that carries the beam report, one channel measurement resource among one or more channel measurement resources for measuring the beam report, and signaling for the beam report.

[0316] <Supplementary information> The terminal in Supplementary Notes 1 to 4 may be terminal 20. The receiver / transmitter in Supplementary Notes 1 to 4 may be transceiver 220. The controller in Supplementary Notes 1 to 4 may be controller 210. The base station in Supplementary Notes A may be base station 10. The receiver / transmitter in Supplementary Notes A may be transceiver 120. The controller in Supplementary Notes A may be controller 110.

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

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

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

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

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

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

[0323] 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 may be formed by multiple antennas / base stations 10. One [virtual] cell (which may be called, for example, a super cell) may be composed of multiple [virtual] cells (which may be called, for example, sub-cells). A super cell may correspond to a cell whose physical range is fixed, and a sub-cell may correspond to a cell whose physical range varies semi-statically / dynamically. In this case, the wireless communication system 1 may be called a cell-free system.

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

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

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

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

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

[0329] The core network 30 may include network functions (Network Functions (NFs)) such as a User Plane Function (UPF), an Access and Mobility management Function (AMF), a Session Management Function (SMF), a Unified Data Management (UDM), an Application Function (AF), a Data Network (DN), a Location Management Function (LMF), and Operation, Administration and Maintenance (Management) (OAM). Note that a single network node (which may simply be referred to as a node) may provide multiple functions. Furthermore, communication with an external network (e.g., the Internet) may be performed via the DN.

[0330] The terminal 20 may be a terminal compatible with at least one of communication methods such as LTE, LTE-A, and 5G.

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

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

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

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

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

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

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

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

[0339] One search space may correspond to PDCCH candidates corresponding to one or more aggregation levels. One or more search spaces may be called a search space set. Note that the terms "search space," "search space set," "search space setting," "search space set setting," "CORESET," "CORESET setting," etc. in the present disclosure may be read interchangeably.

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

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

[0342] 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, a cell-specific reference signal (CRS), a channel state information reference signal (CSI-RS), a demodulation reference signal (DMRS), a positioning reference signal (PRS), a phase tracking reference signal (PTRS), etc. may be transmitted as DL-RS.

[0343] 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 the SS (PSS, SSS) and the PBCH (and DMRS for the PBCH) may be referred to as an SS / PBCH block, an SS Block (SSB), or the like. Note that the SS, SSB, and the like may also be referred to as reference signals.

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

[0345] (base station) 14 is a diagram illustrating an example of the configuration of a base station according to an embodiment of the present disclosure. The base station 10 includes a control unit 110, a transceiver unit 120, a transceiver antenna 130, and a transmission line interface 140. Note that the base station may include one or more of each of the control unit 110, the transceiver unit 120, the transceiver antenna 130, and the transmission line interface 140.

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

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

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

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

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

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

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

[0353] The transceiver 120 may form at least one of a transmission beam and a reception beam using digital beamforming (for example, precoding), analog beamforming (for example, phase rotation), or the like.

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

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

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

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

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

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

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

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

[0362] 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 perform RF processing (digital beamforming, digital-to-analog conversion, analog beamforming, etc.) and lower-level functions of the physical layer (precoding, IFFT, FFT, etc.). The DU may perform higher-level functions of the physical layer (coding to resource element mapping, etc.), MAC layer functions, and RLC layer functions. The CU may perform PDCP layer, Service Data Adaptation Protocol (SDAP) layer, and RRC layer functions.

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

[0364] Furthermore, in the present disclosure, a network device (for example, an LMF node) having the functionality of any of the above-described NFs may be a device having the configuration (for example, the control unit 110 and the transceiver unit 120) of the base station 10. In other words, by replacing the base station with the network device, the configuration of the network device according to an embodiment of the present disclosure may be covered.

[0365] (Terminal) 15 is a diagram illustrating an example of the configuration of a terminal according to an embodiment of the present disclosure. The terminal 20 includes a control unit 210, a transceiver unit 220, and a transceiver antenna 230. Note that the terminal may include one or more of each of the control unit 210, the transceiver unit 220, and the transceiver antenna 230.

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

[0367] The control unit 210 performs overall control of the terminal 20. The control unit 210 can be configured from a controller, a control circuit, and the like that are explained based on common understanding in the technical field to which the present disclosure relates.

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

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

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

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

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

[0373] The transceiver 220 may form at least one of a transmission beam and a reception beam using digital beamforming (for example, precoding), analog beamforming (for example, phase rotation), or the like.

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

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

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

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

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

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

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

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

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

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

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

[0385] In the present disclosure, any two terms selected from a set of terms such as apparatus, circuit, device, section, unit, module, chip, means, etc. may be read as interchangeable. The hardware configurations of the base station 10 and the terminal 20 may be configured to include one or more of the devices shown in the drawings, or may be configured to exclude some of the devices.

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

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

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

[0389] The various processes described above may be performed by one processor 1001, or may be performed by two or more processors 1001 simultaneously, sequentially, or using other techniques. The processor 1001 may be implemented by one or more chips. The program may be transmitted from a network via a telecommunications line, or may be provided to the computer device via, for example, the communication device 1004.

[0390] The present disclosure also provides a computer program product including a computer program, which may implement the steps of the methods described in the above embodiments when the computer program is executed by a computer (e.g., the processor 1001).

[0391] The memory 1002 is a non-transitory computer-readable recording medium and may be configured, for example, by a read-only memory (ROM), an erasable programmable ROM (EPROM), an electrically EEPROM (EEPROM), a random access memory (RAM), or a combination of at least two of these. The memory 1002 may also be referred to as a register, a cache, a main memory, or the like. The memory 1002 may store executable programs (program codes), software modules, and the like for implementing a wireless communication method according to one embodiment of the present disclosure.

[0392] Storage 1003 is a non-transitory computer-readable recording medium, and may be, for example, a flexible disk, a floppy disk, an optical disk (e.g., a compact disc (e.g., a Compact Disc ROM (CD-ROM)), a digital versatile disc, a Blu-ray disc), a magneto-optical disk, a removable disk, a hard disk drive, a smart card, a flash memory (e.g., a card, stick, key drive), a magnetic stripe, or the like, or a combination of at least two of these. Storage 1003 may also be referred to as a secondary storage device.

[0393] The above-mentioned recording medium may be, for example, the memory 1002, the storage 1003, or a database including both the memory 1002 and the storage 1003, a server, or other suitable medium.

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

[0395] The input device 1005 is an input device that accepts input from the outside (for example, a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc., or a combination of at least two of these). The output device 1006 is an output device that performs output to the outside (for example, a display, a speaker, a Light Emitting Diode (LED) lamp, etc., or a combination of at least two of these). Note that the input device 1005 and the output device 1006 may be integrated into one device (for example, a touch panel).

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

[0397] Furthermore, base station 10 and 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), a field programmable gate array (FPGA), a graphics processing unit (GPU), a neural processing unit (NPU), or a combination of at least two of these, and some or all of the functional blocks may be realized using such hardware. For example, processor 1001 may be implemented using at least one of these hardware elements.

[0398] In this disclosure, the term "processor" may encompass a single processor or a group of multiple processors, including, for example, a single-core processor, a multi-core processor, multiple processors in a single device, multiple processors in wired or wireless communication with each other, etc. Similarly, the term "(non-transitory) computer-readable storage medium" may encompass a single storage medium or a group of multiple storage media, including multiple storage media in wired or wireless communication with each other.

[0399] Devices such as processors and storage media in the present disclosure may be distributed locally or remotely, and may perform the processing of the devices by operating cooperatively or independently using a bus, network, the Internet, the cloud, etc.

[0400] Note that the devices included in the core network 30 (for example, network nodes that provide NFs) may also be realized by the above-described functional block / hardware configuration.

[0401] (Variation) Each aspect / embodiment described in the present disclosure may be a mobile communication system other than Long Term Evolution (LTE), LTE-Advanced (LTE-A), International Mobile Telecommunications-Advanced (IMT-Advanced), 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 5G-Advanced (5G-A), 6th generation mobile communication system (6G), xth generation mobile communication system (xG (x is, for example, an integer or a decimal number)), Future Radio Access (FRA), New Radio (NR), New radio access (NX), Future generation radio access (FX), Open Radio Access Network (Open RAN (O-RAN)), Wideband Code Division Multiple Access (W-CDMA (registered trademark)), Global System for Mobile communications (GSM (registered trademark)), CDMA2000, Ultra Mobile Broadband (UMB), Institute of Electrical and Electronics Engineers (IEEE) 802.11, IEEE 802.11x (where x is any character string such as b, a, g, n, ac, ax, be, or bn, and when x = n, it is called Wi-Fi 4, when x = ac, it is called Wi-Fi 5, when x = ax, it is called Wi-Fi 6 or Wi-Fi 6E, when x = be, it is called Wi-Fi 7, and when x = bn, it is called Wi-Fi 8.Note that the present disclosure may be applied to systems based on technologies such as Wi-Fi (a registered trademark), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, Ultra-WideBand (UWB), Bluetooth (registered trademark), network virtualization technologies (e.g., Network Function Virtualization (NFV), Service Function Chaining (SFC), Software Defined Networking (SDN)), or Low Power Wide Area (LPWA). Furthermore, each aspect / embodiment described in the present disclosure may be applied to a system based on a combination of at least two of these technologies. Here, "based on" naturally refers not only to a system that uses the technology in question, but also to a system that uses an extension or modification of the technology.

[0402] In the present disclosure, any two terms selected from a set of terms such as "Base Station (BS)", "Radio Base Station", "Fixed Station", "NodeB", "eNodeB (eNB)", "gNodeB (gNB)", "Access Point (AP)", "Transmission Point (TP)", "Reception Point (RP)", "Transmission / Reception Point (TRP)", "Radio Unit (RU)", "Remote Unit (RU)", "Control Unit (CU)", "Distributed Unit (DU)", "Remote Radio Head (RRH)", "node", "gateway", "terrestrial base station", "stratospheric base station", "unmanned aerial vehicle", "High Altitude Platform Station (HAPS)", "airborne platform", "panel", "cell", "Radio Access Network (RAN)", "network", etc. may be used interchangeably. Each cell accommodated by a base station may be referred to by terms such as a macro cell, a small cell, a femto cell, a pico cell, a serving cell, a super cell, etc. In the present disclosure, any two terms selected from a set of terms such as "cell," "sector," "cell group," "carrier," "component carrier," "cluster," "bandwidth part (BWP)," and "carrier bandwidth" may be used interchangeably.

[0403] In the present disclosure, any two terms selected from the set of terms such as "Mobile Station (MS)", "user terminal", "User Equipment (UE)", "Device", "Module", "Terminal", etc. may be used interchangeably.

[0404] A terminal may be referred to as a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, router (e.g., home router, mobile router, etc.), Telematics Control Unit (TCU), or some other suitable terminology.

[0405] The base station and the terminal may each be composed of one or more devices. The devices constituting at least a part of the base station and the terminal may be called a transmitting device, a receiving device, a [wireless] communication device, etc. In addition, the devices constituting at least a portion of each of the base stations and terminals may be objects themselves, such as vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, handcars, rickshaws, ships and other watercraft, airplanes, rockets, unmanned aerial vehicles, stratospheric base stations (e.g., High Altitude Platform Stations (HAPS)), artificial satellites (e.g., Low Earth Orbit (LEO) satellites, Middle Earth Orbit (MEO) satellites, Geostationary Earth Orbit (GEO) satellites), drones (registered trademark), multicopters, quadcopters, balloons, Internet of Things (IoT) equipment (e.g., smart meters, sensors), etc., or may include, but are not limited to, objects or devices mounted on such objects. Furthermore, the object may be a moving object (hereinafter referred to as a "moving object"; this does not exclude the case where the moving object is stationary and not moving), or may be a fixedly positioned object (hereinafter referred to as a "non-moving object").

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

[0407] The present disclosure is also applicable to cases where at least some of the devices constituting the base station and the terminal operate outside the earth (for example, in the atmosphere or outer space).

[0408] Similarly, the term "terminal" in the present disclosure may be read as "base station." In this case, the base station 10 may be configured to have the functions of the terminal 20 described above.

[0409] In the present disclosure, an operation described as being performed by a base station may be performed by its upper node or by some of its upper nodes (e.g., CU, RU, DU, etc.) in some cases. It is clear that various operations performed for communication with a terminal in a RAN or core network may be performed by at least some of the base station and other network nodes other than the base station. The other network node may be one node or a combination of multiple nodes. The network node is, for example, a node provided in various core networks such as an Evolved Packet Core (EPC) or a 5G Core Network (5GCN, 5GC), and provides one or more network functions (Network Functions (NFs)), but is not limited to these.

[0410] Furthermore, in the present disclosure, the operation of "a terminal receives information from a base station" accompanies the operation of "the base station transmits the information to the terminal," "the base station generates the information," or both. Similarly, the operation of "a terminal transmits information to a base station" accompanies the operation of "the base station receives the information from the terminal." Furthermore, operations such as "a terminal is configured to ..." or "configure UE to ..." may include the operation of "a base station transmits configuration information regarding the configuration of the terminal" or "a terminal configures a predetermined operation based on the configuration information."

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

[0412] The physical layer signaling may be referred to as Layer 1 (L1) control information. The MAC signaling may be referred to as, for example, a MAC Control Element (CE) or a MAC Protocol Data Unit (PDU). The RRC signaling may be referred to as an RRC message or an information element (IE) in the RRC message. The RRC signaling may be, for example, a message used for controlling an RRC connection (e.g., setup, reconfiguration, establishment, reestablishment, release, or resume), mobility, a measurement report, notification of terminal capabilities, or an information element in the message.

[0413] Furthermore, notification of information may be either explicit or implicit. Note that an explicit notification of certain information means notification of the certain information itself, and an implicit notification of certain information may mean notification of information other than the certain information, or the certain information being deemed to have been notified when a certain condition is met.

[0414] Furthermore, notification of information may include not only notification between the same layers of different devices (for example, between a lower layer or an upper layer of the base station 10 and the terminal 20) but also notification between different layers in the same or different devices (for example, between a lower layer and an upper layer in the base station 10 or the terminal 20). Furthermore, notification of information from one device to another device may be performed via one or more devices.

[0415] With respect to any information (e.g., variables, constants, parameters, settings) described in the present disclosure, even if not specifically stated in the above embodiments, any first device (e.g., terminal / base station) may notify any second device (e.g., base station / terminal) of information indicating / identifying (or relating to) the value of the any information.

[0416] Each aspect / embodiment described in this disclosure may be used alone, in combination, or switched depending on the implementation. Furthermore, the order of the procedures, sequences, flowcharts, etc. of each aspect / embodiment described in this disclosure may be changed as long as it is consistent. For example, the methods described in this disclosure present various step elements using an exemplary order and are not limited to the particular order presented. Furthermore, at least one step may be omitted in the procedures, sequences, flowcharts, etc. of each aspect / embodiment described in this disclosure.

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

[0418] In the present disclosure, a radio resource may be defined by a combination of resource units in one or more domains, such as the time domain, the frequency domain, the spatial domain, the code domain, and the power domain.

[0419] For example, a resource in the time domain (which may be referred to as a time resource) may be defined by one or more time units. The one or more time units may include, but are not limited to, a radio frame, a subframe, a slot, a symbol, a transmission time interval (TTI), or a combination of at least two of these. Furthermore, the time unit may be a fixed-length time unit that is independent of numerology, a variable-length time unit that is dependent on numerology, or both.

[0420] Examples of fixed-length time units include, but are not limited to, subframes each consisting of one or more slots and radio frames each including multiple subframes. Examples of variable-length time units include, but are not limited to, symbols and slots each including a fixed number of symbols. A certain time unit may be divided into time units shorter than the certain time unit. Examples of such shorter time units include, but are not limited to, minislots each consisting of fewer symbols than the number of symbols that make up a slot. The above-described time units may include time units used as units for scheduling, link adaptation, and the like. Any time unit in the present disclosure may be interchangeable with another time unit.

[0421] Numerology is a parameter that defines the physical layer structure, and may be a parameter based on at least one of the subcarrier spacing (SCS), the symbol length, the cyclic prefix length, and the sampling time, for example.

[0422] A resource in the frequency domain (which may also be referred to as a frequency resource) may be defined by, for example, one or more frequency units. The one or more frequency units may include, for example, a subcarrier, a resource block (RB), a bandwidth part (BWP), a carrier bandwidth, or a combination of at least two of these, but the name of the frequency unit is not limited to these. Furthermore, the number of subcarriers included in a certain frequency unit may be a fixed number regardless of numerology, or may be a variable number that changes depending on numerology.

[0423] For example, an RB is composed of a predetermined number of consecutive subcarriers in the frequency domain, and the number of subcarriers included in the RB may be the same regardless of numerology, for example, 12, but is not limited to this. Also, a BWP may be composed of, for example, one or more consecutive RBs within a certain carrier bandwidth, but is not limited to this. One or more BWPs may be configured within one carrier for terminal 20, and at least one of the BWPs may be activated. Also, any frequency unit in the present disclosure may be interpreted as another frequency unit.

[0424] Furthermore, resources in both the time domain and the frequency domain may be defined by one or more time / frequency units each consisting of a time unit and a frequency unit, such as, but not limited to, a resource element (RE) consisting of one symbol and one subcarrier, a resource element group (REG) consisting of a predetermined number of REs, or a control resource set (CORESET) consisting of a predetermined number of symbols and a predetermined number of RBs.

[0425] The resources in the spatial domain (which may also be referred to as spatial resources) may be defined, for example, by one or more spatial units, including, but not limited to, beams, layers of Multi-Input Multi-Output (MIMO), antenna ports, etc., or a combination of at least two of them.

[0426] The resource in the code domain (which may also be referred to as a code resource) may be defined by, for example, one or more code units, including, but not limited to, a Cyclic Shift (CS), an Orthogonal Cover Code (OCC), or a combination thereof.

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

[0428] In the present disclosure, terms such as "decide," "determine," "judge," "select," "specify," "compute," "calculate," "process," "derive," "look up / search / inquiry," "confirm," "assume," "expect," and "consider" may be read interchangeably. Also, in the present disclosure, performing a certain process (e.g., sending, receiving) may be read interchangeably as deciding to perform that process. Also, in the present disclosure, "not expected to do..." may be read interchangeably as "assumed not to do...."

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

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

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

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

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

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

[0435] In the present disclosure, an antenna port may be interchangeably read as an antenna port for any signal / channel (e.g., a Demodulation Reference Signal (DMRS) port). In the present disclosure, a resource may be interchangeably read as a resource for any signal / channel (e.g., a reference signal resource). Furthermore, the spatial domain filter may include at least one of a spatial domain transmission filter and a spatial domain reception filter.

[0436] In the present disclosure, beam, sounding reference signal (SRS) resource indicator (SRS Resource Indicator (SRI)), control resource set (CONTROLLER RESOLUTION SET (CORESET)), CORESET pool, uplink shared channel (Physical Downlink Shared Channel (PDSCH)), uplink shared channel (Physical Uplink Shared Channel (PUSCH)), codeword (CW), transport block (TB), reference signal (RS), etc. may be interpreted as interchangeable.

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

[0438] Furthermore, in this disclosure, terms such as "QCL," "QCL assumptions," "QCL relationships," "QCL type information," "QCL properties," "specific QCL type (e.g., Type A, Type D) properties," and "specific QCL type (e.g., Type A, Type D)" may be interchangeable.

[0439] In this disclosure, terms such as index, identifier (ID), identity (ID), indicator, indication, resource ID, etc. may be interchangeable. In this disclosure, terms such as sequence, list, set, group, cluster, subset, etc. may be interchangeable.

[0440] In the present disclosure, a group may include, for example, at least one of a spatial relationship group, a Code Division Multiplexing (CDM) group, an RS group, a CORESET group, a Physical Uplink Control Channel (PUCCH) group, an antenna port group (e.g., a DMRS port group), a layer group, a resource group, a beam group, an antenna group, a panel group, and the like.

[0441] Information in this disclosure (e.g., variables, constants, parameters, settings) may be interchangeably read as the ID of the information. For example, TCI state and TCI state ID may be interchangeably read as the ID of the information. Also, information in this disclosure may be interchangeably read as "a set of the information," "one or more pieces of the information," etc.

[0442] Any signal / channel (e.g., PUCCH) in the present disclosure may be interchangeably read as another signal / channel (e.g., PUSCH, PDSCH, any RS). A signal / channel may be interchangeably read as a signal / channel for the same direction (e.g., UL if the certain signal / channel is in the UL direction, and DL if in the DL direction), or as a signal / channel for another direction (e.g., DL if the certain signal / channel is in the UL direction, and UL if in the DL direction). Also, in the present disclosure, descriptions related to DL communication and descriptions related to UL communication may be interchangeably read. In this case, DL (UL) operation may be interchangeably read as the corresponding UL (DL) operation. For example, reception of a PDSCH in a terminal may be interchangeably read as transmission of a PUSCH in the terminal.

[0443] In the present disclosure, terms such as "X's number," "X number," "the number of X(s)," and "a number of X(s)" may be interchangeable. Note that X here may be replaced with an appropriate expression such as a noun, a gerund, or an ordinary sentence, depending on the context. In the present disclosure, "number" may be interchangeable with terms such as maximum number, minimum number, average number, and total number. In addition, in the present disclosure, terms such as "value," "index," "number," and "quantity" may be interchangeable with each other.

[0444] Values / ranges in this disclosure may be interpreted as approximations, as if the words "about" or "approximately" were preceding the value / range. In this disclosure, "A and B are the same" (A and B are any words) may mean "A and B are identical," "A and B are almost the same," "A and B are partly the same (or partially overlapped)," "There is an error within a certain range between A and B," etc. (i.e., these words may be read interchangeably). Furthermore, in the present disclosure, A and B being the same may mean that at least part of A and at least part of B are the same (or overlapped).

[0445] In this disclosure, the terms "one embodiment," "some embodiments," "another embodiment," etc. may be used interchangeably. The appearances of phrases such as "one embodiment," "some embodiments," "another embodiment," etc. in this disclosure do not necessarily all refer to the same embodiment, nor are they necessarily meant to be mutually exclusive.

[0446] In the present disclosure, expressions such as "at least one of A and B," "at least one of A or B," "A and / or B," and "A / B" may be read interchangeably, and may be understood to include "only A," "only B," or "both A and B." Furthermore, in this disclosure, expressions such as "at least one of A, B, and C," "at least one of A, B, or C," "A, B and / or C," and "A / B / C" may be interpreted interchangeably and may be understood to include "only A," "only B," "only C," "A and B," "B and C," "C and A," or "all of A, B, and C." Note that similar interpretations / interpretations may be applied to any expression in this disclosure such as "at least X of ..." (where the number of elements in "..." and X are each any number).

[0447] In the present disclosure, expressions such as "A, [and] B, and the like" / "such as A [and] B"), "A, [or] B, or the like" / "such as A [or] B"), "A, B, etc." / "A, B, and so on" / "A, B, and so forth"," and "A, B, [and / or] the others" may be read interchangeably.

[0448] In the present disclosure, expressions representing one / single X (e.g., "a X," "one X," "a single X"), expressions representing one or more X (e.g., "one or more X(s)," "at least one of X(s)"), and expressions representing a plurality of X (e.g., "Xs," "more than one X(s)," "multiple X(s)," "a plurarity of X(s)") may be read interchangeably. Note that these expressions may also be read interchangeably with expressions that include specific wording (e.g., when X is an uncountable noun, "pieces of," "amount of," etc.). For example, "a plurality of pieces of spatial relation information" may be read interchangeably as "a plurality of spatial relation information."

[0449] The present disclosure has been described above, but it is for illustrative purposes only, and the present invention is not limited to the aspects / embodiments described in the present disclosure. The present disclosure can be implemented in modified and altered forms without departing from the spirit of the invention. The present disclosure and its modifications and alterations are included in the scope of the present invention and its equivalents.

Claims

1. a receiving unit for receiving a beam report configuration initiated by a terminal; A terminal having a control unit that determines a time period for occupancy of a channel state information (CSI) processing unit for the beam report based on at least one of a physical uplink control channel (PUCCH) that triggers the beam report, a physical uplink shared channel (PUSCH) that carries the beam report, one channel measurement resource among one or more channel measurement resources for measuring the beam report, and signaling for the beam report.

2. The terminal of claim 1 , wherein the time period does not include a time period before triggering the beam report.

3. The terminal of claim 1 , wherein the time period includes a time before triggering the beam report.

4. The terminal according to claim 1 , wherein the control unit evaluates an event for the beam report until the control unit is configured not to use the beam report or until the beam report is sent.

5. receiving a beam report configuration initiated by a terminal; A wireless communication method for a terminal, comprising: determining a time period for occupancy of a channel state information (CSI) processing unit for the beam report based on at least one of a physical uplink control channel (PUCCH) that triggers the beam report, a physical uplink shared channel (PUSCH) that carries the beam report, one channel measurement resource among one or more channel measurement resources for measuring the beam report, and signaling for the beam report.

6. a transmitter for transmitting a beam report configuration initiated by a terminal; A base station having a control unit that determines a time period for occupancy of a channel state information (CSI) processing unit for the beam report based on at least one of a physical uplink control channel (PUCCH) that triggers the beam report, a physical uplink shared channel (PUSCH) that carries the beam report, one channel measurement resource among one or more channel measurement resources for measuring the beam report, and signaling for the beam report.

Images