A communication method and a communication device

Abstract

The application provides a communication method and a communication device, and relates to the technical field of communication. In response to multiple events being triggered at the same time, a UE can screen the multiple events to obtain a first event. Each event in the multiple events is used for triggering a terminal device to send a beam report. Then, the UE sends a PUCCH to a base station. The base station schedules a transmission resource of a PUSCH for the UE to send a beam report of the first event according to the first event, without scheduling a transmission resource of a PUSCH for the UE to send a beam report of each event in the multiple events. Then, the UE can send the beam report of the first event to the base station based on the transmission resource of the PUSCH, thereby avoiding the sending of the beam reports of all the triggered events, sending the beam reports of only part of the events, and reducing the occupation of resources.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a communication method and communication device. Background Technology

[0002] Beam management involves reporting beam reports. These reports include measurements of beam signal quality and other parameters. Currently, terminal devices implement beam management by reporting beam reports based on event-driven mechanisms. Event-driven beam reporting refers to configuring a series of beam-related events for the terminal device; when these events are triggered, the terminal device reports the beams associated with those events.

[0003] Specifically, how terminal devices can report beam reports based on event-driven mechanisms is an issue that needs to be discussed. Summary of the Invention

[0004] This application provides a communication method and communication device for uploading beam reports of some of the multiple events when multiple events are triggered simultaneously, thereby reducing the occupancy of PUSCH transmission resources.

[0005] To achieve the above objectives, this application adopts the following technical solution:

[0006] In a first aspect, this application provides a communication method applied to a terminal device. In response to the triggering of multiple events, the terminal device can send a Physical Uplink Control Channel (PUCCH) to a network device. The PUCCH is used to instruct the network device to schedule transmission resources for the Uplink Physical Shared Channel (PUSCH) according to a first event. The first event includes at least one event determined from events with the same beam information based on the priority of events with the same beam information among the multiple events. Each of the multiple events is used to trigger the terminal device to send a beam report.

[0007] Subsequently, the terminal device can send a beam report of the beam related to the first event to the network device based on the transmission resources of PUSCH.

[0008] In this application, when a terminal device triggers multiple events, it requests the network device to allocate PUSCH transmission resources for sending beam reports of beams related to some of the events, instead of allocating PUSCH transmission resources for sending beam reports of all the events. This reduces resource consumption, lowers signaling overhead, and solves the problem of resource waste. Furthermore, since events with identical beam information have overlapping functions, events with identical beam information are filtered based on event priority to ensure the accuracy of event filtering. This avoids unnecessary transmission of beam reports of event-related beams, thereby preventing duplicate beam information reporting.

[0009] The transmission resources of the PUSCH mentioned above can be the time-domain resources of the PUSCH.

[0010] Optionally, the first event mentioned above is at least one event obtained by filtering multiple events.

[0011] In one possible design, the PUCCH includes an identifier for the first event, enabling network devices to directly determine the events for which beam reports of the relevant beam need to be submitted. This allows them to dynamically schedule transmission resources for terminal devices based on the event, thereby reducing resource consumption.

[0012] Optionally, the PUCCH also includes a first identifier corresponding to the identifier of the first event. The first identifier indicates that a beam report related to the first event corresponding to the first identifier should be sent to the network device. Based on this, the network device can determine through the first identifier that a beam report of the relevant beam of its corresponding first event needs to be reported, and can then dynamically schedule transmission resources for the terminal device according to the event, thereby reducing resource consumption.

[0013] Optionally, the PUCCH also includes an identifier for a second event. Beam reports for the beam associated with the second event are not sent to the network device. The second event is an event other than the first event among multiple events. Based on this, the network device can obtain all events triggered by the terminal device, and can obtain the events for which beam reports of the relevant beams in all triggered events need to be reported, thereby accurately scheduling transmission resources for the terminal device.

[0014] Optionally, the PUCCH also includes a second identifier corresponding to the identifier of the second event; the second identifier indicates that a beam report related to the second event corresponding to the second identifier should not be sent to the network device. Based on this, the network device can obtain all events triggered by the terminal device, and can obtain the events for which beam reports of the relevant beams in all triggered events need to be reported, thereby accurately scheduling transmission resources for the terminal device.

[0015] In one possible design approach, when events with the same beam information have different priorities, the first event includes the highest-priority event among those with the same beam information. Based on this, it's highly likely that the beam information in the beam report of a lower-priority event among those with the same beam information is a subset of the beam information in the beam report of a higher-priority event. Therefore, the terminal device can use the highest-priority event among those with the same beam information as the first event, filtering out other events to ensure the accuracy of event filtering.

[0016] When events with the same beam information all have the same priority, the first event includes all events within the same beam information. Events with the same priority have minimal functional overlap; therefore, the terminal device does not need to filter events with the same priority.

[0017] In one possible design, the terminal device can receive a first message sent by the network device; wherein the first message indicates the priority of all events, in other words, the first message is used to indicate the priority of each of a plurality of events.

[0018] In one possible design approach, the priority of each event among multiple events is determined based on the inclusion relationship between the multiple events.

[0019] In one possible design approach, the priority of the aforementioned events is determined based on a threshold among the third events. In other words, the priority of each of the aforementioned events is determined based on a threshold among the third events.

[0020] In one possible design approach, when there are non-preset events other than preset events among multiple events, the first event includes the event determined from the non-preset events based on the beam information of the non-preset events, that is, the event selected from the non-preset events;

[0021] Here, a preset event refers to an event in which a beam report of a relevant beam is sent to the network device. In other words, a preset event is an event configured in advance to require the reporting of beam reports of the relevant beam. Based on this, since the beam reports of the relevant beams for preset events are required to be reported, the terminal device does not need to determine whether the preset event among the multiple triggered events needs to be reported, thereby avoiding unnecessary event filtering.

[0022] Secondly, this application provides a communication method applied to a network device. The network device receives a Physical Uplink Control Channel (PUCCH) sent by a terminal device. In response to the PUCCH, the network device schedules transmission resources of the Uplink Physical Shared Channel (PUSCH) for the terminal device according to a first event; the first event includes at least one event determined by the terminal device from events with the same beam information based on the priority of events with the same beam information among a plurality of triggered events, each of the plurality of events being used to trigger the terminal device to send a beam report;

[0023] Subsequently, the network device receives a beam report of the beam related to the first event, sent by the terminal device based on the transmission resources of PUSCH.

[0024] In one possible design, the network device receives the Physical Uplink Control Channel (PUCCH) sent by the terminal device; wherein the PUCCH is used to indicate a beam report of a beam related to a first event; the first event is at least one event selected by the terminal device from a plurality of triggered events, each of the plurality of events being used to trigger the terminal device to send a beam report;

[0025] In response to the PUCCH, scheduling information is sent to the terminal device; the scheduling information is used to indicate the transmission resources of the uplink physical shared channel PUSCH.

