Wireless communication method, communication apparatus, storage medium and computer program product

Abstract

The present application provides a wireless communication method, a communication apparatus, a storage medium and a computer program product, and provides a clear solution for a terminal device to indicate the type of a trigger event to a network device. The method is executed by a terminal device, and comprises: if a first trigger event is detected, sending a first channel to a network device, wherein the first channel is used for requesting resources for a second channel from the network device, or the first channel is used for notifying the network device to receive the second channel, the second channel is used for carrying a channel state information report based on the first trigger event, and the first channel and / or the second channel are / is used for indicating related information of the first trigger event.

Description

Wireless communication method, communication apparatus, storage medium and computer program product

[0001] The present application claims priority to the Chinese patent application No. 202411053149.6, filed on August 1, 2024, entitled "Wireless communication method, communication apparatus, storage medium and computer program product", the content of which is incorporated herein by reference in its entirety. TECHNICAL FIELD

[0002] The present application relates to the field of communication, and in particular to a wireless communication method, a communication apparatus, a storage medium and a computer program product. BACKGROUND

[0003] In order to improve the reliability of communication, a terminal device can measure a channel state to obtain a measurement result, and send a channel information state (CSI) report to a network device based on the measurement result. In order to reduce the overhead of sending the CSI report and reduce the feedback delay of the CSI report, a CSI report based on a triggering event is introduced.

[0004] For the CSI report based on the triggering event, how does the terminal device indicate the type of the triggering event to the network device, and there is no clear solution at present. SUMMARY

[0005] The present application provides a wireless communication method, a communication apparatus, a storage medium and a computer program product, which provides a clear solution for the terminal device to indicate the type of the triggering event to the network device.

[0006] In a first aspect, a wireless communication method is provided, the method is executed by a terminal device, and includes: if a first triggering event is detected, sending a first channel to a network device, the first channel is used to request a resource of a second channel from the network device, or the first channel is used to notify the network device to receive the second channel, the second channel is used to carry a channel information state report based on the first triggering event; wherein the first channel and / or the second channel is used to indicate related information of the first triggering event.

[0007] The present application embodiment indicates the related information (i.e. the type of the triggering event) of the triggering event through the first channel and / or the second channel, so that the terminal device knows the way of indicating the type of the triggering event to the network device, and the network device can know which triggering event triggers the current CSI report, which is beneficial to ensure the correct transmission of the CSI report.

[0008] In some implementations, the related information of the first trigger event includes a first report configuration corresponding to the first trigger event, and the first channel and / or the second channel correspond to the first report configuration.

[0009] The embodiments of the present application can indicate the type of the trigger event to the network device through the correspondence between the first channel and / or the second channel and the report configuration, which can reduce the signaling overhead required for indicating the type of the trigger event.

[0010] In some implementations, the first channel and / or the second channel correspond to the first report configuration, including that a first resource corresponds to the first report configuration, and the first resource includes one or more of the following: a transmission resource of the first channel; a resource related to the transmission resource of the first channel; a transmission resource of the second channel.

[0011] Through the correspondence between the first resource and the first report configuration, the terminal device can indicate the type of the trigger event to the network device through the first resource, and the network device can determine the type of the trigger event based on the first resource, so that the network device can quickly determine the type of the trigger event.

[0012] In some implementations, the first resource corresponds to the first report configuration, including that an index of the first resource corresponds to an index of the first report configuration.

[0013] The correspondence between the first resource and the first report configuration can be determined through the index of the first resource and the index of the first report configuration.

[0014] In some implementations, the first resource corresponds to the first report configuration, including that the first resource corresponds to one or more trigger states, and the one or more trigger states are used to indicate the first report configuration.

[0015] The type of the trigger event in the embodiments of the present application can be at the granularity of the trigger state, which can reduce the number of corresponding relationships that need to be configured and reduce the complexity of implementation. In addition, if the first resource corresponds to multiple trigger states, more types of trigger events can be indicated through fewer resources, the number of first resources that need to be configured is reduced, and the resource utilization rate is improved.

[0016] In some implementations, the first resource corresponds to the one or more trigger states, including that an index of the first resource corresponds to an index of the one or more trigger states.

[0017] The correspondence between the first resource and the first report configuration is established by an index of the first resource and an index of the trigger state, so that the correspondence between the first resource and the trigger state can be determined.

[0018] In some implementations, the first resource corresponds to the first report configuration, including that the first resource corresponds to report configuration of one or more component carriers, and the report configuration of the one or more component carriers includes the first report configuration.

[0019] The type of the trigger event in the embodiments of the present application can be in the granularity of a component carrier, which can reduce the number of corresponding relationships that need to be configured and reduce the complexity of implementation. In addition, if the first resource corresponds to multiple component carriers, a smaller number of resources can be used to indicate a larger number of types of trigger events, which reduces the number of first resources that need to be configured and is beneficial to improve resource utilization.

[0020] In some implementations, the transmission resource of the first channel is a physical uplink control channel (PUCCH) resource, and / or the resource related to the transmission resource of the first channel is a scheduling request resource, and / or the transmission resource of the second channel is a PUCCH resource or a physical uplink shared channel (PUSCH) resource.

[0021] In some implementations, the transmission resource of the first channel is a PUCCH resource associated with a scheduling request resource, and one scheduling request resource is associated with one or more PUCCH resources.

[0022] By associating multiple PUCCH resources with one scheduling request resource, more types of trigger events can be indicated to the network device without increasing the number of scheduling request resources.

[0023] In some implementations, the PUCCH resource is determined based on one or more of the following parameters: time domain position of a PUCCH reference resource, frequency domain position of the PUCCH reference resource, cyclic shift, orthogonal cover code, frequency division multiplexing number, frequency division interval, time division multiplexing number, and time division interval.

[0024] The PUCCH resource in the embodiments of the present application can be determined by the terminal device according to some parameters, which can reduce the number of PUCCH resources configured by the network device for the terminal device and reduce signaling overhead. In addition, the PUCCH resource determined in this way is relatively concentrated, which is convenient for the network device to reserve resources.

[0025] In some implementations, the index of the PUCCH resource is related to an ordering priority of the PUCCH resource, and the ordering priority of the PUCCH resource is determined based on one or more of the following parameters: a time domain location of the PUCCH resource, a frequency domain location of the PUCCH resource, a cyclic shift used by a PUCCH sequence, an orthogonal cover code used by a PUCCH sequence.

[0026] By determining the index of the PUCCH resource based on the ordering priority of the PUCCH resource, an explicit solution is provided for determining the index of the PUCCH resource.

[0027] In some implementations, the PUSCH resource is determined based on one or more of the following parameters: a time domain location of a PUSCH reference resource, a frequency domain location of the PUSCH reference resource, a demodulation reference signal (DMRS) port number, a DMRS sequence, a frequency division multiplexing number, a frequency division interval, a time division multiplexing number, and a time division interval.

[0028] The PUSCH resource in the embodiments of the present application can be determined by the terminal device according to some parameters, which can reduce the number of PUSCH resources configured by the network device for the terminal device and reduce the signaling overhead. In addition, the PUSCH resource determined in this way is relatively concentrated, which facilitates the network device to reserve resources.

[0029] In some implementations, the index of the PUSCH resource is related to an ordering priority of the PUSCH resource, and the ordering priority of the PUSCH resource is determined based on one or more of the following parameters: a time domain location of the PUSCH resource, a frequency domain location of the PUSCH resource, a DMRS port number used by the PUSCH reference resource, a DMRS sequence used by the PUSCH reference resource.

[0030] By determining the index of the PUSCH resource based on the ordering priority of the PUSCH resource, an explicit solution is provided for determining the index of the PUSCH resource.

[0031] In some implementations, the second channel includes first indication information, and the first indication information is used to indicate related information of the first trigger event.

[0032] By directly carrying the first indication information in the second channel to indicate the type of the trigger event, the complexity of indicating the type of the trigger event can be reduced.

[0033] In some embodiments, the first indication information is carried in a first field and / or a second field of the channel state information report, the first field is used to indicate information of a first reporting configuration corresponding to the first trigger event, and the second field is used to indicate information of a component carrier to which the first reporting configuration belongs, and the information of the first reporting configuration and / or the information of the component carrier are used to indicate the related information of the first trigger event.

[0034] In some embodiments, the second channel is related to overhead required for transmitting the channel state information, and the overhead required for transmitting the channel state information is used to indicate the related information of the first trigger event.

[0035] By indicating the type of the trigger event through the correspondence between the feedback overhead and the second channel, the signaling overhead required for indicating the type of the trigger event can be reduced.

[0036] In some embodiments, the first trigger event includes a plurality of trigger events, and the method further includes: if the second channel cannot carry all of a plurality of channel state information reports corresponding to the plurality of trigger events, determining the channel state information report carried in the second channel based on priorities of the plurality of channel state information reports.

[0037] For the case where a plurality of trigger events occur, if the second channel cannot carry all CSI reports, the embodiments of the present application provide a scheme for the second channel to carry which CSI reports, i.e., the second channel can carry which CSI reports and discard which reports according to the priorities of the CSI reports.

[0038] In some embodiments, the priorities of the plurality of channel state information reports are determined based on one or more of the following information: a transmission mode of the channel state information report, a channel type carrying the channel state information report, an index of a reporting configuration corresponding to the channel state information report, and an index of a component carrier corresponding to the channel state information report.

[0039] In a second aspect, a wireless communication method is provided, which is performed by a network device and includes: receiving a first channel sent by a terminal device, the sending of the first channel being triggered by a first trigger event; based on the first channel, scheduling a resource of a second channel or receiving the second channel for the terminal device, the second channel being used to carry a channel state information report based on the first trigger event; and the first channel and / or the second channel are used to indicate related information of the first trigger event.

[0040] In some embodiments, the related information of the first trigger event includes a first reporting configuration corresponding to the first trigger event, and the first channel and / or the second channel correspond to the first reporting configuration.

[0041] In some embodiments, the first channel and / or the second channel correspond to the first reporting configuration includes that a first resource corresponds to the first reporting configuration, and the first resource includes one or more of the following: a transmission resource of the first channel; a resource related to the transmission resource of the first channel; a transmission resource of the second channel.

[0042] In some embodiments, the first resource corresponds to the first reporting configuration includes that an index of the first resource corresponds to an index of the first reporting configuration.

[0043] In some embodiments, the first resource corresponds to the first reporting configuration includes that the first resource corresponds to one or more trigger states, and the one or more trigger states are used to indicate the first reporting configuration.

[0044] In some embodiments, the first resource corresponds to the one or more trigger states includes that an index of the first resource corresponds to an index of the one or more trigger states.

[0045] In some embodiments, the first resource corresponds to the first reporting configuration includes that the first resource corresponds to a reporting configuration of one or more component carriers, and the reporting configuration of the one or more component carriers includes the first reporting configuration.

[0046] In some embodiments, the transmission resource of the first channel is a physical uplink control channel (PUCCH) resource; and / or

[0047] The resource related to the transmission resource of the first channel is a scheduling request resource; and / or the transmission resource of the second channel is a PUCCH resource or a physical uplink shared channel (PUSCH) resource.

[0048] In some embodiments, the transmission resource of the first channel is a PUCCH resource associated with a scheduling request resource, and one scheduling request resource is associated with one or more PUCCH resources.

[0049] In some embodiments, the PUCCH resource is determined based on one or more of the following parameters: a time domain position of a PUCCH reference resource, a frequency domain position of the PUCCH reference resource, a cyclic shift, an orthogonal cover code, a frequency division multiplexing number, a frequency division interval, a time division multiplexing number, and a time division interval.

[0050] In some implementations, the index of the PUCCH resource is related to an ordering priority of the PUCCH resource, and the ordering priority of the PUCCH resource is determined based on one or more of the following parameters: a time domain location of the PUCCH resource, a frequency domain location of the PUCCH resource, a cyclic shift used by a PUCCH sequence, an orthogonal cover code used by a PUCCH sequence.

[0051] In some implementations, the PUSCH resource is determined based on one or more of the following parameters: a time domain location of a PUSCH reference resource, a frequency domain location of the PUSCH reference resource, a demodulation reference signal (DMRS) port number used by the PUSCH reference resource, a DMRS sequence used by the PUSCH reference resource, a number of frequency division multiplexing, a frequency division interval, a number of time division multiplexing, and a time division interval.

[0052] In some implementations, the index of the PUSCH resource is related to an ordering priority of the PUSCH resource, and the ordering priority of the PUSCH resource is determined based on one or more of the following parameters: a time domain location of the PUSCH resource, a frequency domain location of the PUSCH resource, a DMRS port number used by the PUSCH reference resource, a DMRS sequence used by the PUSCH reference resource.

[0053] In some implementations, the first indication information is included in the second channel, and the first indication information is used to indicate the related information of the first trigger event.

[0054] In some implementations, the first indication information is carried in a first field and / or a second field of the channel state information report, the first field is used to indicate information of a first reporting configuration corresponding to the first trigger event, and the second field is used to indicate information of a component carrier to which the first reporting configuration belongs, and the information of the first reporting configuration and / or the information of the component carrier are used to indicate the related information of the first trigger event.

[0055] In some implementations, the second channel is related to an overhead required for transmitting the channel state information, and the overhead required for transmitting the channel state information is used to indicate the related information of the first trigger event.

[0056] In a third aspect, a communication apparatus is provided, which includes a unit composed of software and / or hardware, and the unit is configured to execute any of the methods in the technical solutions of the first aspect.

[0057] In a fourth aspect, a communication apparatus is provided, which includes a unit composed of software and / or hardware, and the unit is configured to execute any of the methods in the technical solutions of the second aspect.

[0058] In a fifth aspect, a chip is provided, including a processor; the processor is configured to read and execute a computer program stored in a memory to perform any of the methods in the technical solutions of the first aspect.

[0059] Optionally, the chip further includes a memory, which is connected with the processor through a circuit or a wire.

[0060] Further optionally, the chip further includes a communication interface.

[0061] In a sixth aspect, a chip is provided, including a processor; the processor is configured to read and execute a computer program stored in a memory to perform any of the methods in the technical solutions of the second aspect.

[0062] Optionally, the chip further includes a memory, which is connected with the processor through a circuit or a wire.

[0063] Further optionally, the chip further includes a communication interface.

[0064] In a seventh aspect, a terminal device is provided, including a processor, a memory and an interface; the processor, the memory and the interface cooperate with each other to enable the terminal device to perform any of the methods in the technical solutions of the first aspect; or include any of the chips in the fifth aspect.

[0065] In an eighth aspect, a network device is provided, including a processor, a memory and an interface; the processor, the memory and the interface cooperate with each other to enable the network device to perform any of the methods in the technical solutions of the second aspect; or include any of the chips in the sixth aspect.

[0066] In a ninth aspect, a computer readable storage medium is provided, in which a computer program is stored; when the computer program is executed by a processor, the processor performs any of the methods in the technical solutions of the first aspect or the second aspect.

[0067] In a tenth aspect, a computer program product is provided, including computer program code; when the computer program code is run on a communication device, the communication device performs any of the methods in the technical solutions of the first aspect or the second aspect. BRIEF DESCRIPTION OF DRAWINGS

[0068] FIG. 1 is a schematic diagram of a communication system provided by an embodiment of the present application;

[0069] FIG. 2 is a schematic diagram of a beamforming system to which an embodiment of the present application is applicable;

[0070] FIG. 3 is a schematic diagram of a beamforming system to which embodiments of the present application are applicable;

[0071] FIG. 4 is a schematic diagram of downlink beam sweeping according to an embodiment of the present application;

[0072] FIG. 5 is a schematic diagram of a periodic transmission mode of CSI reporting according to an embodiment of the present application;

[0073] FIG. 6 is a schematic diagram of an aperiodic transmission mode of CSI reporting according to an embodiment of the present application;

[0074] FIG. 7 is a schematic diagram of a semi-persistent transmission mode of CSI reporting according to an embodiment of the present application;

[0075] FIG. 8 is a schematic diagram of an event-triggered transmission mode of CSI reporting according to an embodiment of the present application;

[0076] FIG. 9 is a schematic diagram of another event-triggered transmission mode of CSI reporting according to an embodiment of the present application;

[0077] FIG. 10 is a schematic diagram of a periodic transmission mode of event-triggered CSI reporting according to an embodiment of the present application;

[0078] FIG. 11 is a schematic diagram of a generation mode of PUCCH resources according to an embodiment of the present application;

[0079] FIG. 12 is a schematic diagram of a generation mode of PUSCH resources according to an embodiment of the present application;

[0080] FIG. 13 is a schematic flowchart of a wireless communication method according to an embodiment of the present application;

[0081] FIG. 14 is a schematic block diagram of a communication apparatus according to an embodiment of the present application;

[0082] FIG. 15 is a schematic block diagram of another communication apparatus according to an embodiment of the present application;

[0083] FIG. 16 is a schematic structural diagram of a communication apparatus according to an embodiment of the present application. DETAILED DESCRIPTION

[0084] FIG. 1 is a schematic diagram of an architecture of a communication system 1000 to which embodiments of the present application are applied. As shown in FIG. 1, the communication system includes a radio access network (RAN) 100, wherein the RAN 100 includes at least one RAN node (e.g., 110a and 110b in FIG. 1, collectively referred to as 110), and can further include at least one terminal device (e.g., 120a-120j in FIG. 1, collectively referred to as 120). The RAN 100 can further include other RAN nodes, such as wireless relay devices and / or wireless backhaul devices (not shown in FIG. 1). The terminal devices 120 are connected to the RAN nodes 110 in a wireless manner. The terminal devices and the terminal devices, and the RAN nodes and the RAN nodes can be connected to each other in a wired or wireless manner. The communication system 1000 can further include a core network 200. The RAN nodes 110 are connected to the core network 200 in a wireless or wired manner. The core network devices in the core network 200 and the RAN nodes 110 in the RAN 100 can be independent and different physical devices, or can be the same physical device integrated with the logical functions of the core network devices and the logical functions of the RAN nodes. The communication system 1000 can further include an Internet 300.

[0085] The RAN 100 can be an evolved universal terrestrial radio access (E-UTRA) system, a new radio (NR) system, and a future wireless access system defined in the 3rd generation partnership project (3GPP). The RAN 100 can also be an open RAN (O-RAN or ORAN), a cloud radio access network (CRAN), or a wireless fidelity (WiFi) system. The RAN 100 can also include two or more different wireless access systems described above.

[0086] A RAN node, also referred to as a radio access network device, a RAN entity, or an access node, is configured to help a terminal device access a communication system through wireless means. In one application scenario, the RAN node can be a base station, an evolved NodeB (eNodeB), a transmission reception point (TRP), a next generation NodeB (gNB) in a 5th generation (5G) mobile communication system, a next generation NodeB in a 6th generation (6G) mobile communication system, or a base station in a future mobile communication system. The RAN node can be a macro base station (e.g., 110a in FIG. 1), a micro base station or an indoor station (e.g., 110b in FIG. 1), or a relay node or a donor node.

[0087] In another application scenario, a terminal device can access a communication system through wireless means by cooperation of multiple RAN nodes, and different RAN nodes implement part of functions of a base station. For example, the RAN node can be a central unit (CU), a distributed unit (DU), or a radio unit (RU). Here, the CU implements functions of a radio resource control protocol and a packet data convergence protocol (PDCP) of a base station, and can also implement a function of a service data adaptation protocol (SDAP). The DU implements functions of a radio link control layer and a medium access control (MAC) layer of a base station, and can also implement part of functions of a physical layer or all functions of a physical layer. For details of the protocol layers, refer to relevant technical specifications of 3GPP. The RU can be configured to implement functions of transceiving a radio frequency signal. The CU and the DU can be two independent RAN nodes, or can be integrated in the same RAN node, e.g., integrated in a baseband unit (BBU). The RU can be included in a radio frequency device, e.g., included in a remote radio unit (RRU) or an active antenna unit (AAU). The CU can be further divided into two types of RAN nodes, i.e., a CU-control plane and a CU-user plane.

[0088] The RAN node can have different names in different systems, for example, in an O-RAN system, the CU can be referred to as an open CU (O-CU), the DU can be referred to as an open DU (O-DU), and the RU can be referred to as an open RU (O-RU). The RAN node in the embodiments of the present application can be implemented by a software module, a hardware module, or a combination of a software module and a hardware module. For example, the RAN node can be a server loaded with a corresponding software module. The embodiments of the present application do not limit the specific technology and specific device form of the RAN node. For ease of description, a base station is described as an example of the RAN node in the following.

[0089] The terminal device is a device with wireless transceiving function, which can send signals to the base station or receive signals from the base station. The terminal device can also be referred to as a terminal, user equipment (UE), mobile station, mobile terminal, etc. The terminal device can be widely applied in various scenarios, such as device-to-device (D2D) communication, vehicle-to-everything (V2X) communication, machine-type communication (MTC), internet of things (IoT), virtual reality, augmented reality, industrial control, autonomous driving, remote medical treatment, smart power grid, smart furniture, smart office, smart wear, smart transportation, smart city, etc. The terminal device can be a mobile phone, tablet computer, computer with wireless transceiving function, wearable device, vehicle, airplane, ship, robot, mechanical arm, smart home device, etc. The embodiments of the present application do not limit the specific technology and specific device form of the terminal device.

