Communication method and communication apparatus

Abstract

Provided in the present application are a communication method and a communication apparatus. The method may comprise: a terminal device side receiving configuration information, wherein the configuration information comprises information of at least one event, for example, the event may trigger the reporting of a measurement report; and the terminal device side sending first indication information, wherein the first indication information indicates at least one of the following: whether an event among the at least one event occurs, and related information of the event when the event occurs. On this basis, a network device can learn what event the reporting is triggered by, and can thus know the content to be reported by a terminal device and / or effectively allocate resources.

Description

Communication methods and communication devices

[0001] This application claims priority to Chinese Patent Application No. 202410397715.9, filed with the China National Intellectual Property Administration on April 2, 2024, entitled "Communication Method and Communication Device", the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of wireless communication, and more specifically, to a communication method and a communication device. Background Technology

[0003] In wireless communication, reference signals are transmitted between the transmitting and receiving ends to send and receive data, obtain system synchronization, and provide feedback channel information. For example, the transmitting end sends a reference signal to the receiving end, which receives the reference signal and can then perform corresponding operations based on the reference information, such as performing channel measurements and reporting measurement reports. Currently, the timing of measurement report reporting is mainly determined by network equipment, which results in significant uplink resource overhead. Summary of the Invention

[0004] This application provides a communication method and a communication device that can realize the reporting of measurement reports, reduce the overhead of uplink resources, and achieve reasonable allocation of resources.

[0005] Firstly, a communication method is provided. This method can be applied to the terminal side; that is, it can be executed by the terminal device or by components of the terminal device (such as a chip, chip system, circuit, or communication module). This application does not limit the scope of the method. The following description mainly uses a terminal device as an example.

[0006] The method may include: receiving configuration information, the configuration information including information about at least one event; sending first indication information, the first indication information indicating at least one of the following: whether an event has occurred among the at least one event, and information about the event that has occurred among the at least one event.

[0007] For example, the event is related to measurement reporting.

[0008] Based on the above technical solution, the terminal device can indicate to the network device whether any events have occurred in the configured events, and if so, the information about those events. This enables the reporting of meaningful measurement results (such as measurement results associated with occurred events), reducing uplink resource overhead. Furthermore, the terminal device indicates relevant information about the events to the network device, allowing the network device to understand what event triggered the reporting, and thus determine the content the terminal device should report and / or effectively allocate resources.

[0009] In conjunction with the first aspect, in some implementations of the first aspect, the information of the events occurring in the at least one event includes: an index of the events occurring in the at least one event.

[0010] In conjunction with the first aspect, in some implementations of the first aspect, sending the first indication information includes: sending a sequence, wherein the cyclic shift value of the sequence indicates at least one of the following: whether an event has occurred in the at least one event, and information about the event that has occurred in the at least one event.

[0011] Based on the above technical solution, the cyclic shift value of the sequence can indicate whether an event has occurred, and if so, the information of the event. In this way, by detecting the sequence, the reliability of event information acquisition can be improved and the overhead of reference signals can be saved.

[0012] In conjunction with the first aspect, in some implementations of the first aspect, the first indication information is carried in physical uplink control channel (PUCCH) format 0.

[0013] In conjunction with the first aspect, in some implementations of the first aspect, the first indication information occupies at least 1 bit; the first indication information indicates at least one of the following: whether an event has occurred in the at least one event, and information about the event that has occurred in the at least one event, including: the value of the at least 1 bit indicates at least one of the following: whether an event has occurred in the at least one event, and information about the event that has occurred in the at least one event.

[0014] Based on the above technical solution, at least 1 bit can be used to indicate whether an event has occurred, and if so, the information of the event. In this way, the indication of event-related information can be realized, and the method is simple and easy to implement.

[0015] In conjunction with the first aspect, in some implementations of the first aspect, the first indication information is carried in PUCCH format 1.

[0016] In conjunction with the first aspect, in some implementations of the first aspect, the first indication information is carried in at least one of the following channel formats: PUCCH format 2, PUCCH format 3, and PUCCH format 4.

[0017] In conjunction with the first aspect, in some implementations of the first aspect, the first indication information is a bitmap, or the first indication information indicates a scheduling request associated with an event that has occurred in the at least one event.

[0018] For example, the first indication information includes a scheduling request index associated with at least one event that has occurred.

[0019] Based on the above technical solution, a bitmap can be used to indicate whether an event has occurred, and if so, the information of that event. This reduces the signaling overhead of using multiple signaling methods to indicate multiple events when multiple events need to be indicated. Furthermore, event-related information can be indicated through event-associated scheduling requests. By reusing scheduling requests, the signaling overhead of indicating event information can be reduced.

[0020] In conjunction with the first aspect, in some implementations of the first aspect, each bit in the bitmap corresponds to an event, with a first value indicating that the event has occurred and a second value indicating that the event has not occurred; or, the value of the bitmap is associated with the combination of events that have occurred; or, the value of the bitmap is associated with whether the combination of events has occurred.

[0021] In conjunction with the first aspect, in some implementations of the first aspect, the at least one event is related to a measurement report initiated by the terminal device, and the method further includes: sending a measurement report related to an event occurring in the at least one event.

[0022] Optionally, the measurement report may be at least one of the following: an event-triggered report, an event-triggered beam report, an event-triggered channel state information (CSI) report, an event-triggered beam measurement result report, an event-triggered interference measurement report, a CSI report, a beam measurement result report, etc.

[0023] In conjunction with the first aspect, in some implementations of the first aspect, the at least one event includes at least one of the following: the first beam quality is lower than or equal to a first preset threshold, the second beam quality is higher than or equal to a second preset threshold, the second beam quality is higher than or equal to a third preset threshold of the first beam quality, and the difference between the second beam quality and the first beam quality is less than or equal to a fourth preset threshold; wherein the first beam represents a serving beam, and the second beam represents a beam different from the serving beam.

[0024] In conjunction with the first aspect, in some implementations of the first aspect, before receiving the configuration information, the method further includes: sending second indication information, the second indication information indicating information about events supported by the terminal device.

[0025] Secondly, a communication method is provided that can be applied to the network side. That is, the method can be executed by a network device or by a component of the network device (such as a chip, chip system, or circuit). This application does not limit the scope of the method.

[0026] The method may include: sending configuration information, the configuration information including information about at least one event; receiving first indication information, the first indication information indicating at least one of the following: whether an event has occurred among the at least one event, and information about the event that has occurred among the at least one event.

[0027] In conjunction with the second aspect, in some implementations of the second aspect, the information of the events occurring in the at least one event includes: an index of the events occurring in the at least one event.

[0028] In conjunction with the second aspect, in some implementations of the second aspect, receiving the first indication information includes: receiving a sequence, the cyclic shift value of the sequence indicating at least one of the following: whether an event has occurred among the at least one event, and information about the event that has occurred among the at least one event.

[0029] In conjunction with the second aspect, in some implementations of the second aspect, the first indication information is carried in the uplink control channel PUCCH format 0.

[0030] In conjunction with the second aspect, in some implementations of the second aspect, the first indication information occupies at least 1 bit; the first indication information indicates at least one of the following: whether an event has occurred in the at least one event, and information about the event that has occurred in the at least one event, including: the value of the at least 1 bit indicates at least one of the following: whether an event has occurred in the at least one event, and information about the event that has occurred in the at least one event.

[0031] In conjunction with the second aspect, in some implementations of the second aspect, the first indication information is carried in PUCCH format 1.

[0032] In conjunction with the second aspect, in some implementations of the second aspect, the first indication information is carried in at least one of the following channel formats: PUCCH format 2, PUCCH format 3, and PUCCH format 4.

[0033] In conjunction with the second aspect, in some implementations of the second aspect, the first indication information is a bitmap, or the first indication information indicates a scheduling request index associated with an event that has occurred in the at least one event.

[0034] In conjunction with the second aspect, in some implementations of the second aspect, each bit in the bitmap corresponds to an event, with a first value indicating that the event has occurred and a second value indicating that the event has not occurred; or, the values ​​of the bitmap are associated with combinations of events that have occurred; or, the values ​​of the bitmap are associated with whether combinations of events have occurred.

[0035] In conjunction with the second aspect, in some implementations of the second aspect, the at least one event is related to a measurement report initiated by the terminal device, and the method further includes: receiving a measurement report related to an event occurring in the at least one event.

[0036] In conjunction with the second aspect, in some implementations of the second aspect, the at least one event includes at least one of the following: a first beam quality is lower than or equal to a first preset threshold, a second beam quality is higher than or equal to a second preset threshold, the second beam quality is higher than or equal to a third preset threshold of the first beam quality, and the difference between the second beam quality and the first beam quality is less than or equal to a fourth preset threshold; wherein the first beam represents a serving beam, and the second beam represents a beam different from the serving beam.

[0037] In conjunction with the second aspect, in some implementations of the second aspect, before sending the configuration information, the method further includes: receiving second indication information, the second indication information indicating information about events supported by the terminal device.

[0038] For the beneficial effects and possible designs of the second aspect, please refer to the relevant description in the first aspect, which will not be repeated here.

[0039] Thirdly, a communication apparatus is provided for performing the method in any possible implementation of the first or second aspect described above. Specifically, the apparatus may include units and / or modules for performing the method in any possible implementation of the first or second aspect, such as processing units and / or communication units.

[0040] In one implementation, the device is a communication device (such as a terminal device or a network device). When the device is a communication device, the communication unit can be a transceiver or an input / output interface; the processing unit can be at least one processor. Optionally, the transceiver can be a transceiver circuit. Optionally, the input / output interface can be an input / output circuit.

[0041] In another implementation, the device is a chip, chip system, circuit, or communication module for communication equipment (such as terminal equipment or network equipment). When the device is a chip, chip system, or circuit for communication equipment, the communication unit may be an input / output interface, interface circuit, output circuit, input circuit, pin, or related circuit on the chip, chip system, or circuit; the processing unit may be at least one processor, processing circuit, or logic circuit.

[0042] Fourthly, a communication device is provided, comprising: at least one processor for executing a computer program or instructions to perform the method in any possible implementation of the first or second aspect described above. Optionally, the device further comprises a memory for storing the computer program or instructions. Optionally, the device further comprises a communication interface coupled to the processor, which can be used to input the computer program or instructions to the processor or to output information from the processor.

[0043] In one implementation, the device is a communication device (such as a terminal device or a network device).

[0044] In another implementation, the device is a chip, chip system, circuit, or communication module for communication equipment (such as terminal equipment or network equipment).

[0045] Fifthly, a processor is provided for performing the methods provided in the first or second aspect above.

[0046] Unless otherwise specified, or if it does not contradict its actual function or internal logic in the relevant description, the transmission and acquisition / reception operations involved in the processor can be understood as processor output and reception, input and other operations, or as transmission and reception operations performed by radio frequency circuits and antennas. This application does not limit them in this regard.

[0047] Optionally, the device further includes: a memory for storing a program; correspondingly, at least one processor for executing the computer program or instructions in the memory.

[0048] Optionally, the device also includes a communication interface. The communication interface is coupled to the processor and can be used to input information to the processor or output information from the processor.

[0049] In a sixth aspect, a computer-readable storage medium is provided that stores program code for execution by a device, the program code including methods for performing any possible implementation of the first or second aspect described above.

[0050] In a seventh aspect, a computer program product containing instructions is provided, which, when run on a computer, causes the computer to perform the method in any possible implementation of the first or second aspect described above.

[0051] Eighthly, a chip is provided, the chip including a processor and a communication interface, the processor reading instructions from a memory through the communication interface and executing the method provided by any of the above implementations of the first or second aspect.

[0052] Optionally, the chip is a modem chip, also known as a baseband chip, or a system-on-chip (SoC) chip containing a modem core or a system-in-package (SIP) chip.

[0053] Optionally, as one implementation, the chip also includes a memory storing computer programs or instructions, and a processor for executing the computer programs or instructions in the memory. When the computer programs or instructions are executed, the processor is used to perform the method provided by any of the above implementations of the first or second aspect.

[0054] Ninth aspect, a computer program product containing instructions is provided, which, when run on a computer, causes the computer to perform the method provided by any of the above implementations of the first aspect.

[0055] In a tenth aspect, a communication system is provided, including the aforementioned terminal equipment and network equipment. Attached Figure Description

[0056] Figure 1 is a schematic diagram of a wireless communication system applicable to an embodiment of this application.

[0057] Figure 2 is another schematic diagram of a wireless communication system applicable to an embodiment of this application.

[0058] Figure 3 is a schematic diagram of beam management applicable to embodiments of this application.

[0059] Figure 4 is a schematic diagram of a communication method 400 provided in an embodiment of this application.

[0060] Figure 5 is a schematic diagram of a communication device 500 provided in an embodiment of this application.

[0061] Figure 6 is a schematic diagram of another communication device 600 provided in an embodiment of this application.

[0062] Figure 7 is a schematic diagram of a chip system 700 provided in an embodiment of this application. Detailed Implementation

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

[0064] The technical solutions provided in this application can be applied to various communication systems, such as 5th generation (5G) or new radio (NR) systems, long term evolution (LTE) systems, LTE frequency division duplex (FDD) systems, and LTE time division duplex (TDD) systems. The technical solutions provided in this application can also be applied to future communication systems. Furthermore, the technical solutions provided in this application can be applied to device-to-device (D2D) communication, vehicle-to-everything (V2X) communication, machine-to-machine (M2M) communication, machine-type communication (MTC), and Internet of Things (IoT) communication systems. The technical solutions provided in this application can also be applied to low-frequency scenarios, high-frequency scenarios, and terahertz frequencies.

[0065] The technical solutions provided in this application can also be applied to non-terrestrial network (NTN) systems such as inter-satellite communication and satellite communication. As an example, a satellite communication system includes a satellite base station and terminal equipment. The satellite base station provides communication services to the terminal equipment. The satellite base station can also communicate with other base stations. A satellite can act as a base station or as a terminal device. Here, "satellite" can refer to unmanned aerial vehicles (UAVs), hot air balloons, low-Earth orbit (LEO) satellites, medium-Earth orbit (MEO) satellites, high-Earth orbit (HEO) satellites, etc. "Satellite" can also refer to non-terrestrial base stations or non-terrestrial equipment, etc.

[0066] In a communication system, a device can send signals to or receive signals from another device. These signals can include information, signaling, or data. The term "device" can also be replaced by an entity, network entity, network element, communication equipment, communication module, node, communication node, etc. This disclosure uses "device" as an example. For instance, a communication system can include at least one terminal device and at least one network device. The network device can send downlink signals to the terminal device, and / or the terminal device can send uplink signals to the network device.