[0026] The receiving terminal device sends a PUSCH via the PUSCH transmission resources. The PUSCH carries a beam report of the beam associated with the first event.

[0027] In one possible design, the network device sends a first message (or first indication information) to the terminal device; wherein the first indication information indicates the priority of each of a plurality of events.

[0028] In one possible design approach, the priority of each event among multiple events is determined based on the inclusion relationship between the multiple events;

[0029] The inclusion relationship between multiple events is determined based on the threshold of the events within the multiple events.

[0030] In one possible design approach, PUCCH includes an identifier for the first event.

[0031] In one possible design, the PUCCH also includes a first identifier corresponding to the identifier of the first event, which is used to indicate the beam report of the beam related to the first event.

[0032] In one possible design, PUCCH also includes an identifier for a second event, which is an event other than the first event among a plurality of events. The identifier for the second event is used to indicate that the second event has been triggered.

[0033] In one possible design, the PUCCH also includes a second identifier corresponding to the identifier of the second event; the second identifier indicates that beam reporting of the beam associated with the second event is not reported.

[0034] In one possible design approach, when events with the same beam information have different priorities, the first event includes the event obtained by filtering out the events with lower priority among the events with the same beam information from multiple events.

[0035] In one possible design approach, the priority of an event is determined based on a threshold among all events, specifically the third event.

[0036] In one possible design approach, when there are non-preset events other than preset events among multiple events, the first event includes events selected from the non-preset events based on the beam information of the non-preset events;

[0037] Among them, the preset events are preset events that require reporting beam reports of the relevant beams.

[0038] In one possible design approach, the first event includes a preset event among multiple events.

[0039] Thirdly, this application provides a communication device, including a module for performing the communication method of the first aspect above; and / or a module for performing the communication method of the second aspect above.

[0040] Among them, the communication device can be used as a network device or a terminal device.

[0041] Fourthly, embodiments of this application provide a communication system that may include a terminal device and a network device. The terminal device is used to perform the communication method as described in the first aspect above, and / or the network device is used to perform the communication method as described in the second aspect above.

[0042] In this process, the terminal device sends a Physical Uplink Control Channel (PUCCH) to the network device in response to multiple events. The PUCCH is used to instruct the network device to schedule the transmission resources of the Uplink Physical Shared Channel (PUSCH) according to a first event. The first event includes at least one event determined from events with the same beam information based on the priority of events with the same beam information among the multiple events. Each of the multiple events is used to trigger the terminal device to send a beam report.

[0043] Network devices receive PUCCH;

[0044] In response to the PUCCH, the network device schedules uplink physical shared channel (PUSCH) transmission resources for the terminal device based on the first event.

[0045] Based on the transmission resources of PUSCH, the terminal device sends a beam report of the beam related to the first event to the network device;

[0046] The network device receives a beam report of the beam associated with the first event.

[0047] Fifthly, this application provides a communication device, comprising: at least one processor and an interface circuit, wherein the interface circuit is configured to receive signals from other communication devices outside the communication device and transmit them to the processor or to send signals from the processor to other communication devices outside the communication device, and the processor is configured to implement the communication methods of the first aspect and / or the second aspect above through logic circuits or execution code instructions.

[0048] Sixthly, this application provides a computer-readable storage medium including a computer program or instructions that, when executed on a computer, cause the computer to perform the communication methods described in the first and / or second aspects above.

[0049] In a seventh aspect, this application provides a chip, including: an interface circuit and a logic circuit. The interface circuit is used to receive signals from other chips outside the chip and transmit them to the logic circuit, or to send signals from the logic circuit to other chips outside the chip. The logic circuit is used to implement the communication methods of the first aspect and / or the second aspect above.

[0050] Eighthly, this application provides a computer program product comprising: a computer program or instructions that, when executed on a computer, cause the computer to perform the communication methods as described in the first and / or second aspects above.

[0051] It is understood that any of the communication devices, communication systems, chips, computer-readable storage media, or computer program products provided above can be applied to the corresponding methods provided above. Therefore, the beneficial effects they can achieve can be referred to the beneficial effects described in the corresponding methods. Furthermore, the communication method provided in the second aspect can also refer to the relevant descriptions and beneficial effects in the communication method provided in the first aspect, and will not be repeated here. Attached Figure Description

[0052] Figure 1 This application provides a schematic diagram of the structure of a communication system according to an embodiment of the present application.

[0053] Figure 2 A flowchart illustrating a communication method provided in an embodiment of this application. Figure 1 ;

[0054] Figure 3 A schematic diagram of a PUCCH provided for an embodiment of this application. Figure 1 ;

[0055] Figure 4 A flowchart illustrating a communication method provided in an embodiment of this application. Figure 2 ;

[0056] Figure 5AA schematic diagram of a PUCCH provided for an embodiment of this application. Figure 2 ;

[0057] Figure 5B A schematic diagram of a PUCCH provided for an embodiment of this application. Figure 3 ;

[0058] Figure 6A A schematic diagram of a PUCCH provided for an embodiment of this application. Figure 4 ;

[0059] Figure 6B Figure 5 shows a schematic diagram of a PUCCH provided in an embodiment of this application. Detailed Implementation

[0060] In the description of this application, unless otherwise stated, " / " indicates that the objects before and after are in an "or" relationship. For example, A / B can mean A or B. "And / or" in this application is merely a description of the relationship between the related objects, indicating that there can be three relationships. For example, A and / or B can mean: A exists alone, A and B exist simultaneously, and B exists alone. A and B can be singular or plural.

[0061] In the description of this application, unless otherwise stated, "multiple" means two or more. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of a single item or a plurality of items. For example, at least one of a, b, or c can mean: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or multiple.

[0062] Furthermore, to facilitate a clear description of the technical solutions in the embodiments of this application, the terms "first," "second," "1," "2," "A," "B," and "C" are used in the embodiments of this application to distinguish identical or similar items with essentially the same function and effect. Those skilled in the art will understand that the terms "first," "second," etc., do not limit the quantity or execution order, and that the terms "first," "second," etc., are not necessarily different.

[0063] In the embodiments of this application, the terms "exemplary" or "for example" are used to indicate that something is an example, illustration, or description. Any embodiment or design that is described as "exemplary" or "for example" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or design. Specifically, the use of terms such as "exemplary" or "for example" is intended to present the relevant concepts in a specific manner to facilitate understanding.

[0064] It is understood that the term "embodiment" used throughout the specification means that a specific feature, structure, or characteristic related to an embodiment is included in at least one embodiment of this application. Therefore, various embodiments throughout the specification do not necessarily refer to the same embodiment. Furthermore, these specific features, structures, or characteristics can be combined in any suitable manner in one or more embodiments. It is understood that in the various embodiments of this application, the sequence number of each process does not imply the order of execution; the execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0065] It is understood that in this application, "...when" and "if" both refer to the corresponding processing that will be carried out under certain objective circumstances, and are not limited to a specific time, nor do they require a judgment action to be performed during implementation, nor do they imply any other limitations.

