Event-driven beam management method and apparatus

Abstract

Provided in the embodiments of the present application are an event-driven beam management method and apparatus. The method comprises: a terminal device receiving configuration information sent by a network device, wherein the configuration information comprises first configuration information, and the first configuration information comprises a measurement signal resource set for detecting an event-driven beam management event; and the terminal device using the measurement signal resource set to perform beam management event detection, and sending aperiodic CSI after information triggering the reporting of aperiodic CSI for event-driven beam management is received, wherein the aperiodic CSI comprises beam management information. According to the embodiments of the present application, a network device pre-configures a measurement signal resource set for detecting an event-driven beam management event, and a terminal device uses the measurement signal resource set to detect the event-driven beam management event and reports event-driven beam management information by means of aperiodic CSI, thereby effectively reducing the delay of beam management, reducing signaling overheads, and improving network coverage.

Description

Event-driven beam management method and device Technical Field

[0001] The embodiments of the present application relate to the field of communication technologies. Background Art

[0002] High-band millimeter wave communication is one of the key technical directions of 5G NR (fifth-generation new wireless). Compared to low-band communications, such as those in the sub-6 GHz band, high-band communications face challenges such as high transmission path loss and susceptibility to obstruction. To overcome these challenges, the transmitter uses a large number of densely distributed antenna units and uses beamforming to form beams pointing in specific directions to improve coverage. Correspondingly, the receiver uses beamforming to receive beams in specific directions. This requires the transmitter to select an appropriate transmit beam and the receiver to select an appropriate receive beam to form a beam pair, which together maintain a good wireless link. Beam Management (BM) can establish and maintain such beam pairs.

[0003] In the beam management process of traditional communication systems (3GPP Rel-15 to Rel-18, Release 15 to Release 18 of the Third Generation Partnership Project), the network configures or activates frequent periodic or semi-persistent beam reporting, or triggers frequent aperiodic beam reporting, in order to obtain beam information related to data transmission in a timely manner. However, this method results in large control signaling overhead and reporting overhead. However, if the configured beam reporting frequency is low, the beam information reported by the UE (user equipment, also known as terminal equipment, user, terminal, etc.) may be outdated, and the network may not always obtain the "best or preferred" beam, resulting in degraded system performance.

[0004] Furthermore, beam management in traditional communication systems (3GPP Rel-15 to Rel-18) is primarily initiated by the base station. The base station configures a reference signal (RS) for beam management for the terminal. The terminal then reports its measurement results. The base station then decides whether to initiate beam management based on the terminal's measurement results and sends relevant signaling. The base station then performs the corresponding beam management operations based on the signaling. This type of beam management results in high signaling overhead, long latency, and significantly limited flexibility.

[0005] It should be noted that the above introduction to the technical background is only for the convenience of providing a clear and complete description of the technical solutions of this application and for the convenience of understanding by those skilled in the art. It cannot be considered that the above technical solutions are well known to those skilled in the art simply because these solutions are explained in the background technology part of this application.

[0006] Summary of the Invention

[0007] The inventors discovered that in 3GPP Rel-19, UE-initiated or event-driven beam management (hereinafter referred to as event-driven beam management) has been identified as one of the project contents. Since the UE can obtain better and more timely beam information, in event-driven beam management, the UE can monitor the downlink beam quality. When an event related to beam management is detected, it can actively initiate a beam management (such as beam switching) request to the base station. This can reduce reporting overhead while reporting beams more timely, effectively reducing the delay of beam management, reducing signaling overhead, and improving network coverage.

[0008] Currently, standardization work on event-driven beam management has not yet begun. Therefore, current aperiodic CSI reporting does not support event-triggered beam management.

[0009] In response to at least one of the above problems or other similar problems, an embodiment of the present application provides an event-driven beam management method and device to reduce the latency of beam management, reduce signaling overhead, and improve network coverage.

[0010] According to one aspect of an embodiment of the present application, an event-driven beam management method is provided, the method comprising:

[0011] The terminal device receives configuration information sent by the network device, where the configuration information includes first configuration information, where the first configuration information includes a measurement signal resource set for detecting an event-driven beam management event;

[0012] The terminal device uses the measurement signal set to detect beam management events, and sends a non-periodic CSI report after receiving information that triggers a non-periodic CSI report for event-driven beam management, where the non-periodic CSI report includes beam management information.

[0013] According to another aspect of an embodiment of the present application, there is provided an event-driven beam management apparatus, configured in a terminal device, the apparatus comprising:

[0014] a receiving unit configured to receive configuration information sent by a network device, wherein the configuration information includes first configuration information, and the first configuration information includes a measurement signal resource set for detecting an event-driven beam management event;

[0015] A sending unit uses the measurement signal set to detect a beam management event, and sends non-periodic CSI after the receiving unit receives information that triggers non-periodic CSI reporting for event-driven beam management, where the non-periodic CSI includes beam management information.

[0016] One of the beneficial effects of the embodiments of the present application is that: according to the embodiments of the present application, the beam management information driven by non-periodic CSI reporting events can effectively reduce the delay of beam management, reduce signaling overhead, and improve network coverage.

[0017] With reference to the following description and accompanying drawings, specific embodiments of the present application are disclosed in detail, indicating the manner in which the principles of the present application can be employed. It should be understood that the embodiments of the present application are not limited in scope. Within the spirit and scope of the appended claims, the embodiments of the present application include many variations, modifications and equivalents.

[0018] Features described and / or illustrated with respect to one embodiment may be used in the same or similar manner in one or more other embodiments, combined with features in other embodiments, or substituted for features in other embodiments.

[0019] It should be emphasized that the term "include / comprising" when used herein refers to the presence of features, integers, steps or components, but does not exclude the presence or addition of one or more other features, integers, steps or components. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] The elements and features described in one figure or one embodiment of the present application can be combined with the elements and features shown in one or more other figures or embodiments. In addition, in the accompanying drawings, similar reference numerals represent corresponding parts in several figures and can be used to indicate corresponding parts used in more than one embodiment.

[0021] FIG1 is a schematic diagram of configuration and triggering related to aperiodic CSI reporting;

[0022] FIG2 is a schematic diagram of the current aperiodic CSI reporting process;

[0023] FIG3 is a schematic diagram assuming that the current aperiodic CSI reporting process is used to report event-driven beam switching information;

[0024] FIG4 is a schematic diagram of an event-driven beam management method according to an embodiment of the present application;

[0025] FIG5 is a schematic diagram of an example of a configured measurement signal resource set and new beam information reported by a terminal device;

[0026] FIG6 is a schematic diagram of another example of a configured measurement signal resource set and new beam information reported by a terminal device;

[0027] FIG7 is a schematic diagram of another example of a configured measurement signal resource set and new beam information reported by a terminal device;

[0028] FIG8 is a schematic diagram of a configuration method for event-driven beam management according to an embodiment of the present application;

[0029] FIG9 is a schematic diagram of an event-driven beam management device according to an embodiment of the present application;

[0030] FIG10 is a schematic diagram of a configuration device based on event-driven beam management according to an embodiment of the present application;

[0031] FIG11 is a schematic diagram of a communication system according to an embodiment of the present application;

[0032] FIG12 is a schematic diagram of the structure of a terminal device according to an embodiment of the present application;

[0033] FIG13 is a schematic diagram of the structure of a network device according to an embodiment of the present application. DETAILED DESCRIPTION

[0034] The above and other features of the present application will become apparent through the following description with reference to the accompanying drawings. In the description and the accompanying drawings, specific embodiments of the present application are disclosed in detail, which illustrate some embodiments in which the principles of the present application can be adopted. It should be understood that the present application is not limited to the described embodiments. On the contrary, the present application includes all modifications, variations and equivalents that fall within the scope of the appended claims.

[0035] In the embodiments of the present application, the terms "first", "second", etc. are used to distinguish different elements from the name, but do not indicate the spatial arrangement or temporal order of these elements, and these elements should not be limited by these terms. The term "and / or" includes any one and all combinations of one or more of the associated listed terms. The terms "comprising", "including", "having", etc. refer to the presence of the stated features, elements, components or components, but do not exclude the presence or addition of one or more other features, elements, components or components.

[0036] In the embodiments of this application, the singular forms "a," "the," etc. include plural forms and should be broadly understood to mean "a" or "a type" rather than being limited to "one." Furthermore, the term "said" should be understood to include both singular and plural forms, unless the context clearly indicates otherwise. Furthermore, the term "according to" should be understood to mean "at least in part based on...", and the term "based on" should be understood to mean "at least in part based on...", unless the context clearly indicates otherwise.

[0037] In the embodiments of the present application, the term "communication network" or "wireless communication network" may refer to a network that complies with any of the following communication standards, such as Long Term Evolution (LTE), enhanced Long Term Evolution (LTE-A, LTE-Advanced), Wideband Code Division Multiple Access (WCDMA, Wideband Code Division Multiple Access), High-Speed ​​Packet Access (HSPA, High-Speed ​​Packet Access), 5G (5Generation) New Radio (NR, New Radio), etc.

[0038] Furthermore, communication between devices in the communication system may be carried out according to communication protocols of any stage, for example including but not limited to the following communication protocols: 1G, 2G, 2.5G, 2.75G, 3G, 4G, 4.5G and 5G new wireless, etc., and / or other communication protocols currently known or to be developed in the future.

