Pucch transmission method, terminal, and network side device

Abstract

The present application relates to the technical field of wireless communications, and discloses a PUCCH transmission method, a terminal, and a network side device. The PUCCH transmission method in the embodiments of the present application comprises: a terminal sends a plurality of PUCCHs by means of a plurality of frequency domain units, wherein there are a plurality of frequency domain units that can be used for sending PUCCHs.

Description

PUCCH transmission method, terminal and network side equipment

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to the Chinese patent application filed with the China Patent Office on December 29, 2023, with application number 202311871048.5 and invention name “PUCCH transmission method, terminal and network side equipment”, the entire contents of which are incorporated by reference into this application. Technical Field

[0003] The present application belongs to the field of wireless communication technology, and specifically relates to a PUCCH transmission method, terminal, and network-side equipment. Background Art

[0004] Related Technology: Each cell's carrier is a continuous frequency domain resource. The Physical Uplink Control Channel (PUCCH) resource is allocated within the continuous uplink (UL) bandwidth part (BWP) of each frequency domain resource. Each cell has only one activated UL BWP, and PUCCH transmission occurs within that UL BWP. To efficiently utilize discontinuous frequency domain resources, one potential approach is to have a cell contain multiple discontinuous spectrums. When a cell contains discontinuous spectrum resources, there is no clear solution for how to achieve shared PUCCH transmission across different frequency domain units. Summary of the Invention

[0005] The embodiments of the present application provide a PUCCH transmission method, a terminal, and a network-side device, which can realize the joint transmission of PUCCH by different frequency domain units.

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

[0007] The terminal sends multiple PUCCHs through multiple frequency domain units, where multiple frequency domain units can be used to send PUCCHs.

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

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

[0010] In a third aspect, a PUCCH transmission apparatus is provided, including:

[0011] The first sending module is configured to send a plurality of PUCCHs through a plurality of frequency domain units, wherein a plurality of frequency domain units may be used to send the PUCCHs.

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

[0013] The first receiving module is configured to receive a plurality of PUCCHs through a plurality of frequency domain units, wherein a plurality of frequency domain units may be used to receive the PUCCHs.

[0014] In a fifth aspect, a terminal is provided, comprising a processor and a memory, wherein the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, the steps of the method described in the first aspect are implemented.

[0015] In a sixth aspect, a terminal is provided, comprising a processor and a communication interface, wherein the communication interface is used to send multiple PUCCHs through multiple frequency domain units, wherein there are multiple frequency domain units that can be used to send PUCCHs.

[0016] In the seventh aspect, a network side device is provided, which includes a processor and a memory, wherein the memory stores programs or instructions that can be run on the processor, and when the program or instructions are executed by the processor, the steps of the method described in the first aspect are implemented.

[0017] In an eighth aspect, a network side device is provided, comprising a processor and a communication interface, wherein the communication interface is used to receive multiple PUCCHs through multiple frequency domain units, wherein there are multiple frequency domain units that can be used to receive PUCCHs.

[0018] In a ninth aspect, a readable storage medium is provided, on which a program or instruction is stored. When the program or instruction is executed by a processor, the method described in the first aspect or the method described in the second aspect is implemented.

[0019] In the tenth aspect, a wireless communication system is provided, comprising: a terminal and a network side device, wherein 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 method described in the second aspect.

[0020] In the eleventh aspect, a chip is provided, which includes a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the method as described in the first aspect, or to implement the method as described in the second aspect.

[0021] In the twelfth aspect, a computer program / program product is provided, which is stored in a storage medium and is executed by at least one processor to implement the method as described in the first aspect, or to implement the method as described in the second aspect.

[0022] In an embodiment of the present application, the terminal sends multiple PUCCHs through multiple frequency domain units, wherein there are multiple frequency domain units that can be used to send PUCCHs. When multiple PUCCHs need to be transmitted, multiple PUCCHs are transmitted simultaneously through different frequency domain units, thereby reducing communication delay and being able to more flexibly and efficiently utilize the cell's spectrum resources to improve the effectiveness and performance of the communication system. BRIEF DESCRIPTION OF THE DRAWINGS

[0023] FIG1 is a block diagram of a wireless communication system provided in an embodiment of the present application;

[0024] FIG2 is a flow chart of a PUCCH transmission method according to an embodiment of the present application;

[0025] FIG3 is a second flow chart of the PUCCH transmission method provided in an embodiment of the present application;

[0026] FIG4 is a diagram illustrating an implementation example of a PUCCH transmission method provided in an embodiment of the present application;

[0027] FIG5 is a schematic diagram of a structure of a PUCCH transmission device according to an embodiment of the present application;

[0028] FIG6 is a second structural diagram of a PUCCH transmission device provided in an embodiment of the present application;

[0029] FIG7 is a schematic structural diagram of a communication device provided in an embodiment of the present application;

[0030] FIG8 is a schematic diagram of the hardware structure of a terminal provided in an embodiment of the present application;

[0031] FIG9 is a schematic diagram of the structure of the network side device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0032] The following will be combined with the accompanying drawings in the embodiments of this application to clearly describe the technical solutions in the embodiments of this application. Obviously, the embodiments described are part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field are within the scope of protection of this application.

[0033] The terms "first", "second", etc. in this application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the terms used in this way are interchangeable where appropriate, so that the embodiments of the present 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 type, and do not limit the number of objects, for example, the first object can be one or more. In addition, "or" in this application represents at least one of the connected objects. For example, "A or B" covers three options, namely, Option 1: including A but not including B; Option 2: including B but not including A; Option 3: including both A and B. The character " / " generally indicates that the objects associated before and after are in an "or" relationship.

[0034] The term "indication" in this application can be either a direct indication (or explicit indication) or an indirect indication (or implicit indication). A direct indication can be understood as the sender explicitly informing the receiver of specific information, the operation to be performed, or the requested result, etc. in the instruction sent; an indirect indication can be understood as the receiver determining the corresponding information based on the instruction sent by the sender, or making a judgment and determining the operation to be performed or the requested result, etc. based on the judgment result.

