Communication method and communication apparatus

By having the terminal device report measurement data based on configuration information and triggering events, the problem of high uplink resource overhead in wireless communication measurement reports is solved, and the rational allocation of resources and avoidance of invalid reports are achieved.

WO2025209483A9PCT designated stage Publication Date: 2026-05-21HUAWEI TECH CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
HUAWEI TECH CO LTD
Filing Date
2025-04-01
Publication Date
2026-05-21

AI Technical Summary

Technical Problem

In wireless communication, the uplink resource overhead of measurement reports is significant, and existing technologies cannot effectively reduce it.

Method used

Terminal devices report event-triggered measurement reports based on configuration information, and report event-related measurement reports using information with a fixed load size to avoid resource waste.

Benefits of technology

This reduced the overhead of uplink resources, enabled the rational allocation of resources, and avoided the reporting of invalid measurement reports.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN2025086651_21052026_PF_FP_ABST
    Figure CN2025086651_21052026_PF_FP_ABST
Patent Text Reader

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.
Need to check novelty before this filing date? Find Prior Art

Description

Communication methods and communication devices

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

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

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

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

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

[0006] The method includes: receiving configuration information, the configuration information including information about at least one event, the at least one event being related to a measurement report initiated by a terminal device; sending first information, the first information including a measurement report related to one of the at least one events, the load size corresponding to the first information being the load size corresponding to the measurement report related to the first event in the at least one event.

[0007] Based on the above technical solution, terminal devices can report events, thereby avoiding the reporting of invalid measurement reports to network devices. Furthermore, terminal devices can report event-related measurement reports using a fixed load size as the first piece of information, thus avoiding resource waste caused by allocating reporting resources for each event when the terminal device supports or is configured with multiple events.

[0008] Measurement reports related to different events in at least one event may be predefined by the protocol or configured by the network device; this application does not limit this.

[0009] Optionally, at least two of the events in a given event have different related measurement reports.

[0010] Optionally, at least two of the event-related measurement reports in at least one event have different load sizes.

[0011] The first event can be a predefined event, an event indicated by the network device to the terminal device, an event indicated by the terminal device to the network device, or the first event being the event with the largest load size corresponding to the relevant measurement report among at least one event.

[0012] The payload size for event-related measurement reports refers to the payload size required to report event-related measurement reports, or the number of bits / bit space / bit width required to report event-related measurement reports.

[0013] For example, the above measurement report is at least one of the following: an event-triggered or user equipment (UE) initiated report, an event-triggered or UE initiated beam report, an event-triggered or UE initiated channel state information (CSI) report, an event-triggered or UE initiated beam measurement result report, an event-triggered or UE initiated interference measurement report, interference measurement report, CSI report, beam measurement result report, etc.

[0014] In one possible implementation, at least one of the events is designated as the second event. If the load size corresponding to the measurement report related to the second event is less than the load size corresponding to the first information, then the portion of the first information excluding the measurement report related to the second event is a predefined value.

[0015] The second event differs from the first event. It can be understood that if the first event is the event with the largest load size corresponding to the relevant measurement report among at least one event, then the second event can be any event other than the first event among at least one events.

[0016] Optionally, if one of the at least one events 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 a portion of the measurement reports related to the third event. For example, the terminal device can discard a portion of the measurement reports related to the third event according to a predefined or preconfigured reporting order.

[0017] Optionally, if one of the at least one events is the 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 related to the fourth event, and there is no need to fill in predefined values. For example, the terminal device can report the measurement reports related to the fourth event according to a predefined or preconfigured reporting order.

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

[0019] In conjunction 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 a first beam, the quality of the first beam, an index of a 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 a threshold, an index of a reference signal resource set, a reporting configuration index, information about an event occurring in at least one event, a capability index, and channel state information; wherein the first beam is a serving beam, and the second beam is a beam different from the first beam.

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

[0021] The method includes: sending configuration information, the configuration information including information about at least one event, the at least one event being related to a measurement report initiated by a terminal device; receiving first information, the first information including a measurement report related to one of the at least one events, the load size corresponding to the first information being the load size corresponding to the measurement report related to the first event in the at least one event.

[0022] In conjunction with the second aspect, in some implementations of the second aspect, at least two event-related measurement reports differ in at least one event.

[0023] In conjunction with the second aspect, in some implementations of the second aspect, at least two event-related measurement reports have different load sizes in at least one event.

[0024] In conjunction with the second aspect, in some implementations of the second aspect, the first event is the event with the largest load size corresponding to the relevant measurement report among at least one event.

[0025] In conjunction with the second aspect, in some 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 less than the load size corresponding to the first information, then the portion of the first information excluding the measurement report related to the event occurring in at least one event is a predefined value.

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

[0027] In conjunction 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 a first beam, the quality of the first beam, an index of a 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 a threshold, an index of a reference signal resource set, a reporting configuration index, information about an event occurring in at least one event, a capability index, and channel state information; wherein the first beam is a serving beam, and the second beam is a beam different from the first beam.

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

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

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

[0031] Among them, at least one event includes one or more events.

[0032] Based on the above technical solution, the terminal device can report events, thereby avoiding the reporting of invalid measurement reports to the network device. Furthermore, the terminal device can report measurement reports related to one or more events using a predefined format of first information, thus avoiding resource waste caused by allocating reporting resources for each event when the terminal device supports or is configured with multiple events.

[0033] In conjunction with the third aspect, in some implementations of the third aspect, 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 with at least one public reporting parameter, and the at least one non-public field corresponds one-to-one with 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 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 at least one event.

[0034] It should be understood that if the event-related measurement report for at least one event does not include a first common reporting parameter, then the common field corresponding to the first common reporting parameter is a predefined value. If the event-related measurement report for at least one event includes a first common reporting parameter, then the common field corresponding to the first common reporting parameter carries the first common reporting parameter.

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

[0036] In summary, the load size of the first information is the load size required to report at least one common reporting parameter and at least one non-common reporting parameter.

[0037] In conjunction 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 with at least one event.

[0038] It should be understood that if at least one event #p does not occur, the event field corresponding to event #p will have a predefined value; or, if at least one event #p occurs, the event field corresponding to event #p will carry a measurement report related to event #p.

[0039] In summary, the load size of the first piece of information is the load size required to report at least one event-related measurement report.

[0040] In conjunction with the third aspect, in some implementations of the third aspect, the first information includes multiple event-related measurement reports occurring in at least one event, the multiple event-related measurement reports being arranged in a first order.

[0041] In conjunction with the third aspect, in some implementations of the third aspect, the first order is one of the following: according to the index of multiple events from largest to smallest, according to the index of multiple events from smallest to largest, or according to the priority of multiple events from highest to lowest.

[0042] Based on the above technical solution and the first sequence, the network device can determine the events corresponding to the multiple measurement reports reported by the terminal device.

[0043] In conjunction with the third aspect, in some implementations of the third aspect, the first information includes a measurement report related to event #q that occurred in at least one event, and the multiple reported parameters included in the measurement report related to event #q are arranged in a predefined order.

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

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

[0046] In conjunction 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 a first beam, the quality of the first beam, an index of a 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 a threshold, an index of a reference signal resource set, a reporting configuration index, information about an event occurring in at least one event, a capability index, and channel state information; wherein the first beam is a serving beam, and the second beam is a beam different from the first beam.

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

