Beam reporting method and wireless communication device

Abstract

The present invention provides a beam reporting method, comprising: a user equipment receiving a beam reporting configuration sent by a base station, wherein the beam reporting configuration comprises at least one of the following: a measurement resource configuration, a report resource configuration, an event configuration, a report quantity, a report content configuration, and a cell configuration; and then reporting to the base station at least one of the following: cell information, event information, panel information, and beam information, wherein the beam information comprises at least one of the following: an index of a current beam, a quality value of the current beam, an index of a new beam, and a quality value of the new beam. Therefore, beam reporting overhead and a beam update delay can be reduced.

Description

Beam reporting method and wireless communication device Technical Field

[0001] The present disclosure relates to the field of wireless communications, and in particular to a beam reporting method and wireless communication equipment. Background Art

[0002] Millimeter wave (mmWave) is a key technology in 5G. Its main advantage is its abundant spectrum resources, which can provide greater bandwidth and thus support higher data rates. However, mmWave also faces some challenges. First, mmWave has a short propagation distance, typically only a few hundred meters. Second, mmWave signals are susceptible to atmospheric absorption and rain attenuation, which can affect their performance in outdoor environments. Furthermore, mmWave signals are easily blocked by buildings and other objects.

[0003] To overcome these challenges, beam management technology has been proposed. Beam management focuses wireless signals in a specific direction by controlling the phase and amplitude of an antenna array. This significantly improves signal quality, enhances signal coverage, and reduces interference. In millimeter-wave communications, the narrow beamwidth requires precise beam alignment, which necessitates complex beam management strategies. Beam management involves numerous processes, and these processes present numerous challenges. Therefore, a beam reporting method and wireless communication device are needed to improve existing technologies.

[0004] Summary of the Invention

[0005] The technical problem to be solved by the present invention is to provide a beam reporting method in response to the above-mentioned defects of the prior art, aiming to solve many problems that need to be solved in the beam management process in the prior art.

[0006] According to one aspect of the present disclosure, a beam reporting method is provided, which is executed on a user equipment. The method includes:

[0007] Receiving an event-driven beam reporting configuration, wherein the event-driven beam reporting configuration includes at least one of the following: measurement resource configuration, reporting resource configuration, event configuration, reporting amount, reporting content configuration, and cell configuration;

[0008] Based on the event-driven beam reporting configuration, at least one of the following is reported: cell information, event information, panel information, and beam information, wherein the beam information includes at least one of the following: the index of the current beam, the quality value of the current beam, the index of the new beam, and the quality value of the new beam.

[0009] According to one aspect of the present disclosure, a beam reporting method is provided, which is executed by a base station. The method includes:

[0010] Sending an event-driven beam reporting configuration, wherein the event-driven beam reporting configuration includes at least one of the following: measurement resource configuration, reporting resource configuration, event configuration, reporting amount, reporting content configuration, and cell configuration;

[0011] Receive at least one of the following: cell information, event information, panel information, and beam information, wherein the beam information includes at least one of the following: the index of the current beam, the quality value of the current beam, the index of the new beam, and the quality value of the new beam.

[0012] According to one aspect of the present disclosure, a wireless communication device is provided, comprising a processor and a memory, wherein the memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to perform the steps in the data processing method as described in any one of the above items.

[0013] Beneficial effects of the present invention: The present invention discloses a user device receiving a beam reporting configuration sent by a base station, wherein the beam reporting configuration includes at least one of the following: measurement resource configuration, reporting resource configuration, event configuration, reporting amount, reporting content configuration and cell configuration; and then reporting at least one of the following to the base station: cell information, event information, panel information, beam information, wherein the beam information includes at least one of the following: the index of the current beam, the quality value of the current beam, the index of the new beam and the quality value of the new beam, which can reduce the beam reporting overhead and reduce the update delay of the beam. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] In order to more clearly illustrate the embodiments of the present disclosure or related technologies, the following drawings will be briefly introduced in the embodiments. Obviously, the drawings are only some embodiments of the present disclosure, and ordinary technicians in this field can derive other drawings based on these drawings without inventive work.

[0015] FIG1 is a schematic diagram illustrating a wireless communication system architecture provided by the present disclosure.

[0016] FIG2 illustrates one of the schematic diagrams of a beam reporting method provided by the present disclosure.

[0017] FIG3 illustrates a second schematic diagram of a beam reporting method provided by the present disclosure.

[0018] FIG4 illustrates an exemplary block diagram of a wireless communication system provided by the present disclosure. DETAILED DESCRIPTION

[0019] The embodiments of the present disclosure describe technical matters, structural features, objectives and effects in detail with reference to the accompanying drawings, as described below. Specifically, the terms in the embodiments of the present disclosure are only used to describe the purpose of specific embodiments, rather than to limit the present disclosure.

[0020] The relevant technical terms in this article are explained as follows:

[0021] In this disclosure, "A or B" may mean "only A," "only B," or "both A and B."

[0022] In other words, in the present disclosure, "A or B" may be interpreted as "A and / or B." For example, in the present disclosure, "A, B or C" may mean "only A," "only B," "only C," or "any combination of A, B, and C."

[0023] As used in this disclosure, a slash ( / ) or a comma may mean "and / or". For example, "A / B" may mean "A and / or B". Thus, "A / B" may mean "only A", "only B", or "both A and B". For example, "A, B, C" may mean "A, B, or C".

[0024] In the present disclosure, “at least one of A and B” may mean “only A”, “only B”, or “both A and B”. In addition, in the present disclosure, the expression “at least one of A or B” or “at least one of A and / or B” may be interpreted as “at least one of A and B”.

[0025] In addition, in the present disclosure, “at least one of A, B, and C” may mean “only A,” “only B,” “only C,” or “any combination of A, B, and C.” In addition, “at least one of A, B, or C” or “at least one of A, B, and / or C” may mean “at least one of A, B, and C.”

[0026] Furthermore, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features being referred to. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of the described features. Throughout the description of this application, "plurality" means two or more, unless otherwise specifically defined.

[0027] Those skilled in the art will recognize and appreciate that the details of the described examples are merely illustrative of some embodiments and that the teachings set forth herein are applicable to various alternative arrangements.

[0028] The technical solution disclosed herein can be applied to various wireless communication systems, such as: Long Term Evolution (LTE) system, LTE Frequency Division Duplex (FDD) system, LTE Time Division Duplex (TDD) system, 5G communication system or future wireless communication systems, etc.

[0029] Exemplarily, a wireless communication system 100 applied in the present disclosure is shown in FIG1 . The wireless communication system 100 may include a base station 110, which may be a device that communicates with a user equipment 120 (User Equipment). The base station 110 may provide communication coverage for a specific geographical area and may communicate with user equipment located within the coverage area. Optionally, the base station 110 may be an evolved base station (eNB or eNodeB) in an LTE system, or the base station may be a mobile switching center, a relay station, an access point, a vehicle-mounted device, a wearable device, a hub, a switch, a bridge, a router, a network-side device in a 5G network, or a base station in a future communication system, etc.

[0030] The wireless communication system 100 also includes at least one user equipment 120 located within the coverage area of ​​the base station 110. As used herein, "user equipment" includes, but is not limited to, a device configured to receive / send communication signals via a wired connection, such as a Public Switched Telephone Network (PSTN), a Digital Subscriber Line (DSL), a digital cable, a direct cable connection; and / or another data connection / network; and / or via a wireless interface, such as a cellular network, a Wireless Local Area Network (WLAN), a digital television network such as a DVB-H network, a satellite network, an AM-FM broadcast transmitter; and / or another user equipment; and / or an Internet of Things (IoT) device. A user equipment configured to communicate via a wireless interface may be referred to as a "wireless communication terminal," "wireless terminal," or "mobile terminal." Examples of mobile terminals include, but are not limited to, satellite or cellular telephones; Personal Communications System (PCS) terminals that can combine cellular radiotelephones with data processing, fax, and data communication capabilities; PDAs that can include radiotelephones, pagers, Internet / Intranet access, web browsers, notepads, calendars, and / or Global Positioning System (GPS) receivers; and conventional laptop and / or palmtop receivers or other electronic devices that include radiotelephone transceivers. User equipment can refer to access terminals, subscriber units, subscriber stations, mobile stations, mobile stations, remote stations, remote user equipment, mobile devices, wireless communication devices, or user agents. An access terminal can be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), a handheld device with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, an in-vehicle device, a wearable device, a user device in a 5G network, or a user device in a future evolved PLMN, etc.

[0031] Optionally, the user equipments 120 may perform device-to-device (D2D) communication with each other.

[0032] Optionally, the 5G communication system or 5G network may also be referred to as a New Radio (NR) system or NR network.

[0033] The wireless communication system 100 also includes a core network 130. Core network 130 may be an IP mobile communication network operated by a mobile communication operator. For example, core network 130 may be a core network used by a mobile communication operator that operates and manages the wireless communication system 100, or may be a core network used by a virtual mobile communication operator such as an MVNO (Mobile Virtual Network Operator).

[0034] The core network 130 can be connected to the base station 110 and serve as a relay device for transmitting user data. The user equipment 120 transmits and receives user data via the core network 130. It should be noted that the communication of user data is not limited to IP communication and can also be non-IP communication.

[0035] FIG1 exemplarily shows a base station 110 , two user equipments 120 and a core network 130 . Optionally, the wireless communication system 100 may include multiple base stations and each base station may include other numbers of user equipments within its coverage area, which is not limited in the present disclosure.

[0036] Optionally, the wireless communication system 100 may further include other network entities such as a network controller, a mobility management entity, and a network element, which is not limited in this disclosure. For example, the core network 130 may include other network entities such as a network controller, a mobility management entity, and a network element, which is not limited in this disclosure.

[0037] It should be understood that in this disclosure, a device with wireless communication capabilities in a network / system may be referred to as a wireless communication device. Taking the wireless communication system 100 shown in Figure 1 as an example, the wireless communication device may include a base station 110 with communication capabilities, a user device 120, and a core network 130. The base station 110 and the user device 120 may be the specific devices described above and will not be described in detail here. The wireless communication device may also include other devices in the wireless communication system 100 (core network 130). For example, the core network 130 may include other network entities such as a network controller and a mobility management entity, but this disclosure does not limit this.

[0038] The information sending method provided by the embodiment of the present application is described in detail below through some embodiments and their application scenarios in combination with the accompanying drawings.

[0039] Beam management technology includes many processes. Currently, 5G processes (such as standardization) beam configuration, beam measurement, beam reporting, and beam indication in beam management technology. In the existing technology, these processes are all controlled by the base station. For example, beam reporting, that is, the user equipment 120 sends the measurement information of the beam to the base station according to the reporting time and resources configured by the base station. If the reporting resources are configured very densely in time, this will cause collisions and waste of uplink resources, thereby reducing system performance; if the reporting resources are configured very sparsely in time, this will cause the base station to be unable to know the beam quality in time, thereby reducing system performance.

[0040] Since the user equipment 120 can know the beam quality more easily and timely, the existing technology proposes user equipment 120 initiated / event-driven (UE-initiated / event-driven, hereinafter referred to as "event-driven") beam management to reduce beam reporting overhead or beam update delay.

[0041] FIG2 illustrates one of the flow charts of the beam reporting method provided by the present disclosure. As shown in FIG2 , the method can be applied to the user equipment 120. The method includes:

[0042] Step S100: Receive an event-driven beam reporting configuration, wherein the event-driven beam reporting configuration includes at least one of the following: measurement resource configuration, reporting resource configuration, event configuration, reporting amount, reporting content configuration, and cell configuration;

[0043] Step S200: Based on the event-driven beam reporting configuration, report at least one of the following: cell information, event information, panel information, and beam information, wherein the beam information includes at least one of the following: the index or identifier of the current beam, the quality value of the current beam, the index or identifier of the new beam, and the quality value of the new beam.

[0044] FIG3 illustrates one of the flow charts of the beam reporting method provided by the present disclosure. As shown in FIG3 , the method can be applied to the user equipment 120. The method includes:

[0045] Step H100: Send an event-driven beam reporting configuration, wherein the event-driven beam reporting configuration includes at least one of the following: measurement resource configuration, reporting resource configuration, event configuration, reporting amount, reporting content configuration, and cell configuration;

[0046] Step H200, receive at least one of the following: cell information, event information, panel information, beam information, wherein the beam information includes at least one of the following: the index or identifier of the current beam, the quality value of the current beam, the index or identifier of the new beam and the quality value of the new beam.

[0047] Specifically, the user equipment 120 receives an event-driven beam reporting configuration sent by the base station 110, wherein the event-driven beam reporting configuration includes at least one of the following: measurement resource configuration, reporting resource configuration, event configuration, reporting amount, reporting content configuration and cell configuration; and then reports at least one of the following to the base station 110: cell information, event information, panel information, beam information, wherein the beam information includes at least one of the following: the index or identifier of the current beam, the quality value of the current beam, the index or identifier of the new beam and the quality value of the new beam, which can reduce the beam reporting overhead and reduce the beam update delay.

