WO2025209483A1 - Communication method and communication apparatus - Google Patents

Abstract

Provided in the present application are a communication method and a communication apparatus. The method may comprise: a terminal device side receives configuration information, the configuration information comprising information of at least one event, wherein for example, the event may trigger reporting of a measurement report; and the terminal device side sends first information, the first information comprising a measurement report related to an occurred event among the at least one event, and the payload size of the first information being a payload size corresponding to a measurement report related to a first event among the at least one event. On this basis, the terminal device can report the measurement report related to the occurred event by means of the first information of the fixed payload size, so as to avoid resource waste caused by the terminal device, when supporting or being configured with a plurality of events, allocating a corresponding reporting resource to each event.

Description

Communication method and communication device

This application claims priority to the Chinese patent application filed with the State Intellectual Property Office of China on April 2, 2024, with application number 202410397770.8 and invention name “Communication Method and Communication Device”, the entire contents of which are incorporated by reference into this application.

Technical Field

The present application relates to the field of wireless communications, and more particularly, to a communication method and a communication device.

Background Art

In wireless communications, reference signals are transmitted between transmitters and receivers for purposes such as sending and receiving data, achieving system synchronization, and providing feedback on channel information. For example, the transmitter sends a reference signal to the receiver, which then receives the reference signal and performs corresponding operations based on the reference information, such as performing channel measurements and submitting measurement reports. Currently, the timing of measurement reports is primarily determined by network equipment, resulting in significant uplink resource overhead.

Summary of the Invention

The present application provides a communication method and a communication device, which can realize the reporting of measurement reports related to events, reduce the overhead of uplink resources, and realize reasonable allocation of resources.

In the first aspect, a communication method is provided. This method can be applied to the terminal side, that is, the method can be executed by a terminal device or by a component of the terminal device (such as a chip or chip system or circuit or communication module), which is not limited in this application. The following mainly uses the terminal device as an example for description.

The method includes: receiving configuration information, the configuration information includes information about at least one event, and the at least one event is related to the measurement report reporting initiated by the terminal device; sending first information, the first information includes a measurement report related to an event occurring in the at least one event, and the load size corresponding to the first information is the load size corresponding to the measurement report related to the first event in the at least one event.

Based on the above technical solution, the terminal device can perform event-triggered reporting, thereby avoiding the terminal device from reporting invalid measurement reports to the network device. In addition, the terminal device can report measurement reports related to the occurred event using the first information with a fixed payload size, thereby avoiding resource waste caused by allocating corresponding reporting resources for each event when the terminal device supports or is configured with multiple events.

The measurement reports related to different events in the at least one event may be predefined by a protocol, or may be configured by a network device, which is not limited in this application.

Optionally, in at least one event, at least two event-related measurement reports are different.

Optionally, in at least one event, there are at least two event-related measurement reports whose corresponding load sizes are different.

The first event may be a predefined event, or an event indicated by the network device to the terminal device, or an event indicated by the terminal device to the network device, or the first event is an event in which the load size corresponding to the relevant measurement report is the largest among at least one event.

The payload size corresponding to the event-related measurement report refers to the payload size required for reporting the event-related measurement report, or the number of bits/bit space/bit width required for reporting the event-related measurement report.

Exemplarily, the above-mentioned measurement report is at least one of the following: a report initiated by an event or user equipment (UE), a beam report initiated by an event or UE, a channel state information (CSI) report initiated by an event or UE, a beam measurement result report initiated by an event or UE, an interference measurement report initiated by an event or UE, an interference measurement report, a CSI report, a beam measurement result report, etc.

In one possible implementation, one of the events occurring in at least one event is a second event. If the load size corresponding to the measurement report related to the second event is smaller than the load size corresponding to the first information, then the part of the first information other than the measurement report related to the second event is a predefined value.

The second event is different from the first event. It is understood that if the first event is the event with the largest payload size corresponding to the related measurement report among the at least one event, the second event may be any event among the at least one event except the first event.

Optionally, if one of the events occurring in at least one event is a third event, and the load size corresponding to the measurement report related to the third event is greater than the load size corresponding to the first information, then the first information includes part of the measurement report in the measurement report related to the third event. For example, the terminal device can discard (drop) part of the measurement report in the measurement report related to the third event according to a predefined or preconfigured reporting order.

Optionally, if one of the events occurring in at least one event is a fourth event, and the load size corresponding to the measurement report related to the fourth event is equal to the load size corresponding to the first information, then the first information includes all measurement reports in the measurement report related to the fourth event, and there is no need to fill in the predefined value. For example, the terminal device can report the measurement report related to the fourth event in a predefined or preconfigured reporting order.

In conjunction with the first aspect, in certain implementations of the first aspect, the at least one event includes at least one of the following: the first beam quality is less than or equal to a first preset threshold, the second beam quality is greater than or equal to a second preset threshold, the difference between the second beam quality and the first beam quality is greater than or equal to a third preset threshold, 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. For example, the second beam is a candidate beam.

In combination with the first aspect, in certain implementations of the first aspect, a measurement report related to an event occurring in at least one event includes one or more of the following: an index of the first beam, the quality of the first beam, an index of the second beam, the quality of the second beam, information of the cell corresponding to the event-related measurement report, the reason why the quality of the first beam is lower than the threshold value, an index of a reference signal resource set, a reporting configuration index, information of an event occurring in at least one event, a capability index, and channel status information; wherein, the first beam is a service beam, and the second beam is a beam different from the first beam.

In a second aspect, a communication method is provided. This method 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 or chip system or circuit or communication module), which is not limited in this application. The following mainly uses network devices as an example for explanation.

The method includes: sending configuration information, the configuration information includes information about at least one event, and the at least one event is related to the measurement report reporting initiated by the terminal device; receiving first information, the first information includes a measurement report related to an event occurring in at least one event, and the load size corresponding to the first information is the load size corresponding to the measurement report related to the first event in at least one event.

With reference to the second aspect, in certain implementations of the second aspect, there are at least two event-related measurement reports that are different in at least one event.

With reference to the second aspect, in certain implementations of the second aspect, in at least one event, there are at least two event-related measurement reports whose corresponding load sizes are different.

In combination with the second aspect, in certain implementations of the second aspect, the first event is an event in which a load size corresponding to a related measurement report is the largest among the at least one event.

In combination with the second aspect, in certain implementations of the second aspect, if the load size corresponding to a measurement report related to an event occurring in at least one event is smaller than the load size corresponding to the first information, then the portion of the first information other than the measurement report related to the event occurring in at least one event is a predefined value.

In combination with the second aspect, in certain implementations of the second aspect, at least one event includes at least one of the following: the first beam quality is less than or equal to the first preset threshold, the second beam quality is greater than or equal to the second preset threshold, the difference between the second beam quality and the first beam quality is greater than or equal to the third preset threshold, and the difference between the second beam quality and the first beam quality is less than or equal to the fourth preset threshold; wherein, the first beam represents a service beam, and the second beam represents a beam different from the service beam.

In combination with the second aspect, in certain implementations of the second aspect, a measurement report related to an event occurring in at least one event includes one or more of the following: an index of the first beam, the quality of the first beam, an index of the second beam, the quality of the second beam, information of the cell corresponding to the event-related measurement report, the reason why the quality of the first beam is lower than the threshold value, an index of a reference signal resource set, a reporting configuration index, information of an event occurring in at least one event, a capability index, and channel state information; wherein, the first beam is a service beam, and the second beam is a beam different from the first beam.

Regarding the beneficial effects and possible designs of the second aspect, please refer to the relevant description in the first aspect and will not be repeated here.

In a third aspect, a communication method is provided. This method can be applied to the terminal side, that is, the method can be executed by a terminal device or by a component of the terminal device (such as a chip or chip system or circuit or communication module), which is not limited in this application. The following mainly uses the terminal device as an example for description.

The method includes: receiving configuration information, the configuration information includes information about at least one event, and the at least one event is related to the measurement report reporting initiated by the terminal device; sending first information, the first information includes a measurement report related to an event occurring in the at least one event.

The event occurring in at least one event includes one or more events.

Based on the above technical solution, the terminal device can perform event-triggered reporting, thereby avoiding the terminal device from reporting invalid measurement reports to the network device. In addition, the terminal device can report measurement reports related to one or more events that have occurred through first information in a predefined format, thereby avoiding resource waste caused by allocating corresponding reporting resources for each event when the terminal device supports or is configured with multiple events.

In combination with the third aspect, in certain implementations of the third aspect, the first information includes at least one public field and at least one non-public field, at least one public field corresponds one-to-one to at least one public reporting parameter, and at least one non-public field corresponds one-to-one to at least one non-public reporting parameter. The public reporting parameter is a reporting parameter with the same value included in measurement reports related to at least two events in at least one event, and the non-public reporting parameter is a reporting parameter with different values included in measurement reports related to different events in at least one event.

It should be understood that if the measurement report related to the event occurring in at least one event does not include the first public reporting parameter, the public field corresponding to the first public reporting parameter is a predefined value. If the measurement report related to the event occurring in at least one event includes the first public reporting parameter, the public field corresponding to the first public reporting parameter carries the first public reporting parameter.

It should also be understood that if the measurement report related to the event occurring in at least one event does not include the first non-public reporting parameter, the non-public field corresponding to the first non-public reporting parameter is a predefined value; or, if the measurement report related to the event occurring in at least one event includes the first non-public reporting parameter, the non-public field corresponding to the first non-public reporting parameter carries the first non-public reporting parameter.

In summary, the payload size of the first information is the payload size required to report at least one public reporting parameter and at least one non-public reporting parameter.

In combination with the third aspect, in some implementations of the third aspect, the first information includes at least one event field, and the at least one event field corresponds one-to-one to at least one event.

It should be understood that if event #p in at least one event does not occur, the event field corresponding to event #p is a predefined value; or, if event #p in at least one event occurs, the event field corresponding to event #p carries a measurement report related to event #p.

In summary, the payload size of the first information is the payload size required for reporting a measurement report related to at least one event.

In combination with the third aspect, in certain implementations of the third aspect, the first information includes measurement reports related to multiple events occurring in at least one event, and the measurement reports related to the multiple events are arranged in a first order.

In combination with the third aspect, in certain implementations of the third aspect, the first order is one of the following: order from large to small in the indexes of multiple events, order from small to large in the indexes of multiple events, or order from high to low in the priority of multiple events.

Based on the above technical solution and the first order, the network device can determine the events to which the multiple measurement reports reported by the terminal device respectively correspond.

In combination with the third aspect, in certain implementations of the third aspect, the first information includes a measurement report related to event #q occurring in at least one event, and the multiple reporting parameters included in the measurement report related to event #q are arranged in a predefined order.

Based on the above technical solution and the predefined order, the network device can determine which reporting parameters are included in the measurement report reported by the terminal device.

In combination with the third aspect, in certain implementations of the third aspect, at least one event includes at least one of the following: the first beam quality is less than or equal to the first preset threshold, the second beam quality is greater than or equal to the second preset threshold, the difference between the second beam quality and the first beam quality is greater than or equal to the third preset threshold, and the difference between the second beam quality and the first beam quality is less than or equal to the fourth preset threshold; wherein, the first beam represents a service beam, and the second beam represents a beam different from the service beam.

In combination with the third aspect, in certain implementations of the third aspect, a measurement report related to an event occurring in at least one event includes one or more of the following: an index of the first beam, the quality of the first beam, an index of the second beam, the quality of the second beam, information of the cell corresponding to the event-related measurement report, the reason why the quality of the first beam is lower than the threshold value, an index of a reference signal resource set, a reporting configuration index, information of an event occurring in at least one event, a capability index, and channel status information; wherein, the first beam is a service beam, and the second beam is a beam different from the first beam.

In a fourth aspect, a communication method is provided. This method 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 or chip system or circuit or communication module), which is not limited in this application. The following mainly uses network devices as an example for explanation.

The method includes: sending configuration information, the configuration information includes information of at least one event, and the at least one event is related to the measurement report reporting initiated by the terminal device; receiving first information, the first information includes all or part of the measurement report related to the event occurring in the at least one event.

In combination with the fourth aspect, in certain implementations of the fourth aspect, the first information includes at least one public field and at least one non-public field, at least one public field corresponds one-to-one to at least one public reporting parameter, and at least one non-public field corresponds one-to-one to at least one non-public reporting parameter. The public reporting parameter is a reporting parameter with the same value included in measurement reports related to at least two events in at least one event, and the non-public reporting parameter is a reporting parameter with different values included in measurement reports related to different events in at least one event.

In combination with the fourth aspect, in certain implementations of the fourth aspect, if the measurement report related to the event occurring in at least one event does not include a first public reporting parameter, the public field corresponding to the first public reporting parameter is a predefined value; or, if the measurement report related to the event occurring in at least one event includes a first public reporting parameter, the public field corresponding to the first public reporting parameter carries the first public reporting parameter.

In combination with the fourth aspect, in certain implementations of the fourth aspect, if the measurement report related to the event occurring in at least one event does not include the first non-public reporting parameter, the non-public field corresponding to the first non-public reporting parameter is a predefined value; or, if the measurement report related to the event occurring in at least one event includes the first non-public reporting parameter, the non-public field corresponding to the first non-public reporting parameter carries the first non-public reporting parameter.

In combination with the fourth aspect, in some implementations of the fourth aspect, the first information includes at least one event field, and the at least one event field corresponds one-to-one to at least one event.