[0048] The method includes: sending configuration information, the configuration information including information about at least one event, the at least one event being related to a measurement report initiated by a terminal device; and receiving first information, the first information including all or part of the measurement report related to the event occurring in the at least one event.

[0049] In conjunction with the fourth aspect, in some implementations of the fourth aspect, 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 with at least one public reporting parameter, and the at least one non-public field corresponds one-to-one with 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 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 at least one event.

[0050] In conjunction with the fourth aspect, in some implementations of the fourth aspect, if the event-related measurement report of at least one event does not include the first common reporting parameter, then the common field corresponding to the first common reporting parameter is a predefined value; or, if the event-related measurement report of at least one event includes the first common reporting parameter, then the common field corresponding to the first common reporting parameter carries the first common reporting parameter.

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

[0052] In conjunction 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 with at least one event.

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

[0054] In conjunction with the fourth aspect, in some implementations of the fourth aspect, the first information includes multiple event-related measurement reports occurring in at least one event, the multiple event-related measurement reports being arranged in a first order.

[0055] In conjunction with the fourth aspect, in some implementations of the fourth aspect, the first order is one of the following: according to the index of multiple events from largest to smallest, according to the index of multiple events from smallest to largest, or according to the priority of multiple events from highest to lowest.

[0056] In conjunction with the fourth aspect, in some implementations of the fourth aspect, the first information includes a measurement report related to event #q that occurred in at least one event, and the multiple reported parameters included in the measurement report related to event #q are arranged in a predefined order.

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

[0058] In conjunction 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 a first beam, the quality of the first beam, an index of a 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 a threshold, an index of a reference signal resource set, a reporting configuration index, information about an event occurring in at least one event, a capability index, and channel state information; wherein the first beam is a serving beam, and the second beam is a beam different from the first beam.

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

[0060] Fifthly, a communication apparatus is provided for performing the method in any of the possible implementations of the first to fourth aspects described above. Specifically, the apparatus may include units and / or modules for performing the method in any of the possible implementations of the first to fourth aspects, such as processing units and / or communication units.

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

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

[0063] A sixth aspect provides a communication device comprising: at least one processor for executing a computer program or instructions to perform the method in any of the possible implementations of the first to fourth aspects described above. Optionally, the device further comprises a memory for storing the computer program or instructions. Optionally, the device further comprises a communication interface coupled to the processor, which can be used to input the computer program or instructions to the processor or to output information from the processor.

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

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

[0066] A seventh aspect is to provide a processor for performing the method provided in any one of the first to fourth aspects described above.

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

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

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

[0070] Eighthly, a computer-readable storage medium is provided that stores program code for execution by a device, the program code including methods for performing any of the possible implementations of the first to fourth aspects described above.

[0071] Ninth aspect, a computer program product containing instructions is provided, which, when run on a computer, causes the computer to perform the method in any one of the possible implementations of the first to fourth aspects described above.

[0072] In a tenth aspect, a chip is provided, the chip including a processor and a communication interface, the processor reading instructions from a memory through the communication interface and executing the method provided by any of the above-described implementations of any of the first to fourth aspects.

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

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

[0075] Eleventhly, a computer program product containing instructions is provided, which, when run on a computer, causes the computer to perform the method provided by any of the above-described implementations of the first to fourth aspects.

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

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

[0078] Figure 2 is another example of the architecture of a mobile communication system used in the embodiments of this application.

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

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

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

[0082] Figure 6 is a schematic diagram of a communication method 600 provided in an embodiment of this application.

[0083] Figure 7 is a schematic diagram of a communication device 700 provided in an embodiment of this application.

[0084] Figure 8 is a schematic diagram of another communication device 800 provided in an embodiment of this application.

[0085] Figure 9 is a schematic diagram of a chip system 900 provided in an embodiment of this application. Detailed Implementation

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

[0087] The technical solutions provided in this application can be applied to various communication systems, such as: 5th generation (5G) or new radio (NR) systems, long term evolution (LTE) systems, LTE frequency division duplex (FDD) systems, 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.

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

[0089] In a communication system, a device can send signals to or receive signals from another device. These signals can include information, signaling, or data. The device can also be replaced by an entity, network entity, communication device, mobile device, network element, communication module, node, communication node, communication apparatus, etc. This disclosure uses a device as an example. For instance, a communication system can include at least one terminal device and at least one network device. The network device can send downlink signals to the terminal device, and / or the terminal device can send uplink signals to the network device. It is understood that the terminal device in this disclosure can be replaced by a first communication device, and the network device can be replaced by a second communication device, both performing the corresponding communication methods described in this disclosure. Alternatively, the corresponding communication methods in this disclosure can be applied between network devices or between terminal devices, without limitation herein.

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

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

[0092] In this embodiment, the device for implementing the functions of the terminal device can be the terminal device itself, or it can be any device capable of supporting the terminal device in implementing those functions, such as a chip system. This device can be installed in or used in conjunction with the terminal device. In this embodiment, the chip system can be composed of chips or may include chips and other discrete components. This embodiment only uses the terminal device as an example to illustrate the device for implementing the functions of the terminal device, and does not constitute a limitation on the solution of this embodiment.

[0093] The network device in this application embodiment can be a device or module with corresponding communication functions. The network device can be a device used to communicate with terminal devices; it can also be called an access network device or a wireless access network device, such as a base station. In this application embodiment, the network device can refer to a radio access network (RAN) node (or device) that connects the terminal device to the wireless network. A base station can broadly encompass, or be replaced by, various names including: NodeB, evolved NodeB (eNB), next-generation NodeB (gNB), relay station, access point, transmitting and receiving point (TRP), transmitter 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 can be a macro base station, micro base station, relay node, donor node, or a combination thereof. A base station can also refer to a communication module, modem, or chip installed within the aforementioned equipment or apparatus. A base station can also be a mobile switching center, a device that performs base station functions in D2D, V2X, and M2M communications, or a device that performs base station functions in future communication systems. A base station can support networks using the same or different access technologies. The embodiments of this application do not limit the specific technologies or device forms used in the network equipment.

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

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

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

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

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

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

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

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

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

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

[0104] In different systems, CU (or CU-CP and CU-UP), DU, or RU may have different names, but those skilled in the art will understand their meaning. For example, a radio access network can also be an open radio access network (O-RAN) architecture. In an O-RAN system, CU can also be called an open CU (openCU, O-CU), DU can also be called an open DU (open DU, O-DU), CU-CP can also be called an open CU-CP (open CU-CP, O-CU-CP), CU-UP can also be called an open CU-UP (open CU-UP, O-CU-UP), and RU can also be called an open RU (openRU, O-RU). Any of the units among CU (or CU-CP, CU-UP), DU, and RU in this application can be implemented through software modules, hardware modules, or a combination of software modules and hardware modules.

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

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

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

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

[0109] 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 this application do not limit the number of network devices and terminal devices included in the mobile communication system.

[0110] The communication between network device 101 and terminal device 102 in the communication system shown in Figure 1 can also be represented in another form.

