Sending method and apparatus for uplink report, and receiving method and apparatus for uplink report

Abstract

Provided in the embodiments of the present application are a sending method and apparatus for an uplink report, and a receiving method and apparatus for an uplink report. The sending method comprises: a terminal device determining that a report meets a trigger condition; the terminal device sending a physical uplink control channel (PUCCH); and the terminal device sending the report on an uplink channel associated with the PUCCH, wherein the report occupies a CSI processing unit from a first time point to a second time point, the first time point is determined on the basis of the PUCCH, and / or the second time point is determined on the basis of the uplink channel.

Description

Methods and apparatus for sending and receiving uplink reports Technical Field

[0001] The embodiments of this application relate to the field of communication technology. Background Technology

[0002] 5G NR supports Channel State Information (CSI) reporting. For example, a CSI report may include at least one of the following: CSI-RS Resource Indicator (CRI), SSB Resource Indicator (SSBRI), Layer 1 Reference Signal Received Power (L1-RSRP), and Layer 1 Signal-to-Interference-plus-Noise Ratio (L1-SINR), i.e., beam-related reporting. The terminal device sends beam reports to the network device, which can then perform beam management based on these reports, for example, indicating a better beam for the terminal device.

[0003] When a terminal device sends a CSI report is determined by the network device; that is, the report is scheduled by the network device. The network device can be configured to send periodic CSI reports, thus the terminal device sends CSI reports periodically; the network device can be configured to send semi-persistent CSI reports, which the terminal device sends periodically after being activated by the network device; the network device can be configured to send a non-periodic CSI reports, which the terminal device sends once after being triggered by the network device. The CSI report includes measurement results specific to the serving cell.

[0004] Version 17 (Rel-17) adds support for Inter Cell Beam Management (ICBM). In ICBM, CSI reports can include measurement results for non-serving cells, allowing network devices to instruct terminal devices to use the beam of a non-serving cell without the terminal device switching to the non-serving cell.

[0005] Rel-18 supports Layer 1 / L2 Triggered Mobility (LTM), and adds support for LTM CSI reports. In LTM, terminal devices can send LTM CSI reports. Rel-18 LTM CSI reports include SSBRI and L1-RSRP. Unlike traditional CSI reports, LTM CSI reports include measurement results for candidate cells. Network devices can use this information to determine the beam to use in the candidate cell for the terminal device and indicate the beam to the terminal device before handover, enabling the terminal device to quickly apply the appropriate beam for data transmission after handover. In other words, in LTM, the terminal device hands over to a candidate cell and uses the candidate cell's beam after handover. Similarly, terminal devices can send LTM CSI reports periodically, semi-persistently, or aperiodically. LTM CSI reports are also part of the network device scheduling reports.

[0006] It should be noted that the above introduction to the technical background is only for the purpose of providing a clear and complete explanation of the technical solutions of this application and facilitating understanding by those skilled in the art. It should not be assumed that these technical solutions are known to those skilled in the art simply because they have been described in the background section of this application.

[0007] Summary of the Invention

[0008] The inventors discovered that processing or calculating a report by a terminal device requires a certain number of CSI Processing Units (CPUs). Whether it's a CSI report or an LTM CSI report, a report occupies CPU time for a given period. Existing standards define the CPU occupancy time for reports scheduled by network devices. A terminal device may need to process multiple reports, thus multiple reports may each occupy CPU time. If the total CPU occupancy of multiple reports exceeds the number of CPUs the terminal device can support, the terminal device may choose not to update one or more reports with the lowest priority.

[0009] In the upcoming Rel-19, event-driven reporting (also known as event-triggered reporting or terminal device-initiated reporting) will be introduced. More specifically, further enhancements to CSI and LTM CSI reporting will be introduced, supporting event-driven CSI and event-driven LTM CSI reporting. Event-driven CSI and event-driven LTM CSI reports correspond to traditional CSI and LTM CSI reports, respectively. For simplicity, the term "event-driven reporting" will be used uniformly in the following description; that is, the event-driven report in the embodiments of this application can be either an event-driven CSI report or an event-driven LTM CSI report.

[0010] Unlike traditional reporting, event-driven reporting determines when the terminal device sends a report, i.e., it's triggered by an event. In other words, the terminal device only sends reports when necessary, allowing for more timely reporting. Furthermore, by avoiding unnecessary reporting, reporting overhead is reduced. How to process or generate event-driven reports is a problem that needs to be solved.

[0011] To address at least one of the above-mentioned problems, embodiments of this application provide a method and apparatus for sending and receiving uplink reports.

[0012] According to one aspect of the embodiments of this application, a method for sending an uplink report is provided, comprising:

[0013] The terminal device determines that the report meets the triggering conditions;

[0014] The terminal device sends a Physical Uplink Control Channel (PUCCH);

[0015] The terminal device transmits the report on the uplink channel associated with the Physical Uplink Control Channel (PUCCH);

[0016] The report occupies a CSI processing unit from a first time point to a second time point, wherein the first time point is determined according to the Physical Uplink Control Channel (PUCCH), and / or the second time point is determined according to the uplink channel.

[0017] According to another aspect of the embodiments of this application, an uplink report sending apparatus is provided, comprising:

[0018] The processing unit determines that the report meets the triggering conditions;

[0019] The transmitting unit transmits the Physical Uplink Control Channel (PUCCH);

[0020] The transmitting unit transmits the report on the uplink channel associated with the physical uplink control channel.

[0021] The report occupies a CSI processing unit from a first time point to a second time point, wherein the first time point is determined based on the physical uplink control channel, and / or the second time point is determined based on the uplink channel.

[0022] According to another aspect of the embodiments of this application, a method for sending an uplink report is provided, comprising:

[0023] The terminal device determines that the report meets the triggering conditions;

[0024] The terminal device sends a Physical Uplink Control Channel (PUCCH);

[0025] The terminal device receives the Physical Downlink Control Channel (PDCCH);

[0026] The terminal device transmits the report on the uplink channel indicated by the physical downlink control channel (PDCCH);

[0027] The report occupies the CSI processing unit from the third time point to the fourth time point. The third time point is determined according to the Physical Uplink Control Channel (PUCCH) or the Physical Downlink Control Channel (PDCCH), and / or the fourth time point is determined according to the uplink channel.

[0028] According to another aspect of the embodiments of this application, an uplink report sending apparatus is provided, comprising:

[0029] The processing unit determines that the report meets the triggering conditions;

[0030] The transmitting unit transmits the PUCCH.

[0031] The receiving unit receives the PDCCH;

[0032] The transmitting unit transmits the report on the uplink channel indicated by the PDCCH.

[0033] The report occupies the CSI processing unit from the third time point to the fourth time point, the third time point being determined according to the PUCCH or the PDCCH, and / or the second time point being determined according to the uplink channel.

[0034] According to another aspect of the embodiments of this application, a method for receiving uplink reports is provided, comprising:

[0035] The network device receives a physical uplink control channel sent by the terminal device; wherein the terminal device determines that the report meets the triggering conditions;

[0036] The network device determines an uplink channel; wherein the uplink channel is determined according to the PUCCH, the uplink channel is associated with the PUCCH, and the network device receives the report on the uplink channel;

[0037] The report is a channel status information processing unit (CPU) from a first time point to a second time point, wherein the first time point is determined based on the physical uplink control channel, and / or the second time point is determined based on the uplink channel.

[0038] According to another aspect of the embodiments of this application, an uplink report receiving device is provided, comprising:

[0039] A receiving unit receives a physical uplink control channel sent by a terminal device, wherein the terminal device determines that the report meets the triggering conditions.

[0040] A processing unit that determines an uplink channel, wherein the uplink channel is determined according to the PUCCH, the uplink channel is associated with the PUCCH, and the receiving unit receives the report on the uplink channel;

[0041] The report is a channel status information processing unit (CPU) from a first time point to a second time point, wherein the first time point is determined based on the physical uplink control channel, and / or the second time point is determined based on the uplink channel.

[0042] According to another aspect of the embodiments of this application, a method for receiving uplink reports is provided, comprising:

[0043] The network device receives a PUCCH sent by the terminal device; wherein the terminal device determines that the report meets the triggering conditions;

[0044] The network device sends a PDCCH to the terminal device; wherein the PDCCH indicates the uplink channel;

[0045] The network device receives the report on the uplink channel;

[0046] The report occupies the CSI processing unit from the third time point to the fourth time point, the third time point being determined according to the PUCCH or the PDCCH, and / or the fourth time point being determined according to the uplink channel.

[0047] According to another aspect of the embodiments of this application, an uplink report receiving device is provided, comprising:

[0048] A receiving unit receives a physical uplink control channel sent by a terminal device, wherein the terminal device determines that the report meets the triggering conditions.

[0049] A transmitting unit that transmits a PDCCH to the terminal device; wherein the PDCCH indicates the uplink channel;