[0090] The base station and the terminal device can be fixed in position or movable. The base station and the terminal device can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; can also be deployed on water surface; can also be deployed on airplanes, balloons and artificial satellites. The embodiments of the present application do not limit the application scenarios of the base station and the terminal device.

[0091] The roles of the base station and the terminal device can be relative, for example, the helicopter or the drone 120i in FIG. 1 can be configured as a mobile base station, and for the terminal device 120j that accesses the wireless access network 100 through 120i, 120i is a base station; but for the base station 110a, 120i is a terminal device, that is, 110a communicates with 120i through a wireless air interface protocol. Of course, 110a and 120i can also communicate through a base station-to-base station interface protocol, and in this case, 120i is also a base station relative to 110a. Therefore, the base station and the terminal device can be collectively referred to as a communication device, and 110a and 110b in FIG. 1 can be referred to as a communication device with a base station function, and 120a-120j in FIG. 1 can be referred to as a communication device with a terminal function.

[0092] The base station and the terminal device, the base station and the base station, and the terminal device and the terminal device can communicate through a licensed frequency spectrum, or through an unlicensed frequency spectrum, or through both the licensed frequency spectrum and the unlicensed frequency spectrum; can communicate through a frequency spectrum below 6 gigahertz (GHz), or through a frequency spectrum above 6 GHz, or through both the frequency spectrum below 6 GHz and the frequency spectrum above 6 GHz. The embodiments of the present application do not limit the frequency spectrum resources used for wireless communication.

[0093] In the embodiments of the present application, the functions of the base station can also be performed by a module (such as a chip) in the base station, or by a control subsystem containing base station functions. The control subsystem containing base station functions herein can be a control center in the above-mentioned application scenarios such as smart grid, industrial control, intelligent transportation, and smart city. The functions of the terminal device can also be performed by a module (such as a chip or a modem) in the terminal device, or by a device containing terminal device functions.

[0094] Beamforming system

[0095] The design goals of a communication system (for example, NR) include large-bandwidth communication in a high frequency band (for example, a frequency band above 6 GHz). When the working frequency becomes higher, the path loss in the transmission process increases, which affects the coverage capability of the high-frequency system. Therefore, in order to effectively ensure the coverage range of the high frequency band, an effective technical solution is to form a larger gain beamforming beam based on massive multiple-in multiple-out (massive MIMO) to overcome the propagation loss and ensure the coverage range of the communication system.

[0096] Currently, a common large-scale antenna array is a millimeter wave antenna array. Because the millimeter wave antenna array emits a shorter wavelength, the spacing between the antenna elements of the antenna array can be shorter, and the aperture of the antenna element can be smaller, so that more physical antenna elements can be integrated in a two-dimensional antenna array of a limited size.

[0097] In addition, because the size of the millimeter wave antenna array is limited, from the aspects of hardware complexity, cost overhead, and power consumption, a digital beamforming manner cannot be used, and an analog beamforming manner is usually used, which can enhance network coverage while reducing the implementation complexity of the device.

[0098] In order to facilitate understanding of the beamforming system, the following describes a communication process based on beam communication in the scenario of communication between a network device and a terminal device in combination with FIG. 2 and FIG. 3.

[0099] Referring to FIG. 2, in a conventional communication system (for example, an LTE communication system), a relatively wide beam 210 is usually used to cover an entire cell (or sector). In this way, at each time, the terminal devices (for example, terminal devices 211-215) in the cell can communicate with the network device through the relatively wide beam, for example, to obtain the transmission resource allocated by the network device.

[0100] Referring to FIG. 3, in a newer communication system (for example, an NR system), a beamforming system 310 can be used to cover the entire cell, that is, each beam (for example, beams 311-314) in the beamforming system covers a smaller range in the cell, and the effect of covering the entire cell by multiple beams is achieved through beam sweeping.

[0101] In the process of beam sweeping, different beams are used to cover different areas in the cell at different times. For example, at time 1, the communication system can cover the area where the terminal device 321 is located through the beam 311. At time 2, the communication system can cover the area where the terminal device 322 is located through the beam 312. At time 3, the communication system can cover the area where the terminal devices 323 and 324 are located through the beam 313. At time 4, the communication system can cover the area where the terminal device 325 is located through the beam 314.

[0102] For the beamforming system, because a relatively narrow beam is used, the transmission energy can be more concentrated, and therefore a longer distance can be covered. However, because the beam is relatively narrow, each beam can only cover part of the area in the cell, and therefore the beamforming system can be understood as a system of “exchanging time for space”.

[0103] In a communication scenario between a network device and a terminal device, if the network device and the terminal device support multi-beam transmission, before the network device and the terminal device communicate with each other, the network device and the terminal device need to select appropriate transmission beams and reception beams through a beam management process. Taking downlink beam management as an example, downlink beam management includes processes such as downlink beam sweeping, beam measurement and reporting by the terminal device, and downlink beam indication by the network device. The downlink beam management process is described in detail below.

[0104] The downlink beam sweeping process can be divided into three processes, denoted as P1 process, P2 process and P3 process. The P1 process can refer to that the network device transmits using different transmission beams, and the terminal device receives using different reception beams, as shown in (a) of FIG. 4. The P2 process can refer to that the network device transmits using different transmission beams, and the terminal device receives using the same reception beam, as shown in (b) of FIG. 4. The P3 process can refer to that the network device transmits using the same transmission beam, and the terminal device receives using different reception beams, as shown in (c) of FIG. 4. Generally, the network device can complete the above beam sweeping process by sending a downlink reference signal, which can include, for example, a synchronization signal / physical broadcast channel block (SSB) and / or a channel-state-information reference signal (CSI-RS). The reference signal can also be referred to as a pilot signal or a measurement pilot, etc.

[0105] In some implementations, for the measurement of the downlink beam, the CSI-RS and / or SSB transmitted on the downlink beam can be measured. The terminal device can measure each reference signal to obtain a measurement result. The measurement result can include one or more of the following: reference signal receiving power (RSRP), signal to interference plus noise ratio (SINR), etc.

[0106] The measurement result can be a layer 1 (L1) based measurement result or a L3 based measurement result. If the measurement result is a layer 1 based measurement result, the measurement result can include L1-RSRP and / or L1-SINR, etc. The L1 measurement can be processed directly in the physical layer, with a shorter processing delay. If the measurement result is a L3 based measurement result, the measurement result can include L3-RSRP and / or L3-SINR, etc. Of course, the measurement result applicable to the embodiments of the present application can also be a measurement result newly introduced in future communication systems.

[0107] The beam measurement and reporting process can refer to that the terminal device can measure a plurality of transmission beams (P2 process) or transmission-reception beam pairs (P1 process), so as to perform beam selection. For example, the terminal device can select the optimal beam, and send the optimal beam to the network device. The optimal beam can be, for example, the K beams with the highest L1-RSRP or L1-SINR, K being an integer greater than or equal to 1. When reporting to the network device, the terminal device can report only the beam information of the optimal beam, or can also report the measurement result corresponding to the optimal beam. The information of the beam can include the index of the reference signal, the number of the reference signal, etc. In some embodiments, the terminal device can report the beam in the form of channel information state (CSI) report or beam report.

[0108] The network device can decode the beam information reported by the terminal device, and select the transmission beam to be used from the beams reported by the terminal device. The network device can indicate the beam information to the terminal device through transmission configuration indicator (TCI) state, to indicate the transmission beam to be used. The TCI state can contain SSB index or CSI-RS resource index, and one index can correspond to one beam. The terminal device can use the reception beam corresponding to the transmission beam of the SSB or CSI-RS to perform downlink reception. The above TCI state can be carried through media access control (MAC) signaling and / or downlink control information (DCI) signaling, which is not limited in the embodiments of the present application.

[0109] Generally, the beam used by the sending end to send a signal is referred to as a “transmission beam”. The beam used by the receiving end to receive a signal is referred to as a “reception beam”.

[0110] In some embodiments, a beam can be replaced by a reference signal, a reference signal resource, a transmit-end spatial filter, a receive-end spatial filter, a spatial filter, a spatial reception parameter, a transmit-end precoding, a receive-end precoding, an antenna port, an antenna weight vector, an antenna weight matrix, etc.

[0111] In some embodiments, a beam index can be replaced by a reference signal index or a reference signal resource index.

[0112] In the following, the scheme of the embodiments of the present application is described in detail taking a beam as an example of a reference signal resource.

[0113] Generally, a network device configures a terminal device with multiple reference signal resources, and the terminal device measures the multiple reference signal resources to obtain measurement results. The reference signal resources can include SSB resources and / or CSI-RS resources. The terminal device sends a CSI report to the network device according to the measurement results. A beam report is generally one of the CSI reports. The CSI report includes indices of K reference signals and measurement results corresponding to the K reference signals, where K is an integer greater than or equal to 1. The K reference signals can be the K reference signals with the best measurement results. In some implementations, the CSI report can reflect the state information of a channel. The content of the CSI report reflects one or more optimal beams and their quality, which are used by the network device to determine the beams used to send a channel or a signal to the terminal device, or to indicate the beams used by the terminal device to receive a channel or a signal.

[0114] If the reference signal is an SSB, the reference signal index can be a synchronization signal block resource indicator (SSBRI). If the reference signal is a CSI-RS, the reference signal index can be a channel state information-reference signal resource indicator (CRI).

[0115] In some embodiments, in order to save signaling overhead, multiple reference signal resources can be divided into multiple sets. One reference signal resource set includes one or more reference signal resources. One reference signal resource set can be referred to as one measurement resource, that is, one measurement resource can include one or more reference signal resources. One reference signal resource corresponds to one reference signal.

[0116] In some embodiments, the network device can configure one or more reporting configurations for the terminal device. The reporting configuration can also be referred to as a CSI reporting configuration or a channel measurement configuration or a beam reporting configuration. The terminal device can generate a CSI report according to the reporting configuration.

[0117] The reporting configuration can generally include a reference signal resource indication and / or a CSI report content indication, etc. The reference signal resource indication is used to indicate the reference signal for generating the CSI report, such as indicating that the reference signal for generating the CSI report is the first measurement resource and / or the second measurement resource. The CSI report content indication is used to indicate the type of measurement result and / or the number of measurement results, etc. that need to be reported in the CSI report. The number of measurement results can be 1, 2, 3, 4, etc. and the default value is 1.

[0118] In addition, the reporting configuration can also indicate the sending mode of the CSI report. The sending mode of the CSI report includes periodic, semi-persistent, or aperiodic, etc. The semi-persistent CSI report can be activated by a medium access control control element (MAC CE) or DCI activation. The aperiodic CSI report can be activated or indicated by DCI.

[0119] In some implementations, the DCI can activate or indicate the corresponding CSI report by activating or indicating a trigger state. One trigger state can be associated with one or more reporting configurations. The DCI activates a trigger state, which is equivalent to activating the reporting configuration associated with the trigger state. After the reporting configuration is activated, the terminal device can generate a CSI report using the activated reporting configuration.

[0120] The network device can configure one or more trigger states for the terminal device through RRC, and then activate or indicate the trigger state through DCI to determine which trigger state to use, in order to save signaling overhead.

[0121] Currently, the terminal device generally sends a CSI report to the network device according to the measurement resource, the report content, and the report time configured by the network device, but this method can cause the problem of large sending overhead of the CSI report and large feedback delay of the CSI report. The problem is analyzed and explained as follows.

[0122] The sending mode of the CSI report by the terminal device can be any one of periodic, aperiodic, and semi-persistent. The three sending modes are described as follows.

[0123] FIG. 5 shows a periodic sending manner of CSI reporting. For the periodic sending manner, the network device can configure a periodic reporting resource for the terminal device, and the terminal device sends the CSI report on the periodic reporting resource. As shown in FIG. 5, the terminal device can send the CSI report at time 1, time 2 and time 3 respectively. The terminal device can perform channel measurement before the periodic sending time, and send the CSI report at the periodic sending time.

[0124] If the terminal device measures a large change in the measurement result of the reference signal at time 2', for example, the optimal K reference signals change, then the terminal device needs to send the CSI report to the network device at this time, but since time 2 has not arrived, the terminal device can only wait until time 2 arrives to send the CSI report to the network device, thereby causing a large feedback delay of the CSI report. The CSI report cannot be reported in time, which can affect the communication between the terminal device and the network device.

[0125] If the terminal device measures no change in the measurement result of the reference signal during time 2 to time 3, for example, the optimal K reference signals do not change, but since the network device configures the reporting resource for the terminal device at time 3, the terminal device still needs to send the CSI report to the network device at time 3, thereby causing a large sending overhead of the CSI report.

[0126] FIG. 6 shows a non-periodic sending manner of CSI reporting. For the non-periodic sending manner, the network device can send a DCI to the terminal device, the DCI being used to schedule an uplink resource, and the terminal device sends the CSI report on the uplink resource.

[0127] The terminal device needs to measure the reference signal before time 1, obtain the measurement result, and send the CSI report to the network device at time 1.

[0128] If the terminal device measures a large change in the measurement result of the reference signal at time 1', for example, the optimal K reference signals change, then the terminal device needs to send the CSI report to the network device at this time, but since time 1 has not arrived, or the network device has not sent the DCI to the terminal device for scheduling the uplink resource, the terminal device can only wait until time 1 arrives to send the CSI report to the network device, thereby causing a large feedback delay of the CSI report. The CSI report cannot be reported in time, which can affect the communication between the terminal device and the network device.

[0129] If the terminal device measures the measurement result of the reference signal before time 1 and the measurement result does not change, for example, the optimal K reference signals do not change, but the network device schedules uplink resources for the terminal device through DCI, the terminal device still needs to send the CSI report to the network device at time 1, thereby causing a large sending overhead of the CSI report.

[0130] FIG. 7 shows a semi-persistent sending mode of the CSI report. For the semi-persistent sending mode, after the terminal device receives the MAC CE or the DCI activation instruction sent by the network device, the terminal device can periodically send the CSI report, for example, the terminal device sends the CSI report to the network device at time 1, time 2, and time 3; after the terminal device receives the MAC CE or the DCI deactivation instruction sent by the network device, the terminal device can stop sending the CSI report to the network device. The semi-persistent sending mode has problems similar to the periodic sending mode and the aperiodic sending mode described above. For brevity, the details are not described here.

[0131] Based on the above considerations, an event-triggered CSI report is introduced. When the triggering event occurs, the terminal device sends the CSI report to the network device again; if the triggering event does not occur, the terminal device can not send the CSI report to the network device. The sending time of the CSI report depends on the time when the terminal device detects the occurrence of the triggering event, and therefore, this mode can reduce the sending overhead of the CSI report and reduce the feedback delay of the CSI report.

[0132] First, the types of triggering events are introduced.

[0133] The network device configures measurement resources for the terminal device, and the measurement resources can include first measurement resources and second measurement resources. The terminal device sends the CSI report to the network device according to the first measurement resources and / or the second measurement resources. The CSI report includes at least the index of the reference signal and / or the measurement result (such as RSRP and / or SINR) corresponding to the reference signal index, which can be used to indicate the measurement resources. The terminal device feeds back the CSI report based on one or more triggering events.

[0134] The triggering event can include triggering event 1, triggering event 2, and triggering event 3.

[0135] Triggering event 1: the signal quality of the second measurement resource is greater than the signal quality of the first measurement resource plus a threshold. Triggering event 1 can include triggering event 1-1 to triggering event 1-8.

[0136] Trigger event 1-1: RSRP of one reference signal of the first measurement resource is RSRP1, RSRP of one reference signal of the second measurement resource is RSRP2, and the trigger event is RSRP2>RSRP1+T, where T is the threshold. The first measurement resource and the second measurement resource belong to the same cell. For example, the measurement resources of the same cell are associated with the same physical cell identity (PCI), that is, the first measurement resource and the second measurement resource can be associated with the same PCI.

[0137] Trigger event 1-2: SINR of one reference signal of the first measurement resource is SINR1, SINR of one reference signal of the second measurement resource is SINR2, and the trigger event is SINR2>SINR1+T, where T is the threshold. The first measurement resource and the second measurement resource belong to the same cell. For example, the measurement resources of the same cell are associated with the same physical cell identity, that is, the first measurement resource and the second measurement resource can be associated with the same physical cell identity.

[0138] Trigger event 1-3: RSRP of one reference signal of the first measurement resource is RSRP1, RSRP of one reference signal of the second measurement resource is RSRP2, and the trigger event is RSRP2>RSRP1+T, where T is the threshold. The first measurement resource and the second measurement resource belong to the same component carrier (CC). For example, the measurement resources of the same component carrier are associated with the same component carrier index, that is, the first measurement resource and the second measurement resource can be associated with the same component carrier.

[0139] Trigger event 1-4: SINR of one reference signal of the first measurement resource is SINR1, SINR of one reference signal of the second measurement resource is SINR2, and the trigger event is SINR2>SINR1+T, where T is the threshold. The first measurement resource and the second measurement resource belong to the same component carrier. For example, the measurement resources of the same component carrier are associated with the same component carrier index, that is, the first measurement resource and the second measurement resource can be associated with the same component carrier.

[0140] Trigger event 1-5: RSRP of one reference signal of the first measurement resource is RSRP1, RSRP of one reference signal of the second measurement resource is RSRP2, and the trigger event is RSRP2>RSRP1+T, where T is the threshold. The first measurement resource and the second measurement resource belong to different cells. For example, the measurement resources of different cells are associated with different physical cell identities, that is, the first measurement resource and the second measurement resource can be associated with different physical cell identities.

[0141] Trigger event 1-6: SINR of one reference signal of the first measurement resource is SINR1, and SINR of one reference signal of the second measurement resource is SINR2, and the trigger event is SINR2 > SINR1 + T, where T is a threshold. The first measurement resource and the second measurement resource belong to different cells. For example, the measurement resources of different cells are associated with different physical cell numbers, that is, the first measurement resource and the second measurement resource can be associated with different physical cell numbers.

[0142] Trigger event 1-7: RSRP of one reference signal of the first measurement resource is RSRP1, and RSRP of one reference signal of the second measurement resource is RSRP2, and the trigger event is RSRP2 > RSRP1 + T, where T is a threshold. The first measurement resource and the second measurement resource belong to different component carriers. For example, the measurement resources of different component carriers are associated with different component carrier indexes, that is, the first measurement resource and the second measurement resource can be associated with different component carriers.

[0143] Trigger event 1-8: SINR of one reference signal of the first measurement resource is SINR1, and SINR of one reference signal of the second measurement resource is SINR2, and the trigger event is SINR2 > SINR1 + T, where T is a threshold. The first measurement resource and the second measurement resource belong to different component carriers. For example, the measurement resources of different component carriers are associated with different component carrier indexes, that is, the first measurement resource and the second measurement resource can be associated with different component carriers.

[0144] Trigger event 2: the signal quality of the first measurement resource is worse than a threshold. Trigger event 2 can include trigger event 2-1 and trigger event 2-2.

[0145] Trigger event 2-1: RSRP of one reference signal of the first measurement resource is RSRP1, and the trigger event is RSRP1 < T, where T is a threshold.

[0146] Trigger event 2-2: SINR of one reference signal of the first measurement resource is SINR1, and SINR1 < T, where T is a threshold.

[0147] Trigger event 3: the signal quality of the second measurement resource is greater than or equal to a threshold. Trigger event 3 can include trigger event 3-1 and trigger event 3-2.

[0148] Trigger event 3-1: RSRP of one reference signal of the second measurement resource is RSRP1, and the trigger event is RSRP1 ≥ T, where T is a threshold.

[0149] Trigger event 3-2: the SINR of one reference signal of the second measurement resource is SINR1, and SINR1≥T, where T is a threshold.

[0150] For event-triggered beam reporting, the terminal device can send a CSI report to the network device in the following two ways. The following describes the two ways in combination with FIG. 8 and FIG. 9.

[0151] Way one

[0152] FIG. 8 shows a sending way of a CSI report. The terminal device sends a first channel to the network device, where the first channel is used to inform the network device that a trigger event occurs. The first channel can be a physical random access channel (PRACH) or a physical uplink control channel (PUCCH).

[0153] After receiving the first channel, the network device can send a DCI to the terminal device, where the DCI is used to indicate a second channel and instruct the terminal device to send a CSI report on the second channel. The second channel can be a PUCCH or a physical uplink shared channel (PUSCH).

[0154] After receiving the DCI, the terminal device can send the CSI report on the second channel indicated by the DCI.

[0155] If the terminal device does not detect a trigger event, or does not detect a trigger event before the first channel, the terminal device can not send the first channel to the network device, and thus does not need to send a CSI report to the network device. Compared with the scheme shown in FIG. 6, the transmission overhead of the CSI report can be reduced. In addition, if the terminal device detects a trigger event, the terminal device can immediately send the first channel to the network device to request the network device to configure the second channel, so that the timely transmission of the CSI report can be ensured, and the transmission delay of the CSI report can be reduced.

