Uplink data sending method and apparatus

Abstract

The embodiments of the present application provide an uplink data sending method and apparatus, the apparatus being configured in a terminal device, and the apparatus comprising: a determination unit, which determines a PUCCH set within a slot, the PUCCH set comprising a reference PUCCH and one or more PUCCHs overlapping the reference PUCCH within the slot, and the reference PUCCH being a PUCCH having repetitions; among the PUCCHs comprised in the PUCCH set, one PUCCH is a PUCCH carrying first information, the other PUCCHs being PUCCHs carrying HARQ-ACK, SR, CSI or the first information, and the first information being used for notifying a network device that a terminal device has a report to be sent; a sending unit, wherein, within the slot, the sending unit selects a PUCCH from the PUCCH set for sending according to a priority order of information carried by the PUCCH, and the priority order comprises: a priority of the first information being greater than a priority of the CSI, and / or the priority of the first information being less than a priority of the HARQ-ACK, and / or the priority of the first information being equal to a priority of the SR.

Description

Uplink data transmission method and apparatus 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] Rel-19 will introduce event-driven reporting (also known as event-triggered reporting or end-device-initiated reporting). More specifically, it will introduce further enhancements to CSI reporting, namely support for event-driven CSI reporting. Event-driven CSI reporting corresponds to traditional CSI reporting.

[0005] 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. Summary of the Invention

[0006] The inventors discovered that Rel-19 introduces a new Uplink Control Information type (UCI type) for event-driven reporting, called Request or Notification (RN) information, or simply RN. As a new uplink control information type introduced for event-driven reporting, RN is used to notify network devices that terminal devices have a report to send. A problem to be solved is how to determine which UCIs (one or more) to send when an RN-type UCI overlaps with other types of UCIs in the time domain, or when a PUCCH carrying an RN overlaps with other PUCCHs in the time domain. Overlapping situations include: a PUCCH carrying an RN overlapping with a PUCCH that has duplicates, or a PUCCH carrying HARQ-ACK and / or CSI with a certain PUCCH format.

[0007] To address at least one of the above-mentioned problems, embodiments of this application provide an uplink data transmission method and apparatus.

[0008] According to one aspect of the embodiments of this application, an uplink data transmission method is provided, the method comprising:

[0009] The terminal device determines a set of PUCCHs within a time slot. The set of PUCCHs includes a reference PUCCH and one or more PUCCHs that overlap with the reference PUCCH within the time slot. The reference PUCCH is a PUCCH with repetition. Among the PUCCHs included in the set of PUCCHs, one PUCCH is a PUCCH carrying first information, and the other PUCCHs are PUCCHs carrying HARQ-ACK, SR, CSI, or the first information, which is used to notify the network device that the terminal device has a report to send.

[0010] Within the time slot, the terminal device selects a PUCCH from the PUCCH set and sends it according to the priority order of the information carried by the PUCCH;

[0011] The priority order includes: the priority of the first information is greater than the priority of the CSI, and / or the priority of the first information is less than the priority of the HARQ-ACK, and / or the priority of the first information is equal to the priority of the SR.

[0012] According to another aspect of the embodiments of this application, an uplink data transmission apparatus is provided, configured in a terminal device, the apparatus comprising:

[0013] A determining unit determines a set of PUCCHs within a time slot. The set of PUCCHs includes a reference PUCCH and one or more PUCCHs that overlap with the reference PUCCH within the time slot. The reference PUCCH is a PUCCH with repetition. Among the PUCCHs included in the set of PUCCHs, one PUCCH is a PUCCH carrying first information, and the other PUCCHs are PUCCHs carrying HARQ-ACK, SR, CSI, or the first information, which is used to notify the network device that the terminal device has a report to send.

[0014] The transmitting unit selects a PUCCH from the PUCCH set and transmits it according to the priority order of the information carried by the PUCCH within the time slot.

[0015] The priority order includes: the priority of the first information is greater than the priority of the CSI, and / or the priority of the first information is less than the priority of the HARQ-ACK, and / or the priority of the first information is equal to the priority of the SR.

[0016] According to one aspect of the embodiments of this application, an uplink data transmission method is provided, the method comprising:

[0017] The terminal device determines that a first number of first PUCCHs carrying first information and a second number of second PUCCHs carrying SR overlap with a third PUCCH carrying second information in the time domain;

[0018] The terminal device sends an indication information to the network device, the indication information indicating one or both of the first number of first information and the second number of SRs;

[0019] The first information is used to notify the network device that the terminal device has a report to send, and the first number of first information items are arranged in ascending order according to the PUCCH resource identifier.

[0020] According to another aspect of the embodiments of this application, an uplink data transmission apparatus is provided, configured in a terminal device, the apparatus comprising:

[0021] The determining unit determines that a first number of first PUCCHs carrying first information and a second number of second PUCCHs carrying SR overlap with a third PUCCH carrying second information in the time domain;

[0022] A sending unit that sends indication information to a network device, the indication information indicating one or both of the first number of first messages and the second number of SRs;

[0023] The first information is used to notify the network device that the terminal device has a report to send, and the first number of first information items are arranged in ascending order according to the PUCCH resource identifier.

[0024] According to one aspect of the embodiments of this application, an uplink data transmission method is provided, the method comprising:

[0025] When any one of the reports associated with a first PUCCH carrying first information meets the triggering condition, the terminal device sends the first PUCCH and sends a PUSCH associated with the first PUCCH, the PUSCH carrying one of the reports that meet the triggering condition.

[0026] Before the first time point t1, each report associated with the first PUCCH occupies 1 CPU; after the first time point t1, each report associated with the first PUCCH occupies 1 CPU; the first time point t1 is not earlier than the end time of the first PUCCH in the time domain.

[0027] According to one aspect of the embodiments of this application, an uplink data transmission apparatus is provided, configured in a terminal device, the apparatus comprising:

[0028] The sending unit sends the first PUCCH and a PUSCH associated with the first PUCCH when any one of the reports in one or more reports associated with the first PUCCH carrying the first information meets the triggering condition. The PUSCH carries one of the reports that meet the triggering condition.

[0029] Before the first time point t1, each report associated with the first PUCCH occupies 1 CPU; after the first time point t1, each report associated with the first PUCCH occupies 1 CPU; the first time point t1 is not earlier than the end time of the first PUCCH in the time domain.

[0030] One of the beneficial effects of the embodiments of this application is that, through the uplink data transmission method and apparatus provided in the embodiments of this application, on the one hand, when the PUCCH carrying the RN overlaps with other PUCCHs, the terminal device and the network device can reach a common understanding on which PUCCH is being transmitted, thereby avoiding ambiguity and the resulting PUCCH transmission failure; on the other hand, the number of CPUs can be counted more accurately, so that the remaining available CPUs can be allocated to other reports as needed, thereby achieving more efficient utilization of the CPU.

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

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

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

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

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

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

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

[0038] Figure 4 is a schematic diagram of an uplink data transmission method according to an embodiment of this application;

[0039] Figures 5 to 8 are schematic diagrams of some scenarios for uplink data transmission;

[0040] Figure 9 is another schematic diagram of the uplink data transmission method according to an embodiment of this application;

[0041] Figures 10 and 11 are schematic diagrams of some scenarios for uplink data transmission;

[0042] Figure 12 is another schematic diagram of the uplink data transmission method according to an embodiment of this application;

[0043] Figure 13 is a schematic diagram of an uplink data transmission scenario;

[0044] Figure 14 is another schematic diagram of the uplink data receiving method according to an embodiment of this application;

[0045] Figure 15 is another schematic diagram of the uplink data receiving method according to an embodiment of this application;

[0046] Figure 16 is another schematic diagram of the uplink data receiving method according to an embodiment of this application;

[0047] Figure 17 is a schematic diagram of an uplink data transmission device according to an embodiment of this application;

[0048] Figure 18 is another schematic diagram of the uplink data transmission device according to an embodiment of this application;

[0049] Figure 19 is another schematic diagram of the uplink data transmission device according to an embodiment of this application;

[0050] Figure 20 is another schematic diagram of the uplink data receiving device according to an embodiment of this application;

[0051] Figure 21 is another schematic diagram of the uplink data receiving device according to an embodiment of this application;

[0052] Figure 22 is a schematic diagram of a terminal device according to an embodiment of this application. Detailed Implementation

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0070] Furthermore, 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." Additionally, 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 uplink data carried by the PUSCH.

[0071] In this application embodiment, the terminal device needs to send event-driven reports on certain time-frequency resources. The determination of resources requires corresponding information interaction. For example, the terminal device can send a first message to request dynamically scheduled resources or notify whether semi-statically configured resources are actually used.

[0072] 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 information 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.

[0073] 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 information (first resource) by sending a first message, and then sends a report on the associated second resource.

[0074] Conversely, if the terminal device does not detect an event, it may not send the first message. Without loss of generality, if the terminal device does not detect an event, it may also send the 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.

[0075] 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 for sending the first information is a configured periodic PUCCH resource (only one resource is shown), and the second resource for sending the event-driven report is a PDCCH (or DCI) scheduled resource.

