Beam Information Report

Abstract

A technique for transmitting a beam report is described. An exemplary wireless communication method comprises receiving, by a communication device, a configuration related to a beam report—the configuration indicates one or more trigger events that trigger the communication device to transmit the beam report—; and transmitting the beam report by the communication device in response to the occurrence of a trigger event from one or more trigger events, wherein the beam report is transmitted by the communication device from an uplink resource or from an uplink transmission.

Description

Technology Field

[0001] This document generally relates to digital wireless communication. Background Technology

[0002] Mobile communication technology is transforming the world into an increasingly connected and networked society. Compared to existing wireless networks, next-generation systems and wireless communication technologies will need to support a much wider range of use cases and provide flexibility and access requirements that are more complex and sophisticated.

[0003] LTE (Long-Term Evolution) is a wireless communication standard for mobile devices and data terminals developed by the 3GPP (3rd Generation Partnership Project). LTE-A (LTE Advanced) is a wireless communication standard that enhances the LTE standard. The 5th generation of wireless communication, known as 5G, is dedicated to advancing the LTE and LTE-A wireless standards and supporting higher data rates, multiple connections, ultra-low latency, high reliability, and other new business requirements.

[0004] A technique for transmitting beam information reports in response to the occurrence of a trigger event is disclosed for a device (e.g., user equipment (UE)). Accordingly, the present patent document describes the following exemplary technical solution: a configuration that enables the device (e.g., UE) to perform a beam report; transmission by the device (e.g., UE) in the type of a medium access control-control element (MAC-CE) or uplink control information (UCI); and transmission of the beam report by the device (e.g., UE) in an uplink resource selected from a plurality of uplink resources within a time duration or an uplink resource configured by a network (e.g., base station).

[0005] A first exemplary wireless communication method comprises receiving, by a communication device, a configuration related to a beam report—the configuration indicates one or more trigger events that trigger the communication device to transmit the beam report—; and transmitting the beam report by the communication device in response to the occurrence of a trigger event from one or more trigger events, wherein the beam report is transmitted by the communication device from an uplink resource or from an uplink transmission.

[0006] In some embodiments, the uplink resource or uplink transmit is based on a Type 1 or Type 2 configured grant physical uplink shared channel (PUSCH) transmit configured with a configuration related to beam reporting. In some embodiments, the uplink resource or uplink transmit is based on a Type 1 or Type 2 configured grant physical uplink shared channel (PUSCH) transmit configured to multiplex beam reporting for a corresponding PUSCH transmit. In some embodiments, the uplink resource is a physical uplink control channel (PUCCH) resource configured for beam reporting. In some embodiments, the uplink resource or uplink transmit is based on a physical uplink shared channel (PUSCH) transmit determined based on a PUSCH transmit parameter configuration of a beam reporting-only configuration.

[0007] In some embodiments, the uplink resource or uplink transmission is based on a physical uplink shared channel (PUSCH) transmission determined based on a rule, and the rule specifying the PUSCH transmission parameters for the PUSCH transmission is based on the PUSCH transmission parameters indicated by the PDCCH that schedules a second PUSCH transmission separate from the PUSCH transmission. In some embodiments, the uplink resource or uplink transmission is one of one or more uplink resources or a plurality of uplink transmissions, and the plurality of uplink resources or a plurality of uplink transmissions are transmitted by the communication device within a transmission window. In some embodiments, a plurality of uplink resources or a plurality of uplink transmits comprises at least one of the following: a physical uplink control channel (PUCCH) indicated by a physical downlink control channel (PDCCH) to transmit within a transmit window; a physical uplink shared channel (PUSCH) scheduled by the PDCCH to transmit within a transmit window; a PUCCH resource carrying periodic channel state information (CSI) or semi-persistent CSI reporting; a PUSCH having a Type 1 configuration grant; or a PUSCH having a Type 2 configuration grant enabled by a PDCCH having a Type 2 configuration grant.

[0008] In some embodiments, the communication device performs rate matching to transmit or multiplex beam reports in a physical uplink shared channel (PUSCH) transmission based on a configured beta offset value. In some embodiments, the configuration for beam reporting includes: a first configuration for channel state information (CSI) reporting—the first configuration indicates one or more trigger events associated with CSI reporting—a second configuration for beam reporting indicating at least one of one or more trigger events, a reporting configuration identifier, a reference signal for measurement, or an indicator of reporting indicating content for beam reporting, or at least one configuration for CSI reporting including a reporting configuration type set to 'event triggered'. In some embodiments, the communication device transmits the beam report using a type of media access control—control element (MAC CE) or uplink control information (UCI).

[0009] In some embodiments, a beam report is transmitted using a MAC CE comprising at least one of a beam report presence indicator, a cell indicator, a reference signal resource indicator, a report indicator indicating the content of the beam report, or an identifier of a trigger event. In some embodiments, a beam report is transmitted using a MAC CE associated with only one beam report, or a beam report is transmitted using a MAC CE associated with one beam report indicator associated with a reference signal. In some embodiments, a beam report is transmitted using a MAC CE associated with one or more beam reports, or a beam report is transmitted using a MAC CE associated with one or more report indicators associated with one or more reference signals.

[0010] In some embodiments, a configuration related to beam reporting comprises a reporting indicator that indicates the content for beam reporting, wherein at least one of the following is configured: reference signal receive power (RSRP) corresponds to a synchronization signal block (SSB) resource indicator, RSRP corresponds to a channel state information reference signal resource indicator (CRI), signal-to-noise and interference ratio (SINR) corresponds to an SSB index, or SINR corresponds to CRI. In some embodiments, a communication device receives a second configuration related to a beam reporting indicator message, and the communication device transmits a beam reporting indicator message to a network device based on the second configuration in response to a trigger event of at least one beam reporting, and the beam reporting indicator message indicates to the network device that at least one report is triggered by an event corresponding to at least one beam reporting.

[0011] In some embodiments, a second configuration related to the beam report indication message includes a scheduling request configuration index or a physical uplink control channel (PUSCH) resource index. In some embodiments, the time or transmission window for transmitting the beam report is based on the transmission time of the beam report indication message. In some embodiments, the time or transmission window for transmitting the beam report starts or ends X milliseconds after the beam report indication message is transmitted, and the value of X is the physical uplink shared channel (PUSCH) ready time, a set value, or a predefined value. In some embodiments, the time or transmission window for transmitting the beam starts or ends at a symbol Y symbols after the end symbol of the beam report indication message, and the value of Y is configured or predefined. In some embodiments, the time or transmission window for transmitting the beam report starts or ends at a slot Z slots after another slot in which the beam report indication message is transmitted, and the value of Z is configured or predefined.

[0012] A second exemplary wireless communication method comprises transmitting a configuration associated with a beam report by a network device—the configuration indicates one or more trigger events that trigger the communication device to transmit the beam report—; and receiving a beam report from the communication device by the network device in response to the occurrence of a trigger event from one or more trigger events, wherein the beam report is received from an uplink resource or an uplink transmission.