[0039] In the embodiments of the present application, the term "network device" refers to, for example, a device in a communication system that connects a terminal device to the communication network and provides services to the terminal device. Network devices may include, but are not limited to, the following devices: base station (BS), access point (AP), transmission reception point (TRP), broadcast transmitter, mobile management entity (MME), gateway, server, radio network controller (RNC), base station controller (BSC), etc.

[0040] Base stations may include, but are not limited to, NodeB (NB), evolved NodeB (eNodeB or eNB), and 5G base stations (gNB), among others. They may also include remote radio heads (RRHs), remote radio units (RRUs), relays, or low-power nodes (e.g., femeto, pico, etc.). The term "base station" may include some or all of their functions, and each base station may provide communication coverage for a specific geographic area. The term "cell" may refer to a base station and / or its coverage area, depending on the context in which the term is used.

[0041] In the embodiments of the present application, the term "user equipment" (UE) or "terminal equipment" (TE) refers to, for example, a device that accesses a communication network through a network device and receives network services. A terminal device can be fixed or mobile and may also be referred to as a mobile station (MS), a terminal, a subscriber station (SS), an access terminal (AT), a station, and so on.

[0042] Among them, terminal devices may include but are not limited to the following devices: cellular phones, personal digital assistants (PDAs), wireless modems, wireless communication devices, handheld devices, machine-type communication devices, laptop computers, cordless phones, smart phones, smart watches, digital cameras, etc.

[0043] For another example, in scenarios such as the Internet of Things (IoT), the terminal device can also be a machine or device for monitoring or measurement, including but not limited to: machine type communication (MTC) terminal, vehicle-mounted communication terminal, device-to-device (D2D) terminal, machine-to-machine (M2M) terminal, and so on.

[0044] In addition, the term "network side" or "network device side" refers to one side of the network, which can be a base station or one or more network devices as described above. The term "user side" or "terminal side" or "terminal device side" refers to the user or terminal side, which can be a UE or one or more terminal devices as described above. Unless otherwise specified herein, "device" can refer to either network equipment or terminal equipment.

[0045] To facilitate understanding, some concepts involved in the embodiments of this application are explained below.

[0046] In the following description, "xxx resource" corresponds to an information element / field containing "resource" but not "set / Config," such as NZP-CSI-RS-Resource and SRS-Resource. Each resource has a corresponding ID. "xxx resource set" corresponds to an information element / field containing "xxxResourceSet," such as CSI-SSB-ResourceSet, NZP-CSI-RS-ResourceSet, and SRS-ResourceSet. Each resource set has a corresponding ID, such as CSI-SSB-ResourceSetId. "xxx resource list" corresponds to "xxxResourceToAddModList," such as nzp-CSI-RS-ResourceToAddModList and CSI-SSB-ResourceToAddModList. List elements can be either resources or resource IDs. The "xxx resource set list" corresponds to xxxResourceSetToAddModList, such as nzp-CSI-RS-ResourceSetToAddModList and csi-SSB-ResourceSetToAddModList. List elements can be resource sets or resource set IDs. "Resource collection" is a general term that can refer to the aforementioned "xxx resource set," "xxx resource list," or "xxx resource set list," depending on the context.

[0047] A Scheduling Request (SR) is a type of Uplink Control Information (UCI) sent by the UE to the gNB via the Physical Uplink Control Channel (PUCCH) to request uplink resources from the network. Radio Resource Control (RRC) pre-configures dedicated periodic PUCCH resources, which the UE uses to send SRs on the PUCCH.

[0048] Channel State Information (CSI) is also a type of UCI. The UE feeds back CSI to the base station in the form of a CSI report, which can provide the base station with the parameters required for transmission. The relevant resources for CSI reporting are configured by the high-level parameter CSI-ReportConfig, and the specific CSI reporting content is configured by the reportQuantity field in CSI-ReportConfig. For example, reportQuantity can be configured as:

[0049] 'cri-RSRP' feedback includes the CSI-RS Resource Indicator (CRI) and Layer 1 Reference Signal Receiving Power (L1-RSRP), which are beam index information and beam quality information, respectively. It can be used for CSI-RS-based beam management.

[0050] 'ssb-Index-RSRP': This feedback includes the Synchronization Signal Block Resource Indicator (SSBRI) and L1-RSRP, which are beam index information and beam quality information, respectively. This can be used for SSB-based beam management.

[0051] ●And so on.

[0052] Currently, the configuration related to CSI reporting is primarily determined by the high-level parameter CSI-ReportConfig. In the following description, "CSI reporting configuration" refers specifically to CSI-ReportConfig, unless otherwise specified. Depending on the parameters representing the time domain characteristics in CSI-ReportConfig, CSI reporting can be divided into periodic CSI reporting, semi-persistent CSI reporting, and aperiodic CSI reporting.

[0053] Among them, the non-periodic CSI report is triggered by a combination of MAC-CE and DCI triggering, and is reported through PUSCH (Physical Uplink Shared Channel). Figure 1 is a schematic diagram of the configuration and triggering related to non-periodic CSI reporting. As shown in Figure 1, the base station can configure multiple non-periodic CSI trigger states (CSI-AperiodicTriggerState) for the UE through the high-level parameter CSI-AperiodicTriggerStateList. Each non-periodic trigger state can be associated with one or more CSI reporting configuration information CSI-AssociatedReportConfigInfo, and each CSI-AssociatedReportConfigInfo will be associated with the corresponding CSI-ReportConfig through the reportConfigId field. The CSI request field (CSI request field) in DCI format 0_1 ​​or DCI format 0_2 or DCI format 0_3 can indicate one of the CSI trigger states. The bit width N of the CSI request field TS Can be configured by RRC, N TS The range is 0 to 6 bits, and can indicate up to 63 CSI trigger states (one value is not triggered). MAC-CE selects is mapped to the CSI request field.

[0054] CSI-ReportConfig configures corresponding signal resource set lists for different measurement purposes, such as the CSI-RS resource set list nzp-CSI-RS-ResourceSetList, the SSB resource set list csi-SSB-ResourceSetList, and so on. CSI-AssociatedReportConfigInfo selects a measurement signal resource set from the measurement signal resource set list configured in its associated CSI-ReportConfig for the relevant measurement. In the following description, the CSI-RS resource set and / or SSB resource set used for measurement are referred to as the measurement signal resource set.

[0055] In addition, the Transmission Configuration Indication State (TCI state) can be used to configure the Quasi-Colocation (QCL) relationship between different channels or signals, and is configured in the high-layer parameters in the form of the information element TCI-state and / or TCI-UL-State. Among them, TCI-state can be used to configure the Quasi-Colocation relationship between downlink signals or channels, or can be used to simultaneously configure the Quasi-Colocation relationship between downlink and uplink signals or channels; TCI-UL-State is only used to configure the Quasi-Colocation relationship between uplink signals or channels.

[0056] For example, TCI-state can configure the source RS, QCL type, and other related parameters related to QCL. Starting from Rel-17 (version 17), the specific configuration form of TCI-state is as follows.

[0057] As can be seen from the above configuration, a TCI-state can include the following information:

[0058] ●tci-StateId, used to mark a TCI-State, with a value ranging from 0 to 127.

[0059] ●The first QCL information, QCL-Info.

[0060] ●The second QCL information, QCL-Info (optional).

[0061] A QCL-Info can contain the following information:

[0062] ●QCL configuration type, ranging from 'typeA' to 'typeD'.

[0063] ●QCL source RS configuration, including the cell ID (cell ID), bandwidth part ID (BWP ID) information, and RS identification information, which can be CSI-RS or SSB.

[0064] Currently, the protocol does not include reporting content related to event-driven beam management. If event-driven beam management is introduced, the UE will detect events (events) that require beam management initiation according to specific criteria. Beam management here includes at least beam switching. The specific criteria are not limited in this application. For ease of explanation, events related to beam management (including beam switching events) are collectively referred to as "beam management events" below. In the embodiments of this application, "beam switching events" are used as an example for explanation.

[0065] After detecting a beam switching event, the UE may proactively report the event and other information related to the beam switching, such as optionally including one or more of the following information about the new beam (the target beam to be selected, i.e., the candidate beam):

[0066] CRI / SSBRI information;

[0067] L1-RSRP / L1-SINR (Layer 1 Signal Interference Noise Ratio) information;

[0068] Physical cell ID information;

[0069] Transmission Configuration Indication State ID (TCI-StateId);

[0070] ●And so on.

[0071] For ease of explanation, this information is collectively referred to as "beam switching information" or "beam management information" below. It is worth noting that the beam switching information can belong to CSI, that is, it can be used as a type of CSI, but the present application is not limited to this, and the beam switching information may not belong to CSI.

[0072] The inventors discovered that beam switching information related to CSI can be transmitted in periodic CSI reports, semi-persistent periodic CSI reports, or aperiodic CSI reports. Aperiodic CSI reports offer the most flexibility and the shortest latency. However, current aperiodic CSI reports do not yet support event-triggered beam management. This is illustrated below with an example.