In combination with the fourth aspect, in certain implementations of the fourth aspect, if event #p in at least one event does not occur, the event field corresponding to event #p is a predefined value; or, if event #p in at least one event occurs, the event field corresponding to event #p carries a measurement report related to event #p.

In combination with the fourth aspect, in certain implementations of the fourth aspect, the first information includes measurement reports related to multiple events occurring in at least one event, and the measurement reports related to the multiple events are arranged in a first order.

In combination with the fourth aspect, in certain implementations of the fourth aspect, the first order is one of the following: order from large to small in the indexes of multiple events, order from small to large in the indexes of multiple events, or order from high to low in the priority of multiple events.

In combination with the fourth aspect, in certain implementations of the fourth aspect, the first information includes a measurement report related to event #q occurring in at least one event, and the multiple reporting parameters included in the measurement report related to event #q are arranged in a predefined order.

In combination with the fourth aspect, in certain implementations of the fourth aspect, at least one event includes at least one of the following: the first beam quality is less than or equal to the first preset threshold, the second beam quality is greater than or equal to the second preset threshold, the difference between the second beam quality and the first beam quality is greater than or equal to the third preset threshold, and the difference between the second beam quality and the first beam quality is less than or equal to the fourth preset threshold; wherein, the first beam represents a service beam, and the second beam represents a beam different from the service beam.

In combination with the fourth aspect, in certain implementations of the fourth aspect, a measurement report related to an event occurring in at least one event includes one or more of the following: an index of the first beam, the quality of the first beam, an index of the second beam, the quality of the second beam, information of the cell corresponding to the event-related measurement report, the reason why the quality of the first beam is lower than the threshold value, an index of a reference signal resource set, a reporting configuration index, information of an event occurring in at least one event, a capability index, and channel state information; wherein, the first beam is a service beam, and the second beam is a beam different from the first beam.

Regarding the beneficial effects and possible designs of the fourth aspect, please refer to the relevant description in the third aspect and will not be repeated here.

In a fifth aspect, a communication device is provided, the device being configured to execute the method of any possible implementation of the first to fourth aspects. Specifically, the device may include units and/or modules, such as a processing unit and/or a communication unit, configured to execute the method of any possible implementation of the first to fourth aspects.

In one implementation, the apparatus is a communication device (e.g., a terminal device or a network device). When the apparatus is a communication device, the communication unit may be a transceiver or an input/output interface; the processing unit may be at least one processor. Alternatively, the transceiver may be a transceiver circuit. Alternatively, the input/output interface may be an input/output circuit.

In another implementation, the device is a chip, chip system, circuit, or communication module for a communication device (e.g., a terminal device or a network device). When the device is a chip, chip system, or circuit for a communication device, 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; and the processing unit may be at least one processor, processing circuit, or logic circuit.

In a sixth aspect, a communication device is provided, comprising: at least one processor configured to execute a computer program or instruction to perform the method of any possible implementation of aspects 1 to 4. Optionally, the device further comprises a memory configured to store the computer program or instruction. Optionally, the device further comprises a communication interface coupled to the processor and configured to input the computer program or instruction into the processor, or output information from the processor.

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

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

In a seventh aspect, a processor is provided for executing the method provided in any one of the first to fourth aspects above.

For the operations such as sending and acquiring/receiving involved in the processor, unless otherwise specified, or if they do not conflict with their actual functions or internal logic in the relevant descriptions, they can be understood as processor output, reception, input and other operations, and can also be understood as sending and receiving operations performed by the radio frequency circuit and antenna. This application does not limit this.

Optionally, the device further includes: a memory for storing programs; accordingly, at least one processor is used to execute computer programs or instructions in the memory.

Optionally, the device further includes a communication interface, which is coupled to the processor and can be used to input information to the processor or output information from the processor.

In an eighth aspect, a computer-readable storage medium is provided, which stores a program code for execution by a device, wherein the program code includes a method for executing any possible implementation of the first to fourth aspects above.

In a ninth aspect, a computer program product comprising instructions is provided, which, when run on a computer, enables the computer to execute the method in any possible implementation of the first to fourth aspects above.

In the tenth aspect, a chip is provided, which includes a processor and a communication interface. The processor reads instructions on the memory through the communication interface and executes the method provided by any of the above-mentioned implementation methods of any of the above-mentioned first to fourth aspects.

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

Optionally, as an implementation method, the chip also includes a memory, in which a computer program or instruction is stored, and the processor is used to execute the computer program or instruction on the memory. When the computer program or instruction is executed, the processor is used to execute the method provided in any one of the above-mentioned implementation methods of any one of the first to fourth aspects.

In the eleventh aspect, a computer program product comprising instructions is provided, which, when run on a computer, enables the computer to execute the method provided in any one of the above-mentioned implementations of the first to fourth aspects.

In a twelfth aspect, a communication system is provided, comprising the aforementioned terminal device and network device.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG1 is a schematic diagram of a wireless communication system applicable to an embodiment of the present application.

FIG2 is a schematic diagram of another example of the architecture of a mobile communication system applied in an embodiment of the present application.

FIG3 is another schematic diagram of a wireless communication system applicable to an embodiment of the present application.

FIG4 is a schematic diagram of beam management applicable to an embodiment of the present application.

FIG5 is a schematic diagram of a communication method 500 provided in an embodiment of the present application.

FIG6 is a schematic diagram of a communication method 600 provided in an embodiment of the present application.

FIG7 is a schematic diagram of a communication device 700 provided in an embodiment of the present application.

FIG8 is a schematic diagram of another communication device 800 provided in an embodiment of the present application.

FIG9 is a schematic diagram of a chip system 900 provided in an embodiment of the present application.

DETAILED DESCRIPTION

The technical solution in this application will be described below with reference to the accompanying drawings.

The technical solutions provided in this application can be applied to various communication systems, such as fifth-generation (5G) or new radio (NR) systems, long-term evolution (LTE) systems, LTE frequency division duplex (FDD) systems, LTE time division duplex (TDD) systems, wireless local area network (WLAN) systems, satellite communication systems, future communication systems, or integrated systems of multiple systems. The technical solutions provided in this application can also 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 or other communication systems.

The technical solution provided in this application can also be applied to non-terrestrial communication network (NTN) systems such as intersatellite communication and satellite communication. As an example, a satellite communication system includes a satellite base station and a terminal device. The satellite base station provides communication services for the terminal device. The satellite base station can also communicate with other base stations. A satellite can be used as a base station or as a terminal device. Among them, a satellite can refer to a drone, a hot air balloon, a low-orbit satellite, a medium-orbit satellite, a high-orbit satellite, etc. A satellite can also refer to a non-ground base station or non-ground equipment, etc.

A device in a communication system can send a signal to another device or receive a signal from another device. The signal may include information, signaling, or data, etc. The device can also be replaced by an entity, a network entity, a communication device, a mobile device, a network element, a communication module, a node, a communication node, a communication device, etc. The present disclosure uses the device as an example for description. For example, a communication system may include at least one terminal device and at least one network device. The network device can send a downlink signal to the terminal device, and/or the terminal device can send an uplink signal to the network device. It is understandable that the terminal device in the present disclosure can be replaced by a first communication device, and the network device can be replaced by a second communication device, and the two perform the corresponding communication method in the present disclosure. Alternatively, the corresponding communication method in the present disclosure can be applied between network devices, or between terminal devices, which is not limited here.

The terminal device in the embodiment of the present application can be a device or module that is connected to the above-mentioned communication system and has corresponding communication functions. The terminal device may include various devices with wireless communication functions, which can be used to connect people, objects, machines, etc. The terminal device can be widely used in various scenarios, such as: cellular communication, D2D, V2X, end-to-end (peer to peer), M2M, MTC, IoT, virtual reality (VR), augmented reality (AR), industrial control, autonomous driving, telemedicine, smart grid, smart furniture, smart office, smart wearable, smart transportation, smart city drones, robots, remote sensing, passive sensing, positioning, navigation and tracking, autonomous delivery and other scenarios. The terminal device can be a terminal in any of the above scenarios, such as an MTC terminal, an IoT terminal, etc. The terminal device can be a user equipment (UE) of the 3rd Generation Partnership Project (3GPP) standard, a terminal, a fixed device, a mobile station device or a mobile device, a subscriber unit, a handheld device, a vehicle-mounted device, a wearable device, a cellular phone, a smart phone, a Session Initiation Protocol (SIP) phone, a wireless data card, a personal digital assistant (PDA), or a wireless data card. DA), computer, tablet computer, notebook computer, wireless modem, handheld device (handset), laptop computer, computer with wireless transceiver function, smart book, vehicle, satellite, global positioning system (GPS) device, target tracking device, aircraft (such as drone, helicopter, multi-copter, quadcopter, or airplane, etc.), ship, remote control device, smart home device, industrial equipment, transportation vehicle with wireless communication function, communication module, roadside unit (RSU) with terminal function, or device built into the above devices (such as communication module, modem or chip in the above devices, etc.), or other processing equipment connected to the wireless modem. For the convenience of description, the terminal device will be described below as a terminal or UE as an example.

It should be understood that in some scenarios, a UE can also be used to act as a base station. For example, a UE can act as a scheduling entity that provides sidelink signals between UEs in scenarios such as V2X, D2D, or end-to-end.

In the embodiments of the present application, the device for realizing the function of the terminal device can be a terminal device, or a device capable of supporting the terminal device to realize the function, such as a chip system, which can be installed in the terminal device or used in combination with the terminal device. In the embodiments of the present application, the chip system can be composed of a chip, or it can include a chip and other discrete devices. In the embodiments of the present application, only the terminal device is used as an example for description, and the embodiments of the present application are not limited to the solutions of the embodiments of the present application.

