Terminal, wireless communication method, and base station

Abstract

A terminal according to one aspect disclosed herein comprises: a control unit for controlling a beam report, started by the terminal, on the basis of the number of event instances within a time window; and a transmission unit for transmitting the beam report. When the event instances for at least one reference signal exceed a specific number and the beam report is performed for a plurality of reference signals, the control unit controls so that a report value corresponding to at least one among the range of the number of event instances and the specific number is included in the beam report for each of the reference signals.

Description

Terminal, Wireless Communication Method, and Base Station

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

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

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

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

[0005] In future wireless communication systems (for example, NR, Rel. 19 and later), it is being considered to support beam reporting (or, may also be called event-triggered beam reporting / UE-initiated Beam Report (UEIBR)) initiated by a terminal (user terminal, User Equipment (UE)) based on an event.

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

[0007] However, there are cases where such beam reporting has not been adequately considered. For example, sufficient consideration has not been given to what information should be included in beam reporting. If appropriate information is not included in beam reporting, UE-led beam reporting may not be performed properly, potentially hindering improvements in communication quality and throughput.

[0008] Therefore, one of the objectives of this disclosure is to provide a terminal, a wireless communication method, and a base station that can appropriately perform UE-led beam reporting.

[0009] A terminal according to one aspect of the present disclosure includes a control unit that controls a beam report initiated by the terminal based on the number of event instances within a time window, and a transmission unit that transmits the beam report, wherein, if the number of event instances for at least one reference signal exceeds a certain number and the beam report is to be performed for multiple reference signals, the control unit controls the beam report to include a report value for each reference signal that corresponds to at least one of the range of the number of event instances and the certain number.

[0010] According to one aspect of this disclosure, UE-led beam reporting can be appropriately conducted.

[0011] Figure 1A shows an example of UE movement in Rel. 17. Figure 1B shows an example of UE movement in Rel. 18. Figure 2 shows an example of a timer / counter related to the UEIBR. Figure 3 shows an example of beam reporting with Mode A applied. Figure 4 shows an example of beam reporting with Mode B applied. Figure 5 shows an example of beam reporting with Mode A applied according to the embodiment. Figure 6 shows an example of beam reporting with Mode B applied according to the embodiment. Figures 7A-7C show an example of mapping / association between reported values ​​and event instance ranges according to the embodiment. Figures 8A-8C show other examples of mapping / association between reported values ​​and event instance ranges according to the embodiment. Figures 9A-9C show other examples of mapping / association between reported values ​​and event instance ranges according to the embodiment. Figure 10 shows an example of a schematic configuration of a wireless communication system according to one embodiment. Figure 11 shows an example of a base station configuration according to one embodiment. Figure 12 shows an example of a user terminal configuration according to one embodiment. Figure 13 shows an example of the hardware configuration of a base station and user terminal according to one embodiment. Figure 14 shows an example of a vehicle according to one embodiment.

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

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

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

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

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

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

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

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

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

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

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

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

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

[0025] The UE may report the measurement results (e.g., at least L1-RSRP / L1-SINR and the corresponding resource indicator / RS index) to the NW when a specific event occurs (which may be interpreted in this disclosure as a specific condition being met / not met, a specific event being matched, etc.).

[0026] The specific event may be, for example, at least one of an event relating to a serving cell and an additional cell, and at least one of an event relating to a beam report including at least one of the PCI of the serving cell and the PCI of the additional cell.

[0027] <UEIBR Trigger Conditions / Events for Rel. 19> The UEIBR may be triggered when certain conditions (events) are met. For example, the UE may apply different / same conditions / events to the triggers of the following beam reports.

[0028] UE Feature #1: UEIBR for MIMO in Rel. 19. UE Feature #2: UEIBR for mobility in Rel. 19.

[0029] Different UE capabilities may be introduced / defined between UE features #1 and #2. Furthermore, different higher-level parameters may be set to enable each UE feature. UE features and UE capabilities may be interchangeable.

[0030] UE does not expect UE features #1 and #2 to be set simultaneously in a given BWP / CC / band / frequency range / frequency (or per UE).

[0031] A UE may have UE features #1 and #2 set simultaneously in a given BWP / CC / band / frequency range / frequency (or per UE). For example, a UE may have predefined which events (which UE features) to prioritize, if set, and this may be set / instructed by upper-layer signaling / physical-layer signaling.

[0032] This disclosure may be applied within the Unified TCI Framework.

[0033] This disclosure may apply only if the corresponding UE capability is reported, or if the corresponding higher-layer parameter (e.g., RRC) is notified / reported.

[0034] <UEIBR for MIMO> The following may apply to the UEIBR for MIMO in Rel. 19.

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

[0036] The report content may be essentially the same as existing L1 beam measurement reports, and may include at least one of the following, for example: • SSBRI / CRI. • Number of beams to be reported (X). • Method for selecting X beams. • L1-RSRP / SINR (absolute value / difference value) for each SSBRI / CRI. If MAC CE is used, • Indicator indicating whether the following octets are included. If MAC CE / UCI is used, • Serving cell ID, BWP ID (if the report requires activation of the TCI state or beam switching).

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

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

