PUCCH (Physical Uplink Control Channel) transmission method, terminal and network side equipment

Abstract

The invention discloses a PUCCH (Physical Uplink Control Channel) transmission method, a terminal and network side equipment, and belongs to the technical field of wireless communication, the PUCCH transmission method in the embodiment of the invention comprises the following steps: the terminal sends a plurality of PUCCHs through a plurality of frequency domain units, and the plurality of frequency domain units can be used for sending the PUCCHs.

Description

Technical Field

[0001] This application belongs to the field of wireless communication technologies, and particularly relates to a PUCCH transmission method, a terminal, and a network-side device. Background Art

[0002] In the prior art, the carrier of each cell is a continuous frequency-domain resource, and the Physical Uplink Control Channel (PUCCH) resources are configured in each uplink (UL) bandwidth part (BWP) with continuous frequency-domain resources. Each cell has only one active UL BWP, and the transmission of PUCCH is performed in one UL BWP. In order to efficiently utilize discontinuous frequency-domain resources, it is a potential direction for a cell to include multiple discontinuous spectrums. When a cell includes discontinuous spectrum resources, there is no clear solution on how to achieve the co-transmission of PUCCH by different frequency-domain units. Summary of the Invention

[0003] Embodiments of this application provide a PUCCH transmission method, a terminal, and a network-side device, which can achieve the co-transmission of PUCCH by different frequency-domain units.

[0004] In a first aspect, a PUCCH transmission method is provided, which is executed by a terminal. The method includes:

[0005] The terminal sends multiple PUCCHs through multiple frequency-domain units, where multiple frequency-domain units are available for sending PUCCHs.

[0006] In a second aspect, a PUCCH transmission method is provided, which is executed by a network-side device. The method includes:

[0007] The network-side device receives multiple PUCCHs through multiple frequency-domain units, where multiple frequency-domain units are available for receiving PUCCHs.

[0008] In a third aspect, a PUCCH transmission device is provided, including:

[0009] A first sending module, configured to send multiple PUCCHs through multiple frequency-domain units, where multiple frequency-domain units are available for sending PUCCHs.

[0010] In a fourth aspect, a PUCCH transmission device is provided, including:

[0011] A first receiving module, configured to receive multiple PUCCHs through multiple frequency-domain units, where multiple frequency-domain units are available for receiving PUCCHs.

[0012] Fifth aspect, a terminal is provided, which includes a processor and a memory. The memory stores a program or instructions that can run on the processor. When the program or instructions are executed by the processor, the steps of the method described in the first aspect are implemented.

[0013] Sixth aspect, a terminal is provided, including a processor and a communication interface. The communication interface is used to send multiple PUCCHs through multiple frequency domain units, and there are multiple frequency domain units available for sending PUCCHs.

[0014] Seventh aspect, a network-side device is provided, which includes a processor and a memory. The memory stores a program or instructions that can run on the processor. When the program or instructions are executed by the processor, the steps of the method described in the first aspect are implemented.

[0015] Eighth aspect, a network-side device is provided, including a processor and a communication interface. The communication interface is used to receive multiple PUCCHs through multiple frequency domain units, and there are multiple frequency domain units available for receiving PUCCHs.

[0016] Ninth aspect, a readable storage medium is provided. The readable storage medium stores a program or instructions. When the program or instructions are executed by a processor, the method described in the first aspect is implemented, or the method described in the second aspect is implemented.

[0017] Tenth aspect, a wireless communication system is provided, including: a terminal and a network-side device. The terminal can be used to execute the steps of the method described in the first aspect, and the network-side device can be used to execute the steps of the method described in the second aspect.

[0018] Eleventh aspect, a chip is provided. The chip includes a processor and a communication interface. The communication interface is coupled to the processor. The processor is used to run a program or instructions to implement the method described in the first aspect, or to implement the method described in the second aspect.

[0019] Twelfth aspect, a computer program / program product is provided. The computer program / program product is stored in a storage medium. The program / program product is executed by at least one processor to implement the method described in the first aspect, or to implement the method described in the second aspect.

[0020] In the embodiments of the present application, the terminal sends multiple PUCCHs through multiple frequency domain units. Among them, there are multiple frequency domain units available for sending PUCCHs. When multiple PUCCHs need to be transmitted, multiple PUCCHs are transmitted simultaneously through different frequency domain units, reducing the communication delay and being able to more flexibly and efficiently utilize the spectrum resources of the cell to improve the effectiveness and performance of the communication system. Description of the Drawings

[0021] Figure 1 is a block diagram of a wireless communication system provided by an embodiment of the present application;

[0022] Figure 2 is one of the schematic flowcharts of a PUCCH transmission method provided by an embodiment of the present application;

[0023] Figure 3 is another schematic flowchart of a PUCCH transmission method provided by an embodiment of the present application;

[0024] Figure 4 is an implementation example diagram of a PUCCH transmission method provided by an embodiment of the present application;

[0025] Figure 5 is one of the schematic structural diagrams of a PUCCH transmission device provided by an embodiment of the present application;

[0026] Figure 6 is another schematic structural diagram of a PUCCH transmission device provided by an embodiment of the present application;

[0027] Figure 7 is a schematic structural diagram of a communication device provided by an embodiment of the present application;

[0028] Figure 8 is a schematic hardware structure diagram of a terminal provided by an embodiment of the present application;

[0029] Figure 9 is a schematic structural diagram of a network - side device provided by an embodiment of the present application. Detailed implementation manners

[0030] Next, the technical solutions in the embodiments of the present application will be clearly described with reference to the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are some, rather than all, of the embodiments of the present application. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art belong to the scope of protection of the present application.

[0031] The terms "first", "second", etc. in this application are used to distinguish similar objects, rather than to describe a specific order or sequence. It should be understood that such terms can be interchanged under appropriate circumstances, so that the embodiments of this application can be implemented in an order other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of the same category, and do not limit the number of objects. For example, the first object can be one or more. In addition, "or" in this application means at least one of the connected objects. For example, "A or B" covers three scenarios, namely, Scenario 1: including A and not including B; Scenario 2: including B and not including A; Scenario 3: including both A and B. The character " / " generally indicates that the related objects before and after are in an "or" relationship.

[0032] The term "indication" in this application can be either a direct indication (or an explicit indication) or an indirect indication (or an implicit indication). Among them, a direct indication can be understood as that the sender clearly tells the receiver specific information, operations to be performed, or request results, etc. in the sent indication; an indirect indication can be understood as that the receiver determines the corresponding information according to the indication sent by the sender, or makes a judgment and determines the operations to be performed or request results, etc. according to the judgment result.

[0033] It is worth pointing out that the technology described in the embodiments of this application is not limited to Long Term Evolution (LTE) / LTE-Advanced (LTE-A) systems, and can also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency-Division Multiple Access (SC-FDMA), or other systems. The terms "system" and "network" in the embodiments of this application are often used interchangeably, and the described technology can be used not only in the systems and radio technologies mentioned above, but also in other systems and radio technologies. The following description describes the New Radio (NR) system for example purposes, and uses NR terms in most of the following descriptions, but these technologies can also be applied to systems other than the NR system, such as the 6th generation (6 thGeneration, 6G) communication system.

[0034] Figure 1Block diagram of a wireless communication system to which embodiments of the present application can be applied. The wireless communication system includes a terminal 11 and a network-side device 12. Among them, the terminal 11 can be a mobile phone, a tablet personal computer, a laptop computer, a notebook computer, a personal digital assistant (PDA), a handheld computer, a netbook, an ultra-mobile personal computer (UMPC), a mobile internet device (MID), an augmented reality (AR), a virtual reality (VR) device, a robot, a wearable device, a flight vehicle, a vehicle user equipment (VUE), a shipborne device, a pedestrian user equipment (PUE), a smart home (home devices with wireless communication functions, such as refrigerators, TVs, washing machines, or furniture, etc.), a game console, a personal computer (PC), a teller machine, or a self-service machine, etc. Wearable devices include: smart watches, smart bracelets, smart earphones, smart glasses, smart jewelry (smart bracelets, smart bracelets, smart rings, smart necklaces, smart anklets, smart ankle chains, etc.), smart wristbands, smart clothing, etc. Among them, the vehicle user equipment can also be referred to as a vehicle terminal, a vehicle controller, a vehicle module, a vehicle component, a vehicle chip, or a vehicle unit, etc. It should be noted that the specific type of the terminal 11 is not limited in the embodiments of the present application. The network-side device 12 can include an access network device or a core network device. Among them, the access network device can also be referred to as a radio access network (RAN) device, a radio access network function, or a radio access network unit. The access network device can include a base station, a wireless local area network (WLAN) access point (AP), or a wireless fidelity (WiFi) node, etc.Among them, the base station may be referred to as Node B (NB), Evolved Node B (eNB), the next generation Node B (gNB), New Radio Node B (NR Node B), access point, Relay Base Station (RBS), Serving Base Station (SBS), Base Transceiver Station (BTS), radio base station, radio transceiver, Basic Service Set (BSS), Extended Service Set (ESS), home Node B (HNB), home evolved Node B, Transmission Reception Point (TRP), or some other suitable term in the art. As long as the same technical effect is achieved, the base station is not limited to specific technical terms. It should be noted that in the embodiments of this application, only the base station in the NR system is taken as an example for introduction, and the specific type of the base station is not limited.

