CPU computation for event-based CSI reporting

Abstract

The invention relates to an apparatus (610) comprising: means for determining an event (203, 303) for reporting; means for triggering, due to the event (203, 303), an uplink signal (205, 305) indicating a transmission of a Channel State Information, CSI, report, wherein the CSI report is scheduled to be transmitted in a reporting time slot (206, 306); or an uplink signal (205, 305) indicating the event (203, 303); or an uplink signal (205, 305) requesting a reporting resource; and means for determining an end time for a CSI Processing Unit, CPU, occupation (204, 304) such that, in case the uplink signal (205, 305) does not indicate the event, the CPU occupation (204, 304) lasts based on an uplink signaling occasion.

Description

Technical Field

[0001] This invention relates to R19 MIMO / mobility enhancements regarding event-triggered reporting. Background Technology

[0002] The RAN1 (Radio Access Networks (Working Group 1) specification defines an enhancement to facilitate UE (User Equipment)-initiated or event-driven beam management to reduce overhead and / or latency. It assumes a uniform TCI (Transmission Configuration Indication) while utilizing the traditional CSI (Channel State Information) measurement and reporting configuration framework as much as possible. The goal is intra-cell and inter-cell beam management at FR2 (Frequency Range 2) and sTRP (Single TRP, Transmit / Receive Point). This includes multiple UL (Uplink) signaling contents and procedures required for UE-initiated or event-driven beam reporting to facilitate fast beam switching. Furthermore, this includes UL signaling media or containers that take into account the UE-initiated or event-driven nature of UL transmissions and are primarily designed for beam reporting purposes. Additionally, one of the goals of the 3GPP NR Release 19 Mobility Enhancement is to specify the necessary components to support event-triggered Layer 1 (L1) measurement reports (such as CSI reports, but not limited to) for L1 / L2 triggered mobility (LTM). L1 / L2 triggered mobility (LTM) can also be referred to as L1 / L2 center mobility, lower layer triggered mobility, or L2 mobility.

[0003] Currently, 3GPP standard 38.214 defines periodic / semi-persistent / aperiodic measurements and reporting of L1 (Layer 1) measurements.

[0004] The L1 report has been defined in 3GPP standard 38.214 as follows. First, consider the report settings.

[0005] Each report setting CSI-ReportConfig With (by higher-level parameters) BWP-Id (Indication) A single downlink BWP (bandwidth portion) is associated with which it is used for channel measurements. CSI-ResourceConfig The text is incomplete and contains errors. A more accurate translation would require the full context. CSI- ReportConfigIt includes parameters for a CSI reporting band: codebook configuration (including codebook subset restrictions), time-domain behavior, frequency granularity for CQI (Channel Quality Indicator) and PMI (Precoding Matrix Indicator), measurement restriction configuration, and CSI-related quantities to be reported by the UE, such as Layer Indicator (LI), L1-RSRP (Layer 1 Reference Signal Received Power), L1-SINR (Layer 1 Signal-to-Interference-plus-Noise Ratio), CRI (Channel State Information Reference Signal Resource Indicator), SSBRI (Synchronization Signal Block Resource Indicator), CapabilityIndex, and TDCP (Time-Domain Channel Attributes).

[0006] CSI-ReportConfig The temporal behavior is determined by higher-level parameters. reportConfigType Instructions, and reportConfigType It can be set to 'aperiodic' (non-periodic), 'semiPersistentOnPUCCH' (physical uplink control channel), 'semiPersistentOnPUSCH' (physical uplink shared channel), or 'periodic' (periodic). For 'periodic' and 'semiPersistentOnPUCCH' / 'semiPersistentOnPUSCH' CSI reports, the configured periodicity and slot offset apply to the parameter set on which the CSI report is configured to be transmitted by the UL BWP. Higher layer parameters reportQuantity Indicates the amount of CSI-related, L1-RSRP-related, L1-SINR-related, CapabilityIndex-related, or TDCP-related data to be reported. reportFreqConfiguration Indicates the reporting granularity in the frequency domain, including the CSI reporting band and whether the PMI / CQI report is broadband or subband. CSI-ReportConfig In timeRestrictionForChannelMeasurements The parameters can be configured to enable time-domain constraints for channel measurements, and timeRestrictionForInterferenceMeasu rements It can be configured to enable time-domain constraints for interference measurements.

[0007] Next, we will introduce the resource settings, specifically the resource settings for each CSI. CSI-ResourceConfig Configuration of a list containing S≥1 CSI resource sets (by higher-level parameters) csi-RS-ResourceSetList(Given), where the list consists of references to either or both of the NZP (Non-Zero Power) CSI-RS (Channel State Information Reference Signal) (multiple) resource sets and the SS / PBCH (Synchronization Signal / Physical Broadcast Channel) (multiple) block sets, or the list consists of references to the CSI-IM (Channel State Information for Interference Measurement) (multiple) resource sets. Each CSI resource setting is located within a higher-level parameter... BWP-id The DLBWP (Downlink Bandwidth Portion) is identified, and all CSI resource settings linked to the CSI report settings have the same DLBWP.

[0008] The CPU (CSI processing unit) calculation definition in 3GPP Technical Specification (TS) 38.214 is as follows, covering the CSI processing guidelines in Section 5.2.1.6 of TS 38.214.

[0009] UE using parameters simultaneousCSI-ReportsPerCC Indicates the number of parallel CSI computations supported on a single component carrier. And using parameters simultaneousCSI-ReportsAllCC directive The number of parallel CSI calculations supported across all component carriers. If the UE supports... If there are multiple parallel CSI computations, then it is said to have L CPUs are used to process CSI reports. If, in a given OFDM (Orthogonal Frequency Division Multiplexing) symbol, L CPUs are occupied for CSI report calculation, then the UE has One unused CPU. If N Several CSI reports indicate that they have begun occupying their respective CPUs on the same OFDM symbol, and that symbol has One CPU was not occupied, and each CSI reported Corresponding to Therefore, it is not required that the UE update has the lowest priority. The requested CSI report (in accordance with Clause 5.2.5), in which It makes The maximum value that is valid.

[0010] It is not expected that the UE will be configured to contain more than The report is set to a non-periodic CSI trigger state. The processing of CSI reports consumes multiple CPUs across multiple symbols, as shown below (in the following two paragraphs).

[0011] For those with higher-level parameters reportQuantity CSI-ReportConfig set to 'none' and having higher-level parameters trs-info CSI reports from the configured CSI-RS-ResourceSet .

[0012] For those with higher-level parameters reportQuantity Set to 'cri-RSRP', 'ssb-Index-RSRP', 'cri-SINR', 'ssb-Index-SINR', 'cri-RSRP-Index', 'ssb-Index-RSRP-Index', 'cri-SINR-Index', 'ssb-Index-SINR-Index' or 'none' CSI-ReportConfig (and has higher-level parameters) trs-info CSI reports for CSI-RS-ResourceSets that are not configured. .

[0013] For those with higher-level parameters reportQuantity The CSI report of the CSI-ReportConfig that is not set to 'none' indicates that (multiple) CPUs are occupied on multiple OFDM symbols, as shown below (in the following three paragraphs).

[0014] Periodic or semi-persistent CSI reports (excluding the initial semi-persistent CSI report on the PUSCH after the PDCCH (Physical Downlink Control Channel) that triggers the report) occupy the first symbol of the earliest of each CSI-RS / CSI-IM / SSB (Channel State Information Reference Signal / Channel State Information for Interference Measurement / Synchronization Signal Block) resource used for channel or interference measurements, until the last symbol of the configuration PUSCH / PUCCH carrying the report, with the corresponding latest CSI-RS / CSI-IM / SSB timing no later than the corresponding CSI reference resource.

[0015] A non-periodic CSI report occupies CPU(s) from the first symbol after the PDCCH that triggered the CSI report until the last symbol of the scheduled PUSCH carrying the report. When PDCCH reception includes two PDCCH candidates from two corresponding search space sets, as described in Clause 10.1 of 3GPP Technical Specification 38.213, the PDCCH candidate that ends later in time is used for the purpose of determining the duration of CPU occupation.

[0016] Following PDCCH triggering, the initial semi-persistent CSI report on the PUSCH occupies the CPU from the first symbol after the PDCCH until the last symbol of the scheduled PUSCH carrying the report. When PDCCH reception includes two PDCCH candidates from two corresponding search space sets, as described in Clause 10.1 of 3GPP Technical Specification 38.213, the PDCCH candidate that ends later in time is used for the purpose of determining the duration of CPU occupation.

[0017] The technical problems to be solved can be identified as follows.

[0018] Event-based CSI reporting is currently being discussed in Release 19 (Release 19) MIMO (Multiple-Input Multiple-Output). One aspect of CSI reporting is CPU computation. Each report and measurement configuration (active for the UE) is based on one or more metric consumption processing units (Ncpus) associated with that configuration.

[0019] Currently, CPU computation is defined for periodic / semi-persistent and non-periodic CSI reports.

[0020] As an example of the current periodic report, CPU usage is as follows: Figure 1 As depicted in Figure 10.

[0021] like Figure 1 As shown, there are synchronization signal blocks SSB1 101 (shown with solid arrows) and SSB2 102 (shown with dashed arrows), which are periodically positioned in the time domain as shown. There is a reference resource 103 marked as a white rectangle. The CSI processing unit (CPU) utilization 104 is set to begin immediately preceding the previous SSB1 101 before the reference resource 103. Then there is a report slot 105 marked as a black rectangle. Report slot 105 can be labeled n'. Then, the reference resource 103 can be labeled as: Reference resource = n' – nCSI_ref (1)

[0022] The end time of CPU usage 104 can be determined at the end of reporting time slot 105. Therefore, the length of CPU usage 104 along the time domain can be seen by the thick arrow at the top of the diagram.

[0023] The technical issue is that the CPU computation for event-triggered CSI reports is currently not apparent. Summary of the Invention

[0024] This invention proposes a novel method for determining the start and end times of CSI processing unit occupancy. Event-based CSI reporting is discussed in this context. UEs have certain limitations regarding CSI report transmission and the number of occupied CSI processing units. Therefore, this invention determines the CPU occupancy time interval in a more explicit manner under various conditions. In some embodiments, the end time of CPU occupancy is discussed, and in some other embodiments, the start time of CPU occupancy is discussed.

[0025] According to a first aspect of the present invention, an apparatus is provided, comprising: Components used to determine the events to be reported; Components for triggering the following due to this event: an uplink signal indicating the transmission of a Channel State Information (CSI) report, wherein the CSI report is scheduled to be sent in a reporting slot; or an uplink signal indicating the event; or an uplink signal requesting reporting resources; and A component for determining the end time of CPU occupancy for the CSI processing unit, such that the CPU occupancy continues until the reporting time slot if the uplink signal indicates the event.

[0026] In one embodiment, the device further includes: The component used to send the CSI report in the reporting time slot, wherein the CSI report is part of the transmitted uplink signal.

[0027] In one embodiment, the uplink signaling timing is a symbol or time slot that includes uplink signaling.

[0028] In one embodiment, the event is a CSI report event in a configured or scheduled uplink resource.

[0029] In one embodiment, the uplink signal is the Physical Uplink Shared Channel (PUSCH), the Physical Uplink Control Channel (PUCCH), the Scheduling Request (SR), or the Physical Random Access Channel (PRACH).

[0030] In one embodiment, CPU usage begins on the earliest downlink measurement reference signal prior to the occurrence of the determined event.

[0031] In one embodiment, CPU usage begins at the time slot where the event being reported is triggered.

[0032] In one embodiment, CPU usage continues until the last symbol or time slot of the transmission of the CSI report triggered by the event.

[0033] In one embodiment, the reference point for event-specific CSI reporting is the first symbol of the earliest of each channel measurement resource, wherein the timing of the corresponding latest channel measurement reference signal is located no later than the corresponding CSI reference resource.

[0034] In one embodiment, the reference point for an event-based CSI report is the first symbol or time slot of the channel measurement resource where the event has been triggered.

[0035] In one embodiment, for an event-based CSI report, if at least one condition or criterion for the event is not met, the CSI report does not consume CPU resources from that time slot.

[0036] In one embodiment, the device further includes: The component used to determine the downlink control information (DCI), which schedules uplink resources for event-triggered CSI reports; A component used to determine the start of CPU occupancy on the symbol or time slot of the uplink indication, or on the first symbol or time slot after the uplink indication; and A component used to determine the end of CPU usage at the last symbol of the transmitted CSI report portion of the transmitted uplink signal.

[0037] In one embodiment, the device further includes: The component used to determine the downlink control information (DCI), which schedules uplink resources for event-triggered CSI reports; The component used to determine the start of CPU occupancy on the first symbol of the Physical Downlink Control Channel (PDCCH), or on the first symbol after the PDCCH that triggered the CSI report; and A component used to determine the end of CPU usage at the last symbol of the transmitted CSI report portion of the transmitted uplink signal.

[0038] In one embodiment, the scheduled uplink resource is PUCCH or PUSCH.

[0039] In one embodiment, the CSI reference resource representing a given time slot of an event is a valid downlink time slot specific to event-based reporting.

[0040] In one embodiment, the transmitted CSI report has a report amount set to the reference signal received power RSRP or the signal interference plus noise ratio L1-SINR for layer 1.

[0041] According to a second aspect of the invention, an apparatus is provided, comprising at least one processor and at least one memory, wherein computer program code is stored on the at least one memory, the at least one memory and the computer program code being configured together with the at least one processor such that the apparatus performs at least: Identify the events to be reported; The following are triggered by this event: an uplink signal indicating the transmission of a Channel State Information (CSI) report, wherein the CSI report is scheduled to be sent in a reporting slot; or an uplink signal indicating the event; or an uplink signal requesting reporting resources; and Determine the end time for CPU occupancy of the CSI processing unit, such that CPU occupancy continues until the reporting time slot if the uplink signal indicates the event.

[0042] The above-described embodiments associated with the first aspect of the invention are also applicable to embodiments associated with the second aspect of the invention.

[0043] According to a third aspect of the present invention, a method is provided, the method comprising: Identify the events to be reported in the user equipment (UE); In this UE, the following are triggered by this event: an uplink signal indicating the transmission of a Channel State Information (CSI) report, wherein the CSI report is scheduled to be sent in a reporting slot; or an uplink signal indicating the event; or an uplink signal requesting reporting resources; and In this UE, the end time for CPU occupancy of the CSI processing unit is determined such that, if the uplink signal indicates the event, CPU occupancy continues until the reporting time slot.

[0044] The above-described embodiments associated with the first aspect of the invention are also applicable to embodiments associated with the third aspect of the invention.

[0045] According to a fourth aspect of the invention, a computer program is provided, comprising instructions that, when executed by a device, cause the device to perform at least the following operations: Identify the events to be reported; The following are triggered by this event: an uplink signal indicating the transmission of a Channel State Information (CSI) report, wherein the CSI report is scheduled to be sent in a reporting slot; or an uplink signal indicating the event; or an uplink signal requesting reporting resources; and Determine the end time for CPU occupancy of the CSI processing unit, such that CPU occupancy continues until the reporting time slot if the uplink signal indicates the event.

[0046] The above-described embodiments associated with the first aspect of the invention are also applicable to embodiments associated with the fourth aspect of the invention.

[0047] According to a fifth aspect of the invention, a computer program product is provided, stored on a non-transitory memory medium, the computer program product comprising computer program code, which, when executed by at least one processor, causes the means to at least perform: Identify the events to be reported; The following are triggered by this event: an uplink signal indicating the transmission of a Channel State Information (CSI) report, wherein the CSI report is scheduled to be sent in a reporting slot; or an uplink signal indicating the event; or an uplink signal requesting reporting resources; and Determine the end time for CPU occupancy of the CSI processing unit, such that CPU occupancy continues until the reporting time slot if the uplink signal indicates the event.

[0048] The above-described embodiments associated with the first aspect of the invention are also applicable to embodiments associated with the fifth aspect of the invention.

[0049] According to a sixth aspect of the present invention, an apparatus is provided, comprising: Components used to determine the events to be reported; Components for triggering the following due to this event: an uplink signal indicating the transmission of a Channel State Information (CSI) report, wherein the CSI report is scheduled to be sent in a reporting slot; or an uplink signal indicating the event; or an uplink signal requesting reporting resources; and A component used to determine the end time of CPU occupancy for the CSI processing unit, such that the CPU occupancy continues based on uplink signaling timing even when the uplink signal does not indicate the event.

[0050] In one embodiment, the device further includes: The component used to send the CSI report in the reporting time slot, wherein the CSI report is part of the transmitted uplink signal.

[0051] In one embodiment, the uplink signaling timing is a symbol or time slot that includes uplink signaling.

[0052] In one embodiment, the event is a CSI report event in a configured or scheduled uplink resource.

[0053] In one embodiment, the uplink signal is the Physical Uplink Shared Channel (PUSCH), the Physical Uplink Control Channel (PUCCH), the Scheduling Request (SR), or the Physical Random Access Channel (PRACH).

[0054] In one embodiment, CPU usage begins on the earliest downlink measurement reference signal prior to the occurrence of the determined event.

[0055] In one embodiment, CPU usage begins at the time slot where the event being reported is triggered.

[0056] In one embodiment, CPU usage continues until the last symbol or time slot of the transmission of the CSI report triggered by the event.

[0057] In one embodiment, the reference point for event-specific CSI reporting is the first symbol of the earliest of each channel measurement resource, wherein the timing of the corresponding latest channel measurement reference signal is located no later than the corresponding CSI reference resource.

[0058] In one embodiment, the reference point for an event-based CSI report is the first symbol or time slot of the channel measurement resource where the event has been triggered.

[0059] In one embodiment, for an event-based CSI report, if at least one condition or criterion for the event is not met, the CSI report does not consume CPU resources from that time slot.

[0060] In one embodiment, the scheduled uplink resource is PUCCH or PUSCH.

[0061] In one embodiment, the CSI reference resource representing a given time slot of an event is a valid downlink time slot specific to event-based reporting.

[0062] In one embodiment, the transmitted CSI report has a report amount set to the reference signal received power RSRP or the signal interference plus noise ratio L1-SINR for layer 1.

[0063] According to a seventh aspect of the invention, an apparatus is provided, comprising at least one processor and at least one memory, wherein computer program code is stored on the at least one memory, the at least one memory and the computer program code being configured together with the at least one processor such that the apparatus performs at least: Identify the events to be reported; The following are triggered by this event: an uplink signal indicating the transmission of a Channel State Information (CSI) report, wherein the CSI report is scheduled to be sent in a reporting slot; or an uplink signal indicating the event; or an uplink signal requesting reporting resources; and Determine the end time for CPU occupancy of the CSI processing unit such that, in the absence of an uplink signal indicating the event, the CPU occupancy continues based on uplink signaling timing.

[0064] The embodiments described above in relation to the sixth aspect of the present invention are also applicable to embodiments in relation to the seventh aspect of the present invention.

[0065] According to an eighth aspect of the present invention, a method is provided, the method comprising: Identify the events to be reported in the user equipment (UE); In this UE, the following are triggered by this event: an uplink signal indicating the transmission of a Channel State Information (CSI) report, wherein the CSI report is scheduled to be sent in a reporting slot; or an uplink signal indicating the event; or an uplink signal requesting reporting resources; and In this UE, an end time for CPU occupancy of the CSI processing unit is determined such that, in the absence of an uplink signal indicating the event, the CPU occupancy continues based on uplink signaling timing.

[0066] The above-described embodiments associated with the sixth aspect of the present invention are also applicable to embodiments associated with the eighth aspect of the present invention.

[0067] According to a ninth aspect of the present invention, a computer program is provided, comprising instructions that, when executed by a device, cause the device to perform at least the following operations: Identify the events to be reported; The following are triggered by this event: an uplink signal indicating the transmission of a Channel State Information (CSI) report, wherein the CSI report is scheduled to be sent in a reporting slot; or an uplink signal indicating the event; or an uplink signal requesting reporting resources; and Determine the end time for CPU occupancy of the CSI processing unit such that, in the absence of an uplink signal indicating the event, the CPU occupancy continues based on uplink signaling timing.

[0068] The above-described embodiments associated with the sixth aspect of the present invention are also applicable to embodiments associated with the ninth aspect of the present invention.

[0069] According to a tenth aspect of the present invention, a computer program product is provided, stored on a non-transitory memory medium, the computer program product comprising computer program code, which, when executed by at least one processor, causes the means to at least perform: Identify the events to be reported; The following are triggered by this event: an uplink signal indicating the transmission of a Channel State Information (CSI) report, wherein the CSI report is scheduled to be sent in a reporting slot; or an uplink signal indicating the event; or an uplink signal requesting reporting resources; and Determine the end time for CPU occupancy of the CSI processing unit such that, in the absence of an uplink signal indicating the event, the CPU occupancy continues based on uplink signaling timing.

[0070] The above-described embodiments associated with the sixth aspect of the present invention are also applicable to embodiments associated with the tenth aspect of the present invention.

[0071] According to an eleventh aspect of the present invention, an apparatus is provided, comprising: Components used to determine the events to be reported; Components used to determine the time window for event-based reporting for the device; Components that trigger the following due to the event: an uplink signal indicating the transmission of a Channel State Information (CSI) report, wherein the CSI report is scheduled to be sent in a reporting slot; or an uplink signal indicating the event; or an uplink signal requesting reporting resources; A component used to determine the end time of CPU occupancy for the CSI processing unit, such that the CPU occupancy continues until the reporting time slot when the uplink signal indicates the event; The component used to determine the end time of CPU occupation, such that the CPU occupation continues based on uplink signaling timing even if the uplink signal does not indicate the event; Components for adjusting total CPU load using a defined time window; and The component used to delay the actual event-based reporting ensures that the transmission time of the CSI report remains within a defined time window.

[0072] In one embodiment, by adjusting the total CPU load, the device is configured to maximize the transmission of the latest CSI reports to the network.

[0073] In one embodiment, the device further includes: The component used to send the CSI report in the reporting time slot, wherein the CSI report is part of the transmitted uplink signal.

[0074] In one embodiment, the uplink signaling timing is a symbol or time slot that includes uplink signaling.

[0075] In one embodiment, the event is a CSI report event in a configured or scheduled uplink resource.

[0076] In one embodiment, the uplink signal is the Physical Uplink Shared Channel (PUSCH), the Physical Uplink Control Channel (PUCCH), the Scheduling Request (SR), or the Physical Random Access Channel (PRACH).

[0077] In one embodiment, CPU usage begins on the earliest downlink measurement reference signal prior to the occurrence of the determined event.

[0078] In one embodiment, CPU usage begins at the time slot where the event being reported is triggered.

[0079] In one embodiment, CPU usage continues until the last symbol or time slot of the transmission of the CSI report triggered by the event.

[0080] In one embodiment, the reference point for event-specific CSI reporting is the first symbol of the earliest of each channel measurement resource, wherein the timing of the corresponding latest channel measurement reference signal is located no later than the corresponding CSI reference resource.

[0081] In one embodiment, the reference point for an event-based CSI report is the first symbol or time slot of the channel measurement resource where the event has been triggered.

[0082] In one embodiment, for an event-based CSI report, if at least one condition or criterion for the event is not met, the CSI report does not consume CPU resources from that time slot.

[0083] In one embodiment, the device further includes: The component used to determine the downlink control information (DCI), which schedules uplink resources for event-triggered CSI reports; A component used to determine the start of CPU occupancy on the symbol or time slot of the uplink indication, or on the first symbol or time slot after the uplink indication; and A component used to determine the end of CPU usage at the last symbol of the transmitted CSI report portion of the transmitted uplink signal.

[0084] In one embodiment, the device further includes: The component used to determine the downlink control information (DCI), which schedules uplink resources for event-triggered CSI reports; The component used to determine the start of CPU occupancy on the first symbol of the Physical Downlink Control Channel (PDCCH), or on the first symbol after the PDCCH that triggered the CSI report; and A component used to determine the end of CPU usage at the last symbol of the transmitted CSI report portion of the transmitted uplink signal.

[0085] In one embodiment, the scheduled uplink resource is PUCCH or PUSCH.

[0086] In one embodiment, the CSI reference resource representing a given time slot of an event is a valid downlink time slot specific to event-based reporting.

[0087] In one embodiment, the transmitted CSI report has a report amount set to the reference signal received power RSRP or the signal interference plus noise ratio L1-SINR for layer 1.

[0088] In one embodiment, if the event is a Reference Signal Received Power (RSRP) event and a measurement resource meets the RSRP level criterion, then the CPU occupancy begins on the symbol or time slot for measuring the RSRP of the measurement resource, or on the symbol or time slot for measuring these measurement resources.

[0089] According to a twelfth aspect of the invention, an apparatus is provided, comprising at least one processor and at least one memory, wherein computer program code is stored on the at least one memory, and the at least one memory and the computer program code are configured together with the at least one processor such that the apparatus performs at least the following: Identify the events to be reported; Determine the time window for event-based reporting for this device; The following are triggered by this event: an uplink signal indicating the transmission of a Channel State Information (CSI) report, wherein the CSI report is scheduled to be sent in a reporting slot; or an uplink signal indicating the event; or an uplink signal requesting reporting resources. Determine the end time for CPU occupancy of the CSI processing unit, such that the CPU occupancy continues until the reporting time slot if the uplink signal indicates the event; Determine the end time for CPU usage such that CPU usage continues based on uplink signaling timing if the uplink signal does not indicate the event. Use a defined time window to adjust the total CPU load; and The actual event-based reporting is delayed so that the transmission time of the CSI report remains within a defined time window.

[0090] The above-described embodiments associated with the eleventh aspect of the present invention are also applicable to embodiments associated with the twelfth aspect of the present invention.

[0091] According to a thirteenth aspect of the present invention, a method is provided, the method comprising: Identify the events to be reported in the user equipment (UE); In this UE, a time window for event-based reporting is determined for the device; In this UE, the following are triggered by this event: an uplink signal indicating the transmission of a Channel State Information (CSI) report, wherein the CSI report is scheduled to be sent in a reporting slot; or an uplink signal indicating the event; or an uplink signal requesting reporting resources. In this UE, the end time for CPU occupancy of the CSI processing unit is determined such that, if the uplink signal indicates the event, the CPU occupancy continues until the reporting time slot; In this UE, an end time for CPU occupancy is determined such that, if the uplink signal does not indicate the event, the CPU occupancy continues based on the uplink signaling timing. In this UE, the total CPU load is adjusted using a defined time window; and In this UE, the actual event-based reporting is delayed so that the transmission time of the CSI report remains within a defined time window.

[0092] The above-described embodiments associated with the eleventh aspect of the present invention are also applicable to embodiments associated with the thirteenth aspect of the present invention.

[0093] According to a fourteenth aspect of the invention, a computer program is provided, comprising instructions that, when executed by a device, cause the device to perform at least the following operations: Identify the events to be reported; Determine the time window for event-based reporting for this device; The following are triggered by this event: an uplink signal indicating the transmission of a Channel State Information (CSI) report, wherein the CSI report is scheduled to be sent in a reporting slot; or an uplink signal indicating the event; or an uplink signal requesting reporting resources. Determine the end time for CPU occupancy of the CSI processing unit, such that the CPU occupancy continues until the reporting time slot if the uplink signal indicates the event; Determine the end time for CPU usage such that CPU usage continues based on uplink signaling timing if the uplink signal does not indicate the event. Use a defined time window to adjust the total CPU load; and The actual event-based reporting is delayed so that the transmission time of the CSI report remains within a defined time window.

[0094] The above-described embodiments associated with the eleventh aspect of the present invention are also applicable to embodiments associated with the fourteenth aspect of the present invention.

[0095] According to a fifteenth aspect of the invention, a computer program product is provided, stored on a non-transitory memory medium, the computer program product comprising computer program code, which, when executed by at least one processor, causes the means to at least perform: Identify the events to be reported; Determine the time window for event-based reporting for this device; The following are triggered by this event: an uplink signal indicating the transmission of a Channel State Information (CSI) report, wherein the CSI report is scheduled to be sent in a reporting slot; or an uplink signal indicating the event; or an uplink signal requesting reporting resources. Determine the end time for CPU occupancy of the CSI processing unit, such that the CPU occupancy continues until the reporting time slot if the uplink signal indicates the event; Determine the end time for CPU usage such that CPU usage continues based on uplink signaling timing if the uplink signal does not indicate the event. Use a defined time window to adjust the total CPU load; and The actual event-based reporting is delayed so that the transmission time of the CSI report remains within a defined time window.

[0096] The above-described embodiments associated with the eleventh aspect of the present invention are also applicable to embodiments associated with the fifteenth aspect of the present invention.

[0097] In various embodiments of the device described above, the device may include at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the device to perform. In one embodiment, the device is a UE. Attached Figure Description

[0098] Figure 1 This shows an example of a periodic report on the CPU usage of the current application;

[0099] Figure 2 A first embodiment of CSI processing unit occupancy calculation is shown;

[0100] Figure 3 A second embodiment of CSI processing unit occupancy calculation is shown;

[0101] Figure 4 A third embodiment of CSI processing unit occupancy calculation is shown;

[0102] Figure 5 A fourth embodiment of CSI processing unit occupancy calculation is shown;

[0103] Figure 6a An exemplary wireless network scenario according to at least some embodiments of the present invention is shown; and

[0104] Figure 6b A simplified block diagram of a network node according to an embodiment of the present invention is shown. Detailed Implementation

[0105] The following section provides a more detailed description of suitable apparatus and possible mechanisms for determining CPU usage in performing event-triggered CSI reports. Although the following focuses on 5G and / or 6G networks, the embodiments described below are by no means limited to implementation in said networks, but are applicable to any network that supports the process for determining CPU usage in event-triggered CSI reports.

[0106] Considering the user equipment side, i.e., the device, one embodiment includes the following steps.

[0107] In the first step, the device includes components for determining events to be reported.

[0108] In some examples, the events used for reporting can be one or more of the following (including, but not limited to): Event-1: The quality of the reference signal (e.g., L1-RSRP) is worse than the configured threshold. Event-2: The quality of at least one reference signal becomes a threshold better than that of a certain reference signal (such as the reference signal corresponding to PDCCH / PDSCH reception and / or PUCCH / PUSCH transmission). Event-3: The quality of the reference signal is better than a certain threshold.

[0109] In some example embodiments, an event-triggered report may include a report of the quality of downlink reference signals(s) and the measured quality of the reference signals(s).

[0110] In the second step, the apparatus includes components for triggering the following due to the event: an uplink signal indicating the transmission of a Channel State Information (CSI) report, wherein the CSI report is scheduled to be sent in a reporting slot; or an uplink signal indicating the event; or an uplink signal requesting reporting resources.

[0111] In the third step, the apparatus includes components for determining the end time of CSI processing unit CPU occupancy, such that the CPU occupancy continues based on uplink signaling timing even when the uplink signal does not indicate the event.

[0112] In other words, there are three alternative parts in the above embodiments, namely: 1) A component for triggering an uplink signal indicating the transmission of a Channel State Information (CSI) report due to the event, wherein the CSI report is scheduled to be transmitted in a reporting time slot. In other words, the first option is that the CSI report is instructed to be transmitted in a reporting time slot associated with the uplink signal. 2) Alternatively, it can be used for components that trigger an uplink signal indicating the event due to the event. In other words, the second option is that the uplink signal indicates the event, but reporting resources can be scheduled by the network. The uplink signal only indicates the event, so this is more general and can cover a variety of reporting methods, such as, for example, non-periodic reporting. 3) Alternatively, a component that triggers an uplink signal requesting reporting resources due to the event. In other words, the third option is that the uplink signal indicates the event, but the reporting resources can be scheduled by the network based on the uplink signal requesting the resources. The uplink signal indicates that the UE requests reporting resources.