[0067] The terminal device in this application embodiment can be a device or module that accesses the aforementioned communication system and has corresponding communication functions. The terminal device can include various devices with wireless communication capabilities, which can be used to connect people, objects, machines, etc. The terminal device can be widely applied in various scenarios, such as: cellular communication, D2D, V2X, peer-to-peer (P2P), M2M, MTC, IoT, virtual reality (VR), augmented reality (AR), industrial control, autonomous driving, telemedicine, smart grids, smart furniture, smart offices, smart wearables, smart transportation, smart cities, drones, robots, remote sensing, passive sensing, positioning, navigation and tracking, autonomous delivery, etc. The terminal device can be a terminal in any of the above scenarios, such as an MTC terminal, an IoT terminal, etc. Terminal equipment can be user equipment (UE), terminal, fixed equipment, mobile station equipment or mobile equipment, subscriber unit, handheld device, vehicle-mounted equipment, wearable device, cellular phone, smartphone, session initiation protocol (SIP) phone, wireless data card, personal digital assistant (PDA), computer, tablet computer, laptop computer, wireless modem, handset, laptop computer, computer with wireless transceiver capability, smart book, vehicle, satellite, global positioning system (GPS) device, target tracking device, aircraft (e.g., drone, helicopter, multiple helicopters, four helicopters, or airplanes), ship, remote control device, smart home device, industrial equipment, transportation vehicle with wireless communication capability, communication module, or roadside unit with terminal function, all conforming to the 3rd generation partnership project (3GPP) standard. The terminal device (RSU) can be a unit or a device built into the aforementioned equipment (e.g., a communication module, modem, or chip in the aforementioned equipment), or other processing devices connected to a wireless modem. For ease of description, the terminal device will be described below as a terminal or UE.

[0068] It should be understood that in certain scenarios, a UE can also be used as a base station. For example, a UE can act as a scheduling entity, providing sidelink signaling between UEs in scenarios such as V2X, D2D, or P2P.

[0069] In this embodiment, the device for implementing the functions of a terminal device, i.e., the terminal device, can be the terminal device itself, or it can be any device capable of supporting the terminal device in implementing the functions, such as a chip system, chip, circuit, or communication module (i.e., a communication module that performs communication functions). This device can be installed in the terminal device. In this embodiment, the chip system can be composed of chips, or it can include chips and other discrete devices. Furthermore, the device can also be configured with program instructions for performing corresponding communication functions.

[0070] The network device in this application embodiment can be a device or module with corresponding communication functions. The network device can be a device used to communicate with terminal devices; it can also be called an access network device or a wireless access network device, such as a base station. In this application embodiment, the network device can refer to a radio access network (RAN) node (or device) that connects the terminal device to the wireless network. A base station can broadly encompass, or be replaced by, various names including: NodeB, evolved NodeB (eNB), next-generation NodeB (gNB), relay station, access point, transmitting and receiving point (TRP), transmitter, master station, auxiliary station, multiple standard radio (MSR) node, home base station, network controller, access node, wireless node, access point (AP), transmission node, transceiver node, baseband unit (BBU), remote radio unit (RRU), active antenna unit (AAU), remote radio head (RRH), central unit (CU), distributed unit (DU), positioning node, etc. A base station can be a macro base station, micro base station, relay node, donor node, or similar, or a combination thereof. A base station can also refer to a communication module, modem, or chip installed within the aforementioned equipment or apparatus. A base station can also be a mobile switching center, a device that performs base station functions in D2D, V2X, and M2M communications, a network-side device in future communication systems, or another device that performs base station functions in future communication systems. A base station can support networks using the same or different access technologies. The embodiments of this application do not limit the specific technologies or device forms used in the network equipment.

[0071] Base stations can be fixed or mobile. For example, a helicopter or drone can be configured to act as a mobile base station, and one or more cells can move depending on the location of the mobile base station. In other examples, a helicopter or drone can be configured as a device to communicate with another base station.

[0072] In some deployments, the network devices mentioned in the embodiments of this application may be devices including CU, DU, or CU and DU, or devices with control plane CU nodes (central unit-control plane (CU-CP)) and user plane CU nodes (central unit-user plane (CU-UP)) and DU nodes. For example, the network devices may include gNB-CU-CP, gNB-CU-UP, and gNB-DU.

[0073] In some deployments, multiple RAN nodes collaborate to assist terminals in achieving wireless access, with different RAN nodes each implementing some of the base station's functions. For example, RAN nodes can be CUs, DUs, CU-CPs, CU-UPs, or radio units (RUs). CUs and DUs can be set up separately or included in the same network element, such as a BBU. RUs can be included in radio equipment or radio units, such as RRUs, AAUs, or RRHs.

[0074] In some deployments, the CU (Core Unit) is a logical node that carries the Radio Resource Control (RRC) layer, Service Data Adaptation Protocol (SDAP) layer, Packet Data Convergence Protocol (PDCP) layer, and other control functions of the access network equipment. The CU connects to network nodes such as the core network through interfaces, which may be E2 interfaces, etc. Optionally, the CU possesses some core network functions. The CU (e.g., the PDCP layer and higher layers) connects to the DU (e.g., the Radio Link Control (RLC) layer and lower layers) through interfaces, which may be F1 interfaces, etc. In some examples, these interfaces (e.g., the F1 interface) can provide control plane (C-Plane) and user plane (U-Plane) functions (e.g., interface management, system information management, UE context management, RRC message transmission, etc.). The F1 application protocol (F1AP) is the application protocol for the F1 interface, and in some examples, it defines the F1 signaling procedures. The F1 interface supports both the control plane (F1-C) and the user plane (F1-U).

[0075] In some deployments, the CU can be split into CU-CP and CU-UP. CU-CP is a logical node carrying the RRC layer and the control plane part of PDCP (PDCP-C) layer, used to implement the CU's control plane functions. CU-CP can interact with network elements in the core network used to implement control plane functions. These network elements in the core network can be access and mobility function network elements. CU-UP is a logical node carrying the SDAP layer and the user plane part of PDCP (PDCP-U) layer, used to implement the CU's user plane functions. CU-UP can interact with network elements in the core network used to implement user plane functions. The above CU and DU configurations are merely examples; the functions of CU and DU can be configured as needed. For example, CU or DU can be configured to have more protocol layer functions, or CU or DU can be configured to have only partial protocol layer processing functions. For example, some functions of the RLC layer and the functions of the protocol layer above the RLC layer can be placed in the CU, while the remaining functions of the RLC layer and the functions of the protocol layer below the RLC layer can be placed in the DU. Another example is that the functions of the CU or DU can be divided according to service type or other system requirements. For instance, based on latency, functions that need to meet low latency requirements can be placed in the DU, while functions that do not need to meet such latency requirements can be placed in the CU.

[0076] In some deployments, the DU (Distributed Unit) is a logical node that carries the RLC (Real-Time Control) layer, the medium access control (MAC) layer, the higher physical layer (Higher PHY) layer, and other functions. In some examples, the DU can control at least one RU (Remote Root). The DU connects to the RU through interfaces, which can be fronthaul interfaces. In some examples, the Higher PHY layer includes the PHY layer processing, such as forward error correction (FEC) encoding and decoding, scrambling, modulation, and demodulation.

[0077] In some deployments, the RU is a logical node that carries both lower physical layer (PHY) and radio frequency (RF) processing. In some examples, the RU can be a TRP, RRH, or other similar entity. In some examples, the Low-PHY includes portions of the PHY processing, such as Fast Fourier Transform (FFT), Inverse Fast Fourier Transform (IFFT), digital beamforming, and filtering. The RU communicates with one or more UEs via a radio link.

[0078] The DU and RU can be co-located or not. The DU and RU exchange control plane and user plane information via a fronthaul link through a lower-layer split-control, user, and synchronization (LLS-CUS) interface. LLS-CUS may include interfaces providing control and user plane information respectively. In some examples, the control plane refers to real-time control between the DU and RU. The DU and RU exchange management information via an LLS-M interface on the fronthaul link; the management plane (M-Plane) refers to non-real-time management operations between the DU and RU.

[0079] DU and RU can cooperate to implement the functions of the PHY layer. A DU can be connected to one or more RUs. The functions of DU and RU can be configured in various ways depending on the design. For example, a DU can be configured to implement baseband functions, and an RU can be configured to implement mid-RF functions. Another example is that a DU can be configured to implement higher-level functions in the PHY layer, and an RU can be configured to implement lower-level functions in the PHY layer, or to implement both lower-level and RF functions. Higher-level functions in the physical layer can include a portion of the physical layer's functions that are closer to the MAC layer, while lower-level functions in the physical layer can include another portion of the physical layer's functions that are closer to the mid-RF side.

[0080] In one possible design, the processing unit in the BBU used to implement baseband functions is called the baseband high (BBH) unit, and the processing unit in the RRU / AAU / RRH used to implement baseband functions is called the baseband low (BBL) unit.