[0035] It is worth noting that the technology described in the embodiments of the present application is not limited to the Long Term Evolution (LTE) / LTE-Advanced (LTE-A) system, but 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 the present application are often used interchangeably, and the technology described can be used for the systems and radio technologies mentioned above, as well as for other systems and radio technologies. The following description describes a New Radio (NR) system for illustrative purposes, and NR terminology is used in most of the following description, but these technologies can also be applied to systems other than NR systems, such as 6th generation (6G) systems. thGeneration, 6G) communication system.

[0036] FIG1 is a block diagram of a wireless communication system applicable to an embodiment of the present application. The wireless communication system includes a terminal 11 and a network-side device 12. The terminal 11 may be a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (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 (Wearable Device), an aircraft (Flight Vehicle), a vehicle-mounted device (VUE), a ship-mounted device, a pedestrian user equipment (PUE), a smart home (home appliances with wireless communication capabilities, such as refrigerators, televisions, washing machines, or furniture), a game console, a personal computer (PC), an ATM, or a self-service machine, or other terminal-side devices. Wearable devices include: smart watches, smart bracelets, smart headphones, smart glasses, smart jewelry (smart bracelets, smart bracelets, smart rings, smart necklaces, smart anklets, smart anklets, etc.), smart wristbands, smart clothing, etc. Among them, the vehicle-mounted device can also be called a vehicle-mounted terminal, a vehicle-mounted controller, a vehicle-mounted module, a vehicle-mounted component, a vehicle-mounted chip or a vehicle-mounted unit, etc. It should be noted that the specific type of the terminal 11 is not limited in the embodiment of the present application. The network side device 12 may include an access network device or a core network device, wherein the access network device may also be called a radio access network (Radio Access Network, RAN) device, a radio access network function or a radio access network unit. The access network device may 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 can 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 (home evolved Node B), Transmission Reception Point (TRP) or other appropriate terms in the field. As long as the same technical effect is achieved, the base station is not limited to specific technical vocabulary. It should be noted that in the embodiment of the present application, only the base station in the NR system is used as an example for introduction, and the specific type of the base station is not limited.

[0037] The core network equipment may include but is not limited to at least one of the following: core network node, core network function, mobility management entity (MME), access mobility management function (AMF), session management function (SMF), user plane function (UPF), policy control function (PCF), policy and charging rules function unit (PCRF), edge application service discovery function (EASDF), unified data management (UDM), unified data repository (UDR), home user server (HSS), centralized network configuration (CNC), network storage function (NRF), network exposure function (NEF), local NEF (L-NEF), binding support function (BSF), application function ( It should be noted that in the embodiments of the present application, only the core network device in the NR system is introduced as an example, and the specific type of the core network device is not limited.

[0038] The PUCCH transmission method provided in the embodiments of the present application is described in detail below through some embodiments and their application scenarios in combination with the accompanying drawings.

[0039] FIG2 is a flow chart of a PUCCH transmission method according to an embodiment of the present application. As shown in FIG2 , the method includes the following steps:

[0040] Step 200: The terminal sends multiple PUCCHs through multiple frequency domain units, where multiple frequency domain units can be used to send PUCCHs.

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

[0042] For a cell consisting of multiple frequency domain units, each PUCCH resource can be configured / scheduled within a frequency domain unit. In the same time unit, there may be multiple frequency domain units with available PUCCH resources (for example, there are corresponding PUCCH resource configurations on the corresponding frequency domain units, or the base station can schedule PUCCH resources to be transmitted on the corresponding frequency domain units, etc.), or there are multiple frequency domain units with uplink available 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 in multiple frequency domain units. The network-side equipment receives multiple PUCCHs in multiple frequency domain units.

[0043] Alternatively, multiple frequency domain units may have available PUCCH resources in different time units, or multiple frequency domain units may have available uplink resources. The base station may configure / schedule multiple PUCCHs for transmission in multiple frequency domain units. The UE transmits multiple PUCCHs via multiple frequency domain units. The network-side device receives multiple PUCCHs via multiple frequency domain units. Optionally, the time unit may be a symbol, a symbol set, a time slot, a subslot, a subframe, a frame, or other time period, without limitation.

[0044] In an embodiment of the present 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 transmission delays, and more flexibly and efficiently utilize the cell's spectrum resources to improve the effectiveness and performance of the communication system.

[0045] Optionally, the method further includes:

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

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

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

[0049] The number of PUCCHs supported by the terminal that can be sent simultaneously in different frequency domain units;

[0050] Frequency domain units supported by the terminal that are capable of simultaneous PUCCH transmission;

[0051] The minimum spacing between frequency domain units supported by the terminal that can simultaneously transmit PUCCHs.

[0052] The UE reports to the network side device, wherein it can be understood that whether the UE can support simultaneous transmission of PUCCH in different frequency domain units means that it needs to be reported regardless of whether the UE supports it.

[0053] The UE can support simultaneous transmission of PUCCH in different frequency domain units, which means that if the UE does not report, it means it does not support it, and it will report only when it supports it.

[0054] The number of PUCCHs supported by the UE and capable of being simultaneously transmitted in different frequency domain units may indicate the number of PUCCHs that the UE may simultaneously transmit.

[0055] For example, the UE reports the number N1 of PUCCHs supported by the UE that can be simultaneously transmitted in different frequency domain units, and / or the frequency domain units supported by the UE that can support simultaneous PUCCH transmission.

[0056] For another example, the UE reports the frequency domain units supported by it and capable of simultaneously transmitting the PUCCH and the minimum interval between the frequency domain units supported by it and capable of simultaneously transmitting the PUCCH.

[0057] It should be noted that: in the embodiment of the present application, the UE is able to support simultaneous transmission of PUCCH in different frequency domain units, which means that the base station can schedule the terminal to simultaneously transmit different PUCCHs in different frequency domain units, but whether the UE simultaneously transmits PUCCH 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, and the base station can also schedule the UE to transmit different PUCCHs in different frequency domain units at the same time / overlapping time (where overlapping time means that different PUCCH transmissions overlap in time, which can be complete overlap or partial overlap).

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

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

[0060] In an embodiment of the present application, optionally, when the UE supports simultaneous transmission of PUCCH 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.

[0061] It should be noted that the frequency domain unit group / set may be reported by the UE to the network side device / predefined / configured by a higher layer.

[0062] Optionally, the frequency domain intervals between the multiple frequency domain units meet the first requirement.

[0063] In an embodiment of the present application, when the UE supports PUCCH transmission in different frequency domain units, the frequency domain interval between 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 preset value, etc.

[0064] It should be noted that the requirements for the frequency domain interval may be reported by the UE to the network side device / predefined / configured by a higher layer.

[0065] Optionally, when the base station configures or instructs the UE to transmit different PUCCHs in different frequency domain units, it ensures that the different frequency domain units corresponding to the PUCCH transmission meet the above-mentioned 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 part of the PUCCH transmission / performs PUCCH merging according to the first principle.

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

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

[0068] The terminal discards part of the PUCCH according to a preset rule and sends the remaining PUCCH through multiple frequency domain units;

[0069] The terminal multiplexes at least part of the UCI carried by part of the PUCCH on other channels for transmission according to a preset rule, and sends the remaining PUCCH through multiple frequency domain units.

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

[0071] Optionally, the UE does not expect that multiple PUCCHs scheduled in the same frequency domain unit 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 part of the transmission / merging within the frequency domain unit, so that within one frequency domain unit, at most only one PUCCH needs to be transmitted at the same time.

[0072] 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 PUCCHs in different frequency domain units. At a certain time, the UE does not expect the number N2 of PUCCHs configured / scheduled by the base station to transmit in different frequency domain units to be greater than the UE's reported capability N1 (N2>N1), that is, when the base station schedules the UE to transmit different PUCCHs, it should ensure that it is within the UE's capability to transmit PUCCHs, or if the number N2 of PUCCHs scheduled / configured for transmission by the UE in different frequency domain units is greater than the UE's reported capability N1 (N2>N1), the UE discards part of the PUCCH transmission according to the preset rules and sends the remaining PUCCHs through multiple frequency domain units.

[0073] For another 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 PUCCHs in different frequency domain units. At a certain time, the UE does not expect the base station to configure / schedule the UE to transmit PUCCHs N2 in different frequency domain units greater than the UE's reported capability N1 (N2>N1), or if the UE is scheduled / configured to transmit PUCCHs N2 in different frequency domain units greater than the UE's reported capability N1 (N2>N1), the UE multiplexes at least part of the UCI carried by part of the PUCCHs on other channels for transmission according to preset rules, and sends the remaining PUCCHs through multiple frequency domain units.

[0074] It should be noted that in the embodiment of the present application, the preset rules include at least one of the following:

[0075] According to the predefined priority order, for example, the priority of the PUCCH carrying the Hybrid Automatic Repeat reQuest acknowledgement (HARQ-ACK) is higher than the priority of the PUCCH carrying the SR, which is higher than the priority of the PUCCH carrying the CSI;

[0076] 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 indicates that the downlink control information (DCI) corresponding to the PUCCH corresponds to the physical downlink control channel (PDCCH) / control resource set (CORESET) with a later / earlier start / end position.

[0077] The priority of the dynamically scheduled PUCCH is higher than the priority of the configured PUCCH. It is understandable that the dynamically scheduled PUCCH can be a DCI-scheduled PUCCH, for example, a PUCCH that feeds back HARQ-ACK of a DCI-scheduled physical downlink shared channel (PDSCH), and the configured PUCCH can be a PUCCH that the base station configures the UE to transmit through higher-layer signaling, for example, an SR PUCCH or a periodic CSIPUCCH.

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

[0079] The terminal sends PUCCHs of different priorities through multiple frequency domain units, and different frequency domain units carry PUCCHs of different priorities;

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

[0081] The terminal sends PUCCHs carrying different UCI types through multiple frequency domain units, and different frequency domain units carry PUCCHs of different UCI types;

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

[0083] The terminal sends PUCCHs of different scheduling types through multiple frequency domain units, and different frequency domain units carry PUCCHs of different scheduling types;

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

[0085] 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 PUCCHs carrying different priorities in different frequency domain units, and the base station schedules / configures the UE to transmit PUCCHs carrying the same priority in the same frequency domain unit. The UE sends PUCCHs of different priorities through multiple frequency domain units, and different frequency domain units carry PUCCHs of different priorities; the UE sends PUCCHs of different priorities through multiple frequency domain units, and the same frequency domain unit carries PUCCHs of the same priority. The priority of PUCCH can be a physical layer priority, or it can be represented by a priority index. For example, a priority index of 1 indicates high priority, and a priority index of 0 indicates low priority.

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

[0087] It should be noted that: in the embodiment of the present application, the frequency domain unit for transmitting high-priority PUCCH or the frequency domain unit for transmitting low-priority PUCCH may be different in different time domain units (that is, it may change dynamically, for example, it may change according to the dynamic scheduling of the base station, or the base station may flexibly indicate. It is understandable that if the UE is scheduled to transmit PUCCHs of different priorities at overlapping times, the PUCCHs of different priorities are in different frequency domain units).

[0088] 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 PUCCHs of different UCI types in different frequency domain units, and the base station schedules / configures the UE to transmit PUCCHs carrying the same UCI type in the same frequency domain unit. The UE sends PUCCHs carrying different UCI types through multiple frequency domain units, and different frequency domain units carry PUCCHs of different UCI types; the UE sends PUCCHs carrying different UCI types through multiple frequency domain units, and the same frequency domain unit carries PUCCHs of the same UCI type.

[0089] The association relationship between the UCI type and the frequency domain unit can be determined by predefined rules / high-level 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 in the activated UL frequency domain unit / the frequency domain unit with the largest frequency domain interval from the frequency domain unit with high priority.

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

[0091] HARQ-ACK;

[0092] Scheduling Request (SR);

[0093] Channel State Information (CSI).

[0094] It should be noted that: in this embodiment of the present application, the frequency domain unit where the PUCCH of a certain UCI type is transmitted may be different in different time domain units (that is, it can change dynamically, or the base station can flexibly indicate it. It can be understood that if the UE is scheduled to transmit PUCCHs of different UCI types at overlapping times, the PUCCHs of different UCI types are in different frequency domain units).

[0095] For another 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 types of PUCCH in different frequency domain units. Different types of PUCCH can be DCI-scheduled and non-DCI-scheduled (also referred to as configured transmission / semi-static transmission, for example, SR, Semi-Persistent Scheduling (SPS) CSI, PCSI, 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.

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

[0097] It should be noted that: in the embodiment of the present application, the frequency domain unit where the DCI-scheduled PUCCH is located can be different in different time domain units (i.e., it can be dynamically changed or flexibly indicated by the base station). The frequency domain unit where the non-DCI-scheduled PUCCH is located can be determined according to high-level configuration.

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

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

[0100] In the embodiment of the present application, for a cell consisting of multiple frequency domain units, each PUCCH resource can be configured / scheduled within one frequency domain unit.

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

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

[0103] Optionally, the method further includes:

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

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

[0106] SCS corresponding to downlink transmission;

[0107] Frequency domain unit corresponding to downlink transmission;

[0108] MCS corresponding to downlink transmission;

[0109] MCS corresponding to uplink transmission;

[0110] The processing capacity corresponding to downlink transmission;

[0111] Priority corresponding to downlink transmission;

[0112] QoS corresponding to downlink transmission;

[0113] QoS corresponding to uplink transmission.

[0114] 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 according to the first parameter of DL and / or UL. It can be understood that PUCCHs corresponding to the same first parameter (or the same range) are in one frequency domain unit, and PUCCHs corresponding to different first parameters (or different ranges) are in different frequency domain units.

[0115] The first parameter contains at least one of the following:

[0116] SCS corresponding to downlink transmission;

[0117] Frequency domain unit corresponding to downlink transmission;

[0118] MCS corresponding to downlink transmission;

[0119] MCS corresponding to uplink transmission;

[0120] The processing capacity corresponding to downlink transmission;

[0121] Priority corresponding to downlink transmission;

[0122] QoS corresponding to downlink transmission;

[0123] QoS corresponding to uplink transmission.

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

[0125] For another example, the UE can be scheduled / configured to transmit different PUCCHs in different frequency domain units through the SCS corresponding to the downlink transmission and the quality of service (QoS) corresponding to the downlink transmission.

[0126] For another example, the UE may be scheduled / configured to transmit different PUCCHs in different frequency domain units through the SCS corresponding to downlink transmission, the modulation and coding scheme (MCS) corresponding to uplink transmission, and the processing capability corresponding to downlink transmission.

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

[0128] Regarding the QoS corresponding to downlink transmission and / or previous transmission: for example, grouping according to latency requirements (low latency is in one frequency domain unit, high latency is in another frequency domain unit, and the latency can be a range), or grouping according to transmission reliability requirements (for example, high reliability can be characterized by lower MCS, code rate Alpha / Beta or higher power, etc.).

[0129] Optionally, the method further includes:

[0130] The terminal determines an association relationship between a downlink frequency domain unit and a frequency domain unit for sending a PUCCH by at least one of the following methods:

[0131] High-level signaling configuration;

[0132] DCI indication;

[0133] Predefined.

[0134] For example, when the UE supports / is enabled to simultaneously transmit PUCCH in different frequency domain units, the association between the downlink frequency domain unit n and the frequency domain unit m where the PUCCH is located is determined by at least one of the following methods (ie, the downlink transmission transmitted in the downlink frequency domain unit n, for example, PDCCH, PDSCH, is fed back in the uplink frequency domain unit m, for example, HARQ-ACK feedback):

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

[0136] For uplink PUCCH transmission without DCI scheduling, it is activated by DCI or configured / predefined by higher layers;

[0137] For uplink PUCCH transmission with DCI scheduling, it is indicated by scheduling DCI.

[0138] Optionally, for configuration via higher-layer signaling:

[0139] If high-level signaling configures a downlink frequency domain unit to associate with multiple uplink frequency domain units, the frequency domain units are selected in order of priority (for example, a primary frequency domain unit is set). If a frequency domain unit with a higher priority (for example, a frequency domain unit with good channel quality / low index has a higher priority) is not activated, a frequency domain unit with a lower priority (for example, a frequency domain unit with poor channel quality / high index has a lower priority) is selected. If none of the associated frequency domain units are activated, a higher priority frequency domain unit from the unactivated frequency domain units is selected for activation.

[0140] A Media Access Control Control Element (MAC CE) or DCI indicates that a downlink frequency domain unit is associated with a frequency domain unit (if a high-layer signaling configures that a downlink frequency domain unit is associated with multiple uplink frequency domain units).

[0141] If the uplink frequency domain unit associated with the downlink frequency domain unit indicated by the higher 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 / activated uplink frequency domain unit (when the UE has only one activated uplink frequency domain unit).

[0142] Optionally, there is no DCI scheduled uplink PUCCH transmission, for example, SPS HARQ-ACK, if the uplink frequency domain unit associated with the downlink frequency domain unit is deactivated, the downlink frequency domain unit is associated with another / default frequency domain unit / activated uplink frequency domain unit according to a predefined rule (when the UE has only one activated uplink frequency domain unit)

[0143] Optionally, there is DCI-scheduled uplink PUCCH transmission, such as dynamic grant (DG) PDSCH HARQ-ACK, which the UE expects to be scheduled on an activated uplink frequency domain unit.

[0144] FIG3 is a second flow chart of a PUCCH transmission method according to an embodiment of the present application. As shown in FIG3 , the method includes the following steps:

[0145] Step 300: The network-side device receives multiple PUCCHs through multiple frequency domain units, where multiple frequency domain units can be used to receive PUCCHs.

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

[0147] For a cell consisting of multiple frequency domain units, each PUCCH resource can be configured / scheduled within a frequency domain unit. In the same time unit, multiple frequency domain units can have available PUCCH resources. The base station can configure / schedule multiple PUCCHs for transmission across multiple frequency domain units. The UE transmits multiple PUCCHs across multiple frequency domain units. Network-side equipment receives multiple PUCCHs across multiple frequency domain units.

[0148] Alternatively, multiple frequency domain units may have available PUCCH resources in different time units. The base station can configure / schedule multiple PUCCHs for transmission on the multiple frequency domain units. The UE can send multiple PUCCHs via the multiple frequency domain units. The network-side device can receive multiple PUCCHs via the multiple frequency domain units.

[0149] Optionally, the time unit may be a time period such as a symbol, a symbol set, a time slot, a sub-time slot, a frame, etc., which is not specifically limited.

[0150] In an embodiment of the present application, the terminal sends multiple PUCCHs through multiple frequency domain units, which can ensure the transmission of low-priority PUCCHs, reduce transmission delays, and more flexibly and efficiently utilize the cell's spectrum resources to improve the effectiveness and performance of the communication system.

[0151] Optionally, the method further includes:

[0152] The network side device configures or schedules the UE to transmit PUCCHs of different priorities / UCI types / scheduling types in different frequency domain units.

[0153] For example, for a cell consisting of multiple frequency domain units, each PUCCH resource can be configured / scheduled within one frequency domain unit. In the same time unit, multiple frequency domain units may have available PUCCH resources, and the base station can configure / schedule multiple PUCCHs for transmission on multiple frequency domain units.

[0154] The methods provided in the various embodiments of this application are based on the same application concept, so the implementation of each method can refer to each other, and the repeated parts will not be repeated.

[0155] The following examples illustrate the methods provided in the above embodiments of the present application through specific application scenarios.

[0156] Example 1:

[0157] Assume a cell consists of four frequency domain units, with sizes of 0-3 being 5 MHz, 10 MHz, 5 MHz, and 20 MHz, respectively. A UE can have one or more active frequency domain units in the same time unit. The base station can configure PUCCH resources in the following ways.

[0158] In the same time unit, there may be multiple frequency domain units with available PUCCH resource configurations. For example, the base station configures PUCCH transmission resources on each frequency domain resource separately, or the base station configures PUCCH resources that are common to the frequency domain resources. The base station can configure or instruct the UE to transmit PUCCH 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.

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

[0160] If the UE supports / is enabled to transmit PUCCHs simultaneously in different frequency domain units, then if the UE is configured or instructed to transmit different PUCCHs in the frequency domain units, the UE transmits different PUCCHs in the frequency domain units respectively configured or instructed.

[0161] Optionally, the above-mentioned UE supports the transmission of PUCCH in different frequency domain units, and the different frequency domain units meet the second requirement, for example, different frequency domain units belong to different frequency domain unit groups / frequency domain unit subsets / frequency domain unit sets (frequency domain unit groups / frequency domain unit subsets / frequency domain unit sets may be protocol predefined or UE reported / base station configured), and the intervals between different frequency domain units meet the first requirement, etc. In one embodiment, when the base station configures or instructs the UE to transmit different PUCCHs in different frequency domain units, it ensures that different frequency domain units meet the second requirement, and the UE transmits its own PUCCH in different frequency domain units according to the configuration or instruction of the base station. In one embodiment, 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 part of the PUCCHs in different PUCCHs according to predefined rules, such as PUCCH corresponding priority / early or late scheduling time / early or late transmission time / carrying content / scheduling type (such as semi-static configuration of dynamic scheduling priority), etc. For example, the UE determines the PUCCH with the highest transmission priority, and does not transmit / discard / cancel the PUCCH that cannot be transmitted simultaneously with the highest priority. If there are any remaining PUCCHs, the above steps are repeated among the remaining PUCCHs until the PUCCHs that need to be transmitted (i.e., there are no PUCCHs that are not transmitted / discarded / cancelled) meet certain requirements.

[0162] Example 2:

[0163] 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 activated frequency domain units.

[0164] In one embodiment, the base station indicates or configures PUCCH transmission on different frequency domain units. The base station configures the UE to transmit PUCCHs of 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 simultaneous transmission of PUCCHs in different frequency domain units, under this embodiment, PUCCHs of different priorities can be transmitted separately, which can ensure the transmission of PUCCHs and the reliability of PUCCH transmission, avoid the problem of PUCCH overlap between different priorities (in the prior art, when PUCCHs of different priorities overlap, the UE either discards the low-priority PUCCH, which cannot guarantee the transmission of the low-priority PUCCH and its delay, or multiplexes UCIs of different priorities on one channel for transmission, increasing the processing complexity of the UE), and reduces the transmission delay of PUCCH.

[0165] Example 3:

[0166] 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 activated frequency domain units.

[0167] In one embodiment, the base station instructs or configures PUCCH transmission on different frequency domain units, wherein the base station configures the UE to transmit PUCCH carrying different UCI types (eg, HARQ-ACK, CSI, SR, LRR, etc.) on different frequency domain units.

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

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

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

[0171] Example 4:

[0172] 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 activated frequency domain units.

[0173] 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 corresponding to different PDSCH processing capabilities on different frequency domain units. For example, the processing capabilities corresponding to downlink PDCCH / PDSCH transmissions include processing capability 1 and processing capability 2, where processing capability 2 is stronger / faster than processing capability 1. In the prior art, due to certain implementation issues, PDSCH scheduling requires that the first scheduled transmission be fed back first, rather than the last scheduled transmission. When the UE supports simultaneous transmission of different PUCCHs on different frequency domain units, the base station can schedule the HARQ-ACK for downlink transmissions corresponding to processing capability 1 for feedback on one frequency domain unit, and schedule the HARQ-ACK for downlink transmissions corresponding to processing capability 2 for feedback on another frequency domain unit. In this way, for PDSCH scheduling, only downlink transmissions corresponding to the same capability need to be scheduled first, followed by feedback. For downlink transmissions corresponding to different processing capabilities, the scheduling order is independent and unrestricted. This can reduce the HARQ-ACK feedback delay for downlink transmissions with higher processing capabilities when mixed processing capabilities are present in downlink transmissions, thereby improving system throughput.

[0174] Example 5:

[0175] 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 activated 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 (that is, the downlink transmission transmitted in the downlink frequency domain unit n is fed back in the uplink frequency domain unit m) can be determined by at least one of the following:

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

[0177] 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, where 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 a 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 activated frequency domain unit with the smallest index among the multiple uplink frequency domain units.

[0178] Or for uplink PUCCH transmission without DCI scheduling, such as SPS HARQ-ACK, by activating DCI or high-layer configuration, where 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 transmission with DCI scheduling, such as DG PDSCH HARQ-ACK, it is indicated by scheduling DCI.

[0179] Optionally, if the uplink frequency domain unit associated with a downlink frequency domain unit configured by the high layer is deactivated, 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 in the currently activated uplink frequency domain unit or the default frequency domain unit.

[0180] The PUCCH transmission method provided in the embodiment of the present application may be performed by a PUCCH transmission device. In the embodiment of the present application, the PUCCH transmission device performing the PUCCH transmission method is taken as an example to illustrate the PUCCH transmission device provided in the embodiment of the present application.

[0181] FIG5 is a schematic diagram of a structure of a PUCCH transmission device according to an embodiment of the present application. As shown in FIG5 , an embodiment of the present application provides a PUCCH transmission device 500, including:

[0182] The first sending module 510 sends multiple PUCCHs through multiple frequency domain units, where multiple frequency domain units can be used to send PUCCHs.

[0183] Optionally, the device further comprises:

[0184] The reporting module is used to report at least one of the following capability information to the network-side device:

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

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

[0187] The number of PUCCHs supported by the terminal that can be sent simultaneously in different frequency domain units;

[0188] Frequency domain units supported by the terminal that are capable of simultaneous PUCCH transmission;

[0189] The minimum spacing between frequency domain units supported by the terminal that can simultaneously transmit PUCCHs.

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

[0191] Optionally, the frequency domain intervals between the multiple frequency domain units meet the first requirement.

[0192] Optionally, the sending of multiple PUCCHs through multiple frequency domain units includes:

[0193] When the number of PUCCHs that need to be sent simultaneously is greater than the number of PUCCHs that can be sent simultaneously in different frequency domain units supported by the terminal, PUCCH transmission is performed in at least one of the following ways:

[0194] Part of the PUCCH is discarded according to a preset rule, and the remaining PUCCH is sent through multiple frequency domain units;

[0195] At least part of the UCI carried by part of the PUCCH is multiplexed and transmitted on other channels according to a preset rule, and the remaining PUCCH is sent through multiple frequency domain units.

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

[0197] PUCCHs of different priorities are sent through multiple frequency domain units, and different frequency domain units carry PUCCHs of different priorities;

[0198] PUCCHs of different priorities are sent through multiple frequency domain units, and the same frequency domain unit carries PUCCHs of the same priority;

[0199] PUCCHs carrying different uplink control information (UCI) types are sent via multiple frequency domain units, with different frequency domain units carrying PUCCHs of different UCI types.

[0200] PUCCHs carrying different UCI types are sent through multiple frequency domain units, and the same frequency domain unit carries PUCCHs of the same UCI type;

[0201] PUCCHs of different scheduling types are sent through multiple frequency domain units, and different frequency domain units carry PUCCHs of different scheduling types;

[0202] PUCCHs carrying different scheduling types are sent through multiple frequency domain units, and the same frequency domain unit carries PUCCHs of the same scheduling type.

[0203] Optionally, the sending of multiple PUCCHs through multiple frequency domain units includes:

[0204] Multiple PUCCHs transmitted through multiple frequency domain units may overlap or not overlap in time.

[0205] Optionally, the device further comprises:

[0206] A frequency domain unit determination module, configured to determine the frequency domain units where the multiple PUCCHs are located according to the first parameter;

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

[0208] SCS corresponding to downlink transmission;

[0209] Frequency domain unit corresponding to downlink transmission;

[0210] MCS corresponding to downlink transmission;

[0211] MCS corresponding to uplink transmission;

[0212] The processing capacity corresponding to downlink transmission;

[0213] Priority corresponding to downlink transmission;

[0214] QoS corresponding to downlink transmission;

[0215] QoS corresponding to uplink transmission.

[0216] Optionally, the device further comprises:

[0217] The relationship determination module is configured to determine the association relationship between the downlink frequency domain unit and the frequency domain unit used to send the PUCCH by at least one of the following methods:

[0218] High-level signaling configuration;

[0219] DCI indication;

[0220] Predefined.

[0221] In an embodiment of the present application, the terminal sends multiple PUCCHs through multiple frequency domain units, wherein there are multiple frequency domain units that can be used to send PUCCHs. When multiple PUCCHs need to be transmitted, multiple PUCCHs are transmitted simultaneously through different frequency domain units, thereby reducing communication delay and being able to more flexibly and efficiently utilize the cell's spectrum resources to improve the effectiveness and performance of the communication system.

[0222] FIG6 is a second structural diagram of a PUCCH transmission device provided in an embodiment of the present application. As shown in FIG6 , an embodiment of the present application provides a PUCCH transmission device 600, including:

[0223] The first receiving module 610 receives multiple PUCCHs through multiple frequency domain units, where multiple frequency domain units can be used to receive PUCCHs.

[0224] Optionally, the device further comprises:

[0225] The configuration scheduling module is used to configure or schedule the UE to transmit PUCCHs of different priorities / UCI types / scheduling types in different frequency domain units.

[0226] Optionally, the device further comprises:

[0227] The second receiving module is configured to receive at least one of the following items reported by the terminal:

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

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

[0230] The number of PUCCHs supported by the terminal that can be sent simultaneously in different frequency domain units;

[0231] Frequency domain units supported by the terminal that are capable of simultaneous PUCCH transmission;

[0232] The minimum spacing between frequency domain units supported by the terminal that can simultaneously transmit PUCCHs.

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

[0234] Optionally, the frequency domain intervals between the multiple frequency domain units meet the first requirement.

[0235] Optionally, the device further comprises:

[0236] A second sending module is configured to send a first parameter to the terminal; the first parameter is used to determine the frequency domain units where the multiple PUCCHs are located;

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

[0238] SCS corresponding to downlink transmission;

[0239] Frequency domain unit corresponding to downlink transmission;

[0240] MCS corresponding to downlink transmission;

[0241] MCS corresponding to uplink transmission;

[0242] The processing capacity corresponding to downlink transmission;

[0243] Priority corresponding to downlink transmission;

[0244] QoS corresponding to downlink transmission;

[0245] QoS corresponding to uplink transmission.

[0246] In an embodiment of the present application, the network side device receives multiple PUCCHs through multiple frequency domain units, wherein there are multiple frequency domain units that can be used to receive PUCCHs. When multiple PUCCHs need to be transmitted, multiple PUCCHs are transmitted simultaneously through different frequency domain units, thereby reducing communication delay and being able to more flexibly and efficiently utilize the cell's spectrum resources to improve the effectiveness and performance of the communication system.

[0247] The PUCCH transmission device in the embodiments 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 chip. The electronic device can be a terminal or other device other than a terminal. For example, the terminal can include but is not limited to the types of terminal 11 listed above, and other devices can be servers, network attached storage (NAS), etc., which are not specifically limited in the embodiments of the present application.

[0248] The PUCCH transmission device provided in the embodiment of the present application can implement the various processes implemented in the above-mentioned method embodiments and achieve the same technical effects. To avoid repetition, it will not be repeated here.

[0249] As shown in Figure 7, an embodiment of the present application further provides a communication device 700, including a processor 701 and a memory 702. The memory 702 stores a program or instruction that can be run on the processor 701. For example, when the communication device 700 is a terminal, the program or instruction, when executed by the processor 701, implements the various steps of the PUCCH transmission method embodiment corresponding to the terminal, and can achieve the same technical effect. When the communication device 700 is a network-side device, the program or instruction, when executed by the processor 701, implements the various steps of the PUCCH transmission method embodiment corresponding to the network-side device, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0250] The present application also provides a terminal including a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is configured to execute a program or instruction to implement the steps of the method embodiment shown in FIG2 . This terminal embodiment corresponds to the aforementioned terminal-side method embodiment, and each implementation process and implementation method of the aforementioned method embodiment is applicable to this terminal embodiment and can achieve the same technical effects. Specifically, FIG8 is a schematic diagram of the hardware structure of a terminal implementing an embodiment of the present application.

[0251] The terminal 800 includes but is not limited to: 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 at least some of the components of the processor 810.

[0252] Those skilled in the art will appreciate that the terminal 800 may also include a power supply (such as a battery) to power various components. The power supply may be logically connected to the processor 810 via a power management system, thereby enabling the power management system to manage charging, discharging, and power consumption. The terminal structure shown in FIG8 does not limit the terminal. The terminal may include more or fewer components than shown, or may combine certain components, or have different component arrangements, which will not be described in detail here.

[0253] It should be understood that in an embodiment of the present application, the input unit 804 may include a graphics processing unit (GPU) 8041 and a microphone 8042, and the graphics processor 8041 processes the image data of a static picture or video 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 a touch panel 8071 and at least one of 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. 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 repeated here.

[0254] In the embodiment of the present application, after receiving downlink data from a network-side device, the radio frequency unit 801 may transmit the data to the processor 810 for processing. Furthermore, the radio frequency unit 801 may send uplink data to the network-side device. Typically, 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, and the like.

[0255] 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, wherein the first storage area may store an operating system, applications 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 a volatile memory or a 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 random access memory (RAM), static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct RAM bus random access memory (DRRAM). The memory 809 in the embodiment of the present application includes but is not limited to these and any other suitable types of memory.

[0256] Processor 810 may include one or more processing units. Optionally, processor 810 integrates an application processor and a modem processor. The application processor primarily handles operations related to the operating system, user interface, and application programs, while the modem processor primarily processes wireless communication signals, such as a baseband processor. It is understood that the modem processor may not be integrated into processor 810.

[0257] The radio frequency unit 801 is configured to send multiple PUCCHs through multiple frequency domain units, where multiple frequency domain units may be used to send PUCCHs.

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

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

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

[0261] The number of PUCCHs supported by the terminal that can be sent simultaneously in different frequency domain units;

[0262] Frequency domain units supported by the terminal that are capable of simultaneous PUCCH transmission;

[0263] The minimum spacing between frequency domain units supported by the terminal that can simultaneously transmit PUCCHs.

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

[0265] Optionally, the frequency domain intervals between the multiple frequency domain units meet the first requirement.

[0266] Optionally, the sending of multiple PUCCHs through multiple frequency domain units includes:

[0267] When the number of PUCCHs that need to be sent simultaneously is greater than the number of PUCCHs that can be sent simultaneously in different frequency domain units supported by the terminal, PUCCH transmission is performed in at least one of the following ways:

[0268] Part of the PUCCH is discarded according to a preset rule, and the remaining PUCCH is sent through multiple frequency domain units;

[0269] At least part of the UCI carried by part of the PUCCH is multiplexed and transmitted on other channels according to a preset rule, and the remaining PUCCH is sent through multiple frequency domain units.

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

[0271] PUCCHs of different priorities are sent through multiple frequency domain units, and different frequency domain units carry PUCCHs of different priorities;

[0272] PUCCHs of different priorities are sent through multiple frequency domain units, and the same frequency domain unit carries PUCCHs of the same priority;

[0273] PUCCHs carrying different UCI types are sent through multiple frequency domain units, and different frequency domain units carry PUCCHs of different UCI types;

[0274] PUCCHs carrying different UCI types are sent through multiple frequency domain units, and the same frequency domain unit carries PUCCHs of the same UCI type;

[0275] PUCCHs of different scheduling types are sent through multiple frequency domain units, and different frequency domain units carry PUCCHs of different scheduling types;

[0276] PUCCHs carrying different scheduling types are sent through multiple frequency domain units, and the same frequency domain unit carries PUCCHs of the same scheduling type.

[0277] Optionally, the sending of multiple PUCCHs through multiple frequency domain units includes:

[0278] Multiple PUCCHs transmitted through multiple frequency domain units may overlap or not overlap in time.

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

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

[0281] SCS corresponding to downlink transmission;

[0282] Frequency domain unit corresponding to downlink transmission;

[0283] MCS corresponding to downlink transmission;

[0284] MCS corresponding to uplink transmission;

[0285] The processing capacity corresponding to downlink transmission;

[0286] Priority corresponding to downlink transmission;

[0287] QoS corresponding to downlink transmission;

[0288] QoS corresponding to uplink transmission.

[0289] Optionally, the processor 810 is configured to determine an association relationship between the downlink frequency domain unit and the frequency domain unit used to send the PUCCH in at least one of the following ways:

[0290] High-level signaling configuration;

[0291] DCI indication;

[0292] Predefined.

[0293] In an embodiment of the present application, the terminal sends multiple PUCCHs through multiple frequency domain units, wherein there are multiple frequency domain units that can be used to send PUCCHs. When multiple PUCCHs need to be transmitted, multiple PUCCHs are transmitted simultaneously through different frequency domain units, thereby reducing communication delay and being able to more flexibly and efficiently utilize the cell's spectrum resources to improve the effectiveness and performance of the communication system.

[0294] It can be understood that the implementation process of each implementation method mentioned in this embodiment can refer to the relevant description of the method embodiment and achieve the same or corresponding technical effects. To avoid repetition, it will not be described here.

[0295] The present application also provides a network-side device, including a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is configured to execute a program or instruction to implement the steps of the method embodiment shown in FIG5 . This network-side device embodiment corresponds to the aforementioned network-side device method embodiment, and each implementation process and implementation method of the aforementioned method embodiment are applicable to this network-side device embodiment and can achieve the same technical effects.

[0296] Specifically, embodiments of the present application also provide a network-side device. As shown in Figure 9, 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. Antenna 91 is connected to radio frequency device 92. In the uplink direction, radio frequency device 92 receives information via antenna 91 and sends the received information to baseband device 93 for processing. In the downlink direction, baseband device 93 processes the information to be transmitted and sends it to radio frequency device 92. Radio frequency device 92 processes the received information and then sends it through antenna 91.

[0297] The method executed by the network-side device in the above embodiment may be implemented in the baseband device 93 , which includes a baseband processor.

[0298] The baseband device 93 may include, for example, at least one baseband board, on which multiple chips are arranged, as shown in Figure 9, 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 network side device operations shown in the above method embodiment.

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

[0300] Specifically, the network side device 900 of the embodiment of the present application also includes: instructions or programs stored in the memory 95 and can be run on the processor 94. The processor 94 calls the instructions or programs in the memory 95 to execute the methods executed by each module shown in Figure 5 and achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0301] An embodiment of the present application also provides a readable storage medium, on which a program or instruction is stored. When the program or instruction is executed by a processor, the various processes of the above-mentioned PUCCH transmission method embodiment are implemented and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

[0302] The processor is the processor in the terminal or network-side device described in the above embodiments. 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 disk. In some examples, the readable storage medium may be a non-transitory readable storage medium.

[0303] An embodiment of the present application further provides a chip, which includes a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the various processes of the above-mentioned PUCCH transmission method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0304] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