[0156] Way two

[0157] FIG. 9 shows another sending way of a CSI report. The terminal device sends a first channel to the network device, where the first channel is used to inform the network device that a trigger event occurs. The first channel can be a PRACH or a PUCCH.

[0158] The network device can pre-configure the second channel to the terminal device. The terminal device transmits the CSI report on the second channel. The second channel can be a PUCCH or a PUSCH. The PUCCH can be a pre-configured PUCCH, and the PUSCH can be a configured grant PUSCH (CG-PUSCH).

[0159] The time offset between the first channel and the second channel can be understood as the time for the terminal device to prepare the second channel. In some implementations, the reference signal resource needs to be located before the first channel, because the triggering of the first channel needs to be based on the current channel measurement result. As shown in FIG. 9, the time offset between the reference signal resource and the second channel is Z', and the time offset between the first channel and the second channel is T0, where Z'>T0. Z' can be a predefined value.

[0160] The pre-configured second channel can be a periodic channel or a semi-persistent channel, as shown in FIG. 10. The terminal device will only transmit the CSI report on the second channel when the terminal device detects a triggering event. If the terminal device does not detect the triggering event, the terminal device can not transmit the CSI report to the network device on the second channel. For example, if the terminal device does not detect the triggering event before time 1, the terminal device does not transmit the CSI report on the second channel corresponding to time 1. If the terminal device detects the triggering event between time 2 and time 3, the terminal device can transmit the CSI report on the second channel corresponding to time 3. Compared with the scheme shown in FIG. 5, the transmission overhead of the CSI report can be reduced.

[0161] If the first channel is a PUCCH, the PUCCH can be a PUCCH for scheduling request. At present, if the terminal device has data to be transmitted, the terminal device will notify the network device through the scheduling request. One scheduling request is usually associated with a specific logical channel or a specific function (such as a beam failure request).

[0162] One scheduling request can be associated with a scheduling request resource. One scheduling request resource can be used to indicate a PUCCH resource. The PUCCH resource can be pre-configured by the network device. When the terminal device has data to be transmitted on a specific logical channel, the terminal device can transmit the PUCCH corresponding to the scheduling request to notify the network device. The PUCCH can correspond to the first channel in the embodiments of the present application. Usually, the time instants available for transmitting the scheduling request will also be indicated in the scheduling request resource, and then the PUCCH can be transmitted at these time instants to notify the scheduling request of the terminal device.

[0163] The report configuration mentioned above can be used for event-based CSI reporting and non-event-based CSI reporting (i.e., CSI reporting generated based on a traditional manner).

[0164] For event-based CSI reporting, the type of event can be different due to different scenarios. If the terminal device does not indicate the type of the triggering event to the network device, the network device cannot correctly receive the CSI report or cannot schedule appropriate uplink resources for the terminal device to transmit the CSI report.

[0165] For example, for the transmission mode of the first manner, if the terminal device does not indicate the type of the triggering event to the network device, the network device does not know how many bits of uplink resources to schedule for the terminal device through DCI, and the uplink resources that can be scheduled do not match the resources required by the terminal device to transmit the CSI report, so that the terminal device cannot correctly transmit the CSI report. Further, the network device does not know which trigger state to activate or indicate for the terminal device through DCI, and the trigger state is used to activate or indicate the report configuration corresponding to the triggering event.

[0166] For example, for the transmission mode of the second manner, if the terminal device does not indicate the type of the triggering event to the network device, the network device does not know which CSI report corresponding to the triggering event is transmitted on the second channel, so that the network device cannot correctly decode the CSI report on the second channel (the decoding manner, the measurement result carried, or the number of measurement results of different CSI reports can be different), which causes the CSI report transmission to fail.

[0167] For example, for a carrier aggregation (CA) scenario, the terminal device can detect an event in any component carrier, and if the terminal device does not indicate to the network device which component carrier has the event, the network device will not know which component carrier has the event, so that the network device cannot select a suitable beam for the terminal device.

[0168] Therefore, the embodiments of the present application provide a wireless communication method and a communication device, which indicate the type of the triggering event through the first channel and / or the second channel, so that the network device can determine which triggering event triggers the current CSI report, and the correct transmission of the CSI report is ensured.

[0169] The embodiments of the present application do not make specific limitations on the manner in which the terminal device indicates the type of the triggering event. As an example, the terminal device can indicate the type of the triggering event to the network device in an explicit manner. For example, the terminal device can carry indication information in the first channel and / or the second channel, where the indication information is used to indicate the type of the triggering event. As another example, the terminal device can indicate the type of the triggering event to the network device in an implicit manner. For example, the terminal device can indicate the type of the triggering event to the network device through the association between the transmission resource and the type of the triggering event. The transmission resource is related to the transmission resource of the first channel and / or the second channel.

[0170] Generally, the reporting configuration indicates the type of the triggering event corresponding to the CSI report. For example, if the triggering event is the triggering event 1-1, the reporting configuration corresponding to the CSI report indicates that the measurement result to be reported in the CSI report is the RSRP, and the number of the RSRP is 2. For another example, if the triggering event is the triggering event 1-2, the reporting configuration corresponding to the CSI report indicates that the measurement result to be reported in the CSI report is the SINR, and the number of the SINR is 2. For another example, if the triggering event is the triggering event 2-1, the reporting configuration corresponding to the CSI report indicates that the measurement result to be reported in the CSI report is the RSRP, and the number of the RSRP is 1. For another example, if the triggering event is the triggering event 2-2, the reporting configuration corresponding to the CSI report indicates that the measurement result to be reported in the CSI report is the SINR, and the number of the SINR is 1. As can be seen from the above, the content of the reporting configuration corresponding to different types of triggering events is different.

[0171] The terminal device indicating the type of the triggering event to the network device can include the terminal device indicating the index of the reporting configuration to the network device. In some implementation manners, the terminal device can indicate the index of the reporting configuration to the network device through the corresponding relationship between the transmission resource and the reporting configuration. The network device can determine the type of the triggering event according to the index of the reporting configuration.

[0172] In some embodiments, the first channel is generally the PUCCH. Since the amount of information that can be carried by the PUCCH is small, if the first channel is used to indicate the type of the triggering event, the terminal device can use an implicit manner to indicate the type of the triggering event.

[0173] In some embodiments, the second channel is generally the PUCCH and / or the PUSCH. If the second channel is the PUCCH, and the terminal device uses the second channel to indicate the type of the triggering event, the terminal device can use an implicit manner to indicate the type of the triggering event. If the second channel is the PUSCH, and the terminal device uses the second channel to indicate the type of the triggering event, the terminal device can use an implicit manner to indicate the type of the triggering event, or can use an explicit manner to indicate the type of the triggering event.

[0174] The specific implicit indication manner and explicit indication manner will be described in detail below.

[0175] For the first channel, if an implicit manner is used to indicate the type of the triggering event, the type of the triggering event can be indicated by the correspondence between the first channel and the reporting configuration. For example, the terminal device can determine the used reporting configuration according to the correspondence between the reporting configuration and the triggering event, and then determine the first channel that needs to be used according to the correspondence between the reporting configuration and the first channel, on which the terminal device sends the CSI report. After receiving the first channel sent by the terminal device, the network device can determine the type of the triggering event according to the correspondence between the first channel and the reporting configuration, and the correspondence between the reporting configuration and the triggering event.

[0176] In some implementations, the first channel can be a PUCCH. The correspondence between the first channel and the reporting configuration can refer to the correspondence between the PUCCH (or PUCCH resource) and the reporting configuration, or the correspondence between the scheduling request resource and the reporting configuration, or the correspondence between the scheduling request and the reporting configuration. Among them, one scheduling request can correspond to one scheduling request resource, and one scheduling request resource can indicate one PUCCH resource. In some embodiments, mode one and mode two usually use different scheduling requests, or different scheduling request resources, or different PUCCH resources, so that the network device can distinguish between mode one and mode two.

[0177] For the sending mode of mode one, after indicating the type of the triggering event to the network device through the first channel, the network device can indicate the information corresponding to the type of the triggering event to the terminal device in the DCI, so that the terminal device can associate the first channel with the DCI. For example, the network device can indicate the triggering state corresponding to the type of the triggering event, or indicate the reporting configuration corresponding to the type of the triggering event, or indicate the CSI report corresponding to the type of the triggering event, to the terminal device through the DCI.

[0178] For the sending mode of mode one, after indicating the type of the triggering event to the network device through the first channel, the network device can receive the CSI report on a specific second channel according to the type of the triggering event, which is beneficial to reduce the blind detection complexity of the network device.

[0179] For the second channel, an implicit manner can be used to indicate the type of the triggering event, and the specific manner is similar to the manner indicated through the first channel. For brevity, it will not be described here.

[0180] In some implementations, the indication information can be carried in a domain of the CSI report carried by the second channel to indicate the type of the triggering event.

[0181] In addition to the above manner, the second channel can also have a correlation relationship with the overhead required for transmitting the CSI report. The terminal device can select the second channel according to the overhead required for transmitting the CSI report. The transmission overhead of the CSI report corresponding to different trigger event types can be different. Based on this, after receiving the second channel, the network device can determine the type of the trigger event according to the corresponding relationship between the second channel and the transmission overhead. In this way, the network device can receive the CSI report on a specific second channel according to the overhead required for transmitting the CSI report, which is beneficial to reduce the blind detection complexity of the network device.

[0182] The first channel in the above can be directly configured by the network device, or can also be determined by the terminal device according to the first channel reference resource.

[0183] The second channel in the above can be directly configured by the network device, or can also be determined by the terminal device according to the second channel reference resource.

[0184] The scheme of the embodiments of the present application will be described in detail below in combination with several examples.

[0185] Example One

[0186] Example one is to indicate the type of the trigger event to the network device through the first channel. The network device can determine the type of the trigger event according to the first channel. The first channel can be, for example, PUCCH.

[0187] Since the report configuration usually has a one-to-one correspondence relationship with the trigger event type, different report configurations correspond to different trigger event types. Therefore, the present application embodiment can indicate the type of the trigger event to the network device according to the corresponding relationship between the first channel and the report configuration. That is, the terminal device can indicate the report configuration to the network device through the first channel. The report configuration in the present application embodiment can be used for event-triggered CSI report.

[0188] The first channel in the present application embodiment can be associated with a scheduling request. One scheduling request can be associated with one or more scheduling request resources, and one scheduling request resource can be associated with one PUCCH resource, which is the first channel.

[0189] The association between the first channel and the report configuration can be achieved through the association between the scheduling request resource and the report configuration. One scheduling request resource can be associated with one or more report configurations, and the terminal device can distinguish different report configurations through different scheduling request resources. Generally, different report configurations can correspond to different trigger event types. Based on this, after receiving the first channel, the network device can determine the type of the trigger event according to the association between the first channel and the report configuration, and the corresponding relationship between the report configuration and the type of the trigger event. Further, the network device can determine which CSI report corresponding to the report configuration carried by the second channel is, and which trigger event triggers the report configuration.

[0190] In some implementations, the association between the scheduling request resource and the report configuration can refer to the association between the index of the scheduling request resource and the index of the report configuration. For example, the index of one scheduling request resource can be associated with the index of one or more report configurations.

[0191] The process of the terminal device indicating the type of the trigger event to the network device and the process of the network device determining the type of the trigger event will be described in detail below in combination with Table 1 and Table 2.

[0192] Table 1 shows the corresponding relationship between the index of the scheduling request resource and the index of the report configuration.

[0193] Table 1

[0194] As can be seen from Table 1, the scheduling request resource 0 corresponds to the report configuration a and the report configuration b, the scheduling request resource 1 corresponds to the report configuration c, and the scheduling request resource 2 corresponds to the report configuration d, the report configuration e and the report configuration f.

[0195] Table 2 shows the corresponding relationship between the index of the report configuration and the type of the trigger event.

[0196] Table 2

[0197] As can be seen from Table 2, the report configuration a corresponds to the trigger event type 1, the report configuration b corresponds to the trigger event type 2, the report configuration c corresponds to the trigger event type 3, the report configuration d corresponds to the trigger event type 4, the report configuration e corresponds to the trigger event type 5, and the report configuration f corresponds to the trigger event type 6.

[0198] For example, if the terminal device determines that the trigger event 3 occurs, the terminal device determines that the report configuration c needs to be used according to the corresponding relationship shown in Table 2. Further, the terminal device can determine that the scheduling request resource 1 needs to be used according to the corresponding relationship shown in Table 1. The terminal device determines the PUCCH resource indicated by the scheduling request resource, and sends the PUCCH to the network device.

[0199] After receiving the PUCCH, the network device determines, according to the association relationship between the PUCCH and the scheduling request resource, that the scheduling request resource used by the terminal device is the scheduling request resource 1. Further, the network device determines, according to the corresponding relationship shown in Table 1, that the report configuration used by the terminal device is the report configuration c. The network device determines, according to the corresponding relationship shown in Table 2, that the current beam reporting is triggered by the trigger event 3.

[0200] After the terminal device indicates, to the network device through the first channel, that the type of the trigger event is the trigger event 3, the terminal device can send, on the second channel, the CSI report corresponding to the report configuration c. The network device can determine, according to the type of the trigger event, that the CSI report transmitted on the second channel is the CSI report corresponding to the report configuration c.

[0201] For the sending mode of the first mode, the network device can send DCI to the terminal device to schedule the second channel. The second channel scheduled by the network device for the terminal device can be used to carry the CSI report corresponding to the report configuration c. The DCI can be used to indicate the report configuration c. In some implementation modes, the network device can indicate the type of the event in the DCI. After receiving the DCI, the terminal device can transmit, on the second channel, the CSI report corresponding to the report configuration c.

[0202] For the sending mode of the second mode, the terminal device can transmit, on the second channel preconfigured by the network device, the CSI report corresponding to the report configuration c.

[0203] For example, if the terminal device determines that the trigger event 1 occurs, the terminal device determines, according to the corresponding relationship shown in Table 2, that the report configuration to be used is the report configuration a. Further, the terminal device can determine, according to the corresponding relationship shown in Table 1, that the scheduling request resource to be used is the scheduling request resource 0. The terminal device determines the PUCCH resource indicated by the scheduling request resource 0 and sends the PUCCH to the network device.

[0204] After receiving the PUCCH, the network device determines, according to the association relationship between the PUCCH and the scheduling request resource, that the scheduling request resource used by the terminal device is the scheduling request resource 0. Further, the network device determines, according to the corresponding relationship shown in Table 1, that the report configuration used by the terminal device is the report configuration a and / or the report configuration b. The network device determines, according to the corresponding relationship shown in Table 2, that the current beam reporting is triggered by the trigger event 1 and / or the trigger event 2.

[0205] After the terminal device indicates, through the first channel, that the type of the triggering event is the triggering event 1, the terminal device can send the CSI report corresponding to the reporting configuration a on the second channel. The network device can determine, according to the type of the triggering event, that the CSI report transmitted on the second channel is the CSI report corresponding to the reporting configuration a and / or the reporting configuration b.

[0206] For the sending mode of the first mode, the network device can send DCI to the terminal device to schedule the second channel. The second channel scheduled by the network device for the terminal device can be used to carry the CSI report corresponding to the reporting configuration a and / or the reporting configuration b. The DCI can be used to indicate the reporting configuration a and / or the reporting configuration b. In some implementations, the network device can indicate the type of the event in the DCI. After the terminal device receives the DCI, the terminal device can transmit the CSI report corresponding to the reporting configuration a on the second channel.

[0207] For the sending mode of the second mode, the terminal device can transmit the CSI report corresponding to the reporting configuration a on the second channel preconfigured by the network device.

[0208] Although one scheduling request resource corresponds to multiple reporting configurations, the network device determines multiple possible reporting configurations, thereby increasing the complexity of the terminal device decoding the second channel, but this way can reduce the number of corresponding relationships shown in Table 1 that need to be configured, thereby reducing the overhead.

[0209] The corresponding relationship shown in Table 1 can be determined by the network device. The network device can determine whether one scheduling request resource corresponds to one reporting configuration or multiple reporting configurations according to actual needs.

[0210] In some implementations, the association between the scheduling request resource and the reporting configuration can include that the scheduling request resource is associated with a triggering state. Since there is an association relationship between the triggering state and the reporting configuration, associating the scheduling request resource with the triggering state can establish the association relationship between the scheduling request resource and the reporting configuration.

[0211] In some implementations, one scheduling request resource can be associated with one or more triggering states. This mode is suitable for the sending mode of the first mode described above. The network device can send DCI to the terminal device. The DCI can indicate one triggering state, and the terminal device can send the CSI report corresponding to the reporting configuration associated with the triggering state in the second channel.

[0212] The association between the scheduling request resource and the triggering state can mean that the index of the scheduling request resource is associated with the index of the triggering state. For example, the index of one scheduling request resource is associated with the index of one or more triggering states.

[0213] Table 3 shows the correspondence between the scheduling request resource index and the trigger state index.

[0214] Table 3

[0215] As shown in Table 3, the scheduling request resource 0 corresponds to the trigger state 1 and the trigger state 2, the scheduling request resource 1 corresponds to the trigger state 3, and the scheduling request resource 2 corresponds to the trigger state 4.

[0216] Table 4 shows the correspondence between the trigger state index and the reporting configuration index.

[0217] Table 4

[0218] As shown in Table 4, the trigger state 1 corresponds to the reporting configuration a and the reporting configuration e, the trigger state 2 corresponds to the reporting configuration b, the trigger state 3 corresponds to the reporting configuration c and the reporting configuration f, and the trigger state 4 corresponds to the reporting configuration d.

[0219] Based on the correspondence shown in Table 3 and Table 4, the scheduling request resource 0 corresponds to the reporting configuration a, the reporting configuration b and the reporting configuration e, the scheduling request resource 1 corresponds to the reporting configuration c and the reporting configuration f, and the scheduling request resource 2 corresponds to the reporting configuration d.

[0220] For example, if the terminal device determines that the trigger event 1 occurs, the terminal device determines that the reporting configuration corresponding to the trigger event 1 is the reporting configuration a according to the correspondence shown in Table 2. The terminal device determines that the trigger state corresponding to the reporting configuration a is the trigger state 1 according to the correspondence shown in Table 4. The terminal device determines that the scheduling request resource corresponding to the trigger state 1 is the scheduling request resource 0 according to the correspondence shown in Table 3. The terminal device determines the PUCCH resource indicated by the scheduling request resource 0, and sends the PUCCH to the network device.

[0221] After receiving the PUCCH, the network device determines that the scheduling request resource used by the terminal device is the scheduling request resource 0 according to the association relationship between the PUCCH and the scheduling request resource. Further, the network device determines that the trigger state corresponding to the scheduling request resource 0 is the trigger state 1 and the trigger state 2 according to the correspondence shown in Table 3. The network device determines that the reporting configuration corresponding to the trigger state 1 and the trigger state 2 includes the reporting configuration a, the reporting configuration b and the reporting configuration e according to the correspondence shown in Table 4. According to the correspondence shown in Table 2, the network device can determine that the current beam reporting is triggered by one or more of the trigger event 1, the trigger event 2 and the trigger event 5.

[0222] After the terminal device indicates the type of the triggering event to be the triggering event 1 through the first channel to the network device, the terminal device can send the CSI report corresponding to the reporting configuration a on the second channel. The network device can determine, according to the type of the triggering event, that the CSI report transmitted on the second channel is the CSI report corresponding to one or more of the reporting configuration a, the reporting configuration b and the reporting configuration e.

[0223] For the sending mode of the first mode, the network device can send the DCI to the terminal device to schedule the second channel. The second channel scheduled by the network device for the terminal device can be used to carry the CSI report corresponding to the triggering state 1 and / or the triggering state 2. In some implementations, the network device can indicate the triggering state (such as the triggering state 1 and / or the triggering state 2) in the DCI. After receiving the DCI, the terminal device can transmit the CSI report corresponding to the reporting configuration a on the second channel.

[0224] For the sending mode of the second mode, the terminal device can transmit the CSI report corresponding to the reporting configuration a on the second channel pre-configured by the network device.

[0225] For example, if the terminal device determines that the triggering event 4 occurs, the terminal device determines, according to the corresponding relationship shown in Table 2, that the reporting configuration corresponding to the triggering event 4 is the reporting configuration d. The terminal device determines, according to the corresponding relationship shown in Table 4, that the triggering state corresponding to the reporting configuration d is the triggering state 4. The terminal device determines, according to the corresponding relationship shown in Table 3, that the scheduling request resource corresponding to the triggering state 4 is the scheduling request resource 2. The terminal device determines the PUCCH resource indicated by the scheduling request resource 2 and sends the PUCCH to the network device.

[0226] After receiving the PUCCH, the network device determines, according to the association relationship between the PUCCH and the scheduling request resource, that the scheduling request resource used by the terminal device is the scheduling request resource 2. Further, the network device determines, according to the corresponding relationship shown in Table 3, that the triggering state corresponding to the scheduling request resource 2 is the triggering state 4. The network device determines, according to the corresponding relationship shown in Table 4, that the reporting configuration corresponding to the triggering state 4 includes the reporting configuration d. According to the corresponding relationship shown in Table 2, the network device can determine that the current beam reporting is triggered by the triggering event 4.

