Communication method, apparatus, system and computer readable storage medium

Abstract

The application provides a communication method, device, system and computer readable storage medium. The method can be applied to a communication scenario such as carrier aggregation. In the method, for a plurality of carriers configured by a network device for a terminal device, the terminal device can report a plurality of carrier triggering multiple events to the network device based on a first information. The plurality of carrier triggering event conditions indicated by the first information can include at least one of a triggering event, a carrier triggering the triggering event in the plurality of carriers, and a carrier not triggering the triggering event in the plurality of carriers. The triggering event refers to an event triggered in multiple events. The first information can be a multi-bit uplink control information based on a physical uplink control channel transmission. The method can enable the network device to timely obtain the beam quality of the plurality of carriers based on the first information, and timely adjust the carriers according to the plurality of carrier triggering multiple events, thereby improving the communication efficiency.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a communication method, apparatus, system and computer-readable storage medium. Background Technology

[0002] Carrier aggregation (CA) is a key technology in the field of communications. CA technology achieves higher data transmission rates and more flexible spectrum allocation by aggregating multiple component carriers (CCs).

[0003] In CA communication scenarios, network-side devices (or network equipment) need to know the communication status of multiple CCs in a timely manner so that the network side can quickly and accurately adjust the carrier based on the communication status of multiple CCs and improve communication efficiency. Summary of the Invention

[0004] This application provides a communication method, apparatus, system, and computer-readable storage medium. A terminal device can report a situation where multiple carriers trigger multiple events to a network device through a first piece of information. The events are related to beam quality. This allows the network device to obtain the beam quality of multiple carriers in a timely manner based on the first information and to adjust the carriers in a timely manner according to the situation where multiple carriers trigger multiple events, thereby improving communication efficiency.

[0005] Firstly, a communication method is provided. This method can be executed by a terminal device, or by a component (such as a circuit, chip, or chip system) configured in the terminal device, or by a logic module or software capable of implementing all or part of the functions of the terminal device. This application does not limit this approach. The following description uses a terminal device as an example.

[0006] Network devices configure multiple carriers for terminal devices, which can be used to carry data transmission between the terminal devices and network devices. The terminal devices can monitor these multiple carriers and report situations where multiple events are triggered by these carriers to the network devices, allowing the network devices to adjust the multiple carriers and ensure communication quality between the terminal devices and network devices. The communication method provided in this application mainly relates to an implementation scheme for the terminal devices to report situations where multiple events are triggered by multiple carriers to the network devices.

[0007] The method includes: a terminal device acquiring first information, the first information indicating a multi-carrier-triggered multi-event situation; and the terminal device sending the first information to a network device, so that the network device acquires the multi-carrier-triggered multi-event situation.

[0008] The scenario of multiple carrier-triggered events can include at least one of the following: a trigger event, a carrier that triggers a trigger event among multiple carriers, and a carrier that does not trigger a trigger event among multiple carriers. A trigger event refers to an event among multiple events that meets a preset triggering condition, or an event that is triggered among multiple events.