[0073] Figure 2 illustrates the current aperiodic CSI reporting process, and Figure 3 illustrates the hypothetical use of the current aperiodic CSI reporting process to report event-driven beam switching information. Figures 2 and 3 show that measurements after triggering aperiodic CSI reporting are actually completed before the trigger, and that the resource set j selected in the aperiodic reporting configuration associated with the aperiodic trigger state does not necessarily match the measurement resource set i where the beam switching event is detected.

[0074] As can be seen, in current aperiodic CSI reporting, the base station triggers the UE to perform aperiodic CSI reporting, and the UE reports the measurement results in the form of CSI reports on the measurement resources associated with the triggering state. However, in event-driven beam management, the UE first detects the beam switching event, and the base station then triggers aperiodic CSI reporting. Therefore, the measurement resource set associated with the triggering state and the measurement resource set used when a beam management event (such as a beam switching event) is not guaranteed to be consistent.

[0075] Furthermore, the aperiodic CSI reporting process triggered by event-driven beam management differs from the current aperiodic CSI reporting process. In the current system, measurement is performed before triggering, while beam management events are triggered after measurement results are obtained. This means that the current aperiodic CSI reporting process does not function properly in event-driven beam management scenarios.

[0076] This application is proposed to address at least one of the above problems or other similar problems.

[0077] The following describes embodiments of the present application in conjunction with the accompanying drawings and specific embodiments. In the following description, "when," "if," and "under the circumstances" have similar meanings and are interchangeable. Furthermore, the content in parentheses is used to explain or illustrate the content preceding the parentheses and is not intended to limit this application.

[0078] Embodiments of the first aspect

[0079] An embodiment of the present application provides an event-driven beam management method, which is described from the perspective of a terminal device.

[0080] FIG4 is a schematic diagram of an event-driven beam management method according to an embodiment of the present application. As shown in FIG4 , the method includes:

[0081] 410. A terminal device receives configuration information sent by a network device, where the configuration information includes first configuration information, and the first configuration information includes a measurement signal resource set for detecting an event-driven beam management event.

[0082] 420. The terminal device uses the above-mentioned measurement signal resource set to perform beam management event detection, and sends non-periodic CSI after receiving information triggering non-periodic CSI reporting for event-driven beam management, where the non-periodic CSI includes beam management information.

[0083] It is worth noting that FIG4 is merely a schematic illustration of an embodiment of the present application, and the present application is not limited thereto. For example, other operations may be added or some operations may be reduced, and the objects of the above operations may be adjusted. Those skilled in the art may make appropriate modifications based on the above content, and are not limited to the description of FIG4 above.

[0084] According to an embodiment of the present application, the network device pre-configures a measurement signal resource set for detecting event-driven beam management events. The terminal device uses the measurement signal resource set to perform event-driven beam management event detection and reports event-driven beam management information through non-periodic CSI, which can effectively reduce the delay of beam management, reduce signaling overhead, and improve network coverage.

[0085] In the above embodiment, the configuration information may be sent via RRC signaling, and the above configuration information may also be referred to as RRC configuration information. Furthermore, the beam management event detection performed by the terminal device may be configured by a network device, triggered by a network device, or triggered by the terminal device itself, and this application does not impose any restrictions on this. Furthermore, the relevant content of the beam management information reported by the terminal device has been described above and will not be repeated here.

[0086] In the above embodiment, in some possible implementations, the measurement signal resource set used to detect the event-driven beam management event may be a measurement signal resource set, which includes one or more measurement signal resources. The measurement signal resources may be, for example, CSI-RS resources and / or SSB resources.

[0087] In the above implementation, the measurement signal resource set may be configured in the information element CSI-MeasConfig, and the measurement signal resource set may be a CSI-RS resource set or an SSB resource set.

[0088] The above-mentioned CSI-RS resource set is, for example, a list nzp-CSI-RS-ResourceToAddModList-EventBM, which includes one to multiple CSI-RS resources (NZP-CSI-RS-Resource).

[0089] The above-mentioned SSB resource set is, for example, csi-SSB-ResourceSet-EventBM, whose value is a CSI-SSB-ResourceSet. The CSI-SSB-ResourceSet can contain one to multiple SSB indexes (SSB-Index), and the SSB index corresponds to the SSB resource.

[0090] In the above implementation, the measurement signal resource may further include physical cell identity information (PCI) to indicate the serving cell to which the measurement signal resource belongs. For example, when the measurement signal resource does not include the above PCI, it is considered that the measurement signal resource belongs to the current serving cell.

[0091] In the foregoing embodiment, in other possible implementations, the measurement signal resource set used to detect event-driven beam management events is one to multiple measurement signal resource sets, each measurement signal resource set including one to multiple measurement signal resources. The measurement signal resources are, for example, CSI-RS resources and / or SSB resources.

[0092] In the above implementation, the measurement signal resource set may be configured in the information element CSI-MeasConfig, and the measurement signal resource set may be a CSI-RS resource set list and / or an SSB resource set list.

[0093] The above-mentioned CSI-RS resource set list is, for example, nzp-CSI-RS-ResourceSetToAddModList-EventBM, which contains one to multiple CSI-RS resource sets (NZP-CSI-RS-ResourceSet), and the CSI-RS resource set (NZP-CSI-RS-ResourceSet) can include one to multiple CSI-RS resources (NZP-CSI-RS-Resource).

[0094] The above-mentioned SSB resource set list is, for example, csi-SSB-ResourceSetSetToAddModList-EventBM, which contains one to multiple SSB resource sets (CSI-SSB-ResourceSet). The SSB resource set (CSI-SSB-ResourceSet) may include one to multiple SSB indexes (SSB-Index), which correspond to SSB resources.

[0095] In the above implementation, the measurement signal resource may optionally further include physical cell identity information (PCI) to indicate the serving cell to which the measurement signal resource belongs. For example, when the measurement signal resource does not include the above PCI, it is considered that the measurement signal resource belongs to the current serving cell.

[0096] In the above embodiment, the measurement signal resource set used to detect event-driven beam management events can be determined by the downlink or joint TCI state list dl-OrJointTCI-StateList in the RRC information element PDSCH-Config.

[0097] For example, for each TCI-State in the downlink or joint TCI state list dl-OrJointTCI-StateList, if the qcl-Type value in the field qcl-Type2 is 'typeD', the source RS in the field qcl-Type2 serves as the measurement signal resource and is an element in the above measurement signal resource set.

[0098] In the above embodiment, the terminal device may optionally further receive activation signaling for activating event-driven beam management event detection, where the activation signaling indicates that one or more measurement signal resource sets in the above measurement signal resource sets are used for the above beam management event detection. Thus, the terminal device may use the measurement signal resources included in the activated measurement signal resource sets to perform the above beam management event detection.

[0099] In some embodiments, the configuration information further includes second configuration information, where the second configuration information is SR configuration information specifically used for event-driven beam management.

[0100] In the above embodiment, after detecting an event-driven beam management event, the terminal device can use the SR resources configured by the above-mentioned SR configuration information for event-driven beam management to send a scheduling request to the network device. The network device sends uplink scheduling authorization information for scheduling PUSCH to the terminal device based on the scheduling request.

[0101] In the above embodiment, the uplink grant scheduling information includes a CSI request field, which is used to trigger aperiodic CSI reporting associated with event-driven beam management. Thus, the terminal device can send the above-mentioned aperiodic CSI on the scheduled PUSCH to report the above-mentioned beam management information.

[0102] In the above embodiment, the value of the CSI request field is the same as the CSI request coding point corresponding to the above-mentioned first non-periodic CSI trigger state. For example, when both are k, the above-mentioned first non-periodic CSI trigger state is initiated, and the non-periodic CSI reporting content triggered by the first non-periodic CSI trigger state is the above-mentioned beam management information.

[0103] In some embodiments, the configuration information further includes third configuration information, which is aperiodic CSI triggering state configuration information for event-driven beam management.

[0104] In the above embodiment, the terminal device can confirm whether the non-periodic CSI reporting for event-driven beam management is triggered based on the above-mentioned non-periodic CSI trigger status configuration information, so that when the non-periodic CSI reporting is triggered, the above-mentioned non-periodic CSI is sent to report the above-mentioned beam management information.

[0105] In the above embodiment, the non-periodic CSI trigger state configuration information may be a non-periodic CSI trigger state list, which may include one to multiple non-periodic CSI trigger states, and only one non-periodic CSI trigger state among the one to multiple non-periodic CSI trigger states includes reporting configuration information associated with event-driven beam management, which is called the first non-periodic CSI trigger state, for the terminal device to report the above-mentioned beam management information.

[0106] In the above embodiment, the CSI request codepoint corresponding to the first non-periodic CSI trigger state is k. Correspondingly, when the value of the CSI request field in the above uplink scheduling authorization information received by the terminal device is also k, the above first non-periodic CSI trigger state will be initiated, and the non-periodic CSI reporting content triggered by the first non-periodic CSI trigger state is the above beam management information.

[0107] In some embodiments, the configuration information further includes fourth configuration information, which is CSI reporting configuration information for event-driven beam management.

[0108] In the above embodiment, the terminal device may send the above non-periodic CSI on the scheduled PUSCH according to the above CSI reporting configuration information to report the above beam management information.

[0109] In the above embodiment, the CSI reporting configuration information may include one or more sets of beam information and the number of beam information groups. Each set of beam information may correspond to one measurement signal resource. For example, each set of beam information may include at least one of the following information:

[0110] CSI-RS resource set identification information and / or SSB resource set identification information;

[0111] CRI / SSBRI information;

[0112] L1-RSRP / L1-SINR information;

[0113] Physical cell identification information (Physical cell ID);

[0114] TCI state identification information (TCI-StateId).

[0115] In order to make the method of the embodiment of the present application clearer and easier to understand, the method of the embodiment of the present application is described below with reference to specific examples.

[0116] In one example, the terminal device receives configuration information, which includes the first configuration information and the second configuration information. The relevant content of the second configuration information has been described above and will not be repeated here.

[0117] In the above example, the measurement signal resource set indicated by the first configuration information is a measurement signal resource set. The measurement signal resource set contains one to multiple measurement signal resources.

[0118] In the above example, the measurement signal resource set can be configured in the information element CSI-MeasConfig. For example, a CSI-RS resource set can be configured in the above information element CSI-MeasConfig, or an SSB resource set can be configured. The configured CSI-RS resource set is, for example, nzp-CSI-RS-ResourceToAddModList-EventBM in list form, and the list contains one to multiple CSI-RS resources (NZP-CSI-RS-Resource). The configured SSB resource set is, for example, csi-SSB-ResourceSet-EventBM, and the value is a CSI-SSB-ResourceSet, and the CSI-SSB-ResourceSet contains one to multiple SSB indexes SSB-Index, corresponding to different SSB resources.

[0119] In the above example, the measurement signal resource (CSI-RS resource and / or SSB resource) optionally includes physical cell identification information to indicate to which cell the current measurement signal resource belongs. In some examples, if the measurement signal resource does not include physical cell identification information, the terminal device considers that the measurement signal resource belongs to the current serving cell.

[0120] The following is an example of adding a CSI-RS resource list for event-driven beam management in CSI-MeasConfig:

[0121] nzp-CSI-RS-ResourceToAddModList-EventBM-r19SEQUENCE(SIZE(1..maxNrofNZP-CSI-RS-Resources))OF NZP-CSI-RS-Resource OPTIONAL,--Need N

[0122] The following is an example of adding an SSB resource list for event-driven beam management in CSI-MeasConfig:

[0123] csi-SSB-ResourceSet-EventBM-r19 CSI-SSB-ResourceSet OPTIONAL,--Need N

[0124] In the above example, the configuration information also includes the above third configuration information.

[0125] For example, a new reporting configuration information field associated with event-driven beam management is added to the information element CSI-AperiodicTriggerState, such as the new field eventBM-associatedReportConfigInfo. The value of the new field eventBM-associatedReportConfigInfo is the CSI reporting configuration information associated with event-driven beam management, such as the CSI reporting configuration information associated with event-driven beam management is named EventBM-associatedReportConfigInfo.

[0126] Among them, the above-mentioned new field eventBM-associatedReportConfigInfo is optional. Among all the non-periodic trigger states (CSI-AperiodicTriggerState) in the non-periodic CSI trigger list (CSI-AperiodicTriggerStateList), the above-mentioned new field eventBM-associatedReportConfigInfo will only be configured for one non-periodic trigger state (CSI-AperiodicTriggerState), that is, the terminal device does not expect more than one CSI-AperiodicTriggerState to be configured with the eventBM-associatedReportConfigInfo field. In addition, in the above example, the CSI request codepoint (CSI request codepoint) corresponding to the non-periodic trigger state (CSI-AperiodicTriggerState) configured with the new field (called the first non-periodic CSI trigger state) is k. Correspondingly, when the value of the CSI request field of the uplink scheduling grant information received by the terminal device is also k, the first aperiodic CSI triggering state mentioned above will be initiated, and the aperiodic CSI reporting content triggered by the first aperiodic CSI triggering state is the above beam management information.

[0127] The following is an example of adding CSI reporting configuration information (eventBM-associatedReportConfigInfo) for event-driven beam management in CSI-AperiodicTriggerState:

[0128] eventBM-associatedReportConfigInfo-r19 EventBM-associatedReportConfigInfo

[0129] OPTIONAL,--

[0130] Need R

[0131] In the above example, the configuration information also includes the above-mentioned fourth configuration information, that is, the newly added information element EventBM-associatedReportConfigInfo in the above-mentioned third configuration information. The information element EventBM-associatedReportConfigInfo is used to configure the reported new beam information (belonging to the beam management information), which may include one or more groups of new beam information and the number of groups of new beam information. Each group of new beam information may correspond to a measurement signal resource in the first configuration information. The new beam information may include, for example, the following information:

[0132] CRI / SSBRI information;

[0133] L1-RSRP / L1-SINR information;

[0134] Physical cell ID information (Physical cell ID);

[0135] TCI-StateId;

[0136] etc.

[0137] In some examples, the above CRI / SSBRI information is mandatory information, and other information is optional information.

[0138] In the above example, after the configuration information received by the terminal device takes effect or is activated, the terminal device uses all the measurement signal resources in the above measurement signal resource set to detect beam switching events. After detecting the beam switching event, the terminal device uses the SR resources dedicated to event-driven beam management configured by the above second configuration information to send SR, and receives uplink scheduling authorization information for scheduling PUSCH. The CSI request field in the uplink scheduling authorization information takes the value of the CSI request codepoint (CSI request codepoint) corresponding to the aperiodic CSI trigger state (CSI-AperiodicTriggerState) (referred to as the first aperiodic CSI trigger state) of the new field EventBM-associatedReportConfigInfo configured in the above third configuration information, that is, the value is k. Therefore, the terminal device can use the above-scheduled PUSCH to report beam switching information according to the configuration of EventBM-associatedReportConfigInfo in the third configuration information, and ignore other fields in the CSI-AperiodicTriggerState corresponding to the CSI request codepoint k except EventBM-associatedReportConfigInfo (if there are other fields).

[0139] Figure 5 is a schematic diagram of an example of a configured measurement signal resource set and new beam information (i.e., beam switching information) reported by a terminal device. As shown in Figure 5, the configuration information received by the terminal device includes one measurement signal resource set, which includes measurement signal resource 1, measurement signal resource 2, ..., and measurement signal resource M. The terminal device reports two sets of new beam information: the first set corresponds to measurement signal resource 1, and the second set corresponds to measurement signal resource 3.

[0140] In another example, the terminal device receives configuration information, which includes the first configuration information, the second configuration information, and the third configuration information. The relevant contents of the second configuration information and the third configuration information have been described above and will not be repeated here.

[0141] In the above example, the measurement signal resource set indicated by the first configuration information is one to multiple measurement signal resource sets, and each measurement signal resource set contains one to multiple measurement signal resources.

[0142] In the above example, the measurement signal resource set can be configured in the information element CSI-MeasConfig. For example, a CSI-RS resource set list is configured in the information element CSI-MeasConfig, or an SSB resource set list can be configured, or both a CSI-RS resource set list and an SSB resource set list can be configured. The configured CSI-RS resource set list is, for example, nzp-CSI-RS-ResourceSetToAddModList-EventBM, and the list contains one to multiple CSI-RS resource sets (NZP-CSI-RS-ResourceSet), and the NZP-CSI-RS-ResourceSet contains one to multiple CSI-RS resources (NZP-CSI-RS-Resource). For example, the configured SSB resource set list is csi-SSB-ResourceSetToAddModList-EventBM, and the list contains one to multiple SSB resource sets (CSI-SSB-ResourceSet). The CSI-SSB-ResourceSet contains one to multiple SSB indexes SSB-Index, corresponding to different SSB resources.

[0143] In the above example, the measurement signal resource (CSI-RS resource and / or SSB resource) optionally includes physical cell identification information to indicate to which cell the current measurement signal resource belongs. In some examples, if the measurement signal resource does not include physical cell identification information, the terminal device considers that the measurement signal resource belongs to the current serving cell.

[0144] The following is an example of adding a CSI-RS resource set list for event-driven beam management in CSI-MeasConfig:

[0145] The following is an example of adding an SSB resource set list for event-driven beam management in CSI-MeasConfig:

[0146] csi-SSB-ResourceSetToAddModList-EventBM-r19SEQUENCE(SIZE(1..maxNrofCSI-SSB-ResourceSets))

[0147] OF CSI-SSB-ResourceSet OPTIONAL,--

[0148] Need N

[0149] In the above example, the configuration information also includes the above-mentioned fourth configuration information, that is, the newly added information element EventBM-associatedReportConfigInfo in the above-mentioned third configuration information. The information element EventBM-associatedReportConfigInfo is used to configure the reported new beam information (belonging to the beam management information), which may include one or more groups of new beam information and the number of groups of new beam information. Each group of new beam information may correspond to a measurement signal resource in the first configuration information. The new beam information may include, for example, the following information:

[0150] CSI-RS resource set identification information or SSB resource set identification information (such as resource set ID);

[0151] CRI / SSBRI information;

[0152] L1-RSRP / L1-SINR information;

[0153] Physical cell ID information (Physical cell ID);

[0154] TCI-StateId;

[0155] etc.

[0156] In some examples, the above-mentioned CSI-RS resource set identification information or SSB resource set identification information and the above-mentioned CRI / SSBRI information are mandatory information, and other information is optional information.