[0227] After the terminal device indicates the type of the triggering event to be the triggering event 4 through the first channel to the network device, the terminal device can send the CSI report corresponding to the reporting configuration d on the second channel. The network device can determine, according to the type of the triggering event, that the CSI report transmitted on the second channel is the CSI report corresponding to the reporting configuration d.

[0228] For the sending mode of the first mode, the network device can send a DCI to the terminal device to schedule a second channel, and the second channel scheduled by the network device for the terminal device can be used to carry the CSI report corresponding to the trigger state 4. In some implementations, the network device can indicate the trigger state (such as the trigger state 4) in the DCI. After receiving the DCI, the terminal device can transmit the CSI report corresponding to the report configuration d on the second channel.

[0229] For the sending mode of the second mode, the terminal device can transmit the CSI report corresponding to the report configuration d on the second channel pre-configured by the network device.

[0230] In some implementations, for the CA scenario, the association of the scheduling request resource and the report configuration can include that the scheduling request resource is associated with a component carrier. Since there is an association relationship between the component carrier and the report configuration, the association of the scheduling request resource and the component carrier can establish the association relationship between the scheduling request resource and the report configuration.

[0231] In some implementations, one scheduling request resource can be associated with one or more component carriers. The association of the scheduling request resource and the component carrier can mean that the index of the scheduling request resource is associated with the index of the component carrier.

[0232] Table 5 shows a corresponding relationship between a scheduling request resource index and a component carrier index.

[0233] Table 5

[0234] As can be seen from Table 5, the scheduling request resource 0 corresponds to the component carrier 0, the scheduling request resource 1 corresponds to the component carrier 1, and the scheduling request resource 2 corresponds to the component carrier 2 and the component carrier 3.

[0235] Table 6 shows a corresponding relationship between a component carrier index and a report configuration index.

[0236] Table 6

[0237] As can be seen from Table 6, the component carrier 0 corresponds to the report configuration a and the report configuration b, the component carrier 1 corresponds to the report configuration c, the component carrier 2 corresponds to the report configuration d, and the component carrier 3 corresponds to the report configuration e and the report configuration f.

[0238] For example, if the terminal device determines that the triggering event 4 occurs, the terminal device determines, according to the correspondence relationship shown in Table 2, that the report configuration corresponding to the triggering event 4 is the report configuration d. The terminal device determines, according to the correspondence relationship shown in Table 6, that the component carrier corresponding to the report configuration d is the component carrier 2. The terminal device determines, according to the correspondence relationship shown in Table 5, that the scheduling request resource corresponding to the component carrier 2 is the scheduling request resource 2. The terminal device determines the PUCCH resource indicated by the scheduling request resource 2, and sends the PUCCH to the network device.

[0239] After the network device receives the PUCCH, the network device determines, according to the association relationship between the PUCCH and the scheduling request resource, that the scheduling request resource used by the terminal device is the scheduling request resource 2. Further, the network device determines, according to the correspondence relationship shown in Table 5, that the component carrier corresponding to the scheduling request resource 2 is the component carrier 2 and the component carrier 3. The network device determines, according to the correspondence relationship shown in Table 6, that the report configuration corresponding to the component carrier 2 and the component carrier 3 includes the report configuration d, the report configuration e and the report configuration f. According to the correspondence relationship shown in Table 2, the network device can determine that the beam report this time is triggered by one or more of the triggering event 4, the triggering event 5 and the triggering event 6.

[0240] After the terminal device indicates, through the first channel, that the type of the triggering event is the triggering event 3 to the network device, the terminal device can send the CSI report corresponding to the report configuration d on the second channel. The network device can determine, according to the type of the triggering event, that the CSI report transmitted on the second channel is the CSI report corresponding to one or more of the report configuration d, the report configuration e and the report configuration f.

[0241] For the sending mode of the first mode, the network device can send the DCI to the terminal device to schedule the second channel. The second channel scheduled by the network device for the terminal device can be used to carry the CSI report corresponding to the component carrier 2. The DCI can be used to indicate the component carrier 2. After the terminal device receives the DCI, the terminal device can transmit the CSI report corresponding to the report configuration d on the second channel.

[0242] For the sending mode of the second mode, the terminal device can transmit the CSI report corresponding to the report configuration d on the second channel pre-configured by the network device.

[0243] For example, if the terminal device determines that the trigger event 3 occurs, the terminal device determines, according to the correspondence relationship shown in Table 2, that the report configuration corresponding to the trigger event 3 is the report configuration c. The terminal device determines, according to the correspondence relationship shown in Table 6, that the component carrier corresponding to the report configuration c is the component carrier 1. The terminal device determines, according to the correspondence relationship shown in Table 5, that the scheduling request resource corresponding to the component carrier 1 is the scheduling request resource 1. The terminal device determines the PUCCH resource indicated by the scheduling request resource 1, and sends the PUCCH to the network device.

[0244] After the network device receives the PUCCH, the network device determines, according to the association relationship between the PUCCH and the scheduling request resource, that the scheduling request resource used by the terminal device is the scheduling request resource 1. Further, the network device determines, according to the correspondence relationship shown in Table 5, that the component carrier corresponding to the scheduling request resource 1 is the component carrier 1. The network device determines, according to the correspondence relationship shown in Table 6, that the report configuration corresponding to the component carrier 1 includes the report configuration c. According to the correspondence relationship shown in Table 2, the network device can determine that the current beam report is triggered by the trigger event 3.

[0245] After the terminal device indicates, through the first channel, to the network device that the type of the trigger event is the trigger event 3, the terminal device can send the CSI report corresponding to the report configuration c on the second channel. The network device can determine, according to the type of the trigger event, that the CSI report transmitted on the second channel is the CSI report corresponding to the report configuration c.

[0246] For the sending mode of the first mode, the network device can send the DCI to the terminal device to schedule the second channel. The second channel scheduled by the network device for the terminal device can be used to carry the CSI report corresponding to the component carrier 1. The DCI can be used to indicate the component carrier 1. After the terminal device receives the DCI, the terminal device can transmit the CSI report corresponding to the report configuration c on the second channel.

[0247] For the sending mode of the second mode, the terminal device can transmit the CSI report corresponding to the report configuration c on the second channel pre-configured by the network device.

[0248] In some implementations, the index ordering priority of the reporting configurations is determined by a priority value associated with one reporting configuration. If the priority value of a first CSI report is lower than the priority value of a second CSI report, the first CSI report is considered to have a higher priority than the second CSI report or the index of the reporting configuration of the first CSI report is smaller. The priority value is related to at least one of the transmission mode (e.g., periodic, semi-persistent, or aperiodic) of the CSI report, the channel type on which the CSI report is carried, the content carried by the CSI report, the component carrier index, and the index of the reporting configuration within a component carrier. For example, the priority value can be determined according to the following formula: P(y, k, c, s) = 2 · N cells · M s · y + N cells · M s · k + M s · c + s

[0249] where y = 0 for an aperiodic CSI report transmitted on PUSCH, y = 1 for a semi-persistent CSI report transmitted on PUSCH, y = 2 for a semi-persistent CSI report transmitted on PUCCH, and y = 3 for a periodic CSI report transmitted on PUCCH; k = 0 for a CSI report carrying L1-RSRP or L1-SINR, and k = 1 for a CSI report not carrying L1-RSRP or L1-SINR; c is the component carrier index; N cells is the maximum number of component carriers; s is the index of the reporting configuration within a component carrier; and M s is the maximum number of reporting configurations within a component carrier.

[0250] In some implementations, for the second mode of transmission, the network device can configure the terminal device with multiple scheduling request resources and multiple second channel resources, and the multiple scheduling request resources have a corresponding relationship with the multiple second channel resources. For example, the terminal device determines a scheduling request resource based on a certain triggering event, and then transmits the first channel (i.e., transmits the first channel using the PUCCH resource corresponding to the scheduling request resource). In addition, the terminal device can also determine the second channel resource according to the scheduling request resource, and transmit the second channel using the second channel resource.

[0251] Example One describes the association relationship between the scheduling request resource and the reporting configuration. In the following, Example Two describes the association relationship between the PUCCH resource and the reporting configuration.

[0252] Example Two

[0253] The association between the first channel and the triggering event can be achieved through the association between the PUCCH resource and the reporting configuration. One PUCCH resource can be associated with one or more reporting configurations, and the terminal device can distinguish different reporting configurations through different PUCCH resources. Generally, different reporting configurations can correspond to different triggering event types. Based on this, after the network device receives the first channel, the network device can determine the type of the triggering event according to the association between the first channel and the reporting configuration, and the corresponding relationship between the reporting configuration and the type of the triggering event. Further, the network device can determine which CSI report corresponding to the reporting configuration carried by the second channel.

[0254] In some implementations, one scheduling request resource can be associated with multiple PUCCH resources, and one PUCCH resource can be associated with one or more reporting configurations. The terminal device can distinguish different reporting configurations through different PUCCH resources. Generally, different reporting configurations can correspond to different triggering event types.

[0255] In some implementations, the association between the PUCCH resource and the reporting configuration can refer to the index relationship between the PUCCH resource and the reporting configuration. For example, the index of one PUCCH resource can be associated with the index of one or more reporting configurations.

[0256] The process of the terminal device indicating the type of the triggering event to the network device and the process of the network device determining the type of the triggering event will be described in detail below in combination with Table 7 and Table 8.

[0257] Table 7 shows the corresponding relationship between the PUCCH resource index and the reporting configuration index.

[0258] Table 7

[0259] As can be seen from Table 7, PUCCH resource 0 corresponds to reporting configuration a and reporting configuration b, PUCCH resource 1 corresponds to reporting configuration c, and PUCCH resource 2 corresponds to reporting configuration d, reporting configuration e, and reporting configuration f.

[0260] Table 8 shows the corresponding relationship between the reporting configuration index and the triggering event type.

[0261] Table 8

[0262] As can be seen from Table 8, reporting configuration a corresponds to triggering event type 1, reporting configuration b corresponds to triggering event type 2, reporting configuration c corresponds to triggering event type 3, reporting configuration d corresponds to triggering event type 4, reporting configuration e corresponds to triggering event type 5, and reporting configuration f corresponds to triggering event type 6.

[0263] For example, if the terminal device determines that the trigger event 3 occurs, the terminal device determines that the reporting configuration to be used is the reporting configuration c according to the correspondence relationship shown in Table 8. Further, the terminal device can determine that the PUCCH resource to be used is the PUCCH resource 1 according to the correspondence relationship shown in Table 7. The terminal device determines the PUCCH resource indicated by the PUCCH resource 1, and sends the PUCCH to the network device.

[0264] After receiving the PUCCH, the network device determines that the PUCCH resource used by the terminal device is the PUCCH resource 1. Further, the network device determines that the reporting configuration used by the terminal device is the reporting configuration c according to the correspondence relationship shown in Table 7. The network device determines that the current beam reporting is triggered by the trigger event 3 according to the correspondence relationship shown in Table 8.

[0265] After the terminal device indicates the type of the trigger event to the network device through the first channel, the terminal device can send the CSI report corresponding to the reporting configuration c on the second channel. The network device can determine that the CSI report transmitted on the second channel is the CSI report corresponding to the reporting configuration c according to the type of the trigger event.

[0266] For the transmission mode of the first mode, the network device can send a DCI to the terminal device to schedule the second channel. The second channel scheduled by the network device for the terminal device can be used to carry the CSI report corresponding to the reporting configuration c. The DCI can be used to indicate the reporting configuration c. In some implementations, the network device can indicate the type of the event in the DCI. After receiving the DCI, the terminal device can transmit the CSI report corresponding to the reporting configuration c on the second channel.

[0267] For the transmission mode of the second mode, the terminal device can transmit the CSI report corresponding to the reporting configuration c on the second channel pre-configured by the network device.

[0268] For example, if the terminal device determines that the trigger event 1 occurs, the terminal device determines that the reporting configuration to be used is the reporting configuration a according to the correspondence relationship shown in Table 8. Further, the terminal device can determine that the PUCCH resource to be used is the PUCCH resource 0 according to the correspondence relationship shown in Table 7. The terminal device determines the PUCCH resource indicated by the PUCCH resource 0, and sends the PUCCH to the network device.

[0269] After receiving the PUCCH, the network device determines that the PUCCH resource used by the terminal device is the PUCCH resource 0. Further, the network device determines that the reporting configuration used by the terminal device is the reporting configuration a and / or the reporting configuration b according to the correspondence relationship shown in Table 7. The network device determines that the current beam reporting is triggered by the trigger event 1 and / or the trigger event 2 according to the correspondence relationship shown in Table 8.

[0270] After the terminal device indicates that the type of the triggering event is the triggering event 1 through the first channel to the network device, the terminal device can send the CSI report corresponding to the reporting configuration a on the second channel. The network device can determine that the CSI report transmitted on the second channel is the CSI report corresponding to the reporting configuration a and / or the reporting configuration b according to the type of the triggering event.

[0271] For the sending mode of the first mode, the network device can send the DCI to the terminal device to schedule the second channel. The second channel scheduled by the network device for the terminal device can be used to carry the CSI report corresponding to the reporting configuration a and / or the reporting configuration b. The DCI can be used to indicate the reporting configuration a and / or the reporting configuration b. In some implementations, the network device can indicate the type of the event in the DCI. After the terminal device receives the DCI, the terminal device can transmit the CSI report corresponding to the reporting configuration a on the second channel.

[0272] For the sending mode of the second mode, the terminal device can transmit the CSI report corresponding to the reporting configuration a on the second channel pre-configured by the network device.

[0273] Although one PUCCH resource corresponds to multiple reporting configurations, which can cause the network device to determine multiple possible reporting configurations, thereby increasing the complexity of the terminal device to decode the second channel, this way can reduce the number of corresponding relationships shown in Table 7 that need to be configured, thereby reducing the overhead.

[0274] The corresponding relationship shown in Table 7 can be determined by the network device. The network device can determine whether one PUCCH resource corresponds to one reporting configuration or multiple reporting configurations according to actual needs.

[0275] In some implementations, the association between the PUCCH resource and the reporting configuration can include that the PUCCH resource is associated with a triggering state. Since there is an association relationship between the triggering state and the reporting configuration, associating the PUCCH resource with the triggering state can establish the association relationship between the PUCCH resource and the reporting configuration.

[0276] In some implementations, one PUCCH resource can be associated with one or more triggering states. This mode is suitable for the sending mode of the first mode described above. The network device can send the DCI to the terminal device. The DCI can indicate one triggering state. The terminal device can send the CSI report corresponding to the reporting configuration associated with the triggering state in the second channel.

[0277] The association between the PUCCH resource and the triggering state can mean that the index of the PUCCH resource is associated with the index of the triggering state. For example, the index of one PUCCH resource is associated with the index of one or more triggering states.

[0278] Table 9 shows the correspondence between the PUCCH resource index and the trigger state index.

[0279] Table 9

[0280] As shown in Table 9, PUCCH resource 0 corresponds to trigger state 1 and trigger state 2, PUCCH resource 1 corresponds to trigger state 3, and PUCCH resource 2 corresponds to trigger state 4.

[0281] Table 10 shows the correspondence between the trigger state index and the report configuration index.

[0282] Table 10

[0283] As shown in Table 10, trigger state 1 corresponds to report configuration a and report configuration e, trigger state 2 corresponds to report configuration b, trigger state 3 corresponds to report configuration c and report configuration f, and trigger state 4 corresponds to report configuration d.

[0284] Based on the correspondence shown in Table 9 and Table 10, PUCCH resource 0 corresponds to report configuration a, report configuration b and report configuration e, PUCCH resource 1 corresponds to report configuration c and report configuration f, and PUCCH resource 2 corresponds to report configuration d.

[0285] For example, if the terminal device determines that trigger event 1 occurs, the terminal device determines that the report configuration corresponding to trigger event 1 is report configuration a according to the correspondence shown in Table 8. The terminal device determines that the trigger state corresponding to report configuration a is trigger state 1 according to the correspondence shown in Table 10. The terminal device determines that the PUCCH resource corresponding to trigger state 1 is PUCCH resource 0 according to the correspondence shown in Table 9. The terminal device determines the PUCCH resource indicated by PUCCH resource 0, and sends the PUCCH to the network device.

[0286] After receiving the PUCCH, the network device determines that the PUCCH resource used by the terminal device is PUCCH resource 0. Further, the network device determines that the trigger state corresponding to PUCCH resource 0 is trigger state 1 and trigger state 2 according to the correspondence shown in Table 9. The network device determines that the report configuration corresponding to trigger state 1 and trigger state 2 includes report configuration a, report configuration b and report configuration e according to the correspondence shown in Table 10. According to the correspondence shown in Table 8, the network device can determine that the current beam reporting is triggered by one or more of trigger event 1, trigger event 2 and trigger event 5.

[0287] After the terminal device indicates the type of the triggering event to be the triggering event 1 through the first channel to the network device, the terminal device can send the CSI report corresponding to the reporting configuration a on the second channel. The network device can determine, according to the type of the triggering event, that the CSI report transmitted on the second channel is the CSI report corresponding to one or more of the reporting configuration a, the reporting configuration b and the reporting configuration e.

[0288] For the sending mode of the first mode, the network device can send the DCI to the terminal device to schedule the second channel. The second channel scheduled by the network device for the terminal device can be used to carry the CSI report corresponding to the triggering state 1 and / or the triggering state 2. In some implementations, the network device can indicate the triggering state (such as the triggering state 1 and / or the triggering state 2) in the DCI. After receiving the DCI, the terminal device can transmit the CSI report corresponding to the reporting configuration a on the second channel.

[0289] For the sending mode of the second mode, the terminal device can transmit the CSI report corresponding to the reporting configuration a on the second channel pre-configured by the network device.

[0290] For example, if the terminal device determines that the triggering event 4 occurs, the terminal device determines, according to the corresponding relationship shown in Table 8, that the reporting configuration corresponding to the triggering event 4 is the reporting configuration d. The terminal device determines, according to the corresponding relationship shown in Table 10, that the triggering state corresponding to the reporting configuration d is the triggering state 4. The terminal device determines, according to the corresponding relationship shown in Table 9, that the PUCCH resource corresponding to the triggering state 4 is the PUCCH resource 2. The terminal device determines the PUCCH resource indicated by the PUCCH resource 2 and sends the PUCCH to the network device.

[0291] After receiving the PUCCH, the network device determines that the PUCCH resource used by the terminal device is the PUCCH resource 2. Further, the network device determines, according to the corresponding relationship shown in Table 9, that the triggering state corresponding to the PUCCH resource 2 is the triggering state 4. The network device determines, according to the corresponding relationship shown in Table 10, that the reporting configuration corresponding to the triggering state 4 includes the reporting configuration d. According to the corresponding relationship shown in Table 8, the network device can determine that the current beam reporting is triggered by the triggering event 4.

[0292] After the terminal device indicates the type of the triggering event to be the triggering event 4 through the first channel to the network device, the terminal device can send the CSI report corresponding to the reporting configuration d on the second channel. The network device can determine, according to the type of the triggering event, that the CSI report transmitted on the second channel is the CSI report corresponding to the reporting configuration d.

[0293] For the sending mode of the first mode, the network device can send a DCI to the terminal device to schedule the second channel, and the second channel scheduled by the network device for the terminal device can be used to carry the CSI report corresponding to the trigger state 4. In some implementations, the network device can indicate the trigger state (such as the trigger state 4) in the DCI. After receiving the DCI, the terminal device can transmit the CSI report corresponding to the report configuration d on the second channel.

[0294] For the sending mode of the second mode, the terminal device can transmit the CSI report corresponding to the report configuration d on the second channel pre-configured by the network device.

[0295] In some implementations, for the CA scenario, the association of the PUCCH resource and the report configuration can include the association of the PUCCH resource and the component carrier. Since there is an association relationship between the component carrier and the report configuration, the association of the PUCCH resource and the component carrier can establish the association relationship between the PUCCH resource and the report configuration.

[0296] In some implementations, one PUCCH resource can be associated with one or more component carriers. The association of the PUCCH resource and the component carrier can mean the association of the index of the PUCCH resource and the index of the component carrier.

[0297] Table 11 shows a corresponding relationship between a PUCCH resource index and a component carrier index.

[0298] Table 11

[0299] As can be seen from Table 11, PUCCH resource 0 corresponds to component carrier 0, PUCCH resource 1 corresponds to component carrier 1, PUCCH resource 2 corresponds to component carrier 2 and component carrier 3.

[0300] Table 12 shows a corresponding relationship between a component carrier index and a report configuration index.

[0301] Table 12

[0302] As can be seen from Table 12, component carrier 0 corresponds to report configuration a and report configuration b, component carrier 1 corresponds to report configuration c, component carrier 2 corresponds to report configuration d, and component carrier 3 corresponds to report configuration e and report configuration f.