[0009] Network devices configure multiple events for terminal devices. These events can refer to multiple carrier-related events, such as events related to beam quality (the beam quality of the carrier, or the beam quality of the carrier's beam, etc.). Each event has a corresponding triggering condition, which is related to the carrier. When the carrier meets the triggering condition for the event, the event is triggered by that carrier, or in other words, the carrier triggers the event. Given the multiple carriers and events configured by the network device for the terminal device, each carrier may trigger one or more events, and the situation of multiple carriers triggering multiple events may differ at different times.

[0010] In this scheme, the terminal device uses a first piece of information to indicate the situation of multiple carriers triggering multiple events. There can be various situations of multiple carriers triggering multiple events, and the first piece of information indicates different situations of multiple carriers triggering multiple events.

[0011] In one example, the scenario of multiple carriers triggering multiple events includes a trigger event. For multiple events configured on the network device, the first information indicates the event among the multiple events that meets a preset triggering condition, or indicates the event that is triggered among the multiple events, i.e., the trigger event. In this way, the network device can obtain the current carrier status based on the trigger event and adjust the carrier accordingly.

[0012] Correspondingly, the first information indicates a situation where multiple carriers trigger multiple events, and may also include events that were not triggered or non-triggered events among the multiple events. In this way, the network device can also obtain the triggering events among the multiple events based on the non-triggered events, and then adjust the carrier accordingly.

[0013] In another example, the scenario of multiple carriers triggering multiple events involves carriers among multiple carriers that trigger the event. Among these multiple carriers, some carriers trigger the event, while others do not. The first information indicates the carriers among the multiple carriers that trigger the event, allowing the network device to make adjustments for these carriers.

[0014] In another example, the scenario of multiple carriers triggering multiple events includes carriers among multiple carriers that have not yet triggered a trigger event. In this way, the network device can also indirectly obtain the carriers that triggered the trigger event based on the first information and adjust these carriers accordingly.

[0015] The first information indicating a multi-carrier triggering multiple events scenario can include any one of the above examples or a combination of multiple examples. For example, the first information indicating a multi-carrier triggering multiple events scenario includes a triggering event and the carrier among the multiple carriers that triggers the triggering event.

[0016] The first information can be a 1-bit message or a multi-bit message. Alternatively, the electronic device may use different numbers of bits of the first information to report based on different scenarios where multiple events are triggered by multiple carrier waves.

[0017] In one possible implementation, the first information is carried in the uplink control information, which is carried in the physical uplink control channel of format 3.

[0018] Therefore, based on a first piece of information, the terminal device can indicate the situation of multiple carriers triggering multiple events to the network device, so that the network device can adjust multiple carriers in a timely manner according to the situation of multiple carriers triggering multiple events, thereby ensuring the communication quality of the terminal device.

[0019] One possible implementation provides a configuration scheme in which multiple carriers trigger multiple events.

[0020] Network devices send configuration information to terminal devices to configure triggering conditions for multiple events triggered by multiple carriers. These triggering conditions can include conditions for each of the multiple carriers to trigger each of the multiple events. The carrier-triggered event condition refers to the conditions that the carrier (e.g., beam quality) must meet to trigger the event. Beam quality is related to the carrier's signal quality or the carrier's beam quality. Examples of carrier-triggered event conditions include, for instance, the current beam quality being below a threshold, or the quality of a new beam on the current carrier being higher than the current beam by a certain threshold. Different events have different triggering conditions.

[0021] Based on the configuration information provided by the network equipment, the terminal device monitors the beam quality of each of multiple carriers to determine whether each carrier triggers one or more events. The terminal device can perform periodic monitoring, monitoring the beam quality of multiple carriers within a time window in each period, and determining the triggering of multiple events by multiple carriers in that period based on the beam quality.

[0022] For each carrier, the terminal device determines the triggering status of each carrier among multiple carriers based on the carrier's beam quality and triggering conditions. The triggering status includes at least one of the following: whether the carrier triggers an event, the corresponding triggered event, or the corresponding untriggered event. Whether the carrier triggers an event can refer to whether the carrier triggers at least one event among multiple events, some specific events among multiple events, or all events within the multiple events. The corresponding triggered event refers to the event triggered by the carrier among multiple events; this triggering event can be one or more events among the carriers, or it may be empty, meaning the carrier did not trigger any of the multiple events. The corresponding untriggered event can refer to the event not triggered by the carrier among multiple events; this untriggered event can be one or more events among the carriers, or it may be empty, meaning the carrier triggered all of the multiple events.

[0023] The terminal device generates and reports first information based on the triggering status of each carrier determined by monitoring. For example, the triggering status of each carrier includes the triggering event of that carrier, and the terminal device generates first information based on the triggering status of each of the multiple carriers.

[0024] Therefore, the network device sends configuration information to the terminal device to configure the reporting method for multiple carriers, multiple events, and multiple carriers triggering multiple events. This allows the terminal device to generate and report the first information based on the configuration information. In this way, the terminal device can synchronize the reporting scheme for multiple carriers triggering multiple events with the network device, enabling the terminal device to accurately and promptly report the monitored multiple carriers triggering multiple events. Furthermore, the network device can accurately parse the information about multiple carriers triggering multiple events, facilitating timely carrier adjustments and ensuring the stability of communication between the terminal device and the network device.

[0025] In one possible implementation, the first information is generated in a way that triggers events across carriers. Crossing carriers can refer to merging or spanning multiple carriers, and reporting each of the multiple events triggered by those multiple carriers separately.

[0026] Specifically, the first information includes at least one bit, which corresponds to at least one event among multiple events. One bit is used to indicate whether the event corresponding to that bit is triggered by a carrier among the multiple carriers. For example, if the multiple events include a first event and a second event, then the first information may include a first bit and a second bit, where the first bit corresponds to the first event and the second bit corresponds to the second event. The first bit is used to indicate whether the first event is triggered by a carrier among the multiple carriers, and the second bit is used to indicate whether the second event is triggered by a carrier among the multiple carriers.

[0027] Therefore, by generating first information through cross-carrier merging events, the terminal device can enable the network device to prioritize the triggering of each event and make timely carrier adjustments to ensure communication quality.

[0028] One possible implementation provides the possibility of multiple carriers and multiple events.

[0029] The multiple carriers include Class I carriers and Class II carriers, which refer to two types of carriers with completely different functions and priorities. Specifically, Class I carriers and Class II carriers can be carriers in different frequency bands. For example, Class I carriers can be the primary carriers, and Class II carriers can be secondary carriers. Class I and Class II carriers work together to carry out information transmission between terminal equipment and network equipment.

[0030] The multiple events include a first event and a second event, which can be different events related to the carrier. For example, the first event is event 2, and the second event is event 7 or event 1. Alternatively, the first event is event 7, and the second event is event 1, etc., without limitation. The multiple events may also include other events besides the first and second events.

[0031] The first information includes a first bit and a second bit, wherein the first bit is used to indicate whether a first event is triggered by a first type carrier and / or a second type carrier, and the second bit is used to indicate whether a second event is triggered by a first type carrier and / or a second type carrier.

[0032] The scenarios for whether the first event is triggered by a Type I carrier and / or a Type II carrier can include: the first event is triggered by a Type I carrier; the first event is triggered by a Type II carrier; the first event is triggered by both a Type I carrier and a Type II carrier; and the first event is neither triggered by a Type I carrier nor by a Type II carrier. Specifically, if the first event is triggered by either a Type I carrier or a Type II carrier, it can be considered that the first event is triggered by both a Type I carrier and / or a Type II carrier; conversely, if the first event is not triggered by either a Type I carrier or a Type II carrier, it can be considered that the first event is not triggered by either a Type I carrier or a Type II carrier.

[0033] Whether the second event is triggered by a Type I carrier and / or a Type II carrier can include: the second event is triggered by a Type I carrier; the second event is triggered by a Type II carrier; the second event is triggered by both a Type I carrier and a Type II carrier; and the second event is neither triggered by a Type I carrier nor by a Type II carrier. Specifically, if the second event is triggered by either a Type I carrier or a Type II carrier, it can be considered that the second event is triggered by both a Type I carrier and / or a Type II carrier; conversely, if the second event is not triggered by either a Type I carrier or a Type II carrier, it can be considered that the second event is not triggered by either a Type I carrier or a Type II carrier.

[0034] Therefore, by reporting the triggering status of each event among multiple events to the network device at the event granularity based on the first information, the terminal device can directly obtain the triggering status of each event by multiple carriers, which facilitates timely carrier adjustment based on the beam quality corresponding to the triggered event.

[0035] In other cases, reporting can also be done at the carrier level. For example, the first information includes a first bit and a second bit. The first bit indicates whether a first type of carrier has triggered an event, and the second bit indicates whether a second type of carrier has triggered an event. Whether the first type of carrier has triggered an event can refer to whether it has triggered any one of multiple events, or whether it has triggered all or some specific events among multiple events; it is not limited. The way the second bit indicates whether the second type of carrier has triggered an event is similar and will not be described in detail.

[0036] Therefore, by using the carrier as the granularity, the terminal device reports the trigger status of each of the multiple carriers to the network device based on the first information. This allows the network device to directly obtain the triggering event information of each carrier, facilitating timely carrier adjustment for each carrier.

[0037] In one possible implementation, in addition to the first and second events, a third event is included. These three events are all different events related to beam quality. The priority of the third event is lower than that of the first and second events.

[0038] Correspondingly, the first information includes not only the first and second bits, but also the third and fourth bits. Unlike the cross-carrier indication method using the first and second bits, the third and fourth bits are used to indicate the single-carrier, single-event situation. Specifically, the third bit indicates whether the first type of carrier triggers the third event, and the fourth bit indicates whether the second type of carrier triggers the third event.

[0039] Therefore, for the lower-priority third event, the first information uses two bits to indicate whether the third event was triggered by each of the two carriers. This allows network devices to directly obtain information about whether the third event was triggered by each carrier, facilitating their assessment of whether carrier adjustment is necessary based on the carrier-triggered third event status.

[0040] In one possible implementation, the distribution of bits in the first information is further restricted. After the first information is received by the network device, the lower bits are received and parsed first, while the higher bits are received later. That is, after receiving the first information, the network device will prioritize parsing the information indicated by the lower bits.

[0041] Based on this, the first and second bits are the low bits in the first information, used to indicate the triggering status of the first and second events with higher priority. The third and fourth bits are the high bits in the first information, used to indicate the triggering status of the first and second events with lower priority.

[0042] Specifically, the first bit can be the lowest priority bit, indicating the triggering of the highest priority first event; the third and fourth bits can be the high priority bits in the first information, indicating the triggering of the lowest priority first event. When the first type of carrier has a higher priority than the second type of carrier, the fourth bit can be the highest priority bit, indicating that the lower priority second type of carrier triggers the lowest priority first event. The third bit can be the second highest priority bit, indicating that the higher priority first type of carrier triggers the lowest priority first event.

[0043] The second bit can be the second lowest bit, indicating the triggering status of the second highest priority second event.

[0044] Therefore, the first information indicates the triggering status of the first and second events with higher priority through the low bits. The network device can prioritize the parsing of the triggering status of the first and second events and make timely carrier adjustments based on the triggering status of the first and second events.

[0045] In one possible implementation, after the terminal device sends the first information to the network device, it can also receive information from the network device querying the carrier.

[0046] Specifically, the terminal device sends a first message to the network device, indicating the situation where multiple carriers trigger multiple events. Correspondingly, based on the cross-carrier triggering events reported in the first message, the network device sends a second message to the terminal device to query the carrier corresponding to the triggering event.

[0047] Based on the trigger event queried by the second information, the terminal device provides the carrier corresponding to the trigger event to the network device through the third information, which is used to indicate the carrier corresponding to the trigger event.

[0048] It should be noted that the first and second bits of the first information indicate the scenarios where the first and second events are triggered across carriers, including both cases where the first and / or second events are triggered across carriers and cases where they are not triggered across carriers. When the first information indicates the presence of a cross-carrier triggering event, the network device can query the carrier corresponding to the triggering event using the second information. When the first information indicates the absence of a cross-carrier triggering event, the network device can choose not to query the carrier corresponding to the triggering event using the second information, thus saving signaling overhead.

[0049] Therefore, when the first information indicates that a cross-carrier triggering first event and / or second event exists, the network device can query the carrier corresponding to the triggering event through the second information. This can improve the accuracy of multiple carriers triggering multiple events, thereby improving the accuracy of carrier adjustment by the network device and ensuring communication quality.

[0050] In one possible implementation, the first information indicates the case of multiple carriers triggering multiple events.

[0051] The first information includes multiple bits, each corresponding to a different carrier trigger event. These carrier trigger events are determined based on the carrier types of multiple carriers and the event types of multiple events. Specifically, one bit indicates whether the carrier trigger event corresponding to that bit has been triggered. A carrier trigger event is determined based on a carrier type and an event type.

[0052] In this method, the information indicated by each bit in the first information is further refined, with one bit used to indicate the situation where a certain type of carrier triggers a certain type of event. For example, one bit is used to indicate the situation where a first type of carrier triggers a first event, and another bit is used to indicate the situation where a second type of carrier triggers a second event. In this way, the situation where multiple carriers trigger multiple events indicated by the first information can be more accurate and comprehensive.

[0053] In one possible implementation, the first information indicating the case of multiple carriers triggering multiple events is refined. Here, the multiple carriers include first-type carriers and second-type carriers, and the multiple events include a first event, a second event, and a third event. Correspondingly, the first information includes a first bit, a second bit, a third bit, a fourth bit, a fifth bit, and a sixth bit.

[0054] For the first event, the first bit indicates whether the first type of carrier triggered the first event, and the second bit indicates whether the second type of carrier triggered the first event. For the second event, the third bit indicates whether the first type of carrier triggered the second event, and the fourth bit indicates whether the second type of carrier triggered the second event. For the third event, the fifth bit indicates whether the first type of carrier triggered the third event, and the sixth bit indicates whether the second type of carrier triggered the third event.

[0055] Therefore, the first information can distinguish between carrier type and event type reporting of multiple carriers triggering multiple events, so that network devices can simultaneously, accurately and comprehensively obtain information on multiple carriers triggering multiple events based on this first information, thereby improving the timeliness of information acquisition and the accuracy of carrier adjustment.

[0056] In one possible implementation, the first information indicates the case of multiple carriers triggering multiple events.

[0057] In the case of multiple triggering events, the terminal device uses one bit of the first information to indicate, that is, the one bit is used to indicate all or part of the multiple triggering events.

[0058] For example, in the case of multiple triggering events including a first event and a third event, the terminal device can indicate to the network device, through a 1-bit first information, that the multiple triggering events include a first event and a third event, or that both the first event and the third event have been triggered.

[0059] For example, in the case of multiple triggering events including a first event, a second event, and a third event, the terminal device can also indicate to the network device, through a 1-bit first information, that multiple triggering events include a first event, a second event, and a third event, or that the first event, the second event, and the third event have all been triggered.

[0060] When monitoring multiple events triggered by multiple carriers, the terminal device can select different reporting methods depending on the situation. For example, if multiple triggering events exist, the terminal device can report the situation using a 1-bit reporting method, based on 1 bit of initial information. If there are no multiple triggering events, or if there are no multiple triggering events of a specified type, the terminal device can report the situation using the aforementioned 4-bit, 6-bit, or other multi-bit reporting methods, based on multiple bits of initial information.

[0061] Therefore, when multiple events of different priorities are triggered simultaneously, the terminal device can quickly report the situation using a single 1-bit first information, facilitating timely reporting of the multiple events to the network device. Furthermore, reporting multiple events triggered by multiple carriers using a single 1-bit first information also saves bit capacity.

[0062] In one possible implementation, the configuration information was further expanded.

[0063] The configuration information sent by the network device to the terminal device can also be used to configure at least one of the following: the reporting method for multiple events triggered by multiple carriers, the mapping relationship between events and bits, the event type, the carrier range bound to the event, the allocated bits, or the event priority.

[0064] The reporting methods for multiple carriers triggering multiple events can include the aforementioned 4-bit reporting method, 6-bit reporting method, 1-bit reporting method, etc. The mapping relationship between events and bits can include the type of triggering event indicated by each bit in the first information; for example, the first bit indicates the triggering status of the first event, the second bit indicates the triggering status of the second event, etc. Event types can include first event, second event, and third event, or event types can include event 2, event 7, and event 1. The carrier range bound to the event can refer to which carriers are monitored for which event triggering status; for example, monitoring the first type of carrier and / or the second type of carrier triggering the first event, monitoring the first type of carrier and / or the second type of carrier triggering the second event, monitoring the first type of carrier triggering the third event, monitoring the second type of carrier triggering the fourth carrier, etc., without limitation. The allocated bits refer to the bits allocated for each event triggering status; for example, allocating the first bit for the triggering status of the first event, the first bit indicating the triggering status of the first event, and allocating the second bit for the triggering status of the second event, etc. Event priority refers to the priority of each event among multiple events. For example, the first event has the highest priority, the second event has the second highest priority, and the third event has the second lowest priority. Among them, the highest priority indicates the more important event or the event that needs to be known by network devices first, the second highest priority indicates the event with relatively lower importance, and the lowest priority indicates the event with the least importance.

[0065] The configuration information sent by the network device to the terminal device may include one or more of the above-mentioned information. For example, the configuration information may include multiple carriers, multiple events, the mapping relationship between events and bits, the carrier range bound to the event, the event priority, etc.

[0066] Therefore, based on the mapping relationship between events and bits and the event type configured in the configuration information, the terminal device generates the first information in a comprehensive manner, which facilitates the generation of more accurate first information in a reporting method synchronized with the network device, and reports the situation of multiple carriers triggering multiple events to the network device more accurately.

[0067] In one possible implementation, corresponding reporting methods are provided for different situations. Continuing with the example of multiple carriers, including both Type I and Type II carriers, the number of Type I carriers can be one, and the number of Type II carriers can be one or more, with Type I carriers having higher priority than Type II carriers.

[0068] Therefore, when there is only one Type II carrier, the bit reporting method is 4-bit reporting. When there are multiple Type II carriers, the bit reporting method is 6-bit reporting.

[0069] Therefore, for the case where there is only one Type II carrier, a 4-bit reporting method is adopted to reduce bit overhead while accurately reporting multiple events triggered by multiple carriers. For the case where there are multiple Type II carriers, a 6-bit reporting method can distinguish between reporting multiple events triggered by Type I carriers and multiple events triggered by Type II carriers, further improving the accuracy and comprehensiveness of the first information reporting.

[0070] In one possible implementation, the communication scenario of triggering multiple events based on reporting multiple carriers using the first piece of information is extended. Specifically, this includes the following situations:

[0071] In carrier aggregation scenarios, multiple carriers include one primary carrier and at least one secondary carrier;

[0072] In a sensory communication scenario, multiple carriers include communication carriers and sensing carriers;

[0073] In satellite-terrestrial converged communication scenarios, multiple carriers include terrestrial carriers and satellite carriers;

[0074] In millimeter-wave massive MIMO communication scenarios, multiple carriers include multiple millimeter carriers of different frequency bands.

[0075] In different communication scenarios, when there are multiple carriers, terminal devices can simultaneously report different information of multiple carriers through a single first message, thereby improving the synchronization and timeliness of the transmission of different information of multiple carriers and reducing signaling overhead.

[0076] Secondly, a communication method is provided, which can be executed by a network device, or by a component (such as a circuit, chip, or chip system) configured in the network device, or by a logic module or software capable of implementing all or part of the functions of the network device. This application does not limit this. The following description uses a network device as an example.

[0077] The network device obtains first information sent by the terminal device; the first information is used to indicate the situation of multiple carriers triggering multiple events, and the situation of multiple carriers triggering events includes at least one of the following: a triggering event, a carrier that triggers the triggering event among multiple carriers, and a carrier that does not trigger the triggering event among multiple carriers; the triggering event refers to an event among multiple events that meets a preset triggering condition, or refers to an event that is triggered among multiple events;

[0078] Based on the first information, the network device adjusts the carriers of multiple carriers.

[0079] The second aspect is the implementation on the network device side, which corresponds to the first aspect. The explanations, supplements, and descriptions of the beneficial effects of the first aspect also apply to the second aspect, and will not be repeated here.

[0080] Thirdly, a communication device is provided, which includes a processing module and a transceiver module.

[0081] The processing module is used to obtain first information; the first information is used to indicate the situation of multiple carriers triggering multiple events, the situation of multiple carriers triggering events includes at least one of the following: triggering event, carriers among the multiple carriers that trigger the triggering event, and carriers among the multiple carriers that do not trigger the triggering event; the triggering event refers to an event among the multiple events that meets a preset triggering condition, or refers to an event among the multiple events that is triggered.

[0082] This transceiver module is used to send the first information to the network device.

[0083] Fourthly, a communication device is provided, comprising a processing module and a transceiver module. The transceiver module is used to acquire first information sent by a terminal device; the first information indicates a situation where multiple carriers trigger multiple events, including at least one of the following: a trigger event, a carrier among the multiple carriers that triggers the trigger event, and a carrier among the multiple carriers that does not trigger the trigger event; the trigger event refers to an event among the multiple events that meets a preset triggering condition, or, an event among the multiple events that is triggered. The processing module is used to perform carrier adjustment on the multiple carriers according to the first information.

[0084] The third and fourth aspects are the implementation on the device side, which correspond to the first and second aspects. The explanations, supplements, and descriptions of the beneficial effects of the first and second aspects also apply to the third and fourth aspects, and will not be repeated here.

[0085] Fifthly, a communication device is provided, including a processor. The processor is coupled to a memory and can be used to execute instructions or data in the memory to implement the methods in any possible implementation of the first or second aspect described above.

[0086] Optionally, the communication device also includes a memory.

[0087] Optionally, the communication device also includes a communication interface, to which the processor is coupled.

[0088] In one implementation, the communication interface may be a transceiver, or an input / output interface.

[0089] In another implementation, the communication device is a chip configured in a terminal device. When the communication device is a chip configured in a terminal device, the communication interface can be an input / output interface.

[0090] In a sixth aspect, a communication device is provided, including a processor. The processor is coupled to a memory and can be used to execute instructions or data in the memory to implement the method in any possible implementation of the second aspect described above. Optionally, the communication device further includes a memory. Optionally, the communication device further includes a communication interface, and the processor is coupled to the communication interface.

[0091] In one implementation, the communication interface may be a transceiver, or an input / output interface.

[0092] In another implementation, the communication device is a chip configured in a satellite. When the communication device is a chip configured in a satellite, the communication interface can be an input / output interface.

[0093] In a seventh aspect, a processor is provided, comprising: an input circuit, an output circuit, and a processing circuit. The processing circuit is configured to receive signals through the input circuit and transmit signals through the output circuit, causing the processor to execute a method in any possible implementation of any aspect.

[0094] In specific implementation, the processor can be one or more chips, the input circuit can be input pins, the output circuit can be output pins, and the processing circuit can be transistors, gate circuits, flip-flops, and various logic circuits. The input signal received by the input circuit can be received and input by, for example, but not limited to, a receiver, and the signal output by the output circuit can be, for example, but not limited to, output to and transmitted by a transmitter. Furthermore, the input circuit and the output circuit can be the same circuit, which is used as both the input circuit and the output circuit at different times. This application does not limit the specific implementation of the processor and various circuits.

[0095] Eighthly, a communication device is provided, including a processor and a memory. The processor is used to read instructions stored in the memory, receive signals via a receiver, and transmit signals via a transmitter to execute the method in any possible implementation of any of the preceding aspects.

[0096] Optionally, the processor may be one or more, and the memory may be one or more.

[0097] Ninthly, a computer program product is provided, the computer program product comprising: a computer program (also referred to as code or instructions) that, when the computer program is run, causes a computer to perform a method in any possible implementation of any of the above aspects.

[0098] In a tenth aspect, a computer-readable storage medium is provided that stores a computer program (also referred to as code or instructions) that, when run on a computer, causes the computer to perform the methods in any possible implementation of any of the preceding aspects.

[0099] Eleventhly, embodiments of this application provide a chip system including one or more processors for calling and executing instructions stored in memory, causing the methods in any of the above aspects or possible implementations to be executed. The chip system may be composed of chips or may include chips and other discrete devices.

[0100] The chip system may include input circuits or interfaces for transmitting information or data, and output circuits or interfaces for receiving information or data.

[0101] In a twelfth aspect, a communication system is provided, including the aforementioned terminal device and network device. Optionally, the communication system may further include other devices that communicate with the terminal device and / or network device. Attached Figure Description

[0102] Figure 1 This application provides a schematic diagram of the architecture of a communication system.

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

[0104] Figure 3 A flowchart illustrating another communication method provided in an embodiment of this application;

[0105] Figure 4 This application provides an example of an interactive schematic diagram of a communication system.

[0106] Figure 5 A flowchart illustrating yet another communication method provided in an embodiment of this application;

[0107] Figure 6 A schematic block diagram of a communication device provided in the embodiments of this application;

[0108] Figure 7 Another schematic block diagram of the communication device provided in the embodiments of this application. Detailed Implementation

[0109] The technical solutions in the embodiments of this application will now be described with reference to the accompanying drawings.

[0110] The technical solutions provided in this application can be applied to various communication systems, such as: Global System for Mobile Communications (GSM) systems, General Packet Radio Service (GPRS), Wireless Local Area Network (WLAN), Long Term Evolution (LTE) systems, LTE Frequency Division Duplex (FDD) systems, LTE Time Division Duplex (TDD) systems, sidelink communication systems, Universal Mobile Telecommunication System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX) communication systems, non-terrestrial network (NTN) communication systems, 5th generation (5G) mobile communication systems, or new radio access technology (NR). Among these, 5G mobile communication systems can include non-standalone (NSA) and / or standalone (SA) networking. The technical solutions provided in this application can also be applied to future communication systems. This application does not limit the scope of these applications.

[0111] Figure 1 This is a schematic diagram of the architecture of a communication system used in an embodiment of this application. The communication system may include network devices, such as... Figure 1 The network device 110 is shown. The communication system may also include terminal devices, such as... Figure 1The terminal device 120 shown. The network device 110 and the terminal device 120 can communicate via a wireless link.

[0112] Figure 1 An exemplary network device 110 and a terminal device 120 are shown. Optionally, the communication system may also include multiple network devices and / or multiple terminal devices.

[0113] Figure 1 In this application, the network device 110 may include network-side devices such as access network devices and core network devices. The access network device has wireless transceiver capabilities and is used to communicate with both the terminal device and the core network device to realize data transmission between the terminal device and the core network device. The access network device can configure multiple component carriers (CCs) for the terminal device 120, which are used to realize data transmission between the terminal device and the core network device.

[0114] Access network equipment, also known as access nodes, includes, but is not limited to, base stations, evolved NodeBs (eNodeBs), transmission reception points (TRPs), next-generation NodeBs (gNBs) in 5G mobile communication systems, access network equipment or modules in open RAN (ORAN) systems, satellites in NTN communication systems, base stations in future mobile communication systems, or access nodes in WiFi systems. Access network equipment can also be modules or units capable of performing some of the functions of a base station. Access network equipment can be macro base stations, micro base stations, indoor stations, relay nodes, donor nodes, or radio controllers in cloud radio access networks (CRAN) scenarios. Optionally, access network equipment can also be servers, wearable devices, or vehicle-mounted equipment. For example, in vehicle-to-everything (V2X) technology, the access network equipment can be a roadside unit (RSU). Multiple access network devices in a communication system can be the same type of base station or different types of base stations. Base stations can communicate directly with terminal devices, or they can communicate with terminal devices through relay stations. Terminal devices can communicate with multiple base stations using different access technologies. The embodiments of this application do not limit the specific technologies or device forms used in the access network equipment.

[0115] In this application, the apparatus for implementing the functions of a network device can be the network device itself, or an apparatus capable of supporting the network device in implementing those functions, such as a processor, circuit, chip, or chip system. This apparatus can be installed in or connected to the network device. In the technical solution provided in this application, a base station is used as an example to describe the technical solution provided in this application.

[0116] The terminal device in this application can be a wireless terminal device capable of receiving network device scheduling and instruction information. The wireless terminal device can be a device providing voice and / or data connectivity to a user, a handheld device with wireless connectivity, or other processing devices connected to a wireless modem. For example, the terminal device can communicate with one or more core networks or the Internet via a radio access network (RAN). The terminal device can also be referred to as a terminal, user equipment (UE), mobile station, mobile terminal, etc. Terminal devices can be widely used in various scenarios, such as device-to-device (D2D), vehicle-to-everything (V2X) communication, machine-type communication (MTC), Internet of Things (IoT), ultra-reliable low-latency communication (URLLC), virtual reality, augmented reality, industrial control, autonomous driving, telemedicine, smart grids, smart furniture, smart offices, smart wearables, smart transportation, smart cities, or satellite communication, etc. The terminal device can be a mobile phone, tablet computer, computer with wireless transceiver capabilities, wearable device, vehicle, aircraft (such as drone, helicopter, airplane), hot air balloon, ship, robot, robotic arm, or smart home device, etc. The embodiments of this application do not limit the form of the terminal device.