[0076] 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 first information on the first resource. Then, it receives the PDCCH and sends the report on the second resource scheduled by the PDCCH. The report can be carried by either PUSCH or PUCCH, and the first information is carried by PUCCH. Here, "resources" refers to time-frequency resources.

[0077] In this embodiment, as shown in Figures 2 and 3, the first information is used to notify the network device that a report transmission exists on the PUSCH associated with the first information (Mode B), or to request the PUSCH resources required to send the report from the network device (Mode A). In general, the first information is used to notify the network device that the terminal device has a report to send. After sending the PUCCH carrying the first information, the terminal device will send the report on the PUSCH. This PUSCH is configured by RRC signaling (Mode B) or scheduled by PDCCH (Mode A). For simplicity, in this embodiment, this PUSCH is referred to as the PUSCH associated with the PUCCH.

[0078] In this embodiment, the event that triggers the report is not limited. For example, an event could be that the measurement (L1-RSRP) of a new beam (one of RS1 to RSN) is higher than the measurement of the current beam by a certain value, or an event could be that the measurement of the current beam is lower than a certain value, i.e., corresponding to different types of events. In other words, the triggering condition for event (event 1) is that the measurement of a new beam is higher than the measurement of the current beam by a certain threshold, and the event occurs when the triggering condition is met; or, the triggering condition for event (event 2) is that the measurement of the current beam is lower than a certain threshold, and the event occurs when the triggering condition is met. The terminal device can be configured with different types of events, for example, it can be configured to send reports triggered by event 1 and reports triggered by event 2. A report is associated with an event, and the terminal device sends the report when the event occurs.

[0079] In the embodiments of this application, "event occurrence" can be referred to as an event meeting the triggering condition, or as an event being triggered, or as a report meeting the triggering condition. The embodiments of this application do not limit the content of the report. For example, the report includes a reference signal index and measurements based on that reference signal; the report may include one or more reference signal indices and measurements. The report is used to report beam information, its purpose being to report the beam and measurements for that beam; the report can also be replaced by a beam report. A new beam can also be replaced by a candidate beam. "The measurements of the new beam are higher than the measurements of the current beam" means that the measurements of the reference signal associated with the new beam are higher than the measurements of the reference signal associated with the current beam; it can also be referred to as "the new beam is better than the current beam," or "the quality of the new beam is better than / better than the current beam." "Higher than" can also be replaced by "greater than or equal to." "Lower than" can also be replaced by "less than or equal to."

[0080] 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. The PUCCH carrying the first information and the PUSCH carrying the report are both used by the terminal device during the transmission of the event-driven report.

[0081] In this embodiment, a report is associated with a report configuration (i.e., report configuration information), and the two can be interchanged. The parameters, modules, or components shown in the figures are not limited to appearing simultaneously; some parameters, modules, or components may also be present.

[0082] In the embodiments of this application, for ease of explanation, the information carried by the PUCCH used in the event-driven report is referred to as the first information, or as the information for request or notification (RN), or simply as RN.

[0083] In this embodiment, the PUCCH carries UCIs, which can be of different types. For example, HARQ-ACK, SR, RN, and CSI are four different UCI types. Therefore, it can also be said that the PUCCH carries different UCI types.

[0084] In the embodiments of this application, a PUCCH can be transmitted in more than one time slot (e.g., repeatedly transmitted), which is referred to as a PUCCH with repetition, or PUCCH repetition, or PUCCH repeated transmission. A PUCCH can be transmitted in one time slot. For ease of distinction, a PUCCH transmitted in one time slot is referred to as a PUCCH without repetition, or a non-repetitive PUCCH. A non-repetitive PUCCH is transmitted using one time slot, while a repetitive PUCCH is transmitted using multiple time slots. PUCCH generally refers to a non-repetitive PUCCH or a PUCCH repetition.

[0085] The embodiments of this application will now be described with reference to the accompanying drawings.

[0086] First aspect of the embodiments

[0087] This application provides a method for transmitting uplink data, which will be described from the perspective of the terminal device.

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

[0089] 401. The terminal device determines a set of PUCCHs within a time slot. The set of PUCCHs includes a reference PUCCH and one or more PUCCHs that overlap with the reference PUCCH within the time slot. The reference PUCCH is a PUCCH with repetition. Among the PUCCHs included in the PUCCH set, one PUCCH is a PUCCH carrying first information, and the other PUCCHs are PUCCHs carrying HARQ-ACK, SR, CSI, or the first information, which is used to notify the network device that the terminal device has a report to send.

[0090] 402. Within the aforementioned time slot, the terminal device selects a PUCCH from the aforementioned PUCCH set for transmission according to the priority order of the information carried by the PUCCH.

[0091] The above priority order includes: the priority of the first message is greater than the priority of the CSI, and / or the priority of the first message is less than the priority of the HARQ-ACK, and / or the priority of the first message is equal to the priority of the SR.

[0092] For example, the same UCI (or PUCCH) is transmitted through multiple time slots, each time slot being used to transmit a copy of the UCI (PUCCH). The PUCCH carrying this UCI is called a repeating PUCCH, or a PUCCH duplicate. A repeating PUCCH may overlap in the time domain with one or more PUCCHs within one or more time slots. Here, "one or more PUCCHs" can be repeating PUCCHs or non-repeating PUCCHs (also called non-repeating PUCCHs). In a time slot where there is overlap with a repeating PUCCH, one of the repeating PUCCHs is used as the reference PUCCH. Within that time slot, among the reference PUCCH and the PUCCHs overlapping with it, one PUCCH carries an RN (first information), and the other PUCCHs can carry any UCI type, for example, the other PUCCHs carry at least one of HARQ-ACK, SR, CSI, or RN. Within this time slot, the terminal device selects the PUCCH with the highest priority of UCI type from the reference PUCCH and the PUCCHs overlapping with the reference PUCCH for transmission. The priority order of UCI types is HARQ-ACK > SR = RN > higher priority CSI > lower priority CSI.

[0093] In the above embodiments, the priority of RN is lower than the priority of HARQ-ACK, but higher than the priority of CSI. The relationship between the priorities of RN and SR can also be determined in other ways; in some embodiments, the priority of RN is higher than the priority of SR; in other embodiments, the priority of RN is lower than the priority of SR.

[0094] In the above example, the priority comparison between CSIs can be determined based on existing technologies. For details, please refer to the relevant basics, which will not be elaborated here.

[0095] According to the above embodiments, if there is a duplicate PUCCH and a PUCCH that overlaps with the duplicate PUCCH in a time slot, the terminal device selects one PUCCH to send according to priority. Thus, when the PUCCH carrying the RN overlaps with other PUCCHs, the terminal device and the network device can reach a common understanding on which PUCCH should be sent, thereby avoiding ambiguity and the resulting PUCCH transmission failure.

[0096] In some embodiments, the reference PUCCH is the PUCCH with the highest priority carrying information among multiple repeating PUCCHs within a time slot; and / or, the reference PUCCH is the PUCCH with the earliest start symbol among multiple repeating PUCCHs within a time slot.

[0097] For example, in a time slot that overlaps with multiple PUCCHs (which may or may not overlap), the terminal device designates one of the PUCCHs with overlapping PUCCHs as the reference PUCCH. The reference PUCCH has the earliest start symbol among the multiple PUCCHs with overlapping PUCCHs and / or the highest priority. For example, the start symbol refers to the start symbol of the PUCCH resource within a time slot. For example, the priority order may follow the UCI type priority order described above.

[0098] In the above embodiments, among the multiple repeating PUCCHs in the above time slot, if there are multiple repeating PUCCHs with the earliest start symbol, the reference PUCCH can be the repeating PUCCH with the earliest start symbol and the longest duration.

[0099] For example, as mentioned earlier, the terminal device determines the reference PUCCH based on the PUCCH with the earliest start symbol among multiple repeating PUCCHs. However, if there are multiple repeating PUCCHs with the earliest start symbol, the reference PUCCH is the PUCCH with the longest duration among these multiple PUCCHs. For example, duration refers to the length of time of the PUCCH resource within a time slot.

[0100] In some embodiments, any two PUCCHs in the reference PUCCH and one or more PUCCHs overlapping the reference PUCCH carry information with different priorities, or carry information with the same priority but starting in different time slots.

[0101] For example, in a time slot that overlaps with a repeating PUCCH, the following restrictions apply to both the reference PUCCH and the PUCCH overlapping with it: any two PUCCHs carry UCIs with different priorities, or any two PUCCHs carry UCIs with the same priority but starting in different time slots. For example, if the PUCCH is a repeating PUCCH and occupies time slots 1, 2, and 3, then "the starting time slot of the PUCCH" refers to time slot 1, i.e., the starting time slot of the entire repeating PUCCH. For example, the priority is the priority of the UCI type described above. For example, network devices ensure that the above restrictions are met when scheduling PUCCHs.

[0102] In some embodiments, in the reference PUCCH and one or more PUCCHs overlapping the reference PUCCH, the terminal device does not expect more than one PUCCH to carry information with the same priority and to start in the same time slot.

