Signal sending method and apparatus, and signal receiving method and apparatus

Abstract

Provided in the embodiments of the present application are a signal sending method and apparatus, and a signal receiving method and apparatus. The signal sending method comprises: when a report meets a triggering condition, sending a PUCCH on a first valid PUCCH resource, and the terminal device sending a PUSCH carrying the report on a first valid PUSCH resource associated with the first valid PUCCH resource, wherein an association relationship between the first valid PUCCH resource and the first valid PUSCH resource is determined on the basis of at least one of the following: in ascending order of time, mapping a valid PUSCH resource to the last valid PUCCH resource before a first time interval preceding the valid PUSCH resource; or, in ascending order of time, mapping a valid PUCCH resource to the first valid PUSCH resource after a first time interval following the valid PUCCH resource.

Description

Signal transmission method, signal reception method and device 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] In Rel-19, event-driven reporting (also known as event-triggered reporting or end-device initiated reporting) will be introduced. More specifically, further enhancements to CSI reporting will be introduced, namely support for event-driven CSI reporting. Event-driven CSI reporting corresponds to traditional CSI reporting.

[0005] Unlike traditional reporting, event-driven reporting determines when the terminal device sends a report, i.e., it is 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 can be reduced.

[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 the current process for sending event-driven reports is incomplete, and the problems that need to be solved include at least one of the following: how to determine the association between PUCCH and PUSCH in Mode B; whether to send PUSCH when PUCCH is not sent in Mode B; and on which carrier to receive and trigger the DCI report in Mode A. Therefore, how the terminal device sends event-driven reports is a problem that needs to be solved.

[0009] To address at least one of the aforementioned problems, embodiments of this application provide a signal transmission method, a signal reception method, and an apparatus that can ensure that terminal devices and network devices have a consistent understanding of the transmission and reception of reports, avoid uncertain device behavior during the transmission and reception of reports, and thereby improve the reliability of report transmission.

[0010] According to one aspect of the embodiments of this application, a signal transmission method is provided, which is applied to a terminal device, the terminal device being configured with periodic physical uplink control channel (PUCCH) resources and periodic physical uplink shared channel (PUSCH) resources, wherein the method includes:

[0011] If the report meets the triggering conditions, a PUCCH is sent on the first valid PUCCH resource, and a PUSCH carrying the report is sent on the first valid PUSCH resource associated with the first valid PUCCH resource.

[0012] The association between the first valid PUCCH resource and the first valid PUSCH resource is determined based on at least one of the following:

[0013] In ascending order of time, a valid PUSCH resource is mapped to the last valid PUSCH resource preceding the first time interval before the valid PUSCH resource; or...

[0014] In ascending order of time, a valid PUCCH resource is mapped to the first valid PUSCH resource after the first time interval following the valid PUCCH resource; or...

[0015] In ascending order of time, a PUSCH resource is mapped to the last PUCCH resource preceding the first time interval before the PUSCH resource; or...

[0016] In ascending order of time, a PUCCH resource is mapped to the first PUSCH resource after the first time interval following the PUCCH resource.

[0017] According to another aspect of the embodiments of this application, a signal transmitting apparatus is provided, configured in a terminal device, the terminal device being configured with periodic physical uplink control channel (PUCCH) resources and periodic physical uplink shared channel (PUSCH) resources, wherein the apparatus includes:

[0018] The transmitter, when the report meets the triggering conditions, sends a PUCCH on a first valid PUCCH resource and sends a PUSCH carrying the report on a first valid PUSCH resource associated with the first valid PUCCH resource;

[0019] The association between the first valid PUCCH resource and the first valid PUSCH resource is determined based on at least one of the following:

[0020] In ascending order of time, a valid PUSCH resource is mapped to the last valid PUSCH resource preceding the first time interval before the valid PUSCH resource; or...

[0021] In ascending order of time, a valid PUCCH resource is mapped to the first valid PUSCH resource after the first time interval following the valid PUCCH resource; or...

[0022] In ascending order of time, a PUSCH resource is mapped to the last PUCCH resource preceding the first time interval before the PUSCH resource; or...

[0023] In ascending order of time, a PUCCH resource is mapped to the first PUSCH resource after the first time interval following the PUCCH resource.

[0024] According to another aspect of the embodiments of this application, a signal transmission method is provided, which is applied to a terminal device, wherein the method includes:

[0025] When a PUCCH is not sent on the first PUCCH resource:

[0026] When there is uplink control information (UCI) that overlaps in the time domain with the first PUSCH resource associated with the first PUCCH resource, a PUSCH carrying the UCI is transmitted on the first PUSCH resource; when there is no UCI that overlaps in the time domain with the first PUSCH resource, a PUSCH is not transmitted on the first PUSCH resource.

[0027] or,

[0028] Do not send PUSCH on the first PUSCH resource associated with the first PUCCH resource.

[0029] According to another aspect of the embodiments of this application, a signal transmitting device is provided, configured in a terminal device, wherein the device includes:

[0030] The transmitter, when it does not send a PUCCH on the first PUCCH resource:

[0031] When there is uplink control information (UCI) that overlaps in the time domain with the first PUSCH resource associated with the first PUCCH resource, a PUSCH carrying the UCI is transmitted on the first PUSCH resource; when there is no UCI that overlaps in the time domain with the first PUSCH resource, a PUSCH is not transmitted on the first PUSCH resource.

[0032] or,

[0033] Do not send PUSCH on the first PUSCH resource associated with the first PUCCH resource.

[0034] According to another aspect of the embodiments of this application, a signal transmission method is provided, which is applied to a terminal device, wherein the terminal device is configured with first report configuration information for a first report and second report configuration information for a second report, wherein the first report configuration information is configured on a first cell and the second report configuration information is configured on a second cell; wherein the method includes:

[0035] A transmitter that transmits a PUCCH on a PUCCH resource of the first cell if at least one of the triggering conditions in the first report and the second report is met;

[0036] A receiver that receives downlink control information (DCI) on either the first cell or the second cell, and a transmitter that transmits the first report and / or the second report on the PUSCH indicated by the DCI.

[0037] According to another aspect of the embodiments of this application, a signal transmitting apparatus is provided, configured in a terminal device, the terminal device being configured with first report configuration information for a first report and second report configuration information for a second report, wherein the first report configuration information is configured on a first cell, and the second report configuration information is configured on a second cell; wherein the apparatus includes:

[0038] A transmitter that transmits a PUCCH on a PUCCH resource of the first cell if at least one of the triggering conditions in the first report and the second report is met;

[0039] A receiver that receives downlink control information (DCI) on either the first cell or the second cell, and a transmitter that transmits the first report and / or the second report on the PUSCH indicated by the DCI.

[0040] One of the beneficial effects of the embodiments of this application is that the method provided by the embodiments of this application can ensure that the terminal device and the network device have a consistent understanding of the sending and receiving of reports, avoid uncertain device behavior during the sending and receiving of reports, and thus improve the reliability of report transmission.

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

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

[0043] 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

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

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

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

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

[0048] Figure 4 is a schematic diagram of a signal transmission method according to an embodiment of this application;

[0049] Figures 5 to 12 are schematic diagrams illustrating the mapping relationship between PUSCH resources and PUCCH resources in embodiments of this application;

[0050] Figure 13 is a schematic diagram of a signal transmission method according to an embodiment of this application;

[0051] Figure 14 is a schematic diagram of a signal transmission method according to an embodiment of this application;

[0052] Figure 15 is a schematic diagram of a signal transmission method according to an embodiment of this application;

[0053] Figure 16 is a schematic diagram of a multi-carrier scenario reporting configuration according to an embodiment of this application;

[0054] Figure 17 is a schematic diagram of a signal receiving method according to an embodiment of this application;

[0055] Figure 18 is a schematic diagram of a signal receiving method according to an embodiment of this application;

[0056] Figure 19 is a schematic diagram of a signal receiving method according to an embodiment of this application;

[0057] Figure 20 is a schematic diagram of a signal transmitting device according to an embodiment of this application;

[0058] Figure 21 is a schematic diagram of a signal receiving device according to an embodiment of this application;

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0080] Figure 2 is a schematic diagram of an event-driven report according to an embodiment of this application, referred to as Mode B. As shown in Figure 2, the first resource used to send the first message is a configured periodic PUCCH resource (only one period is shown in Figure 2 for simplicity), and the second resource used to send 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.

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

[0082] Conversely, if the terminal device does not detect an event, it may not send a first message. Without loss of generality, if the terminal device does not detect an event, it may also send a first message, but the content of the first message will be different from the previous one. In this case, the first message will notify the network device that there is no report transmission on the second resource associated with the first message.

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

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

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