The network device in the embodiments of the present application may be a device or module having corresponding communication functions. The network device may be a device for communicating with a terminal device. The network device may also be referred to as an access network device or a wireless access network device. For example, the network device may be a base station. The network device in the embodiments of the present application may refer to a radio access network (RAN) node (or device) that connects a terminal device to a wireless network. The term "base station" may broadly cover various names as follows, or interchangeably with the following names, such as: NodeB, evolved NodeB (eNB), next generation NodeB (gNB), relay station, access point, transmitting and receiving point (TRP), transmitting point, master station, auxiliary station, motor slide retainer (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 may be a macro base station, a micro base station, a relay node, a donor node, or the like, or a combination thereof. A base station may also refer to a communication module, modem, or chip used to be installed in the aforementioned equipment or devices. A base station may also be a mobile switching center, a device that performs base station functions in D2D, V2X, and M2M communications, or a device that performs base station functions in future communication systems. A base station may support networks with the same or different access technologies. The embodiments of this application do not limit the specific technologies and device forms used by network devices.

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 based on the location of the mobile base station. In other examples, a helicopter or drone can be configured to act as a device that communicates with another base station.

In some deployments, the network devices mentioned in the embodiments of the present application may include a CU, a DU, or both a CU and a DU, or a device including a control plane CU node (central unit-control plane (CU-CP)), a user plane CU node (central unit-user plane (CU-UP)), and a DU node. For example, the network devices may include a gNB-CU-CP, a gNB-CU-UP, and a gNB-DU.

In some deployments, multiple RAN nodes collaborate to assist terminals in achieving wireless access, with different RAN nodes implementing portions of the base station's functionality. For example, a RAN node can be a CU, DU, CU-CP, CU-UP, or radio unit (RU). The CU and DU can be separate or included in the same network element, such as the BBU. The RU can be included in a radio frequency device or radio unit, such as an RRU, AAU, or RRH.

In some deployments, the CU is a logical node that carries the radio resource control (RRC), service data adaptation protocol (SDAP), packet data convergence protocol (PDCP), and other control functions of access network equipment. The CU connects to network nodes, such as the core network, through interfaces such as the E2 interface. Optionally, the CU incorporates some core network functionality. 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 such as the F1 interface. 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 of the F1 interface and, in some examples, defines the F1 signaling process. The F1 interface supports the control plane (F1-C) and the user plane (F1-U).

In some deployments, the CU can be split into the CU-CP and the CU-UP. The CU-CP is a logical node that carries the RRC layer and the control plane part of PDCP (PDCP-C) layer, and is used to implement the control plane functions of the CU. The CU-CP can interact with network elements in the core network that implement control plane functions. The network elements in the core network that implement control plane functions can be access and mobility function network elements. The CU-UP is a logical node that carries the SDAP layer and the user plane part of PDCP (PDCP-U) layer, and is used to implement the user plane functions of the CU. The CU-UP can interact with network elements in the core network that implement user plane functions. The network elements in the core network that implement user plane functions. The above CU and DU configurations are only examples. The functions of the CU and DU can also be configured as needed. For example, the CU or DU can be configured to have the functions of more protocol layers, or the CU or DU can be configured to have partial processing functions of the protocol layers. For example, some functions of the RLC layer and the functions of the protocol layers above the RLC layer are placed in the CU, while the remaining functions of the RLC layer and the functions of the protocol layers below the RLC layer are placed in the DU. For another example, the functions of the CU or DU can be divided according to service type or other system requirements. For example, according to latency, functions that need to meet a smaller latency requirement are placed in the DU, while functions that do not need to meet this latency requirement are placed in the CU.

In some deployments, the DU is a logical node that carries the RLC 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. The DU connects to the RU through some interface, which can be a fronthaul interface. In some examples, the Higher PHY layer includes some of the physical (PHY) layer processing, such as forward error correction (FEC) encoding and decoding, scrambling, modulation, and demodulation.

In some deployments, the RU is the logical node that carries the lower physical layer (Lower PHY) and radio frequency (RF) processing. In some examples, the RU can be a TRP or RRH or other similar entity. In some examples, the Low-PHY includes parts 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 over a wireless link.

The DU and RU may or may not be co-located. The DU and RU exchange control plane information and user plane information via the lower-layer split - control, user and synchronization (LLS-CUS) interface over the fronthaul link. The LLS-CUS may include interfaces and interfaces that provide the control plane and user plane, respectively. In some examples, the control plane refers to real-time control between the DU and RU. The DU and RU have an interface on the fronthaul link (such as the so-called LLS-M interface) to exchange management information, and the management plane (M-Plane) refers to non-real-time management operations between the DU and RU.

The DU and RU can work together to implement the functions of the PHY layer. A DU can be connected to one or more RUs. The functions of the DU and RU can be configured in various ways according to the design. For example, the DU is configured to implement the baseband function, and the RU is configured to implement the mid-RF function. For another example, the DU is configured to implement the high-layer functions in the PHY layer, and the RU is configured to implement the low-layer functions in the PHY layer or to implement the low-layer functions and the RF functions. The high-layer functions in the physical layer may include a part of the functions of the physical layer, which is closer to the MAC layer, and the low-layer functions in the physical layer may include another part of the functions of the physical layer, which is closer to the mid-RF side.

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

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 meanings. For example, the radio access network may also be an open radio access network (O-RAN) architecture. In the O-RAN system, the CU may be called an open CU (openCU, O-CU), the DU may be called an open DU (open DU, O-DU), the CU-CP may be called an open CU (open CU-CP, O-CU-CP), the CU-UP may be called an open CU (open CU-UP, O-CU-UP), and the RU may be called an open RU (openRU, O-RU). Any of the CU (or CU-CP, CU-UP), DU and RU in this application may be implemented by a software module, a hardware module, or a combination of a software module and a hardware module.

In the embodiment of the present application, the device for realizing the function of the network device may be a network device, or a device capable of supporting the network device to realize the function, such as a chip system or a chip or a circuit or a communication module (i.e., a communication module that performs a communication function), and the device may be installed in the network device. In the embodiment of the present application, the chip system may be composed of a chip, or may include a chip and other discrete devices. In addition, program instructions for performing corresponding communication functions may also be configured in the device. In the embodiment of the present application, only the device for realizing the function of the network device is used as an example for explanation, and the solution of the embodiment of the present application is not limited.

Network devices and terminal devices can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on the water surface; they can also be deployed on aircraft, balloons and satellites in the air. The embodiments of this application do not limit the scenarios in which network devices and terminal devices are located. In addition, terminal devices and network devices can be hardware devices, or they can be software functions running on dedicated hardware, software functions running on general-purpose hardware, such as virtualization functions instantiated on a platform (e.g., a cloud platform), or entities including dedicated or general-purpose hardware devices and software functions. This application does not limit the specific forms of terminal devices and network devices.

First, a communication system applicable to the embodiments of the present application is briefly introduced as follows.

As shown in FIG1 , the communication system 100 may include one or more network devices, such as the network device 101 shown in FIG1 . The communication system 100 may also include one or more terminal devices, such as the terminal device 102, the terminal device 103, and the terminal device 104 shown in FIG1 . The communication system 100 may support sidelink communication technology, such as sidelink communication between the terminal device 102 and the terminal device 103, and sidelink communication between the terminal device 102 and the terminal device 104.

It should be understood that Figure 1 is only a schematic diagram, and the communication system may also include other network devices, such as core network device 105 and wireless relay devices and wireless backhaul devices not shown in Figure 1. The embodiments of the present application do not limit the number of network devices and terminal devices included in the mobile communication system.

The communication between the network device 101 and the terminal device 102 in the communication system shown in FIG1 can also be represented in another form.

As shown in Figure 2, terminal device 102 includes a processor 121, a memory 122, and a transceiver 123. Transceiver 123 includes a transmitter 1231, a receiver 1232, and an antenna 1233. Receiver 1232 can be configured to receive transmission control information via antenna 1233, and transmitter 1231 can be configured to send transmission feedback information to network device 101 via antenna 1233. Network device 101 includes a processor 111, a memory 112, and a transceiver 113. Transceiver 113 includes a transmitter 1131, a receiver 1132, and an antenna 1133. Transmitter 1131 can be configured to send transmission control information to terminal device 102 via antenna 1133, and receiver 1132 can be configured to receive transmission feedback information sent by terminal device 102 via antenna 1133.

The embodiments of the present application can also be applied to an open RAN (O-RAN) system architecture.

As shown in Figure 3, the O-RAN system may include core network (CN) equipment, access network equipment (RAN) and terminal equipment (UE). The access network equipment communicates with the core network equipment through a backhaul link and communicates with the terminal equipment through an air interface. For example, the BBU in the access network equipment communicates with the core network equipment through a backhaul link, and the RU in the access network equipment communicates with the terminal equipment through an air interface. The BBU communicates with at least one RU through a fronthaul link. The BBU and RU may or may not be co-located. The BBU includes at least one CU and at least one DU. The CU and DU may communicate through at least one midhaul link.

FIG3 is only a schematic diagram. The wireless communication system may also include other devices, which are not shown in FIG3 .

In order 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.

1. Beam: A communication resource. Different beams can be considered different resources. Different beams can send the same or different information.

In the NR protocol, a beam can be represented by a spatial domain filter, also known as a spatial filter, or a spatial domain parameter, spatial parameter, spatial domain setting, spatial setting, or quasi-colocation (QCL) information, QCL assumption, or QCL indication. A beam can be indicated by a transmission configuration indicator (TCI) state (TCI-state or TCIstate) parameter or a spatial relation parameter. Therefore, in this application, beam can be replaced by spatial filter, spatial filter, spatial parameter, spatial parameter, spatial setting, spatial setting, QCL information, QCL assumption, QCL indication, TCI-state (DL TCI-state, UL TCI-state), spatial relation, etc. The above terms are also equivalent to each other. Beam can also be replaced by other terms representing beam, which is not limited in this application.

A beam used to transmit signals may be called a transmission beam (Tx beam), a spatial domain transmission filter, a spatial transmission filter, a spatial domain transmission parameter, a spatial transmission parameter, a spatial domain transmission setting, or a spatial transmission setting. The downlink transmit beam may be indicated by the TCI-state.

The beam used to receive signals can be called a reception beam (Rx beam), or can also be called a spatial domain reception filter, spatial reception filter, spatial domain reception parameter, spatial reception parameter, spatial domain reception setting, or 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 beam, SRS resource, and uplink TCI state are interchangeable.

The transmit beam may refer to the distribution of signal strength in different directions in space after the signal is transmitted by the antenna, and the receive beam may refer to the distribution of signal strength in different directions in space of the wireless signal received from the antenna.

Furthermore, the beam can be a wide beam, a narrow beam, or other types of beams. The beam forming technology can be beamforming technology or other technologies. The beamforming technology can specifically be digital beamforming technology, analog beamforming technology, or hybrid digital/analog beamforming technology.

Beams generally correspond to resources. For example, during beam measurement, network equipment uses different resources to measure different beams. The terminal device then provides feedback on the measured resource quality, allowing the network equipment to determine the quality of the corresponding beam. During data transmission, beam information is also indicated by its corresponding resource. For example, the network equipment uses the TCI field in the downlink control information (DCI) to indicate the physical downlink shared channel (PDSCH) beam information to the terminal device.

Optionally, multiple beams with the same or similar communication characteristics can be considered a single beam. A beam can include one or more antenna ports for transmitting data channels, control channels, and sounding signals. The one or more antenna ports forming a beam can also be considered an antenna port set.

2. Reference signal (RS): This signal can also be called a pilot, reference sequence, or base signal. For consistency, the following description uses the term "reference signal." Reference signals can be used for channel measurement or estimation.

The channel measurement involved in this application also includes beam measurement, that is, obtaining beam quality information by measuring the reference signal. As an example, the 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-noise ratio). In the embodiments of this application, for the convenience of explanation, unless otherwise specified, the channel measurement involved can be regarded as beam measurement.

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

In addition, 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. The handover candidate cell can be the current serving cell or a non-serving cell. The physical cell identifier (PCI) of the handover candidate cell is different from the current primary cell (PCell). In addition, the reference signal can also be a reference signal associated with an additional PCI (additional PCI), that is, a reference signal of a neighboring cell.

The terminal device may be configured with one or more candidate cell configurations, and the configuration of each candidate cell may include a configuration of reference signal resources.

3. Reference signal resources: can be used to configure the transmission properties of reference signals.

Typically, reference signals are configured as resources. Network equipment can configure each reference signal as a resource to a terminal device. A resource is a configuration information unit that typically includes parameters related to a reference signal, such as the reference signal's time-frequency resource location, number of ports, and time domain type (periodic, semi-static, or aperiodic). Transmitting devices can send reference signals based on the reference signal resources, and receiving devices can receive reference signals based on the reference signal resources.

In order to distinguish different reference signal resources, each reference signal resource may correspond to a reference signal resource identifier (or reference signal resource indication, or reference signal resource indicator), for example, a CSI-RS resource identifier (or CSI-RS resource indicator (CSI-RS resource indicator, CRI)), an SSB resource identifier (SSB resource indicator (SSB resource indicator, SSBRI)), or an SRS resource identifier (or SRS resource indicator (SRS resource indicator, SRI)).

4. TCI-state (used to indicate downlink beam):

Network devices can generate different beams pointing in different transmission directions. In 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 transmit beam information it uses. This allows the terminal device to use the receive beam corresponding to the transmit beam to receive the data sent by the network device. One possible method is for the network device to indicate to the terminal device the relevant information about the transmit beam it uses through the TCI (transmission configuration indication) field in the DCI.

For example, the TCI field size is 3 bits (bits), which can specifically represent 8 different field values (codepoints). Each value of the TCI field corresponds to a TCI-state index, and the TCI-state index can uniquely identify a TCI-state. The TCI-state includes several parameters, through which the relevant information of the transmitted beam can be determined. The TCI-state is configured by the network device to each terminal device. The structure of the TCI-state is shown below. Each TCI-state includes its own index TCI state identifier (tci-StateId) and two QCL information (QCL-Info). Each QCL-Info includes a cell field and a bandwidth part (BWP) identifier (ID), which respectively indicate which BWP of which cell the TCI-state applies to. That is, different cells or different BWPs of the same cell can be configured with different QCL-Info. The QCL-Info also includes a reference signal (referenceSignal) field, which is used to indicate which reference signal resource forms the QCL relationship between the beam indicated by the TCI-state. In data transmission and channel measurement, beams correspond to reference signal resources, and one beam corresponds to one reference signal resource. Therefore, when we say here that the beam indicated by TCI-state forms a QCL relationship with which reference signal resource, it actually means that the beam indicated by TCI-state forms a QCL relationship with which beam. A QCL relationship means that two reference signal resources (or two antenna ports, where antenna ports and reference signal resources also correspond one to one) have certain identical spatial parameters. Which specific spatial parameters are the same depends on the type of the QCL-Info, that is, another field of QCL-Info, QCL type (qcl-Type). qcl-Type can have four values {type (type) A, typeB, typeC, typeD}. Taking typeD as an example, typeD indicates that the two reference signal resources have the same spatial reception parameter information, that is, the two beams have the same receiving beam. At most one of the two QCL-Info included in TCI-state can be TypeD.

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

TCI-state configuration: The network device configures multiple TCI-states to the terminal device through RRC signaling. These TCI-states all include a QCL-Info of type D. The network device can also configure TCI-states that do not include QCL-Info of type D, without limitation.

TCI-state activation: After a network device is configured with multiple TCI-states, it must activate eight of them using a MAC control element (CE) (MACCE). These eight TCI-states correspond one-to-one to the eight values of the TCI field in the DCI. The TCI-states corresponding to the eight values of the DCI TCI field are determined through MAC CE signaling. The specific format of MACCE signaling is described in the protocol and is not specified.

TCI-state indication: The network device indicates a specific TCI-state through the TCI field in the DCI. For example, the value of the TCI field in the DCI sent by the network device to the terminal device is 000, indicating the TCI-state corresponding to 000 adopted by the data transmission beam. The reference signal contained in the QCL-Info of type D in the TCI-state is the reference signal with an index of #1 (such as CSI-RS), indicating that the beam used for data transmission is the same as the receiving beam corresponding to the CSI-RS with an index of #1. The receiving beam corresponding to the CSI-RS with an index of #1 can be determined through the beam measurement process 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 adopt the corresponding receiving beam to receive data.

5. Spatial relation (used to indicate uplink beam)

In one possible implementation, the transmit beam for uplink transmission is indicated by a spatial relation, which functions similarly to a TCI-state and is used to inform the terminal device which transmit beam to use for uplink transmission.

Spatial relations also need to be configured through RRC signaling. Its configuration structure may include the spatial relation ID, cell ID, target reference signal resource, path loss measurement reference signal, power control parameters, etc. The target reference signal resource (which can be one of SRS/SSB/CSI-RS) is used to indicate the corresponding uplink beam. If uplink transmission uses spatial relation #1, and this spatial relation #1 includes a target reference signal resource #2, this indicates that the transmit beam used for uplink transmission is the transmit/receive beam of target reference signal resource #2. For example, if target reference signal resource #2 is an uplink SRS resource, this indicates that the transmit beam used for uplink transmission is the transmit beam of this SRS (the transmit beam of this SRS is known). For another example, if target reference signal resource #2 is a downlink resource such as SSB/CSI-RS, this indicates that the transmit beam used for uplink transmission is the receive beam of this SSB/CSI-RS (the receive beam of this SSB/CSI-RS is known).