[0103] For example, the aforementioned restrictions of "any two PUCCHs carrying information with different priorities" and "carrying information with the same priority but starting in different time slots" can also be described as follows: the terminal device does not expect more than one PUCCH to carry information with the same priority and start in the same time slot. In other words, "more than one PUCCH carrying information with the same priority and starting in the same time slot" is considered an error condition. Network devices should avoid this error condition when scheduling PUCCHs.

[0104] In some embodiments, among the reference PUCCH and one or more PUCCHs overlapping with the reference PUCCH, the terminal device selects the PUCCH with the highest priority carrying the information for transmission.

[0105] For example, in a time slot that overlaps with a PUCCH that has duplicates, the terminal device selects the PUCCH with the highest priority carrying the UCI for transmission from the reference PUCCH and the PUCCH that overlaps with the reference PUCCH.

[0106] In some embodiments, if there are multiple PUCCHs with the highest priority carrying information among the reference PUCCH and one or more PUCCHs overlapping with the reference PUCCH, the terminal device selects the PUCCH with the earliest start time slot among the highest priority PUCCHs for transmission.

[0107] For example, as mentioned above, the terminal device selects the PUCCH with the highest priority of the UCI it carries for transmission. However, there are multiple PUCCHs with the highest priority of the UCI they carry. In this case, the terminal device selects the PUCCH with the earliest start time slot from these multiple PUCCHs for transmission.

[0108] The following example illustrates the complete operation process of the terminal device described above.

[0109] For example, suppose a terminal device needs to send N1 (N1≥1) first PUCCHs and N2 (N2≥1) second PUCCHs, where the first PUCCHs are PUCCH repetitions and the second PUCCHs are either non-repetition PUCCHs or PUCCH repetitions. The N1 first PUCCHs and N2 second PUCCHs overlap in the time domain, assuming this overlap occurs over S time slots. Among the N1 first PUCCHs and N2 second PUCCHs, at least one PUCCH carries an RN (first information), and the other PUCCHs carry HARQ-ACK, SR, CSI, or RN. For each of the S time slots, the terminal device performs the following steps.

[0110] Step 1: The terminal device determines a reference PUCCH, which is a repeating PUCCH.

[0111] For example, if multiple PUCCH repetitions overlap within a time slot, the terminal device selects one of the PUCCH repetitions as the reference PUCCH. For instance, the terminal device selects one PUCCH repetition as the reference PUCCH according to a first rule and / or a second rule.

[0112] The first rule is that, among multiple PUCCH repetitions, the terminal device selects the PUCCH repetition with the highest priority of UCI type as the reference PUCCH. In other words, the UCI type carried by the reference PUCCH has the highest priority. The priority of UCI types, from high to low, is HARQ-ACK > SR = RN > CSI. Among multiple CSIs, the higher priority CSI > the lower priority CSI. For example, the priority definition of CSI can be found in related technologies. SR includes regular SR and / or Link Recovery Request (LRR). Therefore, the priority order of UCI types can also be written as HARQ-ACK > SR = RN > higher priority CSI > lower priority CSI. For UCI types other than RN, the priority of different UCI types is different. For RN, its UCI type priority is the same as SR. The priority of UCI type can also be simply referred to as priority.

[0113] The second rule includes: In multiple PUCCH repetitions, the terminal device selects the PUCCH repetition with the earliest start symbol as the reference PUCCH; if the start symbols are the same, the terminal device selects the PUCCH repetition with the longest duration as the reference PUCCH. For example, the start symbol is determined according to the startingSymbolIndex in PUCCH-Config. For example, "earliest start symbol" means the earliest start symbol within a time slot. For example, the duration is determined according to nrofSymbols in PUCCH-Config. For example, "longest duration" means the longest duration within a time slot. For example, the terminal device determines the reference PUCCH only according to the second rule. For example, the terminal device determines the reference PUCCH according to the first rule; if the terminal device cannot determine a unique reference PUCCH according to the first rule, then the terminal device determines the reference PUCCH according to the second rule.

[0114] Step 2: The terminal device determines one or more third PUCCHs that overlap with the reference PUCCH, wherein the third PUCCH is a non-repeating PUCCH or a PUCCH repetition.

[0115] Step 3: The terminal device selects one of the reference PUCCH and the third PUCCH (all third PUCCHs determined in Step 2) to send.

[0116] For example, among multiple PUCCHs from the reference PUCCH and the third PUCCH, any two PUCCHs may either carry UCI types with different priorities, or carry UCI types with the same priority but starting in different time slots. It is impossible for two PUCCHs to carry UCI types with the same priority and start in the same time slot. In other words, the terminal device does not expect the following situation: multiple PUCCHs from the reference PUCCH and the third PUCCH carry UCI types with the same priority and start in the same time slot. Network devices should avoid this situation during scheduling, or the above situation should be considered an error. When determining the starting time slot of a PUCCH, if the PUCCH is a repeating PUCCH, the starting time slot refers to the starting time slot of the entire repeating PUCCH; if the PUCCH is a non-repeating PUCCH, the starting time slot is the time slot where the non-repeating PUCCH is located. In summary, among multiple PUCCHs from the reference PUCCH and the third PUCCH, there cannot be multiple PUCCHs with the same priority UCI type and the same starting time slot.

[0117] For example, among multiple PUCCHs from the reference PUCCH and the third PUCCH, the terminal device sends the PUCCH with the highest priority of type UCI. As mentioned earlier, the terminal device determines which PUCCH to send for each of the S time slots.

[0118] For example, among multiple PUCCHs from the reference PUCCH and the third PUCCH, if there are multiple PUCCHs of the highest priority UCI type, the terminal device sends the PUCCH with the earliest start time slot among the highest priority PUCCHs.

[0119] Step 4: The terminal device repeats steps 1 to 3 until there is no PUCCH overlap with the PUCCH repetition in the time slot.

[0120] Figure 5 is a schematic diagram of an uplink data transmission scenario.

[0121] As shown in Figure 5, assuming CSI uses PUCCH repetition for transmission, while SR and RN do not, the situation shown in Figure 5 is not allowed. As shown in Figure 5, time slot 1 overlaps with PUCCH repetition. The analysis of time slot 1 is as follows: Since CSI uses PUCCH repetition, it is determined as the reference PUCCH. Since both SR and RN overlap with CSI, the terminal device needs to select the highest priority among CSI, SR, and RN for transmission. However, SR and RN have the same priority and start from the same time slot, which does not meet the constraint in step 3 that "there are no multiple PUCCHs of the same UCI type with the same priority and starting time slot." Therefore, the situation shown in Figure 5 is not allowed, and network devices should avoid this situation during scheduling.

[0122] Figure 6 is a schematic diagram of another scenario for uplink data transmission.

[0123] As shown in Figure 6, the SR uses PUCCH repetition for transmission, while the RN does not. Time slot 2 overlaps with PUCCH repetition; the analysis of time slot 2 is as follows: Since the SR uses PUCCH repetition, it is determined as the reference PUCCH. Because the RN and SR overlap, the terminal device needs to select the one with the highest priority between the RN and SR for transmission. Since the RN and SR have the same priority, the terminal device further selects the SR with the earlier starting time slot for transmission. This is because the SR uses PUCCH repetition, and the starting time slot of the PUCCH repetition is time slot 1, which is earlier than the starting time slot of the RN (time slot 2). Therefore, the terminal device transmits the SR in time slot 1 and the SR in time slot 2.

[0124] Figure 7 is a schematic diagram of another scenario of uplink data transmission.

[0125] As shown in Figure 7, CSI is transmitted using PUCCH repetition, while RN is not. Time slot 1 overlaps with PUCCH repetition; the analysis of time slot 1 is as follows: Since CSI uses PUCCH repetition, it is determined as the reference PUCCH. Because RN overlaps with CSI, the terminal device needs to choose the one with the highest priority between RN and CSI for transmission. Since RN has a higher priority than CSI, the terminal device chooses RN for transmission. Therefore, the terminal device transmits RN in time slot 1 and CSI in time slot 2.

[0126] Figure 8 is a schematic diagram of another scenario of uplink data transmission.

[0127] As shown in Figure 8, both CSI and SR are transmitted using PUCCH repetition, while RN is not. Time slot 2 overlaps with PUCCH repetition; the analysis of time slot 2 is as follows: Both CSI and SR use PUCCH repetition, but the start symbol of SR is earlier than that of CSI, therefore SR is determined as the reference PUCCH. Since CSI and SR overlap, the terminal device needs to select the one with the highest priority between CSI and SR for transmission. Since SR has a higher priority than CSI, the terminal device selects SR for transmission. Since RN and SR do not overlap, both can be transmitted. Therefore, the terminal device transmits SR in time slot 1, SR and RN in time slot 2, and CSI in time slot 3.

[0128] The above examples illustrate the uplink data transmission method of this application.

[0129] In some embodiments, the above-mentioned SR includes a first SR and a second SR, and the priority order further includes:

[0130] The priority of the first SR is lower than the priority of HARQ-ACK but higher than the priority of the first message; and / or,

[0131] The priority of the second SR is lower than the priority of the first information but higher than the priority of the CSI.

[0132] In the above embodiments, the first SR can be an SR for link recovery requests, which can be called LRR, and the second SR can be an SR for ordinary scheduling requests, which can be called a regular SR.