[0013] In some embodiments, the uplink resource or uplink transmit is based on a Type 1 or Type 2 configured grant physical uplink shared channel (PUSCH) transmit configured with a configuration related to beam reporting. In some embodiments, the uplink resource or uplink transmit is based on a Type 1 or Type 2 configured grant physical uplink shared channel (PUSCH) transmit configured to multiplex beam reporting for a corresponding PUSCH transmit. In some embodiments, the uplink resource is a physical uplink control channel (PUCCH) resource configured for beam reporting. In some embodiments, the uplink resource or uplink transmit is based on a physical uplink shared channel (PUSCH) transmit determined based on a PUSCH transmit parameter configuration of a beam reporting-only configuration.

[0014] In some embodiments, the uplink resource or uplink transmission is based on a physical uplink shared channel (PUSCH) transmission determined based on a rule, and the rule specifying the PUSCH transmission parameters for the PUSCH transmission is based on the PUSCH transmission parameters indicated by the PDCCH that schedules a second PUSCH transmission separate from the PUSCH transmission. In some embodiments, the uplink resource or uplink transmission is one or more uplink resources or one of a plurality of uplink transmissions, and the plurality of uplink resources or the plurality of uplink transmissions are transmitted within a transmission window. In some embodiments, a plurality of uplink resources or a plurality of uplink transmits comprises at least one of the following: a physical uplink control channel (PUCCH) indicated by a physical downlink control channel (PDCCH) to transmit within a transmit window; a physical uplink shared channel (PUSCH) scheduled by the PDCCH to transmit within a transmit window; a PUCCH resource carrying periodic channel state information (CSI) or semi-persistent CSI reporting; a PUSCH having a Type 1 configuration grant; or a PUSCH having a Type 2 configuration grant enabled by a PDCCH having a Type 2 configuration grant.

[0015] In some embodiments, a configuration for beam reporting comprises: a first configuration for channel state information (CSI) reporting—the first configuration indicates one or more trigger events associated with CSI reporting—a second configuration for beam reporting indicating at least one of one or more trigger events, a reporting configuration identifier, a reference signal for measurement, or an indicator of reporting indicating content for beam reporting, or at least one of a third configuration for CSI reporting including a reporting configuration type set to 'event triggered'. In some embodiments, the communication device transmits the beam report using a type of media access control—control element (MAC CE) or uplink control information (UCI).

[0016] In some embodiments, a beam report is received using a MAC CE comprising at least one of a beam report presence indicator, a cell indicator, a reference signal resource indicator, a report indicator indicating the content of the beam report, or an identifier of a trigger event. In some embodiments, a beam report is received using a MAC CE associated with only one beam report, or a beam report is received using a MAC CE associated with one beam report indicator associated with a reference signal. In some embodiments, a beam report is received using a MAC CE associated with one or more beam reports, or a beam report is received using a MAC CE associated with one or more report indicators associated with one or more reference signals. In some embodiments, a configuration associated with a beam report comprises a report indicator indicating the content for the beam report, wherein at least one of the following is configured: the reference signal received power (RSRP) corresponds to the synchronization signal block (SSB) resource indicator, the RSRP corresponds to the channel state information reference signal resource indicator (CRI), the signal-to-noise and interference ratio (SINR) corresponds to the SSB index, or the SINR corresponds to the CRI.

[0017] In some embodiments, a network device receives a second configuration associated with a beam report indication message, and the network device receives a beam report indication message from a communication device based on the second configuration in response to a trigger event of at least one beam report, and the beam report indication message indicates to the network device that at least one report is triggered by an event corresponding to at least one beam report. In some embodiments, the second configuration associated with the beam report indication message includes a scheduling request configuration index or a physical uplink control channel (PUCCH) resource index. In some embodiments, the time or transmission window for transmitting the beam report is based on the time of reception of the beam report indication message. In some embodiments, the time or transmission window for receiving the beam report starts or ends X milliseconds after the beam report indication message is transmitted, and the value of X is the physical uplink shared channel (PUSCH) ready time, a set value, or a predefined value.

[0018] In some embodiments, the time or transmission window for receiving a beam starts or ends at a symbol Y symbols after the end symbol of the beam report indication message, and the value of Y is configured or pre-defined. In some embodiments, the time or transmission window for receiving a beam report starts or ends at a slot Z slots after another slot in which the beam report indication message was transmitted, and the value of Z is configured or pre-defined.

[0019] In another exemplary embodiment, the method described above is implemented in the form of processor executable code and stored in a non-transient computer-readable storage medium. When executed by a processor, the code contained in the computer-readable storage medium enables the processor to implement the method described in this patent document.

[0020] In another exemplary embodiment, a device configured or operable to perform the method described above is disclosed.

[0021] The above embodiments and other embodiments and their implementations are described in more detail in the drawings, description, and claims. Brief explanation of the drawing

[0022] Figure 1 illustrates an exemplary beam reporting MAC CE having one report. FIG. 2 illustrates an exemplary beam reporting MAC CE having multiple reports. FIGS. 3 to 5 illustrate exemplary flowcharts or communication devices for transmitting beam reports. FIG. 6 illustrates an example of available uplink resources that can be used to carry beam reports within a beam report transmission window. FIG. 7 illustrates an exemplary block diagram of a hardware platform that may be part of a network device or a communication device. FIG. 8 illustrates an example of wireless communication including a base station (BS) and user equipment (UE) based on some embodiments of the disclosed technology. Figure 9 illustrates an exemplary flowchart for transmitting a beam report. Figure 10 illustrates an exemplary flowchart for receiving beam reports. Specific details for implementing the invention

[0023] In current NR systems, Channel State Information (CSI) reporting can assist the network in providing better transmit configuration to the UE. CSI reporting can be configured acyclic, semi-persistent, or cyclic. For acyclic CSI (AP-CSI) reporting triggering, a single set of CSI triggering states is configured for a higher layer. The UE may receive a DCI format to enable CSI trigger states or CSI reporting. For semi-persistent CSI (SP-CSI) reporting over PUSCH, the set of trigger states is configured by a higher layer, where the CSI request field of the DCI scrambled by SP-CSI-RNTI activates one of the trigger states. For semi-persistent reporting over the Physical Uplink Control Channel (PUCCH), the PUCCH resources used to transmit CSI reporting are configured by RRC signaling. Semi-persistent reporting for PUCCH is enabled by an enable command that selects one of the semi-persistent reporting settings to be used by the UE on PUCCH. For periodic CSI reporting, the reporting periodicity, slot offset, and PUCCH resource for reporting are configured.

[0024] The UE may be configured to include one or more of the following reporting indicators for CSI reporting: Channel quality indicator (CQI), Precoding matrix indicator (PMI), rank indicator (RI), CSI-RS Resource Indicator (CRI), Synchronization signal block resource indicator (SSBRI), Signal-to-Noise and Interference Ratio (SINR), or Reference Signal Received Power (RSRP). The reporting indicators may indicate what is reported to the UE (e.g., the reporting indicators indicate whether the report includes CQI, PMI, RI, CRI, SSBRI, SINR, and / or RSRP). The UE calculates the corresponding CSI parameters based on the configured reporting indicators and the corresponding CSI resources for measurement.