[0305] An 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 the various processes of the above-mentioned PUCCH transmission method embodiment and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0306] An embodiment of the present application also provides a PUCCH transmission system, including: a terminal and a network side device, wherein 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.

[0307] It should be noted that, in this article, the terms "comprise", "include" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device comprising a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "comprises a ..." does not exclude the presence of other identical elements in the process, method, article or device comprising the 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 opposite order according to the functions involved. For example, the described method may be performed in an order different from that described, and various steps may also be added, omitted or combined. In addition, the features described with reference to certain examples may be combined in other examples.

[0308] Through the description of the above embodiments, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of a computer software product plus a necessary general-purpose hardware platform, or of course, by hardware. The computer software product is stored in a storage medium (such as ROM, RAM, magnetic disk, optical disk, etc.) and includes a number of instructions for enabling a terminal or network-side device to execute the methods described in each embodiment of the present application.

[0309] The embodiments of the present application are described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of this application, ordinary technicians in this field can also make many forms of implementation methods without departing from the purpose of this application and the scope of protection of the claims. These implementation methods are all within the protection of this application.

Claims

1. A method for transmitting a Physical Uplink Control Channel (PUCCH), wherein, 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 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.

3. The PUCCH transmission method according to claim 1, wherein 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 transmitted is greater than the number of PUCCHs that the terminal supports to be simultaneously transmitted 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 according to a preset rule 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, wherein, The method further includes: The terminal determines the frequency domain units where the multiple PUCCHs are located according to the 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, wherein, 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: Higher layer signaling configuration; Downlink control information DCI indication; Predefined.

10. A method for transmitting a Physical Uplink Control Channel (PUCCH), wherein, Including: The network side device receives multiple PUCCHs through multiple frequency domain units, where multiple frequency domain units are 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 transmission of PUCCH; The minimum interval between the frequency domain units that the terminal supports for simultaneous transmission of PUCCH.

13. The PUCCH transmission method according to claim 10, wherein, 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, wherein, Including: A first sending module, configured to send multiple PUCCHs through multiple frequency domain units, where multiple frequency domain units are 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 transmission of PUCCH; The minimum interval between the frequency domain units that the terminal supports for simultaneous transmission of PUCCH.

18. The PUCCH transmission device according to claim 16, wherein, The sending of multiple PUCCHs through multiple frequency domain units includes: When the number of PUCCHs that need 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, wherein, 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, wherein, 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 apparatus 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 apparatus 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: High-layer signaling configuration; DCI indication; Predefinition.

23. A physical uplink control channel PUCCH transmission device, wherein, 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 apparatus according to claim 23, wherein, The apparatus 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 apparatus 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 apparatus further includes: A second transmitting module, configured to transmit the 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, wherein, It includes a processor and a memory. 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, wherein, It includes a processor and a memory. 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, wherein, 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