WO2019137245A1 - 上行控制信息传输方法及装置 - Google Patents

上行控制信息传输方法及装置 Download PDF

Info

Publication number
WO2019137245A1
WO2019137245A1 PCT/CN2018/124794 CN2018124794W WO2019137245A1 WO 2019137245 A1 WO2019137245 A1 WO 2019137245A1 CN 2018124794 W CN2018124794 W CN 2018124794W WO 2019137245 A1 WO2019137245 A1 WO 2019137245A1
Authority
WO
WIPO (PCT)
Prior art keywords
uci
dci
time domain
domain resource
symbol
Prior art date
Application number
PCT/CN2018/124794
Other languages
English (en)
French (fr)
Other versions
WO2019137245A8 (zh
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 EP18899556.7A priority Critical patent/EP3735071B1/en
Priority to CA3087302A priority patent/CA3087302A1/en
Priority to BR112020014204-2A priority patent/BR112020014204A2/pt
Publication of WO2019137245A1 publication Critical patent/WO2019137245A1/zh
Priority to US16/926,105 priority patent/US11140666B2/en
Publication of WO2019137245A8 publication Critical patent/WO2019137245A8/zh

Links

Images

Classifications

    • 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/0044—Arrangements for allocating sub-channels of the transmission path allocation of payload
    • 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/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/0028—Formatting
    • H04L1/0031—Multiple signaling transmission
    • 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/004—Arrangements for detecting or preventing errors in the information received by using forward error control
    • H04L1/0072—Error control for data other than payload data, e.g. control data
    • H04L1/0073—Special arrangements for feedback channel
    • 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
    • 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]
    • H04L1/1819—Hybrid protocols; Hybrid automatic repeat request [HARQ] with retransmission of additional or different redundancy
    • 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
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0042—Arrangements for allocating sub-channels of the transmission path intra-user or intra-terminal allocation
    • 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/0048—Allocation of pilot signals, i.e. of signals known to the receiver
    • H04L5/0051—Allocation of pilot signals, i.e. of signals known to the receiver of dedicated pilots, i.e. pilots destined for a single user or terminal
    • 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
    • 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/0058—Allocation criteria
    • H04L5/0064—Rate requirement of the data, e.g. scalable bandwidth, data priority
    • 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/0091—Signaling for the administration of the divided path
    • H04L5/0094—Indication of how sub-channels of the path are allocated
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H04W72/044—Wireless resource allocation based on the type of the allocated resource
    • H04W72/0446—Resources in time domain, e.g. slots or frames
    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/27—Transitions between radio resource control [RRC] states
    • 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/0001—Arrangements for dividing the transmission path
    • H04L5/0003—Two-dimensional division
    • H04L5/0005—Time-frequency
    • H04L5/0007—Time-frequency the frequencies being orthogonal, e.g. OFDM(A), DMT
    • 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/0001—Arrangements for dividing the transmission path
    • H04L5/0014—Three-dimensional division
    • H04L5/0016—Time-frequency-code