[0048] In some embodiments, the content of the event-driven beam reporting is predefined or configured by high-level parameters, that is, based on the event-driven beam reporting configuration, at least one of the following is reported: cell information, event information, panel information, and beam information, where the beam information is predefined or configured by high-level parameters. Reporting cell information can enhance cell identification, reporting event information can enhance event identification, reporting panel information can enhance panel identification of user equipment 120, and reporting beam information can enhance beam identification.

[0049] The panel refers to the panel of the user equipment 120, and in existing standards, it is indicated by the capability in the CSI report.

[0050] In some embodiments, the event-driven beam reporting configuration is associated with or includes at least one of the following: measurement resource configuration, reporting resource configuration, event configuration, reporting content configuration, reporting quantity (reportQuantity), and cell configuration.

[0051] In some embodiments, the measurement resource configuration is associated with or includes at least one of the following: a channel measurement reference signal configuration, an interference measurement reference signal configuration.

[0052] In some embodiments, the reporting resource configuration is associated with or includes at least one of the following: aperiodic reporting resource configuration, semi-continuous reporting resource configuration, and periodic reporting resource configuration.

[0053] In some embodiments, the periodic reporting resource configuration is associated with or includes at least one periodic uplink resource.

[0054] In some embodiments, the information element of the event-driven beam reporting configuration adopts an information unit of the CSI reporting configuration, or adopts an information unit of an independent event measurement reporting configuration. The information unit of the CSI reporting configuration can reuse the information unit of the existing CSI reporting configuration (CSI-ReportConfig) or can be an information unit of an independent CSI reporting configuration (event-CSI-ReportConfig).

[0055] In some embodiments, the event configuration is associated with or includes at least one of the following: an event index or identifier, a threshold value (user equipment 120), an offset value, and a hysteresis value.

[0056] In some embodiments, the reported content configuration is associated with or includes at least one of the following: the configuration of the current beam, the configuration of the new beam, the configuration of the cell, the number of reported beams, and the number of reported cell indexes or identifiers. The current beam is the beam in use, and the new beam is the beam selected by the base station 110 or the user equipment 120.

[0057] In some embodiments, the configuration of the current beam is associated with or includes at least one of the following: whether the current beam index or identifier is reported, and whether the quality value of the current beam is reported.

[0058] In some embodiments, the configuration of the new beam is associated with or includes at least one of the following: whether the new beam index or identifier is reported, whether the quality value of the new beam is reported, and the number of new beams reported.

[0059] In some embodiments, the cell configuration in the reporting content configuration is associated with or includes at least one of the following: whether the cell index or identity is reported, and the number of cell indexes or identities reported.

[0060] In some embodiments, the quality value of the beam may be one or more of the following: reference signal received power (RSRP), reference signal received quality (RSRQ), and signal to interference plus noise ratio (SINR).

[0061] In some embodiments, the information element of the event-driven beam reporting configuration adopts the information element of the CSI reporting configuration, and the CSI reporting configuration includes at least one of the following: measurement resource configuration, reporting resource configuration, event configuration, reporting amount, reporting content configuration, and cell configuration. In some embodiments, if the CSI reporting configuration is related to an event, or the reporting configuration identifier in the CSI reporting configuration is associated with an event identifier, or the CSI reporting configuration is configured with an event type, the CSI report corresponding to the CSI reporting configuration is an event-driven beam management CSI report.

[0062] Specifically, the CSI reporting configuration (CSI-ReportConfig) is used to configure event-driven beam reporting. This means that event-driven beam reporting is CSI reporting. The CSI reporting configuration can be configured using the reportQuantity to save signaling overhead.

[0063] Each CSI-ReportConfig is associated with or contains at least one of the following: measurement resource configuration (CSI-ResourceConfig), reporting resource configuration (reportConfigType), event configuration (eventType), reporting quantity (reportQuantity), reporting content configuration, and cell configuration (carrier).

[0064] The method of configuring event-driven beam reporting by multiplexing the information unit CSI reporting configuration (CSI-ReportConfig) includes at least one of the following:

[0065] Method 1:

[0066] If CSI-ReportConfig is event-related, or reportConfigId is associated with an event identifier or index (eventId), or an event type (eventType) is configured in CSI-ReportConfig, then this CSI report is an event-driven beam management CSI report (that is, based on the event-driven beam reporting configuration, at least one of the following is reported: cell information, event information, panel information, beam information), rather than a beam management CSI report initiated by base station 110. In addition, it is stipulated that the reporting quantity reportQuantity in this CSI reporting configuration CSI-ReportConfig can only be configured as beam management-related configurations such as CSI reference signal resource indicator signal received power (cri-RSRP), synchronized broadcast block index signal received power ssb-Index-RSRP, CSI reference signal resource indicator signal to noise ratio cri-SINR, synchronized broadcast block index signal to noise ratio ssb-Index-SINR, etc.

[0067] The CSI report initiated by the base station 110 refers to the CSI-ReportConfig in which the reporting quantity (reportQuantity) is configured as cri-RSRP, ssb-Index-RSRP, cri-SINR, ssb-Index-SINR and other beam management-related configurations.

[0068] Method 2:

[0069] In some embodiments, the higher-layer parameters in the CSI reporting configuration include configuration parameters, wherein the configuration parameters indicate that the CSI reporting corresponding to the CSI reporting configuration is event-driven beam-managed CSI reporting.

[0070] Specifically, the high-level parameter reportQuantity in CSI-ReportConfig includes a configuration parameter (e.g., eventId-ssb-Index-RSRP), which indicates that this CSI report is an event-driven beam-managed CSI report, rather than a beam-managed CSI report initiated by base station 110.

[0071] In some embodiments, the information element of the event-driven beam reporting configuration uses an information element of the event CSI reporting configuration, where the event CSI reporting configuration includes at least one of the following: measurement resource configuration, reporting resource configuration, event configuration, reporting amount, reporting content configuration, and cell configuration. This simplifies defining priorities for the information elements of the event CSI reporting configuration.

[0072] In some embodiments, the event CSI reporting configuration is associated with at least one event type, wherein content related to at least one event corresponding to the at least one event type is configured by the reporting content.

[0073] Specifically, the information element event-CSI-ReportConfig is used to configure event-driven beam reporting, which means that event-driven beam reporting is CSI reporting.

[0074] Each event-CSI-ReportConfig is associated with or includes at least one of the following: measurement resource configuration, reporting resource configuration, event configuration, reporting content configuration (reportContent) or cell configuration (carrier).

[0075] Methods for configuring event-driven beam reporting using the information unit event CSI reporting configuration (event-CSI-ReportConfig) include at least one of the following:

[0076] Method 1:

[0077] An event-CSI-ReportConfig can only be associated with or contain one eventType. This means that an event CSI reporting configuration can only contain content related to one event, or in other words, a reporting resource can only report content related to one event. This allows events to be distinguished by reporting resource, eliminating the need to report event indexes and reducing reporting overhead. Event-related content is configured using the reportContent field.

[0078] The high-level parameter current beam index or identification report configuration (currentBeamIdReport) indicates whether the index or identification of the current beam is reported, the high-level parameter current beam quality report configuration (currentBeamQualityReport) indicates whether the quality value of the current beam is reported, the high-level parameter new beam identification or index report configuration (newBeamIdReport) indicates whether the index or identification of the new beam is reported, the high-level parameter new beam quality report configuration (newBeamQualityReport) indicates whether the quality value of the new beam is reported, and the high-level parameter new beam number (newBeamNumber) indicates the number of new beams reported.

[0079] Method 2:

[0080] An event-CSI-ReportConfig is associated with or contains multiple eventTypes. This means that a single event CSI report can contain content related to multiple events, or a single reporting resource can report content related to multiple events. This way, when the same beam meets the trigger conditions for different events, multiple reports are not required, thus saving signaling. Event-related content is configured using reportContent.

[0081] The high-level parameter eventIdReport indicates the index or identifier of the event to be reported.

[0082] In some embodiments, the information element of the event-driven beam reporting configuration uses an information element of an independent event measurement reporting configuration, where the independent event measurement reporting configuration includes at least one of the following: measurement resource configuration, reporting resource configuration, event configuration, reporting amount, reporting content configuration, and cell configuration. As UCI, the event-driven beam reporting configuration can have an independent priority and an independent encoding method.

[0083] Specifically, the information unit event-beam-report (event-Beam-Report) is used to configure event-driven beam reporting.

[0084] Each event-Beam-Report is associated with or contains at least one of the following: measurement resource configuration, reporting resource configuration, event configuration, reporting content configuration, and cell configuration.

[0085] If PUCCH is used for reporting, it means that the event-driven beam reporting is uplink control information (UCI). If PUSCH is used for reporting, the event-driven beam reporting will use the medium access control control element MAC CE.

[0086] In some embodiments, the method further includes reporting at least one of the following when an event occurs: cell information, event information, panel information, and beam information.

[0087] Optionally, the event (or triggering event) includes at least one of the following:

[0088] Event 1 (similar to L3-A2): The quality of the current beam is worse than a certain threshold.

[0089] Event 2 (similar to L3-A3): The quality of at least one new beam, such as Layer 1 Reference Signal Receiving Power (L1-RSRP), becomes better than the threshold of the current beam.

[0090] Event 3 (similar to L3-A4): The quality of the new beam is better than a certain threshold.

[0091] Event 4 (similar to L3-A5): The quality of the current beam is worse than threshold 1, and the quality of at least one new beam is better than threshold 2.

[0092] It is worth noting that events 1 to 4 are all related to beam management.

[0093] Other possibilities are not ruled out.

[0094] In addition, for the measurement signal, at least SSB and periodic CSI-RS are supported.

[0095] For the reporting content, at least the downlink reference signal index or identifier and L1-RSRP are supported.

[0096] For reporting media, one or more of MAC CE, UCI and other possible media are supported.

[0097] Specifically, the reporting content related to event 1 (the quality of the current beam is worse than the threshold) is at least one of the following:

[0098] 1) Event index or identification only.

[0099] 2) The quality value of the current beam.

[0100] 3) The index or identification of the current beam and the quality value of the current beam.

[0101] 4) Event index or identification, index or identification and quality value of the current beam.

[0102] 5) Cell index or identification, event index or identification.

[0103] 6) Cell index or identification, quality value of the current beam.

[0104] 7) Cell index or identification, index or identification and quality value of the current beam.

[0105] 8) Cell index or identification, event index or identification, current beam index or identification and new beam quality value.

[0106] Event 2 (the quality of at least one new beam is better than the quality of the current beam plus the threshold) is reported with at least one of the following:

[0107] 1) The indices or identifiers and quality values ​​of several new beams.

[0108] 2) The quality value of the current beam, and the indexes or identifiers and quality values ​​of several new beams.

[0109] 3) The index or identification and quality value of the current beam, and the index or identification and quality values ​​of several new beams.

[0110] 4) Event index or identification, indexes or identifications of several new beams and quality values.

[0111] 5) Event index or identifier, quality value of the current beam, indexes or identifiers and quality values ​​of several new beams.

[0112] 6) Event index or identification, index or identification and quality value of the current beam, and index or identification and quality values ​​of several new beams.

[0113] 7) Cell index or identification, indexes or identifications and quality values ​​of several new beams.

[0114] 8) Cell index or identification, quality value of the current beam, indexes or identifications and quality values ​​of several new beams.

[0115] 9) Cell index or identification, index or identification and quality value of the current beam, and index or identification and quality values ​​of several new beams.

[0116] 10) Cell index or identifier, event index or identifier, indexes or identifiers of several new beams and quality values.

[0117] 11) Cell index or identifier, event index or identifier, quality value of the current beam, and indexes or identifiers and quality values ​​of several new beams.

[0118] 12) Cell index or identifier, event index or identifier, index or identifier and quality value of the current beam, and index or identifier and quality values ​​of several new beams.

[0119] Event 3 (the quality of at least one new beam is better than the threshold) is reported with at least one of the following:

[0120] 1) The indices or identifiers and quality values ​​of several new beams.

[0121] 2) Event index or identification, indexes or identifications of several new beams and quality values.

[0122] 3) Cell index or identification, indexes or identifications and quality values ​​of several new beams.

[0123] 4) Cell index or identification, event index or identification, indexes or identifications of several new beams and quality values.

[0124] Event 4 (the quality of the current beam is worse than the first threshold, and the quality of at least one new beam is better than the second threshold) is reported with at least one of the following:

[0125] 1) The indices or identifiers and quality values ​​of several new beams.

[0126] 2) The quality value of the current beam, and the indexes or identifiers and quality values ​​of several new beams.