[0113] In another example embodiment, an apparatus includes: components for determining an event for reporting; components for triggering, due to the event, the following: an uplink signal indicating the transmission of a Channel State Information (CSI) report, wherein the CSI report is scheduled to be sent in a reporting slot; or an uplink signal indicating the event; or an uplink signal requesting reporting resources; and components for determining the end time of CPU occupancy for the CSI processing unit based on the following conditions: If the uplink signal indicates the event, the CPU usage continues until the reporting time slot, and If the uplink signal does not indicate the event, the CPU usage continues based on the uplink signaling timing.

[0114] The above steps form a corresponding embodiment involving a device, in this case, a UE. Furthermore, the embodiment also relates to other aspects, such as corresponding methods, computer programs, and computer program products. On the other hand, some steps may be initiated by a base station, thus one aspect involves a telecommunications system (or connection) involving a base station and a UE. The embodiment may involve various different telecommunications technologies, such as, for example, 5G and 6G.

[0115] Regarding the CSI processing unit (i.e., CPU), when a UE is configured to report CSI, the UE needs to determine the CPU used per CSI report. The UE can indicate to the network the number of parallel CSI calculations supported (e.g., the number of CPUs). The (maximum) number of parallel CPUs can be carrier-specific (e.g., one per carrier / component carrier) and / or across multiple component carriers. There are certain limitations on the number of CSI reports that a UE can process, and these limitations are processed and monitored based on the number of CPUs.