[0117] In this application, the apparatus for implementing the functions of a terminal device can be the terminal device itself, or any apparatus capable of supporting the terminal device in implementing those functions, such as a processor, circuit, chip, or chip system. This apparatus can be installed in or connected to the terminal device. In the technical solution provided in this application, the UE (User Equipment) is used as an example to illustrate the technical solution provided in this application.

[0118] Access network equipment and / or terminal equipment can be fixed or mobile. They can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; on water; or in the air on aircraft, balloons, and satellites. This application does not limit the application scenarios of the access network equipment and terminal equipment. They can be deployed in the same or different scenarios; for example, both can be deployed on land simultaneously; or the access network equipment can be deployed on land while the terminal equipment is deployed on water, etc., and so on.

[0119] In practical applications, multiple network devices can collaborate to assist terminal devices in achieving wireless access, with different network devices each implementing a portion of the base station's functions. For example, network devices can be central units (CUs), distributed units (DUs), CU-control plane (CPs), CU-user plane (UPs), or radio units (RUs), etc. CUs and DUs can be set up separately or included in the same network element, such as a baseband unit (BBU). RUs can be included in radio frequency equipment or radio frequency units, such as remote radio units (RRUs), active antenna units (AAUs), or remote radio heads (RRHs).

[0120] In different systems, CU (or CU-CP and CU-UP), DU, or RU may have different names, but those skilled in the art will understand their meaning. For example, in an ORAN system, CU can also be called O-CU (Open CU), DU can also be called O-DU, CU-CP can also be called O-CU-CP, CU-UP can also be called O-CU-UP, and RU can also be called O-RU. Any of the units among CU (or CU-CP, CU-UP), DU, and RU in this application can be implemented through software modules, hardware modules, or a combination of software and hardware modules. CU (or CU-CP and CU-UP), DU, and RU can implement different protocol layer functions.

[0121] To facilitate understanding of the embodiments of this application, the terminology used in this application will be briefly explained first. Optionally, the explanation of some terms may also refer to the explanations in the 3rd Generation Partnership Project (3GPP) standard protocol.

[0122] 1. Carrier aggregation (CA)

[0123] Carrier aggregation is a communication technique that combines multiple carriers to achieve higher data transmission rates and more efficient frequency utilization. Each of the aggregated carriers corresponds to an independent frequency band or channel.

[0124] In carrier aggregation scenarios, two or more carriers can be aggregated together to cover one or more cells. Within a single cell, multiple carriers simultaneously provide network services. The carriers providing network services within a cell can be mainly divided into: primary component carrier (PCC) and secondary component carrier (SCC).

[0125] The primary carrier is the main communication channel of the cell, responsible for transmitting control information and providing basic data services. It establishes and maintains the connection between the UE and the base station, carrying the transmission of control information such as cell broadcast information, paging information, and random access responses. Secondary carriers are additional carriers used to increase data transmission rates, specifically for transmitting user data. They extend the cell's bandwidth to improve data transmission rates.

[0126] In carrier aggregation scenarios, the carriers connected to a UE include a primary carrier and one or more secondary carriers. The primary carrier is the main carrier of the cell, and the UE needs to connect to the primary carrier before it can communicate with the base station. The base station can allocate one or more secondary carriers to the UE, and these secondary carriers rely on the primary carrier for data transmission. The number of secondary carriers allocated by the base station to the UE depends on factors such as data transmission requirements, the UE's capabilities, network configuration, and application scenarios.

[0127] 2. Carrier-triggered event

[0128] Carrier-triggered events refer to events in a wireless communication system that trigger a series of operations when a carrier or its beam meets certain specific conditions. These events are typically used for wireless link management, handover, and measurement report reporting. Events used for wireless link management are called wireless link management events, events used for handover are called handover events, and events used for measurement report reporting are called measurement report reporting events.

[0129] In this context, the carrier wave is the information carrier and is a type of electromagnetic wave. Beam quality refers to the frequency resource attributes of the carrier itself (such as the overall interference level, bandwidth stability, frequency offset, etc.), which are inherent or overall characteristics of the carrier as a frequency carrier. A beam is an electromagnetic beam that propagates along a specific direction, used to describe the direction and range of electromagnetic wave propagation within a space. The carrier propagates in space in the form of a beam, i.e., the carrier beam. Beam quality refers to the signal attributes of the specific transmitted beam on the carrier, which is the dynamic quality of the beam carried by the carrier in actual transmission, directly determining the logic of beam switching and event triggering. Based on this, the carrier triggering event involved in the embodiments of this application refers to the event triggered when the carrier beam quality meets the triggering conditions of the corresponding event.

[0130] In carrier aggregation scenarios, carrier-triggered events can be categorized into three types based on their event type: Event 1 (Event-1), Event 2 (Event-2), and Event 7 (Event-7). Any carrier can trigger one of these three types of events. The following explanation of the event types will use any carrier as the current carrier.

[0131] Event 1 is an event related to the current carrier's beam. Specifically, Event 1 is triggered when the current beam quality is poor, such as a measurement report reporting event. Optionally, a threshold can be set; when the current beam quality falls below this threshold, it indicates that the current beam quality has deteriorated or worsened, Event 1 is triggered, the UE reports a measurement report to the base station, and the base station adjusts or optimizes the beam quality in a timely manner based on the reported measurement report. However, since the current beam can still be used in the short term, the urgency of Event 1 is relatively low.

[0132] Event 2 is an event related to the beam of the current carrier. Specifically, Event 2 is triggered when the beam quality of the new beam on the current carrier is good, such as a handover event. Optionally, a threshold can be set. Event 2 is triggered when the beam quality of the new beam is higher than the beam quality of the current beam, indicating that the beam quality of the new beam is superior to that of the current beam. When Event 2 is triggered, the UE reports a measurement report to the base station, and the base station performs carrier adjustment (or beam adjustment) in a timely manner based on the reported measurement report. For example, if the base station can quickly switch from the current beam to the new beam, the urgency of Event 2 is relatively high.

[0133] Event 7 is a beam-related event of the current carrier. Specifically, Event 7 refers to an event triggered when the new beam is better than the Q-good threshold of the transmission configuration indication (TCI), such as a handover event. The Q-good threshold of the transmission configuration indication (TCI) means that the beam quality of the new beam exceeds the beam quality of the Q-good reference signal (RS) in the active TCI state. When Event 7 is triggered, the UE reports a measurement report to the base station, and the base station determines whether to switch from the current beam to the new beam based on the reported measurement report.

[0134] In this application, the beam quality of the new beam of the carrier can also refer to the new beam quality, the beam quality of the new carrier, or the beam quality itself. Similarly, the beam quality of the current beam of the carrier can refer to the beam quality of the current carrier or the beam quality of the current carrier. Furthermore, the signal quality of the Qth best reference signal in the TCI state can refer to the signal quality of the Qth reference signal in the activated TCI state, where the Qth reference signal is the signal quality of the Qth reference signal ranked from highest to lowest.

[0135] Regarding urgency, among events 1, 2, and 7, event 7 has a lower urgency than event 2, but a higher urgency than event 1. Regarding priority, event 2 has a higher priority than event 7, and event 7 has a higher priority than event 1.

[0136] It should be understood that carrier-triggered events may also include other event types besides events 1, 2, and 7, and this application embodiment does not limit this. Furthermore, in this application, the current beam may refer to the beam currently providing network services, and the new beam may refer to a candidate beam capable of replacing the current beam in providing network services.

[0137] In carrier aggregation scenarios, the carrier that triggers the above-mentioned event could be the primary carrier or any secondary carrier. When the UE detects that the primary carrier or a secondary carrier has triggered the above-mentioned event, it can report the event type of the triggered event and / or the identification information of the carrier that triggered the event to the base station. The base station responds to the carrier-triggered event, and the response measures differ for different events.

[0138] For example, if the UE detects primary carrier trigger event 2, the corresponding response could be for the base station to switch the primary carrier from the current beam to a new beam. As another example, if the UE detects secondary carrier 1 trigger event 2, the corresponding response could be for the base station to switch secondary carrier 1 from the current beam to the secondary carrier. And as yet another example, if the UE detects primary carrier trigger event 1, the corresponding response could be for the base station to optimize the current beam of the primary carrier.

[0139] 3. Physical uplink control channel (PUCCH)

[0140] PUCCH is a channel used to transmit uplink control information (UCI), primarily responsible for transmitting control information from the UE to the base station. UCI includes scheduling request (SR), hybrid automatic repeat request (HARQ) feedback, and channel state information (CSI). HARQ feedback includes acknowledgment (ACK) or negative acknowledgment (NACK).

[0141] PUCCH is the transmission channel for UCI (User-Defined Communication Interface). UCI is transmitted from the UE to the base station via PUCCH. PUCCH has various formats, each suitable for different UCI types and transmission requirements.

[0142] For example, PUCCH Format 1 is used to transmit SR, PUCCH Format 2 is used to transmit CSI, and PUCCH Format 3 is used to transmit HARQ feedback. PUCCH Format 4 is used to transmit short UCIs, which may include short ACKs, short NACKs, or short CSIs. PUCCH Format 5 is used to transmit long UCIs, which may include long CSIs.

[0143] 4. Cases of UE reporting carrier trigger events

[0144] The UE reports carrier-triggered events via UCI transmitted through PUCCH.

[0145] In single-carrier scenarios, such as those involving only the primary carrier, the UE reports single-carrier trigger events via a 1-bit message carried in the PUCCH. For example, if the UE detects carrier trigger event 1, it reports it with 1 bit of information. If the UE detects carrier trigger event 2, it reports it with 1 bit of information. If the UE detects carrier trigger event 7, it reports it with 1 bit of information. After reporting carrier trigger events with 1 bit of information, the UE can then report the event type of the carrier trigger event using other information.

[0146] As mentioned above, carrier aggregation scenarios include one primary carrier and at least one secondary carrier. Therefore, in carrier aggregation scenarios, carrier-triggered events, classified according to carrier type and event type, may include at least one of the following: primary carrier trigger event 1, primary carrier trigger event 2, primary carrier trigger event 7, secondary carrier trigger event 1, secondary carrier trigger event 2, and secondary carrier trigger event 7. Where there are at least two secondary carriers, each type of secondary carrier trigger event can be further divided into multiple secondary carrier trigger events corresponding to the number of secondary carriers. For example, if the secondary carriers include secondary carrier 1, secondary carrier 2, and secondary carrier 3, the secondary carrier trigger events may further include: secondary carrier 1 trigger event 1 / event 2 / event 7, secondary carrier 2 trigger event 1 / event 2 / event 7, secondary carrier 3 trigger event 1 / event 2 / event 7, etc., without limitation.

[0147] As can be seen from the above, in a carrier aggregation scenario, there may be multiple carrier triggering events. In this case, if the UE performs signal measurement on multiple carriers in the current serving cell within a time window, the triggered events detected within the time window may include one or more of the above multiple carrier triggering events. The UE needs to report one or more carrier triggering events triggered within the current time window to the base station.

[0148] In one example, the UE can refer to the carrier trigger event reporting mechanism in a single-carrier scenario, transmitting UCI multiple times via a 1-bit PUCCH, reporting one carrier trigger event at a time with 1 bit of information per PUCCH, until all carrier trigger events are reported to the base station. While this approach can report multiple carrier trigger events to the base station, the multiple reporting results in significant uplink resource consumption and increased signaling overhead. Furthermore, since each PUCCH transmission introduces a delay, sequentially transmitting multiple pieces of information via PUCCH leads to even greater accumulated delay, preventing the UE from quickly and accurately reporting the event type and corresponding carrier of the triggered event. This hinders the base station's ability to quickly and accurately adjust the carrier, impacting communication efficiency.

[0149] In another example, this application embodiment provides an efficient reporting scheme for multiple carriers and multiple events in a carrier aggregation scenario. This scheme includes: in a communication scenario where multiple carriers exist simultaneously, such as a carrier aggregation scenario, the UE can report the situation of multiple carriers triggering multiple events to the base station using a multi-bit first information. This allows the base station to promptly obtain the situation of multiple carriers triggering multiple events based on the first information and to adjust the carriers accordingly, thereby improving communication efficiency. Compared to the scheme where the UE needs to transmit single-bit information multiple times through the physical uplink control channel to report a single carrier triggering a single event, the multi-bit reporting scheme provided in this application embodiment can save signaling overhead, reduce transmission latency, and improve communication efficiency.

[0150] It should be understood that the technical terms used in this application are for illustrative purposes only and not as limiting. For example, as technology evolves, technical terms may also change, and other technical terms that have the same technical meaning should also apply to this application.

[0151] The solution provided in this application will be described in detail below with reference to the corresponding flowcharts. It is understood that the illustrative flowcharts provided in this application primarily use different devices (such as terminal devices and network devices) as examples to illustrate the method, but this application does not limit the execution subject of the interaction. For example, the device in the illustrative flowchart (e.g., terminal device, network device) can also be a chip, chip system, or processor that supports the implementation of the method on that device, or it can be a logic module or software that can implement all or part of the functions of that device.

[0152] As a general statement, the message or signaling interactions involved in the interaction process of this application embodiment can be standard messages or signaling or newly introduced messages or signaling. This application embodiment does not make specific limitations on this.

[0153] Figure 2 This is a flowchart illustrating a communication method according to an embodiment of this application. It can be understood that... Figure 2 The UE in the middle can be Figure 1 The term "base station" can refer to any terminal device, or a component within that terminal device (such as a processor, chip, or chip system). Figure 1 Any network device, or a component within a network device (such as a processor, chip, or chip system). Figure 2 As shown, the main steps include the following:

[0154] S210, the UE obtains the situation of multiple carriers triggering multiple events.

[0155] Specifically, the UE can monitor the beam quality of multiple carriers (or multiple carriers) and determine / obtain the situation of multiple carriers triggering multiple events based on the monitored beam quality of multiple carriers. Specifically, the situation of multiple carriers triggering multiple events can be used to indicate at least one of the following: a carrier-triggered event (or triggered event / being triggered event), a carrier not triggered event, a carrier that triggered an event, etc. In some embodiments, the situation of multiple carriers triggering multiple events can also be described as: multiple carriers triggering multiple events, multiple carriers triggering events, carriers triggering multiple events, carriers triggering events, etc., without limitation.

[0156] The multiple carriers may include carriers corresponding to the UE's serving cell, which can be the cell currently providing network services to the UE. Optionally, the multiple carriers may have different parameters such as carrier center frequency and carrier bandwidth. For example, the multiple carriers may include Type I carriers and Type II carriers. Type I carriers and Type II carriers can refer to two types of carriers with different parameters such as carrier center frequency and carrier bandwidth. The number of Type I carriers may be one or more, and the number of Type II carriers may also be one or more.

[0157] Taking multiple carriers, including first-class carriers and second-class carriers, as an example, the situation of multiple carriers triggering multiple events can include: whether the first-class carrier has a triggered event, the first-class carrier triggers an event, the first-class carrier does not trigger an event, etc., as well as whether the second-class carrier has a triggered event, the second-class carrier triggers an event, the second-class carrier does not trigger an event, etc.

[0158] In this application, the types of carriers included in multiple carriers may vary depending on the communication scenario. For example, in a carrier aggregation communication scenario, multiple carriers may include a primary carrier and a secondary carrier. In sensing communication scenarios such as 6th generation mobile networks (6G), multiple carriers may include communication carriers and sensing carriers. In a satellite-terrestrial converged communication scenario, multiple carriers may include terrestrial carriers and satellite carriers. In millimeter-wave massive MIMO communication scenarios, multiple carriers may include multiple millimeter carriers of different frequency bands, etc. The embodiments of this application mainly focus on the case where multiple carriers include a primary carrier and a secondary carrier in a carrier aggregation communication scenario; other communication scenarios can refer to the carrier aggregation communication scenario.

