Terminal, wireless communication method, and base station
By optimizing CPU occupancy time for beam reporting through a terminal and base station configuration, the solution addresses the inefficiencies in existing systems, leading to improved communication quality and throughput.
Patent Information
- Application Number
- PCT/JP2026/016429
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2025-05-09
- Filing Date
- 2026-04-24
- Publication Date
- 2026-11-12
AI Technical Summary
Insufficient consideration of the duration of time the CSI processing unit is occupied for beam reporting in existing wireless communication systems leads to a decrease in communication performance and throughput.
A terminal and base station configuration that includes a receiving unit for beam report settings, a physical uplink control channel to trigger beam reports, and a physical uplink sharing channel to carry the beam reports, with the duration of channel state information processing determined based on channel measurement resources and signaling, optimizing CPU occupancy time.
Improves communication quality and throughput by efficiently managing CPU occupancy time for beam reporting, enhancing the performance of wireless communication systems.
Smart Images

Figure JP2026016429_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 existing wireless communication systems (e.g., NR), a terminal (user terminal, User Equipment (UE)) reports channel status information (CSI) to the network (NW, base station), allowing the NW to apply appropriate modulation and encoding to the downlink (DL) data.
[0006] However, the duration of time the CSI processing unit (CPU) is occupied for beam reporting (UEIBR) initiated by the terminal has not been adequately considered. Insufficient consideration of this could lead to a decrease in communication performance / throughput.
[0007] 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 performance / throughput.
[0008] A terminal according to one aspect of the present disclosure includes: a receiving unit that receives a beam report setting initiated by the terminal; a physical uplink control channel (PUCCH) that triggers the beam report; a physical uplink sharing channel (PUSCH) that carries the beam report; a control unit that determines the duration of time occupied by a channel state information (CSI) processing unit for the beam report based on at least one of one of one or more channel measurement resources for measuring the beam report and signaling for the beam report.
[0009] According to one aspect of this disclosure, communication quality / throughput can be improved.
[0010] Figure 1 shows an example of CPU occupancy time. Figures 2A and 2B show another example of CPU occupancy time. Figures 3A and 3B show an example of CSI reference resource and UE CSI calculation time. Figure 4 shows an example of UE CSI calculation time for AP CSI reporting. Figure 5 shows an example of table C-1 for CSI calculation delay requirement 1. Figure 6 shows an example of table C-2 for CSI calculation delay requirement 2. Figures 7A and 7B show an example of CPU occupancy time for AP CSI reporting. Figures 8A and 8B show an example of CPU occupancy time when the event conditions are met in Embodiment 1. Figure 9 shows an example of CPU occupancy time when the event conditions are not met in Embodiment 1. Figure 10 shows an example of CPU occupancy time when the event conditions are met in Embodiment 2. Figure 11 shows an example of CPU occupancy time related to a variation of Embodiment 2. Figure 12 shows an example of CPU occupancy time when the event conditions are met in Embodiment 3. Figure 13 is a diagram showing an example of a schematic configuration of a wireless communication system according to one embodiment of the present disclosure. Figure 14 is a diagram showing an example of a base station configuration according to one embodiment of the present disclosure. Figure 15 is a diagram showing an example of a terminal configuration according to one embodiment of the present disclosure. Figure 16 is a diagram showing an example of a hardware configuration of a base station and a terminal according to one embodiment of the present disclosure.
[0011] (Beam reporting type) <Intra-cell beam reporting in Rel. 15 / 16> Intra-cell beam reporting is supported in Rel. 15 / 16. For example, L1-RSRP / SINR reporting can be configured by upper-layer signaling (RRC).
[0012] For example, in the calculation of L1-RSRP, the UE may configure either or both a CSI-RS resource and / or an SS / PBCH block resource if the resource is associated with QCL type C / type D.
[0013] Furthermore, the UE may configure up to 16 CSI-RS resource sets, each containing up to 64 resources. In all resource sets, the total number of different CSI-RS resources is 128 or less.
[0014] In L1-RSRP reporting, if the upper layer parameter nrofReportedRS (for example, in CSI-ReportConfig) is set to 1, the reported L1-RSRP value is defined as a 7-bit value in the range of [-140 to -44] dBm with a step size of 1 dB.
[0015] Here, the maximum measurement of L1-RSRP is quantized to a 7-bit value in the range of [-140 to -44] dBm with a step size of 1 dB. The difference value of L1-RSRP is quantized to a 4-bit value.
[0016] The difference value is calculated with a step size of 2 dB, referencing the largest measurement that is part of the same L1-RSRP reporting instance.
[0017] For example, in L1-SINR calculation and channel measurement, the UE may configure either an NZP CSI-RS resource and / or an SS / PBCH block resource. Furthermore, for interference measurement, the UE may configure either an NZP CSI-RS resource or a CSI-IM resource.
[0018] For channel measurement, the UE can configure CSI resource settings for up to 64 CSI resources or up to 16 CSI-RS resource sets having SS / PBCH block resources.
[0019] In L1-SINR reporting, if the upper layer parameter nrofReportedRS is set to 1, the reported L1-SINR value is defined as a 7-bit value in the range of [-23 to 40] dBm with a step size of 0.5 dB.
[0020] If the upper layer parameter nrofReportedRS is set to a value greater than 1, or if the upper layer parameter groupBasedBeamReporting is set to "enabled", the UE will use the difference-based L1-SINR value for reporting.
[0021] The difference value is calculated with a step size of 1 dB, referencing the largest measurement that is part of the same L1-SINR reporting instance.
[0022] In this disclosure, the intra-cell beam report of Rel. 15 / 16 (which may also be simply called the intra-cell beam report) may be called a type 1 beam report (beam report type 1), or a beam report for an intra-cell beam switch.
[0023] <Inter-cell beam report for Rel. 17> As mentioned above, L1 / L2 inter-cell mobility is supported in Rel. 17. For example, a UE can send and receive UL / DL channels / signals to and from a PCI of a different cell than the PCI of the serving cell. For example, if a non-serving cell has a larger RSRP than the serving cell, the UE can send and receive UL / DL channels / signals to and from the non-serving cell without performing a handover.
[0024] In the L1-RSRP report, the absolute value / difference value of L1-RSRP may be used, as in Rel. 15 / 16. In the inter-cell beam report of Rel. 17 (Type 2-1 beam report described later), each L1-RSRP value is associated with a PCI ID (for the serving cell / additional cell / candidate cell). The association between the L1-RSRP value and the PCI ID may be set / instructed by upper-layer signaling / physical-layer signaling.
[0025] The configuration using upper-layer signaling supports up to seven additional cells. Note that ID=0 indicates the PCI of the serving cell.
[0026] In this disclosure, inter-cell beam reporting (in Rel. 17 / 18) may be referred to as Type 2 beam reporting (Beam reporting type 2). Type 2 beam reporting can be further classified into types 2-1 and 2-2, as described below.
[0027] In this disclosure, the beam report of Rel. 17 may be referred to as a type 2-1 beam report, or a beam report for inter-cell beam switching.
[0028] <Inter-cell beam reporting for Rel. 18> Furthermore, beam reporting for Rel. 18 is only supported as SSB-based L1-RSRP reporting (beam reporting). Here, the number of candidate cells L is one of 1 to 4, and the number of beams M per cell may be one of 1 to 4. For example, in beam reporting, a 7-bit absolute value (the largest L1-RSRP value among all cells) is reported for one cell, and all remaining L1-RSRP values are reported as difference values.
[0029] Regarding beam selection in SSB-based L1-RSRP reporting, the maximum value of M*L and the combination of M and L that can be set in RRC may vary depending on the UE capabilities.
[0030] In the L1-RSRP report, the absolute value / difference value of L1-RSRP may be used, as in Rel. 15 / 16 / 17.
[0031] In L1-RSRP reporting, the reported L1-RSRP value is defined as a 7-bit value in the range of [-140 to -44] dBm with a step size of 1 dB.
[0032] Here, the maximum measurement of L1-RSRP is quantized to a 7-bit value in the range of [-140 to -44] dBm with a step size of 1 dB. The difference value of L1-RSRP is quantized to a 4-bit value.
[0033] The difference value is calculated with a step size of 2 dB, referencing the largest measurement that is part of the same L1-RSRP reporting instance.
[0034] The L1-RSRP report includes the SSBRI between the configured candidate cells. In other words, the L1-RSRP report includes the SSBRI of the configured candidate cells and the corresponding L1-RSRP. The format may be the same as the existing specification.
[0035] In this disclosure, the beam report of Rel. 18 may be referred to as a type 2-2 beam report, or a beam report for cell switching. Note that the type 2-2 beam report does not include PCI information (PCI ID). Instead, the SSBRI may include PCI information. For example, if four cells have 64 SSBs, the SSBRI will be one of {0, 1, ..., 255}.
[0036] (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).
[0037] Beam management (UEIBM) initiated by UEIBR / UE can be used for measurement reporting, beam switching, cell switching, etc.
[0038] <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.
[0039] 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.).
[0040] 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.
[0041] <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.
[0042] UE Feature #1: UEIBR for MIMO in Rel. 19. UE Feature #2: UEIBR for mobility in Rel. 19.
[0043] 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.
[0044] 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).
[0045] 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.
[0046] This disclosure may be applied within the Unified TCI Framework.
[0047] 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.
[0048] <UEIBR for MIMO> The following may apply to the UEIBR for MIMO in Rel. 19.
[0049] - 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).
[0050] 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).
[0051] 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).
[0052] It should be noted that the events exemplified in this way do not exclude other events.
[0053] 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).
[0054] 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).
[0055] For example, for the current beam in event 2, at least one of the following beam options 2a to 2c may be supported: • Beam option 2a: The RS corresponding to the current beam is implicitly derived / determined based on the QCL RS 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.
[0056] 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).
[0057] 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.
[0058] If there are two QCL RSs in the indicated TCI state, the QCL RSs may be of QCL type D.
[0059] 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).
[0060] 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.
[0061] 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.
[0062] 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:
[0063] • Processing Option 1: An additional scheme is introduced. The RS for the current beam can be the CSI-RS for beam management derived from the QCL RS in the indicated TCI state. • Processing Option 2: TRS is 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.
[0064] 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.
[0065] 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.
[0066] The RS within that single RS resource set may be updated by MAC CE.
[0067] UEIBR for MIMO may be transmitted using UCI.
[0068] In a UCI-based UEIBR procedure using UCI, the following modes may be supported:
[0069] <<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).
[0070] 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.
[0071] Step 2: The UE detects a DCI format (which may also be called the first DL signal) indicating the second UL channel resource.
[0072] Step 3: The UE transmits the beam report using the resource (UCI) on the second UL channel.
[0073] 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.
[0074] In this case, periodic PUCCH resources (PUCCH format 0 / 1) can be set up by dedicated upper-layer signaling.
[0075] 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).
[0076] 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).
[0077] The RRC parameters may include, for example, period and offset setting parameters (periodicityAndOffset) and a PUCCH resource ID (e.g., PUCCH-ResourceID).
[0078] These RRC parameter specifications may also apply to cases using at least one CC (single CC).
[0079] 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.
[0080] 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.
[0081] A new 1-bit field in the DL grant DCI may be defined to instruct the transmission of the UEIBR.
[0082] PUCCH resources intended for HARQ-ACK transmission may be (re)used to transmit both HARQ-ACK and UEIBR.
[0083] <<Mode B>> Mode B relates to the UCI in the pre-configured resources for the second UL channel.
[0084] Step 1: The UE transmits a first UL channel (e.g., PUCCH). The first UL channel is a UL channel that notifies a second UL channel for transmitting beam reports, and may consist of one or more bits.
[0085] Step 2: The UE transmits a beam report on the second UL channel (for example, using a specific resource (UCI) within the channel).
[0086] Note that the notification in Step 1 may be included in a separate reporting instance from the beam report in Step 2.
[0087] 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.
[0088] In this case, periodic PUCCH resources (PUCCH format 0 / 1) can be set up by dedicated upper-layer signaling.
[0089] In either mode A or B as described above, cross-CC (component carrier) beam reporting may be supported.
[0090] 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).
[0091] 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).
[0092] The RRC parameters may include, for example, period and offset setting parameters (periodicityAndOffset) and a PUCCH resource ID (e.g., PUCCH-ResourceID).
[0093] These RRC parameter specifications may also apply to cases using at least one CC (single CC).
[0094] The second UL channel in step 2 may be, for example, a type 1 configured grant (CG) PUSCH or PUCCH.
[0095] <UEIBR for Mobility> The following may apply to the UEIBR for mobility (e.g., lower layer triggered mobility, LTM) in Rel. 19.
[0096] - MAC CE in semi-persistent / aperiodic PUCCH. - UCI in periodic / semi-persistent PUCCH, UCI in semi-persistent / aperiodic PUCCH.
[0097] 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).
[0098] The supported events may be the same as those for a Conditional Hand-Over (CHO).
[0099] For example, since candidate cells are set based on the L3 measurement report, L1-RSRP / SINR may be used as the threshold.
[0100] 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.
[0101] It may also be specified whether flexibility in the trigger time (e.g., 5 milliseconds, 10 milliseconds, 20 milliseconds) is required.
[0102] In the case of L1 measurements using UEIBR, at least the results of beam-level measurements may be used for event evaluation.
[0103] Events related to UEIBR for mobility may be broadly categorized into the following event types: • Event LTM2: The 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.
[0104] 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.
[0105] In the LTM configuration, the L1 measurement resource setting may support both SSB and CSI-RS beam settings.
[0106] 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).
[0107] 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.
[0108] UEIBR for mobility may be transmitted using MAC CE.
[0109] <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.
[0110] 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.
[0111] 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.
[0112] 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.
[0113] 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.
[0114] 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.
[0115] 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.
[0116] <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 (MAC) Control Element (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.
[0117] <<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.
[0118] (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.
[0119] 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.
[0120] Let's consider a scenario where a UE moves from a PCI#1 cell (serving cell) to a PCI#3 cell (additional cell) (overlapping with the serving cell). In this case, L1 / L2 switching of serving cells is not supported in Rel. 17.
[0121] 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).
[0122] <<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.
[0123] (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.
[0124] 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.
[0125] In Rel. 18, serving cells are switched via 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 be removed from the coverage of the current serving cell (e.g., Current serving cell).
[0126] <Rel. 18 LTM> The primary motivation for lower layer-triggered mobility (LTM) is to reduce downtime [in RACH-based cell switching]. LTM has several characteristics: ◆Handover can be performed without using RACH / RRC reconfiguration / MAC reset. ◆One or more candidate cells are in the same CU as the serving cell. ◆One or more candidate cells are on the same or different frequencies as the serving cell.
[0127] After the UE receives the LTM-Config from the serving cell, several steps are taken before a cell switch decision is made for one or more candidate cells: ◆ DL synchronization [between the UE and one or more candidate cells] ◆ L1 measurement report ◆ UL synchronization [between the UE and one or more candidate cells] ◆ TCI status activation [from the serving cell to the UE]
[0128] Subsequently, the serving cell determines the cell switch and, upon selecting one target cell from one or more candidate cells, sends a cell switch command (CSC, LTM cell switch command) MAC CE to the UE. The CSC MAC CE contains several pieces of information about the target cell of the cell switch [from one or more candidate cells], including: ◆ Configuration ID [to indicate the target cell] ◆ TCI status ID ◆ Timing advance (TA) value ◆ CFRA resource index (optional)
[0129] <Configurations in the CSI Reporting Framework for Rel. 18 LTM> In the CSI reporting configuration for Rel. 18 LTM, the resource configuration includes a list of candidate IDs that are one-to-one mapped to a list of SSB indices. Rel. 18 LTM only supports SSB-based L1-RSRP.
[0130] In LTM Rel. 18, the configuration of CSI-RS resources / resource sets may be provided under a parameter (LTM-TCI-Info) for a single LTM candidate ID.
[0131] The configuration of NZP CSI-RS resource sets follows the rules of Rel. 17 and has resource set-specific parameters.
[0132] <MAC CE-based event-triggered beam reporting for mobility> The use of MAC CE is being considered for L1 measurement reporting.
[0133] For example, an event-triggered L1 measurement may be reported from the UE to the network (NW) via the MAC CE.
[0134] The following is specified regarding existing resource allocations:
[0135] Logical channels may be prioritized in the following order (the highest priority may be placed first): • MAC CE for C-RNTI, or data from the Uplink Common Control Channel (UL-CCCH). • [Extended] MAC CE for Beam Fault Recovery (BFR), or MAC CE for Setting Grant (CG) Verification, or MAC CE for Multiple Entry CG Verification. • MAC CE for Sidelink (SL) CG Verification. • MAC CE for Listen Before Talk (LBT) failure. • MAC CE for SL LBT failure according to specific specifications. • MAC CE for Timing Advance Report. • MAC CE for Buffer Status Report (BSR) included for padding. • MAC CE for SL-BSR included for padding.
[0136] The prioritization of MAC CEs with the same priority level may depend on the UE implementation.
[0137] (CSI Reporting) Rel. 15 In NR, a terminal (also called a user terminal, User Equipment (UE), etc.) generates (also called determining, calculating, estimating, measuring, etc.) Channel State Information (CSI) based on a Reference Signal (RS) (or a resource for said RS), and transmits (also called reporting, feedback, etc.) the generated CSI to the network (e.g., a base station). The CSI may be transmitted to the base station using, for example, an uplink control channel (e.g., a Physical Uplink Control Channel (PUCCH)) or an uplink shared channel (e.g., a Physical Uplink Shared Channel (PUSCH)).
[0138] The RS used to generate the CSI may be at least one of the following: Channel State Information Reference Signal (CSI-RS), Synchronization Signal / Physical Broadcast Channel (SS / PBCH) block, Synchronization Signal (SS), or Demodulation Reference Signal (DMRS).
[0139] The CSI-RS may include at least one of Non Zero Power (NZP) CSI-RS and CSI-Interference Management (CSI-Interference Measurement, CSI-IM). The SS / PBCH block is a block that includes SS and PBCH (and corresponding DMRS), and may be called an SS block (SSB), etc. The SS may also include at least one of a Primary Synchronization Signal (PSS) and a Secondary Synchronization Signal (SSS).
[0140] Furthermore, CSI may include at least one of the following: Channel Quality Indicator (CQI), Precoding Matrix Indicator (PMI), CSI-RS Resource Indicator (CRI), SS / PBCH Block Resource Indicator (SSBRI, SSB Index), Layer Indicator (LI), Rank Indicator (RI), L1-RSRP (Layer 1 Reference Signal Received Power), L1-RSRQ (Reference Signal Received Quality), L1-SINR (Signal to Interference plus Noise Ratio), L1-SNR (Signal to Noise Ratio).
[0141] The UE may receive information regarding CSI reporting (report configuration information) and control CSI reporting based on that report configuration information. This report configuration information may be, for example, the "CSI-ReportConfig" information element (IE) of Radio Resource Control (RRC).
[0142] The reporting configuration information (for example, "CSI-ReportConfig" in RRC IE) may include, for example, at least one of the following: ◆ Information about the type of CSI report (report type information, for example, "reportConfigType" in RRC IE) ◆ Information about one or more quantities (one or more CSI parameters) of CSI to be reported (report quantity information, for example, "reportQuantity" in RRC IE) ◆ Information about the RS resources used to generate the quantity (the CSI parameter) (resource information, for example, "CSI-ResourceConfigId" in RRC IE) ◆ Information about the frequency domain to which the CSI report is applied (frequency domain information, for example, "reportFreqConfiguration" in RRC IE)
[0143] For example, the reporting type information may indicate a periodic CSI (P CSI) report, an aperiodic CSI (A CSI, AP CSI) report, or a semi-persistent CSI (SP CSI) report.
[0144] Furthermore, the reported quantity information may specify at least one combination of the above-mentioned CSI parameters (e.g., CRI, RI, PMI, CQI, LI, L1-RSRP, etc.).
[0145] Furthermore, the resource information may also be the ID of the RS resource. The RS resource may include, for example, a non-zero power CSI-RS resource or SSB and a CSI-IM resource (for example, a zero-power CSI-RS resource).
[0146] Furthermore, frequency domain information may indicate the frequency granularity of the CSI report. This frequency granularity may include, for example, wideband and subband. The wideband is the entire CSI reporting band. The wideband may be, for example, the entire carrier (component carrier (CC), cell, serving cell) or the entire bandwidth part (BWP) within a carrier. The wideband may also be referred to as the CSI reporting band, the entire CSI reporting band, etc.
[0147] Furthermore, a subband may be part of the wideband and may consist of one or more resource blocks (Resource Blocks (RBs) or Physical Resource Blocks (PRBs)). The size of the subband may be determined according to the size of the BWP (number of PRBs).
[0148] Frequency domain information may indicate whether to report wideband or subband PMI (frequency domain information may include, for example, the RRC IE's "pmi-FormatIndicator" used to determine whether to report wideband PMI or subband PMI). Based on at least one of the above-mentioned reporting quantity information and frequency domain information, the UE may determine the frequency granularity of the CSI report (i.e., whether to report wideband PMI or subband PMI).
[0149] If wideband PMI reporting is established (decided), one wideband PMI may be reported for the entire CSI reporting band. On the other hand, if subband PMI reporting is established, a single wideband indication i1 may be reported for the entire CSI reporting band, and one subband indication i2 (e.g., subband indication for each subband) may be reported for one or more subbands within the entire CSI reporting band.
[0150] The UE performs channel estimation using the received RS and estimates the channel matrix H. The UE then feeds back the index (PMI) determined based on the estimated channel matrix.
[0151] PMI may represent a precoder matrix (also simply called a precoder) that a UE considers appropriate for use in downlink (DL) transmissions to the UE. Each value of PMI may correspond to a single precoder matrix. A set of PMI values may correspond to a different set of precoder matrices called a precoder codebook (also simply called a codebook).
[0152] In a spatial domain, a CSI report may include one or more types of CSIs. For example, the CSI may include at least one of a first type (Type 1 CSI) used for single-beam selection and a second type (Type 2 CSI) used for multi-beam selection. A single beam may be rephrased as a single layer, and a multi-beam as multiple beams. Furthermore, a Type 1 CSI may not assume multi-user multiple input multiple output (MU-MIMO), while a Type 2 CSI may assume multi-user MIMO.
[0153] The above codebooks may include a codebook for Type 1 CSI (also referred to as a Type 1 codebook, etc.) and a codebook for Type 2 CSI (also referred to as a Type 2 codebook, etc.). Furthermore, Type 1 CSI may include Type 1 single-panel CSI and Type 1 multi-panel CSI, and different codebooks (Type 1 single-panel codebook and Type 1 multi-panel codebook) may be specified for each.
[0154] The Upbound Control Information (UCI) type may include at least one of Hybrid Automatic Repeat reQuest ACKnowledgement (HARQ-ACK), scheduling request (SR), or CSI. The UCI may be carried by PUCCH or by PUSCH.
[0155] In Rel. 15 NR, the UCI may include one CSI part for wideband PMI feedback. CSI report #n includes PMI wideband information, if reported.
[0156] In Rel. 15 NR, the UCI may include two CSI parts for subband PMI feedback. CSI part 1 contains wideband PMI information. CSI part 2 contains one wideband PMI piece and several subband PMI pieces. CSI parts 1 and 2 are encoded separately.
[0157] In Rel. 15 NR, the UE is configured by a higher layer with N (N≧1) CSI reporting settings and M (M≧1) CSI resource settings. For example, a CSI reporting setting (CSI-ReportConfig) includes a resource setting for channel measurement (resourcesForChannelMeasurement), a CSI-IM resource setting for interference (csi-IM-ResourceForInterference), an NZP CSI-RS setting for interference (nzp-CSI-RS-ResourceForInterference), and a report quantity (reportQuantity). Each of the resource settings for channel measurement, the CSI-IM resource setting for interference, and the NZP CSI-RS setting for interference is associated with a CSI resource setting (CSI-ResourceConfig, CSI-ResourceConfigId). The CSI resource configuration includes a list of CSI-RS resource sets (csi-RS-ResourceSetList, for example, the NZP CSI-RS resource set or the CSI-IM resource set).
[0158] To enable more dynamic channel / interference hypotheses for NCJT, targeting both FR1 and FR2, evaluation and specification of CSI reporting for at least one multi-TRP and multi-panel transmission of DL are being considered.
[0159] In this disclosure, Type 1 and Type I may be interpreted as interchangeable. In this disclosure, Type 2 and Type II may be interpreted as interchangeable.
[0160] In the present disclosure, CSI-RS, periodic CSI-RS (P CSI-RS), semi-persistent CSI-RS (SP CSI-RS), and aperiodic CSI-RS (AP CSI-RS, A CSI-RS) may be read interchangeably with one another. In the present disclosure, CSI-RS, periodic CSI report (P CSI report), semi-persistent CSI report (SP CSI report), and aperiodic CSI report (AP CSI report, A CSI report) may be read interchangeably with one another.
[0161] <CSI Trigger State> In the present disclosure, a trigger state, a CSI trigger state, and a trigger state for CSI report may be read interchangeably with one another.
[0162] The trigger state (CSI report trigger) is started using the CSI request field in DCI. When all bits [values] of the CSI request field in DCI are set to 0, this may mean that no CSI is requested.
[0163] The number of CSI trigger states configured in the higher layer parameter CSI-AperiodicTriggerStateList is 2 N TS If greater than −1, the UE may receive a sub-selection indication. The sub-selection indication (e.g., MAC CE) may be used to map up to 2 N TS −1 trigger states to the codepoints of the CSI request field in DCI.
[0164] That is, the MAC CE, when the number of configured trigger states is 2 N TS If greater than −1, may be used to activate up to 2 N TS trigger states for further DCI indication via the CSI request field.
[0165] Here, N TSThis may represent the number of bits in the CSI request field. The CSI request field is configured variably with 0 to 6 bits and is determined by the higher-layer parameter reportTriggerSize.
[0166] The maximum number of trigger states is 2. N TS - There is one trigger state, and each trigger state may correspond to a code point in the CSI request field within the DCI.
[0167] Each trigger state may include multiple (for example, up to 16) reporting configurations (CSI-ReportConfig).
[0168] (Data Physical Layer Procedures / Physical Downlink Shared Channel Related Procedures) <UE Procedures for CSI Reporting / CSI Framework / CSI Processing Criteria> <<Maximum Number of Simultaneous CSI Calculations (Number of CPUs) and the Number of CPUs Dedicated to CSI Calculations>> N CPU This implies the number of CSI processing units (CPUs). UE uses several capability pieces of information to determine the number of supported simultaneous CSI calculations (maximum number of simultaneous CSI calculations) N. CPU Report / disclose / state:
[0169] ◆[within csi-ReportFramework within MIMO-ParametersPerBand] simultaneousCSI-ReportsPerCC. MIMO-ParametersPerBand is used to transmit MIMO-related parameters specific to a given band. csi-ReportFramework indicates whether the UE supports the CSI reporting framework. csi-ReportFramework indicates whether the UE supports the CSI reporting framework. simultaneousCSI-ReportsPerCC indicates the number of CSI reports that the UE can simultaneously measure and process within one CC of a band for which this capability is provided. CSI reports include periodic, semi-persistent, and aperiodic CSIs, and arbitrary latency classes and codebook types. CSI reports within simultaneousCSI-ReportsPerCC include beam reports and CSI reports.
[0170] ◆ [Within CA-ParametersNR] simultaneousCSI-ReportsAllCC. simultaneousCSI-ReportsAllCC indicates whether the UE supports the CSI reporting framework and the number of CSI reports that the UE can process simultaneously across all CCs (master cell group (MCG) and secondary cell group (SCG) in the case of NR-DC). CSI reports include periodic, semi-persistent, and aperiodic CSIs, and any latency class and codebook type. CSI reports within simultaneousCSI-ReportsAllCC include beam reports and CSI reports. This parameter further limits simultaneousCSI-ReportsPerCC and Phy-ParametersFRX-Diff within MIMO-ParametersPerBand for each band in a given band combination.
[0171] UE is N CPU If supporting multiple simultaneous CSI calculations, the UE will have N for processing CSI reports. CPUIt is assumed to have n CPUs. If L CPUs are occupied for the calculation of the CSI report within a given OFDM symbol, then UE is N CPU - It has L unoccupied CPUs. CPU -On the same OFDM symbol where L CPUs are not occupied, N CSI reports start occupying their respective CPUs, and each of the N CSI reports n=0,...,N-1 CPU (n) When corresponding to (number of occupied CPUs and number of consumed CPUs for CSI reporting), the UE follows the priority rules and assigns the lowest priority (highest priority value Pri iCSI It is not required to update (calculate, process) NM requested CSI reports from (y,k,c,s). Here, 0≦M≦N is Σ n=0 M-1 O CPU (n) ≤N CPU This is the maximum value for which -L holds true.
[0172] UE is N CPU It is not expected that the AP CSI trigger state will be set with more than one Report Setting. Processing CSI reports occupies several CPUs for several symbols, as in the following processes 1, 2, a, and 3. Processing CSI reports involves 0, 1, or more (O) CPU It occupies / consumes a certain number of CPUs (CPU occupancy rule).
[0173] ◆Process 1 In the case where CSI reporting is configured using CSI-ReportConfig with the higher layer parameter reportQuantity set to 'none' and CSI-RS-ResourceSet with the higher layer parameter trs-Info, CPU = 0
[0174] ◆Process 2 (Beam Management) In a CSI report using ltm-CSI-ReportConfig, or in a CSI report using CSI-ReportConfig with a reportQuantity that is set to 'cri-RSRP', 'ssb-Index-RSRP', 'cri-SINR', 'ssb-Index-SINR', 'cri-RSRP-Capability[Set]Index', 'ssb-Index-RSRP-Capability[Set]Index', 'cri-SINR-Capability[Set]Index', 'ssb-Index-SINR-Capability[Set]Index', or 'none' [when a CSI-RS-ResourceSet with the upper layer parameter trs-Info is not set], O CPU = 1
[0175] ◆Process a (TDCP report) For a CSI report using CSI-ReportConfig with the upper layer parameter reportQuantity set in 'tdcp' and the number of delays Y set by the upper layer parameter Y, O CPU =(Y+1). Here, the value of X≧1 is reported by the UE ability.
[0176] ◆Process 3 In a CSI report using CSI-ReportConfig with the higher layer parameter reportQuantity set in 'cri-RI-PMI-CQI', 'cri-RI-i1', 'cri-RI-i1-CQI', 'cri-RI-CQI', or 'cri-RI-LI-PMI-CQI', O CPU This is based on the following process 3-x:
[0177] ―◆Process 3-1 (Cases where UE can use the maximum UE capability) max{μ PDCCH , μ CSI-RS , μ ULIf} ≤ 3 and L=0 CPUs are occupied, a PUSCH with at least one transport block and HARQ-ACK is triggered aperiodically, and the CSI corresponds to a single CSI with wideband frequency-granularity and 4 or fewer CSI-RS ports in a single resource without CRI reporting, and codebookType is set to 'typeI-SinglePanel' and reportQuantity is set to 'cri-RI-CQI', O CPU =N CPU μ PDCCH This is the subcarrier spacing (SCS) setting for PDCCH. CSI-RS This is the SCS setting for CSI-RS. UL This is the SCS setting for UL BWP to which CSI reports are sent.
[0178] ―◆Process 3-2 (NCJT CSI case) When a CSI-ReportConfig with a codebookType set in 'typeI-SinglePanel' is configured, and the corresponding CSI-RS resource set for channel measurement is configured with two resource groups and N resource pairs, O CPU =X・N+M, where X is the number of CPUs occupied by pairs of CMRs according to the UE capability. The UE capability mTRP-CSI-numCPU-r17 represents the number of CPUs occupied by pairs of CMRs for the NCJT CSI assumption (hypotheses). s =K1+K2 resources. For the NZP CSI-RS resource set for channel measurement, with resource group 1 having K1 resources and resource group 2 having K2 resources, for the M1 resources and M2 resources associated with the CRI value, M=M1+M2.
[0179] ―◆Process 3-3 (Case of CSI Report Subconfiguration [for NES]) If CSI-ReportConfig contains a list of L subconfigurations provided by the higher-layer parameter csi-ReportSubConfigToAddModList, O CPU This is based on the following process 3-3-x: --◆Process 3-3-1 P In the CSI report, O CPU =Σ i=1 L K s i Here, K s i This is the number of CSI-RS resources corresponding to the i-th sub-setting. --◆Process 3-3-2 In AP CSI reports and SP CSI reports, O CPU =Σ i=1 N K s i Here, K s i This is the number of CSI-RS resources corresponding to the i-th sub-configuration. The i-th sub-configuration is the i-th sub-configuration out of the L sub-configurations contained within the CSI-ReportConfig, selected from the specified N sub-configurations. N ≤ L, N ≥ 1.
[0180] ―◆Process 3-4 (CJT CSI case) A CSI-ReportConfig is set with the upper layer parameter reportQuantity set in 'cri-RI-PMI-CQI' and the codebookType set in 'typeII-CJT-r18' or 'typeII-CJT-PortSelection-r18', and the corresponding 1 < N TRP If an NZP-CSI-RS-ResourceSet for channel measurement with ≤4 resources is configured, O CPU =X・N TRP Here, the value of X≧1 is reported by the UE capability.
[0181] ―◆Process 3-5 (Doppler CSI case) If a CSI-ReportConfig is set with the upper layer parameter reportQuantity set in 'cri-RI-PMI-CQI' and the codebookType set in 'typeII-Doppler-r18' or 'typeII-Doppler-PortSelection-r18', O CPU This is based on the following process 3-5-x: --◆Process 3-5-1 If the corresponding CSI-RS resource set for channel measurement is aperiodic (AP) and is set up with K CSI-RS resources, then for K=12, O CPU = 8, and for K < 12, O CPU = Y1・K. Here, Y1∈{1,2,3} is reported by UE capability indication. ---◆Process 3-5-2 If the corresponding CSI-RS resource set for channel measurement is periodic (P) or semi-persistent (SP) and is set up with a single CSI-RS resource, then for N4=1, O CPU =4, and for N4 > 1, O CPU =Y2・N4≧4. Here, N4 is set by the upper layer parameter N4, and Y2∈{2 / 3,1,2,3} is reported by the UE capability representation.
[0182] ―◆Process 3-6 (Other Cases) In other cases, O CPU =K s That is. K s This is the number of CSI-RS resources in the CSI-RS resource set for channel measurement.
[0183] As mentioned above, when L CPUs are occupied, UE is Σ n=0 M-1 O CPU (n) ≤N CPU -Update the CSI report as long as it is L.
[0184] <<CPU Occupancy Period>> In a CSI report using CSI-ReportConfig with a higher-level parameter reportQuantity that is not set to 'none', or in a CSI report using LTM-CSI-ReportConfig, one or more CPUs are occupied during the following multiple OFDM symbols (CPU occupancy period).
[0185] ◆[Except for the first SP CSI report on PUSCH after the PDCCH that triggers the report, and SP CSI reports on PUSCH with the upper layer parameter codebookType set to 'typeII-Doppler-r18' or 'typeII-Doppler-PortSelection-r18'] A P CSI report or SP CSI report is one in which the latest CSI-RS / CSI-IM / SSB occasion is prior to (but not later than) the corresponding CSI reference resource, and the P corresponds to a CSI-ReportConfig containing a list of subconfigurations provided by csi-ReportSubConfigToAddModList, which is one or more CSI-RS / CSI-IM / SSB resources for channel or interference measurement. The SP corresponding to CSI-ReportConfig, which includes one or more CSI-RS / CSI-IM resources associated with all subconfigurations configured for CSI reporting, or a list of subconfigurations provided by csi-ReportSubConfigToAddModList, occupies one or more CPUs (CPU occupancy period) from the first symbol of the earliest resource to the last symbol of the configured PUSCH / PUCCH carrying that report.
[0186] ◆ An AP CSI report occupies one or more CPUs from the first symbol after the PDCCH that triggers the CSI report until the last symbol of the scheduled PUSCH that carries the report (CPU occupancy period, Figure 1). If the PDCCH reception includes two corresponding PDCCH candidates from two search space sets, the PDCCH candidate that ends later is used to determine the CPU occupancy period.
[0187] ◆The first SP CSI report on a PUSCH after a PDCCH trigger occupies one or more CPUs from the first symbol after that PDCCH until the last symbol of the scheduled PUSCH carrying that report. If the PDCCH reception includes two corresponding PDCCH candidates from two search space sets, the PDCCH candidate that ends later is used to determine the duration of CPU occupancy.
[0188] ◆SP CSI reports on PUSCH with a CSI-ReportConfig set to 'typeII-Doppler-r18' or 'typeII-Doppler-PortSelection-r18' with the higher-layer parameter codebookType are not after the CSI reference resource, K P From the first symbol of the second most recent consecutive P / SP CSI-RS occasion to the last symbol of the PUSCH carrying its report, one or more CPUs are occupied. Here, K P The values for ∈{1,2,4} are displayed / reported by UE capabilities.
[0189] In a CSI report using CSI-ReportConfig with the upper layer parameter reportQuantity set to 'none' and a CSI-RS-ResourceSet with the upper layer parameter trs-info not set, one or more CPUs are occupied during the following multiple OFDM symbols (CPU occupancy period).
[0190] ◆[Except for the first SP CSI report on PUSCH after the PDCCH that triggers the report] The SP CSI report occupies one or more CPUs (CPU occupancy period, Figure 2A) from the first symbol of the earliest of the one or more transmission occasions of the P or SP CSI-RS / SSB resource for channel measurement for L1-RSRP calculation to after the Z'3 symbol of the last symbol of the latest CSI-RS / SSB resource for channel measurement for L1-RSRP calculation within the transmission occasion.
[0191] ◆AP CSI reporting occupies one or more CPUs from the first symbol after the PDCCH that triggers the CSI reporting, through the Z3 symbol of the first symbol after the PDCCH that triggers the CSI reporting, and through the Z'3 symbol of the last symbol of the latest CSI-RS / SSB resource for channel measurement for L1-RSRP calculation, up to the last symbol (CPU occupancy period, Figure 2B).
[0192] In this disclosure, the terms CPU occupancy period, CPU occupancy time, CPU occupancy duration, the period from the start of a CSI resource for P CSI reporting or SP CSI reporting to the end of that CSI reporting, and the period from the end of triggering for AP CSI reporting to the end of that CSI reporting may be interpreted interchangeably.
[0193] <<CSI-RS Resource Counting (Active Resource Counting, ARC)>> Within any given slot, the UE does not assume / expect to have more active CSI-RS ports or active CSI-RS resources within the active BWP than the number reported as capacity. NZP CSI-RS resources are active for a duration of time (active duration) as defined below: ◆ The duration for an AP CSI-RS begins at the end of the PDCCH containing its request and ends at the end of the scheduled PUSCH containing the report associated with that AP CSI-RS. ◆ The duration for an SP CSI-RS begins at the end of the time in which an activation command is applied and ends at the end of the time in which a deactivation command is applied. ◆The duration for a PCSI-RS begins when that PCSI-RS is configured by upper-layer signaling and ends when that PCSI-RS configuration is released.
[0194] If a CSI-RS resource is referenced N times by one or more CSI reporting settings that are not configured with the higher-layer parameter csi-ReportSubConfigToAddModList, then that CSI-RS resource and the CSI-RS ports within that CSI-RS resource are counted N times.
[0195] In a channel measurement CSI-RS resource set configured with two resource groups and N resource pairs, if a CSI-RS resource is referenced X times by at least one of the M CSI-RS resources and one or two resource pairs, then the CSI-RS resource and the CSI-RS ports within that CSI-RS resource are counted X times.
[0196] In a CSI-ReportConfig containing a list of L subconfigurations provided by the higher-layer parameter csi-ReportSubConfigToAddModList, if a CSI-RS resource is referenced by M subconfigurations out of N subconfigurations triggered for CSI reporting to an AP CSI-RS resource, or out of L subconfigurations configured for CSI reporting to a P CSI-RS resource or an SP CSI-RS resource, then that CSI-RS resource is counted M times, and the CSI-RS ports within that CSI-RS resource are counted max(Σ s=1 M P s It is counted ,P) times. Here, P is the number of ports set by nrofPorts, and if the corresponding antenna port subset indicator [portsubsetIndicator] is set, P s This is the number of CSI-RS ports in the sub-settings derived from that indicator, otherwise P s = P.
[0197] For a P CSI-RS resource or SP CSI-RS resource within a CSI-RS resource set for channel measurement, which is linked to a CSI-ReportConfig configured with the higher-layer parameter codebookType set in 'typeII-Doppler-r18' or 'typeII-Doppler-PortSelection-r18', the CSI-RS resource and the CSI-RS port within that CSI-RS resource are K P It is counted multiple times. P The values for ∈{1,2,4} are displayed / reported by UE capabilities.
[0198] A P CSI-RS is always counted as an active CSI-RS, regardless of whether it is received on its OFDM symbol or not.
[0199] UE reports UE capability information (codebookParameter) regarding the codebook for each band in the CSI report.
[0200] The codebookParameter indicates the codebook (type) and the corresponding parameters supported by the UE. Reporting parameters for Type 1 single panel is mandatory. Reporting parameters for Type 1 multi-panel, Type 2, and Type 2 port selection is optional. The parameters may include at least one of the following: maxNumberTxPortsPerResource, maxNumberResourcesPerBand, and totalNumberTxPortsPerBand. maxNumberTxPortsPerResource indicates the maximum number of transmit ports in a single resource. maxNumberResourcesPerBand indicates the maximum number of resources used simultaneously across all CCs in a single band. totalNumberTxPortsPerBand indicates the maximum number of transmit ports used simultaneously across all CCs in a single band.
[0201] In this disclosure, CPU utilization, CPU utilization rate, CPU utilization time, number of occupied CPUs, number of CPUs, O CPU , O CPU (n) , Σ n=0 M-1 O CPU (n) The terms "number of occupied CPUs" and "number of consumed CPUs" may be interpreted interchangeably.
[0202] In this disclosure, the number of processes / calculations, the number of CSI reports, the number of CSI calculations, the number of concurrent CSI calculations, the number of CSI reports that can be measured and processed simultaneously, the number of CSI processes, the number of CPUs, and the number (count) of CSI-RS resources / CSI-RS ports that are calculated / measured / processed for CSI are interchangeable.
[0203] In the present disclosure, a CSI-RS resource and an active resource may be read interchangeably. In the present disclosure, CSI-RS resource counting and Active Resource Counting (ARC) may be read interchangeably. In the present disclosure, the number of CSI-RS resources and the number of active resources may be read interchangeably.
[0204] <UE Procedure for CSI Reporting / CSI / CSI Reference Resource Definition> The CSI reference resource for a serving cell is defined as follows. ◆ In the frequency domain, the CSI reference resource is defined by a group of multiple DL PRBs corresponding to the band to which the derived CSI relates. ◆ In the time domain, the CSI reference resource for CSI reporting in UL slot n' is defined by a single DL slot n-n CSI_ref -K offset ·2 μ_DL / 2 μ_Koffset . Here, K offset is a parameter configured by a higher layer, and μ_K_offset is the subcarrier spacing configuration for K, with a value of 0 in Frequency Range (FR) 1. -◆ Here, n is given by the following equation: n=floor(n'·2 offset / 2 μ_DL )+floor(N μ_UL slot,offset,UL / 2μ_offset,UL-N CA slot,offset,DL / 2μ_offset,DL)·2 CA ). μ_DL and μ_UL are the subcarrier spacing configurations for DL and UL, respectively. N μ_DL slot,offset and μ_offset are determined by a higher layer-configured ca-SlotOffset for the cell transmitting UL and DL. -◆ For P / SP CSI reporting, the following procedure is defined. --◆ If a single CSI-RS / SSB resource for channel measurement is configured, n CA corresponds to a valid DL slot, and 4·2 CSI_ref μ_DL This is the minimum value. --◆If multiple CSI-RS / SSB resources are configured for channel measurement, n CSI_ref 5.2 μ_DL This is the minimum value. —◆In AP CSI reporting, if DCI instructs the UE to report the CSI in the same slot as the CSI request, n CSI_ref n is a value such that the referenced resource is in the same valid DL slot as the corresponding CSI request; otherwise, n CSI_ref is slot nn CSI_ref floor(Z' / N) such that it corresponds to an active DL slot. symb slot This is the minimum value greater than or equal to ). Here, Z' corresponds to the [CSI calculation] delay requirement. N symb slot This is the number of symbols in the slot. —When P or SP's CSI-RS / CSI-IM or SSB is used for channel / interference measurement, UE is not expected to measure channel / interference with respect to the CSI-RS / CSI-IM / SSB where the last OFDM symbol is received, from the Z' symbol before the transmission time of the first OFDM symbol in the AP CSI report.
[0205] A slot in a serving cell is considered a valid DL slot if it contains at least one DL or flexible symbol set by a higher layer, and the slot is not within the measurement gap set for the UE.
[0206] As shown in the example in Figure 3A, the CMR for measurement for AP CSI reporting on the PUSCH is prior to the CSI reference resource (not after the CSI reference resource). The slot of that CSI reference resource is the same slot as the PDCCH (CSI request) that triggers that CSI report (the same slot as the PUSCH that carries that CSI report) (n CSI_ref =0), or floor(Z' / N) from the slot of that PUSCH. symb slot ) is only the previous slot (between CMR and PUSCH, nCSI_ref =floor(Z' / N symb slot (It is [slot] or higher).
[0207] As shown in the example in Figure 3B, the time between the P / SP CMR for measurement for AP CSI reporting on the PUSCH and the start of that PUSCH is greater than the Z' symbol [corresponding to the UE CSI calculation time (CSI calculation delay requirement)].
[0208] <UE CSI Calculation Time> The [UE] CSI calculation time is the processing time for AP CSI reporting. UE reports CSI to gNB if several of the following conditions are met: ◆Condition 1: The time gap #1 (time from end of instruction to start of report) between the last symbol of PDCCH and the first symbol of PUSCH is greater than or equal to Z symbols. ◆Condition 2: If AP CSI-RS is used for reporting, the time gap #2 (time from end of measurement to start of report) between the last symbol of the latest AP CSI-RS and the first symbol of PUSCH is greater than or equal to Z' symbols.
[0209] (Z,Z') depends on the computational load of CSI.
[0210] When a CSI request field on DCI triggers an [AP] CSI report on PUSCH, the UE provides a valid CSI report for the nth triggered report if the following condition (Figure 4) is met: ◆ The first uplink symbol carrying one or more corresponding CSI reports and including the effect of timing advance is symbol Z ref Do not start earlier than (from the last symbol of the PDCCH that carries that DCI to Z ref (Starting after the symbol has elapsed), and ◆The first uplink symbol that carries the nth CSI report and includes the effect of timing advance is symbol Z' ref (n) Do not start earlier than (n) (from the last symbol of the latest AP CMR (AP CSI-RS) for the nth triggered CSI report, Z' ref (n) Starts after the passage of symbols.
[0211] Here, Zref The T at the end of the last symbol of the PDCCH that triggers one or more CSI reports. proc,CSI =(Z)(2048+144)・κ² -μ ・T C +T switch It is defined as the next UL symbol having a later-starting cyclic prefix (CP) (the number of symbols between the last symbol of that PDCCH and that UL symbol is Z ref Therefore, the time from the end of the last symbol of that PDCCH to the start of that UL symbol is T proc,CSI That's all.) Here, Z' ref (n) is the end of T' of the last symbol within the most recent period among the following multiple resources when AP CSI-RS is used for channel measurement for the nth triggered CSI report. proc,CSI =(Z')(2048+144)・κ2 -μ ・T C Defined as the next UL symbol with a later starting CP (the number of symbols between the last symbol in the most recent period among its multiple resources and that UL symbol is Z') ref (n) is such that the time from the end of the last symbol in the most recent period among the multiple resources to the start of that UL symbol is T' proc,CSI (End of statement): For CSI-ReportConfig, or for all triggered sub-configurations if CSI-ReportConfig includes multiple sub-configurations, the multiple periods are the periods for the AP CSI-RS resource for channel measurement, the AP CSI-IM used for interference measurement, and the AP NZP CSI-RS for interference measurement.
[0212] Here, T switch This is defined in the specification and applies only when Z1 is applicable.
[0213] If a PDCCH reception includes two corresponding PDCCH candidates from two search space sets, the PDCCH candidate that terminates later in time is used to determine the last symbol of the PDCCH that triggers the CSI report.
[0214] Z, Z', and μ are defined as follows:
[0215] For m=0,...,M-1, Z=max(Z(m)). For m=0,...,M-1, Z'=max(Z'(m)). Here, M is the number of updated CSI reports. (Z(m),Z'(m)) correspond to the m-th updated CSI report and are defined as follows: Here, CSI computation delay requirement 1 represents (Z1,Z'1) [symbol] for μ∈{0,1,2,3} (Figure 5, Table C-1), and CSI computation delay requirement 2 represents (Z1,Z'1), (Z2,Z'2), (Z3,Z'3) [symbols] for μ∈{0,1,2,3,4,5,6} (Figure 6, Table C-2).
[0216] ◆max{μ PDCCH ,μ CSI-RS ,μ UL If} ≤ 3, and L=0 CPUs are occupied, and the CSI to be transmitted is a single CSI, corresponds to wideband frequency granularity, corresponds to 4 or fewer CSI-RS ports in a single resource without CRI reporting, and CodebookType is set to 'typeI-SinglePanel' or reportQuantity is set to 'cri-RI-CQI', then if the CSI is triggered without a PUSCH with a transport block or HARQ-ACK or both, then (Z(m),Z'(m)) is defined as (Z1,Z'1) in CSI calculation delay requirement 1.
[0217] ◆If the transmitted CSI corresponds to wideband frequency granularity, and the CSI corresponds to four or fewer CSI-RS ports within a single resource without CRI reporting, and the CodebookType is set to 'typeI-SinglePanel' or the reportQuantity is set to 'cri-RI-CQI', then (Z(m),Z'(m)) is defined as (Z1,Z'1) in CSI calculation delay requirement 2.
[0218] ◆When the transmitted CSI corresponds to wideband frequency granularity and reportQuantity is set to 'ssb-Index-SINR', 'cri-SINR', 'ssb-Index-SINR-Index', or 'cri-SINR-Index', (Z(m),Z'(m)) is defined as (Z1,Z'1) in CSI calculation delay requirement 2.
[0219] ◆reportQuantity is set to 'cri-RSRP', 'ssb-Index-RSRP', 'cri-RSRP-Index', or 'ssb-Index-RSRP-Index', X μ According to the capabilities reported by UE, beamReportTiming, KB l If it follows the capability beamSwitchTiming reported by UE, (Z(m),Z'(m)) is defined as (Z3,Z'3) in CSI calculation delay requirement 2.
[0220] ◆The codebookType is set to 'typeII-CJT-r18' or 'typeII-CJT-PortSelection-r18', and the corresponding NZP-CSI-RS-ResourceSet for channel measurement is 1 < N TRP If configured with ≤ 4 resources, (Z(m), Z'(m)) is defined as (Z2, Z'2) or (Z2+r, Z'2+r) according to the capabilities reported by the UE, using (Z2, Z'2) in CSI calculation delay requirement 2.
[0221] ◆If the CSI report is set with N4=1, and the codebookType is set to 'typeII-Doppler-r18' or 'typeII-Doppler-PortSelection-r18', and the corresponding NZP-CSI-RS-ResourceSet for channel measurement is aperiodic (AP) with K CSI-RS resources, then (Z(m),Z'(m)) is defined as (Z2+14(K-1)m,Z'2) using (Z2,Z'2) in CSI calculation delay requirement 2.
[0222] ◆If the CSI report is set with N4=1, and the codebookType is set to 'typeII-Doppler-r18' or 'typeII-Doppler-PortSelection-r18', and the corresponding NZP-CSI-RS-ResourceSet for channel measurement is periodic or semi-persistent (P or SP) with a single CSI-RS resource, then (Z(m),Z'(m)) is defined as (Z2+w,Z'2) using (Z2,Z'2) in CSI calculation delay requirement 2.
[0223] ◆If the CSI report is set with N4>1 and the codebookType is set to 'typeII-Doppler-r18' or 'typeII-Doppler-PortSelection-r18' and the corresponding NZP-CSI-RS-ResourceSet for channel measurement is aperiodic (AP) with K CSI-RS resources, then (Z(m),Z'(m)) is defined as (Z2+14(K-1)m,Z'2) or (Z2+14(K-1)m+r,Z'2+r) according to the capability reported by the UE, using (Z2,Z'2) in CSI calculation delay requirement 2.
[0224] ◆If the CSI report is set with N4>1 and the codebookType is set to 'typeII-Doppler-r18' or 'typeII-Doppler-PortSelection-r18' and the corresponding NZP-CSI-RS-ResourceSet for channel measurement is periodic or semi-persistent (P or SP) with a single CSI-RS resource, then (Z(m),Z'(m)) is defined as (Z2+w,Z'2) according to the capability reported by the UE, using (Z2,Z'2) in CSI calculation delay requirement 2. It is defined as (Z2+14(K-1)m,Z'2) or (Z2+14(K-1)m+r,Z'2+r) according to the capability reported by the UE.
[0225] ◆In other cases, (Z(m), Z'(m)) are given by the specification table.
[0226] ◆μ for CSI calculation delay requirements 1 and 2 is min(μ PDCCH ,μ CSI-RS ,μ UL ) corresponds to μ PDCCH This corresponds to the subcarrier interval of the PDCCH from which DCI was transmitted. μ UL This corresponds to the subcarrier interval of PUSCH to which the CSI report will be transmitted. CSI-RS This corresponds to the minimum subcarrier interval of AP CSI-RS triggered by DCI.
[0227] X μ The beamReportTiming field, which follows the capability beamReportTiming reported by the UE, indicates the number of OFDM symbols between the end of the last symbol in SSB / CSI-RS and the start of the first symbol in the transmit channel containing the beam report. The UE provides capability for the band number for which the report is provided (where the measurement is performed). The UE includes this field for each supported subcarrier interval.
[0228] KB l This follows the capability beamSwitchTiming reported by the UE. beamSwitchTiming indicates the minimum number of OFDM symbols between the DCI triggering of AP CSI-RS and the AP CSI-RS transmission. The number of OFDM symbols is measured from the end of the last symbol containing the instruction to the start of the first symbol of CSI-RS. The UE includes this field for each supported subcarrier interval.
[0229] In this disclosure, the number of symbols from the end of the last symbol of the PDCCH that triggers the CSI report to the symbol that can initiate UL transmission of the CSI report, the UE CSI calculation time, the CSI calculation time, the CSI processing time, and the [CSI processing] timeline, Z ref , Z' ref(n), Z, Z', Z(m), Z'(m), Z1, Z'1, Z2, Z'2, Z3, Z'3, (Z,Z'), (Z(m),Z'(m)), (Z1,Z'1), (Z2,Z'2), and (Z3,Z'3) may be interchangeable with each other.
[0230] (Analysis) In conventional AP CSI reporting, the UE starts measuring / calculating the CSI after DCI triggering. The CPU occupancy period includes the time for CMR measurement, CSI calculation, and preparation for reporting.
[0231] As shown in the example in Figure 7A, if reportQuantity in the CSI reporting settings is not 'none', the CPU occupancy period for that CSI report is from the end of the PDCCH (DCI) that triggers the CSI report to the end of the PUSCH that carries the CSI report. Its length is Z ref The time must be greater than or equal to [Symbol] + PUSCH time. For P / SP CMRs, the CSI calculation time from the end of the CMR for that CSI report to the start of the PUSCH for that CSI report (CSI calculation delay requirement from measurement to report) must be greater than or equal to Z'[Symbol]. For AP CMRs, the CSI calculation time from the end of the CMR for that CSI report to the start of the PUSCH for that CSI report (CSI calculation delay requirement from measurement to report) must be Z' ref [Symbol] That's all.
[0232] As shown in the example in Figure 7B, if reportQuantity is 'none' in the CSI reporting settings, the CPU occupancy period for that CSI report is from the end of the PDCCH that triggers the CSI report to the later of the following symbols: the Z3 symbol after the end of the PDCCH (the CSI calculation delay requirement from triggering to reporting) and the Z'3 symbol after the end of the latest CMR (the CSI calculation delay requirement from measurement to reporting).
[0233] The major differences between UEIBR and existing AP CSI reporting include: ◆ In UEIBR, CSI measurements can occur before the reporting triggering signaling. ◆ In existing AP CSI reporting, CSI measurements occur only after the reporting triggering signaling.
[0234] Other differences include: ◆ In UEIBR, a measurement window for UEIBR is defined. ◆ In UEIBR, even if an event is triggered, the UE may wait for a long time to transmit on the first PUCCH resource, depending on the first PUCCH setting. ◆ In UEIBR, measurements are based solely on P-CMR.
[0235] It is unclear whether the CPU occupancy period includes the CSI measurement prior to the reporting triggering signaling for the UEIBR.
[0236] Therefore, the inventors devised a method for occupying the CPU for UEIBR.
[0237] The embodiments of this disclosure will be described in detail below with reference to the drawings. Each wireless communication method according to the embodiments may be applied individually or in combination.
[0238] (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.
[0239] 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".
[0240] 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.
[0241] 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.
[0242] In this disclosure, the upper layer signaling may be any or a combination thereof, such as Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information, and other messages (e.g., messages from the core network, such as positioning protocol messages (e.g., NR Positioning Protocol A (NRPPPa) / LTE Positioning Protocol (LPP)) messages).
[0243] 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).
[0244] In this disclosure, physical layer signaling may include, for example, Downlink Control Information (DCI) and Uplink Control Information (UCI).
[0245] In this disclosure, ceil(x), the ceiling function, and the ceiling function may be interpreted as interchangeable. In this disclosure, floor(x), the floor function, and the floor function may be interpreted as interchangeable. In this disclosure, ceil(x) and floor(x) may be interpreted as interchangeable. In this disclosure, sqrt(x), the square root of x, and the root x may be interpreted as interchangeable. In this disclosure, x mod y, mod(x, y), the mod function, and the modulo operation may be interpreted as interchangeable. In this disclosure, Σ i=M M+N-1 f(i), Σ i=M M+N-1 f i f(i) or f over i = M, M+1, ..., M+N-1 i The sum of f(M) + f(M+1) + ... + f(M+N-1), f M +f M+1 +...+f M+N-1, can be read interchangeably. C(n,k) is the number of combinations of choosing k values from n values (combinatorial coefficient), binomial coefficients, n C k , C n k , may be interpreted as mutually exclusive. In this disclosure, x / / y and floor(x / y) may be interpreted as mutually exclusive.
[0246] In this disclosure, A b The notations A_b, Ab, and A with a b placed to the lower right may be interpreted as interchangeable. In this disclosure, A c The notation A^c, with a c superscripted above A, may be interpreted as interchangeable. In this disclosure, A b c The notation A_b^c, where b is placed to the lower right of A and c is placed to the upper right of A, may be interpreted as being interchangeable. In this disclosure, x ~ x may be represented by placing a ~ above x, or it may be called x tilde. In this disclosure, x - x may be represented by placing a hyphen above it, or it may be called an x-bar. In this disclosure, x ^ This can also be represented by placing a caret (^) above x, or it may be called an x-hat.
[0247] In this disclosure, FR may be at least one of FR1, FR2, FR2-1, FR2-2, FR3, subterahertz, and terahertz. In this disclosure, the frequency range corresponding to FR1 may be 410–7125 MHz. In this disclosure, FR2 may include FR2-1 and FR2-2, the frequency range corresponding to FR2-1 may be 24250–52600 MHz, and the frequency range corresponding to FR2-1 may be 52600–71000 MHz.
[0248] In this disclosure, the terms event-based beam reporting, event-triggered beam reporting, event-driven beam reporting, UE-triggered beam reporting, UE-initiated beam reporting (UEIBR), UE-initiated beam management (UEIBM), beam reporting, CSI reporting, UEIBR, CSI relating to UEIBR, UEIBR-CSI, UEIBR-UCI, reporting, MAC CE, beam reporting MAC CE, UCI, CSI, and PUSCH may be interpreted as interchangeable. In this disclosure, CSI relating to UEIBR / UCI may be referred to as UEIBR-CSI / UCI.
[0249] In this disclosure, UEIBR, [terminal-initiated] beam reporting / CSI reporting, and event-based beam reporting may be interpreted as mutually exclusive.
[0250] In this disclosure, the first UL channel, the first PUCCH [transmit / resource / occasion], and the PUCCH that triggers the UEIBR may be interpreted as mutually exclusive. In this disclosure, the second UL channel, the second PUSCH, and the PUSCH that carries the UEIBR may be interpreted as mutually exclusive.
[0251] In this disclosure, the terms event[occurrence], event[occurrence / trigger] condition may be interpreted as mutually exclusive. In this disclosure, the terms event occurring, the conditions for an event being met, the UEIBR being triggered, the first PUCCH being transmitted, and the transmission occurring in the first PUCCH resource may be interpreted as mutually exclusive.
[0252] In this disclosure, the [Time] window and the measurement window may be interpreted as interchangeable.
[0253] In this disclosure, the reporting triggering signaling, the first PUCCH, and the DCI / PDCCH scheduling the second PUCCH may be interpreted as mutually exclusive.
[0254] (Wireless communication method) The UE may receive a setting / instruction for a UEIB (Beam Report). The UE / BS may determine the CPU occupancy period for the UEIB based on at least one of the following: a first PUCCH that triggers the UEIB, a second PUSCH that carries the UEIB, one CMR from one or more CMRs for measuring the UEIB, and signaling for the UEIB.
[0255] <Embodiment 1> Embodiment 1 relates to the CPU occupancy time period for UEIBR.
[0256] The CPU occupancy period for UEIBR may consider only the time after the reported triggering signaling. The CPU occupancy period for UEIBR may not include the time before the reported triggering signaling.
[0257] The start timing of the CPU occupancy period may be the first or last symbol of the first PUCCH transmission that triggers the UEIBR.
[0258] The end of that CPU usage period may be the last symbol of the second PUCCH corresponding to the first PUCCH.
[0259] The start and end timings may apply only to Mode B. The CPU occupancy period for Mode A may follow the CPU occupancy period of the [existing] AP CSI report triggered by DCI.
[0260] As shown in the example in Figure 8A, if the event conditions are met, the CPU occupancy period may be from the start of the first PUCCH transmission to the end of the second PUCCH. As shown in the example in Figure 8B, if the event conditions are met in mode A, the CPU occupancy period may be from the start of the first PUCCH transmission that schedules the second PUCCH to the end of the second PUCCH. As shown in the example in Figure 9, if the event conditions are not met, the CPU occupancy period may not be started.
[0261] According to Embodiment 1, the UE / BS can determine an appropriate CPU occupancy period after the triggering of the UEIBR in the UEIBR.
[0262] <Embodiment 2> Embodiment 2 relates to the CPU occupancy time period for UEIBR.
[0263] The CPU occupancy period for a UEIBR may take into account the time before the reported triggering signaling. One CPU occupancy period may be defined for each UEIBR.
[0264] The start timing of that CPU occupancy period may be the first or last symbol of the earliest CMR for measuring / evaluating the UEIBR.
[0265] The start time of the CPU occupancy period may be determined by explicit signaling / instructions from the network to the user interface (UE). For example, the signaling may be the RRC setting of the UEIBR, an activation command for the UEIBR, etc.
[0266] The start timing of the CPU occupancy period may be the first symbol (first symbol) of the earliest CMR for measurement / evaluation of the UEIBR after receiving at least one of the UEIBR RRC settings or UEIBR activation commands, or it may be the first symbol (second symbol) of the earliest CMR for measurement / evaluation of the UEIBR after the previous UEIBR transmission. The first UEIBR CPU occupancy period after the UEIBR RRC settings are applied / received may start at the first symbol (first symbol) of the earliest CMR for measurement / evaluation of the UEIBR after receiving at least one of the UEIBR RRC settings or UEIBR activation commands. Subsequent UEIBR CPU occupancy periods may start at the first symbol (second symbol) of the earliest CMR for measurement / evaluation of the UEIBR after the previous UEIBR transmission.
[0267] The end of the CPU occupancy period may be the last symbol of the second PUCCH corresponding to the first PUCCH. This end timing may mean that, if a UEIBR has not been triggered, the CPU occupancy period continues until a UEIBR is triggered.
[0268] The timing of the end of the CPU usage period may be based on at least one of the following multiple variations x.
[0269] ◆Variation 1: If no transmission occurs in the first PUCCH resource (UEIBR is not triggered, the event conditions are not met), the termination timing may be one of the following options x: —◆Option 1: The first or last symbol of the first PUCCH resource. —◆Option 2: After the Z'3 symbol of the last symbol of the last CMR prior to the first PUCCH resource. —◆Option 3: After the Z'3 symbol of the last symbol of the last CMR in the measurement window.
[0270] ◆Variation 2: When a transmission occurs in the first PUCCH resource (when the UEIBR is triggered, when the event conditions are met), the termination timing may be one of the following options x: —◆Option 1: The last symbol of the second PUCCH transmission corresponding to [that first PUCCH resource]. —◆Option 2: In Mode A, the first or last symbol of that first PUCCH resource. In the subsequent UEIBR DCI triggering procedure, a different CPU occupancy period from the existing specification may be reused.
[0271] As shown in the example in Figure 10, the CPU occupancy period may begin at the earliest start of the CMR for measuring / evaluating the UEIBR. If the event conditions are met, the CPU occupancy period may end at the end of the second PUSCH corresponding to that event.
[0272] According to Embodiment 2, the UE / BS can determine an appropriate CPU occupancy period in the UEIBR, including the time before the triggering of the UEIBR.
[0273] <Variation of Embodiment 2> The CPU occupancy period for the UEIBR may take into account the time before the reporting triggering signaling. One CPU occupancy period may be defined for one UEIBR.
[0274] In a set of multiple CMRs for measuring / evaluating the UEIB, and a set of periodic first PUCCH resources (transmission occasions), the start timing of the CPU occupancy period may be the first or last symbol of the Xth CMR preceding each first PUCCH resource (transmission occasion), or the first or last symbol of the Xth CMR succeeding each first PUCCH resource (transmission occasion). X may be defined in the specification, set, or reported as UE capability.
[0275] The timing of the end of the CPU occupancy period may be the same as in Embodiment 2.
[0276] As shown in the example in Figure 11, the first PUCCH resource may be set / placed periodically. The CPU occupancy period may begin at the start of the Xth CMR preceding the first PUCCH resource ([Send] occasion). If the conditions for the event [based on the measurement of the CMR corresponding to that first PUCCH resource] are met, the CPU occupancy period may end at the end of the second PUCCH corresponding to that event. If the conditions for the event [based on the measurement of the CMR corresponding to that first PUCCH resource] are not met, the CPU occupancy period may end at the end of that first PUCCH resource.
[0277] According to the variation of Embodiment 2, the UE / BS can determine an appropriate CPU occupancy period in the UEIBR, including the time before the triggering of the UEIBR.
[0278] <Embodiment 3> Embodiment 3 relates to the CPU occupancy time period for UEIBR.
[0279] The CPU occupancy period for a UEIBR may take into account the time before the reported triggering signaling. Two CPU occupancy periods (a first CPU occupancy period and a second CPU occupancy period) may be defined for a single UEIBR.
[0280] The start timing of the first CPU occupancy period may be the first or last symbol of the earliest CMR for measuring / evaluating the UEIBR.
[0281] The end timing of the first CPU occupancy period and the second CPU occupancy period may be based on at least one of the following multiple definitions x.
[0282] ◆Definition 1: If the event conditions are met, the end timing of the first CPU occupancy period may be 3 Z' symbols after the last symbol of the last CMR before the conditions were met. [Assuming there are no CSI measurements while the UE is waiting for the first PUCCH resource,] the second CPU occupancy period may be based on at least one of the following timings: —◆The start timing of the second CPU occupancy period may be the first or last symbol of the first PUCCH transmission that triggers the UEIBR. This start timing may apply only to mode B. For mode A, the start timing of the second CPU occupancy period may follow the start timing of the CPU occupancy period for an existing AP CSI report triggered by DCI. —◆The end timing of the second CPU occupancy period may be the last symbol of the second PUCCH corresponding to that event / first PUCCH resource.
[0283] ◆Definition 2: If the event conditions are not met, the end time of the first CPU occupancy period may be the last symbol of the second PUCCH corresponding to [that event / first PUCCH resource]. This end time may mean that the first CPU occupancy period continues until the event conditions are met and UEIBR is triggered.
[0284] As shown in the example in Figure 12, the first CPU occupancy period may begin at the earliest start of the CMR for measuring / evaluating the UEIBR. If the event conditions are met, the first CPU occupancy period may end after 3 Z' symbols from the last symbol of the last CMR before the conditions were met. Subsequently, the second CPU occupancy period may begin at the first symbol of the first PUCCH transmission that triggers the UEIBR. The second CPU occupancy period may end at the last symbol of the second PUCCH corresponding to that event / first PUCCH resource. The UE does not have to occupy the CPU for the UEIBR between the first and second CPU occupancy periods. The UE may retain information about the measurement results / event from the first to the second CPU occupancy period.
[0285] The CPU occupancy period, including the [first CPU occupancy period and the second CPU occupancy period], may be defined by using the same start and end timings as in Embodiment 2, excluding the time period between the last symbol of the last CMR before the condition is met, after the Z'3 symbol, and the first symbol of the first PUCCH that triggers the UEIBR.
[0286] According to Embodiment 3, the UE / BS can determine an appropriate CPU occupancy period in the UEIBR, including the time before the triggering of the UEIBR.
[0287] <Variations to Embodiment 2 / Embodiment 3> In Embodiment 2 / Embodiment 3, [particularly with respect to Mode B] the start timing of the CPU occupancy period may be the first or last symbol of the first PUCCH resource, or the first or last symbol of the second PUCCH resource.
[0288] In Embodiment 2 / Embodiment 3, the start / end timing of the CPU occupancy time period may be based on at least one of the following multiple variations x: ◆ Variation 1: The start / end timing is the timing of receiving MAC CE / DCI for activation / instruction of the TCI state [following the counter reset condition] (first or last symbol). ◆ Variation 2: The start / end timing is the timing of receiving RRC settings for updating the CMR / CSI reporting settings for UEIBR (first or last symbol).
[0289] <Embodiment 4> It is unclear what happens to the CPU occupancy period after the UEIBR is transmitted, and whether the CPU is released.
[0290] Embodiment 4 may assume one of the following options for the UEIBR: ◆ Option 1: When the UEIBR is set to RRC, the UE performs event evaluation until the RRC is reset. After transmitting the UEIBR for one triggering, the UE may continue event evaluation until the RRC is reset to not use the UEIBR. ◆ Option 2: When the UEIBR is set to RRC, the UE performs event evaluation until the UEIBR is transmitted successfully. The UE may stop event evaluation after transmitting the UEIBR once.
[0291] In option 1, after the UEIBR has been sent and the CPU has been released, the CPU occupancy period may be resumed at the first symbol of the first CMR for measurement and evaluation for the continuing UEIBR.
[0292] In option 2, after the RRC reset for UEIBR, the CPU occupancy time period may start at any of the start timings from Embodiment 1 to Embodiment 3.
[0293] According to Embodiment 4, UE / BS can appropriately determine the CPU occupancy period after the transmission of UEIBR.
[0294] <Variations of Embodiments 1 to 4> Which embodiment / option / choice / variation from the above multiple embodiments is applied may depend on at least one of the following multiple states x: ◆State 1: Whether a time window and counter [for the UEIBR] are set, or whether the threshold for that counter is 0, 1, or something else. ◆State 2: Whether a prohibit timer is running for the first PUCCH resource associated with the CMR. For example, if the prohibit timer is running, the CPU occupancy time period does not need to be managed. ◆State 3: Whether the time gap between the first PUCCH resource and the second PUCCH resource [especially for mode B] is greater than or equal to Z' [symbol]. For example, if the time gap is greater than or equal to Z' [symbol], Embodiment 1 may be applied. Otherwise, Embodiments 2 / 3 may be applied.
[0295] <Note> The above multiple embodiments / options / choices / variations may be combined to form a single embodiment / option / choice / variation.
[0296] In the embodiments described above, the measured RS may be a QCL source RS in an active TCI state / indicated / unified TCI state.
[0297] <<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.
[0298] 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.
[0299] 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.
[0300] 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.
[0301] 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 a cell, band, band combination, bandwidth part (BWP), component carrier, etc.), or frequency-specific (per frequency, e.g., per cell).
[0302] In the embodiments described above, the UE may receive at least one piece of information (QCL information) from the NW from among several of the following QCL rules / QCL types: ◆ QCL type A (Doppler shift, Doppler spread, mean delay, and delay spread) ◆ QCL type B (Doppler shift and Doppler spread) ◆ QCL type C (Doppler shift and mean delay) ◆ QCL type D (spatial reception parameters)
[0303] In the embodiments described above, the QCL source RS for each QCL type may be at least one of the following RSs: ◆SSB ◆CSI-RS with / without repetition ◆TRS ◆DMRS for PDCCH / PDSCH
[0304] In the embodiments described above, information from the network may be set / instructed by the following methods: ◆ Common to multiple UEs, or individual to a UE ◆ Cell-specific, or common to multiple cells ◆ Per UE / Per CC / Per BWP / Per band / Per cell / Per cell group (CG)
[0305] <<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.
[0306] 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.
[0307] If the above notice is made by the UCI, the notice may be transmitted using PUCCH or PUSCH.
[0308] 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.
[0309] <<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.
[0310] The above-mentioned specific capabilities may indicate at least one of the following: ◆ Supporting the above-mentioned specific processing / operation / control / assumment / information; ◆ Supporting CPU occupancy time / CSI calculation delay requirements for UEIBR; ◆ The number of settings / resources [sets] to support.
[0311] In this disclosure, "to support" and "whether or not to support" may be interpreted interchangeably.
[0312] 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).
[0313] 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)).
[0314] If the above conditions are not met, UE / BS may follow the behavior specified in existing 3GPP releases.
[0315] (Note) The following inventions are added with respect to one embodiment of the present disclosure. <Note 1> A terminal having: a receiving unit that receives a beam report setting initiated by the terminal; a physical uplink control channel (PUCCH) that triggers the beam report; a physical uplink sharing channel (PUSCH) that carries the beam report; a channel measurement resource from one or more channel measurement resources for measuring the beam report; and signaling for the beam report, which determines the time period for which a channel state information (CSI) processing unit is occupied for the beam report. <Note 2> The terminal according to Note 1, wherein the time period does not include the time before the triggering of the beam report. <Note 3> The terminal according to Note 1 or Note 2, wherein the time period includes the time before the triggering of the beam report. <Note 4> The terminal according to any one of Notes 1 to 3, wherein the control unit evaluates the event for the beam report until it is set not to use the beam report or until the beam report is transmitted. <Note A> A base station having: a transmitting unit that transmits a beam report setting initiated by a terminal; a physical uplink control channel (PUCCH) that triggers the beam report; a physical uplink sharing channel (PUSCH) that carries the beam report; a control unit that determines the duration of the occupancy of a channel state information (CSI) processing unit for the beam report based on at least one of the following: one channel measurement resource from one or more channel measurement resources for measuring the beam report; and signaling for the beam report.
[0316] <Supplement> The terminal in Appendix 1 to Appendix 4 may be terminal 20. The receiving / transmitting unit in Appendix 1 to Appendix 4 may be transmitting / receiving unit 220. The control unit in Appendix 1 to Appendix 4 may be control unit 210. The base station in Appendix A may be base station 10. The receiving / transmitting unit in Appendix A may be transmitting / receiving unit 120. The control unit in Appendix A may be control unit 110.
[0317] (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.
[0318] Figure 13 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).
[0319] 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.
[0320] In EN-DC, the LTE (E-UTRA) base station (eNB) is the Master Node (MN), and the NR base station (gNB) is the Secondary Node (SN). In NE-DC, the NR base station (gNB) is the MN, and the LTE (E-UTRA) base station (eNB) is the SN.
[0321] The wireless communication system 1 may support dual connectivity between multiple base stations within the same RAT (for example, dual connectivity where both MN and SN are NR base stations (gNB) (NR-NR Dual Connectivity (NN-DC))).
[0322] 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.
[0323] The wireless communication system 1 may utilize Multi Input Multi Output (MIMO). For example, one cell may be formed by one antenna / base station 10, or 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.
[0324] 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).
[0325] 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.
[0326] Furthermore, terminal 20 may communicate in each CC using at least one of time division duplex (TDD) and frequency division duplex (FDD).
[0327] 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.
[0328] 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.
[0329] 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.
[0330] Terminal 20 may be a terminal that supports at least one of the following communication methods: LTE, LTE-A, 5G, etc.
[0331] 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).
[0332] 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.
[0333] 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.
[0334] 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.
[0335] 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.
[0336] 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.
[0337] 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.
[0338] 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.
[0339] 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.
[0340] 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.
[0341] 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.
[0342] In the wireless communication system 1, a synchronization signal (SS), a downlink reference signal (DL-RS), etc., may be transmitted. In the wireless communication system 1, 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.
[0343] The synchronization signal may be, for example, at least one of a Primary Synchronization Signal (PSS) and a Secondary Synchronization Signal (SSS). A signal block including 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.
[0344] 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).
[0345] (Base Station) Figure 14 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.
[0346] 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.
[0347] 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.
[0348] 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.
[0349] 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.
[0350] 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.
[0351] 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.
[0352] 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.
[0353] 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.
[0354] 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.
[0355] 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.
[0356] 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.
[0357] On the other hand, the transmitting / receiving unit 120 (RF unit 122) may perform amplification, filtering, demodulation to a baseband signal, etc., on the radio frequency band signal received by the transmitting / receiving antenna 130.
[0358] 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.
[0359] 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.
[0360] The transmission path interface 140 may transmit and receive signals (backhaul signaling) to and from devices included in the core network 30 (e.g., network nodes that provide NF), other base stations 10, and the like, and may acquire, transmit, and the like user data (user plane data), control plane data, and the like for the terminal 20.
[0361] Note that the transmitting unit and the receiving unit of the base station 10 in the present disclosure may be configured by at least one of the transmitting / receiving unit 120, the transmitting / receiving antenna 130, and the transmission path interface 140.
[0362] Note that 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-analog conversion, analog beamforming, etc.) and lower-layer functions of the physical layer (precoding, IFFT, FFT, etc.). The DU may implement upper-layer functions of the physical layer (from coding to resource element mapping, etc.), functions of the MAC layer, and functions of the RLC layer. The CU may implement functions of the PDCP layer, the Service Data Adaptation Protocol (SDAP) layer, and the RRC layer.
[0363] In the present disclosure, the base station 10 may include a single device that implements all the functions of the RU, DU, and CU, or may include a plurality of devices that each implement some of the functions of the RU, DU, and CU and are connected to each other. In the present disclosure, the base station 10 may be interchangeably read as RU / DU / CU.
[0364] Further, in the present disclosure, a network device having any of the NF functions described above (e.g., an LMF node) may be a device comprising the components included in the base station 10 (e.g., the control unit 110 and the transmitting / receiving unit 120). That is, by replacing the base station with a network device, the configuration of the network device according to an embodiment of the present disclosure may be covered.
[0365] (Terminal) FIG. 15 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 transceiving unit 220, and a transceiving antenna 230. Note that one or more of each of the control unit 210, the transceiving unit 220, and the transceiving antenna 230 may be provided.
[0366] Note that 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. A part of the processing of each unit described below may be omitted.
[0367] The control unit 210 performs overall control of the terminal 20. The control unit 210 can be configured with a controller, a control circuit, and the like that are described based on common general knowledge in the technical field related to the present disclosure.
[0368] 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 transceiving 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 transceiving unit 220.
[0369] The transceiving 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 transceiving unit 220 can be configured with a transmitter / receiver, an RF circuit, a baseband circuit, a filter, a phase shifter, a measurement circuit, a transceiving circuit, and the like that are described based on common general knowledge in the technical field related to the present disclosure.
[0370] The transceiving unit 220 may be configured as an integrated transceiving unit, or may be configured of a transmission unit and a reception unit. The transmission unit may be configured of the transmission processing unit 2211 and the RF unit 222. The reception unit may be configured of the reception processing unit 2212, the RF unit 222, and the measurement unit 223.
[0371] The transceiving antenna 230 can be configured with an antenna, for example, an array antenna and the like, which are described based on common general knowledge in the technical field related to the present disclosure.
[0372] The transmitting / receiving unit 220 may receive the downlink channel, synchronization signal, downlink reference signal, etc. The transmitting / receiving unit 220 may also transmit the uplink channel, uplink reference signal, etc.
[0373] The transmitting / receiving unit 220 may use digital beamforming (e.g., precoding), analog beamforming (e.g., phase rotation), or the like to form at least one of the transmitting beam and the receiving beam.
[0374] The transmitting / receiving unit 220 (transmission processing unit 2211) may perform PDCP layer processing, RLC layer processing (e.g., RLC retransmission control), MAC layer processing (e.g., HARQ retransmission control), etc., on data and control information acquired from the control unit 210 to generate a bit sequence to be transmitted.
[0375] The transmitting / receiving unit 220 (transmission processing unit 2211) may perform transmission processing on the bit sequence to be transmitted, such as channel coding (which may include error correction coding), modulation, mapping, filtering, DFT processing (if necessary), IFFT processing, precoding, and digital-to-analog conversion, and output a baseband signal.
[0376] Whether or not to apply DFT processing may be based on the transform precoding settings. The transmitting / receiving unit 220 (transmission processing unit 2211) may perform DFT processing as part of the transmission process to transmit a channel (for example, PUSCH) using a DFT-s-OFDM waveform if transform precoding is enabled for that channel, or it may not perform DFT processing as part of the transmission process if transform precoding is not enabled for that channel.
[0377] The transmitting / receiving unit 220 (RF unit 222) may perform modulation, filtering, amplification, etc., of the baseband signal to the radio frequency band and transmit the signal in the radio frequency band via the transmitting / receiving antenna 230.
[0378] On the other hand, the transmitting / receiving unit 220 (RF unit 222) may perform amplification, filtering, demodulation to a baseband signal, etc., on the radio frequency band signal received by the transmitting / receiving antenna 230.
[0379] The 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.
[0380] 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.
[0381] 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.
[0382] 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.
[0383] (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.
[0384] 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 16 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.
[0385] 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.
[0386] 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.
[0387] 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.
[0388] 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.
[0389] 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.
[0390] 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).
[0391] 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.
[0392] 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.
[0393] 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.
[0394] The communication apparatus 1004 is hardware (transceiving device) for performing communication between computers via a wired network, a wireless network, or both of a wired network and a wireless network, and is also referred to as, for example, a network device, a network controller, a network card, a communication module, or the like. The communication apparatus 1004 may be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc., or a combination of at least two of these. For example, the aforementioned transceiving unit 120 (220), transceiving antenna 130 (230), and the like may be implemented by the communication apparatus 1004. The transceiving unit 120 (220) may be implemented to be physically or logically separated into a transmitting unit 120a (220a) and a receiving unit 120b (220b).
[0395] The input apparatus 1005 is an input device that accepts input from the outside (for example, a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc., or a combination of at least two of these). The output apparatus 1006 is an output device that performs output to the outside (for example, a display, a speaker, a Light Emitting Diode (LED) lamp, etc., or a combination of at least two of these). Note that the input apparatus 1005 and the output apparatus 1006 may have an integrated configuration (for example, a touch panel).
[0396] Further, the respective apparatuses such as the processor 1001 and the memory 1002 are connected by a bus 1007 for communicating information. The bus 1007 may be configured using a single bus, or may be configured using different buses for each pair of apparatuses.
[0397] 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.
[0398] 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.
[0399] 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.
[0400] 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.
[0401] (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.
[0402] In this disclosure, the terms "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", "Ground Base Station", "Stratospheric Base Station", "Unmanned Aerial Vehicle", "High Altitude Platform Station (HAPS)", "Airborne Platform", "Panel", "Cell", and "Radio Access Network (Radio Access)" are used. Any two terms selected from the set of terms such as "Network (RAN)" and "Network" may be used interchangeably. Each cell accommodated by a base station may be referred to by terms such as macrocell, small cell, femtocell, picocell, serving cell, or supercell. In this 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.
[0403] In this 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.
[0404] 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.
[0405] 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").
[0406] 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.
[0407] 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).
[0408] 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.
[0409] 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).
[0410] 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."
[0411] 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.
[0412] 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.
[0413] 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.
[0414] 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.
[0415] 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
[0416] 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.
[0417] 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.
[0418] 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.
[0419] 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.
[0420] 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.
[0421] 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.
[0422] 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.
[0423] 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.
[0424] 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.
[0425] 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.
[0426] 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.
[0427] 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.
[0428] 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..."
[0429] 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).
[0430] 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").
[0431] In this disclosure, "of," "for," "regarding," "related to," and "associated with" may be interpreted as being interchangeable.
[0432] 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.
[0433] 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.
[0434] 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.
[0435] 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.
[0436] 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.
[0437] 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.
[0438] 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.
[0439] 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.
[0440] 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.
[0441] 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.
[0442] 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.
[0443] 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.
[0444] 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).
[0445] 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.
[0446] 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).
[0447] 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.
[0448] 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."
[0449] 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.
[0450] This application is based on Japanese Patent Application No. 2025-078703, filed on May 9, 2025. All of its contents are included here.
Claims
1. A terminal having: a receiving unit that receives the setting of a beam report initiated by the terminal; a physical uplink control channel (PUCCH) that triggers the beam report; a physical uplink sharing channel (PUSCH) that carries the beam report; a control unit that determines the duration of the occupancy of a channel state information (CSI) processing unit for the beam report based on at least one of the following: one channel measurement resource from one or more channel measurement resources for measuring the beam report; and signaling for the beam report.
2. The terminal according to claim 1, wherein the time period does not include the time prior to the triggering of the beam report.
3. The terminal according to claim 1, wherein the time period includes the time prior to the triggering of the beam report.
4. The terminal according to claim 1, wherein the control unit evaluates events for the beam report until it is set not to use the beam report or until it transmits the beam report.
5. A wireless communication method for a terminal, comprising: receiving a beam report setting initiated by the terminal; and determining a time period of occupancy of a channel state information (CSI) processing unit for the beam report based on at least one of a physical uplink control channel (PUCCH) that triggers the beam report, a physical uplink sharing channel (PUSCH) that carries the beam report, one channel measurement resource from one or more channel measurement resources for measuring the beam report, and signaling for the beam report.
6. A base station having: a transmitting unit that transmits a beam report setting initiated by a terminal; a physical uplink control channel (PUCCH) that triggers the beam report; a physical uplink sharing channel (PUSCH) that carries the beam report; a control unit that determines the duration of occupancy of a channel state information (CSI) processing unit for the beam report based on at least one of one of one or more channel measurement resources for measuring the beam report and signaling for the beam report.