[0303] For example, if the terminal device determines that the triggering event 4 occurs, the terminal device determines, according to the correspondence relationship shown in Table 8, that the reporting configuration corresponding to the triggering event 4 is the reporting configuration d. The terminal device determines, according to the correspondence relationship shown in Table 12, that the component carrier corresponding to the reporting configuration d is the component carrier 2. The terminal device determines, according to the correspondence relationship shown in Table 11, that the PUCCH resource corresponding to the component carrier 2 is the PUCCH resource 2. The terminal device determines the PUCCH resource indicated by the PUCCH resource 2, and sends the PUCCH to the network device.

[0304] After the network device receives the PUCCH, the network device determines that the PUCCH resource used by the terminal device is the PUCCH resource 2. Further, the network device determines, according to the correspondence relationship shown in Table 11, that the component carrier corresponding to the PUCCH resource 2 is the component carrier 2 and the component carrier 3. The network device determines, according to the correspondence relationship shown in Table 12, that the reporting configuration corresponding to the component carrier 2 and the component carrier 3 includes the reporting configuration d, the reporting configuration e and the reporting configuration f. According to the correspondence relationship shown in Table 8, the network device can determine that the current beam reporting is triggered by one or more of the triggering event 4, the triggering event 5 and the triggering event 6.

[0305] After the terminal device indicates, to the network device through the first channel, that the type of the triggering event is the triggering event 3, the terminal device can send the CSI report corresponding to the reporting configuration d on the second channel. The network device can determine, according to the type of the triggering event, that the CSI report transmitted on the second channel is the CSI report corresponding to one or more of the reporting configuration d, the reporting configuration e and the reporting configuration f.

[0306] For the sending mode of the first mode, the network device can send the DCI to the terminal device to schedule the second channel. The second channel scheduled by the network device for the terminal device can be used to carry the CSI report corresponding to the component carrier 2. The DCI can be used to indicate the component carrier 2. After the terminal device receives the DCI, the terminal device can transmit the CSI report corresponding to the reporting configuration d on the second channel.

[0307] For the sending mode of the second mode, the terminal device can transmit the CSI report corresponding to the reporting configuration d on the second channel pre-configured by the network device.

[0308] For example, if the terminal device determines that the triggering event 3 occurs, the terminal device determines, according to the correspondence relationship shown in Table 8, that the reporting configuration corresponding to the triggering event 3 is the reporting configuration c. The terminal device determines, according to the correspondence relationship shown in Table 12, that the component carrier corresponding to the reporting configuration c is the component carrier 1. The terminal device determines, according to the correspondence relationship shown in Table 11, that the PUCCH resource corresponding to the component carrier 1 is the PUCCH resource 1. The terminal device determines the PUCCH resource indicated by the PUCCH resource 1, and sends the PUCCH to the network device.

[0309] The network device receives the PUCCH, determines that the PUCCH resource used by the terminal device is PUCCH resource 1. Further, the network device determines that the component carrier corresponding to the PUCCH resource 1 is component carrier 1 according to the correspondence relationship shown in Table 11. The network device determines that the report configuration corresponding to the component carrier 1 includes report configuration c according to the correspondence relationship shown in Table 12. According to the correspondence relationship shown in Table 8, the network device can determine that the current beam reporting is triggered by trigger event 3.

[0310] After the terminal device indicates the type of the trigger event to the network device through the first channel, the type of the trigger event is trigger event 3, the terminal device can send the CSI report corresponding to the report configuration c on the second channel. The network device can determine that the CSI report transmitted on the second channel is the CSI report corresponding to the report configuration c according to the type of the trigger event.

[0311] For the transmission mode of mode one, the network device can send DCI to the terminal device to schedule the second channel. The second channel scheduled by the network device for the terminal device can be used to carry the CSI report corresponding to the component carrier 1. The DCI can be used to indicate the component carrier 1. After the terminal device receives the DCI, the terminal device can transmit the CSI report corresponding to the report configuration c on the second channel.

[0312] For the transmission mode of mode two, the terminal device can transmit the CSI report corresponding to the report configuration c on the second channel preconfigured by the network device.

[0313] In some implementations, the index order priority of the report configuration is determined by a priority value associated with the report configuration. If the priority value of the first CSI report is lower than the priority value of the second CSI report, it is considered that the first CSI report is prior to the second CSI report or the index of the report configuration of the first CSI report is smaller. The priority value is related to at least one of the transmission mode of the CSI report (such as periodic, semi-persistent or aperiodic CSI report), the channel type carrying the CSI report, the report content carried, the component carrier index and the report configuration index in a component carrier. For example, the priority value can be determined according to the following formula: P(y, k, c, s) = 2 N cells M s y + N cells M s k + M s c + s

[0314] where y = 0 for aperiodic CSI reporting transmitted on PUSCH; y = 1 for semi-persistent CSI reporting transmitted on PUSCH; y = 2 for semi-persistent CSI reporting transmitted on PUCCH; and y = 3 for periodic CSI reporting transmitted on PUCCH; k = 0 for CSI reporting carrying L1-RSRP or L1-SINR; and k = 1 for CSI reporting not carrying L1-RSRP or L1-SINR; c is the component carrier index, N cells is the maximum number of component carriers; s is the reporting configuration index within a component carrier, M s is the maximum number of reporting configurations within a component carrier.

[0315] In some implementations, for the second mode of transmission mode, the network device can configure the terminal device with multiple PUCCH resources and multiple second channel resources, and the PUCCH resources have a corresponding relationship with the multiple second channel resources. For example, the terminal device determines a PUCCH resource based on a certain triggering event, and then transmits the first channel (i.e., transmits the first channel by using the PUCCH resource), in addition, the terminal device can also determine the second channel resource according to the PUCCH resource, and transmit the second channel by using the second channel resource.

[0316] The embodiments of the present application do not make specific limitations on the determination mode of the PUCCH resource in example two. As an example, the PUCCH resource can be configured or indicated to the terminal device by the network device. If the PUCCH resource is directly configured or indicated by the network device, the PUCCH resource will have corresponding index information. As another example, the PUCCH resource can also be determined by the terminal device according to the PUCCH reference resource. The PUCCH resource determined in this way can also be referred to as a PUCCH resource unit, and this mode does not require the network device to configure each PUCCH resource, which is beneficial to reduce the signaling overhead. In addition, the PUCCH resource unit determined in this way is relatively concentrated, which is convenient for the network device to reserve resources. The determination mode of the PUCCH resource unit will be described below in connection with example three.

[0317] Example three

[0318] The terminal device can determine a plurality of first channel resource units according to the first information. For example, when the first channel is a PUCCH, the first information includes one or more of the following: a time domain position of a PUCCH reference resource, a frequency domain position of the PUCCH reference resource, a cyclic shift, an orthogonal cover code, a frequency division multiplexing number, a frequency division interval, a time division multiplexing number, and a time division interval. The cyclic shift can be an initial cyclic shift. The above-mentioned first information can be configured by the network device to the terminal device. For example, the PUCCH reference resource (such as the time domain position of the PUCCH reference resource and the frequency domain position of the PUCCH reference resource) can be configured by the network device to the terminal device. In addition, the network device can configure one or more of the cyclic shift, the orthogonal cover code, the frequency division multiplexing number, the frequency division interval, the time division multiplexing number, and the time division interval for the terminal device.

[0319] For the cyclic shift, the cyclic shift used by different PUCCH resource units to generate a PUCCH sequence can be different, or in other words, the initial cyclic shift used by different PUCCH resource units to generate a PUCCH sequence can be different. Generally speaking, if the cyclic shift used by different PUCCH resource units to generate a PUCCH sequence is different, the generated PUCCH sequences are orthogonal.

[0320] For the orthogonal cover code, the orthogonal cover code used by different PUCCH resource units to generate a PUCCH sequence can be different. Generally speaking, different terminal devices can use different orthogonal codes to generate PUCCH sequences when transmitting PUCCH on the same time domain resource and frequency domain resource, so that the PUCCH sequences (or signals) are orthogonal in the code domain, so as to reduce the interference between terminal devices.

[0321] By using different cyclic shifts and / or orthogonal cover codes to generate PUCCH resource units, the multiplexing of multiple terminal devices on the resource can be achieved in the code domain.

[0322] The frequency division multiplexing number can refer to the number of repetitions of the PUCCH reference resource in the frequency domain, the frequency division interval can refer to the interval of two adjacent PUCCH resource units in the frequency domain, the time division multiplexing number can refer to the number of repetitions of the PUCCH reference resource in the time domain, and the time division interval can refer to the interval of two adjacent PUCCH resource units in the time domain, as shown in FIG. 11.

[0323] The following examples illustrate the manner in which the terminal device determines the PUCCH resource unit.

[0324] Example #1-1, assuming that the network device configures the terminal device with the following parameters: the time-frequency domain location of the PUCCH reference resource, and the number of initial cyclic shifts is 4, the terminal device can determine 4 PUCCH resource units. The initial cyclic shifts of different PUCCH resource units are different, but all the PUCCH resource units have the same time-frequency domain location as the PUCCH reference resource.

[0325] Example #1-2, assuming that the network device configures the terminal device with the following parameters: the time-frequency domain location of the PUCCH reference resource, the number of initial cyclic shifts is 2, the number of frequency division multiplexing is 2, and the number of time division multiplexing is 2, the terminal device can determine 8 PUCCH resource units. One or more of the following parameters of different PUCCH resource units are different: initial cyclic shift, time domain location, and frequency domain location.

[0326] Example #1-3, assuming that the network device configures the terminal device with the following parameters: the time-frequency domain location of the PUCCH reference resource, the number of initial cyclic shifts is 2, the number of orthogonal cover codes is 2, the number of frequency division multiplexing is 2, and the number of time division multiplexing is 2, the terminal device can determine a total of 16 PUCCH resource units. One or more of the following parameters of different PUCCH resource units are different: initial cyclic shift, orthogonal cover code, time domain location, and frequency domain location.

[0327] The embodiment of the present application can determine the index of the PUCCH resource unit according to the priority of the PUCCH resource unit. The priority principle of the PUCCH resource unit can include one or more of the following priority principles. The following priority principles are introduced. It should be noted that the following priority principles are only examples and should not limit the embodiment of the present application. The embodiment of the present application can also include other priority principles.

[0328] Priority principle #1-1: sort in the order of cyclic shift, frequency domain location, and time domain location.

[0329] First, sort the multiple PUCCH resource units in the same time domain location and frequency domain location in the order of increasing size of the cyclic shift related index; then, sort in the order of increasing size of the frequency domain location related index; finally, sort in the order of increasing size of the time domain location related index.

[0330] Priority principle #1-2: sort in the order of frequency domain location, cyclic shift, and time domain location.

[0331] First, the PUCCH resource units in the same time domain position and frequency domain position are sorted in ascending order of the size of the cyclic shift related index, and then sorted in ascending order of the size of the orthogonal cover code related index; and finally, sorted in ascending order of the size of the time domain position related index.

[0332] Priority principle #1-3: sorted in the order of cyclic shift, orthogonal cover code, frequency domain position, and time domain position. First, the PUCCH resource units in the same time domain position and frequency domain position are sorted in ascending order of the size of the cyclic shift related index, and then sorted in ascending order of the size of the orthogonal cover code related index; and then, sorted in ascending order of the size of the frequency domain position related index; and finally, sorted in ascending order of the size of the time domain position related index.

[0333] Priority principle #1-4: sorted in the order of frequency domain position, cyclic shift, orthogonal cover code, and time domain position.

[0334] First, the PUCCH resource units in the same time domain position and frequency domain position are sorted in ascending order of the size of the frequency domain position related index; and then, sorted in ascending order of the size of the cyclic shift related index, and then sorted in ascending order of the size of the orthogonal cover code related index; and finally, sorted in ascending order of the size of the time domain position related index.

[0335] Priority principle #1-5: sorted in the order of time domain position, cyclic shift, orthogonal cover code, and frequency domain position.

[0336] First, the PUCCH resource units in the same time domain position and frequency domain position are sorted in ascending order of the size of the time domain position related index; and then, sorted in ascending order of the size of the cyclic shift related index, and then sorted in ascending order of the size of the orthogonal cover code related index; and finally, sorted in ascending order of the size of the frequency domain position related index.

[0337] Priority principle #1-6: sorted in the order of time domain position, orthogonal cover code, cyclic shift, and frequency domain position.

[0338] First, the PUCCH resource units in the same time domain position and frequency domain position are sorted in ascending order of the size of the time domain position related index; and then, sorted in ascending order of the size of the orthogonal cover code related index, and then sorted in ascending order of the size of the cyclic shift related index; and finally, sorted in ascending order of the size of the frequency domain position related index.

[0339] Priority principle #1-7: Sort in the order of frequency domain location, then OCC, then cyclic shift, then time domain location.

[0340] First, sort in the order of increasing size of time domain location related index; then, for multiple PUCCH resource units in the same time domain location and frequency domain location, sort in the order of increasing size of OCC related index, and then in the order of increasing size of cyclic shift related index; finally, sort in the order of increasing size of frequency domain location related index.

[0341] Priority principle #1-8: Sort in the order of time domain location, then cyclic shift, then frequency domain location.

[0342] First, sort in the order of increasing size of time domain location related index; then, for multiple PUCCH resource units in the same time domain location and frequency domain location, sort in the order of increasing size of cyclic shift related index; finally, sort in the order of increasing size of frequency domain location related index.

[0343] In some implementations, the association between the first channel and the triggering event can be achieved through the association between the PUCCH resource unit and the report configuration. One PUCCH resource unit can be associated with one or more report configurations, and the terminal device can distinguish different report configurations through different PUCCH resource units. Generally, different report configurations can correspond to different types of triggering events. Based on this, after the network device receives the first channel, it can determine the type of triggering event according to the association between the first channel and the report configuration, and the corresponding relationship between the report configuration and the type of triggering event. Further, the network device can determine which CSI report corresponding to the report configuration carried by the second channel.

[0344] In some implementations, one scheduling request resource can be associated with multiple PUCCH resource units, and one PUCCH resource unit can be associated with one or more report configurations, and the terminal device can distinguish different report configurations through different PUCCH resource units. Generally, different report configurations can correspond to different types of triggering events.

[0345] According to the aforementioned example #1-2 and priority principle #1-2, the corresponding relationship between the PUCCH resource unit and the report configuration is established. Assuming that the values of the two initial cyclic shifts are 3 and 6 respectively, and the indexes of the 8 report configurations are 1-8 respectively, the following corresponding relationship is obtained.

[0346] The PUCCH resource unit with initial cyclic shift of 3 and the PUCCH resource unit with initial cyclic shift of 6 are associated with the report configuration with index of 1 at the two PUCCH resource units at the first frequency domain position and the first time domain position.

[0347] The PUCCH resource unit with initial cyclic shift of 3 and the PUCCH resource unit with initial cyclic shift of 6 are associated with the report configuration with index of 3 at the two PUCCH resource units at the second frequency domain position and the first time domain position.

[0348] The PUCCH resource unit with initial cyclic shift of 3 and the PUCCH resource unit with initial cyclic shift of 6 are associated with the report configuration with index of 5 at the two PUCCH resource units at the first frequency domain position and the second time domain position.

[0349] The PUCCH resource unit with initial cyclic shift of 3 and the PUCCH resource unit with initial cyclic shift of 6 are associated with the report configuration with index of 7 at the two PUCCH resource units at the second frequency domain position and the second time domain position.

[0350] According to the aforementioned examples #1-3 and the priority principle #1-4, the correspondence between the PUCCH resource units and the report configurations is established. Assuming that the values of the two initial cyclic shifts are 3 and 6 respectively, the indexes of the 16 report configurations are 1-16 respectively, and the indexes of the two orthogonal cover codes are 1 and 2 respectively, the correspondence is as follows.

[0351] The PUCCH resource unit with initial cyclic shift of 3 and the PUCCH resource unit with initial cyclic shift of 6 are associated with the report configuration with index of 1 at the four PUCCH resource units at the first frequency domain position and the first time domain position, the PUCCH resource unit with initial cyclic shift of 3 and the PUCCH resource unit with initial cyclic shift of 6 are associated with the report configuration with index of 2, the PUCCH resource unit with initial cyclic shift of 6 and the PUCCH resource unit with initial cyclic shift of 6 are associated with the report configuration with index of 3, and the PUCCH resource unit with initial cyclic shift of 6 and the PUCCH resource unit with initial cyclic shift of 6 are associated with the report configuration with index of 4.

[0352] The PUCCH resource unit with initial cyclic shift of 3 and index of 1 of the orthogonal cover code is associated with the reporting configuration with index of 9, the PUCCH resource unit with initial cyclic shift of 3 and index of 2 of the orthogonal cover code is associated with the reporting configuration with index of 10, the PUCCH resource unit with initial cyclic shift of 6 and index of 1 of the orthogonal cover code is associated with the reporting configuration with index of 11, and the PUCCH resource unit with initial cyclic shift of 6 and index of 2 of the orthogonal cover code is associated with the reporting configuration with index of 12.

[0353] The PUCCH resource unit with initial cyclic shift of 3 and index of 1 of the orthogonal cover code is associated with the reporting configuration with index of 9, the PUCCH resource unit with initial cyclic shift of 3 and index of 2 of the orthogonal cover code is associated with the reporting configuration with index of 10, the PUCCH resource unit with initial cyclic shift of 6 and index of 1 of the orthogonal cover code is associated with the reporting configuration with index of 11, and the PUCCH resource unit with initial cyclic shift of 6 and index of 2 of the orthogonal cover code is associated with the reporting configuration with index of 12.

[0354] The PUCCH resource unit with initial cyclic shift of 3 and index of 1 of the orthogonal cover code is associated with the reporting configuration with index of 9, the PUCCH resource unit with initial cyclic shift of 3 and index of 2 of the orthogonal cover code is associated with the reporting configuration with index of 10, the PUCCH resource unit with initial cyclic shift of 6 and index of 1 of the orthogonal cover code is associated with the reporting configuration with index of 11, and the PUCCH resource unit with initial cyclic shift of 6 and index of 2 of the orthogonal cover code is associated with the reporting configuration with index of 12.

[0355] In some implementations, the number of PUCCH resource units can be greater than the number of reporting configurations. If there are remaining PUCCH resource units after establishing the correspondence between the PUCCH resource units and the reporting configurations in the above manner, the remaining PUCCH resource units are not associated with the reporting configurations.

[0356] As described above, a PUCCH resource can be associated with a trigger state, that is, a PUCCH resource unit can be associated with a trigger state. In some implementations, the number of PUCCH resource units can be greater than or equal to the number of trigger states. If the number of PUCCH resource units is greater than the number of trigger states, after establishing the association between the PUCCH resource units and the trigger states in the above manner, the remaining PUCCH resource units are not associated with the trigger states.

[0357] In some implementations, for a CA scenario, the index ordering priority of the reporting configuration is related to the index of the component carrier and the index of the reporting configuration. For example, the reporting configuration with a smaller component carrier index has a higher ordering priority; when the component carrier indexes are the same, the CSI report with a smaller reporting configuration index has a higher ordering priority. In some implementations, the reporting configuration with a higher ordering priority has a smaller index value.

[0358] For example, assuming that the network device configures a terminal device with reporting configurations of 2 component carriers, the two component carriers are component carrier 1 and component carrier 2 respectively, and configures the terminal device with 4 reporting configurations, the reporting configurations from high to low ordering priority are: reporting configuration 1 corresponding to component carrier 1 → reporting configuration 2 corresponding to component carrier 1 → reporting configuration 3 corresponding to component carrier 1 → reporting configuration 4 corresponding to component carrier 1 → reporting configuration 1 corresponding to component carrier 2 → reporting configuration 2 corresponding to component carrier 2 → reporting configuration 3 corresponding to component carrier 2 → reporting configuration 4 corresponding to component carrier 2.

[0359] As known from the foregoing, the PUCCH resource can be associated with the component carrier, that is, the PUCCH resource unit can be associated with the component carrier. In some implementations, the ordering priority of the PUCCH resource unit can be associated with the index priority of the component carrier.

[0360] According to the above example #1-2 and priority principle #1-2, the correspondence between the PUCCH resource unit and the component carrier is established, assuming that the values of the two initial cyclic shifts are 3 and 6 respectively, and the indexes of the 8 component carriers are 1-8 respectively, there is the following correspondence.

[0361] In the two PUCCH resource units at the first frequency domain position and the first time domain position, the PUCCH resource unit with an initial cyclic shift of 3 is associated with the component carrier with an index of 1, and the PUCCH resource unit with an initial cyclic shift of 6 is associated with the component carrier with an index of 2.

[0362] In the two PUCCH resource units at the second frequency domain position and the first time domain position, the PUCCH resource unit with an initial cyclic shift of 3 is associated with the component carrier with an index of 3, and the PUCCH resource unit with an initial cyclic shift of 6 is associated with the component carrier with an index of 4.

[0363] In the two PUCCH resource units at the first frequency domain position and the second time domain position, the PUCCH resource unit with an initial cyclic shift of 3 is associated with the component carrier with an index of 5, and the PUCCH resource unit with an initial cyclic shift of 6 is associated with the component carrier with an index of 6.