[0159] In this application embodiment, multiple events may include multiple events related to beam quality. These beam quality-related events can refer to events triggered when beam quality meets relevant conditions, such as the aforementioned events 1, 2, and 7. These events may be pre-configured by the base station to the UE. The UE can monitor the beam quality of each of the multiple carriers. For example, taking a carrier including a first type and a second type, the UE can monitor the beam quality of both types and determine whether the first and second types of carriers have triggered an event based on the beam quality. In this application, if an event related to the beam quality of a carrier is triggered, the event can be called a triggered event; if an event related to the beam quality of a carrier is not triggered, the event can be called a non-triggered event.

[0160] In this embodiment, beam quality-related events include at least a first event and a second event, which are different events. A first type of carrier may trigger the first event and / or the second event, and a second type of carrier may also trigger the first event and / or the second event. Depending on the event type, there can be various combinations of the first event and the second event.

[0161] In one example, the first event and the second event are event 2 and event 7, respectively. For example, the first event is event 2 and the second event is event 7. Or, the first event is event 7 and the second event is event 2.

[0162] In another example, the first event and the second event are event 2 and event 1, respectively. For example, the first event is event 2 and the second event is event 1. Or, the first event is event 1 and the second event is event 2.

[0163] In another example, the first event and the second event are event 7 and event 1, respectively. For example, the first event is event 7 and the second event is event 1. Or, the first event is event 1 and the second event is event 7.

[0164] In another example, the first event is event 2 and / or event 7, and the second event is event 1. Alternatively, the first event is event 1, and the second event is event 2 and / or event 7.

[0165] In this embodiment, the UE can monitor the occurrence of multiple events triggered by multiple carriers within a time window. For example, taking a first-type carrier and a second-type carrier as examples, the UE can monitor the beam quality of the first-type carrier and the second-type carrier within the time window to determine whether the first-type carrier triggers a first event and / or a second event, and whether the second-type carrier triggers a first event and / or a second event. The UE can determine that the occurrence of multiple events triggered by multiple carriers within the time window includes any one or more of the following: the first-type carrier triggers a first event and / or a second event, the first-type carrier does not trigger a first event and a second event, the second-type carrier triggers a first event and / or a second event, and the second-type carrier does not trigger a first event and a second event.

[0166] S220, the UE sends the first information to the base station based on the multi-carrier triggering multi-event situation.

[0167] Correspondingly, the base station receives the first information sent by the UE.

[0168] In this application, the UE obtains information about multiple carriers triggering multiple events and indicates this information through first information. The first information may include multiple bits, which indicate the multi-carrier triggering of multiple events. In specific implementations, multiple bits can be combined into a bit map, and the first information can be indicated in the form of a bit map, or it can be indicated in the form of characters. A bit map is a data structure used to represent the state of a set of bits. Each bit can be 0 or 1, representing a certain state or attribute. The specific implementation scheme for indicating information through each bit in the first information will be explained later in the form of a bit map. Bits can also be bit fields or other byte formats, without limitation.

[0169] In this embodiment of the application, the first information may be up control information (UCI) carried on the physical uplink control channel (PUCCH).

[0170] There are several PUCCH formats, including Format 0, Format 1, Format 2, Format 3, and Format 4. Different PUCCH formats occupy different numbers of symbols in a time slot, and can transmit different numbers of bits of information. Format 0, Format 1, and Format 2 use fewer symbols and can transmit no more than 2 bits of information. Format 3 and Format 4 use more symbols and can transmit more than 2 bits of information. Format 3 is a long PUCCH, occupying 4-14 symbols, and can transmit UCI with larger amounts of information or a larger number of bits.

[0171] In a specific example, the UE can use a PUCCH of Format 3 to send the aforementioned first information. Alternatively, the UE can carry multiple bits of the first information via a Format 3 PUCCH, indicating to the base station the situation of multiple carriers triggering multiple events. Thus, multiple bits of UCI can be carried via PUCCH format 3, with a maximum UCI payload of 6-12 bits, which can meet the encoding requirements of multiple carriers (primary carrier + multiple secondary carriers) and multiple events (events 1, 2, 7). Compared to the traditional PUCCH Format 0 / 1 (which only supports 1-2 bits), this significantly improves the information carrying capacity.

[0172] S230: Based on the first information, the base station adjusts multiple carriers.

[0173] Optionally, the base station receives and parses the first information reported by the UE to obtain the situation of multiple carriers triggering multiple events. Based on the response scheme corresponding to each event, the base station adjusts the carriers of the multiple carriers. For example, taking multiple carriers including a first type of carrier and a second type of carrier as an example, the base station can adjust the carriers of the first type of carrier according to the corresponding response scheme based on the situation of events triggered by the first type of carrier. Similarly, the base station can adjust the carriers of the second type of carrier according to the corresponding response scheme based on the situation of events triggered by the second type of carrier.

[0174] For example, the base station determines that the primary carrier triggers event 1 based on the first information. The response scheme for event 1 is to optimize and adjust the carrier. Based on this, the base station optimizes and adjusts the primary carrier. As another example, the base station determines that the primary carrier triggers event 2 based on the first information. The response scheme for event 2 is to adjust to a new beam. Based on this, for the primary carrier, the base station switches the current beam to the new beam, improving performance through rapid switching. As yet another example, the base station determines that the secondary carrier triggers event 7 based on the first information. The response scheme for event 7 is to evaluate and consider whether to switch to a new beam. Based on this, for the secondary carrier, the base station evaluates the current beam and considers whether to switch from the current beam to the new beam based on the evaluation results.

[0175] In summary, the communication method provided in this application, in a carrier aggregation scenario, allows the UE to simultaneously report multiple carrier-triggered events to the base station using a single multi-bit first information. This enables the base station to promptly obtain information about multiple carrier-triggered events and adjust the carrier accordingly, thereby improving communication efficiency. Furthermore, for multiple carrier-triggered events, the UE does not need to repeatedly report single carrier-triggered single events using single-bit uplink control information, effectively saving signaling overhead and reducing transmission latency, thus improving communication efficiency.

[0176] In this application, the first information can indicate the situation of multiple carriers triggering multiple events in the following ways:

[0177] Method 1: The first information includes at least one bit, which corresponds to at least one event among multiple events. One bit is used to indicate whether the event corresponding to the bit is a triggering event / whether it has been triggered, or it can be described as a bit used to indicate whether the event corresponding to the bit is triggered by a carrier among multiple carriers, or to indicate whether there is a carrier among multiple carriers that has triggered the event corresponding to the bit.

[0178] In Method 1, events are reported at the granular level, and whether an event has been triggered is reported using a single bit. When an event is triggered, it does not distinguish which specific carrier triggered the event. Even if multiple carriers trigger the same event, only a single bit is used to indicate that the event has been triggered. This enables carriers that trigger the same event to share the same bit and report the same bit across carriers, thereby reducing signaling overhead.

[0179] In this application, among multiple events triggered by multiple carriers, the priority relationship and / or the urgency of the events are as follows: first event > second event > third event. When reporting multiple events triggered by multiple carriers, the UE must report the first event first, then the second event, and then the third event. Alternatively, the UE may report the first, second, and third events simultaneously without restriction.

[0180] In one example, the first information includes multiple bits, with one bit corresponding to one of the multiple events, meaning that each of the multiple events implements cross-carrier shared bit reporting.

[0181] For example, taking multiple carriers including a first type carrier and a second type carrier, and multiple events including a first event and a second event as an example, the first information includes a first bit and a second bit; the first bit is used to indicate whether the first event is triggered, that is, whether it is triggered by the first type carrier and / or the second type carrier, and the second bit is used to indicate whether the second event is triggered, that is, whether it is triggered by the first type carrier and / or the second type carrier.

[0182] In another example, the first information includes bits corresponding to a subset of the multiple events, meaning that the partial events across multiple events are reported using cross-carrier shared bit reporting. These partial events can be higher-priority events among the multiple events, while the other events can be lower-priority events.

[0183] In another example, for events other than those between certain events, they can be reported by binding / combining other events with the carrier. For example, a carrier-triggered event can be determined based on the event type of other events and the carrier type, and a single bit can be used to indicate whether a carrier-triggered event has been triggered.

[0184] In this application, the bits corresponding to some events (i.e., high-priority events) are the low bits in the first information, while the bits corresponding to other events (i.e., medium-priority events and / or low-priority events) are the high bits in the first information. This allows the network device, upon receiving the first information, to prioritize parsing the triggered high-priority events according to the parsing order from low to high bits.

[0185] For example, suppose multiple carriers include a first-type carrier and a second-type carrier, and multiple triggered events include a first event, a second event, and a third event. The third event is related to beam quality and is different from both the first and second events. The third event has a lower priority than the first and second events. In this case, the first information includes a first bit, a second bit, a third bit, and a fourth bit. The first bit indicates whether the first event was triggered, i.e., whether it was triggered by a first-type carrier and / or a second-type carrier. The second bit indicates whether the second event was triggered, i.e., whether it was triggered by a first-type carrier and / or a second-type carrier. The third bit indicates whether the first-type carrier triggered the third event, and the fourth bit indicates whether the second-type carrier triggered the third event.

[0186] Optionally, the first bit is a low-order bit in the first information, or the first bit is located in a low-order bit position in the first information. When the low-order first bit is received by the base station, it will be parsed by the base station first, which allows the base station to prioritize obtaining the triggering of the first event and the second event indicated by the first bit.

[0187] Taking multiple carriers, including a primary carrier and one secondary carrier, and multiple events, including event 1, event 2, and event 7, where event 2 and event 7 are high-priority events and event 1 is a low-priority event, as an example, the first information includes four bits: the first bit, the second bit, the third bit, and the fourth bit. The first bit indicates whether event 2 has been triggered. The presence of a carrier that triggers event 2 on the primary carrier and / or the secondary carrier means event 2 has been triggered; conversely, the absence of such a carrier means event 2 has not been triggered. The second bit indicates whether event 7 has been triggered. The presence of a carrier that triggers event 7 on the primary carrier and / or the secondary carrier means event 7 has been triggered; conversely, the absence of such a carrier means event 7 has not been triggered. The third bit indicates whether the primary carrier triggers event 1, and the fourth bit indicates whether the secondary carrier triggers event 1.

[0188] In this embodiment, when events 1, 2, and 7 occur on both the primary and secondary carriers, the UE reports the multi-carrier triggering multiple events to the base station using 4 bits of first information. The UE uses the first bit to indicate the cross-carrier triggering event 2, and the second bit to indicate the cross-carrier triggering event 7. This ensures that higher-priority events 2 and 7 are reported first, while also saving bits in the first information.

[0189] In one specific example, the first information includes bits from low to high: Bit0-Bit3, where the first bit can be Bit0, the second bit can be Bit1, the third bit can be Bit2, and the fourth bit can be Bit3. Thus, the lowest bit in the first information is decoded first, and the highest bit is decoded last. The first information uses the lowest bit to indicate the triggering status of the highest priority event 2. This allows the base station to quickly obtain information about the triggering of event 2, facilitating timely carrier adjustment to ensure communication continuity and stability.

[0190] In this application, the result indicated by each bit is determined based on the value of the bit. For example, in Method 1, the first bit indicates whether the first event is a triggering event, and this indication is based on the value of the first bit.

[0191] For example, the value of the first bit is a first value, indicating that the first event is a triggering event; the value of the first bit is a second value, indicating that the first event is not a triggering event. The first value and the second value can be any different values. For example, the first value is 1 and the second value is 0. Or, the first value is 0 and the second value is 1.

[0192] When a bit is 0, it indicates that the corresponding carrier and / or event has not been triggered; when a bit is 1, it indicates that the corresponding carrier and / or event has been triggered. Alternatively, a bit value of 1 indicates that the corresponding carrier and / or event has not been triggered, and a bit value of 0 indicates that the corresponding carrier and / or event has been triggered; there is no limitation. This application describes the situation using the example of a bit value of 0 indicating that the corresponding carrier and / or event has not been triggered, and a bit value of 1 indicating that the corresponding carrier and / or event has been triggered.

[0193] In a specific example, for a scenario involving multiple carriers including a primary carrier and a secondary carrier, and multiple events including event 1, event 2, and event 7, where event 2 and event 7 are high-priority events and event 1 is a low-priority event, the scheme for the first information to include 4 bits can be shown in Table 1 below:

[0194] Table 1

[0195]

[0196] Based on Table 1 above, the UE can generate first information based on the detected situation where multiple events are triggered by multiple bits. The following examples will describe the possible ways the UE can generate first information based on the situation where multiple events are triggered by multiple carriers, using Table 1 as a reference.

[0197] Example 1: Primary carrier triggers event 2, secondary carrier triggers event 7.

[0198] The process by which the UE determines the encoding of the first information based on the multi-carrier triggering multi-event scenario can be as follows:

[0199] The primary carrier triggers event 2, i.e., Bit 0 is set to 1. The secondary carrier triggers event 7, i.e., Bit 1 is set to 1. The primary carrier does not trigger event 1, i.e., Bit 2 is set to 0. The secondary carrier does not trigger event 1, i.e., Bit 3 is set to 0. Thus, the encoding of the first information is: 1100.

[0200] Alternatively, the process by which the UE determines the encoding of the first information based on the multi-carrier triggering multi-event scenario can be as follows:

[0201] Primary carrier trigger event 2, i.e., Bit 0 is set to 1. Secondary carrier trigger event 7, i.e., Bit 1 is set to 1. All other bits are set to 0.

[0202] Based on this, the UE determines the encoding of the first information as: 1100.

[0203] After receiving the first information, the base station decodes it to obtain:

[0204] If Bit0=1, then event 2 is triggered, meaning that there is a carrier in the primary and / or secondary carriers that triggers event 2, and the beam quality of the new beam of the carrier that triggers event 2 is higher than the threshold. In this case, the base station can switch the beam of the carrier that triggers event 2 from the current beam to the new beam.

[0205] If Bit1=1, then event 2 is triggered, meaning that there is a carrier among the primary and / or secondary carriers that triggers event 7, and the quality of the new beam of the carrier triggering event 7 is better than the Q-th best threshold of TCI. In this case, the base station can evaluate whether to switch the beam of the carrier triggering event 7 from the current beam to the new beam.

[0206] If Bit2=0, then event 1 was not triggered by the primary carrier, or in other words, the primary carrier did not trigger event 1, and the beam quality of the current beam of the primary carrier is not lower than the threshold. In this case, the base station does not need to adjust or optimize the beam quality of the current beam of the primary carrier.

[0207] If Bit3=0, then event 1 was not triggered by the secondary carrier, or in other words, the secondary carrier did not trigger event 1, and the beam quality of the current beam of the secondary carrier is not lower than the threshold. In this case, the base station does not adjust or optimize the beam quality of the current beam of the secondary carrier.

[0208] Example 2, primary carrier triggers event 1, secondary carrier triggers event 1.

[0209] The process by which the UE determines the encoding of the first information based on the multi-carrier triggering multi-event scenario can be as follows:

[0210] When the primary carrier triggers event 1, Bit 2 is set to 1. When the secondary carrier triggers event 1, Bit 3 is set to 1. All other bits are set to 0. Based on this, the UE determines the encoding of the first information to be: 0011.

[0211] After receiving the first information, the base station decodes it to obtain:

[0212] If Bit0=0, then event 2 is not triggered, meaning that there is no carrier in the primary or secondary carrier that can trigger event 2, and the base station does not need to make any corresponding adjustments.

[0213] If Bit1=0, then event 7 is not triggered, meaning that there is no carrier in the primary or secondary carrier that can trigger event 7, and the base station does not need to make any corresponding adjustments.