[0157] In the above example, after the configuration information received by the terminal device takes effect or is activated, the terminal device uses all the measurement signal resources in the above measurement signal resource set to detect beam switching events. After detecting the beam switching event, the terminal device uses the SR resources dedicated to event-driven beam management configured by the above second configuration information to send SR, and receives uplink scheduling authorization information for scheduling PUSCH. The CSI request field in the uplink scheduling authorization information is taken as the CSI request codepoint (CSI request codepoint) corresponding to the aperiodic CSI trigger state (CSI-AperiodicTriggerState) (referred to as the first aperiodic CSI trigger state) configured with the new field EventBM-associatedReportConfigInfo in the above third configuration information, that is, the value is k. Therefore, the terminal device can use the above-scheduled PUSCH to report beam switching information according to the configuration of EventBM-associatedReportConfigInfo in the third configuration information, and ignore other fields (if any) in the CSI-AperiodicTriggerState corresponding to the CSI request codepoint k except EventBM-associatedReportConfigInfo.

[0158] Figure 6 is a schematic diagram of another example of configured measurement signal resource sets and new beam information (i.e., beam switching information) reported by a terminal device. As shown in Figure 6, the configuration information received by the terminal device includes a measurement signal resource set list consisting of measurement signal resource set 1, measurement signal resource set 2, and so on, to measurement signal resource set N. The terminal device reports two sets of new beam information: the first set of new beam information corresponds to a measurement signal resource in measurement signal resource set 1, and the second set of new beam information corresponds to a measurement signal resource in measurement signal resource set 3.

[0159] In another example, the terminal device receives configuration information, which includes the above-mentioned first configuration information, the above-mentioned second configuration information, the above-mentioned third configuration information and the above-mentioned fourth configuration information, wherein the relevant contents of the first configuration information, the second configuration information, the third configuration information and the fourth configuration information have been explained before and will not be repeated here.

[0160] In the above example, the terminal device may also receive signaling for activating event-driven beam switching event detection, referred to as activation signaling. The activation signaling may select (specify, indicate, or include) one to multiple measurement resource sets in the above-mentioned first configuration information for beam switching event detection. The terminal device may use the measurement signal of the selected measurement signal resource set to perform beam switching event detection.

[0161] In the above example, after detecting a beam switching event, the terminal device uses the SR resources dedicated to event-driven beam management configured by the second configuration information to send an SR, and receives uplink scheduling authorization information for scheduling PUSCH. The CSI request field in the uplink scheduling authorization information is taken as the CSI request codepoint (CSI request codepoint) corresponding to the aperiodic CSI trigger state (CSI-AperiodicTriggerState) (referred to as the first aperiodic CSI trigger state) configured with the new field EventBM-associatedReportConfigInfo in the third configuration information, that is, the value is k. Therefore, the terminal device can use the above-scheduled PUSCH to report the beam switching information according to the configuration of EventBM-associatedReportConfigInfo in the third configuration information, and ignore other fields (if any) in the CSI-AperiodicTriggerState corresponding to the CSI request codepoint k except for EventBM-associatedReportConfigInfo.

[0162] Figure 7 is a schematic diagram of another example of a configured measurement signal resource set and new beam information (i.e., beam switching information) reported by a terminal device. As shown in Figure 7, in the configuration information received by the terminal device, the measurement signal resource set is a measurement signal resource set list, which includes measurement signal resource set 1, measurement signal resource set 2...measurement signal resource set N. In the activation signaling received by the terminal device for activating event-driven beam switching event detection, measurement signal resource set 1, measurement signal resource set 3, and measurement signal resource set N are activated. The terminal device reports two groups of new beam information, wherein the first group of new beam information corresponds to a measurement signal resource in measurement signal resource set 1, and the second group of new beam information corresponds to a measurement signal resource in measurement signal resource set 3.

[0163] In another example, the terminal device receives configuration information. The configuration information includes the first configuration information, the second configuration information, and the third configuration information. The relevant contents of the second configuration information and the third configuration information have been described above and will not be repeated here.

[0164] In the above example, the measurement signal resource set indicated by the first configuration information is determined by the downlink or joint TCI state list dl-OrJointTCI-StateList in the RRC information element PDSCH-Config. For each TCI-State in the list, if the value of the qcl-Type field in the qcl-Type2 field is 'typeD', the source RS in the qcl-Type2 field (determined by the referenceSignal field) can be used as a measurement signal resource and is an element in the measurement signal resource set.

[0165] In the above example, the configuration information also includes the above-mentioned fourth configuration information, that is, the newly added information element EventBM-associatedReportConfigInfo in the above-mentioned third configuration information. The information element EventBM-associatedReportConfigInfo is used to configure the reported new beam information (belonging to the beam management information), which may include one or more groups of new beam information and the number of groups of new beam information. Each group of new beam information may correspond to a measurement signal resource in the first configuration information. The new beam information may include, for example, the following information:

[0166] TCI-StateId;

[0167] L1-RSRP / L1-SINR information;

[0168] etc.

[0169] In some examples, the above TCI-StateId is mandatory information, and other information is optional information.

[0170] In the above example, after the configuration information received by the terminal device takes effect or is activated, the terminal device uses all the measurement signal resources in the above measurement signal resource set to detect beam switching events. After detecting the beam switching event, the terminal device uses the SR resources dedicated to event-driven beam management configured by the above second configuration information to send SR, and receives uplink scheduling authorization information for scheduling PUSCH. The CSI request field in the uplink scheduling authorization information is taken as the CSI request codepoint (CSI request codepoint) corresponding to the aperiodic CSI trigger state (CSI-AperiodicTriggerState) (referred to as the first aperiodic CSI trigger state) configured with the new field EventBM-associatedReportConfigInfo in the above third configuration information, that is, the value is k. Therefore, the terminal device can use the above-scheduled PUSCH to report beam switching information according to the configuration of EventBM-associatedReportConfigInfo in the third configuration information, and ignore other fields (if any) in the CSI-AperiodicTriggerState corresponding to the CSI request codepoint k except EventBM-associatedReportConfigInfo.

[0171] The above embodiments are merely exemplary of the present invention, but the present invention is not limited thereto. Appropriate modifications may be made based on the above embodiments. For example, the above embodiments may be used alone, or one or more of the above embodiments may be combined.

[0172] According to the method of the embodiment of the present application, the delay of beam management can be effectively reduced, signaling overhead can be reduced, and network coverage can be improved.

[0173] Embodiments of the second aspect

[0174] An embodiment of the present application provides a configuration method for event-driven beam management, which is explained from the side of the network device. This method is the processing on the network device side corresponding to the method of the embodiment of the first aspect, and the content that is the same as the embodiment of the first aspect is not repeated.

[0175] FIG8 is a schematic diagram of a configuration method for event-driven beam management according to an embodiment of the present application. As shown in FIG8 , the method includes:

[0176] 810: The network device sends configuration information to the terminal device, where the configuration information includes first configuration information, where the first configuration information includes a measurement signal resource set for detecting an event-driven beam management event.

[0177] 820: The network device receives the non-periodic CSI sent by the terminal device, where the non-periodic CSI includes beam management information. The non-periodic CSI is sent by the terminal device after receiving information triggering the non-periodic CSI reporting for event-driven beam management using the above-mentioned measurement signal resource set to detect beam management events.

[0178] It is worth noting that FIG8 above is merely a schematic illustration of an embodiment of the present application, and the present application is not limited thereto. For example, the execution order of the various operations may be appropriately adjusted, and other operations may be added or some operations may be reduced. Those skilled in the art may make appropriate modifications based on the above description, and are not limited to the description of FIG8 above.

[0179] In some embodiments, the above configuration information also includes second configuration information, where the second configuration information is SR configuration information for event-driven beam management.

[0180] In the above embodiment, the network device can also receive a scheduling request sent by the terminal device. The scheduling request is sent to the network device by the terminal device after detecting an event-driven beam management event using the SR resources configured by the above-mentioned SR configuration information for event-driven beam management.

[0181] In the above embodiment, the network device may further send uplink scheduling grant information for scheduling PUSCH to the terminal device, where the uplink scheduling grant information includes a CSI request field, where the CSI request field is used to trigger aperiodic CSI reporting associated with event-driven beam management. Thus, the terminal device may send the aperiodic CSI on the scheduled PUSCH.

[0182] In some embodiments, the network device may further send activation signaling to the terminal device for activating event-driven beam management event detection, where the activation signaling indicates that one or more measurement signal resource sets in the aforementioned measurement signal resource sets are used for beam management event detection. Thus, the terminal device may use the measurement signal resources included in the activated measurement signal resource sets for beam management event detection.

[0183] In some embodiments, the measurement signal resource set for detecting event-driven beam management events is a measurement signal resource set, wherein the measurement signal resource set includes one or more measurement signal resources. The specific resource configuration has been described in the embodiment of the first aspect and will not be repeated here.

[0184] In other embodiments, the measurement signal resource set for detecting event-driven beam management events is one or more measurement signal resource sets, each of which includes one or more measurement signal resources. The specific resource configuration has been described in the embodiment of the first aspect and will not be repeated here.