[0039] Priorities may be assigned to events 1 through 9. For example, one of events 1 through 9 (e.g., event 2) may have the highest priority (e.g., event 2 may be given priority in the decision-making process).

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

[0041] 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 becomes the QCL RS of the indicated TCI state and the QCLed SSB. - Beam Option 2c: The RS corresponding to the current beam is [explicitly] set / indicated using RRC signaling / MAC CE.

[0042] 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 [explicitly] set using RRC signaling (e.g., resetting of existing RS measurements, or setting parameters of the TCI state (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 activated TCI state (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 a set subset of the list of TCI states set by RRC (set TCI state).

[0043] The explicit RS setting for the new beam in Event 2 may be set in one RS resource set associated with the CSI report setting.

[0044] At this time, if the existing UE capabilities cannot be reused, UE capabilities indicating the maximum number of RSs set within the RS resource set may be defined / introduced.

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

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

[0047] <UEIB for Mobility> For UEIB for mobility (e.g., LTM) in Rel. 19, the following may apply.

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

[0049] The content of the report may include, for example, at least one of the following. When the measurement report is used for cell switching report, in addition to MIMO-related information, - An indicator indicating the presence or absence of cell switching, or TA-related information. Otherwise (when the measurement report is not used for cell switching report), - The same content as MIMO-related information (may only differ in terms of being within-cell / between-cells).

[0050] The supported events may be the same as Conditional Hand-Over (CHO).

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

[0052] When the report is used for cell switching commands, to prevent frequent switching, a specific domain filter (e.g., time / frequency / space) may be considered / applied.

[0053] Whether flexibility in the triggering time (e.g., 5 milliseconds, 10 milliseconds, 20 milliseconds) is required may be defined.

[0054] In the case of L1 measurement by UEIB, at least the results of beam-level measurement may be used for event evaluation.

[0055] Events related to UEIBR for mobility may be broadly categorized into the following event types: • Event LTM2: The serving cell's beam quality falls below an (absolute) threshold. • Event LTM3: The candidate cell's beam quality improves beyond a certain offset amount compared to the serving cell's beam quality. • Event LTM4: The candidate cell's beam quality falls below an (absolute) threshold. • Event LTM5: The serving cell's beam quality falls below a first (absolute) threshold, AND the candidate cell's beam quality improves above a second (absolute) threshold.

[0056] It should be noted that the events exemplified in this way do not exclude other events. Furthermore, the MIMO-oriented events described above may be reused as appropriate (in this case, "current beam" may be replaced with "serving cell beam," and "new beam" with "candidate cell beam"). These reused / re-interpreted events may be called mobility / LTM-oriented events corresponding to MIMO-oriented events.

[0057] In the LTM configuration, the L1 measurement resource setting may support both SSB and CSI-RS beam settings.

[0058] In events LTM3 and LTM5, the same type of RS (e.g., CSI-RS / SSB) may be used for both the serving cell and the candidate cell (adjacent cell).

[0059] In mobility event evaluation, at least one of the following may be applied: TimeToTrigger (TTT), hysteresis for entering / leaving, and beam-specific / cell-specific offsets.

[0060] UEIBR for mobility may be transmitted using MAC CE.

[0061] <Definition of wording for specific events> In the existing events described above, the definitions of Serving [cell] and Neighbor [cell] may be reinterpreted / updated as follows in the UEIBR for Rel. 19.

[0062] For example, in existing L3 events, Serving [Cell], SpCell, and PCell may be interpreted interchangeably with the current beam (e.g., the RS ID associated with the indicated [Joint / DL]TCI state) in event-triggered beam reports for MIMO in Rel. 19.

[0063] Furthermore, in existing L3 events, Serving [Cell], SpCell, and PCell may be interpreted interchangeably with the current beam (e.g., the RS ID associated with the indicated [Joint / DL] TCI state) or the serving cell's beam (e.g., the RS ID associated with the serving cell's PCI TCI state) in the event-triggered beam reports for mobility in Rel. 19.

[0064] In existing L3 events, adjacent [cells] may be interpreted interchangeably with other beams (e.g., RS IDs that are not associated with the indicated [joint / DL]TCI state but are associated with the RS ID for the L1 beam measurement) in event-triggered beam reports for MIMO (which may be mobility) in Rel. 19.

[0065] Furthermore, adjacent [cells] in existing L3 events may be interpreted as corresponding to beams of non-serving cells / target cells / candidate cells (e.g., RS IDs associated with the TCI status of the PCI of target cells / candidate cells) in event-triggered beam reports for mobility in Rel. 19.

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

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

[0068] <Event Instance Counters / Timers> In UEIBR / Event Triggered Beam Reporting, the use of counters / timers (which may also be called evaluation windows / time windows) is being considered to determine / judge the triggering / occurrence of events.

[0069] The counter / timer may be used in MIMO / mobility use cases. For example, in the case of an event-triggered beam for mobility (LTM), the timer may be TTT (Time to Trigger).

[0070] The UE may count the number of event instances (e.g., measurements that satisfy the event's entering condition) and determine that the event has occurred / been triggered / satisfied when that number reaches a certain number (e.g., M).

[0071] The number of event instances may, for example, represent a count for event triggers. The counting of event instances may be performed within a timer / time window.

[0072] The counter / timer may be specified in advance, set / instructed using RRC signaling / MAC CE / DCI, or determined based on UE capability information reports.

[0073] Of the events mentioned above, in Event 2, it is being considered that the event instance count will be performed for each new beam.

[0074] Furthermore, the evaluation cycle for the event instance of event 2 mentioned above is being considered.

[0075] For example, the period of the current beam's RS may be the same as the period of the new beam's RS.

[0076] In this case, the evaluation period of the event instance may be the same as the period of the RS of the current beam and the RS of the new beam.

[0077] Furthermore, for example, the RS period of the current beam and the RS period of the new beam may be different (and may be supported).

[0078] In this case, the evaluation period of the event instance may be at least one of the following periods 1 to 5: • The evaluation period of the event instance is the same as the period of the current beam's RS. • The evaluation period of the event instance is the same as the period of the new beam's RS. • The evaluation period of the event instance is the same as the shortest period among the periods of the current beam's RS and the new beam's RS. • The evaluation period of the event instance is the larger of the shortest period among the periods of the current beam's RS and the new beam's RS, and Xms (the maximum value). • The evaluation period of the event instance is the same as the longest period among the periods of the current beam's RS and the new beam's RS.

[0079] Figure 2 shows an example of a timer / counter related to the UEIBR. In the example shown in Figure 2, the count of event instances for determining the trigger of an event / UEIBR is performed using a timer and a counter (which may also be called a count-up timer).

[0080] In the example shown in Figure 2, when an event instance is satisfied (for example, when the event's entering condition is met), a timer of a specific length is started, and thereafter the timer is restarted each time an event instance is satisfied (it is not necessary for timers that are already running to be stopped when a timer is started / restarted).

[0081] In this disclosure, the evaluation window may include timers and counters.

[0082] Furthermore, in this disclosure, at least one of an event matching, an event being triggered, or an event instance being satisfied may be determined with respect to the current beam [only], the current beam and one new beam, the current beam and at least one new beam, or the current beam and multiple (e.g., all) new beams.

[0083] In the example shown in Figure 2, the event / UEIBR is triggered when the event instance count exceeds a certain number of M (M = 3 in the example shown in Figure 2) within a single evaluation window.

[0084] In the example shown in Figure 2, the timer is reset upon its expiration and upon the triggering of an event / UEIBR by an event instance within that timer. In the example shown in Figure 2, the timer is also reset upon restarting a timer after its initial start, but the timer itself continues to run after such restart.

[0085] <UEIBR Procedure> The following modes may be supported in the UEIBR procedure. The UEIBR may be performed using UCI (UCI-based) or using MAC CE.

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

[0087] Step 1: When the number of event instances corresponding to a beam (or reference signal) reaches a specific value (e.g., M), the UE determines that an event has occurred / been triggered / satisfied and transmits a first UL channel (e.g., PUCCH) (see Figure 3). The first UL channel is a UL channel that pre-notifies / requests a second UL channel (e.g., PUCCH) for transmitting beam reports and may consist of one or more bits.

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

[0089] Step 3: The UE transmits the beam report using resources on the second UL channel (e.g., PUSCH).

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

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

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

[0093] Furthermore, an RRC parameter (e.g., firstPUCCHResourceConfig-ModeA-UEIBR) for periodic PUCCH resource configuration corresponding to the 1-bit instruction may be defined. This RRC parameter does not need to be associated with the SR ID (e.g., SchedulingRequestId).

[0094] The RRC parameters may include, for example, period and offset setting parameters (periodicityAndOffset) and a PUCCH resource ID (e.g., PUCCH-ResourceID).

[0095] These RRC parameter specifications may also apply to cases using at least one CC (single CC).

[0096] The DCI format in step 2 may be, for example, UL Grant DCI (e.g., DCI format 0_1 / 0_2 / 0_3), and the second UL channel in step 3 may utilize at least PUSCH.

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

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

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

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

[0101] Step 1: When the number of event instances corresponding to a beam (or reference signal) reaches a specific value (e.g., M), the UE determines that an event has occurred / been triggered / satisfied and transmits a first UL channel (e.g., PUCCH) (see Figure 4). The first UL channel is a UL channel that notifies a second UL channel for transmitting beam reports and may consist of one or more bits.

[0102] Step 2: The UE transmits a beam report on the second UL channel (e.g., Type 1 setting grant PUSCH).

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

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

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

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

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

[0108] Furthermore, an RRC parameter (e.g., firstPUCCHResourceConfig-ModeB-UEIBR) for periodic PUCCH resource configuration corresponding to the 1-bit instruction may be defined. This RRC parameter does not need to be associated with the SR ID (e.g., SchedulingRequestId).

[0109] The RRC parameters may include, for example, period and offset setting parameters (periodicityAndOffset) and a PUCCH resource ID (e.g., PUCCH-ResourceID).

[0110] These RRC parameter specifications may also apply to cases using at least one CC (single CC).

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

[0112] (Analysis) The UEIBR reports a set number (e.g., N) of beam / reference signals (e.g., CRI / SSBRI). The beam report also transmits information about the measurement results corresponding to each of the set number of beam / reference signals (e.g., RSRP). N may be set by a higher layer parameter. N may be 1 or more, or it may be selected from a specific number (e.g., {1, 2, 3, 4} or {1, 2, 3, 4, 5, 6, 7, 8}).

[0113] The UE evaluates events for one or more beams within a predetermined time window and, if it detects a beam / reference signal that satisfies an event (for example, having a specific number of event instances M or more), it issues a beam report. The UE may issue beam reports for N beam / reference signals, each containing at least one beam / reference signal that satisfies an event. In other words, the beam report may also support cases where some of the N beam / reference signals reported do not satisfy an event.

[0114] In this case, a base station receiving a beam report transmitted from a UE may not be able to determine whether each beam / reference signal included in the beam report satisfies the event (event achieved).

[0115] Whether an event for each beam / reference signal has been achieved is determined based on the counter count (e.g., the number of event instances) within a certain time window (or at the time the timer is activated). Therefore, if the UE only reports the beam / reference signal identifier (ID) and information regarding the measurement results corresponding to that beam / reference signal (e.g., L1-RSRP), the base station has a problem in that it cannot determine which beam / reference signal events have been fulfilled.

[0116] To address the aforementioned issues, the beam report transmitted from the UE may include information about the events corresponding to each beam / reference signal. This information about the events for each beam / reference signal may be referred to as an additional indication or additional information.

[0117] As additional instructions / additional information (hereinafter also simply referred to as additional information) for each beam / reference signal, at least one of the following options 1 and 2 may be supported.

[0118] <Option 1> Additional information may be introduced for each reported beam / reference signal (e.g., CRI / SSBRI) indicating whether the beam / reference signal fulfills an event (event achieved). Whether or not such additional information field exists (or is present) in the beam report may be set (or enabled) by UE capability / upper layer parameters.

[0119] The field containing this additional information may exist (or be enabled) only in specific cases. These specific cases may include, for example, at least one of the following: the number of beams / reference signals reported in the beam report (e.g., N) is greater than 1 (N > 1), or a time window and a specific value M are set.

[0120] <Option 2> Additional information indicating the number of event instances within a predetermined time window (or timer period) may be introduced for each reported beam / reference signal (e.g., CRI / SSBRI). Whether or not such a field for additional information exists in the beam report may be set (or enabled) by the UE capability / upper layer parameter.

[0121] The field containing this additional information may exist (or be enabled) only in specific cases. These specific cases may include, for example, at least one of the following: the number of beams / reference signals reported in the beam report (e.g., N) is greater than 1 (N > 1), or a time window and a specific value M are set.

[0122] In Option 1, the event achievement status for each reported beam / reference signal may be reported using one bit (or one bit field).

[0123] On the other hand, Option 2 requires additional reporting of the number of event instances for each reported beam / reference signal (e.g., the actual number of event instances within a given time window). Therefore, Option 2 is expected to report additional information using more bits than Option 1.

[0124] Thus, in Option 2, the number of event instances corresponding to each beam / reference signal is included in the beam report, which may increase the overhead of the beam report. In particular, if the number of event instances (e.g., M) that serves as the criterion for fulfilling an event (or the criterion for whether or not an event has been achieved) becomes large, the number of beam instances corresponding to the beam / reference signal being reported will also increase, which may increase the amount of additional information that needs to be included in the beam report.

[0125] The inventors focused on the increased overhead of beam reporting when reporting information on the number of event instances as additional information to be included in the beam report (Option 2), and conceived this embodiment by investigating a method to suppress the increase in overhead.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0140] In this disclosure, "transmission" and "reception" may be interpreted interchangeably.

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

[0142] In this disclosure, MAC CE, UCI, cell switching command, beam switching command, MAC CE for beam reporting, and MAC CE for cell switching may be interpreted as interchangeable.

[0143] In this disclosure, the UEIBR may be reported using PUSCH (e.g., CG PUSCH / DG PUSCH). That is, the reporting content in this disclosure may be transmitted using at least one of MAC CE / UCI / PUCCH / PUCH.

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

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

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

[0147] In this disclosure, the beam, RS, RS index (CRI / SSBRI), and [L1 / L3] measurement results may be interpreted interchangeably.

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

[0149] In this disclosure, the terms event-based beam reporting, event-triggered beam reporting, UE-triggered beam reporting, UE-initiated beam reporting (UEIBR), UE-initiated beam management (UEIBMM), beam reporting, etc., [for Rel. 19] may be interpreted interchangeably.

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

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

[0152] In this disclosure, rules, cases, factors, conditions, thresholds, etc., may be interpreted as interchangeable.

[0153] In this disclosure, the CSI / UCI relating to the UEIBR may be referred to as the UEIBR-CSI / UCI. In this disclosure, "other" UCI (or simply "UCI") may mean a UCI separate from the CSI / UCI relating to the UEIBR.

[0154] In this disclosure, beam report, CSI report, UEIBR, CSI relating to UEIBR, UEIBR-CSI, UEIBR-UCI, report, etc. may be interpreted interchangeably.

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

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

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

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

[0159] In this disclosure, terms such as switch, switching, activate, deactivate, instruct, change, update, etc., relating to the TCI state may be interpreted interchangeably.

[0160] In this disclosure, beam indicator (DCI / MAC CE), TCI status indicator (DCI / MAC CE), TCI status switching command (DCI / MAC CE), cell switch command (DCI / MAC CE), DCI, MAC CE, etc., may be interpreted interchangeably.

[0161] In this disclosure, the terms "report content," "field," "ID," "measurement result," and "reported quantity" may be interpreted interchangeably.

[0162] In this disclosure, beam report, report, MAC CE, beam report MAC CE, UCI, and PUSCH may be interpreted as interchangeable.

[0163] In this disclosure, beam, beam ID, beam identifier, RS index, SSBRI, and CRI may be interpreted as interchangeable.

[0164] In this disclosure, the current beam, the beam / RS corresponding to the current active TCI state, the beam / RS corresponding to the active TCI state, the beam / RS derived from the [current] active TCI state, etc., may be interpreted interchangeably.

[0165] In this disclosure, beam and beam ID, RS and RS ID, TCI state and TCI state ID may be interpreted as mutually interchangeable.

[0166] In this disclosure, counter, timer, time window, evaluation window, backward sliding window, sliding window, and window may be interpreted interchangeably.

[0167] (Wireless communication method) The UE may apply each embodiment of the disclosure in conjunction with the performance of beam measurement / reporting (e.g., UEIBR). The NW / BS / gNB may provide / transmit to the UE settings / instructions etc. for the UE to perform the operations / controls described in each embodiment of the disclosure. Furthermore, the NW / BS / gNB may perform various operations / controls necessary to receive event-triggered beam reports / UEIBR from the UE.

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

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

[0170] In this disclosure, each operation / option may be applied in at least one of Case 1 and Case 2 described above.

[0171] In this disclosure, each operation / option may be applied in at least one of Mode A and Mode B as described above.

[0172] In this disclosure, the number of RS / beam reports [included in the beam report] may include the number of sets of RS indices (e.g., CRI / SSBRI) and corresponding measurement results (e.g., L1-RSRP) included in the beam report, or it may include the number of either the RS indices or the corresponding measurement results.

[0173] This disclosure shows a case where information regarding the number of event instances is reported in the beam report, but it may be applied interchangeably with a case where information indicating whether or not an event was achieved is reported (Option 1).

[0174] The UE may perform event evaluation on one or more beam / reference signals (e.g., CRI / SSBRI) and, if it detects a beam that satisfies the event, trigger a UE-initiated beam report (see Figures 5 and 6). Figure 5 shows a beam report when Mode A is applied, and Figure 6 shows a beam report when Mode B is applied.

[0175] In its beam report (step 3 in Figure 5, step 2 in Figure 6), the UE may include information regarding the number of event instances for each beam / reference signal being reported. This information regarding the number of event instances may be indicated by a reported value / code point.

[0176] Information regarding the number of event instances may include information regarding the range of the number of event instances.

[0177] For example, in a beam report, multiple reporting values / code points may be defined / configured for reporting information regarding the number of event instances, and at least one (or all) of these reporting values / code points may be associated with a range of event instance counts. The UE may also include reporting values / code points corresponding to the number of event instances for each beam / reference signal in the beam report.

[0178] A mapping / association (e.g., a table) between the reported value / code point (multiple bits) used to report information about the number of event instances and the actual number / range of event instances may be defined / configured. This mapping / association (e.g., a table) between the reported value / code point and the number / range of event instances may be defined in the specification or configured by higher-layer parameters.

[0179] By reporting a range of event instance counts (reported values / code points) rather than the actual number of event instances, it is possible to suppress the increase in overhead in beam reporting compared to reporting the actual number of event instances.

[0180] For mapping / associating reported values / code points with the number / range of event instances, at least one of the following options 1-1 to 1-3 may be applied.

[0181] The following explanation uses the case where the reported value / code point is 2 bits as an example, but the number of bits for the reported value / code point is not limited to this and may be 3 bits or more. Also, the mapping / association (table) between the reported value / code point and the number / range of event instances shown below is just an example, and other numerical values ​​may be applied.

[0182] <Option 1-1> Information regarding the number of event instances reported in the beam report (e.g., reported value / code point) may be defined / configured based on (or using) a specific value.

[0183] In this disclosure, a specific value may be the number of event instances (e.g., M) that serves as a criterion for satisfying an event (or a threshold value for determining whether an event has been achieved). The specific value M may also be called the number of event instances / threshold / condition for an event to be satisfied. For example, a UE may determine that an event has been satisfied if the number of event instances is M or greater within a predetermined time window.

[0184] The number / range of event instances mapped to / associated with a reported value / code point may be defined / set based on at least one of a specific value M and a value obtained by adding a value to that specific value M. Here, we use the value obtained by adding a value to that specific value M as an example, but you may also use a value obtained by subtracting a certain value from the specific value M.

[0185] For example, Figures 7A to 7C show an example of how a range of event instance counts is mapped / associated (e.g., a table) to at least one (or all) of several report values / code points that may be included in a beam report. The range of event instance counts may be defined by at least one of a specific value M and a value obtained by adding a value to the specific value M. The values ​​defined / set in Figures 7A to 7C (e.g., values ​​added to M) are examples, and other values ​​may be defined / set.

[0186] In Figure 7A, the first reported value (e.g., 00) corresponds to the case where the number of event instances is less than M (<M). The second reported value (e.g., 01) corresponds to the case where the number of event instances is M (=M). The third reported value (e.g., 10) corresponds to the case where the number of event instances is greater than M and less than M+2 (>M, ≤M+2). The fourth reported value (e.g., 11) corresponds to the case where the number of event instances is greater than M+2 (>M+2).

[0187] As shown in Figure 7A, a specific value M is mapped / associated with some of the reported values ​​(in this case, one reported value 01), and a range of event instance numbers based on that specific value M is mapped / associated with the remaining reported values.

[0188] In Figure 7B, the first reported value (e.g., 00) corresponds to the case where the number of event instances is less than M (<M). The second reported value (e.g., 01) corresponds to the case where the number of event instances is M or greater and less than M+3 (≧M, <M+3). The third reported value (e.g., 10) corresponds to the case where the number of event instances is M+3 or greater and less than M+6 (≧M+3, <M+6). The fourth reported value (e.g., 11) corresponds to the case where the number of event instances is M+6 or greater (≧M+6).

[0189] As shown in Figure 7B, a range of event instance counts based on a specific value M is mapped / associated with multiple reported values.

[0190] In Figure 7C, the first reported value (e.g., 00) corresponds to the case where the number of event instances is less than M (<M). The second reported value (e.g., 01) corresponds to the case where the number of event instances is M or greater and less than M+x (≧M, <M+x). The third reported value (e.g., 10) corresponds to the case where the number of event instances is M+x or greater and less than M+2x (≧M+x, <M+2x). The fourth reported value (e.g., 11) corresponds to the case where the number of event instances is M+2x or greater (≧M+2x).

[0191] x may be a value set by a higher-level parameter (for example, a variable value). Thus, Figure 7C shows a case where a range of event instance numbers based on a specific value M and x is mapped / associated with multiple reported values.

[0192] In this way, by mapping / associating a range of event instance counts with at least one of multiple reported values, it is possible to suppress the increase in overhead compared to reporting the actual number of event instances.

[0193] <Option 1-2> Information regarding the number of event instances reported in the beam report (e.g., reported value / code point) may be defined / configured based on (or using) a specific value.

[0194] The number / range of event instances mapped to / associated with a reported value / code point may be defined / set based on at least one of a specific value M and a value obtained by multiplying the specific value M by a value.

[0195] For example, Figures 8A to 8C show an example of how a range of event instance counts is mapped / associated (e.g., a table) to at least one (or all) of several report values / code points that may be included in a beam report. The range of event instance counts may be defined by at least one of a specific value M and a value obtained by multiplying the specific value M by a value. The values ​​defined / set in Figures 8A to 8C (e.g., the value multiplied by M) are examples, and other values ​​may be defined / set.

[0196] In Figure 8A, the first reported value (e.g., 00) corresponds to the case where the number of event instances is less than M (<M). The second reported value (e.g., 01) corresponds to the case where the number of event instances is M (=M). The third reported value (e.g., 10) corresponds to the case where the number of event instances is greater than M and less than 1.1 × M (>M, ≤1.1 × M). The fourth reported value (e.g., 11) corresponds to the case where the number of event instances is greater than 1.1 × M (>1.1 × M).

[0197] As shown in Figure 8A, a specific value M is mapped / associated with some of the reported values ​​(in this case, one reported value 01), and a range of event instance numbers based on that specific value M is mapped / associated with the remaining reported values.

[0198] In Figure 8B, the first reported value (e.g., 00) corresponds to the case where the number of event instances is less than M (<M). The second reported value (e.g., 01) corresponds to the case where the number of event instances is M or greater and less than 1.1 × M (≧M, <1.1 × M). The third reported value (e.g., 10) corresponds to the case where the number of event instances is 1.1 × M or greater and less than 1.2 × M (≧1.1 × M, <1.2 × M). The fourth reported value (e.g., 11) corresponds to the case where the number of event instances is 1.2 × M or greater (≧1.2 × M).

[0199] As shown in Figure 8B, a range of event instance counts based on a specific value M is mapped / associated with multiple reported values.

[0200] In Figure 8C, the first reported value (e.g., 00) corresponds to the case where the number of event instances is less than M (<M). The second reported value (e.g., 01) corresponds to the case where the number of event instances is M or greater and less than M + x × M (≧M, <M + x × M). The third reported value (e.g., 10) corresponds to the case where the number of event instances is M + x × M or greater and less than M + 2x × M (≧M + x × M, <M + 2x × M). The fourth reported value (e.g., 11) corresponds to the case where the number of event instances is M + 2x × M or greater (≧M + 2x × M).

[0201] x may be a value set by a higher-level parameter (for example, a variable value). Thus, Figure 8C shows a case where a range of event instance numbers based on a specific value M and x is mapped / associated with multiple reported values.

[0202] In this way, by mapping / associating a range of event instance counts with at least one of multiple reported values, it is possible to suppress the increase in overhead compared to reporting the actual number of event instances.

[0203] <Options 1-3> Information regarding the number of event instances reported in beam reports (e.g., reported value / code point) may be defined / configured without being based on a specific value M (e.g., the number of event instances / threshold / condition for an event to be met). The number / range of event instances mapped / associated with a reported value / code point may be defined / configured based on at least one of an arbitrary fixed value and one or more values ​​(e.g., a variable value) set by upper-layer signaling.

[0204] For example, Figures 9A to 9C show an example of how a range of event instance counts is mapped / associated (e.g., a table) to at least one (or all) of several report values / code points that may be included in a beam report. The range of event instance counts may be defined by at least one of an arbitrary fixed value and one or more values ​​(e.g., variable values) set by upper-layer signaling. The values ​​(e.g., fixed values) defined / set in Figures 9A to 9C are examples, and other values ​​may be defined / set.

[0205] In Figure 9A, the first reported value (e.g., 00) corresponds to the case where the number of event instances is less than 4 (<4). The second reported value (e.g., 01) corresponds to the case where the number of event instances is 4 or greater and less than 8 (≧4, <8). The third reported value (e.g., 10) corresponds to the case where the number of event instances is 8 or greater and less than 12 (≧8, <12). The fourth reported value (e.g., 11) corresponds to the case where the number of event instances is 12 or greater (≧12).

[0206] As shown in Figure 9A, a range of event instance counts based on an arbitrary number is mapped / associated with multiple reported values.

[0207] In Figure 9B, the first reported value (e.g., 00) corresponds to the case where the number of event instances is less than 5 (<5). The second reported value (e.g., 01) corresponds to the case where the number of event instances is 5 or greater and less than 8 (≧5, <8). The third reported value (e.g., 10) corresponds to the case where the number of event instances is 8 or greater and less than 10 (≧8, <10). The fourth reported value (e.g., 11) corresponds to the case where the number of event instances is 10 or greater (≧10).

[0208] As shown in Figure 9B, a range of event instance counts based on an arbitrary number is mapped / associated with multiple reported values.

[0209] In Figure 9C, the first reported value (e.g., 00) corresponds to the case where the number of event instances is less than x (<x). The second reported value (e.g., 01) corresponds to the case where the number of event instances is greater than or equal to x and less than x + delta (≧x, <x + delta). The third reported value (e.g., 10) corresponds to the case where the number of event instances is greater than or equal to x + delta and less than x + 2 × delta (≧x + delta, <x + 2 × delta). The fourth reported value (e.g., 11) corresponds to the case where the number of event instances is greater than or equal to 2 × delta (≧2 × delta). At least one of x and delta may be set by upper-layer signaling.

[0210] As shown in Figure 9C, a range of event instance numbers based on variable values ​​is mapped / associated with multiple reported values.

[0211] In this way, by mapping / associating a range of event instance counts with at least one of multiple reported values, it is possible to suppress the increase in overhead compared to reporting the actual number of event instances.

[0212] <Variations> The tables shown in Options 1-1 to 1-3 are examples only and are not limited to them. Options 1-1 to 1-3 show four cases (2 bits) for the reported value, but the reported value may be less than four or five or more (for example, three bits or more).

[0213] Only one mapping / association (or table) between reported values ​​and event instance count ranges may be defined / configured. Alternatively, multiple mappings / associations (or tables) between reported values ​​and event instance count ranges may be defined / configured, and which mapping / association (or table) applies may be determined based on predetermined conditions.

[0214] For each option (or all options), only one table may be defined / configured / specified, or multiple tables may be defined / configured / specified. For example, multiple tables may be defined / configured from among the one or more tables shown in Option 1-1, the one or more tables shown in Option 1-2, and the one or more tables shown in Option 1-3.

[0215] If multiple tables are defined / configured, the base station may instruct the UE to use RRC parameters / MAC CE / DCI to specify which table to apply in the beam report. Alternatively, if multiple tables are defined / configured, a specific table may be selected based on UE capability information.

[0216] Alternatively, if multiple tables are defined / configured, a specific table may be selected based on predetermined conditions / predetermined settings. The predetermined conditions / predetermined settings may be at least one of the number of beams / reference signals reported in the beam report (N) and the number of event instances (M) that serve as the criterion for determining whether an event has been achieved.

[0217] Information regarding the number of event instances (additional information) may be included in (or not included in) the beam report based on predetermined conditions / RRC parameters. For example, the UE may control whether to include (or not include) information regarding the number of event instances (additional information) in the beam report when predetermined RRC parameters are set.

[0218] Alternatively, the UE may control the inclusion of information regarding the number of event instances (additional information) in the beam report if certain conditions are met (for example, at least one of the following: the number of beams / reference signals to report (N) is a specific value (e.g., 1), and M is a specific value (e.g., 1)). Alternatively, the UE may control the inclusion of information regarding the number of event instances (additional information) in the beam report if certain conditions are met (for example, at least one of the following: the number of beams / reference signals to report (N) is a specific value (e.g., >1), and M is a specific value (e.g., >1)).

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

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

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

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

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

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

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

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

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

[0228] The above specific UE capabilities may include at least one of the following: • Supporting specific processing / operation / control / information for at least one of the above embodiments; • Supporting reporting information regarding the number of event instances in beam reporting; • Supporting reporting a range of event instance numbers in beam reporting; • Supporting event-triggered beam reporting / UEIBR; • Supporting MIMO / mobility from Rel. 19 onwards; • Supporting UEIBR using MAC CE / UCI; • Supporting event combinations (e.g., event 1 / 2 / 7); • Total number of beams reported; • Number of beams that meet the conditions; • Supporting timer / counter reset / continuation for specific events (e.g., event 2 / 7 / 1); • Supporting multi-CC cases / cross-CC cases; • Supporting multi-event cases.

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

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

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

[0232] (Note) The following inventions are added with respect to one embodiment of the present disclosure. [Note 1] A terminal having: a control unit that controls a beam report initiated by a terminal based on the number of event instances within a time window; and a transmission unit that transmits the beam report, wherein the control unit controls the beam report to include a report value corresponding to at least one of the range of the number of event instances and the specific number of times for each reference signal when the number of event instances for at least one reference signal exceeds a specific number of times and the beam report is performed for multiple reference signals. [Note 2] The terminal according to Note 1 in which the range of the number of event instances is defined or set based on the specific number of times. [Note 3] The terminal according to Note 1 or Note 2 in which only one report value is defined or set as the range of the number of event instances to be included in the report value that is less than the specific number of times. [Note 4] The terminal according to any one of Notes 1 to 3 in which the range of the number of event instances is defined or set based on a value different from the specific number of times.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0280] The transmitting / receiving unit 120 may transmit configuration information relating to the evaluation of beam report events initiated by the terminal (at least one of the time window, a specific value (M) that serves as a criterion for whether or not an event has been achieved, and the number of beam / reference signals (N) to be included in the beam report). The transmitting / receiving unit 120 may also receive beam reports initiated by the terminal based on the number of event instances within the time window.

[0281] The control unit 110 may set a range for the number of event instances corresponding to the reported values ​​included in the beam report.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0300] The transmitting / receiving unit 220 may transmit beam reports. The transmitting / receiving unit 220 may receive configuration information relating to the evaluation of beam report events initiated by the terminal (at least one of the time window, a specific value (M) that serves as a criterion for whether or not the event has been achieved, and the number (N) of beam / reference signals to be included in the beam report).

[0301] The control unit 210 may control the beam reporting initiated by the terminal based on the number of event instances within a time window. If the number of event instances for at least one reference signal exceeds a certain number and beam reporting is performed for multiple reference signals, the control unit 210 may control the beam reporting to include a reporting value for each reference signal that corresponds to at least one of the range of the number of event instances and the certain number.

[0302] The range of the number of event instances may be defined or set based on the aforementioned specific number. Only one reporting value less than the aforementioned specific number may be defined or set as the range of the number of event instances to be included in the reporting value. The range of the number of event instances may also be defined or set based on a value different from the aforementioned specific number.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0354] Furthermore, in this disclosure, terms such as beam, SRS Resource Indicator (SRI), CORESET, CORESET pool, PDSCH, PUSCH, Codeword (CW), Transport Block (TB), and RS may be interpreted interchangeably.