[0086] In this embodiment, "report" refers to "event-driven report." "Event-driven" can be replaced with "UE-initiated" or "event-triggered." DCI can be replaced with PDCCH or uplink DCI. The uplink channel carrying the report (also known as a CSI report) is, for example, the Physical Uplink Shared Channel (PUSCH) or the Physical Uplink Control Channel (PUCCH). Report configuration information refers to the report configuration information for event-driven reports; PUCCH and PUSCH are used by the terminal device during the transmission of event-driven reports.

[0087] The following examples illustrate situations where a terminal device needs to send an event-driven report.

[0088] First aspect of the embodiments

[0089] This application provides a signal transmission method, specifically for mode B, described from the perspective of the terminal device.

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

[0091] 401. If the report meets the triggering conditions, send a PUCCH on the first valid PUCCH resource and send a PUSCH carrying the report on the first valid PUSCH resource associated with the first valid PUCCH resource.

[0092] The association between the first valid PUCCH resource and the first valid PUSCH resource is determined based on at least one of the following:

[0093] In ascending order of time, a valid PUSCH resource is mapped to the last valid PUSCH resource before the first time interval preceding the valid PUSCH resource; or...

[0094] In ascending order of time, a valid PUCCH resource is mapped to the first valid PUSCH resource after the first time interval following the valid PUCCH resource.

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

[0096] In some embodiments, the terminal device is configured with periodic Physical Uplink Control Channel (PUCCH) resources and periodic Physical Uplink Shared Channel (PUSCH) resources. For example, the network device configures a PUCCH resource (start position and length) via higher-layer RRC signaling, and simultaneously configures a period for this PUCCH resource. By configuring periodic PUCCH resources, the terminal device can quickly notify the network device using a specific PUCCH resource when a report needs to be sent. The configuration method for periodic PUSCH resources is similar to that of the aforementioned periodic PUCCH resources, and will not be repeated here. The periods of PUCCH resources and PUSCH resources can be the same or different, and this embodiment of the application does not limit this.

[0097] In some embodiments, only a portion of the periodic PUCCH resources and periodic PUSCH resources may be valid resources, while the other portion may be invalid resources.

[0098] A PUCCH resource is a valid PUCCH resource if it meets at least one of the following conditions:

[0099] PUCCH resources are not located before SSBs within a PUCCH time slot;

[0100] The time interval between the PUCCH resource and the last SSB symbol preceding it is greater than or equal to the first threshold;

[0101] The time interval between the PUCCH resource and the last downlink symbol preceding it is greater than or equal to the second threshold;

[0102] The PUCCH resource is located on the uplink symbol;

[0103] A PUSCH resource is a valid PUSCH resource if it meets at least one of the following conditions:

[0104] PUSCH resources are not located before SSBs within a PUSCH slot;

[0105] The time interval between a PUSCH resource and its last preceding SSB symbol is greater than or equal to the third threshold;

[0106] The time interval between the PUSCH resource and the last downlink symbol preceding it is greater than or equal to the fourth threshold;

[0107] The PUSCH resource is located on the uplink symbol.

[0108] For example, for periodic PUCCH resources, not every PUCCH resource (or PUCCH timing) within a period is a valid PUCCH resource. When downlink reception and uplink transmission on a PUCCH resource are close in time, due to the transition time from downlink to uplink or from uplink to downlink, the terminal device may not be able to transmit a PUCCH on the PUCCH resource; such a PUCCH resource is an invalid PUCCH resource. In other words, a valid PUCCH resource needs to maintain a sufficient time interval with downlink reception. When a PUCCH resource is located in an uplink symbol, this time interval can be naturally guaranteed through TDD configuration, therefore, the PUCCH resource is a valid PUCCH resource. When a PUCCH resource is located in a flexible symbol, if the PUCCH resource is not located before an SSB within a PUCCH slot, the time interval between it and the last SSB symbol preceding it is greater than or equal to a first threshold, and the time interval between it and the last downlink symbol preceding it is greater than or equal to that threshold, then the PUCCH resource is a valid PUCCH resource. Similarly, valid PUSCH resources can be determined.

[0109] For example, as mentioned above, effective resources are determined based on the SSB and / or downlink symbols, which in turn are determined based on the TDD configuration. Therefore, effective resources are determined based on the SSB and / or TDD configuration. When periodic PUCCH resources and periodic PUSCH resources are located on carriers CC0 and CC1, respectively, the SSB can include the SSB on CC0 and / or the SSB on CC1, and the TDD configuration can include the TDD configuration on CC0 and / or the TDD configuration on CC1. This is because CC0 and CC1 may each have their own SSB and / or their own TDD configuration.

[0110] In some embodiments, the terminal device needs to send event-driven reports. If a report meets the triggering conditions, the terminal device sends a PUCCH on a valid PUCCH resource (first valid PUCCH resource), and then sends the report on a valid PUSCH resource associated with that valid PUCCH resource (first valid PUSCH resource). The sent PUCCH is used to notify the network device that a report exists on that PUSCH resource; that is, a notification for the report is sent. There is a one-to-one mapping relationship between valid PUCCH resources and their associated valid PUSCH resources. The terminal device can be configured with periodic PUCCH resources and periodic PUSCH resources. Even if the PUCCH resources and PUSCH resources have the same period, the position of the valid PUCCH resource in the periodic PUCCH resource may be different from the position of the valid PUSCH resource in the periodic PUSCH resource.

[0111] Figure 5 is a schematic diagram of configuring periodic PUCCH resources according to an embodiment of this application. For example, as shown in Figure 5, PUCCH 1 and PUCCH 2 in the periodic PUCCH resources are both valid PUCCH resources, while PUSCH 1 in the periodic PUSCH resources is an invalid PUSCH resource, and PUSCH 2 is a valid PUSCH resource. Ensuring a one-to-one mapping relationship is necessary; otherwise, if both PUCCH 1 and PUCCH 2 in the figure are mapped to PUSCH 2, scheduling conflicts may occur. More specifically, suppose the terminal device has no report to send and therefore does not send a PUCCH on PUCCH 1. Since the network device did not receive a PUCCH on PUCCH 1, it can schedule other terminal device transmissions on PUSCH 2, which is associated with PUCCH 1. Suppose the terminal device has a report to send after PUCCH 1, the terminal device will send a PUCCH on PUCCH 2 and send a report on PUSCH 2. Thus, the report sent by the terminal device collides with other transmissions scheduled by the network device on PUSCH 2. Therefore, a one-to-one mapping must be guaranteed during the mapping process.

[0112] The following explains how to determine the one-to-one mapping between valid PUCCH resources and valid PUSCH resources.

[0113] In some embodiments, a valid PUSCH resource is mapped to the last valid PUCCH resource before the first time interval preceding the valid PUSCH resource, in ascending order of time. Specifically, for valid PUCCH resources and valid PUSCH resources with an association, different valid PUCCH resources are associated with different valid PUSCH resources.

[0114] In some embodiments, if the last valid PUCCH resource before the first time interval preceding a valid PUSCH resource has not been mapped, the valid PUSCH resource is mapped to that valid PUCCH resource; if the last valid PUCCH resource before the first time interval preceding a valid PUSCH resource has been mapped, the valid PUSCH resource is not mapped to any valid PUCCH resource.

[0115] Figures 6 to 8 are schematic diagrams illustrating the mapping relationship between valid PUSCH resources and valid PUCCH resources in embodiments of this application. For example, as shown in Figure 6, PUSCH 1 is invalid; PUCCH 2 is the last valid PUCCH resource in the first time interval preceding PUSCH 2, therefore PUSCH 2 is mapped to PUCCH 2, and so on; PUCCH 1 is not mapped to any valid PUSCH resource. For example, as shown in Figure 7, PUCCH 2 is invalid because the last valid PUCCH (PUCCH 1) in the first time interval preceding PUSCH 2 has already been mapped to PUSCH 1, therefore PUSCH 2 is not mapped to any valid PUCCH resource. For example, as shown in Figure 8, PUSCH 1 and PUCCH 2 are invalid because PUCCH 1 is the last valid PUCCH resource in the first time interval preceding PUSCH 2, therefore PUSCH 2 is mapped to PUCCH 1.

[0116] In some embodiments, in ascending order of time, a valid PUCCH resource is mapped to the first valid PUSCH resource after a first time interval following the mapping of the valid PUCCH resource. Specifically, for valid PUCCH resources and valid PUSCH resources with an association relationship, different valid PUCCH resources are associated with different valid PUSCH resources.

[0117] In some embodiments, if the first valid PUSCH resource after a first time interval following a valid PUCCH resource is not mapped, the valid PUCCH resource is mapped to the valid PUSCH resource; if the first valid PUSCH resource after a first time interval following a valid PUCCH resource has been mapped, the valid PUCCH resource is mapped to the next valid PUCCH resource.