[0127] 3) The index or identification and quality value of the current beam, and the index or identification and quality values ​​of several new beams.

[0128] 4) Event index or identification, indexes or identifications of several new beams and quality values.

[0129] 5) Event index or identifier, quality value of the current beam, indexes or identifiers and quality values ​​of several new beams.

[0130] 6) Event index or identification, index or identification and quality value of the current beam, and index or identification and quality values ​​of several new beams.

[0131] 7) Cell index or identification, indexes or identifications and quality values ​​of several new beams.

[0132] 8) Cell index or identification, quality value of the current beam, indexes or identifications and quality values ​​of several new beams.

[0133] 9) Cell index or identification, index or identification and quality value of the current beam, and index or identification and quality values ​​of several new beams.

[0134] 10) Cell index or identifier, event index or identifier, indexes or identifiers of several new beams and quality values.

[0135] 11) Cell index or identifier, event index or identifier, quality value of the current beam, and indexes or identifiers and quality values ​​of several new beams.

[0136] 12) Cell index or identifier, event index or identifier, index or identifier and quality value of the current beam, and index or identifier and quality values ​​of several new beams.

[0137] The index or identifier of each event occupies bits, N events Equal to the number of events. In particular, the index or identifier of each event occupies 2 bits (N events =4).

[0138] Whether an event index or identifier is reported is predefined or configured by higher-level parameters. If an event index or identifier is defined or configured not to be reported, reporting overhead can be reduced. If it is reported, event identification can be improved.

[0139] Whether the cell index or identifier is reported is predefined or configured by higher-level parameters. If the index or identifier of a defined or configured event is not reported, reporting overhead can be reduced. If it is reported, cell identification can be improved.

[0140] Whether the current beam index or identifier is reported is predefined or configured by higher-level parameters. If the index or identifier of a defined or configured event is not reported, reporting overhead can be reduced. If it is reported, identification of the current beam can be improved.

[0141] Whether the current beam quality value is reported is predefined or configured by higher-level parameters. If the index or identifier of the defined or configured event is not reported, reporting overhead can be reduced. If it is reported, identification of the current beam can be improved.

[0142] Whether the index or identifier of the new beam is reported is predefined or configured by a higher-layer parameter.

[0143] Whether the quality value of a new beam is reported is predefined or configured by higher-level parameters. If the quality value of a new beam is not reported, this reduces reporting overhead. If it is reported, more detailed new beam information can be provided.

[0144] The number of new beams to be reported is predefined or configured by a higher-layer parameter. The user equipment 120 needs to know the maximum number of new beams that can be reported.

[0145] The index or identifier of the current beam and the new beam is the index or identifier of the reference signal, such as SSBRI, CRI. The index or identifier of each beam occupies bits, N resources is the number of reference signal resources in a reference signal resource set. In particular, the index or identifier of each beam occupies 6 bits (N resources =64).

[0146] The number of bits occupied by the quality value of each beam is predefined or configured by a higher-layer parameter. Specifically, the quality value of each beam occupies 3, 4, 5, or 7 bits.

[0147] In some embodiments, the method further comprises quantifying a quality value of a beam, wherein the beam is a current beam or a new beam. This method can reduce reporting overhead.

[0148] In some embodiments, the number of bits of the beam quality value is 3 or 4 or 5.

[0149] In some embodiments, quantizing the quality value of the beam includes: differentiating the quality value of the beam from a predefined reference value to obtain a differential value; and quantizing the differential value based on a step size and a number of bits.

[0150] In some embodiments, the step size is any one of the following: 0.5 or 1 or 2 or 3.

[0151] In some embodiments, the step size is predefined or configured by a higher-level parameter; the number of bits is predefined or configured by a higher-level parameter.

[0152] In some embodiments, the reference value includes at least one of the following: an event-related value, a beam quality-related value, a sum of the event-related value and the beam quality-related value, and a difference between the event-related value and the beam quality-related value.

[0153] In some embodiments, the event-related value includes at least one of the following: a threshold value, a hysteresis value, an offset value, the sum of the threshold value and the hysteresis value, the sum of the threshold value and the offset value, the sum of the hysteresis value and the offset value, the difference between the threshold value and the hysteresis value, the difference between the threshold value and the offset value, and the difference between the hysteresis value and the offset value.

[0154] In some embodiments, the step size is an average value.

[0155] In some embodiments, the average value is determined based on a predefined value, the reference value, and the number of bits.

[0156] Specifically, when the beam quality value is greater than the reference value, assuming that N bits are used for quantization, the reference value is Vref, and the step size is Δstep, the quantized value is shown in Table 1:

[0157] Table 1: Quantized beam quality values

[0158] For the case where the beam quality value is less than the reference value, assuming that N bits are used for quantization, the reference value is V ref , the step size is Δ step , the quantized values ​​are shown in Table 2:

[0159] Table 2: Beam quality values ​​after quantization

[0160] For the case where the beam quality value is greater than the reference value, assuming that N bits are used for quantization, the reference value is V ref , the maximum value is V max , then the calculated step size is (V max -V Ref ) / 2 N , the quantized values ​​are shown in Table 3:

[0161] Table 3: Beam quality values ​​after quantization

[0162] For the case where the beam quality value is less than the reference value, assuming that N bits are used for quantization, the reference value is V Ref , the minimum value is V min , then the calculated step size is (V ref -V min ) / 2 N , the quantized values ​​are shown in the following table:

[0163] Table 4: Quantized beam quality values

[0164] In some embodiments, if a reporting entity includes quality values ​​of multiple beams, the quality values ​​of the multiple beams are first differentiated and then quantized based on the same reference value.

[0165] In some embodiments, the reference value is an event-related value (eg, a threshold value).

[0166] Specifically, for event 1 (the quality of the current beam is worse than the threshold), the threshold is used as a reference value, the quality value of the current beam is differentiated from this reference value, and quantized according to a predefined step size and number of bits. For example, if the threshold is -120dBm, the step size is 1dB, the number of quantization bits is 4, and if the RSRP of the current beam is -130dBm, the bit sequence used by user equipment 120 to report the current beam quality is '1010', corresponding to a value of 10. If the step size is 2dB and the number of quantization bits is 3, the bit sequence used by user equipment 120 to report the current beam quality is '101', corresponding to a value of 5.

[0167] For event 2 (the quality of at least one new beam is better than the quality of the current beam plus the threshold), the sum of the RSRP of the current beam and the threshold is used as a reference value, and the quality values ​​of the new beams are differentiated from the reference value and quantized according to a predefined step size and number of bits. For example, if the threshold value is 5dB, the step size is 1dB, the number of quantization bits is 4, the RSRP of the current beam is -120dBm, and the RSRP of the two new beams is -110dBm and -99dBm, then the bit sequences used by the user equipment 120 to report the quality of the two new beams are '0101' and '1111' respectively;

[0168] In existing standards, the maximum beam quality value is quantized using 7 bits, and the differential beam quality value is quantized using 4 bits. The method proposed in this embodiment can quantize beam quality values ​​using 3 to 5 bits. Therefore, compared with the quantization method in existing standards, this method can reduce reporting overhead.

[0169] In some embodiments, if a reporting entity includes quality values ​​of multiple beams, the quality values ​​of the multiple beams are first differentiated and then quantized based on different reference values.

[0170] In some embodiments, a quality value of a best beam is determined based on the quality values ​​of the multiple beams. The quality value of the best beam is first differentiated and then quantized based on an event-related value (e.g., a threshold value). The quality values ​​of beams other than the quality value of the best beam are first differentiated and then quantized based on the quality value of the best beam. In this way, signaling overhead can be reduced.

[0171] Specifically, the quantization step size of the quality value of the best beam and the quantization step sizes of the quality values ​​of other beams may be predefined, configured by high-level parameters, or be an average value.

[0172] The quantization step size of the quality value of the best beam and the quantization step size of the quality values ​​of other beams can be the same or different. For example, the quantization step size of the quality value of the best beam is 1 dB, and the quantization step size of the quality values ​​of other beams is 2 dB.

[0173] The quantization step size of the quality values ​​of other beams may be an integer multiple of the quantization step size of the quality value of the maximum beam, for example, 2. The multiple may be predefined or configured by a high-level parameter.

[0174] The number of bits for quantizing the quality value of the best beam and the number of bits for quantizing the quality values ​​of other beams may be predefined or configured by a higher-layer parameter.

[0175] The number of bits used to quantize the quality value of the best beam and the number of bits used to quantize the quality values ​​of the other beams may be the same or different. For example, the number of bits used to quantize the quality value of the best beam is 5, and the number of bits used to quantize the quality values ​​of the other beams is 3.

[0176] For event 3 (the quality of at least one new beam is better than the threshold), the threshold is used as a reference value, the quality value of the best beam is differentiated from this reference value, and quantized according to a predefined step size and number of bits. The quality value of the best beam is then used as a reference value, and the quality values ​​of the other beams are differentiated from this reference value, and quantized according to a predefined step size and number of bits. For example, if the threshold is -80dB, the quality value of the best beam is -60dBm, the corresponding step size is 1dB, and the corresponding number of quantization bits is 5, then the bit sequence reported by user equipment 120 for the best beam is '10100'. If the quality values ​​of the other two beams are -62dBm and -78dBm, respectively, the corresponding step size is 2dB, and the corresponding number of quantization bits is 3, then the bit sequences reported by user equipment 120 for the quality of the other two beams are '000' and '111'.

[0177] In existing standards, the maximum beam quality value is quantized using 7 bits, and the differential beam quality value is quantized using 4 bits. The method proposed in this embodiment can quantize beam quality values ​​using 3 to 5 bits. Therefore, compared with the quantization method in existing standards, this method can reduce reporting overhead.

[0178] In some embodiments, if a reporting entity includes quality values ​​of multiple beams, the quality values ​​of the multiple beams are first differentiated and then quantized based on different reference values.

[0179] In some embodiments, the quality value of the worst beam is determined based on the quality values ​​of the multiple beams, the quality value of the worst beam is first differentiated and then quantized based on the event-related value, and the quality values ​​of other beams except the quality value of the worst beam are first differentiated and then quantized based on the quality value of the worst beam. If a reporting entity includes the current beam, the worst beam and the other beams do not include the current beam.

[0180] Specifically, the quantization step size of the quality value of the worst beam and the quantization step sizes of the quality values ​​of other beams may be predefined, configured by high-level parameters, or be an average value.

[0181] The quantization step size of the quality value of the worst beam and the quantization step sizes of the quality values ​​of other beams may be the same or different. For example, the quantization step size of the quality value of the worst beam is 1 dB, and the quantization step size of the quality values ​​of other beams is 2 dB.

[0182] The quantization step size of the quality values ​​of other beams may be an integer multiple of the quantization step size of the quality value of the maximum beam, for example, 2. The multiple may be predefined or configured by a high-level parameter.

[0183] The number of bits for quantizing the quality value of the worst beam and the number of bits for quantizing the quality values ​​of other beams may be predefined or configured by a higher-layer parameter.

[0184] The number of bits used to quantize the quality value of the worst beam and the number of bits used to quantize the quality values ​​of other beams may be the same or different. For example, the number of bits used to quantize the quality value of the worst beam is 5, and the number of bits used to quantize the quality values ​​of other beams is 3.

[0185] For event 3 (the quality of at least one new beam is better than the threshold value), the threshold value is used as the reference value, the quality value of the worst beam is differentiated from this reference value, and quantized according to the predefined step size and number of bits; then, the quality value of the worst beam is used as the reference value, the quality values ​​of other beams are differentiated from this reference value, and quantized according to the predefined step size and number of bits.

[0186] For event 4 (the quality of the current beam is worse than the first threshold value, and the quality of at least one new beam is better than the second threshold value), the second threshold value is used as the reference value, and the quality value of the worst beam (excluding the current beam) is differentiated from this reference value, and quantized according to the predefined step size and number of bits; then, the quality value of the worst beam is used as the reference value, and the quality values ​​of other beams (excluding the current beam) are differentiated from this reference value, and quantized according to the predefined step size and number of bits; using the first threshold value as the reference value, the quality value of the current beam is differentiated from this reference value.

[0187] In existing standards, the maximum beam quality value is quantized using 7 bits, and the differential beam quality value is quantized using 4 bits. The method proposed in this embodiment can quantize beam quality values ​​using 3 to 5 bits. Therefore, compared with the quantization method in existing standards, this method can reduce reporting overhead.

[0188] In some embodiments, if a reporting entity includes quality values ​​of multiple beams, the quality values ​​of the multiple beams are first differentiated and then quantized based on different reference values.

[0189] In some embodiments, when the quality values ​​of the multiple beams are correlated with a first value related to an event (e.g., a threshold value), the reference value is the first value related to the event; when the quality values ​​of the multiple beams are correlated with a second value related to an event (e.g., a threshold value), the reference value is the second value related to the event.