[0116] Specific boundaries can be set for CPU usage (number) in the time domain, ensuring that there is a CPU-specific start time (i.e., CPU usage) and a CPU-specific end time in the UE. This time interval is the same as the CPU usage in the UE. Time usage can be calculated for each CSI report. Multiple CSI reports can occupy CPU units at the same time. Specific CSI reports can have different start and end times for specific CPU usage for that report, depending on their type.

[0117] In this invention, various embodiments are used to determine the method for... Event-based The issue of CSI processing unit (i.e., CPU) usage in CSI reports was taken into consideration.

[0118] In other words, a new reporting model is proposed for the CPU in the Layer 1 report for the UE.

[0119] More precisely, in this invention, CPU usage time is proposed for event-based CSI reporting, wherein CPU usage is based on a UL signal indicating that an event has occurred, and / or on whether the UE has determined to perform an event-based report (i.e., the report has been triggered or will be sent).

[0120] In an embodiment of the present invention, reference is made to... Figure 2 Figure 20 in the figure shows a predetermined event 203, which in this embodiment is CSI reference resource slot n. Event 203 is marked with a white rectangle with a full outer line in the figure. SSB1 201 and SSB2 202 utilize... Figure 1 Similar arrows indicate that both SSB1 201 and SSB2 202 use a periodic approach. Alternatively, the arrows could represent CSI-RS or any DL RS configured for measurement (and reporting).