[0035] The core network device may include, but is not limited to, at least one of the following: core network node, core network function, Mobility Management Entity (MME), Access and Mobility Management Function (AMF), Session Management Function (SMF), User Plane Function (UPF), Policy Control Function (PCF), Policy and Charging Rules Function (PCRF), Edge Application Server Discovery Function (EASDF), Unified Data Management (UDM), Unified Data Repository (UDR), Home Subscriber Server (HSS), Centralized network configuration (CNC), Network Repository Function (NRF), Network Exposure Function (NEF), Local NEF (L-NEF), Binding Support Function (BSF), Application Function (AF), etc. It should be noted that in the embodiments of the present application, only the core network devices in the NR system are taken as examples for introduction, and the specific types of core network devices are not limited.

[0036] The PUCCH transmission method provided by the embodiments of the present application will be described in detail below with reference to the accompanying drawings through some embodiments and their application scenarios.

[0037] Figure 2 is one of the schematic flowcharts of the PUCCH transmission method provided by the embodiments of the present application. As Figure 2 shown, the method includes the following steps:

[0038] Step 200: The terminal sends multiple PUCCHs through multiple frequency domain units, where there are multiple frequency domain units available for sending PUCCHs.

[0039] In the implementation of this application, a cell consists of at least one frequency domain unit. A frequency domain unit is a set of continuous frequency domain resources, which can be a band, a carrier, a subband, a BWP, etc. The sizes of different frequency domain units can be the same or different, and different frequency domain units can be discontinuous. For example, a cell consists of four frequency domain units with sizes of 3 MHz, 10 MHz, 5 MHz, and 5 MHz respectively.

[0040] For a cell consisting of multiple frequency domain units, each PUCCH resource can be configured / scheduled within one frequency domain unit. At the same time unit, multiple frequency domain units can have available PUCCH resources (for example, there is a corresponding PUCCH resource configuration on the corresponding frequency domain unit, or the base station can schedule the PUCCH resource to be transmitted on the corresponding frequency domain unit, etc.), or multiple frequency domain units have available uplink resources, and the base station can configure / schedule multiple PUCCHs to be transmitted on multiple frequency domain units. The terminal / user equipment (UE) sends multiple PUCCHs through multiple frequency domain units. The network side device receives multiple PUCCHs through multiple frequency domain units.

[0041] It is also possible that at different time units, multiple frequency domain units have available PUCCH resources, or multiple frequency domain units have available uplink resources, and the base station can configure / schedule multiple PUCCHs to be transmitted on multiple frequency domain units. The UE sends multiple PUCCHs through multiple frequency domain units. The network side device receives multiple PUCCHs through multiple frequency domain units. Optionally, the time unit can be a time period such as a symbol, a set of symbols, a time slot, a sub-time slot, a sub-frame, a frame, etc., which is not specifically limited.

[0042] In the embodiments of this application, the terminal sends multiple PUCCHs through multiple frequency domain units, which can avoid the complexity of uplink control information (UCI) multiplexing, ensure the transmission of low-priority PUCCHs, reduce the transmission delay, and can more flexibly and efficiently utilize the spectrum resources of the cell to improve the effectiveness and performance of the communication system.

[0043] Optionally, the method further includes:

[0044] The terminal reports at least one of the following capability information to the network side device:

[0045] Whether the terminal can support simultaneous transmission of PUCCH in different frequency domain units;

[0046] The terminal can support simultaneous transmission of PUCCH in different frequency domain units;

[0047] The number of PUCCHs that the terminal supports and can be transmitted simultaneously in different frequency domain units;

[0048] The frequency domain units that the terminal supports and in which PUCCHs can be transmitted simultaneously;

[0049] The minimum interval between the frequency domain units that the terminal supports and in which PUCCHs can be transmitted simultaneously.

[0050] The UE reports to the network device. It can be understood that whether the UE can support simultaneous transmission of PUCCHs in different frequency domain units means that it needs to be reported regardless of whether the UE supports it or not.

[0051] If the UE can support simultaneous transmission of PUCCHs in different frequency domain units, it means that if the UE does not report, it means it does not support, and it is reported only when it supports.

[0052] The number of PUCCHs that the UE supports and can be transmitted simultaneously in different frequency domain units can represent the number of PUCCHs that the UE can transmit simultaneously.

[0053] For example, the UE reports the number N1 of PUCCHs that it supports and can be transmitted simultaneously in different frequency domain units, and / or the frequency domain units that the UE supports and in which PUCCHs can be transmitted simultaneously.

[0054] For another example, the UE reports the frequency domain units that it supports and in which PUCCHs can be transmitted simultaneously and the minimum interval between the frequency domain units that it supports and in which PUCCHs can be transmitted simultaneously.

[0055] It should be noted that: in the embodiments of the present application, if the UE can support simultaneous transmission of PUCCHs in different frequency domain units, it means that the base station can schedule the terminal to simultaneously transmit different PUCCHs in different frequency domain units. However, whether the UE performs simultaneous transmission of PUCCHs in different frequency domain units depends on the configuration / scheduling of the base station. For example, the base station can schedule the UE to transmit different PUCCHs in different frequency domain units at different times, or the base station can also schedule the UE to transmit different PUCCHs in different frequency domain units at the same time / overlapping times (where the overlapping times mean that the transmissions of different PUCCHs overlap in time, which can be completely overlapping or partially overlapping).

[0056] It should also be noted that: if the UE supports transmitting different PUCCHs in different frequency domain units at the same time, then the UE can also support transmitting different PUCCHs in different frequency domain units at different times.

[0057] Optionally, the multiple frequency domain units belong to different frequency domain unit groups / sets.

[0058] In an embodiment of the present application, optionally, when the UE supports transmitting PUCCH simultaneously in different frequency domain units, where the different frequency domain units meet the second requirement. For example, the second requirement includes that the different frequency domain units belong to different frequency domain unit groups / sets.

[0059] It should be noted that: the frequency domain unit group / set can be reported by the UE to the network side device / predefined / high-layer configured.

[0060] Optionally, the frequency domain interval between the multiple frequency domain units meets the first requirement.

[0061] In an embodiment of the present application, when the UE supports transmitting PUCCH in different frequency domain units, where the frequency domain interval between the multiple frequency domain units meets the first requirement. For example, the first requirement includes that the frequency domain interval between the frequency domain units is greater than a certain preset value, etc.

[0062] It should be noted that: the requirement that the frequency domain interval meets can be reported by the UE to the network side device / predefined / high-layer configured.

[0063] Optionally, when the base station configures or instructs the UE to transmit different PUCCHs in different frequency domain units, it is ensured that the different frequency domain units corresponding to the PUCCH transmission meet the above second requirement, or when the base station configures or instructs the UE to transmit different PUCCHs in different frequency domain units, if the multiple frequency domain units corresponding to the PUCCH transmission do not meet the above requirements, the UE discards / cancels some PUCCH transmissions / merges the PUCCH according to the first principle.

[0064] Optionally, the terminal sends multiple PUCCHs through multiple frequency domain units, including:

[0065] When the number of PUCCHs that need to be sent simultaneously is greater than the number of PUCCHs that the terminal supports to be sent simultaneously in different frequency domain units, the terminal performs PUCCH transmission in at least one of the following ways:

[0066] The terminal discards some PUCCHs according to a preset rule and sends the remaining PUCCHs through multiple frequency domain units;

[0067] The terminal multiplexes at least part of the UCI carried by some PUCCHs on other channels for transmission and sends the remaining PUCCHs through multiple frequency domain units.

[0068] In an embodiment of the present application, the PUCCHs that need to be sent simultaneously refer to the PUCCHs that the UE needs to send in different frequency domain units within an overlapping time based on the dynamic scheduling and / or configuration of the base station. Here, the PUCCHs can all be in different frequency domain units.

[0069] Optionally, the UE does not expect multiple PUCCHs scheduled in the same frequency domain unit to overlap in time, or, if the UE is scheduled with multiple PUCCHs in the same frequency domain unit, the UE may first perform processing such as discarding / canceling partial transmission / merging within the frequency domain unit, so that at most one PUCCH needs to be transmitted within one frequency domain unit at the same time.

[0070] For example, when the UE supports / is enabled to simultaneously transmit PUCCHs in different frequency domain units, the base station schedules / configures the UE to transmit different PUCCHs in different frequency domain units. At a certain time, if the UE does not expect the number N2 of PUCCHs configured / scheduled by the base station for the UE to transmit in different frequency domain units to be greater than the reported capability N1 of the UE (N2 > N1), that is, when the base station schedules the UE to transmit different PUCCHs, it should ensure that it is within the PUCCH transmission capability range of the UE. Or, if the number N2 of PUCCHs configured / scheduled for the UE to transmit in different frequency domain units is greater than the reported capability N1 of the UE (N2 > N1), the UE discards part of the PUCCH transmissions according to a preset rule and sends the remaining PUCCHs through multiple frequency domain units.

[0071] For another example, when the UE supports / is enabled to simultaneously transmit PUCCHs in different frequency domain units, the base station schedules / configures the UE to transmit different PUCCHs in different frequency domain units. At a certain time, if the UE does not expect the number N2 of PUCCHs configured / scheduled by the base station for the UE to transmit in different frequency domain units to be greater than the reported capability N1 of the UE (N2 > N1), or if the number N2 of PUCCHs configured / scheduled for the UE to transmit in different frequency domain units is greater than the reported capability N1 of the UE (N2 > N1), the UE multiplexes at least part of the UCI carried by part of the PUCCHs onto other channels for transmission according to a preset rule and sends the remaining PUCCHs through multiple frequency domain units.

[0072] It should be noted that: in the embodiments of the present application, the preset rule includes at least one of the following:

[0073] According to a predefined priority order. For example, the priority of the PUCCH carrying Hybrid Automatic Repeat reQuest acknowledgement (HARQ-ACK) is greater than the priority of the PUCCH carrying SR which is greater than the priority of the PUCCH carrying CSI;

[0074] The priority of the later-scheduled PUCCH is higher than that of the earlier-scheduled PUCCH; it can be understood that the later-scheduled / earlier-scheduled PUCCH means that the start / end position of the Physical Downlink Control Channel (PDCCH) / Control Resource Set (CORESET) corresponding to the Downlink Control Information (DCI) corresponding to the PUCCH is later / earlier.

[0075] The priority of the dynamically scheduled PUCCH is higher than that of the configured PUCCH. It can be understood that the dynamically scheduled PUCCH can be the PUCCH scheduled by DCI. For example, the PUCCH that feeds back the Hybrid Automatic Repeat Request - Acknowledgment (HARQ-ACK) of the Physical Downlink Shared Channel (PDSCH) scheduled by DCI, and the configured PUCCH can be the PUCCH that the base station configures the UE to transmit through high-layer signaling. For example, the Scheduling Request (SR) PUCCH, the periodic CSI PUCCH.

[0076] Optionally, the terminal sends multiple PUCCHs through multiple frequency-domain units, including at least one of the following:

[0077] The terminal sends PUCCHs with different priorities through multiple frequency-domain units, and different frequency-domain units carry PUCCHs with different priorities;

[0078] The terminal sends PUCCHs with different priorities through multiple frequency-domain units, and the same frequency-domain unit carries PUCCHs with the same priority;

[0079] The terminal sends PUCCHs carrying different UCI types through multiple frequency-domain units, and different frequency-domain units carry PUCCHs with different UCI types;

[0080] The terminal sends PUCCHs carrying different UCI types through multiple frequency-domain units, and the same frequency-domain unit carries PUCCHs with the same UCI type;

[0081] The terminal sends PUCCHs with different scheduling types through multiple frequency-domain units, and different frequency-domain units carry PUCCHs with different scheduling types;

[0082] The terminal sends PUCCHs carrying different scheduling types through multiple frequency-domain units, and the same frequency-domain unit carries PUCCHs with the same scheduling type.

[0083] For example, when the UE supports / is enabled to simultaneously transmit PUCCH on different frequency domain units, the base station schedules / configures the UE to transmit PUCCH carrying different priorities on different frequency domain units, and the base station schedules / configures the UE to transmit PUCCH carrying the same priority on the same frequency domain unit. The UE sends PUCCH with different priorities through multiple frequency domain units, and different frequency domain units carry PUCCH with different priorities; the UE sends PUCCH with different priorities through multiple frequency domain units, and the same frequency domain unit carries PUCCH with the same priority. The priority of PUCCH can be the physical layer priority or can be represented by a priority index. For example, a priority index of 1 indicates a high priority, and a priority index of 0 indicates a low priority.

[0084] The association relationship between the PUCCH priority and the frequency domain unit can be determined by a predefined rule / high-layer configuration / base station scheduling. For example, the base station configures the PUCCH with a high priority to be transmitted on frequency domain unit A, and the PUCCH with a low priority to be transmitted on frequency domain unit B, or the PUCCH with a high priority is transmitted on the frequency domain unit with the lowest frequency domain index / the largest bandwidth in the active UL frequency domain unit, and the PUCCH with a low priority is transmitted on the frequency domain unit with the highest frequency domain index / the largest frequency domain interval from the frequency domain unit where the high priority is located in the active UL frequency domain unit.

[0085] It should be noted that: in the embodiments of the present application, the frequency domain units for transmitting PUCCH with a high priority or the frequency domain units where PUCCH with a low priority is transmitted can be different in different time domain units (i.e., can be dynamically changed, for example, can be changed according to the dynamic scheduling of the base station, or the base station can flexibly indicate. It can be understood that if the overlapping time of the UE is scheduled to transmit PUCCH with different priorities, then the PUCCH with different priorities is on different frequency domain units).

[0086] For another example, when the UE supports / is enabled to simultaneously transmit PUCCH on different frequency domain units, the base station schedules / configures the UE to transmit PUCCH of different UCI types on different frequency domain units, and the base station schedules / configures the UE to transmit PUCCH carrying the same UCI type on the same frequency domain unit. The UE sends PUCCH carrying different UCI types through multiple frequency domain units, and different frequency domain units carry PUCCH of different UCI types; the UE sends PUCCH carrying different UCI types through multiple frequency domain units, and the same frequency domain unit carries PUCCH of the same UCI type.

[0087] The association relationship between the UCI type and the frequency domain unit can be determined by a predefined rule / high-layer configuration / base station scheduling. The PUCCH of UCI type A (such as HAQ-ACK) is in the frequency domain unit with the lowest frequency domain index / the largest bandwidth in the activated UL frequency domain unit, and the PUCCH of UCI type B (such as CSI) is in the frequency domain unit with the second lowest frequency domain index / the largest frequency domain interval from the frequency domain unit where the high priority is located in the activated UL frequency domain unit.

[0088] The UCI type can include at least one of the following:

[0089] HARQ-ACK;

[0090] Scheduling Request (SR);

[0091] Channel State Information (CSI).