[0081] 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, a radio access network can also be an open radio access network (O-RAN) architecture. In an O-RAN system, CU can also be called an open CU (open CU, O-CU), DU can also be called an open DU (open DU, O-DU), CU-CP can also be called an open CU-CP (O-CU-CP), CU-UP can also be called an open CU-UP (O-CU-UP), and RU can also be called an open RU (open RU, 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 modules and hardware modules.

[0082] In this embodiment, the device for implementing the functions of a network device can be a network device itself, or a device capable of supporting the network device in implementing those functions, such as a chip system, chip, circuit, or communication module (i.e., a communication module that performs communication functions). This device can be installed within the network device. In this embodiment, the chip system can be composed of chips, or it can include chips and other discrete devices. Furthermore, the device can be configured with program instructions for performing corresponding communication functions. This embodiment only uses a network device as an example to illustrate the device for implementing the functions of a network device, and does not limit the solution of this embodiment.

[0083] Network devices and terminal devices can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water; and they can also be deployed in the air on airplanes, balloons, and satellites. This application does not limit the scenario in which the network devices and terminal devices are located. Furthermore, terminal devices and network devices can be hardware devices, software functions running on dedicated hardware, or software functions running on general-purpose hardware, such as virtualization functions instantiated on a platform (e.g., a cloud platform), or entities that include dedicated or general-purpose hardware devices and software functions. This application does not limit the specific form of the terminal devices and network devices.

[0084] First, a brief introduction to the communication system applicable to the embodiments of this application is given below.

[0085] Referring to Figure 1, Figure 1 is a schematic diagram of a wireless communication system applicable to an embodiment of this application.

[0086] As shown in Figure 1, the wireless communication system includes a wireless access network 100. The wireless access network 100 can be a next-generation (e.g., higher version) wireless access network or a traditional (e.g., 5G, 4G, 3G, or 2G) wireless access network. One or more terminal devices (120a-120j, collectively referred to as 12) can be interconnected or connected to one or more network devices (110a, 110b, collectively referred to as 110) within the wireless access network 100. Network elements in the wireless communication system are connected via interfaces (e.g., NG, Xn) or over-the-air interfaces.

[0087] Figure 1 is just a schematic diagram. The wireless communication system may also include other devices, such as core network (CN) devices, wireless relay devices and / or wireless backhaul devices, which are not shown in Figure 1.

[0088] Referring to Figure 2, which is another schematic diagram of a wireless communication system applicable to embodiments of this application.

[0089] As shown in Figure 2, this wireless communication system may include core network equipment, access network equipment (such as RAN), and terminal equipment. Access network equipment communicates with the core network equipment via a backhaul link and with the terminal equipment via an air interface. For example, a BBU in the access network equipment communicates with the core network via a backhaul link, while a RU in the access network equipment communicates with the terminal equipment via an air interface. The BBU can communicate with the RU via a fronthaul link. The BBU and RU may or may not be co-located. In some deployments, the BBU includes at least one CU and at least one DU, and the CU and DU communicate with each other via a midhaul link.

[0090] Figure 2 is just a schematic diagram. The wireless communication system may also include other devices, which are not shown in Figure 2.

[0091] To facilitate a better understanding of the technical solution of this application, some related technologies involved in the technical solution of this application are introduced.

[0092] 1. Beam: A communication resource. Different beams can be considered different resources. The same information or different information can be transmitted through different beams.

[0093] In the NR protocol, beamforming can be represented as a spatial domain filter, spatial parameter, spatial domain setting, spatial setting, quasi-co-location (QCL) information, QCL assumption, QCL indication, etc. Beamforming can be indicated by transmission configuration indicator (TCI) state parameters or spatial relation parameters. Therefore, in this application, beamforming can be replaced by spatial domain filter, spatial filter, spatial parameter, spatial parameter, spatial setting, spatial setting, QCL information, QCL assumption, QCL indication, TCI-state, spatial relation, etc. These terms are also equivalent to each other. Beamforming can also be replaced with other beamforming terms, which are not limited in this application.

[0094] The beam used to transmit signals can be called the transmission beam (Tx beam), or it can be referred to as a spatial domain transmission filter, spatial transmission filter, spatial domain transmission parameter, spatial transmission setting, or spatial transmission setting. The downlink transmission beam can be indicated by TCI-state.

[0095] The beam used to receive signals can be called a reception beam (Rx beam), a spatial domain reception filter, a spatial reception filter, a spatial domain reception parameter, a spatial reception setting, or a spatial reception setting. The uplink transmit beam can be indicated by a spatial relation, an uplink TCI-state, or a sounding reference signal (SRS) resource (indicating the transmit beam using that SRS). Therefore, uplink beams, SRS resources, and uplink TCI-states are interchangeable.

[0096] The transmitting beam can refer to the distribution of signal strength in different directions in space after a signal is transmitted through an antenna, while the receiving beam can refer to the distribution of signal strength in different directions in space of a wireless signal received from an antenna.

[0097] Furthermore, the beam can be a wide beam, a narrow beam, or other types of beam. The beamforming technology can be beamforming technology or other technologies. Specifically, beamforming technology can be digital beamforming technology, analog beamforming technology, or hybrid digital / analog beamforming technology, etc.

[0098] As an example, multiple beams with the same or similar communication characteristics can be considered as a single beam.

[0099] Beams are generally associated with resources. For example, when performing beam measurement, network devices measure different beams through different resources. The terminal devices provide feedback on the measured resource quality, and the network devices then know the quality of the corresponding beam.

[0100] Optionally, multiple beams with the same or similar communication characteristics can be considered as a single beam. A beam may include one or more antenna ports for transmitting data channels, control channels, and detection signals, etc. One or more antenna ports forming a beam can also be considered as a set of antenna ports.

[0101] 2. Reference signal (RS): Also known as pilot, reference sequence, reference signal, etc. For consistency, it will be described as reference signal below. The reference signal can be used for channel measurement or channel estimation, etc.

[0102] The channel measurements involved in this application also include beam measurements, i.e., obtaining beam quality information by measuring a reference signal. As an example, parameters used to measure beam quality include at least one of the following: reference signal receiving power (RSRP), reference signal receiving quality (RSRQ), signal-to-noise ratio (SNR), and signal-to-interference plus noise ratio (SINR) (or simply signal-to-dryness ratio). In the embodiments of this application, for ease of explanation, unless otherwise specified, the channel measurements involved can be regarded as beam measurements.

[0103] The reference signals mentioned in this application, as examples, may include any of the following: channel state information reference signal (CSI-RS), synchronization signal block (SSB), sounding reference signal (SRS), user equipment specific reference signal (US-RS), demodulation reference signal (DMRS), phase track reference signal (PT-RS), cell reference signal (CRS), etc. It should be understood that the reference signals listed above are merely examples and should not constitute any limitation on this application. This application does not preclude the possibility of defining other reference signals in future protocols to achieve the same or similar functions.

[0104] Furthermore, the reference signal can be understood as a reference signal associated with the handover candidate cell configuration. The handover candidate cell can also be called a candidate cell or a neighboring cell. This candidate cell can be the current serving cell or a non-serving cell, and its physical cell identifier (PCI) is different from the current primary cell (PCell). Additionally, the reference signal can also be a reference signal associated with an additional PCI, i.e., the reference signal of a neighboring cell.

[0105] The terminal device can be configured with one or more candidate cells, and the configuration of each candidate cell may include the configuration of reference signal resources.

[0106] 3. Reference signal resources: can be used to configure the transmission attributes of reference signals.

[0107] Generally, reference signals are configured in the form of resources. Network devices can configure various reference signals to terminal devices in the form of resources. Each resource is a configuration information unit, which typically includes parameters related to a reference signal, such as the time-frequency resource location, number of ports, time domain type (periodic / semi-static / aperiodic), etc. Transmitting devices can send reference signals based on reference signal resources, and receiving devices can receive reference signals based on reference signal resources.

[0108] To distinguish different reference signal resources, each reference signal resource can correspond to a reference signal resource identifier, such as CSI-RS resource indicator (CRI), SSB resource indicator (SSBRI), or SRS resource indicator (SRI).

[0109] In the embodiments of this application, the reference signal resource identifier is mentioned several times. It can be understood that the reference signal resource identifier can be replaced by: reference signal resource indicator, reference signal resource marker, or reference signal resource index, and there is no limitation thereto. For the sake of consistency, the reference signal resource identifier is mainly used as an example for explanation.

[0110] 4. TCI-state: Network devices can generate different beams pointing in different transmission directions. During downlink data transmission, when a network device uses a specific beam to send data to a terminal device, it needs to inform the terminal device of the transmitted beam information. This allows the terminal device to use the corresponding received beam to receive the data sent by the network device. One possible approach is for the network device to indicate the transmitted beam information to the terminal device through the Transmission Configuration Indication (TCI) field in the downlink control information (DCI). The TCI can also be replaced with a transmission configuration indicator or transmission configuration identifier, etc., and is not limited to this.

[0111] For example, the TCI field is 3 bits in size and can represent 8 different field values ​​(codepoints). Each value in the TCI field corresponds to a TCI-state index (tci-StateId), which uniquely identifies a TCI-state. A TCI-state includes several parameters that determine information related to the transmitted beam. As an example, each TCI-state includes its own index (tci-StateId) and two QCL information (QCL-Info) entries. Each QCL-Info includes a cell field and a bandwidth part (BWP) identifier (identifier / indication / identity / identification, ID), indicating which BWP in which cell the TCI-state applies to; that is, different cells or different BWPs in the same cell can be configured with different QCL-Infos. The QCL-Info may also include a reference signal (RS) to indicate which reference signal resource constitutes the QCL relationship. In data transmission and channel measurements, beams can be mapped to reference signal resources, such as one beam corresponding to one reference signal resource. Therefore, which reference signal resource constitutes the QCL relationship can also refer to which beam it forms the QCL relationship with. It can be understood that "ID" can be an abbreviation for any of the following: identifier, indication, indicator, index, identity, or identification. These terms can be used interchangeably, and will not be elaborated further below.

[0112] QCL relationship refers to two reference signal resources (or two antenna ports, with a one-to-one correspondence between antenna ports and reference signal resources) having certain identical spatial parameters. Which specific spatial parameters are identical depends on the type of the QCL-Info, specifically another field of the QCL-Info: QCL type (qcl-Type). qcl-Type can have four values: {type A, type B, type C, type D}. For example, type D indicates that the two reference signal resources have the same spatial reception parameter information, meaning the two beams have the same receiving beam. One of the two QCL-Info entries included in the TCI-state may be type D.

[0113] The following example illustrates how a network device uses TCI-state to indicate the receive beam information of the data transmission beam to a terminal device, including the configuration, activation, and indication of TCI-state.

[0114] TCI-state configuration: Network devices configure multiple TCI-states to terminal devices via RRC signaling. Each of these TCI-states includes a QCL-Info of type type D. Network devices can also configure TCI-states that do not include a QCL-Info of type type D; this is not a limitation.

[0115] TCI-state activation: After configuring multiple TCI-states on a network device, eight of them need to be activated via a MAC control element (CE) (MAC CE / MAC-CE). These eight TCI-states correspond one-to-one with the eight values ​​of the TCI field in the DCI. That is, which eight TCI-states correspond to the eight values ​​of the DCI's TCI field is determined by MAC CE signaling. The specific format of the MAC CE signaling can be found in the protocol; it is not limited here.

[0116] TCI-state indication: Network devices indicate a specific TCI-state through the TCI field in the DCI. For example, if the TCI field value in the DCI sent by the network device to the terminal device is 000, it indicates that the data transmission beam uses the TCI-state corresponding to 000. The reference signal contained in the QCL-Info of type D within this TCI-state is the reference signal with index #1 (such as CSI-RS), indicating that the beam used for data transmission is the same as the receiving beam corresponding to CSI-RS with index #1. The receiving beam corresponding to CSI-RS with index #1 can be determined through beam measurement procedures and is known to the terminal device. Therefore, through the specific value of the TCI field, the terminal device can determine the receiving beam corresponding to the data transmission beam and thus use the corresponding receiving beam to receive data.

[0117] 5. Unified TCI: This is a unified beam indication framework. Network devices can indicate a beam for terminal devices, which can be used simultaneously for multiple channels and / or reference signals. The common beam can be an uplink common beam, a downlink common beam, or an uplink-downlink common beam, which the terminal device can use in subsequent transmissions. That is, the network device can indicate an uplink common beam for the transmission of multiple uplink channels and / or uplink reference signals. It can also indicate a downlink common beam for the transmission of multiple downlink channels and / or downlink reference signals. Alternatively, it can indicate an uplink-downlink common beam for the transmission of multiple uplink channels and / or uplink reference signals, as well as multiple downlink channels and / or downlink reference signals. In other words, the uplink-downlink common beam can be used for both uplink and downlink transmissions.

[0118] As an example, the terminal device can be configured with two TCI states, referred to as downlink (DL) or joint TCI (DLorjointTCI) and uplink (UL) TCI (UL TCI).

[0119] For example, the terminal device can be configured with both joint / DL TCI-state (up to 128) and uplink TCI-state (ULTCI-state) (up to 64).

[0120] For example, in the serving cell configuration of RRC signaling, the network device can configure the TCI mode currently used by the UE as joint mode or separate mode. In joint mode, it indicates that a joint TCI-state can be used for uplink and downlink transmission simultaneously; in separate mode, the network device indicates that the DL TCI-state and UL TCI-state are used for uplink and downlink transmission respectively.

[0121] When the terminal device receives the TCI-state activation signaling indicated by MAC CE, which includes the TCI-state ID, the terminal device determines which TCI is activated by MAC CE according to the RRC configuration.

[0122] 6. PUCCH: Used to transmit uplink control information (UCI) to support uplink and downlink data transmission. UCI can also be transmitted on the physical uplink shared channel (PUSCH).

[0123] As an example, the UCI carried by PUCCH includes at least one of the following: scheduling request (SR), hybrid automatic repeat request (HARQ)-acknowledgement (ACK) (HARQ-ACK) information, and CSI.

[0124] The scheduling request can be used for uplink resource requests.

[0125] HARQ-ACK information, also known as HARQ information, represents feedback information on data (such as data on the physical downlink shared channel, PDSCH), such as acknowledgment (ACK) or negative acknowledgment (NACK).

[0126] CSI can include at least one of the following: channel quality indicator (CQI), precoding matrix indicator (PMI), rank indicator (RI), CSI-RS resource indicator (CRI), layer indicator (LI), RSRP, or SINR, etc. The signal-to-interference-plus-noise ratio (SNR) can also be called the signal-to-interference-plus-noise ratio (SINR).

[0127] As examples, PUCCH formats include the following: PUCCH format 0, PUCCH format 1, PUCCH format 2, PUCCH format 3, and PUCCH format 4. PUCCH format 0 and PUCCH format 1 can also be called short PUCCHs, occupying 1-2 time domain units (e.g., symbols); PUCCH format 2, PUCCH format 3, and PUCCH format 4 can also be called long PUCCHs, occupying 4-14 time domain units (e.g., symbols).

[0128] 7. Beam management: This includes, for example, beam measurement, such as measurements based on reference signals, to determine the best quality beam.

[0129] 5G can utilize high-frequency communication, specifically ultra-high-frequency signals, to transmit data. A major problem with high-frequency communication is the sharp decrease in signal energy with transmission distance, resulting in short transmission ranges. To overcome this, high-frequency communication employs analog beamforming technology. By weighting the antenna array, the signal energy is concentrated within a small angular range, forming a beam-like signal (called an analog beam, or simply a beam), thereby increasing the transmission distance. Both network devices and terminal devices use beamforming for transmission. Specifically, network devices and terminal devices use specific beams for uplink and downlink data transmission. Currently, beam management first performs coarse beam alignment based on SSB (Special Signal Stratos), followed by fine beam adjustment based on CSI-RS (Combined Signal Stratosing). The possible beam management process is illustrated below with reference to Figure 3.

[0130] Referring to Figure 3, Figure 3 is a schematic diagram of beam management applicable to embodiments of this application.

[0131] As an example, the overall process of beam management can be divided into the following three stages.

[0132] Phase 1: Coarse beam alignment of network equipment and terminal equipment, as shown in Figure 3(a).

[0133] Specifically, network devices perform beam scanning based on SSB (Service Signal Broadcast) signals, meaning that network devices transmit beams in different directions at different times to achieve broadcast beam coverage of the cell. Simultaneously, terminal devices scan and receive beams, meaning that terminal devices also receive signals using different beams at different times. The terminal devices determine the network device beam and terminal device beam with the best quality (e.g., the optimal network device beam and terminal device beam) based on the received signal strength.

[0134] Phase 2: Network equipment beam fine-tuning, as shown in Figure 3(b).

[0135] Specifically, the network device determines candidate beams based on the high-quality network device beams obtained in Phase 1, scans them using CSI-RS, and the terminal device receives the signals using the receiving beams selected in Phase 1, thereby fine-tuning the network device beams and determining the network device beams (such as the optimal network device beams).

[0136] Phase 3: Beam fine-tuning of terminal equipment, as shown in Figure 3(c).

[0137] Specifically, the network device uses the beam obtained in Phase 2 to transmit CSI-RS, while the terminal device scans the beam to determine the terminal device beam (such as the optimal terminal device beam) and completes beam alignment. The process is similar to Phase 2.

[0138] The stages 1, 2, and 3 described herein are merely illustrative examples, and the embodiments of this application are not limited thereto. In implementation, a system does not necessarily need to implement all of the above processes; for example, it may only implement stages 1 and 2, leaving the determination of the received beam on the terminal device side to the terminal device itself.

[0139] 8. Measurement Result Reporting: Currently, based on the time-domain configuration behavior, network devices can be configured to perform three measurement result reporting processes (also known as beam reporting, beam measurement result reporting, or CSI reporting): periodic reporting, semi-persistent reporting, and aperiodic reporting. A brief introduction follows.

[0140] 1) Periodic Reporting: First, the network device is configured to perform periodic reference signal measurements. This means the network device periodically sends measurement reference signals to the terminal device, which then measures these reference signals and periodically reports the measurement results. After the configuration signaling takes effect, the terminal device periodically reports measurement reports. To terminate the measurement reporting process, an RRC signaling message can be sent to release the relevant configuration parameters for that process.

[0141] 2) Semi-persistent reporting: One type involves periodic reference signal measurement and semi-persistent measurement result reporting. First, the network device can be configured with periodic reference signals, meaning it periodically sends measurement reference signals to the terminal device. The terminal device measures these reference signals. When the terminal device receives an activation signaling message from the network device (such as MAC CE or DCI signaling), it will continuously and periodically report the measurement results. Of course, the network device can also send a deactivation signaling message to the terminal device to deactivate the semi-persistent reporting process. The other type involves semi-persistent reference signal measurement and measurement result reporting. When the terminal device receives an activation signaling message from the network device (such as MAC CE or DCI signaling), it will continuously and periodically measure the reference signals and report the measurement results. When the terminal device receives a deactivation signaling message from the network device, it stops the continuous reporting.

[0142] 3) Non-periodic reporting: This reporting is only executed after the terminal device receives a trigger signaling from the network device. Furthermore, after completing the reporting, the terminal device will stop reporting, making it a one-time reporting process.

[0143] The aforementioned measurement result reporting is either periodic or semi-persistent or aperiodic, triggered by instruction signaling from network devices; that is, the timing of reporting is determined by the network devices. This approach results in significant uplink resource overhead. Specifically, in periodic and semi-persistent measurement reporting, the terminal device needs to report measurement results every other period, and these results may be meaningless to the network devices. For example, the current measurement result may be no different from the previously reported result (e.g., the optimal beam has not changed), making such reporting meaningless and wasting uplink resources.

[0144] Based on this, beam reporting triggered by terminal devices or events is introduced. Specifically, terminal devices can report based on events, and different events may trigger different reporting content. In view of this, this application proposes that terminal devices can indicate relevant information about events to network devices, so that network devices know what event triggered the reporting, and thus know the content to be reported by the terminal device and / or effectively allocate resources.

[0145] Before introducing the scheme of this application, the following points should be noted.

[0146] (1) In this application, “instruction” may include direct instruction, indirect instruction, explicit instruction, and implicit instruction. When describing a certain instruction information for the purpose of instructing A, it can be understood that the instruction information carries A, directly instructs A, or indirectly instructs A.

[0147] In this application, the information indicated by the instruction information is called the information to be instructed. In specific implementations, there are many ways to indicate the information to be instructed, such as, but not limited to, directly indicating the information to be instructed, such as the information to be instructed itself or its index. It can also indirectly indicate the information to be instructed by indicating other information, where there is a relationship between the other information and the information to be instructed. It can also indicate only a part of the information to be instructed, while the other parts are known or pre-agreed upon. For example, the instruction of specific information can be achieved by using a pre-agreed (e.g., protocol-defined) arrangement of various pieces of information, thereby reducing instruction overhead to some extent. Furthermore, the information to be instructed can be sent as a whole or divided into multiple sub-information pieces, and the sending period and / or timing of these sub-information pieces can be the same or different.

[0148] (2) In this application, "send" and "receive" indicate the direction of signal transmission. For example, "send information to XX" can be understood as the destination of the information being XX, which may include direct transmission via the air interface or indirect transmission via the air interface by other units or modules. "Receive information from YY" can be understood as the source of the information being YY, which may include direct reception from YY via the air interface or indirect reception from YY via the air interface by other units or modules. "Send" can also be understood as the "output" of the chip interface, and "receive" can also be understood as the "input" of the chip interface. In other words, sending and receiving can occur between devices, such as between network devices and terminal devices, or within a device, such as between components, modules, chips, software modules, or hardware modules within the device via a bus, wiring, or interface.