[0050] The receiving unit receives the report on the uplink channel indicated by the PDCCH;

[0051] The report occupies the CSI processing unit from the third time point to the fourth time point. The third time point is determined based on the physical uplink control channel or the physical downlink control channel, and / or the fourth time point is determined based on the uplink channel.

[0052] One of the beneficial effects of this application's embodiments is that: the CSI report occupies the CSI processing unit from a first time point to a second time point, where the first time point is determined based on the Physical Uplink Control Channel (PUCCH), and / or the second time point is determined based on the uplink channel. Therefore, CPU usage only occurs when the terminal device has an event-driven report to send, thus avoiding unnecessary CPU usage.

[0053] Specific embodiments of this application are disclosed in detail with reference to the following description and accompanying drawings, indicating how the principles of this application can be adopted. It should be understood that the embodiments of this application are not limited in scope. Within the spirit and scope of the appended claims, embodiments of this application include many changes, modifications, and equivalents.

[0054] Features described and / or illustrated for one embodiment may be used in the same or similar manner in one or more other embodiments, combined with features in other embodiments, or substituted for features in other embodiments.

[0055] It should be emphasized that the term "including / comprises" as used herein refers to the presence of a feature, whole, step, or component, but does not exclude the presence or addition of one or more other features, wholes, steps, or components. Attached Figure Description

[0056] The elements and features described in one drawing or embodiment of this application may be combined with elements and features shown in one or more other drawings or embodiments. Furthermore, in the drawings, similar reference numerals denote corresponding parts in several drawings and can be used to indicate corresponding parts used in more than one embodiment.

[0057] Figure 1 is a schematic diagram of a communication system according to an embodiment of this application;

[0058] Figure 2 is a schematic diagram of an event-driven report according to an embodiment of this application;

[0059] Figure 3 is another schematic diagram of an event-driven report according to an embodiment of this application;

[0060] Figure 4 is a schematic diagram of an uplink report sending method according to an embodiment of this application;

[0061] Figure 5 is an example diagram of an uplink report according to an embodiment of this application;

[0062] Figure 6 is another example diagram of the uplink report according to an embodiment of this application;

[0063] Figure 7 is another example diagram of the uplink report in an embodiment of this application;

[0064] Figure 8 is another example diagram of the uplink report according to an embodiment of this application;

[0065] Figure 9 is another schematic diagram of the uplink report sending method according to an embodiment of this application;

[0066] Figure 10 is another schematic diagram of the uplink report sending method according to an embodiment of this application;

[0067] Figure 11 is another example diagram of the uplink report according to an embodiment of this application;

[0068] Figure 12 is another example diagram of the uplink report in an embodiment of this application;

[0069] Figure 13 is another example diagram of the uplink report in an embodiment of this application;

[0070] Figure 14 is another example diagram of the uplink report according to an embodiment of this application;

[0071] Figure 15 is another example diagram of the uplink report in an embodiment of this application;

[0072] Figure 16 is another example diagram of the uplink report in an embodiment of this application;

[0073] Figure 17 is another example diagram of the uplink report in an embodiment of this application;

[0074] Figure 18 is another schematic diagram of the uplink report sending method according to an embodiment of this application;

[0075] Figure 19 is a schematic diagram of an uplink report receiving method according to an embodiment of this application;

[0076] Figure 20 is a schematic diagram of an uplink report receiving method according to an embodiment of this application;

[0077] Figure 21 is a schematic diagram of an uplink report sending device according to an embodiment of this application;

[0078] Figure 22 is a schematic diagram of an uplink report receiving device according to an embodiment of this application;

[0079] Figure 23 is a schematic diagram of a terminal device according to an embodiment of this application;

[0080] Figure 24 is a schematic diagram of a network device according to an embodiment of this application. Detailed Implementation

[0081] Referring to the accompanying drawings, the foregoing and other features of this application will become apparent from the following description. Specific embodiments of this application are specifically disclosed in the description and drawings, illustrating partial implementations in which the principles of this application may be employed. It should be understood that this application is not limited to the described embodiments; rather, it includes all modifications, variations, and equivalents falling within the scope of the appended claims.

[0082] In the embodiments of this application, the terms "first," "second," etc., are used to distinguish different elements by name, but do not indicate the spatial arrangement or chronological order of these elements, and these elements should not be limited by these terms. The term "and / or" includes any one or more of the terms listed in association and all combinations thereof. The terms "comprising," "including," "having," etc., refer to the presence of the stated features, elements, components, or assemblies, but do not exclude the presence or addition of one or more other features, elements, components, or assemblies.

[0083] In the embodiments of this application, the singular forms "a," "the," etc., including the plural forms, should be broadly understood as "a kind" or "a class" rather than limited to the meaning of "an." Furthermore, the term "the" should be understood to include both the singular and plural forms, unless the context explicitly indicates otherwise. Additionally, the term "according to" should be understood as "at least partially based on…," and the term "based on" should be understood as "at least partially based on…," unless the context explicitly indicates otherwise.

[0084] In the embodiments of this application, the term "communication network" or "wireless communication network" may refer to a network that conforms to any of the following communication standards, such as Long Term Evolution (LTE), LTE-Advanced (LTE-A), Wideband Code Division Multiple Access (WCDMA), High-Speed ​​Packet Access (HSPA), etc.

[0085] Furthermore, communication between devices in a communication system can be carried out according to communication protocols at any stage, including but not limited to the following communication protocols: 1G (generation), 2G, 2.5G, 2.75G, 3G, 4G, 4.5G and 5G, New Radio (NR), future 6G, etc., and / or other currently known or future communication protocols.

[0086] In the embodiments of this application, the term "network device" refers, for example, to a device in a communication system that connects a terminal device to a communication network and provides services to that terminal device. Network devices may include, but are not limited to, the following devices: base station (BS), access point (AP), transmission reception point (TRP), broadcast transmitter, mobile management entity (MME), gateway, server, radio network controller (RNC), base station controller (BSC), etc.

[0087] Base stations can include, but are not limited to: NodeBs (or NBs), evolved NodeBs (eNodeBs or eNBs), and 5G base stations (gNBs), IAB hosts, etc. They can also include Remote Radio Heads (RRHs), Remote Radio Units (RRUs), relays, or low-power nodes (e.g., femeto, pico, etc.). The term "base station" can encompass some or all of their functions, and each base station can provide communication coverage to a specific geographic area. The term "cell" can refer to a base station and / or its coverage area, depending on the context in which the term is used.

[0088] In the embodiments of this application, the terms "User Equipment" (UE) or "Terminal Equipment" (TE) refer, for example, to a device that accesses a communication network and receives network services through a network device. A terminal device can be fixed or mobile, and may also be referred to as a mobile station (MS), terminal, subscriber station (SS), access terminal (AT), station, etc.

[0089] The terminal device may include, but is not limited to, the following devices: cellular phone, personal digital assistant (PDA), wireless modem, wireless communication device, handheld device, machine-type communication device, laptop computer, cordless phone, smartphone, smartwatch, digital camera, etc.

[0090] For example, in scenarios such as the Internet of Things (IoT), terminal devices can also be machines or devices for monitoring or measurement, such as including but not limited to: machine-type communication (MTC) terminals, vehicle communication terminals, device-to-device (D2D) terminals, machine-to-machine (M2M) terminals, and so on.

[0091] Furthermore, the terms "network side" or "network equipment side" refer to one side of the network, which can be a base station or include one or more network devices as described above. The terms "user side," "terminal side," or "terminal equipment side" refer to the side of the user or terminal, which can be a UE or include one or more terminal devices as described above. Unless otherwise specified, "equipment" can refer to either network equipment or terminal equipment.

[0092] The following examples illustrate the scenarios of embodiments of this application, but this application is not limited thereto.

[0093] Figure 1 is a schematic diagram of a communication system according to an embodiment of this application, illustrating the case of a terminal device and a network device as examples. As shown in Figure 1, the communication system 100 may include a network device 101 and terminal devices 102 and 103. For simplicity, Figure 1 only illustrates the case of two terminal devices and one network device, but the embodiments of this application are not limited to this.

[0094] In this embodiment of the application, network device 101 and terminal devices 102 and 103 can transmit existing services or services that can be implemented in the future. For example, these services may include, but are not limited to: enhanced mobile broadband (eMBB), massive machine-type communication (mMTC), and ultra-reliable and low-latency communication (URLLC), etc.

[0095] It is worth noting that Figure 1 shows that both terminal devices 102 and 103 are within the coverage area of ​​network device 101, but this application is not limited to this. Both terminal devices 102 and 103 may be outside the coverage area of ​​network device 101, or one terminal device 102 may be within the coverage area of ​​network device 101 while the other terminal device 103 may be outside the coverage area of ​​network device 101.