[0355] Furthermore, in this disclosure, TCI state, downlink TCI state (DL TCI state), uplink TCI state (UL TCI state), unified TCI state, common TCI state, joint TCI state, etc., may be interpreted interchangeably.

[0356] Furthermore, in this disclosure, terms such as "QCL," "QCL assumption," "QCL relationship," "QCL type information," "QCL property / properties," "specific QCL type (e.g., Type A, Type D) properties," and "specific QCL type (e.g., Type A, Type D)" may be interpreted interchangeably.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0402] This application is based on Japanese Patent Application No. 2025-017608, filed on February 5, 2025. All of its contents are included herein.

Claims

1. A terminal comprising: a control unit that controls a beam report initiated by the terminal based on the number of event instances within a time window; and a transmission unit that transmits the beam report, wherein the control unit controls the beam report to include, for each reference signal, a report value corresponding to at least one of the range of the number of event instances and the specific number, when the number of event instances for at least one reference signal exceeds a certain number and the beam report is performed for multiple reference signals.

2. The terminal according to claim 1, wherein the range of the number of event instances is defined or set based on the specific number of times.

3. The terminal according to claim 1, wherein only one report value is defined or set as the range of the number of event instances to be included in the report value that is less than the specified number.

4. The terminal according to claim 1, wherein the range of the number of event instances is defined or set based on a value different from the specific number of times.

5. A wireless communication method for a terminal, comprising the steps of: controlling a beam report initiated by the terminal based on the number of event instances within a time window; and transmitting the beam report, wherein, if the number of event instances for at least one reference signal exceeds a specific number and the beam report is performed for multiple reference signals, the method controls the beam report to include a report value corresponding to at least one of the range of the number of event instances and the specific number for each reference signal.

6. A base station comprising: a transmitting unit that transmits configuration information relating to the evaluation of beam report events initiated by a terminal; a receiving unit that receives beam reports initiated by a terminal based on the number of event instances within a time window; and a control unit that sets a range for the number of event instances corresponding to the report values ​​included in the beam report.

Images