WO2020057404A1 - 发送和接收上行控制信息的方法以及通信装置 - Google Patents

发送和接收上行控制信息的方法以及通信装置 Download PDF

Info

Publication number
WO2020057404A1
WO2020057404A1 PCT/CN2019/105272 CN2019105272W WO2020057404A1 WO 2020057404 A1 WO2020057404 A1 WO 2020057404A1 CN 2019105272 W CN2019105272 W CN 2019105272W WO 2020057404 A1 WO2020057404 A1 WO 2020057404A1
Authority
WO
WIPO (PCT)
Prior art keywords
configuration
pucch
pdcch
pusch
bwp
Prior art date
Application number
PCT/CN2019/105272
Other languages
English (en)
French (fr)
Inventor
葛士斌
王潇涵
纪刘榴
杭海存
许华
毕晓艳
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to EP19862946.1A priority Critical patent/EP3843303A4/en
Publication of WO2020057404A1 publication Critical patent/WO2020057404A1/zh
Priority to US17/197,227 priority patent/US11968675B2/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/1607—Details of the supervisory signal
    • H04L1/1664—Details of the supervisory signal the supervisory signal being transmitted together with payload signals; piggybacking
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/21—Control channels or signalling for resource management in the uplink direction of a wireless link, i.e. towards the network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/0001—Systems modifying transmission characteristics according to link quality, e.g. power backoff
    • H04L1/0023—Systems modifying transmission characteristics according to link quality, e.g. power backoff characterised by the signalling
    • H04L1/0026—Transmission of channel quality indication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/1607—Details of the supervisory signal
    • H04L1/1671—Details of the supervisory signal the supervisory signal being transmitted together with control information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1812—Hybrid protocols; Hybrid automatic repeat request [HARQ]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1829—Arrangements specially adapted for the receiver end
    • H04L1/1854—Scheduling and prioritising arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1829—Arrangements specially adapted for the receiver end
    • H04L1/1861—Physical mapping arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1867—Arrangements specially adapted for the transmitter end
    • H04L1/1896—ARQ related signaling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signaling, i.e. of overhead other than pilot signals
    • H04L5/0055—Physical resource allocation for ACK/NACK
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signaling, i.e. of overhead other than pilot signals
    • H04L5/0057—Physical resource allocation for CQI
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/10—Scheduling measurement reports ; Arrangements for measurement reports
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal

Definitions

  • the present application relates to the field of wireless communication, and more particularly, to a method for transmitting and receiving uplink control information and a communication device.
  • Coordination multiple point (CoMP) transmission is a method for solving the problem of inter-cell interference and improving the throughput of cell-edge users.
  • the network device may schedule a physical uplink control channel (PUCCH) and a physical uplink shared channel (PUSCH) for the terminal device in advance.
  • a terminal device can send uplink control information (uplink control information (UCI)) to a network device through a PUCCH, and can also send uplink data to a network device through a PUSCH.
  • uplink control information uplink control information
  • the terminal device may transmit some or all of the information in the UCI originally transmitted on the PUCCH through the PUSCH.
  • a multi-site scheduling scheme based on multiple DCIs supports two or more network devices to schedule respective PDSCH and PUSCH for terminal devices through the DCIs respectively sent by them for data transmission.
  • Each network device can receive UCI on the PUCCH configured for the terminal device, in order to obtain hybrid automatic retransmission (HARQ) information and / or channel state information (CSI) for the PDSCHs scheduled by them. .
  • HARQ hybrid automatic retransmission
  • CSI channel state information
  • the network equipment is transparent to the terminal equipment.
  • the terminal device does not know whether the PUCCH and the PUSCH are sent to the same network device.
  • PUCCH is a PUCCH sent to network device # 1
  • PUSCH is a PUSCH scheduled by network device # 2
  • network device # 2 may not know the transmission on the PUSCH UCI cannot analyze the uplink data transmitted on UCI and PUSCH; and network device # 1 cannot receive the UCI.
  • the terminal device may need to resend the uplink data that was not successfully received, and the network device cannot make a UCI in time, and cannot make a reasonable decision for data transmission. Therefore, the performance of data transmission may be reduced, and the user experience is not good.
  • the application provides a method and a communication device for sending and receiving UCI, so as to reduce unnecessary retransmissions, improve resource utilization, and improve transmission performance.
  • a method for sending uplink control information is provided. This method may be executed by a terminal device, or may also be executed by a chip configured in the terminal device, which is not limited in this application.
  • the method includes: determining that there is a resource overlap between the PUSCH and the PUCCH, wherein the PUSCH is scheduled by the PDCCH, and the PUCCH is used to transmit UCI; and if the PUCCH is associated with the PDCCH, UCI is transmitted on the PUSCH.
  • UCI is not transmitted on the PUSCH.
  • whether the UCI can be transmitted through the PUSCH can be determined based on whether there is an association between the configuration parameters of the PUCCH and the PDCCH.
  • UCI may be transmitted through the PUSCH; when the two are not associated, UCI is not transmitted through the PUSCH.
  • a method for receiving uplink control information is provided. This method may be executed by a network device, or may also be executed by a chip configured in the network device, which is not limited in this application.
  • the method includes: determining that there is a resource overlap between the PUSCH and the PUCCH, wherein the PUSCH has PDCCH scheduling, and the PUCCH is used for transmitting UCI; and receiving the UCI on the PUSCH.
  • the network device can know in advance which PUCCH is sent to itself and which PUSCH is scheduled by itself. Therefore, the network device can predict which PUCCH can transmit UCI through the PUSCH, and thus can receive UCI on the PUSCH.
  • transmitting UCI through PUSCH may include: transmitting UCI and uplink data on PUSCH; transmitting UCI without PUSCH may include: transmitting uplink data on PUSCH without transmitting UCI. Therefore, when UCI is transmitted through the PUSCH, it can be referred to as resource multiplexing of the PUSCH.
  • the UCI that can be transmitted through the PUSCH may specifically include at least one of the sum of HARQ information.
  • the terminal device may determine whether the PUCCH and the PUSCH are sent to the same network device based on whether the PUCCH and the PUSCH are associated. Therefore, UCI for the network device can be transmitted through the PUSCH, and UCI for other network devices can also be avoided from being transmitted on the PUSCH. Therefore, the network device may receive UCI on the PUSCH, and then determine whether it is necessary to retransmit the PDSCH and / or CSI.
  • the terminal device cannot determine whether the PUCCH is related to the PUSCH, it is also impossible to determine whether the PUCCH and the PUSCH are sent to the same network device (such as network device # 1), and it is possible to send it to another device.
  • a UCI of a network device (for example, described as network device # 2) is transmitted on the PUSCH, so that the network device # 1 cannot accurately analyze the uplink data transmitted on the PUSCH when receiving the PUSCH.
  • the network device can also receive UCI on the corresponding resources, which will not cause the network device to fail to receive UCI due to the inconsistent resources determined by both parties. Since the network equipment can receive UCI, it can make reasonable decisions based on the received UCI. Therefore, waste of resources caused by unnecessary retransmission is avoided, which is beneficial to improving data transmission performance and improving user experience.
  • the association of the PUCCH and the PDCCH may include: association of the PUCCH with a configuration parameter of the PDCCH.
  • the PDCCH configuration parameter may be a PDCCH configuration or a downlink control parameter.
  • the PUCCH is determined by the PUCCH configuration, and the PUCCH configuration is associated with the PDCCH configuration.
  • the PUCCH configuration may be used to determine a PUCCH, for example, a time-frequency resource of the PUCCH.
  • a PUCCH for example, a time-frequency resource of the PUCCH.
  • the PUCCH configuration includes an indication of the PDCCH configuration.
  • the associated PDCCH configuration may be indicated in the PUCCH configuration in an explicit manner.
  • the PUCCH configuration and the PDCCH configuration are the same bandwidth part BWP configuration, and the identifier of the BWP uplink dedicated parameter of the bandwidth part to which the PUCCH configuration belongs is the same as the identifier of the BWP downlink dedicated parameter to which the PDCCH configuration belongs.
  • the PUCCH configuration and the PDCCH configuration belong to the same serving cell configuration.
  • the associated PUCCH configuration and PDCCH configuration may be indicated in an implicit manner.
  • the resources of the PUCCH are determined by the CSI reporting configuration, and the CSI reporting configuration is associated with the PDCCH configuration.
  • the CSI reporting configuration can be used to determine the PUCCH.
  • the BWP configured and activated by the CSI report may be used to determine time-frequency resources of the PUCCH.
  • the CSI report configuration is associated with the PDCCH configuration, it can be considered that the PUCCH is associated with the PDCCH configuration.
  • the CSI report configuration includes an indication of the PDCCH configuration.
  • the associated PDCCH configuration may be indicated in the CSI reporting configuration in an explicit manner.
  • Each CSI reporting configuration may be associated with one PDCCH configuration.
  • the CSI measurement configuration to which the CSI report configuration belongs includes an indication of the PDCCH configuration.
  • the associated PDCCH configuration may be indicated in the CSI measurement configuration in an explicit manner. Since each CSI measurement configuration may include one or more CSI reporting configurations, when one CSI measurement configuration is associated with one PDCCH configuration, one or more CSI reporting configurations in the CSI measurement configuration may be associated by the same PDCCH configuration.
  • the CSI measurement configuration to which the CSI report configuration belongs and the PDCCH configuration belong to the same serving cell and the identifier of the CSI measurement configuration is the same as the identifier of the BWP downlink dedicated parameter to which the PDCCH configuration belongs.
  • the CSI measurement configuration to which the CSI report configuration belongs and the PDCCH configuration belong to the same BWP-specific parameters in the same serving cell configuration.
  • the CSI measurement configuration to which the CSI report configuration belongs and the PDCCH configuration belong to the same serving cell configuration.
  • the associated CSI measurement configuration and PDCCH configuration can be indicated in an implicit manner, so that the associated CSI reporting configuration and PDCCH configuration can be determined.
  • the PUCCH is taken from multiple PUCCH resources in a PUCCH configuration, and each PUCCH resource is configured by a set of PUCCH resource configuration parameters. Includes an indication of the associated PDCCH configuration.
  • an associated PDCCH configuration can be configured for each PUCCH resource in an explicit manner.
  • a configuration method is provided. The method may be executed by a network device, or may be executed by a chip configured in the network device.
  • the method includes: generating first configuration information, where the first configuration information is used to indicate an associated PUCCH configuration and a PDCCH configuration; and sending the first configuration information.
  • a configuration method is provided. The method may be executed by a terminal device, or may be executed by a chip configured in the terminal device.
  • the method includes: receiving first configuration information, where the first configuration information is used to indicate an associated physical uplink control channel PUCCH configuration and a physical downlink control channel PDCCH configuration; and determining the associated PUCCH configuration and PDCCH configuration according to the first configuration information.
  • the terminal device can determine which PDCCH configuration and PUCCH configuration correspond to the same network device based on the association relationship between the PUCCH configuration and the PDCCH configuration, so that the PUCCH resources can be determined to transmit UCI according to the instructions of the network device.
  • the network device can also receive UCI on the corresponding resources, which will not cause the network device to fail to receive UCI due to inconsistent resources determined by both parties. Therefore, by introducing the first configuration information described above, communication between the terminal device and the network device can be facilitated, which is beneficial to improving transmission performance and user experience.
  • the first configuration information is a PUCCH configuration
  • the PUCCH configuration includes an indication of a PDCCH configuration
  • the associated PDCCH configuration is explicitly indicated in the PUCCH configuration.
  • the first configuration information is a PDCCH configuration
  • the PDCCH configuration includes an indication of a PUCCH configuration
  • the associated PUCCH configuration is explicitly indicated in the PDCCH configuration.
  • the first configuration information is a serving cell configuration
  • the serving cell configuration includes one or more groups of BWP uplink dedicated parameters and one or more groups of BWP downlink Dedicated parameters
  • each set of BWP uplink dedicated parameters includes a PUCCH configuration
  • each set of BWP downlink dedicated parameters includes a PDCCH configuration; where the associated PUCCH configuration and the PDCCH configuration are the same BWP configuration, and the identifier of the BWP uplink dedicated parameter to which the PUCCH configuration belongs It is the same as the identifier of the BWP downlink dedicated parameter to which the PDCCH configuration belongs.
  • the first configuration information is a serving cell configuration
  • the serving cell configuration includes one or more groups of BWP uplink dedicated parameters and one or more groups of BWP Downlink-specific parameters.
  • Each group of BWP uplink-specific parameters includes one or more PUCCH configurations
  • each group of BWP downlink-specific parameters includes one or more PDCCH configurations.
  • the associated PUCCH configuration and the PDCCH configuration are the same BWP configuration, and the PUCCH configuration belongs to
  • the identifier of the BWP uplink dedicated parameter is the same as the identifier of the BWP downlink dedicated parameter to which the PDCCH configuration belongs, and the identifier of the PUCCH configuration is the same as the identifier of the PDCCH configuration.
  • the first configuration information is a serving cell configuration, and an associated PUCCH configuration and a PDCCH configuration belong to a same serving cell configuration.
  • a configuration method is provided.
  • the method may be executed by a network device, or may be executed by a chip configured in the network device.
  • the method includes generating second configuration information, where the second configuration information is used to indicate associated channel state information CSI reporting configuration and physical downlink control channel PDCCH configuration; and transmitting the second configuration information.
  • a configuration method is provided. The method may be executed by a network device, or may be executed by a chip configured in the network device.
  • the method includes: receiving second configuration information, where the second configuration information is used to indicate associated channel state information CSI reporting configuration and physical uplink shared channel PUSCH configuration; and determining the associated CSI reporting configuration and PDCCH configuration.
  • the terminal device can determine which CSI reporting configuration and PDCCH configuration correspond to the same network device based on the association between the CSI reporting configuration and the PDCCH configuration, so that the PUCCH resource can be determined to transmit UCI according to the instructions of the network device.
  • the network device can also receive UCI on the corresponding resources, which will not cause the network device to fail to receive UCI due to inconsistent resources determined by both parties. Therefore, by introducing the second configuration information, it is beneficial to improve transmission performance and user experience.
  • the second configuration information is a CSI report configuration
  • the CSI report configuration includes an indication of a PDCCH configuration
  • the associated PDCCH configuration is explicitly indicated in the CSI reporting configuration.
  • the second configuration information is a CSI measurement configuration
  • the CSI measurement configuration is used to configure one or more CSI reporting configurations including a CSI reporting configuration
  • the CSI measurement configuration includes an indication of a PDCCH configuration.
  • the associated PDCCH configuration is explicitly indicated in the CSI measurement configuration.
  • the CSI measurement configuration may include one or more CSI reporting configurations, when the CSI measurement configuration is associated with a PDCCH configuration, one or more CSIs in the CSI measurement configuration may be associated with the same PDCCH configuration.
  • the second configuration information is a serving cell configuration
  • the serving cell configuration includes one or more CSI measurement configurations and one or more groups of BWP downlink dedicated Parameters
  • the CSI measurement configuration includes one or more CSI reporting configurations
  • the BWP downlink dedicated parameters include one or more PDCCH configurations; wherein the identifier of the CSI measurement configuration to which the CSI reporting configuration belongs and the BWP downlink dedicated parameters to which the associated PDCCH configuration belongs The identity is the same.
  • the second configuration information is a serving cell configuration
  • the serving cell configuration includes one or more groups of BWP-specific parameters
  • each group of BWP-specific parameters includes a PDCCH Instructions for configuration and instructions for CSI reporting configuration.
  • the second configuration information is a serving cell configuration
  • the associated CSI measurement configuration and the PDCCH configuration belong to the same serving cell configuration
  • each CSI measurement configuration includes one or Multiple CSI reporting configurations.
  • the associated CSI reporting configuration and PDCCH configuration are indicated in an implicit manner.
  • a communication device which includes each module or unit for performing the method in any one of the first, fourth, or sixth aspects and any possible implementation manner of the first, fourth, or sixth aspects.
  • a communication device including a processor.
  • the processor is coupled to the memory, and can be used to execute instructions in the memory to implement the method in the first, fourth, or sixth aspect and any possible implementation manner of the first, fourth, or sixth aspect.
  • the communication device further includes a memory.
  • the communication device further includes a communication interface, and the processor is coupled to the communication interface.
  • the communication device is a terminal device.
  • the communication interface may be a transceiver, or an input / output interface.
  • the communication device is a chip configured in a terminal device.
  • the communication interface may be an input / output interface.
  • the transceiver may be a transceiver circuit.
  • the input / output interface may be an input / output circuit.
  • a communication device which includes each module or unit for performing the method in the second, third, or fifth aspect and any one of the possible implementation manners of the second, third, or fifth aspect.
  • a communication device including a processor.
  • the processor is coupled to the memory and can be used to execute instructions in the memory to implement the method in the second, third, or fifth aspect and any possible implementation manner of the second, third, or fifth aspect.
  • the communication device further includes a memory.
  • the communication device further includes a communication interface, and the processor is coupled to the communication interface.
  • the communication device is a network device.
  • the communication interface may be a transceiver, or an input / output interface.
  • the communication device is a chip configured in a network device.
  • the communication interface may be an input / output interface.
  • the transceiver may be a transceiver circuit.
  • the input / output interface may be an input / output circuit.
  • a processor including: an input circuit, an output circuit, and a processing circuit.
  • the processing circuit is configured to receive a signal through the input circuit and transmit a signal through the output circuit, so that the processor executes any of the first to sixth aspects and any one of the first to sixth aspects. method.
  • the processor may be a chip
  • the input circuit may be an input pin
  • the output circuit may be an output pin
  • the processing circuit may be a transistor, a gate circuit, a flip-flop, and various logic circuits.
  • An input signal received by the input circuit may be received and input by, for example, but not limited to, a receiver
  • a signal output by the output circuit may be, for example, but not limited to, output to a transmitter and transmitted by the transmitter
  • the circuits may be the same circuit, which are used as input circuits and output circuits respectively at different times.
  • the embodiments of the present application do not limit specific implementations of the processor and various circuits.
  • a processing device including a processor and a memory.
  • the processor is used to read instructions stored in the memory, and can receive signals through a receiver and transmit signals through a transmitter to perform any of the first or second aspects, and the first to sixth aspects and the first to sixth aspects.
  • processors there are one or more processors, and one or more memories.
  • the memory may be integrated with the processor, or the memory is separately provided from the processor.
  • the memory may be a non-transitory memory, such as a read-only memory (ROM), which may be integrated on the same chip as the processor, or may be separately set in different On the chip, the embodiment of the present application does not limit the type of the memory and the way of setting the memory and the processor.
  • ROM read-only memory
  • sending instruction information may be a process of outputting instruction information from a processor
  • receiving capability information may be a process of receiving input capability information by a processor.
  • the processed output data can be output to the transmitter, and the input data received by the processor can come from the receiver.
  • the transmitter and the receiver may be collectively referred to as a transceiver.
  • the processing device in the above twelfth aspect may be a chip, and the processor may be implemented by hardware or software.
  • the processor may be a logic circuit, an integrated circuit, or the like.
  • the processor may be a general-purpose processor, which is implemented by reading software codes stored in a memory.
  • the memory may be integrated in the processor, may be located outside the processor, and exist independently.
  • a computer program product includes a computer program (also referred to as code or instructions), and when the computer program is executed, causes a computer to execute the first to the first steps described above.
  • the method in the six aspects and any one of the possible implementation manners of the first to sixth aspects.
  • a computer-readable medium stores a computer program (also referred to as code, or instructions), which when executed on a computer, causes the computer to execute the first to the first.
  • a computer program also referred to as code, or instructions
  • a communication system including the foregoing network device and terminal device.
  • FIG. 1 is a schematic diagram of a communication system applicable to a method according to an embodiment of the present application
  • FIG. 2 is a schematic flowchart of a method for sending and receiving configuration information according to an embodiment of the present application
  • FIG. 3 is a schematic flowchart of a method for sending and receiving configuration information according to an embodiment of the present application
  • FIG. 4 is a schematic flowchart of a method for sending and receiving uplink control information according to an embodiment of the present application
  • FIG. 5 is a schematic block diagram of a communication device according to an embodiment of the present application.
  • FIG. 6 is a schematic structural diagram of a terminal device according to an embodiment of the present application.
  • FIG. 7 is a schematic structural diagram of a network device according to an embodiment of the present application.
  • GSM global mobile communication
  • CDMA code division multiple access
  • WCDMA broadband code division multiple access
  • GPRS general packet radio service
  • LTE long term evolution
  • FDD frequency division duplex
  • TDD Time Division Duplex
  • UMTS Universal Mobile Telecommunications System
  • WiMAX Global Interoperability for Microwave Access
  • the network device in the communication system may be any kind of device with wireless transceiver function or a chip that can be set on the device.
  • the device includes but is not limited to: evolved Node B (eNB), wireless Network Controller (RNC), Node B (NB), Base Station Controller (BSC), Base Transceiver Station (BTS), Home Base Station (e.g., Home NodeB) , Or Home NodeB (HNB), BaseBand Unit (BBU), Access Point (AP), wireless relay node, wireless backhaul node, wireless fidelity (WIFI) system, Transmission point (TP) or send and receive point (TRP), etc., can also be 5G, such as NR, gNB in the system, or, transmission point (TRP or TP), one or a group of base stations in the 5G system
  • the antenna panel may also be a network node constituting a gNB or a transmission point, such as a baseband unit (BBU), or a distributed unit (DU).
  • the gNB may include a centralized unit (CU) and a DU.
  • the gNB may also include a radio frequency unit (radio unit, RU).
  • CU implements some functions of gNB
  • DU implements some functions of gNB, for example, CU implements radio resource control (RRC), packet data convergence layer protocol (PDCP) layer functions, and DU implements wireless chain Functions of radio control (RLC), media access control (MAC) and physical (PHY) layers.
  • RRC radio resource control
  • PDCP packet data convergence layer protocol
  • DU implements wireless chain Functions of radio control (RLC), media access control (MAC) and physical (PHY) layers.
  • RRC radio resource control
  • PDCP packet data convergence layer protocol
  • PHY physical
  • the network device may be a CU node, or a DU node, or a device including a CU node and a DU node.
  • the CU can be divided into network devices in the access network RAN, or the CU can be divided into network devices in the core network CN, which is not limited herein.
  • the terminal equipment in the communication system can also be referred to as user equipment (UE), access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user Terminal, terminal, wireless communication device, user agent, or user device.
  • the terminal device in the embodiment of the present application may be a mobile phone, a tablet, a computer with a wireless transmitting and receiving function, a virtual reality (VR) terminal device, or an augmented reality (AR) terminal.
  • Equipment wireless terminals in industrial control, wireless terminals in self driving, wireless terminals in remote medical, wireless terminals in smart grid, transportation security ( wireless terminals in transportation, wireless terminals in smart cities, wireless terminals in smart homes, and so on.
  • the embodiment of the present application does not limit the application scenario.
  • Uplink control information may include one of channel state information (CSI), hybrid automatic repeat request (HARQ) information, and uplink scheduling request (SR) Or more.
  • CSI channel state information
  • HARQ hybrid automatic repeat request
  • SR uplink scheduling request
  • the CSI may include a precoding matrix indicator (PMI), a rank indicator (RI), a channel quality indicator (CQI), and a CSI-RS resource indicator (CSI-RS resource indication). CRI). Based on different time-domain behaviors, CSI can also be divided into periodic CSI, semi-persistent, and aperiodic CSI.
  • PMI precoding matrix indicator
  • RI rank indicator
  • CQI channel quality indicator
  • CSI-RS resource indication CSI-RS resource indicator
  • HARQ information may also be referred to as HARQ-acknowledgement (ACK) information.
  • the HARQ information may include an ACK or (Negative Racknowledgment, NACK) feedback for one or more PDSCHs.
  • ACK may indicate that the PDSCH was successfully received and the data in the PDSCH was successfully decoded; NACK may indicate that the PDSCH was not successfully received or that the data in the PDSCH was not successfully decoded.
  • the network device may perform data retransmission based on the NACK fed back by the terminal device.
  • the embodiments of the present application are mainly described below with respect to UCI that can be transmitted through PUSCH.
  • the UCI may include, for example, HARQ information and / or CSI.
  • the CSI may include periodic CSI and semi-persistent CSI. It should be understood that the method provided in the embodiment of the present application is described in detail below only by taking HARQ information and / or CSI included in the UCI as examples, but this should not constitute any limitation to the present application.
  • This application does not limit the specific content in UCI that can be transmitted through PUSCH. For example, this application does not exclude the possibility that the SR may be placed on the PUSCH for transmission in future protocols.
  • Physical uplink control channel can be used to transmit UCI.
  • the resource determination method for transmitting the PUCCH of the UCI (the PUCCH used for transmitting the UCI is hereinafter referred to as the target PUCCH) may also be different for the sake of differentiation.
  • the terminal device may transmit UCI through the target PUCCH; when the resources of the target PUCCH and PUSCH overlap, the terminal device may further determine the target Whether the PUCCH is related to the PUSCH, and if the PUCCH is associated, send part or all of the information in the UCI through the PUSCH.
  • the association between the target PUCCH and the PUSCH may refer to that the target PUCCH and the PUSCH are PUCCH and PUSCH sent to the same network device. It should be understood that the target PUCCH and PUSCH are PUCCH and PUSCH sent to the same network device, but are only one possible form of association between the target PUCCH and PUSCH, and should not constitute any limitation to this application. The embodiments of this application include but are not limited to this.
  • the PUCCH configuration (PUCCH config) for determining the resource of the target PUCCH and the PDCCH configuration (PDCCH config) for scheduling the PDCCH of the PUSCH may be configured based on the same network device.
  • the associated PUCCH configuration and PDCCH configuration may correspond to the same network device.
  • the CSI report configuration (CSI-report configuration) used to determine the resource of the target PUCCH and the PDCCH configuration used to schedule the PDCCH of the PUSCH may be configured based on the same network device.
  • the associated CSI reporting configuration and PDCCH configuration may correspond to the same network device.
  • Serving cell configuration It can be used to configure a serving cell for a terminal device.
  • the network device can configure the serving cell for the terminal device through high-level parameters, such as the serving cell configuration control element (ServingCellConfiginformation element).
  • servingCellConfiginformation element the serving cell configuration control element
  • the serving cell configuration may include one or more sets of bandwidth part (BWP) downlink parameters, uplink configuration (uplink configuration), and CSI measurement configuration (CSI-MeasConfig).
  • the uplink configuration may include one or more BWP uplink parameters.
  • Each set of BWP downlink parameters may be configured for one BWP, for example, the BWP ID may be indicated in the BWP downlink parameters.
  • Each group of BWP uplink parameters may also be configured for one BWP, for example, the BWP ID may be indicated in the BWP downlink parameters.
  • Each set of BWP downlink parameters may include BWP downlink dedicated (DL dedicated) parameters and BWP downlink common (DL common) parameters.
  • the BWP downlink dedicated parameters may specifically include a PDCCH configuration and a PDSCH configuration.
  • Each set of BWP uplink parameters may include BWP uplink dedicated parameters (ULlink dedicated) and BWP uplink common parameters (UPcommon), among which the BWP uplink dedicated parameters may specifically include PUCCH configuration and PUSCH configuration.
  • the CSI measurement configuration may include one or more CSI reporting configurations.
  • the common parameters can be understood as cell-level (cell-specific) parameters, and the dedicated parameters can be understood as UE-level parameters.
  • the reflection of the BWP uplink specific parameters in the NR protocol may be BWP-UplinkDedicated, and the reflection of the BWP downlink special parameters in the NR protocol may be BWP-DownlinkDedicated.
  • BWP Bandwidth part
  • PUCCH configuration UE-level PUCCH parameters can be configured based on each BWP.
  • the PUCCH configuration may include parameters such as the ID of the PUCCH resource set and the ID of the PUCCH resource.
  • the PUCCH configuration may be configured, for example, through a PUCCH-Config information element (PUCCH-Config) in a high-level parameter.
  • the PUCCH-Config IE may include, for example, a resource set addition state list (resourceSetToAddModList) and a resource set release list (resourceSetToReleaseList). Each list may include IDs of one or more PDCCH resource sets, and each PDCCH resource set may include one or more PDCCH resources.
  • the PUCCH-config IE may further include, for example, a resource addition status list (resourceToAddModList) and a resource release list (resourceToReleaseList). Each list may include IDs of one or more PDCCH resources.
  • the PUCCH configuration may further configure a time domain position and a frequency domain position of each PUCCH resource.
  • one or more network devices can configure a PUCCH resource pool for the terminal device through their respective PUCCH configuration, and the resource pool includes multiple PUCCH resources.
  • the PUCCH resources configured by each network device for the terminal device are taken from the PUCCH resource pool.
  • the PUCCH resource pool is a complete set of PUCCH resources configured by each network device for the same terminal device, and the PUCCH resources configured by each network device for the terminal device may be a subset or a complete set of the PUCCH resource pool. This application does not limit this.
  • the terminal device may determine a corresponding PUCCH resource pool according to one or more PUCCH configurations.
  • the terminal device may select a PUCCH resource set from the above-mentioned resource set addition status list according to the length of the UCI, and may determine a target PUCCH resource from the PUCCH resource set based on the PUCCH resource indicated by the network device .
  • the terminal device can determine the resource of the target PUCCH based on the PUCCH configuration.
  • PUCCH configuration can also be used to configure PUCCH resources for multiple CSIs.
  • the PUCCH-Config IE may include multiple CSI-PUCCH resource lists (multi-CSI-PUCCH-ResourceList), for example, the list may include two PUCCH resources.
  • the terminal device may determine the resources of the target PUCCH from the multi-CSI-PUCCH-ResourceList according to the length of the UCI.
  • CSI reporting configuration can be used to configure resources for reporting of periodic CSI or semi-persistent CSI.
  • the CSI report configuration can be configured, for example, through CSI-ReportConfig in the high-level parameters.
  • the CSI-ReportConfigIE may include, for example, resources of a PUCCH for transmitting semi-persistent CSI and resources of a PUCCH for transmitting periodic CSI.
  • the CSI-ReportConfigIE includes a PUCCH-CSI resource list (pucch-CSI-ResourceList), and the PUCCH resource can be specifically indicated by the PUCCH resource identifier.
  • the terminal device may determine the resource of the target PUCCH according to the CSI report configuration and the BWP activated in physical layer signaling (such as DCI). In other words, when the UCI contains only one CSI, the terminal device can determine the target PUCCH resource based on at least the CSI report configuration.
  • the CSI report configuration can also be used to configure the report quantity. Specifically, it can be used to indicate which information needs to be reported in the reported CSI.
  • the information reported in the CSI can include, but is not limited to, CRI, RI, PMI, and CQI .
  • CSI measurement configuration can be used to configure CSI-RS resources and determine the PUCCH used for CSI reporting.
  • Network devices can configure one or more CSI reporting configurations for a terminal device through CSI measurement configuration.
  • the CSI measurement configuration can be configured by, for example, CSI-MeasConfig in the high-level parameters.
  • the CSI-MeasConfig IE may include, for example, a CSI report configuration increase status list (csi-ReportConfigToAddModList) and a CSI report configuration release list (csi-ReportConfigToReleaseList). Each list includes one or more CSI reporting configurations.
  • Physical uplink shared channel can be used to transmit uplink data, and can also be used to transmit UCI.
  • the PUSCH may be scheduled by a network device, such as through DCI scheduling in the PDCCH. This scheduling method may be called dynamic grant.
  • PUSCH can also be configured grant.
  • the configuration authorization can be fully RRC-configured uplink authorization (fully granting RRC-configured UL grant).
  • This authorization method can be called Type 1 configuration authorized PUSCH transmission (Type PUSCH transmissions with a configured grant), or it can be triggered by PDCCH.
  • This kind of authorization method can be called PUSCH transmission of type 2 configuration authorization (Type 2 PUSCH transmissions with a configured grant). It should be understood that the PUSCH authorization methods listed above are merely examples, and the application does not limit the PUSCH authorization methods.
  • the network device may schedule the PUSCH through the DCI format 0_0 or DCI format 0_1, for example, and indicates the time and frequency domain positions of the PUSCH in the DCI.
  • the network device may, for example, configure resources for the configured and authorized PUSCH through a BWP uplink dedicated parameter, for example, through a configuration authorization configuration control element (ConfiguredGrantConfigIE) in a high-level parameter.
  • ConfiguredGrantConfigIE configuration authorization configuration control element
  • PUSCH configuration UE-level PUSCH parameters can be configured based on each BWP.
  • the PUSCH configuration can be configured, for example, through PUSCH-Config in the high-level parameters.
  • the parameters configured in the PUSCH-Config IE may include, for example, data scrambling code identification, demodulation reference signal (DMRS) type, power control, and the like.
  • DMRS demodulation reference signal
  • PDCCH configuration PDCCH parameters can be configured based on each BWP in each cell (for example, control resource set (CORESET), search space) and other parameters that can be used for blind detection of PDCCH .
  • the PDCCH configuration can be configured by, for example, the PDCCH-config in the high-level parameters.
  • the PDCCH-config IE may include, for example, a control resource set addition state list (controlResourceSetToAddModList) and a control resource set release list (controlResourceSetToReleaseList). Each list may include the ID of one or more control resource sets.
  • the PDCCH-config IE may further include, for example, a search space addition state list (searchSpaceToAddModList) and a search space release list (searchSpaceToReleaseList). Each list may include the ID of one or more search spaces.
  • the PDCCH configuration of the PDCCH can be understood as the PDCCH configuration on which the PDCCH is received, or the terminal device blindly detects the PDCCH in a search space determined by the PDCCH configuration.
  • the PDCCH configuration of the PDCCH can be understood as the PDCCH configuration on which the PDCCH is transmitted, or the network device sends the PDCCH on some resources in the search space determined by the PDCCH configuration.
  • Sounding reference signal (SRS) configuration can be used to configure SRS transmission.
  • SRS configuration can be used to define SRS resource list and SRS resource set list.
  • Each SRS resource set may include one or more SRS resources.
  • SRS configuration can be configured through SRS-config in the high-level parameters.
  • the SRS-config IE may include, for example, an SRS resource set addition status list (srs-ResourceSetToAddModList) and an SRS resource set release list (srs-ResourceSetToReleaseList).
  • Each list may include IDs of one or more SRS resource sets, and each SRS resource set may include one or more SRS resources.
  • the SRS-config IE may further include, for example, an SRS resource addition status list (srs-ResourceToAddModList) and an SRS resource release list (srs-ResourceToReleaseList). Each list may include the ID of one or more SRS resources.
  • Spatial relationship It can also be referred to as uplink transmission configuration indicator (ULTCI).
  • the spatial relationship can be used to determine the transmit beam of the uplink signal. This spatial relationship can be determined by beam training.
  • the reference signal used for beam training can be, for example, an uplink reference signal, such as a sounding reference signal (SRS), or a downlink reference signal, such as a synchronization signal block (synchronization signal block, SSB) or a channel state information reference signal (channel state information reference, CSI-RS).
  • SRS sounding reference signal
  • SSB synchronization signal block
  • CSI-RS channel state information reference signal
  • Each spatial relationship may include an index of a serving cell, an identifier of a BWP (BWP ID), and a reference signal resource identifier.
  • the reference signal resource identifier may be any one of the following: SSB resource index (SSB resource indicator, SSBRI), non-zero power CSI-RS reference signal resource identifier (NZP-CSI-RS-ResourceId) or SRS resource identifier (SRS- ResourceId).
  • the SSB resource identifier may also be referred to as the SSB identifier (SSB index).
  • the index of the serving cell, the BWP ID, and the reference signal resource identifier refer to the reference signal resource used during the beam training process, and the corresponding serving cell and BWP.
  • a spatial relationship is used to determine a transmit beam, that is, an index of a serving cell, a BWP ID, and a reference signal resource identifier can be used to determine a transmit beam.
  • the terminal device can maintain the correspondence between the serving cell index, BWP ID, and reference signal resource identifier and the transmission beam during the beam training process, and the network device can maintain the serving cell index, BWP ID, and reference signal resource during the beam training process. Identify the corresponding relationship with the received beam. By referring to the signal resource identifier, a pairing relationship between the transmitting beam and the receiving beam can be established.
  • the terminal device may determine the transmitting beam based on the spatial relationship indicated by the network device, and the network device may determine the receiving beam based on the same spatial relationship.
  • the network device may configure a spatial relationship list for the terminal device through a high-level parameter, such as PUCCH-config, and the spatial relationship list may include multiple spatial relationships. Thereafter, the network device can activate a spatial relationship through the spatial relationship of high-level signaling (such as MAC CE). This spatial relationship can be used to determine the transmit beam of the PUCCH transmitted by the terminal device and the receive beam of the PUCCH received by the network device.
  • a high-level parameter such as PUCCH-config
  • the spatial relationship list may include multiple spatial relationships.
  • the network device can activate a spatial relationship through the spatial relationship of high-level signaling (such as MAC CE). This spatial relationship can be used to determine the transmit beam of the PUCCH transmitted by the terminal device and the receive beam of the PUCCH received by the network device.
  • the network device can also configure the spatial relationship corresponding to multiple SRS resources for the terminal device through high-level parameters such as SRS-config and IE. Thereafter, the network device may indicate the selected SRS resource through the SRI field of the physical layer signaling (such as DCI). Therefore, the terminal device can determine the selected spatial relationship, and the spatial relationship can be used to determine the transmission beam that the terminal device sends the PUSCH and the reception beam that the network device receives the PUSCH.
  • high-level parameters such as SRS-config and IE.
  • the network device may indicate the selected SRS resource through the SRI field of the physical layer signaling (such as DCI). Therefore, the terminal device can determine the selected spatial relationship, and the spatial relationship can be used to determine the transmission beam that the terminal device sends the PUSCH and the reception beam that the network device receives the PUSCH.
  • Beam The embodiment of the beam in the NR protocol can be a spatial filter, or a spatial filter or a spatial parameter.
  • the beam used to send a signal can be called a transmission beam (transmission beam, Tx beam), it can also be called a spatial transmission filter (spatial domain transmission filter) or a spatial transmission parameter (spatial domain transmission parameter); a beam used to receive a signal It can be called a receive beam (reception beam, Rx beam), it can also be called a spatial receive filter (spatial domain receive filter) or a spatial receive parameter (spatial domain receive parameter).
  • a transmitting beam may refer to a signal intensity distribution in different directions of a space after a signal is transmitted through an antenna
  • a receiving beam may refer to a signal intensity distribution of a wireless signal received from an antenna in different directions in space.
  • Beam pairing relationship That is, the pairing relationship between the transmitting beam and the receiving beam, that is, the pairing relationship between the spatial transmitting filter and the spatial receiving filter. Transmitting a signal between a transmitting beam and a receiving beam having a beam pairing relationship can obtain a large beamforming gain.
  • the transmitting end and the receiving end may obtain a beam pairing relationship through beam training.
  • the transmitting end may send the reference signal in a beam scanning manner
  • the receiving end may also receive the reference signal in a beam scanning manner.
  • the transmitting end may form beams with different directivity in space by means of beamforming, and may poll on multiple beams with different directivity, so as to transmit the reference signal through beams with different directivity, so that The power of the reference signal to transmit the reference signal in the direction pointed by the transmission beam can reach the maximum.
  • the receiving end can also form beams with different directivity in the space by means of beamforming, and can poll on multiple beams with different directivity to receive reference signals through the beams with different directivity, so that the receiving end receives The power of the reference signal can be maximized in the direction pointed by the receiving beam.
  • the receiving end can perform channel measurement based on the received reference signal, and report the measurement result to the transmitting end through CSI.
  • the receiving end may report a portion of the reference signal receiving power (reference signal receiving power (RSRP)) of the larger reference signal resource to the transmitting end, such as reporting the identifier of the reference signal resource, so that the transmitting end uses the channel when transmitting data or signaling.
  • RSRP reference signal receiving power
  • each network device can be divided into one or more serving cells, and the serving cell can be considered to be composed of certain frequency domain resources.
  • the cell may be replaced with a serving cell or a carrier unit (component carrier, CC, or component carrier, component carrier, carrier, etc.).
  • component carrier component carrier
  • CC component carrier
  • CC component carrier
  • Carrier aggregation In order to efficiently use fragmented spectrum, the system supports aggregation between different carrier units. A technology that aggregates two or more carriers together to support a larger transmission bandwidth can be referred to as carrier aggregation.
  • Carrier aggregation is specific to terminal equipment. Different terminal equipment can be configured with different CCs, and each CC can correspond to an independent cell. In the embodiment of the present application, one CC may be equated with one cell.
  • the primary cell corresponds to the primary CC (or primary carrier), which may be a cell that establishes the initial connection for the terminal, or a cell that reestablishes the RRC connection, or is designated during the handover process.
  • Main cell Main cell.
  • a secondary cell corresponds to a secondary CC (or a secondary carrier) and may be a cell that is added during RRC reconfiguration and is used to provide additional wireless resources.
  • the terminal device For a connected terminal device, if carrier aggregation is not configured, the terminal device has a serving cell; if carrier aggregation is configured, the terminal device can have multiple serving cells, which can be called a service Cell collection.
  • the primary cell and the secondary cell described above form a serving cell set of the terminal device.
  • the serving cell set includes at least one primary cell and at least one secondary cell.
  • a terminal configured with carrier aggregation can be connected to one PCell and multiple SCells.
  • a terminal device configured with carrier aggregation can be connected to one PCell and a maximum of four SCells.
  • FIG. 1 is a schematic diagram of a communication system 100 suitable for a method for sending and receiving UCI according to an embodiment of the present application.
  • the communication system 100 may include at least one terminal device, such as the terminal device 101 shown in the figure; the communication system 100 may further include at least two network devices, as shown in the figure, the network device # 1 102 ⁇ ⁇ ⁇ # 2 103.
  • the network device # 1 102 and the network device # 2 103 may be stations in the same cell or stations in different cells, which is not limited in this application.
  • the figure is only an example, and shows an example in which the network device # 1 and the network device # 2 are located in the same cell.
  • the network device # 1, 102 and network device # 2 can communicate with each other through a backhaul link.
  • the backhaul link can be a wired backhaul link (such as optical fiber, copper cable), or Is a wireless backhaul link (such as microwave).
  • Network device # 1 and network device # 2 and 103 can cooperate with each other to provide services to the terminal device 101. Therefore, the terminal device 101 can communicate with the network device # 1 and the network device # 2 through wireless links, respectively.
  • network device # 1, 102 and network device # 2, 103 may also use carrier aggregation technology to schedule PDSCH for terminal device 101 on one or more CCs.
  • network device # 1 may schedule PDSCH for terminal device 101 on CC # 1 and CC # 2
  • network device # 2 may schedule PDSCH for terminal device 101 on CC # 1 and CC # 3.
  • the CCs scheduled by network device # 1 and network device # 2 and 103 may be the same or different, which is not limited in this application.
  • the communication delay between network devices that cooperate with each other can be divided into ideal backhaul and non-ideal backhaul.
  • the communication delay between two sites under ideal backhaul can be in the microsecond level, which is negligible compared with the millisecond level scheduling in NR; the communication delay between two sites under non-ideal backhaul can be in the millisecond level. Compared with millisecond-level scheduling in NR, it cannot be ignored.
  • the multi-site scheduling scheme based on multiple DCIs supports multiple network devices to schedule their respective PDSCHs for terminal devices through the DCIs respectively sent by them for data transmission. Because the network device is transparent to the terminal device, the terminal device can receive multiple DCIs, but it is not known whether the multiple DCIs are from one network device or multiple network devices. Therefore, this multi-site-based multi-site scheduling scheme can also be called a multi-DCI scheduling scheme.
  • the network device # 1 in FIG. 1 may send a PDCCH to the terminal device 101.
  • the PDCCH may carry a DCI.
  • the DCI may be used to schedule a PDSCH for the terminal device 101 and indicate a resource of the PUCCH.
  • the PDSCH scheduled by the network device # 1 is referred to as PDSCH # 1
  • the PUCCH determined by the network device # 1 is referred to as PUCCH # 1, for example.
  • the network device # 2 103 may also send a PDCCH to the terminal device 101.
  • the PDCCH may also carry a DCI, and the DCI may also schedule a PDSCH for the terminal device 101 and indicate the resources of the PUCCH.
  • the PDSCH scheduled by the network device # 2 103 is, for example, PDSCH # 2
  • the PUCCH determined by the network device # 2 103 is, for example, PUCCH # 2.
  • the terminal device 101 can receive PDSCH # 1 from the network device # 1 and 102, and feedback HARQ # 1 for PDSCH # 1 through PUCCH # 1; the terminal device 101 can also receive PDSCH # from the network device # 2 2 and feedback HARQ # 2 for PDSCH # 2 through PUCCH # 2.
  • the terminal device may feedback HARQ to different network devices through different UCIs.
  • the terminal device 101 can send UCI # 1 on PUCCH # 1, and UCI # 1 carries HARQ # 1, and the terminal device 101 can also send UCI # 2 on PUCCH # 2, and UCI # 2 carries HARQ # 2. .
  • network devices such as network device # 1 102
  • PUSCH The PUSCH scheduled by the network device # 1 for the terminal device 101 may overlap with the above-mentioned PUCCH # 1 and / or PUCCH # 2.
  • the resource occupied by the PUSCH scheduled by the network device # 1 for the terminal device and PUCCH # 1 overlap on one or more symbols
  • / or the resource occupied by the PUSCH scheduled by the network device # 1 for the terminal device and the PUCCH # 2 overlap on one or more symbols.
  • the terminal device 101 may send part or all of the information in the UCI to the network device through the PUSCH. Specifically, when there is a resource overlap between PUCCH and PUSCH, the terminal device can transmit HARQ, semi-persistent CSI, and periodic CSI in UCI through the PUSCH.
  • the terminal device may still send both UCI # 1 and UCI # 2 to the network device # 1 through the PUSCH.
  • the network device # 1 may not know that the terminal device will send UCI # 2 through the PUSCH, so it may be considered that the UCI sent by the terminal device through the PUSCH includes only UCI # 1.
  • the PUSCH includes only UCI # 1, it is on the PUSCH.
  • the received signal is demodulated and decoded. Therefore, the terminal device and the network device # 1 do not understand the specific content of the information transmitted on the PUSCH, and the processing performed is also inconsistent.
  • the network device may not be able to resolve the specific content in UCI # 1.
  • the network device # 2 does not know that the resources of PUCCH # 2 and the PUSCH overlap, and may still receive UCI # 2 on the resources of PUCCH # 2, so it cannot obtain UCI # 2. Therefore, network device # 1 may retransmit PDSCH # 1, and network device # 2 may also retransmit PDSCH # 2, which results in a waste of transmission resources, and also causes a delay in data transmission and a poor user experience.
  • this application provides a configuration method so that a terminal device can understand the association relationship between the resources of the PUCCH and the PDCCH configuration in a multi-DCI scheduling scenario.
  • This application also provides a method for sending and receiving UCI, so that a terminal device can determine which UCI can be transmitted through a scheduled PUSCH in a multi-DCI scheduling scenario, and a network device can also receive UCI on corresponding resources, which can avoid network devices Inconsistent with the resources determined by the terminal device. A situation where the network device cannot receive the UCI. Therefore, network devices can make reasonable decisions based on UCI, avoid unnecessary retransmissions, reduce waste of transmission resources, reduce data transmission delays, and improve user experience.
  • the high-level parameters may be transmitted through high-level signaling.
  • the high-level signaling may be, for example, a radio resource control (RRC) message, or may be other high-level signaling, which is not limited in this application.
  • RRC radio resource control
  • "for indication” may include direct indication and indirect indication, and may also include explicit indication and implicit indication.
  • the information indicated by certain information is referred to as to-be-instructed information.
  • there are many ways to instruct the instruction information for example, but not limited to, direct indication of Information, such as the information to be indicated or an index of the information to be indicated.
  • the information to be indicated may also be indicated indirectly by indicating other information, where there is an association relationship between the other information and the information to be indicated. It is also possible to indicate only a part of the information to be indicated, while other parts of the information to be indicated are known or agreed in advance.
  • an indication of specific information may also be implemented by means of an arrangement order of each piece of information agreed in advance (such as stipulated in a protocol), thereby reducing the indication overhead to a certain extent.
  • the association between A and B when A and B are described as being associated with or related to each other, it may indicate that there is an association relationship between A and B. Therefore, "the association between A and B" and “there is an association between A and B” can express the same meaning, or are replaceable.
  • the associated PUCCH configuration and PDCCH configuration may indicate that there is an association relationship between the PUCCH configuration and the PDCCH configuration.
  • the association between the CSI reporting configuration and the PDCCH configuration may indicate that there is an association relationship between the CSI reporting configuration and the PDCCH configuration. For the sake of brevity, we will not explain them one by one here.
  • the first, second, third, fourth, and various numerical numbers are only distinguished for convenience of description, and are not used to limit the scope of the embodiments of the present application. For example, different instruction information is distinguished.
  • pre-acquisition may include indication or pre-definition by network device signaling, for example, protocol definition.
  • pre-defined can be achieved by pre-saving corresponding codes, forms, or other methods that can be used to indicate related information in devices (for example, terminal devices and network devices), and this application does not make specific implementations thereof. limited.
  • saving involved in the embodiments of the present application may refer to saving in one or more memories.
  • the one or more memories may be provided separately or integrated in an encoder or a decoder, a processor, or a communication device.
  • the one or more memories may also be partly provided separately and partly integrated in a decoder, a processor, or a communication device.
  • the type of the memory may be any form of storage medium, which is not limited in this application.
  • the "protocol” involved in the embodiment of the present application may refer to a standard protocol in the communication field, for example, may include an LTE protocol, an NR protocol, and a related protocol applied in a future communication system, which is not limited in this application.
  • At least one means one or more, and “multiple” means two or more.
  • “And / or” describes the association relationship of related objects, and indicates that there can be three kinds of relationships, for example, A and / or B can represent: the case where A exists alone, A and B exist simultaneously, and B alone exists, where A, B can be singular or plural.
  • the character “/” generally indicates that the related objects are an "or” relationship.
  • “At least one or more of the following” or similar expressions refers to any combination of these items, including any combination of single or plural items.
  • At least one (a), a, b, or c may represent: a, or b, or c, or a and b, or a and c, or b and c, or a, b, and c, where a, b, and c may be single or multiple.
  • the method provided in this application may be applicable to a wireless communication system.
  • the terminal device in the embodiment of the present application may communicate with one or more network devices at the same time.
  • the network device in the embodiment of the present application may correspond to any of the network device # 1 and the network device # 3 in FIG.
  • the terminal device in the embodiment of the present application may correspond to the terminal device 101 in FIG. 1.
  • any network device in the wireless communication system that serves the same terminal device can be a terminal device based on the configuration method provided in this application.
  • Configuration parameters In the following, without loss of generality, the configuration method provided in the embodiment of the present application will be described in detail by taking an interaction process between a terminal device and a network device as an example.
  • the multiple network devices may send configuration information to the terminal device, or a certain network device may send configuration information to the terminal device. This is not limited.
  • FIG. 2 is a schematic flowchart of a configuration method 200 provided by an embodiment of the present application from the perspective of device interaction. As shown, the method 200 may include steps 210 to 230. Each step in the method 200 is described in detail below.
  • step 210 the network device generates first configuration information, where the first configuration information may be used to indicate associated PUCCH configuration and PDCCH configuration parameters.
  • the PDCCH configuration parameter may include a PDCCH configuration in a high-level parameter and a downlink control parameter of the PDCCH.
  • the PUCCH configuration can be used to determine the resources of the PUCCH, and the PDCCH configuration can be used to determine the search space of the PDCCH.
  • the associated PUCCH configuration and PDCCH configuration parameters may refer to that the PUCCH configuration and PDCCH configuration parameters may be configured based on the same network device. In other words, the associated PUCCH configuration and PDCCH configuration parameters may correspond to the same network device.
  • a terminal device can receive multiple PUCCH configurations, and each PUCCH configuration can correspond to a network device.
  • the resources determined based on the PUCCH configuration can be used to transmit the PUCCH to the network device, and information transmitted on the resources determined based on the PUCCH configuration can also be sent to the network device. information.
  • the network device may determine a resource based on the same PUCCH configuration, and receive the PUCCH on the resource.
  • the resources used to transmit the PUCCH determined by the PUCCH configuration may be referred to as PUCCH resources.
  • the information transmitted on the PUCCH can be, for example, HARQ information fed back to the PDSCH scheduled by the network device through the PDCCH, or multiple CSIs fed back to the network device. Or, it may also be HARQ information and one or more CSIs fed back to the PDSCH scheduled by the network device through the PDCCH, or it may also be HARQ information (for example, the PDSCH scheduled by the network device through the PDCCH and the PDSCH without the corresponding PDCCH, (Such as SPS PDSCH) and multiple CSI.
  • the network device from which the PDCCH received (or blindly detected) based on the PDCCH configuration parameter and the network device to which the PUCCH is sent may be the same network device.
  • the PDCCH may be a PDCCH for scheduling the PDSCH.
  • the network device used to send the first configuration information may be a network device corresponding to the above-mentioned PUCCH configuration or PDCCH configuration, or may be another network device, which is not limited in this application.
  • the terminal device may receive the PDCCH from the network device based on the PDCCH configuration.
  • a network device can schedule a PDSCH for a terminal device through the PDCCH, and the terminal device can determine a resource for transmitting the PUCCH for UCI from the PUCCH configuration associated with the PDCCH configuration based on the PUCCH resource indicator in the PDCCH, and then use the PUCCH resource Transmit UCI, the network device can receive UCI on the resources of this PUCCH.
  • the terminal device does not know the association relationship between the PUCCH configuration and the PDCCH configuration, when receiving the PDCCH, it may not know which PUCCH configuration should be used to determine the resources of the PUCCH for transmitting UCI. Therefore, the resources determined by the terminal device for transmitting the PUCCH of the UCI and the resources determined by the network device for receiving the PUCCH of the UCI may be different.
  • the network device cannot receive feedback on the scheduled PDSCH, which may cause the network device to make a wrong decision. For example, when the terminal device successfully receives and decodes the data successfully because the UCI is not received, the transmission resources are wasted, the data transmission delay is also caused, and the user experience is affected.
  • the network device can help the terminal device determine which PUCCH configuration and which PDCCH configuration can correspond to the same network device by configuring the association relationship between the PUCCH configuration and the PDCCH configuration.
  • the network device may indicate the associated PUCCH configuration and PDCCH configuration to the terminal device by any of the following methods:
  • Method 1 Add an indication field to the PUCCH configuration to indicate the associated PDCCH configuration
  • Method 2 Add an indication field to the PDCCH configuration to indicate the associated PUCCH configuration
  • Method 3 Configure the associated PUCCH configuration and PDCCH configuration in the serving cell configuration.
  • the network device may add a field to the PUCCH configuration to indicate the associated PDCCH configuration.
  • the PUCCH configuration may be configured through a high-level parameter PUCCH-ConfigIE, and the network device may add a PDCCH-ConfigID field to the PUCCH-ConfigIE to indicate the associated PDCCH configuration.
  • the first configuration information may be a PUCCH configuration, such as PUCCH-ConfigIE or other signaling that can be used to implement the same or similar functions of the PUCCH configuration.
  • the indication of the PDCCH configuration may be, for example, an identifier of the PDCCH configuration, such as PDCCH configuration 0 and PDCCH configuration 1, or other information that may be used to indicate the PDCCH configuration.
  • the specific form of the PDCCH configuration indication is not limited in this application.
  • the network device may add a field to the PDCCH configuration to indicate the associated PUCCH configuration.
  • the PDCCH configuration may be configured through a high-level parameter PDCCH-ConfigIE, and the network device may add a PUCCH-ConfigID field to the PDCCH-ConfigIE to indicate the associated PUCCH configuration.
  • the first configuration information may be a PDCCH configuration, such as PDCCH-ConfigIE or other signaling that can be used to implement the same or similar functions of the PDCCH configuration.
  • the indication of the PUCCH configuration may be, for example, an identifier of the PUCCH configuration, or other information that may be used to indicate the PUCCH configuration.
  • the specific form of the indication of the PUCCH configuration is not limited in this application.
  • the network device may indicate the associated PUCCH configuration and PDDCH configuration through the serving cell configuration.
  • the first configuration information may be configured for a serving cell.
  • the serving cell configuration may be the servingCellConfig in the NR protocol.
  • the serving cell configuration may include one or more groups of BWP uplink parameters and one or more groups of BWP downlink parameters.
  • Each set of BWP uplink parameters may be configured for one BWP, for example, the BWP ID may be indicated in the BWP downlink parameters.
  • Each group of BWP uplink parameters may also be configured for one BWP, for example, the BWP ID may be indicated in the BWP downlink parameters.
  • Each group of BWP uplink parameters may include one or more groups of BWP uplink dedicated parameters, and each group of BWP uplink dedicated parameters may include a PUCCH configuration.
  • Each group of BWP downlink parameters may include one or more groups of BWP downlink dedicated parameters, and each group of BWP downlink dedicated parameters may include a PDCCH configuration.
  • the PUCCH configuration and the PDCCH configuration may be configured for the same BWP, and the identifier of the BWP uplink dedicated parameter to which the PUCCH configuration belongs may be related to the BWP downlink dedicated parameter to which the PDCCH configuration belongs The identity is the same.
  • the ID of the BWP indicated in the BWP uplink parameter to which the PUCCH configuration belongs may be the same as the ID of the BWP indicated in the BWP downlink parameter to which the PDCCH configuration belongs.
  • the BWP uplink parameters configured for a certain BWP in the serving cell configuration may include BWP uplink dedicated parameters 0, BWP uplink dedicated parameters 1, and the BWP downlink parameters configured for the same BWP may include BWP downlink dedicated parameters 0, BWP downlink dedicated parameters 1 .
  • the PUCCH configuration in the BWP uplink dedicated parameter 0 may be associated with the PDCCH configuration in the BWP downlink dedicated parameter 0;
  • the PUCCH configuration in the BWP uplink dedicated parameter 1 may be associated with the PDCCH configuration in the BWP downlink dedicated parameter 1.
  • a BWP configuration parameter configured by a serving cell for a certain BWP configuration may include a group of BWP uplink dedicated parameters, and a BWP downlink parameter configured for the same BWP may include a group of BWP downlink dedicated parameters, then the serving cell configuration is the same
  • the PUCCH configuration of the BWP configuration may be associated with the PDCCH configuration.
  • the serving cell since the serving cell is configured with the same BWP configured with uplink parameters including a set of BWP uplink dedicated parameters, and the downlink parameters configured for the same BWP include a set of BWP downlink dedicated parameters, it can be distinguished without identification.
  • the PUCCH configuration in the BWP uplink dedicated parameters configured with the same BWP configuration and the PDCCH configuration in the BWP downlink dedicated parameters are associated with the serving cell, which can be considered as the identifier of the BWP uplink dedicated parameter to which the PUCCH configuration belongs and the BWP downlink dedicated to the PDCCH configuration A special case of the same parameter identification.
  • the serving cell configuration may include one or more groups of BWP uplink parameters and one or more groups of BWP downlink parameters.
  • Each group of BWP uplink parameters may include one or more groups of BWP uplink dedicated parameters
  • each group of BWP downlink parameters may include one or more groups of BWP downlink dedicated parameters.
  • Each group of BWP uplink dedicated parameters may include one or more PUCCH configurations.
  • Each group of BWP downlink dedicated parameters may include one or more PDCCH configurations.
  • the identifier of the BWP uplink dedicated parameter to which the PUCCH configuration belongs may be the identifier of the BWP downlink dedicated parameter to which the PDCCH configuration belongs.
  • the identifier of the PUCCH configuration may be the same as the identifier of the PDCCH configuration.
  • the ID of the BWP indicated in the BWP uplink parameter to which the PUCCH configuration belongs may be the same as the ID of the BWP indicated in the BWP downlink parameter to which the PDCCH configuration belongs.
  • the BWP uplink parameters configured for a certain BWP in the serving cell configuration may include BWP uplink dedicated parameters 0, BWP uplink dedicated parameters 1, and the BWP downlink parameters configured for the same BWP may include BWP downlink dedicated parameters 0, BWP downlink dedicated parameters 1 .
  • the BWP uplink dedicated parameter 0 may include PUCCH configuration 0 and PUCCH configuration 1.
  • the BWP uplink dedicated parameter 1 may include PUCCH configuration 0 and PUCCH configuration 1.
  • the BWP downlink dedicated parameter 0 may include PDCCH configuration 0 and PDCCH configuration 1.
  • the BWP downlink dedicated parameter 1 may include PDCCH configuration 0 and PDCCH configuration 1.
  • PUCCH configuration 0 in the BWP uplink dedicated parameter 0 may be associated with PDCCH configuration 0 in the BWP downlink dedicated parameter 0;
  • PUCCH configuration 1 in the BWP uplink dedicated parameter 0 may be associated with PDCCH configuration 1 in the BWP downlink dedicated parameter 0;
  • PUCCH configuration 0 in BWP uplink dedicated parameter 1 may be associated with PDCCH configuration 0 in BWP downlink dedicated parameter 1;
  • PUCCH configuration 1 in BWP uplink dedicated parameter 1 may be associated with PDCCH configuration 1 in BWP downlink dedicated parameter 1.
  • the BWP uplink parameters configured for a certain BWP in the serving cell configuration may include a set of BWP uplink dedicated parameters
  • the BWP downlink parameters configured for the same BWP may include a set of BWP downlink dedicated parameters.
  • the BWP uplink dedicated parameters may include PUCCH configuration 0 and PUCCH configuration 1 and the BWP downlink dedicated parameters may include PDCCH configuration 0 and PDCCH configuration 1.
  • PUCCH configuration 0 may be associated with PDCCH configuration 0
  • PUCCH configuration 1 may be associated with PDCCH configuration 1.
  • the parameters configured for the same BWP in the serving cell configuration include a set of BWP uplink dedicated parameters and a set of BWP downlink dedicated parameters, they can be distinguished without identification.
  • the PDCCH configuration in the BWP uplink dedicated parameters configured with the same BWP configuration is associated with the PDCCH configuration with the same identifier in the BWP downlink dedicated parameters, which can be considered as the identifier of the BWP uplink dedicated parameter to which the PUCCH configuration belongs and the BWP downlink to which the PDCCH configuration belongs
  • the configurations in the serving cell configuration may be associated. Then, when the PUCCH configuration and the PDCCH configuration belong to the same serving cell configuration, the PUCCH configuration and the PDCCH configuration may be associated.
  • the first configuration information may also be a mapping relationship, such as a mapping relationship table, or other information that may be used to indicate the mapping relationship.
  • the mapping relationship may be used to indicate the corresponding PUCCH configuration and PDCCH configuration, and the corresponding PUCCH configuration and PDCCH configuration may have an association relationship.
  • the identifiers of the BWP uplink dedicated parameters, the BWP downlink dedicated parameters, the PUCCH configuration identifier, and the PDCCH configuration identifier are exemplarily given, but this should not constitute any limitation on this application. .
  • the manner of allocating an identifier for the configuration of the multiple sets of dedicated parameters included in each set of parameters is also not limited.
  • the identification of the configuration of each group of dedicated parameters may be local or global.
  • the serving cell configuration may also include other configuration parameters other than those listed above, which is not limited in this application.
  • the network device may indicate the associated PUCCH configuration and downlink control parameters of the PDCCH to the terminal device in any of the following ways:
  • Method 1 Add an indication field to the PUCCH configuration to indicate the associated DMRS port group (DMRS port group) or DMRS code division multiplexing (CDM) group (DMRS CDM group); or
  • Manner 2 Add an indication field to the PUCCH configuration to indicate the associated TB or codeword (codeword, CW).
  • the downlink control parameter may be a PDCCH-related parameter included in the DCI, or a parameter related to the parameter in the DCI.
  • the PDCCH-related parameter indicated in the DCI may be an antenna port used for uplink transmission or downlink transmission.
  • the parameters related to the antenna port may be a demodulation reference signal (DMRS) port, a DMRS group, or a DMRS CDM group.
  • the terminal device may determine the DMRS port based on the antenna port indicated in the DCI, and then determine the DMRS port group or DMRS CDM group to which it belongs.
  • the terminal device may also determine the DMRS port group or DMRS CDM group to which it belongs according to the DMRS port.
  • DMRS port groups and DMRS CDM groups can be understood as being obtained by grouping DMRS ports based on different methods.
  • Antenna ports, DMRS ports, DMRS ports, and DMRS groups can be distinguished by indexes or by identifiers, or by other information that can be used to distinguish different ports or different groups, which is not limited in this application. .
  • the PDCCH-related parameter indicated in the DCI is a parameter related to a transport block (TB).
  • the parameters related to TB may include, for example, MCS for configuring modulation order and code rate, NDI for indicating new transmission or retransmission, and RV for indicating.
  • the network device may add a field to the PUCCH configuration to indicate the associated DMRS port group or DMRS CDM group.
  • PUCCH configuration can be configured through high-level parameters PUCCH-Config and IE.
  • Network devices can add a DMRS port ID field in PUCCH-Config to indicate the associated DMRS port group; or, add DMRS to PUCCH-Config CDM group ID field to indicate the associated DMRS CDM group.
  • the first configuration information may be a PUCCH configuration, for example, PUCCH-ConfigIE or other signaling that can be used to implement the same or similar functions as the PUCCH configuration.
  • a terminal device When a terminal device receives a PDCCH for scheduling a PUSCH or PDSCH, it can determine its association based on the downlink control parameters of the PDCCH, such as the correspondence between the antenna port and the DMRS port, DMRS port group, or DMRS group indicated by the DCI. PUCCH configuration.
  • association field in PUCCH configuration 0 when the association field in PUCCH configuration 0 is 0, it is assumed that it can be associated with DMRS port 0; when the association field in PUCCH configuration 1 is 1, it is assumed that it can be associated with DMRS port 1.
  • the PUCCH configuration 1 is associated with the PDCCH.
  • the network device may add a field to the PUCCH configuration to indicate the associated TB or CW.
  • the PUCCH configuration may be configured through the high-level parameter PUCCH-Config, ie, the network device may add a field for indicating a TB or CW in the PUCCH-Config, to indicate the associated TB or CW.
  • the first configuration information may be a PUCCH configuration, for example, PUCCH-ConfigIE or other signaling that can be used to implement the same or similar functions as the PUCCH configuration.
  • DCI format 1_1 As an example, in DCI format 1_1, there will be 2 TB configuration information, such as TB1 and TB2.
  • the parameters corresponding to each TB may include MCS, NDI, and RV.
  • DCI format1_1 supports enabling one TB. Therefore, the network device can enable one TB in the DCI and disable another TB.
  • association field in PUCCH configuration 0 when the association field in PUCCH configuration 0 is 0, it is assumed that it can be associated with TB1; when the association field in PUCCH configuration 1 is 1, it is assumed that it can be associated with TB2.
  • the PUCCH configuration may indicate the associated TB or the associated CW.
  • the terminal device can determine the other associated with the PUCCH configuration.
  • step 220 the network device sends the first configuration information. Accordingly, in step 220, the terminal device receives the first configuration information.
  • the first configuration information may be carried in high-level signaling.
  • the high-level signaling may be, for example, an RRC message.
  • the first configuration information may be sent to each terminal device through different signaling.
  • the terminal device communicates with multiple network devices, it may also receive first configuration information from multiple network devices.
  • step 230 the terminal device determines the associated PUCCH configuration and PDCCH configuration according to the first configuration information.
  • the terminal device When the terminal device receives the first configuration information from one or more network devices, it may determine the associated PUCCH configuration and PDCCH configuration based on the manner described in step 220 above.
  • the network device can generate the first configuration information based on the method defined by the protocol, and the terminal device can parse the first configuration information based on the method defined by the protocol.
  • the terminal device can determine which PDCCH configuration and PUCCH configuration correspond to the same network device based on the association relationship between the PUCCH configuration and the PDCCH configuration, so that the PUCCH resources can be determined to transmit UCI according to the instructions of the network device.
  • the network device can also receive UCI on the corresponding resources, which will not cause the network device to fail to receive UCI due to inconsistent resources determined by both parties. Therefore, by introducing the first configuration information described above, communication between the terminal device and the network device can be facilitated, which is beneficial to improving transmission performance and user experience.
  • the terminal device needs to report CSI to the network device, such as periodic CSI or semi-persistent CSI.
  • the terminal device can determine the PUCCH for reporting CSI according to the CSI reporting configuration.
  • the terminal device may receive multiple CSI reporting configurations.
  • the terminal device and the network device may determine the PUCCH based on different CSI report configurations. As a result, it is determined that the resources of the PUCCH may be different, and the network device cannot successfully receive the CSI. Therefore, this application provides another configuration method, which can be used to configure the association relationship between the CSI report configuration and the PDCCH.
  • FIG. 3 is a schematic flowchart of a configuration method 300 according to an embodiment of the present application, which is shown from the perspective of device interaction. As shown, the method 300 may include steps 310 to 330. Each step in the method 300 is described in detail below.
  • step 310 the network device generates second configuration information, which can be used to indicate the associated CSI reporting configuration and PDCCH configuration parameters.
  • the PDCCH configuration parameter may include a PDCCH configuration in a high-level parameter and a downlink control parameter of the PDCCH.
  • the CSI reporting configuration can be used to determine the PUCCH resource
  • the PDCCH configuration can be used to determine the PDCCH search space.
  • the associated CSI report configuration and PDCCH configuration parameters may refer to that the CSI report configuration and PDCCH configuration parameters may be configured based on the same network device. In other words, the associated CSI reporting configuration and PDCCH configuration parameters may correspond to the same network device.
  • a terminal device may receive multiple CSI measurement configurations, and each CSI measurement configuration may correspond to a network device. Since each CSI measurement configuration may include one or more CSI reporting configurations, in the embodiments of the present application, the CSI reporting configuration may be associated with the PDCCH configuration, or the CSI measurement configuration to which the CSI reporting configuration belongs may be associated with the PDCCH configuration. When a CSI measurement configuration is associated with a PDCCH configuration, one or more CSI reporting configurations in the CSI measurement configuration may be associated with the PDCCH configuration.
  • the resources determined based on the CSI report configuration can be used to transmit PUCCH to the network device, and information transmitted on the resources determined based on the CSI report configuration can also be sent to the network device.
  • the network device may determine a resource based on the same CSI reporting configuration, and receive a PUCCH on the resource.
  • the resources used for transmitting the PUCCH determined by the CSI reporting configuration may be referred to as PUCCH resources.
  • the information transmitted on the PUCCH can be, for example, a CSI fed back to the network device, or it can be fed back to a PDSCH (eg, SPS PDSCH) without a corresponding PDCCH.
  • a PDSCH eg, SPS PDSCH
  • HARQ information and a CSI feedback to the network device can be, for example, a CSI fed back to the network device, or it can be fed back to a PDSCH (eg, SPS PDSCH) without a corresponding PDCCH.
  • the network device from which the PDCCH received (or blindly detected) based on the PDCCH configuration parameter and the network device to which the PUCCH is sent may be the same network device.
  • the network device used to send the second configuration information may be a network device corresponding to the above CSI reporting configuration or PDCCH configuration, or may be another network device, which is not limited in this application.
  • the terminal device may receive the PDCCH from the network device based on the PDCCH configuration.
  • the network device may activate semi-persistent CSI reporting of the terminal device through the PDCCH.
  • the terminal device may determine the resource of the PUCCH for transmitting UCI based on the CSI report configuration associated with the PDCCH configuration, and then send the UCI on the resource of the PUCCH, and the network device may receive the UCI on the resource of the PUCCH.
  • the terminal device determines The resources of the PUCCH used to transmit UCI may be different from the resources determined by the network device to receive the PUCCH of the UCI.
  • the network device cannot receive the CSI reported by the terminal device, and thus cannot obtain the accurate channel state, which may cause the modulation used.
  • the coding method (modulation coding scheme, MCS) is inappropriate, or the precoding matrix (precoding matrix) does not adapt to the channel state, resulting in a decrease in data transmission performance.
  • the network device can help the terminal device determine which CSI reporting configuration and which PDCCH configuration can correspond to the same network device by configuring the association relationship between the CSI reporting configuration and the PDCCH configuration. Specifically, the network device indicates the associated CSI report configuration and PDCCH configuration to the terminal device by any of the following methods:
  • Method 1 Add an indication field to the CSI report configuration to indicate the associated PDCCH configuration /;
  • Method 2 Add an indication field to the CSI measurement configuration to which the CSI report configuration belongs to indicate the associated PDCCH configuration;
  • Method 3 Add an indication field to the PDCCH configuration to indicate the associated CSI reporting configuration
  • Method 4 Add an indication field to the PDCCH configuration to indicate the associated CSI measurement configuration
  • Method 5 Indicate the associated CSI reporting configuration and PDCCH configuration in the serving cell configuration.
  • the network device may add an indication field to the CSI report configuration to indicate the associated PDCCH configuration.
  • the CSI reporting configuration may be configured through a high-level parameter CSI-ReportConfigIE, and the network device may add a PDCCH-ConfigID field to the CSI-ReportConfigIE to indicate an indication of the associated PDCCH configuration.
  • the second configuration information may be a CSI report configuration, such as CSI-ReportConfigIE or other signaling that can be used to implement the same or similar functions as the CSI report configuration.
  • the network device may add an indication field to the CSI measurement configuration to indicate the associated PDCCH configuration.
  • the CSI measurement configuration may be configured through a high-level parameter CSI-MeasConfigIE, and the network device may add a PDCCH-ConfigID field to the CSI-MeasConfigIE to indicate the identity of the associated PDCCH configuration.
  • the second configuration information may be a CSI measurement configuration, such as CSI-MeasConfigIE or other signaling that can be used to implement the same or similar functions of the CSI measurement configuration.
  • the indication of the PDCCH configuration may be, for example, an identifier of the PDCCH configuration, or other information that may be used to indicate the PDCCH configuration.
  • the specific form of the PDCCH configuration indication is not limited in this application.
  • each CSI measurement configuration may include one or more CSI reporting configurations
  • the network device configures the association relationship between the CSI measurement configuration and the PDCCH configuration through the second configuration information, that is, the second method
  • the CSI measurement configuration One or more of the CSI reporting configurations may be associated with the same PDCCH configuration; if the network device configures the association relationship between the CSI reporting configuration and the PDCCH configuration through the second configuration information, that is, mode 1, each CSI reporting under the same CSI measurement configuration
  • the associated PDCCH configuration may be the same or different, which is not limited in this application.
  • the network device may add a field to the PDCCH configuration to indicate the associated CSI reporting configuration.
  • the PDCCH configuration may be configured through a high-level parameter PDCCH-ConfigIE, and a network device may add a CSI-ReportConfigID field to the PDCCH-ConfigIE to indicate an indication of the associated CSI reporting configuration.
  • the second configuration information may be a PDCCH configuration, such as PDCCH-ConfigIE or other signaling that can be used to implement the same or similar functions of the PDCCH configuration.
  • the indication of the CSI report configuration may be, for example, an identifier of the CSI report configuration, or other information that may be used to indicate the CSI report configuration. This application does not limit the specific form of the CSI report configuration indication.
  • the PDCCH configuration associated with each CSI reporting configuration under the same CSI measurement configuration may be the same. It can also be different, which is not limited in this application.
  • the network device may add a field to the PDCCH configuration to indicate the associated CSI measurement configuration.
  • the PDCCH configuration may be configured through a high-level parameter PDCCH-Config, and a network device may add a CSI-MeasConfigID field to the PDCCH-ConfigIE to indicate an indication of an associated CSI measurement configuration.
  • the second configuration information may be a PDCCH configuration, such as PDCCH-ConfigIE or other signaling that can be used to implement the same or similar functions of the PDCCH configuration.
  • the indication of the CSI measurement configuration may be, for example, an identifier of the CSI measurement configuration, or other information that may be used to indicate the CSI measurement configuration.
  • the specific form of the indication of the CSI measurement configuration is not limited in this application.
  • the network device configures the association relationship between the CSI measurement configuration and the PDCCH configuration through the second configuration information, one or more CSI reporting configurations in the CSI measurement configuration may be associated with the same PDCCH configuration. .
  • the network device may indicate the associated CSI reporting configuration and PDDCH configuration through the serving cell configuration.
  • the second configuration information may be a serving cell configuration, such as ServingCellConfig, or other signaling that may be used to implement the same or similar function of the serving cell configuration.
  • the serving cell configuration may include one or more CSI measurement configurations and one or more sets of BWP downlink parameters.
  • Each CSI measurement configuration includes one or more CSI reporting configurations.
  • Each group of BWP downlink parameters may include one or more groups of BWP downlink dedicated parameters, and each group of BWP downlink dedicated parameters may include one or more PDCCH configurations.
  • the identifier of the CSI measurement configuration to which the CSI reporting configuration belongs may be the same as the identifier of the BWP downlink dedicated parameter to which the PDCCH configuration belongs.
  • each group of BWP downlink parameters includes one or more groups of BWP downlink dedicated parameters.
  • the identifiers of the BWP downlink dedicated parameters in the downlink parameters are locally configured, so there may be BWP downlink dedicated parameters with the same identifier in multiple sets of BWP downlink parameters. That is, each CSI reporting configuration in the CSI measurement configuration may be associated with one or more PDCCH configurations.
  • the BWP downlink parameters configured for each BWP in the serving cell configuration may include BWP downlink dedicated parameter 0 and BWP downlink dedicated parameter 1, respectively, and the serving cell configuration may further include CSI measurement configuration 0 and CSI measurement configuration 1.
  • the PDCCH configuration in the BWP downlink dedicated parameter 0 of the BWP downlink parameters configured for each BWP can be associated with the CSI measurement configuration in the CSI measurement configuration 0, and the BWP downlink dedicated parameter 1 in the BWP downlink parameters configured for each BWP
  • the PDCCH configuration can be associated with the CSI measurement configuration in CSI measurement configuration 1.
  • the BWP downlink parameters configured for each BWP in the serving cell configuration may include a set of BWP downlink dedicated parameters, and the serving cell configuration may also include a CSI measurement configuration, and the BWP downlink dedicated among the BWP downlink parameters configured for each BWP may be dedicated.
  • the PDCCH configuration in the parameters can be associated with the CSI measurement configuration.
  • the PDCCH configuration in the BWP downlink dedicated parameters in the BWP downlink parameters configured for each BWP is associated with the CSI measurement configuration, and can be considered as a special case where the identifier of the BWP downlink dedicated parameter to which the PDCCH belongs is the same as the identifier of the CSI measurement configuration.
  • the serving cell configuration includes one or more groups of BWP-specific parameters.
  • Each group of BWP-specific parameters may be a parameter configured for one BWP, or each group of BWP-specific parameters corresponds to one BWP.
  • Each group of BWP-specific parameters may include an associated PDCCH configuration and a CSI reporting configuration.
  • each group of BWP dedicated parameters may include a group of BWP uplink dedicated parameters, a group of BWP downlink dedicated parameters, and a CSI measurement configuration.
  • Each group of BWP downlink dedicated parameters may include a PDCCH configuration, and each CSI measurement configuration may include one or more CSI reporting configurations.
  • the PDCCH configuration in the same set of BWP-specific parameters may be associated with the CSI measurement configuration, that is, the PDCCH configuration in the same set of BWP-specific parameters is associated with one or more CSI reporting configurations in the CSI measurement configuration.
  • the BWP uplink parameters configured for each BWP in the serving cell configuration may include one or more groups of BWP uplink dedicated parameters, and the BWP downlink parameters configured for each BWP in the serving cell configuration may include a Group or groups of BWP downlink specific parameters.
  • Each group of BWP uplink dedicated parameters may include a CSI measurement configuration, and each group of BWP downlink dedicated parameters may include a PDCCH configuration.
  • the CSI reporting configuration and the PDCCH configuration may be coordinated with the same BWP, and the CSI measurement configuration to which the CSI reporting configuration belongs belongs to the BWP uplink dedicated parameter identifier and the PDCCH.
  • the identifiers of the BWP downlink dedicated parameters to which the configuration belongs are the same.
  • the ID of the BWP indicated in the BWP uplink parameter to which the CSI report configuration belongs may be the same as the ID of the BWP indicated in the BWP downlink parameter to which the PDCCH configuration belongs.
  • the BWP downlink parameters configured for a certain BWP in the serving cell configuration may include BWP downlink dedicated parameters 0, BWP downlink dedicated parameters 1, and the BWP uplink parameters configured for the same BWP may include BWP uplink dedicated parameters 0, BWP uplink dedicated parameters 1 .
  • the PDCCH configuration in the BWP downlink dedicated parameter 0 may be associated with the CSI measurement configuration in the BWP uplink dedicated parameter 0, and the PDCCH configuration in the BWP downlink dedicated parameter 1 may be associated with the CSI measurement configuration in the BWP uplink dedicated parameter 1.
  • the BWP uplink parameters that can be configured for a certain BWP in the serving cell configuration may include a set of BWP uplink dedicated parameters
  • the BWP downlink parameters configured for the same BWP may include a set of BWP downlink dedicated parameters.
  • the PDCCH configuration in the BWP downlink dedicated parameter is associated with the CSI measurement configuration in the BWP uplink dedicated parameter.
  • the parameters configured for the same BWP in the serving cell configuration include a set of BWP uplink dedicated parameters and a set of BWP downlink dedicated parameters, they can be distinguished without identification.
  • the PDCCH configuration in the BWP downlink dedicated parameters configured by the serving cell for the same BWP is associated with the CSI measurement configuration in the BWP uplink dedicated parameters, which can be considered as the identifier of the BWP downlink dedicated parameters to which the PDCCH belongs and the BWP uplink dedicated parameters to which the CSI measurement configuration belongs A special case of the same identification.
  • the BWP uplink parameters configured by the serving cell for a certain BWP may include one or more groups of BWP uplink dedicated parameters, and the BWP downlink parameters configured for the same BWP may include one or more groups of BWP Downlink-specific parameters.
  • Each group of BWP uplink dedicated parameters may include one or more CSI measurement configurations, and each group of BWP downlink dedicated parameters may include one or more PDCCH configurations.
  • the CSI report configuration and the PDCCH configuration may be configured for the same BWP.
  • the identifiers of the BWP downlink dedicated parameters are the same, and the identifier of the CSI measurement configuration is the same as the identifier of the PDCCH configuration.
  • the ID of the BWP indicated in the BWP uplink parameter to which the CSI report configuration belongs may be the same as the ID of the BWP indicated in the BWP downlink parameter to which the PDCCH configuration belongs.
  • the BWP downlink parameters configured for a certain BWP in the serving cell configuration may include BWP downlink dedicated parameters 0 and BWP downlink dedicated parameters 1, and the BWP uplink parameters configured for the same BWP may include BWP uplink dedicated parameters 0 and BWP uplink dedicated parameters 1.
  • the BWP uplink dedicated parameter 0 may include CSI measurement configuration 0 and CSI measurement configuration 1.
  • the BWP uplink dedicated parameter 1 may include CSI measurement configuration 0 and CSI measurement configuration 1.
  • the BWP downlink dedicated parameter 0 may include PDCCH configuration 0 and PDCCH configuration 1.
  • the BWP downlink dedicated parameter 1 may include PDCCH configuration 0 and PDCCH configuration 1.
  • CSI measurement configuration 0 in the BWP uplink dedicated parameter 0 is associated with PDCCH configuration 0 in the BWP downlink dedicated parameter 0;
  • CSI measurement configuration 1 in the BWP uplink dedicated parameter 0 is associated with PDCCH configuration 1 in the BWP downlink dedicated parameter 0;
  • CSI measurement configuration 0 in the BWP uplink dedicated parameter 1 is associated with PDCCH configuration 0 in the BWP downlink dedicated parameter 1;
  • CSI measurement configuration 1 in the BWP uplink dedicated parameter 1 is associated with PDCCH configuration 1 in the BWP downlink dedicated parameter 1.
  • the BWP downlink parameters configured for a certain BWP in the serving cell configuration may include a set of BWP uplink dedicated parameters
  • the BWP uplink parameters configured for the same BWP may include a set of BWP downlink dedicated parameters.
  • the BWP uplink dedicated parameters may include CSI measurement configuration 0 and CSI measurement configuration 1
  • the BWP downlink dedicated parameters may include PDCCH configuration 0 and PDCCH configuration 1. Then, CSI measurement configuration 0 is associated with PDCCH configuration 0; CSI measurement configuration 1 is associated with PDCCH configuration 1.
  • the BWP downlink parameters configured for a certain BWP in the serving cell configuration may include one or more groups of BWP downlink dedicated parameters.
  • Each group of BWP downlink dedicated parameters may include a CSI measurement configuration and a PDCCH configuration.
  • CSI measurement configuration and PDCCH configuration in the same set of BWP downlink dedicated parameters are associated. It can be understood that the CSI measurement configuration and the PDCCH configuration in the same set of BWP downlink dedicated parameters may be configured for the same BWP.
  • the BWP downlink parameters configured for a certain BWP in the serving cell configuration may include BWP downlink dedicated parameter 0 and BWP downlink dedicated parameter 1.
  • the BWP downlink dedicated parameter 0 may include a CSI measurement configuration and a PDCCH configuration
  • the BWP downlink dedicated parameter 1 may include a CSI measurement configuration and a PDCCH configuration. Then, the CSI measurement configuration in the BWP downlink dedicated parameter 0 is associated with the PDCCH configuration; the CSI measurement configuration in the BWP downlink dedicated parameter 1 is associated with the PDCCH configuration.
  • the BWP downlink parameters configured for a certain BWP in the serving cell configuration may include one or more groups of BWP downlink dedicated parameters.
  • Each group of BWP downlink dedicated parameters may include one or more CSI measurement configurations and one or more PDCCH configurations.
  • the CSI measurement configuration and the PDCCH configuration belong to the same set of BWP downlink dedicated parameters, and the identifier of the CSI measurement configuration is the same as the identifier of the PDCH configuration. It can be understood that the CSI measurement configuration and the PDCCH configuration in the same set of BWP downlink dedicated parameters may be configured for the same BWP.
  • the BWP downlink parameters configured for a certain BWP in the serving cell configuration may include BWP downlink dedicated parameters 0 and BWP downlink dedicated parameters 1.
  • the BWP downlink dedicated parameter 0 may include CSI measurement configuration 0, CSI measurement configuration 1, and PDCCH configuration 0, PDCCH configuration 1.
  • the BWP downlink dedicated parameter 1 may include CSI measurement configuration 0, CSI measurement configuration 1, and PDCCH configuration 0 and PDCCH configuration 1. It can be understood that the configurations with the same identifier in the BWP downlink dedicated parameter 0 and the BWP downlink dedicated parameter 1 are not necessarily the same. That is, the configuration identifier in each set of parameters may be local.
  • CSI measurement configuration 0 in BWP downlink dedicated parameter 0 is associated with PDCCH configuration
  • CSI measurement configuration 1 in BWP downlink dedicated parameter 0 is associated with PDCCH configuration 1
  • CSI measurement configuration 0 in BWP downlink dedicated parameter 1 is related to PDCCH configuration.
  • CSI measurement configuration 1 in BWP downlink dedicated parameter 1 is associated with PDCCH configuration 1.
  • the configurations in the serving cell configuration may be associated. Then, when the CSI measurement configuration and the PDCCH configuration can belong to the same serving cell configuration, the CSI measurement configuration and the PDCCH configuration can be associated.
  • the CSI report configuration includes configuration information of CSI resources. Therefore, when the CSI reporting configuration is associated with the PDCCH configuration, the CSI resources configured in the CSI reporting configuration are also associated with the PDCCH configuration. For example, the CSI report configuration includes the identifier of the CSI resource configuration. When a CSI reporting configuration is associated with a PDCCH configuration, the CSI configuration included in the CSI reporting configuration may also be associated with the PDCCH configuration.
  • the second configuration information may also be a mapping relationship, such as a mapping relationship table, or other information that may be used to indicate the mapping relationship.
  • the mapping relationship may be used to indicate the corresponding PUCCH configuration and PDCCH configuration, and the corresponding PUCCH configuration and PDCCH configuration may have an association relationship.
  • the foregoing is only for easy understanding, and the identifiers of the BWP dedicated parameters, the BWP uplink dedicated parameters, the BWP downlink dedicated parameters, the CSI reporting configuration identifier, the CSI measurement configuration identifier, and the PDCCH are exemplarily given The identification of the configuration, but this should not constitute any limitation to this application.
  • the number of groups of BWP uplink parameters configured for the same BWP the number of groups of BWP downlink parameters, the number of groups of BWP dedicated parameters, the number of groups of BWP uplink dedicated parameters, the number of groups of BWP downlink dedicated parameters, PDCCH
  • the number of configurations, the number of CSI measurement configurations, and the number of CSI reporting configurations included in each CSI measurement configuration are not limited.
  • the manner of allocating identifiers for the configuration of the multiple sets of dedicated parameters included in each set of parameters is also not limited.
  • the identification of the configuration of each group of dedicated parameters may be local or global.
  • the serving cell configuration may also include other configuration parameters other than those listed above, which is not limited in this application.
  • the network device may indicate the associated CSI report configuration and PDCCH downlink control parameters to the terminal device by any of the following methods:
  • Method 1 Add an indication field to the CSI report configuration to indicate the associated DMRS port group or DMRS CDM group;
  • Method 2 Add an indication field to the CSI measurement configuration to which the CSI report configuration belongs to indicate the associated DMRS port group or DMRS CDM group;
  • Method 3 Add an indication field to the CSI report configuration to indicate the associated TB or CW;
  • Method 4 An indication field is added to the CSI measurement configuration to which the CSI report configuration belongs to indicate the associated TB or CW.
  • the method 200 has been described in detail with reference to downlink control parameters. For brevity, I won't repeat them here.
  • the network device may be added to the CSI report configuration to indicate the associated DMRS port group or DMRS CDM group.
  • the CSI reporting configuration can be configured through the high-level parameter CSIReport-Config.
  • the network device can add the DMRS port group ID field in the CSIReport-ConfigIE to indicate the associated DMRS port group.
  • CDM group ID field to indicate the associated DMRS CDM group.
  • the second configuration information may be a CSI report configuration, for example, CSIReport-Config, or other signaling that may be used to implement the same or similar functions as the CSI report configuration.
  • the network device may be added to the CSI measurement configuration to which the CSI report configuration belongs to indicate the associated DMRS port group or DMRS CDM group.
  • the CSI measurement configuration can be configured through the high-level parameter CSIMeas-Config, and the network device can add the DMRS port group ID field in the CSIMeas-Config IE to indicate the associated DMRS port group; or, add it in the CSIMeas-Config IE DMRS CDM group ID field to indicate the associated DMRS CDM group.
  • the second configuration information may be a CSI measurement configuration, for example, CSIMeas-ConfigIE or other signaling that can be used to implement the same or similar functions of the CSI measurement configuration.
  • each CSI measurement configuration can include one or more CSI reporting configurations
  • when the CSI measurement configuration is associated with a DMRS port group or DMRS CDM group one or more CSI reporting configurations in the CSI measurement configuration can be associated with The same DMRS port group or DMRS CDM group association.
  • the network device may add a field in the CSI report configuration to indicate the associated TB or CW.
  • the CSI report configuration can be configured through the high-level parameter CSIReport-Config, and the network device can add a field indicating the TB or CW in the CSIReport-Config to indicate the associated TB or CW.
  • the second configuration information may be a CSI report configuration, for example, CSIReport-Config, or other signaling that may be used to implement the same or similar functions as the CSI report configuration.
  • the network device may add a field to the CSI measurement configuration to which the CSI report configuration belongs to indicate the associated TB or CW.
  • the CSI measurement configuration may be configured through the high-level parameter CSIMeas-Config, and the network device may add a field for indicating a TB or CW to the CSIMeas-Config, to indicate the associated TB or CW.
  • the second configuration information may be a CSI measurement configuration, for example, CSIMeas-Config, or other signaling that may be used to implement the same or similar functions as the CSI measurement configuration.
  • each CSI measurement configuration can include one or more CSI reporting configurations
  • one or more CSI reporting configurations in the CSI measurement configuration can be associated with the same TB or CW.
  • the CSI reporting configuration or the CSI measurement configuration can indicate the associated TB or the associated CW.
  • the terminal device can determine the other associated with the PUCCH configuration.
  • step 320 the network device sends the second configuration information. Accordingly, in step 320, the terminal device receives the second configuration information.
  • the second configuration information may be carried in high-level signaling.
  • the high-level signaling may be, for example, an RRC message.
  • the two configuration information can be sent to each terminal device through different signaling.
  • the terminal device communicates with multiple network devices, it can also receive the second configuration information from multiple network devices.
  • step 330 the terminal device determines the associated CSI reporting configuration and PDCCH configuration according to the second configuration information.
  • the terminal device When the terminal device receives the second configuration information from one or more network devices, it may determine the associated CSI reporting configuration and PDCCH configuration based on the manner described in step 320 above.
  • the network device may generate the second configuration information based on the method defined by the protocol, and the terminal device may analyze the second configuration information based on the method defined by the protocol.
  • the second configuration information is used to determine the associated CSI reporting configuration and PDCCH configuration.
  • the terminal device can determine which CSI reporting configuration and PDCCH configuration correspond to the same network device based on the association relationship between the CSI reporting configuration and the PDCCH configuration, so that the PUCCH resources can be determined to transmit UCI according to the instructions of the network device.
  • the network device can also receive UCI on the corresponding resources, which will not cause the network device to fail to receive UCI due to inconsistent resources determined by both parties. Therefore, by introducing the second configuration information, it is beneficial to improve transmission performance and user experience.
  • FIG. 4 is a schematic flowchart of a method 400 for sending and receiving UCI according to an embodiment of the present application, which is shown from the perspective of device interaction. As shown, the method 400 may include steps 410 to 450. The steps in the method 400 are described in detail below.
  • FIG. 4 shows a specific process of transmitting UCI by a terminal device and a network device in a wireless communication system.
  • the terminal device may be any terminal device in a wireless communication system, and the terminal device may communicate with one or more network devices, which is not limited in this application.
  • the network equipment it serves is transparent.
  • a terminal device is taken as an example to describe in detail the specific process of transmitting UCI between the terminal device and the network device. It can be understood that any terminal device in the wireless communication system can send UCI to the network device based on the same technical solution, which is not limited in this application.
  • step 410 the terminal device determines that there is a resource overlap between the PUSCH and the target PUCCH.
  • the PUSCH may be scheduled by the network device through the PDCCH.
  • the network device may indicate the time domain and frequency domain positions of the PUSCH in the DCI carried in the PDCCH, for example.
  • the DCI may be, for example, DCI format 0_0 or DCI format 0_1.
  • the PUCCH may be a resource determined by the terminal device for transmitting UCI. In this embodiment, for convenience of identification and description, it is recorded as the target PUCCH. It can be understood that the resources of the target PUCCH are taken from the PUCCH resources configured in the PUCCH configuration. In other words, the PUCCH configuration may configure a PUCCH resource pool, and the PUCCH resource pool includes multiple PUCCH resources.
  • the terminal device can send HARQ information, periodic CSI, or semi-persistent CSI (hereinafter referred to as CSI) to the network device through the PUSCH without Transmitted over the target PUCCH. That is, the PUSCH can be used to transmit at least one of HARQ information and CSI. Therefore, in the embodiment of the present application, the method for sending and receiving UCI is described in detail by taking UCI as HARQ information and CSI (for example, periodic CSI or half-period CSI) as examples. In other words, the UCI may include at least one of HARQ information and CSI.
  • the protocol may also define that the UCI transmitted in the PUSCH may also contain other content, such as SR.
  • the method provided in the embodiment of the present application is mainly directed to a case where PUCCH and PUSCH resources overlap, and determines whether to transmit UCI through PUSCH, and the specific content included in UCI is not limited.
  • the way to determine the target PUCCH resource used to transmit UCI is also different.
  • the specific process of determining the resources of the target PUCCH by the terminal device is first described in detail by taking the UCI including HARQ information and / or CSI (for example, periodic CSI or half-period CSI) as examples.
  • the PDSCH can be a PDSCH scheduled by a network device through the PDCCH, or a PDSCH that is semi-persistently scheduled (SPS), the resource determination method of the target PUCCH for transmitting HARQ information is different according to the PDSCH scheduling method.
  • SPS semi-persistently scheduled
  • the PDSCH is a PDSCH scheduled by the PDCCH.
  • network devices serving the same terminal device can schedule PDSCH for the terminal device through the DCI in their respective PDCCHs.
  • each network device can schedule a PDSCH through its own DCI, and indicate the resources of the PUCCH for transmitting HARQ in its respective DCI.
  • the HARQ information fed back to the multiple PDSCHs can be fed back in one UCI or multiple UCIs, which is not limited in this application.
  • one or more PDSCHs may be scheduled. This application does not limit this. If there are multiple PDSCHs scheduled, the multiple PDSCHs may be scheduled for the same network device or may be scheduled for multiple network devices. When multiple PDSCHs are PDSCHs scheduled by multiple network devices, the terminal device may determine the resources of the target PUCCH corresponding to each network device based on the scheduling of each network device, respectively.
  • the terminal device receives the schedule from the first network device.
  • the method 400 further includes: the terminal device receives PDSCH scheduling information, and the scheduling information is used to schedule the PDSCH.
  • the first network device sends scheduling information of the PDSCH.
  • the scheduling information may be DCI sent by the first network device to the terminal device for scheduling PDSCH.
  • the specific method by which the first network device can schedule the PDSCH and indicate the resource of the target PUCCH for the terminal device through the DCI has been described in detail above, and for the sake of brevity, it will not be repeated here.
  • the network device can configure the PUCCH resource list and the PUCCH resource set list for the terminal device through high-level parameters, such as PUCCH-config and IE.
  • the terminal device may select a PUCCH resource set according to the length of the UCI to be transmitted, and may further determine a target PUCCH resource from the selected PUCCH resource set according to an indication in the DCI.
  • the resource of the target PUCCH can be determined by the PUCCH configuration.
  • the terminal device may also receive scheduling information sent by another network device other than the first network device for scheduling other PDSCHs, which is not limited in this application.
  • PDSCH is SPS PDSCH
  • the network device can configure the resources of the target PUCCH for transmitting HARQ information to the terminal device through the SPS configuration.
  • the network device may indicate the identity of the PUCCH resource to the terminal device through a high-level parameter, such as SPS-Config, ie, the PUCCH-ResourceId is indicated in the n1PUCCH-AN field.
  • the terminal device may determine the resource of the target PUCCH according to the identifier of the PUCCH resource.
  • the resource of the target PUCCH can be determined by the SPS configuration.
  • UCI includes only CSI and can be further divided into two cases: UCI includes only one CSI and UCI includes multiple CSI.
  • the terminal device may report a CSI based on a report amount indicated in a CSI report configuration and a PUCCH resource used for the report.
  • one CSI reported by the terminal device corresponds to one CSI reporting configuration.
  • the CSI may be periodic CSI or semi-persistent CSI.
  • the network device may trigger one or more different periods of CSI, or it may trigger semi-persistent CSI.
  • the terminal device may report multiple CSIs during this period, for example, multiple CSIs are reported in the same time slot.
  • CSI That is, UCI includes multiple CSIs.
  • the resource of the target PUCCH can be determined based on the CSI report configuration and the DCI.
  • the resources of the target PUCCH can be determined based on the pucch-CSI-ResourceList in the CSI reporting configuration and the BWP activated in the DCI; when the terminal device transmits multiple CSIs, the resources of the target PUCCH can be determined based on the PUCCH configuration.
  • the multi-CSI-PUCCH-ResourceList in the configuration determines the resources of the target PUCCH.
  • the target PUCCH resource can be determined by the CSI reporting configuration; if the number of CSI is greater than 1, the target PUCCH resource can be determined by the PUCCH configuration.
  • the terminal device can determine the resource of the target PUCCH according to the PUCCH resource indicator in the DCI carried by the PDCCH. Both the HARQ information and the CSI can be transmitted through the resource of the target PUCCH.
  • the resources of the target PUCCH can be determined by the PUCCH configuration.
  • the terminal device may determine the resource of the target PUCCH according to the method in the second case, and both the HARQ information and the CSI may be transmitted through the resource of the target PUCCH.
  • the resource of the target PUCCH can be determined by the CSI configuration or the PUCCH configuration.
  • the resources of the target PUCCH may be determined by the PUCCH configuration, or may be determined by the CSI report configuration, or may be determined by the SPS configuration.
  • the method 400 further includes: Step 420:
  • the terminal device receives scheduling information of the PUSCH, and the scheduling information is used to schedule the PUSCH.
  • the network device with which it communicates is transparent, and the terminal device does not know that several network devices serve it at the same time. Therefore, the terminal device does not know whether the scheduling information of the PUSCH is sent by the first network device.
  • the network device that sends the scheduling information of the PUSCH is temporarily referred to as the second network device. It can be understood that the second network device may be the same network device as the first network device, or may be different network devices.
  • the terminal device may determine whether the second network device and the first network device are the same network device in a subsequent process based on the method provided in this application.
  • the scheduling information of the PUSCH may be DCI sent by the second network device to the terminal device.
  • the second network device may use the DCI to indicate information such as time-frequency resources, modulation and coding modes of the PUSCH for the terminal device.
  • the terminal device may also receive scheduling information sent by another network device other than the second network device for scheduling other PUSCHs, which is not limited in this application.
  • the terminal device may determine whether the resources of the target PUCCH and the resources of the PUSCH overlap according to the resources determined above. When there is a resource overlap between the target PUCCH and the PUSCH, the terminal device may perform step 430, and the terminal device determines whether the PUSCH is associated with the target PUCCH.
  • the terminal device After the terminal device determines the target PUCCH and PUSCH, it can further determine whether the resources of the target PUCCH and PUSCH overlap. If no overlap occurs, the terminal device may directly send UCI to the first network device through the PUCCH, and send uplink data to the second network device through the PUSCH. If overlap occurs, the terminal device does not know whether the above PUCCH and PUSCH are scheduled by the same network device. In order to avoid sending UCI on PUCCH to PUSCH that is not associated with it, the network device cannot succeed after receiving the PUSCH. Demodulation and decoding.
  • the terminal device may further determine whether the target PUCCH and PUSCH have an association relationship, or whether the target PUCCH and PUSCH are sent to the same network device, or determine the first network device. Whether it is the same network device as the second network device.
  • the terminal device determines that the target PUCCH and PUSCH have an association relationship, it can be determined that the target PUCCH and PUSCH are sent to the same network device, so the UCI originally transmitted through the target PUCCH can be transmitted to the network device through the PUSCH; otherwise, it can be temporarily The UCI is not transmitted, that is, the UCI is not transmitted using the target PUCCH or PUSCH.
  • the PUSCH can be scheduled by the PDCCH, and the terminal device can determine the PDCCH configuration of the PDCCH when receiving the PDCCH. Therefore, when the resource of the target PUCCH is associated with the above-mentioned PDCCH configuration, the PUCCH is associated with the PUSCH.
  • the configuration parameters of the resources used to determine the target PUCCH are also different. For example, when the UCI contains only HARQ information and the HARQ information is HARQ information fed back to the PDSCH scheduled for the PDCCH, the target PUCCH
  • the resources of the target PUCCH can be determined by the SPS configuration when the UCI only contains HARQ information and the PDSCH corresponding to the HARQ information is not scheduled by the PDCCH (such as SPS PDSCH).
  • the resources of the target PUCCH can be determined by the CSI reporting configuration; when the UCI contains only multiple CSIs, the resources of the target PUCCH can be determined by the PUCCH configuration; when the UCI contains HARQ information and CSI (one or Multiple)
  • the resource of the target PUCCH can be determined by the PUCCH configuration; when UCI includes HARQ information and a CSI, and the PDSCH corresponding to the HARQ information is not determined by the PDCCH Scheduled (such as SPS PDSCH), the resource of the target PUCCH can be determined by the CSI report configuration; when UCI contains HARQ information and multiple CSI, and the PDSCH corresponding to the HARQ information is not determined by For PDCCH scheduling (such as SPS PDSCH), the resources of the target PUCCH can be determined by the PUCCH configuration.
  • the PUCCH configuration used to determine the resources of the target PUCCH will be referred to as the PUCCH configuration of the target PUCCH
  • the CSI report configuration used to determine the resources of the target PUCCH will be referred to as the CSI report configuration of the target PUCCH, which will be used for
  • the SPS configuration of the resource of the target PUCCH is determined as the SPS configuration of the target PUCCH.
  • the terminal device may determine the PUCCH configuration associated with the PDCCH configuration based on the first configuration information in the method 200, and then determine whether the PUCCH configuration of the target PUCCH is associated with the PDCCH configuration.
  • a network device when a network device schedules a PDSCH through a PDCCH, it may indicate resources of a target PUCCH.
  • the terminal device may also directly determine whether the PUCCH configuration of the target PUCCH is related to the PDCCH configuration based on whether the PDCCH used to schedule the PDSCH and the PDCCH used to schedule the PUSCH belong to the same PDCCH configuration.
  • the resources of the PUSCH are scheduled by the first PDCCH, and the resources of the PUCCH are indicated by the second PDCCH.
  • the terminal device determines whether the target PUCCH is associated with the PUSCH. By determining the PDCCH configuration on which the second PDCCH is received and the basis on which the first PDCCH is received, It is determined whether the PDCCH configurations are the same. When the PDCCH configuration of the first PDCCH and the PDCCH configuration of the second PDCCH are the same PDCCH configuration, the target PUCCH is considered to be associated with the PUSCH.
  • the terminal device may determine the CSI report configuration associated with the PDCCH configuration based on the second configuration information in the method 300, and then determine whether the CSI report configuration of the target PUCCH is associated with the PDCCH configuration.
  • the specific process in which the network device indicates the associated PUCCH configuration and the PDCCH configuration to the terminal device through the first configuration information is described in detail above in connection with the method 200, and the method for reporting the associated CSI in the network device is indicated through the second configuration information in combination with the method 300
  • the terminal device can determine the associated PUCCH configuration and PDCCH configuration according to the first configuration information, and can also determine the associated CSI reporting configuration and PDCCH configuration according to the second configuration information.
  • the specific process has been described in detail in methods 200 and 300 above. For brevity, I won't repeat them here.
  • the PDSCH may be a semi-persistent scheduling (SPS) PDSCH, and the resource of the target PUCCH may be determined by the SPS configuration.
  • SPS configuration is a BWP downlink-specific parameter
  • the PDCCH configuration for scheduling the PUSCH is also a BWP downlink-specific parameter
  • the target PUCCH can be considered to be associated with PUSCH.
  • the network device may also configure an associated PDCCH configuration for the configuration parameter of each PUCCH resource in the PUCCH configuration.
  • the PUCCH configuration may include configuration parameters of multiple PUCCH resources, and the configuration parameters of each PUCCH resource may include an indication of the associated PDCCH configuration.
  • the indication of the PDCCH configuration may be, for example, an identifier of the PDCCH configuration, or other information that may be used to indicate the PDCCH configuration.
  • This approach can be understood as that the network device configures an associated PDCCH configuration for each PUCCH resource configuration parameter in the PUCCH resource pool.
  • the above target PUCCH may be taken from the PUCCH resource pool. Therefore, based on the associated PDCCH configuration configured by the network device for each PUCCH resource, the PDCCH configuration associated with the target PUCCH can be determined.
  • whether the target PUCCH and the PUSCH are associated can be determined based on whether the PDCCH configuration associated with the target PUCCH and the PDCCH configuration associated with the target PUCCH are the same PDCCH configuration.
  • the terminal device determines whether the PUSCH and the PUCCH are associated based on the PDCCH configuration
  • the association relationship may be further extended. That is, when the PDCCH configuration associated with the resource of the PUCCH and the PDCCH configuration of the PDCCH used for scheduling the PUSCH belong to the same PDCCH configuration group, it can be considered that the PUCCH is associated with the PUSCH.
  • the first network device and the second network device serve the same terminal device based on the CoMP technology
  • the first network device and / or the second network device also schedules more spectrum resources for the terminal device based on carrier aggregation.
  • the first network device may send PDCCH # 1 to the terminal device in CC # 1 to schedule PDSCH # 1 and instruct transmission of HARQ information for the PDSCH # 1 on PUCCH # 1.
  • the first network device may also send PDCCH # 2 to the terminal device at CC # 1 to schedule PUSCH # 1.
  • the first network device may also send PDCCH # 3 to the terminal device in CC # 2 to schedule PDSCH # 2 and instruct PUCCH # 2 to transmit HARQ information for PDSCH # 2 feedback.
  • the PDCCH configuration is configured based on each BWP of each cell.
  • the first network device may send different PDCCH configurations based on CC # 1 and CC # 2. That is, the same network device may send the PDCCH to the terminal device based on two or more different PDCCH configurations.
  • the terminal device determines the associated PUCCH and PUSCH based on different PDCCH configurations, the PUCCH and PUSCH scheduled by the same network device may be regarded as the PUCCH and PUSCH scheduled by different network devices. If there is resource overlap between PUCCH # 1, PUCCH # 2, and PUSCH # 1, the terminal device may only send UCI generated based on CC # 1 to the first network device through PUSCH # 1, and the UCI may include feedback for PDSCH # 1 HARQ instead of HARQ for PDSCH # 2. But in fact, since PUCCH # 1, PUCCH # 2, and PUSCH # 1 all send the first network device, the first network device may receive UCI generated based on CC # 1 and CC # 2 on PUSCH # 1. Because the length of the UCI sent by the terminal device and the UCI expected by the first network device may be different, the first network device may not be able to correctly parse out the information in the UCI.
  • Each PDCCH configuration group may include multiple PDCCH configurations, and each PDCCH configuration is based on one BWP configuration in one cell.
  • the PDCCH configuration group may be configured through high-level signaling.
  • one PDCCH configuration group may be used to indicate the included PDCCH configuration.
  • an indication field is added to indicate a PDCCH configuration group to which each PDCCH configuration belongs.
  • the same network device may send the PDCCH to the terminal device in different cells based on the PDCCH configuration in the PDCCH configuration group.
  • the terminal device determines that the PDCCH configuration based on the blindly detected PDCCH belongs to the same PDCCH configuration group, it can be considered that the blindly detected PDCCHs based on the same PDCCH configuration group are sent by the same network device. Therefore, the terminal device can be considered to be based on the same network device.
  • PDCCH configuration group to associate PUCCH configuration and PUSCH configuration.
  • the methods listed above for determining whether the target PUCCH and PUSCH are associated are all examples and should not be construed as limiting this application. This application does not limit the specific method for determining whether the target PUCCH is related to the PUSCH. Several methods are provided below that can be used to determine whether the target PUCCH and PUSCH are associated. It should be noted that among the methods provided below for determining whether the target PUCCH is related to the PUSCH, the PUSCH may be a PUSCH scheduled by the PDCCH, or a PUSCH configured for authorization, which is not limited in this application.
  • the PUCCH configuration of the target PUCCH may be associated with the PUSCH configuration of the PUSCH, or with the PUSCH configuration authorization Configure the association.
  • the PUSCH configuration of the PUSCH may be used to determine transmission parameters of the PUSCH scheduled by the PDCCH, and the ConfiguredGrant configuration of the PUSCH may be used to determine resources for configuring the authorized PUSCH.
  • the PUCCH and the PUSCH can satisfy at least one of the conditions listed below:
  • the PUCCH configuration of the PUCCH and the PUSCH configuration of the PUSCH belong to the same BWP uplink dedicated parameter (BWP UL dedicated);
  • the PUCCH configuration of the PUCCH and the PUSCH configuration of the PUSCH belong to the same BWP uplink dedicated parameter, and the identifier of the PUCCH configuration is the same as the identifier of the PUSCH configuration;
  • the PUCCH configuration of the PUCCH includes an indication of the PUSCH configuration of the PUSCH;
  • the PUSCH configuration of the PUSCH includes an indication of the PUCCH configuration of the PUCCH
  • the PUSCH configuration of the PUSCH and the PUCCH configuration of the PUCCH are associated with the same PDCCH configuration
  • the PUSCH configuration of the PUSCH and the PUCCH configuration of the PUCCH belong to the same serving cell configuration
  • the transmission beam used to transmit the PUCCH and the transmission beam used to transmit the PUSCH belong to the same transmission beam group.
  • the conditions i) to vii) listed above can be understood as one or more conditions that the associated PUCCH configuration and PUSCH configuration meet.
  • the conditions listed above are explained in detail below.
  • the network device can configure the BWP uplink dedicated parameters for the terminal device through the serving cell configuration.
  • the network device may configure one or more groups of BWP uplink dedicated parameters for the terminal device, and each group of BWP uplink dedicated parameters may include a PUCCH configuration and a PUSCH configuration.
  • the PUCCH configuration and PUSCH configuration configured in the same set of BWP uplink dedicated parameters can be considered to be configured based on the same network device. For example, a PUCCH resource determined based on a PUCCH configuration is used to transmit UCI sent to a certain network device, and a transmission parameter determined based on the PUSCH configuration is used to transmit a PUSCH to the same network device. Therefore, the PUCCH configuration and the PUSCH configuration configured in the same set of uplink dedicated parameters can be considered to be related.
  • the network device may configure the BWP uplink dedicated parameters for the terminal device through the serving cell configuration.
  • the network device may configure one or more groups of BWP uplink dedicated parameters for the terminal device, and each group of BWP uplink dedicated parameters may include one or more PUCCH configurations and one or more PUSCH configurations.
  • Each PUCCH configuration can be distinguished by a PUCCH configuration identifier
  • each PUSCH configuration can be distinguished by a PUSCH configuration identifier.
  • the PUCCH configuration and the PUSCH configuration configured with the same identifier may be considered to be configured based on the same network device. Therefore, a PUCCH configuration and a PUSCH configuration configured with the same identifier in the same set of BWP uplink dedicated parameters can be considered to be related.
  • the network device can configure PUCCH resources for the terminal device through the PUCCH configuration.
  • the PUCCH configuration may include an indication of the associated PUSCH configuration.
  • the network device may add a field for indicating the PUSCH configuration in the PUCCH configuration to indicate the associated PUSCH configuration.
  • the indication of the PUSCH configuration may be, for example, an identifier of the PUSCH configuration, or other information that may be used to indicate the PUSCH configuration.
  • the PUSCH configuration may include an indication of the associated PUCCH configuration.
  • the network device may add a field for indicating the PUCCH configuration in the PUSCH configuration to indicate the associated PUCCH configuration.
  • the indication of the PUCCH configuration may be, for example, an identifier of the PUCCH configuration, or other information that may be used to indicate the PUCCH configuration.
  • the PUCCH configuration and the PUSCH configuration can also be associated through the PDCCH configuration.
  • the PUCCH configuration may include an indication of the associated PDCCH configuration
  • the PUSCH configuration may also include the indication of the associated PDCCH configuration.
  • the network device adds a field for indicating the PDCCH configuration in the PUCCH configuration and the PUSCH configuration to indicate the associated PDCCH configuration.
  • the indication of the PDCCH configuration may be, for example, an identifier of the PDCCH configuration, or other information that may be used to indicate the PDCCH configuration.
  • condition v) may be further extended to that the associated PDCCH configuration indicated in the PUSCH configuration and the associated PDCCH configuration indicated in the PUCCH configuration belong to the same PDCCH configuration group.
  • the PUCCH When the resources of the PUCCH are determined by the PUCCH configuration, if the PDCCH configuration associated with the PUCCH configuration of the PUCCH and the PDCCH configuration associated with the PUSCH configuration belong to the same PDCCH configuration group, the PUCCH may be considered to be associated with the PUSCH.
  • the network device may configure the PUSCH configuration and the PUCCH configuration for the terminal device through the serving cell configuration.
  • a network device can configure one or more BWPs for each terminal device through the high-level parameter ServingCellConfig.IE.
  • the PUCCH configuration and the PUSCH configuration configured in the same serving cell configuration can be considered to be related.
  • the transmission beam used to transmit the PUCCH and the transmission beam used to transmit the PUSCH may belong to the same transmission beam group.
  • the terminal device may determine the selected spatial relationship according to the PUCCH configuration and the SRI indicated by the network device, and then determine the transmit beam used to send the PUCCH.
  • the terminal device can determine the selected SRS resource according to the SRS configuration and the SRI indicated by the network device, and then determine the transmit beam used to send the PUSCH.
  • the network device may indicate the reference signal resource group to which each reference signal resource belongs in the PUCCH configuration.
  • a field is added to the PUCCH-SpatialRelationInfo in the PUCCH configuration to indicate the SSB resource belongs to Reference signal resource group, non-zero power CSI-RS resource, and reference signal resource group to which the SRS belongs.
  • a field is added to PUCCH-SpatialRelationInfo in the PUCCH configuration to indicate a reference signal resource group to which all reference signal resources defined in the PUCCH-SpatialRelationInfo belong.
  • This field may be, for example, a reference signal resource group identifier, an antenna panel identifier, or other information that can be used to distinguish different reference signal resource groups.
  • the network device may indicate the reference signal resource group to which each reference signal resource belongs in the SRS configuration.
  • a field is added to the SRS-SpatialRelationInfo in the SRS configuration to indicate the reference signal to which the SSB resource belongs A resource group, a non-zero power CSI-RS resource, and a reference signal resource group to which the SRS belongs.
  • a field is added to the SRS-SpatialRelationInfo in the SRS configuration, indicating a reference signal resource group to which all the reference signal resources defined in the SRS-SpatialRelationInfo belong.
  • This field may be, for example, a reference signal resource group identifier, an antenna panel identifier, or other information that can be used to distinguish different reference signal resource groups.
  • the transmission beams determined by the reference signal resources belonging to the same reference signal resource group may belong to the same transmission beam group, or the transmission beams determined by the reference signal resources belonging to the same reference signal resource group may be determined by the same antenna panel. Antenna transmission.
  • the terminal device When the terminal device receives the high-level signaling (such as MAC-CE), the reference signal resource in the activated spatial relationship (that is, the spatial relationship for PUCCH) and the spatial relationship indicated by the physical layer signaling (such as DCI) (that is, The reference signal resources in the spatial relationship for PUSCH) belong to the same reference signal resource group, then the PUCCH transmission beam and the PUSCH transmission beam belong to the same transmission beam group, it can be considered that the PUCCH is associated with the PUSCH.
  • the high-level signaling such as MAC-CE
  • the PUCCH and the PUSCH can satisfy at least one of the conditions listed below:
  • the PUCCH configuration of the PUCCH and the ConfiguredGrant configuration of the PUSCH belong to the same BWP uplink dedicated parameters (BWP UL dedicated);
  • the ConfiguredGrant configuration of the PUCCH and the PUSCH configuration of the PUSCH belong to the same BWP UL dedicated, and the identifier of the PUCCH configuration is the same as the identifier of the PUSCH configuration;
  • the PUCCH configuration of the PUCCH includes an indication of the ConfiguredGrant configuration of the PUSCH;
  • the ConfiguredGrant configuration of the PUSCH includes an indication of the PUCCH configuration of the PUCCH
  • the transmission beam used to transmit the PUCCH and the transmission beam used to transmit the PUSCH belong to the same transmission beam group.
  • the conditions i) to vii) listed above can be understood as one or more conditions that the associated PUCCH configuration and ConfiguredGrant configuration meet. The conditions listed above are explained in detail below.
  • the network device can configure the BWP uplink dedicated parameters for the terminal device through the serving cell configuration.
  • the network device may configure one or more groups of BWP uplink dedicated parameters for the terminal device, and each group of BWP uplink dedicated parameters may include a PUCCH configuration and a ConfiguredGrant configuration.
  • the PUCCH configuration and the ConfiguredGrant configuration configured in the same set of BWP uplink dedicated parameters can be considered to be based on the configuration of the same network device.
  • the PUCCH resource determined based on the PUCCH configuration is used to transmit UCI sent to a certain network device, and the resource determined based on the Configured Grant configuration can be used to transmit PUSCH to the same network device. Therefore, the PUCCH configuration and the ConfiguredGrant configuration configured in the same set of uplink dedicated parameters can be considered to be related.
  • the network device may configure the BWP uplink dedicated parameters for the terminal device through the serving cell configuration.
  • the network device may configure one or more groups of BWP uplink dedicated parameters for the terminal device, and each group of BWP uplink dedicated parameters may include one or more PUCCH configurations and one or more ConfiguredGrant configurations.
  • Each PUCCH configuration can be distinguished by a PUCCH configuration identifier
  • each ConfiguredGrant configuration can be distinguished by a ConfiguredGrant configuration identifier.
  • the PUCCH configuration and the ConfiguredGrant configuration configured with the same identifier can be considered to be configured based on the same network device. Therefore, a PUCCH configuration and a ConfiguredGrant configuration configured with the same identifier in the same set of BWP uplink dedicated parameters can be considered to be related.
  • the network device can configure PUCCH resources for the terminal device through the PUCCH configuration.
  • the PUCCH configuration may include an indication of the associated ConfiguredGrant configuration.
  • the network device may add a field in the PUCCH configuration to indicate the ConfiguredGrant configuration to indicate the associated ConfiguredGrant configuration.
  • the indication of the ConfiguredGrant configuration may be, for example, an identifier of the ConfiguredGrant configuration, or other information that may be used to indicate the configuration of the ConfiguredGrant.
  • the ConfiguredGrant configuration may include an indication of the associated PUCCH configuration.
  • the network device may add a field for indicating the PUCCH configuration in the ConfiguredGrant configuration to indicate the associated PUCCH configuration.
  • the indication of the PUCCH configuration may be, for example, an identifier of the PUCCH configuration, or other information that may be used to indicate the PUCCH configuration.
  • the network device may configure the ConfiguredGrant configuration and the PUCCH configuration for the terminal device through the serving cell configuration.
  • a network device can configure one or more BWPs for each terminal device through the high-level parameter ServingCellConfig.IE.
  • the PUCCH configuration and the ConfiguredGran configuration configured in the same serving cell configuration can be considered to be related.
  • the transmit beam used to send the PUSCH may also be determined by the SRS configuration and the SRS resource determined by the SRI indicated by the network device.
  • the conditions under which the PUCCH transmit beam and the PUSCH transmit beam belong to the same transmit beam group have been described in detail above. For brevity, I won't repeat them here.
  • the protocol may define that the associated PUCCH and PUSCH satisfy one or more of the items listed above.
  • the terminal device may determine whether the scheduled PUCCH and the PUSCH are associated based on the one or more conditions.
  • the protocol definition determines whether PUCCH and PUSCH are associated based on one or more of the conditions listed above, it does not mean that the associated PUCCH and PUSCH do not meet the other conditions listed above.
  • the protocol definition determines whether the PUCCH and the PUSCH are associated based on the condition i) listed above, it is possible that the PUCCH and the PUSCH satisfy both condition i) and condition v).
  • the network device and the terminal device determine whether the PUCCH and the PUSCH are associated only based on the condition i). Even if the PUCCH and the PUSCH satisfy the condition v) and the condition i) is not satisfied, the PUCCH and the PUSCH are still considered not to be associated.
  • the terminal device can determine whether the scheduled PUCCH is associated with the PUSCH.
  • the resource of the target PUCCH may also be determined by the CSI report configuration
  • the CSI report configuration of the target PUCCH may be associated with the PUSCH configuration of the PUSCH. Since the CSI reporting configuration is a CSI measurement configuration, the network device can configure one or more CSI reporting configurations for the terminal device through the CSI measurement configuration. Therefore, when the CSI report configuration is associated with the PUSCH configuration, the CSI measurement configuration to which the CSI report configuration belongs may also be associated with the PUSCH configuration.
  • the PUSCH configuration of the PUSCH can be used to determine the transmission parameters of the PUSCH, and the CSI report configuration of the target PUCCH can be used to determine the resources of the PUCCH.
  • the PUCCH and the PUSCH can satisfy at least one of the conditions listed below:
  • the CSI measurement configuration to which the CSI report configuration of the PUCCH belongs (hereinafter referred to as the CSI measurement configuration of the PUCCH) and the PUSCH configuration of the PUSCH belong to the same BWP uplink dedicated parameter (BWP UL dedicated);
  • the CSI measurement configuration of the PUCCH and the PUSCH configuration of the PUSCH belong to the same BWP uplink dedicated parameter, and the identifier of the CSI measurement configuration is the same as the identifier of the PUSCH configuration;
  • the identifier of the BWP downlink dedicated parameter to which the CSI measurement configuration of the PUCCH belongs is the same as the identifier of the BWP uplink dedicated parameter to which the PUSCH of the PUSCH belongs;
  • the identifier of the BWP downlink dedicated parameter to which the CSI measurement configuration of the PUCCH belongs is the same as the identifier of the BWP uplink dedicated parameter to which the PUSCH configuration of the PUSCH belongs, and the identifier of the CSI measurement configuration of the PUCCH is the same as the identifier of the PUSCH configuration of the PUSCH ;
  • the identifier of the CSI measurement configuration of the PUCCH is the same as the identifier of the BWP uplink dedicated parameter to which the PUSCH configuration of the PUSCH belongs;
  • the CSI measurement configuration of the PUCCH includes an indication of the PUSCH configuration of the PUSCH;
  • the PUSCH configuration of the PUSCH includes an indication of the CSI measurement configuration of the PUCCH
  • the PUSCH configuration of the PUSCH and the CSI reporting configuration of the PUCCH are associated with the same PDCCH configuration
  • the transmission beam used to transmit PUCCH and the transmission beam used to transmit PUSCH belong to the same transmission beam group.
  • the conditions a) to i) listed above can be understood as one or more conditions satisfied by the associated CSI measurement configuration and PUSCH configuration.
  • the conditions listed above are explained in detail below.
  • the network device can configure the BWP uplink dedicated parameters for the terminal device through the serving cell configuration.
  • the network device may configure one or more groups of BWP uplink dedicated parameters for the terminal device, and each group of BWP uplink dedicated parameters may include a CSI measurement configuration and a PUSCH configuration.
  • the CSI measurement configuration and PUSCH configuration configured in the same set of BWP uplink dedicated parameters can be considered to be configured based on the same network device. For example, the resources of the PUCCH determined based on the CSI measurement configuration are used to transmit UCI sent to a certain network device, and the transmission parameters determined based on the PUSCH configuration are used to transmit the PUSCH to the same network device. Therefore, the CSI measurement configuration and the PUSCH configuration configured in the same set of uplink dedicated parameters can be considered to be related.
  • the condition a) can be further extended to that the CSI reporting of the PUCCH and the PUSCH configuration of the PUSCH belong to the same BWP uplink dedicated parameter.
  • the network device may configure the BWP uplink dedicated parameters for the terminal device through the serving cell configuration.
  • the network device may configure one or more groups of BWP uplink dedicated parameters for the terminal device, and each group of BWP uplink dedicated parameters may include one or more CSI measurement configurations and one or more PUSCH configurations.
  • Each CSI measurement configuration can be distinguished by a CSI measurement configuration identifier
  • each PUSCH configuration can be distinguished by a PUSCH configuration identifier.
  • the CSI measurement configuration and the PUSCH configuration configured with the same identifier can be considered to be configured based on the same network device. Therefore, a CSI measurement configuration and a PUSCH configuration that are configured in the same set of BWP uplink dedicated parameters and have the same identifier can be considered to be related.
  • condition b) can be further extended to that the CSI reporting configuration of the PUCCH and the PUSCH configuration of the PUSCH belong to the same BWP uplink dedicated parameter, and the identifier of the CSI reporting configuration and The identity of the PUSCH configuration is the same.
  • the network device may configure the BWP uplink dedicated parameter and the BWP downlink dedicated parameter for the terminal device through the serving cell configuration.
  • the network device may configure one or more groups of BWP uplink dedicated parameters and one or more groups of BWP downlink dedicated parameters for the terminal device.
  • Each group of BWP uplink dedicated parameters may include a PUSCH configuration, and each group of BWP downlink dedicated parameters may include a CSI measurement configuration.
  • Each group of BWP uplink dedicated parameters can be distinguished by identification, and each group of BWP downlink dedicated parameters can also be distinguished by identification.
  • the configurations in the BWP uplink dedicated parameters and the BWP downlink dedicated parameters configured with the same identifier can be considered to be configured based on the same network device.
  • the identifier of the BWP downlink dedicated parameter to which the CSI measurement configuration belongs and the identifier of the BWP uplink dedicated parameter to which the PUSCH configuration belongs may be the same.
  • the network device configures a set of BWP uplink dedicated parameters and a set of BWP downlink dedicated parameters for the terminal device, it may not be distinguished by identification.
  • the configuration in the BWP uplink dedicated parameters and the configuration in the BWP downlink dedicated parameters can be considered to be based on the same network device configuration. That is, the PUSCH configuration in the BWP uplink dedicated parameter and the CSI measurement configuration in the BWP downlink dedicated parameter can be considered to be related. This can be understood as a special case where the identifier of the BWP downlink dedicated parameter to which the CSI measurement configuration belongs is the same as the identifier of the BWP uplink dedicated parameter to which the PUSCH configuration belongs.
  • condition c) can be further extended to the identifier of the BWP downlink dedicated parameter to which the CSI reporting configuration of the PUCCH belongs and the BWP uplink dedicated parameter to which the PUSCH configuration of the PUSCH belongs.
  • the identifier configured in the CSI report is the same as the identifier configured in the PUSCH.
  • the network device may configure the BWP uplink dedicated parameter and the BWP downlink dedicated parameter for the terminal device through the serving cell configuration.
  • the network device may configure one or more groups of BWP uplink dedicated parameters and one or more groups of BWP downlink dedicated parameters for the terminal device.
  • Each group of BWP uplink dedicated parameters may include one or more PUSCH configurations, and each group of BWP downlink dedicated parameters may include one or more CSI measurement configurations.
  • Each group of BWP uplink dedicated parameters can be distinguished by identification, and each group of BWP downlink dedicated parameters can also be distinguished by identification.
  • Each PUSCH can be distinguished by an identifier, and each CSI measurement configuration can be distinguished by an identifier.
  • the identifier of the BWP downlink dedicated parameter to which the CSI measurement configuration belongs and the identifier of the BWP uplink dedicated parameter to which the PUSCH configuration belongs may be the same, and the identifier of the CSI measurement configuration and the PUSCH configuration The logo can also be the same.
  • condition d) can be further extended to identify the BWP downlink dedicated parameters to which the CSI reporting configuration of the PUCCH belongs and the BWP uplink dedicated parameters configured for the PUSCH and PUSCH.
  • the identifier is the same, and the identifier of the CSI report configuration of the PUCCH is the same as the identifier of the PUSCH configuration of the PUSCH.
  • the network device may also configure one or more CSI measurement configurations and one or more groups of BWP uplink dedicated parameters for the terminal device.
  • Each group of BWP uplink dedicated parameters may include one or more PUSCH configurations.
  • the identifier of the CSI measurement configuration may be the same as the identifier of the BWP uplink dedicated parameter to which the PUSCH configuration of the PUSCH belongs.
  • the terminal device may determine the resources of the PUCCH based on the CSI report configuration.
  • the CSI measurement configuration to which the CSI report configuration belongs may include an indication of the associated PUSCH configuration.
  • the network device may add a field for indicating the PUSCH configuration in the CSI measurement configuration to indicate the associated PUSCH configuration.
  • the indication of the PUSCH configuration may be, for example, an identifier of the PUSCH, or other information that may be used to indicate the PUSCH configuration.
  • condition f) may be further extended to include an indication that the CSI reporting configuration includes an associated PUSCH configuration. In this case, multiple CSI reporting configurations in the same CSI measurement configuration can be associated with different PUSCH configurations.
  • the PUSCH configuration may include an indication of the associated CSI measurement configuration.
  • the network device may add a field for indicating the CSI measurement configuration in the PUSCH configuration to indicate the associated CSI measurement configuration.
  • the indication of the CSI measurement configuration may be, for example, an identifier of the CSI measurement configuration, or other information that may be used to indicate the CSI measurement configuration.
  • condition g) can be further extended to include an indication of the associated CSI reporting configuration in the PUSCH configuration.
  • multiple CSI reporting configurations in the same CSI measurement configuration can be associated with different PUSCH configurations.
  • the CSI measurement configuration and the PUSCH configuration can also be associated through the PDCCH configuration.
  • the CSI measurement configuration may include an indication of the associated PDCCH configuration
  • the PUSCH configuration may also include the indication of the associated PDCCH configuration.
  • the network device adds a field indicating a PDCCH configuration in the CSI measurement configuration and the PUSCH configuration to indicate the associated PDCCH configuration.
  • the indication of the PDCCH configuration may be, for example, an identifier of the PDCCH configuration, or other information that may be used to indicate the PDCCH configuration.
  • condition h) may be further extended to that the associated PDCCH configuration indicated in the PUSCH configuration and the associated PDCCH configuration indicated in the CSI measurement configuration belong to the same PDCCH configuration group.
  • the above has described in detail the case where the associated PDCCH configuration indicated in the PUSCH configuration and the associated PDCCH configuration indicated in the PUCCH configuration belong to the same PDCCH configuration group.
  • the PUCCH configuration is replaced with the CSI measurement configuration.
  • the method for determining whether the CSI is related to the PUSCH configuration measurement configuration is similar to the method for determining whether the PUCCH configuration is related to the PUSCH configuration based on the condition vi) above. I won't repeat them here.
  • Condition i) is the same as condition vi) above. For brevity, we will not repeat them here.
  • the resource of the target PUCCH is determined by the CSI report configuration, and the PUSCH is the configured PUSCH, when the PUCCH is associated with the PUSCH, the PUCCH and the PUSCH can satisfy at least one of the conditions listed below:
  • the CSI measurement configuration to which the CSI report configuration of the PUCCH belongs (hereinafter referred to as the CSI measurement configuration of the PUCCH) and the ConfiguredGrant configuration of the PUSCH belong to the same BWP uplink dedicated parameter (BWP UL dedicated);
  • the CSI measurement configuration of the PUCCH and the PUSCH configuration of the PUSCH belong to the same BWP uplink dedicated parameters, and the identifier of the CSI measurement configuration is the same as the identifier configured by ConfiguredGrant;
  • the identifier of the BWP downlink dedicated parameter to which the CSI measurement configuration of the PUCCH belongs is the same as the identifier of the BWP uplink dedicated parameter to which the PUSCH's ConfiguredGrant belongs;
  • the identifier of the BWP downlink dedicated parameter to which the CSI measurement configuration of the PUCCH belongs is the same as the identifier of the BWP uplink dedicated parameter to which the ConfiguredGrant configuration of the PUSCH belongs, and the identifier of the CSI measurement configuration of the PUCCH is the same as the identifier of the PUSCH configuration of the PUSCH ;
  • the identifier of the CSI measurement configuration of the PUCCH is the same as the identifier of the BWP uplink dedicated parameter to which the ConfiguredGrant configuration of the PUSCH belongs;
  • the CSI measurement configuration of the PUCCH includes an indication of the configured Grant configuration of the PUSCH;
  • the PUSCH's ConfiguredGrant configuration includes an indication of the PUCCH's CSI measurement configuration
  • the transmission beam used to transmit the PUCCH and the transmission beam used to transmit the PUSCH belong to the same transmission beam group.
  • the conditions a) to h) listed above can be understood as one or more conditions that the associated PUCCH configuration and ConfiguredGrant configuration meet.
  • the conditions listed above are explained in detail below. Since the conditions for whether the PUCCH configuration of the PUCCH and the PUSCH configuration of the PUSCH are associated have been described in detail above, here only the PUSCH configuration is replaced by the ConfiguredGrant configuration, so it is similar to the above. For brevity, detailed descriptions of conditions a) to h) are omitted here.
  • PUCCH and PUSCH in the same serving cell configuration may be associated;
  • PUCCH and PUSCH in the same BWP configured by the same serving cell may be associated;
  • the PUCCH and PUSCH in the same BWP uplink dedicated parameter of the same BWP configured by the same serving cell may be associated.
  • the terminal device determines that the target PUCCH is associated with the PUSCH in step 430, then in step 440, the terminal device sends UCI through the PUSCH.
  • the terminal device may consider that the first network device and the second network device are the same network device. The terminal device may send UCI to the second network device through the PUSCH.
  • this application also provides a method that can be used to determine whether UCI can be transmitted over PUSCH.
  • the PUSCH may be a PUSCH scheduled by the PDCCH.
  • the terminal device may determine whether the UCI can be transmitted through the PUSCH according to the association between the type of the PDCCH used for scheduling the PUSCH and the PUCCH configuration or the association between the type of the PDCCH and the CSI reporting configuration.
  • the type of PDCCH can be understood as the type of DCI. Since the DCI can be carried on the PDCCH and sent to the terminal device, the DCI type can also be extended to the PDCCH type.
  • the protocol may predefine an association relationship between the PUCCH configuration and the type of the PDCCH.
  • PUCCH configuration 0 may be associated with one or more of the primary DCI, fast DCI, and first-level DCI
  • PUCCH configuration 1 may be associated with one or more of the secondary DCI, slow DCI, and second-level DCI.
  • PUCCH configuration 0 can be associated with primary DCI, fast DCI, and first-level DCI
  • PUCCH configuration 1 can be associated with secondary DCI, slow DCI, and second-level DCI
  • the PUCCH determined based on PUCCH configuration 0 is based on If a resource conflict occurs in the PUSCH scheduled by the primary DCI, the fast DCI, or the first-level DCI, the UCI that should be transmitted through the PUCCH can be transmitted through the PUSCH.
  • UCI that should have been transmitted through the PUCCH can be transmitted through the PUSCH.
  • the protocol may also predefine the association between the CSI reporting configuration and the type of the PDCCH.
  • CSI report configuration 0 may be associated with one or more of the primary DCI, fast DCI, and first-level DCI;
  • CSI report configuration 1 may be associated with one or more of the secondary DCI, slow DCI, and second-level DCI. Associated.
  • CSI report configuration 0 can be associated with the primary DCI, fast DCI, and first-level DCI
  • CSI report configuration 1 can be associated with the secondary DCI, slow DCI, and second-level DCI, if determined based on the CSI report configuration 0 If a resource conflict occurs between a PUCCH and a PUSCH scheduled based on the primary DCI, fast DCI, or first-level DCI, UCI that should have been transmitted through the PUCCH can be transmitted through the PUSCH.
  • UCI that should have been transmitted through the PUCCH can be transmitted through the PUSCH.
  • the protocol may also predefine the association relationship between the CSI measurement configuration and the type of the PDCCH.
  • CSI measurement configuration 0 may be associated with one or more of primary DCI, fast DCI, and first-level DCI;
  • CSI measurement configuration 1 may be associated with one or more of secondary DCI, slow DCI, and second-level DCI, or Multiple associations.
  • CSI measurement configuration 0 can be associated with the primary DCI, fast DCI, and first-level DCI
  • CSI measurement configuration 1 can be associated with the secondary DCI, slow DCI, and second-level DCI, if any of the CSI measurement configuration 0-based If a PUCCH determined by a CSI reporting configuration conflicts with a PUSCH scheduled based on the primary DCI, fast DCI, or first-level DCI, UCI that should have been transmitted through the PUCCH can be transmitted through the PUSCH.
  • the PUCCH determined based on any one of the CSI reporting configurations in CSI measurement configuration 1 conflicts with the PUSCH scheduled based on the secondary DCI, slow DCI, or second-level DCI, UCI that should have been transmitted through the PUCCH can be transmitted through the PUSCH. .
  • the DCI can be divided into a primary DCI and a secondary DCI.
  • the information included in the secondary DCI may be a subset of the information included in the primary DCI.
  • the secondary DCI only includes a part of the indication fields included in the primary DCI, that is, the primary DCI contains more indication information than the secondary DCI.
  • the primary DCI and the secondary DCI may contain different information.
  • the main DCI may be a DCI containing one or more specific parameters.
  • the specific parameters may include, for example, at least one of the following: a carrier indicator, a bandwidth indicator, a rate matching indicator, and a zero-power channel state information reference signal trigger.
  • the secondary DCI may be a DCI that does not include any one of the above specific parameters.
  • the secondary DCI is a DCI that can include at least one of the following: resource allocation, modulation coding method (MCS), redundant version (RV), new data indication (NDI), and HARQ process ID .
  • MCS modulation coding method
  • RV redundant version
  • NDI new data indication
  • HARQ process ID HARQ process ID
  • DCI can also be divided into first-level DCI and second-level DCI.
  • the first-level DCI may indicate whether the second-level DCI exists, and may further indicate a time-domain and / or frequency-domain location where the second-level DCI is located.
  • the DCI blindly detected by the terminal device includes the first-level DCI and the second-level DCI, it can be considered that the PDCCH configured on the PDCCH carrying the first-level DCI scheduling is configured as PDCCH configuration 0, and the PDCCH carrying the second-level DCI is based on The PDCCH configuration is PDCCH configuration 1.
  • DCI can be divided into fast DCI and slow DCI.
  • the frequency of fast DCI is higher than the frequency of slow DCI.
  • fast DCI may occur once per time slot
  • slow DCI may occur once in multiple time slots.
  • DCI can also be divided into DCIs in different formats, such as DCI format 1_0, DCI format 1_1, and so on.
  • DCI format 1_0 DCI format 1_0
  • DCI format 1_1 DCI format 1_1
  • the PDCCH based on the PDCCH carrying DCI format 1_0 is configured as PDCCH configuration 0
  • PDCCH based on the PDCCH carrying DCI format 1_1 is configured as PDCCH.
  • different PDCCH configurations can also be distinguished.
  • one DCI contains only a field of configuration information of a transport block (TB) (for example, it may include MCS, NDI, and RV), and another DCI contains a field of configuration information of 2 TBs.
  • TB transport block
  • the DCI blindly detected by the terminal device includes the same DCI format and DCIs with different configurations, it can be considered that the PDCCH configurations carrying DCIs with different configurations are based on different PDCCH configurations.
  • a DCI including only 1 TB may correspond to PDCCH configuration 1
  • a DCI including 2 TB may correspond to PDCCH configuration 0.
  • the specific process for the terminal device to send UCI through the PUSCH may be the same as that in the prior art. For brevity, detailed description of the specific process is omitted here.
  • the terminal device may also send other information than UCI through the PUSCH, such as uplink data.
  • step 440 includes: the terminal device sends UCI and uplink data through the PUSCH.
  • the terminal device determines in step 430 that the target PUCCH is not associated with the PUSCH, the terminal device does not send UCI through the PUSCH. For example, it waits for the next scheduled PUCCH to be sent or does not send, which is not limited in this application.
  • the fact that the terminal device does not send UCI through the PUSCH does not mean that the terminal device does not transmit other information through the PUSCH.
  • the terminal device can still send uplink data through the PUSCH.
  • the terminal device sends uplink data through the PUSCH.
  • the network device may know in advance whether the target PUCCH is sent to itself, or may know in advance whether the PUSCH is scheduled by itself. That is, the network device can know in advance that the target PUCCH is associated with the PUSCH. That is, the first network device and the second network device are the same network device.
  • the method 400 further includes: step 450, the second network device determines whether there is a resource overlap between the target PUCCH and the PUSCH. If there are overlapping resources, the second network device may determine that the terminal device may send UCI through the PUSCH. Corresponding to step 440, the second network device may receive UCI on the PUSCH. Optionally, the network device may also receive uplink data on the PUSCH. If there is no resource overlap, the second network device may determine that the terminal device will not send UCI through the PUSCH. Optionally, the second network device receives uplink data on the PUSCH.
  • the first network device and the second network device are different network devices.
  • the terminal device may not know that the UCI did not send UCI because the target PUCCH and PUSCH resources overlap. It may try to receive UCI on the PUCCH, but may not receive UCI . Therefore, the first network device may retransmit the last scheduled PDSCH or continue to wait for UCI.
  • the second network device because it does not know the existence of the target PUCCH, nor does it know that the resources of the target PUCCH and PUSCH overlap, it will still receive uplink data on the PUSCH.
  • the terminal device since the terminal device can determine that the PUCCH is not associated with the PUSCH, it can still receive uplink data on the PUSCH.
  • the terminal device may determine whether the PUCCH and the PUSCH are sent to the same network device based on whether the PUCCH and the PUSCH are associated. Therefore, UCI for the network device can be transmitted through the PUSCH, and UCI for other network devices can also be avoided from being transmitted on the PUSCH. Therefore, the network device may receive UCI on the PUSCH, and then determine whether it is necessary to retransmit the PDSCH and / or CSI.
  • the terminal device cannot determine whether the PUCCH is related to the PUSCH, it is also impossible to determine whether the PUCCH and the PUSCH are sent to the same network device (for example, the second network device described above).
  • the UCI sent to another network device (such as the first network device or other network device other than the second network device described above) is transmitted on the PUSCH, resulting in the second network device receiving the PUSCH when The uplink data transmitted on the PUSCH cannot be accurately parsed.
  • the network device can receive UCI on the PUSCH, so that it can make a reasonable decision based on the received UCI, and avoid waste of resources caused by unnecessary retransmissions. , Which is conducive to improving data transmission performance and improving user experience.
  • FIG. 5 is a schematic block diagram of a communication device according to an embodiment of the present application.
  • the communication device 1000 may include a communication unit 1100 and a processing unit 1200.
  • the communication device 1000 may correspond to the terminal device in the foregoing method embodiment.
  • the communication device 1000 may be a terminal device or a chip configured in the terminal device.
  • the communication device 1000 may correspond to the terminal device in the method 200 to the method 400 according to the embodiment of the present application, and the communication device 1000 may include a method for performing the method 200 in FIG. 2, the method 300 in FIG. 3, or the figure.
  • each unit in the communication device 1000 and the other operations and / or functions described above are respectively for implementing the corresponding process of the method 200 in FIG. 2, the method 300 in FIG. 3, or the method 400 in FIG. 4.
  • the communication unit 1100 may be used to execute step 220 in the method 200
  • the processing unit 1200 may be used to execute step 230 in the method 200.
  • the communication unit 1100 may be used to execute step 320 in the method 300, and the processing unit 1200 may be used to execute step 330 in the method 300.
  • the communication unit 1100 may be used to perform steps 420 and 440 in the method 400, and the processing unit 1200 may be used to perform steps 410 and 430 in the method 400.
  • the communication unit 1100 in the communication device 1000 may correspond to the transceiver 2020 in the terminal device 2000 shown in FIG. 6, and the processing unit 1200 in the communication device 1000 may Corresponds to the processor 2010 in the terminal device 2000 shown in FIG. 6.
  • the communication unit 1100 in the communication device 1000 may be an input / output interface.
  • the communication device 1000 may correspond to the network device in the foregoing method embodiment.
  • the communication device 1000 may be a network device or a chip configured in the network device.
  • the communication device 1000 may correspond to the network device in the foregoing method embodiment.
  • the communication device 1000 may be a network device or a chip configured in the network device.
  • the communication apparatus 1000 may correspond to the network device in the method 200 to the method 400 according to the embodiment of the present application.
  • the communication apparatus 1000 may include a method for performing the method 200 in FIG. 2, the method 300 in FIG. 3, or the diagram.
  • each unit in the communication device 1000 and the other operations and / or functions described above are respectively for implementing the corresponding process of the method 200 in FIG. 2, the method 300 in FIG. 3, or the method 400 in FIG. 4.
  • the communication unit 1100 may be used to execute step 220 in the method 200
  • the processing unit 1200 may be used to execute step 210 in the method 200.
  • the communication unit 1100 may be used to execute step 320 in the method 300
  • the processing unit 1200 may be used to execute step 310 in the method 300.
  • the communication unit 1100 may be used to execute steps 420 and 440 in the method 400, and the processing unit 1200 may be used to execute step 450 in the method 400.
  • the communication unit in the communication device 1000 is a transceiver 3200 that may correspond to the network device 3000 shown in FIG. 7, and the processing unit 1200 in the communication device 1000 may be Corresponds to the processor 3100 in the network device 3000 shown in FIG. 7.
  • the communication unit 1100 in the communication device 1000 may be an input / output interface.
  • FIG. 6 is a schematic structural diagram of a terminal device 2000 according to an embodiment of the present application.
  • the terminal device 2000 may be applied to the system shown in FIG. 1 to perform the functions of the terminal device in the foregoing method embodiment.
  • the terminal device 2000 includes a processor 2010 and a transceiver 2020.
  • the terminal device 2000 further includes a memory 2030.
  • the processor 2010, the transceiver 2002, and the memory 2030 can communicate with each other through an internal connection path to transfer control and / or data signals.
  • the memory 2030 is used to store a computer program
  • the processor 2010 is used to store the computer program from the memory 2030.
  • the computer program is called and run to control the transceiver 2020 to send and receive signals.
  • the terminal device 2000 may further include an antenna 2040 for sending uplink data or uplink control signaling output by the transceiver 2020 through a wireless signal.
  • the processor 2010 and the memory 2030 may be combined into a processing device, and the processor 2010 is configured to execute program codes stored in the memory 2030 to implement the foregoing functions.
  • the memory 2030 may also be integrated in the processor 2010 or independent of the processor 2010.
  • the processor 2010 may correspond to the processing unit in FIG. 4.
  • the above-mentioned transceiver 2020 may correspond to the communication unit in FIG. 5, and may also be referred to as a transceiver unit.
  • the transceiver 2020 may include a receiver (or receiver, or receiving circuit) and a transmitter (or transmitter, or transmitting circuit). The receiver is used for receiving signals, and the transmitter is used for transmitting signals.
  • the terminal device 2000 shown in FIG. 6 can implement various processes related to the terminal device in the method embodiments shown in FIG. 2 to FIG. 4. Operations and / or functions of each module in the terminal device 2000 are respectively implemented to implement corresponding processes in the foregoing method embodiments. For details, refer to the descriptions in the foregoing method embodiments. To avoid repetition, detailed descriptions are appropriately omitted here.
  • the above processor 2010 may be used to perform the actions implemented in the terminal device described in the previous method embodiment, and the transceiver 2020 may be used to execute the terminal device described in the previous method embodiment to send or receive from the network device to the network device. action.
  • the transceiver 2020 may be used to execute the terminal device described in the previous method embodiment to send or receive from the network device to the network device. action.
  • the above-mentioned terminal device 2000 may further include a power source 2050 for supplying power to various devices or circuits in the terminal device.
  • the terminal device 2000 may further include one or more of an input unit 2060, a display unit 2070, an audio circuit 2080, a camera 2090, and a sensor 2100.
  • the audio circuit A speaker 2082, a microphone 2084, and the like may also be included.
  • FIG. 7 is a schematic structural diagram of a network device according to an embodiment of the present application, and may be, for example, a structural schematic diagram of a base station.
  • the base station 3000 can be applied to the system shown in FIG. 1 and executes the functions of the network device in the foregoing method embodiment.
  • the base station 3000 may include one or more radio frequency units, such as a remote radio unit (RRU) 3100 and one or more baseband units (BBU) (also referred to as a digital unit). , Digital unit, DU) 3200.
  • the RRU 3100 may be referred to as a transceiver unit, and corresponds to the communication unit 1200 in FIG. 5.
  • the transceiver unit 3100 may also be referred to as a transceiver, a transceiver circuit, or a transceiver, etc., which may include at least one antenna 3101 and a radio frequency unit 3102.
  • the transceiver unit 3100 may include a receiving unit and a transmitting unit.
  • the receiving unit may correspond to a receiver (or a receiver or a receiving circuit), and the transmitting unit may correspond to a transmitter (or a transmitter or a transmitting circuit).
  • the RRU 3100 part is mainly used for transmitting and receiving radio frequency signals and converting radio frequency signals to baseband signals, for example, for sending instruction information to terminal equipment.
  • the BBU 3200 part is mainly used for baseband processing and controlling base stations.
  • the RRU 3100 and the BBU 3200 may be physically located together, or may be physically separated, that is, a distributed base station.
  • the BBU 3200 is a control center of a base station, and may also be called a processing unit, which may correspond to the processing unit 1100 in FIG. 5, and is mainly used to complete baseband processing functions, such as channel coding, multiplexing, modulation, spreading, and so on.
  • the BBU Processed Unit
  • the BBU may be used to control the base station to execute the operation procedure on the network device in the foregoing method embodiment, for example, to generate the foregoing instruction information and the like.
  • the BBU 3200 may be composed of one or more boards, and multiple boards may jointly support a wireless access network (such as an LTE network) of a single access system, or may separately support different access systems. Wireless access network (such as LTE network, 5G network or other networks).
  • the BBU 3200 further includes a memory 3201 and a processor 3202.
  • the memory 3201 is used to store necessary instructions and data.
  • the processor 3202 is configured to control a base station to perform necessary actions, for example, to control the base station to perform an operation procedure on a network device in the foregoing method embodiment.
  • the memory 3201 and the processor 3202 may serve one or more single boards. That is, the memory and processor can be set separately on each board. It is also possible that multiple boards share the same memory and processor. In addition, the necessary circuits can be set on each board.
  • the base station 3000 shown in FIG. 7 can implement each process related to the network device in the method embodiments in FIG. 2 to FIG. 4.
  • the operations and / or functions of each module in the base station 3000 are respectively to implement the corresponding processes in the foregoing method embodiments.
  • the above BBU 3200 can be used to perform the actions implemented by the network device described in the previous method embodiment, and the RRU 3100 can be used to perform the actions that the network device described in the previous method embodiment sends to or receives from the terminal device.
  • the RRU 3100 can be used to perform the actions that the network device described in the previous method embodiment sends to or receives from the terminal device.
  • An embodiment of the present application further provides a processing apparatus including a processor and an interface.
  • the processor may be configured to execute the method in the foregoing method embodiment.
  • the processing device may be a chip.
  • the processing device may be a field programmable gate array (FPGA), an application-specific integrated circuit (ASIC), or a system chip (SoC). It is a central processor (CPU), a network processor (NP), a digital signal processor (DSP), or a microcontroller (micro controller). (MCU), can also be a programmable controller (programmable logic device, PLD) or other integrated chips.
  • FPGA field programmable gate array
  • ASIC application-specific integrated circuit
  • SoC system chip
  • CPU central processor
  • NP network processor
  • DSP digital signal processor
  • micro controller microcontroller
  • MCU can also be a programmable controller (programmable logic device, PLD) or other integrated chips.
  • each step of the above method may be completed by an integrated logic circuit of hardware in a processor or an instruction in a form of software.
  • the steps of the method disclosed in combination with the embodiments of the present application may be directly implemented by a hardware processor, or may be performed by a combination of hardware and software modules in the processor.
  • the software module may be located in a mature storage medium such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory, or an electrically erasable programmable memory, a register, and the like.
  • the storage medium is located in a memory, and the processor reads the information in the memory and completes the steps of the foregoing method in combination with its hardware. To avoid repetition, it will not be described in detail here.
  • processor in the embodiment of the present application may be an integrated circuit chip and has a signal processing capability.
  • each step of the foregoing method embodiment may be completed by using an integrated logic circuit of hardware in a processor or an instruction in a form of software.
  • the above processors may be general purpose processors, digital signal processors (DSPs), application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs) or other programmable logic devices, discrete gate or transistor logic devices, and discrete hardware components .
  • DSPs digital signal processors
  • ASICs application specific integrated circuits
  • FPGAs field programmable gate arrays
  • a general-purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
  • the steps of the method disclosed in combination with the embodiments of the present application may be directly implemented by a hardware decoding processor, or may be performed by using a combination of hardware and software modules in the decoding processor.
  • the software module may be located in a mature storage medium such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory, or an electrically erasable programmable memory, a register, and the like.
  • the storage medium is located in a memory, and the processor reads the information in the memory and completes the steps of the foregoing method in combination with its hardware.
  • the memory in the embodiment of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory.
  • the non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (erasable PROM, EPROM), electrical memory Erase programmable read-only memory (EPROM, EEPROM) or flash memory.
  • the volatile memory may be a random access memory (RAM), which is used as an external cache.
  • RAM random access memory
  • DRAM dynamic random access memory
  • SDRAM synchronous dynamic random access memory
  • double SDRAM double SDRAM
  • DDR SDRAM double data rate synchronous dynamic random access memory
  • enhanced SDRAM enhanced SDRAM
  • SLDRAM synchronous connection dynamic random access memory
  • direct RAMbus RAM direct RAMbus RAM
  • the present application also provides a computer program product, the computer program product includes: computer program code, when the computer program code is run on a computer, the computer executes the operations shown in FIG. 2 to FIG. 4 The method of any one of the embodiments is shown.
  • the present application also provides a computer-readable medium, where the computer-readable medium stores program code, and when the program code runs on the computer, the computer executes the operations shown in FIG. 2 to FIG. 4. The method of any one of the embodiments is shown.
  • the present application further provides a system, which includes the foregoing one or more terminal devices and one or more network devices.
  • the computer program product includes one or more computer instructions.
  • the computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices.
  • the computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be from a website site, computer, server, or data center Transmission by wire (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.) to another website site, computer, server, or data center.
  • the computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, a data center, and the like that includes one or more available medium integration.
  • the usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, a magnetic tape), an optical medium (for example, a high-density digital video disc (DVD)), or a semiconductor medium (for example, a solid state disk (solid state disk) SSD)) and so on.
  • a magnetic medium for example, a floppy disk, a hard disk, a magnetic tape
  • an optical medium for example, a high-density digital video disc (DVD)
  • DVD high-density digital video disc
  • semiconductor medium for example, a solid state disk (solid state disk) SSD
  • the network device in each of the foregoing device embodiments corresponds exactly to the network device or terminal device in the terminal device and method embodiments, and the corresponding module or unit performs the corresponding steps, for example, the communication unit (transceiver) performs the receiving or
  • the step of sending, other than sending and receiving, may be performed by a processing unit (processor).
  • processor For the function of the specific unit, refer to the corresponding method embodiment. Among them, there may be one or more processors.
  • a component may be, but is not limited to, a process running on a processor, a processor, an object, an executable, a thread of execution, a program, and / or a computer.
  • an application running on a computing device and a computing device can be components.
  • One or more components can reside within a process and / or thread of execution and a component may be localized on one computer and / or distributed between two or more computers.
  • these components can execute from various computer readable media having various data structures stored thereon.
  • a component may, for example, be based on a signal having one or more data packets (e.g., data from two components that interact with another component between a local system, a distributed system, and / or a network, such as the Internet that interacts with other systems through signals) Communicate via local and / or remote processes.
  • data packets e.g., data from two components that interact with another component between a local system, a distributed system, and / or a network, such as the Internet that interacts with other systems through signals
  • the disclosed systems, devices, and methods may be implemented in other ways.
  • the device embodiments described above are only schematic.
  • the division of the unit is only a logical function division.
  • multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not implemented.
  • the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, which may be electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, may be located in one place, or may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the objective of the solution of this embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each of the units may exist separately physically, or two or more units may be integrated into one unit.
  • each functional unit may be implemented in whole or in part by software, hardware, firmware, or any combination thereof.
  • software When implemented in software, it may be implemented in whole or in part in the form of a computer program product.
  • the computer program product includes one or more computer instructions (programs).
  • programs When the computer program instructions (programs) are loaded and executed on a computer, the processes or functions according to the embodiments of the present application are wholly or partially generated.
  • the computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices.
  • the computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be from a website site, computer, server, or data center Transmission by wire (for example, coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (for example, infrared, wireless, microwave, etc.) to another website site, computer, server, or data center.
  • the computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, a data center, and the like that includes one or more available medium integration.
  • the usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, a magnetic tape), an optical medium (for example, a DVD), or a semiconductor medium (for example, a solid state disk (SSD)).
  • the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium.
  • the technical solution of this application is essentially a part that contributes to the existing technology or a part of the technical solution can be embodied in the form of a software product.
  • the computer software product is stored in a storage medium, including Several instructions are used to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method described in the embodiments of the present application.
  • the aforementioned storage media include: U disks, mobile hard disks, read-only memories (ROMs), random access memories (RAMs), magnetic disks or compact discs and other media that can store program codes .

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Quality & Reliability (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请提供了一种发送和接收UCI的方法以及通信装置。该方法建立了PUCCH与PUSCH之间的关联关系，使得终端设备可以在PUSCH与PUCCH发生资源重叠的情况下，可以确定哪些PUCCH上的UCI可以复用PUSCH的资源传输；网络设备可以在该PUSCH上接收UCI。由于网络设备可以预先知道哪些PUCCH和PUSCH是发送给自己的，因此能够对接收到的PUSCH上的信号进行解调译码，以成功地获取UCI。网络设备可以根据UCI做出合理的决策，有利于数据传输性能，提高用户体验。

Description

发送和接收上行控制信息的方法以及通信装置
本申请要求于2018年9月19日提交中国专利局、申请号为201811092245.6、申请名称为“发送和接收上行控制信息的方法以及通信装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及无线通信领域，并且更具体地，涉及发送和接收上行控制信息的方法以及通信装置。
背景技术
协作多点(coordination multiple point，CoMP)传输是一种用于解决小区间干扰问题并提升小区边缘用户吞吐量的方法。在上行传输中，网络设备可以预先为终端设备调度物理上行控制信道(physical uplink control channel，PUCCH)和物理上行共享信道(physical uplink share channel，PUSCH)。通常情况下，终端设备可以通过PUCCH向网络设备发送上行控制信息(uplink control information，UCI)，还可以通过PUSCH向网络设备发送上行数据。而当PUCCH和PUSCH的资源发生重叠时，终端设备可以将原本传输在PUCCH上的UCI中的部分或全部信息通过PUSCH来传输。
在有些场景下，如非理想回程(non ideal backhaul)场景，鉴于网络设备之间的通信时延较大，一种基于多个DCI的多站点调度的方案被提出。基于多个DCI的多站点调度方案支持两个或更多个网络设备分别通过各自发送的DCI为终端设备调度各自的PDSCH和PUSCH，进行数据传输。各网络设备可以在各自为终端设备配置的PUCCH上接收UCI，以获取对各自调度的PDSCH的混合自动重传(hybrid automatic repeat request，HARQ)信息和/或信道状态信息(channel state information，CSI)。
然而，网络设备对于终端设备而言是透明的。当某一PUCCH与PUSCH发生资源重叠时，终端设备并不知道该PUCCH与PUSCH是否是发送给同一网络设备的。当PUCCH是发送给网络设备#1的PUCCH，而PUSCH为网络设备#2调度的PUSCH时，若终端设备将PUCCH上的UCI放到PUSCH上传输，网络设备#2可能并不知道该PUSCH上传输由UCI，因此无法解析出UCI和PUSCH上传输的上行数据；而网络设备#1也接收不到该UCI。因此，终端设备可能需要重新发送未被成功接收的上行数据，而网络设备由于无法及时地获知UCI，也不能为数据传输做出合理的决策。因此可能会造成数据传输的性能下降，用户体验不好。
发明内容
本申请提供一种发送和接收UCI的方法以及通信装置，以期减少不必要的重传，提高资源利用率，提高传输性能。
第一方面，提供了一种发送上行控制信息的方法。该方法可以由终端设备执行，或者，也可以由配置于终端设备中的芯片执行，本申请对此不作限定。
具体地，该方法包括：确定PUSCH与PUCCH存在资源重叠，其中，该PUSCH由PDCCH调度，该PUCCH用于传输UCI；在该PUCCH与PDCCH关联的情况下，在该PUSCH上传输UCI。
可选地，在该PUCCH与PDCCH的配置参数不关联的情况下，不在该PUSCH上传输UCI。
也就是说，当PDCCH调度的PUSCH与PUCCH存在资源重叠时，可以基于PUCCH与PDCCH的配置参数是否存在关联来确定是否可通过PUSCH来传输UCI。当二者关联时，可通过该PUSCH来传输UCI；当二者不关联时，则不通过该PUSCH来传输UCI。
第二方面，提供了一种接收上行控制信息的方法。该方法可以由网络设备执行，或者，也可以由配置于网络设备中的芯片执行，本申请对此不作限定。
具体地，该方法包括：确定PUSCH与PUCCH存在资源重叠，其中，该PUSCH有PDCCH调度，该PUCCH用于传输UCI；在该PUSCH上接收UCI。
由于网络设备可以预先知道哪些PUCCH是发给自身的，哪些PUSCH是自身调度的。因此，网络设备可以预知哪些PUCCH可以通过PUSCH来传输UCI，从而可以在该PUSCH上接收UCI。
需要说明的是，通过PUSCH传输UCI可以包括：在PUSCH上传输UCI和上行数据；不通过PUSCH传输UCI可以包括：在PUSCH上传输上行数据，而不传输UCI。因此，当通过PUSCH来传输UCI时，可以称为PUSCH的资源复用。
其中，可通过PUSCH传输的UCI具体可以包括HARQ信息和中的至少一项。
基于上述技术方案，在PUCCH与PUSCH发生资源重叠的情况下，终端设备可以基于PUCCH与PUSCH之间是否关联来确定该PUCCH和PUSCH是否为发送给同一网络设备的。从而可以将针对该网络设备的UCI可以通过PUSCH传输，而避免将针对其他网络设备的UCI也放在该PUSCH上传输。因此，网络设备可以在该PUSCH上接收到UCI，进而确定是否需要重传PDSCH和/或CSI。
相反，如果终端设备无法确定PUCCH与PUSCH之间是否关联，也就无法确定该PUCCH和PUSCH是否为发送给同一网络设备(例如记作网络设备#1)的，就有可能将本该发送给另一网络设备(例如记作网络设备#2)的UCI放在PUSCH上传输，导致网络设备#1在接收到PUSCH的时候无法准确地解析出PUSCH上传输的上行数据。
而在本申请实施例中，由于终端设备可以在于PUCCH关联PUSCH上传输UCI，网络设备也可以在相应的资源上接收UCI，不会造成因双方确定的资源不一致网络设备接收不到UCI的情况。由于网络设备可以接收到UCI，也就可以基于接收到的UCI做出合理的决策。从而避免不必要的重传带来的资源浪费，有利于提高数据传输性能，提高用户体验。
在本申请实施例中，PUCCH与PDCCH关联可以包括：PUCCH与PDCCH的配置参数关联。其中，PDCCH的配置参数可以为PDCCH配置或下行控制参数。
结合第一方面或第二方面，在某些可能的实现方式中，PUCCH由PUCCH配置确定，PUCCH配置与PDCCH配置关联。
其中，PUCCH配置可用于确定PUCCH，例如，PUCCH的时频资源。当PUCCH配置与PDCCH配置关联时，可以认为PUCCH与PDCCH配置关联。
可选地，PUCCH配置中包含PDCCH配置的指示。
即，可以通过显式的方式在PUCCH配置中指示关联的PDCCH配置。
可选地，PUCCH配置与PDCCH配置为同一带宽部分BWP配置，且PUCCH配置所属的带宽部分BWP上行专用参数的标识与PDCCH配置所属的BWP下行专用参数的标识相同。
可选地，PUCCH配置与PDCCH配置属于同一服务小区配置。
即，可以通过隐式的方式指示关联的PUCCH配置与PDCCH配置。
结合第一方面或第二方面，在某些可能的实现方式中，PUCCH的资源由CSI上报配置确定，CSI上报配置与PDCCH配置关联。
其中，CSI上报配置可用于确定PUCCH。具体地，CSI上报配置和激活的BWP可以用于确定PUCCH的时频资源。当CSI上报配置与PDCCH配置关联时可以认为PUCCH与PDCCH配置关联。
可选地，CSI上报配置中包含PDCCH配置的指示。
即，可以通过显式的方式在CSI上报配置中指示关联的PDCCH配置。每个CSI上报配置可以与一个PDCCH配置关联。
可选地，CSI上报配置所属的CSI测量配置中包含PDCCH配置的指示。
即，可以通过显式的方式在CSI测量配置中指示关联的PDCCH配置。由于每个CSI测量配置中可以包括一个或多个CSI上报配置，当一个CSI测量配置与一个PDCCH配置关联时，该CSI测量配置中的一个或多个CSI上报配置可以由同一个PDCCH配置关联。
可选地，CSI上报配置所属的CSI测量配置与PDCCH配置属于同一服务小区，且CSI测量配置的标识与PDCCH配置所属的BWP下行专用参数的标识相同。
可选地，CSI上报配置所属的CSI测量配置与PDCCH配置属于同一服务小区配置中的同一BWP专用参数。
可选地，CSI上报配置所属的CSI测量配置与PDCCH配置属于同一服务小区配置。
即，可以通过隐式的方式指示关联的CSI测量配置与PDCCH配置，从而可以确定关联的CSI上报配置与PDCCH配置。
结合第一方面或第二方面，在某些可能的实现方式中，所述PUCCH取自PUCCH配置中的多个PUCCH资源，每个PUCCH资源由一套PUCCH资源配置参数配置，PUCCH资源配置参数中包括所关联的PDCCH配置的指示。
即，可以通过显式的方式为每个PUCCH资源配置一个关联的PDCCH配置。
第三方面，提供了一种配置方法。该方法可以由网络设备执行，或者，也可以由配置于网络设备中的芯片执行。
具体地，该方法包括：生成第一配置信息，该第一配置信息用于指示关联的PUCCH配置与PDCCH配置；发送第一配置信息。
第四方面，提供了一种配置方法。该方法可以由终端设备执行，或者，也可以由配置于终端设备中的芯片执行。
具体地，该方法包括：接收第一配置信息，第一配置信息用于指示关联的物理上行控 制信道PUCCH配置与物理下行控制信道PDCCH配置；根据第一配置信息确定关联的PUCCH配置与PDCCH配置。
基于上述技术方案，终端设备可以基于PUCCH配置与PDCCH配置之间的关联关系，确定哪些PDCCH配置和PUCCH配置对应于同一网络设备，从而可以根据网络设备的指示确定PUCCH的资源来传输UCI。而网络设备也可以在相应的资源上接收UCI，不会造成因双方确定的资源不一致网络设备接收不到UCI的情况。因此，通过引入上述第一配置信息，可以方便终端设备与网络设备之间的通信，有利于提高传输性能，提高用户体验。
结合第三方面或第四方面，在某些可能的实现方式中，该第一配置信息为PUCCH配置，该PUCCH配置中包括PDCCH配置的指示。
即，在PUCCH配置中显式地指示所关联的PDCCH配置。
结合第三方面或第四方面，在某些可能的实现方式中，该第一配置信息为PDCCH配置，该PDCCH配置中包括PUCCH配置的指示。
即，在PDCCH配置中显式地指示所关联的PUCCH配置。
结合第三方面或第四方面，在某些可能的实现方式中，该第一配置信息为服务小区配置，服务小区配置中包括一组或多组BWP上行专用参数以及一组或多组BWP下行专用参数，每组BWP上行专用参数包括一个PUCCH配置，每组BWP下行专用参数包括一个PDCCH配置；其中，关联的PUCCH配置与PDCCH配置为同一BWP配置，且PUCCH配置所属的BWP上行专用参数的标识与PDCCH配置所属的BWP下行专用参数的标识相同。
结合第三方面或第四方面，在某些可能的实现方式中，该第一配置信息为服务小区配置，该服务小区配置中包括一组或多组BWP上行专用参数以及一组或多组BWP下行专用参数，每组BWP上行专用参数包括一个或多个PUCCH配置，每组BWP下行专用参数包括一个或多个PDCCH配置；其中，关联的PUCCH配置与PDCCH配置为同一BWP配置，PUCCH配置所属的BWP上行专用参数的标识与PDCCH配置所属的BWP下行专用参数的标识相同，且PUCCH配置的标识与PDCCH配置的标识相同。
结合第三方面或第四方面，在某些可能的实现方式中，该第一配置信息为服务小区配置，关联的PUCCH配置与PDCCH配置属于同一服务小区配置。
即，通过隐式的方式指示关联的PUCCH配置与PDCCH配置。
第五方面，提供了一种配置方法。该方法可以由网络设备执行，或者，也可以由配置于网络设备中的芯片执行。
具体地，该方法包括：生成第二配置信息，该第二配置信息用于指示关联的信道状态信息CSI上报配置与物理下行控制信道PDCCH配置；发送该第二配置信息。
第六方面，提供了一种配置方法。该方法可以由网络设备执行，或者，也可以由配置于网络设备中的芯片执行。
具体地，该方法包括：接收第二配置信息，该第二配置信息用于指示关联的信道状态信息CSI上报配置与物理上行共享信道PUSCH配置；根据该第二配置信息确定关联的CSI上报配置与PDCCH配置。
基于上述技术方案，终端设备可以基于CSI上报配置与PDCCH配置之间的关联关系，确定哪些CSI上报配置和PDCCH配置对应于同一网络设备，从而可以根据网络设备的指 示确定PUCCH的资源来传输UCI。而网络设备也可以在相应的资源上接收UCI，不会造成因双方确定的资源不一致网络设备接收不到UCI的情况。因此，通过引入上述第二配置信息，有利于提高传输性能，提高用户体验。
结合第五方面或第六方面，在某些可能的实现方式中，该第二配置信息为CSI上报配置，该CSI上报配置中包括PDCCH配置的指示。
即，在CSI上报配置中显式地指示所关联的PDCCH配置。
结合第五方面或第六方面，在某些可能的实现方式中，该第二配置信息为CSI测量配置，该CSI测量配置用于配置包括CSI上报配置在内的一个或多个CSI上报配置，该CSI测量配置中包括PDCCH配置的指示。
即，在CSI测量配置中显式地指示所关联的PDCCH配置。由于CSI测量配置可以包括一个或多个CSI上报配置，当CSI测量配置与一个PDCCH配置关联时，该CSI测量配置中的一个或多个CSI可以与同一个PDCCH配置关联。
结合第五方面或第六方面，在某些可能的实现方式中，该第二配置信息为服务小区配置，该服务小区配置中包括一个或多个CSI测量配置以及一组或多组BWP下行专用参数，CSI测量配置包括一个或多个CSI上报配置，BWP下行专用参数包括一个或多个PDCCH配置；其中，该CSI上报配置所属的CSI测量配置的标识与关联的PDCCH配置所属的BWP下行专用参数的标识相同。
结合第五方面或第六方面，在某些可能的实现方式中，该第二配置信息为服务小区配置，该服务小区配置中包括一组或多组BWP专用参数，每组BWP专用参数包括PDCCH配置的指示和CSI上报配置的指示。
结合第五方面或第六方面，在某些可能的实现方式中，该第二配置信息为服务小区配置，关联的CSI测量配置与PDCCH配置属于同一服务小区配置，每个CSI测量配置包括一个或多个CSI上报配置。
即，通过隐式的方式指示关联的CSI上报配置与PDCCH配置。
第七方面，提供了一种通信装置，包括用于执行第一、第四或第六方面以及第一、第四或第六方面中任一种可能实现方式中的方法的各个模块或单元。
第八方面，提供了一种通信装置，包括处理器。该处理器与存储器耦合，可用于执行存储器中的指令，以实现上述第一、第四或第六方面以及第一、第四或第六方面中任一种可能实现方式中的方法。可选地，该通信装置还包括存储器。可选地，该通信装置还包括通信接口，处理器与通信接口耦合。
在一种实现方式中，该通信装置为终端设备。当该通信装置为终端设备时，所述通信接口可以是收发器，或，输入/输出接口。
在另一种实现方式中，该通信装置为配置于终端设备中的芯片。当该通信装置为配置于终端设备中的芯片时，所述通信接口可以是输入/输出接口。
可选地，所述收发器可以为收发电路。可选地，所述输入/输出接口可以为输入/输出电路。
第九方面，提供了一种通信装置，包括用于执行第二、第三或第五方面以及第二、第三或第五方面中任一种可能实现方式中的方法的各个模块或单元。
第十方面，提供了一种通信装置，包括处理器。该处理器与存储器耦合，可用于执行 存储器中的指令，以实现上述第二、第三或第五方面以及第二、第三或第五方面中任一种可能实现方式中的方法。可选地，该通信装置还包括存储器。可选地，该通信装置还包括通信接口，处理器与通信接口耦合。
在一种实现方式中，该通信装置为网络设备。当该通信装置为网络设备时，所述通信接口可以是收发器，或，输入/输出接口。
在另一种实现方式中，该通信装置为配置于网络设备中的芯片。当该通信装置为配置于网络设备中的芯片时，所述通信接口可以是输入/输出接口。
可选地，所述收发器可以为收发电路。可选地，所述输入/输出接口可以为输入/输出电路。
第十一方面，提供了一种处理器，包括：输入电路、输出电路和处理电路。所述处理电路用于通过所述输入电路接收信号，并通过所述输出电路发射信号，使得所述处理器执行第一至第六方面以及第一至第六方面任一种可能实现方式中的方法。
在具体实现过程中，上述处理器可以为芯片，输入电路可以为输入管脚，输出电路可以为输出管脚，处理电路可以为晶体管、门电路、触发器和各种逻辑电路等。输入电路所接收的输入的信号可以是由例如但不限于接收器接收并输入的，输出电路所输出的信号可以是例如但不限于输出给发射器并由发射器发射的，且输入电路和输出电路可以是同一电路，该电路在不同的时刻分别用作输入电路和输出电路。本申请实施例对处理器及各种电路的具体实现方式不做限定。
第十二方面，提供了一种处理装置，包括处理器和存储器。该处理器用于读取存储器中存储的指令，并可通过接收器接收信号，通过发射器发射信号，以执行第一方面或第二方面以及第一至第六方面以及第一至第六方面任一种可能实现方式中的方法。
可选地，所述处理器为一个或多个，所述存储器为一个或多个。
可选地，所述存储器可以与所述处理器集成在一起，或者所述存储器与处理器分离设置。
在具体实现过程中，存储器可以为非瞬时性(non-transitory)存储器，例如只读存储器(read only memory，ROM)，其可以与处理器集成在同一块芯片上，也可以分别设置在不同的芯片上，本申请实施例对存储器的类型以及存储器与处理器的设置方式不做限定。
应理解，相关的数据交互过程例如发送指示信息可以为从处理器输出指示信息的过程，接收能力信息可以为处理器接收输入能力信息的过程。具体地，处理输出的数据可以输出给发射器，处理器接收的输入数据可以来自接收器。其中，发射器和接收器可以统称为收发器。
上述第十二方面中的处理装置可以是一个芯片，该处理器可以通过硬件来实现也可以通过软件来实现，当通过硬件实现时，该处理器可以是逻辑电路、集成电路等；当通过软件来实现时，该处理器可以是一个通用处理器，通过读取存储器中存储的软件代码来实现，该存储器可以集成在处理器中，可以位于该处理器之外，独立存在。
第十三方面，提供了一种计算机程序产品，所述计算机程序产品包括：计算机程序(也可以称为代码，或指令)，当所述计算机程序被运行时，使得计算机执行上述第一至第六方面以及第一至第六方面中任一种可能实现方式中的方法。
第十四方面，提供了一种计算机可读介质，所述计算机可读介质存储有计算机程序(也可以称为代码，或指令)当其在计算机上运行时，使得计算机执行上述第一至第六方面以及第一至第六方面中任一种可能实现方式中的方法。
第十五方面，提供了一种通信系统，包括前述的网络设备和终端设备。
附图说明
图1是适用于本申请实施例的的方法的通信系统的示意图；
图2是本申请实施例提供的发送和接收配置信息的方法的示意性流程图；
图3是本申请实施例提供的发送和接收配置信息的方法的示意性流程图；
图4是本申请实施例提供的发送和接收上行控制信息的方法的示意性流程图；
图5是本申请实施例提供的通信装置的示意性框图；
图6是本申请实施例提供的终端设备的结构示意图；
图7是本申请实施例提供的网络设备的结构示意图。
具体实施方式
下面将结合附图，对本申请中的技术方案进行描述。
本申请实施例的技术方案可以应用于各种通信系统，例如：全球移动通信(global system for mobile communications，GSM)系统、码分多址(code division multiple access，CDMA)系统、宽带码分多址(wideband code division multiple access，WCDMA)系统、通用分组无线业务(general packet radio service，GPRS)、长期演进(long term evolution，LTE)系统、LTE频分双工(frequency division duplex，FDD)系统、LTE时分双工(time division duplex，TDD)、通用移动通信系统(universal mobile telecommunication system，UMTS)、全球互联微波接入(worldwide interoperability for microwave access，WiMAX)通信系统、未来的第五代(5th generation，5G)系统或新无线(new radio，NR)等。
应理解，该通信系统中的网络设备可以是任意一种具有无线收发功能的设备或可设置于该设备的芯片，该设备包括但不限于：演进型节点B(evolved Node B，eNB)、无线网络控制器(Radio Network Controller，RNC)、节点B(Node B，NB)、基站控制器(Base Station Controller，BSC)、基站收发台(Base Transceiver Station，BTS)、家庭基站(例如，Home evolved NodeB，或Home Node B，HNB)、基带单元(BaseBand Unit，BBU)，无线保真(Wireless Fidelity，WIFI)系统中的接入点(Access Point，AP)、无线中继节点、无线回传节点、传输点(transmission point，TP)或者发送接收点(TRP)等，还可以为5G，如NR，系统中的gNB，或，传输点(TRP或TP)，5G系统中的基站的一个或一组(包括多个天线面板)天线面板，或者，还可以为构成gNB或传输点的网络节点，如基带单元(BBU)，或，分布式单元(distributed unit，DU)等。
在一些部署中，gNB可以包括集中式单元(centralized unit，CU)和DU。gNB还可以包括射频单元(radio unit，RU)。CU实现gNB的部分功能，DU实现gNB的部分功能，比如，CU实现无线资源控制(radio resource control，RRC)，分组数据汇聚层协议(packet data convergence protocol，PDCP)层的功能，DU实现无线链路控制(radio link control，RLC)、媒体接入控制(media access control，MAC)和物理(physical，PHY) 层的功能。由于RRC层的信息最终会变成PHY层的信息，或者，由PHY层的信息转变而来，因而，在这种架构下，高层信令，如RRC层信令或PHCP层信令，也可以认为是由DU发送的，或者，由DU+RU发送的。可以理解的是，网络设备可以为CU节点、或DU节点、或包括CU节点和DU节点的设备。此外，CU可以划分为接入网RAN中的网络设备，也可以将CU划分为核心网CN中的网络设备，在此不做限制。
还应理解，该通信系统中的终端设备也可以称为用户设备(user equipment，UE)、接入终端、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、终端、无线通信设备、用户代理或用户装置。本申请的实施例中的终端设备可以是手机(mobile phone)、平板电脑(Pad)、带无线收发功能的电脑、虚拟现实(Virtual Reality，VR)终端设备、增强现实(Augmented Reality，AR)终端设备、工业控制(industrial control)中的无线终端、无人驾驶(self driving)中的无线终端、远程医疗(remote medical)中的无线终端、智能电网(smart grid)中的无线终端、运输安全(transportation safety)中的无线终端、智慧城市(smart city)中的无线终端、智慧家庭(smart home)中的无线终端等等。本申请的实施例对应用场景不做限定。
为便于理解本申请实施例，首先对本申请中涉及的几个术语做简单说明。
1、上行控制信息(UCI)：可以包括信道状态信息(channel state information，CSI)、混合自动重传请求(hybrid automatic repeat request，HARQ)信息、上行调度请求(scheduling request，SR)中的一项或多项。
其中，CSI可以包括预编码矩阵指示(precoding matrix indicator，PMI)、秩指示(rank indication，RI)、信道质量指示(channel quality indicator，CQI)、CSI-RS资源指示信息(CSI-RS resource indication，CRI)中的一项或多项。基于不同的时域行为，CSI还可以分为周期(periodic)CSI、半持续(semi-persistent)和非周期(aperiodic)CSI。
HARQ信息也可以称为HARQ-确认(acknowledgement，ACK)信息。HARQ信息可以包括针对一个或多个PDSCH反馈的ACK或(negative acknowledgment，NACK)。其中，ACK可表示PDSCH被成功接收，且PDSCH中的数据被成功解码；NACK可表示PDSCH未被成功接收，或PDSCH中的数据未被成功解码。网络设备可以基于终端设备反馈的NACK进行数据重传。
下文中主要针对可以通过PUSCH传输的UCI来描述本申请实施例，该UCI例如可以包括HARQ信息和/或CSI。其中，CSI可以包括周期CSI和半持续CSI。应理解，下文中仅以UCI中包括HARQ信息和/或CSI为例来详细说明本申请实施例提供的方法，但这不应对本申请构成任何限定。本申请对于能够通过PUSCH传输的UCI中的具体内容不作限定。例如，本申请并不排除在未来的协议中规定可以将SR放在PUSCH上传输的可能。
2、物理上行控制信道(PUCCH)：可用于传输UCI。基于UCI中包含的内容，用于传输UCI的PUCCH(为便于区分，下文中将用于传输UCI的PUCCH记作目标PUCCH)的资源的确定方式也可能不同。
在本申请实施例中，当目标PUCCH与PUSCH的资源未发生重叠的情况下，终端设备可以通过目标PUCCH来传输UCI；当目标PUCCH与PUSCH的资源发生重叠的情况下，终端设备可以进一步确定目标PUCCH与PUSCH是否关联，并在关联的情况下通过PUSCH来发送UCI中的部分或全部信息。
其中，目标PUCCH与PUSCH关联可以是指，目标PUCCH与PUSCH是发送给同一网络设备的PUCCH和PUSCH。应理解，目标PUCCH与PUSCH是发送给同一网络设备的PUCCH和PUSCH，只是目标PUCCH与PUSCH关联的一种可能的形式，而不应对本申请构成任何限定，本申请实施例包括但不限于此。
在一种可能的设计中，用于确定目标PUCCH的资源的PUCCH配置(PUCCH config)与用于调度PUSCH的PDCCH的PDCCH配置(PDCCH config)可以是基于同一网络设备而配置的。或者说，关联的PUCCH配置与PDCCH配置可以对应于同一网络设备。
在另一种可能的设计中，用于确定目标PUCCH的资源的CSI上报配置(CSI-report config)与用于调度PUSCH的PDCCH的PDCCH配置可以是基于同一网络设备而配置的。或者说，关联的CSI上报配置与PDCCH配置可以对应于同一网络设备。
3、服务小区配置(serving cell config)：可用于为终端设备配置服务小区。网络设备可以通过高层参数，如服务小区配置控制元素(ServingCellConfig information element)，为终端设备配置服务小区。
服务小区配置中可以包括一组或多组带宽部分(bandwidth part，BWP)下行参数、上行配置(uplink config)和CSI测量配置(CSI-MeasConfig)。上行配置中可以包括一个或多个BWP上行参数。每组BWP下行参数可以是为一个BWP配置的，例如，可以在BWP下行参数中指示BWP的ID。每组BWP上行参数也可以是为一个BWP配置的，例如，可以在BWP下行参数中指示BWP的ID。每组BWP下行参数可以包括BWP下行专用(downlink dedicated，DL dedicated)参数和BWP下行公共(common)参数(DL common)，其中BWP下行专用参数具体可包括PDCCH配置和PDSCH配置。每组BWP上行参数可以包括BWP上行专用参数(uplink dedicated，UL dedicated)和BWP上行公共参数(UP common)，其中BWP上行专用参数具体可包括PUCCH配置和PUSCH配置。此外，CSI测量配置中可以包括一个或多个CSI上报配置。
需要说明的是，公共参数可以理解为是小区级别(cell specific)的参数，专用参数可以理解为UE级别的参数。其中，BWP上行专用参数在NR协议中的体现可以是BWP-UplinkDedicated，BWP下行专用参数在NR协议中的体现可以是BWP-DownlinkDedicated。
4、带宽部分(BWP)：由于NR中同一小区中不同终端设备的发射或者接收能力可能是不同的，系统可以为每个终端设备配置相应的带宽，这一部分配置给终端设备的带宽称为BWP，终端设备在自己的BWP上传输。BWP可以是载波上一组连续的频域资源，不同的BWP可以占用的频域资源可以部分重叠，也可以互不重叠。不同的BWP占用的频域资源的带宽可以相同，也可以不同，本申请对此不作限定。
5、PUCCH配置：可以基于每个BWP配置UE级别的PUCCH参数。例如，PUCCH配置中可以包括PUCCH资源集(PUCCH resource set)的ID以及PUCCH资源的ID等参数。PUCCH配置例如可以通过高层参数中的PUCCH配置控制元素(PUCCH-Config information element，PUCCH-Config IE)配置。该PUCCH-Config IE中例如可以包括资源集增加状态列表(resourceSetToAddModList)和资源集释放列表(resourceSetToReleaseList)。各列表中可以包括一个或多个PDCCH资源集的ID，每个PDCCH资源集中可以包括一个或多个PDCCH资源。该PUCCH-config IE中例如还可以 包括资源增加状态列表(resourceToAddModList)和资源释放列表(resourceToReleaseList)。各列表中可以包括一个或多个PDCCH资源的ID。
PUCCH配置中还可以进一步配置每个PUCCH资源的时域位置和频域位置。事实上，一个或多个网络设备可以通过各自的PUCCH配置为终端设备配置一个PUCCH资源池，该资源池中包括多个PUCCH资源。每个网络设备为终端设备配置的PUCCH资源均取自该PUCCH资源池。换句话说，PUCCH资源池为各网络设备为同一终端设备配置的PUCCH资源的全集，每个网络设备为终端设备配置的PUCCH资源可以是该PUCCH资源池的子集或全集。本申请对此不作限定。终端设备可以根据一个或多个PUCCH配置确定相应的PUCCH资源池。
当UCI仅包含HARQ信息时，终端设备可以根据UCI的长度从上述资源集添加状态列表中选择一个PUCCH资源集，并可基于网络设备所指示的PUCCH resource indicator从该PUCCH资源集中确定目标PUCCH的资源。换句话说，当UCI为HARQ信息时，终端设备可以基于PUCCH配置确定目标PUCCH的资源。
此外，PUCCH配置还可用于为多个CSI配置PUCCH的资源。该PUCCH-Config IE中例如可以包括多个CSI-PUCCH资源列表(multi-CSI-PUCCH-ResourceList)，该列表中例如可以包括两个PUCCH资源。
当UCI仅包含多个CSI时，终端设备可以根据UCI的长度，从该multi-CSI-PUCCH-ResourceList中确定目标PUCCH的资源。
6、CSI上报配置：可用于为周期CSI或半持续(semi-persistent)CSI的上报配置资源。CSI上报配置例如可以通过高层参数中的CSI-ReportConfig IE配置。该CSI-ReportConfig IE中例如可以包括用于传输半持续CSI的PUCCH的资源以及用于传输周期CSI的PUCCH的资源。该CSI-ReportConfig IE包括PUCCH-CSI资源列表(pucch-CSI-ResourceList)，该PUCCH的资源具体可以通过PUCCH资源的标识指示。
当UCI仅包含一个周期CSI或半持续CSI时，终端设备例如可以根据CSI上报配置和物理层信令(如DCI)中所激活的BWP确定目标PUCCH的资源。换句话说，当UCI仅包含一个CSI时，终端设备至少可以基于CSI上报配置确定目标PUCCH的资源。
此外，CSI上报配置还可用于配置上报量(report quantity)，具体可用于指示在所上报的CSI中需要上报哪些信息，CSI中上报的信息例如可以包括但不限于CRI、RI、PMI和CQI等。
7、CSI测量配置(CSI-measurement config)：可用于配置CSI-RS资源以及确定CSI上报所使用的PUCCH。网络设备可以通过CSI测量配置为一个终端设备配置一个或多个CSI上报配置。CSI测量配置例如可以通过高层参数中的CSI-MeasConfig IE配置。该CSI-MeasConfig IE中例如可以包括CSI上报配置增加状态列表(csi-ReportConfigToAddModList)和CSI上报配置释放列表(csi-ReportConfigToReleaseList)。各列表中包括一个或多个CSI上报配置。
8、物理上行共享信道(PUSCH)：可用于传输上行数据，也可以用于传输UCI。PUSCH可以是由网络设备调度，如通过PDCCH中的DCI调度，这种调度方式可以称为动态授权(dynamic grant)。PUSCH也可以是配置授权(configured grant)。其中配置授权可以全RRC配置的上行授权(fully RRC-configured UL grant)，这种授权方式可以称为类型1配 置授权的PUSCH传输(Type 1 PUSCH transmissions with a configured grant)，也可以是需要PDCCH触发的配置调度，这种授权方式可以称为类型2配置授权的PUSCH传输(Type 2 PUSCH transmissions with a configured grant)。应理解，上文列举的PUSCH的授权方式仅为示例，本申请对于PUSCH的授权方式不作限定。
若网络设备通过DCI来调度PUSCH，网络设备例如可以通过DCI格式(format)0_0或DCI format 0_1来调度PUSCH，在DCI中指示PUSCH的时域和频域位置。
若PUSCH为配置授权(configured grant)的PUSCH，网络设备例如可以通过BWP上行专用参数为配置授权的PUSCH配置资源，例如通过高层参数中的配置授权配置控制元素(ConfiguredGrantConfig IE)配置。
9、PUSCH配置：可以基于每个BWP配置UE级别的PUSCH参数。PUSCH配置例如可以通过高层参数中的PUSCH-Config IE配置。PUSCH-Config IE中配置的参数例如可以包括数据的扰码标识、解调参考信号(demodulation reference signal，DMRS)类型、功率控制等。当终端设备基于网络设备的调度确定了PUSCH的资源之后，还可以进一步基于PUSCH配置中的参数发送PUSCH。
10、PDCCH配置：可以基于每个小区(cell)中的每个BWP配置PDCCH参数，例如，控制资源集(control resource set，CORESET)、搜索空间(search space)以及其他可用于盲检测PDCCH的参数。PDCCH配置例如可以通过高层参数中的PDCCH-config IE配置。该PDCCH-config IE中例如可以包括控制资源集增加状态列表(controlResourceSet ToAddModList)和控制资源集释放列表(controlResourceSetToReleaseList)。各列表中可以包括一个或多个控制资源集的ID。该PDCCH-config IE中例如还可以包括搜索空间增加状态列表(searchSpaceToAddModList)和搜索空间释放列表(searchSpaceToReleaseList)。各列表中可以包括一个或多个搜索空间的ID。
在本申请实施例中，对于终端设备而言，PDCCH的PDCCH配置可以理解为接收该PDCCH时所基于的PDCCH配置，或者说，终端设备在由该PDCCH配置确定的搜索空间中盲检PDCCH；对于网络设备而言，PDCCH的PDCCH配置可以理解为发送该PDCCH时所基于的PDCCH配置，或者说，网络设备在由该PDCCH配置所确定的搜索空间中的部分资源上发送PDCCH。
11、探测参考信号(sounding reference signal，SRS)配置：可以用于配置SRS的传输。SRS配置可用于定义SRS资源列表和SRS资源集列表。每个SRS资源集可以包括一个或多个SRS资源。SRS配置可以通过高层参数中的SRS-config IE配置。该SRS-config IE中例如可以包括SRS资源集增加状态列表(srs-ResourceSetToAddModList)和SRS资源集释放列表(srs-ResourceSetToReleaseList)。各列表中可以包括一个或多个SRS资源集的ID，每个SRS资源集可以包括一个或多个SRS资源。该SRS-config IE中例如还可以包括SRS资源增加状态列表(srs-ResourceToAddModList)和SRS资源释放列表(srs-ResourceToReleaseList)。各列表中可以包括一个或多个SRS资源的ID。
12、空间关系(spatial relation，SR)：也可以称为上行传输配置指示(uplink transmission configuration indicator，UL TCI)。空间关系可以用于确定上行信号的发射波束(beam)。该空间关系可以由波束训练确定。用于波束训练的参考信号例如可以是上行参考信号，如探测参考信号(sounding reference signal，SRS)，也可以是下行参考信号，如同步信号块 (synchronization signal block，SSB)或信道状态信息参考信号(channel state information reference signal，CSI-RS)。
每个空间关系可以包括服务小区的索引(index)、BWP的标识(BWP ID)和参考信号资源标识。其中参考信号资源标识例如可以为以下任意一项：SSB资源索引(SSB resource indicator，SSBRI)、非零功率CSI-RS参考信号资源标识(NZP-CSI-RS-ResourceId)或SRS资源标识(SRS-ResourceId)。其中，SSB资源标识也可以称为SSB标识(SSB index)。
其中，服务小区的索引、BWP ID以及参考信号资源标识指的是在波束训练过程中所使用的参考信号资源以及所对应的服务小区和BWP。一个空间关系用于确定一个发送波束，也就是一个服务小区的索引、一个BWP ID和一个参考信号资源标识可以用于确定一个发射波束。终端设备可以在波束训练的过程中维护服务小区的索引、BWP ID以及参考信号资源标识与发射波束的对应关系，网络设备可以在波束训练的过程中维护服务小区的索引、BWP ID以及参考信号资源标识与接收波束的对应关系。通过参考信号资源标识，便可以建立起发射波束和接收波束之间的配对关系。
在此后的通信过程中，终端设备可以基于网络设备所指示的空间关系确定发射波束，网络设备可以基于同一空间关系确定接收波束。
具体地，网络设备可通过高层参数，如PUCCH-config IE，为终端设备配置空间关系列表，该空间关系列表中可以包括多个空间关系。此后，网络设备可以通过高层信令(如MAC CE)的空间关系激活一个空间关系。该空间关系可用于确定终端设备发送PUCCH的发射波束，以及网络设备接收PUCCH的接收波束。
网络设备还可以通过高层参数，如SRS-config IE，为终端设备配置与多个SRS resource对应的空间关系。此后，网络设备可以通过物理层信令(如DCI)的SRI字段指示被选择的一个SRS resource。由此，终端设备可以确定被选择的空间关系，该空间关系可用于确定终端设备发送PUSCH的发射波束，以及网络设备接收PUSCH的接收波束。
13、波束：波束在NR协议中的体现可以是空域滤波器(spatial filter)，或者称空间滤波器或空间参数(spatial parameters)。用于发送信号的波束可以称为发射波束(transmission beam，Tx beam)，也可以称为空间发送滤波器(spatial domain transmit filter)或空间发射参数(spatial domain transmit parameter)；用于接收信号的波束可以称为接收波束(reception beam，Rx beam)，也可以称为空间接收滤波器(spatial domain receive filter)或空间接收参数(spatial domain receive parameter)。
发射波束可以是指信号经天线发射出去后在空间不同方向上形成的信号强度的分布，接收波束可以是指从天线上接收到的无线信号在空间不同方向上的信号强度分布。
14、波束配对关系：即，发射波束与接收波束之间的配对关系，也就是空间发射滤波器与空间接收滤波器之间的配对关系。在具有波束配对关系的发射波束和接收波束之间传输信号可以获得较大的波束赋形增益。
在一种实现方式中，发送端和接收端可以通过波束训练来获得波束配对关系。具体地，发送端可通过波束扫描的方式发送参考信号，接收端也可通过波束扫描的方式接收参考信号。具体地，发送端可通过波束赋形的方式在空间形成不同指向性的波束，并可以在多个具有不同指向性的波束上轮询，以通过不同指向性的波束将参考信号发射出去，使得参考信号在发射波束所指向的方向上发射参考信号的功率可以达到最大。接收端也可通过波束 赋形的方式在空间形成不同指向性的波束，并可以在多个具有不同指向性的波束上轮询，以通过不同指向性的波束接收参考信号，使得该接收端接收参考信号的功率在接收波束所指向的方向上可以达到最大。
通过遍历各发射波束和接收波束，接收端可基于接收到的参考信号进行信道测量，并将测量得到的结果通过CSI上报发送端。例如，接收端可以将参考信号接收功率(reference signal receiving power，RSRP)较大的部分参考信号资源上报给发送端，如上报参考信号资源的标识，以便发送端在传输数据或信令时采用信道质量较好的波束配对关系来收发信号。
15、小区：或称服务小区。是高层从资源管理或移动性管理或服务单元的角度来描述的。每个网络设备的覆盖范围可以被划分为一个或多个服务小区，且该服务小区可以看作由一定频域资源组成。在本申请实施例中，小区可以替换为服务小区或载波单元(component carrier，CC，或者称，成员载波、组成载波、载波等)。在本申请实施例中，“小区”、“服务小区”和“CC”交替使用，在不强调其区别时，其所要表达的含义是一致的。
16、载波聚合(carrier aggregation，CA)：为了高效地利用零碎的频谱，系统支持不同载波单元之间的聚合。将2个或2个以上的载波聚合在一起以支持更大的传输带宽的技术可以称为载波聚合。
载波聚合是终端设备特定的，不同终端设备可以配置不同的CC，每个CC可以对应于一个独立的小区。在本申请实施例中，可以将一个CC等同于一个小区。例如，主小区(primary cell，PCell)对应主CC(或者称，主载波)，可以是为终端进行初始连接建立的小区，或进行RRC连接重建的小区，或是在切换(handover)过程中指定的主小区。辅小区(secondary cell，SCell)对应辅CC(或者称，辅载波)，可以是在RRC重配置时添加的，用于提供额外的无线资源的小区。
对于处于连接态的终端设备来说，若未配置载波聚合，则该终端设备有一个服务小区；若配置了载波聚合，则该终端设备可以有多个服务小区(serving cell)，可以称为服务小区集合。例如，上文所述的主小区和辅小区组成了该终端设备的服务小区(serving cell)集合。换句话说，服务小区集合包括至少一个主小区和至少一个辅小区。或者说，配置了载波聚合的终端可与1个PCell和多个SCell相连。例如在NR中，配置了载波聚合的终端设备可以与1个PCell和最多4个SCell相连。
应理解，上文中对各种配置做了详细说明，并以NR协议中的高层参数为例详细说明了网络设备为终端设备配置各参数的具体方法，如servingCellConfig IE、PUCCH-Config IE、PDCCH-Config IE等，但这不应对本申请构成任何限定。本申请并不排除网络设备采用其他信令或方式为终端设备配置参数的可能。
为便于理解本申请实施例，首先以图1示出的通信系统为例详细说明适用于本申请实施例提供的方法的通信系统。图1示出了适用于本申请实施例的发送和接收UCI的方法的通信系统100的示意图。如图所示，该通信系统100可以包括至少一个终端设备，如图中所示的终端设备101；该通信系统100还可以包括至少两个网络设备，如图中所示的网络设备#1 102和网络设备#2 103。网络设备#1 102和网络设备#2 103可以是同一个小区中的站点，也可以是不同小区中的站点，本申请对此不作限定。图中仅为示例，示出了网络设备#1 102和网络设备#2 103位于同一个小区中的示例。
在通信系统100中，网络设备#1 102和网络设备#2 103彼此之间可通过回程(backhaul)链路通信，该回程链路可以是有线回程链路(例如光纤、铜缆)，也可以是无线回程链路(例如微波)。网络设备#1 102和网络设备#2 103可以进行相互协同，来为终端设备101提供服务。因此，终端设备101可通过无线链路分别与网络设备#1 102和网络设备#2 103通信。
此外，网络设备#1 102和网络设备#2 103中的一个或多个还可以分别采用载波聚合技术，在一个或多个CC上为终端设备101调度PDSCH。例如，网络设备#1 102可以在CC#1和CC#2上为终端设备101调度PDSCH，网络设备#2 103可以在CC#1和CC#3上为终端设备101调度PDSCH。网络设备#1 102和网络设备#2 103所调度的CC可以是相同的，也可以是不同的，本申请对此不作限定。
相互协同的网络设备之间的通信时延可以分为理想回程(ideal backhaul)和非理想回程(non-ideal backhaul)。理想回程下的两站点之间，通信时延可以是微秒级别，与NR中毫秒级别的调度相比，可以忽略不计；非理想回程下的两站点之间，通信时延可以是毫秒级别，与NR中毫秒级别的调度相比，无法忽略。
因此，一种基于多个DCI的多站点调度的方案被提出。基于多个DCI的多站点调度方案支持多个网络设备分别通过各自发送的DCI为终端设备调度各自的PDSCH，进行数据传输。由于网络设备对于终端设备而言是透明的，终端设备可以接收到多个DCI，但并不知道该多个DCI是来自一个网络设备还是多个网络设备。因此，这种基于多个DCI的多站点调度方案又可以称为多DCI调度方案。
举例而言，图1的网络设备#1 102可以向终端设备101发送PDCCH，该PDCCH中可以携带DCI，该DCI可用于为终端设备101调度PDSCH，并指示PUCCH的资源。为便于区分和说明，由网络设备#1 102调度的PDSCH例如记作PDSCH#1，由网络设备#1 102确定的PUCCH例如记作PUCCH#1。网络设备#2 103也可以向终端设备101发送PDCCH，该PDCCH中也可以携带DCI，该DCI也可以为终端设备101调度PDSCH，并指示PUCCH的资源。为便于区分和说明，由网络设备#2 103调度的PDSCH例如记作PDSCH#2，由网络设备#2 103确定的PUCCH例如记作PUCCH#2。换句话说，终端设备101可以从网络设备#1 102接收到PDSCH#1，并通过PUCCH#1反馈针对PDSCH#1的HARQ#1；终端设备101也可以从网络设备#2 103接收到PDSCH#2，并通过PUCCH#2反馈针对PDSCH#2的HARQ#2。具体地，终端设备可以通过不同的UCI向不同的网络设备反馈HARQ。如，终端设备101可以在PUCCH#1上发送UCI#1，该UCI#1中携带HARQ#1，终端设备101还可以在PUCCH#2上发送UCI#2，该UCI#2中携带HARQ#2。
然而，在有些情况下，网络设备，例如网络设备#1 102，可能会基于某些紧急业务，如超可靠低延迟通信(ultra-reliable and low latency communication，URLLC)业务，紧急地为终端设备调度PUSCH。网络设备#1 102为终端设备101调度的PUSCH与上述PUCCH#1和/或PUCCH#2可能发生资源重叠。例如，网络设备#1 102为终端设备调度的PUSCH占用的资源与PUCCH#1在某一个或多个符号上重叠，和/或，网络设备#1 102为终端设备调度的PUSCH占用的资源与PUCCH#2在某一个或多个符号上重叠。
在单站点调度时，终端设备101可以将UCI中的部分或全部信息通过PUSCH发送给网络设备。具体地，当PUCCH与PUSCH存在资源重叠时，终端设备可以通过PUSCH 传输UCI中的HARQ、半持续CSI以及周期CSI。
而在多DCI调度情况下，如果上述PUSCH与PUCCH#1和PUCCH#2均发生资源重叠，终端设备可能仍将UCI#1和UCI#2都通过PUSCH发送给网络设备#1。然而，网络设备#1可能并不知道终端设备会通过该PUSCH发送UCI#2，因此可能认为终端设备通过PUSCH发送的UCI仅包含UCI#1，基于PUSCH仅包含UCI#1的情况对在PUSCH上接收到的信号进行解调译码。因此终端设备和网络设备#1对PUSCH上传输的信息的具体内容的理解不一致，所做的处理也不一致，网络设备可能无法解析出UCI#1中的具体内容。另一方面，网络设备#2并不知道PUCCH#2与PUSCH发生资源重叠，可能仍然在PUCCH#2的资源上接收UCI#2，因此也无法获取到UCI#2。因此网络设备#1可能会重传PDSCH#1，网络设备#2也可能会重传PDSCH#2，从而造成了传输资源的浪费，同时也会造成数据传输的延迟，用户体验不好。
有鉴于此，本申请提供一种配置方法，使得终端设备在多DCI调度场景下能够了解PUCCH的资源与PDCCH配置的关联关系。本申请还提供一种发送和接收UCI的方法，使得终端设备在多DCI调度场景下能够确定哪些UCI可以通过被调度的PUSCH传输，网络设备也可以在相应的资源上接收UCI，可以避免网络设备和终端设备确定的资源不一致网络设备接收不到UCI的情况。因此，网络设备可以根据UCI做出合理的决策，避免不必要的重传，减小传输资源的浪费，减小数据传输的延迟，提高用户体验。
为了便于理解本申请实施例，作出以下几点说明。
第一，在本申请实施例中，多处涉及高层参数，该高层参数可以通过高层信令。该高层信令例如可以是无线资源控制(radio resource control，RRC)消息，也可以是其他高层信令，本申请对此不做限定。
第二，在本申请实施例中，“用于指示”可以包括用于直接指示和用于间接指示，也可以包括显式指示和隐式指示。将某一信息(如下文所述的配置信息)所指示的信息称为待指示信息，则具体实现过程中，对待指示信息进行指示的方式有很多种，例如但不限于，可以直接指示待指示信息，如待指示信息本身或者该待指示信息的索引等。也可以通过指示其他信息来间接指示待指示信息，其中该其他信息与待指示信息之间存在关联关系。还可以仅仅指示待指示信息的一部分，而待指示信息的其他部分则是已知的或者提前约定的。例如，还可以借助预先约定(例如协议规定)的各个信息的排列顺序来实现对特定信息的指示，从而在一定程度上降低指示开销。
第三，在本申请实施例中，当描述A与B关联或关联的A与B时，可表示A与B之间具有关联关系。因此，“A与B关联”与“A与B之间具有关联关系”，可以表达相同的含义，或者说，是可替换的。例如，关联的PUCCH配置与PDCCH配置，可表示PUCCH配置与PDCCH配置之间具有关联关系。又例如，CSI上报配置与PDCCH配置关联，可表示CSI上报配置与PDCCH配置之间具有关联关系。为了简洁，这里不再一一举例说明。
第四，在下文示出的实施例中第一、第二、第三、第四以及各种数字编号仅为描述方便进行的区分，并不用来限制本申请实施例的范围。例如，区分不同的指示信息等。
第五，在下文示出的实施例中，“预先获取”可包括由网络设备信令指示或者预先定义，例如，协议定义。其中，“预先定义”可以通过在设备(例如，包括终端设备和网络设备)中预先保存相应的代码、表格或其他可用于指示相关信息的方式来实现，本申请对于 其具体的实现方式不做限定。
第六，本申请实施例中涉及的“保存”，可以是指的保存在一个或者多个存储器中。所述一个或者多个存储器，可以是单独的设置，也可以是集成在编码器或者译码器，处理器、或通信装置中。所述一个或者多个存储器，也可以是一部分单独设置，一部分集成在译码器、处理器、或通信装置中。存储器的类型可以是任意形式的存储介质，本申请并不对此限定。
第七，本申请实施例中涉及的“协议”可以是指通信领域的标准协议，例如可以包括LTE协议、NR协议以及应用于未来的通信系统中的相关协议，本申请对此不做限定。
第八，“至少一个”是指一个或者多个，“多个”是指两个或两个以上。“和/或”，描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B的情况，其中A，B可以是单数或者复数。字符“/”一般表示前后关联对象是一种“或”的关系。“以下至少一项(个)”或其类似表达，是指的这些项中的任意组合，包括单项(个)或复数项(个)的任意组合。例如，a、b和c中的至少一项(个)，可以表示：a，或b，或c，或a和b，或a和c，或b和c，或a、b和c，其中a，b，c可以是单个，也可以是多个。
下面将结合附图详细说明本申请提供的各个实施例。
应理解，本申请提供的方法可以适用于无线通信系统。例如图1中所示的通信系统100。本申请实施例中的终端设备可以同时与一个或多个网络设备通信，例如，本申请实施例中的网络设备可对应于图1中的网络设备#1 102和网络设备#3 103中的任意一个，本申请实施例中的终端设备可以对应于图1中的终端设备101。
为便于理解本申请所提供的发送和接收UCI的方法，首先结合附图详细说明本申请所提供的配置方法。由于处于无线通信系统中的一个或多个网络设备可以为同一终端设备提供服务，处于该无线通信系统中为同一终端设备服务的任意一个网络设备均可以基于本申请所提供的配置方法为终端设备配置参数。以下，不失一般性，以一个终端设备与一个网络设备之间的交互过程为例详细说明本申请实施例提供的配置方法。
需要说明的是，当多个网络设备为同一终端设备提供服务时，该多个网络设备可以分别向该终端设备发送配置信息，也可以由某一个网络设备向终端设备发送配置信息，本申请对此不做限定。
图2是从设备交互的角度示出的本申请实施例提供的配置方法200的示意性流程图。如图所示，该方法200可以包括步骤210至步骤230。下面详细说明方法200中的各步骤。
在步骤210中，网络设备生成第一配置信息，该第一配置信息可用于指示关联的PUCCH配置与PDCCH配置参数。
在本申请中，为便于区分和说明，将用于指示关联的PUCCH配置与PDCCH配置参数的配置信息称为第一配置信息。其中，PDCCH配置参数可以包括高层参数中的PDCCH配置以及PDCCH的下行控制参数。如前所述，PUCCH配置可用于确定PUCCH的资源，PDCCH配置可用于确定PDCCH的搜索空间。
关联的PUCCH配置与PDCCH配置参数可以是指，该PUCCH配置与PDCCH配置参数可以是基于同一网络设备而配置的。或者说，关联的PUCCH配置与PDCCH配置参数可以对应于同一网络设备。在多DCI调度场景下，终端设备可以接收到多个PUCCH配 置，每个PUCCH配置可以是对应一个网络设备的。当某一PUCCH配置与某一网络设备对应时，基于该PUCCH配置确定的资源可以用于向该网络设备传输PUCCH，基于PUCCH配置所确定的资源上传输的信息也可以是发送给该网络设备的信息。该网络设备可以基于相同的PUCCH配置确定资源，并在该资源上接收PUCCH。由该PUCCH配置确定的用于传输PUCCH的资源可以称为PUCCH的资源。
由于该PUCCH的资源可以是由PUCCH配置确定的，该PUCCH上传输的信息例如可以是针对该网络设备通过PDCCH调度的PDSCH反馈的HARQ信息，或者，也可以是反馈给该网络设备的多个CSI，或者，还可以是针对网络设备通过PDCCH调度的PDSCH反馈的HARQ信息和一个或多个CSI，或者，还可以是HARQ信息(例如包括网络设备通过PDCCH调度的PDSCH和没有对应的PDCCH的PDSCH，如SPS PDSCH)以及多个CSI。
当PUCCH配置与PDCCH配置参数关联时，基于该PDCCH配置参数接收(或者说，盲检)到的PDCCH所来自的网络设备与上述PUCCH发送所至的网络设备可以是同一网络设备。当该UCI包括针对PDSCH的HARQ信息时，该PDCCH可以是用于调度PDSCH的PDCCH。
应注意，用于发送该第一配置信息的网络设备可以是上述PUCCH配置或PDCCH配置对应的网络设备，也可以是其他网络设备，本申请对此不作限定。
在一个可能的场景中，终端设备可以基于PDCCH配置接收到来自网络设备的PDCCH。网络设备可以通过该PDCCH为终端设备调度PDSCH，终端设备可以基于该PDCCH中的PUCCH resource indicator，从与该PDCCH配置关联的PUCCH配置中确定用于传输UCI的PUCCH的资源，进而在该PUCCH的资源传输UCI，网络设备可以在该PUCCH的资源上接收UCI。
相反，如果终端设备不知道PUCCH配置与PDCCH配置之间的关联关系，在接收到PDCCH时可能不知道应该基于哪个PUCCH配置来确定用于传输UCI的PUCCH的资源。因此终端设备所确定的用于传输UCI的PUCCH的资源与网络设备确定的接收UCI的PUCCH的资源可能是不同的。网络设备无法接收到针对所调度的PDSCH的反馈，从而可能导致网络设备做出错误的决策。例如，在终端设备成功接收并成功解码的情况下因未接收到UCI而重传数据，浪费了传输资源，也造成了数据传输时延，影响用户体验。
下面详细说明通过第一配置信息指示关联的PUCCH配置与PDCCH配置以及通过第一指示信息指示关联的PUCCH配置与PDCCH的下行控制参数的具体方法。
在本实施例中，网络设备可以通过配置PUCCH配置与PDCCH配置的关联关系，来帮助终端设备确定哪个PUCCH配置和哪个PDCCH配置可以对应同一网络设备。具体地，网络设备可以通过以下列举的任一种方式来向终端设备指示关联的PUCCH配置与PDCCH配置：
方式一：在PUCCH配置中增加指示字段，以指示关联的PDCCH配置；
方式二：在PDCCH配置中增加指示字段，以指示关联的PUCCH配置；或
方式三：在服务小区配置中配置关联的PUCCH配置与PDCCH配置。
下面详细说明上文列举的三种方式。
在方式一中，网络设备可以在PUCCH配置中增加字段来指示关联的PDCCH配置。 例如，PUCCH配置可以通过高层参数PUCCH-Config IE配置，网络设备可以在该PUCCH-Config IE中增加PDCCH-Config ID的字段，以指示所关联的PDCCH配置。在这种方式中，该第一配置信息可以是PUCCH配置，例如PUCCH-Config IE或其他可用于实现PUCCH配置相同或相似功能的信令。
应理解，PDCCH配置的指示例如可以是PDCCH配置的标识，如PDCCH配置0和PDCCH配置1，或者，其他可用于指示PDCCH配置的信息。本申请对于PDCCH配置的指示的具体形式不作限定。
在方式二中，网络设备可以在PDCCH配置中增加字段来指示关联的PUCCH配置。具体地，PDCCH配置可以通过高层参数PDCCH-Config IE配置，网络设备可以在该PDCCH-Config IE中增加PUCCH-Config ID的字段，以指示所关联的PUCCH配置。在这种方式中，该第一配置信息可以是PDCCH配置，例如PDCCH-Config IE或其他可用于实现PDCCH配置相同或相似功能的信令。
应理解，PUCCH配置的指示例如可以是PUCCH配置的标识，或者，其他可用于指示PUCCH配置的信息。本申请对于PUCCH配置的指示的具体形式不作限定。
在方式三中，网络设备可以通过服务小区配置来指示关联的PUCCH配置和PDDCH配置。该第一配置信息可以为服务小区配置。例如，该服务小区配置可以是NR协议中的servingCellConfig IE。
在一种可能的设计中，该服务小区配置中可以包括一组或多组BWP上行参数以及一组或多组BWP下行参数。每组BWP上行参数可以是为一个BWP配置的，例如，可以在BWP下行参数中指示BWP的ID。每组BWP上行参数也可以是为一个BWP配置的，例如，可以在BWP下行参数中指示BWP的ID。每组BWP上行参数可以包括一组或多组BWP上行专用参数，每组BWP上行专用参数可以包括一个PUCCH配置。每组BWP下行参数可以包括一组或多组BWP下行专用参数，每组BWP下行专用参数可以包括一个PDCCH配置。当某一PUCCH配置与某一PDCCH配置关联时，该PUCCH配置和PDCCH配置可以是为同一BWP配置的，且该PUCCH配置所属的BWP上行专用参数的标识可以与PDCCH配置所属的BWP下行专用参数的标识相同。当PUCCH配置和PDCCH配置为同一BWP配置时，该PUCCH配置所属的BWP上行参数中指示的BWP的ID可以与PDCCH配置所属的BWP下行参数中指示的BWP的ID相同。
例如，服务小区配置中为某一BWP配置的BWP上行参数可以包括BWP上行专用参数0、BWP上行专用参数1，为同一BWP配置的BWP下行参数可以包括BWP下行专用参数0、BWP下行专用参数1。则BWP上行专用参数0中的PUCCH配置可以与BWP下行专用参数0中的PDCCH配置关联；BWP上行专用参数1中的PUCCH配置可以与BWP下行专用参数1中的PDCCH配置关联。
又例如，服务小区配置为某一BWP配置的BWP配置参数中可以包括一组BWP上行专用参数，为同一BWP配置的BWP下行参数可以包括一组BWP下行专用参数，则该服务小区配置中为同一BWP配置的PUCCH配置可以与PDCCH配置关联。此情况下，由于服务小区配置为同一BWP配置的上行参数包括一组BWP上行专用参数，为同一BWP配置的下行参数包括一组BWP下行专用参数，可以无需通过标识来区分。将该服务小区配置为同一BWP配置的BWP上行专用参数中的PUCCH配置与BWP下行专用参数中的 PDCCH配置关联，可认为是PUCCH配置所属的BWP上行专用参数的标识与PDCCH配置所属的BWP下行专用参数的标识相同的一种特例。
在另一种可能的设计中，该服务小区配置中可以包括一组或多组BWP上行参数以及一组或多组BWP下行参数。每组BWP上行参数可以包括一组或多组BWP上行专用参数，每组BWP下行参数可以包括一组或多组BWP下行专用参数。每组BWP上行专用参数可以包括一个或多个PUCCH配置。每组BWP下行专用参数可以包括一个或多个PDCCH配置。当某一PUCCH配置与某一PDCCH配置关联时，该PUCCH配置和PDCCH配置可以是为同一BWP配置的，该PUCCH配置所属的BWP上行专用参数的标识可以与PDCCH配置所属的BWP下行专用参数的标识相同，且该PUCCH配置的标识可以与PDCCH配置的标识相同。当PUCCH配置和PDCCH配置为同一BWP配置时，该PUCCH配置所属的BWP上行参数中指示的BWP的ID可以与PDCCH配置所属的BWP下行参数中指示的BWP的ID相同。
例如，服务小区配置中为某一BWP配置的BWP上行参数可以包括BWP上行专用参数0、BWP上行专用参数1，为同一BWP配置的BWP下行参数可以包括BWP下行专用参数0、BWP下行专用参数1。BWP上行专用参数0可以包括PUCCH配置0和PUCCH配置1。BWP上行专用参数1可以包括PUCCH配置0和PUCCH配置1。BWP下行专用参数0可以包括PDCCH配置0和PDCCH配置1。BWP下行专用参数1可以包括PDCCH配置0和PDCCH配置1。则，BWP上行专用参数0中的PUCCH配置0可以与BWP下行专用参数0中的PDCCH配置0关联；BWP上行专用参数0中的PUCCH配置1可以与BWP下行专用参数0中的PDCCH配置1关联；BWP上行专用参数1中的PUCCH配置0可以与BWP下行专用参数1中的PDCCH配置0关联；BWP上行专用参数1中的PUCCH配置1可以与BWP下行专用参数1中的PDCCH配置1关联。
又例如，服务小区配置中为某一BWP配置的BWP上行参数可以包括一组BWP上行专用参数，为同一BWP配置的BWP下行参数可以包括一组BWP下行专用参数。该BWP上行专用参数可以包括PUCCH配置0和PUCCH配置1，该BWP下行专用参数可以包括PDCCH配置0和PDCCH配置1。则，PUCCH配置0可以与PDCCH配置0关联；PUCCH配置1可以与PDCCH配置1关联。此情况下，由于服务小区配置中为同一BWP配置的参数包括一组BWP上行专用参数和一组BWP下行专用参数，可以无需通过标识来区分。将服务小区配置为同一BWP配置的BWP上行专用参数中的PDCCH配置与BWP下行专用参数中相同标识的PDCCH配置关联，可以认为是PUCCH配置所属的BWP上行专用参数的标识与PDCCH配置所属的BWP下行专用参数的标识相同的一种特例。
在又一种可能的设计中，该服务小区配置中的配置均可以为关联的。则，当PUCCH配置与PDCCH配置属于同一服务小区配置时，该PUCCH配置与PDCCH配置可以是关联的。
应理解，上文列举了第一配置信息的几种可能的形式，但这不应对本申请构成任何限定。本申请对于第一配置信息的具体形式不作限定。
还应理解，上文列举了通过第一配置信息指示关联的PUCCH配置与PDCCH配置的可能的实现方式，但这不应对本申请构成任何限定。本申请并不排除通过其他的方式来指示关联的PUCCH配置与PDCCH配置的可能。例如，该第一配置信息还可以是映射关系， 如，映射关系表，或者其他可用于指示映射关系的信息。该映射关系可用于指示对应的PUCCH配置与PDCCH配置，对应的PUCCH配置与PDCCH配置可以具有关联关系。
还应理解，上文中仅为便于理解，示例性地给出了BWP上行专用参数的标识、BWP下行专用参数的标识、PUCCH配置的标识以及PDCCH配置的标识，但这不应对本申请构成任何限定。本申请对于服务小区配置中为同一BWP配置的BWP上行参数的组数、BWP下行参数的组数、BWP上行专用参数的组数、BWP下行专用参数的组数、PDCCH配置的个数以及PUCCH配置的个数不做限定。此外，本申请对于服务小区配置中包括多组上行或下行参数的情况下，为各组参数中包含的多组专用参数的配置的分配标识的方式也不做限定。各组专用参数的配置的标识可以是局部(local)的，也可以是全局(global)的。
还应理解，上文仅为便于理解，示出了服务小区配置中可能包含的配置参数，但这不应对本申请构成任何限定。服务小区配置中还可能包含除上文列举之外的其他配置参数，本申请对此不作限定。
网络设备可以通过以下列举的任一种方式来向终端设备指示关联的PUCCH配置与PDCCH的下行控制参数：
方式一：在PUCCH配置中增加指示字段，以指示关联的DMRS端口组(DMRS port group)或DMRS码分复用(code division multiplexing，CDM)组(DMRS CDM group)；或
方式二：在PUCCH配置中增加指示字段，以指示关联的TB或码字(codeword，CW)。
其中，该下行控制参数可以是DCI中包含的与PDCCH相关的参数，或者是与该DCI中的参数相关的参数。
例如，DCI中指示的PDCCH相关的参数可以为用于上行传输或下行传输的天线端口(antenna port)。与该天线端口相关的参数可以是解调参考信号(demodulation reference signal，DMRS)端口、DMRS group)或DMRS CDM group。终端设备可以基于DCI中指示的antenna port确定DMRS port，进而确定所属的DMRS port group或DMRS CDM group。例如，下行系统中的antenna port与DMRS port的关系可以为：antenna port＝1000+DMRS port；上行系统中的antenna port与DMRS port的关系可以为：antenna port＝DMRS port。可选地，终端设备还可以根据DMRS port确定所属的DMRS port group或DMRS CDM group。
需要说明的是，DMRS port group和DMRS CDM group可以理解为基于不同的方式对DMRS port进行分组而得到。antenna port、DMRS port、DMRS port group和DMRS CDM group可以通过索引来区分，也可以通过标识来区分，或者还可通过其他可用于区分不同端口或不同组的信息来区分，本申请对此不作限定。
再例如，DCI中指示的PDCCH相关的参数为与传输块(transport block，TB)相关的参数。与TB相关的参数例如可以包括用于配置调制阶数和码率的MCS、用于指示新传还是重传的NDI以及用于指示RV等。
下面详细说明上文列举的两种方式。
在方式一中，网络设备可以在PUCCH配置中增加字段来指示关联的DMRS port group或DMRS CDM group。例如，PUCCH配置可以通过高层参数PUCCH-Config IE配置，网 络设备，可以在PUCCH-Config IE中增加DMRS port group ID的字段，以指示关联的DMRS port group；或者，在PUCCH-Config IE中增加DMRS CDM group ID的字段，以指示关联的DMRS CDM group。在这种方式中，该第一配置信息可以是PUCCH配置，例如，PUCCH-Config IE或其他可用于实现与PUCCH配置相同或相似功能的信令。
当终端设备接收到用于调度PUSCH或PDSCH的PDCCH时，可以根据该PDCCH的下行控制参数，如DCI中指示的antenna port与DMRS port、DMRS port group或DMRS CDM group的对应关系，确定其关联的PUCCH配置。
举例而言，PUCCH配置0中的关联字段为0时，假设可以关联到DMRS port group 0；PUCCH配置1中的关联字段为1时，假设可以关联到DMRS port group 1。当终端设备接收到的PDCCH中的DCI指示的antenna port对应的DMRS port属于group port group 1，则PUCCH配置1与该PDCCH关联。
在方式二中，网络设备可以在PUCCH配置中增加字段来指示关联的TB或CW。例如，PUCCH配置可以通过高层参数PUCCH-Config IE配置，网络设备可以在PUCCH-Config IE中增加用于指示TB或CW的字段，以指示所关联的TB或CW。在这种方式中，该第一配置信息可以是PUCCH配置，例如，PUCCH-Config IE或其他可用于实现与PUCCH配置相同或相似功能的信令。
以DCI format 1_1为例，在DCI format1_1中，会有2个TB的配置信息，如TB1和TB2。每个TB对应的参数可以包括MCS、NDI和RV。在NR中，DCI format1_1支持使能一个TB。因此，网络设备可以在DCI中使能(enable)一个TB，去使能(disable)另一个TB。当某个TB对应的参数中MCS＝26且RV＝1时，则认为该TB被去使能。因此，当终端设备接收到PDCCH时，可以根据DCI中指示的各TB的MCS和RV确定被使能的TB，进而确定其关联的PUCCH配置。
举例而言，PUCCH配置0中的关联字段为0时，假设可以关联到TB1；PUCCH配置1中的关联字段为1时，假设可以关联到TB2。当终端设备接收到的PDCCH中的DCI指示的前一个TB的MCS＝26且RV＝1，则表示TB1被去使能，TB2被使能。则PUCCH配置1与该PDCCH关联。
由于TB与CW具有一一对应关系，PUCCH配置中可以指示关联的TB，也可以指示关联的CW。当PUCCH配置中指示关联的TB和CW中的一个时，终端设备便可以确定PUCCH配置所关联的另一个。
应理解，上文列举了通过第一配置信息指示关联的PUCCH配置与PDCCHCSI上报配置或CSI测量配置的实现方式，但这不应对本申请构成任何限定。本申请并不排除通过其他的方式来指示关联的PUCCH配置与PDCCH的下行控制参数的可能。
在步骤220中，网络设备发送该第一配置信息。相应地，在步骤220中，终端设备接收该第一配置信息。
可选地，该第一配置信息可以携带在高层信令中。该高层信令例如可以为RRC消息。
可以理解的是，当网络设备为多个终端设备服务时，可以通过不同的信令向各终端设备发送该第一配置信息。终端设备在与多个网络设备通信时，也可以通过接收到来自多个网络设备的第一配置信息。
在步骤230中，终端设备根据该第一配置信息确定关联的PUCCH配置和PDCCH配 置。
终端设备在接收到来自一个或多个网络设备的第一配置信息时，可以基于上文步骤220中所描述的方式来确定关联的PUCCH配置和PDCCH配置。
当协议定义基于上文列举的某一种方式来关联PUCCH配置和PDCCH配置时，网络设备可以基于协议所定义的方式来生成第一配置信息，终端设备可以基于协议所定义的方式来解析该第一配置信息，以确定关联的PUCCH配置和PDCCH配置。
基于上述技术方案，终端设备可以基于PUCCH配置与PDCCH配置之间的关联关系，确定哪些PDCCH配置和PUCCH配置对应于同一网络设备，从而可以根据网络设备的指示确定PUCCH的资源来传输UCI。而网络设备也可以在相应的资源上接收UCI，不会造成因双方确定的资源不一致网络设备接收不到UCI的情况。因此，通过引入上述第一配置信息，可以方便终端设备与网络设备之间的通信，有利于提高传输性能，提高用户体验。
在某些情况下，终端设备需要向网络设备上报CSI，如周期CSI或半持续CSI。在单站点调度时，终端设备可以根据CSI上报配置确定用于上报CSI的PUCCH。然而，在多DCI调度时，终端设备可能接收到多个CSI上报配置。此时，由于终端设备并不知道CSI上报配置与网络设备的对应关系，终端设备和网络设备可能会基于不同的CSI上报配置确定PUCCH。由此而确定PUCCH的资源可能不同，网络设备无法成功接收CSI。因此，本申请另提供一种配置方法，可用于配置CSI上报配置与PDCCH的关联关系。
图3是从设备交互的角度示出的本申请实施例提供的配置方法300的示意性流程图。如图所示，该方法300可以包括步骤310至步骤330。下面详细说明方法300中的各步骤。
在步骤310中，网络设备生成第二配置信息，该第二配置信息可用于指示关联的CSI上报配置与PDCCH配置参数。
在本申请中，为便于区分和说明，将用于指示关联的CSI上报配置与PDCCH配置的配置信息称为第二配置信息。其中，PDCCH配置参数可以包括高层参数中的PDCCH配置以及PDCCH的下行控制参数。如前所述，CSI上报配置可用于确定PUCCH资源，PDCCH配置可用于确定PDCCH的搜索空间。
关联的CSI上报配置与PDCCH配置参数可以是指，该CSI上报配置与PDCCH配置参数可以是基于同一网络设备而配置。或者说，关联的CSI上报配置与PDCCH配置参数可以对应于同一网络设备。
在多DCI调度场景下，终端设备可以接收到多个CSI测量配置，每个CSI测量配置可以是对应一个网络设备的。由于每个CSI测量配置可以包括一个或多个CSI上报配置，因此在本申请实施例中，CSI上报配置可以与PDCCH配置关联，或者，CSI上报配置所属的CSI测量配置可以与PDCCH配置关联。当CSI测量配置与PDCCH配置关联时，该CSI测量配置中的一个或多个CSI上报配置均可以与该PDCCH配置关联。
当某一CSI上报配置与某一网络设备对应时，基于该CSI上报配置确定的资源可以用于向该网络设备传输PUCCH，基于CSI上报配置所确定的资源上传输的信息也可以是发送给该网络设备的信息。该网络设备可以基于相同的CSI上报配置确定资源，并在该资源上接收PUCCH。由该CSI上报配置确定的用于传输PUCCH的资源可以称为PUCCH的资源。
由于该PUCCH的资源是由CSI上报配置确定的，该PUCCH上传输的信息例如可以 是反馈给该网络设备的一个CSI，或者，也可以是针对没有对应的PDCCH的PDSCH(例如，SPS PDSCH)反馈的HARQ信息和反馈给该网络设备的一个CSI。
当CSI上报配置与PDCCH配置参数关联时，基于该PDCCH配置参数接收(或者说，盲检)到的PDCCH所来自的网络设备与上述PUCCH发送所至的网络设备可以是同一网络设备。
应注意，用于发送该第二配置信息的网络设备可以是上述CSI上报配置或PDCCH配置对应的网络设备，也可以是其他网络设备，本申请对此不做限定。
在一个可能的场景中，终端设备可以基于PDCCH配置接收来自网络设备的PDCCH。网络设备可以通过该PDCCH激活终端设备的半持续CSI上报。终端设备可以基于该PDCCH配置关联的CSI上报配置确定用于传输UCI的PUCCH的资源，进而在该PUCCH的资源上发送UCI，网络设备可以在该PUCCH的资源上接收UCI。
相反，如果终端设备不知道CSI上报配置与PDCCH配置之间的关联关系，在接收到PDCCH时可能不知道应该基于哪个CSI上报配置来确定用于传输UCI的PUCCH的资源，因此终端设备所确定的用于传输UCI的PUCCH的资源与网络设备确定的接收UCI的PUCCH的资源可能是不同的，网络设备无法接收到终端设备上报的CSI，从而无法获取准确的信道状态，可能会导致所使用的调制编码方式(modulation coding scheme，MCS)不合适，或者预编码矩阵(precoding matrix)与信道状态并不适配，导致数据传输性能下降。
下面详细说明通过第二配置信息指示关联的CSI上报配置与PDCCH配置以及通过第一指示信息指示关联的CSI上报配置与PDCCH的下行控制参数的具体方法。
在本实施例中，网络设备可以通过配置CSI上报配置与PDCCH配置的关联关系，来帮助终端设备确定哪个CSI上报配置和哪个PDCCH配置可以对应同一网络设备。具体地，网络设备通过以下列举的任一种方式来向终端设备指示关联的CSI上报配置与PDCCH配置：
方式一：在CSI上报配置中增加指示字段，以指示关联的PDCCH配置/；
方式二：在CSI上报配置所属的CSI测量配置中增加指示字段，以指示关联的PDCCH配置；
方式三：在PDCCH配置中增加指示字段，以指示关联的CSI上报配置；
方式四：在PDCCH配置中增加指示字段，以指示关联的CSI测量配置；或
方式五：在服务小区配置中指示关联的CSI上报配置和PDCCH配置。
下面详细说明上文列举的五种方式。
在方式一中，网络设备可以在CSI上报配置中增加指示字段来指示关联的PDCCH配置。例如，CSI上报配置可以通过高层参数CSI-ReportConfig IE配置，网络设备可以在该CSI-ReportConfig IE中增加PDCCH-Config ID的字段，以指示所关联的PDCCH配置的指示。在这种方式中，该第二配置信息可以是CSI上报配置，例如CSI-ReportConfig IE或其他可用于实现CSI上报配置相同或相似功能的信令。
在方式二中，网络设备可以在CSI测量配置中增加指示字段来指示关联的PDCCH配置。例如，CSI测量配置可以通过高层参数CSI-MeasConfig IE配置，网络设备可以在该CSI-MeasConfig IE中增加PDCCH-Config ID的字段，以指示所关联的PDCCH配置的标 识。在这种方式中，该第二配置信息可以是CSI测量配置，例如CSI-MeasConfig IE或其他可用于实现CSI测量配置相同或相似功能的信令。
应理解，在上述方式一和方式二中，PDCCH配置的指示例如可以是PDCCH配置的标识，或者，其他可用于指示PDCCH配置的信息。本申请对于PDCCH配置的指示的具体形式不作限定。
需要说明的是，由于每个CSI测量配置中可以包括一个或多个CSI上报配置，若网络设备通过第二配置信息配置CSI测量配置与PDCCH配置的关联关系，即方式二，则该CSI测量配置中的一个或多个CSI上报配置可以与同一个PDCCH配置关联；若网络设备通过第二配置信息配置CSI上报配置与PDCCH配置的关联关系，即方式一，则同一CSI测量配置下的各CSI上报配置所关联的PDCCH配置可以是相同的，也可以是不同的，本申请对此不作限定。
在方式三中，网络设备可以在PDCCH配置中增加字段来指示关联的CSI上报配置。例如，PDCCH配置可以通过高层参数PDCCH-Config IE配置，网络设备可以在该PDCCH-Config IE中增加CSI-ReportConfig ID的字段，以指示所关联的CSI上报配置的指示。在这种方式中，该第二配置信息可以为PDCCH配置，例如PDCCH-Config IE或其他可用于实现PDCCH配置相同或相似功能的信令。
应理解，CSI上报配置的指示例如可以是CSI上报配置的标识，或者，其他可用于指示CSI上报配置的信息。本申请对于CSI上报配置的指示的具体形式不作限定。
与方式一相似地，在方式三中，由于网络设备通过第二配置信息配置CSI上报配置与PDCCH配置的关联关系，同一CSI测量配置下的各CSI上报配置所关联的PDCCH配置可以是相同的，也可以是不同的，本申请对此不作限定。
在方式四中，网络设备可以在PDCCH配置中增加字段来指示关联的CSI测量配置。例如，PDCCH配置可以通过高层参数PDCCH-Config IE配置，网络设备可以在该PDCCH-Config IE中增加CSI-MeasConfig ID的字段，以指示所关联的CSI测量配置的指示。在这种方式中，该第二配置信息可以为PDCCH配置，例如PDCCH-Config IE或其他可用于实现PDCCH配置相同或相似功能的信令。
应理解，CSI测量配置的指示例如可以是CSI测量配置的标识，或者，其他可用于指示CSI测量配置的信息。本申请对于CSI测量配置的指示的具体形式不作限定。
与方式二相似地，在方式四中，由于网络设备通过第二配置信息配置CSI测量配置与PDCCH配置的关联关系，该CSI测量配置中的一个或多个CSI上报配置可以与同一个PDCCH配置关联。
在方式五中，网络设备可以通过服务小区配置来指示关联的CSI上报配置和PDDCH配置。该第二配置信息可以为服务小区配置，例如ServingCellConfig IE或者，其他可用于实现服务小区配置相同或相似功能的信令。
在一种可能的设计中，该服务小区配置中可以包括一个或多个CSI测量配置以及一组或多组BWP下行参数。其中，每个CSI测量配置包括一个或多个CSI上报配置，每组BWP下行参数可以包括一组或多组BWP下行专用参数，每组BWP下行专用参数可以包括一个或多个PDCCH配置。当某一CSI上报配置与某一PDCCH配置关联时，该CSI上报配置所属的CSI测量配置的标识可以与该PDCCH配置所属的BWP下行专用参数的标识相 同。由于同一个服务小区配置中可以包括为一个或多个BWP配置的下行参数，即一组或多组BWP下行参数，每组BWP下行参数包括一组或多组BWP下行专用参数，若每组BWP下行参数中的BWP下行专用参数的标识是局部配置的，则多组BWP下行参数可能存在具有相同标识的BWP下行专用参数。也就是说，该CSI测量配置中的各CSI上报配置可以与一个或多个PDCCH配置关联。
例如，服务小区配置中为各BWP配置的BWP下行参数分别可以包括BWP下行专用参数0、BWP下行专用参数1，服务小区配置中还可以包括CSI测量配置0、CSI测量配置1。则为各BWP配置的BWP下行参数中的BWP下行专用参数0中的PDCCH配置均可以与CSI测量配置0中的CSI测量配置关联，为各BWP配置的BWP下行参数中的BWP下行专用参数1中的PDCCH配置均可以与CSI测量配置1中的CSI测量配置关联。
又例如，服务小区配置中为各BWP配置的BWP下行参数可以包括一组BWP下行专用参数，服务小区配置中还可以包括一个CSI测量配置，则为各BWP配置的BWP下行参数中的BWP下行专用参数中的PDCCH配置均可以与CSI测量配置关联。此情况下，由于为各BWP配置的BWP下行参数中均包括一组BWP下行专用参数，且服务小区配置中包括一个CSI测量配置，无需通过标识来区分。该为各BWP配置的BWP下行参数中的BWP下行专用参数中的PDCCH配置与CSI测量配置关联，可以认为是PDCCH所属的BWP下行专用参数的标识与CSI测量配置的标识相同的一种特例。
在另一种可能的设计中，该服务小区配置中包括一组或多组BWP专用参数，每组BWP专用参数可以是为一个BWP配置的参数，或者说，每组BWP专用参数对应一个BWP。每组BWP专用参数可以包括关联的PDCCH配置和CSI上报配置。具体地，每组BWP专用参数可以包括一组BWP上行专用参数、一组BWP下行专用参数和一个CSI测量配置。每组BWP下行专用参数可以包括一个PDCCH配置，每个CSI测量配置可以包括一个或多个CSI上报配置。同一组BWP专用参数中的PDCCH配置可以与CSI测量配置关联，也就是，同一组BWP专用参数中的PDCCH配置与CSI测量配置中的一个或多个CSI上报配置关联。
在又一种可能的设计中，该服务小区配置中为各BWP配置的BWP上行参数可以包括一组或多组BWP上行专用参数，该服务小区配置中为各BWP配置的BWP下行参数可以包括一组或多组BWP下行专用参数。每组BWP上行专用参数可以包括一个CSI测量配置，每组BWP下行专用参数可以包括一个PDCCH配置。当某一CSI上报配置与某一PDCCH配置关联时，该CSI上报配置与该PDCCH配置可以是为同一BWP配合的，且该CSI上报配置所属的CSI测量配置所属的BWP上行专用参数的标识与PDCCH配置所属的BWP下行专用参数的标识相同。当CSI上报配置与PDCCH配置为同一BWP配置时，该CSI上报配置所属的BWP上行参数中指示的BWP的ID可以与该PDCCH配置所属的BWP下行参数中指示的BWP的ID相同。
例如，服务小区配置中为某一BWP配置的BWP下行参数可以包括BWP下行专用参数0、BWP下行专用参数1，为同一BWP配置的BWP上行参数可以包括BWP上行专用参数0、BWP上行专用参数1。则BWP下行专用参数0中的PDCCH配置可以与BWP上行专用参数0中的CSI测量配置关联，BWP下行专用参数1中的PDCCH配置可以与BWP上行专用参数1中的CSI测量配置关联。
又例如，服务小区配置中可以为某一BWP配置的BWP上行参数可以包括一组BWP上行专用参数，为同一BWP配置的BWP下行参数可以包括一组BWP下行专用参数。则该BWP下行专用参数中的PDCCH配置与该BWP上行专用参数中的CSI测量配置关联。此情况下，由于服务小区配置中为同一个BWP配置的参数包括一组BWP上行专用参数和一组BWP下行专用参数，可以无需通过标识来区分。该服务小区为同一BWP配置的BWP下行专用参数中的PDCCH配置与BWP上行专用参数中的CSI测量配置关联，可以认为是PDCCH所属的BWP下行专用参数的标识与CSI测量配置所属的BWP上行专用参数的标识相同的一种特例。
在再一种可能的设计中，该服务小区配置为某一BWP配置的BWP上行参数可以包括一组或多组BWP上行专用参数，为同一BWP配置的BWP下行参数可以包括一组或多组BWP下行专用参数。每组BWP上行专用参数可以包括一个或多个CSI测量配置，每组BWP下行专用参数可以包括一个或多个PDCCH配置。当某一CSI上报配置与某一PDCCH配置关联时，该CSI上报配置与该PDCCH配置可以是为同一BWP配置的，该CSI上报配置所属的CSI测量配置所属的BWP上行专用参数的标识与PDCCH配置所述的BWP下行专用参数的标识相同，且该CSI测量配置的标识与该PDCCH配置的标识相同。当CSI上报配置与PDCCH配置为同一BWP配置时，该CSI上报配置所属的BWP上行参数中指示的BWP的ID可以与该PDCCH配置所属的BWP下行参数中指示的BWP的ID相同。
例如，服务小区配置中为某一BWP配置的BWP下行参数可以包括BWP下行专用参数0和BWP下行专用参数1，为同一BWP配置的BWP上行参数可以包括BWP上行专用参数0和BWP上行专用参数1。BWP上行专用参数0可以包括CSI测量配置0和CSI测量配置1。BWP上行专用参数1可以包括CSI测量配置0和CSI测量配置1。BWP下行专用参数0可以包括PDCCH配置0和PDCCH配置1。BWP下行专用参数1可以包括PDCCH配置0和PDCCH配置1。则，BWP上行专用参数0中的CSI测量配置0与BWP下行专用参数0中的PDCCH配置0关联；BWP上行专用参数0中的CSI测量配置1与BWP下行专用参数0中的PDCCH配置1关联；BWP上行专用参数1中的CSI测量配置0与BWP下行专用参数1中的PDCCH配置0关联；BWP上行专用参数1中的CSI测量配置1与BWP下行专用参数1中的PDCCH配置1关联。
又例如，服务小区配置中为某一BWP配置的BWP下行参数可以包括一组BWP上行专用参数，为同一BWP配置的BWP上行参数可以包括一组BWP下行专用参数。该BWP上行专用参数可以包括CSI测量配置0和CSI测量配置1，该BWP下行专用参数可以包括PDCCH配置0和PDCCH配置1。则，CSI测量配置0与PDCCH配置0关联；CSI测量配置1与PDCCH配置1关联。
在又一种可能的设计中，该服务小区配置中为某一BWP配置的BWP下行参数可以包括一组或多组BWP下行专用参数。每组BWP下行专用参数可以包括一个CSI测量配置以及一个PDCCH配置。同一组BWP下行专用参数中的CSI测量配置和PDCCH配置关联。可以理解，同一组BWP下行专用参数中的CSI测量配置和PDCCH配置可以是为同一BWP配置的。
例如，服务小区配置中为某一BWP配置的BWP下行参数可以包括BWP下行专用参 数0和BWP下行专用参数1。BWP下行专用参数0可以包括一个CSI测量配置和一个PDCCH配置，BWP下行专用参数1可以包括一个CSI测量配置和一个PDCCH配置。则，该BWP下行专用参数0中的CSI测量配置与PDCCH配置关联；该BWP下行专用参数1中的CSI测量配置与PDCCH配置关联。
在又一种可能的设计中，该服务小区配置中为某一BWP配置的BWP下行参数可以包括一组或多组BWP下行专用参数。每组BWP下行专用参数可以包括一个或多个CSI测量配置以及一个或多个PDCCH配置。当某一CSI测量配置与某一PDCCH配置关联时，该CSI测量配置和PDCCH配置属于同一组BWP下行专用参数，且该CSI测量配置的标识和PDCH配置的标识相同。可以理解，同一组BWP下行专用参数中的CSI测量配置和PDCCH配置可以是为同一BWP配置的。
例如，服务小区配置中为某一BWP配置的BWP下行参数可以包括BWP下行专用参数0和BWP下行专用参数1。BWP下行专用参数0可以包括CSI测量配置0、CSI测量配置1以及PDCCH配置0、PDCCH配置1，BWP下行专用参数1可以包括CSI测量配置0、CSI测量配置1以及PDCCH配置0、PDCCH配置1。可以理解，BWP下行专用参数0和BWP下行专用参数1中具有相同标识的配置并不一定是相同的。也就是说，每组参数中的配置的标识可以是局部(local)的。则，BWP下行专用参数0中的CSI测量配置0与PDCCH配置0关联，BWP下行专用参数0中的CSI测量配置1与PDCCH配置1关联，BWP下行专用参数1中的CSI测量配置0与PDCCH配置0关联，BWP下行专用参数1中的CSI测量配置1与PDCCH配置1关联。
在再一种可能的设计中，该服务小区配置中的配置均可以为关联的。则，当CSI测量配置与PDCCH配置可以属于同一服务小区配置时，该CSI测量配置与PDCCH配置可以是关联的。
需要说明的是，由于CSI上报配置中包括CSI资源的配置信息。因此，当CSI上报配置与PDCCH配置关联时，该CSI上报配置中所配置的CSI资源与PDCCH配置也关联。例如，在CSI上报配置中包括CSI资源配置的标识。当某一CSI上报配置与PDCCH配置关联时，该CSI上报配置中所包含的CSI配置也可以与该PDCCH配置关联。
应理解，上文列举了第二配置信息的几种可能的形式，但这不应对本申请构成任何限定。本申请对于第二配置信息的具体形式不作限定。
还应理解，上文列举了通过第二配置信息指示关联的CSI上报配置与PDCCH配置的可能的实现方式，但这不应对本申请构成任何限定。本申请并不排除通过其他的方式来指示关联的CSI上报配置与PDCCH配置的可能。例如，该第二配置信息还可以是映射关系，如，映射关系表，或者其他可用于指示映射关系的信息。该映射关系可用于指示对应的PUCCH配置与PDCCH配置，对应的PUCCH配置与PDCCH配置可以具有关联关系。
还应理解，上文中仅为便于理解，示例性地给出了BWP专用参数的标识、BWP上行专用参数的标识、BWP下行专用参数的标识、CSI上报配置的标识、CSI测量配置的标识以及PDCCH配置的标识，但这不应对本申请构成任何限定。本申请对于服务小区配置中为同一BWP配置的BWP上行参数的组数、BWP下行参数的组数、BWP专用参数的组数、BWP上行专用参数的组数、BWP下行专用参数的组数、PDCCH配置的个数、CSI测量配置的以及每个CSI测量配置中包含的CSI上报配置的个数不做限定。此外，本申请对于服 务小区配置中包括多组上行或下行参数的情况下，为各组参数中包含的多组专用参数的配置的分配标识的方式也不做限定。各组专用参数的配置的标识可以是局部(local)的，也可以是全局(global)的。
还应理解，上文仅为便于理解，示出了服务小区配置中可能包含的配置参数，但这不应对本申请构成任何限定。服务小区配置中还可能包含除上文列举之外的其他配置参数，本申请对此不作限定。
网络设备可以通过以下列举的任一种方式来向终端设备指示关联的CSI上报配置与PDCCH下行控制参数：
方式一：在CSI上报配置中增加指示字段，以指示关联的DMRS port group或DMRS CDM group；
方式二：在CSI上报配置所属的CSI测量配置中增加指示字段，以指示关联的DMRS port group或DMRS CDM group；
方式三：在CSI上报配置中增加指示字段，以指示关联的TB或CW；或
方式四：在CSI上报配置所属的CSI测量配置中增加指示字段，以指示关联的TB或CW。
上文方法200中已经结合示例详细说明了下行控制参数。为了简洁，这里不再赘述。
下面详细说明上文列举的四种方式。
在方式一中，网络设备可以在CSI上报配置中增加来指示关联的DMRS port group或DMRS CDM group。例如，CSI上报配置可以通过高层参数CSIReport-Config IE配置，网络设备可以在CSIReport-Config IE中增加DMRS port group ID的字段，以指示关联的DMRS port group；或者，在CSIReport-Config IE中增加DMRS CDM group ID的字段，以指示关联的DMRS CDM group。在这种方式中，该第二配置信息可以是CSI上报配置，例如，CSIReport-Config IE或其他可用于实现与CSI上报配置相同或相似功能的信令。
在方式二中，网络设备可以在CSI上报配置所属的CSI测量配置中增加来指示关联的DMRS port group或DMRS CDM group。例如，CSI测量配置可以通过高层参数CSIMeas-Config IE配置，网络设备，可以在CSIMeas-Config IE中增加DMRS port group ID的字段，以指示关联的DMRS port group；或者，在CSIMeas-Config IE中增加DMRS CDM group ID的字段，以指示关联的DMRS CDM group。在这种方式中，该第二配置信息可以是CSI测量配置，例如，CSIMeas-Config IE或其他可用于实现CSI测量配置相同或相似功能的信令。
由于每个CSI测量配置中可以包括一个或多个CSI上报配置，当CSI测量配置与某一DMRS port group或DMRS CDM group关联时，该CSI测量配置中的一个或多个CSI上报配置均可以与同一DMRS port group或DMRS CDM group关联。
在方式三中，网络设备可以在CSI上报配置中增加字段来指示关联的TB或CW。例如，CSI上报配置可以通过高层参数CSIReport-Config IE配置，网络设备可以在CSIReport-Config IE中增加用于指示TB或CW的字段，以指示所关联的TB或CW。在这种方式中，该第二配置信息可以是CSI上报配置，例如，CSIReport-Config IE或其他可用于实现与CSI上报配置相同或相似功能的信令。
在方式四中，网络设备可以在CSI上报配置所属的CSI测量配置中增加字段来指示关 联的TB或CW。例如，CSI测量配置可以通过高层参数CSIMeas-Config IE配置，网络设备可以在CSIMeas-Config IE中增加用于指示TB或CW的字段，以指示所关联的TB或CW。在这种方式中，该第二配置信息可以是CSI测量配置，例如，CSIMeas-Config IE或其他可用于实现与CSI测量配置相同或相似功能的信令。
由于每个CSI测量配置中可以包括一个或多个CSI上报配置，当CSI测量配置与某一TB或CW关联时，该CSI测量配置中的一个或多个CSI上报配置均可以与同一TB或CW关联。由于TB与CW具有一一对应关系，CSI上报配置或CSI测量配置中可以指示关联的TB，也可以指示关联的CW。当CSI上报配置或CSI测量配置中指示关联的TB和CW中的一个时，终端设备便可以确定PUCCH配置所关联的另一个。
应理解，上文列举了通过第二配置信息指示关联的CSI上报配置与PDCCH的下行控制参数的可能的实现方式，但这不应对本申请构成任何限定。本申请并不排除通过其他的方式来指示关联的PUCCH配置与PDCCH的下行控制参数的可能。
在步骤320中，网络设备发送该第二配置信息。相应地，在步骤320中，终端设备接收该第二配置信息。
可选地，该第二配置信息可以携带在高层信令中。该高层信令例如可以为RRC消息。
可以理解的是，当网络设备为多个终端设备服务时，可以通过不同的信令向各终端设备发送该二配置信息。终端设备在与多个网络设备通信时，也可以通过接收到来自多个网络设备的第二配置信息。
在步骤330中，终端设备根据该第二配置信息确定关联的CSI上报配置和PDCCH配置。
终端设备在接收到来自一个或多个网络设备的第二配置信息时，可以基于上文步骤320中所描述的方式来确定关联的CSI上报配置和PDCCH配置。
当协议定义基于上文列举的某一种方式来关联CSI上报配置和PDCCH配置时，网络设备可以基于协议所定义的方式来生成第二配置信息，终端设备可以基于协议所定义的方式来解析该第二配置信息，以确定关联的CSI上报配置和PDCCH配置。
基于上述技术方案，终端设备可以基于CSI上报配置与PDCCH配置之间的关联关系，确定哪些CSI上报配置和PDCCH配置对应于同一网络设备，从而可以根据网络设备的指示确定PUCCH的资源来传输UCI。而网络设备也可以在相应的资源上接收UCI，不会造成因双方确定的资源不一致网络设备接收不到UCI的情况。因此，通过引入上述第二配置信息，有利于提高传输性能，提高用户体验。
图4是从设备交互的角度示出的本申请实施例提供的发送和接收UCI的方法400的示意性流程图。如图所示，该方法400可以包括步骤410至步骤450。下面详细说明方法400中的各步骤。
应理解，图4示出了处于无线通信系统中的终端设备与网络设备传输UCI的具体过程。该终端设备可以为处于无线通信系统中的任意一个终端设备，该终端设备可以与一个或多个网络设备通信，本申请对此不作限定。对于终端设备而言，为其服务的网络设备是透明的。
下面，不失一般性，以一个终端设备为例详细说明终端设备与网络设备传输UCI的具体过程。可以理解的是，处于无线通信系统中的任意一个终端设备均可以基于相同的技术 方案向网络设备发送UCI，本申请对此不做限定。
在步骤410中，终端设备确定PUSCH与目标PUCCH存在资源重叠。
其中，PUSCH可以是由网络设备通过PDCCH调度的。网络设备例如可以通过携带在PDCCH中的DCI中指示PUSCH的时域和频域位置。该DCI例如可以是DCI format 0_0或DCI format 0_1。
PUCCH可以是由终端设备确定的用于传输UCI的资源，在本实施例中，为方便区分和说明，记作目标PUCCH。可以理解的是，目标PUCCH的资源取自PUCCH配置中所配置的PUCCH资源。换句话说，PUCCH配置可以配置PUCCH资源池，该PUCCH资源池中包括多个PUCCH资源。
在单站点调度时，当发送给同一网络设备的目标PUCCH与PUSCH的资源发生重叠时，终端设备可以将HARQ信息、周期CSI或半持续CSI(下文简称CSI)通过PUSCH发送给网络设备，而不通过目标PUCCH传输。也就是说，PUSCH可用于传输HARQ信息和CSI中的至少一项。因此，本申请实施例以UCI分别为HARQ信息和CSI(例如可以为周期CSI或半周期CSI)为例详细说明发送和接收UCI的方法。换句话说，UCI可以包括HARQ信息和CSI中的至少一项。
应理解，本实施例仅为便于理解，以HARQ信息和CSI为例来说明本申请实施例所提供的方法，但这不应对本申请构成任何限定。例如，协议也可以定义在PUSCH中传输的UCI还可以包含其他内容，如SR。本申请实施例所提供的方法主要针对PUCCH和PUSCH资源重叠的情况下，确定是否通过PUSCH来传输UCI，而对UCI中包含的具体内容不作限定。
由于UCI中所包含的信息的不同，用于传输UCI的目标PUCCH的资源的确定方式也有所不同。下面，首先分别以UCI包括HARQ信息和/或CSI(例如可以为周期CSI或半周期CSI)为例详细说明终端设备确定目标PUCCH的资源的具体过程。
情况一、UCI仅包括HARQ信息
由于PDSCH可以是由网络设备通过PDCCH调度的PDSCH，也可以是半持续调度(SPS)的PDSCH，根据PDSCH的调度方式不同，用于传输HARQ信息的目标PUCCH的资源的确定方式也有所不同。
A)该PDSCH为PDCCH调度的PDSCH
在本实施例中，由于支持多DCI调度方案，为同一终端设备服务的网络设备可以分别通过各自的PDCCH中的DCI为终端设备调度PDSCH。如前所述，每个网络设备可以分别通过各自的DCI调度PDSCH，并在各自的DCI中指示用于传输HARQ的PUCCH的资源。
对于同一网络设备而言，为同一终端设备调度的PDSCH有可能是一个，也有可能是多个。若同一网络设备为同一终端设备调度的PDSCH为多个，针对该多个PDSCH反馈的HARQ信息可以在一个UCI中反馈，也可以在多个UCI中反馈，本申请对此不作限定。
对于同一终端设备而言，被调度的PDSCH有可能是一个，也有可能是多个。本申请对此不作限定。若被调度的PDSCH为多个，该多个PDSCH可能为同一网络设备调度，也可能为多个网络设备调度。当多个PDSCH为多个网络设备调度的PDSCH时，终端设备可以分别基于每个网络设备的调度确定与各网络设备对应的目标PUCCH的资源。
在本实施例中，为方便说明，假设终端设备接收到来自第一网络设备的调度。可选地，该方法400还包括：终端设备接收PDSCH的调度信息，该调度信息用于调度PDSCH。相应地，第一网络设备发送该PDSCH的调度信息。
具体地，该调度信息可以为第一网络设备向终端设备发送的用于调度PDSCH的DCI。第一网络设备可以通过该DCI为终端设备调度PDSCH和指示目标PUCCH的资源的具体方法在上文中已经做了详细说明，为了简洁，这里不再赘述。
如前所述，网络设备可以通过高层参数，如PUCCH-config IE，为终端设备配置PUCCH资源列表和PUCCH资源集列表。终端设备可以根据待发送的UCI的长度选择PUCCH资源集，并可以根据DCI中的指示，进一步从选择的PUCCH资源集中确定目标PUCCH的资源。
也就是说，当UCI仅包含HARQ信息，且该HARQ信息所针对的PDSCH为DCI调度的PDSCH时，该目标PUCCH的资源可以由PUCCH配置确定。
应理解，这里仅为示例，描述了第一网络设备向终端设备发送PDSCH的调度信息的步骤，但这不应对本申请构成任何限定。终端设备还可能接收到除第一网络设备之外的其他网络设备发送的用于调度其他PDSCH的调度信息，本申请对此不作限定。
B)PDSCH为SPS PDSCH
当PDSCH为SPS PDSCH时，网络设备可以通过SPS配置为终端设备配置用于传输HARQ信息的目标PUCCH的资源。具体地，网络设备可以通过高层参数，如SPS-Config IE，向终端设备指示PUCCH资源的标识，如在n1PUCCH-AN字段指示PUCCH-ResourceId。终端设备可以根据该PUCCH资源的标识，确定目标PUCCH的资源。
也就是说，当UCI仅包含HARQ信息，且该HARQ信息所针对的PDSCH为SPS PDSCH时，该目标PUCCH的资源可以由SPS配置确定。
情况二、UCI仅包括CSI
UCI仅包括CSI还可以进一步分为UCI仅包括一个CSI和UCI包括多个CSI两种情况。
终端设备可以基于一个CSI上报配置中所指示的上报量和上报使用的PUCCH资源，上报一个CSI。换句话说，终端设备上报的一个CSI对应一个CSI上报配置。
如前所述，该CSI可以为周期CSI，也可以为半持续CSI。网络设备可能触发了一个或多个不同周期的CSI，也可能触发了半持续CSI。当不同周期的CSI在某一时段发生重叠，或者，周期CSI和半持续CSI在某一时段发生重叠，终端设备在该时段就有可能上报多个CSI，例如，在同一个时隙上报多个CSI。也就是UCI包括多个CSI。
当终端设备传输一个CSI时，可以基于CSI上报配置和DCI确定目标PUCCH的资源。例如，可以基于CSI上报配置中的pucch-CSI-ResourceList和DCI中激活的BWP确定目标PUCCH的资源；当终端设备传输多个CSI时，可以基于PUCCH配置确定目标PUCCH的资源，例如，可以基于PUCCH配置中的multi-CSI-PUCCH-ResourceList确定目标PUCCH的资源。
也就是说，当UCI仅包含CSI时，若CSI个数为1，该目标PUCCH资源可以由CSI上报配置确定；若CSI个数大于1，该目标PUCCH资源可以由PUCCH配置确定。
情况三、UCI包括HARQ信息和CSI
若PDSCH为PDCCH调度的PDSCH，则终端设备可以根据该PDCCH携带的DCI中的PUCCH resource indicator，确定目标PUCCH的资源。该HARQ信息和CSI均可以通过该目标PUCCH的资源传输。该目标PUCCH的资源可以由PUCCH配置确定。
若PDSCH不是PDCCH调度的PDSCH，则终端设备可以根据情况二中的方式确定目标PUCCH的资源，该HARQ信息和CSI均可以通过该目标PUCCH的资源传输。该目标PUCCH的资源可以由CSI配置或PUCCH配置确定。
综上所述，目标PUCCH的资源可以由PUCCH配置确定，或者也可以由CSI上报配置确定，或者也可以由SPS配置确定。
上文中结合UCI中包含的不同信息详细说明了终端设备确定目标PUCCH的资源的具体过程。但应理解，这不应对本申请构成任何限定。本申请对于UCI所包含的信息以及终端设备确定目标PUCCH的资源的具体方法不作限定。
可选地，该方法400还包括：步骤420，终端设备接收PUSCH的调度信息，该调度信息用于调度PUSCH。对于终端设备而言，与其通信的网络设备是透明的，终端设备并不知道同时由几个网络设备为其服务。因此，终端设备并不知道该PUSCH的调度信息是否由上述第一网络设备发送。为方便说明和理解，这里暂且将发送该PUSCH的调度信息的网络设备记作第二网络设备。可以理解，该第二网络设备与上述第一网络设备可能为同一网络设备，也可能为不同的网络设备。终端设备可以在后续流程中基于本申请提供的方法确定该第二网络设备与上述第一网络设备是否为同一网络设备。
具体地，该PUSCH的调度信息可以为第二网络设备向终端设备发送的DCI。该第二网络设备可以通过该DCI为终端设备指示PUSCH的时频资源、调制编码方式等信息。
应理解，图中仅为便于示例，示出了第二网络设备向终端设备发送PUSCH的调度信息的步骤，但这不应对本申请构成任何限定。终端设备还可能接收到除第二网络设备之外的其他网络设备发送的用于调度其他PUSCH的调度信息，本申请对此不作限定。
还应理解，本申请对于PUSCH的调度信息和PDSCH的调度信息的发送和接收的先后顺序不做限定。
终端设备可以根据上文所确定的目标PUCCH的资源和PUSCH的资源确定二者是否重叠。在目标PUCCH与PUSCH间存在资源重叠的情况下，终端设备可以执行步骤430，终端设备确定PUSCH与目标PUCCH是否关联。
终端设备在确定了目标PUCCH和PUSCH之后，可以进一步确定目标PUCCH与PUSCH的资源是否发生重叠。若未发生重叠，则终端设备可以直接将UCI通过PUCCH发送给第一网络设备，将上行数据通过PUSCH发送给第二网络设备。若发生重叠，由于终端设备并不知道上述PUCCH和PUSCH是否由同一网络设备调度，为了避免把PUCCH上的UCI放到与之不具有关联关系的PUSCH上发送导致网络设备在接收到PUSCH后无法成功解调译码，在本实施例中，终端设备可以进一步确定该目标PUCCH和PUSCH是否具有关联关系，或者说，该目标PUCCH与PUSCH是否发送给同一网络设备，或者说，确定上述第一网络设备和第二网络设备是否为同一网络设备。终端设备在确定目标PUCCH和PUSCH具有关联关系时，可以确定该目标PUCCH和PUSCH是发送给同一网络设备的，因此可以将原本通过目标PUCCH传输的UCI通过PUSCH传输给该网络设备；否则，可以暂时不发送该UCI，也就是不使用该目标PUCCH或PUSCH传输该UCI。
如前所述，PUSCH可以由PDCCH调度，终端设备在接收到PDCCH时可以确定该PDCCH的PDCCH配置。因此，当目标PUCCH的资源与上述PDCCH配置关联时，该PUCCH与PUSCH关联。
由于UCI中包含的内容，用于确定目标PUCCH的资源的配置参数也不同，例如，当UCI中仅包含HARQ信息时，且该HARQ信息是针对PDCCH调度的PDSCH反馈的HARQ信息时，该目标PUCCH的资源可以由PUCCH配置确定；当UCI中仅包含HARQ信息时，且该HARQ信息对应的PDSCH不是由PDCCH调度的(如SPS PDSCH)时，该目标PUCCH的资源可以由SPS配置确定；当UCI中仅包含一个CSI时，该目标PUCCH的资源可以由CSI上报配置确定；当UCI中仅包含多个CSI时，该目标PUCCH的资源可以由PUCCH配置确定；当UCI中包含HARQ信息和CSI(一个或多个)且该HARQ信息是针对PDCCH调度的PDSCH反馈的HARQ信息时，该目标PUCCH的资源可以由PUCCH配置确定；当UCI中包含HARQ信息和一个CSI，且该HARQ信息对应的PDSCH不是由PDCCH调度的(如SPS PDSCH)，该目标PUCCH的资源可以由CSI上报配置确定；当UCI中包含HARQ信息和多个CSI，且该HARQ信息对应的PDSCH不是由PDCCH调度的(如SPS PDSCH)，该目标PUCCH的资源可以由PUCCH配置确定。
下文中，为方便说明，将用于确定目标PUCCH的资源的PUCCH配置记作目标PUCCH的PUCCH配置，将用于确定目标PUCCH的资源的CSI上报配置记作目标PUCCH的CSI上报配置，将用于确定目标PUCCH的资源的SPS配置记作目标PUCCH的SPS配置。
当目标PUCCH的资源由PUCCH配置确定时，终端设备可以基于方法200中的第一配置信息确定与PDCCH配置关联的PUCCH配置，进而确定该目标PUCCH的PUCCH配置与PDCCH配置是否关联。
此外，当网络设备通过PDCCH调度PDSCH时，可以指示目标PUCCH的资源。终端设备也可以直接基于用于调度PDSCH的PDCCH和用于调度PUSCH的PDCCH是否属于同一PDCCH配置来确定目标PUCCH的PUCCH配置与PDCCH配置是否关联。
即，PUSCH的资源由第一PDCCH调度，PUCCH的资源由第二PDCCH指示，终端设备确定目标PUCCH与PUSCH是否关联，可以通过确定接收第二PDCCH所基于的PDCCH配置与接收第一PDCCH所基于的PDCCH配置是否相同来判断。当第一PDCCH的PDCCH配置与第二PDCCH的PDCCH配置为同一PDCCH配置，则认为该目标PUCCH与PUSCH关联。
当目标PUCCH的资源由CSI上报配置确定时，终端设备可以基于方法300中的第二配置信息确定与PDCCH配置关联的CSI上报配置，进而确定该目标PUCCH的CSI上报配置与PDCCH配置是否关联。
由于上文中结合方法200详细说明了网络设备通过第一配置信息向终端设备指示关联的PUCCH配置和PDCCH配置的具体过程，并结合方法300详细说明了网络设备通过第二配置信息指示关联的CSI上报配置和PDCCH配置的具体过程。终端设备可以根据第一配置信息确定关联的PUCCH配置和PDCCH配置，也可以根据第二配置信息确定关联的CSI上报配置和PDCCH配置，其具体过程在上文方法200和300中已经做了详细说明，为了简洁，这里不再赘述。
当PDSCH没有对应的PDCCH时，如，PDSCH可以为半静态调度(semi-persistant  scheduling，SPS)的PDSCH，目标PUCCH的资源可以由SPS配置确定。由于SPS配置属于BWP下行专用参数，而用于调度PUSCH的PDCCH配置同属于BWP下行专用参数，因此，当目标PUCCH的SPS配置所属的BWP下行专用参数与该PDCCH的PUCCH配置所属的BWP下行专用参数为同一组BWP下行专用参数时，可以认为该目标PUCCH与PUSCH关联。
可选地，网络设备还可以为PUCCH配置中的每一个PUCCH资源的配置参数配置一个关联的PDCCH配置。具体地，PUCCH配置中可以包括多个PUCCH资源的配置参数，每个PUCCH资源的配置参数中可以包括所关联的PDCCH配置的指示。该PDCCH配置的指示例如可以是该PDCCH配置的标识，或者其他可用于指示PDCCH配置的信息。上文中已经结合不同的方式对指示PDCCH配置的方法做了详细说明，为了简洁，这里不再赘述。
这种方式可理解为网络设备为PUCCH资源池中的每一个PUCCH资源的配置参数配置一个关联的PDCCH配置。上述目标PUCCH可以取自该PUCCH资源池。因此，基于网络设备为每个PUCCH资源配置的关联的PDCCH配置，可以确定目标PUCCH所关联的PDCCH配置。
当网络设备通过PDCCH调度PUSCH时，可以基于接收该PDCCH的PDCCH配置与目标PUCCH所关联的PDCCH配置是否为同一PDCCH配置来确定目标PUCCH与PUSCH是否关联。
进一步地，当终端设备基于PDCCH配置来确定PUSCH与PUCCH是否关联时，还可进一步扩展该关联关系。即PUCCH的资源关联的PDCCH配置与用于调度PUSCH的PDCCH的PDCCH配置属于同一PDCCH配置组时，可以认为该PUCCH与PUSCH关联。
具体地，若第一网络设备和第二网络设备基于CoMP技术为同一终端设备服务的同时，第一网络设备和/或第二网络设备还基于载波聚合为终端设备调度更多的频谱资源。例如，该第一网络设备可以在CC#1向终端设备发送PDCCH#1，以调度PDSCH#1，并指示在PUCCH#1传输针对该PDSCH#1反馈的HARQ信息。第一网络设备还可以在CC#1向该终端设备发送PDCCH#2，以调度PUSCH#1。同时，第一网络设备还可以在CC#2向终端设备发送PDCCH#3，以调度PDSCH#2，并指示PUCCH#2用于传输针对PDSCH#2反馈的HARQ信息。
而PDCCH配置是基于每个小区的每个BWP配置的，第一网络设备分别在CC#1和CC#2发送PDCCH所基于的PDCCH配置可能不同。也就是说，同一网络设备可能基于两个或更多个不同的PDCCH配置向终端设备发送PDCCH。
若终端设备基于不同的PDCCH配置确定关联的PUCCH和PUSCH，可能会将同一网络设备调度的PUCCH和PUSCH当成不同网络设备调度的PUCCH和PUSCH。如果PUCCH#1、PUCCH#2以及PUSCH#1存在资源重叠，则终端设备可能仅将基于CC#1生成的UCI通过通过PUSCH#1发送给第一网络设备，该UCI可能包括针对PDSCH#1反馈的HARQ，而不包括针对PDSCH#2的HARQ。但事实上，由于PUCCH#1、PUCCH#2以及PUSCH#1均发送第一网络设备，第一网络设备可能会在PUSCH#1上接收基于CC#1和CC#2生成的UCI。由于终端设备所发送的UCI与第一网络设备所期待的UCI的长度可能不同，第一网络设备可能无法正确解析出UCI中的信息。
因此，本申请另提出了PDCCH配置组的概念。每个PDCCH配置组可以包括多个PDCCH配置，每个PDCCH配置是基于一个小区中的一个BWP配置的。该PDCCH配置组可以通过高层信令配置，例如，可以一个在PDCCH配置组中指示所包含的PDCCH配置。或者，也可以通过高层信令配置各PDCCH配置时，增加一个指示字段，用于指示各PDCCH配置所属的PDCCH配置组。
同一网络设备可以基于PDCCH配置组中的PDCCH配置在不同的小区向终端设备发送PDCCH。当终端设备确定盲检测到的PDCCH所基于的PDCCH配置属于同一PDCCH配置组，则可以认为基于同一个PDCCH配置组盲检测到的PDCCH为同一网络设备发送的，因此，终端设备可以认为基于同一个PDCCH配置组来关联PUCCH配置和PUSCH配置。
上文所列举的用于确定目标PUCCH与PUSCH是否关联的方法均为示例，而不应对本申请构成任何限定。本申请对于确定目标PUCCH与PUSCH是否关联的具体方法不作限定。下文另提供了几种可用于确定目标PUCCH与PUSCH是否关联的方法。需要说明的是，在下文所提供的几种用于确定目标PUCCH与PUSCH是否关联的方法中，PUSCH可以是PDCCH调度的PUSCH，也可以是配置授权的PUSCH，本申请对此不作限定。
在一种实现方式中，由于目标PUCCH的资源可能由PUCCH配置确定，则当PUCCH与PUSCH关联时，该目标PUCCH的PUCCH配置可以与PUSCH的PUSCH配置关联，或者，与PUSCH的配置授权(ConfiguredGrant)配置关联。其中，PUSCH的PUSCH配置可用于确定PDCCH调度的PUSCH的传输参数，PUSCH的ConfiguredGrant配置可用于确定配置授权的PUSCH的资源。
若目标PUCCH的资源由PUCCH配置确定，PUSCH为PDCCH调度的PUSCH，当PUCCH与PUSCH具有关联关系时，该PUCCH与PUSCH可以满足以下列举的至少一项条件：
i)该PUCCH的PUCCH配置与该PUSCH的PUSCH配置属于同一BWP上行专用参数(BWP UL dedicated)中；
ii)该PUCCH的PUCCH配置与该PUSCH的PUSCH配置属于同一BWP上行专用参数中，且PUCCH配置的标识与PUSCH配置的标识相同；
iii)该PUCCH的PUCCH配置中包含该PUSCH的PUSCH配置的指示；
iv)该PUSCH的PUSCH配置中包含该PUCCH的PUCCH配置的指示；
v)该PUSCH的PUSCH配置和该PUCCH的PUCCH配置与同一PDCCH配置关联；
vi)该PUSCH的PUSCH配置和该PUCCH的PUCCH配置属于同一服务小区配置；以及
vii)用于发送PUCCH的发射波束与用于发送PUSCH的PUSCH的发射波束属于同一发射波束组。
上文所列举的条件i)至vii)可以理解为关联的PUCCH配置与PUSCH配置所满足的一项或多项条件。下面详细说明上文列举的各项条件。
条件i)
如前所述，网络设备可以通过服务小区配置为终端设备配置BWP上行专用参数。在本实施例中，网络设备可以为终端设备配置一组或多组BWP上行专用参数，每组BWP 上行专用参数可以包括一个PUCCH配置和一个PUSCH配置。被配置于同一组BWP上行专用参数中的PUCCH配置和PUSCH配置可以认为是基于同一网络设备配置的。例如，基于PUCCH配置确定的PUCCH资源用于传输向某一网络设备发送的UCI，基于PUSCH配置确定的传输参数用于向同一网络设备传输PUSCH。因此，被配置于同一组上行专用参数中的PUCCH配置和PUSCH配置可以认为是关联的。
条件ii)
在本实施例中，网络设备可以通过服务小区配置为终端设备配置BWP上行专用参数。在本实施例中，网络设备可以为终端设备配置一组或多组BWP上行专用参数，每组BWP上行专用参数可以包括一个或多个PUCCH配置和一个或多个PUSCH配置。各PUCCH配置可以通过PUCCH配置标识区分，各PUSCH配置可以通过PUSCH配置标识区分。被配置相同标识的PUCCH配置和PUSCH配置可以认为是基于同一网络设备配置的。因此，被配置于同一组BWP上行专用参数中具有相同标识的PUCCH配置和PUSCH配置可以认为是关联的。
条件iii)
如前所述，网络设备可以通过PUCCH配置为终端设备配置PUCCH资源。在本实施例中，PUCCH配置中可以包括所关联的PUSCH配置的指示。网络设备可以在PUCCH配置中添加用于指示PUSCH配置的字段，以指示所关联的PUSCH配置。该PUSCH配置的指示例如可以是PUSCH配置的标识，或者，其他可用于指示该PUSCH配置的信息。当网络设备在PUCCH配置中指示某一PUSCH配置时，可以认为该PUCCH配置及其所指示的PUSCH配置是基于同一网络设备配置的。因此，PUCCH配置及其所指示的PUSCH配置可以认为是关联的。
条件iv)
条件iv)与条件iii)是相似地。PUSCH配置中可以包括所关联的PUCCH配置的指示。网络设备可以在PUSCH配置中添加用于指示PUCCH配置的字段，以指示所关联的PUCCH配置。该PUCCH配置的指示例如可以是PUCCH配置的标识，或者，其他可用于指示该PUCCH配置的信息。当网络设备在PUSCH配置中指示某一PUCCH配置时，可以认为该PUSCH配置及其所指示的PUCCH配置是基于同一网络设备配置的。因此，PUSCH配置及其所指示的PUCCH配置可以认为是关联的。
条件v)
PUCCH配置和PUSCH配置还可以通过PDCCH配置关联。
在本实施例中，PUCCH配置中可以包括所关联的PDCCH配置的指示，PUSCH配置中也可以包括所关联的PDCCH配置的指示。网络设备分别在PUCCH配置和PUSCH配置中添加用于指示PDCCH配置的字段，以指示所关联的PDCCH配置。该PDCCH配置的指示例如可以是PDCCH配置的标识，或者，其他可用于指示该PDCCH配置的信息。当网络设备分别在PUCCH配置和PUSCH配置中指示同一PDCCH配置时，可以认为该PUCCH配置和PUSCH配置与同一PDCCH配置关联，则该PUSCH配置与该PUCCH配置也关联。
进一步地，条件v)可以进一步扩展为PUSCH配置中指示的关联的PDCCH配置与PUCCH配置中指示的关联的PDCCH配置属于同一PDCCH配置组。
上文已经详细说明了PDCCH配置组的概念，为了简洁，这里不再赘述。
当PUCCH的资源由PUCCH配置确定时，若该PUCCH的PUCCH配置所关联的PDCCH配置与PUSCH配置所关联的PDCCH配置属于同一PDCCH配置组时，可以认为该PUCCH与PUSCH关联。
条件i)
在本实施例中，网络设备可以通过服务小区配置为终端设备配置PUSCH配置和PUCCH配置。例如，网络设备可以通过高层参数ServingCellConfig IE为每个终端设备配置一个或多个BWP。被配置于同一服务小区配置中的PUCCH配置和PUSCH配置可以认为是关联的。
条件vii)
用于发送PUCCH的发射波束与用于发送PUSCH的PUSCH的发射波束可以属于同一发射波束组。如前所述，终端设备可以根据PUCCH配置和网络设备指示的SRI确定被选择的空间关系，进而确定用于发送PUCCH的发射波束。终端设备可以根据SRS配置和网络设备指示的SRI确定被选择的SRS resource，进而确定用于发送PUSCH的发射波束。
在本实施例中，网络设备可以在PUCCH配置中指示各参考信号资源所属的参考信号资源组，例如，在PUCCH配置中的PUCCH空间关系信息(PUCCH-SpatialRelationInfo)中增加字段，分别指示SSB资源所属的参考信号资源组、非零功率CSI-RS资源以及SRS所属的参考信号资源组。又例如，在PUCCH配置中的PUCCH-SpatialRelationInfo中增加字段，指示该PUCCH-SpatialRelationInfo中定义的全部参考信号资源所属的参考信号资源组。
该字段例如可以为参考信号资源组标识，或者天线面板标识，或者其他可用于区分不同参考信号资源组的信息。
相应地，网络设备可以在SRS配置中指示各参考信号资源所属的参考信号资源组，例如，在SRS配置中的SRS空间关系信息(SRS-SpatialRelationInfo)中增加字段，分别指示SSB资源所属的参考信号资源组、非零功率CSI-RS资源以及SRS所属的参考信号资源组。又例如，在SRS配置中的SRS-SpatialRelationInfo中增加字段，指示该SRS-SpatialRelationInfo中定义的全部参考信号资源所属的参考信号资源组。
该字段例如可以为参考信号资源组标识，或者天线面板标识，或者其他可用于区分不同参考信号资源组的信息。
基于上述设计，属于同一参考信号资源组的参考信号资源所确定的发射波束可以属于同一发射波束组，或者说，属于同一参考信号资源组的参考信号资源所确定的发射波束可以由同一天线面板的天线发射。
当终端设备接收到的高层信令(如MAC-CE)激活的空间关系(即，用于PUCCH的空间关系)中的参考信号资源与物理层信令(如DCI)指示的空间关系(即，用于PUSCH的空间关系)中的参考信号资源属于同一参考信号资源组，则该PUCCH的发射波束与PUSCH的发射波束属于同一发射波束组，则可以认为该PUCCH与PUSCH关联。
若目标PUCCH的资源由PUCCH配置确定，PUSCH为配置授权的PUSCH，当PUCCH与PUSCH具有关联关系时，该PUCCH与PUSCH可以满足以下列举的至少一项条件：
i)该PUCCH的PUCCH配置与该PUSCH的ConfiguredGrant配置属于同一BWP上 行专用参数(BWP UL dedicated)中；
ii)该PUCCH的ConfiguredGrant配置与该PUSCH的PUSCH配置属于同一BWP UL dedicated中，且PUCCH配置的标识与PUSCH配置的标识相同；
iii)该PUCCH的PUCCH配置中包含该PUSCH的ConfiguredGrant配置的指示；
iv)该PUSCH的ConfiguredGrant配置中包含该PUCCH的PUCCH配置的指示；
v)该PUSCH的ConfiguredGrant配置和该PUCCH的PUCCH配置属于同一服务小区配置；以及
vi)用于发送PUCCH的发射波束与用于发送PUSCH的PUSCH的发射波束属于同一发射波束组。
上文所列举的条件i)至vii)可以理解为关联的PUCCH配置与ConfiguredGrant配置所满足的一项或多项条件。下面详细说明上文列举的各项条件。
条件i)
如前所述，网络设备可以通过服务小区配置为终端设备配置BWP上行专用参数。在本实施例中，网络设备可以为终端设备配置一组或多组BWP上行专用参数，每组BWP上行专用参数可以包括一个PUCCH配置和一个ConfiguredGrant配置。被配置于同一组BWP上行专用参数中的PUCCH配置和ConfiguredGrant配置可以认为是基于同一网络设备配置的。例如，基于PUCCH配置确定的PUCCH资源用于传输向某一网络设备发送的UCI，基于ConfiguredGrant配置确定的资源可用于向同一网络设备传输PUSCH。因此，被配置于同一组上行专用参数中的PUCCH配置和ConfiguredGrant配置可以认为是关联的。
条件ii)
在本实施例中，网络设备可以通过服务小区配置为终端设备配置BWP上行专用参数。在本实施例中，网络设备可以为终端设备配置一组或多组BWP上行专用参数，每组BWP上行专用参数可以包括一个或多个PUCCH配置和一个或多个ConfiguredGrant配置。各PUCCH配置可以通过PUCCH配置标识区分，各ConfiguredGrant配置可以通过ConfiguredGrant配置标识区分。被配置相同标识的PUCCH配置和ConfiguredGrant配置可以认为是基于同一网络设备配置的。因此，被配置于同一组BWP上行专用参数中具有相同标识的PUCCH配置和ConfiguredGrant配置可以认为是关联的。
条件iii)
如前所述，网络设备可以通过PUCCH配置为终端设备配置PUCCH资源。在本实施例中，PUCCH配置中可以包括所关联的ConfiguredGrant配置的指示。网络设备可以在PUCCH配置中添加用于指示ConfiguredGrant配置的字段，以指示所关联的ConfiguredGrant配置。该ConfiguredGrant配置的指示例如可以是ConfiguredGrant配置的标识，或者，其他可用于指示该ConfiguredGrant配置的信息。当网络设备在PUCCH配置中指示某一ConfiguredGrant配置时，可以认为该PUCCH配置及其所指示的ConfiguredGrant配置是基于同一网络设备配置的。因此，PUCCH配置及其所指示的ConfiguredGrant配置可以认为是关联的。
条件iv)
条件iv)与条件iii)是相似地。ConfiguredGrant配置中可以包括所关联的PUCCH配 置的指示。网络设备可以在ConfiguredGrant配置中添加用于指示PUCCH配置的字段，以指示所关联的PUCCH配置。该PUCCH配置的指示例如可以是PUCCH配置的标识，或者，其他可用于指示该PUCCH配置的信息。当网络设备在ConfiguredGrant配置中指示某一PUCCH配置时，可以认为该ConfiguredGrant配置及其所指示的PUCCH配置是基于同一网络设备配置的。因此，ConfiguredGrant配置及其所指示的PUCCH配置可以认为是关联的。
条件v)
在本实施例中，网络设备可以通过服务小区配置为终端设备配置ConfiguredGrant配置和PUCCH配置。例如，网络设备可以通过高层参数ServingCellConfig IE为每个终端设备配置一个或多个BWP。被配置于同一服务小区配置中的PUCCH配置和ConfiguredGran配置可以认为是关联的。
条件vi)
当PUSCH由ConfiguredGrant配置确定时，用于发送PUSCH的发射波束也可以由SRS配置和网络设备指示的SRI确定的SRS resource确定。上文中已经对PUCCH的发射波束和PUSCH的发射波束属于同一发射波束组这一条件作了详细说明。为了简洁，这里不再赘述。
应理解，当PUCCH与PUSCH关联时，协议可以定义关联的PUCCH与PUSCH满足上文中所列举的某一项或多项。当协议定义了关联的PUCCH与PUSCH满足的上文所列举的某一项或多项条件时，终端设备可以基于该一项或多项条件确定被调度的PUCCH与PUSCH是否关联。
还应理解，当协议定义基于上文列举的某一项或多项条件确定PUCCH与PUSCH是否关联时，并不代表关联的PUCCH与PUSCH不满足上文所列举的其他条件。例如，当协议定义基于上文列举的条件i)确定PUCCH与PUSCH是否关联时，该PUCCH与PUSCH有可能同时满足了条件i)和条件v)。但网络设备和终端设备仅基于条件i)来判断PUCCH与PUSCH是否关联，即便该PUCCH与PUSCH满足条件v)而不满足条件i)，该PUCCH与PUSCH仍被认为不关联。
基于上文所列举的条件，终端设备可以确定被调度的PUCCH与PUSCH是否关联。
在另一种实现方式中，由于目标PUCCH的资源也有可能由CSI上报配置确定，则当PUCCH与PUSCH关联时，该目标PUCCH的CSI上报配置可以与PUSCH的PUSCH配置关联。由于CSI上报配置属于CSI测量配置，网络设备可通过CSI测量配置为终端设备配置一个或多个CSI上报配置。因此，当CSI上报配置与PUSCH配置关联时，该CSI上报配置所属的CSI测量配置也可以与PUSCH配置关联。其中，PUSCH的PUSCH配置可用于确定PUSCH的传输参数，目标PUCCH的CSI上报配置可用于确定PUCCH的资源。
若目标PUCCH的资源由CSI上报配置确定，PUSCH为PDCCH调度的PUSCH，当PUCCH与PUSCH关联时，该PUCCH与PUSCH可以满足以下列举的至少一项条件：
a)该PUCCH的CSI上报配置所属的CSI测量配置(以下简称该PUCCH的CSI测量配置)与该PUSCH的PUSCH配置属于同一BWP上行专用参数(BWP UL dedicated)；
b)该PUCCH的CSI测量配置与该PUSCH的PUSCH配置属于同一BWP上行专用参数，且CSI测量配置的标识与PUSCH配置的标识相同；
c)该PUCCH的CSI测量配置所属的BWP下行专用参数的标识与该PUSCH的PUSCH所属的BWP上行专用参数的标识相同；
d)该PUCCH的CSI测量配置所属的BWP下行专用参数的标识与该PUSCH的PUSCH配置所属的BWP上行专用参数的标识相同，且该PUCCH的CSI测量配置的标识与该PUSCH的PUSCH配置的标识相同；
e)该PUCCH的CSI测量配置的标识与该PUSCH的PUSCH配置所属的BWP上行专用参数的标识相同；
f)该PUCCH的CSI测量配置中包含该PUSCH的PUSCH配置的指示；
g)该PUSCH的PUSCH配置中包含该PUCCH的CSI测量配置的指示；
h)该PUSCH的PUSCH配置和该PUCCH的CSI上报配置与同一PDCCH配置关联；以及
i)用于发送PUCCH的发射波束与用于发送PUSCH的PUSCH的发射波束属于同一发射波束组。
上文所列举的条件a)至i)可以理解为关联的CSI测量配置与PUSCH配置所满足的一项或多项条件。下面详细说明上文列举的各项条件。
条件a)
如前所述，网络设备可以通过服务小区配置为终端设备配置BWP上行专用参数。在本实施例中，网络设备可以为终端设备配置一组或多组BWP上行专用参数，每组BWP上行专用参数可以包括一个CSI测量配置和一个PUSCH配置。被配置于同一组BWP上行专用参数中的CSI测量配置和PUSCH配置可以认为是基于同一网络设备配置的。例如，基于CSI测量配置确定的PUCCH的资源用于传输向某一网络设备发送的UCI，基于PUSCH配置确定的传输参数用于向同一网络设备传输PUSCH。因此，被配置于同一组上行专用参数中的CSI测量配置和PUSCH配置可以认为是关联的。
由于CSI测量配置包括一个或多个CSI上报配置，可选地，该条件a)还可进一步扩展为该PUCCH的CSI上报与PUSCH的PUSCH配置属于同一BWP上行专用参数。
条件b)
在本实施例中，网络设备可以通过服务小区配置为终端设备配置BWP上行专用参数。在本实施例中，网络设备可以为终端设备配置一组或多组BWP上行专用参数，每组BWP上行专用参数可以包括一个或多个CSI测量配置和一个或多个PUSCH配置。各CSI测量配置可以通过CSI测量配置标识区分，各PUSCH配置可以通过PUSCH配置标识区分。被配置相同标识的CSI测量配置和PUSCH配置可以认为是基于同一网络设备配置的。因此，被配置于同一组BWP上行专用参数中具有相同标识的CSI测量配置和PUSCH配置可以认为是关联的。
由于CSI测量配置包括一个或多个CSI上报配置，可选地，条件b)可以进一步扩展为该PUCCH的CSI上报配置与PUSCH的PUSCH配置属于同一BWP上行专用参数，且CSI上报配置的标识与该PUSCH配置的标识相同。
条件c)
网络设备可以通过服务小区配置为终端设备配置BWP上行专用参数和BWP下行专用参数。在本实施例中，网络设备可以为终端设备配置一组或多组BWP上行专用参数以 及一组或多组BWP下行专用参数。每组BWP上行专用参数可以包括一个PUSCH配置，每组BWP下行专用参数可以包括一个CSI测量配置。各组BWP上行专用参数可以通过标识区分，各组BWP下行专用参数也可以通过标识区分。被配置相同标识的BWP上行专用参数和BWP下行专用参数中的配置可以认为是基于同一网络设备配置的。因此，当CSI测量配置与PUSCH配置关联时，该CSI测量配置所属的BWP下行专用参数的标识与该PUSCH配置所属的BWP上行专用参数的标识可以是相同的。
需要说明的是，当网络设备为终端设备配置一组BWP上行专用参数和一组BWP下行专用参数时，可以无需通过标识来区分。此时，该BWP上行专用参数中的配置与BWP下行专用参数中的配置可以认为是基于同一网络设备配置的。也就是说，该BWP上行专用参数中的PUSCH配置与BWP下行专用参数中的CSI测量配置可以认为是关联的。这可以理解为CSI测量配置所属的BWP下行专用参数的标识与PUSCH配置所属的BWP上行专用参数的标识相同的一个特例。
由于CSI测量配置包括一个或多个CSI上报配置，可选地，条件c)可以进一步扩展为该PUCCH的CSI上报配置所属的BWP下行专用参数的标识与该PUSCH的PUSCH配置所属的BWP上行专用参数的标识相同，且该CSI上报配置的标识与该PUSCH配置的标识相同。
条件d)
网络设备可以通过服务小区配置为终端设备配置BWP上行专用参数和BWP下行专用参数。在本实施例中，网络设备可以为终端设备配置一组或多组BWP上行专用参数以及一组或多组BWP下行专用参数。每组BWP上行专用参数可以包括一个或多个PUSCH配置，每组BWP下行专用参数可以包括一个或多个CSI测量配置。各组BWP上行专用参数可以通过标识区分，各组BWP下行专用参数也可以通过标识区分。各PUSCH可以通过标识区分，各CSI测量配置可以通过标识区分。因此，当CSI测量配置与PUSCH配置关联时，该CSI测量配置所属的BWP下行专用参数的标识与PUSCH配置所属的BWP上行专用参数的标识可以是相同的，且该CSI测量配置的标识与PUSCH配置的标识也可以是相同的。
由于CSI测量配置包括一个或多个CSI上报配置，可选地，条件d)可以进一步扩展为该PUCCH的CSI上报配置所属的BWP下行专用参数的标识与该PUSCH的PUSCH配置的BWP上行专用参数的标识相同，且该PUCCH的CSI上报配置的标识与该PUSCH的PUSCH配置的标识相同。
条件e)
在本实施例中，网络设备也可以为终端设备配置一个或多个CSI测量配置以及一组或多组BWP上行专用参数。每组BWP上行专用参数可以包括一个或多个PUSCH配置。当CSI测量配置与PUSCH配置关联时，该CSI测量配置的标识可以与该PUSCH的PUSCH配置所属的BWP上行专用参数的标识相同。
条件f)
如前所述，终端设备可以基于CSI上报配置确定PUCCH的资源。在本实施例中，CSI上报配置所属的CSI测量配置中可以包括所关联的PUSCH配置的指示。网络设备可以在CSI测量配置中添加用于指示PUSCH配置的字段，以指示所关联的PUSCH配置。该 PUSCH配置的指示例如可以是PUSCH的标识，或者，其他可用于指示该PUSCH配置的信息。当网络设备在CSI测量配置中指示某一PUSCH配置时，可以认为该CSI测量配置及其所指示的PUSCH配置是基于同一网络设备配置的。因此，CSI测量配置及其所指示的PUSCH配置可以认为是关联的。
由于CSI测量配置包括一个或多个CSI上报配置，可选地，条件f)可以进一步扩展为CSI上报配置中包括所关联的PUSCH配置的指示。在这种情况下，同一CSI测量配置中的多个CSI上报配置可以关联不同的PUSCH配置。
条件g)
条件g)与条件f)是相似地。PUSCH配置中可以包括所关联的CSI测量配置的指示。网络设备可以在PUSCH配置中添加用于指示CSI测量配置的字段，以指示所关联的CSI测量配置。该CSI测量配置的指示例如可以是CSI测量配置的标识，或者，其他可用于指示该CSI测量配置的信息。当网络设备在PUSCH配置中指示某一CSI测量配置时，可以认为该PUSCH配置及其所指示的CSI测量配置是基于同一网络设备配置的。因此，PUSCH配置及其所指示的CSI测量配置可以认为是关联的。
由于CSI测量配置包括一个或多个CSI上报配置，可选地，条件g)可以进一步扩展为PUSCH配置中包括所关联的CSI上报配置的指示。在这种情况下，同一CSI测量配置中的多个CSI上报配置可以关联不同的PUSCH配置。
条件h)
CSI测量配置和PUSCH配置还可以通过PDCCH配置关联。
在本实施例中，CSI测量配置中可以包括所关联的PDCCH配置的指示，PUSCH配置中也可以包括所关联的PDCCH配置的指示。网络设备分别在CSI测量配置和PUSCH配置中添加用于指示PDCCH配置的字段，以指示所关联的PDCCH配置。该PDCCH配置的指示例如可以是PDCCH配置的标识，或者，其他可用于指示该PDCCH配置的信息。当网络设备分别在CSI测量配置和PUSCH配置中指示同一PDCCH配置时，可以认为该CSI测量配置和PUSCH配置与同一PDCCH配置关联，则该PUSCH配置与该CSI测量配置也关联。
进一步地，条件h)可以进一步扩展为PUSCH配置中指示的关联的PDCCH配置与CSI测量配置中指示的关联的PDCCH配置属于同一PDCCH配置组。
上文对PUSCH配置中指示的关联的PDCCH配置与PUCCH配置中指示的关联的PDCCH配置属于同一PDCCH配置组的情况作了详细说明。这里仅仅将PUCCH配置替换成了CSI测量配置，基于该条件h)确定CSI与PUSCH配置测量配置是否关联的方法与上文中基于条件vi)确定PUCCH配置与PUSCH配置是否关联的方法相似，为了简洁，这里不再赘述。
条件i)
条件i)与上文中条件vi)相同，为了简洁，这里不再赘述。
若目标PUCCH的资源由CSI上报配置确定，PUSCH为配置授权的PUSCH，当PUCCH与PUSCH关联时，该PUCCH与PUSCH可以满足以下列举的至少一项条件：
a)该PUCCH的CSI上报配置所属的CSI测量配置(以下简称该PUCCH的CSI测量配置)与该PUSCH的ConfiguredGrant配置属于同一BWP上行专用参数(BWP UL  dedicated)；
b)该PUCCH的CSI测量配置与该PUSCH的PUSCH配置属于同一BWP上行专用参数，且CSI测量配置的标识与ConfiguredGrant配置的标识相同；
c)该PUCCH的CSI测量配置所属的BWP下行专用参数的标识与该PUSCH的ConfiguredGrant所属的BWP上行专用参数的标识相同；
d)该PUCCH的CSI测量配置所属的BWP下行专用参数的标识与该PUSCH的ConfiguredGrant配置所属的BWP上行专用参数的标识相同，且该PUCCH的CSI测量配置的标识与该PUSCH的PUSCH配置的标识相同；
e)该PUCCH的CSI测量配置的标识与该PUSCH的ConfiguredGrant配置所属的BWP上行专用参数的标识相同；
f)该PUCCH的CSI测量配置中包含该PUSCH的ConfiguredGrant配置的指示；
g)该PUSCH的ConfiguredGrant配置中包含该PUCCH的CSI测量配置的指示；以及
h)用于发送PUCCH的发射波束与用于发送PUSCH的PUSCH的发射波束属于同一发射波束组。
上文所列举的条件a)至h)可以理解为关联的PUCCH配置与ConfiguredGrant配置所满足的一项或多项条件。下面详细说明上文列举的各项条件。由于上文中已经对PUCCH的PUCCH配置与PUSCH的PUSCH配置是否关联的各项条件作了详细说明，这里仅仅将PUSCH配置替换成了ConfiguredGrant配置，因此与上文所述是相似的。为了简洁，这里省略条件a)至h)的详细说明。
上文列举了多个可用于确定PUCCH与PUSCH是否关联的条件。但应理解，这些条件不应对本申请构成任何限定。本领域的技术人员基于相同的构思，对上文列举的某一个或多个条件作出变形或替换，还可以扩展出更多可能的用于确定PUCCH与PUSCH是否关联的方法，这些方法均应落入本申请的保护范围内。
作为示例而非限定，基于上文所列举的条件，可以进一步推出：
同一服务小区配置中的PUCCH和PUSCH可以是关联的；或
同一服务小区配置的同一BWP中的PUCCH和PUSCH可以是关联的；或
同一服务小区配置的同一BWP的同一BWP上行专用参数中的PUCCH和PUSCH可以是关联的。
若终端设备在步骤430中确定目标PUCCH与PUSCH关联，则在步骤440中，终端设备通过PUSCH发送UCI。当终端设备确定目标PUCCH与PUSCH关联时，终端设备可以认为上述第一网络设备和第二网络设备为同一网络设备。终端设备可以通过PUSCH向第二网络设备发送UCI。
除了上文所列举的方法之外，本申请还提供一种可用于确定是否可通过PUSCH传输UCI的方法。其中，该PUSCH可以为PDCCH调度的PUSCH。终端设备可以根据用于调度PUSCH的PDCCH的类型与PUCCH配置的关联关系或PDCCH的类型与CSI上报配置的关联关系来确定是否可通过PUSCH传输UCI。
其中，PDCCH的类型可以理解为DCI的类型。由于DCI可以携带在PDCCH发送给终端设备，故DCI类型也可以引申为PDCCH类型。
具体地，协议可以预先定义PUCCH配置与PDCCH的类型的关联关系。例如，PUCCH配置0可以与主DCI、快DCI和第一级DCI中的一项或多项关联；PUCCH配置1可以与辅DCI、慢DCI和第二级DCI中的一项或多项关联。
当协议预先定义PUCCH配置0可以与主DCI、快DCI和第一级DCI关联，PUCCH配置1可以与辅DCI、慢DCI和第二级DCI关联时，若基于PUCCH配置0所确定的PUCCH与基于主DCI、快DCI或第一级DCI调度的PUSCH发生资源冲突，则可以通过该PUSCH传输本应通过该PUCCH传输的UCI。若基于PUCCH配置1所确定的PUCCH与基于辅DCI、慢DCI或第二级DCI调度的PUSCH发生资源冲突，则可以通过该PUSCH传输本应通过该PUCCH传输的UCI。
协议也可以预先定义CSI上报配置与PDCCH的类型的关联关系。例如，CSI上报配置0可以与主DCI、快DCI和第一级DCI中的一项或多项关联；CSI上报配置1可以与辅DCI、慢DCI和第二级DCI中的一项或多项关联。
当协议预先定义CSI上报配置0可以与主DCI、快DCI和第一级DCI关联，CSI上报配置1可以与辅DCI、慢DCI和第二级DCI关联时，若基于CSI上报配置0所确定的PUCCH与基于主DCI、快DCI或第一级DCI调度的PUSCH发生资源冲突，则可以通过该PUSCH传输本应通过该PUCCH传输的UCI。若基于CSI上报配置1所确定的PUCCH与基于辅DCI、慢DCI或第二级DCI调度的PUSCH发生资源冲突，则可以通过该PUSCH传输本应通过该PUCCH传输的UCI。
协议还可以预先定义CSI测量配置与PDCCH的类型的关联关系。例如，例如，CSI测量配置0可以与主DCI、快DCI和第一级DCI中的一项或多项关联；CSI测量配置1可以与辅DCI、慢DCI和第二级DCI中的一项或多项关联。
当协议预先定义CSI测量配置0可以与主DCI、快DCI和第一级DCI关联，CSI测量配置1可以与辅DCI、慢DCI和第二级DCI关联时，若基于CSI测量配置0中的任意一个CSI上报配置所确定的PUCCH与基于主DCI、快DCI或第一级DCI调度的PUSCH发生资源冲突，则可以通过该PUSCH传输本应通过该PUCCH传输的UCI。若基于CSI测量配置1中的任意一个CSI上报配置所确定的PUCCH与基于辅DCI、慢DCI或第二级DCI调度的PUSCH发生资源冲突，则可以通过该PUSCH传输本应通过该PUCCH传输的UCI。
下面详细说明DCI的类型。
基于DCI中所包含的内容的不同，可以将DCI分为主DCI和辅DCI。其中，辅DCI所包含的信息可以是主DCI所包含的信息的子集。或者说，辅DCI仅包括部分主DCI包含的指示域，即，主DCI比辅DCI包含更多的指示信息。或者，主DCI与辅DCI也可以包含不同的信息。例如，主DCI可以是包含某一项或多项特定参数的DCI。其中，所述特定参数例如可以包括以下至少一项：载波指示(carrier indicator)、部分带宽指示(bandwidth part indicator)、速率匹配指示(rate matching indicator)、零功率信道状态信息参考信号触发(zero power channelstate information reference signal trigger,ZP CSI-RS trigger)；相应地，辅DCI可以为不包含上述任意一项特定参数的DCI。而辅DCI是可以包含以下至少一项的DCI：资源分配(resource allocation)、调制编码方式(MCS)、冗余版本(RV)、新传数据指示(NDI)以及HARQ进程标识(HARQ process ID)。当终端设备盲检测到的 DCI包含有主DCI和辅DCI时，可以认为携带主DCI的PDCCH所基于的PDCCH配置为PDCCH配置0，携带辅DCI的PDCCH所基于的PDCCH配置为PDCCH配置1。
此外，基于DCI所包含的内容的不同，还可以将DCI分为第一级DCI和第二级DCI。第一级DCI中可以指示第二级DCI是否存在，并可进一步指示第二级DCI所在的时域和/或频域位置。当终端设备盲检测到的DCI包含有第一级DCI和第二级DCI时，可以认为携带第一级DCI调度的PDCCH所基于的PDCCH配置为PDCCH配置0，携带第二级DCI的PDCCH所基于的PDCCH配置为PDCCH配置1。
基于DCI出现的频率的不同，可以将DCI分为快DCI和慢DCI。其中，快DCI出现的频率高于慢DCI出现的频率。例如，快DCI可以是每个时隙出现一次，慢DCI可以是多个时隙出现一次。当终端设备盲检测到的DCI包含有快DCI和慢DAI时，可以认为携带快DCI的PDCCH所基于的PDCCH配置为PDCCH配置0，携带慢DCI的PDCCH所基于的PDCCH配置为PDCCH配置1。
基于不同的DCI格式(format)，DCI还可以分为不同格式的DCI，如DCI format 1_0，DCI format 1_1等。当终端设备盲检测到的DCI包含有DCI format 1_0和DCI format 1_1时，可以认为携带DCI format 1_0的PDCCH所基于的PDCCH配置为PDCCH配置0，携带DCI format 1_1的PDCCH所基于的PDCCH配置为PDCCH配置1。
基于相同DCI format的不同配置，也可以区分不同的PDCCH配置。例如，一个DCI中仅包含1个传输块(transport block，TB)的配置信息的字段(例如具体可包括MCS、NDI和RV)，另一个DCI中包含2个TB的配置信息的字段。当终端设备盲检测到的DCI包含有相同DCI format不同配置的DCI时，可以认为携带不同配置的DCI的PDCCH配置所基于的PDCCH配置不同。例如，仅包含1个TB的DCI可对应于PDCCH配置1，包含2个TB的DCI可对应PDCCH配置0。
应理解，上文列举的不同类型的DCI与不同PUCCH配置的关联关系的示例以及不同类型的DCI与不同的CSI上报配置或CSI测量配置的关联关系仅为便于理解而示出，不应对本申请构成任何限定。
终端设备通过PUSCH发送UCI的具体过程可以与现有技术相同，为了简洁，这里省略对其具体过程的详细说明。
终端设备还可以通过PUSCH发送除UCI之外的其他信息，如，上行数据。可选地，步骤440包括：终端设备通过PUSCH发送UCI和上行数据。
若终端设备在步骤430中确定目标PUCCH与PUSCH不关联，则终端设备不通过PUSCH发送UCI。例如等待至下一次调度的PUCCH上发送，或者不发送，本申请对此不作限定。
终端设备不通过PUSCH发送UCI，并不代表终端设备不通过PUSCH传输其他信息，例如，终端设备仍然可以通过PUSCH发送上行数据。可选地，终端设备通过PUSCH发送上行数据。另一方面，网络设备可以预先知道上述目标PUCCH是否是发送给自身的，也可以预先知道上述PUSCH是否由自身调度。也就是说，网络设备可以预先知道该目标PUCCH与PUSCH关联。也就是说，第一网络设备和第二网络设备为同一网络设备。
可选地，在PUCCH和PUSCH的资源到来之前，或者说在步骤440之前，该方法400还包括：步骤450，第二网络设备确定目标PUCCH与PUSCH是否存在资源重叠。若存 在资源重叠，则第二网络设备可以确定终端设备可能通过PUSCH发送UCI。与步骤440对应地，第二网络设备可以在PUSCH上接收UCI。可选地，网络设备还可以在PUSCH接收上行数据。若不存在资源重叠，则第二网络设备可以确定终端设备不会通过PUSCH发送UCI。可选地，第二网络设备在PUSCH上接收上行数据。
相反，如果目标PUCCH与PUSCH不关联，则第一网络设备与第二网络设备为不同的网络设备。
对于第一网络设备而言，由于未调度上述PUSCH，因此可能并不知道终端设备由于目标PUCCH与PUSCH的资源重叠而未发送UCI，可能会尝试在PUCCH上接收UCI，但可能并未接收到UCI。因此，第一网络设备可能重传上一次调度的PDSCH，或者继续等待UCI。
对于第二网络设备而言，由于并不知道目标PUCCH的存在，也不知道目标PUCCH与PUSCH的资源发生重叠，仍然会在PUSCH上接收上行数据。在本实施例中，由于终端设备可以确定PUCCH与PUSCH不关联，则仍然可以在PUSCH上接收到上行数据。
基于上述技术方案，在PUCCH与PUSCH发生资源重叠的情况下，终端设备可以基于PUCCH与PUSCH之间是否关联来确定该PUCCH和PUSCH是否为发送给同一网络设备的。从而可以将针对该网络设备的UCI可以通过PUSCH传输，而避免将针对其他网络设备的UCI也放在该PUSCH上传输。因此，网络设备可以在该PUSCH上接收到UCI，进而确定是否需要重传PDSCH和/或CSI。
相反，如果终端设备无法确定PUCCH与PUSCH之间是否关联，也就无法确定该PUCCH和PUSCH是否为发送给同一网络设备(例如上文所述的第二网络设备)的，就有可能将本该发送给另一网络设备(例如上文所述的第一网络设备或除第二网络设备之外的其他网络设备)的UCI放在PUSCH上传输，导致该第二网络设备在接收到PUSCH的时候无法准确地解析出PUSCH上传输的上行数据。
因此，通过本申请实施例提供的发送和接收UCI的方法，网络设备可以在PUSCH上接收到UCI，从而可以基于接收到的UCI做出合理的决策，避免不必要的重传带来的资源浪费，有利于提高数据传输性能，提高用户体验。
以上，结合图2至图4详细说明了本申请实施例提供的方法。以下，结合图5至图7详细说明本申请实施例提供的通信装置。
图5是本申请实施例提供的通信装置的示意性框图。如图所示，该通信装置1000可以包括通信单元1100和处理单元1200。
在一种可能的设计中，该通信装置1000可对应于上文方法实施例中的终端设备，例如，可以为终端设备，或者配置于终端设备中的芯片。
具体地，该通信装置1000可对应于根据本申请实施例的方法200至方法400中的终端设备，该通信装置1000可以包括用于执行图2中的方法200、图3中的方法300或图4中的方法400中的终端设备执行的方法的单元。并且，该通信装置1000中的各单元和上述其他操作和/或功能分别为了实现图2中的方法200图3中的方法300或图4中的方法400的相应流程。
其中，当该通信装置1000用于执行图2中的方法200时，通信单元1100可用于执行方法200中的步骤220，处理单元1200可用于执行方法200中的步骤230。
当该通信装置1000用于执行图3中的方法300时，通信单元1100可用于执行方法300中的步骤320，处理单元1200可用于执行方法300中的步骤330。
当该通信装置1000用于执行图4中的方法400时，通信单元1100可用于执行方法400中的步骤420和步骤440，处理单元1200可用于执行方法400中的步骤410和步骤430。
应理解，各单元执行上述相应步骤的具体过程在上述方法实施例中已经详细说明，为了简洁，在此不再赘述。
还应理解，该通信装置1000为终端设备时，该通信装置1000中的通信单元1100可对应于图6中示出的终端设备2000中的收发器2020，该通信装置1000中的处理单元1200可对应于图6中示出的终端设备2000中的处理器2010。
还应理解，该通信装置1000为配置于终端设备中的芯片时，该通信装置1000中的通信单元1100可以为输入/输出接口。
在另一种可能的设计中，该通信装置1000可对应于上文方法实施例中的网络设备，例如，可以为网络设备，或者配置于网络设备中的芯片。
在另一种可能的设计中，该通信装置1000可对应于上文方法实施例中的网络设备，例如，可以为网络设备，或者配置于网络设备中的芯片。
具体地，该通信装置1000可对应于根据本申请实施例的方法200至方法400中的网络设备，该通信装置1000可以包括用于执行图2中的方法200、图3中的方法300或图4中的方法400中的网络设备执行的方法的单元。并且，该通信装置1000中的各单元和上述其他操作和/或功能分别为了实现图2中的方法200图3中的方法300或图4中的方法400的相应流程。
其中，当该通信装置1000用于执行图2中的方法200时，通信单元1100可用于执行方法200中的步骤220，处理单元1200可用于执行方法200中的步骤210。
当该通信装置1000用于执行图3中的方法300时，通信单元1100可用于执行方法300中的步骤320，处理单元1200可用于执行方法300中的步骤310。
当该通信装置1000用于执行图4中的方法400时，通信单元1100可用于执行方法400中的步骤420和步骤440，处理单元1200可用于执行方法400中的步骤450。
还应理解，该通信装置1000为网络设备时，该通信装置1000中的通信单元为可对应于图7中示出的网络设备3000中的收发器3200，该通信装置1000中的处理单元1200可对应于图7中示出的网络设备3000中的处理器3100。
还应理解，该通信装置1000为配置于网络设备中的芯片时，该通信装置1000中的通信单元1100可以为输入/输出接口。
图6是本申请实施例提供的终端设备2000的结构示意图。该终端设备2000可应用于如图1所示的系统中，执行上述方法实施例中终端设备的功能。
如图所示，该终端设备2000包括处理器2010和收发器2020。可选地，该终端设备2000还包括存储器2030。其中，处理器2010、收发器2002和存储器2030之间可以通过内部连接通路互相通信，传递控制和/或数据信号，该存储器2030用于存储计算机程序，该处理器2010用于从该存储器2030中调用并运行该计算机程序，以控制该收发器2020收发信号。可选地，终端设备2000还可以包括天线2040，用于将收发器2020输出的上 行数据或上行控制信令通过无线信号发送出去。
上述处理器2010可以和存储器2030可以合成一个处理装置，处理器2010用于执行存储器2030中存储的程序代码来实现上述功能。具体实现时，该存储器2030也可以集成在处理器2010中，或者独立于处理器2010。该处理器2010可以与图4中的处理单元对应。
上述收发器2020可以与图5中的通信单元对应，也可以称为收发单元。收发器2020可以包括接收器(或称接收机、接收电路)和发射器(或称发射机、发射电路)。其中，接收器用于接收信号，发射器用于发射信号。
应理解，图6所示的终端设备2000能够实现图2至图4所示方法实施例中涉及终端设备的各个过程。终端设备2000中的各个模块的操作和/或功能，分别为了实现上述方法实施例中的相应流程。具体可参见上述方法实施例中的描述，为避免重复，此处适当省略详述描述。
上述处理器2010可以用于执行前面方法实施例中描述的由终端设备内部实现的动作，而收发器2020可以用于执行前面方法实施例中描述的终端设备向网络设备发送或从网络设备接收的动作。具体请见前面方法实施例中的描述，此处不再赘述。
可选地，上述终端设备2000还可以包括电源2050，用于给终端设备中的各种器件或电路提供电源。
除此之外，为了使得终端设备的功能更加完善，该终端设备2000还可以包括输入单元2060、显示单元2070、音频电路2080、摄像头2090和传感器2100等中的一个或多个，所述音频电路还可以包括扬声器2082、麦克风2084等。
图7是本申请实施例提供的网络设备的结构示意图，例如可以为基站的结构示意图。该基站3000可应用于如图1所示的系统中，执行上述方法实施例中网络设备的功能。
如图所示，该基站3000可以包括一个或多个射频单元，如远端射频单元(remote radio unit，RRU)3100和一个或多个基带单元(baseband unit，BBU)(也可称为数字单元，digital unit，DU)3200。所述RRU 3100可以称为收发单元，与图5中的通信单元1200对应。可选地，该收发单元3100还可以称为收发机、收发电路、或者收发器等等，其可以包括至少一个天线3101和射频单元3102。可选地，收发单元3100可以包括接收单元和发送单元，接收单元可以对应于接收器(或称接收机、接收电路)，发送单元可以对应于发射器(或称发射机、发射电路)。所述RRU 3100部分主要用于射频信号的收发以及射频信号与基带信号的转换，例如用于向终端设备发送指示信息。所述BBU 3200部分主要用于进行基带处理，对基站进行控制等。所述RRU 3100与BBU 3200可以是物理上设置在一起，也可以物理上分离设置的，即分布式基站。
所述BBU 3200为基站的控制中心，也可以称为处理单元，可以与图5中的处理单元1100对应，主要用于完成基带处理功能，如信道编码，复用，调制，扩频等等。例如所述BBU(处理单元)可以用于控制基站执行上述方法实施例中关于网络设备的操作流程，例如，生成上述指示信息等。
在一个示例中，所述BBU 3200可以由一个或多个单板构成，多个单板可以共同支持单一接入制式的无线接入网(如LTE网)，也可以分别支持不同接入制式的无线接入网(如LTE网，5G网或其他网)。所述BBU 3200还包括存储器3201和处理器3202。所 述存储器3201用以存储必要的指令和数据。所述处理器3202用于控制基站进行必要的动作，例如用于控制基站执行上述方法实施例中关于网络设备的操作流程。所述存储器3201和处理器3202可以服务于一个或多个单板。也就是说，可以每个单板上单独设置存储器和处理器。也可以是多个单板共用相同的存储器和处理器。此外每个单板上还可以设置有必要的电路。
应理解，图7所示的基站3000能够实现图2至图4方法实施例中涉及网络设备的各个过程。基站3000中的各个模块的操作和/或功能，分别为了实现上述方法实施例中的相应流程。具体可参见上述方法实施例中的描述，为避免重复，此处适当省略详述描述。
上述BBU 3200可以用于执行前面方法实施例中描述的由网络设备内部实现的动作，而RRU 3100可以用于执行前面方法实施例中描述的网络设备向终端设备发送或从终端设备接收的动作。具体请见前面方法实施例中的描述，此处不再赘述。
本申请实施例还提供了一种处理装置，包括处理器和接口。所述处理器可用于执行上述方法实施例中的方法。
应理解，上述处理装置可以是一个芯片。例如，该处理装置可以是现场可编程门阵列(field programmable gate array，FPGA)，可以是专用集成芯片(application specific integrated circuit，ASIC)，还可以是系统芯片(system on chip，SoC)，还可以是中央处理器(central processor unit，CPU)，还可以是网络处理器(network processor，NP)，还可以是数字信号处理电路(digital signal processor，DSP)，还可以是微控制器(micro controller unit，MCU)，还可以是可编程控制器(programmable logic device，PLD)或其他集成芯片。
在实现过程中，上述方法的各步骤可以通过处理器中的硬件的集成逻辑电路或者软件形式的指令完成。结合本申请实施例所公开的方法的步骤可以直接体现为硬件处理器执行完成，或者用处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器，处理器读取存储器中的信息，结合其硬件完成上述方法的步骤。为避免重复，这里不再详细描述。
应注意，本申请实施例中的处理器可以是一种集成电路芯片，具有信号的处理能力。在实现过程中，上述方法实施例的各步骤可以通过处理器中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器可以是通用处理器、数字信号处理器(DSP)、专用集成电路(ASIC)、现场可编程门阵列(FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合本申请实施例所公开的方法的步骤可以直接体现为硬件译码处理器执行完成，或者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器，处理器读取存储器中的信息，结合其硬件完成上述方法的步骤。
可以理解，本申请实施例中的存储器可以是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(read-only memory，ROM)、可编程只读存储器(programmable ROM，PROM)、可擦除可编程只 读存储器(erasable PROM，EPROM)、电可擦除可编程只读存储器(electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(random access memory，RAM)，其用作外部高速缓存。通过示例性但不是限制性说明，许多形式的RAM可用，例如静态随机存取存储器(static RAM，SRAM)、动态随机存取存储器(dynamic RAM，DRAM)、同步动态随机存取存储器(synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(double data rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(synchlink DRAM，SLDRAM)和直接内存总线随机存取存储器(direct rambus RAM，DR RAM)。应注意，本文描述的系统和方法的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
根据本申请实施例提供的方法，本申请还提供一种计算机程序产品，该计算机程序产品包括：计算机程序代码，当该计算机程序代码在计算机上运行时，使得该计算机执行图2至图4所示实施例中任意一个实施例的方法。
根据本申请实施例提供的方法，本申请还提供一种计算机可读介质，该计算机可读介质存储有程序代码，当该程序代码在计算机上运行时，使得该计算机执行图2至图4所示实施例中任意一个实施例的方法。
根据本申请实施例提供的方法，本申请还提供一种系统，其包括前述的一个或多个终端设备以及一个或多个网络设备。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机指令时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(digital subscriber line，DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如，软盘、硬盘、磁带)、光介质(例如，高密度数字视频光盘(digital video disc，DVD))、或者半导体介质(例如，固态硬盘(solid state disc，SSD))等。
上述各个装置实施例中网络设备与终端设备和方法实施例中的网络设备或终端设备完全对应，由相应的模块或单元执行相应的步骤，例如通信单元(收发器)执行方法实施例中接收或发送的步骤，除发送、接收外的其它步骤可以由处理单元(处理器)执行。具体单元的功能可以参考相应的方法实施例。其中，处理器可以为一个或多个。
在本说明书中使用的术语“部件”、“模块”、“系统”等用于表示计算机相关的实体、硬件、固件、硬件和软件的组合、软件、或执行中的软件。例如，部件可以是但不限于，在处理器上运行的进程、处理器、对象、可执行文件、执行线程、程序和/或计算机。通过图示，在计算设备上运行的应用和计算设备都可以是部件。一个或多个部件可驻留在进程和/或执行线程中，部件可位于一个计算机上和/或分布在两个或更多个计算机之间。 此外，这些部件可从在上面存储有各种数据结构的各种计算机可读介质执行。部件可例如根据具有一个或多个数据分组(例如来自与本地系统、分布式系统和/或网络间的另一部件交互的二个部件的数据，例如通过信号与其它系统交互的互联网)的信号通过本地和/或远程进程来通信。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各种说明性逻辑块(illustrative logical block)和步骤(step)，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
在上述实施例中，各功能单元的功能可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令(程序)。在计算机上加载和执行所述计算机程序指令(程序)时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质，(例如，软盘、硬盘、磁带)、光介质(例如，DVD)、或者半导体介质(例如固态硬盘(solid state disk，SSD))等。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计 算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(read-only memory，ROM)、随机存取存储器(random access memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。

Claims (28)

  1. 一种发送上行控制信息UCI的方法，其特征在于，包括：
    确定物理上行共享信道PUSCH与物理上行控制信道PUCCH存在资源重叠，所述PUSCH由物理下行控制信道PDCCH调度，所述PUCCH用于传输UCI；
    在所述PUCCH与所述PDCCH的PDCCH配置关联的情况下，在所述PUSCH上传输所述UCI。
  2. 如权利要求1所述的方法，其特征在于，所述UCI包括混合自动重传请求HARQ信息和信道状态信息CSI中的至少一项。
  3. 如权利要求1或2所述的方法，其特征在于，所述PUCCH由PUCCH配置确定，所述PUCCH配置与所述PDCCH配置关联。
  4. 如权利要求3所述的方法，其特征在于，所述PUCCH配置中包含所述PDCCH配置的指示。
  5. 如权利要求3所述的方法，其特征在于，所述PUCCH配置与所述PDCCH配置为同一带宽部分BWP而配置，且所述PUCCH配置所属的带宽部分BWP上行专用参数的标识与所述PDCCH配置所属的BWP下行专用参数的标识相同。
  6. 如权利要求1或2所述的方法，其特征在于，所述PUCCH的资源由CSI上报配置确定，所述CSI上报配置与所述PDCCH配置关联。
  7. 如权利要求6所述的方法，其特征在于，所述CSI上报配置中包含所述PDCCH配置的指示。
  8. 如权利要求6所述的方法，其特征在于，所述CSI上报配置所属的CSI测量配置中包含所述PDCCH配置的指示。
  9. 如权利要求6所述的方法，其特征在于，所述CSI上报配置所属的CSI测量配置与所述PDCCH配置属于同一服务小区，且所述CSI测量配置的标识与所述PDCCH配置所属的BWP下行专用参数的标识相同。
  10. 如权利要求6所述的方法，其特征在于，所述CSI上报配置所属的CSI测量配置与所述PDCCH配置属于同一服务小区配置中的同一BWP专用参数。
  11. 如权利要求1或2所述的方法，其特征在于，所述PUCCH的资源取自PUCCH配置中的多个PUCCH资源，每个PUCCH资源由一套PUCCH资源配置参数配置，所述PUCCH资源配置参数中包括所关联的PDCCH配置的指示。
  12. 一种通信装置，其特征在于，包括：处理单元，用于确定物理上行共享信道PUSCH与物理上行控制信道PUCCH存在资源重叠，所述PUSCH由物理下行控制信道PDCCH调度，所述PUCCH用于传输UCI；
    通信单元，用于在所述PUCCH与所述PDCCH的PDCCH配置关联的情况下，在所述PUSCH上传输所述UCI。
  13. 如权利要求12所述的装置，其特征在于，所述UCI包括混合自动重传请求HARQ信息和信道状态信息CSI中的至少一项。
  14. 如权利要求12或13所述的装置，其特征在于，所述PUCCH的资源由PUCCH 配置确定，所述PUCCH配置与所述PDCCH配置关联。
  15. 如权利要求14所述的装置，其特征在于，所述PUCCH配置中包含所述PDCCH配置的指示。
  16. 如权利要求14所述的装置，其特征在于，所述PUCCH配置与所述PDCCH配置为同一带宽部分BWP而配置，且所述PUCCH配置所属的带宽部分BWP上行专用参数的标识与所述PDCCH配置所属的BWP下行专用参数的标识相同。
  17. 如权利要求12或13所述的装置，其特征在于，所述PUCCH的资源由CSI上报配置确定，所述CSI上报配置与所述PDCCH配置关联。
  18. 如权利要求17所述的装置，其特征在于，所述CSI上报配置中包含所述PDCCH配置的指示。
  19. 如权利要求17所述的装置，其特征在于，所述CSI上报配置所属的CSI测量配置中包含所述PDCCH配置的指示。
  20. 如权利要求17所述的装置，其特征在于，所述CSI上报配置所属的CSI测量配置与所述PDCCH配置属于同一服务小区，且所述CSI测量配置的标识与所述PDCCH配置所属的BWP下行专用参数的标识相同。
  21. 如权利要求17所述的装置，其特征在于，所述CSI上报配置所属的CSI测量配置与所述PDCCH配置属于同一服务小区配置中的同一BWP专用参数。
  22. 如权利要求12或13所述的装置，其特征在于，所述PUCCH的资源取自PUCCH配置中的多个PUCCH资源，每个PUCCH资源由一套PUCCH资源配置参数配置，所述PUCCH资源配置参数中包括所关联的PDCCH配置的指示。
  23. 一种通信装置，其特征在于，包括：
    处理器，用于执行如权利要求1至11中任一项所述方法中确定的步骤；
    收发器，用于执行如权利要求1至11中任一项所述方法中传输的步骤。
  24. 一种通信装置，其特征在于，所述装置用于实现如权利要求1至11中任一项所述的方法。
  25. 一种处理装置，其特征在于，包括处理器，所述处理器用于执行存储器中存储的计算机程序，以使得所述装置实现如权利要求1至11中任一项所述的方法。
  26. 一种处理装置，其特征在于，包括：
    存储器，用于存储计算机程序；
    处理器，用于从所述存储器调用并运行所述计算机程序，以使得所述装置实现如权利要求1至11中任一项所述的方法。
  27. 一种计算机可读介质，其特征在于，包括计算机程序，当所述计算机程序在计算机上运行时，使得所述计算机执行如权利要求1至11中任一项所述的方法。
  28. 一种计算机程序产品，所述计算机程序产品包括计算机程序，当所述计算机程序在计算机上运行时，使得计算机执行如权利要求1至11中任一项所述的方法。
PCT/CN2019/105272 2018-09-19 2019-09-11 发送和接收上行控制信息的方法以及通信装置 WO2020057404A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP19862946.1A EP3843303A4 (en) 2018-09-19 2019-09-11 PROCEDURE FOR SENDING AND RECEIVING UPLINK CONTROL INFORMATION AND COMMUNICATION DEVICE
US17/197,227 US11968675B2 (en) 2018-09-19 2021-03-10 Uplink control information sending and receiving method and communications apparatus

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201811092245.6A CN110932820B (zh) 2018-09-19 2018-09-19 发送和接收上行控制信息的方法以及通信装置
CN201811092245.6 2018-09-19

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/197,227 Continuation US11968675B2 (en) 2018-09-19 2021-03-10 Uplink control information sending and receiving method and communications apparatus

Publications (1)

Publication Number Publication Date
WO2020057404A1 true WO2020057404A1 (zh) 2020-03-26

Family

ID=69855043

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/105272 WO2020057404A1 (zh) 2018-09-19 2019-09-11 发送和接收上行控制信息的方法以及通信装置

Country Status (4)

Country Link
US (1) US11968675B2 (zh)
EP (1) EP3843303A4 (zh)
CN (1) CN110932820B (zh)
WO (1) WO2020057404A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP4171154A4 (en) * 2020-07-10 2023-12-20 Huawei Technologies Co., Ltd. METHOD AND DEVICE FOR COMMUNICATION, TERMINAL DEVICE, NETWORK DEVICE AND MEDIUM

Families Citing this family (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220070855A1 (en) * 2019-01-08 2022-03-03 Apple Inc. Systems and methods for control signaling of uplink transmission for multiple antenna panels
CN111885715B (zh) * 2019-05-01 2023-04-28 华为技术有限公司 信道传输方法及相关设备
CN115002916A (zh) * 2019-09-20 2022-09-02 大唐移动通信设备有限公司 资源确定方法及装置
KR20220123452A (ko) * 2020-01-07 2022-09-06 에프쥐 이노베이션 컴퍼니 리미티드 Pucch 자원들을 구성하기 위한 사용자 장비 및 방법
CN114982281A (zh) * 2020-04-03 2022-08-30 Oppo广东移动通信有限公司 物理信道的资源映射方法、终端设备和网络设备
CN114337961A (zh) * 2020-10-10 2022-04-12 北京紫光展锐通信技术有限公司 上行信道传输资源的方法及相关产品
CN114389771A (zh) * 2020-10-19 2022-04-22 大唐移动通信设备有限公司 一种上行信道的传输方法及设备
WO2023123178A1 (zh) * 2021-12-30 2023-07-06 Oppo广东移动通信有限公司 传输上行信号的方法、终端设备、网络设备及存储介质

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102104972A (zh) * 2010-05-24 2011-06-22 电信科学技术研究院 Uci信息传输的配置方法和设备
CN107295677A (zh) * 2016-03-31 2017-10-24 中兴通讯股份有限公司 执行空闲信道评估的反馈方法及装置

Family Cites Families (18)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120106472A1 (en) * 2009-03-31 2012-05-03 Nokia Siemens Networks Oy Methods, Apparatuses, System, Related Computer Program Product and Data Structure for Uplink Scheduling
US20120113827A1 (en) * 2010-11-08 2012-05-10 Sharp Laboratories Of America, Inc. Dynamic simultaneous pucch and pusch switching for lte-a
CN102045861B (zh) * 2011-01-04 2013-09-18 大唐移动通信设备有限公司 上行控制信息的调度及上报方法、系统和设备
US8718003B2 (en) * 2011-06-20 2014-05-06 Samsung Electronics Co., Ltd. System and method for an uplink control signal in wireless communication systems
CN107017971B (zh) * 2011-06-28 2020-06-16 Lg电子株式会社 发送和接收下行数据的方法、用户设备和基站
JP5927661B2 (ja) * 2011-08-12 2016-06-01 シャープ株式会社 端末装置、基地局装置、集積回路および通信方法
ES2921359T3 (es) * 2012-08-02 2022-08-24 Blackberry Ltd Asignación de recurso de canal de control de enlace ascendente para un canal de control de enlace descendente mejorado de un sistema de comunicación móvil
CN104641678B (zh) * 2012-09-16 2019-07-05 Lg 电子株式会社 在支持协作传输的无线通信系统中收发信道状态信息的方法和设备
US8923880B2 (en) * 2012-09-28 2014-12-30 Intel Corporation Selective joinder of user equipment with wireless cell
JP2015065621A (ja) * 2013-09-26 2015-04-09 株式会社Ｎｔｔドコモ ユーザ端末、基地局及び無線通信方法
US9955356B2 (en) * 2014-09-25 2018-04-24 Intel IP Corporation System and method of handling uplink transmission collision for enhanced coverage mode UEs
US9980204B2 (en) * 2015-03-16 2018-05-22 Ofinno Technologies, Llc Channel state information transmission
CN107431942B (zh) * 2015-04-10 2020-09-08 华为技术有限公司 一种信道状态信息的上报方法、用户设备和基站
WO2017099556A1 (ko) * 2015-12-11 2017-06-15 엘지전자 주식회사 상향링크 신호를 전송하는 방법 및 이를 위한 장치
CN107734688B (zh) * 2016-08-12 2023-05-02 中兴通讯股份有限公司 一种信息发送方法及发送设备
US20180132229A1 (en) * 2016-11-04 2018-05-10 Mediatek Inc. Method And Apparatus For Multiplexing Physical Uplink Control Channels In Mobile Communications
US10716100B2 (en) * 2016-12-13 2020-07-14 Sharp Laboratories Of America, Inc. Base stations, user equipments, and related communication methods
CN108271251A (zh) * 2016-12-30 2018-07-10 中兴通讯股份有限公司 一种上行控制的资源确定方法、装置、发送端和接收端

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102104972A (zh) * 2010-05-24 2011-06-22 电信科学技术研究院 Uci信息传输的配置方法和设备
CN107295677A (zh) * 2016-03-31 2017-10-24 中兴通讯股份有限公司 执行空闲信道评估的反馈方法及装置

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
HUAWEI ET AL.: "3GPP TSG RAN Meeting #80, RP-180889", VIEWS ON NR URLLC WORK IN REL-16, 14 June 2018 (2018-06-14), XP051455307 *
See also references of EP3843303A4

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP4171154A4 (en) * 2020-07-10 2023-12-20 Huawei Technologies Co., Ltd. METHOD AND DEVICE FOR COMMUNICATION, TERMINAL DEVICE, NETWORK DEVICE AND MEDIUM

Also Published As

Publication number Publication date
US20210204276A1 (en) 2021-07-01
US11968675B2 (en) 2024-04-23
CN110932820B (zh) 2022-01-14
CN110932820A (zh) 2020-03-27
EP3843303A4 (en) 2021-10-20
EP3843303A1 (en) 2021-06-30

Similar Documents

Publication Publication Date Title
WO2020048364A1 (zh) 发送和接收混合自动重传请求确认信息的方法、通信装置
US11330424B2 (en) Terminal, base station, and radio communication method
WO2020057404A1 (zh) 发送和接收上行控制信息的方法以及通信装置
US10973023B2 (en) Terminal and radio communication method
US11438898B2 (en) Beam indication method, apparatus and system
US20200221444A1 (en) Dynamic Management of Uplink Control Signaling Resources in Wireless Network
US11956794B2 (en) Data sending and receiving method and communication apparatus
US20210336726A1 (en) User terminal and radio communication method
WO2020098685A1 (zh) 接收数据的方法和通信装置
US20170055249A1 (en) Base station, transmission method, mobile station and retransmission control method
WO2020098661A1 (zh) 发送和接收数据的方法和通信装置
US11638269B2 (en) Channel state information report aggregation and uplink control information multiplexing for sidelink communications
US20180115394A1 (en) User terminal, radio base station and radio communication method
US20220078772A1 (en) Downlink signal transmission method and device
WO2020248101A1 (zh) 上报csi的方法和终端设备
WO2020135105A1 (zh) 上行传输的方法、上行传输的装置、以及终端设备
WO2020063767A1 (zh) 上行免动态授权传输的配置方法及通信装置
WO2021017765A1 (zh) 通信方法和通信装置
WO2020201118A1 (en) Configured uplink control information mapping
WO2019098937A1 (en) Harq requests and responses
EP3952560A1 (en) Communication method, communication device and system
WO2019016950A1 (ja) ユーザ端末及び無線通信方法
JPWO2017078032A1 (ja) ユーザ端末、無線基地局及び無線通信方法
WO2020156002A1 (zh) 通信方法及通信装置
WO2020098662A1 (zh) 发送和接收物理下行控制信道的方法以及通信装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 19862946

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2019862946

Country of ref document: EP

Effective date: 20210324