[0066] It is understood that some optional features in the embodiments of this application can be implemented independently in certain scenarios without relying on other features, such as the current solution on which they are based, to solve the corresponding technical problems and achieve the corresponding effects. Alternatively, they can be combined with other features as needed in certain scenarios. Correspondingly, the apparatus given in the embodiments of this application can also implement these features or functions, which will not be elaborated here.

[0067] In this application, unless otherwise specified, the same or similar parts between the various embodiments can be referred to each other. Unless otherwise specified or logically conflicting, the terminology and / or descriptions between different embodiments are consistent and can be mutually referenced. Different embodiments can be combined to form new embodiments based on their inherent logical relationships. The following descriptions of the embodiments of this application do not constitute a limitation on the scope of protection of this application.

[0068] First, to facilitate understanding of the embodiments of this application, the relevant terms involved in the embodiments of this application are explained:

[0069] A beam is a directional distribution of electromagnetic waves emitted by an antenna array in space.

[0070] Beam management refers to the management of scanning, reporting, and maintenance of static beams. Beam management can include beam scanning, beam measurement, beam identification, beam report reporting / reporting beam reports, and beam fault recovery. For example, beam management can be implemented in Mode A, meaning that the traditional event-triggered transmission process corresponding to Mode A can be used for beam management. The relevant description of Mode A can be found in existing technologies and will not be elaborated further.

[0071] A beam report refers to a terminal device reporting beam measurement results to a network device. The terminal device can report beams based on event-driven / triggered events. The beam report may carry beam information, including beam identifiers. Of course, beam information may also include other information, such as beam direction. For example, the terminal device can obtain the beam information to be reported, encapsulate it, and generate a corresponding beam report. Of course, the beam report may also include other information, and this application does not limit it. In this application, "event" can be replaced with a driving event, a triggering event, an event that triggers beam report reporting, a beam report-related event, or a beam-related event, etc.

[0072] This application provides a communication system, and the method provided in this application can be applied to... Figure 1 The communication system shown. (As shown) Figure 1 As shown, a communication system includes network equipment and terminal equipment. Network equipment is a device deployed in a radio access network to provide wireless communication functions for terminal equipment. Network equipment can include various forms of macro base stations, micro base stations (also called small cells), relay stations, access points, etc. In systems employing different radio access technologies, the name of the network equipment may differ, such as a base transceiver station (BTS) in a Global System for Mobile Communication (GSM) or Code Division Multiple Access (CDMA) network, a node B (NB) in Wideband Code Division Multiple Access (WCDMA), and an evolved Node B (eNB) in Long Term Evolution (LTE). Network equipment can also be a radio controller in a cloud radio access network (CRAN) scenario. Network equipment can also be base station equipment in fifth-generation (5G) mobile communication systems or next-generation wireless communication networks, or network equipment in future evolved Public Land Mobile Network (PLMN) networks. Network equipment can also be wearable devices or vehicle-mounted devices. Network equipment can also be transmission and reception points (TRPs).

[0073] The aforementioned terminal devices can be environmental IoT devices, including various handheld devices, in-vehicle devices, wearable devices, computing devices, or other processing devices connected to a wireless modem with wireless communication capabilities. Terminals can be mobile stations (MS), subscriber units, cellular phones, smartphones, wireless data cards, personal digital assistant (PDA) computers, tablet computers, wireless modems, handsets, laptop computers, machine-type communication (MTC) terminals, etc.

[0074] The aforementioned communication systems can be applied to Long Term Evolution (LTE) systems, Universal Mobile Telecommunications System (UMTS) systems, Code Division Multiple Access (CDMA) systems, Wireless Local Area Network (WLAN) systems, or the Fifth Generation (5G) systems or next-generation wireless communication systems, etc.

[0075] During beam management, network devices can configure beam reporting settings for terminal devices (or user equipment, UE). These settings can include the type of beam report, such as periodic beam reporting or aperiodic beam reporting. Based on these settings, the terminal device can send beam reports to the network device to obtain the optimal beam in a timely manner. To reduce overhead and ensure timely detection of beam quality changes, multiple events can be configured for the UE. When a configured event is triggered, the UE can initiate a beam report (hereinafter referred to as an event report) for the beam associated with that event. Since the UE may trigger multiple events simultaneously, a beam report needs to be initiated for each of the triggered events. If the UE uses Mode A (dynamic scheduling of uplink control information (UCI) by the base station), which corresponds to the traditional event-triggered transmission process, the network device needs to dynamically schedule uplink channel resources (such as PUSCH transmission resources) for the UE. These uplink channel resources are used to send beam reports for each of the triggered events.

[0076] The multiple events configured for the UE mentioned above may include several of the following events:

[0077] Event 1: The quality of the UE's current beam is below threshold 1. Here, the current beam refers to the beam the UE is currently using to maintain the current connection between the network device and the UE.

[0078] Event 2: There exists at least one new beam with a quality higher than the current beam, and the quality difference between the two beams is greater than the threshold 2. In other words, there exists a new beam with a quality higher than the current beam, and the quality difference between the new beam and the current beam is greater than the threshold 2.

[0079] In this application, a new beam can refer to a candidate beam that is to replace the current beam in providing services to the terminal device. The new beam can be a neighboring beam in the current beam, etc.

[0080] Event 3: A new beam exists with a quality higher than threshold 3.

[0081] Event 4: The quality of the current beam is below threshold 4, and the quality of at least one new beam is above threshold 5.

[0082] Event 5: The absolute value of the quality difference between the current beam and at least one new beam is below threshold 6. In other words, there exists a new beam whose absolute value of the quality difference between it and the current beam is below threshold 6. It can be understood that the quality difference between the current beam and multiple new beams represents the quality difference between the current beam and each of the multiple new beams.

[0083] Event 6: The current beam is not among the K best quality beams (the K beams are beams outside the configured measurement and reporting beams), where K is a positive integer greater than 1.

[0084] Event 7a: There exists at least one new beam whose quality is higher than the worst quality of the reference signal (RS) associated with the activated transmission configuration indicator (TCI) state, and the quality difference is greater than threshold 7. In other words, there exists a new beam whose quality is higher than the lowest quality RS associated with the activated TCI, and the quality difference between the new beam and the RS is greater than threshold 7.

[0085] Event 7b: There exists at least one new beam whose quality is higher than the best quality of the reference signal (RS) associated with the active transmission configuration indicator (TCI) state, and the quality difference is greater than threshold 8. In other words, there exists a new beam whose quality is higher than the highest quality RS associated with the active TCI, and the quality difference between the new beam and the RS is greater than threshold 8.

[0086] Event 8: The quality of each of the M new beams is higher than that of the current beam, and the quality difference between each of the M new beams and the current beam is greater than the threshold 9, where M is a positive integer greater than 1. In other words, there exist multiple new beams with higher quality than the current beam and a quality difference between them greater than the threshold 9.