[0025] Measurement reporting is intended to transmit measurement results from the UE to the network. The UE must initiate measurement reporting only after successful Access Stratum (AS) security activation. Measurement reporting is performed by a higher layer of the UE (e.g., Layer 3), and multiple events triggering the measurement report can be configured for the reporting configuration. Triggering events are primarily related to higher-layer parameters, such as serving cell or proximity cell measurement results, interference measurement results, channel usage rates, or UE location. The signaling radio bearers for the measurement report are SRB1 and SRB3, and the logical channel is the Dedicated Control Channel (DCCH).

[0026] A Scheduling Request (SR) is used to request UL-SCH resources for a new transmission. A MAC entity can be composed of zero or one or more SR configurations. An SR configuration consists of a set of PUCCHs for SRs across different BWPs and cells. An SR configuration of a logical channel that triggered a buffer status report or SCell beam failure recovery, or a beam failure recovery of a BFD-RS set, or a consistent LBT failure recovery, or a positioning measurement gap enable / disable request is considered as the corresponding SR configuration for the triggered SR.

[0027] Uplink control information (UCI) types include HARQ-ACK information, scheduling request (SR), link recovery request (LRR), and CSI. UCI bits include HARQ-ACK information bits if present, SR information bits if present, LRR information bits if present, and CSI bits if present. Generally, SR is applicable to the SR and / or LRR of NR systems.

[0028] The exemplary headings for the various sections below are used to facilitate understanding of the disclosed subject matter and do not limit the claimed subject matter in any way. Accordingly, one or more features of one exemplary section may be combined with one or more features of another exemplary section. Additionally, while the term 5G is used for clarity of description, the techniques disclosed in this document are not limited to 5G technology and may be used in wireless systems implementing other protocols.

[0029] I. Introduction

[0030] Beam information reporting is based on current CSI reporting, and the reporting type in the time domain behavior can be configured as periodic, semi-permanent, or non-periodic. In such a method, the UE will report all information associated with the reference signal configured for CSI reporting, which causes significant reporting overhead. Meanwhile, particularly in semi-permanent and periodic CSI reporting, the reporting latency for CSI reporting is also high, because the UE must perform CSI reporting based on the reporting period rather than flexible reporting timing.

[0031] This patent document describes a beam information reporting method that is triggered by an event, that is, allows the UE to report beam information only when a configured event occurs. In such a method, the UE does not need to report information on all configured reference signals, so reporting overhead is reduced. Additionally, the UE is allowed to perform beam reporting when an event is triggered, and since the DCI does not enable reporting, reporting latency is also reduced.

[0032] In this patent document, the following exemplary techniques or exemplary embodiments are described.

[0033] (1) A configuration that enables the UE to perform beam reporting triggered by an event

[0034] (2) The container and contents of the beam report, such as the beam report, may include a Media Access Control-Control Element (MAC CE), a CSI report, or a new type of UCI.

[0035] (3) A beam report indication message (optional) may be sent by the UE before sending a beam report, and the beam report indication message is used to indicate to the network that a beam report has been triggered or that the UE has requested to send a beam report.

[0036] (4) When a beam report indication message is transmitted, the time duration (also known as the time window) for the UE to transmit the beam report is specified. The network may recognize the timing of the beam report based on the time duration and the previous beam report indication message.

[0037] (5) The UE determines an uplink transmission or uplink resource to carry the generated beam report, and the uplink transmission may be an uplink transmission configured, scheduled, and indicated by the network to be transmitted by the UE, or an uplink transmission dedicated to carrying the beam report.

[0038] II. Exemplary Solutions

[0039] FIG. 1 illustrates an exemplary beam reporting MAC CE having a single report. In the example of FIG. 1, the beam reporting MAC CE includes a serving cell index, a reference signal index for beam reporting, and a field displaying the reporting indicator of the beam reporting.

[0040] FIG. 2 illustrates an exemplary beam reporting MAC CE having multiple reports. In the example of FIG. 2, the variable-size beam reporting MAC CE includes fields indicating the presence of a beam report in a serving cell, a reference signal (RS) index for the beam report, and a reporting indicator of the beam report. If the field indicates that a beam report corresponding to a serving cell exists (SP, C1, C2, ..., C7 correspond to SpCell, serving cell index 1, serving cell index 2, ..., serving cell index 7, respectively), the RS ID and reporting indicator fields for the corresponding serving cell exist in the MAC CE, and if not, the field is absent.

[0041] FIGS. 3 through 5 illustrate exemplary flowcharts or communication devices for transmitting beam reports. In the example of FIG. 3, an event triggering a beam report may occur upon measurement of a reference signal for the beam report. When the event is triggered, the UE generates a beam report (e.g., MAC CE or UCI) and transmits the beam report from an uplink resource.

[0042] In the example of FIG. 4, the event triggering the beam report may occur based on the measurement of a reference signal for the beam report. When the event is triggered, the UE first performs the transmission of a beam report indication message to the network, then generates a beam report (e.g., MAC UE or UCI), and transmits the beam report to the network from the uplink resource.

[0043] In the example of FIG. 5, the UE determines the uplink resource to carry the generated beam report based on available uplink resources or dedicated uplink resources.

[0044] FIG. 6 illustrates examples of available uplink resources that can be used to carry beam reports within a beam report transmission window. In FIG. 6, available uplink resources may include, for example, a PUCCH scheduled by a PDCCH, a PUSCH scheduled by a PDCCH, a periodic CSI (P-CSI), and a PUCCH configured to carry an enabled Type 2 configuration grant PUSCH.

[0045] In the present patent document, a beam report may be equivalent to or identical to a beam report triggered by a UE, a beam report triggered by an event, or a Channel State Information (CSI) report triggered by an event. In the present patent document, RSRP may include L1-RSRP, and SINR may include an L1-SINR value. A cell may include a serving cell, a physical cell, a TRP, a CORESET pool, a candidate cell, a neighbor cell, a node, or an access point.

[0046] Each of the embodiments described below may transmit beam reports using the features and / or techniques described in Section II.

[0047] II.a. First embodiment

[0048] A first embodiment describes a UE that receives a configuration of beam reporting that indicates or enables the UE to perform beam reporting triggered by one or more trigger events.

[0049] A beam report is triggered when any one of the configured events occurs, depending on the measurement result of the corresponding reference signal for the beam report. The trigger event may specify conditions related to the measurement result of the reference signal and / or threshold (e.g., an inequality related to the measurement result and the threshold). If the measurement result of the reference signal satisfies the condition, this is considered as the occurrence of a trigger event associated with the reference signal. In the example, the occurrence of a trigger event is defined as the satisfaction of the condition defined as Measurement result + ConfigPara > Threshold, where ConfigPara and Threshold can be configured for the corresponding event, and if the measurement result of the reference signal satisfies the condition, the event is triggered.

[0050] In some embodiments, the UE performs beam reporting based on a trigger event and a reference signal measurement when the UE receives at least one of the following configurations from the network:

[0051] (1) Configuration for CSI reporting, the configuration displays one or more trigger events.

[0052] (2) A configuration for beam reporting triggered by an event, the configuration displays at least one of the trigger event, the reporting configuration identifier, the reference signal for measurement, or the reporting indicator for beam reporting.