[0092] It should be noted that: in the embodiments of the present application, the frequency domain unit where the PUCCH for transmitting a certain UCI type is located can be different in different time domain units (that is, it can change dynamically, or the base station can flexibly indicate. It can be understood that if the UE's overlapping time is scheduled to transmit PUCCHs of different UCI types, then the PUCCHs of the different UCI types are in different frequency domain units).

[0093] For another example, when the UE supports / is enabled to transmit PUCCHs in different frequency domain units simultaneously, the base station schedules / configures the UE to transmit different types of PUCCHs in different frequency domain units. The different types of PUCCHs can be DCI-scheduled and non-DCI-scheduled (also can be called configured transmission / semi-static transmission, for example, SR, Semi-Persistent Scheduling (SPS) CSI, P CSI, etc.). The UE sends PUCCHs of different scheduling types through multiple frequency domain units, and different frequency domain units carry PUCCHs of different scheduling types; the UE sends PUCCHs carrying different scheduling types through multiple frequency domain units, and the same frequency domain unit carries PUCCHs of the same scheduling type.

[0094] The base station configures the semi-static transmission PUCCH (such as P-CSIPUCCH, SP-CSIPUCCH, SR PUCCH) to be transmitted in frequency domain unit A, and the dynamically scheduled PUCCH is in frequency domain unit B, where frequency domain unit B can be dynamically determined according to the scheduling indication of the base station.

[0095] It should be noted that: in the embodiments of the present application, the frequency domain units where the PUCCHs scheduled by DCI are transmitted may be different in different time domain units (i.e., they may change dynamically or be flexibly indicated by the base station). The frequency domain units where the PUCCHs not scheduled by DCI are transmitted may be determined according to the high-layer configuration.

[0096] Optionally, the terminal sends multiple PUCCHs through multiple frequency domain units, including:

[0097] The multiple PUCCHs sent by the terminal through multiple frequency domain units overlap or do not overlap in time.

[0098] In the embodiments of the present application, for a cell composed of multiple frequency domain units, each PUCCH resource may be configured / scheduled within one frequency domain unit.

[0099] As Figure 4 shown, there may be multiple frequency domain units with available PUCCH resources in the same time unit (overlapping in time), and the base station may configure / schedule multiple PUCCHs to be transmitted on multiple frequency domain units.

[0100] There may also be multiple frequency domain units with available PUCCH resources in different time units (not overlapping in time), and the base station may configure / schedule multiple PUCCHs to be transmitted on multiple frequency domain units.

[0101] Optionally, the method further includes:

[0102] The terminal determines the frequency domain units where the multiple PUCCHs are located according to a first parameter;

[0103] The first parameter includes at least one of the following:

[0104] The SCS corresponding to the downlink transmission;

[0105] The frequency domain unit corresponding to the downlink transmission;

[0106] The MCS corresponding to the downlink transmission;

[0107] The MCS corresponding to the uplink transmission;

[0108] The processing capacity corresponding to the downlink transmission;

[0109] The priority corresponding to the downlink transmission;

[0110] The Qos corresponding to the downlink transmission;

[0111] The Qos corresponding to the uplink transmission.

[0112] For example, when the UE supports / is enabled to simultaneously transmit PUCCH in different frequency domain units, the base station schedules / configures the UE to transmit different PUCCH in different frequency domain units according to the first parameter of the DL and / or UL. It can be understood that the PUCCH corresponding to the same (or the same range) of the first parameter is in one frequency domain unit, and the PUCCH corresponding to different (or different ranges) of the first parameter is in different frequency domain units.

[0113] The first parameter includes at least one of the following:

[0114] The SCS corresponding to the downlink transmission;

[0115] The frequency domain unit corresponding to the downlink transmission;

[0116] The MCS corresponding to the downlink transmission;

[0117] The MCS corresponding to the uplink transmission;

[0118] The processing capacity corresponding to the downlink transmission;

[0119] The priority corresponding to the downlink transmission;

[0120] The Qos corresponding to the downlink transmission;

[0121] The Qos corresponding to the uplink transmission.

[0122] For example, the UE can be scheduled / configured to transmit different PUCCH in different frequency domain units by the subcarrier spacing (SCS) corresponding to the downlink transmission. For example, the PDSCH with an SCS of 15 kHz feeds back HARQ-ACK in frequency domain unit A, and the PDSCH with an SCS of 30 kHz feeds back HARQ-ACK in frequency domain unit B.

[0123] For another example, the UE can be scheduled / configured to transmit different PUCCH in different frequency domain units by the SCS corresponding to the downlink transmission and the Quality of Service (QoS) corresponding to the downlink transmission.

[0124] For another example, the UE can be scheduled / configured to transmit different PUCCH in different frequency domain units by the SCS corresponding to the downlink transmission, the Modulation and Coding Scheme (MCS) corresponding to the uplink transmission, and the processing capacity corresponding to the downlink transmission.

[0125] Among them, regarding the processing capabilities corresponding to downlink transmission: For example, the HARQ-ACK corresponding to the processing capability 1 of PDSCH is fed back in frequency domain unit A, and the HARQ-ACK corresponding to the processing capability 2 of PDSCH is fed back in frequency domain unit B, where A and B can be pre-configured or flexibly determined according to the dynamic scheduling of the base station.

[0126] Regarding the Qos corresponding to downlink transmission and / or the previous transmission: For example, grouping according to the delay requirement (low-delay in one frequency domain unit, high-delay in another frequency domain unit, and the low and high delays can be a range), or grouping according to the transmission reliability requirement (for example, high reliability can be characterized by a lower MCS, code rate Alpha / Beta, or higher power, etc.).

[0127] Optionally, the method further includes:

[0128] The terminal determines the association relationship between the downlink frequency domain unit and the frequency domain unit for transmitting PUCCH through at least one of the following methods:

[0129] Higher layer signaling configuration;

[0130] DCI indication;

[0131] Pre-defined.

[0132] For example, when the UE supports / is enabled to transmit PUCCH simultaneously in different frequency domain units, the association between the downlink frequency domain unit n and the frequency domain unit m where the above PUCCH is located is determined through at least one of the following methods (i.e., for the downlink transmission in the downlink frequency domain unit n, such as PDCCH, PDSCH, the feedback is performed in the uplink frequency domain unit m, such as HARQ-ACK feedback):

[0133] The base station configures through higher layer signaling that one downlink frequency domain unit is only associated with one uplink frequency domain unit, or the base station configures one downlink frequency domain unit to be associated with one or more uplink frequency domain units through higher layer signaling (such as RRC);

[0134] For the uplink PUCCH transmission without DCI scheduling, through activating DCI or higher layer configuration / pre-definition;

[0135] For the uplink PUCCH transmission with DCI scheduling, through the scheduling DCI indication.

[0136] Optionally, for the configuration through higher layer signaling:

[0137] If the high-layer signaling configures a downlink frequency-domain unit to be associated with multiple uplink frequency-domain units, the frequency-domain units are selected in the order of priority (for example, a primary frequency-domain unit is set). If the frequency-domain unit with a higher priority (for example, the frequency-domain unit with good channel quality / low index has a higher priority) is not activated, then the frequency-domain unit with a lower priority is selected (for example, the frequency-domain unit with poor channel quality / high index has a lower priority). If all the associated frequency-domain units are not activated, then one with a higher priority is selected from the non-activated frequency-domain units and activated.

[0138] The downlink frequency-domain unit is indicated to be associated with one frequency-domain unit through a Media Access Control Control Element (MAC CE) or DCI (if the high-layer signaling configures a downlink frequency-domain unit to be associated with multiple uplink frequency-domain units).

[0139] If the uplink frequency-domain unit associated with the downlink frequency-domain unit indicated by the high-layer configuration and / or MAC CE is deactivated, according to the predefined rules, the downlink frequency-domain unit is associated with another / default frequency-domain unit / an activated uplink frequency-domain unit (when the UE has only one activated uplink frequency-domain unit).

[0140] Optionally, for an uplink PUCCH transmission without DCI scheduling, such as SPS HARQ-ACK, if the uplink frequency-domain unit associated with the downlink frequency-domain unit is deactivated, according to the predefined rules, the downlink frequency-domain unit is associated with another / default frequency-domain unit / an activated uplink frequency-domain unit (when the UE has only one activated uplink frequency-domain unit)

[0141] Optionally, for an uplink PUCCH transmission with DCI scheduling, such as a Dynamic Grant (DG) PDSCH HARQ-ACK. The UE expects to be scheduled on the activated uplink frequency-domain unit.

[0142] Figure 3 This is the second schematic diagram of the process of the PUCCH transmission method provided by the embodiments of this application. As Figure 3 shown, the method includes the following steps:

[0143] Step 300: The network-side device receives multiple PUCCHs through multiple frequency-domain units, where multiple frequency-domain units are available for receiving PUCCHs.

[0144] In the implementation of this application, a cell consists of at least one frequency-domain unit. A frequency-domain unit is a group of continuous frequency-domain resources, which can be a band, a carrier, a subband, a BWP, etc. Different frequency-domain units can have the same or different sizes, and different frequency-domain units can be discontinuous. For example, a cell consists of four frequency-domain units, and the sizes of these four frequency-domain units are 3 MHz, 10 MHz, 5 MHz, and 5 MHz respectively.

[0145] For a cell consisting of multiple frequency-domain units, each PUCCH resource can be configured / scheduled within one frequency-domain unit. At the same time unit, there can be multiple frequency-domain units with available PUCCH resources, and the base station can configure / schedule multiple PUCCHs to be transmitted on multiple frequency-domain units. The UE sends multiple PUCCHs through multiple frequency-domain units. The network-side device receives multiple PUCCHs through multiple frequency-domain units.

[0146] It is also possible that at different time units, there are multiple frequency-domain units with available PUCCH resources, and the base station can configure / schedule multiple PUCCHs to be transmitted on multiple frequency-domain units. The UE sends multiple PUCCHs through multiple frequency-domain units. The network-side device receives multiple PUCCHs through multiple frequency-domain units.

[0147] Optionally, the time unit can be a time period such as a symbol, a set of symbols, a time slot, a sub-time slot, a frame, etc., and is not specifically limited.

[0148] In the embodiments of this application, the terminal sends multiple PUCCHs through multiple frequency-domain units, which can ensure the transmission of low-priority PUCCHs, reduce the transmission delay, and can more flexibly and efficiently utilize the spectrum resources of the cell to improve the effectiveness and performance of the communication system.

[0149] Optionally, the method further includes:

[0150] The network-side device configures or schedules the UE to transmit PUCCHs with different priorities / UCI types / scheduling types on different frequency-domain units.

[0151] For example, for a cell consisting of multiple frequency-domain units, each PUCCH resource can be configured / scheduled within one frequency-domain unit. At the same time unit, there can be multiple frequency-domain units with available PUCCH resources, and the base station can configure / schedule multiple PUCCHs to be transmitted on multiple frequency-domain units.

[0152] The methods provided in the embodiments of this application are based on the same inventive concept. Therefore, the implementations of the methods can be referred to each other, and the repeated parts will not be elaborated.

[0153] The following uses embodiments of specific application scenarios to illustrate the methods provided in the above embodiments of this application.

[0154] Embodiment 1:

[0155] Assume that a cell consists of four frequency domain units, and the sizes of these four frequency domain units (0 - 3) are 5 MHz, 10 MHz, 5 MHz, and 20 MHz respectively. In the same time unit, a UE can have one or more active frequency domain units. The base station can configure PUCCH resources in the following manner.

[0156] In the same time unit, there can be multiple frequency domain units with available PUCCH resource configurations. For example, the base station configures PUCCH transmission resources on each frequency domain resource respectively, or the base station configures PUCCH resources common to the frequency domain resources. The base station can configure or instruct the UE to perform PUCCH transmission on multiple frequency domain units. In the same time unit, the base station can configure or schedule the UE to transmit different PUCCHs on different frequency domain units. Among them

[0157] If the UE does not support / is not enabled to transmit PUCCH simultaneously on different frequency domain units, at a certain time, the UE expects to be instructed to transmit PUCCH on the same frequency domain unit. Otherwise, if the UE is configured or instructed to transmit different PUCCHs on different frequency domain units, the UE discards some PUCCH transmissions or the UE multiplexes part or all of the UCI on different PUCCHs onto one channel for transmission.

[0158] If the UE supports / is enabled to transmit PUCCH simultaneously on different frequency domain units, then if the UE is configured or instructed to transmit different PUCCHs on the frequency domain units, the UE transmits different PUCCHs on the respective configured or instructed frequency domain units.

[0159] Optionally, the above UE supports transmitting PUCCH in different frequency domain units, and the different frequency domain units meet the second requirement. For example, the different frequency domain units belong to different frequency domain unit groups / frequency domain unit subsets / frequency domain unit sets (the frequency domain unit groups / frequency domain unit subsets / frequency domain unit sets can be predefined by the protocol or reported by the UE / configured by the base station), and the interval between different frequency domain units meets the first requirement, etc. In one implementation, when the base station configures or instructs the UE to transmit different PUCCHs in different frequency domain units and ensures that the different frequency domain units meet the second requirement, the UE transmits its respective PUCCHs in different frequency domain units according to the base station configuration or instruction. In one implementation, when the base station configures or instructs the UE to transmit different PUCCHs in different frequency domain units, if the different frequency domain units do not meet the second requirement, the UE transmits some of the different PUCCHs according to predefined rules, such as the corresponding priority of the PUCCH / earlier or later scheduling time / earlier or later transmission time / bearing content / scheduling type (such as the priority of dynamic scheduling is semi-statically configured). For example, the UE determines to transmit the PUCCH with the highest transmission priority, does not transmit / discard / cancel the PUCCH that cannot be transmitted simultaneously with the highest priority. If there are still remaining PUCCHs, repeat the above steps among the remaining PUCCHs until the PUCCHs to be transmitted (i.e., the PUCCHs that are not transmitted / discarded / canceled) meet certain requirements.

[0160] Embodiment 2:

[0161] Suppose a cell consists of four frequency domain units, and the sizes of these four frequency domain units (0 - 3) are 5MHz, 10MHz, 5MHz, and 20MHz respectively. In the same time unit, the UE can have one or more active frequency domain units.

[0162] In one implementation, the base station indicates or configures PUCCH transmission on different frequency domain units. Among them, the base station configures the UE to transmit PUCCHs with different priorities on different frequency domain units (for example, using a priority index). For example, the base station configures or instructs the UE to transmit a high-priority PUCCH on frequency domain unit 0 and a low-priority PUCCH on frequency domain unit 1. When the UE supports transmitting PUCCHs simultaneously on different frequency domain units, in this implementation, different-priority PUCCHs can be transmitted separately, which can ensure the transmission of PUCCHs and the reliability of PUCCH transmission, and avoid the problem of PUCCH overlap between different priorities (in the prior art, when different-priority PUCCHs overlap, the UE either discards the low-priority PUCCH, unable to ensure the transmission of the low-priority PUCCH and its delay, or multiplexes different-priority UCIs on one channel for transmission, increasing the processing complexity of the UE), and reduces the transmission delay of PUCCHs, etc.

[0163] Embodiment 3:

[0164] Suppose a cell consists of four frequency domain units, and the sizes of these four frequency domain units (0 - 3) are 5 MHz, 10 MHz, 5 MHz, and 20 MHz respectively. In the same time unit, the UE can have one or more active frequency domain units.

[0165] In one implementation, the base station indicates or configures PUCCH transmission on different frequency domain units. The base station configures the UE to transmit PUCCH carrying different UCI types (such as HARQ - ACK, CSI, SR, LRR, etc.) on different frequency domain units.

[0166] In one implementation, the base station configures or indicates the UE to transmit HARQ - ACK on frequency domain unit 0, CSI on frequency domain unit 1, and SR on frequency domain unit 3.

[0167] In another implementation, the base station configures or indicates the UE to transmit HARQ - ACK on frequency domain unit 0, and CSI and SR on frequency domain unit 1.

[0168] In another implementation, the base station configures or indicates the UE to transmit HARQ - ACK and SR on frequency domain unit 0, and CSI and SR on frequency domain unit 1. The SR can be configured or indicated to be transmitted on either one or both of frequency domain unit 0 or frequency domain unit 1 (optionally, for a certain SR, it is only transmitted on one frequency domain unit).

[0169] Example 4:

[0170] Suppose a cell consists of four frequency domain units, and the sizes of these four frequency domain units (0 - 3) are 5 MHz, 10 MHz, 5 MHz, and 20 MHz respectively. In the same time unit, the UE can have one or more active frequency domain units.

[0171] In one embodiment, the base station indicates or configures PUCCH transmission on different frequency domain units. The base station configures the UE to transmit HARQ-ACK corresponding to downlink transmissions with different PDSCH processing capabilities on different frequency domain units. For example, the processing capabilities corresponding to downlink transmissions of PDCCH / PDSCH are processing capability 1 and processing capability 2, where processing capability 2 is stronger / faster than processing capability 1. In the prior art, due to some implementation problems, for the scheduling of PDSCH, it is required that the first scheduled be fed back first, and the later scheduled cannot be fed back first. When the UE supports transmitting different PUCCHs simultaneously on different frequency domain units, the base station can schedule the HARQ-ACK of the downlink transmission corresponding to processing capability 1 to be fed back on one frequency domain unit, and schedule the HARQ-ACK of the downlink transmission corresponding to processing capability 2 to be fed back on another frequency domain unit. In this way, for the scheduling of PDSCH, only the downlink transmissions corresponding to the same capability need to be fed back in the order of first scheduled first, and for the downlink transmissions corresponding to different processing capabilities, their scheduling orders are independent of each other and there is no restriction. This can reduce the HARQ-ACK feedback delay of high-processing-capability downlink transmissions and improve the system throughput when there are mixed processing capabilities in downlink transmissions.

[0172] Embodiment 5:

[0173] Assume that a cell consists of four frequency domain units, and the sizes of these four frequency domain units (0 - 3) are 5MHz, 10MHz, 5MHz, and 20MHz respectively. In the same time unit, the UE can have one or more active frequency domain units. The UE can transmit PUCCH on multiple frequency domain units. For a certain downlink frequency domain unit n, the frequency domain unit m where the HARQ-ACK corresponding to its downlink transmission is located (i.e., the downlink transmission in downlink frequency domain unit n is fed back in uplink frequency domain unit m) can be determined by at least one of the following:

[0174] The base station configures the association relationship between the downlink frequency domain unit and the uplink frequency domain unit through high-layer signaling, such as RRC / MAC CE. One downlink frequency domain unit can be associated with at most one uplink frequency domain unit.

[0175] Alternatively, the base station configures the association relationship between the downlink frequency domain unit and the uplink frequency domain unit through high-layer signaling, such as RRC / MAC CE. One downlink frequency domain unit can be associated with multiple uplink frequency domain units. When a downlink frequency domain unit is associated with multiple uplink frequency domain units, the base station indicates (such as MAC CE or DCI) that the downlink frequency domain unit is associated with one of the multiple uplink frequency domain units configured by the high layer, or the downlink frequency domain unit is associated with one of the multiple uplink frequency domain units configured by the high layer according to a predefined principle, such as the one with the smallest index among the active frequency domain units among the multiple uplink frequency domain units.

[0176] Alternatively, for uplink PUCCH transmissions without DCI scheduling, such as SPS HARQ-ACK, it is through activating DCI or higher layer configuration. If the uplink frequency domain unit associated with the downlink frequency domain unit is deactivated, according to predefined rules, the downlink frequency domain unit is associated with another / default frequency domain unit / activated uplink frequency domain unit (when the UE has only one activated uplink frequency domain unit). For uplink PUCCH transmissions with DCI scheduling, such as DG PDSCH HARQ-ACK, it is indicated by the scheduling DCI.

[0177] Optionally, if the uplink frequency domain unit associated with a certain downlink frequency domain unit configured by the higher layer is deactivated, then the uplink frequency domain unit associated with the downlink frequency domain unit is determined according to predefined rules, such as the frequency domain unit with the smallest index / lowest frequency among the currently activated uplink frequency domain units or the default frequency domain unit, etc.

[0178] In the method for PUCCH transmission provided by the embodiments of this application, the execution subject may be a PUCCH transmission device. In the embodiments of this application, taking the PUCCH transmission device executing the PUCCH transmission method as an example, the PUCCH transmission device provided by the embodiments of this application is described.

[0179] Figure 5 It is one of the schematic structural diagrams of the PUCCH transmission device provided by the embodiments of this application, as Figure 5 shown, the embodiments of this application provide a PUCCH transmission device 500, including:

[0180] A first transmission module 510 transmits multiple PUCCHs through multiple frequency domain units, where there are multiple frequency domain units available for transmitting PUCCHs.

[0181] Optionally, the device further includes:

[0182] A reporting module, configured to report at least one of the following capability information to the network side device:

[0183] Whether the terminal can support simultaneous PUCCH transmission in different frequency domain units;

[0184] The terminal can support simultaneous PUCCH transmission in different frequency domain units;

[0185] The number of PUCCHs that the terminal supports to be simultaneously transmitted in different frequency domain units;

[0186] The frequency domain units that the terminal supports for simultaneous PUCCH transmission;

[0187] The minimum interval between the frequency domain units that the terminal supports for simultaneous PUCCH transmission.

[0188] Optionally, the multiple frequency-domain units belong to different frequency-domain unit groups / sets.

[0189] Optionally, the frequency-domain interval between the multiple frequency-domain units meets a first requirement.

[0190] Optionally, sending multiple PUCCHs through multiple frequency-domain units includes:

[0191] When the number of PUCCHs to be sent simultaneously is greater than the number of PUCCHs that the terminal supports to be sent simultaneously in different frequency-domain units, perform PUCCH transmission in at least one of the following manners:

[0192] Discard some PUCCHs according to a preset rule, and send the remaining PUCCHs through multiple frequency-domain units;

[0193] Multiplex at least part of the UCI carried by some PUCCHs on other channels for transmission according to a preset rule, and send the remaining PUCCHs through multiple frequency-domain units.

[0194] Optionally, sending multiple PUCCHs through multiple frequency-domain units includes at least one of the following:

[0195] Send PUCCHs with different priorities through multiple frequency-domain units, and different frequency-domain units carry PUCCHs with different priorities;

[0196] Send PUCCHs with different priorities through multiple frequency-domain units, and the same frequency-domain unit carries PUCCHs with the same priority;

[0197] Send PUCCHs carrying different types of uplink control information (UCI) through multiple frequency-domain units, and different frequency-domain units carry PUCCHs with different UCI types;

[0198] Send PUCCHs carrying different UCI types through multiple frequency-domain units, and the same frequency-domain unit carries PUCCHs with the same UCI type;

[0199] Send PUCCHs with different scheduling types through multiple frequency-domain units, and different frequency-domain units carry PUCCHs with different scheduling types;

[0200] Send PUCCHs carrying different scheduling types through multiple frequency-domain units, and the same frequency-domain unit carries PUCCHs with the same scheduling type.

[0201] Optionally, sending multiple PUCCHs through multiple frequency-domain units includes:

[0202] The multiple PUCCHs sent through multiple frequency-domain units overlap or do not overlap in time.

[0203] Optionally, the apparatus further comprises:

[0204] A frequency domain unit determination module, configured to determine the frequency domain units where the plurality of PUCCHs are located according to a first parameter;

[0205] The first parameter includes at least one of the following:

[0206] The SCS corresponding to downlink transmission;

[0207] The frequency domain unit corresponding to downlink transmission;

[0208] The MCS corresponding to downlink transmission;

[0209] The MCS corresponding to uplink transmission;

[0210] The processing capacity corresponding to downlink transmission;

[0211] The priority corresponding to downlink transmission;

[0212] The Qos corresponding to downlink transmission;

[0213] The Qos corresponding to uplink transmission.

[0214] Optionally, the apparatus further comprises:

[0215] A relationship determination module, configured to determine the association relationship between the downlink frequency domain unit and the frequency domain unit for transmitting PUCCH through at least one of the following manners:

[0216] High-layer signaling configuration;

[0217] DCI indication;

[0218] Predefined.

[0219] In the embodiments of the present application, the terminal transmits multiple PUCCHs through multiple frequency domain units. Among them, there are multiple frequency domain units available for transmitting PUCCH. When multiple PUCCHs need to be transmitted, multiple PUCCHs are transmitted simultaneously through different frequency domain units, reducing the communication delay and being able to more flexibly and efficiently utilize the spectrum resources of the cell to improve the effectiveness and performance of the communication system.

[0220] Figure 6 This is the second structural schematic diagram of the PUCCH transmission apparatus provided by the embodiments of the present application. As Figure 6 shown, the embodiments of the present application provide a PUCCH transmission apparatus 600, including:

[0221] A first receiving module 610, configured to receive multiple PUCCHs through multiple frequency domain units, where there are multiple frequency domain units available for receiving PUCCH.

[0222] Optionally, the apparatus further comprises:

[0223] Configure a scheduling module for configuring or scheduling the UE to transmit PUCCHs with different priorities / UCI types / scheduling types in different frequency domain units.

[0224] Optionally, the apparatus further comprises:

[0225] A second receiving module, configured to receive at least one of the following reported by a terminal:

[0226] Whether the terminal can support simultaneous transmission of PUCCHs in different frequency domain units;

[0227] The terminal can support simultaneous transmission of PUCCHs in different frequency domain units;

[0228] The number of PUCCHs that the terminal supports and can be simultaneously transmitted in different frequency domain units;

[0229] The frequency domain units that the terminal supports and can be used for simultaneous transmission of PUCCHs;

[0230] The minimum interval between the frequency domain units that the terminal supports and can be used for simultaneous transmission of PUCCHs.

[0231] Optionally, the multiple frequency domain units belong to different frequency domain unit groups / sets.

[0232] Optionally, the frequency domain interval between the multiple frequency domain units meets a first requirement.

[0233] Optionally, the apparatus further comprises:

[0234] A second transmitting module, configured to transmit a first parameter to a terminal; the first parameter is used to determine the frequency domain units where the multiple PUCCHs are located;

[0235] The first parameter includes at least one of the following:

[0236] The SCS corresponding to downlink transmission;

[0237] The frequency domain unit corresponding to downlink transmission;

[0238] The MCS corresponding to downlink transmission;

[0239] The MCS corresponding to uplink transmission;

[0240] The processing capacity corresponding to downlink transmission;

[0241] The priority corresponding to downlink transmission;

[0242] The Qos corresponding to downlink transmission;

[0243] The Qos corresponding to uplink transmission.

[0244] In an embodiment of the present application, a network-side device receives multiple PUCCHs through multiple frequency-domain units. Among them, there are multiple frequency-domain units available for receiving PUCCHs. When multiple PUCCHs need to be transmitted, the multiple PUCCHs are transmitted simultaneously through different frequency-domain units, reducing the communication delay and enabling more flexible and efficient utilization of the cell's spectrum resources to improve the effectiveness and performance of the communication system.

[0245] The PUCCH transmission device in the embodiment of the present application can be an electronic device, such as an electronic device with an operating system, or a component in an electronic device, such as an integrated circuit or a chip. The electronic device can be a terminal or other devices other than the terminal. Exemplarily, the terminal can include, but is not limited to, the types of the terminal 11 listed above, and other devices can be a server, a Network Attached Storage (NAS), etc., which are not specifically limited in the embodiment of the present application.

[0246] The PUCCH transmission device provided in the embodiment of the present application can implement each process implemented in the above method embodiments and achieve the same technical effects. To avoid repetition, it will not be elaborated here.

[0247] As Figure 7 shown, the embodiment of the present application further provides a communication device 700, including a processor 701 and a memory 702. A program or instruction that can run on the processor 701 is stored on the memory 702. For example, when the communication device 700 is a terminal, when the program or instruction is executed by the processor 701, it implements each step of the PUCCH transmission method embodiment corresponding to the above terminal and can achieve the same technical effects. When the communication device 700 is a network-side device, when the program or instruction is executed by the processor 701, it implements each step of the PUCCH transmission method embodiment corresponding to the above network-side device and can achieve the same technical effects. To avoid repetition, it will not be elaborated here.

[0248] The embodiment of the present application further provides a terminal, including a processor and a communication interface. The communication interface is coupled to the processor. The processor is used to run a program or instruction to implement the steps in the method embodiment as Figure 2 shown. This terminal embodiment corresponds to the above terminal-side method embodiment. Each implementation process and implementation manner of the above method embodiment can be applied to this terminal embodiment and can achieve the same technical effects. Specifically, Figure 8 is a schematic diagram of the hardware structure of a terminal for implementing an embodiment of the present application.

[0249] The terminal 800 includes, but is not limited to, at least some components such as a radio frequency unit 801, a network module 802, an audio output unit 803, an input unit 804, a sensor 805, a display unit 808, a user input unit 807, an interface unit 808, a memory 809, and a processor 810.

[0250] Those skilled in the art can understand that the terminal 800 may further include a power supply (such as a battery) for supplying power to each component. The power supply can be logically connected to the processor 810 through a power management system, so as to implement functions such as management of charging, discharging, and power consumption management through the power management system. Figure 8 The terminal structure shown does not limit the terminal. The terminal may include more or fewer components than shown in the figure, or combine some components, or have different component arrangements, which will not be elaborated here.

[0251] It should be understood that in the embodiments of the present application, the input unit 804 may include a graphics processing unit (GPU) 8041 and a microphone 8042. The graphics processing unit 8041 processes the image data of still pictures or videos obtained by an image capture device (such as a camera) in a video capture mode or an image capture mode. The display unit 806 may include a display panel 8061, and the display panel 8061 may be configured in the form of a liquid crystal display, an organic light emitting diode, etc. The user input unit 807 includes at least one of a touch panel 8071 and other input devices 8072. The touch panel 8071 is also called a touch screen. The touch panel 8071 may include two parts: a touch detection device and a touch controller. The other input devices 8072 may include, but are not limited to, a physical keyboard, function keys (such as volume control keys, switch keys, etc.), a trackball, a mouse, and a joystick, which will not be elaborated here.

[0252] In the embodiments of the present application, after the radio frequency unit 801 receives downlink data from a network-side device, it can be transmitted to the processor 810 for processing; in addition, the radio frequency unit 801 can send uplink data to the network-side device. Generally, the radio frequency unit 801 includes, but is not limited to, an antenna, an amplifier, a transceiver, a coupler, a low-noise amplifier, a duplexer, etc.

[0253] The memory 809 can be used to store software programs or instructions and various data. The memory 809 may mainly include a first storage area for storing programs or instructions and a second storage area for storing data. Among them, the first storage area may store an operating system, application programs or instructions required for at least one function (such as a sound playback function, an image playback function, etc.). In addition, the memory 809 may include volatile memory or non-volatile memory. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), a static random access memory (SRAM), a dynamic random access memory (DRAM), a synchronous dynamic random access memory (SDRAM), a double data rate synchronous dynamic random access memory (DDR SDRAM), an enhanced synchronous dynamic random access memory (ESDRAM), a synchronous link dynamic random access memory (SLDRAM), and a direct rambus random access memory (DRRAM). The memory 809 in the embodiments of the present application includes but is not limited to these and any other suitable types of memory.