[0118] Figure 9 is a schematic diagram of the mapping relationship between valid PUSCH resources and valid PUCCH resources in an embodiment of this application. As shown in Figure 9, PUSCH 1 is invalid; PUSCH 2 is the first valid PUCCH resource located in the first time interval after PUCCH 1, so PUCCH 1 is mapped to PUSCH 2, and so on.

[0119] It should be noted that, in the embodiments of this application, "before resource" can refer to the beginning position (symbol) of the resource or the beginning position of the time slot in which the resource is located. "After resource" can refer to the end position (symbol) of the resource or the end position of the time slot in which the resource is located.

[0120] In the above embodiments, the first time interval includes a first number of time units, the length of which is determined based on the subcarrier spacing of the PUCCH resource and / or the subcarrier spacing of the PUSCH resource.

[0121] In some embodiments, the time unit can be a symbol or a time slot, etc. Taking a symbol as an example, for instance, the first time interval includes X symbols, and the symbol length depends on the subcarrier spacing. Since PUCCH resources and PUSCH resources can be located on different carriers (CC, Component Carrier), different carriers can have different subcarrier spacings. The symbol length is determined based on the subcarrier spacing μ1 of the PUCCH, or the subcarrier spacing μ2 of the PUSCH, or the minimum of μ1 and μ2, or the maximum of μ1 and μ2. The carrier can also be replaced by a cell.

[0122] For example, the first quantity X is configured by the network device. For instance, the terminal device reports X1 based on its own device capabilities, and then the network device configures X for the terminal device. X can be equal to X1 or not equal to X1.

[0123] For example, the first quantity X is determined by the terminal device based on its own device capabilities. For instance, the terminal device reports X based on its own device capabilities and uses X.

[0124] For example, if X is 0, then there is no first time interval.

[0125] In some embodiments, within a second time interval, a valid PUSCH resource is mapped to the last valid PUCCH resource before the first time interval preceding the valid PUSCH resource, in ascending order of time; or, within a second time interval, a valid PUCCH resource is mapped to the first valid PUSCH resource after the first time interval following the valid PUCCH resource, in ascending order of time. The mapping method between the valid PUSCH resources and the valid PUCCH resources is the same in different second time intervals, that is, the above mapping relationship can be a periodic mapping.

[0126] Figures 10 to 12 are schematic diagrams illustrating the mapping relationship between valid PUSCH resources and valid PUCCH resources according to embodiments of this application. For example, within each second time interval, the mapping relationship between valid PUCCH resources and valid PUSCH resources is determined using the method described above. Let T represent the second time interval, which can also be replaced by a period T. Within the second time interval T, if there is no valid PUCCH resource satisfying the mapping condition before a valid PUSCH resource, then the valid PUSCH resource is not mapped to any valid PUCCH resource; similarly, if there is no valid PUSCH resource satisfying the mapping condition after a valid PUCCH resource, then the valid PUCCH resource is not mapped to any valid PUSCH resource. Without loss of generality, the following explanation only uses "the valid PUCCH resource being mapped to the first valid PUSCH resource after the first time interval following the valid PUCCH resource" as an example. For example, as shown in Figures 10, 11, or 12, the mapping operation of Figure 9 is performed within each second time interval T. Since the number of valid PUCCH resources and the number of valid PUSCH resources within T are not necessarily the same, it is possible that some valid PUCCH resources are not mapped to any valid PUSCH resources, or some valid PUSCH resources are not mapped to any valid PUCCH resources. Therefore, valid PUCCH resources and valid PUSCH resources are not mapped across periods T, which helps reduce the latency between the notification of sending a PUCCH bearer and the report of sending a PUSCH bearer.

[0127] In some embodiments, the second time interval T is indicated by signaling, or the second time interval T is determined according to at least one of the following:

[0128] The cycle of periodic PUCCH resources;

[0129] The cycle of periodic PUSCH resources;

[0130] Synchronization Signal Block (SSB) period;

[0131] Time Division Duplex (TDD) configuration cycle.

[0132] For example, the second time interval T is indicated by at least one of RRC signaling, MAC CE signaling, and DCI signaling.

[0133] For example, T is determined based on at least one of the periodic PUCCH resource period, the periodic PUSCH resource period, the SSB period, and the TDD configuration period. For example, the periodic PUCCH resource period is equal to the periodic PUSCH resource period. For example, the TDD configuration period is the period of the TDD uplink / downlink pattern configured by the common uplink / downlink time slot configuration tdd-UL-DL-ConfigurationCommon and / or the dedicated uplink / downlink time slot configuration tdd-UL-DL-ConfigurationDedicated. For example, the TDD configuration period is the period P of pattern 1 in tdd-UL-DL-ConfigurationCommon, or the TDD configuration period is the sum of P and the period P2 of pattern 2 in tdd-UL-DL-ConfigurationCommon, i.e., P+P2.

[0134] In some embodiments, the second time interval T satisfies at least one of the following first conditions:

[0135] The second time interval T is an integer multiple of the period of the periodic PUCCH resource;

[0136] The second time interval T is an integer multiple of the period of the periodic PUSCH resource;

[0137] The second time interval T is an integer multiple of the SSB period;

[0138] The second time interval T is an integer multiple of the TDD configuration period;

[0139] or,

[0140] The second time interval T is the minimum value of the time interval that satisfies at least one of the first conditions.

[0141] For example, when determining T, it is ensured that the valid PUCCH resource pattern is the same within each T, and the valid PUSCH resource pattern is also the same within each T, thus making the mapping identical within each T, which facilitates the maintenance of mapping relationships by terminal devices and network devices. Since the determination of "valid" depends on the relative position of PUCCH / PUSCH resources and SSB / downlink symbols in the time domain, setting T to an integer multiple of the PUCCH period, PUSCH period, SSB period, and TDD configuration period ensures that the relative positions are identical within each T, thus making the mapping identical within each T. Terminal devices can be configured with tdd-UL-DL-ConfigurationCommon under TDD (in which case the terminal device has a TDD configuration period) or not configured with tdd-UL-DL-ConfigurationCommon (in which case the terminal device does not have a TDD configuration period), therefore, the TDD configuration period may not exist. When the TDD configuration period does not exist, T is an integer multiple of the PUCCH period, PUSCH period, and SSB period.

[0142] For example, among multiple cycles that are integer multiples of the PUCCH cycle, PUSCH cycle, SSB cycle, and TDD configuration cycle, T is the smallest cycle. In other words, T is the least common multiple of the PUCCH cycle, PUSCH cycle, SSB cycle, and TDD configuration cycle. When the TDD configuration cycle does not exist, T is the least common multiple of the PUCCH cycle, PUSCH cycle, and SSB cycle.

[0143] For example, when periodic PUCCH resources and periodic PUSCH resources are located on carriers CC0 and CC1 respectively, the SSB period can include the SSB period on CC0 and / or the SSB period on CC1, and the TDD configuration period can include the TDD configuration period on CC0 and / or the TDD configuration period on CC1. This is because CC0 and CC1 may each have their own SSB and / or their own TDD configuration.

[0144] In some embodiments, valid PUSCH resources that are not mapped to valid PUCCH resources are not used to send reports, and / or valid PUCCH resources that are not mapped to valid PUSCH resources are not used to send notifications for reports.

[0145] For example, if a report meets the triggering condition, the terminal device sends a notification for the report on the first valid PUCCH resource, informing the network device that a report exists on the first valid PUSCH resource associated with that first valid PUCCH resource, and then sends the report on that first valid PUSCH resource. The first valid PUSCH resource associated with the first valid PUCCH resource can be determined based on the above mapping relationship. However, during the mapping determination process, a valid PUSCH resource may not be mapped to any valid PUCCH resource. Since the network device cannot be notified that a report exists on that valid PUSCH resource, the terminal device will not send a report on that valid PUSCH resource; conversely, a valid PUCCH resource may not be mapped to any valid PUSCH resource. Due to the lack of a valid PUSCH resource for sending reports, the terminal device will not send a notification for the report on that valid PUCCH resource.

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

[0147] Through the embodiments of this application, it can be ensured that terminal devices and network devices have a consistent understanding of the sending and receiving of reports, avoiding uncertain device behavior during the sending and receiving of reports, thereby improving the reliability of report transmission.

[0148] Second aspect of the embodiments