[0149] (3) In the various embodiments of this application, unless otherwise specified or logically conflicting, the terms and / or descriptions of different embodiments are consistent and can be referenced by each other. The technical features of different embodiments can be combined to form new embodiments according to their inherent logical relationship.

[0150] (4) In this application, "first" and "second" are used for descriptive convenience only to distinguish objects and are not intended to limit the scope of the embodiments of this application. They are not used to describe the order or sequence of features. It should be understood that the objects described in this way can be interchanged where appropriate so as to describe solutions other than those in the embodiments of this application.

[0151] (5) In this application, “predefined” may mean a standard protocol predefined, or it may mean that the devices have agreed or negotiated in advance.

[0152] (6) In this application, the words “exemplary,” “for example,” etc., are used to indicate examples, illustrations, or descriptions. Any embodiment or design described as an “example” in this application should not be construed as being more preferred or advantageous than other embodiments or designs. Specifically, the use of the word “example” is intended to present the concept in a concrete manner. In the embodiments of this application, “of,” “corresponding, relevant,” and “corresponding” may sometimes be used interchangeably, and it should be noted that their intended meanings are consistent unless their distinction is emphasized.

[0153] The method provided by the embodiments of this application will be described in detail below with reference to the accompanying drawings. The embodiments provided by this application can be applied to the communication system shown in FIG1 above, and are not limited thereto.

[0154] In the following embodiments, terminal devices and network devices are used as examples for illustrative purposes. The term "terminal device" can be replaced by a component of a terminal device (e.g., a chip, chip system, or circuit), and the term "network device" can be replaced by a component of a network device (e.g., a chip, chip system, or circuit).

[0155] Referring to Figure 4, which is a schematic diagram of a communication method 400 provided in an embodiment of this application, the method 400 shown in Figure 4 may include the following steps.

[0156] Optionally, method 400 includes steps 410 and 420.

[0157] 410. The terminal device sends the second instruction information. Correspondingly, the network device receives the second instruction information.

[0158] The second indication information indicates the event information supported by the terminal device. This second indication information can also be referred to as terminal capability information.

[0159] In this context, an event refers to an event related to a UE-initiated report, a measurement report initiated by the terminal device, a report (or measurement report) submitted after the terminal device performs active measurement, or a specific condition related to a measurement report submitted by the terminal device. For example, the terminal device may actively perform measurements (such as beam measurements or channel measurements) to obtain a measurement report related to the event. Another example is that the terminal device may perform measurements based on reference signals according to the configuration of reference signal resources to obtain a measurement report related to the event. Yet another example is that the terminal device actively performs measurements and submits a measurement report related to the event when specific conditions are met. The event may also be referred to as any of the following: trigger event, layer 1 (L1) trigger event, CSI measurement report trigger event, beam measurement report trigger event, L1 CSI report trigger event, L1 beam measurement report trigger event, etc. The naming of these events is not limited in this embodiment.

[0160] In addition, as an example, an event-related report may be referred to as any of the following: an event-triggered or terminal device-initiated report, an event-triggered or terminal device-initiated beam report, an event-triggered or terminal device-initiated CSI report, an event-triggered or terminal device-initiated beam measurement result report, an event-triggered or terminal device-initiated interference measurement report, interference measurement report, CSI report, beam measurement result report, etc.

[0161] Optionally, the second indication information indicates at least one of the following: whether the terminal device supports the ability to trigger event reporting, and the events supported by the terminal device.

[0162] Example 1: The second indication information indicates whether the terminal device supports the ability to report events.

[0163] Event-triggered reporting can include event-triggered beam reporting, channel state information (CSI) reporting, beam measurement result reporting, interference measurement reporting, etc., and is not limited to any particular type. As an example, event-triggered reporting can also be called a UE-initiated report.

[0164] One possible implementation is that whether a terminal device supports event-triggered reporting is indicated by at least one bit. For example, suppose one bit is used to indicate whether the terminal device supports event-triggered reporting. If this bit is set to "0", it means that the terminal device supports event-triggered reporting; if this bit is set to "1", it means that the terminal device does not support event-triggered reporting. It should be understood that the above is merely an illustrative example and is not intended to be limiting.

[0165] Another possible implementation is to indicate whether the terminal device supports event-triggered reporting by reporting whether it does so. For example, if the terminal device does not report that it does not support event-triggered reporting, it can be assumed that the terminal device supports event-triggered reporting. Or, for example, if the terminal device does not report that it supports event-triggered reporting, it can be assumed that the terminal device does not support event-triggered reporting.

[0166] The above is an illustrative example, and the embodiments of this application are not limited thereto. For example, whether a terminal device supports the ability to trigger event reporting can also be indicated by a specific field. If the second indication information includes the specific field, it indicates that the terminal device supports the ability to trigger event reporting; if the second indication information does not include the specific field, it indicates that the terminal device does not support the ability to trigger event reporting.

[0167] Example 2: The second indication information indicates the events supported by the terminal device.

[0168] For example, the second indication information includes an index of the various events supported by the terminal device.

[0169] For example, the second instruction information includes indexes to various event tables supported by the terminal device, where each event table includes one or more events.

[0170] For example, the second indication may include the number of events supported by the terminal device.

[0171] The above is an illustrative example, and the embodiments of this application are not limited thereto. The terminal device can indicate various information related to events supported by the terminal device to the network device.

[0172] 420, The terminal device receives the configuration information. Correspondingly, the network device sends the configuration information.

[0173] This configuration information includes information on X events, where X is an integer greater than 0.

[0174] Regarding the X events, there are three possible scenarios.

[0175] In the first possible scenario, the X events are determined based on the second indication information. In other words, the X events are events supported by the terminal device, or events indicated by the terminal device through the second indication information. In this case, method 400 may not include step 420, meaning the network device may not need to indicate the information of the X events to the terminal device.

[0176] In the second possible scenario, the X events are configured by the network device, meaning the network device itself configures (or selects) X events. In this case, the terminal device can be assumed to support all events or support these X events. In this scenario, method 400 may not include step 410, meaning the terminal device does not need to indicate the event information it supports to the network device.

[0177] In a third possible scenario, the X events are determined based on the second indication information and the events configured by the network device. For example, the network device is configured with at least one event, and the terminal device supports at least one event; the X events are determined by combining the at least one event configured by the network device and the at least one event supported by the terminal device.

[0178] The three possible scenarios described above are illustrative examples, and the embodiments of this application are not limited to these. For brevity, each scenario will be described using X events.

[0179] Optionally, the configuration information indicates the indices of X events. The terminal device can learn about these X events based on the configuration information.

[0180] For example, the configuration information includes the index of each event in X events.

[0181] For example, the configuration information may include one or more event tables (or indexes to one or more event tables), and each event table may contain one or more events. Thus, based on the indexes of the event tables included in the configuration information, the events contained in those event tables can be determined.

[0182] For example, the configuration information includes the value of X.

[0183] Further optionally, method 400 further includes: the network device sending an activation signaling message to the terminal device to activate some or all of the configured events (i.e., X events).

[0184] Further optionally, method 400 further includes: the network device sending a deactivation signaling message to the terminal device to deactivate some or all of the configured events (i.e., X events).

[0185] Optionally, the X events include at least one of the following: the first beam quality is lower than or equal to a first preset threshold, the second beam quality is higher than or equal to a second preset threshold, the second beam quality is higher than or equal to a third preset threshold of the first beam quality, and the difference between the second beam quality and the first beam quality is less than or equal to a fourth preset threshold.

[0186] In this design, the first beam represents the serving beam, i.e., the current serving beam; the second beam represents a beam different from the serving beam, such as the beams of candidate cells / neighboring cells. The first beam may include one or more beams, and the second beam may also include one or more beams. The number of currently serving beams can be determined based on the number of UL / DL / joint TCI-states indicated by the network device, such as the UL / DL / joint TCI-states indicated by DCI signaling; or the number of beams included in the currently serving beam can be predefined or pre-configured by the network device. The number of beams included in the second beam, or the maximum number of beams included in the second beam, can be predefined or configured by the network device.

[0187] For example, the current serving beam is a reference signal with QCL type type D in the currently indicated TCI-state; or, the current serving beam is a reference signal with QCL type type D in the UL TCI-state applied to the current uplink transmission (PUSCH / PUCCH / SRS); or, the current serving beam is a reference signal with QCL type type D in the downlink or joint TCI-state (DLorjointTCI-state) applied to the current downlink transmission (PDCCH / PDSCH / CSI-RS). As an example, the reference signal could be SSB, CSI-RS, or SRS, etc.

[0188] Among them, beam quality can be characterized by at least one of the following: reference signal receiving power (RSRP) and signal to interference plus noise ratio (SINR).

[0189] Each preset threshold, such as the first, second, third, and fourth preset thresholds, can be predefined, configured, indicated, or determined by the terminal device; there are no restrictions on this. The preset thresholds can be the same or different. Two preset thresholds can be correlated, meaning that a related preset threshold can be derived from one preset threshold, or they can be uncorrelated. The unit for each preset threshold can be decibels (dB), decibel-milliwatts (dBm), etc.

[0190] The events listed above are described below.

[0191] Example 1: The quality of the first beam is lower than or equal to a first preset threshold.

[0192] To distinguish it, this event is referred to as event #1. In other words, event #1 indicates that the current service beam quality is less than or equal to a certain threshold, such as the first preset threshold.

[0193] Example 2: The quality of the second beam is higher than or equal to the second preset threshold.

[0194] To distinguish it, this event is referred to as event #2. In other words, event #2 indicates that there exists at least one new beam (i.e., the second beam) whose beam quality is higher than or equal to a threshold, such as a second preset threshold.