[0121] Then, in this embodiment, the UE triggers an uplink signal 205, which indicates a reporting event on the configured uplink resources. The uplink signal 205 is marked as a gray rectangle in the illustration. This uplink signal 205 includes the following information: an event 203 exists in time slot n (e.g., the UE indicates that a reporting event has occurred) and the CSI report should occur in reporting time slot n' 206. In the illustration, reporting time slot n' 206 is marked as a white rectangle defined by a dashed line, a longer and thicker gray line.

[0122] It should be noted that in this embodiment, CPU usage 204 can begin on the immediately preceding previous measurement RS (SSB1 201) before the determined event 203 (=CSI reference resource slot n). Alternatively, CPU usage 204 can begin on some other, earlier measurement RS (SSB1 201) before the event, i.e., on the second, third, fourth, etc., measurement RS (SSB1) before the occurrence of event 203. The figure illustrates the option of selecting the start time of CPU usage 204 on the second measurement RS (SSB1 201) before the occurrence of event 203, as an example of many possible options.

[0123] exist Figure 2 In the illustrated embodiment, the end time of CSI processing unit (=CPU) occupancy 204 is determined to occur at the end of reporting slot n' 206. The top two arrows indicate the duration of CPU occupancy 204 and its end time. In practice, and in one embodiment, CPU occupancy 204 will continue until the last symbol of the actual event-based report executed in reporting slot n' 206.