[0214] If Bit2=1, then event 1 is triggered by the primary carrier, and the beam quality of the current beam of the primary carrier is below the threshold. In this case, the base station can adjust or optimize the beam quality of the current beam of the primary carrier.

[0215] If Bit3=1, then event 1 is triggered by the secondary carrier, and the beam quality of the current beam of the secondary carrier is below the threshold. In this case, the base station can adjust or optimize the beam quality of the current beam of the secondary carrier.

[0216] Example 3: Primary carrier triggers event 2, secondary carrier triggers event 2 and event 7.

[0217] The process by which the UE determines the encoding of the first information based on the multi-carrier triggering multi-event scenario can be as follows:

[0218] If both the primary carrier and secondary carrier trigger events 2, then Bit 0 is set to 1. If the secondary carrier trigger event 7, then Bit 1 is set to 1. All other bits are set to 0. Based on this, the UE determines the encoding of the first information as: 1100.

[0219] After the base station receives the first information, the process of parsing the first information can be referred to in Examples 1 and 2, and will not be repeated here.

[0220] Example 4: Primary carrier triggers event 2, secondary carrier triggers event 1.

[0221] The process by which the UE determines the encoding of the first information based on the multi-carrier triggering multi-event scenario can be as follows:

[0222] If primary carrier triggers event 2, then Bit 0 is set to 1. If secondary carrier triggers event 1, then Bit 3 is set to 1. All other bits are set to 0. Based on this, the UE determines the encoding of the first information to be: 1001.

[0223] After the base station receives the first information, the process of parsing the first information can be referred to in Examples 1 to 3, and will not be repeated here.

[0224] These examples illustrate the encoding schemes for the first information in the case of multiple carriers triggering multiple events. In actual implementation, there are many other scenarios where multiple carriers trigger multiple events, and there are also various ways to indicate multiple carrier-triggered events using 4-bit first information encoding, which will not be elaborated upon here.

[0225] As shown above, for the highest priority events 2 and 7, a "cross-carrier shared bit" mechanism is adopted. This means that regardless of whether the event is triggered by the primary or secondary carrier, it is reported using the same bit (e.g., Bit 0 corresponds to event 2, Bit 1 corresponds to event 7). Through logical "OR" encoding, one bit can represent the same type of event across multiple carriers, significantly saving bit resources. For the lower priority event 1, bits are allocated independently per carrier (e.g., Bit 2 corresponds to primary carrier event 1, Bit 3 corresponds to secondary carrier event 1), ensuring accurate problem localization. In contrast, existing schemes require independent reporting of the same type of event across different carriers. For example, event 2 on PCC and SCC each occupies one independent PUCCH transmission bit. This scheme merges the triggering of the same event type (e.g., events 2 and 7) on different carriers into a single bit (logical "OR" operation). For example, Bit 0 simultaneously covers event 2 triggering on both PCC and SCC. The UE can quickly report the situation of multiple carriers triggering multiple events to the base station with a small number of bits, so that the base station can obtain relatively accurate information about multiple carriers triggering multiple events in a timely manner, and make carrier adjustments to improve communication efficiency.

[0226] Furthermore, Method 1 above also provides a priority-based dynamic bit allocation mechanism. Existing schemes do not distinguish event priorities, and one PUCCH bit cannot carry multiple event information. This scheme allocates bits according to event urgency (event2>event7>event1) and carrier priority (PCC>SCC), with high-priority events occupying low bits, making it easier for the network side to prioritize the parsing of high-priority event triggering.

[0227] Furthermore, in the above-mentioned method 1, when adopting the "cross-carrier shared bit" mechanism, in order to enable the network device to obtain which carrier the triggering event is, the method further includes: after the terminal device sends first information to the network device, the network device sends second information to the terminal device; the second information is used to query the carrier corresponding to the triggering event, the terminal device receives the second information and sends third information to the network device; the third information is used to indicate the carrier corresponding to the triggering event, such as the third information including the identification information of the carrier corresponding to the triggering event, etc.

[0228] The specific implementation scheme of the network device querying the terminal device for the carrier corresponding to the triggering event through the second information will be described in detail below, and will not be detailed here.

[0229] Method 2: The first information includes at least one bit, which corresponds to at least one carrier among multiple carriers. One bit is used to indicate that the carrier corresponding to the bit has triggered an event, or it can be described as one bit used to indicate whether the carrier corresponding to the bit has triggered an event among multiple events, or to indicate whether there is an event among multiple events that has been triggered by the carrier corresponding to the bit.

[0230] In Method 2, the carrier is used as the granularity. Whether the carrier has triggered an event is reported by a single bit. If the carrier has triggered an event, it does not distinguish which specific event was triggered. Even if the carrier has triggered multiple events, it only indicates that the carrier has triggered an event by a single bit. This enables the same carrier that triggers different events to share the same bit and report the bit across events, thereby reducing signaling overhead.

[0231] For example, taking multiple carriers, including a first type carrier and a second type carrier, as an example, the first information includes a first bit and a second bit. The first bit corresponds to the first type carrier and is used to indicate whether the first type carrier has triggered an event among multiple events; the second bit corresponds to the second type carrier and is used to indicate whether the second type carrier has triggered an event among multiple events.

[0232] In Method 2, the carrier is used as the granularity. The first information indicates the situation where multiple carriers trigger multiple events. For the specific implementation scheme, please refer to the implementation scheme of Method 1 which uses events as the granularity. It will not be elaborated here.

[0233] Method 3: The first information includes multiple bits, which correspond to multiple carrier trigger events. One bit is used to indicate whether the carrier trigger event corresponding to that bit has been triggered.

[0234] As described above, in this application, the carrier-triggered event is determined based on the carrier type and the event type. A carrier type and an event type can be combined to determine one or a class of carrier-triggered events.

[0235] Taking multiple carriers, including a first type of carrier and a second type of carrier, and multiple events, including a first event, a second event, and a third event, as an example, the first information includes at least one first bit, at least one second bit, and at least one third bit. At least one first bit is used to indicate whether the first event has been triggered, and one first bit corresponds to one type of carrier. At least one second bit is used to indicate whether the second event has been triggered, and one second bit corresponds to one type of carrier. At least one third bit is used to indicate whether the third event has been triggered, and one third bit corresponds to one type of carrier. That is, in method 3, the event and the carrier jointly correspond to one bit.

[0236] In some embodiments, the scheme in Method 3 above, in which the first bit indicates whether the first type of carrier and / or the second type of carrier triggers the first event, can be specifically divided into several cases.

[0237] Case 1: The first bit can be used to indicate whether the first type of carrier and the second type of carrier trigger the first event.

[0238] The value of the first bit is the first value, indicating that both the first type carrier and the second type carrier have triggered the first event. The value of the first bit is the second value, indicating that there is a carrier among the first type carrier and the second type carrier that has not triggered the first event. For example, the carrier that has not triggered the first event may include either the first type carrier or the second type carrier, or the carrier that has not triggered the first event may include both the first type carrier and the second type carrier, that is, neither the first type carrier nor the second type carrier has triggered the first event.

[0239] Case 2: The first bit can be used to indicate whether the first type of carrier or the second type of carrier triggers the first event.

[0240] The first bit being a first value indicates that one of the first and second type carriers triggered the first event. The first bit being a second value indicates that neither of the first and second type carriers triggered the first event.

[0241] Case 3: The first bit can be used to indicate whether the first type carrier and the second type carrier triggered the first event. A first value for the first bit indicates that the first type carrier and at least one of the first type carrier and the second type carrier triggered the first event. A second value for the first bit indicates that neither the first type carrier nor the second type carrier triggered the first event.

[0242] The first event is triggered by a first type carrier and / or a second type carrier, including any of the following situations:

[0243] The first type of carrier triggered the first event, while the second type of carrier did not trigger the first event.

[0244] The first type of carrier did not trigger the first event, while the second type of carrier triggered the first event.

[0245] The first type of carrier triggers the first event, and the second type of carrier also triggers the first event.

[0246] The statement that the first type of carrier and / or the second type of carrier did not trigger the first event in the above method 3 refers to the fact that neither the first type of carrier nor the second type of carrier triggered the first event.

[0247] The description of the second bit indicating the triggering of the second event by the first type of carrier and / or the second type of carrier can be found in the above description of the first bit, and will not be repeated here.

[0248] Optionally, if the first event has a higher priority than the second event, and the second event has a higher priority than the third event, the first bit is a low-order bit in the first information, or the first bit is located in a low-order bit position in the first information. When the low-order first bit is received by the base station, it will be parsed by the base station first, allowing the base station to prioritize obtaining information about whether the first event indicated by that first bit has been triggered.

[0249] Continuing with the example of events including event 1, event 2, and event 7, and multiple carriers including a primary carrier and a secondary carrier, there are two types of carriers and three types of events. These two types of carriers and three types of events can form 6 / 6 carrier-triggered events. For these 6 / 6 carrier-triggered events, the first information includes the first bit, the second bit, the third bit, the fourth bit, the fifth bit, and the sixth bit. The first bit indicates whether the primary carrier triggers event 2, the second bit indicates whether the secondary carrier triggers event 2, the third bit indicates whether the primary carrier triggers event 7, the fourth bit indicates whether the secondary carrier triggers event 7, the fifth bit indicates whether the primary carrier triggers event 1, and the sixth bit indicates whether the secondary carrier triggers event 1. The UE reports the situation of multiple carriers triggering multiple events to the base station using the 6 bits of the first information.

[0250] For example, the first bit can be Bit0, the second bit can be Bit1, the third bit can be Bit2, the fourth bit can be Bit3, the fifth bit can be Bit4, and the sixth bit can be Bit5. Bits 0 through 5 are ordered in ascending order in the first information, meaning Bit0 can be the lowest bit and Bit5 is the highest bit. The first information uses the lowest bit to indicate the situation of the most urgent primary carrier triggering event 2, allowing the base station to quickly obtain information about this event and make timely carrier adjustments to ensure communication continuity and stability.

[0251] In this method, the result indicated by each bit can be determined based on the value of the bit. For example, in this method 2, the first bit indicates whether the first event is a triggering event, and this is indicated based on the value of the first bit.

[0252] For example, the value of the first bit is a first value, indicating that event 2 is triggered; the value of the first bit is a second value, indicating that event 2 is not triggered. The first value and the second value can be any different values. For example, the first value is 1 and the second value is 0. Or, the first value is 0 and the second value is 1.

[0253] In a specific example, the bit mapping rules for each bit in the first information can be shown in Table 2 below:

[0254] Table 2

[0255]

[0256] When the base station configures one primary carrier and multiple secondary carriers for the UE, the UE can report the situation of multiple events triggered by multiple carriers through 6 bits of first information. Bit 0 indicates whether the PCC triggers event 2, and Bit 1 represents whether any SCC triggers event 2. Whenever an SCC triggers event 2, Bit 1 is set to 1. This process continues, covering Bits 0-5, since the corresponding bit will be set to 1 whenever an SCC triggers an event.

[0257] Based on Table 2 above, the UE can generate first information based on the detected multiple events triggered by multiple bits. The following examples will describe the possible ways the UE can generate first information based on the situation of multiple events triggered by multiple carriers.

[0258] Example 5: Primary carrier triggers event 2, secondary carrier triggers event 7.

[0259] The process by which the UE determines the encoding of the first information based on the multi-carrier triggering multi-event scenario can be as follows:

[0260] When the primary carrier triggers event 2, Bit 0 is set to 1. When the secondary carrier triggers event 7, Bit 3 is set to 1. When the primary carrier does not trigger events 7 or 1, Bits 2 and 4 are set to 0. When the secondary carrier does not trigger events 2 or 1, Bits 1 and 5 are set to 0. Based on this, the UE determines the encoding of the first information to be: 100100.

[0261] Alternatively, the process by which the UE determines the encoding of the first information based on the multi-carrier triggering multi-event scenario can be as follows:

[0262] Primary carrier trigger event 2, i.e., Bit 0 is set to 1. Secondary carrier trigger event 7, i.e., Bit 3 is set to 1. All other bits are set to 0. Based on this, the UE determines the encoding of the first information as: 100100.

[0263] After receiving the first information, the base station can parse the multi-carrier-triggered multi-event situation according to the encoding of the first information as follows:

[0264] If Bit0=1, then the primary carrier triggers event 2, and the beam quality of the new beam of the primary carrier that triggers event 2 is higher than the threshold. In this case, the base station can switch the beam of the carrier that triggers event 2 from the current beam to the new beam.

[0265] If Bit1=0, then there is no carrier that triggers event 2 among all secondary carriers, and the base station does not need to make any corresponding adjustments.

[0266] If Bit2=0, then event 7 is not triggered on the primary carrier, and the base station does not need to make any corresponding adjustments.

[0267] If Bit3=1, then there exists a carrier among all secondary carriers that triggers event 2, and the beam quality of the new beam of the secondary carrier that triggers event 2 is better than the Q-th best threshold of TCI. In this case, the base station can evaluate whether to switch the beam of the secondary carrier that triggers event 7 from the current beam to the new beam.

[0268] If Bit4=0, then event 1 is not triggered on the primary carrier, and the base station does not need to make any corresponding adjustments.

[0269] If Bit5=0, then there is no carrier among all secondary carriers that triggers event 1, and the base station does not need to make any corresponding adjustments.

[0270] Example 6, primary carrier triggers event 1, secondary carrier triggers event 1.

[0271] The process by which the UE determines the encoding of the first information based on the multi-carrier triggering multi-event scenario can be as follows:

[0272] When the primary carrier triggers event 1, bit 4 is set to 1. When the secondary carrier triggers event 1, bit 5 is set to 1. All other bits are set to 0. Based on this, the UE determines the encoding of the first information as: 000011.

[0273] After receiving the first information, the base station parses the multi-carrier triggering multi-event situation according to the encoding of the first information. For details, please refer to the aforementioned example, which will not be repeated here.

[0274] Example 7: Primary carrier triggers event 2, secondary carrier triggers event 1.

[0275] The process by which the UE determines the encoding of the first information based on the multi-carrier triggering multi-event scenario can be as follows:

[0276] If primary carrier triggers event 2, then Bit 0 is set to 1. If secondary carrier triggers event 1, then Bit 5 is set to 1. All other bits are set to 0. Based on this, the UE determines the encoding of the first information to be: 100001.

[0277] These examples illustrate encoding schemes for the first information in scenarios where multiple carriers trigger multiple events, which frequently occur when using 6 bits of first information to report multiple carrier-triggered events. In practice, there are many other scenarios where multiple carriers trigger multiple events, and there are also various ways to encode and indicate these scenarios using 6 bits of first information, which will not be elaborated upon here.

[0278] Unlike Method 1, Method 3 is more suitable for situations where the UE's current serving cell has multiple secondary carriers. This allows for the separate reporting of multiple events triggered by the primary and secondary carriers. By separating event types and carrier types into different bit indications, this method effectively avoids information ambiguity caused by cross-carrier merging. Furthermore, compared to the single-bit reporting of a single event scheme, Method 2 can still simultaneously and quickly report multiple events triggered by multiple carriers to the base station using multiple bits of information, enabling the base station to obtain relatively accurate information about multiple events triggered by multiple carriers in a timely manner and perform carrier adjustments, thereby improving communication efficiency.

[0279] Method 4: The first information includes a single bit that indicates whether all events out of multiple events have been triggered, or whether some events have been triggered. For example, this single bit can indicate whether the first event and the third event have both been triggered. Which events share the same bit can be set as needed and is not restricted.

[0280] For example, considering multiple events including a first event, a second event, and a third event, the first event has a higher priority than the second event, and the second event has a higher priority than the third event. The triggering status of the first and third events can share the same bit for reporting, while the triggering status of the second event can be ignored and not reported. Alternatively, a separate bit can be set for the second event, and its triggering status can be reported using this corresponding bit.