[0185] In some embodiments, the above-mentioned configuration information also includes third configuration information, which is non-periodic CSI trigger status configuration information for event-driven beam management. The terminal device can confirm whether the non-periodic CSI reporting for event-driven beam management is triggered based on the above-mentioned non-periodic CSI trigger status configuration information. Then, when the non-periodic CSI reporting is triggered, the non-periodic CSI reporting is directly performed without making any measurements. The relevant content of the third configuration information has been explained in the embodiment of the first aspect and will not be repeated here.

[0186] In some embodiments, the configuration information further includes fourth configuration information, which is CSI reporting configuration information for event-driven beam management. The terminal device may send the aperiodic CSI on the scheduled PUSCH based on the CSI reporting configuration information. The relevant content of the fourth configuration information has been described in the embodiment of the first aspect and will not be repeated here.

[0187] In some embodiments, the measurement signal resource set used to detect event-driven beam management events is indicated or configured by the downlink or joint TCI state list dl-OrJointTCI-StateList in the RRC information element PDSCH-Config.

[0188] For example, for each TCI-State in the above-mentioned downlink or joint TCI state list dl-OrJointTCI-StateList, the qcl-Type value in the field qcl-Type2 is indicated or configured as 'typeD', then the source RS in the field qcl-Type2 serves as a measurement signal resource and is an element in the above-mentioned measurement signal resource set.

[0189] The above embodiments are merely exemplary of the present invention, but the present invention is not limited thereto. Appropriate modifications may be made based on the above embodiments. For example, the above embodiments may be used alone, or one or more of the above embodiments may be combined.

[0190] According to the method of the embodiment of the present application, the delay of beam management can be effectively reduced, signaling overhead can be reduced, and network coverage can be improved.

[0191] Embodiments of the third aspect

[0192] The embodiment of the present application provides an event-driven beam management device. The device can be, for example, a terminal device, or one or more components or assemblies configured in the terminal device. The same contents as the first and second aspects of the embodiment are not repeated here.

[0193] FIG9 is a schematic diagram of an event-driven beam management device according to an embodiment of the present application. As shown in FIG9 , the event-driven beam management device 900 according to an embodiment of the present application includes:

[0194] A receiving unit 910 receives configuration information sent by a network device, where the configuration information includes first configuration information, where the first configuration information includes a measurement signal resource set for detecting an event-driven beam management event;

[0195] The processing unit 920 uses the above-mentioned measurement signal resource set to detect beam management events, and sends aperiodic CSI after receiving information triggering aperiodic CSI reporting for event-driven beam management, where the aperiodic CSI includes beam management information.

[0196] In some embodiments, the above configuration information also includes second configuration information, where the second configuration information is SR configuration information for event-driven beam management.

[0197] In the above embodiment, the processing unit 920 may further, after detecting an event-driven beam management event, use the SR resources configured by the SR configuration information for event-driven beam management to send a scheduling request (SR) to the network device; the receiving unit 910 may further receive uplink scheduling grant information sent by the network device for scheduling PUSCH, where the uplink scheduling grant information includes a CSI request field, which is used to trigger aperiodic CSI reporting associated with event-driven beam management. Thus, the processing unit 920 may send the above-mentioned aperiodic CSI on the scheduled PUSCH.

[0198] In some embodiments, the receiving unit 910 may also receive activation signaling for activating event-driven beam management event detection, which activation signaling indicates that one to multiple measurement signal resource sets in the measurement signal resource set are used for the above-mentioned beam management event detection; the processing unit 920 may use the measurement signal resources contained in the above-mentioned activated measurement signal resource set to perform beam management event detection.

[0199] In some embodiments, the measurement signal resource set for detecting event-driven beam management events is a measurement signal resource set, which includes one to multiple measurement signal resources.

[0200] In the above embodiment, the measurement signal resource may include at least one of the following: a CSI-RS resource and an SSB resource.

[0201] In the above embodiment, the measurement signal resource set may be configured in the information element CSI-MeasConfig, and the measurement signal resource set may be a CSI-RS resource set or an SSB resource set.

[0202] In the above embodiment, the CSI-RS resource set may be a list nzp-CSI-RS-ResourceToAddModList-EventBM, which includes one to multiple CSI-RS resources (NZP-CSI-RS-Resource).

[0203] In the above embodiment, the SSB resource set can be a csi-SSB-ResourceSet-EventBM, whose value is a CSI-SSB-ResourceSet, and the CSI-SSB-ResourceSet contains one to multiple SSB indexes (SSB-Index), and the SSB index corresponds to the SSB resource.

[0204] In some embodiments, the measurement signal resource set for detecting event-driven beam management events is one to multiple measurement signal resource sets, and each measurement signal resource set includes one to multiple measurement signal resources.

[0205] In the above embodiment, the measurement signal resource may include at least one of the following: a CSI-RS resource and an SSB resource.

[0206] In the above embodiment, the measurement signal resource set may be configured in the information element CSI-MeasConfig, and the measurement signal resource set may be a CSI-RS resource set list and / or an SSB resource set list.

[0207] In the above embodiment, the CSI-RS resource set list can be nzp-CSI-RS-ResourceSetToAddModList-EventBM, which contains one to multiple CSI-RS resource sets (NZP-CSI-RS-ResourceSet), and the CSI-RS resource set (NZP-CSI-RS-ResourceSet) includes one to multiple CSI-RS resources (NZP-CSI-RS-Resource).

[0208] In the above embodiment, the SSB resource set list can be csi-SSB-ResourceSetSetToAddModList-EventBM, which contains one to multiple SSB resource sets (CSI-SSB-ResourceSet), and the SSB resource set (CSI-SSB-ResourceSet) includes one to multiple SSB indexes (SSB-Index), and the SSB index corresponds to the SSB resource.

[0209] In some embodiments, optionally, the measurement signal resource may include physical cell identification information to indicate the serving cell to which the measurement signal resource belongs.

[0210] In some embodiments, the above configuration information also includes third configuration information, which is non-periodic CSI trigger state configuration information for event-driven beam management.

[0211] In the above embodiment, the processing unit 920 may confirm whether the above aperiodic CSI reporting for event-driven beam management is triggered according to the above aperiodic CSI triggering status configuration information.

[0212] In the above embodiment, the non-periodic CSI trigger state configuration information may be a non-periodic CSI trigger state list, which includes one to multiple non-periodic CSI trigger states, and only one non-periodic CSI trigger state among the multiple non-periodic CSI trigger states includes reporting configuration information associated with event-driven beam management, which is called the first non-periodic CSI trigger state.

[0213] In the above embodiment, the CSI request codepoint corresponding to the first aperiodic CSI triggering state is k. When the value of the CSI request field included in the uplink scheduling grant information used to schedule the PUSCH is also k, the above-mentioned first aperiodic CSI triggering state is initiated, and the aperiodic CSI reporting content triggered by the first aperiodic CSI triggering state is the above-mentioned beam management information.

[0214] In some embodiments, the above configuration information also includes fourth configuration information, which is CSI reporting configuration information for event-driven beam management.

[0215] In the above embodiment, the processing unit 920 may send the above aperiodic CSI on the scheduled PUSCH according to the above CSI reporting configuration information.

[0216] In the above embodiment, the CSI reporting configuration information may include one or more sets of beam information and the number of beam information sets. Each set of beam information corresponds to one measurement signal resource. Each set of beam information may include at least one of the following information:

[0217] CSI-RS resource set identification information and / or SSB resource set identification information;

[0218] CRI / SSBRI information;

[0219] L1-RSRP / L1-SINR information;

[0220] Physical cell identification information (Physical cell ID);

[0221] TCI state identification information (TCI-StateId).

[0222] In some embodiments, the measurement signal resource set for detecting event-driven beam management events may be determined by a downlink or joint TCI state list dl-OrJointTCI-StateList in the RRC information element PDSCH-Config. That is, the processing unit 920 may determine the measurement signal resource set for detecting event-driven beam management events based on the downlink or joint TCI state list dl-OrJointTCI-StateList in the RRC information element PDSCH-Config.

[0223] For example, for each TCI-State in the above downlink or joint TCI state list dl-OrJointTCI-StateList, if the qcl-Type value in the field qcl-Type2 is 'typeD', then the source RS in the field qcl-Type2 serves as the measurement signal resource and is an element in the above measurement signal resource set.

[0224] The present application also provides an event-driven beam management configuration device. The device may be, for example, a network device, or one or more components or assemblies configured on the network device. The contents that are the same as those in the first and second aspects are not repeated here.

[0225] FIG10 is a schematic diagram of a configuration device for event-driven beam management according to an embodiment of the present application. As shown in FIG10 , the configuration device 1000 for event-driven beam management according to an embodiment of the present application includes:

[0226] A sending unit 1010 is configured to send configuration information to a terminal device, where the configuration information includes first configuration information, where the first configuration information includes a measurement signal resource set for detecting an event-driven beam management event;

[0227] The receiving unit 1020 receives the non-periodic CSI sent by the terminal device, which includes beam management information. The non-periodic CSI is sent by the terminal device after receiving the information triggering the non-periodic CSI reporting for event-driven beam management using the above-mentioned measurement signal resource set to detect beam management events.

[0228] In some embodiments, the above configuration information also includes second configuration information, where the second configuration information is SR configuration information for event-driven beam management.