[0124] In one embodiment, the report in report slot n' 206 may be carried by a scheduled PUSCH or PUCCH. In other words, a PUSCH or PUCCH transmitted in the UL direction may include a CSI report. In this sense, the last symbol of that particular PUSCH or PUCCH then determines the end time of CSI processing unit occupancy 204.

[0125] In other words, to summarize Figure 2 In the first primary embodiment 20 shown, if the UE has triggered an uplink signal 205 (=gray box) indicating a reporting event on the configured uplink resources, the event-triggered CSI report occupies one or more CSI processing units on one or more symbols, starting from a reference point specific to the event-based report and ending at the last symbol of the uplink resource (e.g., PUSCH or PUCCH) configured for the event-based report. In this embodiment, the uplink channel carries the event-triggered CSI report.

[0126] In another embodiment of the invention, reference is made to... Figure 3 Figure 30 in the figure shows a predetermined event 303, which in this embodiment is CSI reference resource slot n. Event 303 is marked with a white rectangle with a full outer line in the figure. SSB1 301 and SSB2 302 utilize... Figure 1 and Figure 2Similar arrows indicate that both SSB1 301 and SSB2 302 are in a periodic manner. Arrows can similarly indicate the CSI-RS or any DL-RS used for reporting configuration measurements.

[0127] Then, in this embodiment, the UE sends an uplink (UL) signal 305, but the UL signal does not indicate any reporting in reporting slot n' 306. In the illustration, the uplink signal 305 is marked as a white rectangle with a shorter and thinner dashed outer line.

[0128] In the illustration, reporting slot n' 306 is marked as a white rectangle bounded by a dashed line, a longer and thicker gray line.

[0129] The start time of CPU usage error 304 can be determined by combining the above. Figure 2 The description is similarly organized.

[0130] However, the end time of CPU usage 304 is defined differently.

[0131] exist Figure 3 In the illustrated embodiment 30, the end time of CSI processing unit (=CPU) occupancy 304 is determined to occur at the end of uplink signal 305 transmitted by the UE. The top two arrows indicate the duration of CPU occupancy 304 and its end time. In practice, and in one embodiment, CPU occupancy 304 will continue until the last symbol of the configured uplink resource, i.e., until the last symbol of UL signal 304, which does not indicate a report in reporting slot n' 306.

[0132] In one example, UL signal 305 may refer to, for example, SR (Schedule Request), PRACH (Physical Random Access Channel) preamble, SRS (Sound Reference Signal), PUCCH (Format) that transmits an indication associated with an event-based report or a reported event, or any uplink signal configured to be associated with an event-triggered report (i.e., indicating an event, indicating the use of UL resources for reporting an event, or requesting resources for reporting an event-triggered report).

[0133] In one example, a CSI report can be transmitted using MAC CE.

[0134] for Figure 3 As illustrated in Example 30, it can be concluded that in this case, the UE has nothing to report regarding the CSI report in reporting slot n' 306.