[0195] As an example, the new beam can be a reference signal with QCL type type D in the active TCI-states (except for the indicated TCI-state), or it can be one of the reference signals configured by the network device (such as the reference signal configured by the network device for measurement, or the reference signal configured by the network device for the terminal device to monitor the occurrence of an event or event #2) (except for the reference signal corresponding to the current serving beam).

[0196] Example 3: The quality of the second beam is higher than or equal to the quality of the first beam by a third preset threshold.

[0197] To distinguish it, this event is referred to as event #3. In other words, event #3 indicates that there is at least one new beam with a beam quality higher than that of the currently serving beam, and the difference between the beam quality of the new beam and the beam quality of the currently serving beam is greater than or equal to a threshold, such as a third preset threshold.

[0198] Event #3 can also be described as: the quality of the first beam is lower than or equal to the quality of the second beam by a threshold, where the threshold can be a value less than 0 dB. Alternatively, "the quality of the first beam is lower than or equal to the quality of the second beam by a threshold" can also be considered as an event different from event #3, and is not limited thereto.

[0199] Example 4: The difference between the quality of the second beam and the quality of the first beam is less than or equal to the fourth preset threshold.

[0200] To distinguish it, this event is referred to as event #4. In other words, event #4 indicates that the difference between the beam quality of at least one new beam and the beam quality of the currently serving beam is less than or equal to a threshold, or event #4 indicates that the absolute value of the difference between the beam quality of at least one new beam and the beam quality of the currently serving beam is less than or equal to a threshold, such as the fourth preset threshold.

[0201] It is understood that the above is an illustrative example, and the embodiments of this application are not limited thereto. The X events may also include other events. A few more examples are listed below.

[0202] Example 5: The beam quality of the first beam is lower than or equal to a fifth preset threshold, and the beam quality of the second beam is higher than or equal to a sixth preset threshold. The sixth preset threshold is greater than or equal to the fifth preset threshold.

[0203] To distinguish them, this event is referred to as event #5. In other words, event #5 indicates that there is at least one new beam with a beam quality higher than a certain threshold, and the beam quality of the currently serving beam is lower than or equal to a threshold.

[0204] Example 6: The beam quality of the first beam is lower than or equal to the beam quality of the preset beam, which is the seventh preset threshold.

[0205] For distinction, this event will be referred to as event #6. For example, the current serving beam is the CSI-RS with QCL type type D in the currently indicated TCI-state, and the preset beam is the reference signal (such as SSB) of the CSI-RS that satisfies QCL type type D. The quality of the CSI-RS is lower than or equal to the quality of the reference signal (such as SSB) by a threshold (i.e., the seventh preset threshold). At this time, the seventh preset threshold can be a value less than 0 dB.

[0206] Event #6 can also be described as follows: The beam quality of the preset beam is higher than or equal to the beam quality of the first beam by a threshold, which can be a value greater than 0 dB.

[0207] It is understandable that in the above examples, the situation regarding "equal to" can be a situation where the event has occurred, or a situation where the event has not occurred, or other uses, and there are no limitations on this.

[0208] Taking event #1 as an example, the occurrence of event #1 indicates that the following situation has occurred: the quality of the first beam is lower than the first preset threshold, or the quality of the first beam is equal to the first preset threshold. For example, if the terminal device determines through measurement that the quality of the first beam is lower than or equal to the first preset threshold, then event #1 is determined to have occurred. As another example, if the terminal device determines through measurement that the quality of the second beam is higher than or equal to the second preset threshold, then event #2 is determined to have occurred. The occurrence of an event triggers a report, that is, it triggers the reporting of the measurement report corresponding to that event.

[0209] 430, the terminal device sends a first indication message, which indicates at least one of the following: whether an event has occurred among the X events, and information about the events that have occurred among the X events.

[0210] Accordingly, the network device receives the first instruction information.

[0211] The question of whether any of the X events occurred can also be replaced with whether at least one event occurred.

[0212] The information about the events that occurred among the X events, also referred to simply as event information, represents information related to the events that occurred. As an example, the event information among the X events includes at least one of the following: the index of the event that occurred among the X events, the number of events that occurred among the X events, and the content of the events that occurred among the X events. The number of events that occurred among the X events can be an integer greater than 0.

[0213] Optionally, the first indication information is carried in at least one of the following: PUCCH format 0, PUCCH format 1, PUCCH format 2, PUCCH format 3, PUCCH format 4, PUSCH.

[0214] The following describes several ways to implement the first instruction message.

[0215] Method #1, the first indication information is a sequence, and the cyclic shift value of the sequence indicates at least one of the following: whether an event has occurred among X events, and information about the events that have occurred among X events.

[0216] As an example, the sequence is a complex sequence, such as the ZC(zadoff-chu) sequence. Without loss of generality, sequences will be used to describe the sequence from now on.

[0217] Further optionally, based on this method, the first indication information can be carried in PUCCH format 0, that is, the terminal device sends a sequence through PUCCH format 0 (or on PUCCH format 0 resources), and the cyclic shift value of the sequence can indicate at least one of the following: whether an event has occurred among X events, and information about the events that have occurred among X events.

[0218] One possible implementation is that the terminal device can send multiple different cyclic shift sequences on the PUCCH format 0 resource to represent the occurrence of multiple different events.

[0219] Another possible implementation is that the terminal device sends a sequence (or a cyclic shift value of the sent sequence) on the PUCCH format 0 resource to indicate whether an event has occurred or not.

[0220] Another possible implementation is that the terminal device sends a cyclically shifted sequence of a certain value on the PUCCH format 0 resource, indicating that the event corresponding to the cyclically shifted value has occurred.

[0221] Regarding PUCCH format 0 resources, there are two possible scenarios.

[0222] Scenario 1: The PUCCH format 0 resource is dedicated to reporting event information, or the PUCCH format 0 resource is dedicated to scheduling request resources for reporting event information.

[0223] In scenario 2, the PUCCH format 0 resource is a regular scheduling request resource, meaning that the PUCCH format 0 resource is not dedicated to reporting event information.

[0224] The following section will introduce some implementation methods for method #1, taking into account the two scenarios mentioned above.

[0225] In scenario 1, the PUCCH format 0 resource is dedicated to reporting event information.

[0226] One possible implementation is that a cyclic shift value of the sequence indicates an event has occurred when it is the first value, and an cyclic shift value indicates no event has occurred when it is the second value. The first and second values ​​are different; for example, either the first or second value can be 0. Another example is that the actual cyclic shift value of the transmitted sequence is "the first or second value + the initial cyclic shift value (initialCyclicShift)". Here, initialCyclicShift can be predefined or configured by the network device, such as being indicated to the terminal device via RRC.

[0227] For example, assuming X=1, if the terminal device sends a sequence with a cyclic shift value of the first value in PUCCH format 0 resource, it indicates that the event has occurred; if the terminal device sends a sequence with a cyclic shift value of the second value in PUCCH format 0 resource, it indicates that the event has not occurred.

[0228] For another example, assuming X is greater than 1, if the terminal device sends a sequence with a cyclic shift value of the first value in PUCCH format 0 resource, it indicates that at least one event has occurred; if the terminal device sends a sequence with a cyclic shift value of the second value in PUCCH format 0 resource, it indicates that no event has occurred.

[0229] The second possible implementation is that when a signal (such as a sequence) is sent on the PUCCH format 0 resource, it indicates that an event has occurred; when no signal (such as a sequence) is sent on the PUCCH format 0 resource, it indicates that no event has occurred.

[0230] For example, assuming X=1, if the terminal device sends a signal on the PUCCH format 0 resource, such as sending a sequence with a cyclic shift value of the first value, it indicates that an event has occurred; if the terminal device does not send a signal on the PUCCH format 0 resource, it indicates that the event has not occurred.

[0231] For another example, assuming X is greater than 1, if the terminal device sends a signal on the PUCCH format 0 resource, such as sending a sequence with a cyclic shift value of the first value, it indicates that at least one event has occurred; if the terminal device does not send a signal on the PUCCH format 0 resource, it indicates that no event has occurred.

[0232] The third possible implementation is that different cyclic shift values ​​of the sequence correspond to different events. When the cyclic shift value of the sequence is a certain value, it means that the event corresponding to that value has occurred.

[0233] Based on this implementation, as an example, the sequence has Q cyclic shift values, where X of these Q cyclic shift values ​​correspond to X events. Q is an integer greater than 0. For example, Q equals X. Another example is that Q is greater than X.

[0234] For example, X cyclic shift values ​​are: 0, ..., Q*n / X, representing the occurrence of event 1, event 2, ..., event X, respectively. Here, n is a positive integer from 0 to X-1. If Q*n / X is not an integer, it can be rounded up or down. As an example, the correspondence between the cyclic shift values ​​of the sequence and the events can exist in the form of a table, function, text, or string, such as storage or transmission. Taking a table as an example, the correspondence between the cyclic shift values ​​of the sequence and the events can be shown in Table 1.

[0235] Table 1

[0236] Taking Table 1 as an example, for instance, if X = 1, then the cyclic shift value of the sequence is related to 0 or calculated based on 0 and initialCyclicShift, indicating that event 1 has occurred; if the cyclic shift value of the sequence is not related to 0 or calculated based on 0 and initialCyclicShift, it indicates that event 1 has not occurred. For example, if X = 6, then the cyclic shift value of the sequence is related to 0, or calculated based on 0 and initialCyclicShift, indicating that event 1 has occurred; the cyclic shift value is related to 2, or calculated based on 2 and initialCyclicShift, indicating that event 2 has occurred; the cyclic shift value is related to 4, or calculated based on 4 and initialCyclicShift, indicating that event 3 has occurred; the cyclic shift value is related to 6, or calculated based on 6 and initialCyclicShift, indicating that event 4 has occurred; the cyclic shift value is related to 8, or calculated based on 8 and initialCyclicShift, indicating that event 5 has occurred; and the cyclic shift value is related to 10, or calculated based on 10 and initialCyclicShift, indicating that event 6 has occurred.

[0237] It's understandable that in actual communication, the cyclic shift value of a sequence can be increased by `initialCyclicShift`. Taking X=2 as an example, if the cyclic shift value is "0 + initialCyclicShift", it indicates that event 1 has occurred; if the cyclic shift value is "6 + initialCyclicShift", it indicates that event 2 has occurred. Therefore, the values ​​corresponding to each event in Table 1 above can also be updated to the sum of that value and `initialCyclicShift`.

[0238] Table 1 above is for illustrative purposes only and is not intended to limit the scope of events. For example, Table 1 may include a greater number of events. Furthermore, the correspondence between events and cyclic shift values ​​in Table 1 may be other correspondences. Additionally, events 1-6 mentioned in Table 1 may be events #1-#6 listed in step 420 above, such as event 1 being one of events #1-#6; or they may be other events, without limitation.

[0239] The embodiments of this application do not limit the values ​​of the X cyclic shift values. For example, the range of cyclic shift values, such as 0 to 11, can be predefined.

[0240] Alternatively, if no event occurs, the terminal device does not send a signal on the PUCCH format 0 resource. If the network device does not receive a signal on the PUCCH format 0 resource, it assumes that no event has occurred.

[0241] The fourth possible implementation is that different cyclic shift values ​​of the sequence correspond to different event tables. When the cyclic shift value of the sequence is a certain value, it means that the event in the event table corresponding to that value has occurred.

[0242] This approach is similar to the third possible approach, except that in the third possible implementation, one circular shift value corresponds to one event, while in the fourth possible implementation, one circular shift value corresponds to one event table.

[0243] The above-mentioned possible implementation methods are illustrative examples, and the embodiments of this application are not limited thereto.

[0244] Scenario 2: PUCCH format 0 resource is a normal scheduling request resource.

[0245] This situation can be referred to as the first, third, and fourth possible scenarios in scenario 1 above, which will not be elaborated here.

[0246] In this case 2, as an example, the cyclic shift value of the sequence can satisfy any one or more of the following conditions:

[0247] 1) The cyclic shift value is not 0. Optionally, there is no HARQ-ACK information on this PUCCH format 0 resource.

[0248] 2) The cyclic shift value is not 0, 3, 6, or 9. Optionally, 1 bit of HARQ-ACK information is multiplexed on this PUCCH format 0 resource.

[0249] 3) The cyclic shift value is not 0, 1, 3, 4, 6, 7, 9, 10. Optionally, 2 bits of HARQ-ACK information are multiplexed on this PUCCH format 0 resource.

[0250] The above describes how event information can be indicated by the cyclic shift value of a sequence, using two different scenarios.

[0251] Optionally, the cyclic shift value of the sequence can jointly indicate event information and HARQ-ACK. Specifically, as mentioned above, the PUCCH can also carry HARQ-ACK information; therefore, the cyclic shift value of the sequence can jointly indicate event information and HARQ-ACK information. As an example, the cyclic shift value of the sequence jointly indicating event information and HARQ-ACK can be applied to Case 1 above.

[0252] The HARQ-ACK message may occupy 1 bit, 2 bits, or other bits; there is no limitation on this. The following section will describe the two scenarios where the HARQ-ACK message occupies 1 bit and 2 bits.

[0253] In scenario 1, the HARQ-ACK information occupies 1 bit.

[0254] One possible implementation is that the cyclic shift value of the sequence indicates any of the following: an event occurs, an event occurs and the HARQ-ACK value is A1, or an event occurs and the HARQ-ACK value is A2. For example, A1 = 1, A2 = 0; or A1 = 0, A2 = 1.

[0255] Wherein, a HARQ-ACK value of A1 can indicate that the HARQ-ACK information fed back by the terminal device is ACK, and a HARQ-ACK value of A2 can indicate that the HARQ-ACK information fed back by the terminal device is NACK; or, a HARQ-ACK value of A1 can indicate that the HARQ-ACK information fed back by the terminal device is NACK, and a HARQ-ACK value of A2 can indicate that the HARQ-ACK information fed back by the terminal device is ACK.

[0256] For example, for X events, suppose we need 3X (3X≤12, i.e., X≤4) different cyclic shift values, representing the occurrence of X events, the occurrence of X events and HARQ-ACK values ​​A1, and the occurrence of X events and HARQ-ACK values ​​A2, respectively. As an example, the correspondence between the cyclic shift values ​​of the sequence and the events and HARQ-ACK information can exist in the form of a table, function, text, or string, such as in storage or transmission. Taking a table as an example, the correspondence between the cyclic shift values ​​of the sequence and the events and HARQ-ACK information can be shown in Table 2.

[0257] Table 2

[0258] Taking Table 2 as an example, assuming X = 4, sending sequences with cyclic shift values ​​of 0, 3, 6, and 9 can represent events 1, 2, 3, and 4 occurring respectively; sending sequences with cyclic shift values ​​of 1, 4, 7, and 10 can represent events 1, 2, 3, and 4 occurring with a HARQ-ACK value of A1 respectively; and sending sequences with cyclic shift values ​​of 2, 5, 8, and 11 can represent events 1, 2, 3, and 4 occurring with a HARQ-ACK value of A2 respectively. This is just an example, and the specific cyclic shift value used is not limited. Similar to Table 1, in actual transmission, the cyclic shift value of the sequence can also be increased by `initialCyclicShift`. Taking event 1 + A1 as an example, if the cyclic shift value of the sequence is "1 + initialCyclicShift", it means event 1 has occurred with a HARQ-ACK value of A1. Therefore, the values ​​corresponding to each event and HARQ-ACK value in Table 2 can also be updated to: the sum of the value and `initialCyclicShift`.

[0259] Table 2 above is for illustrative purposes only and is not intended to limit the scope of events. For example, Table 2 may include a greater number of events. Furthermore, events 1-4 mentioned in Table 2 may be events #1-#6 listed in step 420 above, such as event 1 being one of events #1-#6; or they may be other events, which is not limited to these.

[0260] Another possible implementation is that the cyclic shift value of the sequence indicates any of the following: an event occurs, an event occurs and the HARQ-ACK value is A1, an event occurs and the HARQ-ACK value is A2, no event occurs and the HARQ-ACK value is A1, and no event occurs and the HARQ-ACK value is A2.

[0261] For example, for X events, suppose we need 3X+2 (3X+2≤12, i.e., X≤3) different cyclic shift values ​​to represent the occurrence of X events, the occurrence of X events and a HARQ-ACK value of A1, the occurrence of X events and a HARQ-ACK value of A2, no event occurring and a HARQ-ACK value of A1, and no event occurring and a HARQ-ACK value of A2. As an example, the correspondence between the cyclic shift values ​​of the sequence and the event and HARQ-ACK information can exist in the form of a table, function, text, or string, such as storage or transmission. Taking a table as an example, the correspondence between the cyclic shift values ​​of the sequence and the event and HARQ-ACK information can be shown in Table 3.

[0262] Table 3

[0263] Taking Table 3 as an example, assuming X = 3, sending sequences with cyclic shift values ​​of 0, 4, and 8 represents events 1, 2, and 3 occurring, respectively; sending sequences with cyclic shift values ​​of 1, 5, and 9 represents events 1, 2, and 3 occurring with a HARQ-ACK value of A1, respectively; sending sequences with cyclic shift values ​​of 2, 6, and 10 represents events 1, 2, and 3 occurring with a HARQ-ACK value of A2, respectively; sending a sequence with a cyclic shift value of 3 represents no event occurring with a HARQ-ACK value of A1; and sending a sequence with a cyclic shift value of 7 represents no event occurring with a HARQ-ACK value of A2. This is just an example; the specific cyclic shift value used is not limited. Similar to Table 1, in actual transmission, the cyclic shift value of the sequence can also be increased by `initialCyclicShift`. Taking event 2 + A1 as an example, if the cyclic shift value of the sequence is "5 + initialCyclicShift", it means event 2 occurred with a HARQ-ACK value of A1. Therefore, the values ​​corresponding to each event and HARQ-ACK value in Table 3 above can also be updated to: the sum of the value and initialCyclicShift.

[0264] Table 3 above is for illustrative purposes only and is not intended to limit the scope of events. For example, Table 3 may include a greater number of events. Furthermore, events 1-3 mentioned in Table 3 may be events #1-#6 listed in step 420 above, such as event 1 being one of events #1-#6; or they may be other events, which is not limited to these.

[0265] In scenario 2, the HARQ-ACK information occupies 2 bits.

[0266] One possible implementation is that the cyclic shift value of the sequence indicates any of the following: an event occurs, an event occurs and the HARQ-ACK value is A3, an event occurs and the HARQ-ACK value is A4, an event occurs and the HARQ-ACK value is A5, or an event occurs and the HARQ-ACK value is A6. For example, A3 = 00, A4 = 01, A5 = 10, and A6 = 11.

[0267] For example, for X events, suppose 5X (5X≤12, i.e., X≤2) different cyclic shift values ​​are needed, representing the occurrence of X events, the occurrence of X events and HARQ-ACK values ​​A3, X events and HARQ-ACK values ​​A4, X events and HARQ-ACK values ​​A5, and X events and HARQ-ACK values ​​A6 respectively. As an example, the correspondence between the cyclic shift values ​​of the sequence and the event and HARQ-ACK information can exist in the form of a table, function, text, or string, such as storage or transmission. Taking a table as an example, the correspondence between the cyclic shift values ​​of the sequence and the event and HARQ-ACK information can be shown in Table 4.

[0268] Table 4

[0269] Taking Table 4 as an example, assuming X = 2, sending sequences with cyclic shift values ​​of 0 and 6 represents events 1 and 2 occurring respectively; sending sequences with cyclic shift values ​​of 1 and 7 represents events 1 and 2 occurring with a HARQ-ACK value of A3; sending sequences with cyclic shift values ​​of 2 and 8 represents events 1 and 2 occurring with a HARQ-ACK value of A4; sending sequences with cyclic shift values ​​of 3 and 9 represents events 1 and 2 occurring with a HARQ-ACK value of A5; and sending sequences with cyclic shift values ​​of 4 and 10 represents events 1 and 2 occurring with a HARQ-ACK value of A6. This is just an example, and the specific cyclic shift value used is not limited. Similar to Table 1, in actual transmission, the cyclic shift value of the sequence can also be increased by `initialCyclicShift`. Taking event 1 + A4 as an example, if the cyclic shift value of the sequence is "2 + initialCyclicShift", it means event 1 has occurred with a HARQ-ACK value of A4. Therefore, the values ​​corresponding to each event and HARQ-ACK value in Table 4 above can also be updated to: the sum of the value and initialCyclicShift.