[0111] 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 used to receive transmission control information through antenna 1233, and transmitter 1231 can be used to send transmission feedback information to network device 101 through 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 used to send transmission control information to terminal device 102 through antenna 1133, and receiver 1132 can be used to receive transmission feedback information sent by terminal device 102 through antenna 1133.

[0112] The embodiments of this application can also be applied to open RAN (O-RAN) system architecture.

[0113] As shown in Figure 3, an O-RAN system can include core network (CN) equipment, access network (RAN) equipment, and user equipment (UE). Access network equipment communicates with core network equipment via a backhaul link and with UE via an air interface. For example, a BBU in the access network equipment communicates with core network equipment via a backhaul link, and an RU in the access network equipment communicates with UE via an air interface. The BBU communicates with at least one RU via 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, and the CU and DU can communicate via at least one midhaul link.

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

[0115] 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.

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

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

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

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

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

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

[0122] Beams are generally associated with resources. For example, during beam measurement, network devices measure different beams using different resources. The terminal device provides feedback on the measured resource quality, allowing the network device to determine the quality of the corresponding beam. During data transmission, beam information is also indicated through its corresponding resources. For instance, network devices use the TCI field in downlink control information (DCI) to indicate the physical downlink shared channel (PDSCH) beam information of the terminal device.

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

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

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

[0126] The reference signals used in this application, as examples, may include 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 track reference signal (PT-RS), cell reference signal (CRS), etc. It should be understood that the reference signals listed above are merely examples and should not constitute any limitation on this application. This application does not preclude the possibility of defining other reference signals in future protocols to achieve the same or similar functions.

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

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

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

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

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

[0132] 4. TCI-state (used to indicate the downlink beam):

[0133] Network devices can generate different beams pointing in different transmission directions. During downlink data transmission, when a network device uses a specific beam to send data to a terminal device, it needs to inform the terminal device of the transmitted beam information. This allows the terminal device to use the corresponding received beam to receive the data sent by the network device. One possible approach is for the network device to indicate the transmitted beam information to the terminal device through the TCI (transmission configuration indication) field in the DCI (Digital Channel Interface).

[0134] For example, the TCI field is 3 bits in size and can represent 8 different codepoints. Each value in the TCI field corresponds to an index of a TCI-state, which uniquely identifies a TCI-state. A TCI-state includes several parameters that determine information related to the transmitted beam. The TCI-state is configured by the network device for each terminal device, and its structure is shown below. Each TCI-state includes its own index, TCI State Id, and two QCL information entries (QCL-Info). Each QCL-Info includes a cell field and a bandwidth part (BWP) identifier (ID), indicating which cell and BWP the TCI-state applies to. Different cells or different BWPs within the same cell can be configured with different QCL-Info entries. The QCL-Info also includes a reference signal field, indicating which reference signal resource constitutes a QCL relationship between the beam indicated by the TCI-state and that reference signal resource. In data transmission and channel measurement, beams are associated with reference signal resources, one beam per reference signal resource. Therefore, when we say that the beam indicated by the TCI-state forms a QCL relationship with a specific reference signal resource, we are essentially referring to the beam with which the TCI-state forms a QCL relationship. A QCL relationship means that two reference signal resources (or two antenna ports, where there is also a one-to-one correspondence between antenna ports and reference signal resources) share certain spatial parameters. Which specific spatial parameters are identical depends on the type of the QCL-Info, specifically another field of the QCL-Info: QCL type (qcl-Type). qcl-Type can have four values: {type A, type B, type C, type D}. Taking type D as an example, type D indicates that the two reference signal resources have the same spatial reception parameter information, meaning the two beams have the same receiving beam. At most one of the two QCL-Info values ​​included in the TCI-state can be Type D.

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

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

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

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

[0139] 5. Spatial relation (used to indicate the uplink beam)

[0140] In one possible implementation, the uplink transmission beam is indicated by a spatial relation, which functions similarly to TCI-state, informing the terminal device which transmission beam to use for uplink transmission.

[0141] Spatial relations also need to be configured via RRC signaling. Their configuration structure can 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 the uplink transmission uses spatial relation #1, and this spatial relation #1 includes a target reference signal resource #2, it indicates that the transmit beam used for this uplink transmission is the transmit / receive beam of the target reference signal resource #2. For example, if the target reference signal resource #2 is an uplink SRS resource, it means that the transmit beam used for the uplink transmission is the transmit beam of that SRS (the transmit beam of that SRS is known). As another example, if the target reference signal resource #2 is a downlink resource such as SSB / CSI-RS, it means that the transmit beam used for the uplink transmission is the receive beam of that SSB / CSI-RS (the receive beam of that SSB / CSI-RS is known).

[0142] Network devices can configure multiple spatial relations for terminal devices. Then, one of these is activated via MAC-CE for the corresponding data transmission. Uplink transmission includes the Physical Uplink Control Channel (PUCCH), SRS, and Physical Uplink Shared Channel (PUSCH), each requiring a corresponding spatial relation. The spatial relation of PUCCH is indicated via MAC-CE signaling. The spatial relation of SRS is also indicated via MAC-CE signaling. During PUSCH transmission, a specific SRS is associated, and the spatial relation of that SRS is used for transmission.

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

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

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

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

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

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

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

[0150] Referring to Figure 4, which is a schematic diagram of beam management applicable to embodiments of this application.

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

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

[0153] Specifically, network devices perform beam scanning based on SSB (Special Signal Broadcast Band), meaning that network devices transmit beams in different directions at different times to achieve broadcast beam coverage of the cell. Simultaneously, terminal devices scan for and receive beams, meaning that terminal devices also receive signals using different beams 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 exceeding a certain threshold (or the optimal beam) among multiple beams, and the terminal device beam is also the beam with a received signal strength exceeding a certain threshold (or the optimal beam) among multiple beams.

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

[0155] Specifically, the network device determines candidate beams based on the optimal network device beam obtained in Phase 1, scans them using CSI-RS, and the terminal device receives the signal using the receiving beam selected in Phase 1, thereby fine-tuning the network device beams to determine the network device beam with the highest signal strength (or the optimal network device beam).

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

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

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

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

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

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

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

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

[0164] Based on this, beam reporting triggered by terminal devices or events is introduced. Specifically, terminal devices can report based on events, and different events may trigger different reporting content.

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

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

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

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

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

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

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

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

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

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

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

[0176] Optionally, method 500 includes S501 and S502.

[0177] S501, the terminal device sends the first instruction information. Correspondingly, the network device receives the first instruction information.

[0178] The first indication information indicates the event information supported by the terminal device. The first indication information can also be called terminal capability information.

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

[0180] 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 CSI report, an event-triggered or UE-initiated beam measurement result report, an event-triggered or UE-initiated interference measurement report, interference measurement report, CSI report, beam measurement result report, etc.

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

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

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

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

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

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

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

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

[0189] For example, the first indication information includes indexes to various event tables supported by the terminal device, where an event table includes one or more events.

[0190] For example, the information in the first indication includes the number of events supported by the terminal device.

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

[0192] In S502, the terminal device receives configuration information. Correspondingly, the network device sends configuration information.

[0193] This configuration information includes information on X events, where X is an integer greater than 0. It should be understood that X events can also be replaced with at least one event.

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

[0195] 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 events indicated by the terminal device through the first indication information. In this case, method 500 may not include S502, meaning the network device does not need to configure the information of the X events to the terminal device.

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

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

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

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

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

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

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

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

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