[0229] In the above embodiment, the receiving unit 1020 can also receive a scheduling request sent by the terminal device, which is sent to the network device by the terminal device after detecting an event-driven beam management event using the SR resources configured by the above-mentioned SR configuration information for event-driven beam management.

[0230] In the above embodiment, the transmitting unit 1010 may further transmit uplink scheduling grant information for scheduling a PUSCH to the terminal device, where the uplink scheduling grant information includes a CSI request field, where the CSI request field is used to trigger aperiodic CSI reporting associated with event-driven beam management. Thus, the terminal device may transmit the aperiodic CSI on the scheduled PUSCH.

[0231] In some embodiments, the sending unit 1010 may further send activation signaling for activating event-driven beam management event detection to the terminal device, where the activation signaling indicates that one or more measurement signal resource sets in the measurement signal resource set are used for beam management event detection. Thus, the terminal device may use the measurement signal resources included in the activated measurement signal resource set to perform beam management event detection.

[0232] In some embodiments, the measurement signal resource set for detecting event-driven beam management events is a measurement signal resource set, wherein the measurement signal resource set includes one or more measurement signal resources. The specific resource configuration has been described in the embodiment of the first aspect and will not be repeated here.

[0233] In other embodiments, the measurement signal resource set for detecting event-driven beam management events is one or more measurement signal resource sets, each of which includes one or more measurement signal resources. The specific resource configuration has been described in the embodiment of the first aspect and will not be repeated here.

[0234] In some embodiments, the above-mentioned configuration information also includes third configuration information, which is aperiodic CSI trigger state configuration information for event-driven beam management. The terminal device can confirm whether the aperiodic CSI reporting for event-driven beam management is triggered based on the above-mentioned aperiodic CSI trigger state configuration information. Then, when the aperiodic CSI reporting is triggered, the aperiodic CSI reporting is directly performed without performing measurement.

[0235] The relevant content of the third configuration information has been explained in the embodiment of the first aspect and will not be repeated here.

[0236] In some embodiments, the configuration information further includes fourth configuration information, which is CSI reporting configuration information for event-driven beam management. The terminal device can send the aperiodic CSI on the scheduled PUSCH according to the CSI reporting configuration information.

[0237] The relevant content of the fourth configuration information has been explained in the embodiment of the first aspect and will not be repeated here.

[0238] In some embodiments, the measurement signal resource set used to detect event-driven beam management events is indicated or configured by the downlink or joint TCI state list dl-OrJointTCI-StateList in the RRC information element PDSCH-Config.

[0239] For example, for each TCI-State in the above-mentioned downlink or joint TCI state list dl-OrJointTCI-StateList, the qcl-Type value in the field qcl-Type2 is indicated or configured as 'typeD', then the source RS in the field qcl-Type2 serves as a measurement signal resource and is an element in the above-mentioned measurement signal resource set.

[0240] The above embodiments are merely exemplary of the present invention, but the present invention is not limited thereto. Appropriate modifications may be made based on the above embodiments. For example, the above embodiments may be used alone, or one or more of the above embodiments may be combined.

[0241] It is worth noting that the above description only describes the components or modules related to the present application, but the present application is not limited thereto. Apparatuses 900 to 1000 may also include other components or modules, and for details of these components or modules, reference may be made to related art.

[0242] In addition, for the sake of simplicity, Figures 9 and 10 only illustrate the connection relationship or signal direction between various components or modules. However, it should be clear to those skilled in the art that various related technologies such as bus connection can be used. The above-mentioned components or modules can be implemented by hardware facilities such as processors, memories, transmitters, and receivers; the implementation of this application is not limited to this.

[0243] The device according to the embodiment of the present application can effectively reduce the delay of beam management, reduce signaling overhead, and improve network coverage.

[0244] Embodiments of the fourth aspect

[0245] An embodiment of the present application also provides a communication system, which includes a network device and a terminal device.

[0246] FIG11 is a schematic diagram of a communication system according to an embodiment of the present application, schematically illustrating a situation using a terminal device and a network device as an example. As shown in FIG11 , a communication system 1100 may include a network device 1101 and terminal devices 1102 and 1103. For simplicity, FIG11 illustrates only two terminal devices and one network device as an example, but the embodiments of the present application are not limited thereto.

[0247] In the embodiment of the present application, existing services or future services can be transmitted between the network device 1101 and the terminal devices 1102 and 1103. For example, these services may include but are not limited to: enhanced mobile broadband (eMBB), massive machine type communication (mMTC), and ultra-reliable and low-latency communication (URLLC), etc.

[0248] It is worth noting that Figure 11 shows that both terminal devices 1102 and 1103 are within the coverage range of network device 1101, but the present application is not limited thereto. Both terminal devices 1102 and 1103 may not be within the coverage range of network device 1101, or one terminal device 1102 may be within the coverage range of network device 1101 while the other terminal device 1103 is outside the coverage range of network device 1101.

[0249] In some embodiments, the terminal device includes the apparatus 900 described in the embodiment of the third aspect, and is configured to perform the method described in the embodiment of the first aspect. Since the method has been described in detail in the embodiment of the first aspect, its content is incorporated herein and will not be repeated.

[0250] In some embodiments, the network device includes the apparatus 1000 described in the embodiment of the third aspect, configured to perform the method described in the embodiment of the second aspect. Since the method has been described in detail in the embodiment of the second aspect, its content is incorporated herein and will not be repeated.

[0251] An embodiment of the present application further provides a terminal device, which may be, for example, a UE, but the present application is not limited thereto and may also be other devices.

[0252] Figure 12 is a schematic diagram of a terminal device according to an embodiment of the present application. As shown in Figure 12 , terminal device 1200 may include a processor 1210 and a memory 1220. Memory 1220 stores data and programs and is coupled to processor 1210. It should be noted that this diagram is exemplary; other types of structures may be used to supplement or replace this structure to implement telecommunication or other functions.

[0253] For example, the processor 1210 may be configured to execute a program to implement the method described in the embodiment of the first aspect.

[0254] As shown in Figure 12 , the terminal device 1200 may further include: a communication module 1230, an input unit 1240, a display 1250, and a power supply 1260. The functions of these components are similar to those in the prior art and are not described in detail here. It is worth noting that the terminal device 1200 does not necessarily include all of the components shown in Figure 122 , and these components are not essential. Furthermore, the terminal device 1200 may also include components not shown in Figure 12 , for which reference may be made to the prior art.

[0255] An embodiment of the present application further provides a network device, which may be, for example, a base station, but the present application is not limited thereto and may also be other network devices.

[0256] Figure 13 is a schematic diagram illustrating the structure of a network device according to an embodiment of the present application. As shown in Figure 13 , network device 1300 may include a processor 1310 (e.g., a central processing unit (CPU)) and a memory 1320. Memory 1320 is coupled to processor 1310. Memory 1320 may store various data and may also store an information processing program 1330, which is executed under the control of processor 1310.

[0257] For example, the processor 1310 may be configured to execute a program to implement the method as described in the embodiment of the second aspect.

[0258] In addition, as shown in FIG13 , network device 1300 may further include: a transceiver 1340 and an antenna 1350, etc.; wherein, the functions of the above components are similar to those in the prior art and are not described in detail here. It is worth noting that network device 1300 does not necessarily include all the components shown in FIG13 ; in addition, network device 1300 may also include components not shown in FIG13 , and reference may be made to the prior art for details.

[0259] An embodiment of the present application further provides a computer program, wherein when the program is executed in a terminal device, the program causes the terminal device to execute the method described in the embodiment of the first aspect.

[0260] An embodiment of the present application further provides a storage medium storing a computer program, wherein the computer program enables a terminal device to execute the method described in the embodiment of the first aspect.

[0261] An embodiment of the present application further provides a computer program, wherein when the program is executed in a network device, the program causes the network device to execute the method described in the embodiment of the second aspect.

[0262] An embodiment of the present application further provides a storage medium storing a computer program, wherein the computer program enables a network device to execute the method described in the embodiment of the second aspect.

[0263] The above devices and methods of the present application can be implemented by hardware or by a combination of hardware and software. The present application relates to such a computer-readable program that, when executed by a logic component, enables the logic component to implement the devices or components described above, or enables the logic component to implement the various methods or steps described above. The present application also relates to a storage medium for storing the above program, such as a hard disk, a magnetic disk, an optical disk, a DVD, a flash memory, etc.

[0264] The method / device described in conjunction with the embodiments of the present application can be directly embodied as hardware, a software module executed by a processor, or a combination of the two. For example, one or more of the functional block diagrams shown in the figure and / or one or more combinations of functional block diagrams can correspond to various software modules of the computer program flow or to various hardware modules. These software modules can respectively correspond to the various steps shown in the figure. These hardware modules can be implemented by solidifying these software modules, for example, using a field programmable gate array (FPGA).

[0265] The software module may be located in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. A storage medium may be coupled to a processor so that the processor can read information from the storage medium and write information to the storage medium; or the storage medium may be an integral part of the processor. The processor and the storage medium may be located in an ASIC. The software module may be stored in the memory of the mobile terminal or in a memory card that can be inserted into the mobile terminal. For example, if the device (such as a mobile terminal) uses a large-capacity MEGA-SIM card or a large-capacity flash memory device, the software module may be stored in the MEGA-SIM card or the large-capacity flash memory device.