[0096] In the embodiments of this application, the signaling may be, for example, Radio Resource Control (RRC) signaling; for example, referred to as an RRC message, including MIB, system information, dedicated RRC messages; or referred to as an RRC information element. The signaling may also be, for example, Medium Access Control (MAC) signaling; or referred to as a MAC control element. However, this application is not limited to these.

[0097] In the following description, without confusion, the terms "PDCCH" and "Physical Downlink Control Channel" or "Downlink Control Information" are used interchangeably, as are the terms "PDSCH" and "Physical Downlink Data Channel" or "Downlink Data". Furthermore, transmitting or receiving a PDCCH can be understood as transmitting or receiving downlink control information carried by the PDCCH; transmitting or receiving a PDSCH can be understood as transmitting or receiving downlink data carried by the PDSCH.

[0098] The terms "PUCCH" and "Physical Uplink Control Channel" or "Uplink Control Information" are interchangeable, as are the terms "PUSCH" and "Physical Uplink Data Channel" or "Uplink Data." Furthermore, transmitting or receiving a PUCCH can be understood as transmitting or receiving downlink control information carried by the PUCCH; transmitting or receiving a PUSCH can be understood as transmitting or receiving downlink data carried by the PUSCH.

[0099] Terminal devices need to send event-driven reports on certain time-frequency resources. The determination of resources requires corresponding information interaction. For example, the terminal device may send a first message to request dynamically scheduled resources or to notify whether semi-statically configured resources are actually being used.

[0100] Figure 2 is a schematic diagram of an event-driven report according to an embodiment of this application. As shown in Figure 2, the first resource for sending the first message is a configured periodic PUCCH resource (only one period is shown in Figure 2 for simplicity), and the second resource for sending the event-driven report is a configured periodic PUSCH or PUCCH resource (only one resource is shown). There is an association between the first resource and the second resource, for example, one first resource is associated with one second resource.

[0101] As shown in Figure 2, the terminal device measures one or more reference signals (RS1 to RSN). After detecting an event that triggers a report, it notifies the network device that a report is being transmitted on the second resource associated with the first message (first resource) by sending a first message, and then sends a report on the associated second resource.

[0102] Conversely, if the terminal device does not detect an event, it can refrain from sending the first message. This notifies the network device that no report transmission exists on the second resource associated with the first message, allowing the network device to schedule other terminal devices to transmit on the second resource, thus avoiding waste of the pre-configured second resource in a semi-static manner. Without loss of generality, if the terminal device does not detect an event, it can also send the first message, but the content of this first message will differ from the previous one. In this case, the first message will notify the network device that no report transmission exists on the second resource associated with the first message.

[0103] Figure 3 is another schematic diagram of event-driven reporting according to an embodiment of this application. As shown in Figure 3, the first resource for sending the first message is a configured periodic PUCCH resource (only one resource is shown), and the second resource for sending the event-driven report is a PDCCH (or DCI) scheduled resource.

[0104] As shown in Figure 3, the terminal device measures one or more reference signals (RS1 to RSN). After detecting an event that triggers a report, it requests the resources needed to send the report (i.e., requests the second resource) from the network device by sending a first message on the first resource. Then, upon receiving the PDCCH, it sends the report on the second resource scheduled by the PDCCH. The report can be carried by either PUSCH or PUCCH, with the first message carried by PUCCH. Here, "resources" refers to time-frequency resources.

[0105] This application does not limit the events that trigger the report. For example, an event could be that the measurement result (L1-RSRP) of a new beam (one of RS1 to RSN) is higher than the measurement result of the current beam by a certain value, or that the measurement result of the current beam is lower than a certain value. This application does not limit the content of the report. For example, the report includes a reference signal index and the L1-RSRP measured based on that reference signal; the report may include one or more reference signal indices and L1-RSRPs. The report is used to report beam information, and its purpose is to report the beam and the measurement results for that beam. The report can also be replaced by a beam report.

[0106] Existing standards define CPU usage time for network device scheduling reports, allowing terminal devices to determine whether to update one or more reports with the lowest priority based on CPU usage time. More specifically, if the total CPU usage of multiple reports over a period of time exceeds the number of CPUs that the terminal device can support, the terminal device may choose not to update one or more reports with the lowest priority.

[0107] With the introduction of event-driven reporting, it is also necessary to define the CPU time consumed by these reports. In other words, when a terminal device has an event-driven report to send, defining the CPU time consumed is a problem that needs to be solved. For example, how to determine the CPU time consumed by the event-driven report, and how to determine which reference signals the event-driven report is based on. The following examples illustrate the scenario where a terminal device has an event-driven report to send.

[0108] First aspect of the embodiments

[0109] This application provides a method for sending uplink reports, described from the perspective of the terminal device.

[0110] Figure 4 is a schematic diagram of an uplink report transmission method according to an embodiment of this application. As shown in Figure 4, the method includes:

[0111] 401, The terminal device has determined that the report meets the first triggering condition;

[0112] 402, the terminal device sends a Physical Uplink Control Channel (PUCCH);

[0113] 403, the terminal device transmits the report on an uplink channel associated with the Physical Uplink Control Channel (PUCCH); wherein the report occupies a CSI processing unit from a first time point to a second time point, the first time point being determined according to the Physical Uplink Control Channel (PUCCH), and / or the second time point being determined according to the uplink channel.

[0114] In the embodiments of this application, "report" is also known as "event-driven report". "Event-driven" can be replaced with "UE-initiated" or "event-triggered". This application is not limited to these. The uplink channel carrying the report (also known as CSI report) is, for example, the Physical Uplink Shared Channel (PUSCH) or the Physical Uplink Control Channel (PUCCH), but this application is not limited to these.

[0115] For example, for an event-driven report (hereinafter referred to as a report), when an event meets the triggering conditions, the terminal device sends the report and determines the CPU usage time of the report. The terminal device measures the reference signal used for measurement, and when the event meets the triggering conditions, reports the measurement results, etc. The terminal device is configured (e.g., via RRC signaling) with a set of PUCCH resources and a set of uplink channel resources. One PUCCH resource is associated with one (or more) uplink channel resources, which can be PUSCH or PUCCH. If the event meets the triggering conditions, the terminal device sends a PUCCH on a PUCCH resource (i.e., a PUCCH transmission opportunity) and sends the event-driven report on the uplink channel resource (also referred to as the uplink channel) associated with that PUCCH. If the event does not meet the triggering conditions, the terminal device will not send a PUCCH on the PUCCH resource, nor will it send the event-driven report on the uplink channel associated with that PUCCH. Before sending a report, a terminal device needs to process or calculate the report's content (such as measurement results). This processing or calculation consumes a portion of the terminal device's processing resources, the exact amount of which can be measured by the CSI Processing Unit (CPU). Processing or calculating a report requires a certain number of CPUs over a period of time. In other words, a report consumes CPUs over a given period.

[0116] For an event-driven report, when an event meets its triggering conditions, the terminal device sends a PUCCH on a PUCCH resource and then sends the report on the uplink channel resource associated with that PUCCH resource. In this case, the event-driven report occupies CPU time from a first time point to a second time point. The first time point (start point) is determined based on the PUCCH, and the second time point (end point) is determined based on the uplink channel associated with the PUCCH. This time period from the first time point to the second time point can also be called the CPU occupancy time. Each time the terminal device sends an event-driven report, that report corresponds to one CPU occupancy time. If the event does not meet its triggering conditions, the terminal device will not send an event-driven report, and there will be no CPU occupancy. The terminal device sends a PUCCH on the PUCCH resource and an uplink channel on the uplink channel resource. For simplicity, the PUCCH resource and the uplink channel can be used interchangeably.

[0117] The terminal device and network device have a consistent understanding of the time-frequency positions of the reference signal used for measurement (which may be referred to as the measurement reference signal or reference signal), PUCCH, and uplink channel, and the network device determines whether there is an event-driven report to be sent by receiving the PUCCH. In this case, for example, a first time point can be determined based on the reference signal configured by RRC signaling, and a second time point can be determined based on the uplink channel; however, this would result in prolonged CPU usage for the terminal device. In contrast, the embodiments of this application determine the CPU usage time based on the actually transmitted PUCCH and uplink channel, thereby avoiding unnecessary CPU usage only when there is an event-driven report to be sent.

[0118] It is worth noting that Figure 4 above is only an illustrative description of the embodiments of this application, but this application is not limited thereto. For example, the execution order between various operations can be appropriately adjusted, and other operations can be added or some operations can be removed. Those skilled in the art can make appropriate modifications based on the above content, and are not limited to the description in Figure 4 above.