[0254] The processor 810 may include one or more processing units; optionally, the processor 810 integrates an application processor and a modem processor. Among them, the application processor mainly processes operations related to the operating system, user interface, and application programs, etc., and the modem processor mainly processes wireless communication signals, such as a baseband processor. It can be understood that the above modem processor may not be integrated into the processor 810 either.

[0255] Among them, the radio frequency unit 801 is used to send multiple PUCCHs through multiple frequency domain units, where there are multiple frequency domain units available for sending PUCCHs.

[0256] Optionally, the radio frequency unit 801 is used to report at least one of the following capability information to the network-side device:

[0257] Whether the terminal can support simultaneous transmission of PUCCH in different frequency domain units;

[0258] The terminal is capable of supporting simultaneous transmission of PUCCH in different frequency domain units;

[0259] The number of PUCCHs that the terminal supports to be simultaneously transmitted in different frequency domain units;

[0260] The frequency domain units that the terminal supports for simultaneous transmission of PUCCH;

[0261] The minimum interval between the frequency domain units that the terminal supports for simultaneous transmission of PUCCH.

[0262] Optionally, the multiple frequency domain units belong to different frequency domain unit groups / sets.

[0263] Optionally, the frequency domain interval between the multiple frequency domain units meets the first requirement.

[0264] Optionally, the transmission of multiple PUCCHs through multiple frequency domain units includes:

[0265] When the number of PUCCHs to be simultaneously transmitted is greater than the number of PUCCHs that the terminal supports to be simultaneously transmitted in different frequency domain units, the PUCCH is transmitted in at least one of the following ways:

[0266] Discard some PUCCHs according to a preset rule and transmit the remaining PUCCHs through multiple frequency domain units;

[0267] Multiplex at least part of the UCI carried by some PUCCHs on other channels for transmission according to a preset rule and transmit the remaining PUCCHs through multiple frequency domain units.

[0268] Optionally, the transmission of multiple PUCCHs through multiple frequency domain units includes at least one of the following:

[0269] Transmit PUCCHs with different priorities through multiple frequency domain units, and different frequency domain units carry PUCCHs with different priorities;

[0270] Transmit PUCCHs with different priorities through multiple frequency domain units, and the same frequency domain unit carries PUCCHs with the same priority;

[0271] Transmit PUCCHs carrying different UCI types through multiple frequency domain units, and different frequency domain units carry PUCCHs carrying different UCI types;

[0272] Transmit PUCCHs carrying different UCI types through multiple frequency domain units, and the same frequency domain unit carries PUCCHs carrying the same UCI type;

[0273] Transmit PUCCHs of different scheduling types through multiple frequency-domain units, where different frequency-domain units carry PUCCHs of different scheduling types;