[0364] The PUCCH resource unit with initial cyclic shift of 3 is associated with the component carrier with index of 7, and the PUCCH resource unit with initial cyclic shift of 6 is associated with the component carrier with index of 8.

[0365] According to the aforementioned examples #1-3 and the priority principle #1-4, the correspondence between the PUCCH resource units and the component carriers is established. Assuming that the values of the two initial cyclic shifts are 3 and 6 respectively, the indexes of the 16 component carriers are 1-16 respectively, and the indexes of the two orthogonal cover codes are 1 and 2 respectively, the correspondence is as follows.

[0366] The PUCCH resource unit with initial cyclic shift of 3 and the orthogonal cover code with index of 1 is associated with the component carrier with index of 1, the PUCCH resource unit with initial cyclic shift of 3 and the orthogonal cover code with index of 2 is associated with the component carrier with index of 2, the PUCCH resource unit with initial cyclic shift of 6 and the orthogonal cover code with index of 1 is associated with the component carrier with index of 3, and the PUCCH resource unit with initial cyclic shift of 6 and the orthogonal cover code with index of 2 is associated with the component carrier with index of 4.

[0367] The PUCCH resource unit with initial cyclic shift of 3 and the orthogonal cover code with index of 1 is associated with the component carrier with index of 5, the PUCCH resource unit with initial cyclic shift of 3 and the orthogonal cover code with index of 2 is associated with the component carrier with index of 6, the PUCCH resource unit with initial cyclic shift of 6 and the orthogonal cover code with index of 1 is associated with the component carrier with index of 7, and the PUCCH resource unit with initial cyclic shift of 6 and the orthogonal cover code with index of 2 is associated with the component carrier with index of 8.

[0368] The PUCCH resource unit with initial cyclic shift of 3 and the orthogonal cover code with index of 1 is associated with the component carrier with index of 9, the PUCCH resource unit with initial cyclic shift of 3 and the orthogonal cover code with index of 2 is associated with the component carrier with index of 10, the PUCCH resource unit with initial cyclic shift of 6 and the orthogonal cover code with index of 1 is associated with the component carrier with index of 11, and the PUCCH resource unit with initial cyclic shift of 6 and the orthogonal cover code with index of 2 is associated with the component carrier with index of 12.

[0369] The PUCCH resource unit with an initial cyclic shift of 3 and an index of 1 of the orthogonal cover code is associated with the component carrier with an index of 13, the PUCCH resource unit with an initial cyclic shift of 3 and an index of 2 of the orthogonal cover code is associated with the component carrier with an index of 14, the PUCCH resource unit with an initial cyclic shift of 6 and an index of 1 of the orthogonal cover code is associated with the component carrier with an index of 15, and the PUCCH resource unit with an initial cyclic shift of 6 and an index of 2 of the orthogonal cover code is associated with the component carrier with an index of 16.

[0370] In some implementations, the number of PUCCH resource units can be greater than or equal to the number of component carriers. If the number of PUCCH resource units is greater than the number of component carriers, after the association between the PUCCH resource units and the component carriers is established, the remaining PUCCH resource units are not associated with the component carriers.

[0371] For example, according to the above example #1-2 and the priority principle #1-2, assuming that the network device configures 2 cyclic shifts, 2 numbers of frequency division multiplexing, 3 numbers of time division multiplexing, and 8 component carriers for the terminal device, after the association between the PUCCH resource units and the component carriers is established, the PUCCH resource unit corresponding to the third time domain position is not associated with the component carriers.

[0372] In some implementations, the index ordering priority of the report configuration is determined by a priority value associated with the report configuration. If the priority value of a first CSI report is lower than the priority value of a second CSI report, it is considered that the first CSI report is prior to the second CSI report or the report configuration index of the first CSI report is smaller. The priority value is related to at least one of the transmission mode (such as periodic, semi-persistent, or aperiodic) of the CSI report, the channel type carrying the CSI report, the report content carried, the component carrier index, and the report configuration index in a component carrier. For example, the priority value can be determined according to the following formula: P(y, k, c, s) = 2 · N cells · M s · y + N cells · M s · k + M s · c + s

[0373] wherein, for aperiodic CSI reporting transmitted on PUSCH, y = 0; for semi-persistent CSI reporting transmitted on PUSCH, y = 1; for semi-persistent CSI reporting transmitted on PUCCH, y = 2; and for periodic CSI reporting transmitted on PUCCH, y = 3; for CSI reporting carrying L1-RSRP or L1-SINR, k = 0; and for CSI reporting not carrying L1-RSRP or L1-SINR, k = 1; c is a component carrier index, N cells is the maximum number of component carriers; s is a reporting configuration index within a component carrier, M s is the maximum number of reporting configurations within a component carrier.

[0374] In some implementations, for the transmission mode of Mode Two, the network device can configure the terminal device with multiple PUCCH resource units and multiple second channel resources, and the multiple PUCCH resource units have a corresponding relationship with the multiple second channel resources. For example, the terminal device determines a PUCCH resource unit based on a certain trigger event, and then transmits the first channel (i.e., transmits the first channel by using the PUCCH resource unit), in addition, the terminal device can also determine the second channel resource according to the PUCCH resource unit, and transmit the second channel by using the second channel resource.

[0375] Examples One to Three in the foregoing describe a scheme of indicating the type of the trigger event to the network device through the first channel, and Examples Four to Six in the following describe a scheme of indicating the type of the trigger event to the network device through the second channel. Examples Four to Six are different from Examples One to Three in the foregoing in that the terminal device only notifies the occurrence of the event on the first channel, and no longer notifies the type of the trigger event.

[0376] Example Four

[0377] The network device can pre-configure the terminal device with multiple second channels, and the terminal device selects one of the second channels for transmitting the CSI report according to the reporting configuration corresponding to the CSI report. This mode can be applied to the transmission mode of Mode Two described above.

[0378] In some implementations, the selection of the second channel is associated with the overhead required for transmitting the CSI report, and different second channels can carry different maximum numbers of uplink control information (UCI) bits. The second channel can be pre-configured by the network device. The terminal device can select a second channel for transmitting the CSI report according to the overhead required for transmitting the CSI report.

[0379] For example, if the feedback overhead required by the CSI report is less than or equal to a number of bits, the terminal device can select a second channel A; if the feedback overhead required by the CSI report is greater than or equal to a number of bits and less than or equal to a number of bits, the terminal device can select a second channel B; and if the feedback overhead required by the CSI report is greater than or equal to a number of bits, the terminal device can select a second channel C.

[0380] Example Five

[0381] The terminal device indicates the type of the triggering event to the network device through the second channel, which can include that the terminal device indicates the type of the triggering event to the network device through an association between the second channel resource and the report configuration.

[0382] The network device can pre-configure multiple second channels for the terminal device, and the terminal device selects one of the second channels for transmitting the CSI report according to the report configuration corresponding to the CSI report. This mode can be applied to the transmission mode of Mode Two described above.

[0383] The terminal device can select a second channel for transmitting the CSI report according to an index of the report configuration corresponding to the CSI report. For example, it is assumed that the network device configures multiple second channel resources for the terminal device, and one second channel resource can be associated with one or more report configurations. The network device can clearly know the report configuration corresponding to the second channel by receiving a specific second channel, and further clearly know the event type corresponding to the report configuration.

[0384] If the second channel is a PUCCH, the PUCCH can be a PUCCH resource directly configured by the network device for the terminal device, or the PUCCH can be a PUCCH resource unit as described above. The terminal device can determine multiple PUCCH resource units according to the second information, as shown in FIG. 11, the second information including one or more of the following: a time domain position of a PUCCH reference resource, a frequency domain position of the PUCCH reference resource, a cyclic shift, an orthogonal cover code, a number of frequency division multiplexing, a frequency division interval, a number of time division multiplexing, and a time division interval. The second information is similar to the first information, and the related description of the second information can be referred to the related description of the first information described above.

[0385] If the second channel is PUSCH, the PUSCH can be directly configured by the network device for the terminal device, or the PUSCH is a PUSCH resource unit. The terminal device can determine a plurality of PUSCH resource units according to third information, as shown in FIG. 12, the third information includes one or more of the following: a time domain position of a PUSCH reference resource, a frequency domain position of the PUSCH reference resource, a demodulation reference signal (DMRS) port number, a DMRS sequence, a frequency division multiplexing number, a frequency division interval, a time division multiplexing number, and a time division interval. The above third information can be configured by the network device to the terminal device.

[0386] For the DMRS port number, different PUSCH resource units can use different DMRS port numbers, which is beneficial to improve the accuracy of channel estimation.

[0387] For the DMRS sequence, different DMRS sequences can randomize the interference between terminal devices.

[0388] The above PUCCH resource unit and PUSCH resource unit can be collectively referred to as a second channel resource unit. One second channel resource unit can be associated with one or more report configurations. The above association relationship is related to the ordering priority of the second channel resource unit and the index priority of the report configuration.

[0389] If the second channel is PUCCH, the ordering priority of the PUCCH resource unit, the index priority of the report configuration, and the association relationship between the PUCCH resource unit and the report configuration can refer to the description in the foregoing, and for the sake of brevity, will not be repeated here.

[0390] For the case where the second channel is PUSCH, the following examples illustrate the way the terminal device determines the PUSCH resource unit.

[0391] Example #2-1, assuming that the network device configures the terminal device with the following parameters: time-frequency domain position of a PUSCH reference resource, and the number of DMRS port numbers is 4, then the terminal device can determine 4 PUSCH resource units. The DMRS port numbers of different PUSCH resource units are different, but all the PUSCH resource units have the same time-frequency domain position as the PUSCH reference resource.

[0392] Example #2-2, assuming the network device configures the terminal device with the following parameters: time-frequency domain location of PUSCH reference resource, number of DMRS port number is 2, number of frequency division multiplexing is 2, number of time division multiplexing is 2, the terminal device can determine 8 PUSCH resource units. One or more of the following parameters of different PUSCH resource units are different: DMRS port number, time domain location and frequency domain location.

[0393] Example #2-3, assuming the network device configures the terminal device with the following parameters: time-frequency domain location of PUSCH reference resource, number of DMRS port number is 2, number of DMRS sequence is 2, number of frequency division multiplexing is 2, number of time division multiplexing is 2, the terminal device can determine a total of 16 PUSCH resource units. One or more of the following parameters of different PUSCH resource units are different: DMRS port number, DMRS sequence, time domain location and frequency domain location.

[0394] The priority principle of the PUSCH resource unit can include one or more of the following priority principles. The following priority principles are introduced. It should be noted that the following priority principles are only examples and should not limit the embodiments of the present application. The embodiments of the present application can also include other priority principles.

[0395] Priority principle #2-1: sort in the order of DMRS port number, frequency domain location, and time domain location.

[0396] First, sort the multiple PUSCH resource units in the same time domain location and frequency domain location in ascending order of the size of the DMRS port number related index; then, sort in ascending order of the size of the frequency domain location related index; finally, sort in ascending order of the size of the time domain location related index.

[0397] Priority principle #2-2: sort in the order of frequency domain location, DMRS port number, and time domain location.

[0398] First, sort in ascending order of the size of the frequency domain location related index; then, sort the multiple PUSCH resource units in the same time domain location and frequency domain location in ascending order of the size of the DMRS port number related index; finally, sort in ascending order of the size of the time domain location related index.

[0399] Priority principle #2-3: sort in the order of DMRS port number, DMRS sequence, frequency domain location, and time domain location.

[0400] First, the multiple PUSCH resource units in the same time domain position and frequency domain position are sorted in ascending order of the size of the DMRS port number related index, and then sorted in ascending order of the DMRS sequence related index; then, sorted in ascending order of the size of the frequency domain position related index; finally, sorted in ascending order of the size of the time domain position related index.

[0401] Priority principle #2-4: sorted in the order of frequency domain position, DMRS port number, DMRS sequence, and time domain position.

[0402] First, sorted in ascending order of the size of the frequency domain position related index; then, the multiple PUSCH resource units in the same time domain position and frequency domain position are sorted in ascending order of the size of the DMRS port number related index, and then sorted in ascending order of the DMRS sequence related index; finally, sorted in ascending order of the size of the time domain position related index.

[0403] Priority principle #2-5: sorted in the order of time domain position, DMRS port number, DMRS sequence, and frequency domain position.

[0404] First, sorted in ascending order of the size of the time domain position related index; then, the multiple PUSCH resource units in the same time domain position and frequency domain position are sorted in ascending order of the size of the DMRS port number related index, and then sorted in ascending order of the DMRS sequence related index; finally, sorted in ascending order of the size of the frequency domain position related index.

[0405] Priority principle #2-6: sorted in the order of time domain position, DMRS sequence, DMRS port number, and frequency domain position.

[0406] First, sorted in ascending order of the size of the time domain position related index; then, the multiple PUSCH resource units in the same time domain position and frequency domain position are sorted in ascending order of the DMRS sequence related index, and then sorted in ascending order of the size of the DMRS port number related index; finally, sorted in ascending order of the size of the frequency domain position related index.

[0407] Priority principle #2-7: sorted in the order of frequency domain position, DMRS sequence, DMRS port number, and time domain position.

[0408] First, the PUSCH resource units are sorted in ascending order of the size of the time domain location related index; next, the PUSCH resource units in the same time domain location and frequency domain location are sorted in ascending order of the DMRS sequence related index, and then sorted in ascending order of the size of the DMRS port number related index; finally, the PUSCH resource units are sorted in ascending order of the size of the frequency domain location related index.

[0409] Priority principle #2-8: sorting in the order of time domain location, DMRS port number, and frequency domain location.

[0410] First, the PUSCH resource units are sorted in ascending order of the size of the time domain location related index; next, the PUSCH resource units in the same time domain location and frequency domain location are sorted in ascending order of the size of the DMRS port number related index; finally, the PUSCH resource units are sorted in ascending order of the size of the frequency domain location related index.

[0411] According to the aforementioned example #2-2 and priority principle #2-2, the correspondence between the PUSCH resource units and the report configurations is established. Assuming that the values of the two DMRS port numbers are 3 and 6 respectively, and the indexes of the 8 report configurations are 1-8 respectively, the following correspondence is obtained.

[0412] In the two PUSCH resource units in the first frequency domain location and the first time domain location, the PUSCH resource unit with DMRS port number 3 is associated with the report configuration with index 1, and the PUSCH resource unit with DMRS port number 6 is associated with the report configuration with index 2.

[0413] In the two PUSCH resource units in the second frequency domain location and the first time domain location, the PUSCH resource unit with DMRS port number 3 is associated with the report configuration with index 3, and the PUSCH resource unit with DMRS port number 6 is associated with the report configuration with index 4.

[0414] In the two PUSCH resource units in the first frequency domain location and the second time domain location, the PUSCH resource unit with DMRS port number 3 is associated with the report configuration with index 5, and the PUSCH resource unit with DMRS port number 6 is associated with the report configuration with index 6.

[0415] In the two PUSCH resource units in the second frequency domain location and the second time domain location, the PUSCH resource unit with DMRS port number 3 is associated with the report configuration with index 7, and the PUSCH resource unit with DMRS port number 6 is associated with the report configuration with index 8.

[0416] According to the preceding examples #2-3 and the priority principle #2-4, the correspondence between the PUSCH resource units and the reporting configurations is established. Assuming that the values of the two DMRS port numbers are 3 and 6 respectively, the indices of the 16 reporting configurations are 1~16 respectively, and the indices of the two DMRS sequences are 1 and 2 respectively, there are the following correspondence.

[0417] In the 4 PUSCH resource units at the first frequency domain position and the first time domain position, the PUSCH resource unit with the DMRS port number of 3 and the index of the DMRS sequence of 1 is associated with the reporting configuration with the index of 1, the PUSCH resource unit with the DMRS port number of 3 and the index of the DMRS sequence of 2 is associated with the reporting configuration with the index of 2, the PUSCH resource unit with the DMRS port number of 6 and the index of the DMRS sequence of 1 is associated with the reporting configuration with the index of 3, and the PUSCH resource unit with the DMRS port number of 6 and the index of the DMRS sequence of 2 is associated with the reporting configuration with the index of 4.

[0418] In the 4 PUSCH resource units at the second frequency domain position and the first time domain position, the PUSCH resource unit with the DMRS port number of 3 and the index of the DMRS sequence of 1 is associated with the reporting configuration with the index of 5, the PUSCH resource unit with the DMRS port number of 3 and the index of the DMRS sequence of 2 is associated with the reporting configuration with the index of 6, the PUSCH resource unit with the DMRS port number of 6 and the index of the DMRS sequence of 1 is associated with the reporting configuration with the index of 7, and the PUSCH resource unit with the DMRS port number of 6 and the index of the DMRS sequence of 2 is associated with the reporting configuration with the index of 8.

[0419] In the 4 PUSCH resource units at the first frequency domain position and the second time domain position, the PUSCH resource unit with the DMRS port number of 3 and the index of the DMRS sequence of 1 is associated with the reporting configuration with the index of 9, the PUSCH resource unit with the DMRS port number of 3 and the index of the DMRS sequence of 2 is associated with the reporting configuration with the index of 10, the PUSCH resource unit with the DMRS port number of 6 and the index of the DMRS sequence of 1 is associated with the reporting configuration with the index of 11, and the PUSCH resource unit with the DMRS port number of 6 and the index of the DMRS sequence of 2 is associated with the reporting configuration with the index of 12.

[0420] The PUSCH resource unit with DMRS port number 3 and DMRS sequence index 1 at the second frequency domain location and the second time domain location is associated with the reporting configuration with index 13, the PUSCH resource unit with DMRS port number 3 and DMRS sequence index 2 is associated with the reporting configuration with index 14, the PUSCH resource unit with DMRS port number 6 and DMRS sequence index 1 is associated with the reporting configuration with index 15, and the PUSCH resource unit with DMRS port number 6 and DMRS sequence index 2 is associated with the reporting configuration with index 16.

[0421] The second channel is associated with the reporting configuration, which can mean that the second channel is associated with the trigger state. As described above, the second channel resource can be a second channel resource unit, and the second channel being associated with the trigger state can mean that the second channel resource unit is associated with the trigger state. The second channel resource unit can be the PUCCH resource unit or the PUSCH resource unit described above.

[0422] In some implementations, the number of second channel resource units can be greater than or equal to the number of trigger states. If the number of second channel resource units is greater than the number of trigger states, after establishing the association between the second channel resource units and the trigger states in the manner described above, the remaining second channel resource units are not associated with the trigger states.

[0423] In some implementations, for a CA scenario, the index ordering priority of the reporting configuration is related to the index of the component carrier and the index of the reporting configuration. For example, the reporting configuration corresponding to a component carrier with a smaller index has a higher ordering priority; when the component carrier indexes are the same, the CSI report corresponding to the reporting configuration with a smaller index has a higher ordering priority.

[0424] For example, assume that the network device configures the terminal device with reporting configurations of two component carriers, the two component carriers are component carrier 1 and component carrier 2, and the terminal device is configured with four reporting configurations, then the ordering priority of the reporting configurations from high to low is: reporting configuration 1 corresponding to component carrier 1→ reporting configuration 2 corresponding to component carrier 1→ reporting configuration 3 corresponding to component carrier 1→ reporting configuration 4 corresponding to component carrier 1→ reporting configuration 1 corresponding to component carrier 2→ reporting configuration 2 corresponding to component carrier 2→ reporting configuration 3 corresponding to component carrier 2→ reporting configuration 4 corresponding to component carrier 2.

[0425] As described above, the second channel resource can be associated with the component carrier, that is, the second channel resource unit can be associated with the component carrier. In some implementations, the ordering priority of the second channel resource unit can be associated with the index priority of the component carrier.

[0426] According to the aforementioned example #2-2 and the priority principle #2-2, the correspondence between the second channel resource units and the component carriers is established, assuming that the values of the two DMRS port numbers are 3 and 6 respectively, and the indexes of the 8 component carriers are 1-8 respectively, then the correspondence is as follows.

[0427] In the two second channel resource units at the first frequency domain position and the first time domain position, the second channel resource unit with the DMRS port number 3 is associated with the component carrier with the index 1, and the second channel resource unit with the DMRS port number 6 is associated with the component carrier with the index 2.

[0428] In the two second channel resource units at the second frequency domain position and the first time domain position, the second channel resource unit with the DMRS port number 3 is associated with the component carrier with the index 3, and the second channel resource unit with the DMRS port number 6 is associated with the component carrier with the index 4.

[0429] In the two second channel resource units at the first frequency domain position and the second time domain position, the second channel resource unit with the DMRS port number 3 is associated with the component carrier with the index 5, and the second channel resource unit with the DMRS port number 6 is associated with the component carrier with the index 6.

[0430] In the two second channel resource units at the second frequency domain position and the second time domain position, the second channel resource unit with the DMRS port number 3 is associated with the component carrier with the index 7, and the second channel resource unit with the DMRS port number 6 is associated with the component carrier with the index 8.

[0431] According to the aforementioned example #2-3 and the priority principle #2-4, the correspondence between the second channel resource units and the component carriers is established. Assuming that the values of the two DMRS port numbers are 3 and 6 respectively, the indexes of the 16 component carriers are 1-16 respectively, and the indexes of the two DMRS sequences are 1 and 2 respectively, then the correspondence is as follows.