[0133] For example, in the presence of a first SR and a second SR, the above priority order "HARQ-ACK>SR=RN>CSI" can be replaced with "HARQ-ACK>LRR>RN>Regular SR>CSI". The terminal device uses this priority order "HARQ-ACK>LRR>RN>Regular SR>CSI" when performing the steps described above, and all other operations are the same as before.

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

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

[0136] Through the embodiments of this application, when the PUCCH carrying the RN overlaps with a PUCCH that has repetition, the terminal device and the network device can reach a common understanding as to which PUCCH is being sent, thereby avoiding ambiguity and the resulting PUCCH transmission failure.

[0137] Second aspect of the embodiments

[0138] This application provides an uplink data transmission method, which will be described from the perspective of the terminal device. The description of the same content as in the first aspect embodiment is omitted.

[0139] In the embodiments of this application, for a PUCCH used for SR, if the terminal device sends an SR on the PUCCH, it is called a positive SR; if the terminal device does not send an SR on the PUCCH, it is called a negative SR. For a PUCCH used for RN, if the terminal device sends an RN on the PUCCH, it is called a positive RN; if the terminal device does not send an SR on the PUCCH, it is called a negative RN.

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

[0141] 901, The terminal device determines that a first number of first PUCCHs carrying first information and a second number of second PUCCHs carrying SR overlap with a third PUCCH carrying second information in the time domain;

[0142] 902, The terminal device sends an indication message to the network device, the indication message indicating one or both of the first number of first messages and the second number of SRs;

[0143] The first message is used to notify the network device or terminal device that there is a report to send, and the first number of first messages are arranged in ascending order according to the PUCCH resource identifier.

[0144] For example, for K1 (K1≥0) PUCCHs carrying SRs and K2 (K2>0) PUCCHs carrying RNs, which overlap in the time domain with PUCCHs carrying HARQ-ACK and / or CSI, the SRs and RNs use PUCCH format 0 or 1, and the HARQ-ACK and / or CSIs use PUCCH format 2, 3, or 4. The terminal device sends the indication information, along with the HARQ-ACK and / or CSI information, to the network device. For example, the terminal device redetermines the appropriate PUCCH format and PUCCH resources based on the total number of information bits and sends all bits of information via PUCCH. One of the K1 SRs and K2 RNs is indicated as positive by the indication information, or two of the K1 SRs and K2 RNs (e.g., one SR and one RN) are indicated as positive by the indication information. Regardless of whether one or both of the K1 SRs and K2 RNs are indicated as positive, the K2 RNs are arranged in ascending order of PUCCH resource identifiers. Without loss of generality, "ascending order" can also be replaced with "descending order". "The indication information indicates one or both of K1 SRs and K2 RNs" includes: the terminal device is configured with K1 SR resources (i.e., PUCCH resources) and K2 RN resources (i.e., PUCCH resources), but the terminal device needs to send SRs on L1 (L1≤K1) SR resources and needs to send RNs on L2 (L2≤K2) RN resources. In this case, "one or both indicated by the indication information" is generated from L1 SRs and L2 RNs.

[0145] In the above embodiments, when the indication information indicates one of a first number of first information and a second number of SRs, the first number of first information and the second number of SRs can be arranged in ascending order of PUCCH resource identifiers, or the second number of SRs can be arranged in ascending order of scheduling request resource identifiers, and the first number of first information can be arranged in ascending order of PUCCH resource identifiers. The arranged SRs and the arranged first information are then concatenated.

[0146] Figure 10 is a schematic diagram of an uplink data transmission scenario.