Network equipment can configure multiple spatial relations for terminal devices. One of these relations is then activated through MAC CE for the corresponding data transmission. Uplink transmission includes the physical uplink control channel (PUCCH), SRS, and physical uplink shared channel (PUSCH). All of these uplink transmissions require the configuration of corresponding spatial relations. The spatial relation of the PUCCH is indicated through MAC-CE signaling. The spatial relation of the SRS is also indicated through MAC CE signaling. During PUSCH transmission, a specific SRS is associated and the spatial relation of that SRS is used for transmission.

6. Unified TCI: It is a unified beam indication framework. The network device can indicate a beam to the terminal device, and the beam is used for multiple channels and/or reference signals at the same time. The common beam can be an uplink common beam, a downlink common beam, or an uplink and downlink common beam. The terminal device can use the common beam in subsequent transmissions. That is, the network device can indicate an uplink common beam to the terminal device for the transmission of multiple uplink channels and/or uplink reference signals. It can also indicate a downlink common beam to the terminal device for the transmission of multiple downlink channels and/or downlink reference signals. It can also indicate an uplink and downlink common beam to the terminal device 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 and downlink common beams can be used for both uplink and downlink transmissions.

As an example, the terminal device may be configured with two TCI-states, namely downlink (DL) or joint TCI (DL or joint TCI) and uplink (UL) TCI (UL TCI).

For example, the terminal device is configured with both joint/DL TCI-state (e.g., up to 128) and ULTCI-state (e.g., up to 64).

For example, in the serving cell configuration of RRC signaling, the network device can configure the UE's current TCI mode to be joint or separate. In joint mode, a joint TCI-state is indicated for both uplink and downlink transmissions. In separate mode, the network device indicates the DL TCI-state and UL TCI-state for each, respectively.

When the terminal device receives the TCI-state activation signaling indicated by MACCE, the activation signaling includes the ID of the TCI-state. The terminal device determines which TCI is activated by MACCE based on the RRC configuration.

7. Beam management: For example, it includes beam measurement, such as measuring based on reference signals to determine the beam with better quality.

5G can utilize high-frequency communication, that is, ultra-high frequency band signals to transmit data. A major issue with high-frequency communication is that signal energy decreases dramatically with transmission distance, resulting in a short transmission distance. To overcome this problem, high-frequency communication uses simulated beam technology. By weighting the antenna array, the signal energy is concentrated within a smaller angular range, forming a signal similar to a light beam (called a simulated beam, or simply beam), thereby increasing the transmission distance. Both network equipment and terminal devices use beams for transmission. Specifically, specific beams are used for uplink and downlink data transmission between network equipment and terminal devices. Currently, beam management first performs coarse beam alignment based on the SSB, and then fine-tunes the beam based on the CSI-RS. The following describes the possible beam management process with reference to Figure 4.

See FIG. 4 , which is a schematic diagram of beam management applicable to an embodiment of the present application.

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

Phase 1: Coarse beam alignment between the network device and the terminal device, as shown in (a) in Figure 4.

Specifically, the network device performs network device beam scanning based on SSB, that is, the network device sends beams in different directions at different times to complete the broadcast beam coverage of the cell. At the same time, the terminal device scans the receive beam, that is, the terminal device also uses different beams for reception at different times. The terminal device determines the network device beam and the terminal device beam based on the received signal strength. For example, the network device beam is the beam with a received signal strength above a certain threshold (or called the optimal beam) among multiple beams, and the terminal device beam is the beam with a received signal strength above a certain threshold (or called the optimal beam) among multiple beams.

Phase 2: Network equipment beam fine-tuning, as shown in (b) in Figure 4.

Specifically, the network device determines the candidate beam based on the optimal network device beam obtained in stage 1, scans it through CSI-RS, and the terminal device receives it using the receiving beam selected in stage 1, thereby fine-tuning the network device beam to determine the network device beam with the highest signal strength (or called the optimal network device beam).

Phase 3: Fine-tuning of the terminal device beam, as shown in (c) in Figure 4.

Specifically, the network device transmits the CSI-RS using the optimal beam obtained in Phase 2, and the terminal device scans the beams to determine the terminal device beam with the highest signal strength (or the optimal terminal device beam), completing beam alignment. The process is similar to Phase 2.

Among them, stage 1, stage 2, and stage 3 are only examples, and the embodiments of the present application are not limited thereto. In implementation, a system does not necessarily need to implement all of the above processes. For example, it can only implement the processes of stage 1 and stage 2, and leave the determination of the receiving beam on the terminal device side to the terminal device.

8. Measurement Result Reporting: Currently, network devices can be configured with three measurement result reporting (also known as beam reporting, beam measurement result reporting, or CSI reporting) processes based on the reporting time domain configuration behavior: periodic reporting, semi-persistent reporting, and aperiodic reporting. The following briefly describes these.

1) Periodic Reporting: First, the network device configures periodic reference signal measurement. This means the network device periodically sends measurement reference signals to the terminal device, which then measures these reference signals and periodically reports the results. After the configuration signaling takes effect, the terminal device periodically reports measurement reports. To terminate the measurement reporting process, the terminal device can send RRC signaling to release the relevant configuration parameters for the measurement reporting process.

2) Semi-continuous reporting: One is that the reference signal measurement is periodic, and the measurement result reporting is semi-continuous. First, the network device can configure a periodic reference signal, that is, the network device periodically sends a measurement reference signal to the terminal device, and the terminal device measures these reference signals. When the terminal device receives the activation signaling of the network device (such as MAC CE signaling, or DCI signaling), the terminal device will continuously and periodically report the measurement results. Of course, the network device can also send a deactivation signaling to the terminal device to deactivate the semi-continuous reporting process. The other is that both the reference signal measurement and the measurement result reporting are semi-continuous. When the terminal device receives the activation signaling of the network device (such as MAC CE signaling, or DCI signaling), the terminal device will continuously and periodically measure the reference signal and report the measurement results. When the terminal device receives the deactivation signaling sent by the network device, the terminal device stops the continuous reporting.

3) Non-periodic reporting: This reporting is performed only after the terminal device receives a trigger signaling sent by the network device. After the reporting is completed, the terminal device will stop reporting, which is a one-time reporting.

The above-mentioned measurement result reporting is either periodic or semi-continuous or non-periodic reporting triggered by the indication signaling sent by the network device, that is, the timing of the reporting is determined by the network device. This method leads to a large overhead of uplink resources. Specifically, in periodic and semi-continuous measurement reporting, the terminal device needs to report the measurement results every other period, and these measurement results may be meaningless to the network device. For example, there is no difference between the current measurement result and the last reported measurement result (the optimal beam has not changed), and reporting such a measurement result is meaningless, resulting in a waste of uplink resources.

Based on this, beam reporting triggered by terminal devices or events is introduced. Specifically, terminal devices can report based on event triggers, and different events may trigger different reporting contents.

Before introducing the solution of this application, the following points are explained.

(1) In this application, “indication” may include direct indication, indirect indication, explicit indication, and implicit indication. When describing that a certain indication information is used to indicate A, it can be understood that the indication information carries A, directly indicates A, or indirectly indicates A.

In this application, the information indicated by the indication information is referred to as the information to be indicated. In the specific implementation process, there are many ways to indicate the information to be indicated, such as but not limited to, the information to be indicated can be directly indicated, such as the information to be indicated itself or the index of the information to be indicated. The information to be indicated can also be indirectly indicated by indicating other information, wherein there is an association between the other information and the information to be indicated. It is also possible to indicate only a part of the information to be indicated, while the other parts of the information to be indicated are known or agreed in advance. For example, the indication of specific information can also be achieved with the help of the arrangement order of each information agreed in advance (for example, stipulated by the protocol), thereby reducing the indication overhead to a certain extent. In addition, the information to be indicated can be sent together as a whole, or it can be divided into multiple sub-information and sent separately, and the sending period and/or sending time of these sub-information can be the same or different.

(2) In this application, "sending" and "receiving" indicate the direction of signal transmission. For example, "sending information to XX" can be understood as the destination of the information being XX, which can include direct sending through the air interface, and also include indirect sending through the air interface by other units or modules. "Receiving information from YY" can be understood as the source of the information being YY, which can include direct receiving from YY through the air interface, and also include indirect receiving from YY through the air interface from other units or modules. "Sending" can also be understood as the "output" of the chip interface, and "receiving" can also be understood as the "input" of the chip interface. In other words, sending and receiving can be carried out between devices, for example, between a network device and a terminal device, or can be carried out within a device, for example, sending or receiving between components, modules, chips, software modules or hardware modules within the device through a bus, a line or an interface.

(3) In the various embodiments of this application, unless otherwise specified or there is a logical conflict, the terms and/or descriptions between different embodiments are consistent and can be referenced by each other. The technical features in different embodiments can be combined to form new embodiments based on their inherent logical relationships.

(4) In this application, the terms "first" and "second" are used for convenience of description only and are not intended to limit the scope of the embodiments of this application. They are not used to describe the order or precedence of features. It should be understood that the terms described in this manner may be interchangeable, where appropriate, to describe solutions other than the embodiments of this application.

(5) In this application, “predefined” may mean predefined by a standard protocol, or may also mean pre-agreed or pre-negotiated between devices.

(6) In this application, words such as "exemplarily" and "for example" are used to indicate examples, illustrations or descriptions. Any embodiment or design described in this application as an "example" should not be interpreted as being more preferred or more advantageous than other embodiments or designs. Specifically, the use of the word "example" is intended to present concepts in a concrete way. In the embodiments of this application, "of", "corresponding, relevant" and "corresponding" are sometimes used interchangeably. It should be noted that when the distinction between them is not emphasized, the meanings they intend to express are consistent.

The method provided by the embodiment of the present application is described in detail below with reference to the accompanying drawings. The embodiment provided by the present application can be applied to the communication system shown in FIG1 above without limitation.

In the following embodiments, terminal devices and network devices are used as examples for illustrative description. The terminal device can be replaced by a component of the terminal device (such as a chip or a chip system or a circuit or a communication module), and the network device can be replaced by a component of the network device (such as a chip or a chip system or a circuit or a communication module).

Referring to Figure 5, Figure 5 is a schematic diagram of a communication method 500 provided in an embodiment of the present application. The method 500 shown in Figure 5 may include the following steps.

Optionally, method 500 includes S501 and S502.

S501: A terminal device sends first indication information. Correspondingly, a network device receives the first indication information.

The first indication information indicates event information supported by the terminal device. The first indication information may also be referred to as terminal capability information.

Among them, the event represents an event related to a report initiated by a terminal device (UE initiated report), or an event related to a measurement report report initiated by a terminal device, or an event related to a report (or measurement report) after the terminal device actively measures, or a specific condition related to a measurement report report initiated by a terminal device. For example, the terminal device can actively perform measurements (such as beam measurements, or channel measurements, etc.), and thereby obtain a measurement report related to the event. For another example, the terminal device can perform measurements based on a reference signal according to the configuration of reference signal resources, and thereby obtain a measurement report related to the event. For another example, the terminal device actively measures and reports a measurement report related to the event when specific conditions are met. Among them, the event can also be referred to as any of the following: a trigger event, a layer 1 (layer 1, L1) trigger event, a CSI measurement report trigger event, a beam measurement report trigger event, an L1 CSI report trigger event, an L1 beam measurement report trigger event, etc., and the embodiments of the present application do not limit their naming.

In addition, as an example, an event-related report may be referred to as any of the following: an event-triggered or UE-initiated report, an event-triggered or UE-initiated beam report, an event-triggered or UE-initiated CSIreport, an event-triggered or UE-initiated beam measurement result report, an event-triggered or UE-initiated interference measurement report, an interference measurement report, a CSIreport, a beam measurement result report, etc.

Optionally, the first indication information indicates at least one of the following: whether the terminal device supports the capability of event triggering reporting, and the events supported by the terminal device.

Example 1: The first indication information indicates whether the terminal device supports the capability of event triggering reporting.

The event-triggered report may be an event-triggered beam report, CSI report, beam measurement result report, interference measurement report, etc., without limitation. As an example, the event-triggered report may also be referred to as a UE-initiated report.

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

Another possible implementation method is to indicate whether the terminal device supports the event-triggered reporting capability by reporting whether the terminal device supports the event-triggered reporting capability. For example, if the terminal device does not report the capability of not supporting event-triggered reporting, it can be assumed that the terminal device supports the event-triggered reporting capability. Alternatively, for example, if the terminal device does not report the capability of supporting event-triggered reporting, it can be assumed that the terminal device does not support the event-triggered reporting capability.

The above is an example, and the embodiments of the present application are not limited thereto. For example, whether a terminal device supports the capability of event triggering and reporting can also be indicated by a specific field. If the first indication information includes the specific field, it indicates that the terminal device supports the capability of event triggering and reporting; if the first indication information does not include the specific field, it indicates that the terminal device does not support the capability of event triggering and reporting.

Example 2: The first indication information indicates an event supported by the terminal device.

For example, the first indication information includes the indexes of various events supported by the terminal device.

For another example, the first indication information includes indexes of various event tables supported by the terminal device, and an event table includes one or more events.

For another example, the first indicated information includes the number of events supported by the terminal device.

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