[0432] In the four second channel resource units at the first frequency domain position and the first time domain position, the second channel resource unit with the DMRS port number 3 and the index of the DMRS sequence 1 is associated with the component carrier with the index 1, the second channel resource unit with the DMRS port number 3 and the index of the DMRS sequence 2 is associated with the component carrier with the index 2, the second channel resource unit with the DMRS port number 6 and the index of the DMRS sequence 1 is associated with the component carrier with the index 3, and the second channel resource unit with the DMRS port number 6 and the index of the DMRS sequence 2 is associated with the component carrier with the index 4.

[0433] The second channel resource unit with the DMRS port number 3 and the DMRS sequence index 1 is associated with the component carrier with the index 9, the second channel resource unit with the DMRS port number 3 and the DMRS sequence index 2 is associated with the component carrier with the index 10, the second channel resource unit with the DMRS port number 6 and the DMRS sequence index 1 is associated with the component carrier with the index 11, and the second channel resource unit with the DMRS port number 6 and the DMRS sequence index 2 is associated with the component carrier with the index 12.

[0434] The second channel resource unit with the DMRS port number 3 and the DMRS sequence index 1 is associated with the component carrier with the index 9, the second channel resource unit with the DMRS port number 3 and the DMRS sequence index 2 is associated with the component carrier with the index 10, the second channel resource unit with the DMRS port number 6 and the DMRS sequence index 1 is associated with the component carrier with the index 11, and the second channel resource unit with the DMRS port number 6 and the DMRS sequence index 2 is associated with the component carrier with the index 12.

[0435] The second channel resource unit with the DMRS port number 3 and the DMRS sequence index 1 is associated with the component carrier with the index 9, the second channel resource unit with the DMRS port number 3 and the DMRS sequence index 2 is associated with the component carrier with the index 10, the second channel resource unit with the DMRS port number 6 and the DMRS sequence index 1 is associated with the component carrier with the index 11, and the second channel resource unit with the DMRS port number 6 and the DMRS sequence index 2 is associated with the component carrier with the index 12.

[0436] In some implementations, the number of the second channel resource units can be greater than or equal to the number of the component carriers. If the number of the second channel resource units is greater than the number of the component carriers, after the association between the second channel resource units and the component carriers is established, the remaining second channel resource units are not associated with the component carriers.

[0437] For example, according to the above example #2-2 and the priority principle #2-2, if the network device configures 2 DMRS port numbers, 2 frequency division multiplexing numbers, 3 time division multiplexing numbers, and 8 component carriers for the terminal device, after the association between the second channel resource units and the component carriers is established, the second channel resource unit corresponding to the third time domain position is not associated with the component carriers.

[0438] In some implementations, the index of a reporting configuration is prioritized according to a priority value associated with the reporting configuration. If a first CSI report has a priority value lower than a second CSI report, the first CSI report is considered to be prioritized over the second CSI report or the first CSI report has a smaller index of reporting configuration. The priority value is related to at least one of a transmission mode of the CSI report (e.g., periodic, semi-persistent, or aperiodic), a channel type on which the CSI report is carried, a report content carried, a component carrier index, and an index of reporting configuration within a component carrier. For example, the priority value can be determined according to the following formula: P(y, k, c, s) = 2 · N cells · M s · y + N cells · M s · k + M s · c + s

[0439] where y = 0 for an aperiodic CSI report transmitted on PUSCH, y = 1 for a semi-persistent CSI report transmitted on PUSCH, y = 2 for a semi-persistent CSI report transmitted on PUCCH, and y = 3 for a periodic CSI report transmitted on PUCCH; k = 0 for a CSI report carrying L1-RSRP or L1-SINR, and k = 1 for a CSI report not carrying L1-RSRP or L1-SINR; c is a component carrier index; N cells is a maximum number of component carriers; s is an index of reporting configuration within a component carrier; and M s is a maximum number of reporting configurations within a component carrier.

[0440] Example Six

[0441] In some implementations, a CSI report carried in the second channel can include a first field indicating a type of triggering event corresponding to the CSI report carried in the second channel. In some implementations, since there is a one-to-one correspondence between the type of triggering event and the reporting configuration, the first field can be used to indicate an index of the reporting configuration corresponding to the CSI report carried in the second channel.

[0442] In some implementations, for a CA scenario, a CSI report carried in the second channel includes a second field indicating an index of a component carrier on which the reporting configuration is located. In some scenarios, different component carriers can correspond to the same index of reporting configuration, e.g., component carrier 1 and component carrier 2 both correspond to reporting configuration 1. Thus, by indicating the index of the component carrier through the second field, the network device can determine which component carrier the reporting configuration corresponding to the CSI report carried in the second channel belongs to.

[0443] The first field and / or the second field can be a newly added field in the second channel, or can be a field originally in the CSI report carried by the second channel, and embodiments of the present application do not make specific limitations thereto.

[0444] It should be noted that the above various examples can be used in combination with each other in the absence of conflicts, and embodiments of the present application do not make specific limitations thereto.

[0445] The CSI report in the above examples 1 to 6 can be triggered by one event, or can be triggered by multiple events, and embodiments of the present application do not make specific limitations thereto. If the CSI report is triggered by multiple events, multiple CSI reports can be carried in the second channel.

[0446] The sorting priority of the multiple CSI reports in the second channel can be determined according to the index of the component carrier and / or the index of the report configuration. For example, the CSI report with a smaller component carrier index has a higher priority; when the component carrier indexes are the same, the CSI report with a smaller report configuration index has a higher priority. For example, as described above, the smaller the priority value corresponding to the report configuration, the higher the priority.

[0447] When multiple trigger events occur at the same time, the second channel can not be able to carry all the CSI reports. In this case, the terminal device can determine which CSI reports to carry in the second channel and which CSI reports to discard according to the sorting priority of the CSI reports. The sorting priority can be determined according to the priority value described above, and the report configuration with a smaller priority value has a higher sorting priority.

[0448] For example, it is assumed that the CSI reports corresponding to the multiple trigger events are CSI report 1, CSI report 2 and CSI report 3, the bits occupied by the CSI report 1 are a, the bits occupied by the CSI report 2 are b, and the bits occupied by the CSI report 3 are c. The terminal device determines the sorting priority of the above three CSI reports from high to low according to the sorting priority of the CSI reports: CSI report 1→CSI report 2→CSI report 3. If the maximum bits that the second channel can carry are X, and (a+b) < X < (a+b+c), the terminal device can determine to carry the CSI report 1 and the CSI report 2 in the second channel, and discard the CSI report 3.

[0449] In some implementations, the network device can also configure the terminal device with a maximum code rate that can be used when channel encoding the second channel. The terminal device can determine the maximum number of bits of the CSI report that the second channel can carry according to the maximum code rate, to ensure that the channel encoding of the second channel when carrying the CSI report does not exceed the maximum code rate.

[0450] In some implementations, each CSI report includes the first field and / or the second field, i.e., the first field and / or the second field are part of the CSI report. Further, the first field and / or the second field have a higher priority than other information in the CSI report. For example, assuming that a CSI report includes the first field and / or the second field, one or more indexes of reference signals, and measurement results corresponding to the one or more indexes of reference signals, the priority of the information in the CSI report from high to low is the first field and / or the second field, the one or more indexes of reference signals, and the measurement results corresponding to the one or more indexes of reference signals.

[0451] In some implementations, the CSI report information carried in the second channel is divided into two parts, the first part includes one or more first fields and / or second fields. The overhead of the first part is fixed, for example, the first part always includes N first fields and / or second fields, and the value of N is configured by the network device or predefined; the second part includes M CSI reports (M≤N), and the CSI report includes one or more indexes of reference signals and measurement results corresponding to the one or more indexes of reference signals. The overhead of the second part is determined by the second part. For example, the first part includes 3 (for example, N=3) first fields: assuming N=M, for example, the first first field is used to indicate the reporting configuration index corresponding to the first CSI report in the second part, the second first field is used to indicate the reporting configuration index corresponding to the second CSI report in the second part, and the third first field is used to indicate the reporting configuration index corresponding to the third CSI report in the second part; assuming M=2, for example, the first first field is used to indicate the reporting configuration index corresponding to the first CSI report in the second part, the second first field does not indicate any reporting configuration index (for example, at this time, the second first field can indicate a default state 0), and the third first field is used to indicate the reporting configuration index corresponding to the second CSI report in the second part. In the latter case, the second part only includes two CSI reports, although the second first field does not indicate any reporting configuration index, the second first field indicating a default state still occupies a fixed overhead. Further, to ensure that the network device can correctly decode the two parts of information, the two parts of information need to be respectively channel encoded, i.e., the two parts of information correspond to a cyclic redundancy check (CRC) respectively.

[0452] In some implementations, for the transmission mode of mode one, if the terminal device does not receive the DCI sent by the network device after sending the first channel, the terminal device can repeatedly transmit the first channel until receiving a DCI indicating a reporting configuration or a trigger state associated with the first channel. The maximum number of repeated transmissions is configured by the network device.

[0453] The wireless communication method provided by the embodiment of the present application is described in detail below in combination with FIG. 13. It should be noted that the content below can be combined with the content above, and the content not described in detail below can be referred to the description above.

[0454] The method shown in FIG. 13 is described from the perspective of device interaction. The specific forms and quantities of the devices shown are only examples and should not constitute any limitation on the implementation of the method provided by the present application. The communication method of the embodiment of the present application is described in detail below taking the network device and the terminal device as the execution subject.

[0455] It should be understood that the terminal device in the embodiment of the present application can be the terminal device itself, or a chip, chip system or processor supporting the terminal device to implement the communication method, or a logic module or software capable of implementing all or part of the terminal device. The network device in the embodiment of the present application can be the network device itself, or a chip, chip system or processor supporting the network device to implement the communication method, or a logic module or software capable of implementing all or part of the network device.

[0456] Referring to FIG. 13, in step S1310, if a first trigger event is detected, the terminal device sends a first channel to the network device.

[0457] In some implementations, before step S1310, the terminal device can measure the channel state to obtain a measurement result. The measurement result can include RSRP and / or SINR. The terminal device can detect the first trigger event based on the measurement result, or in other words, the terminal device can determine whether the first trigger event occurs based on the measurement result. If the terminal device detects the first trigger event based on the measurement result, the terminal device can send the first channel to the network device.

[0458] In some implementations, the measurement of the terminal device on the channel state can include that the terminal device measures a reference signal resource. The reference signal resource can be configured by the network device to the terminal device. The reference signal resource can include, for example, SSB resource and / or CSI-RS resource.

[0459] As described above, the reference signal resource can be understood as a reference signal, a beam, etc. The reference signal can include, for example, SSB and / or CSI-RS.

[0460] In some implementations, the first trigger event can include one trigger event or multiple trigger events. The trigger event in the embodiment of the present application can be any one of the trigger events described above.

[0461] In some implementations, the first channel can be either PRACH or PUCCH. The PUCCH can be the PUCCH corresponding to the scheduling request. The PUCCH format can be PUCCH format 1 or PUCCH format 2. The PUCCH can occupy one or more bits.

[0462] In some implementations, the first channel can be used to indicate that a triggering event has occurred or that a triggering event has been detected; or the first channel can be used to notify the network device that a triggering event has occurred.

[0463] In some implementations, the first channel can be used to request or notify the second channel. As an example, for the sending mode of Method 1 above, the first channel can be used to request the second channel. For instance, the first channel can be used by the terminal device to request resources for the second channel from the network device. After receiving the first channel, the network device can schedule resources for the second channel for the terminal device. Alternatively, the network device can schedule resources for the second channel for the terminal device based on the first channel. As another example, for the sending mode of Method 2 above, the first channel can be used to notify the second channel. For instance, the first channel can be used by the terminal device to notify the network device to receive the second channel, or the first channel can be used by the terminal device to notify the network device that a second channel will be sent subsequently. After receiving the first channel, the network device can receive the second channel. Alternatively, the network device can receive the second channel based on the first channel.

[0464] In some implementations, if the first channel is used to request the second channel, the network device, upon receiving the first channel, can send a DCI to the terminal device, which indicates the second channel. In some implementations, the DCI may include information related to the first triggering event.

[0465] In some implementations, the terminal device may not receive the DCI sent by the network device. In this case, the terminal device can repeatedly transmit the first channel until it receives a DCI or the maximum number of retransmissions is reached. If the terminal device does not receive a DCI, it does not need to send a second channel to the network device.

[0466] In some implementations, the terminal device can send a second channel to the network device based on the measurement results. The second channel can be used to carry a CSI report based on the first triggering event, or in other words, the second channel can be used to carry a CSI report corresponding to the first triggering event, or the second channel can be used to carry a CSI report generated based on the first triggering event.

[0467] In some implementations, the second channel can be either PUCCH or PUSCH. PUCCH can be a pre-configured PUCCH, and PUSCH can be CG-PUSCH.

[0468] In some implementations, the first channel and / or the second channel can be used to indicate relevant information about the first triggering event. For example, the first channel can be used to indicate relevant information about the first triggering event. Similarly, the second channel can be used to indicate relevant information about the first triggering event. In some implementations, the relevant information about the first triggering event can refer to the type of the first triggering event.

[0469] By indicating the relevant information of the first triggering event, the network device can clearly identify which triggering event caused the CSI report in the second channel, which helps ensure the correct transmission of the CSI report. For the first transmission mode, the network device can indicate the appropriate second channel to the terminal device based on the relevant information of the first triggering event. For the second transmission mode, if the network device has multiple pre-configured second channels, it can receive the CSI report on a specific second channel based on the relevant information of the first triggering event, thereby reducing the complexity of blind detection. Alternatively, if the network device has only configured one second channel, it can use the correct decoding method to decode the second channel, improving the success rate of receiving the CSI report.

[0470] In some implementations, the information related to the first triggering event can refer to the type of the first triggering event; that is, the first channel and / or the second channel can be used to indicate the type of the first triggering event.

[0471] This application does not specifically limit the information related to the first triggering event in its embodiments. As an example, the information related to the first triggering event may include the first report configuration (or information of the first report configuration) corresponding to the first triggering event. Since there is a one-to-one correspondence between the report configuration and the triggering event, the type of the triggering event can be indicated by indicating the report configuration.

[0472] As another example, information related to the first triggering event may include the triggering state corresponding to the first triggering event. Since there is a correlation between the triggering state and the reporting configuration, and a one-to-one correspondence between the reporting configuration and the type of triggering event, the type of triggering event can be indicated by indicating the triggering state.

[0473] As another example, information related to the first triggering event may include the component carrier corresponding to the first triggering event. Since there is an association between the component carrier and the reporting configuration, and a one-to-one correspondence between the reporting configuration and the type of triggering event, the type of triggering event can be indicated by indicating the component carrier.

[0474] The following describes the solution of this application embodiment using the relevant information of the first triggering event, including the report configuration corresponding to the first triggering event, as an example.

[0475] In some implementations, the first report configuration may include one report configuration or multiple report configurations.

[0476] In some implementations, the first channel and / or the second channel may correspond to the first report configuration, or in other words, the first channel and / or the second channel may be associated with the first report configuration. For example, the first channel may correspond to the first report configuration. After receiving the first channel, the network device can determine that the CSI report in the second channel is related to the first report configuration based on the correspondence between the first channel and the first report configuration, and further determine the type of the triggering event based on the first report configuration. Similarly, the second channel may correspond to the first report configuration. After receiving the second channel, the network device can determine that the CSI report in the second channel is related to the first report configuration based on the correspondence between the second channel and the first report configuration, and further determine the type of the triggering event based on the first report configuration.

[0477] In some implementations, the correspondence between the first channel and / or the second channel and the first report configuration may include: the correspondence between the first resource and the first report configuration. The correspondence between the first resource and the first report configuration may mean that the first resource and the first report configuration are associated. The association between the first resource and the first report configuration can be found in the description above, and for the sake of brevity, will not be repeated here.

[0478] The first resource may include one or more of the following: transmission resources for a first channel, resources associated with the transmission resources of the first channel, and transmission resources for a second channel. The transmission resources for the first channel may, for example, include PRACH resources and / or PUCCH resources. Resources associated with the transmission resources of the first channel may, for example, include scheduling request resources. The transmission resources for the second channel may, for example, include PUCCH resources and / or PUSCH resources.

[0479] In some implementations, the transmission resource of the first channel can be a PUCCH resource associated with a scheduling request resource, or in other words, the transmission resource of the first channel can be a PUCCH resource indicated by a scheduling request resource identifier (ID). In some implementations, a scheduling request resource can be associated with one or more PUCCH resources. Associating a scheduling request resource with multiple PUCCH resources allows for the indication of more types of triggering events to the network device without increasing the number of scheduling request resources.

[0480] In some implementations, the correspondence between the first resource and the first report configuration can refer to the correspondence between the index of the first resource and the index of the first report configuration. For example, if the first resource is a PUCCH resource, its index can correspond to the index of the first report configuration. Similarly, if the first resource is a PUSCH resource, its index can correspond to the index of the first report configuration. The relationships between the PUCCH resource index and the report configuration index, as well as the relationships between the PUSCH resource index and the report configuration index, can be found in the description above and will not be repeated here for brevity.

[0481] In some implementations, the correspondence between the first resource and the first report configuration may include: the first resource corresponding to one or more trigger states, which are used to indicate the first report configuration. The correspondence between the first resource and one or more trigger states may mean that the first resource and one or more trigger states are associated. The association between the first resource and the trigger states can be found in the description above, and for the sake of brevity, it will not be repeated here.

[0482] In this embodiment, the trigger event type can be configured at the trigger state level, which reduces the number of corresponding relationships that need to be configured and lowers the implementation complexity. Furthermore, if the first resource corresponds to multiple trigger states, more types of trigger events can be indicated with fewer resources, reducing the number of first resources that need to be configured and improving resource utilization.

[0483] In some implementations, the correspondence between the first resource and one or more trigger states can mean that the index of the first resource corresponds to the index of one or more trigger states.

[0484] In some implementations, the correspondence between the first resource and the first report configuration may include: the first resource corresponding to the report configuration of one or more component carriers, where the report configuration of the one or more component carriers includes the first report configuration. The correspondence between the first resource and the report configuration of one or more component carriers may mean that the first resource is associated with one or more component carriers. The association between the first resource and one or more component carriers can be found in the description above, and for brevity, will not be repeated here.

[0485] In this embodiment, the trigger event type can be granular at the component carrier level, which reduces the number of correspondences that need to be configured and lowers the implementation complexity. Furthermore, if the first resource corresponds to multiple component carriers, more trigger event types can be indicated with fewer resources, reducing the number of first resources that need to be configured and improving resource utilization.

[0486] The reporting configuration corresponding to the first resource and one or more component carriers may include: the index of the first resource corresponds to the index of one or more component carriers.

[0487] The PUCCH resources mentioned above can be directly configured by network devices or determined by terminal devices based on certain parameters. For example, PUCCH resources can be determined based on one or more of the following parameters: the time-domain position of the PUCCH reference resource, the frequency-domain position of the PUCCH reference resource, cyclic shift, orthogonal overlay code, the number of frequency division multiplexing (FDM) units, the frequency division interval, the number of time division multiplexing (TDM) units, and the time division interval. PUCCH resources determined in this way can also be called PUCCH resource units. For details on how to determine PUCCH resources, please refer to the description above; for brevity, they will not be repeated here.

[0488] In this embodiment, the PUCCH resources can be determined by the terminal device based on the aforementioned parameters. This reduces the number of PUCCH resources configured by the network device for the terminal device, thereby lowering signaling overhead. Furthermore, the PUCCH resources determined in this way are more concentrated, facilitating resource reservation by the network device.

[0489] If the PUCCH resource is determined based on the parameters mentioned above, then the index of the PUCCH resource can be related to its sorting priority. The sorting priority of the PUCCH resource can be determined based on one or more of the following parameters: the time-domain position of the PUCCH resource, the frequency-domain position of the PUCCH resource, the cyclic shift used in the PUCCH sequence, and the orthogonal covering code used in the PUCCH sequence. Specific sorting priorities are described above and will not be repeated here for brevity.

[0490] The PUSCH resources mentioned above can be directly configured by network devices, or they can be determined by terminal devices based on certain parameters. For example, PUSCH resources can be determined based on one or more of the following parameters: the time-domain location of the PUSCH reference resource, the frequency-domain location of the PUSCH reference resource, the DMRS port number, the DMRS sequence, the number of frequency division multiplexing (FDM) units, the frequency division interval, the number of time division multiplexing (TDM) units, and the time division interval. For details on how to determine PUSCH resources, please refer to the description above; for brevity, it will not be repeated here.

[0491] In this embodiment, the PUSCH resources can be determined by the terminal device based on the aforementioned parameters. This reduces the number of PUSCH resources configured by the network device for the terminal device, thereby lowering signaling overhead. Furthermore, the PUSCH resources determined in this way are more concentrated, facilitating resource reservation by the network device.