[0274] Transmit PUCCHs carrying different scheduling types through multiple frequency-domain units, where the same frequency-domain unit carries PUCCHs of the same scheduling type.

[0275] Optionally, the transmitting of multiple PUCCHs through multiple frequency-domain units includes:

[0276] The multiple PUCCHs transmitted through multiple frequency-domain units overlap or do not overlap in time.

[0277] Optionally, a processor 810 is configured to determine the frequency-domain units where the multiple PUCCHs are located according to a first parameter;

[0278] The first parameter includes at least one of the following:

[0279] The SCS corresponding to the downlink transmission;

[0280] The frequency-domain unit corresponding to the downlink transmission;

[0281] The MCS corresponding to the downlink transmission;

[0282] The MCS corresponding to the uplink transmission;

[0283] The processing capacity corresponding to the downlink transmission;

[0284] The priority corresponding to the downlink transmission;

[0285] The Qos corresponding to the downlink transmission;

[0286] The Qos corresponding to the uplink transmission.

[0287] Optionally, a processor 810 is configured to determine the association relationship between the downlink frequency-domain unit and the frequency-domain unit used to transmit the PUCCH through at least one of the following methods:

[0288] Higher-layer signaling configuration;

[0289] DCI indication;

[0290] Predefined.

[0291] In the embodiments of the present application, a terminal transmits multiple PUCCHs through multiple frequency-domain units. Among them, there are multiple frequency-domain units available for transmitting PUCCHs. When multiple PUCCHs need to be transmitted, multiple PUCCHs are simultaneously transmitted through different frequency-domain units, reducing the communication delay and enabling more flexible and efficient utilization of the cell's spectrum resources to improve the effectiveness and performance of the communication system.

[0292] It can be understood that the implementation processes of the various implementation manners mentioned in this embodiment can refer to the relevant descriptions of the method embodiment and achieve the same or corresponding technical effects. To avoid repetition, they will not be elaborated herein.

[0293] The embodiment of the present application further provides a network-side device, including a processor and a communication interface. The communication interface is coupled to the processor. The processor is used to run programs or instructions to implement the steps of the method embodiment as Figure 5 shown. This embodiment of the network-side device corresponds to the above-mentioned method embodiment of the network-side device. Each implementation process and implementation manner of the above method embodiment can be applied to this embodiment of the network-side device and can achieve the same technical effect.

[0294] Specifically, the embodiment of the present application further provides a network-side device. As Figure 9 shown, the network-side device 900 includes: an antenna 91, a radio frequency device 92, a baseband device 93, a processor 94, and a memory 95. The antenna 91 is connected to the radio frequency device 92. In the uplink direction, the radio frequency device 92 receives information through the antenna 91 and sends the received information to the baseband device 93 for processing. In the downlink direction, the baseband device 93 processes the information to be sent and sends it to the radio frequency device 92. After processing the received information, the radio frequency device 92 sends it out through the antenna 91.

[0295] The method executed by the network-side device in the above embodiments can be implemented in the baseband device 93. The baseband device 93 includes a baseband processor.

[0296] The baseband device 93 may include, for example, at least one baseband board, on which a plurality of chips are provided. As Figure 9 shown, one of the chips is, for example, a baseband processor, which is connected to the memory 95 through a bus interface to call the program in the memory 95 and execute the operations of the network-side device shown in the above method embodiments.

[0297] The network-side device may further include a network interface 96, which is, for example, a Common Public Radio Interface (CPRI).

[0298] Specifically, the network-side device 900 of the embodiment of the present application further includes: instructions or programs stored on the memory 95 and executable on the processor 94. The processor 94 calls the instructions or programs in the memory 95 to execute Figure 5 the methods executed by the respective modules shown and achieve the same technical effect. To avoid repetition, they will not be elaborated herein.

[0299] The embodiment of the present application further provides a readable storage medium, on which a program or instruction is stored. When the program or instruction is executed by a processor, each process of the above-described embodiment of the PUCCH transmission method is implemented, and the same technical effect can be achieved. To avoid repetition, it will not be elaborated here.

[0300] Wherein, the processor is the processor in the terminal or network-side device described in the above embodiment. The readable storage medium includes a computer-readable storage medium, such as a computer read-only memory ROM, a random access memory RAM, a magnetic disk, or an optical disc, etc. In some examples, the readable storage medium may be a non-transitory readable storage medium.

[0301] The embodiment of the present application further provides a chip, which includes a processor and a communication interface. The communication interface is coupled to the processor. The processor is used to run a program or instruction to implement each process of the above-described embodiment of the PUCCH transmission method, and the same technical effect can be achieved. To avoid repetition, it will not be elaborated here.

[0302] It should be understood that the chip mentioned in the embodiment of the present application may also be referred to as a system-on-chip, a system chip, a chip system, or a system-on-chip, etc.

[0303] The embodiment of the present application further provides a computer program / program product, which is stored in a storage medium. The computer program / program product is executed by at least one processor to implement each process of the above-described embodiment of the PUCCH transmission method, and the same technical effect can be achieved. To avoid repetition, it will not be elaborated here.

[0304] The embodiment of the present application further provides a PUCCH transmission system, including: a terminal and a network-side device. The terminal can be used to execute the steps of the PUCCH transmission method corresponding to the terminal as described above, and the network-side device can be used to execute the steps of the PUCCH transmission method corresponding to the network-side device as described above.

[0305] It should be noted that in this text, the term "including", "comprising", or any other variant thereof is intended to cover non-exclusive inclusion, such that a process, method, article, or device that includes a series of elements not only includes those elements but also other elements not explicitly listed, or elements that are inherent to such a process, method, article, or device. Without further limitation, an element defined by the statement "including one..." does not exclude the existence of additional identical elements in the process, method, article, or device that includes such an element. In addition, it should be pointed out that the scope of the methods and devices in the embodiments of the present application is not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in the reverse order according to the functions involved. For example, the described methods may be performed in an order different from that described, and various steps may be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

[0306] Through the description of the above embodiments, those skilled in the art can clearly understand that the above-described example methods can be implemented by means of a computer software product plus a necessary general hardware platform, and of course, they can also be implemented by hardware. This computer software product is stored in a storage medium (such as ROM, RAM, magnetic disk, optical disk, etc.) and includes several instructions for causing a terminal or a network-side device to execute the methods described in various embodiments of the present application.

[0307] The embodiments of the present application have been described above in conjunction with the accompanying drawings. However, the present application is not limited to the above specific embodiments. The above specific embodiments are merely illustrative and not restrictive. Under the inspiration of the present application, those of ordinary skill in the art can also make many forms of embodiments without departing from the purpose of the present application and the scope protected by the claims. All these embodiments fall within the protection scope of the present application.

Claims

1. A method for transmitting a Physical Uplink Control Channel (PUCCH), characterized in that, including: The terminal sends multiple PUCCHs through multiple frequency domain units, where there are multiple frequency domain units available for sending PUCCH.

2. The PUCCH transmission method according to claim 1, wherein The method further includes: The terminal reports at least one of the following capability information to the network side device: Whether the terminal can support simultaneous transmission of PUCCH in different frequency domain units; The terminal can support simultaneous transmission of PUCCH in different frequency domain units; The number of PUCCHs that the terminal supports for simultaneous transmission in different frequency domain units; The frequency domain units that the terminal supports for simultaneous transmission of PUCCH; The minimum interval between the frequency domain units that the terminal supports for simultaneous transmission of PUCCH.

3. The PUCCH transmission method according to claim 1, characterized in that, The multiple frequency domain units belong to different frequency domain unit groups / sets.

4. The PUCCH transmission method according to claim 1, wherein The frequency domain interval between the multiple frequency domain units meets the first requirement.

5. The PUCCH transmission method according to claim 1, wherein The terminal sends multiple PUCCHs through multiple frequency domain units, including: When the number of PUCCHs to be simultaneously sent is greater than the number of PUCCHs that the terminal supports for simultaneous transmission in different frequency domain units, the terminal performs PUCCH transmission in at least one of the following ways: The terminal discards some PUCCHs according to a preset rule and sends the remaining PUCCHs through multiple frequency domain units; The terminal multiplexes at least part of the uplink control information UCI carried by some PUCCHs on other channels for transmission and sends the remaining PUCCHs through multiple frequency domain units.