[0205] 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.

[0206] Here, the first beam represents the serving beam, that is, the current serving beam; the second beam represents a beam different from the serving beam, such as the beam of the 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.

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

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

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

[0210] The events listed above are described below.

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

[0212] To distinguish it, 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.

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

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

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

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

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

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

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

[0220] To distinguish it, this event is referred to as 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 currently serving 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 currently serving beam is less than or equal to a threshold, such as the fourth preset threshold.

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

[0222] 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.

[0223] To distinguish them, this event is called event #E. In other words, event #E indicates that there is at least one new beam with a beam quality greater than a certain threshold, and the beam quality of the currently serving beam is less than or equal to a threshold.

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

[0225] To distinguish it, this event is referred to as event #F. For example, the current serving beam is a CSI-RS with QCL type type D in the currently indicated TCI-state, and the preset beam is an SSB that satisfies that the CSI-RS has QCL type type D. 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). At this time, the seventh preset threshold can be a value less than 0 dB.

[0226] The event #F can also be described as follows: the beam quality of the preset beam is greater than or equal to the beam quality of the first beam by a threshold, and this threshold can be a value greater than 0 dB.

[0227] It is understandable that in the above examples, the situation regarding "equal to" can be either a situation where the event has occurred or a situation where the event has not occurred. That is, the events defined above may not include "equal to", or they may be used for other purposes, which are not limited.

[0228] In S503, the terminal device sends the first information. Correspondingly, the network device receives the first information.

[0229] If at least one of the X events occurs, the terminal device sends first information to the network device. Taking event #A as an example, the occurrence of event #A indicates that the following condition has occurred: the first beam quality is less than a 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, then event #A is determined to have occurred. As another example, if the terminal device determines through measurement that the second beam quality is greater than or equal to the second preset threshold, then event #B is determined to have occurred. The occurrence of an event triggers a report, that is, it triggers the reporting of the measurement report corresponding to that event.

[0230] The terminal device reports a measurement report related to one of X events through first information. Specifically, the first information includes the measurement report related to one of the X events, or the first information indicates the measurement report related to one of the X events. The load corresponding to the first information is the load corresponding to the measurement report related to the first event among the X events. The event occurring among the X events can be the first event, or it can be another event different from the first event; this application does not limit this.

[0231] The first event can be a predefined event, an event indicated by the network device to the terminal device, or an event indicated by the terminal device to the network device. Alternatively, the first event can be the event among X events where the load size of the related measurement reports is greater than or equal to a threshold. For example, the first event is the event with the largest load size among the X events. For instance, if the X events are event #1, event #2, ..., event #X, and the load sizes of the related measurement reports for event #1, event #2, ..., event #X are P1, P2, ..., PX respectively, and the load size Pn of the related measurement report for event #n is the largest among P1 to PX, then event #n is the first event.

[0232] The payload size for event-related measurement reports refers to the payload size required to report the event-related measurement report, or the number of bits / bit space / bit width required to report the event-related measurement report. More specifically, the payload size required to report an event-related measurement report refers to the payload size (or number of bits / bit space / bit width) required to report the reported parameters included in the event-related measurement report. For example, if an event #m-related measurement report includes reported parameters #a, #b, ..., #k, and the number of bits required to report each reported parameter is Pa, Pb, ..., Pk respectively, then the payload size required to report the event #m-related measurement report is (Pa + Pb + ... + Pk). For example, if an event #m-related measurement report includes k reported parameters #a, l reported parameters #b, ..., m reported parameters #k, and the number of bits required to report each reported parameter is Pa, Pb, ..., Pk respectively, then the payload size required to report the event #m-related measurement report is (k * Pa + Pb + ... + m * Pk). Wherein, the reported parameter #a can be one of the reported parameters #1 to #11 described below, the reported parameter #b can be one of the reported parameters #1 to #11 described below, ..., the reported parameter #k can be one of the reported parameters #1 to #11 described below. Alternatively, one or more of the reported parameters #a to #k may not be limited to the reported parameters described below. It is understood that when the terminal device and network device determine the event-related measurement report, they can determine the workload required to report the event-related measurement report.

[0233] Measurement reports related to different events among the X events can be predefined by the protocol or configured by the network device; this application does not limit this.

[0234] Optionally, at least two of the X events may have different measurement reports.

[0235] Optionally, at least two of the X events have different load sizes for the related measurement reports.

[0236] Measurement reports related to any one of the X events may include one or more of the following reported parameters (or reported quantities).

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

[0238] Report parameter #2, the quality of the current serving beam. For example, the RSRP or SINR of the current serving beam.

[0239] The currently serving beam may include one or more beams, and this application does not limit this. The number of currently serving beams can be determined based on the number of UL / DL / jointTCI states indicated by the network device, such as the UL / DL / jointTCI states indicated by DCI signaling. Alternatively, the number of beams included in the currently serving beam may be predefined by the protocol or preconfigured by the network device. Or, the maximum number of beams included in the currently serving beam may be predefined by the protocol or configured by the network device.

[0240] Report parameter #3, the index of the second beam, can also be understood as the index of the reference signal with QCL type type D in the activated TCI-states (excluding the indicated TCI-state), or it can be one or more reference signals (excluding the reference signal corresponding to the current serving beam) in the reference signals configured by the network device (such as the reference signal configured by the network device for measurement, or the reference signal configured by the network device for the terminal device to monitor the occurrence of events).

[0241] Report parameter #4, the quality of the second beam. For example, the RSRP or SINR of the second beam.

[0242] The second beam may include one or more beams, and this application does not limit this. 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.

[0243] Reporting parameter #5, cell information, can also be understood as identifying which cell the reported measurement report corresponds to, or stating which cell's reference signal resources the reported measurement result refers to. For example, cell information can be the handover candidate cell ID, the non-serving cell ID (additional PCI), the component carrier (CC) index, or the PCI. In this application embodiment, the ID mentioned can be an abbreviation of any one of identifier, indication, indicator, index, identity, or identification; these terms can be interchanged.

[0244] Report parameter #6, the reason why the current service beam quality is below a threshold (e.g., the first preset threshold). For example, network device beam misalignment, terminal device receive beam misalignment, transmit / receive beam misalignment, etc. "Misalignment" can also be replaced with terms like "expired" or "invalid." Alternatively, it can indicate whether to trigger a CSI-RS set measurement with "repetition" set to "on" to poll the UE's receive beam.

[0245] Report parameter #7, reference signal resource set index, such as CSI-RS resource set index, CSI-IM resource set index, CSI-SSB resource set index, or reference signal resource set index configured by the network device for the terminal device to monitor the occurrence of events, used to indicate which reference signal resource set the reported current serving beam and / or second beam belongs to.

[0246] Report parameter #8, report configuration index, such as CSI report configuration identifier (CSI-ReportConfigId), or event-triggered report configuration index.

[0247] Report parameter #9, event information, such as an index of the event that occurred, or one or more bits indicating whether the event occurred. For example, the event information includes M bits. An index used to indicate an event that has occurred. For example, event information includes X bits, each corresponding to one of X events. The x-th bit of the X bits indicates whether the event corresponding to that x-th bit has occurred, where x = 1, 2, ..., X. For instance, if the x-th bit has a value of "0", then the x-th bit indicates that the event corresponding to that x-th bit has occurred; or, if the x-th bit has a value of "1", then the x-th bit indicates that the event corresponding to that x-th bit has occurred.