[0053] (3) Configuration for CSI reporting, the reporting configuration type is configured as 'Event triggered'.

[0054] In some embodiments, the configuration of the beam indicates a priority for beam reporting or a priority for triggers associated with beam reporting. The priority of beam reporting is determined based on the priority for beam reporting or the priority for events triggering beam reporting.

[0055] II.b. Second Example

[0056] A second embodiment specifies a UE that transmits a beam report using a MAC CE or uplink control information type.

[0057] In some embodiments, the beam report includes a MAC CE, and at least one of a beam report presence indicator indicating the presence of the beam report, an indicator (e.g., a candidate cell index, a serving cell index, or a physical cell index), a reference signal resource indicator (e.g., an SSB resource index or a CSI resource index), a reporting metric, or an identifier of a trigger event is displayed.

[0058] In some embodiments, the MAC CE is associated with only one beam report. In some embodiments, the MAC CE includes one report indicator field associated with a reference signal.

[0059] In some embodiments, the MAC CE is associated with more than one beam report. In some embodiments, the MAC CE includes more than one report indicator field associated with more than one reference signal.

[0060] In some embodiments, when the presence indication of a beam report indicates that the corresponding beam report was not triggered (e.g., set to 0), an octet containing fields for a reference signal index, a report indicator, or a trigger event identifier is absent within the MAC CE.

[0061] In some embodiments, the beam report includes a channel state information (CSI) report. The beam report may be transmitted in the Part 1 CSI report, or in the Part 1 and Part 2 CSI reports.

[0062] In some embodiments, the beam report includes a novel type of uplink control information (e.g., uplink control information-beam report; UCI-BR).

[0063] In the aforementioned embodiment, the reporting indicators for beam reporting may be configured by a network, and the network comprises at least one of: an RSRP corresponding to an SSB resource, an RSRP corresponding to a CSI-RS resource, a SINR corresponding to an SSB resource, or a SINR corresponding to a CSI-RS.

[0064] In some embodiments, RSRP or SINR may be an absolute value, a range of absolute values, a different value, or a range of different values.

[0065] In one example, the reported RSRP is -50 dB.

[0066] In one example, the reported RSRP is mapped to a range of [-50, -40) dB.

[0067] In one example, the reported RSRP differs by -5 dB from the reference RSRP value.

[0068] In one example, the reported RSRP is mapped to a range different from the reference RSRP value by [+5, -5) dB. The reference RSRP value can be associated with the reference signal of the serving cell.

[0069] In some embodiments, the network configures reporting metrics based on UE performance.

[0070] In the example, the UE reports that the performance of the supported reporting metrics for RSRP and SINR corresponds to the SSB index, and the network is configured so that the reporting metric to the UE is SSB-index-RSRP or SSB-index-SINR.

[0071] II.c. Third Example

[0072] A third embodiment specifies a UE that transmits a beam report indication message to a network before transmitting a beam report, and a UE that transmits a beam report within a time duration (also known as a time window) after the UE transmits the beam report indication message.

[0073] In some embodiments, the UE receives a configuration of a beam report indication message, and the beam report indication message indicates that at least one beam report is sent to the network by the UE and is triggered by the corresponding event(s), or that at least one beam report is requested by the UE and is to be sent after the beam report indication message is sent. The configuration of the beam report indication message configures the UE as an uplink resource for the beam report indication message (e.g., a PUCCH resource index or a scheduling request configuration index).

[0074] The configuration of the Beam report display message displays the scheduling request configuration index or the PUCCH resource index.

[0075] In the example, the UE can be configured by schedulingRequestID-BeamReport, which is a scheduling request configuration used by the UE when triggering a beam report.

[0076] In the example, the UE can be configured by a PUCCH-BeamReportIndication-Resource, which is a PUCCH resource having PUCCH format 0 or PUCCH format 1.

[0077] In each logical channel, SCell beam failure recovery, BFD-RS set beam failure recovery, and consistent LBT failure recovery, beam reporting triggered by events can be mapped to 0 or one SR configuration.

[0078] In some embodiments, the UE determines a time duration for a beam report (hereinafter referred to as the beam report transmission window) after the UE transmits a beam report indication message, and the time duration is determined based on at least one of the following:

[0079] (1) The time duration starts or ends at X milliseconds after the beam report display message, and the value of X may be determined according to (or based on) at least one of the PUSCH preparation time, a configured value, or a predefined value. In some embodiments, the value of X may be the PUSCH preparation time, a configured value, or a predefined value.

[0080] (2) The time duration starts or ends at a symbol that is after the end symbol of the beam report display message, and the Y value can be configured or pre-defined.

[0081] (3) The time duration may start or end in a slot that is Z slot after the slot in which the beam report indication message was transmitted, and the Z value may be configured or predefined (e.g., 0, 1, 2, etc.).

[0082] Time duration is used to specify the UE to transmit beam reports within the time duration, or to transmit beam reports no later than the end of the time duration.

[0083] II.d. 4th Example

[0084] A fourth embodiment specifies a UE that transmits a beam report triggered by a trigger event in an uplink resource or uplink transmission.

[0085] Example Scheme-A:

[0086] In some embodiments, the uplink resource or uplink transmission for carrying / multiplexing beam reports is determined based on at least one of the following:

[0087] (1) A Type 1 or Type 2 configured grant PUSCH transmission configured with a beam report or CSI report configuration. In one example, the identifier of the configured grant PUSCH transmission (e.g., ConfiguredGrantConfigIndex) is displayed in the beam report configuration or CSI report configuration.

[0088] (2) A Type 1 or Type 2 configured grant PUSCH transmission is configured to multiplex beam reports for the corresponding PUSCH transmission. In one example, a CSI report ID or a UE-triggered beam report ID may be indicated in the configuration of the PUSCH transmission with the configured grant. In another example, an enable indicator may be indicated in the configuration of the PUSCH transmission with the configured grant. If the field is present or is set to enable, the UE multiplexes the UCI-BR for the PUSCH transmission to the configured grant.

[0089] (3) PUCCH resources configured for Beam reporting. In one example, one or more PUCCH resources may be configured for Beam reporting.

[0090] (4) A PUSCH transmission determined based on a beam reporting-only PUSCH transmission configuration, the configuration comprises at least one of the following PUSCH transmission parameters: frequency hopping type, modulation and coding scheme (MCS), frequency domain resource assignment (FDRA), time domain resource assignment (TDRA), antenna port, SRS resource, transmit precoding or transmit layer.

[0091] (5) PUSCH transmission determined based on rules, rules, the TDRA for PUSCH transmission is based on the first element in the PUSCH TDRA list; the PUSCH transmission parameters for PUSCH transmission are based on the PUSCH transmission parameters indicated by the most recently received PDCCH that schedules the PUSCH transmission prior to the beam report indication message transmission; the PUSCH transmission parameters for PUSCH transmission are based on the PUSCH transmission parameters for another PUSCH transmission recently transmitted by the UE prior to the beam report indication message transmission.

[0092] (6) PUSCH transmission is scheduled by PDCCH to multiplex beam reports.