[0149] This application provides a signal transmission method, specifically for mode B, described from the perspective of the terminal device. Descriptions identical to those in the first aspect of the embodiment are omitted. In the first aspect of the embodiment, valid PUSCH resources and valid PUCCH resources are first determined, and then a mapping relationship is established between the valid PUSCH resources and the valid PUCCH resources. The difference from the first aspect of the embodiment is that in this application, the mapping relationship between PUSCH resources is determined first, and then the valid PUSCH resources and PUCCH resources are determined. Figure 13 is a schematic diagram of a signal transmission method according to an embodiment of this application. As shown in Figure 13, the method includes:

[0150] 1301. If the report meets the triggering conditions, send a PUCCH on the first valid PUCCH resource and send a PUSCH carrying the report on the first valid PUSCH resource associated with the first valid PUCCH resource.

[0151] The association between the first valid PUCCH resource and the first valid PUSCH resource is determined based on at least one of the following:

[0152] In ascending order of time, a PUSCH resource is mapped to the last PUCCH resource before the first time interval preceding the PUSCH resource; or...

[0153] In ascending order of time, a PUCCH resource is mapped to the first PUSCH resource after the first time interval following the PUCCH resource.

[0154] In some embodiments, for PUCCH resources and PUSCH resources that are associated, the association is a one-to-one mapping. Different valid PUCCH resources are associated with different valid PUSCH resources.

[0155] In some embodiments, within a second time interval, a PUSCH resource is mapped to the last PUCCH resource before the first time interval preceding the PUSCH resource, in ascending order of time; or, within a second time interval, a PUCCH resource is mapped to the first PUSCH resource after the first time interval following the PUCCH resource, in ascending order of time. The mapping method between the PUSCH resource and the PUCCH resource is the same in different second time intervals. Regarding the first time interval, the implementation of the second time interval is the same as in the embodiments of the first aspect, and will not be repeated here.

[0156] In some embodiments, the implementation of how to determine whether PUCCH resources and PUSCH resources are valid can be referred to the embodiments of the first aspect, and will not be repeated here.

[0157] Therefore, the difference between the above method and the embodiment of the first aspect is that the mapping is performed between PUCCH resources and PUSCH resources, that is, it is not necessary to consider whether PUCCH resources and PUSCH are valid during the mapping stage, thereby forming the following associations: (1) valid PUCCH resources are associated with valid PUSCH resources; (2) valid PUCCH resources are associated with invalid PUSCH resources; (3) invalid PUCCH resources are associated with valid PUSCH resources; (4) invalid PUCCH resources are associated with invalid PUSCH resources. Among them, the terminal device can only send notifications for reports on the valid PUCCH resources in association (1), and can only send reports on the valid PUSCH resources in association (1), that is, only association (1) is available. It is equivalent to performing mapping first and then determining whether it is valid. Only when both PUCCH resources and PUSCH resources constituting the one-to-one mapping are valid is the mapping available and can be used by the terminal device in the process of sending event-driven reports. (2)-(4) are not used to send the report, and / or are not used to send the PUCCH.

[0158] It is worth noting that Figure 13 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 13 above.

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

[0160] Through the embodiments of this application, it can be ensured that terminal devices and network devices have a consistent understanding of the sending and receiving of reports, avoiding uncertain device behavior during the sending and receiving of reports, thereby improving the reliability of report transmission.

[0161] Third aspect of the embodiments

[0162] This application provides a signal transmission method, specifically for mode B, described from the perspective of the terminal device. Descriptions identical to those in the first and second aspects are omitted. Figure 14 is a schematic diagram of a signal transmission method according to an embodiment of this application. As shown in Figure 14, the method includes:

[0163] 1401, When no PUCCH is sent on the first PUCCH resource:

[0164] When there is uplink control information (UCI) that overlaps in the time domain with the first PUSCH resource associated with the first PUCCH resource, a PUSCH carrying the UCI is transmitted on the first PUSCH resource; when there is no UCI that overlaps in the time domain with the first PUSCH resource, a PUSCH is not transmitted on the first PUSCH resource.

[0165] or,

[0166] Do not send PUSCH on the first PUSCH resource associated with the first PUCCH resource.

[0167] For example, if the report meets the triggering conditions, the terminal device sends a PUCCH on the first PUCCH resource and a PUSCH carrying the report on the first PUSCH resource associated with the first PUCCH resource. The terminal device may also not send a PUCCH on the first PUCCH resource; in this case, it needs to be determined whether the terminal device needs to send a PUSCH on the first PUSCH resource. This application embodiment does not limit the reasons why the terminal device does not send a PUCCH on the first PUCCH resource. For example, reasons may include the report not meeting the triggering conditions (i.e., there is no report that meets the triggering conditions), or the terminal device having other higher priority channels or signals to send simultaneously.

[0168] In some embodiments, if the terminal device does not send a PUCCH on the first PUCCH resource, the terminal device does not report the need to send on the first PUSCH resource. As one implementation, in this case, if the terminal device has a PUCCH or PUSCH carrying a UCI to send, and the PUCCH or PUSCH carrying the UCI overlaps with the first PUSCH resource in the time domain (partial or complete overlap), the terminal device multiplexes the UCI onto the PUSCH and sends it on the first PUSCH resource. If there is no PUCCH or PUSCH carrying a UCI that overlaps with the first PUSCH resource in the time domain (a UCI exists, but it does not overlap with the first PUSCH at all, or there is no UCI), the terminal device does not send the PUSCH on the first PUSCH resource, and the network device can use the PUSCH resource to schedule other terminal devices. As another implementation, in this case, the terminal device does not send the PUSCH on the first PUSCH resource. Thus, the terminal device and the network device have a consistent understanding regarding whether to send a report. When the terminal device does not send a report, the network device can use the PUSCH resource to schedule other terminal devices, thereby avoiding resource waste.

[0169] In some embodiments, the mapping relationship (association relationship) between PUSCH resources and PUCCH resources can be determined according to any relevant technology. This application embodiment does not limit this. For example, the mapping relationship can also be determined in the manner described in the first or second aspect embodiment, which will not be elaborated here.

[0170] In some embodiments, the first, second, and third aspects may be implemented individually or in combination, and will not be exemplified one by one here.

[0171] It is worth noting that Figure 14 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 14 above.

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

[0173] Through the embodiments of this application, it can be ensured that terminal devices and network devices have a consistent understanding of the sending and receiving of reports, avoiding uncertain device behavior during the sending and receiving of reports, thereby improving the reliability of report transmission.

[0174] Fourth aspect of the embodiment

[0175] This application provides a signal transmission method, specifically for mode A, described from the perspective of a terminal device. Figure 15 is a schematic diagram of a signal transmission method according to an embodiment of this application. As shown in Figure 15, the method includes:

[0176] 1501, if at least one of the triggering conditions in the first report and the second report is met, send a PUCCH on a PUCCH resource in the first cell;

[0177] 1502, Receive downlink control information (DCI) on either the first cell or the second cell, and transmit the first report and / or the second report on the PUSCH indicated by the DCI.

[0178] It is worth noting that Figure 15 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 15 above.

[0179] In some embodiments, the terminal device is configured with first report configuration information for a first report and second report configuration information for a second report. The first report configuration information is configured on a first cell, and the second report configuration information is configured on a second cell. That is, the terminal device receives the first report configuration information and the second report configuration information sent by the network device. This example only uses two report configuration information sets and two cells; the embodiments of this application do not limit this number. Cells can be replaced with carriers or component carriers.

[0180] Figure 16 is a schematic diagram of the configuration information of the configuration report in an embodiment of this application. For example, as shown in Figure 16, the configuration information of a report is configured through CSI-ReportConfig. In the case of carrier aggregation, the terminal device is configured with multiple carriers or cells or component carriers (CC). A carrier (CC0 or CC1) can be configured with one or more CSI-ReportConfigs. A carrier (CC2) may not be configured with CSI-ReportConfig. For example, the CSI-ReportConfig of CC2 is configured on CC0, or CC2 is not configured with event-driven reports, but only with network device scheduling reports. Therefore, CC2 is not configured with CSI-ReportConfig related to event-driven reports. The CSI-ReportConfig configured on CC0 and CC1 is associated with the periodic PUCCH resource configured on CC0. To achieve this association, for example, CSI-ReportConfig can be associated with the PUCCH resource ID and the carrier ID; or, for example, CSI-ReportConfig can be associated with the PUCCH resource ID and the PUCCH cell group ID, where the PUCCH cell group ID is used to identify the primary PUCCH cell group or the secondary PUCCH cell group.

[0181] In some embodiments, if any report configured by a CSI-ReportConfig meets the triggering condition, the terminal device transmits a PUCCH on a PUCCH resource. Upon receiving the PUCCH, the network device allocates PUSCH resources for reporting by transmitting a DCI. The DCI indicates a trigger state (or CSI trigger state) associated with one or more CSI-ReportConfigs; for example, the CSI-ReportConfigs associated with the trigger state include all CSI-ReportConfigs associated with periodic PUCCH resources. The terminal device receives the DCI and transmits one or more reports on the PUSCH scheduled by the DCI, the reports corresponding to at least one of the CSI-ReportConfigs associated with the trigger state.