[0266] One or more of the functional blocks and / or one or more combinations of functional blocks described in the accompanying drawings may be implemented as a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component, or any appropriate combination thereof for performing the functions described in this application. One or more of the functional blocks and / or one or more combinations of functional blocks described in the accompanying drawings may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in communication with a DSP, or any other such configuration.

[0267] The present application has been described above in conjunction with specific embodiments. However, those skilled in the art should understand that these descriptions are merely illustrative and are not intended to limit the scope of protection of the present application. Those skilled in the art may make various modifications and variations to the present application based on the spirit and principles of the present application, and such modifications and variations are also within the scope of the present application.

[0268] Regarding the implementation methods including the above embodiments, the following additional notes are also disclosed:

[0269] 1. A method for configuring event-driven beam management, wherein the method comprises:

[0270] The network device sends configuration information to the terminal device, where the configuration information includes first configuration information, where the first configuration information includes a set of measurement signal resources for detecting an event-driven beam management event;

[0271] The network device receives the non-periodic CSI sent by the terminal device, where the non-periodic CSI includes beam management information, and the non-periodic CSI is sent by the terminal device after receiving information that triggers the non-periodic CSI reporting for event-driven beam management when the terminal device uses the measurement signal resource set to detect a beam management event.

[0272] 2. The method according to Supplement 1, wherein:

[0273] The configuration information also includes second configuration information, which is SR configuration information for event-driven beam management.

[0274] 3. The method according to Supplementary Note 2, wherein the method further comprises:

[0275] The network device receives a scheduling request sent by a terminal device, where the scheduling request is sent to the network device by the terminal device after detecting an event-driven beam management event using the SR resources configured by the SR configuration information for event-driven beam management.

[0276] 4. The method according to Supplementary Note 3, wherein the method further comprises:

[0277] The network device sends uplink scheduling authorization information for scheduling PUSCH to the terminal device, where the uplink scheduling authorization information includes a CSI request field, and the CSI request field is used to trigger non-periodic CSI reporting associated with event-driven beam management.

[0278] 5. The method according to Supplementary Note 1, wherein the method further comprises:

[0279] The network device sends activation signaling for activating event-driven beam management event detection to the terminal device, where the activation signaling indicates that one or more measurement signal resource sets in the measurement signal resource sets are used for beam management event detection.

[0280] 6. The method according to Supplement 1, wherein:

[0281] The measurement signal resource set used to detect event-driven beam management events is a measurement signal resource set, and the measurement signal resource set includes one to multiple measurement signal resources.

[0282] 7. The method according to Supplement 1, wherein:

[0283] The measurement signal resource set used to detect event-driven beam management events is one to multiple measurement signal resource sets, and each of the measurement signal resource sets includes one to multiple measurement signal resources.

[0284] 8. The method according to Supplement 1, wherein:

[0285] The configuration information also includes third configuration information, which is non-periodic CSI triggering state configuration information for event-driven beam management.

[0286] 9. The method according to Supplement 1, wherein:

[0287] The configuration information also includes fourth configuration information, which is CSI reporting configuration information for event-driven beam management.

[0288] 10. The method according to Supplement 1, wherein:

[0289] The measurement signal resource set used to detect event-driven beam management events is indicated or configured by the downlink or joint TCI state list dl-OrJointTCI-StateList in the RRC information element PDSCH-Config.

Claims

1. An event-driven beam management device, configured in a terminal device, wherein: The device comprises: a receiving unit configured to receive configuration information sent by a network device, wherein the configuration information includes first configuration information, and the first configuration information includes a measurement signal resource set for detecting an event-driven beam management event; A processing unit uses the measurement signal resource set to detect beam management events, and sends non-periodic channel state information (CSI) after receiving information that triggers non-periodic CSI reporting for event-driven beam management, wherein the non-periodic CSI includes beam management information.

2. The device according to claim 1, wherein The configuration information further includes second configuration information, where the second configuration information is scheduling request (SR) configuration information for event-driven beam management; After detecting an event-driven beam management event, the processing unit sends a scheduling request to the network device using the SR resources configured by the SR configuration information for event-driven beam management; The receiving unit receives uplink scheduling grant information sent by the network device, where the uplink scheduling information is used to schedule a physical uplink shared channel (PUSCH), and the uplink scheduling grant information includes a CSI request field, where the CSI request field is used to trigger aperiodic CSI reporting associated with event-driven beam management; The processing unit sends the aperiodic CSI on the scheduled PUSCH.

3. The device according to claim 1, wherein The receiving unit receives activation signaling for activating event-driven beam management event detection, where the activation signaling indicates that one or more measurement signal resource sets in the measurement signal resource set are used for the beam management event detection; The processing unit uses the measurement signal resources included in the activated measurement signal resource set to perform beam management event detection.

4. The device according to claim 1, wherein The measurement signal resource set used to detect event-driven beam management events is a measurement signal resource set, and the measurement signal resource set includes one to multiple measurement signal resources.

5. The device according to claim 4, wherein The measurement signal resource set is configured in the information element CSI-MeasConfig, and the measurement signal resource set is a channel state information reference signal (CSI-RS) resource set or a synchronization signal block (SSB) resource set.

6. The device according to claim 5, wherein The CSI-RS resource set is a list nzp-CSI-RS-ResourceToAddModList-EventBM, and the list includes one to multiple CSI-RS resources.

7. The device according to claim 5, wherein The SSB resource set is csi-SSB-ResourceSet-EventBM, whose value is a CSI-SSB-ResourceSet, and the CSI-SSB-ResourceSet contains one to multiple SSB indexes, and the SSB index corresponds to the SSB resource.

8. The device according to claim 1, wherein The measurement signal resource set used to detect event-driven beam management events is one to multiple measurement signal resource sets, and each of the measurement signal resource sets includes one to multiple measurement signal resources.

9. The device according to claim 8, wherein The measurement signal resource set is configured in the information element CSI-MeasConfig, and the measurement signal resource set is a CSI-RS resource set list and / or an SSB resource set list.

10. The device according to claim 9, wherein The CSI-RS resource set list is nzp-CSI-RS-ResourceSetToAddModList-EventBM, and the list contains one to multiple CSI-RS resource sets, and the CSI-RS resource set includes one to multiple CSI-RS resources.

11. The device according to claim 9, wherein The SSB resource set list is csi-SSB-ResourceSetSetToAddModList-EventBM, and the list contains one to multiple SSB resource sets. The SSB resource set includes one to multiple SSB indexes, and the SSB index corresponds to the SSB resource.

12. The device according to claim 4, wherein The measurement signal resource includes physical cell identification information to indicate the serving cell to which the measurement signal resource belongs.

13. The device according to claim 1, wherein The configuration information also includes third configuration information, which is non-periodic CSI trigger status configuration information for event-driven beam management. The terminal device confirms whether the non-periodic CSI reporting for event-driven beam management is triggered based on the non-periodic CSI trigger status configuration information.

14. The device according to claim 13, wherein The aperiodic CSI trigger state configuration information is an aperiodic CSI trigger state list, the aperiodic CSI trigger state list includes one to multiple aperiodic CSI trigger states, and only one aperiodic CSI trigger state among the multiple aperiodic CSI trigger states includes reporting configuration information associated with event-driven beam management, which is called the first aperiodic CSI trigger state. Periodic CSI trigger status.

15. The device according to claim 14, wherein When the CSI request code point corresponding to the first aperiodic CSI triggering state is k and the value of the CSI request field of the uplink scheduling grant information used for scheduling PUSCH is also k, the first aperiodic CSI triggering state is initiated.

16. The device according to claim 1, wherein The configuration information also includes fourth configuration information, which is CSI reporting configuration information for event-driven beam management. The terminal device sends the non-periodic CSI on the scheduled PUSCH according to the CSI reporting configuration information.

17. The device according to claim 16, wherein The CSI reporting configuration information includes one or more groups of beam information and the number of groups of beam information. Each group of beam information corresponds to one measurement signal resource. Each group of beam information includes at least one of the following information: CSI-RS resource set identification information and / or SSB resource set identification information; CRI / SSBRI information; L1-RSRP / L1-SINR information; Physical cell identification information (Physical cell ID); TCI state identification information (TCI-StateId).

18. The device according to claim 1, wherein The measurement signal resource set used to detect event-driven beam management events is determined by the downlink or joint TCI state list dl-OrJointTCI-StateList in the RRC information element PDSCH-Config.

19. The device according to claim 18, wherein For each TCI-State in the downlink or joint TCI state list dl-OrJointTCI-StateList, if the qcl-Type value in the field qcl-Type2 is 'typeD', the source RS in the field qcl-Type2 serves as a measurement signal resource and is an element in the measurement signal resource set.

20. A terminal device comprising a memory and a processor, wherein the memory stores a computer program, wherein: The processor is configured to execute the computer program to implement the following method: receiving configuration information sent by a network device, where the configuration information includes first configuration information, where the first configuration information includes a measurement signal resource set for detecting an event-driven beam management event; The measurement signal resource set is used to perform beam management event detection, and aperiodic CSI is sent after receiving information triggering aperiodic CSI reporting for event-driven beam management, where the aperiodic CSI includes beam management information.

Images