[0270] Table 4 above is for illustrative purposes only and is not intended to limit the scope of events. For example, Table 4 may include a greater number of events. Furthermore, events 1-2 mentioned in Table 4 may be events #1-#6 listed in step 420 above, such as event 1 being one of events #1-#6; or they may be other events, which is not limited to these.

[0271] Another possible implementation is that the cyclic shift value of the sequence indicates any of the following: an event occurs, an event occurs and the HARQ-ACK value is A3, an event occurs and the HARQ-ACK value is A4, an event occurs and the HARQ-ACK value is A5, an event occurs and the HARQ-ACK value is A6, or no event occurs and the HARQ-ACK value is A3 / A4 / A5 / A6.

[0272] For example, for X events, suppose we need 5X+4 (5X+4≤12, i.e., X≤1) different cyclic shift values ​​to represent: an event occurring, an event occurring with HARQ-ACK value A3, an event occurring with HARQ-ACK value A4, an event occurring with HARQ-ACK value A5, an event occurring with HARQ-ACK value A6, and no event occurring with HARQ-ACK values ​​A3 / A4 / A5 / A6. As an example, the correspondence between the cyclic shift values ​​of the sequence and the event / HARQ-ACK information can exist in the form of a table, function, text, or string, such as storage or transmission. Taking a table as an example, the correspondence between the cyclic shift values ​​of the sequence and the event / HARQ-ACK information can be shown in Table 5.

[0273] Table 5

[0274] Taking Table 5 as an example, assuming X = 1, sending a sequence with a cyclic shift value of 0 indicates that event 1 has occurred; sending sequences with cyclic shift values ​​of 1, 4, and 710 indicates that event 1 has occurred and the HARQ-ACK value is A3 / A4 / A5 / A6, respectively; and sending sequences with cyclic shift values ​​of 2, 5, 8, and 11 indicates that no event has occurred and the HARQ-ACK value is A3 / A4 / A5 / A6, respectively. This is just an example, and the specific cyclic shift used is not limited. Similar to Table 1, in actual transmission, the cyclic shift value of the sequence can also be increased by `initialCyclicShift`. Taking event 1 + A5 as an example, if the cyclic shift value of the sequence is "7 + initialCyclicShift", it indicates that event 1 has occurred and the HARQ-ACK value is A5. Therefore, the values ​​corresponding to each event and HARQ-ACK value in Table 5 can also be updated to: the sum of the value and `initialCyclicShift`.

[0275] Table 5 above is for illustrative purposes only and is not intended to limit the scope of events. For example, Table 5 may include a greater number of events. Furthermore, event 1 mentioned in Table 5 may be any of the events listed in step 420 above, such as event 1 being one of events #1 to #6; or it may be any other event, which is not limited to this.

[0276] The above describes method #1 in conjunction with two scenarios of PUCCH format 0 resources. It can be understood that each of the above implementation methods can also be used independently. That is, when using method #1, the first indication information can also be carried on other signaling, and there is no limitation on this.

[0277] Method #2 will be introduced below.

[0278] Method #2, the first indication information occupies at least 1 bit (for ease of description, it is called N bits, where N is an integer greater than or equal to 1), and the value of the N bits indicates at least one of the following: whether an event has occurred among the X events, and information about the events that have occurred among the X events.

[0279] Further optionally, based on this method, the first indication information can be carried in PUCCH format 1, that is, the terminal device sends N bits through PUCCH format 1 (or on PUCCH format 1 resources), and the N bits can indicate at least one of the following: whether an event has occurred among X events, and information about the events that have occurred among X events.

[0280] The PUCCH format 1 resource can also include the following two scenarios.

[0281] Scenario 1: The PUCCH format 1 resource is dedicated to reporting event information, or the PUCCH format 1 resource is dedicated to scheduling request resources for reporting event information.

[0282] In scenario 2, the PUCCH format 1 resource is a regular scheduling request resource, meaning that the PUCCH format 1 resource is not dedicated to reporting event information.

[0283] The following section will introduce some implementation methods for method #2, taking into account the two scenarios mentioned above.

[0284] In scenario 1, the PUCCH format 1 resource is dedicated to reporting event information.

[0285] In one possible implementation, the N bits are configured such that a first value indicates an event has occurred, and a second value indicates no event has occurred. The first and second values ​​are different. For example, the first value could be 0 and the second value could be 1; or the first value could be 1 and the second value could be 0.

[0286] For example, assuming X = 1, the first indication is conveyed using 1 bit, that is, using 1 bit to indicate whether an event has occurred. If this bit is set to the first value, it means that the event has occurred; if this bit is set to the second value, it means that the event has not occurred.

[0287] For another example, suppose X is greater than 1. The first indication is implemented using 1 bit, that is, using 1 bit to indicate whether at least one event has occurred. If this bit is set to the first value, it means that at least one event has occurred; if this bit is set to the second value, it means that no event has occurred.

[0288] The second possible implementation is that when a signal (such as an N-bit signal) is sent on the PUCCH format 1 resource, it indicates that an event has occurred; when no signal is sent on the PUCCH format 1 resource, it indicates that no event has occurred.

[0289] For example, assuming X = 1, if the terminal device sends an N-bit signal on the PUCCH format 1 resource, it indicates that an event has occurred; if the terminal device does not send a signal on the PUCCH format 1 resource, it indicates that the event has not occurred.

[0290] For another example, assuming X is greater than 1, if the terminal device sends an N-bit signal on the PUCCH format 1 resource, it indicates that at least one event has occurred; if the terminal device does not send a signal on the PUCCH format 1 resource, it indicates that no event has occurred.

[0291] The third possible implementation is that different values ​​of the N bits correspond to different events. When the N bits take a certain value, it means that the event corresponding to that value has occurred.

[0292] For example, X = 2, and the two events are called event 1 and event 2. The first indication information is implemented using 2 bits, that is, using 2 bits to indicate the information of the event that occurred among the X events. If the bit is set to "00", it means that event 1 occurred; if the bit is set to "01", it means that event 2 occurred; if the bit is set to "10" or "11" or no signal is sent, it means that no event occurred.

[0293] For example, X = 2, and the two events are called event 1 and event 2. The first indication information is implemented using 2 bits, that is, using 2 bits to indicate: the information of the events that occurred among the X events. This is represented by a bitmap: whether an event occurred among the two events, and the information of the events that occurred. For example, "assume 1" indicates that an event occurred, and "0" indicates that no event occurred. If the bit is set to "00", it means no event occurred; if the bit is set to "10", it means event 1 occurred; if the bit is set to "01", it means event 2 occurred.

[0294] For example, X = 3, and the two events are called event 1, event 2, and event 3. The first indication information is implemented using 2 bits, that is, using 2 bits to indicate the information of the event that occurred among the X events. If the bit is set to "00", it means that event 1 occurred; if the bit is set to "01", it means that event 2 occurred; if the bit is set to "10", it means that event 3 occurred; if the bit is set to "11" or no signal is sent, it means that no event occurred.

[0295] For example, X = 4, and the two events are called event 1, event 2, event 3, and event 4. The first indication information is implemented using 2 bits, that is, using 2 bits to indicate the information of the event that occurred among the X events. If the bit is set to "00", it indicates that event 1 occurred; if the bit is set to "01", it indicates that event 2 occurred; if the bit is set to "10", it indicates that event 3 occurred; and if the bit is set to "11", it indicates that event 4 occurred. Further optionally, if no signal is sent, it indicates that no event occurred.

[0296] The examples listed above are merely illustrations, and the specific bit information used to represent the occurrence of different events is not limited in the embodiments of this application.

[0297] The fourth possible implementation is that different values ​​of the N bits correspond to different event tables. When the N bits take a certain value, it means that the event in the event table corresponding to that value has occurred.

[0298] This method is similar to the third possible method, except that in the third possible implementation, an event is associated with a certain value of an N-bit bit, while in the fourth possible implementation, an event table is associated with a certain value of an N-bit bit.

[0299] The above-mentioned possible implementation methods are illustrative examples, and the embodiments of this application are not limited thereto.

[0300] Scenario 2: PUCCH format 1 resources are ordinary scheduling request resources.

[0301] This situation can be referred to as the first, third, and fourth possible scenarios in scenario 1 above, which will not be elaborated here.

[0302] In this case 2, as an example, the bit values ​​of N bits can satisfy the following condition: the bit value is not 0.

[0303] Optionally, the N bits can be used to jointly indicate event information and HARQ-ACK. Specifically, as mentioned above, the PUCCH can also carry HARQ-ACK information; therefore, the N bits can be used to jointly indicate event information and HARQ-ACK information.

[0304] For example, when X=1 or the first indication information only indicates whether an event has occurred out of X events, the first indication information can be multiplexed with up to 2 bits of HARQ-ACK information on a PUCCH format 1 resource. When an event occurs, HARQ-ACK information can be sent on the resource requested by the scheduling request; when no event occurs, HARQ-ACK information can be sent on the resource corresponding to the HARQ.

[0305] Method #3, the first indication information is a bitmap, which indicates at least one of the following: whether an event has occurred among X events, and information about the events that have occurred among X events.

[0306] Further optionally, based on this method, the first indication information can be carried in PUCCH format 2 / 3 / 4, that is, the terminal device sends a bitmap through PUCCH format 2 / 3 / 4 (or on PUCCH format 2 / 3 / 4 resources), and the bitmap can indicate at least one of the following: whether an event has occurred among X events, and information about the events that have occurred among X events.

[0307] Regarding PUCCH format 2 / 3 / 4 resources, the following two scenarios can be included.

[0308] Scenario 1: PUCCH format 2 / 3 / 4 resources are dedicated to reporting event information, or PUCCH format 2 / 3 / 4 resources are dedicated to scheduling request resources for reporting event information;

[0309] In scenario 2, the PUCCH format 2 / 3 / 4 resources are ordinary scheduling request resources, meaning that the PUCCH format 2 / 3 / 4 resources are not dedicated to reporting event information.

[0310] The following describes some implementation methods for method #3.

[0311] One possible implementation is that each bit in the bitmap corresponds to an event. A first value indicates that the event has occurred, and a second value indicates that the event has not occurred. The first and second values ​​are different. For example, the first value could be 0 and the second value could be 1; or the first value could be 1 and the second value could be 0.

[0312] For example, an X-bit bitmap indicates X events. Specifically, each bit represents one event; a bit value of "1" indicates that the event occurred, and a bit value of "0" indicates that the event did not occur. For instance, the bitmap corresponds to the event index from left to right, from smallest to largest. If X = 5, and the bitmap is "10100", it means that events 1 and 3 occurred, and the remaining events did not occur. As another example, the bitmap corresponds to the event index from largest to smallest, from left to right. If X = 5, and the bitmap is "10100", it means that events 5 and 3 occurred, and the remaining events did not occur. The examples listed above are merely illustrations; the specific bit information used to represent the occurrence of different events is not limited in the embodiments of this application.

[0313] The second possible implementation is that the value of the bitmap is related to whether the event combination has occurred, or the value of the bitmap is related to the event combination that has already occurred.

[0314] An event combination, also known as an event group or event list, may include one or more events. The number of events in each event combination may be the same or different; this is not limited. For consistency, the term event list will be used hereafter.

[0315] For example, each bit in the bitmap corresponds to an event table. A first value for a bit indicates that an event in the event table has occurred, and a second value for a bit indicates that an event in the event table has not occurred. This method is similar to the first possible method, except that in the first possible implementation, each bit in the bitmap corresponds to one event, while in the second possible implementation, each bit in the bitmap corresponds to an event table. The examples listed above are merely illustrative, and the specific bit information used to represent the occurrence of different events is not limited in the embodiments of this application.

[0316] The above implementation is for illustrative purposes only, and the embodiments in this application are not limited thereto. For example, the value of the bitmap may be related to whether an event has occurred.

[0317] The third possible implementation is that the bit value directly indicates the event index.

[0318] For example, for X events, it can be achieved through... The index of the event is used to indicate its occurrence. Assuming X = 5, 3 bits are used to indicate different events. For example, 3 bits of "000" indicate event 1; 3 bits of "001" indicate event 2; 3 bits of "010" indicate event 3; 3 bits of "011" indicate event 4; and 3 bits of "100" indicate event 5. As an example, if the 3 bits are of a certain value, the remaining bits can indicate no event occurred or other uses, and this is not limited. The examples listed above are merely examples; the specific bit information used to represent the occurrence of different events is not limited in the embodiments of this application.

[0319] The fourth possible implementation is that the bit value directly indicates the event table.

[0320] For example, different bit values ​​correspond to different event tables. For instance, 2 bits are used to indicate different event tables. If 2 bits are "11", it means that the event in event table 4 has occurred. If 2 bits are "10", it means that the event in event table 3 has occurred. If 2 bits are "01", it means that the event in event table 2 has occurred. If 1 bit is "00", it means that the event in event table 1 has occurred.

[0321] Method #4, the first indication information indicates the scheduling request associated with the events that have occurred in X events, and the scheduling request associated with the events that have occurred in X events indicates at least one of the following: whether any event has occurred in X events, and information about the events that have occurred in X events.

[0322] Further optionally, based on this method, the first indication information can be carried in PUCCH format 2 / 3 / 4, that is, the terminal device indicates at least one of the following through the scheduling request on PUCCH format 2 / 3 / 4 (or in other words, on PUCCH format 2 / 3 / 4 resources): whether an event has occurred among X events, and information about the events that have occurred among X events. For information on PUCCH format 2 / 3 / 4 resources, please refer to method #3.

[0323] For example, different events correspond to different scheduling requests. Therefore, if an event occurs, the terminal device can generate an index of the scheduling request corresponding to the event on the PUCCH format 2 / 3 / 4 resource. Based on this index, the network device can know which events have occurred.

[0324] Method #5, the first indication information is a resource, in other words, the resource indicates at least one of the following: whether an event has occurred among X events, and information about the events that have occurred among X events.

[0325] The resources can be one or more of PUCCH format 0, PUCCH format 1, PUCCH format 2, PUCCH format 3, PUCCH format 4, and PUSCH.

[0326] One possible scenario is that a resource is associated with different events (or different event tables). In this case, the event-related information can be determined based on the methods #1 to #4 described above.

[0327] Another possible scenario is that different resources are associated with different events (or different event tables). In this case, the occurrence of the corresponding event (or event table) can be indicated based on the resource from which the information is transmitted.

[0328] Let's take different resources as an example to illustrate the concept, and assume that X = 3, and the X events are called event #1, event #2, and event #3 respectively. Event #1 is associated with resource #1, event #2 is associated with resource #2, and event #3 is associated with resource #3.