[0281] Continuing with the example of events including event 1, event 2, and event 7, if both the highest priority event 2 and the lowest priority event 1 are triggered, the UE can report the triggering of events 2 and 1 using 1 bit of first information. The following example illustrates this situation:

[0282] Example 8: Primary carrier triggers event 2, secondary carrier triggers event 1.

[0283] If the UE detects that both event 2 and event 1 have been triggered, the UE can encode the first information as: 1. If the first information includes 1 bit and the value of that bit is 1, it indicates that both event 2 and event 1 have been triggered.

[0284] In some implementations, the solution provided by this method 4 can be used in conjunction with the above-described method 1. For example, in one instance, if at least one of events 2 and 1 is not triggered, the UE can generate and report the first information according to the aforementioned method 1. If both events 2 and 1 are triggered, the UE can generate and report the first information according to method 4.

[0285] For example, in the cases shown in Examples 1 to 3 above, if at least one of Event 2 and Event 1 is not triggered, the UE generates and reports the first information using Method 1. In the case shown in Example 4 above, if both Event 2 and Event 1 are triggered, the UE generates the first information using Method 4 instead of Method 1.

[0286] In other implementations, the solution provided by method 4 can be used in conjunction with method 3 described above. In one example, if at least one of events 2 and 1 is not triggered, the UE can generate and report the first information according to method 3. If both events 2 and 1 are triggered, the UE can generate and report the first information according to method 4.

[0287] For example, in the cases shown in Examples 5 and 6 above, at least one of events 2 and 1 is not triggered, and the UE generates the first information using method 3. In the case shown in Example 7 above, both events 2 and 1 are triggered, and the UE generates the first information using method 4 instead of method 3.

[0288] The communication method provided in this approach allows the UE to report to the base station, based on 1 bit of initial information, that both high-priority event 2 and low-priority event 1 have been triggered. Alternatively, the UE can report only that event 2 has been triggered. This further saves bit overhead and ensures that emergency events are reported first, thus guaranteeing communication efficiency.

[0289] As can be seen from the above, various implementation methods are provided to indicate the situation of multiple carriers triggering multiple events. Specifically, in order for the network device and the terminal device to obtain the situation of multiple carriers triggering multiple events through the first information, the network device and the terminal device need to synchronize the first information. In view of this, before executing S10, the communication method provided in this application embodiment may further include:

[0290] The network device sends configuration information to the terminal device. The configuration information is used to configure multiple carriers, multiple events, the triggering conditions of each event, and the reporting method after the event is triggered; the multiple events include event 2, event 7, and event 1, and the multiple carriers include the primary carrier and the secondary carrier.

[0291] The network device synchronizes this first information with the terminal device through configuration information. The following provides another communication method, detailing how the network device configures the 4-bit first information provided in method 1 above for the terminal device. See [link to documentation]. Figure 3 This is a schematic diagram of another communication method provided in an embodiment of this application. Figure 3 As shown, the main steps include:

[0292] S300: The base station sends configuration information to the UE.

[0293] Correspondingly, the UE receives configuration information sent by the base station.

[0294] The configuration information is used to configure multiple carriers, multiple events, the triggering conditions of each event, and the reporting method after the event is triggered; the multiple events include event 2, event 7, and event 1, and the multiple carriers include the primary carrier and the secondary carrier.

[0295] The reporting method for multiple events triggered by multiple carriers includes method 1 described above. Alternatively, the reporting method for multiple events triggered by multiple carriers includes both method 1 and method 3 described above.

[0296] In some embodiments, the configuration information can also be used to configure at least one of the following: the reporting method for multiple events triggered by multiple carriers, the mapping relationship between events and bits, the event type, the carrier range bound to the event, the allocated bits, or the event priority. The mapping relationship between events and bits, the event type, the carrier range bound to the event, the allocated bits, or the event priority can all be used to assist in instructing the terminal device to generate first information. In other words, the information indicated by the configuration information can all be used to configure the reporting method for multiple events triggered by multiple carriers to the terminal device. The terminal device can generate and report first information based on this configuration information and the current situation of multiple events triggered by multiple carriers.

[0297] In this embodiment, the base station sends configuration information to the UE so that the UE can obtain the triggering conditions of events and the reporting method after the events are triggered. The base station can send this configuration information to the UE after the UE establishes a radio resource control (RRC) connection with the base station. Alternatively, the base station can also send this configuration information to the UE each time a new carrier is allocated to the UE, so that the UE can monitor and report the triggering conditions and reporting methods of multiple events triggered by multiple carriers according to the configuration information.

[0298] In practice, the configuration information can be carried in RRC reconfiguration messages or other downlink control information (DCI) messages, without limitation.

[0299] In a specific example, the base station can send configuration information using the following process and format:

[0300] The base station defines the Channel State Information Reporting Configuration (CSI - ReportConfig), which indicates the correspondence between bits in the reported information and the events indicated.

[0301] The report configuration identifier is defined as: reportConfigId INTEGER (0..63).

[0302] The report type set is defined as: reportType ENUMERATED {event1, event2, event7}. That is, reports are made for events 1, 2, and 7.

[0303] The carrier set is defined as: carrierAssociation ENUMERATED {pcc, scc, anyCarrier}. The bound carrier range includes PCC, SCC, and any carrier (primary and / or secondary carriers).

[0304] The bit identifier is defined as: bitPosition INTEGER (0..3), which means that the allocated bit is Bit (0-3).

[0305] Event priority can be defined as eventPriority INTEGER (1..3), meaning event priority can be defined as 1-3. Event priorities include 1, 2, and 3, in ascending order of numerical value and descending order of priority. Event priority 1 indicates the highest priority, event priority 2 indicates the second highest priority, and event priority 3 indicates the lowest priority.

[0306] Based on this, the correspondence between bits and events in the reported information can include: Bit 0 corresponds to event 2.

[0307] Furthermore, the base station can also configure the format of the PUCCH carrying the first information, the resources of the PUCCH, and the number of bits (i.e., bit capacity) occupied by the first information / UCI carrying the first information. The PUCCH resources include time-domain resources and frequency-domain resources. The following fields are examples of the base station configuring the format and capacity of the PUCCH carrying the first information for the UE:

[0308] PUCCH-Resource ::= SEQUENCE {

[0309] format ENUMERATED {format3}, -- Use Format 3 to support multi-bit operations.

[0310] uci-PayloadSize INTEGER (4), -- Configure 4 bits

[0311] resourceAllocation SEQUENCE {

[0312] startingSymbolIndex INTEGER (0..13),

[0313] nrofSymbols INTEGER (4..14), --OFDM format symbols

[0314] }

[0315] }

[0316] The above configuration method primarily provides a configuration scheme for Mode 1 by configuring a reporting method with a PayloadSize INTEGER of 4 bits. In other cases, the base station can also dynamically adjust the number of bits configured in the PUCCH to instruct the UE to select either Mode 1 or Mode 3 to generate the first information based on the configuration information. For example, when there is only one secondary carrier, the configuration information sent by the base station is used to configure a reporting method with a 4-bit bit count, instructing the UE to generate the first information using the 4-bit reporting method (i.e., Mode 1). When there are two or more secondary carriers, the configuration information sent by the base station is used to configure a reporting method with a 6-bit bit count, instructing the UE to generate the first information using the 6-bit reporting method (i.e., Mode 3). In this way, the base station adaptively configures different reporting methods according to the carrier allocation, which can improve the reporting efficiency under different conditions and avoid resource waste by rationally allocating transmission resources.

[0317] The base station dynamically adjusts the number of bits in the PUCCH based on the UE's carrier configuration (such as one SCC or multiple SCCs) through this signaling to avoid resource waste.

[0318] In some embodiments, the specific scheme for configuring multiple carriers, multiple events, triggering conditions for each event, and reporting methods after event triggering may also include: carrying the reportConfigId field, reportType field, eventPriority field, etc. in the configuration information.

[0319] The `reportConfigId` field is the reporting configuration identifier, used to indicate the information currently configured. This configuration information can include events, carriers, event triggering conditions, reporting methods, etc. Different information corresponds to different reporting configuration identifiers. The `reportType` field indicates the reporting type, which can include events (such as event 2, event 7, and event 1), carriers (primary and secondary carriers), event triggering conditions, reporting methods, etc. The `eventPriority` field indicates the event priority.

[0320] The configuration information includes the fields mentioned above, which are used to configure events and the reporting method after an event is triggered. The following section explains the fields that may be included in the configuration information for each event.

[0321] The configuration information used to configure the triggering conditions and reporting method for event 2 (arbitrary carrier) can be as follows:

[0322] {reportConfigId=0, reportType=event2, carrierAssociation=anyCarrier,bitPosition=0,

[0323] eventPriority=1}.

[0324] In this configuration, `reportConfigId=0` indicates that the reporting configuration identifier is 0, `reportType=event2` indicates that the reporting type is event2, i.e., event 2. `carrierAssociation=anyCarrie` indicates that the carrier corresponding to event 2 can be any carrier, and `bitPosition` of 0 indicates that the reporting of event 2 occupies bit 0, which is the least significant bit in the information. `eventPriority=1` indicates that the priority of event 2 is 1, meaning that event 2 has the highest priority.

[0325] The configuration event 7 information is used to configure the triggering conditions and reporting method for (arbitrary carriers) as follows:

[0326] {reportConfigId=1, reportType=event7, carrierAssociation=anyCarrier, bitPosition=1, eventPriority=2}.

[0327] In this configuration, reportConfigId=1 indicates that the reporting configuration identifier is 1, reportType=event7 indicates that the reporting type is event7, i.e., event 7. carrierAssociation=anyCarrier indicates that the carrier corresponding to event 7 is any carrier, bitPosition=1 indicates that the reporting of event 7 occupies bit1. eventPriority=2 indicates that the priority of event 7 is 2, i.e., the second highest priority of event 7 (the priority of event 7 is lower than the priority of event 2).

[0328] The configuration information is used to configure the triggering conditions and reporting method for Event 1 (PCC), as follows:

[0329] {reportConfigId=2, reportType=event1, carrierAssociation=pcc, bitPosition=2, eventPriority=3}.

[0330] In this context, reportConfigId=2 indicates that the reported configuration identifier is 2, reportType=event1 indicates that the reported type is event1, i.e., event 1. carrierAssociation=pcc indicates that the carrier corresponding to event 1 is the primary carrier, bitPosition=2 indicates that the report of event 7 occupies bit 2. eventPriority=3 indicates that the priority of event 4 is 3, i.e., event 1 has the lowest priority (event 1's priority is lower than event 7's priority).

[0331] Configure the triggering conditions and reporting method for Event 1 (SCC):

[0332] {reportConfigId=2, reportType=event1, carrierAssociation=scc, bitPosition=3, eventPriority=3}.

[0333] In this context, reportConfigId=2 indicates that the reported configuration identifier is 2, reportType=event1 indicates that the reported type is event7, i.e., event 1. carrierAssociation=pcc indicates that the carrier corresponding to event 4 is the primary carrier, bitPosition=3 indicates that the report of event 7 occupies bit 3. eventPriority=3 indicates that the priority of event 4 is 3, i.e., the priority of event 1 is the lowest (the priority of event 1 is lower than the priority of event 7).

[0334] In practice, base stations may also use other formats or forms to generate configuration information so that UEs can obtain multiple carriers triggering multiple events based on the configuration information, without limitation.

[0335] It should be noted that when sending configuration information, the base station can also configure the specific reporting method (mode 3 or mode 1) after an event is triggered through certain fields of the configuration information. For example, the configuration information may also include a reporting method indication field, which is used to configure the bit capacity to be 4 bits or 1 bit. Specifically, if the reporting method indication field is configured with a bit capacity of 1 bit, the corresponding reporting condition is that event2 and event1 are triggered simultaneously. If the reporting method indication field is configured with a bit capacity of 4 bits, the corresponding reporting condition is any condition other than the simultaneous triggering of event2 and event1.

[0336] Alternatively, the base station can also use other forms of configuration information to indicate to the UE the reporting method under different event triggering conditions. The UE reports the multi-carrier-triggered multi-event situation based on method 1, and the UE selects either method 1 or method 4 to report the multi-carrier-triggered multi-event situation based on the multi-carrier-triggered multi-event situation.

[0337] When the base station receives multi-bit first information, it parses the first information using method 1. When the base station receives single-bit first information, it parses the first information using method 4.

[0338] The above method primarily uses the 4-bit reporting method provided in Method 1 as an example to explain the specific implementation scheme of the base station sending configuration information to the terminal device. In other embodiments, the specific implementation method of the base station sending configuration information to the terminal device can also be applied to the 6-bit reporting method provided in Method 3. The implementation method of the base station instructing the UE to report multiple carriers triggering multiple events in Method 3 can be found in the implementation method of the base station instructing the UE to report multiple carriers triggering multiple events in Method 1. Furthermore, the implementation method of the base station instructing the UE to report multiple carriers triggering multiple events in "Method 3 + Method 4" can also be found in the implementation method of the base station instructing the UE to report multiple carriers triggering multiple events in "Method 1 + Method 3", and will not be elaborated further.

[0339] This solution allows for flexible configuration of the binding relationship between events, carriers, and bits, and supports multi-bit reporting, enabling the reporting of multiple carriers that trigger multiple events. An enhanced CSI report configuration mechanism is also included. By modifying the CSI-ReportConfig structure, new fields such as carrierAssociation (binding carrier range) and eventPriority are added to support dynamic mapping between events and bits.

[0340] S310, the UE monitors the beam quality of multiple carriers based on the configuration information, and obtains the situation of multiple carriers triggering multiple events based on the monitored beam quality of multiple carriers.

[0341] Optionally, the UE obtains configuration information sent by the base station and stores the triggering conditions and reporting methods for multiple events triggered by multiple carriers. Based on the triggering conditions for multiple events triggered by multiple carriers, the UE monitors the beam quality on multiple carriers to determine whether to trigger the relevant events.

[0342] The specific implementation method of the UE obtaining multiple carriers to trigger multiple events can be found in the relevant description of S210 in the aforementioned embodiment, and will not be repeated here.

[0343] S320, the UE generates the first information according to the reporting method indicated by the configuration information and the case of multiple events triggered by multiple carriers.

[0344] S330, the UE sends the first information to the base station.

[0345] The first information includes multiple bits and is used to indicate the situation where multiple carriers trigger multiple events.

[0346] The UE acquires information about multiple carriers triggering multiple events and generates first information based on the reporting method configured in the configuration information. Specifically, the UE configures the reporting method, determines the current situation of multiple carriers triggering multiple events, matches the triggered events, carriers, and bits to determine the bits and values ​​of each reported event, and encodes them according to the values ​​and order of the bits to generate the first information. The UE sends the first information to the base station so that the base station can acquire information about multiple carriers triggering multiple events based on this first information. Note that the bits can also be any number of bits and are not limited to this.

[0347] The specific implementation method for the UE to generate the first information can be found in the aforementioned S230 and methods 1 to 4, and will not be repeated here.

[0348] S340, the base station receives and parses the first information to obtain the situation of multiple carriers triggering multiple events.

[0349] The base station receives the first information sent by the UE, and according to a predetermined reporting method of multiple events triggered by multiple carriers, parses the value of each bit in the first information to obtain the triggering status of the corresponding event.

[0350] In the first information, the first bit indicates that event 2 has been triggered. The base station can quickly know that event 2 has been triggered based on the first information, but it cannot clearly know whether the primary carrier or the secondary carrier triggered event 2. Based on this, the base station can further query the UE for the carrier that triggered event 2. If the second bit in the first information indicates that event 7 has been triggered, the base station can also further query the UE for the carrier that triggered event 7 through the following S350.

[0351] S350, the base station sends the second information to the UE.

[0352] Correspondingly, the UE receives the second information sent by the base station.

[0353] The second information is used to query the identification information of the carrier that triggered event 2 and / or event 7.