[0087] Event 9: There is at least one new beam whose quality is higher than that of the configured RS, and the quality difference is greater than a threshold of 10. In other words, there is a new beam with quality higher than that of the configured RS, and the quality difference between it and the configured RS is greater than a threshold of 10.

[0088] In this application, the aforementioned reference signal may include, but is not limited to, channel state information-reference signal (CSI-RS) and synchronization signal block (SSB).

[0089] In this application, the thresholds in the events (such as thresholds 1-10 mentioned above) can be configured by the network device or predefined by the protocol, and are not limited thereto. It is understood that an event being triggered indicates that the beam associated with that event satisfies the event, the conditions corresponding to the event, or the relevant requirements corresponding to the event. The beam associated with the event can be understood as the beam involved in the event. For example, if event 1 is associated with the current beam, and event 1 is triggered, it indicates that the quality of the current beam is lower than threshold 1. The quality of the current beam being lower than threshold 1 is the condition corresponding to event 1.

[0090] Optionally, when the UE triggers multiple events, the traditional event triggering transmission process corresponding to mode A above can be as follows: Figure 2Steps 1-5 are shown below. First, the network device can perform step 1, sending a reference signal to the UE. Then, after receiving the reference signal, the UE can perform step 2, recording the identifier of each event in response to multiple triggered events. Additionally, the UE can also record the beam information of the triggered events. The beam information includes information about the current beam and information about the new beam. The current beam information includes, but is not limited to, the identifier of the current beam. The new beam information includes, but is not limited to, the identifier of the new beam.

[0091] Then, the UE can perform step 3, sending a traditional physical uplink control channel carrying an identifier for each event to the network device. The traditional physical uplink control channel (PUCCH) is used to request transmission resources for the physical uplink shared channel (PUSCH) used to send reports of each event. Optionally, Figure 3 The PUCCH mentioned is a traditional PUCCH. For example... Figure 3 As shown, a traditional PUCCH can include identifiers for multiple events to indicate the various events triggered by the UE and request transmission resources for the PUSCH, thereby enabling the UE to utilize the transmission resources of the PUSCH to transmit beam reports of the various events triggered by the UE.

[0092] After receiving the PUCCH, the network device can execute step 4: dynamically schedule PUSCH transmission resources for the UE based on the identifiers of each event in the PUCCH. Then, the UE can execute step 5: based on the PUSCH transmission resources, send beam reports for each event to the network device, that is, send beam reports for all triggered events. The event beam reports are generated based on the event beam information. For example, the network device sends scheduling information to the UE based on the identifiers of each event in the PUCCH, which instructs the network device to dynamically schedule PUSCH transmission resources for the UE. Correspondingly, the UE receives the scheduling information from the network device. The UE then sends beam reports of beams related to each event to the network device based on the PUSCH transmission resources, that is, sends beam reports of beams related to all triggered events.

[0093] However, since the functions of events may partially overlap, meaning the beam information in the beam report of one event might be a subset of the beam information in the beam report of another event, reporting all events triggered by the UE to the network device could lead to duplicate beam information reporting, resulting in a waste of uplink channel resources (such as PUCCH and PUSCH). The function of an event, also known as event information, can refer to the conditions corresponding to the event, or the beam information carried in the beam report that should be reported when the event is triggered.

[0094] Therefore, to address the aforementioned issues, this application provides an event filtering mechanism based on user-initiated (UEI) / event-driven (ED) principles, specifically an event-triggered transmission process for Mode A, or a communication method. When multiple events configured by the terminal device are triggered simultaneously, the terminal device can filter these events, sending only beam reports for a subset of the events, rather than sending beam reports for all events. This allows the network device to allocate fewer PUSCH transmission resources, reducing PUSCH resource consumption. Furthermore, it avoids resource waste caused by duplicate beam information reporting.

[0095] The implementation process of the communication method provided in this application will be described in detail below. For example... Figure 4 As shown, the implementation process may include S201-S205.

[0096] S201. In response to multiple events being triggered, the terminal device sends a PUCCH to the network device.

[0097] Specifically, the PUCCH is used to instruct the network device to schedule the transmission resources of the PUSCH according to the first event (or described as transmission resources for requesting the network device to configure the transmission of beam reports related to the first event for the terminal device). Alternatively, the PUCCH is used to instruct the reporting of beam reports related to the first event, or to instruct the terminal device to report beam reports related to the first event; or to instruct that the first event has been triggered and beam reports related to the first event are to be reported; or to request the network device to schedule the transmission resources of the PUSCH carrying / carrying beam reports related to the first event.

[0098] Optionally, the transport resources of PUSCH may include the time-domain resources of PUSCH.

[0099] In this application, the first event is at least one event determined from a plurality of events, that is, the first event is at least one event selected from a plurality of events, and each of the plurality of events is used to trigger the terminal device to send a beam report. The plurality of events may refer to the plurality of events 1-9 described above.

[0100] In this embodiment, the terminal device is configured with different events, each of which triggers the terminal device to send a beam report. That is, when an event is triggered, the terminal device should send a beam report for that event to the network device. Correspondingly, when multiple events are triggered simultaneously, the terminal device should send beam reports for each of the multiple events to the network device. However, to reduce resource consumption, when the terminal device triggers multiple events, it can determine at least one event from these events (i.e., filter out at least one event), that is, determine a subset of events and designate this subset as the first event. The first event represents the event for which the beam report of the relevant beam actually needs to be reported; in other words, beam reports for events other than the first event do not actually need to be sent to the network device. Based on this, the terminal device achieves event filtering by determining the first event from the triggered multiple events.

[0101] Then, the terminal device can generate a PUCCH based on the first event. This PUCCH indicates the beam report of the beam related to the first event, that is, it instructs the network device to schedule the transmission resources of the PUSCH carrying the beam report of the beam related to the first event. In other words, this PUCCH instructs the network device to schedule the transmission resources of the PUSCH for the beam report of the first event for the terminal device, without the network device having to schedule the transmission resources of the PUSCH for the beam report of all triggered events, thus reducing resource consumption.

[0102] Optionally, in response to the triggering of multiple events, the terminal device records the identifier of each event and the beam information (or event beam information) of the beam associated with the event. The beam information may include current beam information and / or new beam information. The current beam information may include the identifier (ID) of the current beam, and the new beam information may include the identifier of the new beam. Optionally, when the beam associated with an event only includes the current beam, then when the event is triggered, it indicates that the condition corresponding to the event only involves the current beam, and the terminal device may only record the current beam information of the event, such as the identifier of the current beam. For example, when event 1 is triggered, the beam associated with event 1 only includes the current beam, so the terminal device may only record the identifier of the current beam.

[0103] Alternatively, when the beam associated with an event only includes the new beam, then when the event is triggered, it indicates that the condition corresponding to the event only involves the new beam, and the terminal device can only record the new beam information of the event, such as the identifier of the new beam. For example, when the above event 3 is triggered, the beam associated with event 3 only includes the new beam, so the terminal device can only record the identifier of the new beam.