[0135] In other words, to summarize Figure 3In the second primary embodiment 30 shown, if the UE does not trigger an uplink signal indicating an event report, an event-triggered CSI report occupies one or more CSI processing units on one or more symbols, starting from a reference point specific to the event-based report and ending at the last symbol of the uplink resources configured for the signal indicating the event report. In this embodiment, the uplink channel triggers the event-triggered CSI report, but in this specific case, the UE does not send an actual CSI report. Therefore, in other words, the uplink channel does not carry an actual event-triggered CSI report.

[0136] This operating mode effectively reduces the number of event-triggered CSI reports (and CPU-intensive CSI reports). Since the number of CSI reports a UE can process is limited, this alleviates the UE's workload. This shows a significant advantage in event-based channel state information reporting.

[0137] In one exemplary embodiment, if it is determined that a reporting event has not yet been triggered, an event-triggered CSI report occupies CPU(s) on one or more symbols, starting from a reference point specific to the event-based report and extending up to N symbols or time slots prior to the uplink resources configured for the event-based report, where N is a positive integer.

[0138] In one example embodiment, if it is determined that a reporting event has not yet been triggered, an event-triggered CSI report occupies CPU(s) on one or more symbols, starting from a reference point specific to the event-based report and extending to the first symbol of the uplink resources configured for the event-based report.

[0139] In one example embodiment, the reference point for the event-specific CSI report is the first symbol of the earliest of each channel measurement resource, wherein the timing of the corresponding latest channel measurement reference signal is located no later than the corresponding CSI reference resource.

[0140] In one example embodiment, the reference point for event-specific CSI reporting is the first symbol or time slot of the channel measurement resource where the event has been triggered. In one embodiment, an event is triggered when at least one condition or criterion for the event has been determined to be met. Furthermore, the following example is presented: If the event is an RSRP (Reference Signal Received Power) event, and a measurement resource meets the RSRP level criterion, then CPU occupancy begins on the symbol or time slot where the RSRP of that measurement resource is measured, or on the symbol or time slot where those measurement resources are measured.

[0141] In one example embodiment, in a time slot or symbol where a CSI report for an event determines that at least one condition or criterion for the event has not been met, the CSI report does not consume CPU resources from that time slot (or symbol).

[0142] In another embodiment 40 of the present invention, reference is made to... Figure 4 .

[0143] According to Figure 4 In this exemplary embodiment 40, the event-based CSI report occupies (multiple) CPUs from the first symbol after the uplink indication for the event-based report (or from the time slot or symbol where the signal is transmitted) until the last symbol of the scheduled PUSCH or PUCCH carrying the CSI report. In other words, in the first option, the CPU occupancy 404 begins on the symbol or time slot of the uplink indication. Alternatively, in the second option, the CPU occupancy 404 begins on the first time slot or symbol after the uplink indication. The beginning of CPU occupancy 404 is marked in the illustration, and a UL signal 405 is present on time slot n'_event to indicate an event-triggered report (a rectangle with a thin dashed outer line). After the UL signal 405, there is a DCI 407 (downlink control information) that schedules uplink resources for the event-triggered report. This is marked as a rectangle with the text "DCI". After the DCI 407 block, there is a reporting time slot n'406 marked with a thicker gray dashed outer line. In reporting slot n'406, an actual report occurs on the scheduled resource. Simultaneously, in this embodiment, the end of CPU usage 404 is determined at the end of reporting slot n'406. The entire CPU usage 404 time interval can now be viewed as indicated by the thicker horizontal arrow at the top. As in an earlier embodiment, the leftmost block in the time domain is CSI reference resource slot n, representing event 403.

[0144] In another embodiment 50 of the present invention, reference is made to... Figure 5 . Figure 5 This indicates that the above text has been combined Figure 4 Alternative options for the discussed embodiments.

[0145] like Figure 5As shown, in one example embodiment, an event-triggered (scheduled) CSI report occupies CPU(s) from the first symbol after the PDCCH that triggers the CSI report until the last symbol of the scheduled UL resource carrying the CSI report on report slot n' 506. In other words, CPU occupancy 504 begins at the start of DCI 507, which schedules uplink resources for CSI reporting (i.e., for event-triggered reporting). CPU occupancy 504 ends at the end of the CSI report on the scheduled resource on report slot n' 506 (= at the last symbol or slot), i.e., at the end of report slot n' 506. This CPU occupancy 504 time interval is also shown at the top of the figure using a thicker arrow. As in the previous embodiments and illustrations, the leftmost block in the time domain is CSI reference resource slot n, representing event 503. Thereafter, as shown by the rectangle with a thinner dashed outer line, a UL signal 505 is present on slot n'_event to indicate an event-triggered report. In this embodiment, the CPU usage of 504 is relatively short compared to earlier embodiments. When comparing... Figure 5 and Figure 4 When specifying alternative implementations of DCI, it is obvious Figure 5 The CPU usage time interval of the embodiment is 504 times higher than Figure 4 The CPU usage 404 time interval in this embodiment is shorter.

[0146] In Figure 5 In another embodiment related to the arrangement shown, the scheduled UL resource is a PUCCH or a PUSCH.

[0147] In one example embodiment, the CSI reference resource (at slot n representing the event) is a valid downlink slot specific to event-based reporting.

[0148] In one example embodiment, the reported CSI report has a reporting amount that is set to the Reference Signal Received Power (RSRP) or the Signal Interference-to-Noise Ratio (L1-SINR) for Layer 1.

[0149] Regarding the symbols used, in embodiments where the uplink signal does not indicate an event, this can mean at least two different possible scenarios. In the first possible option, this means that the uplink signal was not initially sent. In the second possible option, this means that the uplink signal was sent, but that uplink signal does not indicate any event (or it indicates that no event has been triggered).

[0150] In one exemplary embodiment, a time window for event-based reporting is determined for the UE, allowing the UE to adjust its total CPU load using this time window to maximize the delivery of the latest CSI reports to the network. Therefore, the UE can delay actual event-based reporting as long as the transmission time of the CSI report is within the time window defined by the UE. However, the time window is defined such that the delay in event-based reporting is insignificant. In other words, the delay in event-based reporting can be set relatively small. In this exemplary embodiment, there is an advantage that the UE can have better overall performance when configured with both non-event-based and event-based CSI reporting.

[0151] In one embodiment of the present invention, the user equipment 610 discussed above is a smartphone.

[0152] In a more general manner, certain device and network arrangements are subsequently disclosed, and the present invention is applicable to these various telecommunications connection arrangements.

[0153] Figure 6a and Figure 6b Examples of wireless telecommunications network implementations and apparatuses as part of exemplary telecommunications network implementations are shown.

[0154] Figure 6a An exemplary wireless network scenario is shown according to at least some embodiments of the present invention.

[0155] Figure 6a An exemplary wireless network scenario according to at least some embodiments of the present invention is illustrated. Figure 6a An example scenario could include a wireless communication network comprising a user equipment (UE) 610, access nodes (such as a base station (BS) 620), and core network components 630.

[0156] This invention focuses on the UE 610 side of wireless telecommunication connection, and Figure 6a An example of uplink and downlink connection is presented, where UE 610 transmits and base station 620 receives, or vice versa. In one example, some actions can be performed in UE 610, and some other actions can be performed in base station 620.

[0157] Figure 6a The configuration presented here is merely a single example of many possible devices in many possible wireless communication systems. Therefore, the invention is not limited to... Figure 6a and Figure 6b Examples of devices, connection types / directions, and systems.

[0158] Back Figure 6aUE 610 may include, for example, a smartphone, cellular phone, machine-to-machine (M2M) node, machine-type communication (MTC) node, Internet of Things (IoT) node, automobile, automotive telemetry unit, laptop computer, tablet computer, or another suitable UE or mobile station. Generally, UE refers to any terminal device capable of wireless communication. It can be a mobile device or a fixed device. By way of example and not limitation, UE may also be referred to as a communication device, terminal device, subscriber station (SS), portable subscriber station, mobile station (MS), or access terminal (AT). Figure 6a In the example system, UE 610 can wirelessly communicate with BS 620 or a cell of BS 620 via air interface 615. In some example embodiments, BS 620 can be considered the serving BS of UE 610. UE 610 can also communicate simultaneously with more than one BS 620 and / or more than one cell of BS 620.