[0119] In this embodiment, a report meeting the trigger condition indicates that the event associated with the report meets the trigger condition, also referred to as the event meeting the trigger condition. For example, a report is associated with an event. When the event meets the trigger condition, the report associated with the event becomes a report meeting the trigger condition (the triggered report), and the terminal device sends the report associated with the event. This embodiment does not limit the definition of an event. For example, an event (the trigger condition of an event) is defined as: the measurement result of at least one new beam is higher than the measurement result of the current beam by a certain threshold value (or the number of times it exceeds a certain threshold value exceeds a certain number); for example, the measurement of the new beam refers to the measurement of the reference signal in the reference signal set, and the measurement of the current beam refers to the measurement of the source reference signal (or the SSB quasi-co-addressable with the source reference signal) of the currently applied TCI state (downlink TCI state or joint TCI state); for example, the measurement result can be L1-RSRP or filtered L1-RSRP. The threshold value can be configured by RRC signaling, for example, configuring independent threshold values ​​for CSI-RS-based measurements and SSB-based measurements respectively.

[0120] In some embodiments, the second time point is the last symbol of the uplink channel, and / or the first time point is the first symbol after the Physical Uplink Control Channel (PUCCH).

[0121] Figure 5 is an example diagram of an uplink report according to an embodiment of this application. As shown in Figure 5, the second time point is the last symbol of the uplink channel, and the first time point is the first symbol after the Physical Uplink Control Channel (PUCCH).

[0122] As shown in Figure 5, the terminal device measures reference signals, including periodic reference signal 1 (RS1), periodic reference signal 2 (RS2), and so on, up to periodic reference signal N (RSN). The reference signals can be CSI-RS or SSB. The terminal device is configured with periodic PUCCH resources and periodic uplink channel resources by RRC signaling. The uplink channel can be simply referred to as the channel. PUCCH 1 is associated with channel 1, PUCCH 2 with channel 2, and so on. If the triggering condition is met before PUCCH 1, the terminal device sends PUCCH 1 and a report on channel 1. This report occupies CPU from the first symbol after PUCCH 1 (first time point) to the last symbol of channel 1 (second time point). If the triggering condition is met again before PUCCH 3, the terminal device sends PUCCH 3 and a report on channel 3. This report occupies CPU from the first symbol after PUCCH 3 to the last symbol of channel 3. If the event does not meet the triggering conditions before PUCCH 2, the terminal device will not send PUCCH 2 and will not send a report on channel 2. At this time, there is no CPU usage.

[0123] In this application's embodiments, "symbol" can also be replaced with "time slot". "The first symbol after PUCCH" can also be replaced with "the last symbol of PUCCH" or "the first symbol of PUCCH", with no fundamental technical difference. Through this application's embodiments, CPU usage only occurs when there are event-driven reports to be sent, thereby avoiding unnecessary CPU usage and resource waste.

[0124] In some embodiments, the first time point is the first symbol after the first time interval following the Physical Uplink Control Channel (PUCCH).

[0125] Figure 6 is another example diagram of the uplink report according to an embodiment of this application. For example, the difference between Figure 6 and Figure 5 is that the position of the first time point determined by the terminal device is different. In Figure 6, the first time point is the first symbol after the first time interval after PUCCH 1. That is, there is a first time interval T1 (T1>0) between the first time point shown in Figure 6 and the first symbol after PUCCH 1.

[0126] Wherein, T1 can be configured or predefined. For example, T1 may be configured by RRC signaling or determined according to predefined rules. T1 can be related to the capabilities of the terminal device. For example, the terminal device may include reporting T1 in its device capability report, and the first time interval is the T1 reported by the terminal device; or, for example, the terminal device may include reporting T1 in its device capability report, and the network device may configure T1 for the terminal device based on the reported device capabilities, and the first time interval is the T1 configured by the network device. This application embodiment does not limit the unit of T1; for example, the unit of T1 may be a symbol, a time slot, or a second.

[0127] In the above embodiments, the terminal device measures the reference signal and includes the measurement results for the reference signal in the event-driven report. For a sent event-driven report, determining which reference signals' measurement results are included in the report content is also a problem that needs to be addressed. That is, it needs to be clarified which reference signals the terminal device calculates or generates the report content based on.

[0128] In some embodiments, the terminal device determines the measurement results to be included in the report based on a reference signal no later than a second time interval before the Physical Uplink Control Channel (PUCCH), and includes them in the report for transmission. This allows sufficient preparation time for the terminal device to generate report content, transmit the PUCCH, and send the report.

[0129] Figure 7 is another example diagram of the uplink report according to an embodiment of this application. As shown in Figure 7, the terminal device determines the measurement results included in the transmitted report (e.g., a report transmitted on channel 1) based on a reference signal of a second time interval T2 (T2≥0) no later than the transmitted PUCCH (e.g., PUCCH 1). The terminal device determines the measurement results included in the report based on the reference signal of the time interval T2 no later than the PUCCH. This embodiment of the application does not limit the reference signal; for example, the reference signal may be CSI-RS and / or SSB.

[0130] T2 can be configured or predefined, or it can be related to the capabilities of the terminal device; this application does not impose any restrictions on this.

[0131] This application does not limit the unit of T2; for example, the unit of T2 can be a symbol, a time slot, or a second. Thus, the terminal device determines the measurement result based on one or more reference signals at a time no later than a certain point before the PUCCH, and transmits the measurement result and other information on the uplink channel associated with the PUCCH.

[0132] In the above embodiments, "determining the measurement results included in the report based on a reference signal no later than a second time interval before the PUCCH" can be replaced with "determining the measurement results included in the report based on a reference signal no later than a reference resource, wherein the reference resource is a second time interval earlier than the PUCCH." Regardless of the description used, it describes how the terminal device determines the measurement results based on a reference signal at a time point no later than the PUCCH. For example, assuming the terminal device transmits the PUCCH in time slot n, the reference resource is located in time slot nn. ref n ref This indicates the second time interval.

[0133] In the above embodiments, "the terminal device determines the measurement result based on a reference signal at a time point no later than the PUCCH" can be implemented separately from "the report occupies CPU from the first time point to the second time point". For example, the terminal device determines that the report meets the triggering condition, sends a PUCCH, and sends the report on the uplink channel associated with the PUCCH, wherein the terminal device determines the measurement result included in the report based on a reference signal at a second time interval no later than the PUCCH.

[0134] In some embodiments, the first time point is the first symbol of the earliest reference signal in a set of reference signals, wherein the set of reference signals is the latest set of reference signals no later than the second time interval before the Physical Uplink Control Channel (PUCCH).

[0135] Figure 8 is another example diagram of the uplink report according to an embodiment of this application. As shown in Figures 7 and 8, the time of the second time interval before the transmission of PUCCH is denoted as t2, and reference signals 1 to reference signals N are denoted as a set of reference signals. That is, the terminal device determines the measurement results included in the transmitted report based on a set of reference signals (RS1 to RSN) no later than t2.

[0136] As shown in Figure 8, the reference signal no later than t2 can include multiple sets of reference signals. Among these, for the latest set of reference signals in time, the first time point is the first symbol of the earliest reference signal (RS1) in time within that set of reference signals.

[0137] In some embodiments, an event-driven report occupies 1 CSI processing unit.

[0138] Figure 9 is another schematic diagram of the uplink report sending method according to an embodiment of this application. As shown in Figure 9, the method includes:

[0139] 901, The terminal device has confirmed that the triggering conditions are met;

[0140] 902, the terminal device sends a Physical Uplink Control Channel (PUCCH);

[0141] 903, the terminal device cancels the transmission of the report on the uplink channel associated with the Physical Uplink Control Channel (PUCCH); the report occupies a CSI processing unit from a first time point to a second time point, the first time point being determined according to the Physical Uplink Control Channel (PUCCH), and / or the second time point being determined according to the uplink channel.

[0142] In this embodiment, as described above, if the terminal device determines that an event meets the triggering conditions, the terminal device sends a report on the uplink channel associated with the PUCCH. This report occupies CPU time from the first time point to the second time point. If the event does not meet the triggering conditions, the terminal device does not send a report, and therefore the report does not occupy CPU time. Furthermore, there is a situation where the terminal device determines that the event meets the triggering conditions, but cancels the report that should have been sent on the uplink channel associated with the PUCCH for some reason. In this case, the report still occupies CPU time from the first time point to the second time point. The first and second time points can be determined according to the method described in the previous embodiment. That is, although the terminal device does not send a report in this case, the report still occupies CPU time.

[0143] In the above embodiments, for example, the terminal device needs to send a first event-driven report (low priority) and a second information (high priority) at the same time. Due to the limitations of the terminal device's capabilities, the terminal device cancels the sending of the first event-driven report with lower priority and only sends the second information with higher priority. This application embodiment does not limit the reasons for the terminal device to cancel sending the event-driven report.

[0144] It is worth noting that Figure 9 above is only an illustrative description of the embodiments of this application, but this application is not limited thereto. For example, the execution order between various operations can be appropriately adjusted, and other operations can be added or some operations can be removed. Those skilled in the art can make appropriate modifications based on the above content, and are not limited to the description in Figure 9 above.