[0093] In some embodiments, a PDCCH that schedules a PUSCH transmission to multiplex beam reports is received after the UE transmits a beam report indication message, and the beam report indication message is associated with the beam report.

[0094] In some embodiments, PDCCH displays at least one of a trigger status, a report configuration index, or a non-zero CSI request associated with a beam report.

[0095] In some embodiments, the indication field of the PDCCH indicates that the scheduled PUSCH transmission will multiplex beam reports. In one example, the indication field indicates a value of 1 or a non-zero value, and the UE multiplexes or transmits beam reports in the PUSCH transmission scheduled by the PDCCH.

[0096] In some embodiments, the UE does not expect non-zero values ​​to be displayed for both the CSI request field and the display field in the PDCCH.

[0097] In some embodiments, the PUSCH transmission configuration dedicated to beam reporting displays the identifier of the PUSCH TDRA in the PUSCH TDRA list, where the identifier value 0 refers to the first PUSCH TDRA in the list, the value 1 refers to the second PUSCH TDRA in the list, and so on.

[0098] In some embodiments, when the UE transmits a beam report in a Type-2 configuration grant PUSCH transmission without receiving a PDCCH that enables the Type-2 configuration grant, the UE disables or releases the Type-2 configuration grant when it receives an indication from the PDCCH indicating the disablement of the configuration grant (e.g., an indication field of the PDCCH scrambled with the configuration scheduling RNTI (CS-RNTI) indicates to disable the configuration grant).

[0099] In some embodiments, when the UE transmits a beam report in a Type-2 setting grant PUSCH transmission without receiving a PDCCH that activates the Type-2 setting grant, the UE sets a field indicating whether the activation or deactivation of the corresponding setting grant has been received, or a field indicating whether the corresponding setting grant has been activated by the UE in the setting grant verification MAC CE to 1, i.e., the field indicates that the activation or deactivation of the setting grant has been received, or that the setting grant has been activated by the UE without receiving the activation.

[0100] In some embodiments, after the UE transmits a beam report in a Type-2 configuration grant PUSCH transmission without receiving a PDCCH that enables the Type-2 configuration grant, the UE disables the Type-2 configuration grant PUSCH without receiving a PDCCH that disables the Type-2 configuration grant.

[0101] In some embodiments, the UE is configured with a transmission cycle of uplink resources for beam reporting, and the UE transmits uplink resources in a slot or frame based on the transmission cycle.

[0102] In some embodiments, the UE determines whether to transmit an uplink resource in a slot or frame based on whether a beam report has been transmitted or multiplexed from the uplink resource. In one example, if the UE does not multiplex the beam from the uplink resource (e.g., due to overlapping handling or because no beam report was generated), the UE does not transmit the uplink resource in a slot or frame determined based on the transmission cycle.

[0103] Example Scheme-B:

[0104] In some embodiments, the uplink resource or uplink transmission carrying the beam report is determined to be one of a plurality of uplink resources or a plurality of uplink transmissions within a beam report transmission window, and the uplink resource or uplink transmission determined for the beam report includes at least one of the following:

[0105] (1) PUCCH indicated by PDCCH (e.g., by the PDSCH-to-HARQ_feedback timing indicator field) to be transmitted within the beam report transmission window;

[0106] (2) A PUSCH scheduled by PDCCH to transmit within the beam report transmission window;

[0107] (3) PUCCH resources carrying periodic CSI reports or semi-permanent CSI reports;

[0108] (4) PUSCH having a Type 1 configuration grant;

[0109] (5) PUSCH with Type 2 configuration grants enabled by PDCCH..

[0110] In some embodiments, a plurality of uplink resources for beam reporting or the reception time of a PDCCH associated with an uplink transmission satisfies at least one of the following conditions:

[0111] (1) PDCCH is received from the start symbol or start slot of the time duration prior to the PUSCH preparation time for the UE performance.

[0112] (2) PDCCH is received before or after the beam report display message associated with the beam report.

[0113] In some embodiments, one of a plurality of uplink resources or uplink transmissions determined to carry a beam report is determined based on at least one of the following:

[0114] (1) Uplink transmission starts at the earliest symbol among multiple uplink transmissions;

[0115] (2) Uplink transmission is terminated at the latest symbol among multiple uplink transmissions;

[0116] (3) Uplink transmission having the same priority as the beam report;

[0117] (4) Uplink transmission with higher priority;

[0118] (5) Uplink transmission capable of carrying a beam report, for example, having bits available for beam reporting or resource elements available for beam reporting;

[0119] (6) Uplink transmission having a transmission block;

[0120] (7) Uplink transmission carrying a specific type of UCI, e.g., HARQ-ACK, SR, or CSI Part 1;

[0121] (8) Uplink transmission with or without repetition.

[0122] In some embodiments, if the upper layer does not deliver a transport block to be transmitted on a resource allocated for a grant-free uplink transmission, and if the beam report is not transmitted or multiplexed when the UE receives the configuration of the beam report, the UE must not transmit anything on the resource configured by configuredGrantConfig.

[0123] In some embodiments, when there are no uplink resources available for beam reporting (e.g., scheme-B) within the beam reporting transmission window, the UE determines uplink transmission for beam reporting based on scheme-A.

[0124] In some embodiments, the UE determines uplink transmission for beam reporting based on Example Scheme-A or Example Scheme-B, depending on the configuration and UE performance.

[0125] In some embodiments, the UE performs rate matching for transmitting or multiplexing beam reporting of a PUSCH transmission based on a beta offset value, and the beta offset value may be configured for CSI part 1, CSI part 2, or UCI for beam reporting in a PUSCH configuration (e.g., PUSCH-Config) or a configured grant (e.g., ConfiguredGrantConfig) configuration.

[0126] FIG. 7 illustrates an exemplary block diagram of a hardware platform (700) that may be part of a network device (e.g., a base station) or a communication device (e.g., a user device (UE)). The hardware platform (700) includes at least one processor (710) in which instructions are stored and a memory (705). When executed by the processor (710), the instructions configure the hardware platform (700) to perform the operations described in FIG. 1 through 6 and FIG. 8 through 10 and in various embodiments described in this patent document. A transmitter (715) transmits or sends information or data to another device. For example, a network device transmitter may transmit a message to a user device. A receiver (720) receives information or data transmitted or sent by another device. For example, a user device may receive a message from a network device.

[0127] The aforementioned implementation will be applied to wireless communication. FIG. 8 illustrates an example of a wireless communication system (e.g., a 5G or NR cellular network) comprising a base station (820) and one or more user equipment (UE) (811, 812, and 813). In some embodiments, the UE accesses a BS (e.g., a network) using a communication link to the network (also referred to as the uplink direction and illustrated as dashed arrows (831, 832, 833)), which subsequently enables subsequent communication from the BS to the UE (e.g., illustrated as the direction from the network to the UE, also referred to as the downlink direction and illustrated by arrows (841, 842, 843)). In some embodiments, the BS transmits information to the UE (sometimes referred to as the downlink direction, as indicated by arrows (841, 842, 843)), which subsequently enables subsequent communication from the UE to the BS (e.g., shown in the direction from the UE to the BS, sometimes referred to as the uplink direction, as indicated by dashed arrows (831, 832, 833)). The UE may be, for example, a smartphone, tablet, mobile computer, machine-to-machine (M2M) device, Internet of Things (IoT) device, etc.