[0190] Specifically, the quantization step size of the quality value of the beam associated with the value associated with the first event and the quantization step size of the quality value of the beam associated with the second value associated with the event may be predefined, configured by a high-level parameter, or be an average value.

[0191] The quantization step size of the quality value of the beam associated with the first value associated with the event and the quantization step size of the quality value of the beam associated with the second value associated with the event may be the same or different. For example, the quantization step size of the quality value of the beam associated with the first value associated with the event may be 1 dB, and the quantization step size of the quality value of the beam associated with the second value associated with the event may be 2 dB.

[0192] The quantization step size of the quality value of the beam associated with the first value associated with the event may be an integer multiple of the quantization step size of the quality value of the beam associated with the second value associated with the event, for example, 2. The multiple may be predefined or configured by a high-level parameter.

[0193] The number of bits for quantizing the quality value of the worst beam and the number of bits for quantizing the quality values ​​of other beams may be predefined or configured by a high-level parameter.

[0194] The number of quantized bits for the quality value of the beam associated with the first value associated with the event and the number of quantized bits for the quality value of the beam associated with the second value associated with the event may be the same or different. For example, the number of quantized bits for the quality value of the worst beam may be 5, and the number of quantized bits for the quality values ​​of the other beams may be 3.

[0195] For event 4 (the quality of the current beam is worse than the first threshold, and the quality of at least one new beam is better than the second threshold), the quality value of the current beam is differentiated from the reference value using the first threshold as a reference, and quantized using a predefined step size and number of bits. The quality value of the new beam is differentiated from the reference value using the second threshold as a reference, and quantized using a predefined step size and number of bits.

[0196] In some embodiments, the beam information is included in CSI, and the method further includes reporting other CSI, where the other CSI is traditional CSI, including traditional beam management CSI and CSI acquired CSI. The beam information and the other CSI are reported based on priority. In this way, more important CSI can be reported first.

[0197] In some embodiments, the priority is determined based on a formula, and the formula is related to at least one of the following: time domain behavior of CSI reporting, parameter type of CSI reporting, cell index or identifier associated with CSI reporting, and configuration index or identifier of CSI reporting.

[0198] In some embodiments, the time domain behavior of the CSI is related to the reporting configuration type configuration in the CSI reporting configuration, and the time domain behavior of the CSI includes at least one of the following: non-periodic CSI reporting carried by the physical uplink shared channel (PUSCH), semi-persistent CSI reporting carried by the PUSCH, semi-persistent CSI reporting carried by the physical uplink control channel (PUCCH), and periodic CSI reporting carried by the PUCCH.

[0199] In some embodiments, the parameter type of CSI reporting is related to the reporting quantity configuration in the CSI reporting configuration, including at least one of the following: event-driven beam-managed CSI reporting, beam-managed CSI reporting initiated by base station 110, and non-beam-managed CSI reporting.

[0200] In some embodiments, the cell index or identifier associated with the CSI report is related to the carrier configuration in the CSI reporting configuration.

[0201] In some embodiments, the configuration index or identifier of the CSI reporting is related to the reporting configuration index or identifier configuration in the CSI reporting configuration.

[0202] In some embodiments, the formula is determined based on the type of parameter reported by the CSI.

[0203] Specifically, event-driven beam reporting is a type of CSI.

[0204] The priority of CSI reporting is determined according to the following formula:

[0205] Pri iCSI (y,k,c,s)=Γ1·y+Γ2·k+Γ3·c+Γ4·s, where Γ j (j=1, 2, 3, 4) are all positive integers, y corresponds to the time domain behavior of CSI reporting, k corresponds to the parameter type of CSI reporting, c corresponds to the cell index or identifier, and s corresponds to the reporting configuration index or identifier.

[0206] In particular, Γ1 = 2·N cells ·M s , Γ2=N cells ·M s , Γ3=M s , Γ4=1, that is, Pri iCSI (y,k,c,s)=2·N cells ·M s y+N cells ·M s k+M s c+s, where N cells is the number of cells, configured by the high-level parameter maxNrofServingCells; M sIt is the number of reported configurations, which is configured by the high-level parameter maxNrofCSI-ReportConfigurations.

[0207] The smaller the Pri value calculated according to the formula, the higher the priority of the CSI.

[0208] The specific y, k, c, and s in the CSI reporting priority formula are:

[0209] Where y=0 corresponds to aperiodic CSI reporting carried by PUSCH, y=1 corresponds to semi-persistent CSI reporting carried by PUSCH, y=2 corresponds to semi-persistent CSI reporting carried by PUCCH, and y=3 corresponds to periodic CSI reporting carried by PUCCH;

[0210] Wherein, k=0 corresponds to beam-managed CSI reporting or event-driven beam-managed CSI reporting initiated by base station 110, and k=1 corresponds to non-beam-managed CSI reporting;

[0211] c corresponds to the cell index or identity;

[0212] Wherein, s corresponds to the reporting configuration index or identifier.

[0213] When only the parameter type of CSI reporting is considered, that is, when the time domain behavior, cell index or identifier, and configuration index or identifier of the CSI reporting are the same, the CSI reporting for beam management initiated by base station 110 and the CSI reporting for event-driven beam management have the same priority, both higher than the CSI reporting for non-beam management. When an event is triggered, user equipment 120 reports the CSI for event-driven beam management and discards the CSI for beam management initiated by base station 110. When no event is triggered, user equipment 120 reports the CSI for beam management initiated by base station 110 and discards the CSI for event-driven beam management.

[0214] In some embodiments, the priority is determined based on a formula, and the formula is related to at least one of the following: the time domain behavior of CSI reporting, the parameter type of CSI reporting, the cell index or identifier associated with the CSI reporting, the configuration index or identifier of the CSI reporting, and the event index or identifier of the CSI reporting.

[0215] Specifically, event-driven beam reporting is a type of CSI.

[0216] The priority of event-driven beam management CSI reporting over other CSI reporting is determined according to a formula that is related to at least one of the following: the time domain behavior of the CSI reporting, the parameter type of the CSI reporting, the cell index or identifier of the CSI reporting, and the configuration index or identifier of the CSI reporting.

[0217] The time domain behavior of CSI is related to the reportConfigType configuration in CSI-ReportConfig, including at least one of the following: aperiodic CSI reporting carried by PUSCH, semi-persistent CSI reporting carried by PUSCH, semi-persistent CSI reporting carried by PUCCH, and periodic CSI reporting carried by PUCCH;

[0218] The parameter type of CSI reporting is related to the reportQuantity configuration in CSI-ReportConfig, including at least one of the following: event-driven beam-managed CSI reporting, beam-managed CSI reporting initiated by base station 110, and non-beam-managed CSI reporting.

[0219] The non-beam managed CSI reporting at least includes the CSI reporting of CSI measurement.

[0220] The cell index or identifier associated with the CSI report is related to the carrier configuration in the CSI-ReportConfig.

[0221] The configuration index or identifier reported by the CSI is related to the reportConfigId configuration in the CSI-ReportConfig.

[0222] Other CSI reporting refers to CSI reporting in existing standards, including at least beam-managed CSI reporting and non-beam-managed CSI reporting initiated by the base station 110 .

[0223] Specifically, the priority of CSI reporting is determined according to the following formula:

[0224] Pri iCSI (y,k,c,s)=Γ1·y+Γ2·k+Γ3·c+Γ4·s, where Γ j (j=1, 2, 3, 4) are all positive integers, y corresponds to the time domain behavior of CSI reporting, k corresponds to the parameter type of CSI reporting, c corresponds to the cell index or identifier, and s corresponds to the reporting configuration index or identifier.

[0225] In particular, Γ1 = 3·N cells ·M s , Γ2=N cells ·M s , Γ3=M s , Γ4=1, that is, Pri iCSI (y, k, c, s) = 3·N cells ·M s y+N cells ·M s k+M s c+s, where N cellsis the number of cells, configured by the high-level parameter maxNrofServingCells; M s It is the number of reported configurations, which is configured by the high-level parameter maxNrofCSI-ReportConfigurations.

[0226] The smaller the Pri value calculated according to the formula, the higher the priority of the CSI.

[0227] The CSI reporting priority can be at least one of the following:

[0228] Method 1:

[0229] The specific y, k, c, and s in the CSI reporting priority formula are:

[0230] Where y=0 corresponds to aperiodic CSI reporting carried by PUSCH, y=1 corresponds to semi-persistent CSI reporting carried by PUSCH, y=2 corresponds to semi-persistent CSI reporting carried by PUCCH, and y=3 corresponds to periodic CSI reporting carried by PUCCH;

[0231] Wherein, k=0 corresponds to event-driven beam-managed CSI reporting, k=1 corresponds to beam-managed CSI reporting initiated by base station 110, and k=2 corresponds to non-beam-managed CSI reporting;

[0232] Wherein, c corresponds to the cell index or identity;

[0233] Wherein, s corresponds to the reporting configuration index or identifier.

[0234] When only the parameter types of CSI reporting are considered, the CSI priorities from high to low are: event-driven beam management CSI reporting, beam management CSI reporting initiated by base station 110, and non-beam management CSI reporting.

[0235] When considering the cell index or identifier of CSI reporting, the time domain behavior of CSI reporting, and the parameter type of CSI reporting, the CSI priority calculated according to the formula is from high to low (that is, the CSI priority corresponding to item 1 is the highest, and the CSI priority corresponding to item 24) is the lowest):

[0236] 1) Aperiodic, event-triggered CSI reporting for beam management carried by the PUSCH in the primary cell;

[0237] 2) CSI reporting for aperiodic, event-triggered beam management carried by PUSCH in the secondary cell;

[0238] 3) Aperiodic CSI reporting for beam management initiated by base station 110 on the primary cell and carried by the PUSCH;

[0239] 4) Aperiodic CSI reporting for beam management carried by the PUSCH of the secondary cell and initiated by the base station 110;

[0240] 5) Aperiodic, non-beam-managed CSI reporting carried by the PUSCH in the primary cell;

[0241] 6) Aperiodic, non-beam-managed CSI reporting carried by PUSCH in the secondary cell;

[0242] 7) Semi-persistent CSI reporting for event-triggered beam management carried by PUSCH in the primary cell;

[0243] 8) Semi-persistent CSI reporting for event-triggered beam management carried by PUSCH in the secondary cell;

[0244] 9) Semi-persistent CSI reporting for beam management initiated by base station 110 on the PUSCH of the primary cell;

[0245] 10) Semi-persistent CSI reporting for beam management initiated by base station 110 and carried by PUSCH in the secondary cell;

[0246] 11) Semi-persistent, non-beam-managed CSI reporting carried by the PUSCH in the primary cell;

[0247] 12) Semi-persistent, non-beam-managed CSI reporting carried by PUSCH in the secondary cell;

[0248] 13) Semi-persistent, event-triggered beam management CSI reporting for the primary cell and carried by PUCCH;

[0249] 14) Semi-persistent CSI reporting for event-triggered beam management carried by PUCCH in the secondary cell;

[0250] 15) Semi-persistent CSI reporting for beam management initiated by base station 110 and carried by PUCCH in the primary cell;

[0251] 16) Semi-persistent CSI reporting for beam management initiated by base station 110 and carried by PUCCH in the secondary cell;

[0252] 17) Semi-persistent, non-beam-managed CSI reporting carried by PUCCH in the primary cell;

[0253] 18) Periodic non-beam management CSI reporting carried by PUCCH in the secondary cell;

[0254] 19) Periodic CSI reporting for event-triggered beam management carried by the PUCCH in the primary cell;

[0255] 20) Periodic CSI reporting for event-triggered beam management carried by PUCCH in secondary cells;

[0256] 21) Periodic CSI reporting for beam management initiated by base station 110 and carried by PUCCH in the primary cell;

[0257] 22) Periodic CSI reporting for beam management initiated by base station 110 and carried by PUCCH in the secondary cell;

[0258] 23) Periodic non-beam management CSI reporting carried by PUCCH in the primary cell;

[0259] 24) Periodic non-beam-managed CSI reporting carried by PUCCH in the secondary cell.

[0260] Method 2:

[0261] The specific y, k, c, and s in the CSI reporting priority formula are:

[0262] Where y=0 corresponds to aperiodic CSI reporting carried by PUSCH, y=1 corresponds to semi-persistent CSI reporting carried by PUSCH, y=2 corresponds to semi-persistent CSI reporting carried by PUCCH, and y=3 corresponds to periodic CSI reporting carried by PUCCH;

[0263] Wherein, k=0 corresponds to beam-managed CSI reporting initiated by base station 110, k=1 corresponds to event-driven beam-managed CSI reporting, and k=2 corresponds to non-beam-managed CSI reporting;

[0264] Wherein, c corresponds to the cell index or identity;

[0265] Wherein, s corresponds to the reporting configuration index or identifier.