[0145] The above embodiments are merely illustrative examples of the embodiments of this application, but this application is not limited thereto, and appropriate modifications can be made based on the above embodiments. For example, the above embodiments can be used alone, or one or more of the above embodiments can be combined. The embodiments of this application are illustrated using two reports as an example, but can be extended to cases with more than two reports, which will not be elaborated further.

[0146] Through the embodiments of this application, the terminal device only uses CPU when there is an event-driven report to send. This avoids unnecessary CPU usage and thus prevents resource waste.

[0147] Second aspect of the embodiments

[0148] This application provides a method for sending an uplink report, described from the perspective of a terminal device. Descriptions identical to those in the first aspect of the embodiment are omitted. Figure 10 is a schematic diagram of an uplink report sending method according to an embodiment of this application. As shown in Figure 10, the method includes:

[0149] 1001, The terminal device confirms that the report meets the triggering conditions;

[0150] 1002, the terminal device sends a Physical Uplink Control Channel (PUCCH);

[0151] 1003, the terminal device receives the Physical Downlink Control Channel (PDCCH);

[0152] 1004, the terminal device sends the report on the uplink channel indicated by the physical downlink control channel (PDCCH); the report occupies the CSI processing unit from a third time point to a fourth time point, the third time point being determined according to the physical uplink control channel (PUCCH) or the physical downlink control channel (PDCCH), and / or the fourth time point being determined according to the uplink channel.

[0153] In the above embodiments, the terminal device is configured with a set of PUCCH resources. If an event meets the triggering conditions, the terminal device sends a PUCCH on a PUCCH resource, i.e., requests resources from the network device for sending a report. Afterwards, the terminal device receives a PDCCH (i.e., DCI) sent by the network device and sends a report on the uplink channel indicated by the PDCCH. In this case, the event-driven report occupies CPU time from a third time point to a fourth time point. The third time point is determined based on the PUCCH or the PDCCH, and the fourth time point is determined based on the uplink channel indicated by the PDCCH.

[0154] The uplink channel can be either PUSCH or PUCCH. "Uplink channel indicated by PDCCH (DCI)" can be either "PUSCH indicated by uplink DCI" or "PUCCH indicated by downlink DCI". Therefore, CPU usage only occurs when there are event-driven reports to be sent, avoiding unnecessary CPU consumption.

[0155] It is worth noting that Figure 10 above is only an illustrative description of the embodiments of this application, but this application is not limited thereto. For example, the execution order between various operations can be appropriately adjusted, and other operations can be added or some operations can be removed. Those skilled in the art can make appropriate modifications based on the above content, and are not limited to the description in Figure 10 above.

[0156] Figure 11 is another example diagram of uplink reporting in an embodiment of this application. For example, Figure 11 makes the same assumption as Figure 5 regarding PUCCH, that is, the event meets the triggering condition before PUCCH 1 and PUCCH 3, so the terminal device sends PUCCH 1 and PUCCH 3.

[0157] The difference between Figure 11 and Figure 5 is that in Figure 11, the resource location of the uplink channel used by the terminal device to send the report is indicated by the DCI (i.e., the terminal device determines the uplink channel based on the DCI). For example, as shown in Figure 11, the terminal device measures the reference signal (SSB or CSI-RS) to determine that the report meets the triggering conditions; the terminal device sends a PUCCH, that is, notifies the network device that it has a report to send and requests the network device for the resource to send the report; after receiving the PUCCH, the network device sends a DCI to indicate the resource used by the terminal device to send the report, that is, to indicate the resource where the uplink channel is located; the terminal device receives the DCI and determines the resource location of the uplink channel. The DCI can be an uplink DCI (e.g., DCI format 0_1 ​​or 0_2) or a downlink DCI (e.g., DCI format 1_1 or 1_2), and the uplink channel can be a PUSCH or a PUCCH; the terminal device sends a report on the uplink channel, and the report content includes the index of the reference signal and the L1-RSRP of the reference signal.

[0158] As shown in Figure 11, the terminal device sends a report on channel 1 indicated by DCI 1 and on channel 3 indicated by DCI 3. This report occupies CPU time from the third time point to the fourth time point. Furthermore, if the event does not meet the triggering condition before PUCCH 2, the terminal device does not send PUCCH 2, and there is no CPU usage in this case.

[0159] In some embodiments, the fourth time point is the last symbol of the uplink channel, and / or the third time point is the first symbol after the Physical Uplink Control Channel (PUCCH).

[0160] As shown in Figure 11, the uplink channel resources in Figure 11 are dynamically indicated by DCI. If the triggering condition is met before PUCCH 1, the terminal device sends PUCCH 1, receives DCI 1, and sends a report on channel 1 indicated by DCI 1. This report occupies CPU from the first symbol after PUCCH 1 (third time point) to the last symbol of channel 1 (fourth time point). Similarly, if the triggering condition is met before PUCCH 3, the terminal device sends PUCCH 3, receives DCI 3, and sends a report on channel 3 indicated by DCI 3. This report occupies CPU from the first symbol after PUCCH 3 (third time point) to the last symbol of channel 3 (fourth time point).

[0161] Figure 12 is another example diagram of the uplink report of an embodiment of this application. As shown in Figure 12, in some embodiments, the third time point is the first symbol after the third time interval after PUCCH, and the third time interval is denoted as T3 (T3>0).

[0162] T3 can be configured or predefined. For example, T3 may be configured by RRC signaling or determined according to predefined rules. T3 can be related to the terminal device's capabilities. For example, the terminal device may include a report of T3 in its capability report, and the third time interval is the T3 reported by the terminal device. Alternatively, the terminal device may include a report of T3 in its capability report, and the network device may configure T3 for the terminal device based on the reported capabilities, in which case the third time interval is the T3 configured by the network device. This application does not limit the unit of T3; for example, the unit of T3 can be a symbol, a time slot, or a second.

[0163] Figure 13 is another example diagram of the uplink report according to an embodiment of this application. As shown in Figure 13, in some embodiments, the terminal device determines the measurement results included in the transmitted report (e.g., the report transmitted on channel 1) based on a reference signal of a fourth time interval T4 (T4≥0) no later than the transmitted PUCCH (e.g., PUCCH 1).

[0164] T4 can be configured or predefined, or it can be related to the capabilities of the terminal device; this application does not impose any restrictions on this.

[0165] This application does not limit the unit of T4; for example, the unit of T4 can be a symbol, a time slot, or a second. Thus, the terminal device determines the measurement result based on one or more reference signals at a time no later than a certain point before the PUCCH, and transmits the measurement result and other information on the uplink channel associated with the PUCCH.

[0166] In some embodiments, the third time point is the first symbol of the earliest reference signal in a set of reference signals, wherein the set of reference signals is the latest set of reference signals no later than the fourth time interval preceding the Physical Uplink Control Channel (PUCCH).

[0167] Figure 14 is another example diagram of the uplink report according to an embodiment of this application. For example, as shown in Figures 13 and 14, the time of the fourth time interval before the transmitted PUCCH is denoted as t4. The terminal device determines the measurement results included in the transmitted report (e.g., the report transmitted on channel 1) based on the reference signal of the fourth time interval T4 before the transmitted PUCCH (e.g., PUCCH 1), and takes the first symbol of RS1 in the latest set of reference signals (RS1 to RSN) no later than t4 as the third time point.

[0168] In some embodiments, the third time point is the first symbol following the Physical Downlink Control Channel (PDCCH).

[0169] Figure 15 is another example diagram of the uplink report of an embodiment of this application. As shown in Figure 15, in some embodiments, the third time point is the first symbol after the Physical Downlink Control Channel (PDCCH), that is, the third time point is the first symbol after the DCI.

[0170] In some embodiments, the third time point is the first symbol after the fifth time interval following the Physical Downlink Control Channel (PDCCH).

[0171] Figure 16 is another example diagram of the uplink report in an embodiment of this application. As shown in Figure 16, the third time point is the first symbol after the fifth time interval T5 (T5>0) following the Physical Downlink Control Channel (PDCCH). T5 can be configured or predefined; for example, T5 may be configured by RRC signaling or determined according to predefined rules. T5 can be related to the terminal device's capabilities. For example, the terminal device may include a report of T5 in its device capability report, and the fifth time interval is the T5 reported by the terminal device. Alternatively, the terminal device may include a report of T5 in its device capability report, and the network device may configure T5 for the terminal device based on the reported device capabilities; in this case, the fifth time interval is the T5 configured by the network device. This embodiment of the application does not limit the unit of T5; for example, the unit of T5 can be a symbol, a time slot, or a second.

[0172] In some embodiments, the terminal device determines the measurement results included in the report based on a reference signal no later than the sixth time interval before the Physical Downlink Control Channel (PDCCH).