[0128] FIG. 9 illustrates an exemplary flowchart for transmitting a beam report. An operation (902) includes receiving a configuration related to a beam report by a communication device, wherein the configuration indicates one or more trigger events that trigger the communication device to transmit the beam report. An operation (904) includes transmitting a beam report by the communication device in response to the occurrence of a trigger event from one or more trigger events, wherein the beam report is transmitted by the communication device from an uplink resource or from an uplink transmission.

[0129] In some embodiments, the uplink resource or uplink transmit is based on a Type 1 or Type 2 configured grant physical uplink shared channel (PUSCH) transmit configured with a configuration related to beam reporting. In some embodiments, the uplink resource or uplink transmit is based on a Type 1 or Type 2 configured grant physical uplink shared channel (PUSCH) transmit configured to multiplex beam reporting for a corresponding PUSCH transmit. In some embodiments, the uplink resource is a physical uplink control channel (PUCCH) resource configured for beam reporting. In some embodiments, the uplink resource or uplink transmit is based on a physical uplink shared channel (PUSCH) transmit determined based on a PUSCH transmit parameter configuration of a beam reporting-only configuration.

[0130] In some embodiments, the uplink resource or uplink transmission is based on a physical uplink shared channel (PUSCH) transmission determined based on a rule, and the rule specifying the PUSCH transmission parameters for the PUSCH transmission is based on the PUSCH transmission parameters indicated by the PDCCH that schedules a second PUSCH transmission separate from the PUSCH transmission. In some embodiments, the uplink resource or uplink transmission is one of one or more uplink resources or a plurality of uplink transmissions, and the plurality of uplink resources or a plurality of uplink transmissions are transmitted by the communication device within a transmission window. In some embodiments, a plurality of uplink resources or a plurality of uplink transmits comprises at least one of the following: a physical uplink control channel (PUCCH) indicated by a physical downlink control channel (PDCCH) to transmit within a transmit window; a physical uplink shared channel (PUSCH) scheduled by the PDCCH to transmit within a transmit window; a PUCCH resource carrying periodic channel state information (CSI) or semi-persistent CSI reporting; a PUSCH having a Type 1 configuration grant; or a PUSCH having a Type 2 configuration grant enabled by a PDCCH having a Type 2 configuration grant.

[0131] In some embodiments, the communication device performs rate matching to transmit or multiplex beam reports in a physical uplink shared channel (PUSCH) transmission based on a configured beta offset value. In some embodiments, a configuration for beam reporting includes: a first configuration for channel state information (CSI) reporting—the first configuration indicates one or more triggers associated with CSI reporting—a second configuration for beam reporting indicating at least one of one or more trigger events, a reporting configuration identifier, a reference signal for measurement, or an indicator of reporting indicating content for beam reporting, or at least one configuration for CSI reporting including a reporting configuration type set to 'event triggered'. In some embodiments, the communication device transmits beam reports using a type of media access control—control element (MAC CE) or uplink control information (UCI).

[0132] In some embodiments, a beam report is transmitted using a MAC CE comprising at least one of a beam report presence indicator, a cell indicator, a reference signal resource indicator, a report indicator indicating the content of the beam report, or an identifier of a trigger event. In some embodiments, a beam report is transmitted using a MAC CE associated with only one beam report, or a beam report is transmitted using a MAC CE associated with one beam report indicator associated with a reference signal. In some embodiments, a beam report is transmitted using a MAC CE associated with one or more beam reports, or a beam report is transmitted using a MAC CE associated with one or more report indicators associated with one or more reference signals.

[0133] In some embodiments, a configuration related to beam reporting comprises a reporting indicator that indicates the content for beam reporting, wherein at least one of the following is configured: Reference Signal Received Power (RSRP) corresponds to a Synchronization Signal Block (SSB) resource indicator, RSRP corresponds to a Channel State Information Reference Signal Resource Indicator (CRI), Signal-to-Noise and Interference Ratio (SINR) corresponds to an SSB index, or SINR corresponds to CRI. In some embodiments, a communication device receives a second configuration related to a beam reporting indication message, and the communication device transmits a beam reporting indication message to a network device based on the second configuration in response to a trigger event of at least one beam reporting, and the beam reporting indication message indicates to the network device that at least one report is triggered by an event corresponding to at least one beam reporting.

[0134] In some embodiments, a second configuration related to the beam report indication message includes a scheduling request configuration index or a physical uplink control channel (PUSCH) resource index. In some embodiments, the time or transmission window for transmitting the beam report is based on the transmission time of the beam report indication message. In some embodiments, the time or transmission window for transmitting the beam report starts or ends X milliseconds after the beam report indication message is transmitted, and the value of X is the physical uplink shared channel (PUSCH) ready time, a set value, or a predefined value. In some embodiments, the time or transmission window for transmitting the beam starts or ends at a symbol Y symbols after the end symbol of the beam report indication message, and the value of Y is configured or predefined. In some embodiments, the time or transmission window for transmitting the beam report starts or ends at a slot Z slots after another slot in which the beam report indication message is transmitted, and the value of Z is configured or predefined.

[0135] FIG. 10 illustrates an exemplary flowchart for receiving a beam report. An operation (1002) includes transmitting a configuration associated with a beam report by a network device, wherein the configuration indicates one or more trigger events that trigger a communication device to transmit a beam report. An operation (1004) includes receiving a beam report by a network device from a communication device in response to the occurrence of a trigger event from one or more trigger events, wherein the beam report is received from an uplink resource or from an uplink transmission.

[0136] In some embodiments, the uplink resource or uplink transmit is based on a Type 1 or Type 2 configured grant physical uplink shared channel (PUSCH) transmit configured with a configuration related to beam reporting. In some embodiments, the uplink resource or uplink transmit is based on a Type 1 or Type 2 configured grant physical uplink shared channel (PUSCH) transmit configured to multiplex beam reporting for a corresponding PUSCH transmit. In some embodiments, the uplink resource is a physical uplink control channel (PUCCH) resource configured for beam reporting. In some embodiments, the uplink resource or uplink transmit is based on a physical uplink shared channel (PUSCH) transmit determined based on a PUSCH transmit parameter configuration of a beam reporting-only configuration.

[0137] In some embodiments, the uplink resource or uplink transmission is based on a physical uplink shared channel (PUSCH) transmission determined based on a rule, and the rule specifying the PUSCH transmission parameters for the PUSCH transmission is based on the PUSCH transmission parameters indicated by the PDCCH that schedules a second PUSCH transmission separate from the PUSCH transmission. In some embodiments, the uplink resource or uplink transmission is one of one or more uplink resources or a plurality of uplink transmissions, and the plurality of uplink resources or a plurality of uplink transmissions are transmitted within a transmission window. In some embodiments, a plurality of uplink resources or a plurality of uplink transmits comprises at least one of the following: a physical uplink control channel (PUCCH) indicated by a physical downlink control channel (PDCCH) to transmit within a transmit window; a physical uplink shared channel (PUSCH) scheduled by the PDCCH to transmit within a transmit window; a PUCCH resource carrying periodic channel state information (CSI) or semi-persistent CSI reporting; a PUSCH having a Type 1 configuration grant; or a PUSCH having a Type 2 configuration grant enabled by a PDCCH having a Type 2 configuration grant.