[0159] BS 620 can be directly connected to core network 630 via interface 625, or connected to core network 630 via at least one intermediate node. Furthermore, core network 630 can connect to another network (…) via interface 635. Figure 6a (Not shown in the image) coupling, through which connectivity to other networks, such as the Global Interconnect Network, can be obtained. The BS 620 can also be coupled via an inter-base station interface (…). Figure 6a (Not shown in the image) Connects to one or more other BSs.

[0160] UE 610 can connect to BS 620 via air interface 615. Air interface 615 between UE 610 and BS 620 can be configured according to the supported Radio Access Technology (RAT) for UE 610 and BS 620. Examples of cellular RATs include Long Term Evolution (LTE), New Radio (NR), which can also be referred to as fifth-generation (5G) radio access technology. For example, in the context of LTE, BS 620 can be referred to as eNB, while in the context of NR, BS 620 can be referred to as gNB. In any case, the example embodiments are not limited to any particular wireless technology. Rather, the example embodiments can be utilized in any wireless communication network (which can be cellular or non-cellular) operating according to 3GPP standards, IEEE standards (such as IEEE 802.11-based LANs), or some other wireless technology where improved transmission and / or reception performance, and particularly improved MIMO performance, is desired between access nodes such as BS and UEs.

[0161] The ever-increasing data throughput requirements in wireless communication networks necessitate the use of wide spectrum. Therefore, frequency bands used for 5G (also known as NR) are currently divided into different frequency ranges. Frequency range 1 (FR1) includes bands below 6 GHz, some of which were traditionally used in previous standards, but this range has been expanded to cover potential new spectrum availability up to 7125 MHz. Another range is frequency range 2 (FR2), which currently includes bands from 24.25 GHz to 52.6 GHz. Frequencies in this range and above are referred to as millimeter-wave (mmWave) frequencies. The mmWave frequency range is attractive because it offers significantly higher available bandwidth compared to the bands in FR1, which helps provide the data rates required for 5G.

[0162] The described embodiments may be particularly advantageous for millimeter-wave frequencies including the FR2 range, but can be equally applied to FR1 or any other frequency. As previously stated, while applicable to any wireless network, for simplicity, the examples discussed focus primarily on 5G. 5G is envisioned to utilize more base stations or nodes (the so-called small cell concept) than current LTE networks, including macro sites operating in cooperation with smaller local access nodes, and perhaps also employing various wireless technologies to achieve better coverage and enhanced data rates. 5G will likely consist of more than one radio access technology / radio access network (RAT / RAN), each optimized for specific use cases and / or spectrum. 5G mobile communications can have a wide range of use cases and associated applications, including video streaming, augmented reality, different data sharing methods, and various forms of machine-type applications, including vehicle safety, different sensors, and real-time control.

[0163] MIMO is one of the key enabling technologies for 5G wireless technology. The basic principle of MIMO is to use multiple transmit and receive antennas to increase the throughput and / or reliability of data transmission. Increased throughput can be achieved by sending / receiving different data streams on multiple antennas, while increased reliability can be achieved by using multiple antennas to send / receive multiple versions of the same data.

[0164] Beamformed antenna arrays play a crucial role in 5G implementation. While offering high bandwidth, mmWave frequencies have higher propagation losses, which vary significantly depending on the environment. Smaller wavelengths at higher carrier frequencies allow for smaller antenna element sizes, giving the opportunity to place one or more (e.g., two, three, or more) relatively large antenna arrays at the UE. This, in turn, leads to various challenges in maintaining the expected performance.

[0165] Considering 2×2 MIMO as a non-limiting example, downlink (DL) MIMO performance (e.g., FR2 in the mmWave frequency range) can be achieved by using polarization separation (common polarization and cross-polarization) of dual-fed antenna arrays at the base station (also known as gNB) and / or at the UE, where each polarization corresponds to a MIMO branch. The rationale behind this approach is to achieve high and similar antenna gain performance in both MIMO channels while maintaining a compact spatial antenna design.

[0166] Achieving high cross-polarization discrimination (XPD) is important when designing dual-polarized antenna arrays. XPD can be defined as the ratio of the common polarization component to the orthogonal cross-polarization component in a sector or beamwidth angle.

[0167] Decorrelation at the antenna array can be achieved by ensuring that each antenna feed corresponds to a single polarization and that the resulting dual-feed polarizations are designed to be orthogonal. This allows for the design of antenna arrays with high XPD at the feed points. This approach will ensure full utilization of both MIMO channels for line-of-sight (LoS) and / or non-line-of-sight (NLoS) operation, provided that the maximum gain direction and orthogonal polarization orientation are aligned between the antenna arrays at the UE and the gNB.

[0168] Furthermore, the high antenna gain requirements for mmWave frequencies (e.g., FR2) will reduce its radiated beamwidth, thus necessitating beam steering at the antenna array (or multiple arrays) to cover the required angular space. Beam steering capability can be achieved using adjustable phase shifters at each element in the antenna array, allowing the beam direction to be controlled electrically (phased array) rather than mechanically.

[0169] The XPD of any antenna (or antenna array) depends on its radiation pattern and can change dynamically as a function of the angle of departure (AoD) and / or angle of arrival (AOA). This dependence increases with changes in the radiation pattern and with electrical changes in the radiation pattern. Higher antenna gain patterns result in larger XPD variations in angular space. Phase-controlled arrays also exhibit increased XPD variations in angular space.

[0170] Therefore, the physical orientation of the antenna at mmWave frequencies will have a much greater impact on MIMO throughput than the impact seen at frequencies below 6 GHz, where decorrelation at the UE is achieved through physical separation between two receive antennas, each with a random and distinct radiation pattern. In contrast, mmWave architectures can utilize dual orthogonally polarized antennas (or antenna arrays) designed for equal high-gain radiation patterns.

[0171] Figure 6b A simplified block diagram of a network node according to an embodiment of the present invention is shown.

[0172] Figure 6b An example of a device 6000 for wireless communication is shown, which involves a transmitter and a receiver (i.e., transceiver 6006). In this example, device 6000 may be a base station 620. In the following sections, device 6000 is also referred to as a network node. In another embodiment, device 6000 may be a UE 610, since the main structural components between UE 610 and base station 620 are identical. However, the following discussion focuses primarily on the functionality of base station 620.

[0173] Such a device may include, for example Figure 6b The functional units disclosed in the document Figure 6b A simplified block diagram of a network node (i.e., device) according to various aspects and related embodiments is shown.

[0174] Figure 6b The network node 6000 can be a base station, access point, access node, gNB, evolved NodeB (eNB), server, host, or any other network entity that can communicate with UE 610.

[0175] The device 6000 may include at least one processor or control unit or module 6002 (labeled CPU). At least one memory 6004 may be provided in the device. The memory 6004 may include computer program instructions or computer code contained therein. One or more transceivers 6006 may be provided, and the device may also include an antenna 6008. Although only one antenna is shown, many antennas and multiple antenna elements may be provided in the device. For example, other configurations of the device may be provided. For example, in addition to wireless communication, the network node may be additionally configured for wired communication with the UE, and in this case, the antenna 6008 may be shown as any form of communication hardware, not limited to an antenna only.

[0176] The transceiver 6006 can be a transmitter, a receiver, or both, or a unit or device that can be configured to transmit and receive both. The transmitter and / or receiver (in relation to the wireless portion) can also be implemented as a remote wireless head, which is not located within the device itself but, for example, within a mast. Operation and functionality can be flexibly performed in different entities, such as nodes, hosts, or servers. In other words, the division of labor can vary depending on the circumstances. One possible use case is enabling network nodes to deliver local content. One or more functions can also be implemented as virtual applications(s) within software that can run on a server.