[0104] Alternatively, when the beam associated with an event includes both the current beam and the new beam, then when the event is triggered, it indicates that the conditions corresponding to the event involve both the current beam and the new beam, and the terminal device can record the current beam information and the new beam information of the event. For example, when event 2 is triggered, the beam associated with event 2 includes both the current beam and the new beam, so the terminal device can record the identifier of the current beam and the identifier of the new beam.

[0105] In this application, the first event may include at least one event selected by the terminal device from multiple events based on the event's beam information. Specifically, the method for determining the first event can be referred to below, and will not be repeated here.

[0106] S202, Network devices receive PUCCH.

[0107] In one example, the above PUCCH includes an identifier for the first event. For example... Figure 5A As shown, the PUCCH can include only the identifier of the first event, that is, only the identifier of the triggered event that needs to be reported. Simply put, the PUCCH includes field 1, whose value is the identifier of the first event. The network device reads the identifier of the first event from the PUCCH, determines that the terminal device needs to report the first event, and thus schedules PUSCH transmission resources for the terminal device to send the beam report of the first event. In this example, the event identifier carried by the PUCCH implicitly indicates that the event indicated by the event identifier has been triggered and that a beam report related to the event indicated by the event identifier needs to be reported.

[0108] In another example, the PUCCH includes an event and an identifier corresponding to the event. The event identifier carried in the PUCCH is used to indicate that the event indicated by the event identifier has been triggered, while the identifier corresponding to the event carried in the PUCCH is used to indicate whether the event needs to be reported / is pending reporting / has been reported.

[0109] Specifically, such as Figure 5BAs shown, a PUCCH can include an event identifier and an identifier (or event reporting identifier) ​​corresponding to that event identifier. The event identifier is the identifier of the first event (i.e., the field value of the event identifier is the identifier of the first event), and the identifier is the first identifier (i.e., the field value of the identifier is the first identifier). The first identifier indicates that the identifier of its corresponding event is the identifier of the first event, meaning it indicates that a beam report for the first event corresponding to that first identifier needs to be sent to the network device. In other words, a PUCCH can include the identifier of the first event and the identifier corresponding to that first event identifier.

[0110] Additionally, the beam report of event-related beams in this application can be replaced by describing the beam report as event / event-related beam report.