S502: The terminal device receives configuration information. Correspondingly, the network device sends configuration information.

The configuration information includes information of X events, where X is an integer greater than 0. It should be understood that the X events may also be replaced by at least one event.

Regarding X events, there are three situations as follows.

In the first possible scenario, the X events are determined based on the first indication information. In other words, the X events are events supported by the terminal device, or in other words, the X events are events indicated by the terminal device via the first indication information. In this scenario, method 500 may not include S502, meaning that the network device may not configure information about the X events to the terminal device.

In the second possible scenario, the X events are configured by the network device, that is, the network device itself configures (or selects) the X events. In this case, the terminal device may be assumed to support all events or the X events. In this case, method 500 may not include S501, that is, the terminal device may not indicate the event information it supports to the network device.

In a third possible scenario, X events are determined based on the first indication information and events configured on 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 based on a combination of the at least one event configured on the network device and the at least one event supported by the terminal device.

The above three possible scenarios are for illustration only, and the embodiments of the present application are not limited thereto. For simplicity, the following description will be made using X events.

Optionally, the configuration information indicates indexes of X events. The terminal device may learn about the X events based on the configuration information.

For example, the configuration information includes an index of each of the X events.

For another example, the configuration information includes one or more event tables (or indexes of one or more event tables), and one event table includes one or more events. In this way, based on the index of the event table included in the configuration information, the events contained in the event table can be known.

For another example, the configuration information includes the value of X.

Further optionally, the method 500 further includes: the network device sends activation signaling to the terminal device to activate part or all of the configured events (ie, X events).

Further optionally, the method 500 further includes: the network device sends a deactivation signaling to the terminal device, for deactivating some or all of the configured events (ie, X events).

Optionally, the X events include at least one of the following: the first beam quality is less than or equal to a first preset threshold, the second beam quality is greater than or equal to a second preset threshold, the second beam quality is greater 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.

The first beam represents a serving beam, i.e., the current serving beam; the second beam represents a beam different from the serving beam, such as a beam of a candidate cell/neighboring cell, etc. The first beam may include one or more beams, and the second beam may also include one or more beams.

For example, the current serving beam is a reference signal with a QCL type of type D in the currently indicated TCI-state; or, the current serving beam is a reference signal with a QCL type of type D in the UL TCI-state applied by the current uplink transmission (PUSCH/PUCCH/SRS/physical random access channel (PRACH)); or, the current serving beam is a reference signal with a QCL type of type D in the downlink or joint TCI-state (DL or joint TCI-state) applied by the current downlink transmission (physical downlink control channel (PDCCH)/physical downlink shared channel (PDSCH)/CSI-RS). As an example, the reference signal is SSB, CSI-RS, SRS, etc.

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

Each preset threshold, such as the first preset threshold, the second preset threshold, the third preset threshold, and the fourth preset threshold, may be predefined, configured, indicated, or determined by the UE, without limitation. Each preset threshold may be the same or different. Two preset thresholds may be associated, meaning that an associated preset threshold can be derived from one preset threshold, or they may be unassociated. The units of each preset threshold may be decibel (dB), decibel milliwatt (dBm), etc.

The following describes the events listed above.

Example 1: The first beam quality is less than or equal to a first preset threshold.

For the sake of distinction, this event is referred to as event #A. In other words, event #A indicates that the current service beam quality is less than or equal to a certain threshold, such as the first preset threshold.

Example 2: The second beam quality is greater than or equal to a second preset threshold.

For distinction, this event is referred to as event #B. In other words, event #B indicates that there is at least one new beam (ie, the second beam) whose beam quality is greater than or equal to a threshold, such as the second preset threshold.