[0266] When only the parameter types of CSI reporting are considered, the CSI priorities from high to low are: beam-managed CSI reporting initiated by the base station 110, event-driven beam-managed CSI reporting, and non-beam-managed CSI reporting.

[0267] When considering the cell index of CSI reporting, the time domain behavior of CSI reporting, and the parameter type of CSI reporting, the CSI priority calculated according to the formula is from high to low (that is, the CSI priority corresponding to item 1 is the highest, and the CSI priority corresponding to item 24) is the lowest):

[0268] 1) Aperiodic CSI reporting for beam management initiated by the base station on the primary cell and carried by the PUSCH;

[0269] 2) Aperiodic CSI reporting for beam management initiated by the base station on the secondary cell and carried by the PUSCH;

[0270] 3) CSI reporting for aperiodic, event-triggered beam management carried by the PUSCH in the primary cell;

[0271] 4) CSI reporting for aperiodic, event-triggered beam management carried by PUSCH in the secondary cell;

[0272] 5) Aperiodic, non-beam-managed CSI reporting carried by the PUSCH in the primary cell;

[0273] 6) Aperiodic, non-beam-managed CSI reporting carried by PUSCH in the secondary cell;

[0274] 7) Semi-persistent CSI reporting for beam management initiated by the base station on the PUSCH of the primary cell;

[0275] 8) Semi-persistent CSI reporting for beam management initiated by the base station on the PUSCH carried by the secondary cell;

[0276] 9) Semi-persistent CSI reporting for event-triggered beam management carried by PUSCH in the primary cell;

[0277] 10) Semi-persistent CSI reporting for event-triggered beam management carried by PUSCH in the secondary cell;

[0278] 11) Semi-persistent, non-beam-managed CSI reporting carried by the PUSCH in the primary cell;

[0279] 12) Semi-persistent, non-beam-managed CSI reporting carried by PUSCH in the secondary cell;

[0280] 13) Semi-persistent CSI reporting for beam management initiated by the base station on the PUCCH of the primary cell;

[0281] 14) Semi-persistent CSI reporting for beam management initiated by the base station and carried by PUCCH in the secondary cell;

[0282] 15) Semi-persistent, event-triggered beam management CSI reporting for the primary cell and carried by PUCCH;

[0283] 16) Semi-persistent CSI reporting for event-triggered beam management carried by PUCCH in the secondary cell;

[0284] 17) Semi-persistent, non-beam-managed CSI reporting carried by PUCCH in the primary cell;

[0285] 18) Periodic non-beam management CSI reporting carried by PUCCH in the secondary cell;

[0286] 19) Periodic CSI reporting for beam management initiated by the base station for the primary cell and carried by PUCCH;

[0287] 20) Periodic CSI reporting of beam management initiated by the base station for the secondary cell and carried by PUCCH;

[0288] 21) Periodic CSI reporting for event-triggered beam management carried by the PUCCH in the primary cell;

[0289] 22) CSI reporting for secondary cells, PUCCH-carried periodic, event-triggered beam management;

[0290] 23) Periodic non-beam management CSI reporting carried by PUCCH in the primary cell;

[0291] 24) Periodic non-beam-managed CSI reporting carried by PUCCH in the secondary cell.

[0292] Method 3:

[0293] The specific y, k, c, and s in the CSI reporting priority formula are:

[0294] Where y=0 corresponds to aperiodic CSI reporting carried by PUSCH, y=1 corresponds to semi-persistent CSI reporting carried by PUSCH, y=2 corresponds to semi-persistent CSI reporting carried by PUCCH, and y=3 corresponds to periodic CSI reporting carried by PUCCH;

[0295] Wherein, k=0 corresponds to the CSI reporting of beam management initiated by the base station 110, k=1 corresponds to the CSI reporting of non-beam management, and k=2 corresponds to the CSI reporting of event-driven beam management;

[0296] Wherein, c corresponds to the cell index or identity;

[0297] Wherein, s corresponds to the reporting configuration index or identifier.

[0298] When only the parameter types of CSI reporting are considered, the CSI priorities from high to low are: beam-managed CSI reporting initiated by the base station 110, non-beam-managed CSI reporting, and event-driven beam-managed CSI reporting.

[0299] When considering the cell index of CSI reporting, the time domain behavior of CSI reporting, and the parameter type of CSI reporting, the CSI priority calculated according to the formula is from high to low (that is, the CSI priority corresponding to item 1 is the highest, and the CSI priority corresponding to item 24) is the lowest):

[0300] 1) Aperiodic CSI reporting for beam management initiated by the base station on the primary cell and carried by the PUSCH;

[0301] 2) Aperiodic CSI reporting for beam management initiated by the base station on the secondary cell and carried by the PUSCH;

[0302] 3) Aperiodic, non-beam-managed CSI reporting carried by the PUSCH in the primary cell;

[0303] 4) Aperiodic, non-beam-managed CSI reporting carried by PUSCH in the secondary cell;

[0304] 5) CSI reporting for aperiodic, event-triggered beam management carried by the PUSCH in the primary cell;

[0305] 6) CSI reporting for aperiodic, event-triggered beam management carried by PUSCH in the secondary cell;

[0306] 7) Semi-persistent CSI reporting for beam management initiated by the base station on the PUSCH of the primary cell;

[0307] 8) Semi-persistent CSI reporting for beam management initiated by the base station on the PUSCH carried by the secondary cell;

[0308] 9) Semi-persistent, non-beam-managed CSI reporting carried by the PUSCH in the primary cell;

[0309] 10) Semi-persistent, non-beam-managed CSI reporting carried by PUSCH in the secondary cell;

[0310] 11) Semi-persistent CSI reporting for event-triggered beam management carried by PUSCH in the primary cell;

[0311] 12) Semi-persistent CSI reporting for event-triggered beam management carried by PUSCH in the secondary cell;

[0312] 13) Semi-persistent CSI reporting for beam management initiated by the base station on the PUCCH of the primary cell;

[0313] 14) Semi-persistent CSI reporting for beam management initiated by the base station and carried by PUCCH in the secondary cell;

[0314] 15) Semi-persistent, non-beam-managed CSI reporting carried by PUCCH in the primary cell;

[0315] 16) Periodic non-beam management CSI reporting carried by PUCCH in the secondary cell;

[0316] 17) Semi-persistent, event-triggered beam management CSI reporting for the primary cell and carried by PUCCH;

[0317] 18) Semi-persistent CSI reporting for event-triggered beam management carried by PUCCH in the secondary cell;

[0318] 19) Periodic CSI reporting for beam management initiated by the base station for the primary cell and carried by PUCCH;

[0319] 20) Periodic CSI reporting of beam management initiated by the base station for the secondary cell and carried by PUCCH;

[0320] 21) Periodic non-beam management CSI reporting carried by PUCCH in the primary cell;

[0321] 22) Periodic non-beam management CSI reporting carried by PUCCH in the secondary cell;

[0322] 23) Periodic CSI reporting for event-triggered beam management carried by the PUCCH in the primary cell;

[0323] 24) Periodic CSI reporting for event-triggered beam management carried by PUCCH in the secondary cell.

[0324] Method 4:

[0325] In some embodiments, based on methods 1 to 3 above, when two CSI reports partially or completely overlap in the time domain, if both CSI reports are beam-managed CSI and the corresponding k values ​​are different, or if one CSI report is a beam-managed CSI report initiated by the base station 110 and the other CSI report is an event-driven beam-managed CSI report, the user equipment 120 discards the CSI report with a larger Prics value, that is, the user equipment 120 does not report the CSI report with a larger Prics value.

[0326] In particular, when two CSI reports partially or completely overlap in the time domain, if both CSI reports are beam-managed CSI and are periodic reports (i.e., y = 3), and the corresponding k values ​​are different, or if one CSI report is a periodic CSI report for beam management initiated by the base station 110, and the other CSI report is a periodic CSI report for event-driven beam management, the user equipment 120 discards the CSI report with a larger value of Pris, that is, the user equipment 120 does not report the CSI report with a larger value of Pris.

[0327] In some embodiments, event-driven beam reporting is a type of CSI.

[0328] The priority of event-driven beam management CSI reporting over other CSI reporting is determined according to a formula that is related to at least one of the following: the time domain behavior of the CSI reporting, the parameter type of the CSI reporting, the cell index or identifier of the CSI reporting, the configuration index or identifier of the CSI reporting, and the event index or identifier of the CSI reporting.

[0329] The time domain behavior of CSI is related to the reportConfigType configuration in CSI-ReportConfig, including at least one of the following: aperiodic CSI reporting carried by PUSCH, semi-persistent CSI reporting carried by PUSCH, semi-persistent CSI reporting carried by PUCCH, and periodic CSI reporting carried by PUCCH;

[0330] The parameter type of CSI reporting is related to the reportQuantity configuration in CSI-ReportConfig, including at least one of the following: event-driven beam-managed CSI reporting, beam-managed CSI reporting initiated by base station 110, and non-beam-managed CSI reporting.

[0331] The cell index or identifier associated with the CSI report is related to the carrier configuration in the CSI-ReportConfig.

[0332] The configuration index or identifier reported by the CSI is related to the reportConfigId configuration in the CSI-ReportConfig.

[0333] The event index or identifier associated with the CSI report includes the configuration related to the event in CSI-ReportConfig.

[0334] Other CSI reporting refers to CSI reporting in existing standards, including at least beam-managed CSI reporting and non-beam-managed CSI reporting initiated by the base station 110 .

[0335] Specifically, the priority of CSI is determined according to the following formula:

[0336] Pri iCSI (x,y,k,c,s)=Γ1·y+Γ2·k+Γ3·+Γ4·+Γ5·x, where Γ j (j=1, 2, 3, 4, 5) s are all positive integers, y corresponds to the time domain behavior of CSI reporting, k corresponds to the parameter type of CSI reporting, c corresponds to the cell index or identifier, s corresponds to the reporting configuration index or identifier, and x corresponds to the event index or identifier.

[0337] In particular, Γ1 = 2·N cells ·M s ·N events, Γ2=N cells ·M s ·N events , Γ3=M s ·N events , Γ4=N events , Γ5=1, where N cells is the number of cells, configured by the high-level parameter maxNrofServingCells; M s The number of reported configurations is configured by the high-level parameter maxNrofCSI-ReportConfigurations, N events is the number of events, configured by high-level parameters.

[0338] The smaller the Pri value calculated according to the formula, the higher the priority of the CSI.

[0339] The CSI reporting priority can be at least one of the following:

[0340] Method 1:

[0341] The specific y, k, c, and s in the CSI reporting priority formula are:

[0342] Where y=0 corresponds to aperiodic CSI reporting carried by PUSCH, y=1 corresponds to semi-persistent CSI reporting carried by PUSCH, y=2 corresponds to semi-persistent CSI reporting carried by PUCCH, and y=3 corresponds to periodic CSI reporting carried by PUCCH;

[0343] Where k = 0 corresponds to beam-managed CSI reporting, and k = 1 corresponds to non-beam-managed CSI reporting;

[0344] Wherein, c corresponds to the cell index or identity;

[0345] Where s corresponds to the reporting configuration index or identifier;

[0346] Where x=0 corresponds to non-event driven CSI reporting, and x>0 corresponds to an event index or identifier;

[0347] Among them, the CSI reporting of beam management includes the CSI reporting of beam management initiated by the base station and the CSI reporting of beam management driven by events.

[0348] Method 2:

[0349] The specific y, k, c, and s in the CSI reporting priority formula are:

[0350] -y=0 corresponds to aperiodic CSI reporting carried by PUSCH, y=1 corresponds to semi-persistent CSI reporting carried by PUSCH, y=2 corresponds to semi-persistent CSI reporting carried by PUCCH, and y=3 corresponds to periodic CSI reporting carried by PUCCH;

[0351] Where k = 0 corresponds to beam-managed CSI reporting, and k = 1 corresponds to non-beam-managed CSI reporting;

[0352] Wherein, c corresponds to the cell index or identity;

[0353] Where s corresponds to the reporting configuration index or identifier;

[0354] Among them, x <N events Corresponding to the event index or identifier, x=N events Corresponding to non-event-driven CSI reporting;

[0355] Among them, the CSI reporting of beam management includes the CSI reporting of beam management initiated by the base station and the CSI reporting of beam management driven by events.

[0356] Specifically, event-driven beam reporting is a type of CSI. The priority of CSI reporting can adopt at least one of the following:

[0357] Method 1:

[0358] In some embodiments, the priority is a predefined priority, and the predefined priority order is that the priority of the information of the beam is higher than the CSI of layer 1 / layer 2 triggered mobility (LTM), and the priority of the LTM CSI is higher than the other CSI.

[0359] Specifically, if the event-related CSI-ReportConfig collides with other CSI-ReportConfigs and / or LTM-CSI-ReportConfigs, the event-related CSI-ReportConfig has the highest priority.