[0111] In another example, PUCCH includes not only the identifier of the first event but also the identifier of the second event (e.g., Figure 6A As shown in the example, the second event is the event other than the first event among the multiple triggered events. The identifier of the second event in the PUCCH can indicate that the second event has been triggered. The beam report of the second event does not need to be sent to the network device, i.e., it does not need to be reported. In this example, the beam report of the beam associated with the second event can be implicitly indicated by the field where the identifier of the second event is located. For example, the PUCCH includes field 1 and field 2, where the field value corresponding to field 1 is the identifier of the first event, and the field value corresponding to field 2 is the identifier of the second event. The beam report of the beam associated with the event indicated by the identifier carried on field 2 does not need to be reported.

[0112] Based on this, the terminal device not only reports the first event requiring the transmission of a relevant beam report to the network device, but also reports the second event requiring no beam report transmission, enabling the network device to know all events actually triggered by the terminal device. Consequently, the network device can not only schedule PUSCH resources for the terminal device solely for transmitting beam reports based on the first event, but also perform accurate processing operations based on all events triggered by the terminal device. For example, the network device can further determine whether to trigger the terminal device to transmit a beam report for the second event.

[0113] Understandably, the network device will execute different handlers (i.e., processing operations) for different events. Therefore, the terminal device reports all triggered events to the network device, allowing the network device to determine how (or whether to trigger) the handlers for each event based on its needs. However, if only the filtered first event is reported to the network device, the network device might infer a second event based on the first event reported by the terminal device. Based on the first event and the inferred second event, the network device can then execute relevant processing operations. If the second event is inferred incorrectly, the network device might erroneously execute processing operations, such as mistakenly triggering the terminal device to send unnecessary beam reports.

[0114] In another example, similar to the previous one, such as Figure 6B As shown, a PUCCH can include an event identifier and its corresponding identifier. The event identifier in the PUCCH includes the identifier of a first event and the identifier of a second event. Similarly, the event identifier can include a first identifier and a second identifier. The first identifier corresponds to the identifier of the first event. The second identifier corresponds to the identifier of the second event, and the second identifier indicates that it is not necessary to send a beam report of the second event corresponding to that second identifier to the network device; that is, the second identifier indicates that a beam report of the second event's beam is not reported. In other words, the PUCCH includes not only the identifier of the first event and its corresponding identifier, but also the identifier of the second event and its corresponding identifier.

[0115] It is understandable that the identifier corresponding to the event identifier in PUCCH can be located after the event identifier and adjacent to the event identifier (see above). Figure 5B , Figure 6B Of course, the identifier corresponding to the event identifier can also be located before the event identifier, and this application does not restrict this. Optionally, the value of the identifier corresponding to the event identifier (i.e., the first identifier and the second identifier mentioned above) can be set as needed, and correspondingly, the number of bits occupied by the event identifier can also be set as needed. For example, if the first identifier is 0, the second identifier is 1, and the event identifier occupies 1 bit.

[0116] S203. In response to PUCCH, the network device schedules PUSCH transmission resources for the terminal device based on the first event.

[0117] S204. The terminal device sends a beam report of the beam related to the first event to the network device based on the transmission resources of PUSCH.

[0118] In this application, the network device sends scheduling information to the terminal device based on the PUCCH. Correspondingly, the terminal device receives the scheduling information. The scheduling information is used to schedule transmission resources for the PUSCH for the terminal device. The scheduling information can be carried in the Physical Downlink Control Channel. Subsequently, the terminal device sends the PUSCH to the network device based on the PUSCH transmission resources; wherein the PUSCH carries a beam report of the beam related to the first event, so that after the network device receives the PUSCH, it can obtain the beam report of the beam related to the first event from the PUSCH.

[0119] The first event mentioned above may include an event determined by the terminal device from multiple events based on the event's beam information, that is, an event selected from multiple events.

[0120] In one implementation, the aforementioned first event may include an event determined by the terminal device from events with the same beam information among multiple events (i.e., the filtered event). Specifically, the terminal device may filter out second events that do not meet the reporting requirements from events with the same beam information among multiple events, and take all events other than the second event as the first event. In other words, the first event includes not only events whose beam information is different from the beam information of other events among multiple events, but also events retained after filtering events with the same beam information, excluding the second event.

[0121] The phrase "same beam information" indicates that the identifier of the current beam and / or the identifier of the new beam are the same. Events with the same beam information indicate events where related beams have the same beam identifier. For example, event a1 is related to only the new beam, event a2 is related to both the current beam and the new beam, event a3 is related to only the current beam, and event a4 is related to both the current beam and the new beam.

[0122] When the new beam identifiers for events a1 and a2 are the same, it indicates that the beam identifiers for events a1 and a2 are identical, meaning that the beam information for events a1 and a2 is the same. Otherwise, when the new beam identifiers for events a1 and a2 are different, it indicates that the beam identifiers for events a1 and a2 are different.

[0123] When event a3 has the same current beam identifier as event a2, it indicates that events a2 and a3 have the same beam identifier. Furthermore, since event a1 is also a beam identifier-related event to event a2, events a1, a2, and a3 are events with the same beam identifier.

[0124] When event a4 has the same current beam identifier as event a2, and event a4 also has the same new beam identifier as event a2, it indicates that event a4 and event a2 have the same beam identifier. Additionally, events a1, a2, a3, and a4 have the same beam identifier. Otherwise, when event a4 has a different current beam identifier than event a2, or when event a4 has a different new beam identifier than event a2, it indicates that event a4 and event a2 have different beam identifiers.

[0125] Optionally, identical beam identifiers indicate that the beams associated with the event with fewer related beams are a subset of the beams associated with the event with more related beams. In other words, for two events, the identifier of any beam associated with the event with fewer related beams belongs to the identifier of the beam associated with the event with more related beams. Taking events a1 and a2 as an example, if the number of new beams in event a1 is greater than the number of new beams in event a2, then when the identifier of any new beam in event a2 belongs to the identifier of a new beam in event a1, it indicates that the new beam identifiers of events a1 and a2 are the same.

[0126] Taking events a2 and a4 as examples again, the number of new beams in event a2 is greater than the number of new beams in event a4, and the number of current beams in event a2 is greater than the number of current beams in event a4. Therefore, if the identifier of any new beam in event a4 is the same as the identifier of a new beam in event a2, it indicates that the identifiers of the new beams in events a2 and a4 are the same. Otherwise, the identifiers of the new beams in events a2 and a4 are different.

[0127] If the identifier of any current beam in event a4 is the same as the identifier of the current beam in event a2, it indicates that the identifiers of the current beams in event a2 and event a4 are the same. Otherwise, the identifiers of the current beams in event a2 and event a4 are different.

[0128] It is understandable that when the number of beams associated with two events is the same, the identifier of the beam associated with either event belongs to the identifier of the beam associated with the other event. This is similar to the situation where the beams associated with an event with fewer associated beams are a subset of the beams associated with an event with more associated beams, except that it is not necessary to determine the number of beams associated with an event.

[0129] In this application, when two events have the same beam identifier, the beam information of these two events is the same. Events with the same beam information have a high degree of functional overlap. Therefore, the terminal device can filter events from those with the same beam information, avoiding duplicate reporting of beam information and ensuring the accuracy of event filtering.

[0130] For example, the multiple events triggered by the terminal device include event 1, event 2, event 3, event 4, and event 8. Event 1 and event 2 have the same beam information, and event 3 and event 8 have the same beam information, but event 3 has different beam information from event 2. Therefore, the first event includes the event determined from event 1 and event 2, the event determined from event 3 and event 8, and event 4.

[0131] For example, a terminal device can determine an event set from multiple events based on the beam information of each event in the event set, where the events in the event set have the same beam information, and the events in different event sets have different beam information. Then, for each event set, the terminal device can determine event A from that event set, and event A can be used as the first event; that is, the first event includes event A, thereby achieving event filtering.

[0132] Continuing with the examples above, events 1 and 2 can be considered as one event set, and events 3 and 8 can be considered as another event set. Therefore, the terminal device can determine event A from each event set.

[0133] Optionally, the first event includes events determined by the terminal device from events with the same beam information based on their priority, thereby achieving accurate event filtering based on event priority. For example, the terminal device can determine event A from the event set based on the priority of each event in the event set. In other words, the second event includes events filtered by the terminal device from events with the same beam information based on their priority. For example, the terminal device can filter out the second event from the event set based on the priority of each event in the event set, thus determining event A.

[0134] Specifically, when events with the same beam information have different priorities, the function of a higher-priority event may override the function of a lower-priority event. In other words, the beam information in the beam report of a lower-priority event may be a subset of the beam information in the beam report of a higher-priority event. Therefore, the first event includes the highest-priority event among those with the same beam information, without including lower-priority events, ensuring the accuracy of event filtering and avoiding duplicate reporting of beam information.

[0135] When events with the same beam information have the same priority, there may be no overlap in the functions of the events. Therefore, the first event includes all events with the same beam information to avoid missed beam messages.

[0136] Continuing with the example above, event 1 has a higher priority than event 2; therefore, event 1 can be considered the first event. Events 3 and 8 have the same priority; therefore, both events 3 and 8 can be considered the first event.

[0137] In this application, events are ranked by priority. By prioritizing events with the same beam information, the accuracy of event selection can be ensured.

[0138] In some embodiments, since certain events among all events (i.e., preset events) may not participate in event filtering, when a preset event is triggered, the terminal device directly reports it to the network device. In other words, a preset event represents an event in which a beam report of a relevant beam is sent to the network device; that is, a preset event represents a pre-configured event that requires the reporting of beam reports of a relevant beam. Therefore, the above filtering can be performed from events other than preset events (i.e., non-preset events) among the multiple events. When there are non-preset events other than preset events among the multiple events, the first event described above, which includes events determined from the multiple events based on the beam information of the events, can actually mean that the first event includes events determined from non-preset events based on the beam information of non-preset events among the events. Furthermore, the above first event can include not only events determined from non-preset events but also preset events among the multiple events.

[0139] Specifically, the description above regarding determining an event from multiple events can be replaced with a description of determining an event from non-preset events. In other words, the process of determining an event that can be the first event from non-preset events is similar to the process described above regarding determining an event that can be the first event from multiple events. That is to say, the description above regarding filtering events from multiple events can be replaced with a description of filtering events from non-preset events. The process of filtering events from non-preset events is similar to the process of filtering events from multiple events. The process of filtering non-preset events can refer to the process of filtering multiple events described above, and will not be repeated here.

[0140] Optionally, the preset events may include events 5, 6, 7a, 7b and event 9.

[0141] In this application, considering that there is no overlap in function between preset events or between preset events and non-preset events, when the triggered event includes a preset event, the terminal device can directly use the preset event in the triggered event as the first event without filtering from the preset events, thereby avoiding unnecessary event filtering and also avoiding mis-filtering of preset events.

[0142] Alternatively, since the preset events do not need to participate in the filtering, the first message can indicate the priority of all events other than the preset events. For example, if the preset events include events 5, 6, 7a, 7b and event 9, then the first message indicates the priority of all events from event 1 to event 9 except for events 5, 6, 7a, 7b and event 9.

[0143] In some embodiments, the priority of the aforementioned events can be configured by the network device. The terminal device can receive a first message sent by the network device, which indicates the priority of all events. For example, if all events include events 1-9, then the priority of all events can include the priority of each event among events 1-9. Of course, the event priority can also be configured by the terminal device. Correspondingly, the terminal device can also send relevant messages to the network device to indicate the priority of all events.

[0144] In some embodiments, the priority of events can be determined based on the inclusion relationship of events. In other words, the priority relationship of events is related to the inclusion relationship of events. In this application, the inclusion relationship of events can refer to: the condition corresponding to one event includes the condition corresponding to another event. Or it can be understood as the function of one event overlapping with the function of another event. Or it can be understood as the beam information in the beam report of the beam of one event includes the beam information in the beam report of the beam of another event, that is, a subset of the beam information in the beam report of the beam of one event is the beam information in the beam report of the beam of another event.

[0145] In some embodiments, the priority of the aforementioned events can be determined based on a threshold in the event (such as a third event). The third event includes / is associated with two thresholds, namely a first threshold and a second threshold. When the first threshold is greater than the second threshold, the priority of the event can be determined according to a first priority scheme (i.e., a first priority configuration rule). When the first threshold is less than or equal to the second threshold, the priority of the event can be determined according to a second priority scheme (i.e., a second priority configuration rule).

[0146] For example, the third event is event 4. The first threshold can be threshold 4 in event 4, and the second threshold can be threshold 5 in event 4. When threshold 4 is greater than threshold 5, the network device can use the first priority scheme to configure the event priority. When threshold 4 is less than or equal to threshold 5, the network device can use the second priority scheme to configure the event priority.

[0147] The first priority scheme can be shown in Table 1, and the second priority scheme can be shown in Table 2.

[0148] Table 1

[0149] event Priority Event 8 1 Event 2 2 Event 4 3 Event 1, Event 3 4

[0150] Table 2

[0151] event Priority Event 4, Event 8 1 Event 2 2 Event 1, Event 3 3

[0152] It is understandable that the smaller the priority number in Table 1 or Table 2 above, the higher the priority. For example, priority "1" in Table 1 or Table 2 above is the highest priority.

[0153] In some embodiments, as shown in Tables 1 and 2 above, the priority of all events (here or alternatively described as all events except the preset event) may be determined based on a threshold in the third event. Alternatively, the priority of some events may be determined based on a threshold in the third event, while the priority of others may not be determined based on a threshold. For example, as shown in Tables 1 and 2 above, regardless of whether the first threshold is greater than the second threshold or less than or equal to the second threshold, the priority of event 8 is always 1, and the priority of event 2 is always 2. Therefore, the priorities of events 8 and 2 may not be determined based on thresholds, but may be fixed. However, the priorities of events 4, 1, and 3 may be determined based on thresholds.

[0154] In some embodiments, the priority of the events described above can be represented based on the inclusion relationship between events. A higher priority event contains a lower priority event; that is, the functionality of a higher priority event includes the functionality of a lower priority event. In other words, the beam information in the beam report of a lower priority event is a subset of the beam information in the beam report of a higher priority event.

[0155] For example, event 8 may include event 2. When events 2 and 8 are triggered simultaneously, and both are triggered by the same current beam (i.e., their beam information is identical), the beam information included in the beam report of event 2 is a subset of the beam information in the beam report of event 8. In other words, both the current beam information and the new beam information of event 2 are included in the beam report of event 8. Therefore, event 8 has a higher priority than event 2. Accordingly, the terminal device can filter out event 2 and report event 8. Event 2 can be considered the second event, and event 8 can be considered the first event. Consequently, event 8 has a higher priority than event 2.

[0156] Similarly, if threshold 4 in event 4 is less than or equal to threshold 1 in event 1, then event 4 includes event 1. Accordingly, event 4 has a higher priority than event 1. Based on this, when event 4 and event 1 are triggered simultaneously and their beam information is the same, the terminal device can filter out event 1 and report event 8 instead, avoiding duplicate beam information reporting and unnecessary resource consumption.

[0157] If threshold 5 in event 4 is greater than or equal to threshold 3 in event 3, then event 4 includes event 3. Accordingly, event 4 has a higher priority than event 3. Based on this, when event 4 and event 3 are triggered simultaneously and their beam information is the same, the terminal device can filter out event 3 and report event 4, thus avoiding the reporting of duplicate beam information and avoiding unnecessary resource consumption.

[0158] Furthermore, if threshold 5 in event 4 is greater than or equal to threshold 4, then when event 4 is triggered, the quality of all beams will always be higher than the quality of the current beam. Thus, the triggering of event 2 and the beam information contained in the beam report of event 2 can be implicitly determined from the beam report of event 4. Therefore, when events 2 and 4 are triggered simultaneously and their beam information is the same, it indicates that events 2 and 4 are simultaneously triggered by the same current beam and new beam. To avoid wasting resources, the terminal device can filter out event 2 and report event 4 instead.

[0159] If threshold 4 for event 4 is greater than threshold 5, there is a possibility that the quality of the new beam triggered by event 4 may be lower than that of the current beam. Therefore, the triggering of event 2 and the beam information contained in the beam report of event 2 cannot be implicitly determined from event 4. However, the terminal device always wants to communicate with the network device using the beam with the best quality. If only event 4 is reported without reporting event 2, it may not be possible to find the best quality beam for the UE. Conversely, it can be assumed that only reporting event 2 can find the best quality beam for the terminal device.

[0160] In some embodiments, the quality of the beam can be measured by metrics such as reference signal receiving power (RSRP).

[0161] It should be noted that the PUCCH in this application is merely an example instruction. That is, the terminal device can send first information to the network device, which instructs the reporting of beam reports related to the first event. This first information can be carried in the PUCCH or other signaling messages. Similarly, PUSCH is also merely an example; that is, the network device can send beam reports related to the first event to the network device based on the uplink channel's transmission resources. The uplink channel can be carried in the PUCCH or other messages, without limitation.

[0162] S205. The network device receives a beam report of the beam associated with the first event.

[0163] In this embodiment of the application, after receiving the beam report of the first event, the network device can perform related operations based on the beam report, such as determining the optimal beam based on the beam information in the beam report.

[0164] In some embodiments, this application also provides a computer-readable storage medium including computer instructions that, when executed on an electronic device (or communication device, computer), cause the electronic device to perform the above-described communication method.

[0165] In some embodiments, this application also provides a computer program product, including a computer program that, when executed by a processor, implements the communication method described above.

[0166] In some embodiments, this application also provides a communication device, including: at least one processor and an interface circuit, wherein the interface circuit is used to receive signals from other communication devices outside the communication device and transmit them to the processor or to send signals from the processor to other communication devices outside the communication device, and the processor is used to implement the communication method as described above through logic circuits or execution code instructions.

[0167] In some embodiments, this application also provides a communication device including a module for performing the communication method as described above.

[0168] In some embodiments, this application also provides a communication system, which may include a network device and a terminal device. The network device or the terminal device can implement the communication method described above.

[0169] It is understood that any of the communication devices, terminal equipment, electronic equipment, network equipment, computer-readable storage media or computer program products provided above can be applied to the corresponding methods provided above. Therefore, the beneficial effects that can be achieved can be referred to the beneficial effects in the corresponding methods, and will not be repeated here.

[0170] These or other aspects of this application will become more readily apparent in the following description.

[0171] In addition, embodiments of this application also provide an apparatus, which may specifically be a chip, component, or module. The apparatus may include a connected processor and a memory; wherein the memory is used to store computer execution instructions, and when the apparatus is running, the processor may execute the computer execution instructions stored in the memory to cause the chip to execute the communication methods in the above-described method embodiments.

[0172] Through the above description of the embodiments, those skilled in the art will understand that, for the sake of convenience and brevity, only the division of the above functional modules is used as an example. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above.

[0173] In the several embodiments provided in this application, it should be understood that the disclosed apparatus and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of modules or units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another device, or some features may be ignored or not executed. Furthermore, the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between devices or units may be electrical, mechanical, or other forms.

[0174] The units described as separate components may or may not be physically separate. A component shown as a unit can be one or more physical units; that is, it can be located in one place or distributed in multiple different locations. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0175] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0176] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a readable storage medium. Based on this understanding, the technical solutions of the embodiments of this application, essentially or in other words, the parts that contribute to the prior art, or all or part of the technical solutions, can be embodied in the form of a software product. This software product is stored in a storage medium and includes several instructions to cause a device (which may be a microcontroller, chip, etc.) or processor to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0177] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A communication method, characterized in that, Applied to a terminal device, the method includes: In response to the triggering of multiple events, a Physical Uplink Control Channel (PUCCH) is sent to the network device; wherein the PUCCH is used to instruct the network device to schedule transmission resources of the Uplink Physical Shared Channel (PUSCH) according to a first event; each of the multiple events is used to trigger the terminal device to send a beam report; the first event includes at least one event determined from the events with the same beam information according to the priority of the events with the same beam information among the multiple events; Based on the transmission resources of the PUSCH, a beam report of the beam related to the first event is sent to the network device.