As an example, the new beam is a reference signal whose QCL type is typeD in the activated TCI-states (except 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, and the reference signal configured by the network device for the terminal device to monitor the occurrence of events or event #B) (except the reference signal corresponding to the current service beam).

Example 3: The second beam quality is greater than or equal to a third preset threshold of the first beam quality.

To distinguish, this event is called event #C. In other words, event #C indicates that there is at least one new beam whose beam quality is greater than the beam quality of the current service beam, and the difference between the beam quality of the new beam and the beam quality of the current service beam is greater than or equal to a threshold, such as the third preset threshold.

Event #C can also be described as: the first beam quality is less than or equal to the second beam quality by a threshold. In this case, the threshold can be a value less than 0 dB. Alternatively, "the first beam quality is less than or equal to the second beam quality by a threshold" can be considered an event different from event #C, and this is not limited to this.

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

To distinguish, this event is called event #D. In other words, event #D indicates that the difference between the beam quality of at least one new beam and the beam quality of the current service beam is less than or equal to a threshold, or event #D indicates that the absolute value of the difference between the beam quality of at least one new beam and the beam quality of the current service beam is less than or equal to a threshold, such as the fourth preset threshold.

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

Example 5: The beam quality of the first beam is less than or equal to a fifth preset threshold, and the beam quality of the second beam is greater than or equal to a sixth preset threshold, wherein the sixth preset threshold is greater than or equal to the fifth preset threshold.

To distinguish, this event is called event #E. In other words, event #E indicates that there is at least one new beam whose beam quality is greater than a certain threshold, and the beam quality of the current service beam is less than or equal to a threshold.

Example 6: The beam quality of the first beam is less than or equal to a seventh preset threshold of the beam quality of the preset beam.

For distinction, this event is referred to as event #F. For example, the current serving beam is a CSI-RS with a QCL type of type D in the currently indicated TCI-state, the preset beam is an SSB with a QCL type of type D for the CSI-RS, and the quality of the CSI-RS is less than or equal to the quality of the SSB by a threshold (i.e., the seventh preset threshold). In this case, the seventh preset threshold can be a value less than 0 dB.

The event #F can also be described as: the beam quality of the preset beam is greater than or equal to a threshold of the beam quality of the first beam. In this case, the threshold can be a value greater than 0 dB.

It can be understood that in the above examples, the situation regarding "equal" may be a situation where an event occurs, or it may be a situation where the event does not occur, that is, the above-defined event may not include "equal", or it may be used for other purposes, and there is no limitation on this.

S503: The terminal device sends first information, and the network device receives the first information accordingly.

If at least one of the X events occurs, the terminal device sends the first information to the network device. Taking event #A as an example, the occurrence of event #A indicates that the following situation has occurred: the first beam quality is less than the first preset threshold, or the first beam quality is equal to the first preset threshold. For example, if the terminal device determines through measurement that the first beam quality is less than or equal to the first preset threshold, it is determined that event #A has occurred. For another example, if the terminal device determines through measurement that the second beam quality is greater than or equal to the second preset threshold, it is determined that event #B has occurred. The occurrence of an event triggers a report, that is, triggers the reporting of the measurement report corresponding to the event.

The terminal device reports a measurement report related to one of the X events through the first information, that is, the first information includes a measurement report related to one of the X events, or the first information indicates a measurement report related to one of the X events. The load size corresponding to the first information is the load size corresponding to the measurement report related to the first event of the X events. The event occurring in the X events may be the first event or another event different from the first event, and this application does not limit this.

The first event may be a predefined event, or an event indicated by the network device to the terminal device, or an event indicated by the terminal device to the network device, or the first event is an event in which the load size of the relevant measurement report among the X events is greater than or equal to a threshold, for example, the first event is the event in which the load size corresponding to the relevant measurement report among the X events is the largest. For example, the X events are event #1, event #2, ..., event #X, and the load sizes corresponding to the measurement reports related to event #1, event #2, ..., event #X are P1, P2, ..., PX, respectively, where the load size Pn corresponding to the measurement report related to event #n is the largest among P1 to PX, then event #n is the first event.

Among them, the payload size corresponding to the event-related measurement report refers to the payload size required for reporting the measurement report related to the event, or the number of bits/bit space/bit width required for reporting the measurement report related to the event. Furthermore, the payload size required for reporting the measurement report related to the event refers to the payload size (or number of bits/bit space/bit width) required for the reporting parameters included in the measurement report related to the event. For example, the measurement report related to event #m includes reporting parameter #a, reporting parameter #b, ..., reporting parameter #k, and the number of bits required to report each reporting parameter in sequence is Pa, Pb, ..., Pk respectively. Then, the payload size required for reporting the measurement report related to event #m is (Pa+Pb+...+Pk). For example, the measurement report related to event #m includes k reporting parameters #a, 1 reporting parameter #b, ..., m reporting parameters #k. The number of bits required to report each reporting parameter in sequence is Pa, Pb, ..., Pk respectively. Then, the payload size required for reporting the measurement report related to event #m is (k*Pa+Pb+...+m*Pk). Among them, reporting parameter #a can be one of reporting parameters #1 to reporting parameters #11 described below, reporting parameter #b can be one of reporting parameters #1 to reporting parameters #11 described below, ..., reporting parameter #k can be one of reporting parameters #1 to reporting parameters #11 described below. Alternatively, one or more of reporting parameters #a to reporting parameters #k may not be limited to the reporting parameters described below. It can be understood that when the terminal device and the network device determine the measurement report related to the event, the load size required for reporting the measurement report related to the event can be determined.

The measurement reports related to different events among the X events may be predefined by a protocol, or may be configured by a network device, which is not limited in this application.

Optionally, measurement reports related to at least two events among the X events are different.

Optionally, there are at least two events among the X events, and the measurement reports corresponding to the event have different payload sizes.

The measurement report related to any one of the X events may include one or more of the following reporting parameters (or referred to as reporting quantities).

Reporting parameter #1, the current serving beam index, can also be understood as the reference signal index of the QCL type of type D in the currently indicated TCI-state; or, the reference signal index of the QCL type of type D in the UL TCI-state applied for the current uplink transmission (PUSCH/PUCCH/SRS/PRACH); or, the reference signal index of the QCL type of type D in the downlink or joint TCI-state (DLorjointTCI-state) applied for the current downlink transmission (PDCCH/PDSCH/CSI-RS).

Report parameter #2, the quality of the current serving beam, for example, the RSRP or SINR of the current serving beam.

The current serving beam may include one beam or multiple beams, which is not limited in this application. The number of current serving beams may be determined based on the number of UL/DL/jointTCI states indicated by the network device, such as the UL/DL/jointTCI state indicated by DCI signaling. Alternatively, the number of beams included in the current serving beam may be predefined by the protocol or preconfigured by the network device. Alternatively, the maximum number of beams included in the current serving beam may be predefined by the protocol or configured by the network device.

Reporting parameter #3, the index of the second beam, can also be understood as the reference signal index of the activated TCI-states (except the indicated TCI-state) whose QCL type is typeD, or it can be the index of one or more reference signals (except the reference signal corresponding to the current service beam) in the reference signal configured by the network device (such as the reference signal configured by the network device for measurement, and the reference signal configured by the network device for the terminal device to monitor the occurrence of events).

Report parameter #4, the quality of the second beam, for example, the RSRP or SINR of the second beam.

The second beam may include one beam or multiple beams, which is not limited in this application. The number of beams included in the second beam may be predefined by the protocol or preconfigured by the network device. Alternatively, the maximum number of beams included in the second beam may be predefined by the protocol or configured by the network device.

Reporting parameter #5, cell information, can also be understood as which cell the reported measurement report corresponds to, or which cell's reference signal resources the reported measurement result is measured. For example, the cell information can be the handover candidate cell ID, the non-serving cell ID (additional PCI), the component carrier (CC) index, PCI. The ID mentioned in the embodiments of the present application can be any abbreviation of identifier, indication, indicator, index, identity, and identification, and identifier, indication, indicator, index, identity, and identification can be interchangeable.

Report parameter #6: The reason why the current serving beam quality is below a threshold (e.g., a first preset threshold). Examples include network device beam misalignment, terminal device receive beam misalignment, or transmit/receive beam misalignment. The term "misaligned" can also be replaced with "expired" or "invalid." Alternatively, this parameter indicates whether to trigger CSI-RS set measurements with "repetition" set to "on" to poll the UE's receive beam.

Reporting parameter #7, reference signal resource set index, for example, CSI-RS resource set (CSI-RS-ResourceSet) index, CSI interference measurement (interferencemeasurement, IM) resource set (CSI-IM-ResourceSet) index, CSI-SSB resource set (CSI-SSB-ResourceSet) index, or a reference signal resource set index configured by the network device for the terminal device to monitor the occurrence of events, used to indicate to which reference signal resource set the reported current serving beam and/or second beam belongs.

Reporting parameter #8, reporting configuration index, for example, CSI report configuration identifier (CSI-ReportConfigId), or event-triggered reporting configuration index.

Report parameter #9, event information, such as the index of the event that occurred, or one or more bits used to indicate whether the event occurred. For example, event information includes M bits, Used to indicate the index of an event that occurred. For another example, event information includes X bits, each of which corresponds to X events. The xth bit of the X bits is used to indicate whether the event corresponding to the xth bit has occurred, where x = 1, 2, ..., X. For example, if the value of the xth bit is "0", then the xth bit is used to indicate that the event corresponding to the xth bit has occurred. Alternatively, if the value of the xth bit is "1", then the xth bit is used to indicate that the event corresponding to the xth bit has occurred.

Report parameter #10, capability index, is used to determine the maximum number of SRS ports.

Reporting parameter #11, channel state information, for example, may include one or more of precoding matrix indicator (PMI), rank indicator (RI), channel quality indicator (CQI), and layer indicator (LI).

Optionally, if the measurement report related to one of the X events includes multiple reporting parameters, the terminal device reports the multiple reporting parameters in a predefined or preconfigured reporting order. In other words, the bit space of the first information is allocated to the multiple reporting parameters included in the measurement report related to one of the X events in a predefined or preconfigured order. For example, the measurement report related to one of the X events includes the above-mentioned reporting parameter #1 and reporting parameter #2. According to the predefined or preconfigured reporting order, the terminal device first reports reporting parameter #1 and then reports reporting parameter #2, that is, reporting parameter #1 occupies the bit space in front of the first information, and reporting parameter #2 occupies the bit space after the first information.

Optionally, if one of the X events is the second event, and the payload size corresponding to the measurement report related to the second event is smaller than the payload size corresponding to the first information, then the portion of the first information other than the measurement report related to the second event is a predefined value. For example, the remaining bits in the first information other than the bits used to carry the measurement report related to the second event are filled with 0. For example, the payload size of the first information is S bits, and the payload size corresponding to the measurement report related to the second event is L bits. If L<S, the first L bits of the first information are used to carry the measurement report related to the second event, and the remaining bits are filled with 0. S and L are positive integers. For another example, the payload size of the first information is S bits, and the measurement report related to the second event includes reporting parameter #a and reporting parameter #b. The number of bits required for reporting parameter #a and reporting parameter #b are Pa and Pb respectively. If (Pa+Pb)<S, the first (Pa+Pb) bits of the first information are used to carry the measurement report related to the second event, and the remaining bits are filled with 0. Among them, the reporting parameter #a can be one or more of the reporting parameters #1 to reporting parameters #11 described above, and the reporting parameter #b can be one or more of the reporting parameters #1 to reporting parameters #11 described above.

The second event is different from the first event. It is understood that if the first event is the event with the largest payload size corresponding to the related measurement report among the X events, the second event can be any event among the X events except the first event.

Optionally, if one of the X events is the third event, and the load size corresponding to the measurement report related to the third event is larger than the load size corresponding to the first information, the first information includes part of the measurement report in the measurement report related to the third event. For example, the terminal device may discard (drop) part of the measurement report in the measurement report related to the third event according to a predefined or preconfigured reporting order. For example, the load size of the first information is S bits, and the load size corresponding to the measurement report related to the third event is L’ bits. If L’＞S, the terminal device drops the last (L’-S) bits in the measurement report related to the third event, and reports the first S bits in the measurement report related to the third event through the first information. L’ is a positive integer. For another example, the payload size of the first information is S bits, and the measurement report related to the third event includes reporting parameter #c, reporting parameter #d and reporting parameter #e. The number of bits required for reporting parameter #c, reporting parameter #d and reporting parameter #e are Pc, Pd and Pe respectively. If (Pc+Pd+Pe)＞S, the terminal device reports some parameters of reporting parameter #c, reporting parameter #d and reporting parameter #e through the first information in a predefined or preconfigured reporting order. For example, if the reporting order of reporting parameter #c and reporting parameter #d is in the front, and (Pc+Pd)≤S, (Pc+Pd+Pe)＞S, then the terminal device drops reporting parameter #e, and reports reporting parameter #c and reporting parameter #d through the first information, or the terminal device drops the last (S-Pc-Pd) bits of reporting parameter #e, and reports reporting parameter #c, reporting parameter #d and the first (Pc+Pd+Pe-S) bits of reporting parameter #e through the first information. Among them, reporting parameter #c can be one or more of reporting parameters #1 to reporting parameters #11 described above, reporting parameter #d can be one or more of reporting parameters #1 to reporting parameters #11 described above, and reporting parameter #e can be one or more of reporting parameters #1 to reporting parameters #11 described above.

Among them, the third event is different from the first event.

Optionally, if one of the X events is a fourth event, and the payload size corresponding to the measurement report related to the fourth event is equal to the payload size corresponding to the first information, then the first information includes all measurement reports in the measurement report related to the fourth event, and there is no need to fill in the predefined value. In other words, the terminal device can report the measurement report related to the fourth event in a predefined or preconfigured reporting order.

The fourth event is the same as or different from the first event.

Optionally, if one of the X events is a fifth event, the measurement report related to the fifth event includes one or more reporting parameters, and the number of reports corresponding to reporting parameter #f in the one or more reporting parameters is less than the maximum number of reports corresponding to reporting parameter #f specified by the network device or protocol, then the portion of the first information corresponding to reporting parameter #f, excluding reporting parameter #f included in the measurement report related to the fifth event, is a predefined value. Reporting parameter #f may be one of reporting parameters #1 to reporting parameter #11 described above. For example, the reporting parameter #f is the reporting parameter #3 described above, that is, the index of the second beam. The network device or protocol stipulates that the maximum number of beams included in the second beam is 4. In this case, the number of bits corresponding to the reporting parameter #f in the first information is Pf. Pf bits can be used to carry the indexes of 4 beams, and the reporting parameter #f included in the measurement report related to the fifth event includes the indexes of 2 beams. The number of bits required for the indexes of the 2 beams is Pf/2. Therefore, Pf/2 bits of the Pf bits corresponding to the reporting parameter #f in the first information carry the reporting parameter #f included in the measurement report related to the fifth event, and the other Pf/2 bits are filled with 0.

Optionally, if at least one of the X events occurs, and the terminal device does not need to report a measurement report for the at least one event, the terminal device does not send the first information.

Optionally, if at least one of the X events occurs and the terminal device does not send the first information, the terminal device may send indication information #1 to the terminal device, where the indication information #1 indicates at least one of the following: whether an event among the X events occurs, and information about the event that occurred among the X events.

Optionally, the events occurring among the X events include multiple events, and the terminal device reports a measurement report related to one of the multiple events occurring through the first information. For example, the terminal device reports a measurement report related to an event ranked first among the multiple events occurring through the first information in a predefined or preconfigured first order. For example. The events occurring among the X events include event #m and event #r, and event #m is ranked first, then the terminal device reports the measurement report related to event #m through the first information. Optionally, the terminal device can also report the measurement report related to event #r through the second information. For more descriptions of the second information, please refer to the first information. Among them, the predefined or preconfigured first order can be: in order from large to small according to the index of the event, or in order from small to large according to the index of the event, or in order from high to low according to the priority of the event.

Optionally, the terminal device may report measurement reports related to multiple events occurring in X events through the first information. If the sum of the load sizes corresponding to the measurement reports related to the multiple events occurring in the X events is less than the load size of the first information, the first information sent by the terminal device may include measurement reports related to the multiple events occurring, and the part of the first information other than the measurement reports related to the multiple events occurring is a predefined value. For example, the part of the first information other than the measurement reports related to the multiple events occurring is filled with all 0s. For example, the multiple events occurring in the X events include the sixth event and the seventh event, and the sum of the load size corresponding to the measurement report related to the sixth event and the load size corresponding to the measurement report related to the seventh event is less than the load size of the first information, then the first information sent by the terminal device may include the measurement report related to the sixth event and the measurement report related to the seventh event. Assuming that the load size of the first information is S, the load size required for the measurement report related to the sixth event is S1, and the load size required for the measurement report related to the seventh event is S2, (S1+S2)＜S, then the first (S1+S2) bits of the first information are used to carry the measurement reports related to the sixth event and the seventh event, and the last (S-S1-S2) bits of the first information are filled with all 0s.

Optionally, if the sum of the load sizes corresponding to the measurement reports related to multiple events occurring in the X events is greater than the load size of the first information, the terminal device can report the measurement reports related to some of the multiple events occurring in accordance with a predefined or preconfigured first order. In other words, the terminal device can discard (drop) the measurement reports related to some of the multiple events occurring in accordance with a predefined or preconfigured first order. For example, the multiple events occurring in the X events include the eighth event and the ninth event, and the sum of the load size corresponding to the measurement report related to the eighth event and the load size corresponding to the measurement report related to the ninth event is greater than the load size of the first information, and the eighth event is sorted first, then the terminal device can drop the measurement report related to the ninth event, and report the measurement report related to the eighth event through the first information. Alternatively, if the load size corresponding to the measurement report related to the eighth event is smaller than the load size corresponding to the first information, the terminal device can report all measurement reports related to the eighth event and part of the measurement report related to the ninth event through the first information. For example, the terminal device can report part of the reporting parameters in the measurement report related to the ninth event in a predefined or preconfigured reporting order, and drop the remaining reporting parameters.

Optionally, if the sum of the load sizes corresponding to the measurement reports related to multiple events occurring in X events is equal to the load size of the first information, the first information includes all measurement reports in the measurement reports related to the multiple events that occurred, and the first information does not need to be filled with a predefined value. For example, the terminal device can report the measurement reports related to the multiple events that occurred in a predefined or preconfigured first order.

Optionally, X events are associated with X different measurement report configurations, or X events are associated with the same measurement report configuration. Exemplarily, the measurement report configuration includes one or more of the following: beam measurement configuration, conditions for triggering measurement reports (such as one or more of the above X events), measurement report format, and measurement report period. Exemplarily, the beam measurement configuration may include information such as the measured beam identifier, frequency bandwidth, and reference signal type.

In a possible implementation manner, measurement reports related to X events are reported through the same uplink resource, that is, the first information including measurement reports related to different events is sent through the same uplink resource.

Optionally, the method 500 further includes: the network device configuring, for the terminal device, a same uplink resource associated with X event-related measurement reports.

In another possible implementation, measurement reports related to X events are reported through different uplink resources, that is, the first information including measurement reports related to different events is sent through different uplink resources.

Optionally, the method further includes: the network device configuring, for the terminal device, X uplink resources associated with measurement reports related to X events, one uplink resource of the X uplink resources being associated with a measurement report related to one of the X events. Optionally, the X uplink resources may be different uplink resources. Then, when a tenth event of the X events occurs, the payload size of the first information including the measurement report related to the tenth event is the payload size corresponding to the measurement report related to the tenth event.

In an embodiment of the present application, a terminal device can perform event-triggered reporting, thereby preventing the terminal device from reporting invalid measurement reports to a network device. In addition, the terminal device can report measurement reports related to an event that has occurred using first information with a fixed payload size, thereby avoiding resource waste caused by allocating corresponding reporting resources for each event when the terminal device supports or is configured with multiple events.

Referring to Figure 6, Figure 6 is a schematic diagram of another communication method 600 provided in an embodiment of the present application. The method 600 shown in Figure 6 may include the following steps.

Optionally, method 600 includes S601 and S602.

S601: A terminal device sends first indication information, and a network device receives the first indication information accordingly.

For more description of S601, please refer to S501 in the above method 500. For the sake of brevity, it will not be repeated here.

S602: The terminal device receives configuration information, and the network device sends configuration information accordingly.

For more description of S602, please refer to S502 in the above method 500, which will not be repeated here for the sake of brevity.

S603: The terminal device sends the first information, and the network device receives the first information accordingly.

If at least one of the X events occurs, the terminal device sends the first information to the network device. Taking event #A as an example, the occurrence of event #A indicates that the following situation has occurred: the first beam quality is less than the first preset threshold, or the first beam quality is equal to the first preset threshold. For example, if the terminal device determines through measurement that the first beam quality is less than or equal to the first preset threshold, it is determined that event #A has occurred. For another example, if the terminal device determines through measurement that the second beam quality is greater than or equal to the second preset threshold, it is determined that event #B has occurred. The occurrence of an event triggers a report, that is, triggers the reporting of the measurement report corresponding to the event.

The terminal device reports a measurement report related to at least one event occurring among X events through the first information, that is, the first information includes a measurement report related to at least one event occurring among X events, or the first information indicates a measurement report related to at least one event occurring among X events.

The first information is in a predefined format. Two possible formats of the first information are described below.

Format 1: The first information includes at least one public field and at least one non-public field.

Among them, at least one public field corresponds to at least one public reporting parameter. For example, at least one public field corresponds to at least one public reporting parameter one-to-one. Taking public field #1 in at least one public field as an example, public field #1 is used to carry the public reporting parameter corresponding to public field #1. In other words, the payload size of public field #1 is the payload size corresponding to the public reporting parameter corresponding to public field #1. It should be noted that the public field can also be named with other names, which is not limited in this application. The public reporting parameter can also be named with other names, which is not limited in this application.

It should be understood that if the measurement report related to the event occurring in the X events includes the common reporting parameter corresponding to the common field #1, then the common field #1 included in the first information carries the common reporting parameter corresponding to the common field #1. If the measurement report related to the event occurring in the X events does not include the common reporting parameter corresponding to the common field #1, or in other words, none of the events in which the measurement report includes the common reporting parameter corresponding to the common field #1 has occurred, then the common field #1 included in the first information is a predefined value, for example, each bit of the common field #1 included in the first information is filled with 0.

At least one non-public field corresponds to at least one non-public reporting parameter. For example, at least one non-public field corresponds to at least one non-public reporting parameter one-to-one. Taking non-public field #1 in at least one non-public field as an example, non-public field #1 is used to carry the non-public reporting parameter corresponding to non-public field #1. In other words, the load size of non-public field #1 is the load size corresponding to the non-public reporting parameter corresponding to non-public field #1. It should be noted that the non-public field can also be named with other names, which is not limited in this application. The non-public reporting parameter can also be named with other names, which is not limited in this application.

It should be understood that if the measurement report related to the event occurring in the X events includes the non-public reporting parameter corresponding to the non-public field #1, then the non-public field #1 included in the first information carries the non-public reporting parameter corresponding to the non-public field #1. If the measurement report related to the event occurring in the X events does not include the non-public reporting parameter corresponding to the non-public field #1, or in other words, if the event in which the measurement report includes the non-public reporting parameter corresponding to the non-public field #1 does not occur, then the non-public field #1 included in the first information is a predefined value, for example, each bit of the non-public field #1 included in the first information is filled with 0.

In summary, the payload size of the first information is the payload size required to report at least one public reporting parameter and at least one non-public reporting parameter.

Common reporting parameters are reporting parameters with the same value included in at least two of the X events. For example, common reporting parameters include one or more of the following: reporting parameter #1, reporting parameter #2, reporting parameter #3, reporting parameter #4, reporting parameter #5, reporting parameter #6, reporting parameter #7, reporting parameter #8, reporting parameter #10, and reporting parameter #11. For more information about the above reporting parameters, please refer to S503 of method 500 above.

Non-public reporting parameters are reporting parameters with different values included in measurement reports related to different events among the X events. For example, non-public reporting parameters are one or more of the following: reporting parameter #3, reporting parameter #4, reporting parameter #7, reporting parameter #8, and reporting parameter #9. For more description of the above reporting parameters, please refer to S503 in method 500 above.

The following uses an example to illustrate the method of determining the format of the first information.

As shown in Table 1, X events include four events, namely, event #1 to event #4. The measurement report related to event #1 includes reporting parameter #g, the measurement report related to event #2 includes reporting parameter #g and reporting parameter #h, the measurement report related to event #3 includes reporting parameter #g and reporting parameter #i, and the measurement report related to event #4 includes reporting parameter #i and reporting parameter #j. Reporting parameter #g is one of reporting parameters #1 to reporting parameters #11 described in S503 above, reporting parameter #h is one of reporting parameters #1 to reporting parameters #11 described in S503 above, reporting parameter #i is one of reporting parameters #1 to reporting parameters #11 described in S503 above, reporting parameter #j is one of reporting parameters #1 to reporting parameters #11 described in S503 above, and reporting parameter #1 is one of reporting parameters #1 to reporting parameters #11 described in S503 above.

Table 1

The measurement reports related to event #1, event #2, and event #3 all include reporting parameter #g. If reporting parameter #g is a public reporting parameter, the first information includes a public field corresponding to reporting parameter #g (denoted as public field #1). The measurement reports related to event #2 include reporting parameter #h, and the measurement reports related to the remaining events do not include reporting parameter #h. If reporting parameter #h is a non-public reporting parameter, the first information includes a non-public field corresponding to reporting parameter #h (denoted as non-public field #1). The measurement reports related to event #3 and event #4 both include reporting parameter #i. If the value of reporting parameter #i included in the measurement report related to event #3 is the same as the value of reporting parameter #i included in the measurement report related to event #4, then reporting parameter #i is a public reporting parameter, and the first information includes a public field corresponding to reporting parameter #i (denoted as public field #2); if the value of reporting parameter #i included in the measurement report related to event #3 is different from the value of reporting parameter #i included in the measurement report related to event #4, then reporting parameter #3 is a non-public reporting parameter, and the first information includes a non-public field corresponding to reporting parameter #i included in the measurement report related to event #3 (denoted as non-public field #2), and a non-public field corresponding to reporting parameter #i included in the measurement report related to event #4 (denoted as non-public field #3). The measurement related to event #4 includes reporting parameter #j, and the measurement reports related to other events do not include reporting parameter #j. Then the reporting parameter #j is a non-public reporting parameter, and the first information includes a non-public field corresponding to reporting parameter #j (recorded as non-public field #4).

In summary, based on the four events shown in Table 1 and the measurement reports related to the events, a possible format of the first information is: the first information includes a common field #1, a non-common field #1, a common field #2, and a non-common field #4. Among them, the common field #1 is used to carry the reporting parameter #g included in the measurement reports related to events #1 to #3, the non-common field #1 is used to carry the reporting parameter #h included in the measurement report related to event #2, the common field #2 is used to carry the reporting parameter #i included in the measurement reports related to events #3 and #4, and the non-common field #4 is used to carry the reporting parameter #j included in the measurement report related to event #4. The payload size of the first information is the sum of the payload size corresponding to the reporting parameter #g, the payload size corresponding to the reporting parameter #h, the payload size corresponding to the reporting parameter #i, and the payload size corresponding to the reporting parameter #j.

If event #1 and event #2 among events #1 to #4 occur, the first information sent by the terminal device can be as shown in Table 2, that is, the reporting parameter #g is carried on the public field #1, the reporting parameter #h is carried on the non-public field #1, and the public field #2 and the non-public field #4 are predefined values, for example, filled with all 0s.

Table 2

Based on the four events shown in Table 1 and the measurement reports related to the events, another possible format of the first information is as follows: the first information includes common field #1, non-common field #1, non-common field #2, non-common field #3, and non-common field #4. Common field #1 is used to carry reporting parameter #g included in the measurement reports related to events #1 to #3, non-common field #1 is used to carry reporting parameter #h included in the measurement report related to event #2, non-common field #2 is used to carry reporting parameter #i included in the measurement report related to event #3, non-common field #3 is used to carry reporting parameter #i included in the measurement report related to event #4, and non-common field #4 is used to carry reporting parameter #j included in the measurement report related to event #4. The payload size of the first information is the sum of the payload size corresponding to reporting parameter #g, the payload size corresponding to reporting parameter #h, the payload size corresponding to reporting parameter #i included in the measurement report related to event #3, the payload size corresponding to reporting parameter #i included in the measurement report related to event #4, and the payload size corresponding to reporting parameter #j.

If event #1 and event #2 among events #1 to #4 occur, the first information sent by the terminal device can be as shown in Table 3, that is, the reporting parameter #g is carried on the public field #1, the reporting parameter #h is carried on the non-public field #1, and the non-public field #2 to the non-public field #4 are predefined values, for example, filled with all 0s.

Table 3

Optionally, if the first information includes multiple fields, the multiple fields are arranged in a predefined or preconfigured order. In other words, the terminal device reports the public reporting parameters and/or non-public reporting parameters included in the measurement report related to the event in a predefined or preconfigured order.

Format 2: the first information includes at least one event field.

At least one event field corresponds to X events. For example, at least one event field corresponds to X events one-to-one. Taking event field #1 in the at least one event field as an example, event field #1 is used to carry a measurement report related to the event corresponding to event field #1. In other words, the payload size of event field #1 is the payload size corresponding to the measurement report related to the event corresponding to event field #1. It should be noted that the event field may also be named by other names, and this application does not limit this.

It should be understood that if the events occurring among the X events include the event corresponding to event field #1, then the event field #1 included in the first information carries the measurement report related to the event corresponding to event field #1. If the events occurring among the X events do not include the event corresponding to event field #1, then the event field #1 included in the first information is a predefined value, for example, each bit of the event field #1 included in the first information is filled with 0. For example, the X events are event #1, event #2, ..., event #X, and the events occurring among the X events are events other than event #2. Then the first information sent by the terminal device can be as shown in Table 4, that is, event field #1 carries the measurement report related to event #1, event #3 carries the measurement report related to event #3, ..., event field #X carries the measurement report related to event #X, and event field #2 is a predefined value, for example, filled with all 0s.

Table 4

In summary, the payload size of the first information is the sum of the payload sizes corresponding to the measurement reports related to the X events. For example, if the X events are event #1, event #2, ..., event #X, event #1, event #2, ..., and the payload sizes corresponding to the measurement reports related to event #X are P1, P2, ..., PX, respectively, then the payload size of the first information is (P1 + P2 + ... + PX).

Optionally, if the first information includes multiple event fields, the multiple event fields are arranged in a predefined or preconfigured first order. In other words, the terminal device reports measurement reports related to different events in a predefined or preconfigured first order. The predefined or preconfigured first order is one of the following: in descending order of the indexes of the multiple events, in descending order of the indexes of the multiple events, or in descending order of the priorities of the multiple events.

In an embodiment of the present application, a terminal device can perform event-triggered reporting, thereby avoiding the terminal device from reporting invalid measurement reports to a network device. In addition, the terminal device can report measurement reports related to one or more events that have occurred using a first message in a predefined format, thereby avoiding resource waste caused by allocating corresponding reporting resources for each event when the terminal device supports or is configured with multiple events.

It can be understood that some optional features in the various embodiments of the present application may not depend on other features in certain scenarios, and may also be combined with other features in certain scenarios, without limitation.

It can also be understood that the solutions in the various embodiments of the present application can be reasonably combined and used, and the explanations or descriptions of the various terms appearing in the embodiments can be referenced or explained with each other in the various embodiments, without limitation to this.

It can also be understood that in the above-mentioned various method embodiments, the methods and operations implemented by devices (such as terminal devices, network devices) can also be implemented by components of the devices (such as chips or circuits) without limitation.

The method provided in the embodiment of the present application is described in detail above in conjunction with Figures 5 and 6. Below, the apparatus provided in the embodiment of the present application is described in detail in conjunction with Figures 7 to 9. It should be understood that the description of the apparatus embodiment corresponds to the description of the method embodiment. Therefore, for matters not described in detail, please refer to the method embodiment above. For the sake of brevity, they are not repeated here.

Referring to FIG. 7 , FIG. 7 is a schematic diagram of a communication device 700 provided in an embodiment of the present application. The device 700 includes a transceiver unit 710. The transceiver unit 710 can be used to implement corresponding communication functions. The transceiver unit 710 can also be referred to as a communication interface or a communication unit. Optionally, the device 700 also includes a processing unit 720. The processing unit 720 can be used to perform processing, such as beam measurement. The functions of the processing unit 720 can be implemented by one or more processors. Specifically, the processor can include a modem chip, or a system-on-chip (SoC) chip or SIP chip containing a modem core.

Optionally, the device 700 may further include a storage unit, which may be used to store instructions and/or data. The processing unit 720 may read the instructions and/or data in the storage unit so that the device implements the aforementioned method embodiment.

Optionally, the transceiver unit 710 may include a receiving unit and a sending unit, wherein the receiving unit may be used to perform reception-related operations (such as receiving data or messages), and the sending unit may be used to perform transmission-related operations (such as sending data or messages).

In a first possible design, the apparatus 700 may be the terminal device in the aforementioned embodiment, and the apparatus 700 may implement the steps or processes corresponding to those performed by the terminal device in the above method embodiment. The transceiver unit 710 may be used to perform the transceiver-related operations (such as operations of sending and/or receiving data or messages) of the terminal device in the above method embodiment. For example, the transceiver unit 710 may be used to perform S501, S502, and S503 in the embodiment shown in FIG5 , or the transceiver unit 710 may be used to perform S601, S602, and S603 in the embodiment shown in FIG6 . The processing unit 720 may be used to perform the processing-related operations of the terminal device in the above method embodiment, or operations other than transceiver (such as operations other than sending and/or receiving data or messages).

In one possible implementation, the transceiver unit 710 is used to receive configuration information, where the configuration information includes information about at least one event, and the at least one event is related to a measurement report submitted by a terminal device; the transceiver unit 710 is also used to send first information, where the first information includes a measurement report related to an event occurring in at least one event, and the load size corresponding to the first information is the load size corresponding to the measurement report related to the first event in at least one event.

In one possible implementation, the transceiver unit 710 is used to receive configuration information, which includes information about at least one event, and the at least one event is related to the measurement report reporting initiated by the terminal device; the transceiver unit 710 is also used to send first information, which includes measurement reports related to one or more events occurring in at least one event.

In a second possible design, the device 700 may be a network device in the aforementioned embodiment, and the device 700 may implement the steps or processes corresponding to those performed by the network device in the above method embodiment. The transceiver unit 710 may be used to perform the transceiver-related operations (such as operations of sending and/or receiving data or messages) of the network device in the above method embodiment. For example, the transceiver unit 710 may be used to perform steps S501, S502, and S503 in the embodiment shown in FIG5 , or the transceiver unit 710 may be used to perform S601, S602, and S603 in the embodiment shown in FIG6 . The processing unit 720 may be used to perform the processing-related operations of the network device in the above method embodiment, or operations other than transceiver (such as operations other than sending and/or receiving data or messages).

In one possible implementation method, the transceiver unit 710 is used to send configuration information, where the configuration information includes information about at least one event, and the at least one event is related to a measurement report initiated by a terminal device; the transceiver unit 710 is also used to receive first information, where the first information includes a measurement report related to an event occurring in at least one event, and the load size corresponding to the first information is the load size corresponding to the measurement report related to the first event in at least one event.

In one possible implementation, the transceiver unit 710 is used to send configuration information, the configuration information includes information about at least one event, and the at least one event is related to the measurement report reporting initiated by the terminal device; the transceiver unit 710 is also used to receive first information, the first information includes measurement reports related to one or more events occurring in at least one event.

It should be understood that the specific process of each unit executing the above corresponding steps has been described in detail in the above method embodiment, and for the sake of brevity, it will not be repeated here.

It should also be understood that the device 700 herein is embodied in the form of a functional unit. The term "unit" herein may refer to an application specific integrated circuit (ASIC), an electronic circuit, a processor (e.g., a shared processor, a dedicated processor, or a group processor, etc.) and memory for executing one or more software or firmware programs, a combined logic circuit, and/or other suitable components that support the described functions. In an optional example, those skilled in the art will understand that the device 700 may be specifically the communication device in the above-mentioned embodiment, and may be used to execute the various processes and/or steps corresponding to the communication device in the above-mentioned method embodiments. To avoid repetition, they will not be described here.

The apparatus 700 of each of the above-described solutions has the function of implementing the corresponding steps performed by the communication device in the above-described method. The functions can be implemented by hardware, or by hardware executing corresponding software implementations. The hardware or software includes one or more modules corresponding to the above-described functions; for example, the transceiver unit can be replaced by a transceiver (for example, 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 the processing unit, can be replaced by a processor to respectively perform the transceiver operations and related processing operations in each method embodiment.

In addition, the transceiver unit 710 may also be a transceiver circuit (for example, may include a receiving circuit and a sending circuit), and the processing unit may be a processing circuit.

It should be noted that the apparatus in FIG7 may be the communication device in the aforementioned embodiments, or may be a chip or chip system, such as a system on a chip (SoC). The transceiver unit may be an input/output circuit or a communication interface, and the processing unit may be a processor, microprocessor, or integrated circuit integrated on the chip. This is not limited here.

Referring to FIG8 , FIG8 is a schematic diagram of another communication device 800 provided in an embodiment of the present application. The device 800 includes a processor 810, which is coupled to a memory 820. The memory 820 is configured to store computer programs or instructions and/or data. The processor 810 is configured to execute the computer programs or instructions stored in the memory 820, or read data stored in the memory 820, to perform the methods described in the above method embodiments.

Optionally, there are one or more processors 810 .

Optionally, there are one or more memories 820 .

Optionally, the memory 820 is integrated with the processor 810 or provided separately.

Optionally, as shown in Figure 8, the apparatus 800 further includes a transceiver 830, which is configured to receive and/or transmit signals. For example, the processor 810 is configured to control the transceiver 830 to receive and/or transmit signals.

As an example, the processor 810 may have the function of the processing unit 720 shown in FIG. 7 , the memory 820 may have the function of a storage unit, and the transceiver 830 may have the function of the transceiver unit 710 shown in FIG. 7 .

As a solution, the device 800 is used to implement the operations performed by the communication device in the above various method embodiments.

For example, the processor 810 is configured to execute computer programs or instructions stored in the memory 820 to implement relevant operations of the terminal device or network device in each of the above method embodiments.

It should be understood that the processor mentioned in the embodiments of the present application may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field programmable gate arrays (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or any conventional processor, etc.

It should also be understood that the memory mentioned in the embodiments of the present application can be a volatile memory and/or a non-volatile memory. Among them, the non-volatile memory can be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory can be a 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 RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct rambus RAM (DR RAM).

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, discrete hardware component, the memory (storage module) can be integrated into the processor.

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.

It should also be noted that if the device 800 includes a processor 810, the device 800 may be a chip, a chip system, or a circuit. If the device 800 also includes a transceiver 830, the transceiver 830 may be a transceiver interface of the device, which is used to perform receiving or sending actions. The transceiver interface may include a receiving interface and a sending interface, the receiving interface being used to perform receiving actions, and the sending interface being used to perform sending actions. If the device 800 also includes a memory 820, the device 800 may be a communication module.

9 , which is a schematic diagram of a chip system 900 according to an embodiment of the present application. The chip system 900 (or processing system) includes a logic circuit 910 and an input/output interface 920.

The logic circuit 910 may be a processing circuit in the chip system 900. The logic circuit 910 may be coupled to a storage unit and call instructions in the storage unit so that the chip system 900 can implement the methods and functions of the various embodiments of the present application. The input/output interface 920 may be an input/output circuit in the chip system 900, outputting information processed by the chip system 900 or inputting data or signaling information to be processed into the chip system 900 for processing.

Alternatively, the logic circuit 910 may be implemented by one or more processors, including the one or more processors or a processing portion in the one or more processors.

Optionally, the input/output interface 920 may include a transceiver circuit, a transceiver, an input/output circuit, or a communication interface.

As a solution, the chip system 900 is used to implement the operations performed by a communication device (such as a terminal device or a network device) in the above various method embodiments.

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

An embodiment of the present application further 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-mentioned method embodiments.

For example, when the computer program is executed by a computer, the computer can implement the methods performed by a communication device (such as a terminal device, or a network device) in each embodiment of the above method.

An embodiment of the present application further provides a computer program product comprising instructions, which, when executed by a computer, implement the methods performed by a communication device (such as a terminal device or a network device) in the above-mentioned method embodiments.

The present application also provides a communication system, which includes the terminal device and/or network device in the above embodiments. For example, the system includes the terminal device and network device in Figure 5 or Figure 6.

The explanation of the relevant contents and beneficial effects of any of the above-mentioned devices can be referred to the corresponding method embodiments provided above, which will not be repeated here.

In the several embodiments provided in this application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part 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, the process or function described in the embodiment of the present application is generated in whole or in part. 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 computer-readable storage medium. For example, the computer instructions can be transmitted from one website, computer, server or data center to another website, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode. 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 includes one or more available media integrations. The available medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid state disk (SSD)). For example, the aforementioned available medium includes, but is not limited to, various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.

Claims (34)

A communication method, comprising: Receive configuration information, where the configuration information includes information about at least one event, where the at least one event is related to a measurement report initiated by a terminal device; Send first information, where the first information includes a measurement report related to an event occurring in the at least one event, and the load size corresponding to the first information is the load size corresponding to the measurement report related to the first event in the at least one event. A communication method, comprising: Sending configuration information, where the configuration information includes information about at least one event, where the at least one event is related to a measurement report initiated by a terminal device; Receive first information, where the first information includes a measurement report related to an event occurring in the at least one event, and the load size corresponding to the first information is the load size corresponding to the measurement report related to the first event in the at least one event. The method according to claim 1 or 2 is characterized in that the at least one event-related measurement report is associated with the same uplink resource, and the uplink resource is used to carry the first information. The method according to any one of claims 1 to 3, characterized in that, in the at least one event, there are at least two event-related measurement reports that are different. The method according to any one of claims 1 to 4, characterized in that, in the at least one event, there are at least two event-related measurement reports corresponding to different load sizes. The method according to any one of claims 1 to 5, characterized in that the first event is an event having a largest load size corresponding to a related measurement report among the at least one event. The method according to any one of claims 1 to 6 is characterized in that one event occurring among the at least one event is a second event, and if the load size corresponding to the measurement report related to the second event is smaller than the load size corresponding to the first information, then the part of the first information other than the measurement report related to the second event is a predefined value. The method according to claim 7, characterized in that the predefined value is 0. The method according to any one of claims 1 to 8, wherein the at least one event comprises at least one of the following: The first beam quality is less than or equal to a first preset threshold; The second beam quality is greater than or equal to a second preset threshold; The difference between the second beam quality and the first beam quality is greater than or equal to a third preset threshold; The difference between the second beam quality and the first beam quality is less than or equal to a fourth threshold; The first beam is a service beam, and the second beam is a beam different from the first beam. The method according to any one of claims 1 to 9, wherein the measurement report related to an event occurring in the at least one event includes one or more of the following: The index of the first beam, the quality of the first beam, the index of the second beam, the quality of the second beam, information about the cell corresponding to the event-related measurement report, the reason why the quality of the first beam is lower than the threshold, the reference signal resource set index, the reporting configuration index, information about an event that occurred in the at least one event, the capability index, and the channel state information; The first beam is a service beam, and the second beam is a beam different from the first beam. The method according to any one of claims 1 to 10, characterized in that different events in the at least one event are associated with different measurement report configurations, or the at least one event is associated with the same measurement report configuration. A communication method, comprising: Receive configuration information, where the configuration information includes information about at least one event, where the at least one event is related to a measurement report initiated by a terminal device; First information is sent, where the first information includes a measurement report related to an event occurring in the at least one event. A communication method, comprising: Sending configuration information, where the configuration information includes information about at least one event, where the at least one event is related to a measurement report initiated by a terminal device; First information is received, where the first information includes a measurement report related to an event occurring in the at least one event. The method according to claim 12 or 13 is characterized in that the at least one event-related measurement report is associated with the same uplink resource, and the uplink resource is used to carry the first information. The method according to any one of claims 12 to 14 is characterized in that the first information includes at least one public field and at least one non-public field, the at least one public field corresponds one-to-one to at least one public reporting parameter, the at least one non-public field corresponds one-to-one to at least one non-public reporting parameter, the public reporting parameter is a reporting parameter with the same value included in the measurement reports related to at least two events in the at least one event, and the non-public reporting parameter is a reporting parameter with different values included in the measurement reports related to different events in the at least one event. The method according to claim 15, characterized in that The measurement report related to the event occurring in the at least one event does not include the first common reporting parameter, and the common field corresponding to the first common reporting parameter is a predefined value; or, If the measurement report related to the event occurring in the at least one event includes a first common reporting parameter, the common field corresponding to the first common reporting parameter carries the first common reporting parameter. The method according to claim 15 or 16, characterized in that The measurement report related to the event occurring in the at least one event does not include the first non-public reporting parameter, and the non-public field corresponding to the first non-public reporting parameter is a predefined value; or, If the measurement report related to the event occurring in the at least one event includes a first non-public reporting parameter, the non-public field corresponding to the first non-public reporting parameter carries the first non-public reporting parameter. The method according to any one of claims 12 to 14, characterized in that the first information includes at least one event field, and the at least one event field has a one-to-one correspondence with the at least one event. The method according to claim 18, characterized in that If event #p in the at least one event does not occur, the event field corresponding to event #p is a predefined value; or If event #p among the at least one event occurs, the event field corresponding to the event #p carries a measurement report related to the event #p. The method according to claim 18 or 19 is characterized in that the first information includes measurement reports related to multiple events occurring in the at least one event, and the measurement reports related to the multiple events are arranged in a first order. The method according to claim 20 is characterized in that the first order is one of the following: in order of the indexes of the multiple events from large to small, in order of the indexes of the multiple events from small to large, and in order of the priorities of the multiple events from high to low. The method according to any one of claims 18 to 21 is characterized in that the first information includes a measurement report related to event #q occurring in the at least one event, and the multiple reporting parameters included in the measurement report related to event #q are arranged in a predefined order. The method according to any one of claims 16, 17 or 19, characterized in that the predefined value is 0. The method according to any one of claims 12 to 23, wherein the at least one event comprises at least one of the following: The first beam quality is less than or equal to a first preset threshold; The second beam quality is greater than or equal to a second preset threshold; The difference between the second beam quality and the first beam quality is greater than or equal to a third preset threshold; The difference between the second beam quality and the first beam quality is less than or equal to a fourth preset threshold; The first beam represents a serving beam, and the second beam represents a beam different from the serving beam. The method according to any one of claims 12 to 24, wherein the measurement report related to an event occurring in the at least one event comprises one or more of the following: The index of the first beam, the quality of the first beam, the index of the second beam, the quality of the second beam, information about the cell corresponding to the event-related measurement report, the reason why the quality of the first beam is lower than the threshold, the reference signal resource set index, the reporting configuration index, information about an event that occurred in at least one event, the capability index, and the channel state information; The first beam is a service beam, and the second beam is a beam different from the first beam. A communication device, comprising a transceiver unit, The transceiver unit is configured to receive configuration information, where the configuration information includes information about at least one event, where the at least one event is related to a measurement report initiated by a terminal device; The transceiver unit is also used to send first information, wherein the first information includes a measurement report related to an event occurring in the at least one event, and the load size corresponding to the first information is the load size corresponding to the measurement report related to the first event in the at least one event. A communication device, comprising a transceiver unit, The transceiver unit is configured to receive configuration information, where the configuration information includes information about at least one event, where the at least one event is related to a measurement report initiated by a terminal device; The transceiver unit is further configured to send first information, where the first information includes a measurement report related to an event occurring in the at least one event. A communication device, comprising a transceiver unit, The transceiver unit is configured to send configuration information, where the configuration information includes information about at least one event, where the at least one event is related to a measurement report initiated by a terminal device; The transceiver unit is also used to receive first information, wherein the first information includes a measurement report related to an event occurring in the at least one event, and the load size corresponding to the first information is the load size corresponding to the measurement report related to the first event in the at least one event. A communication device, comprising a transceiver unit, The transceiver unit is configured to send configuration information, where the configuration information includes information about at least one event, where the at least one event is related to a measurement report initiated by a terminal device; The transceiver unit is further configured to receive first information, where the first information includes a measurement report related to an event occurring in the at least one event. A communication device, characterized in that it includes a module or unit for executing the method of any one of claims 1, 3 to 12, or 14 to 25, or includes a module or unit for executing the method of any one of claims 3 to 11 or 13 to 25. A communication device, characterized in that it includes at least one processor, wherein the at least one processor is used to execute a computer program or instruction so that the device performs the method described in any one of claims 1, 3 to 12, or 14 to 25, or so that the device performs the method described in any one of claims 3 to 11 or 13 to 25. The device according to claim 31, characterized in that The apparatus further comprises a memory for storing the computer program or instructions; and/or, The apparatus further comprises a communication interface coupled to the at least one processor, the communication interface being configured to input and/or output information. A computer-readable storage medium, characterized in that a computer program or instruction is stored on the computer-readable storage medium, and when the computer program or instruction is run on a communication device or a computer, the communication device executes the method as described in any one of claims 1, 3 to 12, or 14 to 25, or the communication device executes the method as described in any one of claims 3 to 11 or 13 to 25. A computer program product, characterized in that the computer program product includes a computer program or instructions for executing the method according to any one of claims 1, 3 to 12, or 14 to 25, or the computer program product includes a computer program or instructions for executing the method according to any one of claims 3 to 11 or 13 to 25.