Terminal, wireless communication method, and base station
The terminal and base station configuration optimizes beam reporting in next-generation mobile communication systems, addressing latency and quality issues by managing synchronization signal blocks and TCI states, thereby enhancing communication quality and throughput.
Patent Information
- Application Number
- PCT/JP2026/016426
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2025-05-07
- Filing Date
- 2026-04-24
- Publication Date
- 2026-11-12
AI Technical Summary
Existing wireless communication systems, particularly in next-generation mobile communication systems like 5G and beyond, face challenges in adequately supporting event-based beam reporting, leading to potential hindrances in achieving lower latency communication and compromising communication quality and throughput.
A terminal and base station configuration that includes a transmitting unit for initiating beam reports and a control unit to manage synchronization signal blocks, enhancing communication quality and throughput by optimizing beam reporting processes.
Improves communication quality and throughput by efficiently managing beam reporting events, reducing latency, and ensuring seamless transitions between TCI states.
Smart Images

Figure JP2026016426_12112026_PF_FP_ABST
Abstract
Description
Terminal, wireless communication method, and base station
[0001] This disclosure relates to terminals, wireless communication methods, and base stations in next-generation mobile communication systems.
[0002] In the Universal Mobile Telecommunications System (UMTS) network, Long Term Evolution (LTE) was specified with the aim of achieving even higher data rates and lower latency (Non-Patent Literature 1). Furthermore, LTE-Advanced (3GPP Rel. 10-14) was specified with the aim of further increasing the capacity and sophistication of LTE (Third Generation Partnership Project (3GPP®) Release (Rel.) 8, 9).
[0003] Successor systems to LTE (for example, 5th generation mobile communication system (5G), 5G+ (plus), 6th generation mobile communication system (6G), New Radio (NR), 3GPP Rel. 15 and later) are also being considered.
[0004] 3GPP TS 36.300 V8.12.0 “Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 (Release 8)”, April 2010
[0005] In future wireless communication systems (e.g., NR, Rel. 19 and later), support for event-based beam reporting (or possibly called event-triggered beam reporting / UE-initiated Beam Report (UEIBR)) initiated by a terminal (user terminal, user equipment (UE)) is being considered.
[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 is not adequately considered. If this consideration is insufficient, it may not be possible to achieve lower latency communication, potentially hindering improvements in communication quality and throughput.
[0008] Therefore, one of the objectives of this disclosure is to provide a terminal, a wireless communication method, and a base station that can improve communication quality / throughput.
[0009] A terminal according to one aspect of the present disclosure includes a transmitting unit that transmits a beam report initiated by the terminal, and a control unit that controls the continuation of receiving a synchronization signal block associated with a reference signal index included in the beam report after the transmission of the beam report.
[0010] According to one aspect of this disclosure, communication quality / throughput can be improved.
[0011] Figure 1A shows an example of UE movement in Rel. 17. Figure 1B shows an example of UE movement in Rel. 18. Figure 2 shows an example of delay related to updating the active TCI state in the conventional way. Figure 3 shows an example of delay related to updating the active TCI state according to the present disclosure. Figure 4 shows an example of a schematic configuration of a wireless communication system according to one embodiment of the present disclosure. Figure 5 shows an example of a base station configuration according to one embodiment of the present disclosure. Figure 6 shows an example of a terminal configuration according to one embodiment of the present disclosure. Figure 7 shows an example of a hardware configuration of a base station and terminal according to one embodiment of the present disclosure.
[0012] (TCI State Switching) Rel. 15 / 16 specifies the delay time for switching to an active TCI state for UEs in a serving cell that have one or more Transmission Configuration Indication (TCI) states set.
[0013] Even if a UE measures, stores, and maintains QCL properties, the network (NW, e.g., base station) cannot recognize that the UE is measuring, storing, and maintaining the QCL properties unless the UE provides L1-RSRP reports / beam reports to the network. Therefore, the UE must measure and report beam / RS, and the UE and the NW must have a common understanding of whether the TCI status is known or unknown.
[0014] In Rel. 16, a TCI state being known means that the following conditions 0-5 are met: (Condition 0): From the last transmission of the RS resource used to report the L1-RSRP measurement of the target TCI state until the switching of the active TCI state is complete, the RS resource for the L1-RSRP measurement is the RS of the target TCI state or the RS with a QCL relationship to the target TCI state. (Condition 1): A TCI state switch command is received within 1280 ms of the last transmission of the RS resource for beam reporting or measurement. (Condition 2): Prior to the TCI state switch command, the UE has transmitted at least one L1-RSRP report for the target TCI state. (Condition 3): The TCI state remains detectable during the TCI state switching period. (Condition 4): The SSB associated with the TCI state remains detectable during the TCI state switching period. (Condition 5) The Signal to Noise Ratio (SNR) in the TCI state must be -3 dB or higher.
[0015] The TCI state being unknown means that the TCI state is not known.
[0016] In this disclosure, a known TCI state may be referred to as a "Known TCI State," and an unknown TCI state may be referred to as an "Unknown TCI State."
[0017] In the case of using a MAC CE for TCI state switching (MAC-CE based TCI state switch), where the target TCI state (the TCI state after switching) is a known TCI state, when a UE receives a Physical Downlink Shared Channel (PDSCH) including an activation command for the TCI state (TCI state indication) in slot n, at slot n+T HARQ +3N subframe,μ slot +TO k *(T first-SSB +T SSB-proc ) / (NR slot length), the first slot after that, the UE receives the Physical Downlink Control Channel (PDCCH) of the target TCI state of the serving cell on which the TCI state switching has occurred. Further, the UE can receive the PDCCH of the old (pre-switching) TCI state up to slot n+T HARQ +3N subframe,μ slot The UE can receive the PDCCH of the old (pre-switching) TCI state. Slot n+T HARQ +3N subframe,μ slot From slot n+T HARQ +3N subframe,μ slot +TO k *(T first-SSB +T SSB-proc ) / (NR slot length), the TCI state applied by the UE in the period up to this point is undefined.
[0018] Here, T HARQ represents the timing from the transmission of a downlink data signal (e.g., PDSCH) to delivery confirmation information (e.g., HARQ-ACK information). N subframe,μ slot represents the number of slots per subframe for the subcarrier configuration μ. T first-SSB is the time until the SSB is first transmitted after the UE decodes the MAC CE command used for activation of the TCI state. T SSB-proc is 2 ms. TO kThis value is 1 if the target TCI state is not included in the list of active TCI states for PDSCH, and 0 otherwise. NR slot length indicates the length of the slot.
[0019] The TCI state of PDCCH indicates the QCL type A / D relationship between the demodulation reference signal (DMRS) for PDCCH and TRS (or CSI-RS, here TRS#1). The TCI state of TRS indicates the QCL type C / D relationship between TRS, SSB (here SSB#1), and QCL type C / D. The target QCL RS of the DMRS for PDCCH may be TRS, the root QCL RS of the DMRS for PDCCH may be SSB, and the target / root QCL RS of TRS may be SSB. Note that target and root may be interchangeable.
[0020] When MAC CE is used for TCI state switching, and the target TCI state is an unknown TCI state, when the UE receives a PDSCH containing a TCI state activation command in slot n, it switches to slot n+T HARQ +3N subframe,μ slot +T L1-RSRP +TO uk * (T first-SSB +T SSB-proc In the first slot after ) / (NR slot length), the PDCCH of the target TCI state of the serving cell where the TCI state switching occurred is received. Also, UE receives the PDCCH of slot n+T HARQ +3N subframe,μ slot Up to this point, it is possible to receive the PDCCH in the old (pre-switching) TCI state.
[0021] Here, TO uk This is 1 for L1-RSRP measurement using CSI-RS, or for switching in a TCI state where a QCL type other than QCL type D is set. On the other hand, TO uk This is a switching of the TCI state in which at least QCL type D is set, and is 0 for L1-RSRP measurement using SSB.
[0022] Also, T first-SSB This is the time from the L1-RSRP measurement to the first SSB transmission when switching in a TCI state where at least QCL type D is set. Alternatively, T first-SSB This is the time between when the UE decodes the MAC CE command used to activate a TCI state other than QCL type D, and when it first sends an SSB.
[0023] Compared to when the target TCI state is a known TCI state, when the target TCI state is an unknown TCI state, switching the TCI state takes T L1-RSRP This will require an additional amount of time. L1-RSRP This is the time related to the measurement of received power. L1-RSRP This value is 0 when the frequency range (FR) is 1, or when FR2 is set and QCL type D is not configured. Otherwise, it represents the time required for beam determination / refinement in FR2.
[0024] Furthermore, when using downlink control information (DCI) for TCI state switching (DCI-based TCI state switch), and the target TCI state is a known TCI state, if the upper-layer parameter tci-PresentInDCI for the CORESET that schedules the PDSCH is set to enabled for the UE in slot n, the PDSCH of the target TCI state of the serving cell where the TCI state switching occurred is received in the first slot after slot n + timeDurationForDCI. Here, timeDurationForDCI is the time required for receiving the PDCCH and for applying spatial QCL information to the reception of the DCI for the PDSCH.
[0025] Furthermore, in the case of using RRC signaling for TCI state switching (RRC-based TCI state switch), when the target TCI state is a known TCI state, when the UE receives a PDSCH transmitting a TCI state RRC activation command in slot n, slot n + (T RRC_processing +TO k * (T first-SSB +T SSB-proc In the first slot after )) / (NR slot length), receive the PDCCH of the target TCI state of the serving cell where the TCI state switching occurred.
[0026] Here, T RRC_processing This is the delay related to the RRC process (RRC processing delay). first-SSB This is the time from the UE's RRC process until the first SSB is sent. SSB-proc TO k And (NR slot length) is the same as in the case of a known TCI state in TCI state switching using MAC CE.
[0027] Furthermore, when RRC signaling is used for TCI state switching (RRC-based TCI state switch), and the target TCI state is an unknown TCI state, when the UE receives a PDSCH transmitting a TCI state RRC activation command in slot n, slot n + (T RRC_processing +T L1-RSRP +TO uk * (T first-SSB +T SSB-proc In the first slot after )) / (NR slot length), receive the PDCCH of the target TCI state of the serving cell where the TCI state switching occurred.
[0028] Here, T RRC_processing This is the delay related to the RRC process (RRC processing delay). SSB-proc TO ukAnd (NR slot length) is the same as in the case of an unknown TCI state in TCI state switching using MAC CE.
[0029] Also, T first-SSB This is the time from the L1-RSRP measurement to the first SSB transmission when switching in a TCI state where at least QCL type D is set. Alternatively, T first-SSB This is the time between when the UE decodes the MAC CE command used to activate a TCI state other than QCL type D, and when it first sends an SSB.
[0030] Rel. 17 specifies the delay time for switching related to the unified TCI state.
[0031] For example, if an RRC parameter (DLorJoint-TCIState) relating to the unified TCI state for the DL channel of a serving cell is set for the UE, the specified delay time may be applied.
[0032] In MR-DC or standalone NR, the delay time also applies to all lists of multiple serving cells in a simultaneous TCI update list across multiple CCs / cells (e.g., simultaneousU-TCI-UpdateList1, simultaneousU-TCI-UpdateList2, simultaneousU-TCI-UpdateList3, simultaneousU-TCI-UpdateList4).
[0033] If the target DL TCI state refers to an additional PCI that is different from the physical cell ID (PCI) of the serving cell to which this DL TCI state is set, the delay time may be applied provided that the following conditions are met: • The active BWP of the serving cell and the additional PCI cell are the same. • The center frequency, subcarrier spacing (SCS), and system frame number (SFN) offset of the additional PCI cell are the same as those of the serving cell. • The additional PCI cell is known to the UE.
[0034] Additionally, the cells of the additional PCI may be known if the following conditions are met: • The UE has sent a valid L3 measurement report to the cells of the additional PCI in the last 5 seconds immediately before the L1-RSRP measurement is set. • The timing offset between the serving cell and the cells of the additional PCI is within the CP of the corresponding SCS.
[0035] If this condition is not met, the cells of the additional PCI may be unknown.
[0036] A DL TCI state being known in a unified TCI state may also satisfy the following conditions: • From the last transmission of the RS resource used to report the L1-RSRP measurement of the target DL TCI state until the switching of the active DL TCI state is complete, the RS resource for the L1-RSRP measurement is the RS of the target DL TCI state or the RS with a QCL relationship to the target DL TCI state. • A downlink TCI state switch command is received within 1280 ms of the last transmission of the RS resource for beam reporting or measurement. • The UE has transmitted at least one L1-RSRP report for the target DL TCI state prior to the DL TCI state switch command. • The DL TCI state remains detectable throughout the DL TCI state switching period. - During the DL TCI state switching period, detection of SSBs associated with the DL TCI state must remain possible. - The Signal to Noise Ratio (SNR) of the DL TCI state must be -3 dB or higher.
[0037] The SSB may be associated with the PCI of the serving cell or a PCI different from the serving cell PCI.
[0038] If the above conditions are not met, the DL TCI status may be unknown.
[0039] In the case of joint TCI state switching, if the target PL-RS is not maintained, the UE does not need to expect reception in DL based on the target TCI state before completing the DL and UL TCI state switch.
[0040] When MAC-CE is used for switching to a DL TCI state (MAC-CE based downlink TCI state switch), and the target TCI state (TCI state of the switching destination) is a known TCI state, when the UE receives a PDSCH containing a TCI state activation command (TCI state instruction) in slot n, slot n+T HARQ +3N subframe,μ slot +TO k * (T first-SSB +T SSB-proc In the first slot after ) / (NR slot length), the physical downlink control channel (PDCCH) of the target TCI state of the serving cell where the TCI state switching occurred is received. Also, the UE receives the slot n+T HARQ +3N subframe,μ slot Until then, the old (pre-switching) TCI state can be used to receive UE-specific PDSCH / PDCCH. Slot n+T HARQ +3N subframe,μ slot From slot n+T HARQ +3N subframe,μ slot +TO k * (T first-SSB +T SSB-proc During the period up to (NR slot length), the TCI status applied by the UE is not specified.
[0041] Here, T HARQ This indicates the timing from the transmission of the downlink data signal (e.g., PDSCH) to the delivery confirmation information (e.g., HARQ-ACK information). subframe,μ slot This represents the number of slots per subframe relative to the subcarrier setting μ. first-SSBis the time from when the UE decodes the MAC CE command used for TCI state activation until the first transmission of SSB. T SSB-proc is 2 ms. TO k is 1 if the target TCI state is not included in the list of active TCI states for PDSCH, and 0 otherwise. NR slot length indicates the length of the slot.
[0042] When MAC CE is used for DL TCI state switching, and the target TCI state is an unknown TCI state, when the UE receives the PDSCH including the TCI state activation command in slot n, in the first slot after slot n+T HARQ +3N subframe,μ slot +T L1-RSRP +TO uk *(T first-SSB +T SSB-proc ) / (NR slot length), the UE receives the PDCCH of the target TCI state of the serving cell where TCI state switching occurs. In addition, the UE may receive the UE-specific PDSCH / PDCCH using the old (pre-switching) TCI state until slot n+T HARQ +3N subframe,μ slot
[0043] Here, TO uk is 1 for L1-RSRP measurement using CSI-RS, or for TCI state switching configured with a QCL type other than QCL type D. On the other hand, TO uk is 0 for at least TCI state switching configured with QCL type D, and for L1-RSRP measurement using SSB.
[0044] In addition, T first-SSB is the time from after L1-RSRP measurement when performing TCI state switching configured with at least QCL type D until the first transmission of SSB. Alternatively, T first-SSB This is the time between when the UE decodes the MAC CE command used to activate a TCI state other than QCL type D, and when it first sends an SSB.
[0045] Compared to when the target TCI state is a known TCI state, when the target TCI state is an unknown TCI state, switching the TCI state takes T L1-RSRP This will require an additional amount of time. L1-RSRP This is the time related to the measurement of received power. L1-RSRP This value is 0 when the frequency range (FR) is 1, or when FR2 is set and QCL type D is not configured. Otherwise, it represents the time required for beam determination / refinement in FR2.
[0046] Furthermore, if, for example, an RRC parameter (DLorJoint-TCIState (when unifiedTCI-StateType indicates Joint), or UL-TCIState) relating to the unified TCI state is set for the UL channel / signal of the serving cell for the UE, the specified delay time may be applied.
[0047] In MR-DC or standalone NR, the delay time also applies to all lists of multiple serving cells in a simultaneous TCI update list across multiple CCs / cells (e.g., simultaneousU-TCI-UpdateList1, simultaneousU-TCI-UpdateList2, simultaneousU-TCI-UpdateList3, simultaneousU-TCI-UpdateList4).
[0048] For UL TCI status (or joint TCI status), the known / unknown status of the additional PCI cells and the known / unknown status of the UL TCI status are the same as the known / unknown status of the additional PCI cells and TCI status for the DL TCI status described above, but with "DL TCI status" replaced by "UL TCI status (or joint TCI status)".
[0049] In the case of a joint TCI state switch, the UE does not need to be expected to transmit in UL before the DL and UL TCI state switch is complete.
[0050] When MAC-CE is used for switching separate UL TCI states / joint TCI states for UL channels / signals (MAC-CE based uplink TCI state switch), and the target TCI state (the TCI state of the switching destination) is a known TCI state, when the UE receives a PDSCH containing a TCI state activation command (TCI state instruction) in slot n, slot n+T HARQ +3N subframe,μ slot +NM*(T first-target-PL-RS +4*T target-PL-RS A UL signal of the target TCI state can be transmitted at +2ms) / (NR slot length). Here, the UL channel / signal may be PUCCH, PUSCH, or semi-persistent / periodic / aperiodic SRS (when beamCorrespondenceWithoutUL-BeamSweeping is set to 1).
[0051] Furthermore, when MAC CE is used for switching separate UL TCI states / joint TCI states for UL channels / signals, and the target TCI state is an unknown TCI state, when UE receives a PDSCH containing a TCI state activation command (TCI state instruction) in slot n, slot n+T HARQ +3N subframe,μ slot + (T L1-RSRP +T first-target-PL-RS +4*T target-PL-RS A UL signal indicating the target TCI status can be transmitted within a time frame of +2ms) / (NR slot length).
[0052] Here, T HARQ This indicates the timing from the transmission of the downlink data signal (e.g., PDSCH) to the delivery confirmation information (e.g., HARQ-ACK information). subframe,μ slotThis represents the number of slots per subframe relative to the subcarrier setting μ. NR slot length indicates the length of the slot.
[0053] NM is 1 if the target PL-RS is maintained, and 0 otherwise.
[0054] T first-target-PL-RS This is the time from the L1-RSRP measurement until the first path loss RS is transmitted when the target TCI state is unknown. first-target-PL-RS This is the time between the transmission of the first path loss RS after the MAC CE command is decoded by the UE for the known TCI state.
[0055] T target-PL-RS This is the period of the target PL-RS.
[0056] That is, 4*T target-PL-RS This means the time it takes for the target PL-RS to be transmitted / received four times. first-target-PL-RS +4*T target-PL-RS This refers to the time period after a specific timing during which the target PL-RS is transmitted / received five times. This takes into account the effect of fading on the PL-RS and is designed to switch the TCI state by considering the average of multiple PL-RS measurement results.
[0057] T target-PL-RS This is the period of the target PL-RS, which is the SSB or NZP CSI-RS, when the PL-RS is associated with the serving cell. target-PL-RS This is the period of the PL-RS that becomes SSB when the PL-RS is associated with a PCI different from the serving cell.
[0058] Compared to when the target TCI state is a known TCI state, when the target TCI state is an unknown TCI state, switching the TCI state takes T L1-RSRP This will require an additional amount of time. L1-RSRP This is the time related to the measurement of received power. L1-RSRPThis value is 0 when the frequency range (FR) is 1, or when FR2 is set and QCL type D is not configured. Otherwise, it represents the time required for beam determination / refinement in FR2.
[0059] (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.
[0060] <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.
[0061] (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.
[0062] 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.
[0063] 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.
[0064] 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).
[0065] <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.
[0066] (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.
[0067] 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.
[0068] 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).
[0069] (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).
[0070] Beam management (UEIBM) initiated by UEIBR / UE can be used for measurement reporting, beam switching, cell switching, etc.
[0071] <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.
[0072] 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.).
[0073] 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.
[0074] <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.
[0075] UE Feature #1: UEIBR for MIMO in Rel. 19. UE Feature #2: UEIBR for mobility in Rel. 19.
[0076] Different UE capabilities may be introduced / defined between UE features #1 and #2. Furthermore, different higher-layer parameters may be set to enable each UE feature. UE features and UE capabilities may be interchangeable.
[0077] 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).
[0078] 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.
[0079] This disclosure may be applied within the Unified TCI Framework.
[0080] 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.
[0081] <UEIBR for MIMO> The following may apply to the UEIBR for MIMO in Rel. 19.
[0082] - 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).
[0083] 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).
[0084] 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).
[0085] It should be noted that the events exemplified in this way do not exclude other events.
[0086] 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).
[0087] 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).
[0088] 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 in the indicated TCI state. • Beam option 2b: The RS corresponding to the current beam is an SSB that is QCL'd with the QCL RS in the indicated TCI state. • Beam option 2c: The RS corresponding to the current beam is explicitly set / indicated using RRC signaling / MAC CE.
[0089] For example, for a 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 for TCI states (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 setting subset of the list of TCI states set by RRC (set TCI states).
[0090] For example, multiple schemes may be supported for the reference signal measurement (RS measurement) of the current beam for event 2 (and beam option 2a): • Scheme 1: The RS of the current beam is the QCL RS in the indicated TCI state. • Scheme 2: The RS of the current beam is the QCL RS in the indicated TCI state and the QCLed SSB.
[0091] If there are two QCL RSs in the indicated TCI state, the QCL RSs may be of QCL type D.
[0092] At least one of CSI-RS and SSB may be supported as a QCL RS to be set / applied to the indicated TCI state. When CSI-RS is set / applied as the QCL RS, at least one of a tracking CSI-RS (TRS) and a measurement CSI-RS may be supported. The measurement CSI-RS may be a CSI-RS used for L1-RSRP / L1-SINR or a CSI-RS used for beam management (BM).
[0093] In Scheme 1, only a TRS (e.g., one tracking CSI-RS) may be set as the QCL-RS (e.g., type A / D) for the indicated TCI state.
[0094] If only TRS is set as the QCL-RS for the indicated TCI state, a reference signal different from the TRS (e.g., the RS corresponding to the TRS) may be selected for measuring / reporting the RS of the current beam.
[0095] For the current beam RS measurement in Event 2 / Option 2a, [in addition to Schemes 1 and 2], at least one of the following processing options 1 to 4 may be applied when only one TRS is set in the indicated TCI state:
[0096] • Processing Option 1: An additional scheme is introduced. The RS for the current beam can be the CSI-RS for beam management derived from the QCL RS in the indicated TCI state. • Processing Option 2: TRS is further supported as the measured RS for the current beam to determine the L1-RSRP. • Processing Option 3: An additional scheme is introduced. The RS for the current beam is explicitly set / indicated by the RRC or MAC CE. • Processing Option 4: No further extensions are made.
[0097] Explicit RS settings for measuring new beams in Event 2 may be configured in a single RS resource set associated with the CSI reporting settings.
[0098] In this case, if existing UE capabilities cannot be reused, a UE capability indicating the maximum number of RSs to be set within the RS resource set may be defined / introduced.
[0099] The RS within that single RS resource set may be updated by MAC CE.
[0100] UEIBR for MIMO may be transmitted using UCI.
[0101] In a UCI-based UEIBR procedure using UCI, the following modes may be supported:
[0102] <<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).
[0103] Step 1: The UE transmits a first UL channel (e.g., PUCCH). The first UL channel is a UL channel that pre-notifies / requests a second UL channel (e.g., PUCCH) for transmitting beam reports, and may consist of one or more bits.
[0104] Step 2: The UE detects a DCI format (which may also be called the first DL signal) indicating the second UL channel resource.
[0105] Step 3: The UE transmits the beam report using the resource (UCI) on the second UL channel.
[0106] 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.
[0107] In this case, periodic PUCCH resources (PUCCH format 0 / 1) can be set up by dedicated upper-layer signaling.
[0108] 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).
[0109] 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).
[0110] The RRC parameters may include, for example, period and offset setting parameters (periodicityAndOffset) and a PUCCH resource ID (e.g., PUCCH-ResourceID).
[0111] These RRC parameter specifications may also apply to cases using at least one CC (single CC).
[0112] 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.
[0113] 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.
[0114] A new 1-bit field in the DL grant DCI may be defined to instruct the transmission of the UEIBR.
[0115] PUCCH resources intended for HARQ-ACK transmission may be (re)used to transmit both HARQ-ACK and UEIBR.
[0116] <<Mode B>> Mode B relates to the UCI in the pre-configured resources for the second UL channel.
[0117] Step 1: The UE transmits a first UL channel (e.g., PUCCH). The first UL channel is a UL channel that notifies a second UL channel for transmitting beam reports, and may consist of one or more bits.
[0118] Step 2: The UE transmits a beam report on the second UL channel (for example, using a specific resource (UCI) within the channel).
[0119] Note that the notification in Step 1 may be included in a separate reporting instance from the beam report in Step 2.
[0120] 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.
[0121] In this case, periodic PUCCH resources (PUCCH format 0 / 1) can be set up by dedicated upper-layer signaling.
[0122] In either mode A or B as described above, cross-CC (component carrier) beam reporting may be supported.
[0123] 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).
[0124] 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).
[0125] The RRC parameters may include, for example, period and offset setting parameters (periodicityAndOffset) and a PUCCH resource ID (e.g., PUCCH-ResourceID).
[0126] These RRC parameter specifications may also apply to cases using at least one CC (single CC).
[0127] The second UL channel in step 2 may be, for example, a type 1 configured grant (CG) PUSCH or PUCCH.
[0128] <UEIBR for Mobility> With respect to the UEIBR for mobility (e.g., LTM) in Rel. 19, the following may apply:
[0129] - MAC CE in semi-persistent / aperiodic PUCCH. - UCI in periodic / semi-persistent PUCCH, UCI in semi-persistent / aperiodic PUCCH.
[0130] The report may include, for example, at least one of the following: If the measurement report is used for cell switching reporting, in addition to MIMO-related information: an indicator showing whether or not a cell switch has occurred, or TA-related information. Otherwise (if the measurement report is not used for cell switching reporting): the same information as MIMO-related information (the only difference being whether it is within a cell or between cells).
[0131] The supported events may be the same as those for a Conditional Hand-Over (CHO).
[0132] For example, since candidate cells are set based on the L3 measurement report, L1-RSRP / SINR may be used as the threshold.
[0133] If the report is used for cell switching commands, specific domain filters (e.g., time / frequency / space) may be considered / applied to prevent frequent switching.
[0134] It may also be specified whether flexibility in the trigger time (e.g., 5 milliseconds, 10 milliseconds, 20 milliseconds) is required.
[0135] In the case of L1 measurements using UEIBR, at least the results of beam-level measurements may be used for event evaluation.
[0136] 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.
[0137] 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.
[0138] In the LTM configuration, the L1 measurement resource setting may support both SSB and CSI-RS beam settings.
[0139] 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).
[0140] 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.
[0141] UEIBR for mobility may be transmitted using MAC CE.
[0142] <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.
[0143] 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.
[0144] 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.
[0145] 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.
[0146] 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.
[0147] 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.
[0148] 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.
[0149] (Analysis) In the above-mentioned UEIBR, after the transmission of the UEIBR (second UL channel) [for example, for event 7], it is being considered that the UE stores the QCL characteristics of the SSB associated with the reference signal reported in the report [according to the UE capability].
[0150] By saving the QCL characteristics of the activatable reporting beam, it becomes unnecessary to receive additional SSBs after receiving the TCI status activation command, thus reducing the delay until the new beam is applied (for example, the delay related to updating the active TCI status).
[0151] To achieve such latency reduction, the UE and NW need to have a common understanding of at least one of the following: the period for which the UE preserves QCL characteristics, the conditions under which the UE resets QCL characteristics, and the number of QCL characteristics that the UE preserves (or can preserve).
[0152] For example, if UEIBR is not set, the target TCI state is known, and the target TCI state is not included in the active TCI state list for PDSCH, additional SSB reception will be required (case shown in Figure 2).
[0153] On the other hand, for example, if a UEIBR is set up and a beam application delay reduction process is applied (e.g., if QCL characteristics are preserved), additional SSB reception can be omitted by considering the beams included in the UEIBR as known and synchronized (i.e., the delay for additional SSB reception (e.g., T) as shown in Figure 3). first-SSB +TSSB-proc (This will reduce the amount of the reduction.)
[0154] However, detailed considerations for reducing such delays have not been sufficient.
[0155] For example, the detailed examination of UE operation regarding the monitoring of SSBs related to beams included in the UEIBR is insufficient. If this examination is insufficient, the UEIBM may not function properly due to a mismatch between UE operation and network assumptions.
[0156] For example, there is insufficient consideration given to how many QCL characteristics the UE can save, for how long the UE continues to save the QCL characteristics, and when the UE resets the saved QCL characteristics.
[0157] If this consideration is insufficient, it may not be possible to properly operate the updating / modification of the active TCI state based on UEIBR, and low-latency communication that takes advantage of the benefits of UEIBR may not be achieved, potentially leading to a suppression of improvements in communication quality and throughput.
[0158] Therefore, the inventors of this invention conceived a way to solve these problems.
[0159] The embodiments relating to this disclosure will be described in detail below with reference to the drawings. Each wireless communication method relating to an embodiment / option may be applied individually or in combination. This disclosure also provides embodiments / options which are configured by combining some or all of one embodiment / option with some or all of another embodiment / option.
[0160] (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.
[0161] 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".
[0162] 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.
[0163] 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.
[0164] In this disclosure, terms such as signaling, message, field, parameter, information, and payload may be interpreted interchangeably.
[0165] 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, Non-Access Stratum (NAS) signaling [of the control plane], and other messages (e.g., messages communicated with the core network, such as positioning protocol (e.g., NR Positioning Protocol A (NRPPPa) / LTE Positioning Protocol (LPP)) messages).
[0166] 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).
[0167] In this disclosure, physical layer signaling may include, for example, Downlink Control Information (DCI) and Uplink Control Information (UCI).
[0168] In this disclosure, base station, gNB, and network (NW) may be interpreted as interchangeable.
[0169] 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.
[0170] 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.
[0171] In this disclosure, "transmission" and "reception" may be interpreted interchangeably.
[0172] In this disclosure, tables, mappings, associations, lists, formats, content, reports, etc., may be interpreted interchangeably.
[0173] 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.
[0174] 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.
[0175] In this disclosure, "Serving" may be interpreted as "Serving beam," "Serving cell," or "SpCell."
[0176] In this disclosure, "Neighbor" may be interpreted as any beam or cell other than a serving beam / serving cell / SpCell / SCell.
[0177] In this disclosure, candidate cells, target cells, adjacent cells, cells, etc., may be interpreted interchangeably.
[0178] In this disclosure, the beam, RS, RS index (CRI / SSBRI), and [L1 / L3] measurement results may be interpreted interchangeably.
[0179] In this disclosure, the measured RS may be the QCL source RS in an active TCI state / indicated TCI state.
[0180] 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.
[0181] In this disclosure, indicated TCI state, active TCI state, activated TCI state, configured TCI state, and RS set in RRC may be interpreted interchangeably.
[0182] Each embodiment of this disclosure is applicable to any event.
[0183] In this disclosure, rules, cases, factors, conditions, thresholds, etc., may be interpreted as interchangeable.
[0184] 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.
[0185] In this disclosure, beam report, CSI report, UEIBR, CSI relating to UEIBR, UEIBR-CSI, UEIBR-UCI, report, etc. may be interpreted interchangeably.
[0186] In this disclosure, Mode A and Mode B may be interpreted as interchangeable.
[0187] In this disclosure, multiplexing (to multiplex / to be multiplexed) and mapping (to map / to be mapped) may be interpreted interchangeably.
[0188] 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.
[0189] In this disclosure, other UL channels (for transmitting other UCIs), PUCCH, and PUSCH may be interpreted as interchangeable.
[0190] In this disclosure, terms such as switch, switching, activate, deactivate, instruct, change, update, etc., relating to the TCI state may be interpreted interchangeably.
[0191] 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.
[0192] In this disclosure, the terms "report content," "field," "ID," "measurement result," and "reported quantity" may be interpreted interchangeably.
[0193] In this disclosure, beam report, report, MAC CE, beam report MAC CE, UCI, and PUSCH may be interpreted as interchangeable.
[0194] In this disclosure, beam, beam ID, beam identifier, RS index, SSBRI, and CRI may be interpreted as interchangeable.
[0195] 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.
[0196] In this disclosure, beam and beam ID, RS and RS ID, TCI state and TCI state ID may be interpreted as mutually interchangeable.
[0197] In this disclosure, “all” may mean “all that are set for the UE.”
[0198] In this disclosure, new information elements, event types (settings), event settings, combinations of event types (settings), and combinations of event settings, etc., may be interpreted interchangeably.
[0199] In this disclosure, CSI reporting settings, reporting settings, CSI reporting settings for UEIBR, reporting settings for UEIBR, UEIBR settings, etc., may be interpreted interchangeably.
[0200] In this disclosure, "candidate," "candidate value," and "value" may be interpreted as interchangeable.
[0201] In this disclosure, the beam / RS used to determine whether or not an event is met may be called the reference beam / RS. For example, the Qth beam (the beam with rank Q) in event 7 may be called the reference beam, where Q is the rank of the reference beam.
[0202] In this disclosure, the activated TCI state corresponding to the reference beam / RS (which may also be called the active TCI state) may be referred to as the reference active TCI state.
[0203] In this disclosure, Q [value], the rank [value] of the beam / TCI state for determining the trigger conditions of the event [related to event 7], the reference beam [value], the reference TCI state [value], etc., may be interpreted as being interchangeable.
[0204] (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.
[0205] This disclosure is applicable to mobility / MIMO use cases.
[0206] In this disclosure, each operation / option may be applied individually or in combination with others.
[0207] In this disclosure, each operation / option may be applied in at least one of Case 1 and Case 2 described above.
[0208] In this disclosure, each operation / option may be applied in at least one of Mode A and Mode B as described above.
[0209] 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.
[0210] In this disclosure, “a report contains a beam” may mean that the report contains information about the beam (e.g., the RS ID corresponding to the beam and information about at least one of the measurement results of the RS). In this disclosure, the number of reported beams may be the same as the number of CRI / SSBRI fields included in one report.
[0211] In this disclosure, Event 7 will be used as a specific example, but this is merely one example, and the method can be applied to other events as appropriate.
[0212] For example, event 7 in the embodiments of this disclosure may be interpreted as another event for MIMO, or as an event for mobility (e.g., for LTM / conditional LTM). In other words, the behavior / restrictions according to the embodiments of this disclosure can be appropriately applied to other events other than event 7.
[0213] In this case, the beam report transmitted by the UE may be UCI-based or MAC CE-based. Therefore, the above-described operation / restriction may apply to beam reports using UCI or to beam reports using MAC CE. For example, the beam report may be transmitted in UCI / MAC CE for UL cell switch commands.
[0214] In this case, in step 2 of mode A, the UE may receive a DCI that triggers / schedules a UL channel / resource related to the UCI of the UL cell switch command.
[0215] In this case, the UE may also receive a conditional LTM setting as a reporting setting for the UEIBR. The UE may control the UEIBR operation based on the conditional LTM setting.
[0216] The UE / NW may switch the application of different event types (e.g., events 2 and 7) using (or at the higher layer) higher-layer signaling, or under specific conditions.
[0217] The bit size of the UCI transmitted using the second UL channel may be standardized to a larger size for different event types (e.g., events 2 and 7). In this case, the UCI for events with smaller reporting content may be zero-padded to match the size of the larger UCI.
[0218] Each embodiment of this disclosure may apply only if the target TCI state (e.g., the TCI state to be changed / updated) is known.
[0219] <First Embodiment> The first embodiment relates to UE operation related to SSB monitoring.
[0220] The UE may control the reception / monitoring / measurement of the SSB associated with the beam / RS (index) contained in the UEIBR (e.g., the second UL channel) after transmission.
[0221] For example, UE may control the continuation of receiving / monitoring / measuring the SSB after the UEIBR has been transmitted.
[0222] The network may assume that after the transmission of the UEIBR, the UE controls the continuation of receiving / monitoring / measuring the SSB.
[0223] UE / NW may also conform to the following embodiments 1-1 / 1-2.
[0224] <<Embodiment 1-1>> The UE may continue to receive / monitor / measure the SSB associated with the beam / RS included in the UEIB for a specific period after the transmission of the UEIB.
[0225] If an activation command for the TCI state is received during that specific period, an additional delay for SSB reception (for example, T) will be added to the delay related to updating / changing the active TCI state associated with that activation command. first-SSB +T SSB-proc ) does not need to be included.
[0226] If an activation command for the TCI status is received after the expiration of the specified period, an additional delay for SSB reception (for example, T) will be added to the delay related to updating / changing the active TCI status associated with the activation command. first-SSB +T SSB-proc ) may be included.
[0227] The specific period may be, for example, at least one of the following: • A period of Xms from a specific timing. • A period of Y SSB transmissions from a specific timing.
[0228] At least one of X and Y may be specified in advance in the specifications, set / instructed / notified using RRC / MAC CE / DCI, determined based on UE capability information, or determined based on a combination of at least two of these.
[0229] The specific timing may be, for example, at least one of the following: • The timing when the second UL channel, including the UEIBR, is transmitted. • The timing when the first UL channel is transmitted. • The timing when the first DL signal is received. • The timing when the response (ACK) to the second UL channel is received. • The timing when a specific (e.g., first) SSB for the UEIBR is received / measured.
[0230] <<Embodiment 1-2>> The UE does not need to continue receiving / monitoring / measuring the SSB associated with the beam / RS included in the UEIB after the UEIB has transmitted.
[0231] UE may store the QCL characteristics obtained for UEIBR.
[0232] The QCL characteristic may be, for example, the QCL characteristic of the SSB corresponding to the beam / RS (index) included in the UEIBR.
[0233] According to the first embodiment described above, by appropriately defining the monitoring operation of the SSB after UEIB transmission, beam management processing by the UE can be performed appropriately, and the delay related to updating the active TCI state can be reduced, thereby contributing to improved communication throughput.
[0234] <Second Embodiment> The second embodiment relates to the number of QCL characteristics to be stored.
[0235] UE may store a specific number (one or more) of QCL characteristics obtained for UEIBR.
[0236] NW may assume that a specific number (one or more) of QCL characteristics acquired for UEIBR are stored in UE.
[0237] UE / NW may also conform to the following embodiments 2-1 / 2-2.
[0238] <<Embodiment 2-1>> The UE may store the QCL characteristics of each RS corresponding to multiple (e.g., all) beams contained within the UEIBR, [until at least one specific condition is met].
[0239] These multiple beams may, for example, include multiple beams that include additional instructions on whether or not an event condition is met.
[0240] The UE may store QCL characteristics corresponding to multiple reports [simultaneously]. In this case, the [maximum] number of QCL characteristics stored by the UE may be equal to the total number of beams reported in each report.
[0241] <<Embodiment 2-2>> The UE may use the UE capability report to report the maximum number of storable QCL characteristics.
[0242] UE( / NW) may sort the reported candidate beams in a specific order.
[0243] UE( / NW) may store the QCL characteristics corresponding to the RS of the candidate beam up to the maximum number, in sorted order, until at least one specific condition is met.
[0244] UE( / NW) does not need to save any QCL characteristics that exceed the [maximum] number among the QCL characteristics corresponding to the RS of the candidate beam.
[0245] The specific order may be, for example, at least one of the following: • Ascending / descending order for beam quality (measurement result, e.g., L1-RSRP). • Ascending / descending order for RS ID. • Order based on event type.
[0246] The candidate beam may be, for example, at least one of the following: • Multiple (e.g., all) beams included in the UEIBR; or • A beam included in the UEIBR that satisfies the event condition (e.g., the beam may have additional indications as to whether it satisfies the event condition).
[0247] For each UEIBR transmission, the UE may perform processing / operations related to saving new QCL characteristics (newly saved QCL characteristics) / old QCL characteristics (currently saved QCL characteristics).
[0248] The process / operation may be at least one of the following: - Resetting multiple (e.g., all) currently saved QCL characteristics. - Updating (old QCL characteristics) by saving new QCL characteristics [only]. - Sorting new / old QCL characteristics in a specific order. - Saving X QCL characteristics based on priority / rank (e.g., selected in order from highest priority).
[0249] The priority / rank may have higher values in ascending / descending order among the QCL characteristics sorted by that specific order.
[0250] The specific order may be at least one of the following (or at least two in combination): - Ascending / descending order for beam quality (measurement result, e.g., L1-RSRP); - Ascending / descending order for RS ID; - Ascending / descending order for the timing of QCL characteristic preservation (i.e., the order in which a particular QCL is preserved, either earlier or later in time); - Order based on event type.
[0251] For example, multiple QCL characteristics may first be sorted from newest (most recent) in terms of beam preservation timing, and then sorted in descending order of measurement quality for QCL characteristics with the same preservation timing.
[0252] Assume that the maximum number of QCL characteristics that a UE can store is X, the number of QCL characteristics stored by a new UEIBR transmission is A, and the number of QCL characteristics currently stored is B.
[0253] In this case, if A + B is less than or equal to X, UE may add (all) new QCL characteristics to the stored QCL characteristics.
[0254] Furthermore, in this case, if A + B is greater than X, UE may update the QCL characteristics with lower priority / rank among the currently stored QCL characteristics with the new QCL characteristics based on the specific order described above.
[0255] At least one specific condition relating to Embodiments 2-1 / 2-2 (for example, the timing of QCL characteristic reset) will be described in detail in the third embodiment below.
[0256] According to the second embodiment described above, by appropriately defining the number of QCL characteristics related to the UEIB, the beam management process by the UE can be performed appropriately, and the delay related to updating the active TCI state can be reduced, thereby contributing to improved communication throughput.
[0257] <Third Embodiment> The third embodiment relates to the period for storing QCL characteristics and the resetting of stored QCL characteristics.
[0258] The UE may reset the QCL characteristics that are saved at a specific time.
[0259] In other words, the UE may store the QCL characteristics of the SSB associated with the reference signal reported in the UEIBR until the QCL characteristics are reset.
[0260] The specific timing may be determined according to at least one of the embodiments 3-1 to 3-9 below. At least two of the embodiments 3-1 to 3-9 below may be combined.
[0261] In embodiments 3-1 to 3-9 below, the term "novel" may be omitted.
[0262] <<Embodiment 3-1>> The specific timing may be the timing of the expiration of the period [set by the NW].
[0263] The length of the period may be specified in advance in the specifications, set / instructed / notified using RRC / MAC CE / DCI, determined based on UE capability information, or determined based on a combination of at least two of these.
[0264] The relevant period may be defined / set, for example, in units of symbols / slots / frames / subframes / ms.
[0265] The period may be applied to multiple (e.g., all) QCL characteristics, or it may be applied to each QCL characteristic separately.
[0266] The period may begin at at least one of the following: - When a UEIBR (second UL channel) is transmitted. - When a response (ACK) to a UEIBR (second UL channel) is received.
[0267] <<Embodiment 3-2>> The specific timing may be the timing at which a new beam report is transmitted.
[0268] When a new beam report is submitted, multiple (e.g., all) stored QCL characteristics may be reset.
[0269] When a new beam report associated with a specific event type (e.g., event 7 / 2 / 1) is transmitted, the stored QCL characteristics associated with the same event type may be reset.
[0270] When a new beam report is sent associated with a specific CSI reporting configuration for the UEIBR (e.g., CSI-ReportConfig), the saved QCL characteristics associated with the same CSI reporting configuration may be reset.
[0271] <<Embodiment 3-3>> The specific timing may be the timing at which X new beam reports are transmitted.
[0272] X may be specified in advance in the specifications, set / instructed / notified using RRC / MAC CE / DCI, determined based on UE capability information, or determined based on a combination of at least two of these.
[0273] When X new beam reports are sent, multiple (e.g., all) of the stored QCL characteristics may be reset.
[0274] When X new beam reports are sent associated with a specific event type (e.g., event 7 / 2 / 1), the stored QCL characteristics associated with the same event type may be reset.
[0275] When X new beam reports are sent associated with a specific CSI reporting configuration for the UEIBR (e.g., CSI-ReportConfig), the saved QCL characteristics associated with the same CSI reporting configuration may be reset.
[0276] <<Embodiment 3-4>> The specific timing may be the timing at which a new first UL channel is transmitted.
[0277] When a new first UL channel is transmitted, multiple (e.g., all) stored QCL characteristics may be reset.
[0278] When a new first UL channel associated with a specific event type (e.g., event 7 / 2 / 1) is transmitted, the stored QCL characteristics associated with the same event type may be reset.
[0279] When a new first UL channel is sent associated with a specific CSI reporting configuration for the UEIBR (e.g., CSI-ReportConfig), the stored QCL properties associated with the same CSI reporting configuration may be reset.
[0280] <<Embodiment 3-5>> The specific timing may be the timing when a new first DL signal is received.
[0281] When a new first DL signal is received, multiple (e.g., all) stored QCL characteristics may be reset.
[0282] When a new first DL signal associated with a specific event type (e.g., event 7 / 2 / 1) is received, the stored QCL characteristics associated with the same event type may be reset.
[0283] When a new first DL signal is received associated with a specific CSI reporting configuration for the UEIBR (e.g., CSI-ReportConfig), the stored QCL characteristics associated with the same CSI reporting configuration may be reset.
[0284] <<Embodiment 3-6>> The specific timing may be the timing at which a response (ACK) to a new beam report is received.
[0285] When a response to a new beam report is received, multiple (e.g., all) stored QCL characteristics may be reset.
[0286] When a response to a new beam report associated with a specific event type (e.g., event 7 / 2 / 1) is received, the stored QCL characteristics associated with the same event type may be reset.
[0287] When a response to a new beam report associated with a specific CSI reporting configuration for the UEIBR (e.g., CSI-ReportConfig) is received, the stored QCL characteristics associated with the same CSI reporting configuration may be reset.
[0288] <<Embodiment 3-7>> The specific timing may be the timing at which the active TCI state is updated.
[0289] <<Embodiment 3-8>> The specific timing may be the timing after the second timing has elapsed when the number of event evaluation opportunities for the UEIBR reaches X.
[0290] For example, the specific timing could be the time when the number of event evaluation opportunities for the UEIBR after a specific (e.g., the last) event evaluation opportunity that triggers the UEIBR reaches X.
[0291] For example, the specific timing may be the timing at which the number of event evaluation opportunities for the UEIBR after the event evaluation opportunity following the UEIBR transmission reaches X.
[0292] For example, the specific timing may be the timing at which the number of event evaluation opportunities for the UEIBR (second UL channel) after the event evaluation opportunity following the receipt of the response (ACK) to the UEIBR reaches X.
[0293] <<Embodiment 3-9>> The specific timing may be the timing after the second timing has elapsed when the number of SSB transmissions / receptions / measurements reaches X.
[0294] For example, the specific timing may be the timing at which the number of SSB transmissions / receptions / measurements after a specific (e.g., the first) SSB measurement / reception for the UEIBR reaches X.
[0295] For example, the specific timing may be the timing when the number of SSB transmissions / receptions / measurements after a UEIBR transmission reaches X.
[0296] For example, the specific timing may be the timing when the number of SSB transmissions / receptions / measurements after receiving the response (ACK) to the UEIBR (second UL channel) reaches X.
[0297] In the above embodiments 3-8 / 3-9, X may be specified in advance by the specifications, set / instructed / notified using RRC / MAC CE / DCI, determined based on UE capability information, or determined based on a combination of at least two of these.
[0298] In the above embodiments 3-8 / 3-9, the second timing may be at least one of the following: - Timing of a specific (e.g., last) event evaluation opportunity. - Timing of a specific (e.g., first) SSB measurement / reception / transmission. - Timing of first UL channel transmission. - Timing of first DL signal reception. - Timing of second UL channel / UEIBR transmission. - Timing of transmission / reception of response (ACK) to the second UL channel.
[0299] Furthermore, if at least one of the following conditions is met, the UE may receive an additional SSB (i.e., a delay for receiving an additional SSB in addition to the delay for updating / changing the active TCI state related to the TCI state activation command (for example, T first-SSB +T SSB-proc (May include): - The UE does not have QCL characteristics. - The UE has reset the saved QCL characteristics. - Multiple (e.g., all) active TCI states are not related to the SSB corresponding to the reference signal reported in the beam report (in other words, at least one of the multiple (e.g., all) active TCI states is not related to the SSB corresponding to the reference signal reported in the beam report).
[0300] According to the third embodiment described above, by appropriately defining the reset of the stored QCL characteristics, the beam management process by the UE can be performed appropriately, and the delay related to updating the active TCI state can be reduced, thereby contributing to improved communication throughput.
[0301] <Fourth Embodiment> The fourth embodiment relates to network operations related to activating / deactivating the TCI state.
[0302] The network may instruct the user (UE) to activate / deactivate at least one of the following TCI states using activation / deactivation commands: • Multiple (e.g., all) TCI states that are set. • TCI states in which the user (UE) saves QCL characteristics.
[0303] The UE may assume that it will be instructed by the NW to activate / deactivate at least one of the above TCI states using activation / deactivation commands.
[0304] <Modification> The application of the first to fourth embodiments described above is not limited to UEIBR, but may also be applied to beam reporting initiated / triggered by the NW / base station.
[0305] In this case, the first to fourth embodiments described above may apply to all report configuration types (e.g., reportConfigTypes) in beam reports initiated / triggered by the NW / base station, or to some report configuration types (e.g., reportConfigTypes) in beam reports initiated / triggered by the NW / base station.
[0306] Furthermore, the application of the first to fourth embodiments described above is not limited to UEIBR, but may also be applied to beam reporting for LTM.
[0307] In this case, the first to fourth embodiments described above may be applied by substituting MAC CE for the second UL channel.
[0308] In this case, the SSB used for measurement and storage of QCL characteristics may be an SSB from at least one of the serving cell, non-serving cell, additional cell, and candidate cell.
[0309] In this disclosure, SSB may be interpreted as any reference signal (for example, CSI-RS).
[0310] <Supplement> <<Notification of Information to UE / BS>> In the embodiments described above, notification of any information from the Network (NW) (e.g., Base Station (BS)) / NW node) to the UE / BS (in other words, reception of any information from the BS / NW node at the UE / BS) may be performed using physical layer signaling (e.g., DCI), higher layer signaling (e.g., RRC signaling, MAC CE, NAS signaling, LPP messages, NRPPa messages), specific signals / channels (e.g., PDCCH, PDSCH, reference signals), or a combination thereof.
[0311] 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.
[0312] 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.
[0313] Furthermore, the notification of arbitrary information to the UE / BS in the above-described embodiments may be periodic, semi-persistent, or aperiodic. Semi-persistent or aperiodic notification of information may be triggered by instructions from the UE / BS / NW.
[0314] In the embodiments described above, information from the network may be set / instructed by any or a combination thereof in the following ways: • Common to multiple UEs, or individual to each UE (per UE). • Common to multiple BSs, or individual to each BS (per BS). • Common to multiple frequencies (e.g., one or a combination thereof, such as cells, bands, band combinations, bandwidth parts (BWPs), component carriers, etc.) (e.g., common to cells), or frequency-specific (per frequency, e.g., per cell).
[0315] <<Notification of Information from UE / BS>> Notification of any information from UE / BS to the NW in the embodiments described above (in other words, transmission / reporting of any information from UE / BS to BS / NW nodes) may be performed using physical layer signaling (e.g., UCI), higher layer signaling (e.g., RRC signaling, MAC CE, NAS signaling, LPP messages, NRPPa messages), specific signals / channels (e.g., PUCCH, PUSCH, PRACH, reference signals), or a combination thereof.
[0316] If the above notification is made by a MAC CE, the MAC CE may be identified by the inclusion of a new LCID not specified in existing standards in the MAC subheader.
[0317] If the above notice is made by the UCI, the notice may be transmitted using PUCCH or PUSCH.
[0318] Furthermore, notifications of arbitrary information from the UE / BS in the above-described embodiments may be periodic, semi-persistent, or aperiodic. Semi-persistent or aperiodic notifications of information may be triggered by instructions from the UE / BS / NW.
[0319] <<Regarding the Application of Each Embodiment>> In a UE / BS, specific (e.g., one or more, or some) processing / operation / control / assumption / 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 processing / operation / control / assumption / information is set in the UE / BS. - The specific processing / operation / control / assumption / information is determined in the UE / BS based on the relevant higher-layer parameter. - The specific processing / operation / control / assumption / information is designated / activated / triggered for the UE / BS by MAC CE / DCI / UCI / Resource / Channel / RS. - The UE / BS reports or supports a specific capability (e.g., UE capability) indicating (or related to) the specific processing / operation / control / assumption / information. - The application of the specific processing / operation / control / assumption / information is determined in the UE / BS based on specific conditions.
[0320] The above-mentioned specific capabilities may indicate that they support the above-mentioned specific processes / operations / controls / assumptions / information.
[0321] In this disclosure, "to support" and "whether or not to support" may be interpreted interchangeably.
[0322] Furthermore, the above-mentioned specific capabilities may be capabilities that apply across all frequencies (commonly regardless of frequency), capabilities per frequency (e.g., one or a combination thereof, such as cell, band, band combination, BWP, component carrier, etc.), capabilities per frequency range (e.g., Frequency Range 1 (FR1), FR2, FR3, FR4, FR5, FR2-1, FR2-2), capabilities per subcarrier spacing (SCS), or capabilities per feature set (FS) or feature set per component-carrier (FSPC).
[0323] Furthermore, the specific 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)).
[0324] If the above conditions are not met, UE / BS may follow the behavior specified in existing 3GPP releases.
[0325] Information on whether one or more of the above embodiments / options / choices / examples apply / are used, or which of the above embodiments / options / choices / examples apply / are used, may be based on several of the following methods: • The information is set by one or more higher-layer parameters / RRC IEs. • The information is determined by one or more relevant higher-layer parameters / RRC IEs. • The information is indicated by MAC CE / DCI. • The information is based on one or more UE capabilities. • The information is described / defined in the specification. • The information is based on conditions described / defined in the specification. • The information is determined by a combination of several of the above. For example, the information is determined by the setting / indication of higher-layer parameters / MAC CE / DCIs and reported by UE capabilities.
[0326] The above multiple embodiments / options / choices may be combined into a single embodiment / option / choice.
[0327] (Note) The following inventions are added with respect to one embodiment of the present disclosure. [Note 1] A terminal having a transmitting unit that transmits a beam report initiated by the terminal, and a control unit that controls the continuation of receiving a synchronization signal block associated with a reference signal index included in the beam report after the transmission of the beam report. [Note 2] The terminal according to Note 1, wherein the control unit controls the continuation of receiving the synchronization signal block after the transmission of the beam report. [Note 3] The terminal according to Note 1 or Note 2, wherein the transmitting unit reports the maximum number of Quasi-Co-Location (QCL) characteristics of the synchronization signal block that can be stored. [Note 4] The terminal according to any one of Notes 1 to 3, wherein the control unit stores the Quasi-Co-Location (QCL) characteristics of the synchronization signal block within a specific period of time.
[0328] (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.
[0329] Figure 4 shows an example of a schematic configuration of a wireless communication system according to one embodiment of the present disclosure. 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).
[0330] 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.
[0331] 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.
[0332] 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))).
[0333] 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. Terminals 20 may be located within at least one cell. The arrangement, number, shape, size, etc., of each cell and 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.
[0334] 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.
[0335] Terminal 20 may be connected to at least one of the multiple base stations 10. Terminal 20 may utilize at least one of Carrier Aggregation (CA) using multiple Component Carriers (CC) and Dual Connectivity (DC).
[0336] 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.
[0337] Furthermore, terminal 20 may communicate in each CC using at least one of time division duplex (TDD) and frequency division duplex (FDD).
[0338] 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.
[0339] 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, 5GC), Next Generation Core (NGC), etc.
[0340] The core network 30 may include, for example, network functions (Network Functions (NFs)) 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 (which may simply be called a node). Furthermore, communication with an external network (e.g., the Internet) may occur via the DN.
[0341] Terminal 20 may be a terminal that supports at least one of the following communication methods: LTE, LTE-A, 5G, etc.
[0342] 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).
[0343] 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.
[0344] 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 terminal 20.
[0345] 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 Random Access Channel (PRACH), or the like, all of which are shared by each terminal 20.
[0346] 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.
[0347] 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.
[0348] 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.
[0349] 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.
[0350] 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.
[0351] 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.
[0352] 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.
[0353] 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.
[0354] 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.
[0355] 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).
[0356] (Base Station) Figure 5 shows an example of the configuration of a base station according to one embodiment of the present disclosure. 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.
[0357] 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.
[0358] 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.
[0359] 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.
[0360] 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.
[0361] 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.
[0362] 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.
[0363] 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.
[0364] 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.
[0365] 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.
[0366] 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.
[0367] 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.
[0368] 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.
[0369] 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.
[0370] 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.
[0371] 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 terminal 20.
[0372] 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.
[0373] 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.
[0374] 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.
[0375] The transmitting / receiving unit 120 may receive beam reports initiated by the terminal. The control unit 110 may assume that, after the transmission of the beam report, the terminal controls the continuation of receiving synchronization signal blocks associated with the reference signal index included in the beam report (first embodiment).
[0376] Furthermore, in this disclosure, a network device having any of the above-described NF functions (for example, a node of an LMF) may be a device having the same configuration as the base station 10 (for example, a control unit 110 and a transceiver unit 120) as in Figure 5. In other words, in the description relating to Figure 5, the configuration of a network device according to one embodiment of this disclosure may be covered by replacing the base station with a network device.
[0377] (Terminal) FIG. 6 is a diagram illustrating an example of a configuration of a terminal according to an embodiment of the present disclosure. The terminal 20 includes a control unit 210, a transceiver unit 220, and a transceiving antenna 230. Note that one or more of each of the control unit 210, the transceiver unit 220, and the transceiving antenna 230 may be provided.
[0378] Here, in this example, functional blocks of characteristic parts in the present embodiment are mainly illustrated, and the terminal 20 may be assumed to also have other functional blocks necessary for wireless communication. Part of the processing of each unit described below may be omitted.
[0379] The control unit 210 performs overall control of the terminal 20. The control unit 210 can be constituted by a controller, a control circuit, and the like described based on common general knowledge in the technical field related to the present disclosure.
[0380] The control unit 210 may control signal generation, mapping, and the like. The control unit 210 may control transmission and reception, measurement, and the like using the transceiver unit 220 and the transceiving antenna 230. The control unit 210 may generate data, control information, sequences, and the like to be transmitted as signals, and transfer the generated data, control information, sequences, and the like to the transceiver unit 220.
[0381] The transceiver unit 220 may include a baseband unit 221, an RF unit 222, and a measurement unit 223. The baseband unit 221 may include a transmission processing unit 2211 and a reception processing unit 2212. The transceiver unit 220 can be constituted by a transmitter / receiver, an RF circuit, a baseband circuit, a filter, a phase shifter, a measurement circuit, a transceiving circuit, and the like described based on common general knowledge in the technical field related to the present disclosure.
[0382] The transceiver unit 220 may be configured as an integrated transceiver unit, or may be constituted by a transmission unit and a reception unit. The transmission unit may be constituted by the transmission processing unit 2211 and the RF unit 222. The reception unit may be constituted by the reception processing unit 2212, the RF unit 222, and the measurement unit 223.
[0383] The transceiving antenna 230 can be constituted by an antenna, for example, an array antenna and the like, described based on common general knowledge in the technical field related to the present disclosure.
[0384] The transceiver 220 may receive the aforementioned downlink channel, synchronization signal, downlink reference signal, and the like. The transceiver 220 may transmit the aforementioned uplink channel, uplink reference signal, and the like.
[0385] The transceiver 220 may form at least one of a transmit beam and a receive beam using digital beamforming (e.g., precoding), analog beamforming (e.g., phase rotation), and the like.
[0386] The transceiver 220 (transmission processing unit 2211) may perform PDCP layer processing, RLC layer processing (e.g., RLC retransmission control), MAC layer processing (e.g., HARQ retransmission control), and the like on data, control information, and the like acquired from, for example, the control unit 210, to generate a bit sequence to be transmitted.
[0387] The transceiver 220 (transmission processing unit 2211) may perform transmission processing such as channel coding (which may include error correction coding), modulation, mapping, filtering processing, DFT processing (as necessary), IFFT processing, precoding, digital-to-analog conversion, and the like on the bit sequence to be transmitted, and output a baseband signal.
[0388] Note that whether to apply DFT processing may be based on the transform precoding configuration. For a certain channel (e.g., PUSCH), when transform precoding is enabled, the transceiver 220 (transmission processing unit 2211) may perform DFT processing as the above transmission processing to transmit the channel using a DFT-s-OFDM waveform, otherwise, the DFT processing may not be performed as the above transmission processing.
[0389] The transceiver 220 (RF unit 222) may perform modulation to a radio frequency band, filtering processing, amplification, and the like on the baseband signal, and transmit the signal in the radio frequency band via the transmit / receive antenna 230.
[0390] On the other hand, the transmitting / receiving unit 220 (RF unit 222) may perform amplification, filtering, demodulation to a baseband signal, etc., on the radio frequency band signal received by the transmitting / receiving antenna 230.
[0391] The transmitting / receiving unit 220 (receiving processing unit 2212) may apply reception processing such as analog-to-digital conversion, FFT processing, IDFT processing (if necessary), filtering, demapping, demodulation, decoding (may include error correction decoding), MAC layer processing, RLC layer processing, and PDCP layer processing to the acquired baseband signal to acquire user data, etc.
[0392] The transmitting / receiving unit 220 (measuring unit 223) may perform measurements related to the received signal. For example, the measuring unit 223 may perform RRM measurement, CSI measurement, etc., based on the received signal. The measuring unit 223 may also measure received power (e.g., RSRP), received quality (e.g., RSRQ, SINR, SNR), signal strength (e.g., RSSI), propagation path information (e.g., CSI), etc. The measurement results may be output to the control unit 210.
[0393] The measurement unit 223 may derive channel measurements for CSI calculation based on channel measurement resources. Channel measurement resources may be, for example, Non Zero Power (NZP) CSI-RS resources. The measurement unit 223 may also derive interference measurements for CSI calculation based on interference measurement resources. Interference measurement resources may be at least one of the following: NZP CSI-RS resources for interference measurement, CSI-Interference Measurement (IM) resources, etc. CSI-IM may also be called CSI-Interference Management (IM), and may be interpreted interchangeably with Zero Power (ZP) CSI-RS. In this disclosure, CSI-RS, NZP CSI-RS, ZP CSI-RS, CSI-IM, CSI-SSB, etc., may be interpreted interchangeably.
[0394] In this disclosure, the transmitting unit and receiving unit of the terminal 20 may be composed of at least one of a transmitting / receiving unit 220 and a transmitting / receiving antenna 230.
[0395] The transmitting / receiving unit 220 may transmit a beam report initiated by the terminal. The control unit 210 may, after the transmission of the beam report, control the continuation of receiving the synchronization signal block associated with the reference signal index included in the beam report (first embodiment).
[0396] The control unit 210 may be controlled to continue receiving the synchronization signal block after the transmission of the beam report (first embodiment).
[0397] The transmitting / receiving unit 220 may report the maximum number of Quasi-Co-Location (QCL) characteristics of the storable synchronization signal blocks (second embodiment).
[0398] The control unit 210 may store the Quasi-Co-Location (QCL) characteristics of the synchronization signal block within a specific period (third embodiment).
[0399] (Hardware Configuration) The block diagram used in the description of the above embodiment shows functional units. These functional blocks (components) are realized by hardware, software, or a combination thereof. 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.
[0400] For example, a base station, terminal, network node, etc. in one embodiment of the present disclosure may function as a computer that processes the wireless communication method of the present disclosure. Figure 7 is a diagram showing an example of the hardware configuration of a base station and terminal according to one embodiment of the present disclosure. The base station 10 and 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.
[0401] In this disclosure, any two terms selected from the set of terms such as apparatus, circuit, device, section, unit, module, chip, and means may be read as interchangeable. The hardware configuration of the base station 10 and terminal 20 may include one or more of the devices shown in the figure, or it may be configured to omit some of the devices.
[0402] Each function in the base station 10 and 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 to control the reading, writing, or both of the reading and writing of data in the memory 1002 and storage 1003.
[0403] The processor 1001 controls the entire computer, for example, by running an operating system. The processor 1001 may be composed of a central processing unit (CPU) that includes interfaces with peripheral devices, control devices, arithmetic units, registers, etc. For example, at least a part of the control unit 110 (210) and the transmitting / receiving unit 120 (220) described above may be implemented by the processor 1001. Although only one processor 1001 is shown, there may be multiple processors.
[0404] Furthermore, the processor 1001 reads programs (program code), software modules, data, etc., from the storage 1003, the communication device 1004, or both the storage 1003 and the communication device 1004 into the memory 1002, and executes various processes accordingly. The program used is one that causes the computer to execute at least a part of the operations described in the above embodiment. For example, the control unit 110 (210) may be implemented by a control program stored in the memory 1002 and running on the processor 1001, and other functional blocks may be implemented similarly.
[0405] The various processes described above may be executed by a single processor 1001, or by two or more processors 1001 simultaneously, sequentially, or by other means. The processor 1001 may be implemented using one or more chips. The program may be transmitted from a network via a telecommunications line, or provided to the computer device via, for example, a communication device 1004.
[0406] Furthermore, this disclosure also provides a computer program product, which includes a computer program. This computer program product may implement the steps of the method described in the above embodiments when the computer program is executed by a computer (for example, a processor 1001).
[0407] Memory 1002 is a non-temporary computer-readable recording medium and may consist of, for example, Read Only Memory (ROM), Erasable Programmable ROM (EPROM), Electrically EPROM (EEPROM), Random Access Memory (RAM), or at least two combinations thereof. Memory 1002 may also be called a register, cache, main memory, etc. 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.
[0408] The storage 1003 is a [non-temporary] computer-readable recording medium, which may consist of, for example, a flexible disk, a floppy disk, an optical disk (e.g., Compact Disc ROM (CD-ROM), etc.), a digital multipurpose disk, a Blu-ray disk), a magneto-optical disk, a removable disk, a hard disk drive, a smart card, flash memory (e.g., a card, stick, key drive), a magnetic stripe, or at least two of these. The storage 1003 may also be called an auxiliary storage device.
[0409] The recording medium described above may be, for example, a memory 1002, a storage 1003, or a database, server, or other suitable medium including both the memory 1002 and the storage 1003.
[0410] The communication device 1004 is hardware (transceiver / receiver device) for communicating between computers via a wired network, a wireless network, or both wired and wireless networks, 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 a high-frequency switch, duplexer, filter, frequency synthesizer, or at least two combinations thereof. For example, the above-mentioned transmit / receive unit 120 (220), transmit / receive antenna 130 (230), etc., may be implemented by the communication device 1004. The transmit / receive unit 120 (220) may be implemented in physically or logically separated form, consisting of a transmit unit 120a (220a) and a receive unit 120b (220b).
[0411] 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., or at least two combinations thereof). 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., or at least two combinations thereof). The input device 1005 and the output device 1006 may be configured as an integrated unit (e.g., a touch panel).
[0412] 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.
[0413] Furthermore, the base station 10 and terminal 20 may be configured with hardware such as a microprocessor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a programmable logic device (PLD), a field programmable gate array (FPGA), a graphics processing unit (GPU), a neural processing unit (NPU), or a combination of at least two of these, and some or all of each functional block may be realized using such hardware. For example, the processor 1001 may be implemented using at least one of these hardware components.
[0414] In this disclosure, the term “processor” may encompass a single processor or a group of processors, including, for example, a single-core processor, a multi-core processor, multiple processors in a single device, or multiple processors that can communicate with each other by wire or wireless means. Similarly, the term “[non-temporary] computer-readable recording medium” may encompass a single storage medium or a group of storage mediums, including multiple storage mediums that can communicate with each other by wire or wireless means.
[0415] The devices in this disclosure, such as processors and storage media, may be distributed locally or remotely, and may perform processing by operating cooperatively or independently using buses, networks, the internet, clouds, etc.
[0416] 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.
[0417] (Modifications) Each aspect / embodiment described in this disclosure is Long Term Evolution (LTE), LTE-Advanced (LTE-A), International Mobile Telecommunications-Advanced (IMT-Advanced), 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 5G-Advanced (5G-A), 6th generation mobile communication system (6G), xth generation mobile communication system (xG (where x is, for example, an integer or decimal)), Future Radio Access (FRA), New Radio (NR), New radio access (NX), Future generation radio access (FX), Open Radio Access Network (Open RAN (O-RAN)), Wideband Code Division Multiple Access (W-CDMA®), Global System for Mobile communications (GSM®), CDMA2000, Ultra Mobile Broadband (UMB), Institute of Electrical and Electronics Engineers (IEEE) 802.11, IEEE 802.11x (where x is any string such as b, a, g, n, ac, ax, be, bn, etc., and x=n is Wi-Fi4, x=ac is Wi-Fi5, x=ax is Wi-Fi6 or Wi-Fi6E, x=be is Wi-Fi7, x=bn is Wi-Fi8, etc.)The invention may also be applied to systems based on technologies such as Wi-Fi (a registered trademark), IEEE 802.16 (WiMAX®), IEEE 802.20, Ultra-WideBand (UWB), Bluetooth®, network virtualization technologies (e.g., Network Function Virtualization (NFV), Service Function Chaining (SFC), Software Defined Networking (SDN)), or Low Power Wide Area (LPWA). Furthermore, each aspect / embodiment described in this disclosure may be applied to systems based on a combination of at least two of these technologies. Hereinafter, "based on" means not only systems that utilize the technologies, but also systems that utilize extensions or modifications of the technologies.
[0418] In the present disclosure, any two terms selected from the set of terms such as "Base Station (BS)", "radio base station", "fixed station", "NodeB", "eNodeB (eNB)", "gNodeB (gNB)", "Access Point (AP)", "Transmission Point (TP)", "Reception Point (RP)", "Transmission / Reception Point (TRP)", "Radio Unit (RU)", "Remote Unit (RU)", "Control Unit (CU)", "Distributed Unit (DU)", "Remote Radio Head (RRH)", "node", "gateway", "terrestrial base station", "stratospheric base station", "unmanned aerial vehicle", "High Altitude Platform Station (HAPS)", "airborne platform", "panel", "cell", "Radio Access Network (RAN)", and "network" may be used interchangeably. Each cell accommodated by a base station may be referred to by terms such as a macro cell, a small cell, a femto cell, a pico cell, a serving cell, and a super cell. In the present disclosure, any two terms selected from the set of terms such as "cell", "sector", "cell group", "carrier", "component carrier", "cluster", "Bandwidth Part (BWP)", and "carrier bandwidth" may be used interchangeably.
[0419] In the present disclosure, any two terms selected from the set of terms such as "Mobile Station (MS)", "user terminal", "User Equipment (UE)", "Device", "module", and "terminal" may be used interchangeably.
[0420] The terminal may 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, router (e.g., home router, mobile router, etc.), Telematics Control Unit (TCU), or some other appropriate term.
[0421] A base station and a terminal may each consist of one or more devices. At least some of the devices constituting a base station and a terminal may be called a transmitting device, a receiving device, a wireless communication device, etc. Furthermore, the devices constituting at least a part of each base station and terminal may be, but are not limited to, objects themselves such as 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, unmanned aerial vehicles, stratospheric base stations (e.g., High Altitude Platform Stations (HAPS)), artificial satellites (e.g., Low Earth Orbit (LEO) satellites, Middle Earth Orbit (MEO) satellites, Geostationary Earth Orbit (GEO) satellites), drones (registered trademark), multicopters, quadcopters, balloons, and Internet of Things (IoT) devices (e.g., smart meters, sensors), or include, but are not limited to, objects or devices mounted on such objects. Furthermore, the object in question may be a moving object (hereinafter referred to as a "moving object," without prejudice that the moving object may be in a stationary state) or a fixedly positioned object (hereinafter referred to as a "non-moving object").
[0422] Furthermore, the term "base station" in this disclosure may be interpreted as "terminal." For example, the various aspects / embodiments of this disclosure may be applied to configurations in which communication between a base station and a terminal is replaced with communication between multiple terminals (which may be called, for example, Device-to-Device (D2D), Vehicle-to-Everything (V2X), etc.) or communication over a Non-Terrestrial Network (NTN). In this case, the terminal 20 may have the functions that the base station 10 has. Also, terms such as "uplink" and "downlink" may be interpreted as terms corresponding to terminal-to-terminal communication (for example, "sidelink") or terms corresponding to NTN (for example, feeder link, service link). For example, uplink channel, downlink channel, etc., may be interpreted as sidelink channel.
[0423] Furthermore, this disclosure is also applicable when at least some of the equipment constituting the base station and terminal operates outside of the ground (for example, in the atmosphere or in outer space).
[0424] Similarly, the term "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 terminal 20 described above.
[0425] In this disclosure, operations performed by a base station may, in some cases, be performed by its upper node, or by a part of it (e.g., CU, RU, DU, etc.). It is clear that various operations performed for communication with terminals in a RAN or core network may be performed by at least a part of the base station and other network nodes other than the base station. The other network nodes may be a single node or a combination of multiple nodes. A network node is, for example, a node provided in various core networks such as an Evolved Packet Core (EPC) or a 5G Core Network (5GCN, 5GC), and provides one or more Network Functions (NFs).
[0426] Furthermore, in this disclosure, the action of "a terminal receiving information from a base station" is accompanied by the actions of "a base station transmitting the information to the terminal," "a base station generating the information," or both. Similarly, the action of "a terminal transmitting information to a base station" is accompanied by the action of "a base station receiving the information from the terminal." In addition, actions such as "a terminal is configured to..." or "a terminal is configured to..." may include the actions of "a base station transmitting configuration information regarding the terminal's settings" or "the terminal configuring a predetermined action based on the configuration information."
[0427] 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 at least two combinations thereof.
[0428] Physical layer signaling may also be called Layer 1 (L1) control information. MAC signaling may be called, for example, a MAC control element (CE), a MAC protocol data unit (PDU), etc. RRC signaling may also be called an RRC message or an information element (IE) within such an RRC message. Such RRC signaling may be a message used for, for example, controlling an RRC connection (e.g., setup, reconfiguration, establishment, reestablishment, release, or resume), mobility, measurement report, terminal capability notification, etc., or it may be an information element within such a message.
[0429] Furthermore, notification of information may be explicit or implicit. Explicit notification of information means notifying the information itself, while implicit notification of information may be notification of other information or the fulfillment of certain conditions which constitutes notification of the information.
[0430] Furthermore, information notification may include not only notifications between the same layer of different devices (for example, between lower layers or upper layers of base station 10 and terminal 20), but also notifications between different layers within the same or different devices (for example, between lower layers and upper layers within base station 10 or terminal 20). Also, information notification from one device to another may be carried out via one or more devices.
[0431] Any information described in this disclosure (e.g., variables, constants, parameters, settings) may be communicated from any first device (e.g., terminal / base station) to any second device (e.g., base station / terminal) to any second device (e.g., base station / terminal) to any first device (e.g., base station / terminal) to any second device (e.g., base station / terminal) to any second device (e.g., base station / terminal) to any second device (e.g., base station / terminal) to any second device (e.g., base station / terminal) to any second device (e.g., base station / terminal) to any second device (e.g., base station / terminal) to any second device (e.g., base station / terminal) to any second device (e.g., base station / base station
[0432] Each aspect / embodiment described in this disclosure may be used individually, in combination, or switched between 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. Also, at least one step may be omitted in the processing procedures, sequences, flowcharts, etc., of each aspect / embodiment described in this disclosure.
[0433] 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.
[0434] In this disclosure, a radio resource may be defined as a combination of units of resources in one or more domains, such as the time domain, frequency domain, spatial domain, code domain, and power domain.
[0435] For example, a resource in the time domain (which may also be called a time resource) may be defined by one or more time units. These one or more time units may include, for example, a radio frame, a subframe, a slot, a symbol, and a transmission time interval (TTI), or at least two of these, but the names of the time units are not limited to these. Furthermore, these time units may be fixed-length time units that do not depend on numerology, variable-length time units that depend on numerology, or both.
[0436] Examples of fixed-length time units include, but are not limited to, subframes consisting of one or more slots, and wireless frames containing multiple subframes. Examples of variable-length time units include, but are not limited to, symbols and slots containing a fixed number of symbols. A certain time unit may be divided into shorter time units. Examples of shorter time units include, but are not limited to, mini-slots consisting of fewer symbols than the number of symbols that make up a slot. Such time units may include, for example, time units used as units for scheduling, link adaptation, etc. Furthermore, any time unit in this disclosure may be interpreted as a substitute for another time unit.
[0437] Numerology refers to parameters that define the physical layer structure, and may be parameters based on at least one of the following: subcarrier spacing (SCS), symbol length, cyclic prefix length, and sampling time.
[0438] Resources in the frequency domain (which may also be called frequency resources) may be defined, for example, by one or more frequency units. Such one or more frequency units may include, for example, subcarriers, resource blocks (RBs), bandwidth parts (BWPs), carrier bandwidths, or at least two combinations thereof, but the names of frequency units are not limited to these. Furthermore, the number of subcarriers included in a frequency unit may be a fixed number regardless of the neurology, or it may be a variable number that changes depending on the neurology.
[0439] For example, an RB consists of a predetermined number of consecutive subcarriers in the frequency domain, and the number of subcarriers included in the RB may be the same regardless of the neurology, and may be, for example, 12, but is not limited thereto. Also, a BWP may consist of, for example, one or more consecutive RBs within a certain carrier bandwidth, but is not limited thereto. One or more BWPs may be set up for a terminal 20 within a single carrier, and at least one of the BWPs may be activated. Furthermore, any frequency unit in this disclosure may be interpreted as any other frequency unit.
[0440] Furthermore, resources in both the time domain and the frequency domain may be defined in one or more time / frequency units, for example, consisting of time units and frequency units. Such time / frequency units are, but are not limited to, a Resource Element (RE) consisting of one symbol and one subcarrier, a Resource Element Group (REG) consisting of a predetermined number of REs, or a Control Resource Set (CORESET) consisting of a predetermined number of symbols and a predetermined number of RBs.
[0441] Resources in a spatial domain (which may also be called spatial resources) may be defined, for example, by one or more spatial units. Such one or more spatial units include, but are not limited to, beams, Multi Input Multi Output (MIMO) layers, antenna ports, or at least two combinations thereof.
[0442] Resources in the code domain (which may also be called code resources) may be defined, for example, by one or more code units. These one or more code units include, but are not limited to, cyclic shifts (CS), orthogonal cover codes (OCC), or combinations thereof.
[0443] 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.
[0444] In this disclosure, the words "decide," "determine," "judge," "select," "specify," "compute," "calculate," "process," "derive," "look up / search / inquiry," "confirm," "assume," "expect," and "consider" may be interpreted interchangeably. Also, in this disclosure, performing a certain process (e.g., sending, receiving) may be interpreted interchangeably with deciding to perform that process. Furthermore, in this disclosure, "do not assume that..." may be interpreted interchangeably with "assume that..."
[0445] 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).
[0446] 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").
[0447] In this disclosure, "of," "for," "regarding," "related to," and "associated with" may be interpreted as being interchangeable.
[0448] 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.
[0449] 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.
[0450] In this disclosure, terms such as “precoding,” “precoder,” “weight (precoding weight),” “quasi-co-location (QCL),” “transmission configuration indication state (TCI state),” “spatial relation,” “spatial relation information,” “spatial domain filter,” “transmit power,” “phase rotation,” “antenna port,” “port,” “layer,” “number of layers,” “rank,” “resource,” “resource set,” “beam,” “beam width,” “beam angle,” “antenna,” “antenna element,” “panel,” “UE panel,” “transmitting entity,” and “receiving entity” may be used interchangeably.
[0451] 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)." Furthermore, a spatial domain filter may include at least one of a spatial domain transmission filter and a spatial domain reception filter.
[0452] In this disclosure, beam, sounding reference signal (SRS), resource indicator (SRS Resource Indicator (SRI)), control resource set (CORESET), CORESET pool, physical downlink shared channel (PDSCH), physical uplink shared channel (PUSCH), codeword (CW), transport block (TB), reference signal (RS) and the like may be interchangeable.
[0453] In this disclosure, TCI state, TCI, Downlink (DL) TCI state, Uplink (UL) TCI state, unified TCI state, common TCI state, joint TCI state, etc., may be interpreted interchangeably.
[0454] 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.
[0455] In this disclosure, the terms index, identifier (ID), identity (ID), indicator, indication, resource ID, etc., may be interpreted interchangeably. In this disclosure, the terms sequence, list, set, group, cluster, subset, etc., may be interpreted interchangeably.
[0456] In this disclosure, the group may include, for example, at least one of the following: a spatial relationship group, a Code Division Multiplexing (CDM) group, an RS group, a CORESET group, a Physical Uplink Control Channel (PUCCH) group, an antenna port group (e.g., a DMRS port group), a layer group, a resource group, a beam group, an antenna group, or a panel group.
[0457] The information in this disclosure (e.g., variables, constants, parameters, settings) may be interpreted as IDs of such information. For example, TCI status and TCI status ID may be interpreted as IDs of such information. In addition, the information in this disclosure may be interpreted as "a set of such information," "one or more such pieces of information," etc.
[0458] Any signal / channel in this disclosure (e.g., PUCCH) may be interpreted as another signal / channel (e.g., PUSCH, PDSCH, any RS). A signal / channel may be interpreted as a signal / channel for the same direction (e.g., if the above signal / channel is in the UL direction, it is UL, and if it is in the DL direction, it is DL), or as a signal / channel for the opposite direction (e.g., if the above signal / channel is in the UL direction, it is DL, and if it is in the DL direction, it is UL). Also, in this disclosure, descriptions relating to DL communication and descriptions relating to UL communication may be interpreted as one another. In this case, the operation of DL (UL) may be interpreted as the operation of the corresponding UL (DL). For example, the reception of PDSCH at a terminal may be interpreted as the transmission of PUSCH at the same terminal.
[0459] In this disclosure, "X's number," "X number," "the number of X(s)," and "a number of X(s)" may be interpreted as interchangeable. Herein, X may be replaced with a noun, gerund, or ordinary sentence as appropriate, depending on the context. In this disclosure, "number" may be interpreted as maximum number, minimum number, average number, total number, etc. Furthermore, in this disclosure, terms related to "value," "index," "number," and "quantity" may be interpreted as interchangeable.
[0460] Values / ranges in this disclosure may be interpreted as approximations, as if preceded by the words “about” or “near.” In this disclosure, “[A and B] [are] the same” (where A and B are any words) may mean “[A and B] [are] identical,” “[A and B] [are] almost the same,” “[A and B] [are] partly the same (or [partly] overlapped),” or “[There is] an error within a certain range [between A and B]” (i.e., these words may be interpreted as interchangeable). Furthermore, in this disclosure, "A and B are the same" may mean that at least part of A and at least part of B are the same (or overlapped).
[0461] In this disclosure, “one embodiment,” “several embodiments,” and “another embodiment” may be used interchangeably. In this disclosure, the terms “one embodiment,” “several embodiments,” and “another embodiment” do not necessarily all refer to the same embodiment, nor do they necessarily mean that they are mutually exclusive.
[0462] In this disclosure, expressions such as “at least one of A and B,” “at least one of A or B,” “A and / or B,” and “A / B” may be interpreted as including “only A,” “only B,” or “both A and B.” Furthermore, in this disclosure, expressions such as “at least one of A, B or C,” “at least one of A, B or C,” “A, B and / or C,” and “A / B / C” may be interpreted as including “only A,” “only B,” “only C,” “A and B,” “B and C,” “C and A,” or “all of A, B and C.” Similar reinterpretations may be applied to any expression in this disclosure that means "at least X of ..." (where the number of elements in "..." and X are arbitrary numbers).
[0463] In this disclosure, expressions such as “A, [and] B, and the like” / “such as A and B”,” “A, [or] B, or the like” / “such as A or B”,” “A, B, etc.” / “A, B, and so on” / “A, B, and so forth”,” and “A, B, [and / or] the others” may be interpreted as one another.
[0464] In this disclosure, expressions representing one / singular X (e.g., "a X," "one X," "a single X"), expressions representing one or more X (e.g., "one or more X(s)," "at least one of X(s)"), and expressions representing multiple X (e.g., "Xs," "more than one X(s)," "multiple X(s)," "a plurality of X(s)") may be interpreted as one another. These expressions may also be interpreted as one another with expressions that include specific wording (e.g., "pieces of," "amount of," etc., when X is an uncountable noun). For example, "a plurality of pieces of spatial relation information" may be interpreted as "a plurality of spatial relation information."
[0465] The above description of the disclosure is illustrative, and the present invention is not limited to the embodiments described herein. The disclosure can be implemented as modified and altered forms without departing from the spirit of the invention. The disclosure and its modifications and altered forms are included within the scope of the present invention and its equivalents.
[0466] This application is based on Japanese Patent Application No. 2025-077462, filed on May 7, 2025. All of its contents are included herein.
Claims
1. A terminal comprising: a transmitting unit that transmits a beam report initiated by the terminal; and a control unit that controls the continuation of receiving a synchronization signal block associated with a reference signal index included in the beam report after the transmission of the beam report.
2. The terminal according to claim 1, wherein the control unit controls the terminal to continue receiving the synchronization signal block after transmitting the beam report.
3. The terminal according to claim 1, wherein the transmitting unit reports the maximum number of Quasi-Co-Location (QCL) characteristics of the storable synchronization signal blocks.
4. The terminal according to claim 1, wherein the control unit stores the Quasi-Co-Location (QCL) characteristics of the synchronization signal block within a specific period.
5. A wireless communication method for a terminal, comprising the steps of: transmitting a beam report initiated by the terminal; and, after the transmission of the beam report, controlling the continuation of receiving a synchronization signal block associated with a reference signal index included in the beam report.
6. A base station having a receiving unit that receives beam reports initiated by a terminal, and a control unit that assumes that after the transmission of the beam report, the terminal controls the continuation of receiving synchronization signal blocks associated with the reference signal index included in the beam report.