[0182] In the presence of multiple control cells (CCs), it is necessary to determine which CC the DCI resides in. In this embodiment, the terminal device can receive the DCI on either the first cell or the second cell. That is, it can receive the DCI on any cell where reporting configuration information is configured. The terminal device will not receive the DCI on cells where reporting configuration information is not configured.

[0183] In some embodiments, on the one hand, the triggering state is configured on a carrier-by-carrier basis, and the triggering state configured on a certain carrier is associated with at least one CSI-ReportConfig on that carrier. On the other hand, after receiving the PUCCH, the network device cannot know which CSI-ReportConfig reports the terminal device wants to send, i.e., it cannot know which CSI-ReportConfig reports meet the triggering conditions. Considering the above two aspects, in order to trigger the reports corresponding to CSI-ReportConfigs on CC0 and / or CC1, the network device can send a DCI on CC0, indicating the triggering state configured on CC0, thereby triggering the terminal device to report the report corresponding to the CSI-ReportConfig associated with that triggering state; or, the network device can send a DCI on CC1, indicating the triggering state configured on CC1, thereby triggering the terminal device to report the report corresponding to the CSI-ReportConfig associated with that triggering state.

[0184] When a DCI is transmitted on a specific carrier, it indicates the triggering state on that carrier. Since CC2 is not configured with CSI-ReportConfig, it will not be configured with a triggering state independent of CC2 itself but only related to the CSI-ReportConfig of other CCs. Because CC2 is not configured with a triggering state related to the CSI-ReportConfig of event-driven reporting, the DCI transmitted on CC2 cannot indicate the triggering state associated with the CSI-ReportConfig on CC0 and / or CC1. Therefore, network devices will not transmit DCIs on CC2 to trigger reporting. Thus, the terminal device and network device have a consistent understanding of which carrier the DCI resides on, enabling successful report transmission and reception.

[0185] In some embodiments, a trigger state configured on a carrier can be associated not only with the CSI-ReportConfig on the same carrier but also with CSI-ReportConfig on other carriers. As shown in Figure 16, a trigger state configured on CC0 can be associated with a CSI-ReportConfig configured on CC1, and a trigger state configured on CC1 can be associated with a CSI-ReportConfig configured on CC0. For example, a trigger state can be associated with a report ID (CSI-ReportConfig ID) and a carrier ID (cell ID), meaning a trigger state is associated with one (report ID, carrier ID) tuple, and a trigger state can also be associated with multiple (report ID, carrier ID) tuples.

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

[0187] Through the embodiments of this application, the terminal device and the network device have a consistent understanding of which carrier the DCI is located on, thereby enabling the smooth transmission and reception of reports.

[0188] Fifth aspect of the embodiment

[0189] This application provides a signal receiving method, described from the perspective of a network device. The embodiments of the fifth 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.

[0190] Figure 17 is a schematic diagram of a signal receiving method according to an embodiment of this application. As shown in Figure 17, the method includes:

[0191] 1701, The receiving terminal device sends a PUCCH on the first valid PUCCH resource when the report meets the triggering condition, and sends a PUSCH carrying the report on the first valid PUSCH resource associated with the first valid PUCCH resource; the terminal device is configured with periodic physical uplink control channel (PUCCH) resources and periodic physical uplink shared channel (PUSCH) resources.

[0192] The association between the first valid PUCCH resource and the first valid PUSCH resource is determined based on at least one of the following:

[0193] In ascending order of time, a valid PUSCH resource is mapped to the last valid PUSCH resource before the first time interval preceding the valid PUSCH resource; or...

[0194] In ascending order of time, a valid PUCCH resource is mapped to the first valid PUSCH resource after the first time interval following the valid PUCCH resource; or...

[0195] In ascending order of time, a PUSCH resource is mapped to the last PUCCH resource before the first time interval preceding the PUSCH resource; or...

[0196] In ascending order of time, a PUCCH resource is mapped to the first PUSCH resource after the first time interval following the PUCCH resource.

[0197] It is worth noting that Figure 17 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 17 above.

[0198] In some embodiments, within a second time interval, a valid PUSCH resource is mapped to the last valid PUSCH resource preceding the first time interval in ascending order of time; or...

[0199] Within a second time interval, in ascending order of time, a valid PUCCH resource is mapped to the first valid PUSCH resource following the first time interval after the valid PUCCH resource; or...

[0200] Within a second time interval, in ascending order of time, a PUSCH resource is mapped to the last PUCCH resource preceding the first time interval; or...

[0201] Within a second time interval, in ascending order of time, a PUCCH resource is mapped to the first PUSCH resource after the first time interval following the PUCCH resource.

[0202] In some embodiments, the second time interval is indicated by signaling, or,

[0203] The second time interval is determined based on at least one of the following:

[0204] The cycle of periodic PUCCH resources;

[0205] The cycle of periodic PUSCH resources;

[0206] Synchronization Signal Block (SSB) period;

[0207] Time Division Duplex (TDD) configuration cycle.

[0208] In some embodiments, the second time interval satisfies at least one of the following first conditions:

[0209] The second time interval is an integer multiple of the period of the periodic PUCCH resource;

[0210] The second time interval is an integer multiple of the period of the periodic PUSCH resource;

[0211] The second time interval is an integer multiple of the SSB period;

[0212] The second time interval is an integer multiple of the TDD configuration period;

[0213] or,

[0214] The second time interval is the minimum value of the time interval that satisfies at least one of the first conditions.

[0215] In some embodiments, the mapping between valid PUSCH resources and valid PUCCH resources is the same in different second time intervals.

[0216] In some embodiments, the mapping between PUSCH resources and PUCCH resources is the same in different second time intervals.

[0217] In some embodiments, the first time interval includes a first number of time units, the length of which is determined based on the subcarrier spacing of the PUCCH resource and / or the subcarrier spacing of the PUSCH resource.

[0218] In some embodiments, if the last valid PUCCH resource before the first time interval preceding a valid PUSCH resource has not been mapped, the valid PUSCH resource is mapped to a valid PUCCH resource; if the last valid PUCCH resource before the first time interval preceding a valid PUSCH resource has already been mapped, the valid PUSCH resource is not mapped to any valid PUCCH resource; or...

[0219] If the first valid PUSCH resource after the first time interval following a valid PUCCH resource is not mapped, the valid PUCCH resource is mapped to a valid PUSCH resource. If the first valid PUSCH resource after the first time interval following a valid PUCCH resource has been mapped, the valid PUCCH resource is mapped to the next valid PUSCH resource.

[0220] In some embodiments, valid PUSCH resources that are not mapped to valid PUCCH resources are not used to send reports, and / or valid PUCCH resources that are not mapped to valid PUSCH resources are not used to send PUCCHs.

[0221] In some embodiments, for valid PUCCH resources and valid PUSCH resources that have an association relationship, the association relationship is a one-to-one mapping relationship.

[0222] In some embodiments, for PUCCH resources and PUSCH resources that are associated, the association is a one-to-one mapping relationship.

[0223] In some embodiments, for valid PUCCH resources and valid PUSCH resources that have an association relationship, different valid PUCCH resources are associated with different valid PUSCH resources.

[0224] In some embodiments, for PUCCH resources and PUSCH resources that are associated, different PUCCH resources are associated with different PUSCH resources.

[0225] In some embodiments, a PUCCH resource that meets at least one of the following conditions is a valid PUCCH resource:

[0226] PUCCH resources are not located before SSBs within a PUCCH time slot;

[0227] The time interval between the PUCCH resource and the last SSB symbol preceding it is greater than or equal to the first threshold;

[0228] The time interval between the PUCCH resource and the last downlink symbol preceding it is greater than or equal to the second threshold;

[0229] The PUCCH resource is located on the uplink symbol;

[0230] A PUSCH resource is a valid PUSCH resource if it meets at least one of the following conditions:

[0231] PUSCH resources are not located before SSBs within a PUSCH slot;

[0232] The time interval between a PUSCH resource and its last preceding SSB symbol is greater than or equal to the third threshold;

[0233] The time interval between the PUSCH resource and the last downlink symbol preceding it is greater than or equal to the fourth threshold;

[0234] The PUSCH resource is located on the uplink symbol.

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

[0236] Through the embodiments of this application, it can be ensured that terminal devices and network devices have a consistent understanding of the sending and receiving of reports, avoiding uncertain device behavior during the sending and receiving of reports, thereby improving the reliability of report transmission.