[0147] As shown in Figure 10, SR1, SR2, RN1, and RN2 overlap with HARQ-ACK, where HARQ-ACK(O ACK The terminal device transmits (bits) using one of PUCCH format 2, PUCCH format 3, or PUCCH format 4. The terminal device is configured with K1 (K1=2) SRs and K2 (K2=2) RNs, meaning K1+K2 PUCCHs are configured for the SRs and RNs. The terminal device will... Bits appended to O ACK For each bit, one of PUCCH format 2, PUCCH format 3, and PUCCH format 4 is used for transmission. Bit. For An additional bit, all zeros, indicates that none of the K1+K2 PUCCHs were sent, meaning that both the K1+K2 SRs and RNs were negative SRs and negative RNs. A non-zero value indicates which of the K1+K2 PUCCHs was sent, meaning it indicates either a positive SR or a positive RN among the K1+K2 SRs and RNs. In other words, Each additional bit can indicate K1+K2+1 states. A value of all zeros indicates that all K1+K2 SRs and RNs are negative, while a non-zero value indicates that one of the K1+K2 SRs and RNs is positive. That is, the terminal device selects one of the K1+K2 SRs and RNs to indicate positive. To achieve this functionality, the correspondence between the non-zero values ​​of the additional bits and the K1+K2 PUCCHs needs to be clearly defined. The non-zero values ​​of the additional bits correspond to the K1+K2 SRs and RNs arranged in a certain order, in ascending order. Therefore, determining the order of the K1+K2 SRs and RNs is a problem that needs to be solved.

[0148] According to the embodiments of this application, since each SR or RN is associated with a PUCCH resource ID, that is, with a PUCCH-ResourceId, K1+K2 SRs and RNs can be arranged in ascending order of PUCCH-ResourceId. As shown in Figure 10, the terminal device is configured with K1=2 SRs and K2=2 RNs, and the K1+K2 SRs and RNs are arranged in ascending order of PUCCH-ResourceId as RN1, RN2, SR1, SR2; the additional bits include In the bit representation, "000" indicates that both SRs and both RNs are negative, "001" indicates that only RN1 is positive, "010" indicates that only RN2 is positive, "011" indicates that only SR1 is positive, and "100" indicates that only SR2 is positive. "In ascending order" can also be replaced with "in descending order", which is "in descending order".

[0149] Furthermore, according to the embodiments of this application, since each SR is associated with an SR resource ID, that is, associated with a schedulingRequestResourceId, K1 SRs can be arranged in ascending order of schedulingRequestResourceId; since each RN is associated with a PUCCH resource ID, that is, associated with a PUCCH-ResourceId, K2 RNs can be arranged in ascending order of PUCCH-ResourceId; finally, the K2 arranged RNs are placed after the K1 arranged SRs to obtain K1+K2 arranged SRs and RNs.

[0150] As shown in Figure 10, the terminal device is configured with K1 = 2 SRs and K2 = 2 RNs. According to the method described above, K1 + K2 SRs and RNs are arranged as SR1, SR2, RN1, and RN2. Additional bits include... In the bitwise AND operation, "000" indicates that both SRs and RNs are negative, "001" indicates that only SR1 is positive, "010" indicates that only SR2 is positive, "011" indicates that only RN1 is positive, and "100" indicates that only RN2 is positive. Without loss of generality, "placing K2 arranged RNs after K1 arranged SRs" can be replaced with "placing K2 arranged RNs before K1 arranged SRs." Similarly, "arranging K1 SRs in ascending order of schedulingRequestResourceId" can be replaced with "arranging K1 SRs in ascending order of PUCCH-ResourceId."

[0151] In the above embodiments, if the indication information indicates a first piece of information, the first piece of information may have the highest priority among a first number of first pieces of information.

[0152] For example, if the terminal device needs to select one indication as positive from K1+K2 SRs and RNs, the terminal device selects according to priority, choosing the highest priority indication as positive. SRs include LRRs and regular SRs, and their priority, in descending order, is LRR>RN>regular SR. If the terminal device needs to select one RN indication as positive from multiple RNs, the terminal device selects according to the RN priority, choosing the highest priority RN.

[0153] For example, "the first message has the highest priority among the first messages of the first quantity" includes: the first message has the highest priority among the triggered first messages of the first quantity. A terminal device is configured with K2 RN resources (i.e., PUCCH resources), but the terminal device may only need to send RNs on L2 (L2≤K2) RN resources, meaning the L2 RNs are the triggered RNs among the K2 RNs. This is because a report associated with an RN may not meet the triggering conditions, therefore there is no need to send that RN. For RNs that do not need to be sent (i.e., untriggered RNs), their priority is not considered, or the untriggered RNs are considered to have the lowest priority. If a report associated with an RN meets the triggering conditions, that RN is called a triggered RN. When the terminal device needs to indicate one of the K2 RNs, the terminal device indicates the RN with the highest priority among the L2 triggered RNs. For the K2-L2 untriggered RNs, their priority is considered the lowest, or the untriggered RNs are not considered when determining and comparing priorities.

[0154] In the above embodiments, the priority of the first information can be determined according to at least one of the following:

[0155] The priority of reports sent in one or more reports associated with the PUCCH carrying the first information;

[0156] The PUCCH resource identifier associated with the PUCCH carrying the first information;

[0157] The event type of the report associated with the PUCCH carrying the first information.

[0158] For example, the priority of an RN is determined based on the priority of reports sent from one or more reports associated with the PUCCH carrying the RN. An RN (the PUCCH carrying the RN) can be associated with one or more event-driven reports; any report that meets a trigger condition will trigger the terminal device to send the RN. The terminal device selects one report from the reports that meet the trigger condition to send on the PUSCH. Therefore, the priority of the RN is equal to the priority of the report sent on the PUSCH.

[0159] Figure 11 is a schematic diagram of another scenario for uplink data transmission.

[0160] As shown in Figure 11, an RN (PUCCH) is associated with Report 1, Report 2, and Report 3. Assuming all three reports meet the triggering conditions, and the terminal device selects Report 1 for transmission, the priority of the RN is equal to the priority R1 of Report 1. When the terminal device needs to select one RN from multiple RNs to indicate positive, it determines the priority of each RN in the manner described above and selects the RN with the highest priority. For example, if the terminal device selects the highest priority report (Report 1) from the reports (Report 1, Report 2, and Report 3) that meet the triggering conditions for transmission, the priority of the RN is equal to the priority of that highest priority report (Report 1). In other words, the priority of an RN is equal to the priority of the highest priority report among the reports associated with that RN that meet the triggering conditions. For example, if the terminal device needs to select one of multiple regular SRs (or multiple LRRs) to indicate positive, the terminal device can choose one independently.

[0161] In the above embodiments, the priority of a report can be determined based on at least one of event type, mode type, measurement type, cell index, and report configuration ID. The terminal device can be configured to send multiple reports for various event types; for example, the terminal device can be configured to send report 1 for event 1 and report 2 for event 2, with a specific type of event having a higher priority. The terminal device can send event-driven reports using mode A or mode B, with a specific type of mode having a higher priority. Measurement types include SSB-based measurements and CSI-RS-based measurements, with a specific type of measurement having a higher priority. The terminal device can be configured with multiple CCs, each configured with an event-driven report; the smaller the CC index (cell index), the higher the priority of the event-driven report associated with that CC. The terminal device can be configured with multiple reports, each associated with a report configuration ID; the smaller the report configuration ID, the higher the priority of the report.

[0162] For example, the priority of an RN is determined based on the PUCCH resource identifier associated with the PUCCH carrying the RN. The smaller the PUCCH resource identifier, the higher the priority of the associated RN.

[0163] For example, the priority of an RN is determined based on the event type of the report associated with the PUCCH carrying the RN. One or more reports associated with a PUCCH carrying an RN may all be reports for the same type of event, thus multiple RNs can be associated with different types of events. The priority of different RNs can be determined based on the priority of different event types. For example, if event 1 has a higher priority than event 2, then the RN associated with event 1 has a higher priority than the RN associated with event 2.

[0164] In the above embodiments, the priority of the first information can be determined based on the priority of the report associated with the PUCCH carrying the first information.

[0165] For example, the priority of an RN is equal to the priority of the highest-priority report among the reports associated with the RN that meet the triggering condition. Each report has a priority, and if an RN is associated with R1 reports, and R2 (R2≤R1) reports meet the triggering condition, then the priority of the RN is equal to the highest-priority report among the R2 reports.

[0166] For example, the priority of an RN is equal to the priority of the highest-priority report among the reports associated with the RN. Each report has a priority, and if an RN is associated with R1 reports, then the priority of the RN is equal to the highest-priority report among the R1 reports.

[0167] In some embodiments, when the above-mentioned indication information indicates two of a first number of first information and a second number of SRs, the indication information may include first indication information and second indication information, wherein the first indication information indicates one of the first number of first information and the second indication information indicates one of the second number of SRs; wherein the first number of first information is arranged in ascending order of PUCCH resource identifiers; and the second number of SRs is arranged in ascending order of scheduling request resource identifiers.

[0168] For example, in the case shown in Figure 10, the terminal device sends... Bit. The bits allow the terminal device to select one of the K1 SRs as positive (all zeros indicate that all SRs are negative). The bits allow the terminal device to select one of the K2 RNs as positive (all zeros indicate that all RNs are negative). The K1 SRs can be arranged in ascending order of schedulingRequestResourceId or PUCCH-ResourceId. The K2 RNs can be arranged in ascending order of PUCCH-ResourceId.

[0169] In the above embodiments, the first information indicated by the first indication information may have the highest priority among the first number of first information.

[0170] For example, "the first piece of information has the highest priority among the first number of first pieces of information" includes: the first piece of information has the highest priority among the first pieces of information that are triggered.

[0171] For example, the priority of the first piece of information can be determined based on at least one of the following:

[0172] The priority of reports sent in one or more reports associated with the PUCCH carrying the first information;

[0173] The PUCCH resource identifier associated with the PUCCH carrying the first information;

[0174] The event type of the report associated with the PUCCH that carries the first information.

[0175] For example, if a terminal device needs to select one RN from multiple RNs to indicate as positive, the terminal device selects according to the RN's priority, which is equal to the priority of the report sent on the PUSCH. Other similarities will not be repeated here.

[0176] In this application embodiment, the priority of RN is defined, but it is not limited to the above-mentioned scenario of "selecting one RN from multiple RNs to indicate positive". This application does not limit the scenario of applying RN priority. For example, when multiple PUCCHs carrying RNs overlap in the time domain, if the terminal device needs to select one PUCCH to send, it can also select according to the priority of RN and select the PUCCH with the highest priority of the carried RN to send.

[0177] In some embodiments, the second information described above may be, for example, HARQ-ACK and / or CSI, but this application is not limited thereto.

[0178] In some embodiments, the third PUCCH may be PUCCH format 2, PUCCH format 3, or PUCCH format 4, and this application is not limited thereto.

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

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

[0181] Through the embodiments of this application, when a PUCCH carrying an RN overlaps with a PUCCH carrying a HARQ-ACK and / or CSI with a certain PUCCH format, the terminal device and the network device can reach a common understanding as to which PUCCH is being sent, thereby avoiding ambiguity and the resulting PUCCH transmission failure.

[0182] Third aspect of the embodiments

[0183] This application provides an uplink data transmission method, which will be described from the perspective of a terminal device.

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

[0185] 1201, When any one of the reports associated with a first PUCCH carrying first information satisfies the triggering condition, the terminal device sends the first PUCCH and sends a PUSCH associated with the first PUCCH, the PUSCH carrying one of the reports that satisfies the triggering condition;

[0186] Before the first time point t1, each report associated with the first PUCCH occupies 1 CPU; after the first time point t1, each report associated with the first PUCCH occupies 1 CPU; the first time point t1 is not earlier than the end time of the first PUCCH in the time domain.

[0187] In the above embodiment, a first time period T1 may be spaced between the first PUCCH and the first time point t1, and the first time period T1 is greater than or equal to 0.

[0188] Figure 13 is a schematic diagram of an uplink data transmission scenario.

[0189] As shown in Figure 13, an RN (PUCCH) is associated with Report 1, Report 2, and Report 3. When any of these reports meets a trigger condition, the terminal device sends an RN, selecting one report from those meeting the trigger condition to send on the PUSCH. A report occupies a certain number of CSI Processing Units (CPUs) over a period of time. For a report scheduled by a traditional network device, CPU occupancy begins with a measurement of the reference signal (RS) associated with the report and ends after the report is sent. The measured report is always sent, and the number of CPUs remains unchanged throughout the CPU occupancy period. For event-driven reports, the terminal device measures Report 1, Report 2, and Report 3 before the PUCCH, but only sends one of the measured reports; some measured reports are not sent. In this case, determining the number of CPUs within the CPU occupancy period is a problem that needs to be solved.

[0190] Suppose an event-driven report occupies C (e.g., C=1) CPUs. Before the first time point (t1) after the PUCCH, each report associated with the PUCCH occupies 1 CPU. After the first time point (t1) after the PUCCH, since only one report is sent, the reports associated with the PUCCH collectively occupy 1 CPU. From the network device's perspective, although it cannot know which report will actually be sent when it receives the PUCCH, it assumes that the reports associated with the PUCCH collectively occupy 1 CPU during the period from the first time point after the PUCCH to the end of the PUSCH. This allows the terminal device to fully utilize the remaining available CPUs and allocate them to other reports (e.g., report 4, report 5).

[0191] According to the embodiments of this application, the time interval between "the first time point t1 after PUCCH" and PUCCH is denoted as T1, where T1 ≥ 0. In Figure 13, the starting point of T1 is defined as the end time of PUCCH; when T1 = 0, it represents the end time of PUCCH. Without loss of generality, the starting point of T1 can also be defined as the start time of PUCCH. T1 can be configured or predefined. For example, T1 is configured by RRC signaling, or it can be determined according to predefined rules. T1 can be related to the capabilities of the terminal device. For example, the terminal device includes a report of T1 in its device capability report and uses the reported T1; or, for another example, the terminal device includes a report of T1 in its device capability report, the network device configures T1 for the terminal device based on the reported device capabilities, and the terminal device uses the configured T1. The embodiments of this application do not limit the unit of T1; for example, the unit of T1 can be a symbol, a time slot, or a second.

[0192] In some embodiments, the report associated with the first PUCCH occupies the CPU starting from a second time point t2; the second time point t2 is the first symbol of the earliest reference signal resource in a set of reference signal resources used for channel measurements and / or interference measurements.

[0193] In the above embodiments, a set of reference signal resources may be the latest set of reference signal resources at a third time point t3 no later than the first PUCCH, but this application is not limited thereto.

[0194] In the above embodiment, a third time period T3 may be spaced between the first PUCCH and the third time point t3, and the third time period T3 is greater than or equal to 0.

[0195] For example, as shown in Figure 13, for a report associated with PUCCH, CPU usage begins at the second time point (t2). The second time point (t2) is the first symbol of the earliest RS resource in a set of RS resources used for channel measurement and / or interference measurement, where the latest set of RS resources is no later than the third time point (t3) before PUCCH. For example, a set of RS resources includes CSI-RS resources and CSI-IM resources, where the earliest RS resource in the set is a CSI-RS resource. Alternatively, a set of RS resources may include CSI-RS resources or SSB resources. The time interval between the "third time point t3 before PUCCH" and PUCCH is denoted as T3, where T3 ≥ 0. The end point of T3 in the figure is defined as the start time of PUCCH; when T3 = 0, it represents the start time of PUCCH. Without loss of generality, the end point of T3 can also be defined as the end time of PUCCH. T3 can be configured or predefined; the specific determination method can be found in T1 and will not be repeated here. For example, for a report associated with PUCCH, CPU usage continues until the end of PUSCH, that is, until the last symbol of PUSCH ends.

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

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

[0198] Through the embodiments of this application, the number of CPUs can be counted more accurately, so that the remaining available CPUs can be allocated to other reports as needed, thereby achieving more efficient utilization of the CPU.

[0199] Fourth aspect of the embodiment

[0200] This application provides an uplink data receiving method, described from the perspective of a network device corresponding to the terminal device in the first aspect embodiment. The fourth aspect embodiment can be combined with the first aspect embodiment, and content identical to that in the first aspect embodiment will not be repeated.

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

[0202] 1401, The network device receives a PUCCH sent by the terminal device. This PUCCH is selected and sent by the terminal device from a set of PUCCHs determined within a time slot. The set of PUCCHs includes a reference PUCCH and one or more PUCCHs that overlap with the reference PUCCH within the time slot. The reference PUCCH is a PUCCH with repetition. Among the PUCCHs included in the PUCCH set, one PUCCH is a PUCCH carrying first information, and the other PUCCHs are PUCCHs carrying HARQ-ACK, SR, CSI, or the first information, which is used to notify the network device that the terminal device has a report to send.

[0203] Specifically, the terminal device selects a PUCCH from the PUCCH set for transmission according to the priority order of the information carried by the PUCCH; the priority order includes: the priority of the first information is greater than the priority of the CSI, and / or the priority of the first information is less than the priority of the HARQ-ACK, and / or the priority of the first information is equal to the priority of the SR.

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

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

[0206] Through the embodiments of this application, when the PUCCH carrying the RN overlaps with a PUCCH that has repetition, the terminal device and the network device can reach a common understanding as to which PUCCH is being sent, thereby avoiding ambiguity and the resulting PUCCH transmission failure.

[0207] Fifth aspect of the embodiment

[0208] This application provides an uplink data receiving method, described from the perspective of a network device corresponding to the terminal device of the second aspect embodiment. The fifth aspect embodiment can be combined with the second aspect embodiment, and content identical to that in the second aspect embodiment will not be repeated.

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

[0210] 1501, The network device receives an indication message sent by the terminal device, the indication message indicating one or both of a first number of first messages and a second number of SRs;

[0211] The first message is used to notify the network device or terminal device that there is a report to send, and the first number of first messages are arranged in ascending order according to the PUCCH resource identifier.

[0212] In this embodiment of the application, the aforementioned indication information is sent by the terminal device after determining that a first number of first PUCCHs carrying first information and a second number of second PUCCHs carrying SR overlap with a third PUCCH carrying second information in the time domain.

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

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

[0215] Through the embodiments of this application, when a PUCCH carrying an RN overlaps with a PUCCH carrying a HARQ-ACK and / or CSI with a certain PUCCH format, the terminal device and the network device can reach a common understanding as to which PUCCH is being sent, thereby avoiding ambiguity and the resulting PUCCH transmission failure.

[0216] Implementation of the sixth aspect

[0217] This application provides an uplink data receiving method, described from the perspective of a network device corresponding to the terminal device of the third aspect embodiment. The sixth aspect embodiment can be combined with the third aspect embodiment, and content identical to that of the third aspect embodiment will not be repeated.

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

[0219] 1601, The network device receives a first PUCCH and a PUSCH associated with the first PUCCH sent by the terminal device when any one of one or more reports associated with the first PUCCH carrying the first information meets the triggering condition;

[0220] Before the first time point t1, each report associated with the first PUCCH occupies 1 CPU; after the first time point t1, each report associated with the first PUCCH occupies 1 CPU; the first time point t1 is not earlier than the end time of the first PUCCH in the time domain.

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

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

[0223] Through the embodiments of this application, the number of CPUs can be counted more accurately, so that the remaining available CPUs can be allocated to other reports as needed, thereby achieving more efficient utilization of the CPU.

[0224] Seventh aspect of the embodiment

[0225] This application provides an uplink data transmission device. Since the principle of this device in solving the problem is similar to that of the method in the first aspect embodiment, its specific implementation can refer to the implementation of the method described in the first aspect embodiment. The same or related contents will not be repeated.

[0226] Figure 17 is a schematic diagram of an uplink data transmission apparatus according to an embodiment of this application. As shown in Figure 17, the uplink data transmission apparatus 1700 includes:

[0227] The determining unit 1701 determines a set of PUCCHs within a time slot. The set of PUCCHs includes a reference PUCCH and one or more PUCCHs that overlap with the reference PUCCH within the time slot. The reference PUCCH is a PUCCH with repetition. Among the PUCCHs included in the PUCCH set, one PUCCH is a PUCCH carrying first information, and the other PUCCHs are PUCCHs carrying HARQ-ACK, SR, CSI, or the first information. The first information is used to notify the network device that the terminal device has a report to send.

[0228] Within a time slot, the transmitting unit 1702 selects a PUCCH from the PUCCH set for transmission according to the priority order of the information carried by the PUCCH.

[0229] The priority order includes: the priority of the first message is greater than the priority of the CSI, and / or the priority of the first message is less than the priority of the HARQ-ACK, and / or the priority of the first message is equal to the priority of the SR.

[0230] In the above embodiments, SR includes a first SR and a second SR, and the priority order further includes:

[0231] The priority of the first SR is lower than the priority of HARQ-ACK but higher than the priority of the first message; and / or,

[0232] The priority of the second SR is lower than the priority of the first information but higher than the priority of the CSI.

[0233] In the above embodiments, the first SR is used for link recovery requests, and the second SR is used for normal scheduling requests.

[0234] In some embodiments, the reference PUCCH is the PUCCH with the highest priority carrying information among multiple repeating PUCCHs within a time slot; and / or,

[0235] The reference PUCCH is the PUCCH with the earliest start symbol among multiple repeating PUCCHs within a time slot.

[0236] In the above embodiment, among multiple repeating PUCCHs within a time slot, if there are multiple repeating PUCCHs with the earliest start symbol, the reference PUCCH is the repeating PUCCH with the earliest start symbol and the longest duration.

[0237] In some embodiments, any two PUCCHs in the reference PUCCH and one or more PUCCHs overlapping the reference PUCCH carry information with different priorities, or carry information with the same priority but starting in different time slots.

[0238] In some embodiments, in the reference PUCCH and one or more PUCCHs overlapping the reference PUCCH, the terminal device does not expect more than one PUCCH to carry information with the same priority and to start in the same time slot.

[0239] In some embodiments, among the reference PUCCH and one or more PUCCHs overlapping with the reference PUCCH, the transmitting unit 1702 selects the PUCCH with the highest priority carrying the information for transmission.

[0240] In some embodiments, if there are multiple PUCCHs with the highest priority carrying information among the reference PUCCH and one or more PUCCHs overlapping with the reference PUCCH, the transmitting unit 1702 selects the PUCCH with the earliest start time slot among the highest priority PUCCHs for transmission.

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

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

[0243] Through the embodiments of this application, when the PUCCH carrying the RN overlaps with a PUCCH that has repetition, the terminal device and the network device can reach a common understanding as to which PUCCH is being sent, thereby avoiding ambiguity and the resulting PUCCH transmission failure.

[0244] Eighth aspect of the embodiment

[0245] This application provides an uplink data transmission device. Since the principle of this device in solving the problem is similar to the method of the second aspect embodiment, its specific implementation can refer to the implementation of the method described in the second aspect embodiment. The same or related contents will not be repeated.

[0246] Figure 18 is a schematic diagram of an uplink data transmission apparatus according to an embodiment of this application. As shown in Figure 18, the uplink data transmission apparatus 1800 includes:

[0247] The determining unit 1801 determines that a first number of first PUCCHs carrying first information and a second number of second PUCCHs carrying SR overlap with a third PUCCH carrying second information in the time domain;

[0248] The sending unit 1901 sends indication information to the network device, the indication information indicating one or both of the first number of first messages and the second number of SRs;

[0249] The first message is used to notify the network device or terminal device that there is a report to send, and the first number of first messages are arranged in ascending order according to the PUCCH resource identifier.

[0250] In the above embodiments, when the indication information indicates one of a first number of first pieces of information and a second number of SRs,

[0251] The first number of first information and the second number of SRs are arranged in ascending order according to the PUCCH resource identifier.

[0252] or,

[0253] The second number of SRs are arranged in ascending order of scheduling request resource identifiers, and the first number of first information items are arranged in ascending order of PUCCH resource identifiers. The arranged SRs and the arranged first information items are then concatenated.

[0254] In some embodiments, if the indication information indicates a first piece of information, the first piece of information has the highest priority among a first number of first pieces of information.

[0255] In some embodiments, the priority of the first information is determined according to at least one of the following:

[0256] The priority of reports sent in one or more reports associated with the PUCCH carrying the first information;

[0257] The PUCCH resource identifier associated with the PUCCH carrying the first information;

[0258] The event type of the report associated with the PUCCH that carries the first information.

[0259] In some embodiments, when the indication information indicates two of a first number of first information and a second number of SRs, the indication information includes a first indication information and a second indication information, wherein the first indication information indicates one of the first number of first information and the second indication information indicates one of the second number of SRs;

[0260] in,

[0261] The first number of first information items are arranged in ascending order according to the PUCCH resource identifier;

[0262] The second number of SRs are arranged in ascending order according to the resource identifier of the scheduling request.

[0263] In the above embodiments, the first information indicated by the first indication information has the highest priority among the first number of first information.

[0264] In the above embodiments, the priority of the first information is determined according to at least one of the following:

[0265] The priority of reports sent in one or more reports associated with the PUCCH carrying the first information;

[0266] The PUCCH resource identifier associated with the PUCCH carrying the first information;

[0267] The event type of the report associated with the PUCCH that carries the first information.

[0268] In some embodiments, the second information is HARQ-ACK and / or CSI.

[0269] In some embodiments, the third PUCCH uses PUCCH format 2, PUCCH format 3, or PUCCH format 4.

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

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

[0272] Through the embodiments of this application, when a PUCCH carrying an RN overlaps with a PUCCH carrying a HARQ-ACK and / or CSI with a certain PUCCH format, the terminal device and the network device can reach a common understanding as to which PUCCH is being sent, thereby avoiding ambiguity and the resulting PUCCH transmission failure.

[0273] Ninth aspect of the embodiment

[0274] This application provides an uplink data transmission device. Since the principle of this device in solving the problem is similar to the method of the third aspect embodiment, its specific implementation can refer to the implementation of the method described in the third aspect embodiment. The same or related contents will not be repeated.

[0275] Figure 19 is a schematic diagram of an uplink data transmission apparatus according to an embodiment of this application. As shown in Figure 19, the uplink data transmission apparatus 1900 includes:

[0276] The sending unit 1901 sends the first PUCCH and the PUSCH associated with the first PUCCH when any one of the reports in one or more reports associated with the first PUCCH carrying the first information meets the triggering condition. The PUSCH carries one of the reports that meet the triggering condition.

[0277] Before the first time point t1, each report associated with the first PUCCH occupies 1 CPU; after the first time point t1, each report associated with the first PUCCH occupies 1 CPU; the first time point t1 is not earlier than the end time of the first PUCCH in the time domain.

[0278] In the above embodiment, the first PUCCH and the first time point t1 are separated by a first time period T1, and the first time period T1 is greater than or equal to 0.

[0279] In the above embodiment, the report associated with the first PUCCH starts occupying the CPU from the second time point t2;

[0280] The second time point t2 is the first symbol of the earliest reference signal resource in a set of reference signal resources used for channel measurement and / or interference measurement.

[0281] In the above embodiments, a set of reference signal resources is the latest set of reference signal resources at a third time point t3 before the first PUCCH.

[0282] In the above embodiment, the interval between the first PUCCH and the third time point t3 is a third time period T3, and the third time period T3 is greater than or equal to 0.

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

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

[0285] Through the embodiments of this application, the number of CPUs can be counted more accurately, so that the remaining available CPUs can be allocated to other reports as needed, thereby achieving more efficient utilization of the CPU.

[0286] Tenth aspect embodiment

[0287] This application provides an uplink data receiving device. This device may be, for example, a network device. Since the principle by which this device solves the problem is similar to the methods in the embodiments of the fourth and fifth aspects, its specific implementation can refer to the implementation of the methods described in the embodiments of the fourth and fifth aspects. Where the content is the same or related, it will not be repeated.

[0288] Figure 20 is a schematic diagram of an uplink data receiving device according to an embodiment of this application. As shown in Figure 20, the uplink data receiving device 2000 includes a receiving unit 2001.

[0289] In some embodiments, the receiving unit 2001 receives a PUCCH sent by the terminal device. The PUCCH is selected and sent by the terminal device from a set of PUCCHs determined within a time slot. The PUCCH set includes a reference PUCCH and one or more PUCCHs that overlap with the reference PUCCH within the time slot. The reference PUCCH is a PUCCH with repetition. Among the PUCCHs included in the PUCCH set, one PUCCH is a PUCCH carrying first information, and the other PUCCHs are PUCCHs carrying HARQ-ACK, SR, CSI, or first information.

[0290] Specifically, the terminal device selects a PUCCH from the PUCCH set for transmission according to the limited order of the information carried by the PUCCH; the priority order includes: the priority of the first information is greater than the priority of the CSI, and / or the priority of the first information is less than the priority of the HARQ-ACK, and / or the priority of the first information is equal to the priority of the SR.

[0291] In other embodiments, the receiving unit 2001 receives indication information sent by the terminal device, the indication information indicating one or both of a first number of first messages and a second number of SRs; wherein, the first message is used to notify the network device that the terminal device has a report to send, and the first number of first messages are arranged in ascending order according to the PUCCH resource identifier.

[0292] In the above embodiments, the above indication information is sent by the terminal device after determining that a first number of first PUCCHs carrying first information and a second number of second PUCCHs carrying SR overlap with a third PUCCH carrying second information in the time domain.

[0293] For details, please refer to the aforementioned embodiments, which will not be repeated here.

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

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

[0296] Through the embodiments of this application, when a PUCCH carrying an RN overlaps with a PUCCH that has duplicates, or when a PUCCH carrying an RN overlaps with a PUCCH carrying HARQ-ACK and / or CSI with a certain PUCCH format, the terminal device and the network device can reach a common understanding as to which PUCCH is being sent, thereby avoiding ambiguity and the resulting PUCCH transmission failure.

[0297] Eleventh aspect of the embodiment

[0298] This application provides an uplink data receiving device. This device may be, for example, a network device. Since the principle by which this device solves the problem is similar to the method in the sixth aspect embodiment, its specific implementation can refer to the implementation of the method described in the sixth aspect embodiment. Where the content is the same or related, it will not be repeated.

[0299] Figure 21 is a schematic diagram of an uplink data receiving device according to an embodiment of this application. As shown in Figure 21, the uplink data receiving device 2100 includes:

[0300] The receiving unit 2101 receives the first PUCCH and the PUSCH associated with the first PUCCH sent by the terminal device when any one of the reports associated with the first PUCCH carrying the first information meets the triggering condition.

[0301] Before the first time point t1, each report associated with the first PUCCH occupies 1 CPU; after the first time point t1, each report associated with the first PUCCH occupies 1 CPU; the first time point t1 is not earlier than the end time of the first PUCCH in the time domain.

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

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

[0304] Through the embodiments of this application, the number of CPUs can be counted more accurately, so that the remaining available CPUs can be allocated to other reports as needed, thereby achieving more efficient utilization of the CPU.

[0305] Twelfth aspect of the embodiment

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

[0307] In some embodiments, the communication system 100 may include at least: terminal device 102 or 103 and / or network device 101. Terminal device 102 / 103 may perform the methods described in any of the embodiments of the first to third aspects, including the apparatus described in any of the embodiments of the seventh to ninth aspects, and network device 101 may perform the methods described in any of the embodiments of the fourth to sixth aspects, including the apparatus described in the embodiments of the tenth or eleventh aspect, which will not be described further here.

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

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

[0310] For example, processor 2210 can be configured to execute a program to implement the uplink data transmission method as described in the embodiments of the first to third aspects.

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

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

[0313] This application also provides a computer program, wherein when the program is executed in a terminal device, the program causes the terminal device to perform the uplink data transmission method described in the embodiments of the first to third aspects.

[0314] This application also provides a storage medium storing a computer program, wherein the computer program causes a terminal device to execute the uplink data transmission method described in the first to third embodiments.

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

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

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

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

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

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

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

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

[0323] 1. An uplink data transmission method, wherein the method includes:

[0324] The terminal device determines a set of PUCCHs within a time slot. The set of PUCCHs includes a reference PUCCH and one or more PUCCHs that overlap with the reference PUCCH within the time slot. The reference PUCCH is a PUCCH with repetition. Among the PUCCHs included in the set of PUCCHs, one PUCCH is a PUCCH carrying first information, and the other PUCCHs are PUCCHs carrying HARQ-ACK, SR, CSI, or the first information, which is used to notify the network device that the terminal device has a report to send.

[0325] Within the time slot, the terminal device selects a PUCCH from the PUCCH set and sends it according to the priority order of the information carried by the PUCCH;

[0326] The priority order includes: the priority of the first information is greater than the priority of the CSI, and / or the priority of the first information is less than the priority of the HARQ-ACK, and / or the priority of the first information is equal to the priority of the SR.

[0327] 2. An uplink data transmission method, wherein the method includes:

[0328] The terminal device determines that a first number of first PUCCHs carrying first information and a second number of second PUCCHs carrying SR overlap with a third PUCCH carrying second information in the time domain;

[0329] The terminal device sends an indication information to the network device, the indication information indicating one or both of the first number of first information and the second number of SRs;

[0330] The first information is used to notify the network device that the terminal device has a report to send, and the first number of first information items are arranged in ascending order according to the PUCCH resource identifier.

[0331] 3. An uplink data transmission method, wherein the method includes:

[0332] When any one of the reports associated with a first PUCCH carrying first information meets the triggering condition, the terminal device sends the first PUCCH and sends a PUSCH associated with the first PUCCH, the PUSCH carrying one of the reports that meet the triggering condition.

[0333] Before the first time point t1, each report associated with the first PUCCH occupies 1 CPU; after the first time point t1, each report associated with the first PUCCH occupies 1 CPU; the first time point t1 is not earlier than the end time of the first PUCCH in the time domain.

[0334] 4. An uplink data receiving method, wherein the method includes:

[0335] The network device receives a PUCCH sent by the terminal device. The PUCCH is selected and sent by the terminal device from a set of PUCCHs determined within a time slot. The set of PUCCHs includes a reference PUCCH and one or more PUCCHs that overlap with the reference PUCCH within the time slot. The reference PUCCH is a PUCCH with repetition. Among the PUCCHs included in the PUCCH set, one PUCCH is a PUCCH carrying first information, and the other PUCCHs are PUCCHs carrying HARQ-ACK, SR, CSI, or the first information.

[0336] The terminal device selects a PUCCH from the PUCCH set for transmission according to a finite order of the information carried by the PUCCH; the priority order includes: the priority of the first information is greater than the priority of the CSI, and / or the priority of the first information is less than the priority of the HARQ-ACK, and / or the priority of the first information is equal to the priority of the SR.

[0337] 5. An uplink data receiving method, wherein the method includes:

[0338] The network device receives indication information sent by the terminal device, the indication information indicating one or both of a first number of first information and a second number of SRs;

[0339] The first information is used to notify the network device that the terminal device has a report to send, and the first number of first information items are arranged in ascending order according to the PUCCH resource identifier.

[0340] 6. An uplink data receiving method, wherein the method comprises:

[0341] The network device receives the first PUCCH and the PUSCH associated with the first PUCCH sent by the terminal device when any one of the reports associated with the first PUCCH carrying the first information meets the triggering condition.

[0342] Before the first time point t1, each report associated with the first PUCCH occupies 1 CPU; after the first time point t1, each report associated with the first PUCCH occupies 1 CPU; the first time point t1 is not earlier than the end time of the first PUCCH in the time domain.

[0343] 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 method as described in Appendices 1 to 3.

[0344] 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 method as described in Appendices 4 to 6.

[0345] 9. A communication system having a terminal device as described in Appendix 7 and a network device as described in Appendix 8.

Claims

1. A report uplink data transmission device, configured in a terminal device, wherein, The device includes: A determining unit determines a set of PUCCHs within a time slot. The set of PUCCHs includes a reference PUCCH and one or more PUCCHs that overlap with the reference PUCCH within the time slot. The reference PUCCH is a PUCCH with repetition. Among the PUCCHs included in the set of PUCCHs, one PUCCH is a PUCCH carrying first information, and the other PUCCHs are PUCCHs carrying HARQ-ACK, SR, CSI, or the first information, which is used to notify the network device that the terminal device has a report to send. The transmitting unit selects a PUCCH from the PUCCH set and transmits it according to the priority order of the information carried by the PUCCH within the time slot. The priority order includes: the priority of the first information is greater than the priority of the CSI, and / or the priority of the first information is less than the priority of the HARQ-ACK, and / or the priority of the first information is equal to the priority of the SR.

2. The apparatus according to claim 1, wherein, The SR includes a first SR and a second SR, and the priority order also includes: The priority of the first SR is lower than the priority of the HARQ-ACK but higher than the priority of the first information; and / or, The priority of the second SR is lower than the priority of the first information but higher than the priority of the CSI.

3. The apparatus according to claim 2, wherein, The first SR is used for link recovery requests, and the second SR is used for normal scheduling requests.

4. The apparatus according to claim 1, wherein, The reference PUCCH is the PUCCH with the highest priority among multiple repeating PUCCHs within the time slot; and / or, The reference PUCCH is the PUCCH with the earliest start symbol among the multiple repeating PUCCHs within the time slot.

5. The apparatus according to claim 4, wherein, Among the multiple repeating PUCCHs within the time slot, if there are multiple repeating PUCCHs with the earliest start symbol, the reference PUCCH is the repeating PUCCH with the earliest start symbol and the longest duration.

6. The apparatus according to claim 1, wherein, In the reference PUCCH and one or more PUCCHs overlapping the reference PUCCH, any two PUCCHs carry information with different priorities, or carry information with the same priority but starting in different time slots.

7. The apparatus according to claim 1, wherein, In the reference PUCCH and one or more PUCCHs overlapping the reference PUCCH, the terminal device does not expect more than one PUCCH to carry information with the same priority and start in the same time slot.

8. The apparatus according to claim 1, wherein, Among the reference PUCCH and one or more PUCCHs overlapping the reference PUCCH, the transmitting unit selects the PUCCH with the highest priority carrying the information for transmission.

9. The apparatus according to claim 1, wherein, If there are multiple PUCCHs with the highest priority carrying information, among the reference PUCCH and one or more PUCCHs overlapping with the reference PUCCH, the transmitting unit selects the PUCCH with the earliest start time slot among the highest priority PUCCHs for transmission.

10. An uplink data transmission device, configured in a terminal device, wherein, The device includes: The determining unit determines that a first number of first PUCCHs carrying first information and a second number of second PUCCHs carrying SR overlap with a third PUCCH carrying second information in the time domain; A sending unit that sends indication information to a network device, the indication information indicating one or both of the first number of first messages and the second number of SRs; The first information is used to notify the network device that the terminal device has a report to send, and the first number of first information items are arranged in ascending order according to the PUCCH resource identifier.

11. The apparatus according to claim 10, wherein, When the indication information indicates one of the first number of first information and the second number of SRs. The first number of first information items and the second number of SRs are arranged in ascending order according to the PUCCH resource identifier. or, The second number of SRs are arranged in ascending order of scheduling request resource identifiers, and the first number of first information items are arranged in ascending order of PUCCH resource identifiers. The arranged SRs and the arranged first information items are concatenated.

12. The apparatus according to claim 11, wherein, If the indication information indicates a first piece of information, the first piece of information has the highest priority among the first number of first pieces of information.

13. The apparatus according to claim 12, wherein, The priority of the first information is determined according to at least one of the following: The priority of reports sent in one or more reports associated with the PUCCH carrying the first information; The PUCCH resource identifier associated with the PUCCH carrying the first information; The event type of the report associated with the PUCCH carrying the first information.

14. The apparatus according to claim 10, wherein, When the indication information indicates two of the first quantity of first information and the second quantity of SRs, the indication information includes first indication information and second indication information, wherein the first indication information indicates one of the first quantity of first information and the second indication information indicates one of the second quantity of SRs; in, The first number of first information items are arranged in ascending order according to the PUCCH resource identifier; The second number of SRs are arranged in ascending order according to the scheduling request resource identifier.

15. The apparatus according to claim 14, wherein, The first information indicated by the first instruction information has the highest priority among the first number of first information.

16. The apparatus according to claim 15, wherein, The priority of the first information is determined according to at least one of the following: The priority of reports sent in one or more reports associated with the PUCCH carrying the first information; The PUCCH resource identifier associated with the PUCCH carrying the first information; The event type of the report associated with the PUCCH carrying the first information.

17. The apparatus according to claim 10, wherein, The second information is HARQ-ACK and / or CSI.

18. The apparatus according to claim 10, wherein, The third PUCCH uses PUCCH format 2, PUCCH format 3, or PUCCH format 4.

19. An uplink data transmission device, configured with a terminal device, wherein, The device includes: The sending unit sends the first PUCCH and the PUSCH associated with the first PUCCH when any one of the reports in one or more reports associated with the first PUCCH carrying the first information meets the triggering condition. The PUSCH carries one of the reports that meet the triggering condition. Before the first time point t1, each report associated with the first PUCCH occupies 1 CPU; after the first time point t1, each report associated with the first PUCCH occupies 1 CPU; the first time point t1 is not earlier than the end time of the first PUCCH in the time domain.

20. The apparatus according to claim 19, wherein, The first PUCCH is separated from the first time point t1 by a first time period T1, and the first time period T1 is greater than or equal to 0.

Images