Definitions

  • the present application relates to the field of wireless communications technologies, and in particular, to an uplink control information transmission method and apparatus.
  • the fifth generation (5G) mobile communication system supports enhanced mobile broadband (eMBB) services, ultra reliable and low latency communications (URLLC) services, and massive machine-like communications ( Massive machine type communications, mMTC) business.
  • eMBB services include: ultra high definition video, augmented reality (AR), virtual reality (VR), etc.
  • the main features of these services are large amount of transmitted data and high transmission rate.
  • Typical URLLC services include wireless control in industrial manufacturing or production processes, motion control for driverless cars and drones, and tactile interaction applications such as remote repair and remote surgery.
  • the main features of these services are ultra-high reliability. Low latency, low data transfer and burstiness.
  • Typical mMTC services include: smart grid distribution automation, smart city, etc.
  • the main features are huge number of networked devices, small amount of transmitted data, and insensitive data transmission delay. These mMTC terminals need to meet low cost and very long standby. The demand for time.
  • the URLLC service requires extremely high latency.
  • the transmission delay is required to be within 0.5 milliseconds (millisecond, ms).
  • the transmission delay is required to be within 1 ms.
  • the smallest time scheduling unit is a transmission time interval (TTI) of 1 ms duration.
  • TTI transmission time interval
  • the data transmission of the wireless air interface can use a shorter time scheduling unit.
  • slot based scheduling and non-slot based scheduling may be supported, wherein one time slot may include 12 or 14 time domain symbols, where time The domain symbol may be an orthogonal frequency division multiplexing (OFDM) symbol, or may be a discrete Fourier transform spread OFDM (DFTS-OFDM) symbol.
  • OFDM orthogonal frequency division multiplexing
  • DFTS-OFDM discrete Fourier transform spread OFDM
  • the corresponding time length is 1 millisecond (millisecond, ms); for a time when the subcarrier spacing is 60 kHz
  • the gap length is shortened to 0.25ms.
  • the method of transmitting uplink control information (UCI) cannot guarantee the reliability of the URLLC service.
  • the present application provides an uplink control information transmission method, a related device, and a system, which can better ensure the high reliability of the URLLC service.
  • the present application provides an uplink control information transmission method, and an execution body of the method may be a network device or a chip or component for a network device.
  • the method includes transmitting a first DCI and receiving a first UCI, the first UCI being triggered by the first DCI. After the first time domain resource and the time domain resource of the uplink data channel partially or completely overlap, and the first condition is met, the first symbol carries the first UCI, and the uplink data channel is not carried, the first symbol is A time domain symbol in which the first time domain resource and the time domain resource of the uplink data channel overlap; the first time domain resource is used to transmit the first UCI.
  • the present application provides an uplink control information transmission method, and the execution body of the method may be a terminal device or a chip or component for the terminal device.
  • the method includes: receiving first downlink control information DCI, and transmitting first uplink control information UCI, where the first UCI is triggered by the first DCI; and partially or completely overlapping the time domain resource of the first time domain resource and the uplink data channel PUSCH And the first condition is satisfied, the first UCI is carried on the first symbol, and the PUSCH is not carried, and the first symbol is a time domain symbol in which the time domain resources of the first time domain resource and the PUSCH overlap; The domain resource is used to transmit the first UCI.
  • the first premise is that the resources for transmitting the first UCI and the resources for transmitting the PUSCH partially or completely overlap in the time domain.
  • the second premise is that resources for transmitting the first UCI and resources for transmitting the PUSCH partially or completely overlap in the time domain, and partially or completely overlap in the frequency domain.
  • the third premise is that the resource for transmitting the first UCI and the resource for transmitting the PUSCH are not overlapped in the frequency domain, but the terminal does not have the capability of transmitting multiple services simultaneously, such as power limitation or adopting an uplink single carrier. transfer method.
  • the basic premise of providing protection for the first UCI is that the first time domain resource and the time domain resource of the PUSCH overlap partially or completely, that is, the first UCI and the PUSCH multiplex the time domain resource.
  • the first premise indicates that, under the condition that the first time domain resource and the time domain resource of the PUSCH partially or completely overlap, if the first condition is met, the terminal may provide special protection for the first UCI.
  • the second premise indicates that, under the condition that the first UCI and the PUSCH are multiplexed with time-frequency resources, if the first condition is met, the terminal can provide special protection for the first UCI.
  • the third premise indicates that if the first UCI and the PUSCH only multiplex the time domain resources (the frequency domain resources are not multiplexed), and the terminal does not have the capability of transmitting the multi-service simultaneously, if the first UCI satisfies the first condition
  • the terminal can provide special protection for the first UCI.
  • symbols 7, 8, and 11 are used to transmit URLLC UCI
  • symbols 7-14 are used to transmit PUSCH.
  • the symbols overlapping in the symbols 7, 8, 11 and the symbols 7-14 are: symbols 7, 8, 11 and symbols 7, 8, 11 are the first symbols.
  • the frequency domain resource multiplexing of the first UCI and the PUSCH may include the following:
  • the frequency domain resources occupied by the first UCI and the PUSCH on the first symbol do not overlap at all, that is, the first UCI and the PUSCH each occupy completely different frequency domain resources on the first symbol.
  • the first UCI and the PUSCH partially overlap the frequency domain resources occupied by the first symbol, that is, the first UCI and the PUSCH have the same frequency domain resources in the frequency domain resources occupied by the first symbol. .
  • the frequency domain resources occupied by the first UCI and the PUSCH on the first symbol completely overlap, that is, the first UCI and the PUSCH occupy the same frequency domain resources on the first symbol.
  • the terminal may puncture all the RBs on the first symbol for the first UCI, that is, the first symbol is only used to transmit the first UCI and not transmit the PUSCH.
  • symbols 7, 8, and 11 are used to transmit URLLC UCI
  • symbols 7-14 are used to transmit PUSCH.
  • the symbols overlapping in the symbols 7, 8, 11 and the symbols 7-14 are: symbols 7, 8, 11 and symbols 7, 8, 11 are the first symbols.
  • the terminal can puncture all RBs on symbols 7, 8, 11. In this way, more resources can be allocated for the first UCI to ensure high reliability of the URLLC service.
  • the terminal may further set the transmit power of the PUSCH on the first symbol to be 0, that is, the transmit power on the first symbol is concentrated for transmitting the first UCI. This can greatly improve the transmission power of the first UCI and improve the reliability of the URLLC service.
  • the present application provides an uplink control information transmission method, and an execution body of the method may be a network device or a chip or component for a network device.
  • the method includes: transmitting a first DCI, and receiving a first UCI, where the first UCI is triggered by the first DCI; a condition in which the first time domain resource partially or completely overlaps with the second time domain resource, and the first condition is satisfied
  • the end time domain symbol carrying the first UCI is earlier than the start time domain symbol carrying the second UCI; the first time domain resource is used to transmit the first UCI, and the second time domain resource is used to transmit the second UCI.
  • the application provides an uplink control information transmission method
  • the execution body of the method may be a terminal device or a chip or component for the terminal device.
  • the method includes: receiving the first downlink control information DCI, and transmitting the first uplink control information UCI, where the first UCI is triggered by the first DCI; and the first time domain resource and the second time domain resource partially or completely overlap, and the method Under the condition that a condition is satisfied, the end time domain symbol carrying the first UCI is earlier than the start time domain symbol carrying the second UCI.
  • the first time domain resource is used to transmit the first UCI
  • the second time domain resource is used to transmit the second UCI.
  • the application provides an uplink control information transmission method
  • the execution body of the method may be a terminal device or a chip or component for the terminal device.
  • the method includes transmitting a first DCI and receiving a first UCI, the first UCI being triggered by the first DCI; under the condition that the first time domain resource and the second time domain resource partially or completely overlap, and the first condition is met
  • the first coding mode adopted by the first UCI is superior to the second coding mode adopted by the second UCI in terms of data transmission reliability; the first time domain resource is used for transmitting the first UCI, and the second time domain resource is used for transmitting the second coding mode.
  • the uplink control information transmission method described in the third aspect, the fourth aspect, the fifth aspect, and the sixth aspect can implement special protection for the URLLC UCI when the URLLC UCI and the eMBB UCI are multiplexed resources, and ensure the URLLC service. reliability.
  • the resources for transmitting the first UCI and the resources for transmitting the second UCI overlap partially or completely in the time domain.
  • the second premise is that resources for transmitting the first UCI and resources for transmitting the second UCI overlap partially or completely in the time domain, and partially or completely overlap in the frequency domain.
  • the third premise is that the resources for transmitting the first UCI and the resources for transmitting the second UCI overlap partially or completely in the time domain, and do not overlap in the frequency domain, but the terminal does not have the capability of transmitting multiple services simultaneously on the uplink. For example, power is limited or uplink single carrier transmission is adopted.
  • the basic premise of providing protection for the first UCI is that the first time domain resource and the second time domain resource overlap partially or completely, that is, the first UCI and the second UCI multiplex time domain resource.
  • the first premise indicates that, under the condition that the first UCI and the second UCI multiplex time domain resources, if the first UCI satisfies the first condition, the terminal may provide special protection for the first UCI.
  • the second premise indicates that, under the condition that the first UCI and the second UCI are multiplexed with time-frequency resources, if the first UCI satisfies the first condition, the terminal may provide special protection for the first UCI.
  • the third premise indicates that if the first UCI and the second UCI are only multiplexed with time domain resources (the frequency domain resources are not multiplexed), and the terminal does not have the capability of transmitting multiple services simultaneously, if the first UCI satisfies the first In one condition, the terminal can provide special protection for the first UCI.
  • the end time domain symbol carrying the first UCI is earlier than the start time domain symbol carrying the second UCI, that is, the second UCI may be delayed.
  • the first UCI with high reliability requirements is transmitted first, and then the second UCI is sent to ensure the reliability of the URLLC service.
  • the terminal may perform HARQ-ACK bits bundling on the second UCI that is delayed in transmission, so that the feedback delay of the second UCI can be reduced.
  • the terminal may determine whether to perform HARQ-ACK bits bundling on the delayed second UCI according to the symbol resource corresponding to the second UCI being delayed to be sent. If the symbol resource is tight, the terminal is insufficient to pass the HARQ-ACK bits multiplexing manner. Transmitting the second UCI may determine to perform HARQ-ACK bits bundling on the second UCI that is delayed.
  • the first UCI adopts the first coding method
  • the first coding mode adopted by the first UCI is superior to the second coding mode adopted by the second UCI in terms of data transmission reliability.
  • the first coding mode is different from the second coding mode, and the difference between the two may be, but is not limited to, the first coding mode may increase the number of bits after the first UCI coding, and/or the second coding mode reduces the second UCI code. The number of bits. specific:
  • the first encoding manner may include: performing redundancy encoding on the first UCI. That is, the terminal may first add redundancy to the source of the first UCI and then encode, or may first encode and then perform bit plus redundancy on the encoded first UCI. In this way, the number of bits after the first UCI encoding can be increased, so that the first UCI has higher error correction capability than the second UCI, and the high reliability of the URLLC service is ensured.
  • the second coding mode may include performing HARQ-ACK bit binding on the second UCI. This reduces the number of bits after the second UCI encoding.
  • the first UCI may be redundantly coded, and the HARQ-ACK bit bundling is performed on the second UCI, so that the transmission reliability of the first UCI can be improved, and the first UCI and the second UCI are jointly reduced.
  • the first condition may include, but is not limited to:
  • DCI format is DCI format for URLLC service
  • the DCI format for the URLLC service may be referred to as a compact DCI (compact DCI, also known as URLLC DCI) format.
  • compact DCI compact DCI, also known as URLLC DCI
  • the compact DCI format may be indicated by, but not limited to, at least one of the following: the payload size of the DCI is equal to the first value; or the payload size of the DCI is equal to the first value, and the DCI is in the DCI.
  • the value of the DCI format identifier is equal to the second value; or the payload size of the DCI is equal to the first value, and the search space of the DCI is the specific search space of the terminal device UE; or the payload of the DCI
  • the size of the DCI format identifier field of the first DCI is equal to the second value, and the search space of the DCI is the UE-specific search space; or the search space of the DCI is the first search space; or, DCI
  • the check bit length of the cyclic redundancy check CRC is equal to the third value; or, the check bit length of the DCI cyclic redundancy check CRC is equal to the third value; or, the CRC check for scrambling the DCI
  • the bit wireless network temporary identity RNTI is equal to the first RNTI; or the control resource set CORESET transmitting the DCI is the first CORESET.
  • the first value, the second value, the third value, the first search space, and the first CORESET may all be network devices through high layer signaling, such as radio resource control (RRC). Signaling, MAC CE signaling, configured.
  • the first value is the payload size of the compact DCI.
  • the second value is the value of the DCI format identifier field in the compact DCI.
  • the third value is the check bit length of the CRC of the compact DCI.
  • the first search space is a search space for detecting a compact DCI.
  • the first CORESET is the CORESET for transmitting the compact DCI.
  • the compact DCI format can be configured through high-level signaling, and the compact DCI format is different from the normal DCI format (such as the DCI format for eMBB services).
  • the compact DCI format may have at least one of the following attributes: the first value is smaller than the payload size of the normal DCI, and the second value is different from the value of the DCI format identifier field in the normal DCI.
  • the third value is greater than the check bit length of the CRC of the normal DCI.
  • the first search space is different from the search space for detecting normal DCI.
  • the first CORESET is different from the CORESET used to transmit the normal DCI.
  • the terminal can distinguish whether the received first DCI is a compact DCI according to the payload size. If the received payload size of the first DCI is equal to the first value, it can be determined that the DCI is a compact DCI, that is, the first condition is met. .
  • the terminal can combine the payload size and the Identifier for DCI format field to distinguish whether the received first DCI is a compact DCI, if the received first DCI payload size is equal to the first value and the Identifier for DCI format field is equal to The second value determines that the DCI is a compact DCI, that is, the first condition is satisfied.
  • the terminal may further combine the value of the Identifier for DCI format field to distinguish the compact DCI on the premise of the payload alignment of the received multiple DCIs.
  • the terminal can distinguish whether the received first DCI is a compact DCI according to the check bit length of the CRC. If the received check bit length of the CRC of the first DCI is equal to the third value, it can be determined that the DCI is Compact DCI, that is, the first condition is met.
  • the terminal can distinguish whether the received first DCI is a compact DCI according to the resource location of the first DCI, and if the resource location of the first DCI is detected as the first search space, it can be determined that the first DCI is a compact DCI. , that is, the first condition is met.
  • the terminal can distinguish whether the received first DCI is a compact DCI according to the resource location occupied by the first DCI. If the resource location occupied by the first DCI is the first CORESET, it can be determined that the first DCI is a compact DCI, that is, the first DCI is satisfied. First condition.
  • the radio network temporary identifier (RNTI) used to scramble the CRC check bits of the DCI is equal to the first RNTI
  • the first RNTI may be configured by the network device by using high layer signaling, such as RRC signaling and MAC CE signaling.
  • the first RNTI is used to scramble the CRC check bits of the compact DCI. That is to say, the RNTI for scrambling the CRC check bits of the compact DCI can be configured by higher layer signaling. In this way, the terminal can distinguish whether the received first DCI is a compact DCI according to the RNTI of the CRC check bit of the scrambled DCI.
  • the search space of DCI is the first search space.
  • the first search space may be configured by the network device by using high layer signaling, such as RRC signaling and MAC CE signaling.
  • the DCI detected on the first search space is the compact DCI. That is to say, the attribute of the search space (whether it is the search space of the URLLC) can be configured through higher layer signaling. In this way, the terminal can distinguish whether the DCI is a compact DCI according to the attribute of the search space detecting the DCI.
  • CORESET DCI's control resource set
  • the first CORESET may be configured by the network device by using high layer signaling, such as RRC signaling and MAC CE signaling.
  • the first CORESET is used to send the compact DCI. That is to say, the attribute of CORESET (whether it is CORESET of URLLC) can be configured through higher layer signaling. In this way, the terminal can distinguish whether the DCI is a compact DCI according to the attribute of the CORESET receiving the DCI.
  • the terminal can also determine whether the DCI satisfies the first condition by the following manner.
  • the terminal may determine, by the step of verifying, whether the DCI is a compact DCI.
  • the terminal can determine that the DCI is a compact DCI, that is, the DCI satisfies the first condition.
  • the terminal may determine whether there is a field in the DCI for reducing the probability of an error probability. If the field is present, it may be determined that the DCI is a compact DCI, that is, the DCI satisfies the first condition.
  • the terminal can determine whether the DCI is a compact DCI according to an encoding manner used by the DCI.
  • the coding mode adopted by the DCI is a specific coding mode
  • the terminal may determine that the DCI is a compact DCI, that is, the DCI satisfies the first condition.
  • the specific coding mode is one of low-density parity check (LDPC) or polar coding or Reed-Muller coding or dual Reed-Muller coding.
  • the foregoing implementation manner of determining whether the DCI satisfies the first condition is a manner of implicitly determining whether the corresponding UCI needs protection.
  • an explicit manner can also be used to determine whether UCI corresponding to the DCI requires protection.
  • the specific solution may be as follows: The DCI may carry a 1-bit field for distinguishing whether the UCI corresponding to the DCI needs to be protected.
  • the present application provides a communication device, which may include a plurality of functional modules for respectively performing the methods provided by the first aspect, the third aspect, the fifth aspect, or a possible implementation of the aspects.
  • the method provided by any of the modes.
  • the present application provides a communication device, which may include a plurality of functional modules for respectively performing the methods provided by the second aspect, the fourth aspect, the sixth aspect, or a possible implementation of the aspects.
  • the method provided by any of the modes.
  • the present application provides a communication apparatus for performing the uplink control information transmission method described in the first aspect.
  • the communication device can include a memory and a processor, transceiver coupled to the memory, wherein the transceiver is for communicating with other communication devices, such as communication devices.
  • the memory is used to store the implementation code of the uplink control information transmission method described in the first aspect, the third aspect, and the fifth aspect, where the processor is configured to execute the program code stored in the memory, that is, the first aspect, the third aspect, and the fifth aspect are performed.
  • the application provides a communication apparatus for performing the uplink control information transmission method described in the second aspect.
  • the communication device can include a memory and a processor, transceiver coupled to the memory, wherein the transceiver is for communicating with other communication devices, such as communication devices.
  • the memory is used to store the implementation code of the signal transmission described in the second aspect, the fourth aspect, and the sixth aspect
  • the processor is configured to execute the program code stored in the memory, that is, the second aspect, the fourth aspect, and the sixth aspect are provided. A method, or a method provided by any of the possible embodiments of these aspects.
  • a communication system comprising: a terminal and a network device, wherein: the network device can be the communication device described in the seventh aspect or the ninth aspect.
  • the terminal may be the communication device described in the eighth aspect or the tenth aspect.
  • a computer readable storage medium is provided, the instructions being stored on a readable storage medium, when executed on a computer, causing the computer to perform the uplink described in the first aspect, the third aspect, and the fifth aspect A method of controlling an information transmission method, or any of the possible embodiments of these aspects.
  • a thirteenth aspect there is provided another computer readable storage medium having instructions stored on a readable storage medium, when executed on a computer, causing the computer to perform the second aspect, the fourth aspect, and the sixth aspect described above An uplink control information transmission method, or a method provided by any of the possible implementations of these aspects.
  • a computer program product comprising instructions for causing a computer to execute the uplink control information transmission method described in the first aspect, the third aspect, and the fifth aspect, or the aspects, when the computer is running on the computer A method provided by any of the possible embodiments.
  • a fifteenth aspect there is provided another computer program product comprising instructions for causing a computer to perform the uplink control information transmission method described in the second aspect, the fourth aspect, the sixth aspect, or the like when operating on a computer A method provided by any of the possible embodiments.
  • FIG. 1 is a schematic structural diagram of a wireless communication system according to the present application.
  • FIG. 2 is a schematic diagram of multiplexing a transmission URLLC UCI and an eMBB PUCCH by using an existing UCI feedback manner
  • FIG. 3 is a schematic diagram of multiplexing a transmission URLLC UCI and an eMBBPUSCH by using an existing UCI feedback manner
  • FIG. 4 is a schematic diagram of a hardware architecture of a terminal provided by an embodiment of the present application.
  • FIG. 5 is a schematic diagram of a hardware architecture of a base station according to an embodiment of the present application.
  • FIG. 6 is a schematic diagram of a control resource set involved in the present application.
  • FIG. 7 is an exemplary schematic diagram of an uplink control information transmission method provided by the present application.
  • 10 is an exemplary schematic diagram of stopping transmission of a remaining PUSCH after a URLLC UCI
  • 11A is an exemplary schematic diagram of resource locations of an eMBB UCI relative to a PUSCH DMRS;
  • 11B is an exemplary schematic diagram of resource locations of a URLLC UCI relative to a PUSCH DMRS in the present application
  • FIG. 12 is an exemplary schematic diagram of another uplink control information transmission method provided by the present application.
  • FIG. 13A is an exemplary schematic diagram of a first UCI and a second UCI completely overlapping on a time domain resource
  • 13B is an exemplary schematic diagram of a partial overlap of a first UCI and a second UCI on a time domain resource
  • 14A is an exemplary schematic diagram of a case of a second UCI delayed transmission
  • 14B is an exemplary schematic diagram of another case of delayed transmission of a second UCI
  • FIG. 15A is an exemplary schematic diagram of coding modes using different degrees of redundancy for the first UCI and the second UCI;
  • 15B is an exemplary diagram of performing HARQ-ACK bits bundling on a second UCI in the example of FIG. 15A;
  • 16A is an exemplary schematic diagram of one manner of employing different code distances for a first UCI and a second UCI;
  • 16B is an exemplary schematic diagram of another manner of employing different code distances for the first UCI and the second UCI;
  • 17 is a schematic diagram of the number of resources of the first UCI indicated by a beta offset corresponding to the URLLC;
  • 18 is a schematic diagram of power on a PUSCH for increasing transmit power of a URLLC UCI
  • 19 is a functional block diagram of a wireless communication system, a terminal, and a network device provided by the present application.
  • FIG. 1 shows a wireless communication system to which the present application relates.
  • the wireless communication system is not limited to the LTE system, and may be a fifth generation 5G mobile communication system, a new air interface (NR) system, a future mobile communication system, or the like.
  • wireless communication system 100 can include one or more network devices 101, one or more terminals 103, and a core network 115. among them:
  • the network device 101 can be a base station that can be used to communicate with one or more terminals, and can also be used to communicate with one or more base stations having partial terminal functions (such as communication between a macro base station and a micro base station).
  • the base station may be an evolved base station (eNB) in an LTE system, and a base station in a 5G system, a new air interface (NR) system.
  • the base station may also be an Access Point (AP), a TransNode (Trans TRP), a Central Unit (CU), or other network entity, and may include some or all of the functions of the above network entities. .
  • AP Access Point
  • Trans TRP Trans Node
  • CU Central Unit
  • the embodiments of the present application do not limit the specific technologies and specific device modes adopted by the network device.
  • Terminals 103 may be distributed throughout wireless communication system 100, either stationary or mobile.
  • the terminal 103 may also be referred to as a user equipment (UE), a mobile station (MS), a mobile terminal (MT), or the like.
  • the terminal 103 can be a mobile phone, a tablet, a computer with wireless transceiver function, a virtual reality (VR) terminal, an augmented reality (AR) terminal, and an industrial control.
  • Wireless terminal wireless terminal in self driving, wireless terminal in remote medical surgery, wireless terminal in smart grid, wireless terminal in transportation safety, A wireless terminal in a smart city, a wireless terminal in a smart home, and the like.
  • network device 101 can be used to communicate with terminal 103 over wireless interface 105 under the control of a network device controller (not shown).
  • the network device controller may be part of the core network 115 or may be integrated into the network device 101.
  • the network device 101 can be configured to transmit control information or user data to the core network 115 through a blackhaul interface 113 (such as an S1 interface).
  • the network device 101 and the network device 101 can also communicate with each other directly or indirectly through a blackhaul interface 111 (such as an X2 interface).
  • the network device 101 and the terminal 103 can support simultaneous transmission of multiple services, such as 5G and future new air interface (NR) supported eMBB, URLLC and eMTC services.
  • NR new air interface
  • eMBB enhanced mobile broadband
  • URLLC enhanced mobile broadband
  • eMTC enhanced mobile broadband
  • the UCI may include, but is not limited to, a scheduling request (SR), a HARQ ACK/NACK corresponding to a downlink data packet in the PDSCH, and channel state information (CSI).
  • the CSI may include a downlink channel quality indicator (CQI), a rank indication (RI) and a precoding matrix indicator (PMI) related to the MIMO feedback.
  • the CSI may also include periodic CSI and aperiodic CSI.
  • the URLLC HARQ ACK/NACK is triggered by the DCI of the scheduling URLLC PDSCH
  • the URLLC aperiodic CSI is triggered by the DCI of the scheduling URLLC PUSCH
  • the eMBB HARQ ACK/NACK is triggered by the DCI scheduling the eMBB PDSCH
  • the aperiodic eMBB CSI is triggered by the DCI scheduling the eMBB PUSCH.
  • the UCI can be transmitted in the PUSCH or in the PUCCH.
  • the current UCI feedback method does not specifically consider the reliability requirements of the URLLC service, and does not guarantee the reliability of the URLLC service.
  • the existing UCI feedback methods are used to analyze the problems of the URLLC UCI for two different scenarios.
  • Scenario 1 Simultaneous transmission of URLLC UCI and eMBB UCI
  • the terminal In a time division duplexing (TDD) scenario, the terminal needs to feed back ACK/NACK in the same uplink subframe for the downlink data received by the terminal in multiple downlink subframes, that is, the terminal needs to be in the same uplink subframe. Multiple ACK/NACK are fed back. It is assumed that there are four downlink subframes in which ACK/NACK needs to be fed back in one uplink subframe, and the four downlink subframes respectively schedule URLLC data and eMBB data, as shown in FIG. 2 .
  • HARQ-ACK bits multiplexing is a direct feedback of 4 bits of "1101".
  • the existing HARQ-ACK bits multiplexing method does not have special protection for the URLLC ACK/NACK design to ensure the high reliability of the URLLC UCI, and the URLLC ACK/NACK is also affected by the eMBB ACK/NACK, the URLLC UCI Reliability is not guaranteed.
  • the present application designs a new feedback rule for the scenarios in which the above eMBBACK/NACK and URLLCACK/NACK need to be simultaneously fed back.
  • the subsequent embodiments please refer to the subsequent embodiments, which will not be described here.
  • Scenario 2 Simultaneous transmission of URLLC UCI and eMBB PUSCH
  • the current technical solution is to indicate the number of resource elements (REs) occupied by the UCI through the beta offset field in the DCI for transmitting the uplink grant (UL grant).
  • the value of beta offset is related to the code rate, which can be used to indicate the amount of resources occupied by UCI.
  • the DCI configures a betaoffset value for the ACK/NACK of the PDSCH before the UL grant is transmitted.
  • the URLLC service is usually bursty.
  • the number of REs occupied by the URLLC UCI is not indicated in the DCI that sends the UL grant.
  • the URLLC PDSCH burst appears after the UL grant.
  • the beta offset value ie beta offset1
  • the beta offset1 indicates that the number of resources occupied by the eMBB UCI is 4 REs.
  • the beta offset value is not configured for the UCI of the URLLC PDSCH (ie, the URLLC UCI) in the DCI that transmits the UL grant.
  • the number of resources occupied by the URLLC UCI of the URLLC PDSCH that appears after the UL grant can only follow the number of resources indicated by the beta offset1 configured for the eMBB UCI (ie, 4 REs), and cannot be specifically assigned to the URLLC UCI. Multi-resources, the reliability of URLLC UCI is not guaranteed.
  • the protection mode may include, but is not limited to, allocating more resources (such as time domain resources, frequency domain resources, code domain resources, power domain resources) to the URLLCUCI, using a more reliable coding method for the URLLCUCI, and the like.
  • the protection method may also include: how small and cooperative to transmit the URLLC UCI. For example, in order to improve the reliability of the cell edge users, a multi-cell cooperative transmission of the URLLC UCI is adopted. That is to say, the URLLC UCI is a network device (such as a base station) to be sent to multiple cells, so that the URLLC UCI naturally has higher reliability.
  • the transmission method for the special protection of the URLLC UCI provided by the present application, please refer to the following embodiments for details, which will not be described here.
  • the terminal 200 may include: one or more terminal processors 201, a memory 202, a receiver 205, a transmitter 206, a coupler 207, an antenna 208, a user interface 202, and input and output modules (including audio input).
  • bus 204 or other means FIG. 4 is exemplified by a bus connection. among them:
  • Transmitter 206 can be used to perform transmission processing, such as signal modulation, on signals output by terminal processor 201.
  • Receiver 205 can be used to perform reception processing, such as signal demodulation, on the mobile communication signals received by antenna 208.
  • transmitter 206 and receiver 205 can be viewed as a wireless modem.
  • the number of the transmitter 206 and the receiver 205 may each be one or more.
  • the antenna 208 can be used to convert electromagnetic energy in a transmission line into electromagnetic waves in free space, or to convert electromagnetic waves in free space into electromagnetic energy in a transmission line.
  • the coupler 207 is configured to divide the mobile communication signal received by the antenna 208 into multiple channels and distribute it to a plurality of receivers 205.
  • the terminal 200 may also include other communication components such as a GPS module, a Bluetooth module, a Wireless Fidelity (Wi-Fi) module, and the like. Not limited to the above-described wireless communication signals, the terminal 200 can also support other wireless communication signals such as satellite signals, short-wave signals, and the like. Not limited to wireless communication, the terminal 200 may also be configured with a wired network interface (such as a LAN interface) to support wired communication.
  • a wired network interface such as a LAN interface
  • the input and output module can be used to implement the interaction between the terminal 200 and the user/external environment, and can include the audio input and output module 210, the key input module 211, the display 212, and the like. Specifically, the input and output module may further include: a camera, a touch screen, a sensor, and the like. The input and output modules communicate with the terminal processor 201 through the user interface 209.
  • the memory 202 may be used to store an implementation program of the uplink control information transmission method provided by one or more embodiments of the present application on the terminal 200 side.
  • the uplink control information transmission method provided by one or more embodiments of the present application refer to the subsequent embodiments.
  • Terminal processor 201 can be used to read and execute computer readable instructions. Specifically, the terminal processor 201 can be used to invoke a program stored in the memory 212, such as an implementation program of the uplink control information transmission method provided by one or more embodiments of the present application on the terminal 200 side, and execute the instructions included in the program. .
  • the terminal 200 can be the terminal 103 in the wireless communication system 100 shown in FIG. 3, and can be implemented as a mobile device, a mobile station, a mobile unit, a wireless unit, a remote unit, and a user agent. , mobile client and more.
  • the terminal 200 shown in FIG. 4 is only one implementation of the embodiment of the present application. In an actual application, the terminal 200 may further include more or less components, which are not limited herein.
  • network device 300 can include one or more network device processors 301, memory 302, transmitter 305, receiver 306, coupler 307, and antenna 308. These components can be connected via bus 304 or other types, and FIG. 5 is exemplified by a bus connection. among them:
  • Transmitter 305 can be used to perform transmission processing, such as signal modulation, on signals output by network device processor 301.
  • Receiver 306 can be used to perform reception processing on the mobile communication signals received by antenna 308. For example, signal demodulation.
  • transmitter 305 and receiver 306 can be viewed as a wireless modem. In the network device 300, the number of the transmitter 305 and the receiver 306 may each be one or more.
  • the antenna 308 can be used to convert electromagnetic energy in a transmission line into electromagnetic waves in free space, or to convert electromagnetic waves in free space into electromagnetic energy in a transmission line.
  • Coupler 307 can be used to divide the mobile pass signal into multiple channels and distribute it to multiple receivers 306.
  • Memory 302 is coupled to network device processor 301 for storing various software programs and/or sets of instructions.
  • memory 302 may include high speed random access memory, and may also include non-volatile memory, such as one or more magnetic disk storage devices, flash memory devices, or other non-volatile solid state storage devices.
  • the memory 302 can store an operating system (hereinafter referred to as a system) such as an embedded operating system such as uCOS, VxWorks, or RTLinux.
  • the memory 302 can also store a network communication program that can be used to communicate with one or more additional devices, one or more terminal devices, one or more network devices.
  • the network device processor 301 can be used to perform wireless channel management, implement call and communication link establishment and teardown, and provide cell handover control and the like for users in the control area.
  • the network device processor 301 may include: an Administration Module/Communication Module (AM/CM) (a center for voice exchange and information exchange), and a Basic Module (BM) (for Complete call processing, signaling processing, radio resource management, radio link management and circuit maintenance functions), code conversion and sub-multiplexer (TCSM) (for multiplexing demultiplexing and code conversion functions) )and many more.
  • AM/CM Administration Module/Communication Module
  • BM Basic Module
  • TCSM code conversion and sub-multiplexer
  • the network device processor 301 can be used to read and execute computer readable instructions. Specifically, the network device processor 301 can be used to invoke a program stored in the memory 302. For example, the uplink control information transmission method provided by one or more embodiments of the present application is implemented on the network device 300 side, and the program is executed. Instructions.
  • the network device 300 can be the base station 101 in the wireless communication system 100 shown in FIG. 3, and can be implemented as a base transceiver station, a wireless transceiver, a basic service set (BSS), and an extended service set (ESS). NodeB, eNodeB, access point or TRP, etc.
  • the network device 300 shown in FIG. 5 is only one implementation of the embodiment of the present application. In actual applications, the network device 300 may further include more or fewer components, which are not limited herein.
  • the embodiment of the present application provides an uplink control information transmission method. The details are described below.
  • the main design idea of the present application may include: the terminal may determine, according to the received first DCI, whether the corresponding UCI (ie, the UCI triggered by the DCI) needs protection, and if protection is required, design a special transmission strategy for the UCI. Provide protection for the UCI to ensure the reliability of the URLLC service.
  • the special transmission strategy may be superior to the common UCI transmission strategy in at least one of the following: a transmission resource, an encoding mode, a cascading order of a bit stream, a sending order, and the like.
  • the better in terms of transmission resources may refer to more resources allocated for the URLLC UCI.
  • the better coding method can mean that the coding method adopted by the URLLC UCI has higher error correction capability than the coding method adopted by the ordinary UCI.
  • the cascading order of the bit stream may mean that the bit stream of the URLLC UCI is concatenated prior to the bit stream of the normal UCI.
  • Better in terms of transmission order may mean that the URLLC UCI is preferentially transmitted to the normal UCI.
  • the subsequent content will describe in detail the specific implementation of the special transmission strategy, which will not be described here.
  • the normal UCI may include, but is not limited to, an eMBB UCI.
  • the reliability requirement of the PDSCH responded by the normal UCI is lower than the reliability requirement of the PDSCH responded by the URLLC UCI.
  • the URLLC UCI may be referred to as a first UCI, and the ordinary UCI may be referred to as a second UCI.
  • the first UCI may also include a UCI of a new service type defined in a future communication standard, not limited to a URLLC service. This new service type is similar to the URLLC service type and has a high demand for reliability.
  • scheme 1 discusses how to provide protection for URLLC UCI in the scenario of URLLC UCI and PUSCH multiplexing resources.
  • Scheme 2-4 discusses how to provide protection for URLLC UCI in the context of URLLC UCI and eMBB UCI multiplex resources.
  • Solution 1 The terminal determines, according to the received first DCI, whether the DCI satisfies the first condition, and if yes, transmits the first UCI and PUSCH multiplexed symbols on the premise of the first UCI and the PUSCH multiplexed resources.
  • Solution 2 The terminal determines, according to the received first DCI, whether the DCI satisfies the first condition, and if yes, sends the first UCI first, and then sends the second UCI on the premise of the first UCI and the second UCI multiplexing resource. . That is, the end time domain symbol carrying the first UCI is earlier than the start time domain symbol carrying the second UCI. That is to say, the URLLC UCI that ensures high reliability requirements is sent first, and then the eMBB UCI is sent to ensure low latency of the URLLC service.
  • Solution 3 The terminal determines, according to the received first DCI, whether the DCI satisfies the first condition. If yes, the first UCI adopts the first coding mode on the premise of the first UCI and the second UCI multiplexing resource.
  • the coding mode is superior to the second coding mode adopted by the second UCI in terms of data transmission reliability. That is to say, the URLLC UCI adopts a better coding mode to ensure high reliability of the URLLC service.
  • Each of the above solutions involves how to determine whether DCI meets the first condition. If it is determined that the DCI satisfies the first condition, it may be determined that the UCI corresponding to the DCI requires protection.
  • the first condition may include, but is not limited to:
  • DCI format is DCI format for URLLC service
  • the DCI format for the URLLC service may be referred to as a compact DCI (compact DCI, also known as URLLC DCI) format.
  • compact DCI compact DCI, also known as URLLC DCI
  • the compact DCI format may be indicated by, but not limited to, at least one of the following: the payload size of the DCI is equal to the first value; or the payload size of the DCI is equal to the first value, and the DCI is in the DCI.
  • the value of the DCI format identifier is equal to the second value; or the payload size of the DCI is equal to the first value, and the search space of the DCI is the specific search space of the terminal device UE; or the payload of the DCI
  • the size of the DCI format identifier field of the first DCI is equal to the second value, and the search space of the DCI is the UE-specific search space; or the search space of the DCI is the first search space; or, DCI
  • the check bit length of the cyclic redundancy check CRC is equal to the third value; or, the check bit length of the DCI cyclic redundancy check CRC is equal to the third value; or, the CRC check for scrambling the DCI
  • the bit wireless network temporary identity RNTI is equal to the first RNTI; or the control resource set CORESET transmitting the DCI is the first CORESET.
  • the first value, the second value, the third value, the first search space, and the first CORESET may all be network devices through high layer signaling, such as radio resource control (RRC). Signaling, MAC CE signaling, configured.
  • the first value is the payload size of the compact DCI.
  • the second value is the value of the DCI format identifier field in the compact DCI.
  • the third value is the check bit length of the CRC of the compact DCI.
  • the first search space is a search space for detecting a compact DCI.
  • the first CORESET is the CORESET for transmitting the compact DCI.
  • the compact DCI format can be configured through high-level signaling, and the compact DCI format is different from the normal DCI format (such as the DCI format for eMBB services).
  • the compact DCI format may have at least one of the following attributes: the first value is smaller than the payload size of the normal DCI, and the second value is different from the value of the DCI format identifier field in the normal DCI.
  • the third value is greater than the check bit length of the CRC of the normal DCI.
  • the first search space is different from the search space for detecting normal DCI.
  • the first CORESET is different from the CORESET used to transmit the normal DCI.
  • the terminal can distinguish whether the received first DCI is a compact DCI according to the payload size. If the received payload size of the first DCI is equal to the first value, it can be determined that the DCI is a compact DCI, that is, the first condition is met. .
  • the terminal can combine the payload size and the Identifier for DCI format field to distinguish whether the received first DCI is a compact DCI, if the received first DCI payload size is equal to the first value and the Identifier for DCI format field is equal to The second value determines that the DCI is a compact DCI, that is, the first condition is satisfied.
  • the terminal may further combine the value of the Identifier for DCI format field to distinguish the compact DCI on the premise of the payload alignment of the received multiple DCIs.
  • the terminal can distinguish whether the received first DCI is a compact DCI according to the check bit length of the CRC. If the received check bit length of the CRC of the first DCI is equal to the third value, it can be determined that the DCI is Compact DCI, that is, the first condition is met.
  • the terminal can distinguish whether the received first DCI is a compact DCI according to the resource location of the first DCI, and if the resource location of the first DCI is detected as the first search space, it can be determined that the first DCI is a compact DCI. , that is, the first condition is met.
  • the terminal can distinguish whether the received first DCI is a compact DCI according to the resource location occupied by the first DCI. If the resource location occupied by the first DCI is the first CORESET, it can be determined that the first DCI is a compact DCI, that is, the first DCI is satisfied. First condition.
  • the radio network temporary identifier (RNTI) used to scramble the CRC check bits of the DCI is equal to the first RNTI
  • the first RNTI may be configured by the network device by using high layer signaling, such as RRC signaling and MAC CE signaling.
  • the first RNTI is used to scramble the CRC check bits of the compact DCI. That is to say, the RNTI for scrambling the CRC check bits of the compact DCI can be configured by higher layer signaling. In this way, the terminal can distinguish whether the received first DCI is a compact DCI according to the RNTI of the CRC check bit of the scrambled DCI.
  • the search space of DCI is the first search space.
  • the first search space may be configured by the network device by using high layer signaling, such as RRC signaling and MAC CE signaling.
  • the DCI detected on the first search space is the compact DCI. That is to say, the attribute of the search space (whether it is the search space of the URLLC) can be configured through higher layer signaling. In this way, the terminal can distinguish whether the DCI is a compact DCI according to the attribute of the search space detecting the DCI.
  • CORESET DCI's control resource set
  • the first CORESET may be configured by the network device by using high layer signaling, such as RRC signaling and MAC CE signaling.
  • the first CORESET is used to send the compact DCI. That is to say, the attribute of CORESET (whether it is CORESET of URLLC) can be configured through higher layer signaling. In this way, the terminal can distinguish whether the DCI is a compact DCI according to the attribute of the CORESET receiving the DCI.
  • a CORESET is a time-frequency resource within the control region.
  • the first four time domain symbols of the 14 time domain symbols are used as the control region, but only a part of the resources in the first four time domain symbols may be defined as resources corresponding to a certain CORESET.
  • a CORESET corresponds to a group of users (such as UE1, UE2, UE3, etc.).
  • the physical downlink control channel (PDCCH) of this group of users is sent on this CORESET.
  • Each user has a search space on a CORESET whose resources are less than or equal to the resources of the CORESET.
  • a user can correspond to multiple CORESETs.
  • the Numerology associated with these CORESETs can be the same or different.
  • the numerology here can include subcarrier spacing and cyclic prefix (CP) length.
  • the terminal can also determine whether the DCI satisfies the first condition by the following manner.
  • the terminal may determine, by the step of verifying, whether the DCI is a compact DCI.
  • the terminal can determine that the DCI is a compact DCI, that is, the DCI satisfies the first condition.
  • the terminal may determine whether there is a field in the DCI for reducing the probability of an error probability. If the field is present, it may be determined that the DCI is a compact DCI, that is, the DCI satisfies the first condition.
  • the terminal can determine whether the DCI is a compact DCI according to an encoding manner used by the DCI.
  • the coding mode adopted by the DCI is a specific coding mode
  • the terminal may determine that the DCI is a compact DCI, that is, the DCI satisfies the first condition.
  • the specific coding mode is one of low-density parity check (LDPC) or polar coding or Reed-Muller coding or dual Reed-Muller coding.
  • the foregoing implementation manner of determining whether the DCI satisfies the first condition is a manner of implicitly determining whether the corresponding UCI needs protection.
  • an explicit manner can also be used to determine whether UCI corresponding to the DCI requires protection.
  • the specific solution may be as follows: The DCI may carry a 1-bit field for distinguishing whether the UCI corresponding to the DCI needs to be protected.
  • mapping relationship may be predefined by the protocol or semi-statically configured by RRC signaling.
  • Whether the DCI contains a 1-bit field may be predefined by a protocol or may be configured through RRC signaling.
  • the mapping relationship exemplarily shown in Table 1 may be predefined by a protocol or may be configured through RRC signaling.
  • the first DCI may be a compact DCI/URLLC DCI (ie, a DCI that satisfies the first condition), or a normal DCI (such as an eMBB DCI).
  • a compact DCI/URLLC DCI ie, a DCI that satisfies the first condition
  • a normal DCI such as an eMBB DCI
  • the reliability requirement of the first DCI scheduled PDSCH (such as URLLC PDSCH) that satisfies the first condition is higher than the reliability requirement of the normal DCI scheduled PDSCH (such as eMBB PDSCH).
  • This application provides special protection for the UCI corresponding to the compact DCI/URLLC DCI (ie, the UCI triggered by the DCI tone), which ensures high reliability of the URLLC service.
  • the resource concepts involved in the present application such as a symbol, a resource element (RE), a resource block (RB), a CORESET, a search space, etc.
  • a channel concept designed by the present application such as PDSCH, PDCCH, etc.
  • the terminal may determine whether the received first DCI satisfies the first condition, and if the first condition is met, the terminal may be multiplexed in the first UCI and the PUSCH.
  • the first UCI is sent on the symbol without transmitting the PUSCH.
  • FIG. 7 is a schematic flowchart diagram of an uplink control information transmission method provided by the present application. The following expands as follows:
  • the network device sends the first DCI to the terminal.
  • the terminal receives the first DCI sent by the network device.
  • the terminal sends a first UCI to the network device, where the first UCI is triggered by the first DCI.
  • the first UCI is carried on the first symbol without carrying the PUSCH, whether the first UCI and the PUSCH are multiplexed with the time domain resource and the first condition is met.
  • the first symbol is a time domain symbol multiplexed by the first UCI and PUSCH.
  • a time domain resource for transmitting a first UCI may be referred to as a first time domain resource.
  • the first symbol may specifically be a time domain symbol in which the first time domain resource and the time domain resource of the PUSCH overlap. That is to say, when the first time domain resource overlaps with the time domain resource of the PUSCH partially or completely, and the first condition is satisfied, the first UCI is carried on the first symbol, and the PUSCH is not carried.
  • the terminal may provide special protection for the first UCI. The details are described below.
  • the first premise is that the resources for transmitting the first UCI and the resources for transmitting the PUSCH partially or completely overlap in the time domain.
  • the second premise is that resources for transmitting the first UCI and resources for transmitting the PUSCH partially or completely overlap in the time domain, and partially or completely overlap in the frequency domain.
  • the third premise is that the resource for transmitting the first UCI and the resource for transmitting the PUSCH are not overlapped in the frequency domain, but the terminal does not have the capability of transmitting multiple services simultaneously, such as power limitation or adopting an uplink single carrier. transfer method.
  • the basic premise of providing protection for the first UCI is that the first time domain resource and the time domain resource of the PUSCH overlap partially or completely, that is, the first UCI and the PUSCH multiplex the time domain resource.
  • the first premise indicates that, under the condition that the first time domain resource and the time domain resource of the PUSCH partially or completely overlap, if the first condition is met, the terminal may provide special protection for the first UCI, that is, execute S103.
  • the second premise indicates that, under the condition that the first UCI and the PUSCH are multiplexed with time-frequency resources, if the first condition is met, the terminal may provide special protection for the first UCI, that is, execute S103.
  • the third premise indicates that if the first UCI and the PUSCH only multiplex the time domain resources (the frequency domain resources are not multiplexed), and the terminal does not have the capability of transmitting the multi-service simultaneously, if the first UCI satisfies the first condition
  • the terminal can provide special protection for the first UCI, that is, execute S103.
  • symbols 7, 8, and 11 are used to transmit a URLLC UCI
  • symbols 7-14 are used to transmit a PUSCH.
  • the symbols overlapping in the symbols 7, 8, 11 and the symbols 7-14 are: symbols 7, 8, 11 and symbols 7, 8, 11 are the first symbols.
  • the frequency domain resource multiplexing of the first UCI and the PUSCH may include the following:
  • the frequency domain resources occupied by the first UCI and the PUSCH on the first symbol do not overlap at all, that is, the first UCI and the PUSCH each occupy completely different frequency domain resources on the first symbol.
  • the first symbol is symbol 7
  • the frequency domain resources occupied by the first UCI and the PUSCH do not overlap at all.
  • the first UCI and the PUSCH partially overlap the frequency domain resources occupied by the first symbol, that is, the first UCI and the PUSCH have the same frequency domain resources in the frequency domain resources occupied by the first symbol.
  • the first symbol is symbol 8
  • the frequency domain resources occupied by the first UCI and the PUSCH partially overlap.
  • the frequency domain resources occupied by the first UCI and the PUSCH on the first symbol are completely overlapped, that is, the first UCI and the PUSCH occupy the same frequency domain resources on the first symbol.
  • the first symbol is the symbol 11
  • the frequency domain resources occupied by the first UCI and the PUSCH completely overlap.
  • the terminal may puncture all the RBs on the first symbol for the first UCI, that is, the first symbol is only used to transmit the first UCI and not transmit the PUSCH.
  • symbols 7, 8, and 11 are used to transmit a URLLC UCI
  • symbols 7-14 are used to transmit a PUSCH.
  • the symbols overlapping in the symbols 7, 8, 11 and the symbols 7-14 are: symbols 7, 8, 11 and symbols 7, 8, 11 are the first symbols.
  • the terminal can puncture all RBs on symbols 7, 8, 11. In this way, more resources can be allocated for the first UCI to ensure high reliability of the URLLC service.
  • the terminal may further set the transmit power of the PUSCH on the first symbol to be 0, that is, the transmit power on the first symbol is concentrated for transmitting the first UCI. This can greatly improve the transmission power of the first UCI and improve the reliability of the URLLC service.
  • the first UCI can be protected from the number of resources, that is, the first UCI is configured with more resources, and the first UCI can be protected from the transmission power, that is, the first UCI is provided with higher transmission. power. Both of these methods can improve the transmission reliability of the URLLC UCI, thereby ensuring high reliability of the URLLC service.
  • more resources may be configured for the first UCI in the following manner.
  • the network device may pre-define the number of frequency domain resources that the first UCI punctured the PUSCH on the first symbol.
  • the network device may configure multiple options, for example, assuming that the frequency domain resource size of the PUSCH scheduling is 10 RBs.
  • the network device is configured with two options: punching 2 RBs and punching 5 RBs.
  • the network device can notify the terminal of which option is adopted by using RRC signaling. In this way, the terminal can punct the frequency domain resource of the PUSCH on the first symbol according to the configuration of the network device, and can implement more resources for the first UCI.
  • the number of the physical resources that the terminal device finally maps may be the number of resources that the first UCI configured by the network device punctured the PUSCH on the first symbol, or the number of resources actually needed by the first UCI, or It is the number of resources occupied by the PUCCH, and may also be the minimum of the number of resources actually needed by the first UCI and the number of resources occupied by the PUCCH.
  • the transmit power of the first UCI may also be increased in the following manner.
  • the transmit power of the first UCI can be predefined.
  • the transmit power of the first UCI may be predefined as a preset power value.
  • the transmit power of the first UCI may be predefined as the maximum transmit power of the terminal.
  • the power boosting multiple of the first UCI can be predefined. In this way, it is also possible to provide a higher transmission power for the first UCI, ensuring high reliability of the first UCI.
  • the transmit power of the first UCI may be consistent with the transmit power of the PUSCH on the adjacent symbol. As shown in FIG. 10, the adjacent symbol refers to a time domain for transmitting the PUSCH adjacent to the first symbol. symbol.
  • the predefined here can be system or protocol pre-defined.
  • the terminal may stop transmitting the remaining portion of the PUSCH after the first UCI after transmitting the first UCI.
  • the specific strategy for stopping the transmission of the PUSCH can be as follows:
  • the network device can configure whether to continue transmitting the remaining part of the PUSCH.
  • the terminal continues to transmit the remaining part of the PUSCH, otherwise, stops transmitting the remaining part of the PUSCH.
  • the first threshold may be pre-defined by the protocol, or may be predefined by the network device, or may be dynamically configured by the network device according to the sending capability reported by the terminal.
  • the first UCI carries the (piggyback) PUSCH transmission
  • the PUSCH DMRS (shown in FIG. 11A) is immediately adjacent to the time-frequency resources to improve channel estimation performance.
  • the first UCI transmitted after the PUSCH DMRS as shown in FIG. 11B, the first UCI may be piggybacked onto the PUSCH physical resource according to the timing requirement of the first UCI.
  • the timing requirement of the first UCI is that the terminal needs to send the first UCI at the feedback time of the PDSCH as required, and meets the delay requirement of the first UCI.
  • the terminal may use the protocol to take the value of the beta offset field predefined by the first UCI, or the RRC signaling takes the value of the beta offset field of the first UCI configuration.
  • the terminal can also take the value of the largest beta offset field in all the predefined beta offset field values. In this way, it is ensured that more resources are allocated for the first UCI to ensure reliable transmission of the first UCI.
  • the transmission priority of the three is: ACK/NACK>RI>CQI/PMI.
  • a greater than sign indicates a higher priority.
  • the DMRS of the PUSCH is a comb DMRS corresponding to the CP-OFDM
  • the DMRS of the URLLC ACK/NACK and the PUSCH may multiplex the time domain resources, that is, may be sent on the same symbol.
  • the URLLC ACK/NACK may skip the symbols of the DMRS used to transmit the PUSCH.
  • the URLLC ACK/NACK may be mapped on the resource of the DMRS for transmitting the PUSCH. Because the 1-2 bit URLLC ACK/NACK sequence does not affect the channel estimation, the network side can blindly detect this sequence and then do channel estimation.
  • the starting RB of the first UCI may be: m 0 or m k-1 .
  • the starting RB of the first UCI may also be: or or or or
  • the actual RB of the first UCI may also be or
  • the signal quality of the filter edge for processing the transmitted signal may be lost by setting the starting RB of the first UCI to the intermediate frequency domain position of the PUSCH. Reduce the impact of the filter on UCI performance. At the same time, setting the initial RB of the first UCI in the intermediate frequency domain position of the PUSCH can reduce the interference of the neighbor frequency domain to the UCI.
  • the frequency domain resource to which the first UCI is mapped in the PUSCH may be a continuous frequency domain resource block.
  • the subcarrier spacing (SCS) of the first UCI may adopt a subcarrier spacing of the PUSCH. This can reduce frequency domain interference between the first UCI and the PUSCH.
  • the first UCI may further adopt a longer cyclic prefix (CP) to further reduce frequency domain interference.
  • CP cyclic prefix
  • the subcarrier spacing (SCS) of the first UCI may adopt a subcarrier spacing of the URLLC PUCCH to reduce the delay.
  • the timing requirement of the URLLC UCI is to point to the received PDSCH, and the terminal needs to send the URLLC UCI at the feedback time of the PDSCH as required to meet the delay requirement of the first UCI.
  • the terminal may determine whether the received first DCI meets the first condition, and if the first condition is met, the terminal may provide the first UCI.
  • the first UCI may be preferentially transmitted, or a more reliable coding mode may be set for the first UCI.
  • FIG. 12 is a schematic flowchart diagram of another uplink control information transmission method provided by the present application. The following expands as follows:
  • the network device sends the first DCI to the terminal.
  • the terminal receives the first DCI sent by the network device.
  • the terminal sends a first UCI to the network device, where the first UCI is triggered by the first DCI.
  • the first UCI may be protected in at least one of the following conditions: the sending sequence and the encoding mode, where the first UCI and the second UCI are multiplexed with the time domain resources, and the first condition is satisfied: the first UCI
  • the first UCI is preferentially transmitted, and the first coding mode adopted by the first UCI is superior to the second coding mode adopted by the second UCI in terms of data transmission reliability.
  • a time domain resource for transmitting a first UCI may be referred to as a first time domain resource
  • a time domain resource for transmitting a second UCI may be referred to as a second time domain resource
  • the first UCI and the second UCI multiplexed time domain resource means that the first time domain resource and the second time domain resource partially or completely overlap.
  • the first UCI priority second UCI is sent to mean that the end time domain symbol carrying the first UCI is earlier than the start time domain symbol carrying the second UCI.
  • the method for determining whether the first DCI received by the terminal meets the first condition is specifically referred to the foregoing content, and details are not described herein again.
  • the terminal may provide special protection for the UCI (ie, the first UCI) corresponding to the DCI. The details are described below.
  • the resources for transmitting the first UCI and the resources for transmitting the second UCI overlap partially or completely in the time domain.
  • the second premise is that resources for transmitting the first UCI and resources for transmitting the second UCI overlap partially or completely in the time domain, and partially or completely overlap in the frequency domain.
  • the third premise is that the resources for transmitting the first UCI and the resources for transmitting the second UCI overlap partially or completely in the time domain, and do not overlap in the frequency domain, but the terminal does not have the capability of transmitting multiple services simultaneously on the uplink. For example, power is limited or uplink single carrier transmission is adopted.
  • the basic premise of providing protection for the first UCI is that the first time domain resource and the second time domain resource overlap partially or completely, that is, the first UCI and the second UCI multiplex time domain resource.
  • the first premise indicates that, under the condition that the first UCI and the second UCI are multiplexed with the time domain resource, if the first UCI satisfies the first condition, the terminal may provide special protection for the first UCI, that is, execute S203.
  • the second premise indicates that, under the condition that the first UCI and the second UCI are multiplexed with time-frequency resources, if the first UCI satisfies the first condition, the terminal may provide special protection for the first UCI, that is, execute S203.
  • the third premise indicates that if the first UCI and the second UCI are only multiplexed with time domain resources (the frequency domain resources are not multiplexed), and the terminal does not have the capability of transmitting multiple services simultaneously, if the first UCI satisfies the first In one condition, the terminal can provide special protection for the first UCI, that is, execute S203.
  • the end time domain symbol carrying the first UCI is earlier than the start time domain symbol of the second UCI, that is, the second UCI may be Delayed transmission, first sending the first UCI, then sending the second UCI.
  • the first UCI with high reliability requirements is transmitted first, and then the second UCI is sent to ensure the reliability of the URLLC service.
  • the symbol for transmitting the first UCI is symbol 1
  • the symbol for transmitting the second UCI is also symbol 1
  • the second UCI can be delayed to be transmitted on symbol 2. That is, the end time domain symbol (ie, symbol 1) carrying the first UCI is earlier than the start time domain symbol (ie, symbol 2) carrying the second UCI.
  • symbols for transmitting the first UCI are symbols 1-2
  • symbols for transmitting the second UCI are also symbols 2-3
  • the second UCI can be delayed to symbols 3-4. send. That is, the end time domain symbol (ie, symbol 2) carrying the first UCI is earlier than the start time domain symbol (ie, symbol 3) carrying the second UCI.
  • the terminal may perform HARQ-ACK bits bundling on the second UCI that is delayed in transmission, so that the feedback delay of the second UCI can be reduced.
  • the terminal may determine whether to perform HARQ-ACK bits bundling on the delayed second UCI according to the symbol resource corresponding to the second UCI being delayed to be sent. If the symbol resource is tight, the terminal is insufficient to pass the HARQ-ACK bits multiplexing manner. Transmitting the second UCI may determine to perform HARQ-ACK bits bundling on the second UCI that is delayed.
  • the first UCI adopts the first coding method
  • the first coding mode adopted by the first UCI is superior to the second coding mode adopted by the second UCI in terms of data transmission reliability.
  • the first coding mode is different from the second coding mode, and the difference between the two may be, but is not limited to, the first coding mode may increase the number of bits after the first UCI coding, and/or the second coding mode reduces the second UCI code. The number of bits. specific:
  • the first encoding manner may include: performing redundancy encoding on the first UCI. That is, the terminal may first add redundancy to the source of the first UCI and then encode, or may first encode and then perform bit plus redundancy on the encoded first UCI.
  • the number of bits after the first UCI encoding can be increased, so that the first UCI has higher error correction capability than the second UCI, and the high reliability of the URLLC service is ensured.
  • FIG. 15A shows 4 bits of continuous feedback, wherein the first, second, and fourth bits are the second UCI, and the third bit is the first UCI.
  • the first UCI is repeatedly coded, and the sequence length of the first UCI is increased from 1 bit to 3 bits, the redundancy is increased, and the reliability is also increased.
  • the examples are merely illustrative of the application and should not be construed as limiting.
  • the second coding mode may include performing HARQ-ACK bit binding on the second UCI. This reduces the number of bits after the second UCI encoding.
  • the first UCI may be redundantly coded, and the HARQ-ACK bit bundling is performed on the second UCI, so that the transmission reliability of the first UCI can be improved, and the first UCI and the first feedback can be reduced.
  • Two resources required for UCI For example, as shown in FIG. 15B, by HARQ-ACK bits bundling, the sequence length of the second UCI is shortened from 3 bits to 1 bit, even if the first UCI is redundantly processed and then increased to 3 bits, the first UCI and the second UCI The data length of the common feedback remains unchanged.
  • the HARQ-ACK bit bundling of the second UCI may be a Bundling of HARQ-ACK bits corresponding to different CBGs, or a Bundling of HARQ-ACK bits corresponding to different TBs (Transport Blocks), or different component carriers or The HARQ-ACK bit corresponding to the bandwidth part is used for bundling.
  • the high reliability of the URLLC can be guaranteed by the settings of the encoding.
  • URLLC ACK/NACK and eMBB ACK/NACK are 2 bits in total
  • the first bit is URLLC ACK/NACK
  • the second bit is eMBB ACK/ NACK.
  • These 2 bits have four states: "00", “01”, “10”, “11”. Where “0” represents NACK and "1" stands for "ACK”.
  • it is necessary to reduce the probability that the "0" of the first bit is misdetected to "1” or "1" is misdetected to "0".
  • the terminal may set a larger code distance for "00” and “10", “00” and “11”, “01” and “11”, “01” and “10".
  • the reliability requirements of eMBB are not high, so a small code distance can be set for 00 and 01, 10 and 11.
  • mapping to the constellation map is corresponding. The longer the distance on the constellation, the higher the reliability.
  • the mapping position of "00" on the constellation map and the mapping position of "10” on the constellation map can be expanded.
  • the distance between the mapping position of "00” on the constellation map and the mapping position of "11” on the constellation diagram, the mapping position of "01” on the constellation diagram and the mapping of "10” on the constellation diagram The distance between the positions, the distance between the mapped position of "01” on the constellation map and the mapped position of "11” on the constellation map.
  • the terminal may further provide more protection for the first UCI in the following manner:
  • the terminal may use the protocol to take the value of the beta offset field predefined by the first UCI, or the RRC signaling takes the value of the beta offset field configured by the first UCI.
  • the terminal can also take the value of the largest beta offset field in all the predefined beta offset field values. In this way, it is ensured that more resources are allocated for the first UCI to ensure reliable transmission of the first UCI.
  • the above method is also applicable to the case shown in the above-mentioned FIG. As shown in FIG. 17, for the URLLC service after the burst occurs in the UL grant, although the number of REs occupied by the URLLC UCI is not indicated in the DCI (specifically, the beta offset in the DCI) for transmitting the UL grant, the terminal
  • the value of the beta offset field predefined by the URLLC UCI can be used to ensure that the URLLC UCI obtains more resources and better guarantees the high reliability of the URLLC.
  • the above method can also be applied to the scenario where the URLLC UCI is separately sent.
  • the URLLC UCI is transmitted separately, and the eMBB UCI does not reuse the time domain resource.
  • the code rate of the first UCI is lower than the code rate of the second UCI.
  • the terminal may adopt a protocol-predefined or RRC signaling configured code rate for the first UCI to better guarantee the low code rate of the first UCI and ensure high reliability of the URLLC service.
  • the network device may predefine the transmit power of the first UCI.
  • the network device may pre-define the transmit power of the first UCI as a preset power value.
  • the network device may predefine the transmit power of the first UCI as the maximum transmit power of the terminal.
  • the network device may predefine a power boosting multiple of the first UCI.
  • the symbol 2-4 is the first symbol.
  • URLLC ACK/NACK and eMBB PUCCH multiplexing symbol 2 URLLC RI and eMBB PUCCH multiplexing symbol 3
  • the network device may configure the transmit power of the first UCI (ACK/NACK, RI, CQI/PMI) on the symbol 2-4 to be a preset power value, or configure the power boost multiple of the first UCI on the symbol 2-4 ( That is, the transmission power of the first UCI increases, and the transmission power of the eMBB PUCCH decreases.
  • the transmit power of the eMBB PUCCH can be configured to be 0, that is, all the power at symbols 2-4 is used to transmit the first UCI. In this way, the first UCI can be provided with higher transmission power, ensuring high reliability of the URLLC UCI.
  • the present application also provides an uplink control information transmission method.
  • the first DCI implicitly or explicitly determined by the terminal in the foregoing embodiment is determined to be protected by the UCI corresponding to the first DCI (ie, the first DCI triggered UCI).
  • the terminal may UCI's own characteristics to determine whether the UCI transmission requires special protection. This embodiment is not limited to the URLLC UCI or the eMBB UCI.
  • This example provides the following two ways of judging.
  • Judging method 1 determines whether the UCI currently sent by the terminal needs special protection by whether the terminal is in the cooperation set. If the terminal is in the cooperation set, it is determined that the UCI needs special protection.
  • each transmission point TRP can receive the UCI sent by the terminal, and special protection is needed for the UCI.
  • TRP transmission point
  • Judging method 2 according to the number of symbols of the PUCCH or the SCS, it is determined whether it is necessary to provide special protection for the UCI currently sent by the terminal. If the number of symbols of the PUCCH is small or the SCS is large, it is determined that the UCI requires special protection.
  • the first threshold or the second threshold may be protocol pre-defined or RRC signaling configured.
  • the present application also proposes a method for determining whether the SR needs protection.
  • the method may include, but is not limited to, the following two methods:
  • the URLLC service is predefined by RRC signaling configuration or protocol.
  • the MAC layer of the terminal sends the SR, it attaches a label or attribute to the SR to identify whether the SR is a URLLC SR that requires special protection.
  • the network device configuration or protocol pre-defines certain services (represented by logical channel or QCI (QoS class identifier)) is a URLLC service.
  • QCI QoS class identifier
  • Manner 2 Configuring multiple sets of SR configurations through RRC (configuration may include time domain resources, frequency domain resources, or time-frequency resources, etc.), where a certain (or some) set of configurations is used to transmit URLLC SRs.
  • RRC Radio Resource Control
  • the network device configures multiple sets of SR configurations, one (or some) of which is configured to transmit URLLC SRs.
  • the MAC layer of the terminal sends a URLLC SR to the physical layer of the terminal, the SR configuration corresponding to the URLLC SR is adopted.
  • the SR After combining the mode 1 or the mode 2, after determining that the SR needs to be protected, the SR can be specially protected according to the solution provided in the foregoing embodiment, and details are not described herein again.
  • FIG. 19 illustrates a wireless communication system and associated communication device.
  • the wireless communication system 10 includes a terminal 400 and a network device 500.
  • the wireless communication system 10 can be the wireless communication system 100 shown in FIG.
  • the terminal 400 may be the terminal device 103 in the wireless communication system 100 shown in FIG. 2.
  • Network device 500 may be network device 101 in wireless communication system 100 shown in FIG.
  • the functional units respectively included in the terminal 400 and the network device 500 are described below.
  • the terminal 400 may include a receiving unit 401 and a transmitting unit 403. among them:
  • the receiving unit 401 can be configured to receive the first DCI.
  • the sending unit 403 can be configured to send the first UCI, where the first UCI is triggered by the first DCI.
  • the physical hardware corresponding to the receiving unit 401 may be a receiver; and the physical hardware corresponding to the sending unit 403 may be a transmitter.
  • the terminal 400 can also include a memory for storing programs and/or data executed by the processor.
  • the network device 500 may include: a transmitting unit 501 and a receiving unit 503. among them:
  • the sending unit 501 can be configured to send the first DCI.
  • the receiving unit 503 is configured to receive the first UCI, where the first UCI is triggered by the first DCI.
  • the physical hardware corresponding to the receiving unit 502 may be a receiver; and the physical hardware corresponding to the sending unit 501 may be a transmitter.
  • Network device 500 can also include a memory for storing programs and/or data executed by the processor.
  • the first symbol when the first time domain resource overlaps with the time domain resource of the uplink data channel partially or completely, and the first condition is met, the first symbol carries the first UCI without being carried. Upstream data channel.
  • the first symbol is a time domain symbol in which the time domain resources of the first time domain resource and the uplink data channel overlap.
  • the first time domain resource is used to transmit the first UCI.
  • the end time domain symbol carrying the first UCI is earlier than the second UCI.
  • the first time domain resource is used to transmit the first UCI
  • the second time domain resource is used to transmit the second UCI.
  • the first coding mode adopted by the first UCI is in terms of data transmission reliability. Better than the second encoding method adopted by the second UCI.
  • the first time domain resource is used to transmit the first UCI
  • the second time domain resource is used to transmit the second UCI.
  • the network device chip implements the functions of the network device in the foregoing method embodiment.
  • the network device chip transmits the first DCI or receives the first UCI from other modules in the network device (such as a radio frequency module or an antenna) to other modules in the network device, such as a radio frequency module or an antenna.
  • the first DCI is sent to the terminal via other modules of the network device.
  • the first UCI is sent by the terminal to the network device.
  • the terminal chip When the embodiment of the present application is applied to a terminal backup chip, the terminal chip implements the function of the terminal in the foregoing method embodiment.
  • the terminal chip receives the first DCI from other modules in the terminal, such as a radio frequency module or an antenna, or sends the first UCI through other modules in the terminal, such as a radio frequency module or an antenna.
  • the first UCI is sent to the network device via other modules of the terminal.
  • the first DCI is sent by the network device to the terminal.
  • the implementation of the technical solution provided by the present application can provide special protection for the URLLC UCI in terms of transmission resources, coding mode, and transmission sequence, and can better ensure the high reliability of the URLLC service.
  • the program can be stored in a computer readable storage medium, when the program is executed
  • the flow of the method embodiments as described above may be included.
  • the foregoing storage medium includes various media that can store program codes, such as a ROM or a random access memory RAM, a magnetic disk, or an optical disk.

Landscapes

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

Abstract

本申请公开了一种上行控制信息传输方法，所述方法可包括：终端可以根据接收到的第一DCI判断该DCI触发的UCI是否是高可靠UCI，如果是，则针对该UCI设计特殊传输策略，为该UCI提供保护，确保URLLC业务的可靠性。本申请中，该特殊传输策略可以在以下至少一个方面优于普通的UCI传输策略：传输资源、编码方式、发送顺序等。上述方案可实现为URLLC UCI的传输提供特殊保护，更好的保证URLLC业务的高可靠性。

Description

上行控制信息传输方法及装置 技术领域
本申请涉及无线通信技术领域，尤其涉及上行控制信息传输方法及装置。
背景技术
第五代(the fifth generation，5G)移动通信系统支持增强型移动宽带(enhanced mobile broadband，eMBB)业务、高可靠低时延通信(ultra reliable and low latency communications，URLLC)业务以及海量机器类通信(massive machine type communications，mMTC)业务。典型的eMBB业务有：超高清视频、增强现实(augmented reality，AR)、虚拟现实(virtual reality，VR)等，这些业务的主要特点是传输数据量大、传输速率很高。典型的URLLC业务有：工业制造或生产流程中的无线控制、无人驾驶汽车和无人驾驶飞机的运动控制以及远程修理、远程手术等触觉交互类应用，这些业务的主要特点是超高可靠性、低延时，传输数据量较少以及具有突发性。典型的mMTC业务有：智能电网配电自动化、智慧城市等，主要特点是联网设备数量巨大、传输数据量较小、数据对传输时延不敏感，这些mMTC终端需要满足低成本和非常长的待机时间的需求。
不同业务对移动通信系统的需求不同，如何更好地同时支持多种不同业务的数据传输需求，是当前5G移动通信系统所需要解决的技术问题。例如，如何同时支持URLLC业务和eMBB业务就是当前5G移动通信系统的讨论热点之一。
URLLC业务对时延要求极高，不考虑可靠性的情况下，传输时延要求在0.5毫秒(millisecond，ms)以内；在达到99.999％的可靠性的前提下，传输时延要求在1ms以内。
在长期演进(long term evolution，LTE)系统中，最小的时间调度单元为一个1ms时间长度的传输时间间隔(transmission time interval，TTI)。为了满足URLLC业务的传输时延需求，无线空口的数据传输可以使用更短的时间调度单元。在5G移动通信系统中，可以支持基于时隙的(slot based)调度和基于非时隙的(non-slot based)调度,其中，一个时隙可以包括12或14个时域符号，这里的时域符号可以是正交频分复用(orthogonal frequency division multiplexing，OFDM)符号，也可以是离散傅里叶变换扩展正交频分复用(discrete fourier transform spread OFDM，DFTS-OFDM)符号。对于子载波间隔为15千赫兹(kilohertz，kHz)的一个时隙，包括12个或14个时域符号，对应的时间长度为1毫秒(millisecond，ms)；对于子载波间隔为60kHz的一个时隙，对应的时间长度则缩短为0.25ms。
目前，传输上行控制信息(uplink control information，UCI)的方式都不能很好地保证URLLC业务的可靠性。
发明内容
本申请提供了上行控制信息传输方法、相关装置及系统，可更好的保证URLLC业务的高可靠性。
第一方面，本申请提供了一种上行控制信息传输方法，该方法的执行主体可以是网络设备也可以是用于网络设备的芯片或部件。该方法包括：发送第一DCI，并接收第一UCI，第一UCI是由第一DCI触发。在第一时域资源与上行数据信道的时域资源部分或全部重叠，且第一条件被满足的条件下，第一符号上承载有第一UCI，而没有承载上行数据信道，第一符号为第一时域资源和上行数据信道的时域资源重叠的时域符号；第一时域资源用于传输第一UCI。
第二方面，本申请提供了一种上行控制信息传输方法，该方法的执行主体可以是终端设备也可以是用于终端设备的芯片或部件。该方法包括：接收第一下行控制信息DCI，并发送第一上行控制信息UCI，第一UCI由第一DCI触发；在第一时域资源与上行数据信道PUSCH的时域资源部分或全部重叠，且第一条件被满足的条件下，第一符号上承载有第一UCI，而没有承载PUSCH，第一符号为第一时域资源和PUSCH的时域资源重叠的时域符号；第一时域资源用于传输第一UCI。
下面详细介绍第一方面和第二方面描述的上行控制信息传输方法：
(1)为第一UCI提供保护的前提
第一种前提，用于传输第一UCI的资源和用于传输PUSCH的资源在时域上部分或全部重叠。
第二种前提，用于传输第一UCI的资源和用于传输PUSCH的资源在时域上部分或全部重叠，且在频域上部分或全部重叠。
第三种前提，用于传输第一UCI的资源和用于传输PUSCH的资源，且在频域上不重叠，但是终端没有上行同时发送多业务的能力，例如功率受限或者是采用上行单载波传输方式。
综合上述三种前提可以看出，为第一UCI提供保护的基本前提为：第一时域资源和PUSCH的时域资源部分或全部重叠，即第一UCI和PUSCH复用时域资源。其中，第一种前提表示，在第一时域资源和PUSCH的时域资源部分或全部重叠的条件下，如果第一条件是否被满足，则终端可以为第一UCI提供特殊保护。第二种前提表示，在第一UCI和PUSCH复用时频资源的条件下，如果第一条件是否被满足，则终端可以为第一UCI提供特殊保护。第三种前提表示，在第一UCI和PUSCH仅仅复用时域资源(不复用频域资源)，且终端不具备上行同时发送多业务的能力的条件下，如果第一UCI满足第一条件，则终端可以为第一UCI提供特殊保护。
(2)第一符号(第一UCI和PUSCH复用的时域资源)
举例说明，符号7、8、11用于传输URLLC UCI，符号7-14用于传输PUSCH。其中，符号7、8、11和符号7-14中相重叠的符号为：符号7、8、11，符号7、8、11即第一符号。
具体的，在第一符号上，第一UCI和PUSCH的频域资源复用情况可以包括以下几种：
第1种情况：第一UCI和PUSCH在第一符号上各自占用的频域资源完全不重叠，即第一UCI和PUSCH在第一符号上各自占用完全不同的频域资源。
第2种情况：第一UCI和PUSCH在第一符号上各自占用的频域资源部分重叠，即第一UCI和PUSCH在第一符号上各自占用的频域资源中有部分频域资源是相同的。
第3种情况：第一UCI和PUSCH在第一符号上各自占用的频域资源完全重叠，即第 一UCI和PUSCH在第一符号上各自占用的频域资源完全相同。
(3)第一符号上承载第一UCI而不承载PUSCH
具体的，终端可以为第一UCI打孔(puncture)第一符号上的所有RB，即第一符号仅用于传输第一UCI而不传输PUSCH。
举例说明，符号7、8、11用于传输URLLC UCI，符号7-14用于传输PUSCH。其中，符号7、8、11和符号7-14中相重叠的符号为：符号7、8、11，符号7、8、11即第一符号。为了特殊保护第一UCI，终端可以打孔(puncture)符号7、8、11上的所有RB。这样，可实现为第一UCI分配更多资源，保证URLLC业务的高可靠性。
可选的，终端还可以设置第一符号上的PUSCH的发射功率为0，即将第一符号上的发射功率都集中用于发射第一UCI。这样可以大大提高第一UCI的发射功率，提高URLLC业务的可靠性。
实施第一方面和第二方面描述的方法，可实现在URLLC UCI和PUSCH复用资源时，为URLLC UCI提供特殊保护，确保URLLC业务的可靠性。
第三方面，本申请提供了一种上行控制信息传输方法，该方法的执行主体可以是网络设备也可以是用于网络设备的芯片或部件。该方法包括：发送第一DCI，并接收第一UCI，第一UCI是由第一DCI触发；在第一时域资源与第二时域资源部分或全部重叠，且第一条件被满足的条件下，承载第一UCI的结束时域符号早于承载第二UCI的起始时域符号；第一时域资源用于传输第一UCI，第二时域资源用于传输第二UCI。
第四方面，本申请提供了一种上行控制信息传输方法，该方法的执行主体可以是终端设备也可以是用于终端设备的芯片或部件。该方法包括：接收第一下行控制信息DCI，并发送第一上行控制信息UCI，第一UCI由第一DCI触发；在第一时域资源与第二时域资源部分或全部重叠，且第一条件被满足的条件下，承载第一UCI的结束时域符号早于承载第二UCI的起始时域符号。第一时域资源用于传输第一UCI，第二时域资源用于传输第二UCI。
第五方面，本申请提供了一种上行控制信息传输方法，该方法的执行主体可以是网络设备也可以是用于网络设备的芯片或部件。该方法包括：接收第一DCI，并发送第一UCI，第一UCI由第一DCI触发；在第一时域资源与第二时域资源部分或全部重叠，且第一条件被满足的条件下，第一UCI采用的第一编码方式在数据传输可靠性方面优于第二UCI采用的第二编码方式；第一时域资源用于传输第一UCI，第二时域资源用于传输第二UCI。
第六方面，本申请提供了一种上行控制信息传输方法，该方法的执行主体可以是终端设备也可以是用于终端设备的芯片或部件。该方法包括发送第一DCI，并接收第一UCI，第一UCI是由第一DCI触发；在第一时域资源与第二时域资源部分或全部重叠，且第一条件被满足的条件下，第一UCI采用的第一编码方式在数据传输可靠性方面优于第二UCI采用的第二编码方式；第一时域资源用于传输第一UCI，第二时域资源用于传输第二UCI。
可以看出，第三方面和第四方面、第五方面和第六方面描述的上行控制信息传输方法可实现在URLLC UCI和eMBB UCI复用资源时，为URLLC UCI提供特殊保护，确保URLLC业务的可靠性。
下面详细介绍第三方面和第四方面、第五方面和第六方面描述的上行控制信息传输方法：
(1)为第一UCI提供保护的前提
第一种前提，用于传输第一UCI的资源和用于传输第二UCI的资源在时域上部分或全部重叠。
第二种前提，用于传输第一UCI的资源和用于传输第二UCI的资源在时域上部分或全部重叠，且在频域上部分或全部重叠。
第三种前提，用于传输第一UCI的资源和用于传输第二UCI的资源在时域上部分或全部重叠，且在频域上不重叠，但是终端没有上行同时发送多业务的能力，例如功率受限或者是采用上行单载波传输方式。
综合上述三种前提可以看出，为第一UCI提供保护的基本前提为：第一时域资源和第二时域资源部分或全部重叠，即第一UCI和第二UCI复用时域资源。其中，第一种前提表示，在第一UCI和第二UCI复用时域资源的条件下，如果第一UCI满足第一条件，则终端可以为第一UCI提供特殊保护。第二种前提表示，在第一UCI和第二UCI在复用时频资源的条件下，如果第一UCI满足第一条件，则终端可以为第一UCI提供特殊保护。第三种前提表示，在第一UCI和第二UCI仅仅复用时域资源(不复用频域资源)，且终端不具备上行同时发送多业务的能力的条件下，如果第一UCI满足第一条件，则终端可以为第一UCI提供特殊保护。
(2)承载第一UCI的结束时域符号早于承载第二UCI的起始时域符号
具体的，在第一时域资源和第二时域资源部分或全部重叠时，承载第一UCI的结束时域符号早于承载第二UCI的起始时域符号，即第二UCI可以被延迟发送，先发送第一UCI，后发送第二UCI。这样，确保可靠性需求高的第一UCI先发送，然后再发送第二UCI，保证URLLC业务的可靠性。
进一步的，终端可以对被延迟发送的第二UCI做HARQ-ACK bits bundling，这样可以减少第二UCI的反馈时延。
可选的，终端具体可以根据第二UCI被延迟发送所对应的符号资源确定是否对延迟的第二UCI做HARQ-ACK bits bundling，如果该符号资源比较紧张，不足以通过HARQ-ACK bits multiplexing方式传输第二UCI，则可以确定对被延迟发送的第二UCI做HARQ-ACK bits bundling。
(3)第一UCI采用第一编码方式
具体的，第一UCI采用的第一编码方式在数据传输可靠性方面优于第二UCI采用的第二编码方式。第一编码方式不同于第二编码方式，二者的区别可以体现在但不限于：第一编码方式可以增加第一UCI编码后的比特数，和/或第二编码方式减少第二UCI编码后的比特数。具体的：
第一编码方式可包括：对第一UCI进行冗余编码。即终端可以先对第一UCI的信源加冗余然后编码，也可以先编码然后对编码后的第一UCI进行比特加冗余。这样，可增加第一UCI编码后的比特数，使得第一UCI比第二UCI具有更高的纠错能力，保证URLLC业务的高可靠性。
第二编码方式可包括：对第二UCI进行HARQ-ACK比特绑定。这样可减少第二UCI编码后的比特数。
可选的，可以对第一UCI进行冗余编码，且对第二UCI做HARQ-ACK比特bundling，这样不仅可以提高第一UCI的传输可靠性，还可以减少共同反馈第一UCI和第二UCI所需的资源。
结合第一方面或第二方面，结合第三方面或第四方面，结合第五方面或第六方面，在一些可选实施例中，第一条件可以包括但不限于：
(1)DCI格式是用于URLLC业务的DCI格式
本申请中，用于URLLC业务的DCI格式可以称为紧凑型DCI(compact DCI，又称为URLLC DCI)格式。
具体的，compact DCI格式可以通过但不限于以下至少一项来指示：DCI的净荷大小等于第一取值；或，DCI的净荷大小(payload size)等于第一取值，且DCI中的DCI格式标识(Identifier for DCI format)字段取值等于第二取值；或，DCI的净荷大小等于第一取值，且DCI的搜索空间为终端设备UE特定搜索空间；或，DCI的净荷大小等于第一取值，第一DCI的DCI格式标识字段的取值等于第二取值，且DCI的搜索空间为UE特定搜索空间；或，DCI的搜索空间为第一搜索空间；或，DCI的循环冗余校验CRC的校验比特长度等于第三取值；或，DCI的循环冗余校验CRC的校验比特长度等于第三取值；或，用于加扰DCI的CRC校验比特的无线网络临时标识RNTI等于第一RNTI；或，传输DCI的控制资源集合CORESET为第一CORESET。
其中，第一取值、第二取值、第三取值、第一搜索空间、第一CORESET这几项参数均可以是网络设备通过高层信令，如无线资源控制(radio resource control，RRC)信令、MAC CE信令，配置的。第一取值为compact DCI的净荷大小。第二取值为compact DCI中的DCI格式标识字段取值。第三取值为compact DCI的CRC的校验比特长度。第一搜索空间为用于检测compact DCI的搜索空间。第一CORESET为用于传输compact DCI的CORESET。
也即是说，可以通过高层信令配置compact DCI格式，compact DCI格式不同于普通DCI格式(如用于eMBB业务的DCI格式)。相比于普通DCI(如eMBBDCI)格式，compact DCI格式可以具备以下至少一项属性：第一取值小于普通DCI的净荷大小、第二取值不同于普通DCI中的DCI格式标识字段取值、第三取值大于普通DCI的CRC的校验比特长度。第一搜索空间不同于用于检测普通DCI的搜索空间。第一CORESET不同于用于传输普通DCI的CORESET。
这样，终端便可以根据payload size区分接收到的第一DCI是不是compact DCI，如果接收到的第一DCI的payload size等于第一取值，则可以确定该DCI是compact DCI，即满足第一条件。
这样，终端便可以结合payload size和Identifier for DCI format字段区分接收到的第一DCI是不是compact DCI，如果接收到的第一DCI的payload size等于第一取值且Identifier for DCI format字段取值等于第二取值，则可以确定该DCI是compact DCI，即满足第一条件。可选的，在接收到的多个DCI的payload size一致(payload alignment)的前提下，终端可以进一步结合Identifier for DCI format字段取值来区分出compact DCI。
这样，终端便可以根据CRC的校验比特长度区分接收到的第一DCI是不是compact DCI， 如果接收到的第一DCI的CRC的校验比特长度等于第三取值，则可以确定该DCI是compact DCI，即满足第一条件。
这样，终端便可以根据检测到第一DCI的资源位置区分接收到的第一DCI是不是compact DCI，如果检测到第一DCI的资源位置为第一搜索空间，则可以确定第一DCI是compact DCI，即满足第一条件。
这样，终端便可以根据第一DCI占用的资源位置区分接收到的第一DCI是不是compact DCI，如果第一DCI占用的资源位置为第一CORESET，则可以确定第一DCI是compact DCI，即满足第一条件。
(2)用于加扰DCI的CRC校验比特的无线网络临时标识(radio network temporary identifier，RNTI)等于第一RNTI
具体的，第一RNTI可以是网络设备通过高层信令，如RRC信令、MAC CE信令，配置的。第一RNTI用于加扰compact DCI的CRC校验比特。也即是说，可以通过高层信令配置用于加扰compact DCI的CRC校验比特的RNTI。这样，终端便可以根据加扰DCI的CRC校验比特的RNTI区分接收到的第一DCI是否是compact DCI。
(3)DCI的搜索空间(search space)为第一搜索空间
具体的，第一搜索空间可以是网络设备通过高层信令，如RRC信令、MAC CE信令，配置的。在第一搜索空间上检测到的DCI即compact DCI。也即是说，可以通过高层信令配置search space的属性(是否是URLLC的search space)。这样，终端便可以根据检测DCI的search space的属性来区分该DCI是否是compact DCI。
(4)DCI的控制资源集合(CORESET)为第一CORESET
具体的，第一CORESET可以是网络设备通过高层信令，如RRC信令、MAC CE信令，配置的。第一CORESET用于发送compact DCI。也即是说，可以通过高层信令配置CORESET的属性(是否是URLLC的CORESET)。这样，终端便可以根据接收DCI的CORESET的属性来区分该DCI是否是compact DCI。
除了上述几种方式，终端还可以通过下述方式来判断DCI是否满足第一条件。
可选的，终端可以通过校验的步骤来判断DCI是否是compact DCI。当DCI需要采用两步或两步以上的校验方式时，则终端可以确定该DCI是compact DCI，即该DCI满足第一条件。
可选的，终端可以判断DCI中是否有用于降低错误概率概率的字段，如果有该字段，则可以确定该DCI是compact DCI，即该DCI满足第一条件。
可选的，终端可以根据DCI采用的编码方式来判断DCI是否是compact DCI。当DCI采用的编码方式是特定编码方式时，则终端可以确定该DCI是compact DCI，即该DCI满足第一条件。该特定编码方式是低密度奇偶校验(low-density parity check,LDPC)或极化(polar)编码或者Reed-Muller编码或双Reed-Muller编码中的一种。
上述判断DCI是否满足第一条件的实现方式属于隐式判断相应UCI是否需要保护的方式。另外，还可以采用显式方式来判断对应于该DCI的UCI是否需要保护。具体方案可如下：DCI可以携带1比特的字段，用于区分对应于该DCI的UCI是否需要被保护。
例如，如表1所示，当该比特取值为“0”时，表示对应于该DCI的UCI不需要被保护； 当该比特取值为“1”时，表示对应于该DCI的UCI需要被保护。
第七方面，本申请提供了一种通信装置，该通信装置可包括多个功能模块，用于相应的执行第一方面、第三方面、第五方面所提供的方法，或者这些方面可能的实施方式中的任意一种所提供的方法。
第八方面，本申请提供了一种通信装置，该通信装置可包括多个功能模块，用于相应的执行第二方面、第四方面、第六方面所提供的方法，或者这些方面可能的实施方式中的任意一种所提供的方法。
第九方面，本申请提供了一种通信装置，用于执行第一方面描述的上行控制信息传输方法。通信装置可包括：存储器以及与存储器耦合的处理器、收发器，其中：收发器用于与其他通信设备(如通信装置)通信。存储器用于存储第一方面、第三方面、第五方面描述的上行控制信息传输方法的实现代码，处理器用于执行存储器中存储的程序代码，即执行第一方面、第三方面、第五方面所提供的方法，或者这些方面可能的实施方式中的任意一种所提供的方法。
第十方面，本申请提供了一种通信装置，用于执行第二方面描述的上行控制信息传输方法。通信装置可包括：存储器以及与存储器耦合的处理器、收发器，其中：收发器用于与其他通信设备(如通信装置)通信。存储器用于存储第二方面、第四方面、第六方面描述的信号传输的实现代码，处理器用于执行存储器中存储的程序代码，即执行第二方面、第四方面、第六方面所提供的方法，或者这些方面可能的实施方式中的任意一种所提供的方法。
第十一方面，提供了一种通信系统，通信系统包括：终端和网络设备，其中：网络设备可以是第七方面或第九方面描述的通信装置。终端可以是第八方面或第十方面描述的通信装置。
第十二方面，提供了一种计算机可读存储介质，可读存储介质上存储有指令，当其在计算机上运行时，使得计算机执行上述第一方面、第三方面、第五方面描述的上行控制信息传输方法，或者这些方面可能的实施方式中的任意一种所提供的方法。
第十三方面，提供了另一种计算机可读存储介质，可读存储介质上存储有指令，当其在计算机上运行时，使得计算机执行上述第二方面、第四方面、第六方面描述的上行控制信息传输方法，或者这些方面可能的实施方式中的任意一种所提供的方法。
第十四方面，提供了一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机执行上述第一方面、第三方面、第五方面描述的上行控制信息传输方法，或者这些方面可能的实施方式中的任意一种所提供的方法。
第十五方面，提供了另一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机执行上述第二方面、第四方面、第六方面描述的上行控制信息传输方法，或者这些方面可能的实施方式中的任意一种所提供的方法。
附图说明
为了更清楚地说明本申请实施例或背景技术中的技术方案，下面将对本申请实施例或背景技术中所需要使用的附图进行说明。
图1是本申请涉及的一种无线通信系统的架构示意图；
图2是采用已有的UCI反馈方式来复用传输URLLC UCI和eMBB PUCCH的示意图；
图3是采用已有的UCI反馈方式来复用传输URLLC UCI和eMBBPUSCH的示意图；
图4是本申请的一个实施例提供的终端的硬件架构示意图；
图5是本申请的一个实施例提供的基站的硬件架构示意图；
图6是本申请涉及的控制资源集合的示意图；
图7是本申请提供的一种上行控制信息传输方法的示例性示意图；
图8是URLLC UCI和PUSCH复用时域资源的示意图；
图9是URLLC UCI打孔PUSCH中的整个第一符号的示意图；
图10是URLLC UCI之后停止发送剩余PUSCH的示例性示意图；
图11A是eMBB UCI相对于PUSCH DMRS的资源位置的示例性示意图；
图11B是本申请中URLLC UCI相对于PUSCH DMRS的资源位置的示例性示意图；
图12是本申请提供的另一种上行控制信息传输方法的示例性示意图；
图13A是第一UCI和第二UCI在时域资源上完全重叠的示例性示意图；
图13B是第一UCI和第二UCI在时域资源上部分重叠的示例性示意图；
图14A是第二UCI延迟发送的一种情况的示例性示意图；
图14B是第二UCI延迟发送的另一种情况的示例性示意图；
图15A是对第一UCI和第二UCI采用不同冗余程度的编码方式的示例性示意图；
图15B是在图15A实例中对第二UCI进行HARQ-ACK bits bundling的示例性示意图；
图16A是对第一UCI和第二UCI采用不同码距的一种方式的示例性示意图；
图16B是对第一UCI和第二UCI采用不同码距的另一种方式的示例性示意图；
图17是第一UCI的资源数量由URLLC对应的beta offset指示的示意图；
图18是PUSCH上的功率用于提高URLLC UCI的发射功率的示意图；
图19是本申请的提供的无线通信系统，终端和网络设备的功能框图。
具体实施方式
本申请的实施方式部分使用的术语仅用于对本申请的具体实施例进行解释，而非旨在限定本申请。
图1示出了本申请涉及的无线通信系统。所述无线通信系统不限于LTE系统，还可以第五代5G移动通信系统、新空口(NR)系统，未来的移动通信系统等。如图1所示，无线通信系统100可包括：一个或多个网络设备101，一个或多个终端103，以及核心网115。其中：
网络设备101可以为基站，基站可以用于与一个或多个终端进行通信，也可以用于与一个或多个具有部分终端功能的基站进行通信(比如宏基站与微基站之间的通信)。基站可以是LTE系统中的演进型基站(Evolutional Node B，eNB)，以及5G系统、新空口(NR)系统中的基站。另外，基站也可以为接入点(Access Point，AP)、传输节点(Trans TRP)、中心单元(Central Unit，CU)或其他网络实体，并且可以包括以上网络实体的功能中的一些或所有功能。本申请的实施例对网络设备所采用的具体技术和具体设备形态不做限定。
终端103可以分布在整个无线通信系统100中，可以是静止的，也可以是移动的。终端103也可以称为用户设备(user equipment，UE)、移动台(mobile station，MS)、移动终端(mobile terminal，MT)等。终端103可以是手机(mobile phone)、平板电脑(Pad)、带无线收发功能的电脑、虚拟现实(Virtual Reality，VR)终端、增强现实(Augmented Reality，AR)终端、工业控制(industrial control)中的无线终端、无人驾驶(self driving)中的无线终端、远程手术(remote medical surgery)中的无线终端、智能电网(smart grid)中的无线终端、运输安全(transportation safety)中的无线终端、智慧城市(smart city)中的无线终端、智慧家庭(smart home)中的无线终端等等。
具体的，网络设备101可用于在网络设备控制器(未示出)的控制下，通过无线接口105与终端103通信。在一些实施例中，所述网络设备控制器可以是核心网115的一部分，也可以集成到网络设备101中。具体的，网络设备101可用于通过回程(blackhaul)接口113(如S1接口)向核心网115传输控制信息或者用户数据。具体的，网络设备101与网络设备101之间也可以通过回程(blackhaul)接口111(如X2接口)，直接地或者间接地，相互通信。
本申请中，网络设备101和终端103之间可支持多业务的同时传输，如5G及未来新空口(NR)支持的eMBB、URLLC和eMTC三大业务。应理解的，URLLC业务和eMBB业务不同，URLLC的可靠性要求很高，为了确保URLLC业务的可靠性，需要保证URLLC UCI的可靠性。
本申请中，UCI可以包括但不限于：调度请求(scheduling request，SR)、对应于PDSCH中下行数据包的HARQ ACK/NACK、信道状态信息(channel state information，CSI)。其中，CSI可以包括下行信道质量指示(channel quality indicator，CQI)，与MIMO反馈相关的秩指示(rank indication，RI)和预编码指示(precoding matrix indicator，PMI)。CSI还可以包括周期CSI和非周期CSI。URLLC HARQ ACK/NACK由调度URLLC PDSCH的DCI触发，URLLC非周期CSI由调度URLLC PUSCH的DCI触发，eMBB HARQ ACK/NACK由调度eMBB PDSCH的DCI触发，非周期eMBB CSI由调度eMBB PUSCH的DCI触发。
UCI可以在PUSCH中传输，也可以在PUCCH中传输。目前已有的UCI反馈方式并未特别考虑URLLC业务的可靠性需求，不能很好的保证URLLC业务的可靠性。下面分别针对两个不同的场景分析采用已有的UCI反馈方式来传输URLLC UCI所存在的问题。
场景1：URLLC UCI和eMBB UCI同时传输
在时分双工(time division duplexing，TDD)场景下，针对终端在多个下行子帧接收到的下行数据，终端需要在同一个上行子帧反馈ACK/NACK，即终端需要在同一个上行子帧中反馈多个ACK/NACK。假设存在四个下行子帧的ACK/NACK需要在一个上行子帧中反馈，这四个下行子帧分别调度了URLLC的数据和eMBB的数据，如图2所示。
针对UCI传输在PUCCH中，目前已有的反馈方法有两种方式：HARQ-ACK bits bundling(HARQ反馈比特绑定)和HARQ-ACK bits multiplexing(HARQ反馈比特复用)。HARQ-ACK bits bundling是将多个下行子帧的ACK/NACK做逻辑“与操作”。例如，假如图2所示的四个下行子帧的ACK/NACK分别是“0”、“0”、“1”、“1”(“1”代表ACK，“0”代表NACK)，经过HARQ-ACK bits bundling(即0&0&1&1＝0)后即反馈1比特的“0”，表 示这4个下行子帧(包括URLLC下行子帧)都要重传。这也意味着只有当URLLC的下行数据和eMBB的下行数据都被终端正确接收的时候，网络设备才认为终端设备正确接收了URLLC的业务数据，等效于URLLC的ACK反馈只有当eMBB子帧反馈的都是ACK的时候才能译码成功。HARQ-ACK bits multiplexing是直接反馈4比特的“1101”。
可以看出，已有HARQ-ACK bits multiplexing的方式没有对URLLC的ACK/NACK设计特殊的保护来保证URLLC UCI的高可靠性，URLLC ACK/NACK还会受到eMBB ACK/NACK的影响，URLLC UCI的可靠性得不到保证。
针对问题1，为了保证URLLC UCI的可靠性，本申请对上述eMBBACK/NACK和URLLCACK/NACK需要同时反馈的场景，设计新的反馈规则。具体详见后续实施例，这里先不赘述。
场景2：URLLC UCI和eMBB PUSCH同时传输
对于UCI在PUSCH中携带传输的场景，目前的技术方案是通过用于发送上行授权(UL grant)的DCI中的beta offset字段来指示UCI所占的资源单元(resource element，RE)的个数。这里，beta offset的取值与码率(code rate)相关，即可以用于指示UCI占用的资源数量。
具体的，DCI为发送UL grant之前的PDSCH的ACK/NACK配置betaoffset值。但是，URLLC业务通常是突发的，对于突发出现在发送UL grant之后的URLLC业务，URLLC UCI占用的RE个数并没有在发送UL grant的DCI中进行指示，没有特殊机制来保护URLLC UCI占用的资源数量，从而确保URLLC UCI的传输可靠性。
例如，如图3所示，eMBB PDSCH在UL grant之前，URLLC PDSCH突发出现在该UL grant之后。在发送该UL grant的DCI中，仅为eMBB PDSCH配置了beta offset值，即beta offset1。如图3所示，该beta offset1指示了eMBB UCI占用的资源数量为4个RE。对于出现在该UL grant之后的URLLC PDSCH，在发送该UL grant的DCI中并未为URLLC PDSCH的UCI(即URLLC UCI)配置beta offset值。这样，出现在该UL grant之后的URLLC PDSCH的URLLC UCI所占用的资源数量只能遵循为eMBB UCI配置的beta offset1所指示的资源数量(即4个RE)，而不能特别的为URLLC UCI分配更多资源，URLLC UCI的可靠性得不到保障。
本申请中，为了确保URLLC的可靠性，可以为URLLC UCI提供特殊保护。保护方式可包括但不限于：给URLLCUCI分配更多资源(如时域资源、频域资源、码域资源、功率域资源)、URLLCUCI使用可靠性更高的编码方式等等。保护方式还可包括：多小协作传输URLLC UCI。例如，为了提升小区边缘用户的可靠性，会采取多小区协作传输URLLC UCI的方式。也即是说，URLLC UCI是要发给多个小区的网络设备(如基站)的，这样URLLC UCI自然就具备更高的可靠性。关于本申请提供的用于特殊保护URLLC UCI的传输方法，请具体参考后续实施例，这里先不赘述。
需要说明的，图1示出的无线通信系统100仅仅是为了更加清楚的说明本申请的技术方案，并不构成对本申请的限定，本领域普通技术人员可知，随着网络架构的演变和新业务场景的出现，本申请提供的技术方案对于类似的技术问题，同样适用。
参考图4，图4示出了本申请的一些实施例提供的终端200。如图4所示，终端200可包括：一个或多个终端处理器201、存储器202、接收器205、发射器206、耦合器207、天线208、用户接口202，以及输入输出模块(包括音频输入输出模块210、按键输入模块211以及显示器212等)。这些部件可通过总线204或者其他方式连接，图4以通过总线连接为例。其中：
发射器206可用于对终端处理器201输出的信号进行发射处理，例如信号调制。接收器205可用于对天线208接收的移动通信信号进行接收处理，例如信号解调。在本申请的一些实施例中，发射器206和接收器205可看作一个无线调制解调器。在终端200中，发射器206和接收器205的数量均可以是一个或者多个。天线208可用于将传输线中的电磁能转换成自由空间中的电磁波，或者将自由空间中的电磁波转换成传输线中的电磁能。耦合器207用于将天线208接收到的移动通信信号分成多路，分配给多个的接收器205。
除了图4所示的发射器206和接收器205，终端200还可包括其他通信部件，例如GPS模块、蓝牙(Bluetooth)模块、无线高保真(Wireless Fidelity，Wi-Fi)模块等。不限于上述表述的无线通信信号，终端200还可以支持其他无线通信信号，例如卫星信号、短波信号等等。不限于无线通信，终端200还可以配置有有线网络接口(如LAN接口)来支持有线通信。
所述输入输出模块可用于实现终端200和用户/外部环境之间的交互，可主要包括包括音频输入输出模块210、按键输入模块211以及显示器212等。具体的，所述输入输出模块还可包括：摄像头、触摸屏以及传感器等等。其中，所述输入输出模块均通过用户接口209与终端处理器201进行通信。
存储器202与终端处理器201耦合，用于存储各种软件程序和/或多组指令。具体的，存储器202可包括高速随机存取的存储器，并且也可包括非易失性存储器，例如一个或多个磁盘存储设备、闪存设备或其他非易失性固态存储设备。存储器202可以存储操作系统(下述简称系统)，例如ANDROID，IOS，WINDOWS，或者LINUX等嵌入式操作系统。存储器202还可以存储网络通信程序，该网络通信程序可用于与一个或多个附加设备，一个或多个终端设备，一个或多个网络设备进行通信。存储器202还可以存储用户接口程序，该用户接口程序可以通过图形化的操作界面将应用程序的内容形象逼真的显示出来，并通过菜单、对话框以及按键等输入控件接收用户对应用程序的控制操作。
在本申请的一些实施例中，存储器202可用于存储本申请的一个或多个实施例提供的上行控制信息传输方法在终端200侧的实现程序。关于本申请的一个或多个实施例提供的上行控制信息传输方法的实现，请参考后续实施例。
终端处理器201可用于读取和执行计算机可读指令。具体的，终端处理器201可用于调用存储于存储器212中的程序，例如本申请的一个或多个实施例提供的上行控制信息传输方法在终端200侧的实现程序，并执行该程序包含的指令。
可以理解的，终端200可以是图3示出的无线通信系统100中的终端103，可实施为移动设备，移动台(mobile station)，移动单元(mobile unit)，无线单元，远程单元，用户代理，移动客户端等等。
需要说明的，图4所示的终端200仅仅是本申请实施例的一种实现方式，实际应用中， 终端200还可以包括更多或更少的部件，这里不作限制。
参考图5，图5示出了本申请的一些实施例提供的网络设备300。如图5所示，网络设备300可包括：一个或多个网络设备处理器301、存储器302、发射器305、接收器306、耦合器307和天线308。这些部件可通过总线304或者其他式连接，图5以通过总线连接为例。其中：
发射器305可用于对网络设备处理器301输出的信号进行发射处理，例如信号调制。接收器306可用于对天线308接收的移动通信信号进行接收处理。例如信号解调。在本申请的一些实施例中，发射器305和接收器306可看作一个无线调制解调器。在网络设备300中，发射器305和接收器306的数量均可以是一个或者多个。天线308可用于将传输线中的电磁能转换成自由空间中的电磁波，或者将自由空间中的电磁波转换成传输线中的电磁能。耦合器307可用于将移动通信号分成多路，分配给多个的接收器306。
存储器302与网络设备处理器301耦合，用于存储各种软件程序和/或多组指令。具体的，存储器302可包括高速随机存取的存储器，并且也可包括非易失性存储器，例如一个或多个磁盘存储设备、闪存设备或其他非易失性固态存储设备。存储器302可以存储操作系统(下述简称系统)，例如uCOS、VxWorks、RTLinux等嵌入式操作系统。存储器302还可以存储网络通信程序，该网络通信程序可用于与一个或多个附加设备，一个或多个终端设备，一个或多个网络设备进行通信。
网络设备处理器301可用于进行无线信道管理、实施呼叫和通信链路的建立和拆除，并为本控制区内的用户提供小区切换控制等。具体的，网络设备处理器301可包括：管理/通信模块(Administration Module/Communication Module，AM/CM)(用于话路交换和信息交换的中心)、基本模块(Basic Module，BM)(用于完成呼叫处理、信令处理、无线资源管理、无线链路的管理和电路维护功能)、码变换及子复用单元(Transcoder and SubMultiplexer，TCSM)(用于完成复用解复用及码变换功能)等等。
本申请实施例中，网络设备处理器301可用于读取和执行计算机可读指令。具体的，网络设备处理器301可用于调用存储于存储器302中的程序，例如本申请的一个或多个实施例提供的上行控制信息传输方法在网络设备300侧的实现程序，并执行该程序包含的指令。
可以理解的，网络设备300可以是图3示出的无线通信系统100中的基站101，可实施为基站收发台，无线收发器，一个基本服务集(BSS)，一个扩展服务集(ESS)，NodeB，eNodeB，接入点或TRP等等。
需要说明的，图5所示的网络设备300仅仅是本申请实施例的一种实现方式，实际应用中，网络设备300还可以包括更多或更少的部件，这里不作限制。
基于前述无线通信系统100、终端200以及网络设备300分别对应的实施例，本申请实施例提供了一种上行控制信息传输方法。下面详细介绍。
(一)本申请的主要设计思想可包括：终端可以根据接收到的第一DCI判断相应的UCI(即该DCI触发的UCI)是否需要保护，如果需要保护，则针对该UCI设计特殊传输策略， 为该UCI提供保护，确保URLLC业务的可靠性。
本申请中，该特殊传输策略可以在以下至少一个方面优于普通的UCI传输策略：传输资源、编码方式、比特流的级联顺序、发送顺序等。其中，在传输资源方面更优可以是指为URLLC UCI分配的资源更多。在编码方式方面更优可以是指URLLC UCI采用的编码方式比普通UCI采用的编码方式具有更高的纠错能力。在比特流的级联顺序方面更优可以是指URLLC UCI的比特流先于普通UCI的比特流被级联。在发送顺序方面更优可以是指URLLC UCI优先传输于普通UCI。后续内容会详细描述该特殊传输策略的具体实现，这里先不赘述。
本申请中，普通UCI可以包括但不限于eMBB UCI，普通UCI所响应的PDSCH的可靠性需求低于URLLC UCI所响应的PDSCH的可靠性需求。本申请中，可以将URLLC UCI称为第一UCI，可以将普通UCI称为第二UCI。这里，第一UCI还可以包括未来通信标准中定义的新业务类型的UCI，不限于URLLC业务。该新业务类型类似于URLLC业务类型，对可靠性有较高需求。
(二)为了保护第一UCI，本申请主要提供了下述几种方案。其中，方案1讨论在URLLC UCI和PUSCH复用资源的场景下，如何为URLLC UCI提供保护的方法。方案2-4讨论在URLLC UCI和eMBB UCI复用资源的场景下，如何为URLLC UCI提供保护的方法。
下面概述各个主要方案：
方案1：终端根据接收到的第一DCI判断该DCI是否满足第一条件，如果满足，则在第一UCI和PUSCH复用资源的前提下，在第一UCI和PUSCH复用的符号上发送第一UCI，而不发送PUSCH。也即是说，特殊考虑可靠性需求高的URLLC UCI，保证URLLC业务的可靠性。
关于方案1的具体实现可参考后续实施例一，这里先不赘述。
方案2：终端根据接收到的第一DCI判断该DCI是否满足第一条件，如果满足，则在第一UCI和第二UCI复用资源的前提下，先发送第一UCI，后发送第二UCI。即，承载第一UCI的结束时域符号早于承载第二UCI的起始时域符号。也即是说，确保可靠性需求高的URLLC UCI先发送，然后再发送eMBB UCI，保证URLLC业务的低时延。
关于方案2的具体实现可参考后续实施例二，这里先不赘述。
方案3：终端根据接收到的第一DCI判断该DCI是否满足第一条件，如果满足，则在第一UCI和第二UCI复用资源的前提下，第一UCI采用第一编码方式，第一编码方式在数据传输可靠性方面优于第二UCI采用的第二编码方式。也即是说，为URLLC UCI采用更优的编码方式，保证URLLC业务的高可靠性。
关于方案3的具体实现可参考后续实施例二，这里先不赘述。
(三)上述各个方案都涉及到如何判断DCI是否满足第一条件。如果判断出DCI满足第一条件，则可以确定对应于该DCI的UCI需要保护。
本申请中，针对终端接收到的第一DCI，第一条件可以包括但不限于：
(1)DCI格式是用于URLLC业务的DCI格式
本申请中，用于URLLC业务的DCI格式可以称为紧凑型DCI(compact DCI，又称为URLLC DCI)格式。
具体的，compact DCI格式可以通过但不限于以下至少一项来指示：DCI的净荷大小等于第一取值；或，DCI的净荷大小(payload size)等于第一取值，且DCI中的DCI格式标识(Identifier for DCI format)字段取值等于第二取值；或，DCI的净荷大小等于第一取值，且DCI的搜索空间为终端设备UE特定搜索空间；或，DCI的净荷大小等于第一取值，第一DCI的DCI格式标识字段的取值等于第二取值，且DCI的搜索空间为UE特定搜索空间；或，DCI的搜索空间为第一搜索空间；或，DCI的循环冗余校验CRC的校验比特长度等于第三取值；或，DCI的循环冗余校验CRC的校验比特长度等于第三取值；或，用于加扰DCI的CRC校验比特的无线网络临时标识RNTI等于第一RNTI；或，传输DCI的控制资源集合CORESET为第一CORESET。
其中，第一取值、第二取值、第三取值、第一搜索空间、第一CORESET这几项参数均可以是网络设备通过高层信令，如无线资源控制(radio resource control，RRC)信令、MAC CE信令，配置的。第一取值为compact DCI的净荷大小。第二取值为compact DCI中的DCI格式标识字段取值。第三取值为compact DCI的CRC的校验比特长度。第一搜索空间为用于检测compact DCI的搜索空间。第一CORESET为用于传输compact DCI的CORESET。
也即是说，可以通过高层信令配置compact DCI格式，compact DCI格式不同于普通DCI格式(如用于eMBB业务的DCI格式)。相比于普通DCI(如eMBBDCI)格式，compact DCI格式可以具备以下至少一项属性：第一取值小于普通DCI的净荷大小、第二取值不同于普通DCI中的DCI格式标识字段取值、第三取值大于普通DCI的CRC的校验比特长度。第一搜索空间不同于用于检测普通DCI的搜索空间。第一CORESET不同于用于传输普通DCI的CORESET。
这样，终端便可以根据payload size区分接收到的第一DCI是不是compact DCI，如果接收到的第一DCI的payload size等于第一取值，则可以确定该DCI是compact DCI，即满足第一条件。
这样，终端便可以结合payload size和Identifier for DCI format字段区分接收到的第一DCI是不是compact DCI，如果接收到的第一DCI的payload size等于第一取值且Identifier for DCI format字段取值等于第二取值，则可以确定该DCI是compact DCI，即满足第一条件。可选的，在接收到的多个DCI的payload size一致(payload alignment)的前提下，终端可以进一步结合Identifier for DCI format字段取值来区分出compact DCI。
这样，终端便可以根据CRC的校验比特长度区分接收到的第一DCI是不是compact DCI，如果接收到的第一DCI的CRC的校验比特长度等于第三取值，则可以确定该DCI是compact DCI，即满足第一条件。
这样，终端便可以根据检测到第一DCI的资源位置区分接收到的第一DCI是不是compact DCI，如果检测到第一DCI的资源位置为第一搜索空间，则可以确定第一DCI是compact DCI，即满足第一条件。
这样，终端便可以根据第一DCI占用的资源位置区分接收到的第一DCI是不是compact DCI，如果第一DCI占用的资源位置为第一CORESET，则可以确定第一DCI是compact DCI，即满足第一条件。
(2)用于加扰DCI的CRC校验比特的无线网络临时标识(radio network temporary identifier，RNTI)等于第一RNTI
具体的，第一RNTI可以是网络设备通过高层信令，如RRC信令、MAC CE信令，配置的。第一RNTI用于加扰compact DCI的CRC校验比特。也即是说，可以通过高层信令配置用于加扰compact DCI的CRC校验比特的RNTI。这样，终端便可以根据加扰DCI的CRC校验比特的RNTI区分接收到的第一DCI是否是compact DCI。
(3)DCI的搜索空间(search space)为第一搜索空间
具体的，第一搜索空间可以是网络设备通过高层信令，如RRC信令、MAC CE信令，配置的。在第一搜索空间上检测到的DCI即compact DCI。也即是说，可以通过高层信令配置search space的属性(是否是URLLC的search space)。这样，终端便可以根据检测DCI的search space的属性来区分该DCI是否是compact DCI。
(4)DCI的控制资源集合(CORESET)为第一CORESET
具体的，第一CORESET可以是网络设备通过高层信令，如RRC信令、MAC CE信令，配置的。第一CORESET用于发送compact DCI。也即是说，可以通过高层信令配置CORESET的属性(是否是URLLC的CORESET)。这样，终端便可以根据接收DCI的CORESET的属性来区分该DCI是否是compact DCI。
下面介绍控制资源集合这一概念。如图6所示，一个CORESET是控制区域内的一块时频资源。图6中以14个时域符号的前4个时域符号为控制区域，但可以只定义前4个时域符号中一部分资源为某一个CORESET所对应的资源。一个CORESET对应一组用户(如UE1，UE2，UE3等)。在这个CORESET上会发送这一组用户的物理下行控制信道(PDCCH)。每个用户在一个CORESET上有一个搜索空间(search space)，该search space的资源小于等于CORESET的资源。一个用户可以对应多个CORESET，这些CORESET关联的Numerology可以相同或不同，这里的numerology可包括子载波间隔和循环前缀(cyclic prefix，CP)长度。
除了上述几种方式，终端还可以通过下述方式来判断DCI是否满足第一条件。
可选的，终端可以通过校验的步骤来判断DCI是否是compact DCI。当DCI需要采用两步或两步以上的校验方式时，则终端可以确定该DCI是compact DCI，即该DCI满足第一条件。
可选的，终端可以判断DCI中是否有用于降低错误概率概率的字段，如果有该字段，则可以确定该DCI是compact DCI，即该DCI满足第一条件。
可选的，终端可以根据DCI采用的编码方式来判断DCI是否是compact DCI。当DCI采用的编码方式是特定编码方式时，则终端可以确定该DCI是compact DCI，即该DCI满足第一条件。该特定编码方式是低密度奇偶校验(low-density parity check,LDPC)或极化(polar)编码或者Reed-Muller编码或双Reed-Muller编码中的一种。
上述判断DCI是否满足第一条件的实现方式属于隐式判断相应UCI是否需要保护的方式。另外，还可以采用显式方式来判断对应于该DCI的UCI是否需要保护。具体方案可如下：DCI可以携带1比特的字段，用于区分对应于该DCI的UCI是否需要被保护。
例如，如表1所示，当该比特取值为“0”时，表示对应于该DCI的UCI不需要被保护； 当该比特取值为“1”时，表示对应于该DCI的UCI需要被保护。下面这个映射关系可以是由协议预定义的，也可以是由RRC信令半静态配置的。
比特信息 UCI类型
0 普通UCI
1 需要被保护的UCI
表1
DCI是否包含1比特的字段可以通过协议预定义，也可以通过RRC信令配置。表1示例性示出的映射关系可以是通过协议预定义，也可以通过RRC信令配置。
本申请中，第一DCI可能是compact DCI/URLLC DCI(即满足第一条件的DCI)，也可能是普通DCI(如eMBB DCI)。可以理解的，满足第一条件的第一DCI调度的PDSCH(如URLLC PDSCH)的可靠性需求高于普通DCI调度的PDSCH(如eMBB PDSCH)的可靠性需求。本申请为compact DCI/URLLC DCI对应的UCI(即由该DCI调触发的UCI)提供特殊保护，这样可以确保URLLC业务的高可靠性。
需要说明的，本申请涉及的资源概念，如符号(symbol)、资源单元(resource element，RE)、资源块(resource block，RB)、CORESET、search space等，以及本申请设计的信道概念，如PDSCH、PDCCH等，可以参考现有定义(如LTE标准、NR通信系统中的已有规定)，但是不限于现有定义，未来通信标准中关于这些资源概念和这些信道概念的定义或称呼可能不同，不影响本申请的实施。
下面结合附图通过多个实施例详细介绍本申请提供的技术方案。
(一)实施例一
本实施例中，在第一UCI和PUSCH复用资源的场景下，终端可以判断接收到的第一DCI是否满足第一条件，如果满足第一条件，则终端可以在第一UCI和PUSCH复用的符号上发送第一UCI，而不发送PUSCH。本实施例将主要讨论前述方案1。下面结合图7详细说明。
图7是本申请提供的一种上行控制信息传输方法的流程示意图。下面展开如下：
S101，网络设备向终端发送第一DCI。相应的，终端接收到网络设备发送的第一DCI。
S102，终端向网络设备发送第一UCI，第一UCI由第一DCI触发。其中，在第一UCI和PUSCH是否复用时域资源，且第一条件被满足的条件下，第一符号上承载第一UCI而不承载PUSCH。第一符号为第一UCI和PUSCH复用的时域符号。
本申请中，可以将用于传输第一UCI的时域资源称为第一时域资源。第一符号具体可以为第一时域资源和PUSCH的时域资源重叠的时域符号。也即是说，在第一时域资源与PUSCH的时域资源部分或全部重叠，且第一条件被满足的条件下，第一符号上承载有第一UCI，而没有承载PUSCH。
本实施例中，关于如何判断第一条件是否被满足，具体可参考前述内容，这里不再赘述。在判断出第一条件是否被满足后，终端可以为第一UCI提供特殊保护。下面详细描述。
(1)为第一UCI提供保护的前提
第一种前提，用于传输第一UCI的资源和用于传输PUSCH的资源在时域上部分或全部重叠。
第二种前提，用于传输第一UCI的资源和用于传输PUSCH的资源在时域上部分或全部重叠，且在频域上部分或全部重叠。
第三种前提，用于传输第一UCI的资源和用于传输PUSCH的资源，且在频域上不重叠，但是终端没有上行同时发送多业务的能力，例如功率受限或者是采用上行单载波传输方式。
综合上述三种前提可以看出，为第一UCI提供保护的基本前提为：第一时域资源和PUSCH的时域资源部分或全部重叠，即第一UCI和PUSCH复用时域资源。其中，第一种前提表示，在第一时域资源和PUSCH的时域资源部分或全部重叠的条件下，如果第一条件是否被满足，则终端可以为第一UCI提供特殊保护，即执行S103。第二种前提表示，在第一UCI和PUSCH复用时频资源的条件下，如果第一条件是否被满足，则终端可以为第一UCI提供特殊保护，即执行S103。第三种前提表示，在第一UCI和PUSCH仅仅复用时域资源(不复用频域资源)，且终端不具备上行同时发送多业务的能力的条件下，如果第一UCI满足第一条件，则终端可以为第一UCI提供特殊保护，即执行S103。
(2)第一符号(第一UCI和PUSCH复用的时域资源)
举例说明，如图8所示，符号7、8、11用于传输URLLC UCI，符号7-14用于传输PUSCH。其中，符号7、8、11和符号7-14中相重叠的符号为：符号7、8、11，符号7、8、11即第一符号。
具体的，在第一符号上，第一UCI和PUSCH的频域资源复用情况可以包括以下几种：
第1种情况：第一UCI和PUSCH在第一符号上各自占用的频域资源完全不重叠，即第一UCI和PUSCH在第一符号上各自占用完全不同的频域资源。例如，参考图8，当第一符号为符号7时，第一UCI和PUSCH各自占用的频域资源完全不重叠。
第2种情况：第一UCI和PUSCH在第一符号上各自占用的频域资源部分重叠，即第一UCI和PUSCH在第一符号上各自占用的频域资源中有部分频域资源是相同的。例如，参考图8，当第一符号为符号8时，第一UCI和PUSCH各自占用的频域资源部分重叠。
第3种情况：第一UCI和PUSCH在第一符号上各自占用的频域资源完全重叠，即第一UCI和PUSCH在第一符号上各自占用的频域资源完全相同。例如，参考图8，当第一符号为符号11时，第一UCI和PUSCH各自占用的频域资源完全重叠。
(3)第一符号上承载第一UCI而不承载PUSCH
具体的，终端可以为第一UCI打孔(puncture)第一符号上的所有RB，即第一符号仅用于传输第一UCI而不传输PUSCH。
举例说明，如图9所示，符号7、8、11用于传输URLLC UCI，符号7-14用于传输PUSCH。其中，符号7、8、11和符号7-14中相重叠的符号为：符号7、8、11，符号7、8、11即第一符号。为了特殊保护第一UCI，终端可以打孔(puncture)符号7、8、11上的所有RB。这样，可实现为第一UCI分配更多资源，保证URLLC业务的高可靠性。
可选的，终端还可以设置第一符号上的PUSCH的发射功率为0，即将第一符号上的发射功率都集中用于发射第一UCI。这样可以大大提高第一UCI的发射功率，提高URLLC 业务的可靠性。
可以看出，既可以从资源数量方面为第一UCI提供保护，即为第一UCI配置更多资源，也可以从发射功率方面为第一UCI提供保护，即为第一UCI提供更高的发射功率。这两种方式都可以提高URLLC UCI的传输可靠性，从而保证URLLC业务的高可靠性。
实施例一的相关扩展
1.除了打孔(puncture)第一符号上的所有RB，在一些可选实施例中，还可以通过下述方式来为第一UCI配置更多资源。
具体的，网络设备可以预定义第一UCI在第一符号上打孔PUSCH的频域资源数量。可选的，网络设备可以配置多个选项，例如，假设PUSCH调度的频域资源大小为10个RB。网络设备配置了2个选项：打孔2个RB和打孔5个RB。可选的，网络设备可以通过RRC信令通知终端采用哪个选项。这样，终端便可以根据网络设备的配置在第一符号上打孔PUSCH的频域资源，可实现为第一UCI配置更多资源。
具体的，终端设备最终映射的物理资源数量可以是预定义的或者网络设备配置的第一UCI在第一符号上打孔PUSCH的资源数量，也可以是第一UCI实际需要的资源数量，也可以是PUCCH占据的资源数量，还可以是第一UCI实际需要的资源数量和PUCCH占据的资源数量中的最小值。
2.除了设置第一符号上的PUSCH的发射功率为0，在一些可选实施例中，还可以通过下述方式来提高第一UCI的发射功率。
具体的，可以预定义第一UCI的发射功率。可选的，可以将第一UCI的发射功率预定义为预设的功率值。可选的，可以将第一UCI的发射功率预定义为终端的最大发射功率。可选的，可以预定义第一UCI的功率提升倍数。这样，也可以为第一UCI提供更高的发射功率，确保第一UCI的高可靠性。可选的，可以将第一UCI的发射功率与相邻符号上的PUSCH的发射功率保持一致，以图10为例，相邻符号是指与第一符号相邻的用于发送PUSCH的时域符号。这里的预定义可以是系统或者协议预定义。
3.第一UCI之后的PUSCH的发送策略
具体的，如图10所示，为了降低终端和网络设备的通信复杂度，终端可以在发送第一UCI之后，停止发送第一UCI之后的PUSCH的剩余部分。具体的停止发送PUSCH的策略可如下：
可选的，网络设备可以配置是否继续传输PUSCH的剩余部分。
可选的，如果PUSCH的剩余部分的数据量大于第一阈值，则终端继续传输PUSCH的剩余部分，否则，停止传输PUSCH的剩余部分。第一阈值可以是协议预定义的，也可以是网络设备预定义的，还可以是网络设备根据终端上报的发送能力后动态配置的。
4.第一UCI携带在(piggyback)PUSCH中传输
不同于现有的UCI在时频资源上紧靠PUSCH DMRS(如图11A所示)以提高信道估计性能。对于PUSCH DMRS之后发送的第一UCI，如图11B所示，可以根据第一UCI的时序要求将第一UCIpiggyback到PUSCH物理资源上。
这里，第一UCI的时序要求是指针对接收到的PDSCH，终端需要按照要求在PDSCH 的反馈时刻发送第一UCI，满足第一UCI的时延要求。
5.针对第一UCI携带在PUSCH中传输的情况，为第一UCI配置更多资源
针对第一UCI携带在PUSCH中传输的情况，终端可以采用协议为第一UCI预定义的beta offset字段取值，或者RRC信令为第一UCI配置的beta offset字段取值。终端还可以采用预定义的所有beta offset字段取值中最大的beta offset字段取值。这样，可以保证为第一UCI分配更多资源，保证第一UCI的可靠传输。
6.ACK/NACK、RI、CQI/PMI的传输优先级
对于ACK/NACK、RI、CQI/PMI这几种类型的第一UCI，ACK/NACK的时延要求最高，CQI/PMI需要通过RI确定。因此，三者的传输优先级为：ACK/NACK>RI>CQI/PMI。这里，大于号表示优先级更高。
7.第一UCI和PUSCH的DMRS存在资源冲突
可选的，如果PUSCH的DMRS是CP-OFDM对应的梳状DMRS，则URLLC ACK/NACK和PUSCH的DMRS可以复用时域资源，即可以在相同的符号上被发送。
可选的，如果PUSCH的DMRS是DFT-S-OFDM波形的DMRS，则URLLC ACK/NACK可以跳过用于传输PUSCH的DMRS的符号。
可选的，如果PUSCH的DMRS是DFT-S-OFDM波形的DMRS，且URLLC ACK/NACK的比特长度为1-2比特，则URLLC ACK/NACK可以映射在用于传输PUSCH的DMRS的资源上。因为，1-2比特的URLLC ACK/NACK序列不会影响信道估计，网络侧可以盲检出这个序列，然后做信道估计。
8.第一UCI在PUSCH中映射到的频域资源
假设，PUSCH占用的频域资源/物理资源块(physical resource block，PRB)/虚拟资源块(Virtual Resource block，VRB)是m 0、m 1、…、m k-1。则：
可选的，第一UCI的起始RB可以是：m 0或m k-1。
可选的，第一UCI的起始RB也可以是：
Figure PCTCN2018124794-appb-000001
或者
Figure PCTCN2018124794-appb-000002
或者
Figure PCTCN2018124794-appb-000003
或者
Figure PCTCN2018124794-appb-000004
可选的，如果第一UCI的RB数目是n，则第一UCI的其实RB也可以是
Figure PCTCN2018124794-appb-000005
或者
Figure PCTCN2018124794-appb-000006
可以理解的，用于处理发送信号的滤波器边缘(即滤波器带宽的两端频率附近)的信号质量会出现损失，通过将第一UCI的起始RB设置在PUSCH的中间频域位置，可降低对滤波器对UCI性能的影响。同时，将第一UCI的起始RB设置在PUSCH的中间频域位置可以降低邻居频域对UCI的干扰。
可选的，第一UCI在PUSCH中映射到的频域资源可以是一段连续的频域资源块。
9.第一UCI采用的numerology
可选的，当URLLC UCI的时序要求能够满足时，第一UCI的子载波间隔(subcarrier spacing，SCS)可以采用PUSCH的子载波间隔。这样可以减少第一UCI和PUSCH之间的频域干扰。可选的，第一UCI还可以进一步采用较长的循环前缀(cyclic prefix，CP)，以进一步减少频域干扰。
可选的，当URLLC UCI的时序要求不能满足时，第一UCI的子载波间隔(SCS)可 以采用URLLC PUCCH的子载波间隔，以降低时延。
这里，URLLC UCI的时序要求是指针对接收到的PDSCH，终端需要按照要求在PDSCH的反馈时刻发送URLLC UCI，满足第一UCI的时延要求。
(二)实施例二
本实施例中，在第一UCI和第二UCI复用资源的场景下，终端可以判断接收到的第一DCI是否满足第一条件，如果满足第一条件，则终端可以为第一UCI提供更多的保护，具体可以优先传输第一UCI，也可以为第一UCI设置可靠性更高的编码方式等等。本实施例将主要讨论前述方案2-3。下面结合图12详细说明。
图12是本申请提供的另一种上行控制信息传输方法的流程示意图。下面展开如下：
S201，网络设备向终端发送第一DCI。相应的，终端接收到网络设备发送的第一DCI。
S202，终端向网络设备发送第一UCI，第一UCI由第一DCI触发。其中，在第一UCI和第二UCI复用时域资源，且第一条件被满足的条件下，可以在以下至少一方面为第一UCI提供保护：发送顺序、编码方式，其中，第一UCI优先第二UCI被发送，第一UCI采用的第一编码方式在数据传输可靠性方面优于第二UCI采用的第二编码方式。
本申请中，可以将用于传输第一UCI的时域资源称为第一时域资源，可以将用于传输第二UCI的时域资源称为第二时域资源。这里，第一UCI和第二UCI复用时域资源是指第一时域资源和第二时域资源部分或全部重叠。这里，第一UCI优先第二UCI被发送是指承载所述第一UCI的结束时域符号早于承载第二UCI的起始时域符号。
本实施例中，关于如何判断终端接收到的第一DCI是否满足第一条件，具体可参考前述内容，这里不再赘述。在判断出终端接收到的第一DCI满足第一条件后，终端可以为对应于该DCI的UCI(即第一UCI)提供特殊保护。下面详细描述。
(1)为第一UCI提供保护的前提
第一种前提，用于传输第一UCI的资源和用于传输第二UCI的资源在时域上部分或全部重叠。
第二种前提，用于传输第一UCI的资源和用于传输第二UCI的资源在时域上部分或全部重叠，且在频域上部分或全部重叠。
第三种前提，用于传输第一UCI的资源和用于传输第二UCI的资源在时域上部分或全部重叠，且在频域上不重叠，但是终端没有上行同时发送多业务的能力，例如功率受限或者是采用上行单载波传输方式。
综合上述三种前提可以看出，为第一UCI提供保护的基本前提为：第一时域资源和第二时域资源部分或全部重叠，即第一UCI和第二UCI复用时域资源。其中，第一种前提表示，在第一UCI和第二UCI复用时域资源的条件下，如果第一UCI满足第一条件，则终端可以为第一UCI提供特殊保护，即执行S203。第二种前提表示，在第一UCI和第二UCI在复用时频资源的条件下，如果第一UCI满足第一条件，则终端可以为第一UCI提供特殊保护，即执行S203。第三种前提表示，在第一UCI和第二UCI仅仅复用时域资源(不复用频域资源)，且终端不具备上行同时发送多业务的能力的条件下，如果第一UCI满足第一条件，则终端可以为第一UCI提供特殊保护，即执行S203。
(2)承载所述第一UCI的结束时域符号早于承载第二UCI的起始时域符号
具体的，在第一时域资源和第二时域资源部分或全部重叠时，承载所述第一UCI的结束时域符号早于承载第二UCI的起始时域符号，即第二UCI可以被延迟发送，先发送第一UCI，后发送第二UCI。这样，确保可靠性需求高的第一UCI先发送，然后再发送第二UCI，保证URLLC业务的可靠性。
例如，如图14A所示，用于传输第一UCI的符号为符号1，用于传输第二UCI的符号也为符号1，第二UCI可以被延迟到符号2上发送。即承载第一UCI的结束时域符号(即符号1)早于承载第二UCI的起始时域符号(即符号2)。
又例如，如图14B所示，用于传输第一UCI的符号为符号1-2，用于传输第二UCI的符号也为符号2-3，第二UCI可以被延迟到符号3-4上发送。即承载第一UCI的结束时域符号(即符号2)早于承载第二UCI的起始时域符号(即符号3)。
示例仅仅用于解释本申请是，不应构成限定。
进一步的，终端可以对被延迟发送的第二UCI做HARQ-ACK bits bundling，这样可以减少第二UCI的反馈时延。
可选的，终端具体可以根据第二UCI被延迟发送所对应的符号资源确定是否对延迟的第二UCI做HARQ-ACK bits bundling，如果该符号资源比较紧张，不足以通过HARQ-ACK bits multiplexing方式传输第二UCI，则可以确定对被延迟发送的第二UCI做HARQ-ACK bits bundling。
(3)第一UCI采用第一编码方式
具体的，第一UCI采用的第一编码方式在数据传输可靠性方面优于第二UCI采用的第二编码方式。第一编码方式不同于第二编码方式，二者的区别可以体现在但不限于：第一编码方式可以增加第一UCI编码后的比特数，和/或第二编码方式减少第二UCI编码后的比特数。具体的：
1.不同的冗余度
第一编码方式可包括：对所述第一UCI进行冗余编码。即终端可以先对第一UCI的信源加冗余然后编码，也可以先编码然后对编码后的第一UCI进行比特加冗余。
这样，可增加第一UCI编码后的比特数，使得第一UCI比第二UCI具有更高的纠错能力，保证URLLC业务的高可靠性。
例如，图15A示出了连续反馈的4比特，其中，第1、2、4个比特是第二UCI，第3个比特是第一UCI。对第一UCI做重复编码，第一UCI的序列长度从1比特增加至3比特，冗余度增加，可靠性也增高。示例仅仅用于解释本申请，不应构成限定。
第二编码方式可包括：对第二UCI进行HARQ-ACK比特绑定。这样可减少第二UCI编码后的比特数。
可选的，可以对所述第一UCI进行冗余编码，且对第二UCI做HARQ-ACK比特bundling，这样不仅可以提高第一UCI的传输可靠性，还可以减少共同反馈第一UCI和第二UCI所需的资源。例如，如图15B所示，通过HARQ-ACK bits bundling，第二UCI的序列长度从3比特缩短至1比特，即使第一UCI进行冗余处理后增加至3比特，第一UCI和第二UCI共同反馈的数据长度仍不变。第二UCI的HARQ-ACK比特bundling可以是不同 CBG(code block group)对应的HARQ-ACK比特做bundling，或者是不同TB(Transport block)对应的HARQ-ACK比特做bundling，或者是不同component carrier或者bandwidth part对应的HARQ-ACK比特做bundling。
2.不同的码距
在一种实现方式中，可以通过编码的设置来保证URLLC的高可靠性。
以URLLC ACK/NACK和eMBB ACK/NACK为例，假设终端当前需要反馈URLLC ACK/NACK和eMBB ACK/NACK，共2比特，第一个比特是URLLC ACK/NACK，第二个比特是eMBB ACK/NACK。这2个比特有四种状态：“00”、“01”、“10”、“11”。其中，“0”代表NACK，“1”代表“ACK”。为了保证URLLC的高可靠性，需要减小第一个比特的“0”被错检成“1”或者“1”被错检成“0”的概率。具体的，终端可以为“00”和“10”，“00”和“11”，“01”和“11”，“01”和“10”设置更大的码距。而eMBB的可靠性要求不高，因此可以为00和01,10和11设置小的码距。
如图16A所示，可以对“00”、“01”、“10”和“11”进行编码。编码后，“00”变成了“00000000”，“01”变成了“00000001”，“10”变成了“11111110”和“11”变成了“11111111”。也即是说，“00”和“10”的码距为7，“00”和“11”的码距为8，“01”和“11”的码距为7，“01”和“10”的码距为7。可以理解的，对于码距为7的“00000000”和“11111110”。URLLC ACK和URLLC NACK不容易被混淆。这样，即使前面7个比特中有一个或一些比特在传输过程中发生翻转，也不影响接收端正确判断URLLC UCI是ACK还是NACK，可以更好地保证URLLC的可靠性。
在另一种实现方式中，对应到星座图的映射。星座图上的距离越长，可靠性越高。
例如，如图16B所示，针对上述示例中的2比特的URLLC ACK/NACK和eMBB ACK/NACK，可以扩大“00”在星座图上的映射位置与“10”在星座图上的映射位置之间的距离，“00”在星座图上的映射位置与“11”在星座图上的映射位置之间的距离，“01”在星座图上的映射位置与“10”在星座图上的映射位置之间的距离，“01”在星座图上的映射位置与“11”在星座图上的映射位置之间的距离。
可以理解的，通过区别设置码距可以减少第一UCI被错检的概率，可实现第一UCI比第二UCI具有更高的纠错能力，保证URLLC业务的高可靠性。
实施例二的相关扩展
除了上述(2)-(3)，在一些可选实施例中，终端可还可以通过下述方式为第一UCI提供更多的保护：
1.为第一UCI配置更多资源
具体的，终端可以采用协议为第一UCI预定义的beta offset字段取值，或者RRC信令为第一UCI配置的beta offset字段取值。终端还可以采用预定义的所有beta offset字段取值中最大的beta offset字段取值。这样，可以保证为第一UCI分配更多资源，保证第一UCI的可靠传输。
上述方式对前述图3所示的情况同样适用。如图17所示，对于突发出现在UL grant之后的URLLC业务，虽然URLLC UCI占用的RE个数并没有在发送UL grant的DCI(具 体为DCI中的beta offset)中进行指示，但是，终端可以采用协议为URLLC UCI预定义的beta offset字段取值，可以保证URLLC UCI获得更多资源，更好的保证了URLLC的高可靠性。
上述方式还可以适用URLLC UCI单独发送的场景，图17中URLLC UCI便是单独传输的，和eMBB UCI没有复用时域资源。
2.不同的码率
具体的，第一UCI的码率低于第二UCI的码率。终端可以采用协议预定义的或者RRC信令配置的针对第一UCI的码率，以更好的保证第一UCI的低码率，确保URLLC业务的高可靠性。
3.为第一UCI配置更高的发射功率
具体的，网络设备可以预定义第一UCI的发射功率。可选的，网络设备可以将第一UCI的发射功率预定义为预设的功率值。可选的，网络设备可以将第一UCI的发射功率预定义为终端的最大发射功率。可选的，网络设备可以预定义第一UCI的功率提升倍数。
举例说明，如图18所示，符号2-4即第一符号。其中，URLLC ACK/NACK和eMBB PUCCH复用符号2，URLLC RI和eMBB PUCCH复用符号3，URLLC CQI/PMI和eMBB PUCCH复用符号4。网络设备可以配置符号2-4上的第一UCI(ACK/NACK、RI、CQI/PMI)的发射功率为预设功率值，也可以配置符号2-4上的第一UCI的功率提升倍数(即第一UCI的发射功率增加，eMBB PUCCH的发射功率降低)。极端的做法，可以配置eMBB PUCCH的发射功率为0，即将符号2-4上的全部功率都用来发射第一UCI。这样，可以为第一UCI提供更高的发射功率，确保URLLC UCI的高可靠性。
另外，本申请还提了一种上行控制信息传输方法。不同于前述实施例中描述的通过终端接收到的第一DCI隐式或显式的判断对应于该第一DCI的UCI(即第一DCI触发的UCI)需要保护，本实施例中终端可以根据UCI自己的特性来判断该UCI的传输是否需要特殊保护。本实施例不局限于URLLC UCI或eMBB UCI。
本实例提供了以下两种判断方式。
判断方式1，通过终端是否处于协作集内来判断该终端当前发送的UCI是否需要特殊保护，如果该终端处于协作集内，则确定该UCI需要特殊保护。
可以理解的，为了进一步辅助下行协作发送的性能，确保各个传输点(transmission receptionpoint，TRP)都能收到终端发送的UCI，需要对该UCI提供特殊保护。关于如何为该UCI提供保护，可以参考前述实施例中描述的为第一UCI提供保护的方案，这里不再赘述。
判断方式2，根据PUCCH的符号数或SCS判断是否需要对终端当前发送的UCI提供特殊保护，如果PUCCH的符号数较少或SCS较大，则确定该UCI需要特殊保护。
可以理解的，较少的符号数或者较大的SCS会降低PUCCH的覆盖性能，为了保证UCI的可靠传输，需要对UCI提供特殊保护。关于如何为该UCI提供保护，可以参考前述实施例中描述的为第一UCI提供保护的方案，这里不再赘述。
具体的，当PUCCH的符号数少于第一阈值时，可以确定需要对UCI的传输提供特殊 保护；当SCS大于第二阈值时，可以确定需要对UCI的传输提供特殊保护。第一阈值或第二阈值可以是协议预定义的或者RRC信令配置的。
可以理解的，以上方案可以扩展到载波聚合的场景，即对于不同载波CC或者Bandwidth part上对应的HARQ-ACK比特或者SR或者CSI的反馈同样适用。
另外，本申请还提了一种用来判断SR是否需要保护的方法。具体可包括但不限于下述两种方式：
方式1：通过RRC信令配置或者协议预定义哪些业务时URLLC业务。终端的MAC层在下发SR时会在SR上附加标签或者属性，标识该SR是否是需要特殊保护的URLLC SR。
在方式1中，网络设备配置或者协议预定义某些业务(用逻辑信道或者QCI(QoS class identifier)表示)是URLLC业务。终端的MAC层在收到URLLC上行数据从而生成SR时会指示终端的物理层该SR是URLLC SR。
方式2：通过RRC配置多套SR配置(配置可包括时域资源、频域资源或者时频资源等)，其中某一(或某些)套配置是用于传输URLLC SR。终端的MAC层下发SR时会制定属于哪套配置的SR。
在方式2中，网络设备配置多套SR配置，其中某一(或某些)套配置是用于传输URLLC SR。终端的MAC层在给终端的物理层下发URLLC SR时，采用URLLC SR对应的SR配置。
结合方式1或方式2，在判断出SR需要保护之后，可以根据前述实施例中提供的方案来为SR提供特殊保护，这里不再赘述。
参见图19，图19示出了本申请提供一种无线通信系统及相关通信装置。无线通信系统10包括：终端400和网络设备500。无线通信系统10可以是图1所示的无线通信系统100。其中，终端400可以是图2所示的无线通信系统100中的终端设备103。网络设备500可以是图2所示的无线通信系统100中的网络设备101。下面分别描述终端400和网络设备500各自包含的功能单元。
如图19所示，终端400可包括：接收单元401和发送单元403。其中：
接收单元401可用于接收第一DCI。
发送单元403可用于发送第一UCI，第一UCI由第一DCI触发。
可选的，上述接收单元401对应的实体硬件可以为接收器；上述发送单元403对应的实体硬件可以为发送器。终端400还可以包括：存储器，用于存储处理器执行的程序和/或数据。
如图19所示，网络设备500可包括：发送单元501和接收单元503。其中：
发送单元501可用于发送第一DCI。
接收单元503可用于接收第一UCI，第一UCI由第一DCI触发。
可选的，上述接收单元502对应的实体硬件可以为接收器；上述发送单元501对应的实体硬件可以为发送器。网络设备500还可以包括：存储器，用于存储处理器执行的程序和/或数据。
在一些可选实施例中，在第一时域资源与上行数据信道的时域资源部分或全部重叠，且第一条件被满足的条件下，第一符号上承载有第一UCI，而没有承载上行数据信道。第一符号为第一时域资源和上行数据信道的时域资源重叠的时域符号。第一时域资源用于传输第一UCI。具体可参考图7实施例，这里不再赘述。
在一些可选实施例中，在第一时域资源与第二时域资源部分或全部重叠，且第一条件被满足的条件下，承载第一UCI的结束时域符号早于承载第二UCI的起始时域符号。第一时域资源用于传输第一UCI，第二时域资源用于传输第二UCI。具体可参考图12实施例，这里不再赘述。
在一些可选实施例中，在第一时域资源与第二时域资源部分或全部重叠，且第一条件被满足的条件下，第一UCI采用的第一编码方式在数据传输可靠性方面优于第二UCI采用的第二编码方式。第一时域资源用于传输第一UCI，第二时域资源用于传输第二UCI。具体可参考图12实施例，这里不再赘述。
可以理解的，关于终端400包括的各个功能单元的具体实现以及网络设备500包括的各个功能单元的具体实现，可以参考图7或图12实施例，这里不再赘述。
可以理解的是，当本申请的实施例应用于网络设备芯片时，该网络设备芯片实现上述方法实施例中网络设备的功能。该网络设备芯片向网络设备中的其它模块(如射频模块或天线)发送上述第一DCI或者接收来自网络设备中的其它模块(如射频模块或天线)的第一UCI。该第一DCI经由网络设备的其它模块发送给终端。该第一UCI是终端发送给网络设备的。
当本申请的实施例应用于终端备芯片时，该终端芯片实现上述方法实施例中终端的功能。该终端芯片从终端中的其它模块(如射频模块或天线)接收上述第一DCI或者通过终端中的其它模块(如射频模块或天线)发送上述第一UCI。该第一UCI经由终端的其它模块发送给网络设备。该第一DCI是网络设备发送给终端的。
综上，实施本申请提供的技术方案，可以在传输资源、编码方式、发送顺序等方面为URLLC UCI提供特殊保护，可更好的保证URLLC业务的高可靠性。
本领域普通技术人员可以理解实现上述实施例方法中的全部或部分流程，该流程可以由计算机程序来指令相关的硬件完成，该程序可存储于计算机可读取存储介质中，该程序在执行时，可包括如上述各方法实施例的流程。而前述的存储介质包括：ROM或随机存储记忆体RAM、磁碟或者光盘等各种可存储程序代码的介质。

Claims (23)

  1. 一种上行控制信息传输方法，其特征在于，包括：
    接收第一下行控制信息DCI；
    发送第一上行控制信息UCI，所述第一UCI由所述第一DCI触发；在第一时域资源与上行数据信道PUSCH的时域资源部分或全部重叠，且第一条件被满足的条件下，第一符号上承载有所述第一UCI，而没有承载所述PUSCH，所述第一符号为所述第一时域资源和所述PUSCH的时域资源重叠的时域符号；所述第一时域资源用于传输所述第一UCI。
  2. 一种上行控制信息传输方法，其特征在于，包括：
    接收第一DCI；
    发送第一UCI，所述第一UCI由所述第一DCI触发；在第一时域资源与第二时域资源部分或全部重叠，且第一条件被满足的条件下，承载所述第一UCI的结束时域符号早于承载第二UCI的起始时域符号；所述第一时域资源用于传输所述第一UCI，所述第二时域资源用于传输所述第二UCI。
  3. 一种上行控制信息传输方法，其特征在于，包括：
    接收第一DCI；
    发送第一UCI，所述第一UCI由所述第一DCI触发；在第一时域资源与第二时域资源部分或全部重叠，且第一条件被满足的条件下，所述第一UCI采用的第一编码方式在数据传输可靠性方面优于第二UCI采用的第二编码方式；所述第一时域资源用于传输所述第一UCI，所述第二时域资源用于传输所述第二UCI。
  4. 一种上行控制信息传输方法，其特征在于，包括：
    发送第一DCI；
    接收第一UCI，所述第一UCI是由所述第一DCI触发；在第一时域资源与上行数据信道的时域资源部分或全部重叠，且第一条件被满足的条件下，第一符号上承载有所述第一UCI，而没有承载上行数据信道，所述第一符号为所述第一时域资源和所述上行数据信道的时域资源重叠的时域符号；第一时域资源用于传输所述第一UCI。
  5. 一种上行控制信息传输方法，其特征在于，包括：
    发送第一DCI；
    接收第一UCI，所述第一UCI是由所述第一DCI触发；在第一时域资源与第二时域资源部分或全部重叠，且第一条件被满足的条件下，承载所述第一UCI的结束时域符号早于承载第二UCI的起始时域符号；所述第一时域资源用于传输所述第一UCI，所述第二时域资源用于传输所述第二UCI。
  6. 一种上行控制信息传输方法，其特征在于，包括：
    发送第一DCI；
    接收第一UCI，所述第一UCI是由所述第一DCI触发；在第一时域资源与第二时域资源部分或全部重叠，且第一条件被满足的条件下，所述第一UCI采用的第一编码方式在数据传输可靠性方面优于第二UCI采用的第二编码方式；所述第一时域资源用于传输所述第一UCI，所述第二时域资源用于传输所述第二UCI。
  7. 如权利要求1-6中任一项所述的方法，其特征在于，所述第一编码方式增加所述第一UCI编码后的比特数，和/或所述第二编码方式减少第二UCI编码后的比特数。
  8. 如权利要求7所述的方法，其特征在于，所述第一编码方式包括：对所述第一UCI进行冗余编码；和/或，所述第二编码方式包括：对所述第二UCI进行HARQ-ACK比特绑定。
  9. 如权利要求1-8中任一项所述的方法，其特征在于，所述第一条件，具体包括：
    所述第一DCI的净荷大小等于第一取值；或，
    所述第一DCI的净荷大小等于所述第一取值，且所述第一DCI中的DCI格式标识字段取值等于第二取值；或，
    所述第一DCI的净荷大小等于所述第一取值，且所述第一DCI的搜索空间为终端设备UE特定搜索空间；或，
    所述第一DCI的净荷大小等于所述第一取值，所述第一DCI的DCI格式标识字段的取值等于所述第二取值，且所述第一DCI的搜索空间为所述UE特定搜索空间；或，
    所述第一DCI的搜索空间为第一搜索空间；或，
    所述第一DCI的循环冗余校验CRC的校验比特长度等于第三取值；或，
    用于加扰所述第一DCI的CRC校验比特的无线网络临时标识RNTI等于第一RNTI；或，
    传输所述第一DCI的控制资源集合CORESET为第一CORESET。
  10. 如权利要求9所述的方法，其特征在于，以下至少一项是通过无线资源控制RRC信令获得的：所述第一取值、所述第二取值、所述第一搜索空间、所述第三取值、所述第一RNTI、第一CORESET。
  11. 一种通信装置，其特征在于，包括：
    接收单元，用于接收第一下行控制信息DCI；
    发送单元，用于发送第一上行控制信息UCI，所述第一UCI由所述第一DCI触发；在第一时域资源与上行数据信道PUSCH的时域资源部分或全部重叠，且第一条件被满足的条件下，第一符号上承载有所述第一UCI，而没有承载所述PUSCH，所述第一符号为所述第一时域资源和所述PUSCH的时域资源重叠的时域符号；所述第一时域资源用于传输所述第一UCI。
  12. 一种通信装置，其特征在于，包括：
    接收单元，用于接收第一下行控制信息DCI；
    发送单元，用于发送第一上行控制信息UCI，所述第一UCI由所述第一DCI触发；在第一时域资源与第二时域资源部分或全部重叠，且第一条件被满足的条件下，承载所述第一UCI的结束时域符号早于承载第二UCI的起始时域符号；所述第一时域资源用于传输所述第一UCI，所述第二时域资源用于传输所述第二UCI。
  13. 一种通信装置，其特征在于，包括：
    接收单元，用于接收第一下行控制信息DCI；
    发送单元，用于发送第一上行控制信息UCI，所述第一UCI由所述第一DCI触发；在第一时域资源与第二时域资源部分或全部重叠，且第一条件被满足的条件下，所述第一UCI采用的第一编码方式在数据传输可靠性方面优于第二UCI采用的第二编码方式；所述第一时域资源用于传输所述第一UCI，所述第二时域资源用于传输所述第二UCI。
  14. 一种通信装置，其特征在于，包括：
    发送单元，用于发送第一DCI；
    接收单元，接收第一UCI，所述第一UCI是由所述第一DCI触发；在第一时域资源与上行数据信道的时域资源部分或全部重叠，且第一条件被满足的条件下，第一符号上承载有所述第一UCI，而没有承载上行数据信道，所述第一符号为所述第一时域资源和所述上行数据信道的时域资源重叠的时域符号；第一时域资源用于传输所述第一UCI。
  15. 一种通信装置，其特征在于，包括：
    发送单元，用于发送第一DCI；
    接收单元，接收第一UCI，所述第一UCI是由所述第一DCI触发；在第一时域资源与第二时域资源部分或全部重叠，且第一条件被满足的条件下，承载所述第一UCI的结束时域符号早于承载第二UCI的起始时域符号；所述第一时域资源用于传输所述第一UCI，所述第二时域资源用于传输所述第二UCI。
  16. 一种通信装置，其特征在于，包括：
    发送单元，用于发送第一DCI；
    接收单元，接收第一UCI，所述第一UCI是由所述第一DCI触发；在第一时域资源与第二时域资源部分或全部重叠，且第一条件被满足的条件下，所述第一UCI采用的第一编码方式在数据传输可靠性方面优于第二UCI采用的第二编码方式；所述第一时域资源用于传输所述第一UCI，所述第二时域资源用于传输所述第二UCI。
  17. 如权利要求10-16中任一项所述的通信装置，其特征在于，所述第一编码方式增加所述第一UCI编码后的比特数，和/或所述第二编码方式减少第二UCI编码后的比特数。
  18. 如权利要求17所述的通信装置，其特征在于，所述第一编码方式包括：对所述第一UCI进行冗余编码；和/或，所述第二编码方式包括：对所述第二UCI进行HARQ-ACK比特绑定。
  19. 如权利要求10-18中任一项所述的通信装置，其特征在于，所述第一条件，具体包括：
    所述第一DCI的净荷大小等于第一取值；或，
    所述第一DCI的净荷大小等于所述第一取值，且所述第一DCI中的DCI格式标识字段取值等于第二取值；或，
    所述第一DCI的净荷大小等于所述第一取值，且所述第一DCI的搜索空间为终端设备UE特定搜索空间；或，
    所述第一DCI的净荷大小等于所述第一取值，所述第一DCI的DCI格式标识字段的取值等于所述第二取值，且所述第一DCI的搜索空间为所述UE特定搜索空间；或，
    所述第一DCI的搜索空间为第一搜索空间；或，
    所述第一DCI的循环冗余校验CRC的校验比特长度等于第三取值；或，
    用于加扰所述第一DCI的CRC校验比特的无线网络临时标识RNTI等于第一RNTI；或，
    传输所述第一DCI的控制资源集合CORESET为第一CORESET。
  20. 一种通信装置，其特征在于，包括：发射器和接收器，存储器以及耦合于所述存储器的处理器，所述存储器用于存储可由所述处理器执行的指令，所述处理器用于调用所述存储器中的所述指令，执行权利要求1-3、7-10中任一项所述的方法。
  21. 一种通信装置，其特征在于，包括：发射器和接收器，存储器以及耦合于所述存储器的处理器，所述存储器用于存储可由所述处理器执行的指令，所述处理器用于调用所述存储器中的所述指令，执行权利要求4-6、7-10中任一项所述的方法。
  22. 一种计算机可读存储介质，其特征在于，包括：所述可读存储介质上存储有指令，当所述指令被运行时，实现如权利要求1-3、7-10中任一项所述的方法。
  23. 一种计算机可读存储介质，其特征在于，包括：所述可读存储介质上存储有指令，当所述指令被运行时，实现如权利要求4-6、7-10中任一项所述的方法。
PCT/CN2018/124794 2018-01-12 2018-12-28 上行控制信息传输方法及装置 WO2019137245A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
EP18899556.7A EP3735071B1 (en) 2018-01-12 2018-12-28 Uplink control information transmission method and device
CA3087302A CA3087302A1 (en) 2018-01-12 2018-12-28 Uplink control information transmission method and apparatus
BR112020014204-2A BR112020014204A2 (pt) 2018-01-12 2018-12-28 método e aparelho de transmissão de informação de controle de enlace ascendente
US16/926,105 US11140666B2 (en) 2018-01-12 2020-07-10 Uplink control information transmission method and apparatus

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201810032725.7A CN110035531B (zh) 2018-01-12 2018-01-12 上行控制信息传输方法及装置
CN201810032725.7 2018-01-12

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/926,105 Continuation US11140666B2 (en) 2018-01-12 2020-07-10 Uplink control information transmission method and apparatus

Publications (2)

Publication Number Publication Date
WO2019137245A1 true WO2019137245A1 (zh) 2019-07-18
WO2019137245A8 WO2019137245A8 (zh) 2020-07-16

Family

ID=67218448

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/124794 WO2019137245A1 (zh) 2018-01-12 2018-12-28 上行控制信息传输方法及装置

Country Status (6)

Country Link
US (1) US11140666B2 (zh)
EP (1) EP3735071B1 (zh)
CN (1) CN110035531B (zh)
BR (1) BR112020014204A2 (zh)
CA (1) CA3087302A1 (zh)
WO (1) WO2019137245A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021034234A1 (en) * 2019-08-16 2021-02-25 Telefonaktiebolaget Lm Ericsson (Publ) Priority based multiplexing
EP3975640A4 (en) * 2019-08-20 2022-06-29 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Data transmission method, terminal device, and network device

Families Citing this family (20)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108282881B (zh) * 2017-01-06 2020-12-15 华为技术有限公司 一种资源配置方法及装置
AR114517A1 (es) * 2018-01-19 2020-09-16 Ericsson Telefon Ab L M Transmisión de uci urllc
KR20200138747A (ko) * 2018-03-30 2020-12-10 광동 오포 모바일 텔레커뮤니케이션즈 코포레이션 리미티드 업 링크 제어 정보 전송 방법 및 장치
CN113938264B (zh) * 2018-05-10 2024-05-24 北京三星通信技术研究有限公司 一种用于发送信号的方法与设备
US20210084644A1 (en) * 2018-05-11 2021-03-18 Lg Electronics Inc. Method for transmitting and receiving uplink control information in wireless communication system and apparatus therefor
CN110474747B (zh) * 2018-05-11 2022-01-25 中兴通讯股份有限公司 一种信号传输方法和装置、及终端
JP7309335B2 (ja) * 2018-09-19 2023-07-18 シャープ株式会社 端末装置、基地局装置、および、通信方法
MX2021011158A (es) * 2019-03-15 2021-10-22 Fg innovation co ltd Metodo y aparato para la multiplexacion de la informacion de control del enlace ascendente (uci).
US11758540B2 (en) * 2019-03-21 2023-09-12 Acer Incorporated Multiplexing method of uplink control information (UCI) for ultra-reliable and low latency communications (URLLC)
WO2021012285A1 (zh) * 2019-07-25 2021-01-28 Oppo广东移动通信有限公司 一种信息传输方法、电子设备及存储介质
CN117412382A (zh) * 2019-08-19 2024-01-16 北京小米移动软件有限公司 确定资源复用方法及装置、信息解调方法及装置、介质
EP4221016A1 (en) * 2019-09-30 2023-08-02 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Reception method and device for uplink control information
CN114270988A (zh) * 2019-10-17 2022-04-01 Oppo广东移动通信有限公司 传输数据的方法、终端设备和网络设备
CN114073156A (zh) * 2019-11-07 2022-02-18 Oppo广东移动通信有限公司 信号传输方法、装置、移动终端以及存储介质
EP4046448A4 (en) * 2019-11-08 2023-11-15 FG Innovation Company Limited METHOD AND APPARATUS FOR INDICATING CANCELLATION OF A UPLINK CONNECTION
CN113163502B (zh) * 2020-01-22 2023-04-25 维沃移动通信有限公司 一种通信处理方法及相关设备
WO2021147104A1 (zh) * 2020-01-23 2021-07-29 华为技术有限公司 一种数据的传输方法及装置
CN113676952A (zh) * 2020-05-13 2021-11-19 深圳市中兴微电子技术有限公司 编码方法、装置、设备和存储介质
WO2022198461A1 (zh) * 2021-03-23 2022-09-29 北京小米移动软件有限公司 一种传输混合自动重传请求确认信息的方法、装置及介质
US11438122B2 (en) 2021-06-14 2022-09-06 Ultralogic 6G, Llc Custom downlink search-spaces for low-complexity 5G/6G messaging

Family Cites Families (16)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP5823387B2 (ja) * 2009-06-19 2015-11-25 インターデイジタル パテント ホールディングス インコーポレイテッド Ｌｔｅ−ａにおけるアップリンク制御情報のシグナリング
US8971261B2 (en) * 2010-06-02 2015-03-03 Samsung Electronics Co., Ltd. Method and system for transmitting channel state information in wireless communication systems
US20120113827A1 (en) * 2010-11-08 2012-05-10 Sharp Laboratories Of America, Inc. Dynamic simultaneous pucch and pusch switching for lte-a
KR101587508B1 (ko) * 2012-10-12 2016-01-22 주식회사 케이티 단말의 상향링크 전력제어방법 및 그 단말
US10555286B2 (en) * 2013-07-30 2020-02-04 Qualcomm Incorporated Uplink control information (UCI) transmission with bundling considerations
CN105850057B (zh) * 2013-12-03 2019-04-09 Lg 电子株式会社 在支持机器型通信的无线接入系统中发送上行链路的方法和设备
CN105794280B (zh) * 2013-12-05 2019-05-31 Lg 电子株式会社 在无线接入系统中控制上行链路传输功率的方法和装置
WO2015115851A1 (en) * 2014-01-29 2015-08-06 Samsung Electronics Co., Ltd. Multicarrier-based data transmission method and apparatus in mobile communication system
CN104936300A (zh) * 2014-03-20 2015-09-23 中兴通讯股份有限公司 上行信道处理方法、终端、基站和系统
WO2017099556A1 (ko) * 2015-12-11 2017-06-15 엘지전자 주식회사 상향링크 신호를 전송하는 방법 및 이를 위한 장치
KR102288627B1 (ko) * 2016-03-02 2021-08-11 삼성전자 주식회사 통신 시스템에서 단말의 상향링크 제어 정보 전송 방법 및 장치
CN107276715A (zh) * 2016-04-01 2017-10-20 中兴通讯股份有限公司 一种传输信号的方法和装置
US10492184B2 (en) * 2016-12-09 2019-11-26 Samsung Electronics Co., Ltd. Multiplexing control information in a physical uplink data channel
US10716100B2 (en) * 2016-12-13 2020-07-14 Sharp Laboratories Of America, Inc. Base stations, user equipments, and related communication methods
US10965407B2 (en) * 2017-02-02 2021-03-30 Sharp Kabushiki Kaisha User equipments, base stations and communication methods
CN111133815B (zh) * 2017-07-21 2024-03-12 株式会社Ntt都科摩 用户终端以及无线通信方法

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
HUAWEI: "On UCI multiplexing", 3GPP TSG RAN WG1 MEETING AH_NR#3, 3GPP DRAFT, R1-1715404, 17 September 2017 (2017-09-17), XP051328967 *
See also references of EP3735071A4 *
ZTE: "On short PUCCH for up to 2 bits UCI", 3GPP TSG RAN WG1 MEETING AH_NR#3, 3GPP DRAFT, R1-1715522, 12 September 2017 (2017-09-12), XP051329400 *
ZTE: "UCI multiplexing on PUSCH", 3GPP TSG RAN WG1 MEETING NR#3, 3GPP DRAFT, RL-1715526, 12 September 2017 (2017-09-12), XP051329404 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021034234A1 (en) * 2019-08-16 2021-02-25 Telefonaktiebolaget Lm Ericsson (Publ) Priority based multiplexing
EP3975640A4 (en) * 2019-08-20 2022-06-29 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Data transmission method, terminal device, and network device

Also Published As

Publication number Publication date
CA3087302A1 (en) 2019-07-18
EP3735071B1 (en) 2023-07-12
US20200351867A1 (en) 2020-11-05
CN110035531A (zh) 2019-07-19
EP3735071A1 (en) 2020-11-04
CN110035531B (zh) 2021-12-03
EP3735071A4 (en) 2021-03-03
WO2019137245A8 (zh) 2020-07-16
BR112020014204A2 (pt) 2020-12-01
US11140666B2 (en) 2021-10-05

Similar Documents

Publication Publication Date Title
WO2019137245A1 (zh) 上行控制信息传输方法及装置
TWI691225B (zh) 衝突處理之方法、及其使用者設備和基地台
CN110169000B (zh) 用于上行链路超高可靠低延迟通信的信令、过程、用户设备和基站
TW202014005A (zh) 側邊鏈路車聯網通訊方法及其使用者設備
US12010665B2 (en) Method and apparatus for transmitting and receiving information for providing plurality of communication services
US20180063858A1 (en) System and Method for Co-existence of Low-Latency and Latency-Tolerant Communication Resources
US10368343B2 (en) Systems and methods for downlink scheduling that mitigate PDCCH congestion
US11018725B2 (en) Data transmission method, apparatus, and system
CN109479196B (zh) 用于上行链路穿孔传输的方法和设备
WO2020262202A1 (en) User equipment and base stations that achieve uplink multiplexing
US11765714B2 (en) Method and device for supporting latency services via a logical channel in a mobile communication system
US20230232373A1 (en) Method and device in nodes used for wireless communication
WO2017113077A1 (zh) 一种上行紧急业务传输方法、基站、用户设备及系统
WO2019192589A1 (zh) 通信方法、通信装置以及计算机可读存储介质
CN110035519B (zh) 一种上行数据传输方法及装置
US11382108B2 (en) Data transmission method, and apparatus
WO2022048509A1 (zh) 一种被用于无线通信的节点中的方法和装置
CN110943799B (zh) 一种通信方法及装置
KR20240074801A (ko) 방법들, 통신 디바이스들, 및 기반구조 장비
OA19794A (en) Methods and devices for uplink puncturing transmission.

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: 18899556

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 3087302

Country of ref document: CA

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2018899556

Country of ref document: EP

Effective date: 20200728

REG Reference to national code

Ref country code: BR

Ref legal event code: B01A

Ref document number: 112020014204

Country of ref document: BR

ENP Entry into the national phase

Ref document number: 112020014204

Country of ref document: BR

Kind code of ref document: A2

Effective date: 20200710