[0329] For example, if the terminal device sends information on resource #1, it indicates that event #1 has occurred; if the terminal device sends information on resource #2, it indicates that event #2 has occurred; and if the terminal device sends information on resource #3, it indicates that event #3 has occurred. As an example, this resource is a scheduling request resource. In other words, different scheduling request resources can be associated with different events, and different scheduling request resources can be associated with different scheduling request indices. The scheduling request resource can be a PUCCH format 0 resource. Assume that event #1 is associated with scheduling request resource #1, event #2 with scheduling request resource #2, and event #3 with scheduling request resource #3. For example, if a terminal device sends information on scheduling request resource #1, such as a sequence of cyclic shifts to a specific value (e.g., a ZC sequence), it indicates (or implies) that event #1 has occurred; if the terminal device sends information on scheduling request resource #2, such as a sequence of cyclic shifts to a specific value (e.g., a ZC sequence), it indicates (or implies) that event #2 has occurred; and if the terminal device sends information on scheduling request resource #3, such as a sequence of cyclic shifts to a specific value (e.g., a ZC sequence), it indicates (or implies) that event #3 has occurred. As an example, the specific value is, for example, 0, or 0 + "initialCyclicShift".

[0330] For example, if the terminal device sends information on resource #1, it means that event #1 has not occurred. As a further example, it can also mean that an event other than event #1 (such as event #2 and event #3) has occurred. If the terminal device sends information on resource #2, it means that event #2 has not occurred. As a further example, it can also mean that an event other than event #2 (such as event #1 and event #3) has occurred. If the terminal device sends information on resource #3, it means that event #3 has not occurred. As a further example, it can also mean that an event other than event #3 (such as event #1 and event #2) has occurred.

[0331] The examples listed above are merely illustrations, and the specific corresponding methods used are not limited in the embodiments of this application.

[0332] The above-described methods #1-#5 describe the implementation methods of the first indication information, and the embodiments of this application are not limited thereto. For example, the first indication information is carried on the PUSCH, in which case the first indication information can be carried in at least one of the following signaling: MAC CE, UCI, etc. For example, the first indication information may include information about events that occurred in X events (such as indexes), or the first indication information may indicate whether a certain event or event table has occurred through a bitmap.

[0333] Further optionally, method 300 also includes: the terminal device sending a measurement report (i.e., an event-related report) related to the X event that has occurred.

[0334] Accordingly, the network device receives the measurement report. The measurement report and the first indication information may be carried on the same uplink resource, such as PUCCH or PUSCH; or they may be carried on different uplink resources, such as the measurement report being carried on PUCCH and the first indication information being carried on PUSCH, or the measurement report being carried on PUSCH and the first indication information being carried on PUCCH, or the measurement report being carried on one PUCCH and the first indication information being carried on another PUCCH, or the measurement report being carried on one PUSCH and the first indication information being carried on another PUSCH. Furthermore, the measurement report and the first indication information may be carried on the same signaling, such as UCI and / or MAC CE; or they may be carried on different signaling, such as the measurement report being carried on UCI and the first indication information being carried on MAC CE, or the measurement report being carried on MAC CE and the first indication information being carried on UCI, or the measurement report being carried on one MAC CE and the first indication information being carried on another MAC CE, or the measurement report being carried on one UCI and the first indication information being carried on another UCI; there is no limitation on this.

[0335] A measurement report is the reported content corresponding to an event that has occurred. As an example, such a measurement report includes at least one or more of the following: RSRP, SINR, precoding matrix indicator (PMI), rank indication (RI), channel quality indicator (CQI), beam availability, whether uplink transmit timing needs adjustment, whether downlink receive timing changes exceed a threshold, the resource identifier or logical identifier of the antenna panel used to obtain the measurement results (e.g., capability value identifier), and the cause of the event (e.g., receive beam change, transmit beam change, transmit / receive beam change, others, etc.).

[0336] In one possible scenario, after receiving the first instruction information, the network device sends information about scheduling resources to the terminal device; the terminal device then sends a measurement report on that scheduled resource.

[0337] In another possible scenario, after receiving the first instruction information, the network device sends feedback information to the terminal device, indicating that the first instruction information has been received; after receiving the feedback information, the terminal device sends a measurement report on a preset resource. This preset resource can be a specific reporting resource or any resource.

[0338] Another possible scenario is that after the terminal device sends the first instruction information to the network device, it directly sends a measurement report on the preset resources.

[0339] Another possible scenario is that the terminal device sends the first indication information and measurement report to the network device. In other words, the first indication information and measurement report can be sent to the network device in a single transmission (or in the same signaling).

[0340] Optionally, the events occurring in the X events include multiple events, and the terminal device sends measurement reports related to one or more of the multiple events.

[0341] As an example, a terminal device reports a measurement report related to an event. For instance, the terminal device reports the measurement report related to the first of several events that occurred, in sequence. For example, if X events include event #1 and event #2, and event #1 occurs first, then the terminal device reports the measurement report related to event #1. The order can be: in descending order of event index, or in ascending order of event index, or in descending order of event priority.

[0342] Another example is that the terminal device reports multiple event-related measurement reports. For instance, the terminal device can send these multiple event-related measurement reports via a single signaling signal, or it can send each event-related measurement report separately via multiple signaling signals; there is no limitation on this.

[0343] It is understandable that the terminal device may not send measurement reports related to the occurred event (i.e., event-related reports) in event X. In other words, an event occurs, but the measurement results for that event do not need to be reported. For example, event A does not require reporting measurement results. Assuming the event information is not in the measurement report, it does not need to be sent; it is sufficient to inform the user of the occurrence of event A through the first indication information.

[0344] Optionally, method 300 further includes: the terminal device determining a reference signal resource. The reference signal resource represents a reference signal resource for a measurement corresponding to the event, or a reference signal resource for a measurement corresponding to the terminal device.

[0345] One possible implementation is that the network device is configured with reference signal resource information for measurements corresponding to different events.

[0346] Based on this method, the terminal device determines the reference signal resource, including: the terminal device receiving third indication information, which indicates the reference signal resource. The information of the reference signal resource and the information of X events can be carried in the same signaling, such as the configuration information in step 420 including the information of X events and the information of the reference signal resource; or they can be carried in different signaling, which is not limited thereto.

[0347] As an example, a network device configures reference signal resources (one or more reference signals), reference signal resource sets (containing one or more reference signals), or reference signal resource settings (containing one or more reference signal resource sets) corresponding to different events, to monitor whether a certain event has occurred. If an event occurs, a report is triggered. Alternatively, the measurement result reported by a certain event corresponds to: the reference signal resource / reference signal resource set / reference signal resource configuration corresponding to that event.

[0348] Optionally, the network device may configure or associate different reference signal resources / sets of reference signal resources / configurations for different events; or, the network device may configure or associate the same reference signal resources / sets of reference signal resources / configurations for different events.

[0349] Another example is that the network device sends an event-triggered reporting configuration to the end device, which is a dedicated event reporting configuration.

[0350] For example, the configuration information may include information indicating that the report corresponds only to event-triggered measurement result reporting, or information indicating that the report can be event-triggered, or a dedicated RRC cell configured for the report, so that the terminal device knows that the configuration is for event-triggered reporting. Furthermore, the reporting configuration can also be associated with reference signal resources / reference signal resource sets / reference signal resource settings, allowing the terminal device to determine which reference signal resources' measurement results can be reported during event reporting.

[0351] Another example is that network devices send different event-triggered reporting configurations to terminals.

[0352] For example, the configuration information includes event information, such as an event index, which indicates that the reporting configuration corresponds to a specific event. If the event occurs, the information is reported according to the corresponding configuration information.

[0353] Another possible implementation is to predefine the reference signal resource information for different events that trigger the reporting of corresponding measurements.

[0354] For example, the reference signal resources for measurements triggered by different events can be predefined as the reference signal resources corresponding to the current serving beam. For instance, the reference signal resources for measurements triggered by different events could be reference signals with QCL type type D in the currently indicated TCI-state, or reference signals with QCL type type D in the UL TCI-state of the current uplink transmission (PUSCH / PUCCH / SRS / physical random access channel, PRACH) application, or reference signals with QCL type type D in the DLorjointTCI-state of the current downlink transmission (PDCCH / PDSCH / CSI-RS) application.

[0355] For another example, the reference signal resources for the measurement triggered by different events can be predefined as reference signals of type D in the currently active TCI-states with QCL type.

[0356] The aforementioned predefined reference signal resources may correspond to different events or the same event, and there is no limitation on this. Furthermore, the aforementioned reference signals may be reference signals for the serving cell or reference signals for candidate cells / neighboring cells.

[0357] It is understood that in the above embodiments, specific correspondences between events and bit values ​​or sequence cyclic shift values ​​are listed. This is merely an illustrative example for ease of understanding. Any association between events and bit values, or between bits and sequence cyclic shift values, falls within the protection scope of this application. For example, when the cyclic shift value of a sequence is related to another parameter, an association between an event and that other parameter can also be established, allowing indication of whether the corresponding event has occurred based on the other parameter. Furthermore, when using a bitmap to indicate whether X events have occurred, the correspondence between each bit and the event can be arbitrary. For instance, a bitmap from left to right corresponds to event indices from smallest to largest; a bitmap from left to right corresponds to event indices from largest to smallest; or other correspondences may exist; a bitmap from left to right corresponds to event priorities from highest to lowest; or a bitmap from left to right corresponds to event priorities from lowest to highest.

[0358] It is understood that some optional features in the various embodiments of this application may not depend on other features in some scenarios, or may be combined with other features in some scenarios, without limitation.

[0359] It is also understood that the solutions in the various embodiments of this application can be used in reasonable combinations, and the explanations or descriptions of the various terms appearing in the embodiments can be referenced or explained to each other in the various embodiments, without limitation.

[0360] It is also understood that, in the above-described method embodiments, the methods and operations implemented by a device (such as a terminal device or a network device) can also be implemented by components of the device (such as chips or circuits), without limitation.

[0361] The method provided by the embodiments of this application has been described in detail above with reference to FIG. 4. The apparatus provided by the embodiments of this application will be described in detail below with reference to FIGS. 5 to 7. It should be understood that the description of the apparatus embodiments corresponds to the description of the method embodiments; therefore, any content not described in detail can be referred to the method embodiments above, and for the sake of brevity, will not be repeated here.

[0362] Referring to Figure 5, which is a schematic diagram of a communication device 500 provided in an embodiment of this application, the device 500 includes a transceiver unit 510. The transceiver unit 510 can be used to implement corresponding communication functions. The transceiver unit 510 can also be referred to as a communication interface or a communication unit.

[0363] Optionally, the device 500 further includes a processing unit 520. The processing unit 520 can be used to perform processing, such as beam measurement. The functionality of the processing unit 520 can be implemented by one or more processors. Specifically, the processor may include a modem chip, or a system-on-a-chip (SoC) or SIP chip containing a modem core.

[0364] Optionally, the device 500 may further include a storage unit, which can be used to store instructions and / or data, and the processing unit 520 can read the instructions and / or data in the storage unit to enable the device to implement the aforementioned method embodiments.

[0365] Optionally, the transceiver unit 510 may include a receiving unit and a sending unit. The receiving unit can be used to perform receiving-related operations (such as receiving data or messages), and the sending unit can be used to perform sending-related operations (such as sending data or messages).

[0366] In a first possible design, the device 500 can be the terminal device in the foregoing embodiments, which can implement the steps or processes corresponding to those executed by the terminal device in the above method embodiments. Specifically, the transceiver unit 510 can be used to perform transceiver-related operations (such as sending and / or receiving data or messages) of the terminal device in the above method embodiments, for example, the transceiver unit 510 can be used to execute steps 410, 420, and 430 in the embodiment shown in FIG4. The processing unit 520 can be used to perform processing-related operations of the terminal device in the above method embodiments, or operations other than transceiver (such as operations other than sending and / or receiving data or messages).

[0367] In one possible implementation, the transceiver unit 510 is configured to receive configuration information, the configuration information including information about at least one event; the transceiver unit 510 is also configured to send first indication information, the first indication information indicating at least one of the following: whether an event has occurred in at least one event, and information about the event that has occurred in at least one event.

[0368] In a second possible design, the device 500 can be a network device as described in the foregoing embodiments. This device 500 can implement the steps or processes performed by the network device corresponding to those described in the method embodiments above. Specifically, the transceiver unit 510 can be used to perform transceiver-related operations (such as sending and / or receiving data or messages) of the network device in the method embodiments above. For example, the transceiver unit 510 can be used to perform steps 410, 420, and 430 in the embodiment shown in FIG4. The processing unit 520 can be used to perform processing-related operations of the network device in the method embodiments above, or operations other than transceiver (such as operations other than sending and / or receiving data or messages).

[0369] In one possible implementation, the transceiver unit 510 is used to send configuration information, which includes information about at least one event; the transceiver unit 510 is also used to receive first indication information, which indicates at least one of the following: whether an event has occurred in at least one event, and information about the event that has occurred in at least one event.

[0370] It should be understood that the specific process of each unit performing the above-mentioned corresponding steps has been described in detail in the above method embodiments, and will not be repeated here for the sake of brevity.

[0371] It should also be understood that the device 500 here is embodied in the form of a functional unit. The term "unit" here can refer to an application-specific integrated circuit (ASIC), electronic circuitry, a processor (e.g., a shared processor, a proprietary processor, or a group processor, etc.) and memory for executing one or more software or firmware programs, integrated logic circuitry, and / or other suitable components supporting the described functions. In an alternative example, those skilled in the art will understand that the device 500 can specifically be the communication device in the above embodiments, and can be used to execute the various processes and / or steps corresponding to the communication device in the above method embodiments; to avoid repetition, these will not be described again here.

[0372] The apparatus 500 of each of the above-described schemes has the function of implementing the corresponding steps performed by the communication device in the above-described methods. The function can be implemented in hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions; for example, the transceiver unit can be replaced by a transceiver (e.g., the transmitting unit in the transceiver unit can be replaced by a transmitter, and the receiving unit in the transceiver unit can be replaced by a receiver), and other units, such as processing units, can be replaced by processors, each executing the transceiver operations and related processing operations in each method embodiment.

[0373] In addition, the transceiver unit 510 may also be a transceiver circuit (for example, it may include a receiving circuit and a transmitting circuit), and the processing unit may be a processing circuit.

[0374] It should be noted that the device in Figure 5 can be the communication device in the foregoing embodiments, or it can be a chip or chip system, such as a modem chip or a system-on-a-chip (SoC) chip or SIP chip containing a modem core. The transceiver unit can be an input / output circuit or a communication interface; the processing unit is a processor, microprocessor, or integrated circuit integrated on the chip. No limitations are imposed here.

[0375] Referring to Figure 6, which is a schematic diagram of another communication device 600 provided in an embodiment of this application, the device 600 includes a processor 610 coupled to a memory 620. The memory 620 is used to store computer programs or instructions and / or data. The processor 610 is used to execute the computer programs or instructions stored in the memory 620, or to read the data stored in the memory 620, to perform the methods in the above-described method embodiments.

[0376] Optionally, there may be one or more processors 610.

[0377] Optionally, the memory 620 may be one or more.

[0378] Alternatively, the memory 620 can be integrated with the processor 610, or it can be set separately.

[0379] Optionally, as shown in FIG6, the device 600 further includes a transceiver 630 for receiving and / or transmitting signals. For example, the processor 610 is used to control the transceiver 630 to receive and / or transmit signals.