[0360] If event-CSI-ReportConfig collides with other CSI-ReportConfig and / or LTM-CSI-ReportConfig, event-CSI-ReportConfig takes precedence.

[0361] Method 2:

[0362] In some embodiments, the priority is a predefined priority, and the predefined priority order is that the priority of the LTM CSI is higher than the information of the beam, and the priority of the information of the beam is higher than the other CSI.

[0363] Specifically, if the event-related CSI-ReportConfig collides with the LTM-CSI-ReportConfig, the event-related CSI-ReportConfig has a lower priority.

[0364] If an event-related CSI-ReportConfig collides with another CSI-ReportConfig, the event-related CSI-ReportConfig has a higher priority.

[0365] If event-CSI-ReportConfig conflicts with LTM-CSI-ReportConfig, event-CSI-ReportConfig takes a lower priority.

[0366] If event-CSI-ReportConfig collides with other CSI-ReportConfig, event-CSI-ReportConfig takes precedence.

[0367] Option 3:

[0368] In some embodiments, the priority is a predefined priority, and the predefined priority order is that the priority of the LTM CSI is higher than the other CSI, and the priority of the other CSI is higher than the information of the beam.

[0369] Specifically, if the event-related CSI-ReportConfig collides with other CSIs and / or LTM CSIs, the event-related CSI-ReportConfig has the lowest priority.

[0370] If event-CSI-ReportConfig collides with other CSIs and / or LTM CSIs, event-CSI-ReportConfig has the lowest priority.

[0371] In some embodiments, the priority between event-driven beam management CSI reporting and other CSI reporting is predefined, and the priority of several event-driven beam management CSI reports is determined based on a formula.

[0372] In some embodiments, the formula is related to at least one of the following: a cell index or identifier of CSI reporting, a configuration index or identifier of CSI reporting, and an event index or identifier of CSI reporting.

[0373] Specifically, the formula is related to at least one of the following: a cell index or identifier of CSI reporting, a configuration index or identifier of CSI reporting, and an event index or identifier of CSI reporting.

[0374] The priority within the CSI reported by the event-driven beam is determined according to at least one of the following formulas:

[0375] Method 1:

[0376] Pri iEvent (c,s)=Γ3·c+Γ4·s, where Γ j (j=3,4) are all positive integers. In particular, Γ3=M s , Γ4=1,M s It is the number of reported configurations, which is configured by the high-level parameter maxNrofCSI-ReportConfigurations.

[0377] Wherein, c corresponds to the cell index or identity;

[0378] Where s corresponds to the reporting configuration index or identifier;

[0379] Method 2:

[0380] Pri iEvent (z,c,s)=Γ3·c+Γ4·z, where Γ j (j=3,4) are all positive integers. In particular, Γ3=L events , Γ4=1,L events Configured by the high-level parameter maxNrofEvents.

[0381] Wherein, c corresponds to the cell index or identity;

[0382] Where z corresponds to the index or identifier of the triggering event.

[0383] In some embodiments, when the information reporting of the event-driven beam collides with the information reporting of the traditional beam, or when the resources of the information reporting of the event-driven beam and the information reporting of the traditional beam are in the same time window, or when the information reporting of the event-driven beam and the information reporting of the traditional beam are multiplexed, where the information reporting of the event-driven beam and the information reporting of the traditional beam belong to the same cell, the user equipment 120 does not report the event-driven beam reporting and the beam reporting initiated by the base station at the same time, or discards the information reporting of one of the beams according to priority or according to predefined rules.

[0384] Specifically, the event-driven beam reporting is one of CSI, UCI or MAC CE.

[0385] Time windows are predefined or configured by high-level parameters.

[0386] The predefined drop rule is at least one of the following:

[0387] Method 1:

[0388] The user equipment 120 discards the event-driven beam reporting, that is, the user equipment 120 does not report the event-driven beam reporting.

[0389] Method 2:

[0390] The user equipment 120 discards the regular beam reporting, that is, the user equipment 120 does not report the regular beam reporting.

[0391] In particular, it is considered that event-driven beam reporting is usually performed on a periodic reference signal. When the event-driven beam reporting collides with the beam reporting initiated by the base station 110, or when the resources of the event-driven beam reporting and the periodic beam reporting initiated by the base station 110 are in the same time window, or when the event-driven beam reporting and the resources of the periodic beam reporting initiated by the base station 110 are multiplexed, wherein the event-driven beam reporting and the periodic beam reporting initiated by the base station 110 belong to the same cell, the user equipment 120 does not report the event-driven beam reporting and the periodic beam reporting initiated by the base station 110 at the same time, or discards one of the beam reports according to priority or according to predefined rules. Since the periodic beam reporting initiated by the base station 110 is usually also performed on a periodic reference signal, the reporting contents of the two are likely to be the same, so reporting only one of them can save reporting overhead.

[0392] In some embodiments, event-driven beam reporting (EDBR) is a type of uplink control information (UCI). Therefore, the UCI bit sequence includes at least one of the following: HARQ bits, SR bits, CSI bits, and EDBR bits.

[0393] When UCI is transmitted on the physical uplink control channel PUCCH, the order of the UCI bit sequence and the length of the bit sequence need to be defined.

[0394] Case 1: No CSI report has two parts.

[0395] The order of the UCI bit sequence is:

[0396] Alt 1: The order of the UCI bit sequence is: HARQ bit → SR bit → EDBR bit → CSI bit, that is, the EDBR bit comes after the SR bit and before the CSI bit.

[0397] Alt 2: The order of the UCI bit sequence is: HARQ bit → SR bit → CSI bit → EDBR bit, that is, the EDBR bit comes after the CSI bit.

[0398] The length of the UCI bit sequence is shown in Table 5:

[0399] Table 5: UCI bit sequence length

[0400] Among them E UCI Indicates the length of the UCI bit sequence, E tot Indicates the length of the bit sequence after rate matching.

[0401] Case 2: At least one CSI report has two parts, and the EDBR bits are in the first UCI sequence.

[0402] The order of the UCI bit sequence is:

[0403] Alt 1: The order of the first UCI bit sequence is: HARQ bits → SR bits → EDBR bits → CSI-part1 bits. That is, the EDBR bits are in the first UCI sequence, after the SR bits and before the CSI-part1 bits. The order of the second UCI bit sequence is: CSI-part2 bits.

[0404] Alt 2: The order of the first UCI bit sequence is: HARQ bits → SR bits → CSI-part1 bits → EDBR bits. That is, the EDBR bits are in the first UCI sequence and follow the CSI-part1 bits. The order of the second UCI bit sequence is: CSI-part2 bits.

[0405] The length of the UCI bit sequence is shown in Table 6:

[0406] Table 6: UCI bit sequence length

[0407] Among them, E UCI Indicates the length of the UCI bit sequence, E tot Indicates the length of the bit sequence after rate matching, O ACK Indicates the number of HARQ bits, O SR Indicates the number of bits of SR, O CSI-part1 Indicates the number of bits in CSI part 1, Indicates the bit rate, Q m represents the modulation order, and L represents the number of CRC check bits.

[0408] Case 3: At least one CSI report has two parts, and the EDBR bits are in the second UCI sequence.

[0409] The order of the UCI bit sequence is:

[0410] Alt 1: The order of the first UCI bit sequence is: HARQ bits → SR bits → CSI-part 1 bits. The order of the second UCI bit sequence is: EDBR bits → CSI-part 2 bits, that is, EDBR bits are in the second UCI sequence and before CSI-part 2 bits.

[0411] Alt 2: The order of the first UCI bit sequence is: HARQ bits → SR bits → CSI-part 1 bits. The order of the second UCI bit sequence is: CSI-part 2 bits → EDBR bits. That is, the EDBR bits are in the second UCI sequence and after the CSI-part 2 bits.

[0412] The length of the UCI bit sequence is shown in Table 7:

[0413] Table 7: UCI bit sequence length

[0414] Among them E UCI Indicates the length of the UCI bit sequence, E tot Indicates the length of the bit sequence after rate matching, O ACK Indicates the number of HARQ bits, O SR Indicates the number of bits of SR, O CSI-part1 Indicates the number of bits in CSI part 1, Indicates the bit rate, Q m represents the modulation order, and L represents the number of CRC check bits.

[0415] In some embodiments, event-driven beam reporting (EDBR) is a type of UCI. Therefore, the UCI bit sequence includes at least one of the following: HARQ bits, SR bits, CSI bits, and EDBR bits.

[0416] When EDBR and SR are transmitted on PUCCH, the multiplexing of EDBR and SR is as follows:

[0417] The number of bits of EDBR is 0 EDBR (usually greater than 2 bits) and is carried by PUCCH format 2 / 3 / 4. SR is carried by PUCCH format 1. When the PUCCH resources carrying K SRs overlap with the PUCCH resources carrying EDBR, SR will be multiplexed onto the PUCCH resources for beam prediction information. The total number of bits of these two types of UCI is

[0418] When EDBR and SR are transmitted on PUCCH, EDBR is multiplexed with HARQ (if any), SR (if any), and CSI (if any):

[0419] When different PUCCH resources carrying EDBR, HARQ (if any), SR (if any), and CSI (if any) overlap, the set of these PUCCH resources is first obtained according to the resource selection rules in the existing standard, and then the PUCCH for transmission is selected from the set of PUCCH resources according to the sum of the number of bits of EDBR, HARQ (if any), SR (if any), CSI (if any) and CRC.

[0420] In some embodiments, event-driven beam reporting (EDBR) is a type of UCI. Therefore, the UCI bit sequence includes at least one of the following: HARQ bits, SR bits, CSI bits, and EDBR bits.

[0421] When UCI is transmitted on the PUSCH, the calculation order of the coded modulation symbols of the UCI and the resource mapping order need to be defined.

[0422] Alt 1:

[0423] The calculation order of coded modulation symbols is: HARQ → EDBR → CSI-part1 → CSI-part2.

[0424] The number of coded modulation symbols in HARQ is the same as that in existing standards.

[0425] Number of coded modulation symbols for EDBR

[0426] Among them O EDBR Indicates the number of EDBR bits, L EDBR Indicates the number of bits of EDBR CRC check. Indicates the rate compensation factor of EDRA, Indicates the number of subcarriers on symbol l that can be used to carry UCI, Indicates the number of REs that can be used by PUSCH to carry UCI. Indicates the payload size of uplink data.

[0427] Number of coded modulation symbols in CSI-part1

[0428] Number of coded modulation symbols in CSI-part2

[0429] Resource mapping order:

[0430] HARQ bits are mapped to the partial resources of the first symbol after the first DMRS of PUSCH; EDBR bits are mapped starting from the first non-DMRS symbol of PUSCH; after the EDBR bits are mapped, CSI-part1 bits are mapped next to the EDBR resources; after the CSI-part1 bits are mapped, CSI-part2 bits are mapped next; the mapping of EDBR, CSI-part1, and CSI-part2 bits skips DMRS symbols.

[0431] Alt 2:

[0432] The calculation / allocation order of coded modulation symbols is: HARQ → CSI-part1 → EDBR → CSI-part2.

[0433] The number of coded modulation symbols for HARQ and CSI-part 1 is the same as that in the existing standard.

[0434] Number of coded modulation symbols for EDBR

[0435] Among them, O EDBR Indicates the number of EDBR bits, L EDBR Indicates the number of EDBR CRC check bits.

[0436] Number of coded modulation symbols in CSI-part2

[0437] Resource mapping order:

[0438] HARQ bits are mapped to the partial resources of the first symbol after the first DMRS of PUSCH; CSI-part1 bits are mapped starting from the first non-DMRS symbol of PUSCH; after the CSI-part1 bits are mapped, the EDBR bits are mapped next; after the EDBR bits are mapped, the CSI-part2 bits are mapped next to the EDBR resources; the mapping of EDBR, CSI-part1, and CSI-part2 bits skips the DMRS symbol.

[0439] Alt 3:

[0440] The calculation / allocation order of coded modulation symbols is: HARQ → CSI-part1 → CSI-part2 → EDBR.

[0441] The number of coded modulation symbols for HARQ, CSI-part1, and CSI-part2 is the same as that in existing standards.

[0442] Number of coded modulation symbols for EDBR

[0443] Among them O EDBR Indicates the number of EDBR bits, L EDBR Indicates the number of EDBR CRC check bits.

[0444] When UCI is transmitted on PUSCH,

[0445] Resource mapping order:

[0446] HARQ bits are mapped to part of the resources of the first symbol after the first DMRS of PUSCH; CSI-part1 bits are mapped starting from the first non-DMRS symbol of PUSCH; after the CSI-part1 bits are mapped, the CSI-part2 bits are mapped next; after the CSI-part2 bits are mapped, the EDBR bits are mapped next; the mapping of EDBR, CSI-part1, and CSI-part2 bits skips DMRS symbols.