[0177] In some embodiments, the device 6000 may include at least one processor 6002 and at least one memory 6004 including computer program code. The at least one memory 6004 including computer program code may be configured, together with the at least one processor 6002, to cause the device 6000 to perform at least any of the processes described herein.

[0178] The processor 6002 can be embodied by any computing or data processing device, such as a central processing unit (CPU), digital signal processor (DSP), application-specific integrated circuit (ASIC), programmable logic device (PLD), field-programmable gate array (FPGA), digital enhancement circuitry, or similar devices or combinations thereof. The processor 6002 can be implemented as a single controller, or multiple controllers or processors.

[0179] For firmware or software, the implementation may include modules or units (e.g., procedures, functions, etc.) of at least one chipset. At least one memory 6004 may independently be any suitable storage device, such as a non-transitory computer-readable medium. As used herein, the term "non-transitory" refers to a limitation on the medium itself (i.e., tangible, not tactile), rather than a limitation on the persistence of data storage (e.g., RAM versus ROM). Hard disk drives (HDDs), random access memory (RAM), flash memory, or other suitable memory may be used. Memory 6004 may be combined with processor 6002 on a single integrated circuit, or memory 6004 may be separate from it. Furthermore, computer program instructions may be stored in memory 6004, and those that can be processed by processor 6002 may be any suitable form of computer program code, such as a compiled or interpreted computer program written in any suitable programming language. Memory 6004 or the data storage entity is typically internal, but may also be external or a combination thereof, such as in the case of obtaining additional storage capacity from a service provider. Memory 6004 may be fixed or removable.

[0180] The memory 6004 and computer program instructions can be configured, together with the processor 6002 of a particular device, to cause a hardware device (such as a network node 6000) to perform any of the processes described above. Therefore, in some embodiments, a non-transitory computer-readable medium can be encoded with instructions or one or more computer programs (such as added or updated software routines, applets, or macros) that, when executed in hardware, can perform a process such as one of the processes described herein. In other embodiments, a computer program product can be embodied in instructions for performing any of the processes described above, or a computer program product containing and encoding instructions that, when executed in hardware, perform any of the processes described above. The computer program can be encoded by a programming language, which can be a high-level programming language such as Objective-C, C, C++, C#, Java, etc., or a low-level programming language such as machine language or assembly language. Alternatively, some embodiments can be executed entirely in hardware.

[0181] although Figure 6b The network element examples discussed herein refer to base station 620, but the corresponding main elements are also part of UE 610, as the corresponding part in the connection of BS 620. Therefore, the applicability of the above general structural elements and the above process steps via computer program also exists on the UE 610 side.

[0182] Given the prior art, the technical effects and advantages of this invention lie in its clear and concise definition of CPU usage rules for event-based CSI reporting. Therefore, the limitations that the UE can process regarding CSI reports and their number are better managed and satisfied, preventing the UE from discarding CSI reports due to excessive CPU utilization. This makes UE operations around CSI reporting smoother, thereby ensuring better UE operability in both UL and DL transmission directions. Typically, this invention defines CPU usage for event-triggered reporting, and some examples provide components for determining CPU usage that can limit the number of CPUs used for event-triggered reporting, thus preventing the UE from discarding CSI reports (e.g., due to priority issues and exceeding CPU limits). Reducing discarded CSI reports can increase throughput because the reports provide the network with information about the UE's channel conditions and enable more flexible scheduling.

[0183] The foregoing description has provided a complete and informative description of exemplary embodiments of the invention through exemplary and non-limiting examples. However, various modifications and adaptations will be apparent to those skilled in the art when read in conjunction with the accompanying drawings and examples, given the foregoing description. Nevertheless, all such and similar modifications taught in this invention will still fall within the scope of this invention, which is defined by the claims.

Claims

1. An apparatus (610) comprising: The component used to identify the events (203, 303) to be reported; Components for triggering the following due to the events (203, 303): an uplink signal (205, 305) indicating the transmission of a Channel State Information (CSI) report, wherein the CSI report is scheduled to be sent in a reporting slot (206, 306); or an uplink signal (205, 305) indicating the event (203, 303); or an uplink signal (205, 305) requesting reporting resources; and A component for determining the end time of CPU occupation (204, 304) for CSI processing unit, such that the CPU occupation (204, 304) continues based on the uplink signaling timing when the uplink signal (205, 305) does not indicate the event.

2. The apparatus (610) according to claim 1, wherein the apparatus further comprises: Components for transmitting the CSI report in the reporting time slots (206, 306), wherein the CSI report is part of the transmitted uplink signal (205, 305).

3. The apparatus (610) according to claim 1, wherein the uplink signaling timing includes symbols or time slots for uplink signaling.

4. The apparatus (610) according to claim 1, wherein the event (203, 303) is a CSI report event in a configured or scheduled uplink resource.

5. The apparatus (610) according to claim 1, wherein the uplink signals (205, 305) are Physical Uplink Shared Channel (PUSCH), Physical Uplink Control Channel (PUCCH), Scheduling Request (SR), or Physical Random Access Channel (PRACH).

6. The apparatus (610) of claim 1, wherein the CPU occupancy (204, 304) begins on the earliest downlink measurement reference signal prior to the occurrence of the determined event (203, 303).

7. The apparatus (610) of claim 1, wherein the CPU occupancy (204, 304) begins at the time position of the time slot in which the event (203, 303) for reporting is triggered.

8. The apparatus (610) of claim 1, wherein the CPU occupancy (204, 304) continues until the last symbol or time slot of the transmission is reported by the CSI triggered by the event.

9. The apparatus (610) of claim 1, wherein the reference point for the event-based CSI report is the first symbol of the earliest of each channel measurement resource, wherein the timing of the corresponding latest channel measurement reference signal is located no later than the corresponding CSI reference resource.

10. The apparatus (610) of claim 1, wherein the reference point for the event-based CSI report is the first symbol or time slot of the channel measurement resource in which the event (203, 303) has been triggered.

11. The apparatus (610) of claim 1, wherein, for the event-based CSI report, the time slot or symbol in which at least one condition or criterion for the event (203, 303) is not met is determined, and the CSI report does not consume CPU resources from that time slot.

12. The apparatus (610) according to claim 4, wherein the scheduled uplink resource is PUCCH or PUSCH.

13. The apparatus (610) of claim 9, wherein the CSI reference resource in the given time slot representing the event (203, 303) is a valid downlink time slot specific to the event-based reporting.

14. The apparatus (610) of claim 1, wherein the transmitted CSI report has a report quantity set to Reference Signal Received Power RSRP or for Layer 1 Signal Interference Plus Noise Ratio L1-SINR.

15. A method comprising: Identify the events (203, 303) used for reporting in the user equipment (UE). In the UE, the following are triggered due to the events (203, 303): an uplink signal (205, 305) indicating the transmission of a Channel State Information (CSI) report, wherein the CSI report is scheduled to be sent in a reporting slot (206, 306); or an uplink signal (205, 305) indicating the event (203, 303); or an uplink signal (205, 305) requesting reporting resources; and In the UE, an end time for CPU occupation (204, 304) of the CSI processing unit is determined such that, in the absence of uplink signals (205, 305) indicating the event, the CPU occupation (204, 304) continues based on the uplink signaling timing.

16. A computer program comprising instructions that, when executed by a device, cause the device to perform at least the following operations: Identify the events to be reported (203, 303); The following are triggered by the events (203, 303): an uplink signal (205, 305) indicating the transmission of a Channel State Information (CSI) report, wherein the CSI report is scheduled to be sent in a reporting slot (206, 306); or an uplink signal (205, 305) indicating the event (203, 303); or an uplink signal (205, 305) requesting reporting resources; and The end time for CPU occupation (204, 304) of the CSI processing unit is determined such that, in the absence of uplink signals (205, 305) indicating the event, the CPU occupation (204, 304) continues based on the uplink signaling timing.

Images