2. The method according to claim 1, characterized in that, The PUCCH includes the identifier of the first event.

3. The method according to claim 2, characterized in that, The PUCCH also includes a first identifier corresponding to the identifier of the first event, the first identifier being used to indicate the beam report of the beam related to the first event.

4. The method according to claim 2 or 3, characterized in that, The PUCCH also includes an identifier for a second event, which is an event other than the first event among the plurality of events. The second event indicates that the terminal device is triggered to not report a beam report of the relevant beam.

5. The method according to claim 4, characterized in that, The PUCCH also includes a second identifier corresponding to the identifier of the second event; the second identifier indicates that beam reports related to the second event should not be reported.

6. The method according to any one of claims 1 to 5, characterized in that, When events with the same beam information have different priorities, the first event includes the event with the highest priority among the events with the same beam information; When events with the same beam information have the same priority, the first event includes each of the events with the same beam information.

7. The method according to any one of claims 1 to 6, characterized in that, The priority of each of the multiple events is determined based on the inclusion relationship between the multiple events.

8. The method according to any one of claims 1 to 7, characterized in that, The method further includes: Receive a first message sent by the network device; wherein the first message is used to indicate the priority of an event among the plurality of events.

9. The method according to any one of claims 1 to 8, characterized in that, The priority of the event is determined based on a threshold value of the third event among the plurality of events.