[0138] In some embodiments, a configuration for beam reporting includes: a first configuration for channel state information (CSI) reporting—the first configuration indicates one or more triggers associated with CSI reporting—a second configuration for beam reporting indicating at least one of one or more trigger events, a reporting configuration identifier, a reference signal for measurement, or an indicator of reporting indicating content for beam reporting, or at least one configuration for CSI reporting including a reporting configuration type set to 'event triggered'. In some embodiments, the communication device transmits the beam report using a type of media access control—control element (MAC CE) or uplink control information (UCI).

[0139] In some embodiments, a beam report is received using a MAC CE comprising at least one of a beam report presence indicator, a cell indicator, a reference signal resource indicator, a report indicator indicating the content of the beam report, or an identifier of a trigger event. In some embodiments, a beam report is received using a MAC CE associated with only one beam report, or a beam report is received using a MAC CE associated with one beam report indicator associated with a reference signal. In some embodiments, a beam report is received using a MAC CE associated with one or more beam reports, or a beam report is received using a MAC CE associated with one or more report indicators associated with one or more reference signals. In some embodiments, a configuration associated with a beam report comprises a report indicator indicating the content for the beam report, wherein at least one of the following is configured: the reference signal received power (RSRP) corresponds to the synchronization signal block (SSB) resource indicator, the RSRP corresponds to the channel state information reference signal resource indicator (CRI), the signal-to-noise and interference ratio (SINR) corresponds to the SSB index, or the SINR corresponds to the CRI.

[0140] In some embodiments, a network device receives a second configuration associated with a beam report indication message, and the network device receives a beam report indication message from a communication device based on the second configuration in response to a trigger event of at least one beam report, and the beam report indication message indicates to the network device that at least one report is triggered by an event corresponding to at least one beam report. In some embodiments, the second configuration associated with the beam report indication message includes a scheduling request configuration index or a physical uplink control channel (PUCCH) resource index. In some embodiments, the time or transmission window for transmitting the beam report is based on the time of reception of the beam report indication message. In some embodiments, the time or transmission window for receiving the beam report starts or ends X milliseconds after the beam report indication message is transmitted, and the value of X is the physical uplink shared channel (PUSCH) ready time, a set value, or a predefined value.

[0141] In some embodiments, the time or transmission window for receiving a beam starts or ends at a symbol Y symbols after the end symbol of the beam report indication message, and the value of Y is configured or pre-defined. In some embodiments, the time or transmission window for receiving a beam report starts or ends at a slot Z slots after another slot in which the beam report indication message was transmitted, and the value of Z is configured or pre-defined.

[0142] In this document, the term “exemplary” means “an example of” and, unless otherwise specified, does not mean an ideal or preferred embodiment.

[0143] Some of the embodiments described herein are described in general circumstances of a method or process, which may be implemented in one embodiment by a computer program product embodied on a computer-readable medium, comprising computer-executable instructions, such as program code, executed by a computer in a networked environment. The computer-readable medium may include removable and non-removable storage devices, such as ROM (Read Only Memory), RAM (Random Access Memory), CD (compact disc), DVD (digital versatile disc), etc., but are not limited thereto. Accordingly, the computer-readable medium may include non-transient storage media. Generally, a program module may include a routine, program, object, component, data structure, etc., that performs a specific task or implements a specific abstract data type. Computer-executable, or processor-executable, instructions, associated data structures, and program modules represent examples of program code that execute the steps of the method disclosed herein. A specific sequence of such executable instructions or associated data types represents examples of corresponding operations for implementing the functions described in such steps or processors.

[0144] Some of the disclosed embodiments may be implemented as devices or modules using hardware circuits, software, or a combination thereof. For example, hardware circuit implementations may include discrete analog and / or digital components integrated as part of a printed circuit board. Alternatively or additionally, the disclosed components or modules may be implemented as Application Specific Integrated Circuits (ASICs) and / or Field Programmable Gate Array (FPGA) devices. Some embodiments may additionally or alternatively include a digital signal processor (DSP), which is a specialized microprocessor having an architecture optimized for the operational requirements of digital signal processing associated with the functions disclosed in this application. Similarly, various components or sub-components within each module may be implemented in software, hardware, or firmware. Connectivity between modules and / or components within a module may be provided using any one of conventional connectivity methods and media, including but not limited to communication over the Internet, wired, or wireless networks using suitable protocols.

[0145] Although this document contains many details, they are not intended to limit the scope of the claimed or claimable invention, but rather should be interpreted as a description of features specific to a particular embodiment. Specific features described in this document in the context of a separate embodiment may also be implemented in combination in a single embodiment. Conversely, various features described in the context of a single embodiment may also be implemented in multiple embodiments separately or in any suitable sub-combination. Furthermore, while features may be described above as operating in a specific combination and may even be initially claimed as such, in some cases, one or more features from the claimed combination may be removed from the combination, and the claimed combination may relate to a sub-combination or a variation of the sub-combination. Similarly, operations are depicted in a specific order in the drawings, but this should not be understood as requiring that these operations be performed in the specific order depicted, in a sequential order, or that all of the exemplified operations be performed in order to achieve a desired result.

[0146] Only a few embodiments and examples have been described, and other embodiments, improvements, and variations may be made based on what has been described and illustrated in this document.

Claims