[0173] Figure 17 is another example diagram of the uplink report of an embodiment of this application. As shown in Figure 17, in some embodiments, the terminal device determines the measurement results included in the report based on a reference signal no later than the sixth time interval T6 (T6≥0) before the Physical Downlink Control Channel (PDCCH).

[0174] In some embodiments, the third time point is the first symbol of the earliest reference signal in a set of reference signals, wherein the set of reference signals is the latest set of reference signals no later than the sixth time interval before the Physical Downlink Control Channel (PDCCH).

[0175] As shown in Figure 17, the time interval six before the transmitted PUCCH is denoted as t6. Reference signals 1 to N are denoted as a set of reference signals. That is, the terminal device determines the measurement results included in the transmitted report based on a set of reference signals (RS1 to RSN) no later than t6. The reference signals no later than t6 may include multiple sets of reference signals. Among these, for the latest set of reference signals in time, the third time point is the first symbol of the earliest reference signal (RS1) in that set of reference signals.

[0176] In the above embodiment, an event-driven report occupies 1 CSI processing unit.

[0177] Figure 18 is another schematic diagram of the uplink report transmission method according to an embodiment of this application; as shown in Figure 18, the method further includes:

[0178] 1801, The terminal device confirms that the report meets the triggering conditions;

[0179] 1802, the terminal device sends the Physical Uplink Control Channel (PUCCH);

[0180] 1803, the terminal device receives the Physical Downlink Control Channel (PDCCH);

[0181] 1804, the terminal device cancels the transmission of the report on the uplink channel indicated by the physical downlink control channel (PDCCH); the report occupies the CSI processing unit from a third time point to a fourth time point, the third time point being determined according to the physical uplink control channel (PUCCH) or the physical downlink control channel (PDCCH), and / or the fourth time point being determined according to the uplink channel.

[0182] In the above embodiments, for example, similar to the case where the terminal device cancels a report that should have been sent on the uplink channel associated with PUCCH for some reason, if the terminal device cancels a report that should have been sent on the uplink channel indicated by DCI for some reason, the report still occupies the CPU from the third time point to the fourth time point. This application embodiment does not limit the reasons why the terminal device cancels sending event-driven reports. For example, if the terminal device needs to send a first event-driven report (low priority) and second information (high priority) simultaneously, limited by the terminal device's capabilities, the terminal device cancels sending the lower-priority first event-driven report and only sends the higher-priority second information.

[0183] The above embodiments are merely illustrative examples of embodiments of this application, but this application is not limited thereto, and appropriate modifications can be made based on the above embodiments. For example, the above embodiments can be used alone, or one or more of the above embodiments can be combined.

[0184] Through the embodiments of this application, the terminal device will only generate CPU usage when there is an event-driven report to send, which can avoid unnecessary CPU usage and thus avoid waste of resources.

[0185] Third aspect of the embodiments

[0186] This application provides a method for receiving uplink reports, described from the perspective of a network device. The embodiments of the third aspect can be combined with the embodiments of the first and second aspects, and the content identical to that in the embodiments of the first and second aspects will not be repeated.

[0187] Figure 19 is a schematic diagram of an uplink report receiving method according to an embodiment of this application. As shown in Figure 19, the method includes:

[0188] 1901, The network device receives a PUCCH sent by the terminal device; wherein the terminal device determines that the report meets the triggering conditions;

[0189] 1902, the network device determines an uplink channel; wherein, the uplink channel is determined according to the PUCCH, and the uplink channel is associated with the PUCCH;

[0190] 1903, the network device receives the report on the uplink channel; wherein the report occupies a CSI processing unit from a first time point to a second time point, the first time point being determined according to the physical uplink control channel, and / or the second time point being determined according to the uplink channel.

[0191] It is worth noting that Figure 19 above is only an illustrative description of the embodiments of this application, but this application is not limited thereto. For example, the execution order between various operations can be appropriately adjusted, and other operations can be added or some operations can be removed. Those skilled in the art can make appropriate modifications based on the above content, and are not limited to the description in Figure 19 above.

[0192] In some embodiments, the network device can determine the uplink channel based on the PUCCH and the association between the PUCCH and the uplink channel.

[0193] In some embodiments, the network device may also send configuration information to the terminal device to configure the terminal device to perform event-driven reporting. For example, triggering conditions can be configured by the network device, and this application is not limited to this; for example, they can also be predefined or defaulted.

[0194] The above embodiments are merely illustrative examples of embodiments of this application, but this application is not limited thereto, and appropriate modifications can be made based on the above embodiments. For example, the above embodiments can be used alone, or one or more of the above embodiments can be combined.

[0195] Through the embodiments of this application, the terminal device will only generate CPU usage when there is an event-driven report to send, which can avoid unnecessary CPU usage and thus avoid waste of resources.

[0196] Fourth aspect of the embodiment

[0197] This application provides a method for receiving uplink reports, described from the perspective of a network device. The embodiments of the fourth aspect can be combined with the embodiments of the first and second aspects, and the content identical to that in the embodiments of the first and second aspects will not be repeated.

[0198] Figure 20 is a schematic diagram of an uplink report receiving method according to an embodiment of this application. As shown in Figure 20, the method includes:

[0199] 2001, The network device receives a PUCCH sent by the terminal device; wherein the terminal device determines that the report meets the triggering conditions;

[0200] 2002, the network device sends a PDCCH to the terminal device; wherein the PDCCH indicates the uplink channel;

[0201] 2003, the network device receives the report on the uplink channel, wherein the report occupies the CSI processing unit from a third time point to a fourth time point, the third time point being determined according to the PUCCH or the PDCCH, and / or the fourth time point being determined according to the uplink channel.

[0202] It is worth noting that Figure 20 above is only an illustrative description of the embodiments of this application, but this application is not limited thereto. For example, the execution order between various operations can be appropriately adjusted, and other operations can be added or some operations can be removed. Those skilled in the art can make appropriate modifications based on the above content, and are not limited to the description in Figure 20 above.

[0203] In some embodiments, the network device may send a DCI to the terminal device and determine the uplink channel based on the DCI.

[0204] In some embodiments, the network device may also send configuration information to the terminal device to configure the terminal device to perform event-driven reporting. For example, triggering conditions can be configured by the network device, and this application is not limited to this; for example, they can also be predefined or defaulted.

[0205] The above embodiments are merely illustrative examples of embodiments of this application, but this application is not limited thereto, and appropriate modifications can be made based on the above embodiments. For example, the above embodiments can be used alone, or one or more of the above embodiments can be combined.

[0206] Through the embodiments of this application, the terminal device will only generate CPU usage when there is an event-driven report to send, which can avoid unnecessary CPU usage and thus avoid waste of resources.

[0207] Fifth aspect of the embodiment

[0208] This application provides an uplink report sending device. This device may be, for example, a terminal device, or one or more components or parts configured within the terminal device; details identical to those in the embodiments of the first to fourth aspects will not be repeated.

[0209] Figure 21 is a schematic diagram of an uplink report sending apparatus according to an embodiment of this application. As shown in Figure 21, the uplink report sending apparatus 2100 includes a processing unit 2101 and a sending unit 2102.

[0210] In some embodiments, the processing unit 2101 determines that the report meets the triggering conditions; the sending unit 2102 sends the Physical Uplink Control Channel (PUCCH);

[0211] The transmitting unit 2102 determines the uplink channel according to the PUCCH and transmits the report on the uplink channel associated with the physical uplink control channel;

[0212] The report occupies a CSI processing unit from a first time point to a second time point, wherein the first time point is determined based on the physical uplink control channel, and / or the second time point is determined based on the uplink channel.

[0213] In some embodiments, as shown in FIG21, the uplink report sending device 2100 includes a receiving unit 2103.

[0214] In some embodiments, after the transmitting unit 2102 transmits the PUCCH, the receiving unit 2103 receives the PDCCH; the transmitting unit transmits the report on the uplink channel indicated by the PDCCH;

[0215] The report occupies the CSI processing unit from the third time point to the fourth time point. The third time point is determined according to the Physical Uplink Control Channel (PUCCH) or the Physical Downlink Control Channel (PDCCH), and / or the fourth time point is determined according to the uplink channel.

[0216] It is worth noting that the above description only covers the components or modules relevant to this application, but this application is not limited thereto. The uplink reporting transmission device 2100 may also include other components or modules, and for details regarding these components or modules, please refer to related technologies.

[0217] Furthermore, for simplicity, Figure 21 only illustrates the connection relationships or signal flow between the various components or modules, but those skilled in the art should understand that various related technologies such as bus connections can be used. The aforementioned components or modules can be implemented using hardware facilities such as processors, memory, transmitters, and receivers; this application does not limit this implementation.