[0354] When the base station receives the first information and parses it to obtain the value of each bit indicating the multi-carrier triggering multiple events, if the first bit indicates that event 2 is triggered and / or the second bit indicates that event 7 is triggered, the base station sends the second information to the UE to query the identification information of the carrier that triggered event 2 and / or event 7.

[0355] There are multiple ways to query the carrier identification information of the second information triggering event 2 and / or event 7. Taking querying the carrier of the second information triggering event 2 as an example, we will explain the possible implementation methods of the second information.

[0356] In one example, the second information includes identification information from the first bit and / or the second bit. When the second information includes the identification information from the first bit, the second information is used to query the carrier that triggered event 2.

[0357] For example, in the first information sent by the UE to the base station, the value of the first bit is 1, indicating that event 2 has been triggered. The base station sends a second message to the UE, which includes the identification information of the first bit, to query the carrier that triggered event 2.

[0358] In another example, the second information includes identification information for event 2. When the second information includes identification information for event 2, the second information is used to query the carrier that triggered event 2.

[0359] In practical implementation, when the first bit of the first information indicates that event 2 is triggered and event 7 is triggered, the base station can query the carrier that triggered event 2 and the carrier that triggered event 7 through a second piece of information. Alternatively, the base station can query the carrier that triggered event 2 through one piece of second information and then query the carrier that triggered event 7 through another piece of second information.

[0360] The second information sent by the base station to the UE can be carried in a media access control (MAC) control element (CE) message or other downlink (DL) messages, without limitation.

[0361] Event reporting process update mechanism. In the beam reporting process, supplementary encoding rules for multi-bit PUCCH and a supplementary query mechanism for the base station to request carrier ID via MAC-CE are added.

[0362] S360, the UE sends third information to the base station.

[0363] Correspondingly, the base station receives the third information sent by the UE.

[0364] The third information includes or is used to indicate the identification information of the carrier that triggered event 2 and / or the carrier that triggered event 7. Upon receiving the second information sent by the base station, the UE, in response to the second information, sends the third information to the base station to provide the identification information of the carrier that triggered event 2 and / or event 7.

[0365] For example, if the second information is used to query the carrier that triggered event 2, and the carrier that triggered event 2 is a primary carrier, then the third information may include the identification information of the primary carrier, such as a carrier ID. Also, if the carrier that triggered the event is both a primary carrier and a secondary carrier, the third information may include the identification information of both the primary carrier and the secondary carrier.

[0366] Alternatively, if the second information is used to query the identification information of the carriers that triggered events 2 and 7, the third information may include the carrier ID of the carrier that triggered event 2 and the carrier ID of the carrier that triggered event 7.

[0367] The third information sent by the UE to the base station can be carried in MAC CE messages or other uplink (UL) messages, without limitation.

[0368] S370, the base station adjusts the carrier based on the first information, or the base station adjusts the carrier based on the first information and the third information.

[0369] The base station performs carrier adjustment in response to the multi-carrier triggering multiple events reported by the UE. The base station can obtain the multi-carrier triggering multiple events information from the first message sent by the UE, or it can obtain it from both the first and third messages sent by the UE.

[0370] It should be noted that the steps shown in S330 and S340 above are not necessary steps. For example, if the first information sent in S320 indicates that neither event 2 nor event 7 has been triggered, the base station may not need to execute the step of sending the second information to the UE in S330, and the UE may not need to send the information of sending the third information to the UE in S340. The base station can directly execute S350 after receiving the first information.

[0371] For example, if the UE sends the first information in S320 indicating that event 2 and / or event 7 have been triggered, the UE can directly execute S340 (sending the third information to the base station to indicate the identification information of the carrier that triggered event 2 and / or event 7) without the base station executing S330. This allows the base station to obtain detailed information about multiple carriers triggering multiple events more quickly and to perform carrier adjustments in a timely and accurate manner.

[0372] In summary, the communication method provided in this application reports multiple events triggered by multiple carriers using a single multi-bit information, thus improving resource utilization. Compared to schemes that independently encode and report each event on each carrier, it can reduce bit consumption by 33%-50%. By prioritizing low-priority bits, the real-time performance of high-priority events can be guaranteed, avoiding missed reporting of critical events. Dynamic signaling configuration adapts to different network scenarios (such as dense urban areas and high-speed mobile environments), meeting the high reliability and low latency communication requirements of 5G, 6G, and other communication scenarios.

[0373] See Figure 4 This is a schematic diagram of the interaction of a communication system provided in an embodiment of this application. In this embodiment, the functions of the base station and the UE are modularized, and the interaction process between the base station and the UE is explained from the perspective of the functional modules.

[0374] like Figure 4 As shown, the communication system includes a base station and a UE. The base station includes an RRC signaling configuration module, a PUCCH parsing module, and a beam management module. The UE includes a carrier monitoring module, an event priority processing module, and a PUCCH encoding module.

[0375] See Figure 5 This is a flowchart illustrating another communication method provided in an embodiment of this application. The following will be combined with... Figure 4 and Figure 5 This provides a specific implementation scheme for the UE to report multiple carriers to the base station, triggering multiple events.

[0376] On the base station side, the RRC signaling configuration module is used to send configuration information to the UE via RRC signaling to configure carriers (primary carrier PCC and secondary carrier SCC), events (event 1, event 2, event 7) and event triggering conditions, bit mapping rules, etc. The configuration information can also configure carrier priority (PCC > SCC) and PUCCH resource parameters (such as Format 3 multi-bit bearer capability), etc., to agree on beam management and event reporting rules with the UE. For the specific implementation scheme of the RRC signaling configuration module sending configuration information to the UE, please refer to the aforementioned implementation method of S300, which will not be elaborated here.

[0377] After the RRC signaling configuration module configures the event triggering conditions and reporting rules for the UE, the UE can perform beam quality monitoring and reporting based on the configuration information. Specifically, the UE-side procedures may include S510 to S540 as follows, and the base station-side procedures may include S550 to S580 as follows.

[0378] S510: The carrier monitoring module performs event monitoring.

[0379] Specifically, the UE's carrier monitoring module monitors the beam quality of each carrier in real time (such as L1-RSRP) and determines whether to trigger a corresponding event based on the beam quality. The carrier monitoring module acquires the events triggered within a time window, as well as the carriers that triggered each event.

[0380] For the specific implementation scheme of the carrier monitoring module for event monitoring, please refer to the specific implementation method of S210 mentioned above, which will not be repeated here.

[0381] For example, the carrier monitoring module monitors beam quality in real time on the PCC and SCC. Suppose that the PCC triggers event2 and the SCC triggers event1.

[0382] S520: The event priority processing module performs priority and bit matching based on the case of multiple events triggered by multiple carriers.

[0383] The event priority processing module performs cross-carrier combining on high-priority events 2 / 7 according to the priority order of "event 2 > 7 > 1, PCC > SCC" to determine the corresponding bit positions. For low-priority event 1, the corresponding bit positions are determined according to the carrier type.

[0384] Continuing with the previous example, PCC triggers event2, with the corresponding bit being Bit0; SCC triggers event1, with the corresponding bit being Bit3.

[0385] S530: The PUCCH encoding module encodes based on bit mapping rules to obtain multi-bit signals.

[0386] The PUCCH encoding module encodes the event into a multi-bit signal. Continuing the previous example, the PUCCH encoding module determines Bit0=1, Bit3=1, and the rest are 0 according to the logical "OR" and independent allocation rules, thus obtaining a multi-bit signal encoded as "1001".

[0387] The specific implementation schemes for the event priority processing module to match priorities with bits and for the PUCCH encoding module to encode multi-bit signals can be found in the aforementioned implementation of S220, and will not be elaborated upon here.

[0388] S540: The UE sends a multi-bit signal to the base station.

[0389] The PUCCH encoding module transmits the multi-bit signal encoded as "1001" via PUCCH format3 back to the base station through the wireless link.

[0390] S550: The base station receives multi-bit signals.

[0391] The base station's PUCCH parsing module receives a multi-bit signal encoded as "1001" sent by the UE.

[0392] S560: The PUCCH parsing module parses multi-bit signals to obtain information on multi-carrier triggering multiple events.

[0393] The PUCCH parsing module parses the multi-bit signal according to the multi-bit mapping rules configured by the base station, obtaining: Bit0=1 and Bit3=1. Bit0=1 indicates the triggering of cross-carrier event 2, and Bit3=1 indicates the triggering of SCC event 1.

[0394] S570: The base station requests the carrier ID from the UE via MAC-CE.

[0395] After the PUCCH parsing module determines that event 2 has been triggered across carriers, it can also request the carrier ID from the UE via MAC-CE signaling. Based on this, the UE can return the carrier ID of the carrier that triggered event 2, i.e., the PCC, to the base station via MAC-CE signaling.

[0396] The scheme for the PUCCH parsing module to parse multi-bit signals and request carrier ID can be found in the specific implementation of S340 and S360 mentioned above, and will not be repeated here.

[0397] S580: The beam management module performs carrier adjustment.

[0398] The base station's beam management module adjusts beam parameters based on events. Specifically, the beam management module can adjust carriers based on multiple events triggered by multiple carriers reported by the UE.

[0399] In the example above, the PCC triggers event 2, and the beam management module responds to event 2 by switching the PCC to the new beam. The SCC triggers event 1, and in response to event 1, the beam management module optimizes the beam quality of the SCC.

[0400] After the beam management module performs carrier adjustment, it can also update the configuration of the adjusted carrier information via RRC signaling. For example, the beam management module can synchronize the information of the new beam after PCC switching to the UE via RRC signaling, etc., without limitation. The scheme for the beam management module to perform carrier adjustment can be found in the specific implementation scheme of S230 mentioned above, and will not be elaborated further.

[0401] The communication method provided in this embodiment involves the base station's PUCCH parsing module first decoding multi-bit signals to identify the event type reported by the UE. For cross-carrier events, it requests the specific carrier ID through MAC-CE signaling. Finally, the beam management module dynamically adjusts the beam according to priority (such as switching to a new beam or restoring a degraded beam). This achieves efficient, low-latency, and accurate localization (MAC-CE supplements the carrier ID) beam optimization in multiple carrier scenarios, effectively solving the technical problems of insufficient resources, latency conflicts, and ambiguous localization that exist in other solutions.

[0402] The above embodiments are mainly limited to carrier aggregation scenarios, where cross-carrier merging and reporting are performed when multiple events are triggered by the primary and secondary carriers. The communication method provided in this application can also be extended to the following communication scenarios.

[0403] (1) In the integrated communication scenarios such as 6G, the first type of carrier can be a communication carrier and the second type of carrier can be a sensing carrier. In the integrated communication scenario, the combined reporting of multiple events triggered across carriers can be realized.

[0404] In a 6G integrated sensing network, base stations need to support both communication and sensing core functions simultaneously. The corresponding communication carriers and sensing carriers differ significantly in their beam characteristics. The communication carrier's beam focuses on coverage to ensure the continuity of services such as high-definition video and real-time control; the sensing carrier's beam, on the other hand, prioritizes resolution and accuracy to achieve dynamic perception of the surrounding environment and target localization. This difference necessitates that the UE simultaneously monitor the beam status of both types of carriers, resulting in more frequent and complex event triggers. For example, the communication carrier may experience beam quality degradation due to factors such as obstruction, while the sensing carrier may achieve better sensing performance due to the acquisition of new beams.

[0405] The UE-provided scheme, which uses a single multi-bit information report to trigger multiple events across multiple carriers, integrates high-priority events from both communication and sensing carriers into a unified scheduling framework. The priority order of these events is dynamically adjusted based on service requirements. For example, when a sensing task involves emergency environmental awareness, priority can be given to reporting events related to the sensing carrier. Simultaneously, leveraging the high-frequency characteristics commonly used by sensing carriers, phase-domain tracking reference signals are used to enhance signal transmission stability, ensuring accurate demodulation of the multi-bit PUCCH signal. This adaptation effectively resolves signaling conflicts in sensing-sensor collaboration scenarios, ensuring real-time response to high-priority events and providing reliable beam management support for scenarios such as environmental perception and command transmission in intelligent driving, and dynamic target tracking in intelligent security.

[0406] (2) In the scenario of satellite-terrestrial converged communication, the first type of carrier can be a terrestrial carrier (or a terrestrial base station carrier), and the second type of carrier can be a satellite carrier.

[0407] In a satellite-terrestrial converged network, a UE typically needs to connect to both terrestrial base station carriers and satellite carriers simultaneously. Terrestrial carriers, with their low latency, handle real-time interactive services (such as emergency communication commands and remote control). Satellite carriers, leveraging their wide coverage, serve the communication needs of remote areas or maritime scenarios, but resources are relatively limited and transmission links are longer. The event characteristics of the two types of carriers differ significantly: terrestrial carrier events are mostly related to rapid beam switching, requiring extremely high timeliness; satellite carrier events involve more gradual changes in beam quality and can be handled with appropriate delays.

[0408] The cross-carrier multi-event merging and reporting scheme provided in the above embodiments distinguishes the event priorities of the two types of carriers, independently and quickly reporting high-priority events on the terrestrial carrier, and aggregating low-priority events on the satellite carrier across carriers, reducing the occupation of scarce satellite resources. Simultaneously, by reusing PUCCH resources and dynamically adjusting configuration parameters, the same beam management mechanism can adapt to the different characteristics of terrestrial and satellite links. This adaptation ensures both the low latency requirements of terrestrial services and optimizes the resource utilization efficiency of satellite links, providing effective support for balancing "wide coverage and high reliability" in scenarios such as emergency communication in remote areas and marine IoT.

[0409] (3) In the millimeter wave massive MIMO scenario, the first type carrier and the second type carrier can be millimeter waves of different frequency bands.

[0410] In millimeter-wave massive MIMO scenarios, base stations expand bandwidth by deploying multiple millimeter-wave carriers in different frequency bands to support high-bandwidth services such as indoor high-definition video and AR / VR. The narrow beam characteristics of millimeter-wave beams make them extremely sensitive to factors such as obstruction and movement, and each carrier is prone to frequently triggering new beam acquisition events due to environmental changes; at the same time, phase domain noise problems in the high-frequency band can also affect the reliability of signal transmission.

[0411] The cross-carrier multi-event merging and reporting scheme provided in the above embodiments reduces signaling transmission resource consumption by aggregating similar events from multiple millimeter-wave carriers. To address phase domain noise issues, the phase domain tracking mechanism is enhanced to improve signal demodulation accuracy. Furthermore, it supports dynamic adjustment of the PUCCH load capacity based on the number of carriers, adapting to future expansion needs with more frequency bands. This adaptation effectively solves the resource overhead and reliability problems of managing multiple carrier events in millimeter-wave scenarios, providing efficient beam management support for the continuous and stable operation of high-bandwidth indoor services and promoting the implementation of emerging applications such as immersive interaction.

[0412] In summary, the various communication methods provided in this application, through multi-bit PUCCH design, cross-carrier event merging, and dynamic signaling configuration, achieve efficient beam management to solve the resource efficiency and real-time issues of beam status reporting in multi-carrier scenarios.

[0413] It should be understood that Figures 1 to 5 The flowcharts or scene diagrams shown are for illustrative purposes only and are not intended to limit the embodiments of this application to the examples illustrated. In fact, those skilled in the art can interpret the embodiments based on... Figures 1 to 5 The examples in the document can be transformed into equivalent ways to obtain more implementations.

[0414] The above text combined Figures 1 to 5 This document describes in detail the communication method provided in the embodiments of this application. The following will combine... Figures 6 to 7 The device embodiments of this application are described in detail below. It should be understood that the communication device of this application embodiment can execute the various communication methods of the foregoing embodiments of this application, that is, the specific working processes of the various products below can be referred to the corresponding processes in the foregoing method embodiments.