Claim 1 A wireless communication method comprising: receiving a configuration related to a beam report by a communication device, wherein the configuration indicates one or more trigger events that trigger the communication device to transmit the beam report; and transmitting the beam report by the communication device in response to the occurrence of a trigger event from the one or more trigger events, wherein the beam report is transmitted by the communication device from an uplink resource or from an uplink transmission. Claim 2 A wireless communication method according to claim 1, wherein the uplink resource or the uplink transmission is based on a Type 1 or Type 2 configured grant physical uplink shared channel (PUSCH) transmission configured with a configuration associated with the beam report. Claim 3 A wireless communication method according to claim 1, wherein the uplink resource or the uplink transmission is based on a Type 1 or Type 2 configured grant physical uplink shared channel (PUSCH) transmission configured to multiplex the beam report for the corresponding PUSCH transmission. Claim 4 A wireless communication method according to claim 1, wherein the uplink resource is a physical uplink control channel (PUCCH) resource configured for the beam report. Claim 5 A wireless communication method according to claim 1, wherein the uplink resource or the uplink transmission is based on a physical uplink shared channel (PUSCH) transmission determined based on the configuration of PUSCH transmission parameters dedicated to the beam report. Claim 6 A wireless communication method according to claim 1, wherein the uplink resource or the uplink transmission is based on a physical uplink shared channel (PUSCH) transmission determined based on a rule, and the rule specifying the PUSCH transmission parameters for the PUSCH transmission is based on the PUSCH transmission parameters indicated by a PDCCH that schedules a second PUSCH transmission other than the PUSCH transmission. Claim 7 A wireless communication method according to claim 1, wherein the uplink resource or the uplink transmission is one of a plurality of uplink resources or one of a plurality of uplink transmissions, and the plurality of uplink resources or the plurality of uplink transmissions are transmitted within a transmission window by the communication device. Claim 8 A wireless communication method according to claim 7, wherein the plurality of uplink resources or the plurality of uplink transmissions comprises at least one of a physical uplink control channel (PUCCH) indicated by a physical downlink control channel (PDCCH) to transmit within the transmission window, a physical uplink shared channel (PUSCH) scheduled by the PDCCH to transmit within the transmission window, a PUCCH resource carrying periodic channel state information (CSI) or semi-persistent CSI reporting, a PUSCH having a Type 1 setting grant, and a PUSCH having a Type 2 setting grant activated by the PDCCH. Claim 9 A wireless communication method according to claim 1, wherein the communication device performs rate matching for the step of transmitting the beam report in a physical uplink shared channel (PUSCH) transmission based on a configured beta offset value or the step of multiplexing the beam report. Claim 10 A wireless communication method according to claim 1, wherein the configuration related to the beam report comprises: a first configuration for channel state information (CSI) reporting - the first configuration displays one or more trigger events associated with the CSI report -; a second configuration for the beam report displaying at least one of the one or more trigger events, a report configuration identifier, a reference signal for measurement, and a report indicator displaying content for the beam report; and at least one of the third configuration for the CSI report including a report configuration type set to 'event triggered'. Claim 11 A wireless communication method according to claim 1, wherein the communication device transmits the beam report using a medium access control-control element (MAC CE) or uplink control information (UCI) type. Claim 12 A wireless communication method according to claim 11, wherein the beam report is transmitted using the MAC CE comprising at least one of a cell indicator, a reference signal resource indicator, a report indicator indicating the content of the beam report, and an identifier of the trigger event. Claim 13 A wireless communication method according to claim 11, wherein the beam report is transmitted using the MAC CE associated with only one beam report, or the beam report is transmitted using the MAC CE associated with one beam report indicator associated with a reference signal. Claim 14 A wireless communication method according to claim 11, wherein the beam report is transmitted using the MAC CE associated with one or more beam reports, or the beam report is transmitted using the MAC CE associated with one or more report indicators associated with one or more reference signals. Claim 15 A wireless communication method according to claim 1, wherein the configuration related to the beam report comprises a report indicator that displays the content of the beam report, wherein the reference signal receive power (RSRP) corresponds to a synchronization signal block (SSB), the RSRP corresponds to a channel state information reference signal resource indicator (CRI), and the signal-to-noise and interference ratio (SINR) corresponds to an SSB index or the SINR corresponds to the CRI; at least one of which is configured. Claim 16 A wireless communication method according to claim 1 or 7, wherein the communication device receives a second configuration related to a beam report indication message, and the communication device transmits the beam report indication message to a network device based on the second configuration in response to a trigger event of at least one beam report, and the beam report indication message indicates to the network device that at least one beam report has been triggered by an event corresponding to the at least one beam report. Claim 17 A wireless communication method according to claim 16, wherein the second configuration related to the beam report display message comprises a scheduling request configuration index or a physical uplink control channel (PUCCH) resource index. Claim 18 A wireless communication method according to claim 16, wherein the time or transmission window for transmitting the beam report is based on the transmission time of the beam report display message. Claim 19 A wireless communication method according to claim 18, wherein the time or transmission window for transmitting the beam report starts or ends after X milliseconds after the beam report indication message is transmitted, and the value of X is the physical uplink shared channel (PUSCH) preparation time, a configured value, or a predetermined value. Claim 20 A wireless communication method according to claim 18, wherein the time or transmission window for transmitting the beam report starts or ends at a symbol after the Y symbol after the end symbol of the beam report indication message, and the value of Y is configured or pre-defined. Claim 21 A wireless communication method according to claim 18, wherein the time or transmission window for transmitting the beam report starts or ends in a slot after Z slot from another slot in which the beam report indication message is transmitted, and the value of Z is configured or pre-defined. Claim 22 A wireless communication method comprising: a step of transmitting a configuration related to a beam report by a network device, wherein the configuration indicates one or more trigger events that trigger the communication device to transmit the beam report; and a step of receiving a beam report from the communication device by the network device in response to the occurrence of a trigger event from the one or more trigger events, wherein the beam report is received in an uplink report or uplink transmission. Claim 23 A wireless communication method according to claim 22, wherein the uplink resource or the uplink transmission is based on a Type 1 or Type 2 configured grant physical uplink shared channel (PUSCH) transmission configured with a configuration associated with the beam report. Claim 24 A wireless communication method according to claim 22, wherein the uplink resource or the uplink transmission is based on a Type 1 or Type 2 configured grant physical uplink shared channel (PUSCH) transmission configured to multiplex the beam report for the corresponding PUSCH transmission. Claim 25 A wireless communication method according to claim 22, wherein the uplink resource is a physical uplink control channel (PUCCH) resource configured for the beam report. Claim 26 A wireless communication method according to claim 22, wherein the uplink resource or the uplink transmission is based on a physical uplink shared channel (PUSCH) transmission determined based on the configuration of PUSCH transmission parameters dedicated to the beam report. Claim 27 A wireless communication method according to claim 22, wherein the uplink resource or the uplink transmission is based on a physical uplink shared channel (PUSCH) transmission determined based on a rule, and the rule specifying the PUSCH transmission parameters for the PUSCH transmission is based on the PUSCH transmission parameters indicated by a PDCCH that schedules a second PUSCH transmission different from the PUSCH transmission. Claim 28 A wireless communication method according to claim 22, wherein the uplink resource or the uplink transmission is one of a plurality of uplink resources or one of a plurality of uplink transmissions, and the plurality of uplink resources or the plurality of uplink transmissions are transmitted within a transmission window. Claim 29 A wireless communication method according to claim 28, wherein the plurality of uplink resources or the plurality of uplink transmissions comprises at least one of a physical uplink control channel (PUCCH) indicated by a physical downlink control channel (PDCCH) to transmit within the transmission window, a physical uplink shared channel (PUSCH) scheduled by the PDCCH to transmit within the transmission window, a PUCCH resource carrying periodic channel state information (CSI) or semi-persistent CSI reports, a PUSCH having a Type 1 configuration grant, and a PUSCH having a Type 2 configuration grant activated by the PDCCH. Claim 30 A wireless communication method according to claim 22, wherein the configuration related to the beam report comprises: a first configuration for channel state information (CSI) reporting - said first configuration displays said one or more trigger events associated with said CSI reporting -; a second configuration for the beam report displaying at least one of said one or more trigger events, a report configuration identifier, a reference signal for measurement, and a report indicator displaying content for said beam reporting; and at least one of said third configuration for the CSI reporting including a report configuration type set to 'event triggered'. Claim 31 A wireless communication device comprising a processor, wherein the processor is configured to implement a method described in one or more of claims 1 to 30. Claim 32 A non-transient computer-readable program storage medium storing code, wherein the code, when executed by a processor, causes the processor to implement the method described in one or more of claims 1 to 30.

Images