10. The method according to any one of claims 1 to 9, characterized in that, If there are non-preset events other than preset events among the plurality of events, the first event includes an event determined from the non-preset events with the same beam information according to the priority of the non-preset events with the same beam information among the plurality of events; The preset event refers to the event in which a beam report of a relevant beam is sent to a network device.

11. The method according to any one of claims 1 to 10, characterized in that, The first event includes a preset event among the plurality of events.

12. A communication method, characterized in that, Applied to network devices, the method includes: Receive the Physical Uplink Control Channel (PUCCH) sent by the terminal device; In response to the PUCCH, transmission resources of the uplink physical shared channel (PUSCH) are scheduled for the terminal device according to a first event; the first event includes at least one event determined by the terminal device from the events with the same beam information according to the priority of the events with the same beam information among the triggered events, and each of the events is used to trigger the terminal device to send a beam report; Receive beam reports of the beams related to the first event sent by the terminal device based on the transmission resources of the PUSCH.

13. The method according to claim 12, characterized in that, The method further includes: Send a first message to the terminal device; wherein the first message indicates the priority of an event among the plurality of events.

14. The method according to claim 12 or 13, characterized in that, The priority of the event is determined based on a threshold value of the third event among the plurality of events.

15. A communication device, characterized in that, include: Module for performing the communication method as described in any one of claims 1-11; And / or, a module for performing the communication method as described in any one of claims 12-14.

16. A communication system, characterized in that, include: Terminal equipment and network equipment; In response to multiple events, the terminal device sends a Physical Uplink Control Channel (PUCCH) to the network device; wherein, the PUCCH is used to instruct the network device to schedule transmission resources of the Uplink Physical Shared Channel (PUSCH) according to a first event; each of the multiple events is used to trigger the terminal device to send a beam report; the first event includes at least one event determined from the events with the same beam information according to the priority of the events with the same beam information among the multiple events; The network device receives the PUCCH; In response to the PUCCH, the network device schedules uplink physical shared channel (PUSCH) transmission resources for the terminal device according to the first event; The terminal device sends a beam report of the beam related to the first event to the network device based on the transmission resources of the PUSCH. The network device receives a beam report of the beam associated with the first event.

17. A communication device, characterized in that, include: At least one processor and an interface circuit, the interface circuit being configured to receive signals from other communication devices besides the communication device and transmit them to the processor or to send signals from the processor to other communication devices besides the communication device, the processor being configured to implement the method as described in any one of claims 1-11 via logic circuits or executable code instructions; and / or, the processor being configured to implement the method as described in any one of claims 12-14 via logic circuits or executable code instructions.

18. A computer-readable storage medium, characterized in that, It includes a computer program or instructions that, when run on a computer, cause the computer to perform the method as described in any one of claims 1-11; and / or cause the computer to perform the method as described in any one of claims 12-14.

19. A chip, characterized in that, include: An interface circuit and a logic circuit, wherein the interface circuit is used to receive signals from other chips besides the chip and transmit them to the logic circuit, or to send signals from the logic circuit to other chips besides the chip, and the logic circuit is used to implement the method as described in any one of claims 1-11; and / or, the logic circuit is used to implement the method as described in any one of claims 12-14.

20. A computer program product, characterized in that, The computer program product includes: a computer program or instructions that, when executed on a computer, cause the computer to perform the method as described in any one of claims 1-11; and / or cause the computer to perform the method as described in any one of claims 12-14.

Images