[0218] Through the embodiments of this application, the terminal device will only generate CPU usage when there is an event-driven report to send, which can avoid unnecessary CPU usage and thus avoid waste of resources.

[0219] Implementation of the sixth aspect

[0220] This application provides an uplink report receiving device. This device may be, for example, a network device, or one or more components or parts configured within a network device; details identical to those in the embodiments of the first to fifth aspects will not be repeated.

[0221] Figure 22 is a schematic diagram of an uplink report receiving device according to an embodiment of this application. As shown in Figure 22, the uplink report receiving device 2200 includes a receiving unit 2201 and a processing unit 2202.

[0222] In some embodiments, the receiving unit 2201 receives a PUCCH sent by the terminal device; wherein the terminal device determines that the report meets the triggering condition.

[0223] Processing unit 2202 determines the uplink channel; wherein the uplink channel is determined according to the PUCCH, and the uplink channel is associated with the PUCCH.

[0224] The network device receives the report on the uplink channel; wherein the report occupies the channel state information processing unit (CPU, CSI Processing Unit) from a first time point to a second time point, the first time point being determined based on the physical uplink control channel, and / or the second time point being determined based on the uplink channel.

[0225] In some embodiments, the uplink reporting receiving device 2200 may further include a transmitting unit (not shown in FIG22), which may transmit, for example, a PDCCH (bearer DCI), or configuration information and / or indication information. This application is not limited thereto. The PDCCH transmitted by the network device indicates the uplink channel.

[0226] The network device receives the report on the uplink channel; wherein the report occupies the channel state information processing unit (CPU, CSI Processing Unit) from a third time point to a fourth time point, the third time point being determined according to PUCCH or PDCCH, and / or the fourth time point being determined according to the uplink channel.

[0227] It is worth noting that the above description only covers the components or modules relevant to this application, but this application is not limited thereto. The uplink reporting receiving device 2200 may also include other components or modules, and for details regarding these components or modules, please refer to related technologies.

[0228] Furthermore, for simplicity, Figure 22 only illustrates the connection relationships or signal flow between the various components or modules, but those skilled in the art should understand that various related technologies such as bus connections can be used. The aforementioned components or modules can be implemented using hardware facilities such as processors, memory, transmitters, and receivers; this application does not limit this implementation.

[0229] Through the embodiments of this application, the terminal device will only generate CPU usage when there is an event-driven report to send, which can avoid unnecessary CPU usage and thus avoid waste of resources.

[0230] Seventh aspect of the embodiment

[0231] This application also provides a communication system, which can be referred to FIG1. ​​The contents that are the same as those in the embodiments of the first to sixth aspects will not be repeated.

[0232] In some embodiments, the communication system 100 may include at least:

[0233] The terminal device determines that the report meets the triggering conditions; sends a physical uplink control channel (PUCCH); and sends the report on an uplink channel associated with the physical uplink control channel (PUCCH) or on an uplink channel indicated by a physical downlink control channel (PDCCH).

[0234] A network device that receives the Physical Uplink Control Channel (PUCCH); determines an uplink channel associated with the Physical Uplink Control Channel (PUCCH) or an uplink channel indicated by the Physical Downlink Control Channel (PDCCH), and receives the report on the uplink channel;

[0235] The report occupies a CSI processing unit from a first time point to a second time point, where the first time point is determined based on the Physical Uplink Control Channel (PUCCH), and / or the second time point is determined based on the uplink channel; or

[0236] The report occupies the CSI processing unit from the third time point to the fourth time point, the third time point being determined based on the Physical Uplink Control Channel (PUCCH) or the Physical Downlink Control Channel (PDCCH), and / or the fourth time point being determined based on the uplink channel.

[0237] This application also provides a terminal device, but the application is not limited thereto and may also include other devices.

[0238] Figure 23 is a schematic diagram of a terminal device according to an embodiment of this application. As shown in Figure 23, the terminal device 2300 may include a processor 2310 and a memory 2320; the memory 2320 stores data and programs and is coupled to the processor 2310. It is worth noting that this figure is exemplary; other types of structures may also be used to supplement or replace this structure to implement telecommunications functions or other functions.

[0239] For example, processor 2310 may be configured to execute a program to implement the uplink report transmission method as described in the embodiments of the first and second aspects. For example, processor 2310 may be configured to perform the following control: determine that a report meets a triggering condition; transmit a physical uplink control channel (PUCCH); determine an uplink channel according to the PUCCH, and transmit the report on the uplink channel associated with the physical uplink control channel, wherein the report occupies a CSI processing unit from a first time point to a second time point, the first time point being determined according to the physical uplink control channel, and / or the second time point being determined according to the uplink channel.

[0240] For example, processor 2310 may be configured to perform the following control: determine that a report meets the triggering conditions; send a PUCCH; receive a PDCCH; and send the report on the uplink channel indicated by the PDCCH, wherein the report occupies a CSI processing unit from a third time point to a fourth time point, the third time point being determined according to the PUCCH or the PDCCH, and / or the fourth time point being determined according to the uplink channel.

[0241] As shown in Figure 23, the terminal device 2300 may further include: a communication module 2330, an input unit 2340, a display 2350, and a power supply 2360. The functions of these components are similar to those in the prior art and will not be described in detail here. It is worth noting that the terminal device 2300 does not necessarily include all the components shown in Figure 23; these components are not essential. Furthermore, the terminal device 2300 may also include components not shown in Figure 23, which can be referred to in the prior art.

[0242] This application also provides a network device, such as a base station, but this application is not limited to this and may also include other network devices.

[0243] Figure 24 is a schematic diagram of the network device configuration according to an embodiment of this application. As shown in Figure 24, the network device 2400 may include: a processor 2410 (e.g., a central processing unit CPU) and a memory 2420; the memory 2420 is coupled to the processor 2410. The memory 2420 can store various data; in addition, it also stores an information processing program 2430, and executes the program 2430 under the control of the processor 2410.

[0244] For example, processor 2410 may be configured to execute a program to implement the uplink report receiving method as described in the embodiments of the third and fourth aspects. For example, processor 2410 may be configured to perform the following control: receiving a physical uplink control channel sent by a terminal device; wherein the terminal device determines that a report meets a triggering condition; determining an uplink channel; wherein the uplink channel is determined according to the PUCCH, and the uplink channel is associated with the PUCCH; receiving the report on the uplink channel; wherein the report occupies a channel state information processing unit (CPU, CSI Processing Unit) from a first time point to a second time point, the first time point being determined according to the physical uplink control channel, and / or the second time point being determined according to the uplink channel.

[0245] For example, the processor 2410 may be configured to perform the following control: receive a PUCCH sent by a terminal device; wherein the terminal device determines that a report meets a triggering condition; send a PDCCH to the terminal device; wherein the PDCCH indicates an uplink channel; receive the report on the uplink channel, wherein the report occupies a CSI processing unit from a third time point to a fourth time point, the third time point being determined based on the PUCCH or the PDCCH, and / or the fourth time point being determined based on the uplink channel.

[0246] In addition, as shown in Figure 24, network device 2400 may also include transceiver 2440 and antenna 2450, etc.; the functions of the above components are similar to those in the prior art, and will not be described in detail here. It is worth noting that network device 2400 does not necessarily include all the components shown in Figure 24; furthermore, network device 2400 may also include components not shown in Figure 24, which can be referred to in the prior art.

[0247] This application also provides a computer program, wherein when the program is executed in a terminal device, the program causes the terminal device to perform the uplink report sending method described in the embodiments of the first and second aspects.

[0248] This application also provides a storage medium storing a computer program, wherein the computer program causes a terminal device to execute the uplink report sending method described in the embodiments of the first and second aspects.

[0249] This application also provides a computer program, wherein when the program is executed in a network device, the program causes the network device to perform the uplink report receiving method described in the third and fourth aspects of the embodiments.

[0250] This application also provides a storage medium storing a computer program, wherein the computer program causes a network device to perform the uplink report receiving method described in the third and fourth aspects of the embodiments.

[0251] The apparatus and methods described above in this application can be implemented in hardware or in combination with software. This application relates to a computer-readable program that, when executed by a logic component, enables the logic component to implement the apparatus or components described above, or to implement the various methods or steps described above. This application also relates to storage media for storing the above programs, such as hard disks, magnetic disks, optical disks, DVDs, flash memory, etc.

[0252] The methods / apparatus described in conjunction with the embodiments of this application can be directly embodied in hardware, software modules executed by a processor, or a combination of both. For example, one or more and / or combinations of one or more functional block diagrams shown in the figures can correspond to various software modules in a computer program flow, or to various hardware modules. These software modules can correspond to the various steps shown in the figures, respectively. These hardware modules can be implemented, for example, using a field-programmable gate array (FPGA) to embed these software modules.