[0447] In some embodiments, event-driven beam reporting (EDBR) is a type of UCI.

[0448] If an EDBR is associated with only one event, the uplink resources of the EDBRs associated with different events are different and may overlap in the time domain.

[0449] When UCI is multiplexed on PUCCH or PUSCH, the order of EDBR bits related to different events needs to be defined.

[0450] The order of EDBR bits: EDBR bits associated with the first event → EDBR bits associated with the second event → EDBR bits associated with the third event → ...

[0451] Alt 1: Sort by event index size

[0452] The first event is the event with index 1, the second event is the event with index 2, the third event is the event with index 3, and so on.

[0453] Alt 2: Sort by event priority

[0454] The first event has a higher priority than the second event, the second event has a higher priority than the third event...

[0455] Alt 3: Arrange in order of event triggering time

[0456] The first event is triggered earlier than the second event, the second event is triggered earlier than the third event...

[0457] Described herein is a beam reporting method applicable to, for example, communications between user equipment 120 and base station 110. However, these inventive concepts, methods, apparatuses, devices, computer-readable storage media, chips, and computer program products are not limited to 5G communications and can also be extended to other communication scenarios, such as 6G, to achieve the same technical benefits and effects.

[0458] In these scalable communication scenarios, a communication device can be a user equipment 120 (UE), a base station 110 (such as a gNB, eNodeB, transmission reception point (TRP), a next-generation communication NodeB, or a Wi-Fi access point), or an entity such as a network element. A user equipment (UE) refers to a device used for communication at the user end, such as a mobile phone. It can also be called a terminal, mobile station, or mobile terminal. User equipment 120 can be a variety of devices, including but not limited to mobile phones, tablets, virtual reality (VR) devices, augmented reality (AR) devices, wireless terminals for industrial control, wireless terminals for autonomous driving, wireless terminals for telemedicine, wireless terminals for smart grids, wireless terminals for environmental monitoring, wireless terminals for smart cities, and wireless terminals for smart homes.

[0459] Furthermore, the user equipment 120 and the base station 110 may be deployed in different environments, including but not limited to indoors, outdoors, as handheld devices, in vehicles, or even on water, in the air, on airplanes, drones, or satellites.

[0460] Therefore, although this document describes methods and devices for beam reporting, the inventive concepts and technologies contained therein can be extended to other communication scenarios and are expected to achieve the same technical benefits and effects. It is easy to understand that these inventive concepts have broad applicability and scalability, whether in communications between different types of base stations 110 and user equipment 120, or in communications in different deployment environments.

[0461] It should be noted that the above steps are merely examples and do not limit the scope of the present invention. Various modifications and variations can be made to the steps without departing from the spirit and scope of the present invention.

[0462] The order of the described steps (signaling / boxes) is not intended to be construed as a limitation, and any number of the described steps (signaling / boxes) may be skipped or combined in any order to implement a method or an alternative method.

[0463] The present disclosure describes examples of communication between terminals and network element components in a network architecture in the above embodiments, which are mainly for illustrative purposes and not restrictive.

[0464] The order of the steps (signaling / boxes) described is not intended to be interpreted as limiting, and any number of the steps (signaling / boxes) described can be skipped or combined in any order to implement a method or alternative method. Typically, any of the components, modules, methods, and operations described herein can be implemented using software, firmware, hardware (e.g., fixed logic circuitry), manual processing, or any combination thereof. Some operations of the example methods can be described in the general context of executable instructions stored on a computer-readable memory locally and / or remotely on a computer processing system, and implementation methods can include software applications, programs, functions, and the like. Alternatively or in addition, any function described herein can be performed, at least in part, by one or more hardware logic components, such as, but not limited to, a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), an application specific standard product (ASSP), a system on a chip (SoC), a complex programmable logic device (CPLD), and the like.

[0465] In addition, the signaling described in the embodiments of the present disclosure can be implemented in any manner known in the art. For example, the signaling can be explicit and / or implicit. In addition, the steps (signaling / frames) shown are for illustrative purposes only and are not intended to limit the present application.

[0466] FIG4 is a schematic structural diagram of a wireless communication device 900 provided by the present disclosure. The wireless communication device includes: a processor and a memory, the memory is used to store a computer program, and the processor is used to call and execute the computer program stored in the memory, and perform the following operations:

[0467] Receiving an event-driven beam reporting configuration, wherein the event-driven beam reporting configuration includes at least one of the following: measurement resource configuration, reporting resource configuration, event configuration, reporting amount, reporting content configuration, and cell configuration;

[0468] Based on the event-driven beam reporting configuration, at least one of the following is reported: cell information, event information, panel information, and beam information, wherein the beam information includes at least one of the following: the index or identifier of the current beam, the quality value of the current beam, the index or identifier of the new beam, and the quality value of the new beam.

[0469] or

[0470] Sending an event-driven beam reporting configuration, wherein the event-driven beam reporting configuration includes at least one of the following: measurement resource configuration, reporting resource configuration, event configuration, reporting amount, reporting content configuration, and cell configuration;

[0471] Receive at least one of the following: cell information, event information, panel information, and beam information, wherein the beam information includes at least one of the following: the index or identifier of the current beam, the quality value of the current beam, the index or identifier of the new beam, and the quality value of the new beam.

[0472] The wireless communication device may be a user device, a base station, or a network element. The wireless communication device 900 shown in FIG4 includes a processor 910. The processor 910 may call and run a computer program from a memory to implement the method in the embodiment of the present application.

[0473] Optionally, as shown in FIG4 , the wireless communication device 900 may further include a memory 920. The processor 910 may call and execute a computer program from the memory 920 to implement the method in the embodiment of the present application. The memory 920 may be a separate device independent of the processor 910 or may be integrated into the processor 910.

[0474] Optionally, as shown in FIG4 , the wireless communication device 900 may further include a transceiver 930. The processor 910 may control the transceiver 930 to communicate with other devices. Specifically, the transceiver 930 may send information or data to other devices or receive information or data sent by other devices. The transceiver 930 may include a transmitter and a receiver. The transceiver 930 may further include one or more antennas.

[0475] Optionally, the wireless communication device 900 may specifically be a base station in an embodiment of the present application, and the wireless communication device 900 may implement the corresponding processes implemented by the base station in each method in the embodiment of the present application. For the sake of brevity, they will not be repeated here.

[0476] Optionally, the wireless communication device 900 may specifically be a mobile user device / user device in an embodiment of the present application, and the wireless communication device 900 may implement the corresponding processes implemented by the mobile user device / user device in each method of the embodiment of the present application. For the sake of brevity, they will not be repeated here.

[0477] Optionally, the wireless communication device 900 may specifically be a network element in an embodiment of the present application, and the wireless communication device 900 may implement the corresponding processes implemented by the network element in each method in the embodiment of the present application. For the sake of brevity, they will not be repeated here.

[0478] According to an example embodiment, a chip is provided, comprising: a processor for calling and running a computer program from a memory, so that a device equipped with the chip executes a method according to any one of the above embodiments, examples, or exemplary embodiments.

[0479] According to an example embodiment, there is provided a computer-readable storage medium for storing a computer program, wherein the computer program causes a computer to execute a method according to any one of the above-mentioned embodiments, examples, or exemplary embodiments.

[0480] According to an example embodiment, a computer program product is provided, comprising a computer program / instruction, which, when executed by a processor (e.g., by the processor or an apparatus, device, computer or machine including the processor), implements a method according to any one of the above-mentioned embodiments, examples, or example embodiments.

[0481] The embodiments of the present disclosure are a combination of techniques / processes that may be employed in 3GPP specifications to create a final product.

[0482] While the present disclosure has been described in connection with what is considered to be the most practical and preferred embodiment, it is to be understood that the disclosure is not limited to the disclosed embodiment, but is intended to cover various arrangements embodied within the broadest interpretation of the appended claims.

Claims

1. A beam reporting method, executed by a user equipment, comprising: Receiving an event-driven beam reporting configuration, wherein the event-driven beam reporting configuration includes at least one of the following: measurement resource configuration, reporting resource configuration, event configuration, reporting amount, reporting content configuration, and cell configuration; Based on the event-driven beam reporting configuration, at least one of the following is reported: cell information, event information, panel information, and beam information, wherein the beam information includes at least one of the following: the index of the current beam, the quality value of the current beam, the index of the new beam, and the quality value of the new beam.

2. The method according to claim 1, wherein The method further includes reporting at least one of the following when an event occurs: cell information, event information, panel information, and beam information.

3. The method according to claim 1 or 2, wherein: The information element of the event-driven beam reporting configuration adopts the information unit of the channel state information CSI reporting configuration, or adopts the information unit of the independent event measurement reporting configuration.

4. The method according to claim 1 or 2, wherein: The event configuration includes at least one of the following: an event index, a threshold value, an offset value, and a hysteresis value.

5. The method according to claim 1 or 2, wherein: The reporting content configuration includes at least one of the following: configuration of the current beam, configuration of the new beam, configuration of the cell, number of beams reported, and number of cell indexes reported.

6. The method according to claim 5, wherein: The configuration of the current beam includes at least one of the following: whether the current beam index is reported, whether the current beam quality value is reported; the configuration of the new beam includes at least one of the following: whether the new beam index is reported, whether the new beam quality value is reported, the number of reported new beam indexes, and the number of reported new beam quality values; the configuration of the cell includes at least one of the following: whether the cell index is reported, and the number of reported cell indexes.

7. The method according to claim 1 or 2, wherein: The information element of the event-driven beam reporting configuration adopts the information unit of the CSI reporting configuration, and the CSI reporting configuration includes at least one of the following: measurement resource configuration, reporting resource configuration, event configuration, reporting amount, reporting content configuration, and cell configuration.

8. The method according to claim 7, wherein: If the CSI reporting configuration is related to an event, or the reporting configuration index in the CSI reporting configuration is associated with an event index, or the CSI reporting configuration is configured with an event type, the CSI reporting corresponding to the CSI reporting configuration is an event-driven beam-managed CSI reporting.

9. The method according to claim 7, wherein: The higher-layer parameters in the CSI reporting configuration include configuration parameters, wherein the configuration parameters indicate that the CSI reporting corresponding to the CSI reporting configuration is event-driven beam-managed CSI reporting.

10. The method according to claim 1 or 2, wherein: The information element of the event-driven beam reporting configuration adopts the information unit of the event CSI reporting configuration, and the event CSI reporting configuration includes at least one of the following: measurement resource configuration, reporting resource configuration, event configuration, reporting content configuration, and cell configuration.

11. The method according to claim 10, wherein: The event CSI reporting configuration is associated with at least one event type, wherein content related to the event corresponding to the event type is configured by the reporting content.

12. The method according to claim 1 or 2, wherein: The information element of the event-driven beam reporting configuration adopts the information unit of the independent event measurement reporting configuration, and the independent event measurement reporting configuration includes at least one of the following: measurement resource configuration, reporting resource configuration, event configuration, reporting content configuration, and cell configuration.

13. The method according to claim 1, wherein The method further includes quantifying a quality value of the beam, wherein the beam is a current beam or a new beam.

14. The method according to claim 13, wherein The number of bits of the beam quality value is 3, 4, or 5.

15. The method according to claim 13, wherein: The quantifying the quality value of the beam includes: Differentiating the beam quality value from a predefined reference value to obtain a differential value; The difference value is quantized based on the step size and the number of bits.

16. The method according to claim 15, wherein The step size is any of the following: 0.5 or 1 or 2 or 3.

17. The method according to claim 15, wherein: The step size is predefined or configured by a high-level parameter; the number of bits is predefined or configured by a high-level parameter.

18. The method according to claim 15, wherein The reference value includes at least one of the following: an event-related value, a beam quality-related value, a sum of an event-related value and a beam quality-related value, and a difference between an event-related value and a beam quality-related value.

19. The method according to claim 18, wherein The event-related value includes at least one of the following: a threshold value, a hysteresis value, an offset value, the sum of the threshold value and the hysteresis value, the sum of the threshold value and the offset value, the sum of the hysteresis value and the offset value, the difference between the threshold value and the hysteresis value, the difference between the threshold value and the offset value, and the difference between the hysteresis value and the offset value.

20. The method according to claim 15, wherein The step size is an average value.

21. The method according to claim 20, wherein The average value is determined based on a predefined value, the reference value, and the number of bits.

22. The method according to claim 15, wherein If a reporting entity includes quality values ​​of multiple beams, the quality values ​​of the multiple beams are first differentiated and then quantized based on the same reference value.

23. The method according to claim 22, wherein The reference value is an event-related value.

24. The method according to claim 15, wherein If a reporting entity includes quality values ​​of multiple beams, the quality values ​​of the multiple beams are first differentiated and then quantized based on different reference values.