6. The PUCCH transmission method according to claim 1, wherein The terminal sends multiple PUCCHs through multiple frequency domain units, including at least one of the following: The terminal sends PUCCHs with different priorities through multiple frequency domain units, and different frequency domain units carry PUCCHs with different priorities; The terminal sends PUCCHs with different priorities through multiple frequency domain units, and the same frequency domain unit carries PUCCHs with the same priority; The terminal sends PUCCHs carrying different UCI types through multiple frequency domain units, and different frequency domain units carry PUCCHs with different UCI types; The terminal sends PUCCHs carrying different UCI types through multiple frequency domain units, and the same frequency domain unit carries PUCCHs with the same UCI type; The terminal sends PUCCHs with different scheduling types through multiple frequency domain units, and different frequency domain units carry PUCCHs with different scheduling types; The terminal sends PUCCHs carrying different scheduling types through multiple frequency domain units, and the same frequency domain unit carries PUCCHs with the same scheduling type.

7. The PUCCH transmission method according to claim 1, wherein The terminal sends multiple PUCCHs through multiple frequency domain units, including: The multiple PUCCHs sent by the terminal through multiple frequency domain units overlap or do not overlap in time.

8. The PUCCH transmission method according to claim 1, characterized in that, The method further includes: The terminal determines the frequency domain units where the multiple PUCCHs are located according to a first parameter; The first parameter includes at least one of the following: The subcarrier spacing SCS corresponding to the downlink transmission; The frequency domain unit corresponding to the downlink transmission; The modulation and coding scheme MCS corresponding to the downlink transmission; The MCS corresponding to the uplink transmission; The processing capability corresponding to the downlink transmission; The priority corresponding to the downlink transmission; The quality of service Qos corresponding to the downlink transmission; Qos corresponding to uplink transmission.

9. The PUCCH transmission method according to any one of claims 1 to 8, characterized in that, The method further includes: The terminal determines the association relationship between the downlink frequency domain unit and the frequency domain unit for transmitting PUCCH in at least one of the following ways: High-layer signaling configuration; Downlink control information DCI indication; Predefined.

10. A method for transmitting a Physical Uplink Control Channel (PUCCH), characterized in that, Including: The network-side device receives multiple PUCCHs through multiple frequency domain units, where there are multiple frequency domain units available for receiving PUCCH.

11. The PUCCH transmission method according to claim 10, wherein The method further includes: The network-side device configures or schedules the UE to transmit PUCCHs with different priorities / UCI types / scheduling types in different frequency domain units.

12. The PUCCH transmission method according to claim 10, wherein The method further includes: The network-side device receives at least one of the following capability information reported by the terminal: Whether the terminal can support simultaneous transmission of PUCCH in different frequency domain units; The terminal can support simultaneous transmission of PUCCH in different frequency domain units; The number of PUCCHs that the terminal supports to be simultaneously transmitted in different frequency domain units; The frequency domain units that the terminal supports for simultaneous PUCCH transmission; The minimum interval between the frequency domain units that the terminal supports for simultaneous PUCCH transmission.

13. The PUCCH transmission method according to claim 10, characterized in that, The multiple frequency domain units belong to different frequency domain unit groups / sets.

14. The PUCCH transmission method according to claim 10, wherein The frequency domain interval between the multiple frequency domain units meets the first requirement.

15. The PUCCH transmission method according to claim 10, wherein The method further includes: Sending a first parameter to the terminal; the first parameter is used to determine the frequency domain units where the multiple PUCCHs are located; The first parameter includes at least one of the following: SCS corresponding to downlink transmission; Frequency domain unit corresponding to downlink transmission; MCS corresponding to downlink transmission; MCS corresponding to uplink transmission; Processing capability corresponding to downlink transmission; Priority corresponding to downlink transmission; Qos corresponding to downlink transmission; Qos corresponding to uplink transmission.

16. A physical uplink control channel PUCCH transmission device, characterized in that, Including: A first sending module, configured to send multiple PUCCHs through multiple frequency domain units, where there are multiple frequency domain units available for sending PUCCH.

17. The PUCCH transmission device according to claim 16, wherein The apparatus further includes: A reporting module, configured to report at least one of the following capability information to the network-side device: Whether the terminal can support simultaneous transmission of PUCCH in different frequency domain units; The terminal can support simultaneous transmission of PUCCH in different frequency domain units; The number of PUCCHs that the terminal supports to be simultaneously transmitted in different frequency domain units; The frequency domain units that the terminal supports for simultaneous PUCCH transmission; The minimum interval between the frequency domain units that the terminal supports for simultaneous PUCCH transmission.

18. The PUCCH transmission device according to claim 16, characterized in that, The sending of multiple PUCCHs through multiple frequency domain units includes: When the number of PUCCHs to be simultaneously transmitted is greater than the number of PUCCHs that the terminal supports to be simultaneously transmitted in different frequency domain units, perform PUCCH transmission in at least one of the following ways: Discard some PUCCHs according to a preset rule, and send the remaining PUCCHs through multiple frequency domain units; Multiplex at least part of the UCI carried by some PUCCHs on other channels for transmission according to a preset rule, and send the remaining PUCCHs through multiple frequency domain units.

19. The PUCCH transmission device according to claim 16, characterized in that, The sending of multiple PUCCHs through multiple frequency domain units includes at least one of the following: Transmit PUCCH with different priorities through multiple frequency-domain units, where different frequency-domain units carry PUCCH with different priorities; Transmit PUCCH with different priorities through multiple frequency-domain units, where the same frequency-domain unit carries PUCCH with the same priority; Transmit PUCCH carrying different UCI types through multiple frequency-domain units, where different frequency-domain units carry PUCCH carrying different UCI types; Transmit PUCCH carrying different UCI types through multiple frequency-domain units, where the same frequency-domain unit carries PUCCH carrying the same UCI type; Transmit PUCCH with different scheduling types through multiple frequency-domain units, where different frequency-domain units carry PUCCH with different scheduling types; Transmit PUCCH carrying different scheduling types through multiple frequency-domain units, where the same frequency-domain unit carries PUCCH carrying the same scheduling type.

20. The PUCCH transmission device according to claim 16, characterized in that, The transmitting of multiple PUCCH through multiple frequency-domain units includes: The multiple PUCCH transmitted through multiple frequency-domain units overlap or do not overlap in time.

21. The PUCCH transmission device according to claim 16, wherein The device further includes: A frequency-domain unit determination module, configured to determine the frequency-domain units where the multiple PUCCH are located according to a first parameter; The first parameter includes at least one of the following: The SCS corresponding to the downlink transmission; The frequency-domain unit corresponding to the downlink transmission; The MCS corresponding to the downlink transmission; The MCS corresponding to the uplink transmission; The processing capacity corresponding to the downlink transmission; The priority corresponding to the downlink transmission; The Qos corresponding to the downlink transmission; The Qos corresponding to the uplink transmission.

22. The PUCCH transmission device according to claim 16, wherein The device further includes: A relationship determination module, configured to determine the association relationship between the downlink frequency-domain unit and the frequency-domain unit for transmitting PUCCH through at least one of the following methods: Higher-layer signaling configuration; DCI indication; Predefinition.

23. A Physical Uplink Control Channel (PUCCH) transmission device, characterized in that, Includes: A first receiving module, configured to receive multiple PUCCH through multiple frequency-domain units, where there are multiple frequency-domain units available for receiving PUCCH.

24. The PUCCH transmission device according to claim 23, wherein The device further includes: A configuration scheduling module, configured to configure or schedule the UE to transmit PUCCH with different priorities / UCI types / scheduling types in different frequency-domain units.

25. The PUCCH transmission device according to claim 23, wherein The device further includes: A second receiving module, configured to receive at least one of the following reported by the terminal: Whether the terminal can support simultaneous transmission of PUCCH in different frequency-domain units; The terminal can support simultaneous transmission of PUCCH in different frequency-domain units; The number of PUCCH that the terminal supports to be simultaneously transmitted in different frequency-domain units; The frequency-domain units that the terminal supports for simultaneous transmission of PUCCH; The minimum interval between the frequency-domain units that the terminal supports for simultaneous transmission of PUCCH.

26. The PUCCH transmission device according to claim 23, wherein The device further includes: A second transmitting module, configured to transmit a first parameter to the terminal; the first parameter is used to determine the frequency-domain units where the multiple PUCCH are located; The first parameter includes at least one of the following: The SCS corresponding to the downlink transmission; The frequency-domain unit corresponding to the downlink transmission; The MCS corresponding to the downlink transmission; The MCS corresponding to the uplink transmission; The processing capacity corresponding to the downlink transmission; The priority corresponding to the downlink transmission; The Qos corresponding to the downlink transmission; The Qos corresponding to the uplink transmission.

27. A terminal, characterized in that, It includes a processor and a memory, and the memory stores programs or instructions that can run on the processor. When the programs or instructions are executed by the processor, the PUCCH transmission method described in any one of claims 1 to 9 is implemented.

28. A network-side device, characterized in that, It includes a processor and a memory, and the memory stores programs or instructions that can run on the processor. When the programs or instructions are executed by the processor, the PUCCH transmission method described in any one of claims 10 to 15 is implemented.

29. A readable storage medium, characterized in that, Programs or instructions are stored on the readable storage medium. When the programs or instructions are executed by a processor, the PUCCH transmission method described in any one of claims 1 to 9 is implemented, or the PUCCH transmission method described in any one of claims 10 to 15 is implemented.

Images