[0415] In the embodiments described above, the terminal device may execute some or all of the steps in each embodiment; the network device may execute some or all of the steps in each embodiment. These steps or operations are merely examples, and the embodiments of this application may also perform other operations or variations thereof. Furthermore, the steps may be executed in different orders as presented in the embodiments, and it is not necessary to execute all the operations in the embodiments of this application. Moreover, the sequence number of each step 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.

[0416] Figure 6 This is a schematic block diagram of a communication device provided in an embodiment of this application. Figure 6 As shown, the communication device 600 may include a communication module 620. The communication module 620 can implement corresponding communication functions, which can be internal communication functions of the communication device 600 or communication functions between the communication device 600 and other devices. Optionally, the communication module 620 may also be referred to as a communication interface or transceiver module. Optionally, the communication device 600 further includes a processing module 610. The processing module 610 can implement corresponding processing functions.

[0417] Optionally, the communication device 600 further includes a storage module, which can be used to store instructions and / or data; the processing module 610 can read the instructions and / or data in the storage module so that the communication device 600 can implement the aforementioned method embodiments.

[0418] In one possible design, the communication device 600 may correspond to the terminal device in the above method embodiments, or to a component (such as a circuit, chip, or chip system) configured in the terminal device. The communication device 600 can be used to perform the steps or processes performed by the terminal device in any of the above method embodiments.

[0419] For example, the communication device 600 may correspond to the above. Figure 4 The UE in the communication system shown.

[0420] In one case, communication device 600 corresponds to Figure 4 The UE is connected to the communication module 620, which can correspond to a communication module within the UE side, such as a carrier monitoring module and a PUCCH encoding module. The processing module 610 can correspond to a processing module within the UE side, such as an event priority processing module.

[0421] In one possible design, the communication device 600 may correspond to a network device (such as a base station) in the above method embodiments, or a component (such as a circuit, chip, or chip system) configured in a network device. The communication device 600 can be used to perform the steps or processes performed by the network device in any of the above method embodiments.

[0422] For example, the communication device 600 may correspond to the above. Figure 4 The base station in the communication system shown.

[0423] In one case, communication device 600 corresponds to Figure 4 The base station in the system. The communication module 620 can correspond to a module with communication function on the base station side, such as an RRC signaling configuration module and a beam management module, and the processing module 610 can correspond to a module with communication function on the policy side, such as a PUCCH parsing module.

[0424] Figure 7 This is another schematic block diagram of the communication device provided in the embodiments of this application. The communication device 700 may be a chip, chip system, or processor, etc., in a terminal device or network device that implements the above-described methods. The communication device 700 can be used to implement the methods described in the above-described method embodiments; for details, please refer to the descriptions in the above-described method embodiments.

[0425] like Figure 7As shown, the communication device 700 may include one or more processors 710, which may also be referred to as processing units or processing modules, and can implement certain control functions. The processor 710 may be a general-purpose processor or a dedicated processor, such as a baseband processor or a central processing unit. The baseband processor can be used to process communication protocols and communication data, while the central processing unit can be used to control the communication device 700 (e.g., a base station, baseband chip, user, user chip), execute software programs, and process data from the software programs.

[0426] In an alternative design, the processor 710 may also store instructions and / or data that can be executed by the processor 710 to cause the communication device 700 to perform the methods described in the above method embodiments.

[0427] In another alternative design, the communication device 700 may include a communication interface 720 for implementing receiving and transmitting functions. For example, the communication interface 720 may be a transceiver circuit, interface, interface circuit, or transceiver. The transceiver circuit, interface, interface circuit, or transceiver for implementing receiving and transmitting functions may be separate or integrated. The aforementioned transceiver circuit, interface, interface circuit, or transceiver may be used for reading and writing code / data, or it may be used for transmitting or relaying signals.

[0428] Optionally, the communication device 700 may include one or more memories 730, which may store instructions that can be executed on the processor 710, causing the communication device 700 to perform the methods described in the above method embodiments. Optionally, the memories 730 may also store data. Optionally, the processor 710 may also store instructions and / or data. The processor 710 and the memories 730 may be provided separately or integrated together.

[0429] It should be understood that, in one possible design, the steps in the method embodiments provided in this application can be implemented by integrated logic circuits in the processor's hardware or by instructions in software form. The steps of the methods disclosed in the embodiments of this application can be directly implemented by a hardware processor, or implemented by a combination of hardware and software modules in the processor. The software modules can reside in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. This storage medium is located in memory, and the processor reads information from the memory and, in conjunction with its hardware, completes the steps of the above method. To avoid repetition, detailed descriptions are not provided here.

[0430] In one implementation, the communication device 700 may correspond to the terminal device in the above method embodiments and may be used to execute the various steps and / or processes executed by the terminal device in the above method embodiments. The processor 710 may be used to execute instructions stored in the memory 730, and when the processor 710 executes the instructions stored in the memory, the processor 710 is used to execute the various steps and / or processes of the above method embodiments corresponding to the terminal device.

[0431] In another implementation, the communication device 700 may correspond to the network device in the above method embodiments and may be used to execute the various steps and / or processes executed by the network device in the above method embodiments. The processor 710 may be used to execute instructions stored in the memory 730, and when the processor 710 executes the instructions stored in the memory, the processor 710 is used to execute the various steps and / or processes of the above method embodiments corresponding to the network device.

[0432] It should be understood that the aforementioned processing device can be one or more chips. For example, the processing device can be a field-programmable gate array (FPGA), an application-specific integrated circuit (ASIC), a system-on-chip (SoC), a central processor unit (CPU), a network processor (NP), a digital signal processor (DSP), a microcontroller unit (MCU), a programmable logic device (PLD), or other integrated chips.

[0433] It is understood that the memory in the embodiments of this application can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous linked dynamic random access memory (SLDRAM), and direct rambus RAM (DR RAM). It should be noted that the memory used in the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0434] According to the method provided in the embodiments of this application, this application also provides a chip system, which includes one or more processors for calling and executing instructions stored in memory, thereby causing the method described in the embodiments of this application to be executed. The chip system may be composed of chips or may include chips and other discrete devices.

[0435] The chip system may include input circuits or interfaces for transmitting information or data, and output circuits or interfaces for receiving information or data.

[0436] According to the method provided in the embodiments of this application, this application also provides a communication system, which includes the aforementioned network device and terminal device.

[0437] According to the method provided in the embodiments of this application, this application also provides a computer program product, which includes: computer program code, which, when run on a computer, causes the computer to execute the various steps or processes executed by the network device or terminal device in any of the foregoing method embodiments.

[0438] According to the method provided in the embodiments of this application, this application also provides a computer-readable storage medium storing program code, which, when run on a computer, causes the computer to execute the various steps or processes executed by the network device or terminal device in any of the foregoing method embodiments.

[0439] The computer-readable storage medium may be the aforementioned volatile memory or non-volatile memory, or it may include both volatile memory and non-volatile memory.

[0440] In the embodiments of this application, the terms and English abbreviations are exemplary examples given for ease of description and should not be construed as limiting the application in any way. This application does not preclude the possibility of defining other terms that can achieve the same or similar functions in existing or future agreements.

[0441] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented, in whole or in part, as a computer program product. The computer program product includes one or more computer instructions. When these computer instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated.

[0442] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of 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 system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0443] It should be 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.

[0444] In summary, the above description is merely a preferred embodiment of the technical solution of this application and is not intended to limit the scope of protection of this application. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of protection of this application.

Claims

1. A communication method, characterized in that, include: Obtain first information; The first information is used to indicate a situation where multiple carriers trigger multiple events, which includes at least one of the following: a trigger event, a carrier among multiple carriers that triggers the trigger event, and a carrier among multiple carriers that does not trigger the trigger event; the trigger event refers to an event among multiple events that meets a preset trigger condition, or an event among multiple events that is triggered; the first information includes at least one bit, the at least one bit corresponding to at least one event among multiple events, and one bit used to indicate whether the event corresponding to the bit is triggered by a carrier among multiple carriers; Send the first information to the network device.

2. The method according to claim 1, characterized in that, The method further includes: The system receives configuration information sent by the network device; the configuration information is used to configure the triggering conditions for the multiple carriers to trigger the multiple events. Based on the configuration information, monitor the beam quality of each of the multiple carriers; For each carrier, the triggering status of the carrier is determined based on the beam quality of the carrier and the triggering conditions. The triggering status includes at least one of the following: whether the carrier triggers an event, the triggering event corresponding to the carrier, or the non-triggering event corresponding to the carrier. The acquisition of the first information includes: acquiring the first information based on the triggering status of each carrier.

3. The method according to claim 2, characterized in that, The multiple carriers include a first type of carrier and a second type of carrier; The multiple events include the first event and the second event; The first information includes a first bit and a second bit; the first bit is used to indicate whether the first event is triggered by the first type of carrier and / or the second type of carrier, and the second bit is used to indicate whether the second event is triggered by the first type of carrier and / or the second type of carrier.

4. The method according to claim 3, characterized in that, The plurality of events also includes a third event; the priority of the third event is lower than the priority of the first event and the priority of the second event; The first information also includes the third and fourth bits; The third bit is used to indicate whether the first type of carrier triggers the third event, and the fourth bit is used to indicate whether the second type of carrier triggers the third event.

5. The method according to claim 4, characterized in that, The first bit and the second bit are the low bits of the first information. The third bit and the fourth bit are the high bits in the first information.

6. The method according to claim 1, characterized in that, After sending the first information to the network device, the method further includes: Receive second information sent by the network device; the second information is used to query the carrier corresponding to the triggering event. Send third information to the network device; the third information is used to indicate the carrier corresponding to the triggering event.

7. The method according to claim 1 or 2, characterized in that, The first information includes multiple bits corresponding to multiple carrier trigger events; one bit is used to indicate whether the carrier trigger event corresponding to the bit has been triggered; The multiple carrier trigger events are determined based on the carrier type of the multiple carriers and the event type of the multiple events, and a single carrier trigger event is determined based on a carrier type and an event type.

8. The method according to claim 7, characterized in that, The multiple carriers include a first type of carrier and a second type of carrier; The multiple events include the first event, the second event, and the third event; The first information includes a first bit, a second bit, a third bit, a fourth bit, a fifth bit, and a sixth bit; The first bit is used to indicate whether the first type of carrier triggers the first event, and the second bit is used to indicate whether the second type of carrier triggers the first event; The third bit is used to indicate whether the first type of carrier triggers the second event, and the fourth bit is used to indicate whether the second type of carrier triggers the second event; The fifth bit is used to indicate whether the first type of carrier triggers the third event, and the sixth bit is used to indicate whether the second type of carrier triggers the third event.

9. The method according to claim 1 or 2, characterized in that, In the presence of multiple triggering events, the first information includes a bit that indicates all or some of the multiple triggering events.

10. The method according to claim 2, characterized in that, The configuration information is also used to configure at least one of the following: the reporting method for triggering the multiple events on the multiple carriers, the mapping relationship between events and bits, the event type, the carrier range bound to the event, the allocated bits, or the event priority.

11. The method according to claim 10, characterized in that, The multiple carriers include a first type of carrier and a second type of carrier; When the number of carriers of the second type is one, the bit reporting method is a 4-bit reporting method; When there are multiple carriers of the second type, the bit reporting method is a 6-bit reporting method.

12. The method according to claim 1 or 2, characterized in that, The plurality of events includes at least one of event 1, event 2, or event 7.

13. The method according to claim 1 or 2, characterized in that, In a carrier aggregation scenario, the multiple carriers include a primary carrier and at least one secondary carrier; In a sensory communication scenario, the multiple carriers include communication carriers and sensing carriers; In a satellite-terrestrial converged communication scenario, the multiple carriers include terrestrial carriers and satellite carriers; In millimeter-wave massive MIMO communication scenarios, the multiple carriers include multiple millimeter carriers of different frequency bands.

14. The method according to claim 1 or 2, characterized in that, The first information is contained in the uplink control information; The uplink control information is carried in a physical uplink control channel with a format of Format3.

15. A communication method, characterized in that, Applied to network devices, the method includes: The system acquires first information sent by a terminal device. This first information indicates a scenario where multiple carriers trigger multiple events, including at least one of the following: a trigger event, a carrier that triggers the trigger event among multiple carriers, and a carrier among multiple carriers that does not trigger the trigger event. The trigger event refers to an event among multiple events that meets a preset trigger condition, or an event among multiple events that is triggered. The first information includes at least one bit, which corresponds to at least one event among the multiple events, and one bit is used to indicate whether the event corresponding to the bit is triggered by a carrier among the multiple carriers. Based on the first information, carrier adjustment is performed on the plurality of carriers.

16. The method according to claim 15, characterized in that, The method further includes: Send configuration information to the terminal device; the configuration information is used to configure the triggering conditions for the multiple carriers to trigger the multiple events.

17. The method according to claim 15, characterized in that, The multiple carriers include a first type of carrier and a second type of carrier; The multiple events include the first event and the second event; The first information includes a first bit and a second bit; the first bit is used to indicate whether the first event is triggered by the first type of carrier and / or the second type of carrier, and the second bit is used to indicate whether the second event is triggered by the first type of carrier and / or the second type of carrier.

18. The method according to claim 17, characterized in that, The plurality of events also includes a third event; the priority of the third event is lower than the priority of the first event and the priority of the second event; The first information also includes the third and fourth bits; The third bit is used to indicate whether the first type of carrier triggers the third event, and the fourth bit is used to indicate whether the second type of carrier triggers the third event.

19. The method according to claim 18, characterized in that, The first bit and the second bit are the low bits in the first information; The third bit and the fourth bit are the high bits in the first information.

20. The method according to claim 15, characterized in that, After obtaining the first information sent by the terminal device, the method further includes: Send second information to the terminal device; the second information is used to query the carrier corresponding to the triggering event; The terminal device sends third information; the third information is used to indicate the carrier corresponding to the triggering event.

21. The method according to claim 15 or 16, characterized in that, The first information includes multiple bits corresponding to multiple carrier trigger events; one bit is used to indicate whether the carrier trigger event corresponding to the bit has been triggered; The multiple carrier trigger events are determined based on the carrier type of the multiple carriers and the event type of the multiple events, and a single carrier trigger event is determined based on a carrier type and an event type.

22. The method according to claim 21, characterized in that, The multiple carriers include a first type of carrier and a second type of carrier; The multiple events include the first event, the second event, and the third event; The first information includes a first bit, a second bit, a third bit, a fourth bit, a fifth bit, and a sixth bit; The first bit is used to indicate whether the first type of carrier triggers the first event, and the second bit is used to indicate whether the second type of carrier triggers the first event; The third bit is used to indicate whether the first type of carrier triggers the second event, and the fourth bit is used to indicate whether the second type of carrier triggers the second event; The fifth bit is used to indicate whether the first type of carrier triggers the third event, and the sixth bit is used to indicate whether the second type of carrier triggers the third event.

23. The method according to claim 15 or 16, characterized in that, In the presence of multiple triggering events, the first information includes a bit that indicates all or some of the multiple triggering events.

24. The method according to claim 16, characterized in that, The configuration information is also used to configure at least one of the following: the reporting method for triggering the multiple events on the multiple carriers, the mapping relationship between events and bits, the event type, the carrier range bound to the event, the allocated bits, or the event priority.

25. A communication device, characterized in that, The device includes at least one processor coupled to a memory storing a program or instructions, wherein the processor executes the program or instructions to cause the device to perform the communication method as claimed in any one of claims 1 to 14, or the communication method as claimed in any one of claims 15 to 24.

26. A computer-readable storage medium having a computer program or instructions stored thereon, characterized in that, When the computer program or instructions are executed, they cause the computer to perform the communication method as described in any one of claims 1 to 14, or the communication method as described in any one of claims 15 to 24.

27. A communication system, characterized in that, Includes the communication device as described in claim 25.

28. A chip system, characterized in that, The chip system includes one or more processors, which are configured to retrieve and execute instructions stored in memory, such that the communication method as described in any one of claims 1 to 14 is executed, or the communication method as described in any one of claims 15 to 24 is executed.

Images