[0237] Implementation of the sixth aspect

[0238] This application provides a signal receiving method, described from the perspective of a network device. The embodiments of the sixth aspect can be combined with the embodiments of the third aspect, and the content identical to that in the embodiments of the third aspect will not be repeated.

[0239] Figure 18 is a schematic diagram of a signal receiving method according to an embodiment of this application. As shown in Figure 18, the method includes:

[0240] 1801, when no PUCCH is received on the first PUCCH resource:

[0241] When there is uplink control information (UCI) that overlaps in the time domain with the first PUSCH resource associated with the first PUCCH resource, the PUSCH carrying the UCI is received on the first PUSCH resource; when there is no UCI that overlaps in the time domain with the first PUSCH resource, the PUSCH is not received on the first PUSCH resource.

[0242] or,

[0243] Do not receive PUSCH on the first PUSCH resource associated with the first PUCCH resource.

[0244] It is worth noting that Figure 18 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 18 above.

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

[0246] Through the embodiments of this application, it can be ensured that terminal devices and network devices have a consistent understanding of the sending and receiving of reports, avoiding uncertain device behavior during the sending and receiving of reports, thereby improving the reliability of report transmission.

[0247] Seventh aspect of the embodiment

[0248] This application provides a signal receiving method, described from the perspective of a network device. The embodiments of the seventh aspect can be combined with the embodiments of the fourth aspect, and the content identical to that in the embodiments of the fourth aspect will not be repeated.

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

[0250] 1901, Send the first report configuration information of the first report and the second report configuration information of the second report to the terminal device, wherein the first report configuration information is configured on the first cell and the second report configuration information is configured on the second cell;

[0251] 1902, receive PUCCH on a PUCCH resource in the first cell;

[0252] In 1903, it also sends downlink control information (DCI) on either the first cell or the second cell, and receives a first report and / or a second report on the PUSCH indicated by the DCI.

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

[0254] In some embodiments, network devices do not receive DCI on cells that are not configured to report configuration information.

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

[0256] Through the embodiments of this application, the terminal device and the network device have a consistent understanding of which carrier the DCI is located on, thereby enabling the smooth transmission and reception of reports.

[0257] Eighth aspect of the embodiment

[0258] This application provides a signal transmitting device. This device may be, for example, a terminal device, or one or more components or parts configured within a terminal device; details identical to those in the embodiments of the first to seventh aspects will not be repeated.

[0259] Figure 20 is a schematic diagram of a signal transmitting device according to an embodiment of this application. As shown in Figure 20, the signal transmitting device 2000 includes a transmitter 2001.

[0260] In some embodiments, when the report meets the triggering condition, the transmitter 2001 transmits a PUCCH on the first valid PUCCH resource and transmits a PUSCH carrying the report on the first valid PUSCH resource associated with the first valid PUCCH resource.

[0261] The association between the first valid PUCCH resource and the first valid PUSCH resource is determined based on at least one of the following:

[0262] In ascending order of time, a valid PUSCH resource is mapped to the last valid PUSCH resource before the first time interval preceding the valid PUSCH resource; or...

[0263] In ascending order of time, a valid PUCCH resource is mapped to the first valid PUSCH resource after the first time interval following the valid PUCCH resource; or...

[0264] In ascending order of time, a PUSCH resource is mapped to the last PUCCH resource before the first time interval preceding the PUSCH resource; or...

[0265] In ascending order of time, a PUCCH resource is mapped to the first PUSCH resource after the first time interval following the PUCCH resource.

[0266] In some embodiments, within a second time interval, a valid PUSCH resource is mapped to the last valid PUSCH resource preceding the first time interval in ascending order of time; or...

[0267] Within a second time interval, in ascending order of time, a valid PUCCH resource is mapped to the first valid PUSCH resource following the first time interval after the valid PUCCH resource; or...

[0268] Within a second time interval, in ascending order of time, a PUSCH resource is mapped to the last PUCCH resource preceding the first time interval; or...

[0269] Within a second time interval, in ascending order of time, a PUCCH resource is mapped to the first PUSCH resource following the first time interval after the PUCCH resource.

[0270] In some embodiments, the second time interval is indicated by signaling, or,

[0271] The second time interval is determined based on at least one of the following:

[0272] The cycle of periodic PUCCH resources;

[0273] The cycle of periodic PUSCH resources;

[0274] Synchronization Signal Block (SSB) period;

[0275] Time Division Duplex (TDD) configuration cycle.

[0276] In some embodiments, the second time interval satisfies at least one of the following first conditions:

[0277] The second time interval is an integer multiple of the period of the periodic PUCCH resource;

[0278] The second time interval is an integer multiple of the period of the periodic PUSCH resource;

[0279] The second time interval is an integer multiple of the SSB period;

[0280] The second time interval is an integer multiple of the TDD configuration period;

[0281] or,

[0282] The second time interval is the minimum value of the time interval that satisfies at least one of the first conditions.

[0283] In some embodiments, the mapping between valid PUSCH resources and valid PUCCH resources is the same in different second time intervals.

[0284] In some embodiments, the mapping between PUSCH resources and PUCCH resources is the same in different second time intervals.

[0285] In some embodiments, the first time interval includes a first number of time units, the length of which is determined based on the subcarrier spacing of the PUCCH resource and / or the subcarrier spacing of the PUSCH resource.

[0286] In some embodiments, if the last valid PUCCH resource before the first time interval preceding a valid PUSCH resource has not been mapped, the valid PUSCH resource is mapped to a valid PUCCH resource; if the last valid PUCCH resource before the first time interval preceding a valid PUSCH resource has already been mapped, the valid PUSCH resource is not mapped to any valid PUCCH resource; or...

[0287] If the first valid PUSCH resource after the first time interval following a valid PUCCH resource is not mapped, the valid PUCCH resource is mapped to a valid PUSCH resource. If the first valid PUSCH resource after the first time interval following a valid PUCCH resource has been mapped, the valid PUCCH resource is mapped to the next valid PUSCH resource.

[0288] In some embodiments, valid PUSCH resources that are not mapped to valid PUCCH resources are not used to send reports, and / or valid PUCCH resources that are not mapped to valid PUSCH resources are not used to send PUCCHs.

[0289] In some embodiments, for valid PUCCH resources and valid PUSCH resources that have an association relationship, the association relationship is a one-to-one mapping relationship.

[0290] In some embodiments, for PUCCH resources and PUSCH resources that are associated, the association is a one-to-one mapping relationship.

[0291] In some embodiments, for valid PUCCH resources and valid PUSCH resources that have an association relationship, different valid PUCCH resources are associated with different valid PUSCH resources.

[0292] In some embodiments, for PUCCH resources and PUSCH resources that are associated, different PUCCH resources are associated with different PUSCH resources.

[0293] In some embodiments, a PUCCH resource that meets at least one of the following conditions is a valid PUCCH resource:

[0294] PUCCH resources are not located before SSBs within a PUCCH time slot;

[0295] The time interval between the PUCCH resource and the last SSB symbol preceding it is greater than or equal to the first threshold;

[0296] The time interval between the PUCCH resource and the last downlink symbol preceding it is greater than or equal to the second threshold;

[0297] The PUCCH resource is located on the uplink symbol;

[0298] A PUSCH resource is a valid PUSCH resource if it meets at least one of the following conditions:

[0299] PUSCH resources are not located before SSBs within a PUSCH slot;

[0300] The time interval between a PUSCH resource and its last preceding SSB symbol is greater than or equal to the third threshold;

[0301] The time interval between the PUSCH resource and the last downlink symbol preceding it is greater than or equal to the fourth threshold;

[0302] The PUSCH resource is located on the uplink symbol.

[0303] In other embodiments, when the transmitter 2101 does not transmit a PUCCH on the first PUCCH resource:

[0304] When there is uplink control information (UCI) that overlaps in the time domain with the first PUSCH resource associated with the first PUCCH resource, a PUSCH carrying the UCI is transmitted on the first PUSCH resource; when there is no UCI that overlaps in the time domain with the first PUSCH resource, a PUSCH is not transmitted on the first PUSCH resource.

[0305] or,

[0306] Do not send PUSCH on the first PUSCH resource associated with the first PUCCH resource.

[0307] In other embodiments, the terminal device is configured with first report configuration information for a first report and second report configuration information for a second report, wherein the first report configuration information is configured on a first cell and the second report configuration information is configured on a second cell; wherein, as shown in FIG20, the signal transmitting device 2000 further includes a receiver 2002.

[0308] If at least one of the triggering conditions in the first report and the second report is met, the transmitter 2001 transmits a PUCCH on a PUCCH resource of the first cell;