[0492] If the PUSCH resource is determined based on the parameters mentioned above, the index of the PUSCH resource is related to its sorting priority. The sorting priority of the PUSCH resource can be determined based on one or more of the following parameters: the time-domain location of the PUSCH resource, the frequency-domain location of the PUSCH resource, the DMRS port number used by the PUSCH reference resource, and the DMRS sequence used by the PUSCH reference resource. Specific sorting priorities are described above and will not be repeated here for brevity.

[0493] In some implementations, the second channel may include first indication information, which can be used to indicate relevant information about the first triggering event. For example, if the second channel is a PUCCH, the PUCCH may carry the first indication information. Similarly, if the second channel is a PUSCH, the PUSCH may carry the first indication information.

[0494] In some implementations, the domain containing the first indication information is located in the CSI report.

[0495] In some implementations, the first indication information may be carried in a first field and / or a second field of the CSI report. The first field is used to indicate information about the first report configuration corresponding to the first triggering event, and the second field is used to indicate information about the component carrier to which the first report configuration belongs.

[0496] In some implementations, the information from the first report configuration and / or the component carrier information can be used to indicate relevant information about the first triggering event. For example, in a single-carrier scenario, the information from the first report configuration can indicate which report configuration corresponds to the first triggering event. Similarly, in a CA scenario, the information from the component carrier can indicate which component carrier corresponds to the first triggering event. Furthermore, in a CA scenario, the information from the first report configuration and the component carrier information can indicate which report configuration within which component carrier corresponds to the first triggering event.

[0497] In some implementations, the second channel is related to the overhead required to transmit the CSI report. In other implementations, the terminal device can select the second channel based on the overhead required for transmitting the CSI report. The correspondence between the second channel and the overhead required for transmitting the CSI report can be found in the description above, and will not be repeated here for the sake of brevity.

[0498] In some implementations, the first triggering event may include multiple triggering events. If the second channel cannot carry all the reports in the multiple CSI reports corresponding to the multiple triggering events, the terminal device can determine the CSI reports carried in the second channel based on the priority of the multiple CSI reports. Alternatively, the terminal device can determine which CSI reports to discard based on the priority of the multiple CSI reports.

[0499] In some implementations, the priority of CSI reports can be determined based on one or more of the following information: the transmission method of the CSI report, the channel type carrying the CSI report, the index of the report configuration corresponding to the CSI report, and the index of the component carrier corresponding to the channel state report.

[0500] In some implementations, CSI reports are transmitted periodically, aperiodically, and semi-persistently. The channel types carrying CSI reports can include PUCCH and PUSCH.

[0501] The method embodiments of this application have been described in detail above with reference to Figures 1 to 13. The apparatus embodiments of this application will be described below with reference to Figures 14 to 16. It should be understood that the descriptions of the method embodiments correspond to the descriptions of the apparatus embodiments; therefore, any parts not described in detail can be referred to the preceding method embodiments.

[0502] Figure 14 is a schematic block diagram of a communication device provided in an embodiment of this application. As shown in Figure 14, the communication device 1400 includes a transmitting module 1410.

[0503] In one possible implementation, the device 1400 can be used to perform the steps described above by the terminal device.

[0504] The sending module 1410 is configured to: if a first triggering event is detected, send a first channel to the network device, wherein the first channel is used to request resources for a second channel from the network device, or the first channel is used to notify the network device to receive the second channel, wherein the second channel is used to carry a channel status information report based on the first triggering event; wherein the first channel and / or the second channel are used to indicate relevant information of the first triggering event.

[0505] In some implementations, the relevant information of the first triggering event includes a first reporting configuration corresponding to the first triggering event, and the first channel and / or the second channel corresponding to the first reporting configuration.

[0506] In some implementations, the first channel and / or the second channel corresponds to the first report configuration, including: a first resource corresponding to the first report configuration, wherein the first resource includes one or more of the following: transmission resources of the first channel; resources related to the transmission resources of the first channel; and transmission resources of the second channel.

[0507] In some implementations, the first resource corresponds to the first report configuration, including: the index of the first resource corresponds to the index of the first report configuration.

[0508] In some implementations, the first resource corresponds to the first report configuration, including: the first resource corresponds to one or more trigger states, the one or more trigger states being used to indicate the first report configuration.

[0509] In some implementations, the first resource corresponds to one or more trigger states, including: the index of the first resource corresponds to the index of the one or more trigger states.

[0510] In some implementations, the first resource corresponds to the first report configuration, including: the first resource corresponds to the report configuration of one or more component carriers, wherein the report configuration of the one or more component carriers includes the first report configuration.

[0511] In some implementations, the transmission resources of the first channel are Physical Uplink Control Channel (PUCCH) resources; and / or the resources associated with the transmission resources of the first channel are scheduling request resources; and / or the transmission resources of the second channel are PUCCH resources or Physical Uplink Shared Channel (PUSCH) resources.

[0512] In some implementations, the transmission resource of the first channel is a PUCCH resource associated with a scheduling request resource, and one scheduling request resource is associated with one or more PUCCH resources.

[0513] In some implementations, the PUCCH resource is determined based on one or more of the following parameters: the time-domain position of the PUCCH reference resource, the frequency-domain position of the PUCCH reference resource, cyclic shift, orthogonal overlay code, number of frequency division multiplexing, frequency division interval, number of time division multiplexing, and time division interval.

[0514] In some implementations, the index of the PUCCH resource is related to the sorting priority of the PUCCH resource, which is determined based on one or more of the following parameters: the time-domain position of the PUCCH resource, the frequency-domain position of the PUCCH resource, the cyclic shift used by the PUCCH sequence, and the orthogonal overlay code used by the PUCCH sequence.

[0515] In some implementations, the PUSCH resource is determined based on one or more of the following parameters: the time-domain location of the PUSCH reference resource, the frequency-domain location of the PUSCH reference resource, the DMRS port number of the demodulation reference signal, the DMRS sequence, the number of frequency division multiplexing (FDM) units, the frequency division interval, the number of time division multiplexing (TDM) units, and the time division interval.

[0516] In some implementations, the index of the PUSCH resource is related to the sorting priority of the PUSCH resource, which is determined based on one or more of the following parameters: the time domain position of the PUSCH resource, the frequency domain position of the PUSCH resource, the DMRS port number used by the PUSCH reference resource, and the DMRS sequence used by the PUSCH reference resource.

[0517] In some implementations, the second channel includes first indication information, which is used to indicate relevant information about the first triggering event.

[0518] In some implementations, the first indication information is carried in a first field and / or a second field of the channel state information report. The first field is used to indicate information of the first report configuration corresponding to the first triggering event, and the second field is used to indicate information of the component carrier to which the first report configuration belongs. The information of the first report configuration and / or the information of the component carrier are used to indicate relevant information of the first triggering event.

[0519] In some implementations, the second channel is related to the overhead required to transmit the channel state information, and the overhead required to transmit the channel state information is used to indicate relevant information about the first triggering event.

[0520] In some implementations, the first triggering event includes multiple triggering events, and the device further includes a determining module: configured to determine the channel state information reports carried in the second channel based on the priority of the multiple channel state information reports if the second channel cannot carry all the reports in the multiple channel state information reports corresponding to the multiple triggering events.

[0521] In some implementations, the priority of the multiple channel state information reports is determined based on one or more of the following: the transmission mode of the channel state information report, the channel type carrying the channel state information report, the index of the report configuration corresponding to the channel state information report, and the index of the component carrier corresponding to the channel state information report.

[0522] Figure 15 is a schematic block diagram of a communication device provided in an embodiment of this application. As shown in Figure 15, the communication device 1500 includes a receiving module 1510 and a processing module 1520.

[0523] In one possible implementation, the device 1500 can be used to perform the steps described above by the network device.

[0524] The receiving module 1510 is used to: receive a first channel sent by the terminal device, wherein the transmission of the first channel is triggered by a first triggering event.

[0525] The processing module 1520 is configured to: schedule resources of a second channel for the terminal device or receive a second channel based on the first channel, wherein the second channel is used to carry a channel status information report based on the first triggering event.

[0526] The first channel and / or the second channel are used to indicate relevant information about the first triggering event.

[0527] In some implementations, the relevant information of the first triggering event includes a first reporting configuration corresponding to the first triggering event, and the first channel and / or the second channel corresponding to the first reporting configuration.

[0528] In some implementations, the first channel and / or the second channel corresponds to the first report configuration, including: a first resource corresponding to the first report configuration, wherein the first resource includes one or more of the following: transmission resources of the first channel; resources related to the transmission resources of the first channel; and transmission resources of the second channel.

[0529] In some implementations, the first resource corresponds to the first report configuration, including: the index of the first resource corresponds to the index of the first report configuration.

[0530] In some implementations, the first resource corresponds to the first report configuration, including: the first resource corresponds to one or more trigger states, the one or more trigger states being used to indicate the first report configuration.

[0531] In some implementations, the first resource corresponds to one or more trigger states, including: the index of the first resource corresponds to the index of the one or more trigger states.

[0532] In some implementations, the first resource corresponds to the first report configuration, including: the first resource corresponds to the report configuration of one or more component carriers, wherein the report configuration of the one or more component carriers includes the first report configuration.

[0533] In some implementations, the transmission resources of the first channel are Physical Uplink Control Channel (PUCCH) resources; and / or

[0534] The resources associated with the transmission resources of the first channel are scheduling request resources; and / or the transmission resources of the second channel are PUCCH resources or Physical Uplink Shared Channel (PUSCH) resources.

[0535] In some implementations, the transmission resource of the first channel is a PUCCH resource associated with a scheduling request resource, and one scheduling request resource is associated with one or more PUCCH resources.

[0536] In some implementations, the PUCCH resource is determined based on one or more of the following parameters: the time-domain position of the PUCCH reference resource, the frequency-domain position of the PUCCH reference resource, cyclic shift, orthogonal overlay code, number of frequency division multiplexing, frequency division interval, number of time division multiplexing, and time division interval.

[0537] In some implementations, the index of the PUCCH resource is related to the sorting priority of the PUCCH resource, which is determined based on one or more of the following parameters: the time-domain position of the PUCCH resource, the frequency-domain position of the PUCCH resource, the cyclic shift used by the PUCCH sequence, and the orthogonal overlay code used by the PUCCH sequence.

[0538] In some implementations, the PUSCH resource is determined based on one or more of the following parameters: the time-domain location of the PUSCH reference resource, the frequency-domain location of the PUSCH reference resource, the DMRS port number of the demodulation reference signal, the DMRS sequence, the number of frequency division multiplexing (FDM) units, the frequency division interval, the number of time division multiplexing (TDM) units, and the time division interval.

[0539] In some implementations, the index of the PUSCH resource is related to the sorting priority of the PUSCH resource, which is determined based on one or more of the following parameters: the time domain position of the PUSCH resource, the frequency domain position of the PUSCH resource, the DMRS port number used by the PUSCH reference resource, and the DMRS sequence used by the PUSCH reference resource.

[0540] In some implementations, the second channel includes first indication information, which is used to indicate relevant information about the first triggering event.

[0541] In some implementations, the first indication information is carried in a first field and / or a second field of the channel state information report. The first field is used to indicate information of the first report configuration corresponding to the first triggering event, and the second field is used to indicate information of the component carrier to which the first report configuration belongs. The information of the first report configuration and / or the information of the component carrier are used to indicate relevant information of the first triggering event.

[0542] In some implementations, the second channel is related to the overhead required to transmit the channel state information, and the overhead required to transmit the channel state information is used to indicate relevant information about the first triggering event.

[0543] It should be understood that devices 1400 and 1500 are embodied in the form of functional modules. The term "module" here can refer to application-specific integrated circuits (ASICs), electronic circuits, processors (e.g., shared processors, proprietary processors, or group processors, etc.) and memories for executing one or more software or firmware programs, integrated logic circuits, and / or other suitable components supporting the described functions. In an alternative example, those skilled in the art will understand that device 1400 can be specifically a terminal device in the above embodiments, and device 1400 can be used to execute the various processes and / or steps corresponding to the terminal device in the above method embodiments. Device 1500 can be specifically a network device in the above embodiments, and device 1500 can be used to execute the various processes and / or steps corresponding to the network device in the above method embodiments. To avoid repetition, further details are omitted here.

[0544] The aforementioned device 1400 has the function of implementing the corresponding steps performed by the terminal device in the aforementioned method, and the aforementioned device 1500 has the function of implementing the corresponding steps performed by the network device in the aforementioned method. These functions can be implemented in hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the aforementioned functions.

[0545] In embodiments of this application, devices 1400 and 1500 may also be chips, such as a system-on-a-chip (SOC) or a modem. Correspondingly, the receiving module and the transmitting module may be the transceiver circuits of the chip, and are not limited herein.

[0546] Figure 16 is a schematic structural diagram of a communication device according to an embodiment of this application. The dashed lines in Figure 16 indicate that the unit or module is optional. This device 1600 can be used to implement the methods described in the above method embodiments. Device 1600 can be a chip, a terminal device, or a network device.

[0547] Apparatus 1600 may include one or more processors 1610. The processor 1610 may support apparatus 1600 in implementing the methods described in the preceding method embodiments. The processor 1610 may be a general-purpose processor or a special-purpose processor. For example, the processor may be a central processing unit (CPU). Alternatively, the processor may be other general-purpose processors, digital signal processors (DSPs), ASICs, field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or any conventional processor.

[0548] The apparatus 1600 may further include one or more memories 1620. The memories 1620 store a program that can be executed by the processor 1610, causing the processor 1610 to perform the methods described in the preceding method embodiments. The memories 1620 may be independent of the processor 1610 or integrated within the processor 1610.

[0549] The device 1600 may also include a transceiver 1630. The processor 1610 can communicate with other devices or chips via the transceiver 1630. For example, the processor 1610 can send and receive data with other devices or chips via the transceiver 1630.

[0550] This application also provides a computer-readable storage medium for storing a program. This computer-readable storage medium can be applied to a terminal device or network device provided in this application embodiment, and the program causes a computer to execute the methods performed by the terminal device or network device in the various embodiments of this application.

[0551] This application also provides a computer program product. The computer program product includes a program. This computer program product can be applied to a terminal device or network device provided in the embodiments of this application, and the program causes a computer to execute the methods performed by the terminal device or network device in the various embodiments of this application.

[0552] This application also provides a computer program. This computer program can be applied to the terminal device or network device provided in this application, and the computer program causes the computer to execute the methods performed by the terminal device or network device in various embodiments of this application.

[0553] It should be understood that in the embodiments of this application, "B corresponding to A" means that B is associated with A, and B can be determined based on A. However, it should also be understood that determining B based on A does not mean that B is determined solely based on A; B can also be determined based on A and / or other information.

[0554] It should be understood that the term "and / or" in this article is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. Additionally, the character " / " in this article generally indicates that the preceding and following related objects have an "or" relationship.

[0555] It should be understood that in the various embodiments of this application, the order of the above-mentioned processes does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0556] In this application, entity A sends information to entity B, either directly or indirectly through other entities. Similarly, entity B receives information from entity A, either directly or indirectly through other entities. Entities A and B can be RAN nodes or terminals, or modules within RAN nodes or terminals. Information transmission and reception can be between RAN nodes and terminals, such as between a base station and a terminal; between two RAN nodes, such as between a CU and a DU; or between different modules within a single device, such as between a terminal chip and other modules of the terminal, or between a base station chip and other modules of the base station.

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

[0558] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0559] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0560] 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. 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 read or a data storage device such as a server or data center that integrates one or more available media. The available media may be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., digital video discs, DVDs) or semiconductor media (e.g., solid-state disks, SSDs), etc.

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

Claims

1. A method of wireless communication, the method comprising: The method is performed by a terminal device, comprising: if a first trigger event is detected, sending a first channel to a network device, the first channel being used for requesting resources of a second channel from the network device, or the first channel being used for notifying the network device to receive the second channel, the second channel being used for carrying a channel state information report based on the first trigger event; wherein the first channel and / or the second channel is used for indicating related information of the first trigger event.

2. The method of claim 1, wherein, The related information of the first trigger event comprises a first report configuration corresponding to the first trigger event, and the first channel and / or the second channel corresponds to the first report configuration.

3. The method of claim 2, wherein, The first channel and / or the second channel corresponding to the first report configuration comprises that a first resource corresponds to the first report configuration, and the first resource comprises one or more of the following: a sending resource of the first channel; a resource related to the sending resource of the first channel; a sending resource of the second channel.

4. The method of claim 3, wherein, The first resource corresponding to the first report configuration comprises: an index of the first resource corresponding to an index of the first report configuration.

5. The method of claim 3, wherein, The first resource corresponding to the first report configuration comprises: the first resource corresponding to one or more trigger states, the one or more trigger states being used for indicating the first report configuration.

6. The method of claim 5, wherein, The first resource corresponding to the one or more trigger states comprises: an index of the first resource corresponding to an index of the one or more trigger states.

7. The method of claim 3, wherein, The first resource corresponding to the first report configuration comprises: the first resource corresponding to a report configuration of one or more component carriers, the report configuration of the one or more component carriers comprising the first report configuration.

8. The method according to any one of claims 3-7, characterized in that, The sending resource of the first channel is a physical uplink control channel (PUCCH) resource; and / or the resource related to the sending resource of the first channel is a scheduling request resource; and / or the sending resource of the second channel is a PUCCH resource or a physical uplink shared channel (PUSCH) resource.

9. The method of claim 8, wherein, The sending resource of the first channel is a PUCCH resource associated with a scheduling request resource, one scheduling request resource being associated with one or more PUCCH resources.

10. The method according to claim 8 or 9, characterized in that, The PUCCH resource is determined based on one or more of the following parameters: a time domain position of a PUCCH reference resource, a frequency domain position of the PUCCH reference resource, a cyclic shift, an orthogonal cover code, a frequency division multiplexing number, a frequency division interval, a time division multiplexing number, and a time division interval.

11. The method of claim 10, wherein, An index of the PUCCH resource corresponds to an ordering priority of the PUCCH resource, and the ordering priority of the PUCCH resource is determined based on one or more of the following parameters: a time domain position of the PUCCH resource, a frequency domain position of the PUCCH resource, a cyclic shift used by a PUCCH sequence, and an orthogonal cover code used by the PUCCH sequence.

12. The method of claim 8, wherein, The PUSCH resource is determined based on one or more of the following parameters: a time domain location of a PUSCH reference resource, a frequency domain location of the PUSCH reference resource, a demodulation reference signal (DMRS) port number, a DMRS sequence, a frequency division multiplexing number, a frequency division interval, a time division multiplexing number, and a time division interval.

13. The method of claim 12, wherein, An index of the PUSCH resource is related to a priority of the PUSCH resource in an order, and the priority of the PUSCH resource in the order is determined based on one or more of the following parameters: a time domain location of the PUSCH resource, a frequency domain location of the PUSCH resource, a DMRS port number used by the PUSCH reference resource, and a DMRS sequence used by the PUSCH reference resource.

14. The method of any one of claims 1-13, wherein, The first indication information is included in the second channel, and the first indication information is used to indicate related information of the first trigger event.

15. The method of claim 14, wherein, The first indication information is carried in a first field and / or a second field of the channel state information report, the first field is used to indicate information of a first reporting configuration corresponding to the first trigger event, and the second field is used to indicate information of a component carrier to which the first reporting configuration belongs, and the information of the first reporting configuration and / or the information of the component carrier are used to indicate the related information of the first trigger event.

16. The method of claim 1, wherein, The second channel is related to overhead required for transmitting the channel state information, and the overhead required for transmitting the channel state information is used to indicate the related information of the first trigger event.

17. The method of any one of claims 1-16, wherein, The first trigger event includes a plurality of trigger events, and the method further includes: If the second channel cannot carry all of a plurality of channel state information reports corresponding to the plurality of trigger events, determining a channel state information report carried in the second channel based on priorities of the plurality of channel state information reports.

18. The method of claim 17, wherein, The priorities of the plurality of channel state information reports are determined based on one or more of the following information: a transmission mode of the channel state information report, a channel type carrying the channel state information report, an index of a reporting configuration corresponding to the channel state information report, and an index of a component carrier corresponding to the channel state information report.

19. A method of wireless communication, the method comprising: The method is performed by a network device, and includes: receiving a first channel sent by a terminal device, and the sending of the first channel is triggered by a first trigger event; scheduling a resource of a second channel or receiving the second channel for the terminal device based on the first channel, and the second channel is used to carry a channel state information report based on the first trigger event; The first channel and / or the second channel are used to indicate related information of the first trigger event.

20. A communications device, characterized by including: a processor coupled to a memory, the memory being used to store a computer program, and when the processor invokes the computer program, the communication device performs the method of any one of claims 1 to 18 or the method of claim 19.

21. A computer-readable storage medium, characterized in that, The computer program is stored in the computer readable storage medium and, when executed by the processor, causes the processor to perform the method of any one of claims 1 to 18, or the method of claim 19.

22. A computer program product, characterised in that, The computer program product comprises computer program code which, when run on the communication device, causes the communication device to perform the method of any one of claims 1 to 18, or the method of claim 19.

Images