[0253] The software module can reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium known in the art. A storage medium can be coupled to the processor, enabling the processor to read information from and write information to the storage medium; or the storage medium can be an integral part of the processor. The processor and storage medium can reside in an ASIC. The software module can be stored in the memory of a mobile terminal or in a memory card that can be inserted into the mobile terminal. For example, if the device (such as a mobile terminal) uses a high-capacity MEGA-SIM card or a high-capacity flash memory device, the software module can be stored in the MEGA-SIM card or the high-capacity flash memory device.

[0254] One or more and / or one or more combinations of functional blocks described in the accompanying drawings can be implemented as a general-purpose processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA), or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, or any suitable combination thereof for performing the functions described herein. One or more and / or one or more combinations of functional blocks described in the accompanying drawings can also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in communication with a DSP, or any other such configuration.

[0255] The present application has been described above with reference to specific embodiments. However, those skilled in the art should understand that these descriptions are exemplary and not intended to limit the scope of protection of the present application. Those skilled in the art can make various modifications and variations to the present application based on its spirit and principles, and these modifications and variations are also within the scope of the present application.

[0256] Regarding the implementation methods including the above embodiments, the following notes are also disclosed:

[0257] 1. A method for sending an uplink report, comprising:

[0258] The terminal device determines that the report meets the triggering conditions;

[0259] The terminal device sends a Physical Uplink Control Channel (PUCCH);

[0260] The terminal device determines the uplink channel based on the PUCCH and sends the report on the uplink channel associated with the physical uplink control channel.

[0261] The report occupies a CSI processing unit from a first time point to a second time point, wherein the first time point is determined based on the physical uplink control channel, and / or the second time point is determined based on the uplink channel.

[0262] 2. A method for sending an uplink report, comprising:

[0263] The terminal device determines that the report meets the triggering conditions;

[0264] The terminal device sends a PUCCH;

[0265] The terminal device receives the PDCCH;

[0266] The terminal device sends the report on the uplink channel indicated by the PDCCH.

[0267] The report occupies the CSI processing unit from the third time point to the fourth time point, the third time point being determined according to the PUCCH or the PDCCH, and / or the fourth time point being determined according to the uplink channel.

[0268] 3. A method for sending an uplink report, comprising:

[0269] The terminal device determines that the report meets the triggering conditions;

[0270] The terminal device sends a Physical Uplink Control Channel (PUCCH);

[0271] The terminal device cancels the transmission of the report on the uplink channel associated with the Physical Uplink Control Channel (PUCCH);

[0272] The report occupies a CSI processing unit from a first time point to a second time point, wherein the first time point is determined according to the Physical Uplink Control Channel (PUCCH), and / or the second time point is determined according to the uplink channel.

[0273] 4. A method for sending an uplink report, comprising:

[0274] The terminal device determines that the report meets the triggering conditions;

[0275] The terminal device sends a Physical Uplink Control Channel (PUCCH);

[0276] The terminal device receives the Physical Downlink Control Channel (PDCCH);

[0277] The terminal device cancels the transmission of the report on the uplink channel indicated by the physical downlink control channel (PDCCH);

[0278] The report occupies the CSI processing unit from the third time point to the fourth time point. The third time point is determined according to the Physical Uplink Control Channel (PUCCH) or the Physical Downlink Control Channel (PDCCH), and / or the fourth time point is determined according to the uplink channel.

[0279] 5. A method for receiving an uplink report, comprising:

[0280] The network device receives a physical uplink control channel sent by the terminal device; wherein the terminal device determines that the report meets the triggering conditions;

[0281] The network device determines the uplink channel; wherein the uplink channel is determined according to the PUCCH, and the uplink channel is associated with the PUCCH;

[0282] The network device receives the report on the uplink channel; wherein the report occupies the channel state information processing unit (CPU, CSI Processing Unit) from a first time point to a second time point, the first time point being determined based on the physical uplink control channel, and / or the second time point being determined based on the uplink channel.

[0283] 6. A method for receiving an uplink report, comprising:

[0284] The network device receives a PUCCH sent by the terminal device; wherein the terminal device determines that the report meets the triggering conditions;

[0285] The network device sends a PDCCH to the terminal device; wherein the PDCCH indicates the uplink channel;

[0286] The network device receives the report on the uplink channel, wherein the report occupies the CSI processing unit from a third time point to a fourth time point, the third time point being determined according to the PUCCH or the PDCCH, and / or the fourth time point being determined according to the uplink channel.

[0287] 7. A terminal device comprising a memory and a processor, the memory storing a computer program and the processor being configured to execute the computer program to implement a method for transmitting an uplink report as described in any one of Appendices 1 to 4.

[0288] 8. A network device comprising a memory and a processor, the memory storing a computer program and the processor being configured to execute the computer program to implement a method for receiving uplink reports as described in any one of Appendices 5 to 6.

[0289] 9. A computer program product comprising at least a computer program that, when executed by a processor, causes a terminal device to perform an uplink report transmission method as described in any one of Appendices 1 to 4.

[0290] 10. A computer program product comprising at least a computer program that, when executed by a processor, causes a network device to perform an uplink report receiving method as described in any one of Appendices 5 to 6.

Claims

1. An uplink reporting device, comprising: The processing unit determines that the report meets the triggering conditions; The transmitting unit transmits the physical uplink control channel; The transmitting unit transmits the report on the uplink channel associated with the physical uplink control channel; The report is a channel status information processing unit from a first time point to a second time point, wherein the first time point is determined based on the physical uplink control channel, and / or the second time point is determined based on the uplink channel.

2. The apparatus according to claim 1, wherein, The second time point is the last symbol of the uplink channel.

3. The apparatus according to claim 1, wherein, The first time point is the first symbol after the physical uplink control channel.

4. The apparatus according to claim 1, wherein, The first time point is the first symbol after the first time interval following the physical uplink control channel.

5. The apparatus according to claim 1, wherein, The processing unit determines the measurement results included in the report based on a reference signal no later than the second time interval preceding the physical uplink control channel.

6. The apparatus according to claim 5, wherein, The first time point is the first symbol of the earliest reference signal in a set of reference signals, wherein the set of reference signals is the latest set of reference signals no later than the second time interval before the physical uplink control channel.

7. The apparatus according to claim 1, wherein, The report occupies one channel state information processing unit.

8. An uplink reporting device, comprising: The processing unit determines that the report meets the triggering conditions; The transmitting unit transmits the physical uplink control channel; The receiving unit receives the physical downlink control channel; The transmitting unit transmits the report on the uplink channel indicated by the physical downlink control channel; The report is a channel status information processing unit from the third time point to the fourth time point. The third time point is determined based on the physical uplink control channel or the physical downlink control channel, and / or the fourth time point is determined based on the uplink channel.

9. The apparatus according to claim 8, wherein, The fourth time point is the last symbol of the uplink channel.

10. The apparatus according to claim 8, wherein, The third time point is the first symbol after the physical uplink control channel.

11. The apparatus according to claim 8, wherein, The third time point is the first symbol after the third time interval following the physical uplink control channel.

12. The apparatus according to claim 8, wherein, The processing unit determines the measurement results included in the report based on a reference signal no later than the fourth time interval preceding the physical uplink control channel.

13. The apparatus according to claim 12, wherein, The third time point is the first symbol of the earliest reference signal in a set of reference signals, wherein the set of reference signals is the latest set of reference signals no later than the fourth time interval before the physical uplink control channel.

14. The apparatus according to claim 8, wherein, The third time point is the first symbol after the physical downlink control channel.

15. The apparatus according to claim 8, wherein, The third time point is the first symbol after the fifth time interval following the physical downlink control channel.

16. The apparatus according to claim 9, wherein, The processing unit determines the measurement results included in the report based on a reference signal no later than the sixth time interval preceding the physical downlink control channel.

17. The apparatus according to claim 16, wherein, The third time point is the first symbol of the earliest reference signal in a set of reference signals, wherein the set of reference signals is the latest set of reference signals no later than the sixth time interval before the physical downlink control channel.

18. The apparatus according to claim 8, wherein, The report occupies one channel state information processing unit.

19. A communication system, comprising: The terminal device determines that the report meets the triggering conditions; Send the physical uplink control channel; The report is transmitted on the uplink channel associated with the physical uplink control channel, or on the uplink channel indicated by the physical downlink control channel; A network device that receives the physical uplink control channel; determines an uplink channel associated with the physical uplink control channel or an uplink channel indicated by a physical downlink control channel, and receives the report on the uplink channel; The report, from a first time point to a second time point, is processed by a channel state information processing unit. The first time point is determined based on the physical uplink control channel, and / or the second time point is determined based on the uplink channel; or... The report is processed by the channel occupancy status information unit from the third time point to the fourth time point. The third time point is determined based on the physical uplink control channel or the physical downlink control channel, and / or the fourth time point is determined based on the uplink channel.

Images