[0309] Receiver 2002 receives downlink control information (DCI) on either the first cell or the second cell, and transmitter 2001 transmits a first report and / or a second report on the PUSCH indicated by the DCI.

[0310] In the above embodiment, the receiver 2002 does not receive the DCI on cells that are not configured with reporting configuration information.

[0311] 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 signal transmitting device 2000 may also include other components or modules, and for details regarding these components or modules, please refer to related technologies.

[0312] Furthermore, for simplicity, Figure 20 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.

[0313] Through the embodiments of this application, it can be ensured that terminal devices and network devices have a consistent understanding of the sending and receiving of reports, avoiding uncertain device behavior during the sending and receiving of reports, thereby improving the reliability of report transmission.

[0314] Through the embodiments of this application, the terminal device and the network device have a consistent understanding of which carrier the DCI is located on, thereby enabling the smooth transmission and reception of reports.

[0315] Ninth aspect of the embodiment

[0316] This application provides a signal 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 eighth aspects will not be repeated.

[0317] Figure 21 is a schematic diagram of a signal receiving device according to an embodiment of this application. As shown in Figure 21, the signal receiving device 2100 includes a receiver 2101.

[0318] In some embodiments, receiver 2101 receives a PUCCH transmitted by the terminal device on a first valid PUCCH resource when the report meets the triggering condition, and a PUSCH carrying the report transmitted on a first valid PUSCH resource associated with the first valid PUCCH resource; the terminal device is configured with periodic physical uplink control channel (PUCCH) resources and periodic physical uplink shared channel (PUSCH) resources.

[0319] The association between the first valid PUCCH resource and the first valid PUSCH resource is determined based on at least one of the following:

[0320] In ascending order of time, a valid PUSCH resource is mapped to the last valid PUSCH resource before the first time interval preceding the valid PUSCH resource; or...

[0321] In ascending order of time, a valid PUCCH resource is mapped to the first valid PUSCH resource after the first time interval following the valid PUCCH resource; or...

[0322] In ascending order of time, a PUSCH resource is mapped to the last PUCCH resource before the first time interval preceding the PUSCH resource; or...

[0323] In ascending order of time, a PUCCH resource is mapped to the first PUSCH resource after the first time interval following the PUCCH resource.

[0324] In other embodiments, when receiver 2101 does not receive a PUCCH on the first PUCCH resource:

[0325] When there is uplink control information (UCI) that overlaps in the time domain with the first PUSCH resource associated with the first PUCCH resource, the PUSCH carrying the UCI is received on the first PUSCH resource; when there is no UCI that overlaps in the time domain with the first PUSCH resource, the PUSCH is not received on the first PUSCH resource.

[0326] or,

[0327] Do not receive PUSCH on the first PUSCH resource associated with the first PUCCH resource.

[0328] In other embodiments, a transmitter 2102 may also be included, which sends first report configuration information of a first report and second report configuration information of a second report to a terminal device, wherein the first report configuration information is configured on a first cell and the second report configuration information is configured on a second cell.

[0329] Receiver 2201 receives PUCCH on a PUCCH resource in the first cell;

[0330] Transmitter 2202 also transmits downlink control information (DCI) on either the first cell or the second cell, and receiver 2201 receives a first report and / or a second report on the PUSCH indicated by the DCI.

[0331] 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 signal receiving device 2100 may also include other components or modules, and for details regarding these components or modules, please refer to related technologies.

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

[0333] Through the embodiments of this application, it can be ensured that terminal devices and network devices have a consistent understanding of the sending and receiving of reports, avoiding uncertain device behavior during the sending and receiving of reports, thereby improving the reliability of report transmission.

[0334] Through the embodiments of this application, the terminal device and the network device have a consistent understanding of which carrier the DCI is located on, thereby enabling the smooth transmission and reception of reports.

[0335] Tenth aspect embodiment

[0336] 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 ninth aspects will not be repeated.

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

[0338] The terminal equipment includes the aforementioned signal transmitting device 2000, and the network equipment includes the aforementioned signal receiving device 2100. Repeated details will not be repeated.

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

[0340] Figure 22 is a schematic diagram of a terminal device according to an embodiment of this application. As shown in Figure 22, the terminal device 2200 may include a processor 2210 and a memory 2220; the memory 2220 stores data and programs and is coupled to the processor 2210. 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.

[0341] For example, processor 2210 can be configured to execute a program to implement the signal transmission method as described in the embodiments of the first to fourth aspects.

[0342] As shown in Figure 22, the terminal device 2200 may further include: a communication module 2230, an input unit 2240, a display 2250, and a power supply 2260. 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 2200 does not necessarily include all the components shown in Figure 22; these components are not essential. Furthermore, the terminal device 2200 may also include components not shown in Figure 22, which can be referred to in the prior art.

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

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

[0345] For example, processor 2310 may be configured to execute a program to implement the signal receiving method as described in the embodiments of aspects five to seven.

[0346] In addition, as shown in Figure 23, network device 2300 may also include: transceiver 2340 and antenna 2350, 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 2300 does not necessarily have to include all the components shown in Figure 23; in addition, network device 2300 may also include components not shown in Figure 23, which can be referred to in the prior art.

[0347] 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 signal transmission method described in the first to fourth embodiments.

[0348] This application also provides a storage medium storing a computer program, wherein the computer program causes a terminal device to execute the signal transmission method described in the first to fourth embodiments.

[0349] 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 signal receiving method described in the embodiments of the fifth to seventh aspects.

[0350] This application also provides a storage medium storing a computer program, wherein the computer program causes a network device to perform the signal receiving method described in the embodiments of the fifth to seventh aspects.

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

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

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

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

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

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

[0357] 1. A signal receiving device, configured in a network device, wherein the device comprises:

[0358] A receiver receives a PUCCH transmitted on a first valid PUCCH resource by a terminal device when a report meets a triggering condition, and a PUSCH carrying the report transmitted on a first valid PUSCH resource associated with the first valid PUCCH resource; the terminal device is configured with periodic physical uplink control channel (PUCCH) resources and periodic physical uplink shared channel (PUSCH) resources.

[0359] The association between the first valid PUCCH resource and the first valid PUSCH resource is determined according to at least one of the following:

[0360] In ascending order of time, a valid PUSCH resource is mapped to the last valid PUSCH resource preceding the first time interval before the valid PUSCH resource; or...

[0361] In ascending order of time, a valid PUCCH resource is mapped to the first valid PUSCH resource after the first time interval following the valid PUCCH resource; or...

[0362] In ascending order of time, a PUSCH resource is mapped to the last PUCCH resource preceding the first time interval before the PUSCH resource; or...

[0363] In ascending order of time, a PUCCH resource is mapped to the first PUSCH resource after the first time interval following the PUCCH resource.

[0364] 2. A signal receiving device, configured in a network device, wherein the device comprises:

[0365] When the receiver does not receive a PUCCH on the first PUCCH resource:

[0366] When there is uplink control information (UCI) that overlaps in the time domain with the first PUSCH resource associated with the first PUCCH resource, the PUSCH carrying the UCI is received on the first PUSCH resource; when there is no UCI that overlaps in the time domain with the first PUSCH resource, the PUSCH is not received on the first PUSCH resource.

[0367] or,

[0368] PUSCH is not received on the first PUSCH resource associated with the first PUCCH resource.

[0369] 3. A signal receiving device, configured in a network device, wherein the device comprises:

[0370] A transmitter that sends first report configuration information of a first report and second report configuration information of a second report to a terminal device, wherein the first report configuration information is configured on a first cell and the second report configuration information is configured on a second cell;

[0371] The receiver receives a PUCCH on a PUCCH resource in the first cell;

[0372] The transmitter also transmits downlink control information (DCI) on either the first cell or the second cell, and the receiver receives the first report and / or the second report on the PUSCH indicated by the DCI.

[0373] 4. A signal transmission method applied to a terminal device, the terminal device being configured with periodic physical uplink control channel (PUCCH) resources and periodic physical uplink shared channel (PUSCH) resources, wherein the method includes:

[0374] If the report meets the triggering conditions, a PUCCH is sent on the first valid PUCCH resource, and a PUSCH carrying the report is sent on the first valid PUSCH resource associated with the first valid PUCCH resource.

[0375] The association between the first valid PUCCH resource and the first valid PUSCH resource is determined according to at least one of the following:

[0376] In ascending order of time, a valid PUSCH resource is mapped to the last valid PUSCH resource preceding the first time interval before the valid PUSCH resource; or...

[0377] In ascending order of time, a valid PUCCH resource is mapped to the first valid PUSCH resource after the first time interval following the valid PUCCH resource; or...