25. The method according to claim 24, wherein The quality value of the best beam is determined based on the quality values ​​of the multiple beams, the quality value of the best beam is first differentiated and then quantized based on the event-related value, and the quality values ​​of other beams except the quality value of the best beam are first differentiated and then quantized based on the quality value of the best beam.

26. The method according to claim 24, wherein The quality value of the worst beam is determined based on the quality values ​​of the multiple beams, the quality value of the worst beam is first differentiated and then quantized based on the event-related value, and the quality values ​​of other beams except the quality value of the worst beam are first differentiated and then quantized based on the quality value of the worst beam. If a reporting entity includes the current beam, the worst beam and the other beams do not include the current beam.

27. The method according to claim 24, wherein When the quality values ​​of the multiple beams are correlated with a first value related to an event, the reference value is the first value related to the event; when the quality values ​​of the multiple beams are correlated with a second value related to an event, the reference value is the second value related to the event.

28. The method according to claim 1, wherein The information of the beam is included in the CSI. The method also includes reporting other CSI, which is traditional CSI. The other CSI includes at least CSI reporting of beam management initiated by the base station and CSI reporting of CSI measurement. The information of the beam and the reporting of the other CSI are based on priority reporting.

29. The method according to claim 28, wherein The priority is determined based on a formula, where the formula is related to at least one of the following: a time domain behavior of CSI reporting, a parameter type of CSI reporting, a cell index associated with CSI reporting, and a configuration index of CSI reporting.

30. The method according to claim 29, wherein The time domain behavior of the CSI is related to the reporting configuration type configuration in the CSI reporting configuration, and the time domain behavior of the CSI includes at least one of the following: non-periodic CSI reporting carried by PUSCH, semi-persistent CSI reporting carried by PUSCH, semi-persistent CSI reporting carried by PUCCH, and periodic CSI reporting carried by PUCCH.

31. The method according to claim 29, wherein The parameter type of CSI reporting is related to the reporting quantity configuration in the CSI reporting configuration, and includes at least one of the following: event-driven beam-managed CSI reporting, base station-initiated beam-managed CSI reporting, and non-beam-managed CSI reporting.

32. The method of claim 29, wherein: The cell index associated with the CSI report is related to the carrier configuration in the CSI reporting configuration.

33. The method of claim 29, wherein: The configuration index of CSI reporting is related to the reporting configuration index configuration in the CSI reporting configuration.

34. The method of claim 29, wherein: The formula is determined based on the parameter type reported by the CSI.

35. The method of claim 28, wherein The priority is determined based on a formula, where the formula is related to at least one of the following: a time domain behavior of CSI reporting, a parameter type of CSI reporting, a cell index associated with CSI reporting, a configuration index of CSI reporting, and an event index of CSI reporting.

36. The method of claim 28, wherein The priority is a predefined priority, and the predefined priority order is that the priority of the beam information is higher than the CSI of the mobility LTM triggered by layer 1 / layer 2, and the priority of the LTM CSI is higher than the other CSI.

37. The method of claim 28, wherein: The priority is a predefined priority, and the predefined priority order is that the priority of the LTM CSI is higher than the information of the beam, and the priority of the beam information is higher than the other CSI.

38. The method of claim 28, wherein The priority is a predefined priority, and the predefined priority order is that the priority of the LTM CSI is higher than the other CSI, and the priority of the other CSI is higher than the information of the beam.

39. The method of claim 28, wherein The priority between event-driven beam management CSI reporting and other CSI reporting is predefined, and the priority of several event-driven beam management CSI reports is determined based on a formula.

40. The method of claim 39, wherein The formula is related to at least one of the following: a cell index of CSI reporting, a configuration index of CSI reporting, and an event index of CSI reporting.

41. The method of claim 1, wherein When the information reporting of the event-driven beam collides with the information reporting of the traditional beam, or when the resources of the information reporting of the event-driven beam and the information reporting of the traditional beam are in the same time window, or when the information reporting of the event-driven beam and the information reporting of the traditional beam are multiplexed, where the information reporting of the event-driven beam and the information reporting of the traditional beam belong to the same cell, the user equipment discards the information reporting of one of the beams according to priority or according to predefined rules.

42. A wireless communication device, wherein: The wireless communication device includes: a processor and a memory, the memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to execute the method according to any one of claims 1 to 41.

43. A beam reporting method, executed by a base station, the method comprising: Sending an event-driven beam reporting configuration, wherein the event-driven beam reporting configuration includes at least one of the following: measurement resource configuration, reporting resource configuration, event configuration, reporting amount, reporting content configuration, and cell configuration; Receive at least one of the following: cell information, event information, panel information, and beam information, wherein the beam information includes at least one of the following: an index of a current beam, a quality value of a current beam, an index of a new beam, and a quality value of a new beam.

44. The method according to claim 43, wherein The method further includes receiving at least one of the following when an event occurs: cell information, event information, panel information, and beam information.

45. The method according to claim 43 or 44, wherein The information element of the event-driven beam reporting configuration adopts the information unit of the channel state information CSI reporting configuration, or adopts the information unit of the independent event measurement reporting configuration.

46. ​​The method according to claim 43 or 44, wherein The event configuration includes at least one of the following: an event index, a threshold value, an offset value, and a hysteresis value.

47. The method according to claim 43 or 44, wherein The reporting content configuration includes at least one of the following: configuration of the current beam, configuration of the new beam, configuration of the cell, number of beams reported, and number of cell indexes reported.

48. The method of claim 47, wherein The configuration of the current beam includes at least one of the following: whether the current beam index is reported, whether the current beam quality value is reported; the configuration of the new beam includes at least one of the following: whether the new beam index is reported, whether the new beam quality value is reported, the number of reported new beam indexes, and the number of reported new beam quality values; the configuration of the cell includes at least one of the following: whether the cell index is reported, and the number of reported cell indexes.

49. The method according to claim 43 or 44, wherein The information element of the event-driven beam reporting configuration adopts the information unit of the CSI reporting configuration, and the CSI reporting configuration includes at least one of the following: measurement resource configuration, reporting resource configuration, event configuration, reporting amount, reporting content configuration, and cell configuration.

50. The method of claim 49, wherein If the CSI reporting configuration is related to an event, or the reporting configuration index in the CSI reporting configuration is associated with an event index, or the CSI reporting configuration is configured with an event type, the CSI reporting corresponding to the CSI reporting configuration is an event-driven beam-managed CSI reporting.

51. The method of claim 49, wherein The higher-layer parameters in the CSI reporting configuration include configuration parameters, wherein the configuration parameters indicate that the CSI reporting corresponding to the CSI reporting configuration is event-driven beam-managed CSI reporting.

52. The method according to claim 43 or 44, wherein The information element of the event-driven beam reporting configuration adopts the information unit of the event CSI reporting configuration, and the event CSI reporting configuration includes at least one of the following: measurement resource configuration, reporting resource configuration, event configuration, reporting content configuration, and cell configuration.

53. The method of claim 52, wherein: The event CSI reporting configuration is associated with at least one event type, wherein content related to the event corresponding to the event type is configured by the reporting content.

54. The method according to claim 43 or 44, wherein The information element of the event-driven beam reporting configuration adopts the information unit of the independent event measurement reporting configuration, and the independent event measurement reporting configuration includes at least one of the following: measurement resource configuration, reporting resource configuration, event configuration, reporting content configuration, and cell configuration.

55. The method of claim 43, wherein The method further includes quantifying a quality value of the beam, wherein the beam is a current beam or a new beam.

56. The method of claim 55, wherein: The number of bits of the beam quality value is 3, 4, or 5.

57. The method of claim 55, wherein: The quantifying the quality value of the beam includes: Differentiating the beam quality value from a predefined reference value to obtain a differential value; The difference value is quantized based on the step size and the number of bits.

58. The method of claim 57, wherein The step size is any of the following: 0.5 or 1 or 2 or 3.

59. The method of claim 57, wherein The step size is predefined or configured by a high-level parameter; the number of bits is predefined or configured by a high-level parameter.

60. The method of claim 57, wherein The reference value includes at least one of the following: an event-related value, a beam quality-related value, a sum of an event-related value and a beam quality-related value, and a difference between an event-related value and a beam quality-related value.

61. The method of claim 60, wherein: The event-related value includes at least one of the following: a threshold value, a hysteresis value, an offset value, the sum of the threshold value and the hysteresis value, the sum of the threshold value and the offset value, the sum of the hysteresis value and the offset value, the difference between the threshold value and the hysteresis value, the difference between the threshold value and the offset value, and the difference between the hysteresis value and the offset value.

62. The method of claim 57, wherein: The step size is an average value.

63. The method of claim 62, wherein: The average value is determined based on a predefined value, the reference value, and the number of bits.

64. The method of claim 57, wherein If a reporting entity includes quality values ​​of multiple beams, the quality values ​​of the multiple beams are first differentiated and then quantized based on the same reference value.

65. The method of claim 64, wherein The reference value is an event-related value.

66. The method of claim 57, wherein If a reporting entity includes quality values ​​of multiple beams, the quality values ​​of the multiple beams are first differentiated and then quantized based on different reference values.

67. The method of claim 66, wherein The quality value of the best beam is determined based on the quality values ​​of the multiple beams, the quality value of the best beam is first differentiated and then quantized based on the event-related value, and the quality values ​​of other beams except the quality value of the best beam are first differentiated and then quantized based on the quality value of the best beam.

68. The method of claim 66, wherein The quality value of the worst beam is determined based on the quality values ​​of the multiple beams, the quality value of the worst beam is first differentiated and then quantized based on the event-related value, and the quality values ​​of other beams except the quality value of the worst beam are first differentiated and then quantized based on the quality value of the worst beam. If a reporting entity includes the current beam, the worst beam and the other beams do not include the current beam.

69. The method of claim 66, wherein When the quality values ​​of the multiple beams are correlated with a first value related to an event, the reference value is the first value related to the event; when the quality values ​​of the multiple beams are correlated with a second value related to an event, the reference value is the second value related to the event.

70. The method of claim 43, wherein The information of the beam is included in the CSI. The method also includes receiving other CSI, which is traditional CSI. The other CSI at least includes CSI reporting for beam management initiated by the base station and CSI reporting for CSI measurement. The reception of the beam information and the other CSI is based on priority reception.

71. The method of claim 70, wherein The priority is determined based on a formula, where the formula is related to at least one of the following: a time domain behavior of CSI reporting, a parameter type of CSI reporting, a cell index associated with CSI reporting, and a configuration index of CSI reporting.

72. The method of claim 71, wherein The time domain behavior of the CSI is related to the reporting configuration type configuration in the CSI reporting configuration, and the time domain behavior of the CSI includes at least one of the following: aperiodic CSI reporting carried by PUSCH, semi-persistent CSI reporting carried by PUSCH, semi-persistent CSI reporting carried by PUCCH, and periodic CSI reporting carried by PUCCH.

73. The method of claim 71, wherein The parameter type of CSI reporting is related to the reporting quantity configuration in the CSI reporting configuration, and includes at least one of the following: event-driven beam-managed CSI reporting, base station-initiated beam-managed CSI reporting, and non-beam-managed CSI reporting.

74. The method of claim 71, wherein The cell index associated with the CSI report is related to the carrier configuration in the CSI reporting configuration.

75. The method of claim 71, wherein The configuration index of CSI reporting is related to the reporting configuration index configuration in the CSI reporting configuration.

76. The method of claim 71, wherein The formula is determined based on the parameter type reported by the CSI.

77. The method of claim 70, wherein The priority is determined based on a formula, where the formula is related to at least one of the following: a time domain behavior of CSI reporting, a parameter type of CSI reporting, a cell index associated with CSI reporting, a configuration index of CSI reporting, and an event index of CSI reporting.

78. The method of claim 70, wherein The priority is a predefined priority, and the predefined priority order is that the priority of the beam information is higher than the CSI of the mobility LTM triggered by layer 1 / layer 2, and the priority of the LTM CSI is higher than the other CSI.

79. The method of claim 70, wherein The priority is a predefined priority, and the predefined priority order is that the priority of the LTM CSI is higher than the information of the beam, and the priority of the beam information is higher than the other CSI.

80. The method of claim 70, wherein The priority is a predefined priority, and the predefined priority order is that the priority of the LTM CSI is higher than the other CSI, and the priority of the other CSI is higher than the information of the beam.

81. The method of claim 70, wherein The priority between event-driven beam management CSI reporting and other CSI reporting is predefined, and the priority of several event-driven beam management CSI reports is determined based on a formula.

82. The method of claim 81, wherein The formula is related to at least one of the following: a cell index of CSI reporting, a configuration index of CSI reporting, and an event index of CSI reporting.

83. A wireless communication device, wherein: The wireless communication device includes: a processor and a memory, the memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to execute the method as described in any one of claims 43 to 82.

Images