[0248] Report parameter #10, capabilityindex, used to determine the maximum number of SRS ports.

[0249] Report parameter #11, channel state information, which may include one or more of the following: precoding matrix indicator (PMI), rank indicator (RI), channel quality indicator (CQI), and layer indicator (LI).

[0250] Optionally, if a measurement report related to one of the X events includes multiple reporting parameters, the terminal device reports these multiple reporting parameters in a predefined or preconfigured reporting order. In other words, the bit space of the first information is sequentially 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, if a measurement report related to one of the X events includes the aforementioned reporting parameter #1 and reporting parameter #2, the terminal device reports reporting parameter #1 first, then reporting parameter #2, according to the predefined or preconfigured reporting order. That is, reporting parameter #1 occupies the bit space before the first information, and reporting parameter #2 occupies the bit space after the first information.

[0251] Optionally, if one of the X events is the second event, and the payload size of the measurement report related to the second event is smaller than the payload size of the first information, then the portion of the first information excluding the measurement report related to the second event is a predefined value. For example, the bits in the first information other than those used to carry the measurement report related to the second event are padded with 0. For example, if the payload size of the first information is S bits, and the payload size of the measurement report related to the second event is L bits, if L < S, then 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 padded with 0. S and L are positive integers. As another example, if the payload size of the first information is S bits, and the measurement report related to the second event includes reporting parameters #a and #b, with the number of bits required for reporting parameters #a and #b being Pa and Pb respectively, if (Pa + Pb) < S, then 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 padded with 0. Among them, the reporting parameter #a can be one or more of the reporting parameters #1 to #11 described above, and the reporting parameter #b can be one or more of the reporting parameters #1 to #11 described above.

[0252] The second event differs from the first event. It can be understood that if the first event is the event with the largest load size corresponding to the relevant measurement report among the X events, then the second event can be any event among the X events other than the first event.