[0380] As an example, processor 610 may have the functions of processing unit 520 shown in FIG5, memory 620 may have the functions of storage unit, and transceiver 630 may have the functions of transceiver unit 510 shown in FIG5.

[0381] As one option, the device 600 is used to implement the operations performed by the communication device in the various method embodiments described above.

[0382] For example, processor 610 is used to execute computer programs or instructions stored in memory 620 to implement the relevant operations of terminal devices or network devices in the various method embodiments described above.

[0383] It should be understood that the processor mentioned in the embodiments of this application can be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor can be a microprocessor or any conventional processor.

[0384] It should also be understood that the memory mentioned in the embodiments of this application can be volatile memory and / or non-volatile memory. 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. Volatile memory can be random access memory (RAM). For example, RAM can be used as an external cache. By way of example and not limitation, RAM includes the following forms: 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).

[0385] It should be noted that when the processor is a general-purpose processor, DSP, ASIC, FPGA, or other programmable logic device, discrete gate or transistor logic device, or discrete hardware component, the memory (storage module) can be integrated into the processor.

[0386] It should also be noted that the memory described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0387] Referring to Figure 7, Figure 7 is a schematic diagram of a chip system 700 provided in an embodiment of this application. The chip system 700 (or may also be referred to as a processing system) includes logic circuitry 710 and an input / output interface 720.

[0388] The logic circuit 710 can be a processing circuit in the chip system 700. The logic circuit 710 can be coupled to a memory unit, calling instructions from the memory unit, enabling the chip system 700 to implement the methods and functions of the embodiments of this application. The input / output interface 720 can be an input / output circuit in the chip system 700, outputting processed information or inputting data or signaling information to be processed into the chip system 700 for processing.

[0389] Optionally, the logic circuit 710 may be implemented by one or more processors, including the one or more processors or the processing portion of the one or more processors.

[0390] Optionally, the input / output interface 720 may include transceiver circuitry, a transceiver, input / output circuitry, or a communication interface.

[0391] As one approach, the chip system 700 is used to implement the operations performed by the communication device (such as a terminal device or a network device) in the various method embodiments described above.

[0392] For example, logic circuit 710 is used to implement processing-related operations performed by a communication device (such as a terminal device or a network device) in the above method embodiments; input / output interface 720 is used to implement sending and / or receiving-related operations performed by a communication device (such as a terminal device or a network device) in the above method embodiments.

[0393] This application also provides a computer-readable storage medium storing computer instructions for implementing the methods executed by a communication device (such as a terminal device or a network device) in the above-described method embodiments.

[0394] For example, when the computer program is executed by a computer, it enables the computer to implement the methods described in the embodiments of the above methods, which are executed by a communication device (such as a terminal device or a network device).

[0395] This application also provides a computer program product comprising instructions which, when executed by a computer, implement the methods described above as being performed by a communication device (such as a terminal device or a network device).

[0396] This application also provides a communication system that includes the terminal device and / or network device described in the preceding embodiments. For example, the system includes the terminal device and network device shown in FIG4.

[0397] The explanations and beneficial effects of the relevant contents in any of the devices provided above can be found in the corresponding method embodiments provided above, and will not be repeated here.

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

[0399] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program 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. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. For example, the computer can be a personal computer, a server, or a network device, etc. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available media can be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., DVDs), or semiconductor media (e.g., solid-state disks, SSDs). For example, the aforementioned available media include, but are not limited to, USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks, and other media capable of storing program code.

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

Claims

1. A communication method, characterized in that, include: Receive configuration information, the configuration information including information about at least one event; Send a first indication message, which indicates at least one of the following: whether an event has occurred among the at least one event, and information about the event that has occurred among the at least one event.

2. The method according to claim 1, characterized in that, The sending of the first indication information includes: A sequence is transmitted, the cyclic shift value of which indicates at least one of the following: whether an event has occurred in the at least one event, and information about the event that has occurred in the at least one event.

3. The method according to claim 2, characterized in that, When the cyclic shift value of the sequence is a first value, the cyclic shift value of the sequence indicates that an event has occurred in the at least one event.

4. [Amended according to Rule 26, 14.04.2025] The method according to claim 3, characterized in that, The first value is 0.

5. [Amended according to Rule 26, 14.04.2025] The method according to any one of claims 1 to 4, characterized in that, The first indication information is carried in the PUCCH resource of uplink control channel PUCCH format 0.

6. The method according to claim 5, characterized in that, When a signal or sequence is carried on the PUCCH resource of PUCCH format 0, an event occurs in at least one of the events; or, When no signal or sequence is carried on the PUCCH resource of PUCCH format 0, no event occurs in the at least one event.

7. The method according to claim 1, characterized in that, The first indication information occupies at least 1 bit; The first indication information indicates at least one of the following: whether an event has occurred among the at least one event, and information about the events that have occurred among the at least one event, including: The value of the at least 1 bit indicates at least one of the following: whether an event has occurred in the at least one event, and information about the event that has occurred in the at least one event.

8. The method according to claim 7, characterized in that, The value of at least 1 bit being 0 indicates that an event has occurred in the at least one event.

9. The method according to claim 8, characterized in that, The at least one event is a single event.

10. The method according to any one of claims 1, 7, 8, or 9, characterized in that, The first indication information is carried in the PUCCH resource of PUCCH format 1.

11. The method according to any one of claims 1, 7, 8, or 9, characterized in that, The first indication information is carried in a PUCCH resource of at least one of the following channel formats: PUCCH format 2, PUCCH format 3, and PUCCH format 4.

12. The method according to claim 11, characterized in that, The first indication information is a bitmap, or the first indication information indicates a scheduling request associated with an event that has occurred in at least one of the events.

13. The method according to claim 12, characterized in that, In the bitmap, each bit corresponds to an event, with the first value indicating that the event has occurred and the second value indicating that the event has not occurred; or... The values ​​of the bitmap are associated with combinations of events that have occurred; or The values ​​of the bitmap are related to whether the event combination occurs.

14. The method according to any one of claims 1 to 13, characterized in that, The at least one event is related to a measurement report initiated by the terminal device, and the method further includes: Send a measurement report related to the event that occurred in at least one of the events.

15. The method according to claim 14, characterized in that, Sending a measurement report related to an event occurring in at least one of the events includes: Send a measurement report related to the event that occurred in the at least one of the events on a preset resource; or... Send measurement reports related to the events that occurred in the at least one event on the scheduling resources.

16. The method according to claim 15, characterized in that, The method further includes: Receive the information about the scheduled resources.

17. The method according to any one of claims 1 to 16, characterized in that, The method further includes: Receive event triggering reporting configuration, wherein the event triggering reporting configuration includes at least one of the following information: Event information, Reference signal resource information associated with the event.

18. The method according to any one of claims 1 to 17, characterized in that, The at least one event includes at least one of the following: The first beam quality is lower than or equal to a first preset threshold, the second beam quality is higher than or equal to a second preset threshold, the second beam quality is higher than or equal to a third preset threshold of the first beam quality, and the difference between the second beam quality and the first beam quality is less than or equal to a fourth preset threshold. Wherein, the first beam represents the serving beam, and the second beam represents a beam different from the serving beam.

19. The method according to any one of claims 1 to 18, characterized in that, Before receiving configuration information, the method further includes: Send a second indication message, which indicates information about events supported by the terminal device.

20. The method according to any one of claims 1 to 19, characterized in that, Information about the events that occurred in the at least one event includes: an index of the events that occurred in the at least one event.

21. A communication method, characterized in that, include: Send configuration information, which includes information about at least one event; Receive first indication information, the first indication information indicating at least one of the following: whether an event has occurred among the at least one event, and information about the event that has occurred among the at least one event.

22. The method according to claim 21, characterized in that, The receiving of the first indication information includes: A received sequence, the cyclic shift value of which indicates at least one of the following: whether an event has occurred in the at least one event, and information about the event that has occurred in the at least one event.

23. The method according to claim 22, characterized in that, When the cyclic shift value of the sequence is a first value, the cyclic shift value of the sequence indicates that an event has occurred in the at least one event.

24. The method according to claim 23, characterized in that, The first value is 0.

25. The method according to any one of claims 21 to 24, characterized in that, The first indication information is carried in the PUCCH resource of uplink control channel PUCCH format 0.

26. The method according to claim 25, characterized in that, When a signal or sequence is carried on the PUCCH resource of PUCCH format 0, an event occurs in at least one of the events; or, When no signal or sequence is carried on the PUCCH resource of PUCCH format 0, no event occurs in the at least one event.

27. The method according to claim 21, characterized in that, The first indication information occupies at least 1 bit; The first indication information indicates at least one of the following: whether an event has occurred among the at least one event, and information about the events that have occurred among the at least one event, including: The value of the at least 1 bit indicates at least one of the following: whether an event has occurred in the at least one event, and information about the event that has occurred in the at least one event.

28. The method according to claim 27, characterized in that, The value of at least 1 bit being 0 indicates that an event has occurred in the at least one event.

29. The method according to claim 28, characterized in that, The at least one event is a single event.

30. The method according to any one of claims 21, 27, 28, or 29, characterized in that, The first indication information is carried in the PUCCH resource of PUCCH format 1.

31. The method according to any one of claims 21, 27, 28, or 29, characterized in that, The first indication information is carried in a PUCCH resource of at least one of the following channel formats: PUCCH format 2, PUCCH format 3, and PUCCH format 4.

32. The method according to claim 31, characterized in that, The first indication information is a bitmap, or the first indication information indicates a scheduling request associated with an event that has occurred in at least one of the events.

33. The method according to claim 32, characterized in that, In the bitmap, each bit corresponds to an event, with the first value indicating that the event has occurred and the second value indicating that the event has not occurred; or... The values ​​of the bitmap are associated with combinations of events that have occurred; or The values ​​of the bitmap are related to whether the event combination occurs.

34. The method according to any one of claims 21 to 33, characterized in that, The at least one event is related to a measurement report initiated by the terminal device, and the method further includes: Receive measurement reports related to the events that occurred in the at least one of the events.

35. The method according to claim 34, characterized in that, Receiving a measurement report related to an event occurring in the at least one of the events includes: Receive measurement reports related to the events occurring in the at least one of the events on preset resources; or... Receive measurement reports related to the events that occurred in the at least one event on the scheduling resource.

36. The method according to claim 35, characterized in that, The method further includes: Send the information about the scheduled resources.

37. The method according to any one of claims 21 to 36, characterized in that, The method further includes: Send event-triggered reporting configuration, wherein the event-triggered reporting configuration includes at least one of the following information: Event information, Reference signal resource information associated with the event.

38. The method according to any one of claims 21 to 37, characterized in that, The at least one event includes at least one of the following: The first beam quality is lower than or equal to a first preset threshold, the second beam quality is higher than or equal to a second preset threshold, the second beam quality is higher than or equal to a third preset threshold of the first beam quality, and the difference between the second beam quality and the first beam quality is less than or equal to a fourth preset threshold. Wherein, the first beam represents the serving beam, and the second beam represents a beam different from the serving beam.

39. The method according to any one of claims 21 to 38, characterized in that, Before sending the configuration information, the method further includes: Receive second indication information, which indicates information about events supported by the terminal device.

40. The method according to any one of claims 21 to 39, characterized in that, Information about the events that occurred in the at least one event includes: an index of the events that occurred in the at least one event.

41. A communication device, characterized in that, Including transceiver units, The transceiver unit is used to receive configuration information, which includes information about at least one event. The transceiver unit is further configured to send first indication information, the first indication information indicating at least one of the following: whether an event has occurred among the at least one event, and information about the event that has occurred among the at least one event.

42. The apparatus according to claim 41, characterized in that, The transceiver unit is further configured to send first indication information, including: The transceiver unit is also configured to transmit a sequence, the cyclic shift value of which indicates at least one of the following: whether an event has occurred in the at least one event, and information about the event that has occurred in the at least one event.

43. The apparatus according to claim 41 or 42, characterized in that, The at least one event is related to the reporting of a measurement report initiated by the terminal device, and the transceiver unit is further configured to send a measurement report related to the event that occurred in the at least one event.

44. The apparatus according to claim 43, characterized in that, The transceiver unit is further configured to send a measurement report related to an event occurring in the at least one of the events, including: The transceiver unit is further configured to send a measurement report related to an event occurring in the at least one event on a preset resource; or, The transceiver unit is also configured to send measurement reports related to events occurring in the at least one event on the scheduling resources.

45. The apparatus according to claim 44, characterized in that, The transceiver unit is also used to receive information about the scheduling resources.

46. ​​The apparatus according to any one of claims 41 to 45, characterized in that, The transceiver unit is also configured to receive event triggering reporting configuration, which includes at least one of the following information: event information and reference signal resource information associated with the event.

47. A communication device, characterized in that, Including transceiver units, The transceiver unit is used to send configuration information, which includes information about at least one event. The transceiver unit is further configured to receive first indication information, the first indication information indicating at least one of the following: whether an event has occurred among the at least one event, and information about the event that has occurred among the at least one event.

48. The apparatus according to claim 47, characterized in that, The transceiver unit is further configured to receive first indication information, including: The transceiver unit is also configured to receive a sequence, the cyclic shift value of which indicates at least one of the following: whether an event has occurred in the at least one event, and information about the event that has occurred in the at least one event.

49. The apparatus according to claim 47 or 48, characterized in that, The at least one event is related to the reporting of a measurement report initiated by the terminal device, and the transceiver unit is further configured to receive a measurement report related to an event occurring in the at least one event.

50. The apparatus according to claim 49, characterized in that, The transceiver unit is further configured to receive measurement reports related to events occurring in the at least one event, including: The transceiver unit is further configured to receive, on preset resources, a measurement report related to an event occurring in the at least one event; or, The transceiver unit is also configured to receive measurement reports related to events occurring in the at least one event on the scheduling resources.

51. The apparatus according to claim 50, characterized in that, The transceiver unit is also used to send information about the scheduling resources.

52. The apparatus according to any one of claims 47 to 51, characterized in that, The transceiver unit is also used to send an event triggering reporting configuration, which includes at least one of the following information: event information and reference signal resource information associated with the event.

53. A communication device, characterized in that, It includes modules or units for performing the method of any one of claims 1 to 20, or modules or units for performing the method of any one of claims 21 to 40.

54. A communication device, characterized in that, The device includes at least one processor, which is configured to execute a computer program or instructions to cause the device to perform the method of any one of claims 1 to 20, or to cause the device to perform the method of any one of claims 21 to 40.

55. The apparatus according to claim 54, characterized in that, The device further includes a memory for storing the computer program or instructions; and / or, The device further includes a communication interface coupled to the at least one processor, the communication interface being used for inputting and / or outputting information.

56. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program or instructions that, when executed on a communication device or computer, cause the communication device to perform the method as described in any one of claims 1 to 20, or cause the communication device to perform the method as described in any one of claims 21 to 40.

57. A computer program product, characterized in that, The computer program product includes a computer program or instructions for performing the method as described in any one of claims 1 to 20, or the computer program product includes a computer program or instructions for performing the method as described in any one of claims 21 to 40.

Images