Devices and methods for event-based CSI reporting
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-12-13
- Publication Date
- 2026-08-14
AI Technical Summary
然而,gNB可能不知晓当前波束和对应信道已经改变,使得波束切换是需要的
Smart Images

Figure CN122580918A_ABST
Abstract
Description
Technical Field
[0001] This application generally relates to information technology. Some example embodiments of this application relate to supporting both event-based Channel State Information (CSI) reporting and non-event-based CSI reporting. Background Technology
[0002] User equipment (UE) can transmit CSI reports to the network to provide information about current channel conditions. CSI reporting helps the network optimize various aspects of communication based on current channel conditions, such as resource allocation, beamforming, and transmission parameters. In the existing CSI framework in 5G NR, beamforming and CSI reporting can be fully controlled and scheduled by network nodes (such as gNBs). However, the gNB may be unaware that the current beam and corresponding channel have changed, making beam switching necessary. This could be due to changes in the location, rotation, or speed of user nodes (such as UEs), or other environmental reasons that have significantly altered the beam's impact on link quality since the last beam report or beam refinement. Therefore, there is room for improvement in the CSI reporting process. Summary of the Invention
[0003] This summary is provided to introduce the selection of concepts in a simplified form, which will be further described in the detailed embodiments below. This summary is not intended to identify key or essential features of the claimed subject matter, nor is it intended to limit the scope of the claimed subject matter.
[0004] Example embodiments enable the processing of both event-based and non-event-based CSI reports within the same framework. In an embodiment, the UE is configured to notify the network of a triggering event for CSI reporting using at least one uplink resource associated with the event, and to receive a response to the triggering event from a network node. The UE can then determine whether to transmit at least one of the following based on a priority ordering rule set by the network or pre-configured at the UE: an event-based CSI report, or a non-event-based CSI report that is available simultaneously with an event-based CSI report. This can be achieved through the features of the independent claims. Additional implementations are provided in the dependent claims, the specification, and the drawings.
[0005] According to a first aspect, a user node may include: at least one processor; and at least one memory including instructions that, when executed by the at least one processor, cause the user node to at least: receive from a network node configuration for non-event-based Channel State Information (CSI) reporting and event-based CSI reporting; receive from the network node configuration for at least one condition to trigger an event for event-based CSI reporting; receive from the network node configuration for at least one uplink resource associated with an event for event-based CSI reporting; and receive from the network node an indication for triggering an event for event-based CSI reporting. When at least one of the reported or non-event-based CSI reports can be used for transmission on the same time slot, priority is given to at least one of the event-based or non-event-based CSI reports; an event is detected as being triggered based on a measurement performed by the user node; an uplink signal is transmitted using at least one uplink resource to notify the network node that an event has been triggered; an uplink grant is received from the network node in response to the uplink signal; and in response to the uplink grant, at least one of the following is transmitted to the network node based on the received indication: an event-based CSI report or one or more non-event-based CSI reports that can be transmitted on the same time slot.
[0006] According to an example embodiment of the first aspect, an indication is received via Media Access Control Element (MAC CE) signaling or Radio Resource Control (RRC) configuration.
[0007] According to an example embodiment of the first aspect, the uplink signal includes a scheduling request, an uplink reference signal, a probe reference signal, or a non-contentionable physical random access channel preamble.
[0008] According to an example embodiment of the first aspect, an uplink grant is received together with at least one of an information element or a code point field, the information element or code point field being configured to indicate that the uplink grant is associated with an uplink signal.
[0009] According to an example embodiment of the first aspect, the indicated priority ordering includes, for the transmission, a selection of at least one of an event-based CSI report or one or more non-event-based CSI reports.
[0010] According to an example embodiment of the first aspect, at least one memory includes instructions that, when executed by at least one processor, cause a user node to apply event-based CSI reporting and one or more non-event-based CSI reporting to the same uplink resource based on a configured priority order.
[0011] According to a second aspect, a network node includes: at least one processor; and at least one memory including instructions that, when executed by the at least one processor, cause the network node to at least: transmit to a user node a configuration for non-event-based Channel State Information (CSI) reporting and event-based CSI reporting; transmit to the user node a configuration for at least one condition to trigger an event for event-based CSI reporting; transmit to the user node a configuration for at least one uplink resource, wherein the at least one uplink resource is associated with an event for event-based CSI reporting; and transmit to the user node a configuration for at least one uplink resource. User node transmission indication, the indication being used to prioritize at least one of event-based CSI reports or non-event-based CSI reports when at least one of event-based CSI reports or non-event-based CSI reports is available for transmission on the same time slot; receive an uplink signal from the user node via at least one uplink resource indicating that an event has been triggered; transmit uplink grant to the user node in response to the uplink signal; and receive at least one of event-based CSI reports or one or more non-event-based CSI reports from the user node in response to the uplink grant.
[0012] According to an example embodiment of the second aspect, the instruction is transmitted via Media Access Control Element (MAC CE) signaling or Radio Resource Control (RRC) configuration.
[0013] According to an example embodiment of the second aspect, the uplink signal includes a scheduling request, an uplink reference signal, a probe reference signal, or a non-contentionable physical random access channel preamble.
[0014] According to an example embodiment of the second aspect, the uplink grant is transmitted together with at least one of the information elements or code point fields, which are configured to indicate that the uplink grant is associated with an uplink signal.
[0015] According to an example embodiment of the second aspect, the indicated priority ordering includes: selection of event-based CSI reporting or one or more non-event-based CSI reporting.
[0016] According to an example embodiment of the second aspect, event-based CSI reporting and one or more non-event-based CSI reporting are received on the same uplink resource.
[0017] According to a third aspect, a method may include: receiving from a network node configuration for non-event-based Channel State Information (CSI) reporting and event-based CSI reporting; receiving from the network node configuration for at least one condition to trigger an event for event-based CSI reporting; receiving from the network node configuration for at least one uplink resource, wherein the at least one uplink resource is associated with an event for event-based CSI reporting; and receiving from the network node an indication that when at least one of event-based CSI reporting or non-event-based CSI reporting is available in a phase When transmitted on the same time slot, at least one of event-based CSI reports or non-event-based CSI reports is prioritized; an event is detected as triggered based on a measurement performed by the user node; an uplink signal is transmitted using at least one uplink resource to notify the network node that the event has been triggered; an uplink grant in response to the uplink signal is received from the network node; and in response to the uplink grant, based on the received indication, at least one of the following is transmitted to the network node: an event-based CSI report or one or more non-event-based CSI reports that can be transmitted on the same time slot. This method can be performed, for example, by the user node.
[0018] According to an example embodiment of the third aspect, an indication is received via Media Access Control Element (MAC CE) signaling or Radio Resource Control (RRC) configuration.
[0019] According to an example embodiment of the third aspect, the uplink signal includes a scheduling request, an uplink reference signal, a probe reference signal, or a non-contentionable physical random access channel preamble.
[0020] According to an example embodiment of the third aspect, an uplink grant is received together with at least one of an information element or a code point field, the information element or code point field being configured to indicate that the uplink grant is associated with an uplink signal.
[0021] According to an example embodiment of the third aspect, the indicated priority ordering includes, for the transmission, a selection of at least one of event-based CSI reporting or one or more non-event-based CSI reporting.
[0022] According to an example embodiment of the third aspect, the method includes applying event-based CSI reporting and one or more non-event-based CSI reporting to the same uplink resource based on a configured priority order.
[0023] According to a fourth aspect, a method may include: transmitting to a user node a configuration for non-event-based channel state information (CSI) reporting and event-based CSI reporting; transmitting to the user node a configuration for at least one condition to trigger an event for event-based CSI reporting; transmitting to the user node a configuration for at least one uplink resource associated with an event for event-based CSI reporting; transmitting to the user node an indication to prioritize at least one of event-based CSI reporting or non-event-based CSI reporting when at least one of event-based CSI reporting or non-event-based CSI reporting is available for transmission in the same time slot; receiving from the user node via at least one uplink resource an uplink signal notifying that an event has been triggered; transmitting uplink grant to the user node in response to the uplink signal; and receiving from the user node, in response to the uplink grant, at least one of event-based CSI reporting or one or more non-event-based CSI reporting.
[0024] According to an example embodiment of the fourth aspect, the instruction is transmitted via Media Access Control Element (MAC CE) signaling or Radio Resource Control (RRC) configuration.
[0025] According to an example embodiment of the fourth aspect, the uplink signal includes a scheduling request, an uplink reference signal, a probe reference signal, or a non-contentionable physical random access channel preamble.
[0026] According to an example embodiment of the fourth aspect, the uplink grant is transmitted together with at least one of the information elements or code point fields, which are configured to indicate that the uplink grant is associated with an uplink signal.
[0027] According to an example embodiment of the fourth aspect, the indicated priority ordering includes: selection of event-based CSI reporting or one or more non-event-based CSI reporting.
[0028] According to an example embodiment of the fourth aspect, event-based CSI reporting and one or more non-event-based CSI reporting are received on the same uplink resource.
[0029] According to a fifth aspect, a computer program can be configured, when executed by a processor, to cause a device to perform at least the following: receiving from a network node a configuration for non-event-based Channel State Information (CSI) reporting and event-based CSI reporting; receiving from the network node a configuration for at least one condition to trigger an event for event-based CSI reporting; receiving from the network node a configuration for at least one uplink resource associated with an event for event-based CSI reporting; and receiving from the network node an indication for triggering an event for event-based CSI reporting or non-event-based CSI reporting. At least one of the reporting methods can be used to prioritize at least one of event-based CSI reports or non-event-based CSI reports when transmitted in the same time slot; detect that an event has been triggered based on a measurement performed by the user node; transmit an uplink signal using at least one uplink resource to notify the network node that the event has been triggered; receive an uplink grant from the network node in response to the uplink signal; and, in response to the uplink grant, transmit at least one of the following to the network node based on the received indication: event-based CSI reports or one or more non-event-based CSI reports that can be transmitted in the same time slot. The computer program may also include instructions for causing the device to perform any example embodiment of the method of the third aspect.
[0030] According to a sixth aspect, an apparatus may include: components for receiving from a network node a configuration for non-event-based channel state information (CSI) reporting and event-based CSI reporting; components for receiving from the network node a configuration for at least one condition, the at least one condition being used to trigger an event for event-based CSI reporting; components for receiving from the network node a configuration for at least one uplink resource, wherein the at least one uplink resource is associated with an event for event-based CSI reporting; and components for receiving from the network node an indication for when at least one of event-based CSI reporting or non-event-based CSI reporting is available. When transmitted on the same time slot, the device includes: a component for prioritizing at least one of event-based CSI reports or non-event-based CSI reports; a component for detecting that an event has been triggered based on a measurement performed by a user node; a component for transmitting an uplink signal using at least one uplink resource to notify a network node that an event has been triggered; a component for receiving an uplink grant from a network node in response to the uplink signal; and a component for transmitting, in response to the uplink grant, at least one of event-based CSI reports or one or more non-event-based CSI reports that can be transmitted on the same time slot to a network node based on a received indication. The device may also include components for performing any example embodiment of the method of the third aspect.
[0031] According to a seventh aspect, a computer program may include instructions for causing a device to perform at least the following: transmitting to a user node a configuration for non-event-based Channel State Information (CSI) reporting and event-based CSI reporting; transmitting to the user node a configuration for at least one condition to trigger an event for event-based CSI reporting; transmitting to the user node a configuration for at least one uplink resource, wherein the at least one uplink resource is associated with an event for event-based CSI reporting; transmitting to the user node an indication for prioritizing at least one of event-based CSI reporting or non-event-based CSI reporting when at least one of event-based CSI reporting or non-event-based CSI reporting is available for transmission in the same time slot; receiving from the user node via at least one uplink resource an uplink signal notifying that an event has been triggered; transmitting uplink grant to the user node in response to the uplink signal; and receiving from the user node, in response to the uplink grant, at least one of event-based CSI reporting or one or more non-event-based CSI reporting. The computer program may also include instructions for any example embodiment of the method for causing the device to perform the fourth aspect.
[0032] According to an eighth aspect, an apparatus may include: components for transmitting to a user node a configuration for non-event-based channel state information (CSI) reporting and event-based CSI reporting; components for transmitting to the user node a configuration of at least one condition for triggering an event for event-based CSI reporting; components for transmitting to the user node a configuration of at least one uplink resource, wherein the at least one uplink resource is associated with an event for event-based CSI reporting; and components for transmitting to the user node an indication for triggering an event for event-based CSI reporting. At least one of the following can be used to prioritize at least one of the event-based CSI reports or non-event-based CSI reports when they are transmitted on the same time slot: a component for receiving an uplink signal from a user node via at least one uplink resource indicating that an event has been triggered; a component for transmitting an uplink grant to a user node in response to the uplink signal; and a component for receiving at least one of the event-based CSI reports or one or more non-event-based CSI reports from a user node in response to the uplink grant. The device may also include components for performing any example embodiment of the method of the fourth aspect.
[0033] Many of the accompanying features will become more readily understood as they are considered in conjunction with the following detailed description, which takes into account the accompanying drawings. Attached Figure Description
[0034] The accompanying drawings, which are included to provide a further understanding of the exemplary embodiments and form part of this specification, illustrate exemplary embodiments and, together with the description, help to explain the exemplary embodiments. In the drawings:
[0035] Figure 1 An example of a method for multiplexing multiple CSI reports into uplink resources, according to an example embodiment, is shown;
[0036] Figure 2 An example message sequence diagram between user nodes and network nodes for event-based CSI reporting is shown according to an example embodiment;
[0037] Figure 3 An example of a device configured to practice one or more example embodiments is shown;
[0038] Figure 4 An example of a method for event-based CSI reporting according to an example embodiment is shown;
[0039] Figure 5 An example of a method for assisting event-based CSI reporting, according to an example embodiment, is shown;
[0040] Figure 6 An example of a method for event-based CSI reporting according to another example embodiment is shown;
[0041] Figure 7 An example of a method for assisting event-based CSI reporting, according to another exemplary embodiment, is shown;
[0042] Figure 8 An example of a method for event-based CSI reporting according to another example embodiment is shown; and
[0043] Figure 9 An example of a method for assisting event-based CSI reporting, according to another exemplary embodiment, is shown.
[0044] In the accompanying drawings, the same reference numerals may be used to denote the same parts. Detailed Implementation
[0045] Reference will now be made in detail to exemplary embodiments, examples of which are illustrated in the accompanying drawings. The detailed description provided below, in conjunction with the accompanying drawings, is intended as a description of the example and is not intended to represent the only form in which the example can be constructed or utilized. This description illustrates the functionality of the example and the possible sequences of operations for constructing and operating the example. However, the same or equivalent functionality and sequences can be implemented through different examples.
[0046] This specification relates to 3GPP 5G NR and 6G physical layer design. In 3GPP 5G NR, a UE can be configured with one or more CSI reporting configurations. Furthermore, each CSI reporting configuration can be configured to report at least one of the following: L1-RSRP (Layer 1 Reference Signal Received Power), L1-SINR (Layer 1 Signal-to-Interference-and-Noise Ratio), PMI (Precoding Matrix Indicator), RI (Rank Indicator), CQI (Channel Quality Indicator), etc. L1-RSRP and L1-SINR can be used for beam measurement reporting, and PMI, RI, and CQI are used for CSI reporting. Additionally, each reporting configuration can be configured to have time-domain behavior: periodic, semi-persistent, or aperiodic. The UE performs measurements based on the received downlink reference signal, which can be transmitted in a periodic, semi-persistent, or aperiodic manner. The UE can then use uplink resources to report the prepared CSI(s) to the network.
[0047] When a UE has UL (uplink) resources for CSI report transmission, multiple CSI reports may be available. The UE can perform multiplexing and prioritization among CSI reports and report certain CSI reports in (multiple) UL resources according to predefined rules (e.g., as defined in Section 9.2.5 of 3GPP TS38.213). For example, different CSI reports may have different pre-configured priorities. In the NR CSI reporting framework, multiple concurrent CSI reports and resources may exist to be processed. The UE can be configured, for example, to transmit a single CSI report with the highest priority, or to multiplex multiple CSI reports based on their priorities. When beam and CSI reporting are entirely controlled and scheduled by the gNB, the gNB may be unaware of beam / channel changes that have occurred. To address this, UE-initiated / event-driven beam reporting and possible subsequent beam switching can be used to reduce overhead (reducing the need for highly periodic beam reporting) and latency.
[0048] One objective is to support event-based CSI reporting, such as event-based beamforming, within the CSI reporting framework. Therefore, the UE can be configured for both event-based and non-event-based reporting. Furthermore, the UE can be configured to indicate to the network via uplink resources associated with an event that triggers an event-based L1 CSI report. For example, the UE can be configured to use UL information elements or information that can be modulated into uplink signaling transmissions (e.g., on / off keying for a configured periodic scheduling request resource (PUCCH resource)) to notify the network of the triggered event based on the associated UL resource. After receiving a response from the network associated with the indicated event trigger, the UE can determine which CSI reports to transmit from the available CSI reports based on a priority ordering rule. In embodiments, the network can control which CSI reports the UE reports to the network when both event-based and non-event-based CSI reports are simultaneously available. For example, the network can be configured to indicate via DCI, RRC, or MAC CE messages which CSI reports from among the available CSI reports will be transmitted by the UE in the next uplink resource after a triggered event. Alternatively, in the case of both event-based and non-event-based CSI reports being available simultaneously, the priority ordering of CSI report transmission can be pre-configured at the UE.
[0049] The example implementation enables the triggering of event-based CSI reports in situations where the network may be unaware of potential beam switching needs (e.g., during congestion). Furthermore, prioritization between non-event-based and event-based CSI reports is enabled, as is the transmission of both types of CSI reports on the same UL resource based on priority. Therefore, UL reporting overhead can be reduced.
[0050] Figure 1 The illustration shows an example of multiplexing multiple CSI reports into uplink resources from the UE's perspective, according to an example embodiment.
[0051] The UE's reporting domain can be divided into a non-event-based reporting domain and an event-based reporting domain. The UE can be configured by the network node with multiple CSI reporting configurations for both event-based and non-event-based CSI reporting. Non-event-based CSI reporting may include, for example, periodic CSI reporting. Event-based CSI reporting may include, for example, CSI reporting triggered by an L1 UE event. The UE can be configured to continuously measure downlink reference signals and detect when an L1 UE event occurs based on one or more conditions and parameters configured by the network for event-based CSI reporting. For example, an (L1 UE) event could be the UE notifying of a change in the currently serving beam or a change in the previously reported beam(s), where the change could be an RSRP difference exceeding a specific threshold. Furthermore, the event can be associated with at least one UL resource of the network node, which the UE is configured to use to indicate to the network node that an event has been triggered. For example, (multiple) scheduling request resources (specific physical uplink control channel, PUCCH, resources) can be explicitly associated with L1 UE events, i.e., at a specific L1 UE event (such as sending a beam / CSI report to the network), the UE can be configured to transmit an affirmative SR (scheduling request) to the network.
[0052] At least one uplink resource associated with the event may also be, for example, a UL resource used for transmitting a non-contention PRACH (Physical Random Access Channel) preamble. Additionally or alternatively, the at least one UL resource may include (multiple) UL SRS (Detection Reference Signal) resources associated with a UL SRS resource set having a specific purpose. An example of a UL SRS resource set could be: "beam management, antenna switching, codebook, non-codebook, positioning".
[0053] For example, the UE can detect that event 110 has been triggered for event-based CSI report 104 (e.g., L1-RSRP report). The UE can then transmit an uplink signal associated with event 110 to the network node to declare that event 110 has occurred in the reporting resource domain. For example, the UE can send a scheduling request 112 to the network node requesting UL resources for reporting event-based CSI report 104.
[0054] The UE can then be configured to monitor responses from network nodes to scheduling request 112. The UE can be configured to anticipate a network response after a minimum delay of 114. A correlation may exist between a specific scheduling request resource (associated with a specific L1 UE event) and a specific network response. The network node may respond, for example, using UL authorization via downlink control information (DCI) 116. DCI may refer to a dynamic physical layer control message from the network to (multiple) UEs, containing aspects of downlink and / or uplink data scheduling. DCI 116 may have specific information elements indicating that the specific DCI on the PDCCH (Physical Downlink Control Channel) also provides a response to the L1 UE event (event 110) indicated via the specific scheduling request resource.
[0055] Alternatively, one or more specific UL SRS resource IDs (associated with the UL signal reporting the UE L1 event) and corresponding network responses (e.g., DCI 116) can be configured. DCI 116 can be configured to have a new code point field defined as an indication that the DCI provides a response, or an existing code point field can be reused to provide that indication, such as the last entry of the SRS request code point, which is currently reserved.
[0056] Upon receiving DCI 116, the UE can determine whether the transmission of event-based CSI report 104 needs to be prioritized. For example, there may be time slots with shared time and frequency UL resources for both event-based and non-event-based CSI reporting. Furthermore, in a non-event-based CSI reporting configuration, the UE may have two CSI reports 100 and 102 that are available simultaneously with event-based CSI report 104 and are to be transmitted during the next UL resource 118 used for CSI reporting.
[0057] In an embodiment, the UE can be configured to determine which CSI reports should be prioritized based on an indication received from a network node. This indication can be included, for example, in a network response (e.g., DCI 116). Alternatively, the indication can be received by the UE via a higher layer (such as in an RRC configuration). Radio Resource Control (RRC) can refer to the provision of radio resource-related control data. Radio Resource Control messages can be transmitted on various logical control channels, such as, for example, a common control channel (CCCH) or a dedicated control channel (DCCH). Logical control channels can be mapped to one or more signaling radio bearers (SRBs). Alternatively, the indication can be received by the UE via MAC CE signaling. Therefore, the network node can instruct the UE on how to perform prioritization either after a network-notified event or beforehand.
[0058] For example, a network node may instruct the UE to prioritize event-based CSI reports 104 over non-event-based CSI reports 100, 102. Alternatively, the network node may instruct the UE to prioritize non-event-based CSI reports 100, 102 over event-based CSI reports 104. Based on this instruction, the UE may, for example, first populate the next UL resource 118 for CSI reporting with event-based CSI reports, and then, if space remains, populate the UL resource with lower-priority non-event-based CSI reports. The network node may also instruct the UE to select event-based CSI reports 104 instead of non-event-based CSI reports 100, 102, or vice versa. For example, the network node may detect the existence of a limited number of UL resources available for CSI reporting. The network node may then instruct in DCI 116 to schedule UL resources for providing event-based CSI reports 104. The instruction in DCI 116 may include, for example, a bit field indicating the scheduling of UL resources for event-based reporting. Alternatively, the indication can be in DCI format. The indication can also have a separate Radio Network Temporary Identifier (RNTI) (a UE-specific RNTI is used for the Cyclic Redundancy Check (CRC) of the masked DCI), which the UE uses to monitor the PDCCH, particularly for scheduling event-triggered reporting.
[0059] The UE can transmit one or more CSI reports from CSI reports 100, 102, and 104 on the next UL resource 118 according to the indicated selection / priority sorting instruction received from the network node.
[0060] In embodiments, priority ordering rules can be pre-configured at the UE. For example, after receiving a network response with UL authorization, the UE can retrieve instructions from its memory to determine whether to prioritize event-based CSI reports 104 if multiple CSI reports are available for transmission. Instead of receiving a priority ordering rule determined by the network in response to an event triggered by a notification, the UE can be configured to follow a pre-configured priority ordering rule. For example, the UE can be configured to prioritize event-based CSI reports. Alternatively, event-based CSI reports can be configured to be treated with the same priority as one or more other types of CSI reports. For example, event-based CSI reports can be configured to have the same priority as non-periodic CSI reports. The UE can be configured to transmit one or more available CSI reports according to a pre-configured priority ordering rule after receiving an uplink authorization from a network node in response to an event triggered by a notification to a network node. The priority ordering rules configured at the UE can be, for example, based on standards.
[0061] Following a transmission on UL resource 118, and when no new events are triggered, the UE can be configured to transmit (multiple) non-event-based CSI reports (e.g., L1-RSRP report 106 and / or CSI report 108) available for transmission on the next UL resource 120 based on other configured multiplexing rules for reporting; that is, without using event-triggered priority ordering rules. Therefore, the UE can be configured to apply different priority ordering and multiplexing rules for different CSI report transmissions.
[0062] Figure 2 The diagram illustrates an example flowchart for CSI reporting between a user node and a network node. The user node can be, for example, UE 200. The network node can be, for example, a gNB supporting 5G New Radio (NR) or a Node B (6gNB) 202 supporting 6G. UE 200 can communicate with 6gNB 202 via multiple radio channels. Communication between UE 200 and 6gNB 202 can be bidirectional. Therefore, any device can be configured to operate as a transmitter and / or receiver.
[0063] At 204, UE 200 can be configured to indicate to 6gNB 202 the ability to report event-based L1 CSI, such as for beam reporting.
[0064] At position 206, 6gNB 202 can configure UE 200 for both non-event-based CSI reporting and event-based CSI reporting. Event-based CSI reporting can be, for example, L1-RSRP reporting / beamcasting.
[0065] At position 208, the 6gNB 202 can be configured to send configurations of one or more conditions and parameters to the UE 200 for triggering an event. Furthermore, the 6gNB 202 can be configured to send UL resources explicitly associated with the event to the UE 200. The UL resource can be, for example, a scheduling request resource used by the UE 200 to notify the 6gNB 202 of the triggered event. This configuration can be performed via an RRC / MAC CE signaling message. The MAC CE signaling can also be used by the 6gNB 202, for example, to activate or deactivate CSI reporting.
[0066] At 210, UE 200 can trigger events for CSI reporting based on measurements performed by UE 200. The UE can measure parameters configured by 6gNB 202 and detect when one or more conditions are met.
[0067] At 212, UE 200 can be configured to transmit event-related uplink signals on the uplink resources indicated at 208. For example, the UE can transmit a scheduling request to 6gNB 202 on the next scheduling request timing (PUSCCH resource).
[0068] At 214, UE 200 can be configured to monitor network responses to uplink signals. This network response can refer to the DL signal associated with the UL signal transmitted at 212. The network response may include UL authorization. For example, UE 200 can monitor a specific PDCCH used for DCI associated with scheduling request transmissions.
[0069] At position 216, the 6gNB 202 can transmit network responses, such as DCI, to the UE 200.
[0070] At 218, UE 200 can be configured to detect network responses associated with transmitted UL signals, such as DCIs associated with scheduling request transmissions.
[0071] Upon receiving a network response, at 220, UE 200 can be configured to select / prioritize event-based CSI reports to be transmitted on the next uplink resource with sufficient resources for CSI reporting.
[0072] In this embodiment, UE 200 can read from DCI, and if multiple CSI reports are available, the UE should prioritize or select event-based CSI reporting. For example, DCI may indicate at least one of the following: - If both an event-based CSI report and (multiple) non-event-based CSI reports need to be transmitted by UE 200 in the same time slot, should the event-based CSI report or (multiple) non-event-based CSI reports associated with the L1 UE event be transmitted according to existing rules? - If there are both event-based CSI reports and (multiple) non-event-based CSI reports to be transmitted by UE 200 in the same time slot, should the event-based CSI report associated with the L1 UE event take precedence over (multiple) non-event-based CSI reports?
[0073] In an embodiment, UE 200 may be instructed by 6gNB 202 in a higher-layer configuration (such as in an RRC signaling message) to prioritize or select event-based CSI reports. The RRC may be configured to indicate which of the following is prioritized or selected by UE 200 over another when both are simultaneously available for transmission: event-based CSI reports or one or more non-event-based CSI reports. For example, the prioritization / selection instruction may be received by UE 200 in the same RRC or MAC CE message configured to trigger an event-based CSI reporting.
[0074] In an embodiment, the 6gNB 202 can be configured to provide an indication in the MAC CE signaling of prioritization or selection of event-based CSI reports. The MAC CE can be configured to indicate which of the following is prioritized or selected over another when both are available for transmission: event-based CSI reports or one or more non-event-based CSI reports.
[0075] In this embodiment, the prioritization or selection of event-based CSI reports can be determined by the UE 200 without instruction from the network. For example, the UE can be pre-configured to prioritize event-based CSI reports over one or more types of non-event-based CSI reports.
[0076] At 220, UE 200 can be configured to transmit a CSI report for the event to 6gNB 202 based on the priority sorting / selection performed.
[0077] Figure 3 An example of a device configured to perform one or more example embodiments is illustrated.
[0078] Device 300 may include at least one processor 302. At least one processor 302 may include one or more processing devices, such as, for example, a coprocessor, microprocessor, controller, digital signal processor (DSP), processing circuitry system with or without an accompanying DSP, or various other processing devices, including integrated circuits, such as, for example, application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), microcontroller units (MCUs), hardware accelerators, dedicated computer chips, etc.
[0079] Device 300 may also include at least one memory 304. At least one memory 304 may be configured to store, for example, computer program code 306, such as operating system software and application software. At least one memory 304 may include one or more volatile memory devices, one or more non-volatile memory devices, and / or combinations thereof. For example, at least one memory 304 may be embodied as a magnetic storage device (such as a hard disk drive, magnetic tape, etc.), an optical storage device, or a semiconductor memory (such as a mask ROM, PROM (programmable ROM), EPROM (erasable PROM), flash ROM, RAM (random access memory), etc.).
[0080] Device 300 may also include one or more communication interfaces 308 configured to enable device 300 to transmit information to and receive information from other devices. Communication interface 308 may be configured to provide at least one wireless radio connection, such as, for example, a 3GPP mobile broadband connection (e.g., 3G, 4G, 5G, or higher). However, communication interface 308 may be configured to provide one or more other types of connections, such as wireless local area network (WLAN) connections (e.g., standardized by the IEEE 802.11 series or the Wi-Fi Alliance); short-range wireless network connections (e.g., Bluetooth, NFC (Near Field Communication), or RFID connections); wired connections (e.g., local area network (LAN) connections, universal serial bus (USB) connections, or optical network connections); or wired internet connections. Communication interface 308 may include or be configured to be coupled to at least one antenna to transmit and / or receive radio frequency signals. One or more of the various types of connections may also be implemented as a separate communication interface, which may be coupled to or configured to be coupled to multiple antennas.
[0081] Device 300 may include, for example, computing devices such as base stations, network nodes, server devices, client nodes, mobile phones, tablet computers, laptop computers, etc. Although device 300 is illustrated as a single device, it should be understood that, where applicable, the functionality of device 300 may be distributed across multiple devices.
[0082] When device 300 is configured to perform a certain function, one or more components of device 300 (such as, for example, at least one processor 302 and / or memory 304) can be configured to perform that function. Furthermore, when at least one processor 302 is configured to perform a certain function, that function can be implemented using, for example, program code 306 included in memory 304.
[0083] In this embodiment, device 300 may be a network node and is configured to perform at least the functions of a network node as described herein. The network node may be a base station, such as a 5G or 6G NodeB. A network node may also be referred to as a network device or a radio access network (RAN) node. Although depicted as a single device, a network node may not be a standalone device, but rather a distributed computing system, for example, coupled to a remote wireless headend.
[0084] A network node can be configured to transmit configurations for event-based and non-event-based CSI reporting to a user node. The network node can also be configured to configure the user node to trigger events for CSI reporting and to notify the network node of the triggered events via (multiple) specific UL resources. The network node can also be configured to send responses associated with (multiple) specific UL resources to the UE. In an embodiment, the network node can further be configured to indicate to the user node whether to prioritize or select event-based CSI reporting or (multiple) non-event-based CSI reporting if both CSI reporting types are available simultaneously. This indication can be provided, for example, via DCI, RRC, or MAC CE messages.
[0085] In this embodiment, device 300 may be a user node, such as a UE, and is configured to perform at least the functions of the UE described herein. The user node may also be referred to as a client node or user equipment. The user node may be configured to receive from a network node a configuration that triggers an event for CSI reporting, wherein the event is associated with (multiple) UL resources. Based on the associated (multiple) UL resources, the user node may be configured to notify the network node of the triggered event. The user node may be configured to determine, based on an indication received from the network node or based on a preset configuration, whether to prioritize or select the event-based CSI report or (multiple) non-event-based CSI reports to be transmitted to the network node if both CSI report types are simultaneously available for transmission. This indication may be received, for example, via a DCI, RRC, or MAC CE message. Thus, depending on the implementation, the indication may be received from the network node in response to the notified event, or before the event is triggered.
[0086] The functions described herein can be performed at least in part by one or more computer program product components, such as software components. According to an embodiment, device 300 includes a processor or processor circuitry, such as, for example, a microcontroller, which is configured by program code at execution to perform embodiments of the described operations and functions. Alternatively or additionally, the functions described herein can be performed at least in part by one or more hardware logic components. For example, and not limitingly, illustrative types of hardware logic components that can be used include field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standard products (ASSPs), system-on-a-chip (SoCs), complex programmable logic devices (CPLDs), and graphics processing units (GPUs).
[0087] The device 300 includes components for performing at least one method described herein. In one example, the components include at least one processor 302 and at least one memory 304, the at least one memory 304 including program code 306 configured to cause the device 300 to perform the method when executed by the at least one processor 302.
[0088] Figure 4 An example of a method for event-based CSI reporting according to an exemplary embodiment is illustrated. Method 400 can be performed, for example, by a user node.
[0089] At 402, the method may include receiving configuration from a network node for non-event-based channel state information (CSI) reporting and event-based CSI reporting.
[0090] At 404, the method may include: receiving configuration of at least one condition from a network node, the at least one condition being used to trigger an event for event-based CSI reporting.
[0091] At 406, the method may include: receiving configuration of at least one uplink resource from a network node, wherein the at least one uplink resource is associated with an event reported for event-based CSI.
[0092] At 408, the method may include: detecting that an event has been triggered based on a measurement performed by the user node.
[0093] At 410, the method may include: using at least one uplink resource to transmit an uplink signal to notify network nodes that an event has been triggered.
[0094] In an embodiment, the method may include: receiving a downlink signal from a network node in response to an uplink signal. The downlink signal may include an indication for prioritizing at least one of event-based CSI reports or one or more non-event-based CSI reports that may be transmitted in the same time slot. The method may further include: transmitting an event-based CSI report or at least one of one or more available non-event-based CSI reports to the network node in response to the downlink signal. The user node may be configured to transmit the event-based CSI report and / or one or more non-event-based reports based on the indicated priority order.
[0095] Figure 5 An example of a method for assisting event-based CSI reporting, according to an exemplary embodiment, is illustrated. Method 500 can be performed, for example, by a network node.
[0096] At 502, the method may include transmitting to the user node a configuration for non-event-based channel state information (CSI) reporting and event-based CSI reporting.
[0097] At 504, the method may include: transmitting to the user node the configuration of at least one condition for triggering an event for event-based CSI reporting.
[0098] At 506, the method may include: transmitting to a user node the configuration of at least one uplink resource, wherein the at least one uplink resource is associated with an event reported for event-based CSI.
[0099] At 508, the method may include: receiving an uplink signal from a user node via at least one uplink resource indicating that a notification event has been triggered.
[0100] In an embodiment, the method may include: transmitting a downlink signal to a user node in response to an uplink signal. The downlink signal may include an indication for prioritizing event-based CSI reports or one or more non-event-based CSI reports that may be transmitted in the same time slot. The method may further include: receiving from the user node at least one of an event-based CSI report or one or more non-event-based CSI reports in response to the downlink signal. The event-based CSI report or at least one of the one or more non-event-based CSI reports may be received from the user node based on the indicated priority order.
[0101] Figure 6 An example of a method for event-based CSI reporting is illustrated according to another exemplary embodiment. Method 600 can be performed, for example, by a user node.
[0102] At 602, the method may include receiving configuration from a network node for non-event-based channel state information (CSI) reporting and event-based CSI reporting.
[0103] At 604, the method may include: receiving configuration of at least one condition from a network node, the at least one condition being used to trigger an event for event-based CSI reporting.
[0104] At 606, the method may include: receiving configuration of at least one uplink resource from a network node, wherein the at least one uplink resource is associated with an event reported for event-based CSI.
[0105] At 608, the method may include: detecting that an event has been triggered based on a measurement performed by the user node.
[0106] At 610, the method may include: using at least one uplink resource to transmit an uplink signal to notify the network node that an event has been triggered.
[0107] At 612, the method may include: receiving an uplink grant from a network node in response to an uplink signal.
[0108] At 614, the method may include: in response to an uplink grant, transmitting to a network node at least one of the following: an event-based CSI report or one or more non-event-based CSI reports that may be transmitted in the same time slot, wherein the user node is configured to prioritize at least one of the event-based CSI reports or non-event-based CSI reports.
[0109] Figure 7 An example of a method for assisting event-based CSI reporting, according to another exemplary embodiment, is illustrated. Method 700 can be performed, for example, by a network node.
[0110] At 702, the method may include transmitting to the user node a configuration for non-event-based channel state information (CSI) reporting and event-based CSI reporting.
[0111] At 704, the method may include: transmitting to a user node the configuration of at least one condition for triggering an event for event-based CSI reporting.
[0112] At 706, the method may include: transmitting to a user node the configuration of at least one uplink resource, wherein the at least one uplink resource is associated with an event reported for event-based CSI.
[0113] At 708, the method may include: receiving an uplink signal from a user node via at least one uplink resource indicating that a notification event has been triggered.
[0114] At 710, the method may include: transmitting an uplink grant to a user node in response to an uplink signal.
[0115] At 712, the method may include: in response to uplink authorization, receiving from the user node at least one of an event-based CSI report or one or more non-event-based CSI reports.
[0116] Figure 8 The illustration shows an example of a method for event-based CSI reporting according to another example embodiment. Method 800 can be executed, for example, by a user node.
[0117] At 802, the method may include receiving configuration from a network node for non-event-based channel state information (CSI) reporting and event-based CSI reporting.
[0118] At 804, the method may include: receiving configuration of at least one condition from a network node, the at least one condition being used to trigger an event for event-based CSI reporting.
[0119] At 806, the method may include: receiving configuration of at least one uplink resource from a network node, wherein the at least one uplink resource is associated with an event reported for event-based CSI.
[0120] At 808, the method may include: receiving an indication from a network node to prioritize at least one of the event-based CSI reports or non-event-based CSI reports when at least one of the event-based CSI reports or non-event-based CSI reports is available for transmission in the same time slot. This indication may be included, for example, in a higher-layer configuration or in MAC CE signaling.
[0121] At 810, the method may include: detecting that an event has been triggered based on a measurement performed by the user node.
[0122] At 812, the method may include: using at least one uplink resource to transmit an uplink signal to notify the network node that an event has been triggered.
[0123] At 814, the method may include: receiving an uplink grant from a network node in response to an uplink signal.
[0124] At 816, the method may include: after uplink authorization, transmitting to the network node, based on the received indication, at least one of the following: an event-based CSI report or one or more non-event-based CSI reports that can be transmitted in the same time slot.
[0125] Figure 9 An example of a method for assisting event-based CSI reporting, according to another exemplary embodiment, is illustrated. Method 900 can be performed, for example, by a network node.
[0126] At 902, the method may include transmitting to the user node a configuration for non-event-based channel state information (CSI) reporting and event-based CSI reporting.
[0127] At 904, the method may include: transmitting to a user node the configuration of at least one condition for triggering an event for event-based CSI reporting.
[0128] At 906, the method may include: transmitting to a user node the configuration of at least one uplink resource, wherein the at least one uplink resource is associated with an event reported for event-based CSI.
[0129] At 908, the method may include: transmitting an indication to the user node to prioritize at least one of the event-based CSI reports or non-event-based CSI reports when at least one of event-based CSI reports or non-event-based CSI reports is available for transmission in the same time slot. This indication may be included, for example, in a higher-layer configuration or in MAC CE signaling.
[0130] At 910, the method may include: receiving an uplink signal from a user node via at least one uplink resource indicating that a notification event has been triggered.
[0131] At 912, the method may include: transmitting an uplink grant to the user node in response to an uplink signal.
[0132] At 914, the method may include: in response to uplink authorization, receiving from the user node at least one of an event-based CSI report or one or more non-event-based CSI reports.
[0133] Further features of the method arise directly from the functions and parameters of the apparatus as described in the appended claims and throughout the specification, and therefore will not be repeated here. It should be noted that one or more operations of the method may be performed in different orders.
[0134] Devices (e.g., network nodes or user nodes) may be configured to perform or cause to perform any aspect of the methods(s) described herein. Furthermore, a computer program may include instructions for causing the device to perform any aspect of the methods(s) described herein when executed. Additionally, the device may include components for performing any aspect of the methods(s) described herein. According to an example embodiment, such components include at least one processor and a memory including program code configured to cause any aspect of the methods(s) to be executed when executed by the at least one processor.
[0135] Any ranges or device values given herein may be extended or changed without losing the desired effect. Furthermore, any embodiment may be combined with another embodiment unless expressly permitted.
[0136] Although the subject matter has been described in language specific to structural features and / or actions, it should be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or actions described above. Rather, the specific features and actions described above are disclosed as examples of implementing the claims, and other equivalent features and actions are intended to be within the scope of the claims.
[0137] It will be understood that the above benefits and advantages may relate to one embodiment or several embodiments. The embodiments are not limited to those that solve any or all of the described problems, or those that have any or all of the described benefits and advantages. It will be further understood that reference to "an" may refer to one or more of those items.
[0138] The methods described herein can be performed in any suitable order, or simultaneously where appropriate. Furthermore, individual blocks can be removed from any method without departing from the scope of the subject matter described herein. Aspects of any of the above embodiments can be combined with aspects of any other described embodiments to form further embodiments without losing the desired effects.
[0139] The term “comprising” is used herein to mean including the identified method, box, or element, but such box or element does not include an exclusive list, and the method or apparatus may include additional boxes or elements.
[0140] As used in this application, the term "circuit system" may refer to one or more or all of the following: (a) a hardware circuit implementation only (such as an implementation only in analog and / or digital circuit systems) and (b) a combination of hardware circuitry and software, such as (if applicable): (i) a combination of (multiple) analog and / or digital hardware circuitry with software / firmware; and (ii) any portion of (multiple) hardware processors (including (multiple) digital signal processors), software, and (multiple) memories having software, which work together to enable a device such as a mobile phone or server to perform various functions; and (c) (multiple) hardware circuitry and / or (multiple) processors, such as (multiple) microprocessors or portions thereof, which require software (e.g., firmware) to operate, but may be absent when operation is not required. This definition of circuit system applies to all uses of the term in this application (including in any claim).
[0141] As another example, as used herein, the term "circuit system" also encompasses only hardware circuitry or a processor (or multiple processors) or a portion thereof, and its accompanying software and / or firmware. For instance, if applicable to certain claim elements, the term "circuit system" also encompasses baseband integrated circuits or processor integrated circuits for mobile devices, or similar integrated circuits in servers, cellular network devices, or other computing or network devices.
[0142] It will be understood that the above description is given by way of example only, and various modifications can be made by those skilled in the art. The above specification, examples, and data provide a complete description of the structure and use of exemplary embodiments. Although various embodiments have been described above with a degree of specificity or by reference to one or more individual embodiments, many changes can be made to the disclosed embodiments by those skilled in the art without departing from the scope of this specification.
Claims
1. A user node, comprising: At least one processor; as well as At least one memory, including instructions that, when executed by the at least one processor, cause the user node to at least: Receive configuration from network nodes for non-event-based Channel State Information (CSI) reporting and event-based CSI reporting; Receive configuration of at least one condition from the network node, the at least one condition being used to trigger an event for the event-based CSI reporting; Receive configuration of at least one uplink resource from the network node, wherein the at least one uplink resource is associated with the event reported for the event-based CSI; Receive an indication from the network node, the indication being used to prioritize the at least one of the event-based CSI report or the non-event-based CSI report when at least one of the event-based CSI report or the non-event-based CSI report is available for transmission in the same time slot; Based on the measurement performed by the user node, it is detected that the event has been triggered; The uplink signal is transmitted using the at least one uplink resource to notify the network node that the event has been triggered; Receive uplink grants in response to the uplink signals from the network node; as well as In response to the uplink grant, based on the received instruction, at least one of the following is transmitted to the network node: an event-based CSI report or one or more non-event-based CSI reports that can be transmitted in the same time slot.
2. The user node of claim 1, wherein the indication is received via Media Access Control (MAC) CE signaling or Radio Resource Control (RRC) configuration.
3. The user node according to claim 1 or 2, wherein the uplink signal includes a scheduling request, an uplink reference signal, a probe reference signal, or a non-contention-based physical random access channel preamble.
4. The user node according to any of the preceding claims, wherein the uplink grant is received together with at least one of an information element or a code point field, the information element or the at least one of the code point fields being configured to indicate that the uplink grant is associated with the uplink signal.
5. The user node according to any of the preceding claims, wherein the indicated priority ordering includes: For the transmission, a selection of at least one of the event-based CSI reporting or the one or more non-event-based CSI reporting.
6. The user node according to any one of claims 1 to 5, wherein the at least one memory includes instructions that, when executed by the at least one processor, cause the user node to: Based on the configured priority order, the event-based CSI reports and the one or more non-event-based CSI reports are applied to the same uplink resources.
7. A network node, comprising: At least one processor; as well as At least one memory, including instructions that, when executed by the at least one processor, cause the network node to at least: Transmit the configuration for non-event-based Channel State Information (CSI) reporting and event-based CSI reporting to the user node; The configuration of at least one condition is transmitted to the user node, the at least one condition being used to trigger an event for the event-based CSI reporting; The configuration of at least one uplink resource is transmitted to the user node, wherein the at least one uplink resource is associated with the event reported in response to the event-based CSI. The instruction is transmitted to the user node to prioritize the at least one of the event-based CSI report or the non-event-based CSI report when at least one of the event-based CSI report or the non-event-based CSI report is available for transmission in the same time slot. Receive from the user node an uplink signal notifying that the event has been triggered via the at least one uplink resource; In response to the uplink signal, an uplink authorization is transmitted to the user node; as well as In response to the uplink authorization, the user node receives at least one of the event-based CSI report or one or more non-event-based CSI reports.
8. The network node of claim 7, wherein the indication is transmitted via a Media Access Control (MAC) control element CE signaling or a Radio Resource Control (RRC) configuration.
9. The network node according to claim 7 or 8, wherein the uplink signal includes a scheduling request, an uplink reference signal, a probe reference signal, or a non-contention-based physical random access channel preamble.
10. The network node according to any one of claims 7 to 9, wherein the uplink grant is transmitted together with at least one of an information element or a code point field, the information element or the at least one of the code point fields being configured to indicate that the uplink grant is associated with the uplink signal.
11. The network node according to any one of claims 7 to 10, wherein the indicated priority ordering includes: The selection of the event-based CSI reporting or the one or more non-event-based CSI reporting.
12. The network node according to any one of claims 7 to 10, wherein the event-based CSI reporting and the one or more non-event-based CSI reporting are received on the same uplink resource.
13. A method executed by a user node, comprising: Receive configuration from network nodes for non-event-based Channel State Information (CSI) reporting and event-based CSI reporting; Receive configuration of at least one condition from the network node, the at least one condition being used to trigger an event for the event-based CSI reporting; Receive configuration of at least one uplink resource from the network node, wherein the at least one uplink resource is associated with the event reported for the event-based CSI; Receive an indication from the network node, the indication being used to prioritize the at least one of the event-based CSI report or the non-event-based CSI report when at least one of the event-based CSI report or the non-event-based CSI report is available for transmission in the same time slot; Based on the measurement performed by the user node, it is detected that the event has been triggered; The uplink signal is transmitted using the at least one uplink resource to notify the network node that the event has been triggered; Receive uplink grants in response to the uplink signals from the network node; as well as In response to the uplink grant, based on the received instruction, at least one of the following is transmitted to the network node: an event-based CSI report or one or more non-event-based CSI reports that can be transmitted in the same time slot.
14. A method executed by a network node, comprising: Transmit the configuration for non-event-based Channel State Information (CSI) reporting and event-based CSI reporting to the user node; The configuration of at least one condition is transmitted to the user node, the at least one condition being used to trigger an event for the event-based CSI reporting; The configuration of at least one uplink resource is transmitted to the user node, wherein the at least one uplink resource is associated with the event reported in response to the event-based CSI. The instruction is transmitted to the user node to prioritize the at least one of the event-based CSI report or the non-event-based CSI report when at least one of the event-based CSI report or the non-event-based CSI report is available for transmission in the same time slot. Receive from the user node an uplink signal notifying that the event has been triggered via the at least one uplink resource; In response to the uplink signal, an uplink authorization is transmitted to the user node; as well as In response to the uplink authorization, the user node receives at least one of the event-based CSI report or one or more non-event-based CSI reports.