[0253] Optionally, if one of the X events is a third event, and the payload size of the measurement report related to the third event is greater than the payload size of the first information, then the first information includes a portion of the measurement report related to the third event. For example, the terminal device can discard (drop) a portion of the measurement report related to the third event according to a predefined or preconfigured reporting order. For example, if the payload size of the first information is S bits, and the payload size of the measurement report related to the third event is L' bits, if L' > S, then the terminal device drops the last (L'-S) bits of the measurement report related to the third event and reports the first S bits of the measurement report related to the third event through the first information. L' is a positive integer. For example, the payload size of the first information is S bits, and the measurement report related to the third event includes reporting parameters #c, #d, and #e. The number of bits required for reporting parameters #c, #d, and #e are Pc, Pd, and Pe, respectively. If (Pc+Pd+Pe)>S, then the terminal device reports some of the parameters from reporting parameters #c, #d, and #e through the first information according to the predefined or preconfigured reporting order. For example, if the reporting order of reported parameters #c and #d is first, and (Pc+Pd)≤S, (Pc+Pd+Pe)>S, then the terminal device drops reported parameter #e and reports reported parameters #c and #d through the first information; or, the terminal device drops the last (S-Pc-Pd) bits of reported parameter #e and reports the first (Pc+Pd+Pe-S) bits of reported parameters #c, #d, and #e through the first information. Here, reported parameter #c can be one or more of reported parameters #1 to #11 described above, reported parameter #d can be one or more of reported parameters #1 to #11 described above, and reported parameter #e can be one or more of reported parameters #1 to #11 described above.

[0254] The third event differs from the first event.

[0255] Optionally, if one of the X events is the 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 related to the fourth event, and there is no need to fill in predefined values. In other words, the terminal device can report the measurement reports related to the fourth event according to a predefined or preconfigured reporting order.

[0256] Among them, the fourth event may be the same as or different from the first event.

[0257] Optionally, if one of the X events is the fifth event, and the measurement report related to the fifth event contains one or more reporting parameters, and the number of reports corresponding to reporting parameter #f 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 the reporting parameter #f included in the measurement report related to the fifth event, is a predefined value. Here, reporting parameter #f can be one of the reporting parameters #1 to #11 described above. For example, the reported parameter #f is the reported parameter #3 described above, which is the index of the second beam. The network device or protocol specifies that the maximum number of beams included in the second beam is 4. In this case, the number of bits corresponding to the reported parameter #f in the first information is Pf. Pf bits can be used to carry the index of 4 beams. The reported parameter #f included in the measurement report related to the fifth event includes the index of 2 beams. The number of bits required for the index of these 2 beams is Pf / 2. Therefore, Pf / 2 bits of the Pf bits corresponding to the reported parameter #f in the first information carry the reported parameter #f included in the measurement report related to the fifth event, and the other Pf / 2 bits are filled with 0.

[0258] 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, then the terminal device does not send the first information.

[0259] 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. Indication information #1 indicates at least one of the following: whether an event has occurred among the X events, and information about the events that have occurred among the X events.

[0260] Optionally, the X events may include multiple events. The terminal device reports a measurement report related to one of the multiple events using the first information. For example, the terminal device reports the measurement report related to the first-ordered event among the multiple events using the first information, according to a predefined or pre-configured first order. For example, if the X events include events #m and #r, and event #m is ordered first, then the terminal device reports the measurement report related to event #m using the first information. Optionally, the terminal device may also report the measurement report related to event #r using second information. Further description of the second information can be found in the first information. The predefined or pre-configured first order can be: in descending order of event index, or in ascending order of event index, or in descending order of event priority.

[0261] Optionally, the terminal device can report measurement reports related to multiple events occurring in X events via the first information. If the sum of the payload sizes corresponding to the measurement reports related to the multiple events occurring in X events is less than the payload size of the first information, then the first information sent by the terminal device may include the measurement reports related to the multiple events occurring, and the portion of the first information other than the measurement reports related to the multiple events occurring is a predefined value. For example, the portion of the first information other than the measurement reports related to the multiple events occurring is filled with all zeros. For example, if the multiple events occurring in X events include the sixth event and the seventh event, and the sum of the payload sizes corresponding to the measurement reports related to the sixth event and the seventh event is less than the payload size of the first information, then the first information sent by the terminal device may include the measurement reports related to the sixth event and the seventh event. Assuming the payload size of the first information is S, the payload size required for the measurement reports related to the sixth event is S1, the payload size required for the measurement reports related to the seventh event is S2, and (S1+S2)<S, then the first (S1+S2) bits of the first information are used to carry the measurement reports related to the sixth and seventh events, and the last (S-S1-S2) bits of the first information are filled with all zeros.

[0262] Optionally, if the sum of the load sizes corresponding to the measurement reports related to multiple events occurring within the X events is greater than the load size of the first information, the terminal device can report some of the event-related measurement reports from the multiple events occurring in a predefined or preconfigured first order. In other words, the terminal device can discard (drop) some of the event-related measurement reports from the multiple events occurring in a predefined or preconfigured first order. For example, if the multiple events occurring within the X events include an eighth event and a ninth event, and the sum of the load sizes corresponding to the measurement reports related to the eighth event and the ninth event is greater than the load size of the first information, and the eighth event is listed first, then the terminal device can drop the measurement reports related to the ninth event and report the measurement reports related to the eighth event through the first information. Alternatively, if the load size corresponding to the measurement reports related to the eighth event is less than the load size corresponding to the first information, the terminal device can report all the measurement reports related to the eighth event and some of the measurement reports related to the ninth event through the first information. For example, the terminal device can report some of the reported parameters from the measurement reports related to the ninth event in a predefined or preconfigured reporting order and drop the remaining reported parameters.

[0263] Optionally, if the sum of the load sizes corresponding to the measurement reports related to multiple events occurring in X events equals the load size of the first information, then the first information includes all the measurement reports related to the multiple events occurring, and there is no need to fill in predefined values ​​in the first information. For example, the terminal device can report the measurement reports related to the multiple events occurring in a predefined or preconfigured first order.

[0264] Optionally, X events can be associated with X different measurement report configurations, or X events can be associated with the same measurement report configuration. For example, a measurement report configuration may include one or more of the following: beam measurement configuration, conditions for triggering a measurement report (such as one or more of the X events mentioned above), the format of the measurement report, and the period of the measurement report. For example, a beam measurement configuration may include information such as the beam identifier, bandwidth, and reference signal type being measured.

[0265] One possible implementation is that X event-related measurement reports 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.

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

[0267] Another possible implementation is that X event-related measurement reports are reported through different uplink resources, that is, the first information including the measurement reports related to different events is sent through different uplink resources.

[0268] Optionally, the method further includes: the network device configuring X uplink resources associated with X event-related measurement reports for the terminal device, wherein one of the X uplink resources is associated with one event-related measurement report from the X events. Optionally, the X uplink resources can be different uplink resources. Then, when the tenth event among the X events occurs, the load size of the first information including the measurement report related to the tenth event is the load size corresponding to the measurement report related to the tenth event.

[0269] In this embodiment, the terminal device can report events, thereby avoiding the terminal device reporting invalid measurement reports to the network device. Furthermore, the terminal device can report event-related measurement reports using first information with a fixed load size, thus avoiding resource waste caused by allocating corresponding reporting resources for each event when the terminal device supports or is configured with multiple events.

[0270] Referring to Figure 6, which is a schematic diagram of another communication method 600 provided in an embodiment of this application, the method 600 shown in Figure 6 may include the following steps.

[0271] Optionally, method 600 includes S601 and S602.

[0272] S601, the terminal device sends the first instruction information. Correspondingly, the network device receives the first instruction information.

[0273] For a more detailed description of S601, please refer to S501 in Method 500 above. For the sake of brevity, it will not be repeated here.

[0274] S602: The terminal device receives configuration information. Correspondingly, the network device sends configuration information.

[0275] For a more detailed description of S602, please refer to S502 in Method 500 above. For the sake of brevity, it will not be repeated here.

[0276] S603: The terminal device sends the first information. Correspondingly, the network device receives the first information.

[0277] If at least one of the X events occurs, the terminal device sends first information to the network device. Taking event #A as an example, the occurrence of event #A indicates that the following condition has occurred: the first beam quality is less than a 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, then event #A is determined to have occurred. As another example, if the terminal device determines through measurement that the second beam quality is greater than or equal to the second preset threshold, then event #B is determined to have occurred. The occurrence of an event triggers a report, that is, it triggers the reporting of the measurement report corresponding to that event.

[0278] The terminal device reports a measurement report related to at least one of the X events through a first information, that is, the first information includes a measurement report related to at least one of the X events, or the first information indicates a measurement report related to at least one of the X events.

[0279] The first message has a predefined format. The following describes two possible formats for the first message.

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

[0281] In this application, at least one common field corresponds to at least one common reporting parameter; for example, there is a one-to-one correspondence between at least one common field and at least one common reporting parameter. Taking common field #1 as an example, common field #1 carries the common reporting parameter corresponding to common field #1. In other words, the load size of common field #1 is the load size of the common reporting parameter corresponding to common field #1. It should be noted that common fields can also be named using other names, and this application does not limit this. Common reporting parameters can also be named using other names, and this application does not limit this.

[0282] It should be understood that if the measurement reports related to the X events include the public reporting parameters corresponding to public field #1, then the public field #1 included in the first information carries the public reporting parameters corresponding to public field #1. If the measurement reports related to the X events do not include the public reporting parameters corresponding to public field #1, or in other words, none of the events for which the measurement reports include the public reporting parameters corresponding to public field #1 have occurred, then the public field #1 included in the first information has a predefined value, for example, each bit of the public field #1 included in the first information is padded with 0.

[0283] At least one non-public field corresponds to at least one non-public reporting parameter; for example, there is a one-to-one correspondence between at least one non-public field and at least one non-public reporting parameter. Taking non-public field #1 among the 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 of non-public field #1. It should be noted that non-public fields can also be named with other names, and this application does not limit this. Non-public reporting parameters can also be named with other names, and this application does not limit this.

[0284] It should be understood that if the measurement reports related to the X events include non-public reporting parameters corresponding to non-public field #1, then the non-public field #1 included in the first information carries the non-public reporting parameters corresponding to non-public field #1. If the measurement reports related to the X events do not include the non-public reporting parameters corresponding to non-public field #1, or in other words, if the event for which the measurement report includes the non-public reporting parameters corresponding to non-public field #1 has not occurred, then the non-public field #1 included in the first information has a predefined value; for example, each bit of the non-public field #1 included in the first information is padded with 0.

[0285] In summary, the load size of the first information is the load size required to report at least one common reporting parameter and at least one non-common reporting parameter.

[0286] A common reporting parameter is a reporting parameter with the same value included in at least two of the X events. For example, a common reporting parameter is 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. Further description of the above reporting parameters can be found in S503 of method 500 above.

[0287] Non-common reporting parameters are reporting parameters with different values ​​included in the measurement reports related to different events among X events. For example, non-common 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. Further descriptions of the above reporting parameters can be found in S503 of Method 500 above.

[0288] The following example illustrates how to determine the format of the first message.

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

[0290] Table 1

[0291] The measurement reports related to events #1, #2, and #3 all include the reported parameter #g. If the reported parameter #g is a common reported parameter, then the first information includes a common field corresponding to the reported parameter #g (denoted as common field #1). The measurement related to event #2 includes the reported parameter #h, and the measurement reports related to the other events do not include the reported parameter #h. Therefore, the reported parameter #h is a non-common reported parameter, and the first information includes a non-common field corresponding to the reported parameter #h (denoted as non-common field #1). Both the measurement reports related to events #3 and #4 include reported parameter #i. If the value of reported parameter #i in the measurement report related to event #3 is the same as the value of reported parameter #i in the measurement report related to event #4, then reported parameter #i is a common reported parameter, and the first information includes a common field corresponding to reported parameter #i (denoted as common field #2). If the value of reported parameter #i in the measurement report related to event #3 is different from the value of reported parameter #i in the measurement report related to event #4, then reported parameter #3 is a non-common reported parameter, and the first information includes a non-common field corresponding to reported parameter #i in the measurement report related to event #3 (denoted as non-common field #2), and also includes a non-common field corresponding to reported parameter #i in the measurement report related to event #4 (denoted as non-common field #3). If the measurement related to event #4 includes reported parameter #j, and the measurement reports related to other events do not include reported parameter #j, then reported parameter #j is a non-public reported parameter. The first information includes a non-public field corresponding to reported parameter #j (denoted as non-public field #4).

[0292] In summary, based on the four events shown in Table 1 and the related measurement reports, a possible format for the first information is as follows: The first information includes a common field #1, a non-common field #2, a common field #3, and a non-common field #4. Specifically, common field #1 carries the reported parameter #g from the measurement reports related to events #1 to #3; non-common field #1 carries the reported parameter #h from the measurement report related to event #2; common field #2 carries the reported parameter #i from the measurement reports related to events #3 and #4; and non-common field #4 carries the reported parameter #j from the measurement report related to event #4. The load size of the first information is the sum of the load sizes corresponding to reported parameter #g, reported parameter #h, reported parameter #i, and reported parameter #j.

[0293] If events #1 and #2 out of 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 common field #1, the reporting parameter #h is carried on the non-common field #1, and the common field #2 and the non-common field #4 are predefined values, such as being filled with all 0s.

[0294] Table 2

[0295] Based on the four events shown in Table 1 and the related measurement reports, another possible format for the first information is as follows: The first information includes a common field #1, a non-common field #2, a non-common field #3, and a non-common field #4. Specifically, common field #1 carries the reported parameter #g from the measurement reports related to events #1 to #3; non-common field #1 carries the reported parameter #h from the measurement report related to event #2; non-common field #2 carries the reported parameter #i from the measurement report related to event #3; non-common field #3 carries the reported parameter #i from the measurement report related to event #4; and non-common field #4 carries the reported parameter #j from the measurement report related to event #4. The load size of the first information is the sum of the load sizes corresponding to reported parameter #g, reported parameter #h, reported parameter #i from the measurement report related to event #3, reported parameter #i from the measurement report related to event #4, and reported parameter #j.

[0296] If events #1 and #2 occur in events #1 to #4, 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 common field #1, the reporting parameter #h is carried on the non-common field #1, and the non-common fields #2 to #4 are predefined values, such as being filled with all 0s.

[0297] Table 3

[0298] 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 common reporting parameters and / or non-common reporting parameters related to the event in a predefined or preconfigured order.

[0299] Format 2, the first information includes at least one event field.

[0300] In this application, at least one event field corresponds to X events; for example, at least one event field corresponds one-to-one with X events. Taking event field #1 as an example, event field #1 is used to carry the measurement report related to the event corresponding to event field #1. In other words, the load size of event field #1 is the load size of the measurement report related to the event corresponding to event field #1. It should be noted that event fields can also be named with other names, and this application does not limit this.

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

[0302] Table 4

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

[0304] 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 index of the multiple events, in ascending order of the index of the multiple events, or in descending order of the priority of the multiple events.

[0305] In this embodiment, the terminal device can report events, thereby avoiding the terminal device reporting invalid measurement reports to the network device. Furthermore, the terminal device can report measurement reports related to one or more events using a predefined format of first information, thus avoiding resource waste caused by allocating corresponding reporting resources for each event when the terminal device supports or is configured with multiple events.

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

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

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

[0309] The methods provided by the embodiments of this application have been described in detail above with reference to Figures 5 and 6. The apparatus provided by the embodiments of this application will be described in detail below with reference to Figures 7 to 9. It should be understood that the descriptions of the apparatus embodiments correspond to the descriptions of the method embodiments; therefore, any content not described in detail can be referred to the method embodiments above, and for the sake of brevity, will not be repeated here.

[0310] Referring to Figure 7, which is a schematic diagram of a communication device 700 provided in an embodiment of this 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 communication unit. Optionally, the device 700 further 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 may include a modem chip, or a system-on-a-chip (SoC) chip or a SIP chip containing a modem core.

[0311] Optionally, the device 700 may further include a storage unit for storing instructions and / or data, and the processing unit 720 may read the instructions and / or data from the storage unit to enable the device to implement the aforementioned method embodiments.

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

[0313] In a first possible design, the device 700 can be the terminal device in the foregoing embodiments, which can implement the steps or processes corresponding to those executed by the terminal device in the above method embodiments. Specifically, the transceiver unit 710 can be used to perform transceiver-related operations (such as sending and / or receiving data or messages) of the terminal device in the above method embodiments. For example, the transceiver unit 710 can be used to execute S501, S502, and S503 in the embodiment shown in FIG. 5, or S601, S602, and S603 in the embodiment shown in FIG. 6. The processing unit 720 can be used to perform processing-related operations of the terminal device in the above method embodiments, or operations other than transceiver operations (such as operations other than sending and / or receiving data or messages).

[0314] In one possible implementation, the transceiver unit 710 is configured to receive configuration information, the configuration information including information about at least one event, the at least one event being related to a measurement report initiated by the terminal device; the transceiver unit 710 is also configured to send first information, the first information including a measurement report related to one of the at least one events, the load size corresponding to the first information being the load size corresponding to the measurement report related to the first event in the at least one event.

[0315] In one possible implementation, the transceiver unit 710 is configured to receive configuration information, the configuration information including information about at least one event, the at least one event being related to a measurement report initiated by the terminal device; the transceiver unit 710 is also configured to send first information, the first information including a measurement report related to one or more events occurring in the at least one event.

[0316] In a second possible design, the device 700 can be a network device as described in the foregoing embodiments. This device 700 can implement the steps or processes performed by the network device corresponding to those described in the method embodiments above. Specifically, the transceiver unit 710 can be used to perform transceiver-related operations (such as sending and / or receiving data or messages) of the network device in the method embodiments above. For example, the transceiver unit 710 can be used to execute steps S501, S502, and S503 in the embodiment shown in FIG. 5, or it can be used to execute S601, S602, and S603 in the embodiment shown in FIG. 6. The processing unit 720 can be used to perform processing-related operations of the network device in the method embodiments above, or operations other than transceiver operations (such as operations other than sending and / or receiving data or messages).

[0317] In one possible implementation, the transceiver unit 710 is configured to send configuration information, which includes information about at least one event, the at least one event being related to a measurement report initiated by the terminal device; the transceiver unit 710 is also configured to receive first information, which includes a measurement report related to one of the at least one events, 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.

[0318] In one possible implementation, the transceiver unit 710 is configured to send configuration information, the configuration information including information about at least one event, the at least one event being related to a measurement report initiated by the terminal device; the transceiver unit 710 is also configured to receive first information, the first information including a measurement report related to one or more events occurring in the at least one event.

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

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

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

[0322] In addition, the transceiver unit 710 described above can also be a transceiver circuit (for example, it may include a receiving circuit and a transmitting circuit), and the processing unit can be a processing circuit.

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

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

[0325] Optionally, there may be one or more processors 810.

[0326] Optionally, the memory 820 may be one or more.

[0327] Alternatively, the memory 820 can be integrated with the processor 810, or it can be set separately.

[0328] Optionally, as shown in FIG8, the device 800 further includes a transceiver 830 for receiving and / or transmitting signals. For example, the processor 810 is used to control the transceiver 830 to receive and / or transmit signals.

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

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

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

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

[0333] It should also be understood that the memory mentioned in the embodiments of this application can be volatile memory and / or non-volatile memory. Non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory can be random access memory (RAM). For example, RAM can be used as an external cache. By way of example and not limitation, RAM includes the following forms: static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous linked dynamic random access memory (SLDRAM), and direct rambus RAM (DR RAM).

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

[0335] 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.

[0336] It should also be noted that if device 800 includes processor 810, then device 800 can be a chip, chip system, or circuit. If device 800 also includes transceiver 830, then transceiver 830 can be the transceiver interface of the device, which is used to perform receiving or transmitting operations. The transceiver interface can include a receiving interface and a transmitting interface, where the receiving interface is used to perform receiving operations and the transmitting interface is used to perform transmitting operations. If device 800 also includes memory 820, then device 800 can be a communication module.

[0337] Referring to Figure 9, which is a schematic diagram of a chip system 900 provided in an embodiment of this application, the chip system 900 (or processing system) includes logic circuitry 910 and an input / output interface 920.

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

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

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

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

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

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

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

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

[0346] This application also provides a communication system that includes the terminal device and / or network device described in the above embodiments. For example, the system includes the terminal device and network device shown in FIG5 or FIG6.

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

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

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

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

Claims

A communication method characterized by comprising: include: Receive configuration information, the configuration information including information on at least one event, the at least one event being related to the measurement report initiated by the terminal device; Send first information, the first information including a measurement report related to an event that occurred 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 characterized by comprising: include: Send configuration information, which includes information about at least one event, the at least one event being related to the measurement report initiated by the terminal device; Receive first information, the first information including a measurement report related to an event that occurred 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, characterized in that The measurement reports related to at least one event are associated with the same uplink resource, which is used to carry the first information. The method according to any one of claims 1 to 3, characterized in that At least two of the events mentioned above have different related measurement reports. The method according to any one of claims 1 to 4, characterized in that In the at least one event, at least two of the related measurement reports have different load sizes. The method according to any one of claims 1 to 5, characterized in that The first event is the event with the largest load size corresponding to the relevant measurement report among the at least one events. The method according to any one of claims 1 to 6, characterized in that If one of the at least one events occurs, it is designated as the second event. If the load size corresponding to the measurement report related to the second event is less than the load 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. The method of claim 7, wherein The predefined value is 0. The method according to any one of claims 1 to 8, characterized in that 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 the 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 the fourth threshold value; Wherein, the first beam is the serving beam, and the second beam is a beam different from the first beam. The method according to any one of claims 1 to 9, characterized in that The measurement report related to one of the at least one events 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 of 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 of one of the at least one events, the capability index, and the channel state information. Wherein, the first beam is the serving 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 characterized by comprising: include: Receive configuration information, the configuration information including information on at least one event, the at least one event being related to the measurement report initiated by the terminal device; Send a first message, which includes a measurement report related to an event that occurred in the at least one event. A communication method characterized by comprising: include: Send configuration information, which includes information about at least one event, the at least one event being related to the measurement report initiated by the terminal device; Receive first information, the first information including an event-related measurement report that occurred in the at least one event. The method according to claim 12 or 13, characterized in that The measurement reports related to at least one event are associated with the same uplink resource, which is used to carry the first information. The method according to any one of claims 12 to 14, 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 with at least one public reporting parameter, and the at least one non-public field corresponds one-to-one with 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 of the at least one events. The non-public reporting parameter is a reporting parameter with different values ​​included in the measurement reports related to different events of the at least one event. The method according to claim 15, characterized in that, If the event-related measurement report for at least one of the events does not include the first common reporting parameter, then 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 at least one of the events includes a first public reporting parameter, then the public field corresponding to the first public reporting parameter carries the first public reporting parameter. The method according to claim 15 or 16 is characterized in that, If the event-related measurement report for at least one of the events does not include a first non-public reporting parameter, then 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 of the events includes a first non-public reporting parameter, then 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 corresponds one-to-one with the at least one event. The method according to claim 18, characterized in that, If event #p in at least one of the events does not occur, then the event field corresponding to event #p is a predefined value; or, If event #p occurs in at least one of the events, the event field corresponding to event #p carries a measurement report related to event #p. The method according to claim 18 or 19, characterized in that The first information includes multiple event-related measurement reports that occurred in the at least one event, and the multiple event-related measurement reports are arranged in a first order. The method of claim 20, wherein The first order is one of the following: in descending order of the indexes of the plurality of events, in ascending order of the indexes of the plurality of events, or in descending order of the priority of the plurality of events. The method according to any one of claims 18 to 21, characterized in that The first information includes a measurement report related to event #q that occurred in the at least one event, and the multiple reported parameters included in the event #q measurement report 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, characterized in that 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 the second preset threshold; The difference between the quality of the second beam and the quality of the first beam is greater than or equal to the third preset threshold; The difference between the quality of the second beam and the quality of the first beam is less than or equal to the fourth preset threshold; Wherein, the first beam represents the 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, characterized in that The measurement report related to one of the at least one events includes one or more of the following: Index of the first beam, quality of the first beam, index of the second beam, quality of the second beam, information of the cell corresponding to the event-related measurement report, reason why the quality of the first beam is lower than the threshold, reference signal resource set index, reporting configuration index, information of an event that occurred in at least one event, capability index, channel state information; Wherein, the first beam is the serving beam, and the second beam is a beam different from the first beam. A communication device, characterized by Including transceiver units, The transceiver unit 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 initiated by the terminal device. The transceiver unit is further configured to send first information, the first information including 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, characterized by Including transceiver units, The transceiver unit 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 initiated by the terminal device. The transceiver unit is further configured to send first information, the first information including a measurement report related to an event that occurred in the at least one event. A communication device, characterized by Including transceiver units, The transceiver unit is used to send configuration information, which includes information about at least one event, and the at least one event is related to the measurement report initiated by the terminal device. The transceiver unit is further configured to receive first information, the first information including 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, characterized by Including transceiver units, The transceiver unit is used to send configuration information, which includes information about at least one event, and the at least one event is related to the measurement report initiated by the terminal device. The transceiver unit is further configured to receive first information, the first information including a measurement report related to an event that occurred in the at least one event. A communication device, characterized by It includes modules or units for performing the method of any one of claims 1, 3 to 12, or 14 to 25, or includes modules or units for performing the method of any one of claims 3 to 11 or 13 to 25. A communication device, characterized by The device includes at least one processor, which is configured to execute a computer program or instructions to cause the device to perform the method of any one of claims 1, 3 to 12 or 14 to 25, or to cause the device to perform the method of any one of claims 3 to 11 or 13 to 25. The apparatus according to claim 31 is characterized in that, The device further includes a memory for storing the computer program or instructions; and / or, The device further includes a communication interface coupled to the at least one processor, the communication interface being used for inputting and / or outputting information. A computer-readable storage medium, characterized by The computer-readable storage medium stores a computer program or instructions that, when executed on a communication device or computer, cause the communication device to perform the method as described in any one of claims 1, 3 to 12, or 14 to 25, or cause the communication device to perform 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 performing the method as described in any one of claims 1, 3 to 12, or 14 to 25; or, the computer program product includes a computer program or instructions for performing the method as described in any one of claims 3 to 11 or 13 to 25.