[0378] In ascending order of time, a PUSCH resource is mapped to the last PUCCH resource preceding the first time interval before the PUSCH resource; or...

[0379] In ascending order of time, a PUCCH resource is mapped to the first PUSCH resource after the first time interval following the PUCCH resource.

[0380] 5. A signal transmission method applied to a terminal device, wherein the method comprises:

[0381] When a PUCCH is not sent on the first PUCCH resource:

[0382] When there is uplink control information (UCI) that overlaps in the time domain with the first PUSCH resource associated with the first PUCCH resource, a PUSCH carrying the UCI is transmitted on the first PUSCH resource; when there is no UCI that overlaps in the time domain with the first PUSCH resource, a PUSCH is not transmitted on the first PUSCH resource.

[0383] or,

[0384] Do not send PUSCH on the first PUSCH resource associated with the first PUCCH resource.

[0385] 6. A signal transmission method applied to a terminal device, the terminal device being configured with first report configuration information for a first report and second report configuration information for a second report, wherein the first report configuration information is configured on a first cell, and the second report configuration information is configured on a second cell; wherein the method comprises:

[0386] If at least one of the triggering conditions in the first report and the second report is met, a PUCCH is sent on a PUCCH resource of the first cell;

[0387] Receive downlink control information (DCI) on either the first cell or the second cell, and transmit the first report and / or the second report on the PUSCH indicated by the DCI.

[0388] 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 the signal transmission method as described in any one of Appendices 4 to 6.

[0389] 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 the signal receiving method as described in any one of Appendices 1 to 3.

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

[0391] 10. A computer program product comprising at least a computer program that, when executed by a processor, causes a network device to perform a signal receiving method as described in any one of Appendices 1 to 3.

Claims

1. A signal transmitting apparatus configured in a terminal device, the terminal device being configured with periodic physical uplink control channel (PUCCH) resources and periodic physical uplink shared channel (PUSCH) resources, wherein, The device includes: The transmitter, when the report meets the triggering conditions, sends a PUCCH on a first valid PUCCH resource and sends a PUSCH carrying the report on a first valid PUSCH resource associated with the first valid PUCCH resource; The association between the first valid PUCCH resource and the first valid PUSCH resource is determined according to at least one of the following: In ascending order of time, a valid PUSCH resource is mapped to the last valid PUSCH resource preceding the first time interval before the valid PUSCH resource; or... In ascending order of time, a valid PUCCH resource is mapped to the first valid PUSCH resource after the first time interval following the valid PUCCH resource; or... In ascending order of time, a PUSCH resource is mapped to the last PUCCH resource preceding the first time interval before the PUSCH resource; or... In ascending order of time, a PUCCH resource is mapped to the first PUSCH resource after the first time interval following the PUCCH resource.

2. The apparatus according to claim 1, wherein, Within a second time interval, in ascending order of time, a valid PUSCH resource is mapped to the last valid PUSCH resource preceding the first time interval before the valid PUSCH resource; or... Within a second time interval, in ascending order of time, a valid PUCCH resource is mapped to the first valid PUSCH resource following the first time interval after the valid PUCCH resource; or... Within a second time interval, in ascending order of time, a PUSCH resource is mapped to the last PUCCH resource preceding the first time interval; or... Within a second time interval, in ascending order of time, a PUCCH resource is mapped to the first PUSCH resource following the first time interval after the PUCCH resource.

3. The apparatus according to claim 2, wherein, The second time interval is indicated by signaling, or, The second time interval is determined according to at least one of the following: The periodicity of the periodic PUCCH resource; The periodicity of the periodic PUSCH resource; Synchronization Signal Block (SSB) period; Time Division Duplex (TDD) configuration cycle.

4. The apparatus according to claim 2, wherein, The second time interval satisfies at least one of the following first conditions: The second time interval is an integer multiple of the period of the periodic PUCCH resource; The second time interval is an integer multiple of the period of the periodic PUSCH resource; The second time interval is an integer multiple of the SSB period; The second time interval is an integer multiple of the TDD configuration period; or, The second time interval is the minimum value of the time interval that satisfies at least one of the first conditions.

5. The apparatus according to claim 2, wherein, The mapping method between the valid PUSCH resource and the valid PUCCH resource is the same in different second time intervals.

6. The apparatus according to claim 2, wherein, The mapping method between the PUSCH resource and the PUCCH resource is the same in different second time intervals.

7. The apparatus according to claim 1, wherein, The first time interval includes a first number of time units, the length of which is determined based on the subcarrier spacing of the PUCCH resource and / or the subcarrier spacing of the PUSCH resource.

8. The apparatus according to claim 1 or 2, wherein, When the last valid PUCCH resource before the first time interval before a valid PUSCH resource has not been mapped, the valid PUSCH resource is mapped to the valid PUCCH resource; when the last valid PUCCH resource before the first time interval before a valid PUSCH resource has been mapped, the valid PUSCH resource is not mapped to any valid PUCCH resource. or, When the first valid PUSCH resource after the first time interval following a valid PUCCH resource is not mapped, the valid PUCCH resource is mapped to the valid PUSCH resource; when the first valid PUSCH resource after the first time interval following a valid PUCCH resource has been mapped, the valid PUCCH resource is mapped to the next valid PUSCH resource.

9. The apparatus according to claim 1, wherein, A valid PUSCH resource that is not mapped to a valid PUCCH resource is not used to send the report, and / or a valid PUCCH resource that is not mapped to a valid PUSCH resource is not used to send the PUCCH.

10. The apparatus according to claim 1, wherein, For valid PUCCH resources and valid PUSCH resources that have an association relationship, the association relationship is a one-to-one mapping relationship.

11. The apparatus according to claim 1, wherein, For PUCCH and PUSCH resources that are associated, the association is a one-to-one mapping relationship.

12. The apparatus according to claim 1, wherein, For valid PUCCH resources and valid PUSCH resources that are associated, different valid PUCCH resources are associated with different valid PUSCH resources.

13. The apparatus according to claim 1, wherein, For PUCCH and PUSCH resources that are related, different PUCCH resources are associated with different PUSCH resources.

14. The apparatus according to claim 1, wherein, A PUCCH resource is a valid PUCCH resource if it meets at least one of the following conditions: PUCCH resources are not located before SSBs within a PUCCH time slot; The time interval between the PUCCH resource and the last SSB symbol preceding it is greater than or equal to the first threshold; The time interval between the PUCCH resource and the last downlink symbol preceding it is greater than or equal to the second threshold; The PUCCH resource is located on the uplink symbol; A PUSCH resource is a valid PUSCH resource if it meets at least one of the following conditions: PUSCH resources are not located before SSBs within a PUSCH slot; The time interval between a PUSCH resource and its last preceding SSB symbol is greater than or equal to the third threshold; The time interval between the PUSCH resource and the last downlink symbol preceding it is greater than or equal to the fourth threshold; The PUSCH resource is located on the uplink symbol.

15. The apparatus according to claim 1, wherein, When no PUCCH is sent on the first valid PUCCH resource: When there is uplink control information (UCI) that overlaps with the first valid PUSCH resource in the time domain, the transmitter transmits a PUSCH carrying the UCI on the first valid PUSCH resource; when there is no UCI that overlaps with the first valid PUSCH resource in the time domain, the transmitter does not transmit a PUSCH on the first valid PUSCH resource. or, The transmitter does not send PUSCH on the first valid PUSCH resource.

16. A signal transmitting device, configured in a terminal device, wherein, The device includes: The transmitter, when it does not send a PUCCH on the first PUCCH resource: When uplink control information (UCI) exists that overlaps in the time domain with the first PUSCH resource associated with the first PUCCH resource, a PUSCH carrying the UCI is transmitted on the first PUSCH resource; when no uplink control information (UCI) exists that overlaps in the time domain with the first PUSCH resource, a PUSCH carrying the UCI is transmitted on the first PUSCH resource; When the first PUSCH resource overlaps with a UCI in the time domain, PUSCH is not sent on the first PUSCH resource. or, Do not send PUSCH on the first PUSCH resource associated with the first PUCCH resource.

17. A signal transmitting device, configured in a terminal device, the terminal device being configured with first report configuration information for a first report and second report configuration information for a second report, wherein... The first report configuration information is configured on the first cell, and the second report configuration information is configured on the second cell; wherein, the device includes: A transmitter that transmits a PUCCH on a PUCCH resource of the first cell if at least one of the triggering conditions in the first report and the second report is met; A receiver that receives downlink control information (DCI) on either the first cell or the second cell, and a transmitter that transmits the first report and / or the second report on the PUSCH indicated by the DCI.

18. The apparatus according to claim 17, wherein, The receiver does not receive the DCI on cells that are not configured with reporting configuration information.

Images