WO2020135214A1 - 上行控制信息uci的传输方法及终端 - Google Patents

上行控制信息uci的传输方法及终端 Download PDF

Info

Publication number
WO2020135214A1
WO2020135214A1 PCT/CN2019/126572 CN2019126572W WO2020135214A1 WO 2020135214 A1 WO2020135214 A1 WO 2020135214A1 CN 2019126572 W CN2019126572 W CN 2019126572W WO 2020135214 A1 WO2020135214 A1 WO 2020135214A1
Authority
WO
WIPO (PCT)
Prior art keywords
uci
priority
different priorities
ucis
beta
Prior art date
Application number
PCT/CN2019/126572
Other languages
English (en)
French (fr)
Inventor
李娜
沈晓冬
鲁智
Original Assignee
维沃移动通信有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 维沃移动通信有限公司 filed Critical 维沃移动通信有限公司
Priority to KR1020217021383A priority Critical patent/KR102512967B1/ko
Priority to JP2021535231A priority patent/JP7225405B2/ja
Priority to EP19901441.6A priority patent/EP3905570A4/en
Publication of WO2020135214A1 publication Critical patent/WO2020135214A1/zh
Priority to US17/356,890 priority patent/US11968676B2/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/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
    • 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/0009—Systems modifying transmission characteristics according to link quality, e.g. power backoff by adapting the channel coding
    • 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/0009—Systems modifying transmission characteristics according to link quality, e.g. power backoff by adapting the channel coding
    • H04L1/001—Systems modifying transmission characteristics according to link quality, e.g. power backoff by adapting the channel coding applied to control information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/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
    • 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/0056—Systems characterized by the type of code used
    • H04L1/007—Unequal error protection
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/1607—Details of the supervisory signal
    • H04L1/1671—Details of the supervisory signal the supervisory signal being transmitted together with control information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1829—Arrangements specially adapted for the receiver end
    • H04L1/1854—Scheduling and prioritising arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1829—Arrangements specially adapted for the receiver end
    • H04L1/1861—Physical mapping arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1829—Arrangements specially adapted for the receiver end
    • H04L1/1864—ARQ related signaling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signaling, i.e. of overhead other than pilot signals
    • 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
    • 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/04—Wireless resource allocation
    • H04W72/044—Wireless resource allocation based on the type of the allocated resource
    • H04W72/0466—Wireless resource allocation based on the type of the allocated resource the resource being a scrambling code
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling
    • H04W72/1263—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows
    • 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
    • H04W72/00—Local resource management
    • H04W72/50—Allocation or scheduling criteria for wireless resources
    • H04W72/56—Allocation or scheduling criteria for wireless resources based on priority criteria
    • 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
    • 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

Definitions

  • the present disclosure relates to the field of communication technology, and in particular, to a method and terminal for transmitting uplink control information UCI.
  • 5G mobile communication systems need to adapt to more diverse scenarios and business needs.
  • the main scenarios of 5G include: enhanced mobile bandwidth (Enhance Mobile Broadband, eMBB), low latency, high reliability communication (Ultra Reliable & Low Latency Communication, URLLC), massive machine type communication (Massive Machine Type Communication, mMTC).
  • eMBB enhanced mobile bandwidth
  • URLLC Ultra Reliable & Low Latency Communication
  • mMTC massive machine type communication
  • the system proposes high reliability, low latency, large bandwidth, and wide coverage.
  • For terminals that support URLLC low latency and high reliability services in order to achieve higher reliability, lower bit rates need to be used to transmit data, and faster and more accurate feedback of Channel State Information (Channel) Information (CSI) is required .
  • Channel State Information Channel State Information
  • CSI Channel State Information
  • the terminal supports both URLLC low latency and high reliability services, and at the same time supports large capacity and high rate eMBB services.
  • the reliability requirements of different service types are mainly reflected in different BLER target (block error rate target value) and latency (latency) requirements.
  • each physical uplink control channel (Physical Uplink Control Channel, PUCCH) resource has a radio resource control (Radio Resource Control, RRC) configuration corresponding maxcoderate (maximum bit rate) and nrofPRBs (maximum) Number of physical resource blocks).
  • RRC Radio Resource Control
  • the terminal transmits uplink control information (Uplink Control Information, UCI) on the PUCCH
  • UCI Uplink Control Information
  • the terminal needs to discard some UCI according to certain rules.
  • Different code rates can adapt to different channel conditions and meet different BLER target requirements. For example, if the BLER target is low (such as 10 ⁇ -5), a lower code rate is required. Conversely, if the BLER target is relatively high (such as 10 ⁇ -2), a higher code rate can be used to reduce the use of Resources to improve resource utilization.
  • the terminal when the PUCCH and Physical Uplink Shared Channel (PUSCH) time domains overlap, if the multiplexing time requirements are met, the terminal multiplexes the UCI content on the PUCCH on the PUSCH for transmission, and UCI transmits on the PUSCH At the time, the terminal determines the number of resource particles (Resource Elements, RE) occupied by UCI on the PUSCH through the RRC configuration or DCI indicated beta_offset (resource occupancy ratio offset value), and performs coding and rate matching according to the RE number .
  • RE resource Elements
  • the hybrid automatic repeat request confirmation (Hybrid Automatic Repeat-request-ACK, HARQ-ACK) feedback of the physical downlink shared channel (PDSCH) of the URLLC and eMBB services can use different The codebook (codebook) feeds back on different PUCCH resources.
  • the codebook codebook feeds back on different PUCCH resources.
  • the present disclosure provides in real time a method and terminal for transmitting uplink control information UCI to solve the coding problem when UCIs of different service types are transmitted on the same channel.
  • a method for transmitting uplink control information UCI, applied to a terminal includes:
  • UCIs of different priorities are transmitted on the same target channel
  • UCIs of different priorities are separately encoded and then transmitted on the target channel
  • the priority of the UCI is determined by the target parameters of the downlink control information DCI and/or the information contained in the UCI; DCI is used to indicate the DCI corresponding to the UCI transmission.
  • An embodiment of the present disclosure also provides a terminal, including:
  • An encoding transmission module configured to encode UCIs of different priorities and transmit them on the target channel after UCIs of different priorities are transmitted on the same target channel;
  • the priority of the UCI is determined by the target parameters of the downlink control information DCI and/or the information contained in the UCI; DCI is used to indicate the DCI corresponding to the UCI transmission.
  • An embodiment of the present disclosure also provides a terminal, including a processor, a memory, and a computer program stored on the memory and executable on the processor.
  • the computer program is implemented as described above when executed by the processor. The steps of the above-mentioned uplink control information UCI transmission method.
  • Embodiments of the present disclosure also provide a computer-readable storage medium that stores a computer program on the computer-readable storage medium, and when the computer program is executed by a processor, implements the steps of the transmission method of the uplink control information UCI described above .
  • the reliability of UCI with high priority can be achieved, and the resource utilization rate can be improved.
  • FIG. 1 shows a schematic diagram of steps of a method for transmitting uplink control information UCI provided by an embodiment of the present disclosure
  • FIG. 2 is a schematic diagram showing an example of a method for transmitting uplink control information UCI provided by an embodiment of the present disclosure
  • FIG. 3 is a schematic diagram showing another example of a method for transmitting uplink control information UCI provided by an embodiment of the present disclosure
  • FIG. 4 is a schematic diagram showing still another example of the method for transmitting uplink control information UCI provided by an embodiment of the present disclosure
  • FIG. 5 shows one of the structural schematic diagrams of the terminal provided by the embodiment of the present disclosure
  • FIG. 6 shows a second structural schematic diagram of a terminal provided by an embodiment of the present disclosure.
  • an embodiment of the present disclosure provides a method for transmitting uplink control information UCI, which is applied to a terminal and includes:
  • Step 101 In the case that UCIs with different priorities are transmitted on the same target channel, UCIs with different priorities are separately encoded and then transmitted on the target channel;
  • the priority of the UCI is determined by the target parameters of the downlink control information DCI and/or the information contained in the UCI; DCI is used to indicate the DCI corresponding to the UCI transmission.
  • the target parameter of the DCI includes at least one of the following:
  • Temporary wireless network identity corresponding to DCI
  • Control resource set (control reset, CORESET) corresponding to DCI
  • DCI corresponding modulation and coding strategy (modulation and coding scheme, MCS) table
  • Resource indication information carried in the DCI is a time domain resource and/or a frequency domain resource newly used to indicate data or control information transmission;
  • the pilot mapping type information carried in the DCI to indicate the transmission of data or control information.
  • the DCI corresponding to the UCI transmission indicating high priority is the following DCI:
  • DCI scrambled using a specific RNTI eg MCS-C-RNTI
  • the MCS configured in the DCI uses a MCS table with low spectrum efficiency (eg MCS table 3, MCS table 3);
  • the DCI corresponding to the UCI transmission indicating low priority is the following DCI:
  • the information contained in the UCI includes Hybrid Automatic Repeat Request Confirmation (Hybrid Automatic Repeat-request-ACK, HARQ-ACK), Channel State Information (Channel State Information, CSI), Scheduling Request (SR), etc.
  • the UCI priority may also be referred to as being related to the UCI service type.
  • the UCI of the eMBB service and the UCI of the URLLC service are UCIs of different priorities.
  • the DCI target parameters used to indicate the UCI transmission of different service types are different.
  • the format of the DCI used to indicate the UCI transmission of the eMBB service is DCI format 1, which is used to indicate the UCI transmission of the URLLC service.
  • the format of DCI is DCI format 2, then the terminal can determine different priorities of UCIs of different service types according to different DCI formats.
  • the target channel includes: a physical uplink control channel PUCCH or a physical uplink shared channel PUSCH.
  • the method further includes:
  • UCIs of different priorities use different code rates.
  • the method further includes:
  • the code rate used by UCI with different priorities determine the code rate used by UCI with different priorities
  • the code rates corresponding to UCIs of different priorities are determined.
  • the first scaling factor is configured by radio resource control RRC, or indicated by DCI, or specified by a protocol.
  • the code rate corresponding to the PUCCH resource is specifically: a code rate configured by the network-side device for the PUCCH resource through RRC signaling.
  • the network side device configures different code rates for PUCCH resources through RRC signaling, and UCIs with different priorities respectively correspond to different code rates.
  • the UCI with high priority uses the code rate corresponding to the PUCCH resource
  • the UCI with low priority uses the code rate corresponding to the code rate corresponding to the PUCCH resource times the first scaling factor.
  • the first scaling The factor is less than 1.
  • the UCI with low priority uses the code rate corresponding to the PUCCH resource
  • the UCI with high priority uses the code rate corresponding to the code rate corresponding to the PUCCH resource times the first scaling factor.
  • the first scaling The factor is greater than 1.
  • the method further includes:
  • the resources used to transmit the UCI of the first priority are allocated according to the code rate configured by RRC, and the remaining resources are used to transmit the UCI of the second priority; that is, the UCI of the first priority and the The UCI of the second priority uses the number of physical resource blocks PRB configured by RRC together.
  • the first priority is higher than the second priority.
  • the UCI of the first priority uses the maximum bit rate configured by the RRC to determine the resource unit RE required to transmit the UCI of the first priority, and determines the physical resources configured by the RRC
  • the remaining REs in the block except the REs required to transmit the UCI of the first priority are used to transmit the UCI of the second priority;
  • the transmission of the second priority UCI is completely or partially discarded.
  • it is discarded according to a certain configuration or a predefined UCI discard rule, such as preferentially discarding CSI part 2 (Part 2 CSI), then CSI part 1 (Part 1 CSI), then HARQ-ACK or SR, etc. .
  • step 101 includes:
  • UCIs with different priorities are encoded separately, and the UCIs with different priorities after encoding are mapped onto physical resources using a time-domain-first mapping method and transmitted on the target channel.
  • UCIs with different priorities are low-priority HARQ-ACK (such as eMBB HARQ-ACK) and high-priority HARQ-ACK (such as URLLC HARQ-ACK); when low-priority HARQ-ACK and high-priority HARQ-ACK When multiplexed together, if the terminal misses the PDCCH corresponding to the last PDSCH of the low-priority service (such as eMBB service), it will cause the base station and the terminal to misunderstand the number of low-priority HARQ-ACK bits.
  • low-priority HARQ-ACK such as eMBB HARQ-ACK
  • high-priority HARQ-ACK such as URLLC HARQ-ACK
  • the PRB resources used are inconsistent, so in order to reduce the impact of low-priority PDCCH miss detection on high-priority HARQ-ACK feedback, high-priority HARQ-ACK and low-priority HARQ-ACK are coded separately, and time-domain-first The way is mapped to physical resources, which can ensure that the base station correctly receives the high priority HARQ-ACK feedback.
  • UCI that is mapped to physical resources using a time-domain-first mapping method
  • the embodiments of the present disclosure do not limit the encoding rate and/or beta_offset of UCI, that is, different priorities for transmission using the time-domain-first mapping method
  • UCI of different priorities can be coded with the same code rate, or with different code rates, with the same beta_offset, or with different beta_offset.
  • the PUCCH carrying low priority HARQ-ACK overlaps with multiple time division multiplexed PUCCH carrying high priority HARQ-ACK (respectively HARQ-ACK1 and HARQ-ACK2), in order to reduce High-priority HARQ-ACK feedback delay, multiplexing low-priority HARQ-ACK on high-priority PUCCH, while considering the terminal processing time, the low-priority HARQ-ACK and the first one meet the multiplexing time condition
  • the high priority PUCCH is multiplexed.
  • low-priority HARQ-ACK and high-priority HARQ-ACK 2 are multiplexed and transmitted on one PUCCH
  • low-priority HARQ-ACK and high-priority HARQ-ACK 2 are coded separately, and the two use different code rates to determine their Number of REs used.
  • the high-priority HARQ-ACK2 uses the maxcoderate (maximum code rate) corresponding to the PUCCH resource configured by RRC to determine the RE it occupies.
  • the terminal determines the number of PRBs used by the URLCC HARQ-ACK bit number and its bit rate and the low priority HARQ-ACK bit number and its bit rate (the determined PRB number is less than or equal to the maximum PRB number of the PUCCH resource configured by RRC ).
  • the terminal uses the maximum code rate to transmit high-priority HARQ-ACK and discards some low-priority -Level HARQ-ACK bits or compressed HARQ-ACK bits of low priority HARQ-ACK bits (eg, code block group (CBG) granularity HARQ-ACK back to transmission block (TB) granularity HARQ-ACK ( Determine the number of feedback HARQ-ACK bits according to the number of TB); or, bind HARQ-ACK to meet the HARQ-ACK bit rate requirement of eMBB.
  • CBG code block group
  • TB transmission block
  • the low-priority BLER target (block error rate target value) is 10 ⁇ -2 and the high-priority BLER target is 10 ⁇ -5/-6
  • the low-priority PDCCH miss detection probability is 1%
  • the high-priority The probability of missed detection of the PDCCH of the first level is 0.001%, so if the last PDCCH of the low priority is missed, when the low priority HARQ-ACK and the high priority HARQ-ACK are multiplexed together, it will cause the base station and the UE to respond to the HARQ-ACK
  • the number of bits is inconsistent and the PRB resources used by PUCCH are inconsistent.
  • the high-priority HARQ-ACK and low Priority HARQ-ACK is coded separately and mapped to physical resources in a time-domain-first manner. Ensure that the base station can correctly receive the high priority HARQ-ACK feedback.
  • the method further includes:
  • UCIs of different priorities use different resource occupancy ratio offset values of beta_offset to determine the resource particles RE and bit rate used by each UCI.
  • the method further includes:
  • beta_offset used by UCI of different priorities; for example, UCI with high priority adopts RRC configuration or beta_offset indicated by DCI, and UCI with low priority adopts preset beta_offset (pre- Let beta_offset be a fixed beta_offset), for example, the default beta_offset is equal to 1.
  • This method is generally applicable to low-priority UCI and high-priority UCI multiplexed on high-priority PUSCH.
  • beta_offset corresponding to UCIs of different priorities indicated in DCI (for example, UL grant)
  • DCI indicates the beta_offset of UCI of high priority and the low priority of UCI respectively UCI's beta_offset.
  • the beta_offset is indicated in the form of Table 1, where the beta_offset in DCI indicates the beta_offset of each state indicating different priorities (such as high-priority service URLLC and low-priority service eMBB), and the same priority contains different UCI type (such as HARQ-ACK, CSI part1 and CSI part 2) and the number of bits (such as less than 3 bits, greater than 3 bits and less than 12 bits, greater than 11 bits, etc.), where the priority can be used to indicate the UCI
  • the target parameter of the downlink control information DCI corresponding to the transmission is determined.
  • the indexes corresponding to less than or equal to 2 bits HARQ-ACK, the indexes corresponding to greater than 2 bits and less than 12 bits HARQ-ACK, and the indexes corresponding to greater than 11 bits HARQ-ACK with Represents the indexes corresponding to 11-bit CSI part 1 and CSI part 2 respectively, with Respectively indicate the indexes corresponding to CSI part 1 and CSI part 2 that are larger than 11 bits.
  • the second scaling factor and the beta_offset of UCI of the first priority indicated by the RRC configuration or DCI determine the beta_offset used by UCI of different priorities; wherein, the second scaling factor is configured by RRC or indicated by DCI, Or specified by the protocol; for example, the RRC configuration or DCI indicates the beta_offset of high priority UCI; the low priority UCI beta_offset is equal to the product of the RRC configuration or DCI indicated beta_offset and the second scaling factor; and for example, The RRC configuration or DCI indicates the beta_offset of the UCI with low priority; the beta_offset of the UCI with high priority is equal to the product of the beta_offset indicated by the RRC configuration or DCI and the second scaling factor.
  • the aforementioned high priority HARQ-ACK may be URLLC HARQ-ACK, and the low priority HARQ-ACK may be eMBB HARQ-ACK;
  • the high priority UCI mentioned above may be URLLC CSI, and the low priority UCI may be eMBB CSI.
  • the high priority UCI mentioned above may be URLLC CSI, and the low priority UCI may be eMBB HARQ-ACK.
  • the priority of HARQ-ACK is determined through the DCI format, control resource set, and/or search space, etc.
  • the specific method of determining the priority of UCI has been described in detail in the above embodiments, and will not be repeated here Repeat.
  • the above embodiments of the present disclosure can achieve the reliability of high-priority UCI and improve the resource utilization rate by defining or configuring the encoding method and bit rate of UCIs of different priorities when transmitted on the same target channel.
  • an embodiment of the present disclosure also provides a terminal 500, including:
  • the encoding transmission module 501 is used to encode UCIs of different priorities and transmit them on the target channel after UCIs of different priorities are transmitted on the same target channel;
  • the priority of the UCI is determined by the target parameters of the downlink control information DCI and/or the information contained in the UCI; DCI is used to indicate the DCI corresponding to the UCI transmission.
  • the target channel includes: a physical uplink control channel PUCCH or a physical uplink shared channel PUSCH.
  • the terminal further includes:
  • the first encoding module is used to encode UCIs of different priorities when the target channel is PUCCH, and UCIs of different priorities use different code rates.
  • the terminal further includes:
  • the code rate determining module is used to determine the code rate used by UCIs of different priorities according to the first scaling factor and the code rate corresponding to the PUCCH resource; or, the code corresponding to UCI of different priorities configured by radio resource control RRC Rate, determine the bit rate used by UCI with different priorities;
  • the first scaling factor is configured by radio resource control RRC, or indicated by DCI, or specified by a protocol.
  • the second encoding module is used to encode UCIs of different priorities according to the RRC configuration when the target channel is PUCCH and the priority of the UCI includes at least the first priority and the second priority
  • the code rate is allocated to transmit the UCI resources of the first priority, and the remaining resources are used to transmit the UCI of the second priority;
  • the encoding transmission module includes:
  • the terminal further includes:
  • the third encoding module is used for encoding UCIs of different priorities when the target channel is PUSCH, and UCIs of different priorities use different resource occupancy ratio offset values of beta_offset to determine the use of each UCI The resource particles and bit rate.
  • the terminal further includes:
  • the offset value determination module is used to determine the beta_offset used by UCI of different priorities according to the RRC configuration or the beta_offset indicated by DCI and the preset beta_offset;
  • the priority of the UCI includes at least the first Priority and second priority
  • the second scaling factor is configured by RRC or indicated by DCI, Or as stipulated by the agreement.
  • the terminal provided by the embodiment of the present disclosure can implement various processes implemented by the terminal in the method embodiments of FIG. 1 to FIG. 4. To avoid repetition, details are not described herein again.
  • the above embodiments of the present disclosure can achieve the reliability of high-priority UCI and improve the resource utilization rate by defining or configuring the encoding method, code rate, etc. of UCIs of different priorities when transmitted on the same target channel.
  • the terminal provided by the embodiment of the present disclosure is a terminal capable of executing the above-mentioned uplink control information UCI transmission method, then all the embodiments of the above-mentioned uplink control information UCI transmission method are applicable to the terminal, and all can achieve the same Or similar beneficial effects.
  • the terminal 600 includes but is not limited to: a radio frequency unit 601, a network module 602, an audio output unit 603, an input unit 604, a sensor 605, a display unit 606, The user input unit 607, interface unit 608, memory 609, processor 610, power supply 611 and other components.
  • a radio frequency unit 601 a radio frequency unit 601
  • a network module 602 an audio output unit 603, an input unit 604, a sensor 605, a display unit 606,
  • the user input unit 607, interface unit 608, memory 609, processor 610, power supply 611 and other components Those skilled in the art may understand that the terminal structure shown in FIG. 6 does not constitute a limitation on the terminal, and the terminal may include more or less components than those illustrated, or combine certain components, or arrange different components.
  • the terminal includes but is not limited to a mobile phone, a tablet computer, a notebook computer, a palmtop computer, an in-vehicle terminal, a wearable device, and a pedometer.
  • the processor 610 is configured to separately encode UCIs of different priorities when UCIs of different priorities are transmitted on the same target channel,
  • the radio frequency unit 601 is configured to transmit on the target channel after separately encoding UCIs of different priorities
  • the priority of the UCI is determined by the target parameters of the downlink control information DCI and/or the information contained in the UCI; DCI is used to indicate the DCI corresponding to the UCI transmission.
  • the above embodiments of the present disclosure can achieve the reliability of high-priority UCI and improve the resource utilization rate by defining or configuring the encoding method and bit rate of UCIs of different priorities when transmitted on the same target channel.
  • the terminal provided by the embodiment of the present disclosure is a terminal capable of executing the above-mentioned uplink control information UCI transmission method, then all the embodiments of the above-mentioned uplink control information UCI transmission method are applicable to the terminal, and all can achieve the same Or similar beneficial effects.
  • the radio frequency unit 601 may be used to receive and send signals during sending and receiving information or during a call. Specifically, after receiving the downlink data from the base station, it is processed by the processor 610; The uplink data is sent to the base station.
  • the radio frequency unit 601 includes but is not limited to an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, and the like.
  • the radio frequency unit 601 can also communicate with the network and other devices through a wireless communication system.
  • the terminal provides users with wireless broadband Internet access through the network module 602, such as helping users send and receive e-mail, browse web pages, and access streaming media.
  • the audio output unit 603 may convert the audio data received by the radio frequency unit 601 or the network module 602 or stored in the memory 609 into an audio signal and output as sound. Moreover, the audio output unit 603 may also provide audio output related to a specific function performed by the terminal 600 (eg, call signal reception sound, message reception sound, etc.).
  • the audio output unit 603 includes a speaker, a buzzer, a receiver, and the like.
  • the input unit 604 is used to receive audio or video signals.
  • the input unit 604 may include a graphics processor (Graphics, Processing, Unit, GPU) 6041 and a microphone 6042, and the graphics processor 6041 may process a still picture or video image obtained by an image capture device (such as a camera) in a video capture mode or an image capture mode The data is processed.
  • the processed image frame may be displayed on the display unit 606.
  • the image frame processed by the graphics processor 6041 may be stored in the memory 609 (or other storage medium) or sent via the radio frequency unit 601 or the network module 602.
  • the microphone 6042 can receive sound, and can process such sound into audio data.
  • the processed audio data can be converted into a format that can be sent to the mobile communication base station via the radio frequency unit 601 in the case of a telephone call mode and output.
  • the terminal 600 further includes at least one sensor 605, such as a light sensor, a motion sensor, and other sensors.
  • the light sensor includes an ambient light sensor and a proximity sensor, wherein the ambient light sensor can adjust the brightness of the display panel 6061 according to the brightness of the ambient light, and the proximity sensor can close the display panel 6061 and/or when the terminal 600 moves to the ear Or backlight.
  • the accelerometer sensor can detect the magnitude of acceleration in various directions (generally three axes), and can detect the magnitude and direction of gravity when at rest, and can be used to identify the posture of the terminal (such as horizontal and vertical screen switching, related games, Magnetometer attitude calibration), vibration recognition related functions (such as pedometer, tap), etc.; sensor 605 can also include fingerprint sensor, pressure sensor, iris sensor, molecular sensor, gyroscope, barometer, hygrometer, thermometer, infrared Sensors, etc., will not be repeated here.
  • the display unit 606 is used to display information input by the user or information provided to the user.
  • the display unit 606 may include a display panel 6061, and the display panel 6061 may be configured in the form of a liquid crystal display (Liquid Crystal) (LCD), an organic light-emitting diode (Organic Light-Emitting Diode, OLED), or the like.
  • LCD Liquid Crystal
  • OLED Organic Light-Emitting Diode
  • the touch detection device detects the user's touch orientation, and detects the signal brought by the touch operation, and transmits the signal to the touch controller; the touch controller receives touch information from the touch detection device, and converts it into contact coordinates, and then sends To the processor 610, the command sent by the processor 610 is received and executed.
  • the touch panel 6071 may be implemented in various types such as resistive, capacitive, infrared, and surface acoustic waves.
  • the user input unit 607 may also include other input devices 6072.
  • other input devices 6072 may include, but are not limited to, physical keyboards, function keys (such as volume control keys, switch keys, etc.), trackballs, mice, and joysticks, which are not repeated here.
  • the touch panel 6071 may be overlaid on the display panel 6061.
  • the touch panel 6071 detects a touch operation on or near it, it is transmitted to the processor 610 to determine the type of touch event, and then the processor 610 according to the touch The type of event provides corresponding visual output on the display panel 6061.
  • the touch panel 6071 and the display panel 6061 are implemented as two independent components to realize the input and output functions of the terminal, in some embodiments, the touch panel 6071 and the display panel 6061 may be integrated to The input and output functions of the terminal are implemented, which is not limited here.
  • the interface unit 608 is an interface for connecting an external device to the terminal 600.
  • the external device may include a wired or wireless headset port, an external power (or battery charger) port, a wired or wireless data port, a memory card port, a port for connecting a device with an identification module, audio input/output (input/output, I/O) port, video I/O port, headphone port, etc.
  • the interface unit 608 may be used to receive input from external devices (eg, data information, power, etc.) and transmit the received input to one or more elements within the terminal 600 or may be used between the terminal 600 and external devices Transfer data between.
  • the memory 609 can be used to store software programs and various data.
  • the memory 609 may mainly include a storage program area and a storage data area, wherein the storage program area may store an operating system, application programs required by at least one function (such as a sound playback function, an image playback function, etc.), etc.; the storage data area may store Data created by the use of mobile phones (such as audio data, phonebooks, etc.), etc.
  • the memory 609 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one magnetic disk storage device, a flash memory device, or other volatile solid-state storage devices.
  • the processor 610 is the control center of the terminal, and uses various interfaces and lines to connect the various parts of the entire terminal, executes or executes the software programs and/or modules stored in the memory 609, and calls the data stored in the memory 609 to execute Various functions and processing data of the terminal, so as to monitor the terminal as a whole.
  • the processor 610 may include one or more processing units; optionally, the processor 610 may integrate an application processor and a modem processor, where the application processor mainly processes an operating system, a user interface, and application programs, etc.
  • the modulation processor mainly handles wireless communication. It can be understood that the foregoing modem processor may not be integrated into the processor 610.
  • the terminal 600 may also include a power supply 611 (such as a battery) that supplies power to various components.
  • a power supply 611 (such as a battery) that supplies power to various components.
  • the power supply 611 may be logically connected to the processor 610 through a power management system, thereby managing charge, discharge, and power consumption management through the power management system And other functions.
  • the terminal 600 includes some functional modules not shown, which will not be repeated here.
  • an embodiment of the present disclosure further provides a terminal, including a processor, a memory, and a computer program stored on the memory and executable on the processor, and the computer program is executed by the processor to implement the above uplink control information
  • a terminal including a processor, a memory, and a computer program stored on the memory and executable on the processor, and the computer program is executed by the processor to implement the above uplink control information
  • Embodiments of the present disclosure also provide a computer-readable storage medium that stores a computer program on the computer-readable storage medium.
  • the computer program is executed by a processor, each process of the foregoing embodiment of the method for transmitting uplink control information UCI is implemented, To achieve the same technical effect, in order to avoid repetition, it will not be repeated here.
  • the computer-readable storage medium such as read-only memory (Read-Only Memory, ROM for short), random access memory (Random Access Memory, RAM for short), magnetic disk or optical disk, etc.
  • the disclosed device and method may be implemented in other ways.
  • the device embodiments described above are only schematic.
  • the division of the units is only a logical function division, and there may be other divisions in actual implementation, for example, multiple units or components may be combined or Can be integrated into another system, or some elements can be ignored, or not implemented.
  • the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, and may be in electrical, mechanical, or other forms.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
  • each functional unit in each embodiment of the present disclosure may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit.
  • the function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium.
  • the technical solution of the present disclosure essentially or part of the contribution to the related technology or part of the technical solution can be embodied in the form of a software product, the computer software product is stored in a storage medium, including several
  • the instructions are used to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods described in the embodiments of the present disclosure.
  • the foregoing storage media include various media that can store program codes, such as U disk, mobile hard disk, ROM, RAM, magnetic disk, or optical disk.
  • the program can be stored in a computer-readable storage medium. When executed, it may include the processes of the foregoing method embodiments.
  • the storage medium may be a magnetic disk, an optical disk, a read-only memory (Read-Only Memory, ROM) or a random access memory (Random Access Memory, RAM), etc.
  • the embodiments described in the embodiments of the present disclosure may be implemented by hardware, software, firmware, middleware, microcode, or a combination thereof.
  • the processing unit can be implemented in one or more application specific integrated circuits (Application Specific Integrated Circuits, ASIC), digital signal processor (Digital Signal Processor, DSP), digital signal processing device (DSP Device, DSPD), programmable Logic Device (Programmable Logic Device, PLD), Field Programmable Gate Array (Field-Programmable Gate Array, FPGA), general-purpose processor, controller, microcontroller, microprocessor, others for performing the functions described in this disclosure Electronic unit or its combination.
  • ASIC Application Specific Integrated Circuits
  • DSP Digital Signal Processor
  • DSP Device digital signal processing device
  • DPD digital signal processing device
  • PLD programmable Logic Device
  • Field Programmable Gate Array Field-Programmable Gate Array
  • FPGA Field-Programmable Gate Array
  • the technology described in the embodiments of the present disclosure may be implemented by modules (eg, procedures, functions, etc.) that perform the functions described in the embodiments of the present disclosure.
  • the software codes can be stored in memory and executed by the processor.
  • the memory may be implemented in the processor or external to the processor.

Landscapes

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

Abstract

本公开提供一种上行控制信息UCI的传输方法及终端，该方法包括：在不同优先级的UCI在同一目标信道传输的情况下，对不同优先级的UCI分别进行编码之后在所述目标信道上传输；其中，所述UCI的优先级由下行控制信息DCI的目标参数和/或UCI包含的信息确定；DCI为用于指示所述UCI传输所对应的DCI。

Description

上行控制信息UCI的传输方法及终端
相关申请的交叉引用
本申请主张在2018年12月25日在中国提交的中国专利申请号No.201811594137.9的优先权，其全部内容通过引用包含于此。
技术领域
本公开涉及通信技术领域，尤其是指一种上行控制信息UCI的传输方法及终端。
背景技术
与以往的移动通信系统相比，未来5G移动通信系统需要适应更加多样化的场景和业务需求。5G的主要场景包括：增强型移动带宽(Enhance Mobile Broadband，eMBB)，低时延、高可靠通信(Ultra Reliable&Low Latency Communication，URLLC)，海量机器类通信(Massive Machine Type Communication，mMTC)，这些场景对系统提出了高可靠，低时延，大带宽，广覆盖等要求。对于支持URLLC低时延高可靠业务的终端，为了达到更高的可靠性，需要使用更低的码率传输数据，同时需要更快、更精确的信道状态信息(Channel State Information，CSI)的反馈。另外对于某些终端可能支持不同数值配置的业务，终端既支持URLLC低时延高可靠业务，同时支持大容量高速率的eMBB业务。不同业务类型的可靠性要求主要体现在不同的BLER target(误块率目标值)和latency(延迟)要求。
新空口(New Raido，NR)R15中每个物理上行控制信道(Physical Uplink Control Channel，PUCCH)资源都有无线资源控制(Radio Resource Control，RRC)配置相应的maxcoderate(最大码率)和nrofPRBs(最大物理资源块数量)。终端在该PUCCH传输上行控制信息(Uplink Control Information，UCI)时，根据UCI的payload size(有效载荷大小)和maxcoderate(最大码率)确定所需要的物理资源块(Physical Resource Block，PRB)(<＝nrofPRBs)，使得实际传输的码率小于等于maxcoderate，如果终端使用所有PRB的码率 仍然高于该配置的最大码率，则终端需按照一定规则丢弃部分UCI。不同的码率可以适应不同的信道状态，满足不同的BLER target要求。例如，如果BLER target较低(如10^-5)，则需要较低的码率，反之，如果BLER target相对较高(如10^-2)则可以使用更高的码率来减少使用的资源，提高资源利用率。
NR R15中当PUCCH和物理上行共享信道(Physical Uplink Shared Channel，PUSCH)时域重叠时，如果满足复用的时间要求，终端将PUCCH上的UCI内容复用在PUSCH上传输，UCI在PUSCH上传输时，终端通过RRC配置的或DCI指示的beta_offset(资源占用比偏移值)确定UCI在PUSCH上传输时所占用的资源粒子(Resource Element，RE)数，并根据该RE数进行编码与速率匹配。
对于同时支持URLLC和eMBB业务的终端，URLLC和eMBB业务的物理下行共享信道(physical downlink shared channel，PDSCH)的混合自动重传请求确认(Hybrid Automatic Repeat request-ACK，HARQ-ACK)反馈可以使用不同的codebook(码本)在不同的PUCCH资源上反馈，当不同的PUCCH冲突时，如果丢弃某个PUCCH上的HARQ-ACK，基站就需要重传其相应的PDSCH，因而会大大降低下行吞吐量。因此需要考虑将不同PUCCH上的HARQ-ACK复用在一个PUCCH。由于一个PUCCH只有一个maxcoderate，如果该maxcoderate为URLLC的码率，则eMBB反馈需要较多的资源，造成资源浪费。如果该maxcoderate为eMBB的码率，则URLLC反馈的可靠性无法保证。同样的，如果对于同时支持URLLC和eMBB业务的终端，URLLC和eMBB的PDSCH的HARQ-ACK反馈可以使用相同的码本在相同的PUCCH资源上反馈，也需要考虑不同业务类型的UCI复用时的编码问题。
发明内容
本公开实时提供一种上行控制信息UCI的传输方法及终端，以解决不同业务类型的UCI在同一信道上传输时的编码问题。
为了解决上述技术问题，本公开是这样实现的：一种上行控制信息UCI的传输方法，应用于终端，包括：
在不同优先级的UCI在同一目标信道传输的情况下，对不同优先级的UCI分别进行编码之后在所述目标信道上传输；
其中，所述UCI的优先级由下行控制信息DCI的目标参数和/或UCI包含的信息确定；DCI为用于指示所述UCI传输所对应的DCI。
本公开实施例还提供了一种终端，包括：
编码传输模块，用于在不同优先级的UCI在同一目标信道传输的情况下，对不同优先级的UCI分别进行编码之后在所述目标信道上传输；
其中，所述UCI的优先级由下行控制信息DCI的目标参数和/或UCI包含的信息确定；DCI为用于指示所述UCI传输所对应的DCI。
本公开实施例还提供了一种终端，包括处理器、存储器及存储在所述存储器上并可在所述处理器上运行的计算机程序，所述计算机程序被所述处理器执行时实现如上所述的上行控制信息UCI的传输方法的步骤。
本公开实施例还提供了一种计算机可读存储介质，所述计算机可读存储介质上存储计算机程序，所述计算机程序被处理器执行时实现如上所述的上行控制信息UCI的传输方法的步骤。
在本公开实施例中，通过对不同优先级的UCI在同一目标信道传输时的编码方式、码率等进行定义或配置，可以实现高优先级的UCI的可靠性，提高资源利用率。
附图说明
为了更清楚地说明本公开实施例的技术方案，下面将对本公开实施例的描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本公开的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动性的前提下，还可以根据这些附图获得其他的附图。
图1表示本公开实施例提供的上行控制信息UCI的传输方法的步骤示意图；
图2表示本公开实施例提供的上行控制信息UCI的传输方法中一示例的示意图；
图3表示本公开实施例提供的上行控制信息UCI的传输方法中另一示例 的示意图；
图4表示本公开实施例提供的上行控制信息UCI的传输方法中又一示例的示意图；
图5表示本公开实施例提供的终端的结构示意图之一；
图6表示本公开实施例提供的终端的结构示意图之二。
具体实施方式
下面将结合本公开实施例中的附图，对本公开实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例是本公开一部分实施例，而不是全部的实施例。基于本公开中的实施例，本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例，都属于本公开保护的范围。
如图1所示，本公开实施例提供一种上行控制信息UCI的传输方法，应用于终端，包括：
步骤101，在不同优先级的UCI在同一目标信道传输的情况下，对不同优先级的UCI分别进行编码之后在所述目标信道上传输；
其中，所述UCI的优先级由下行控制信息DCI的目标参数和/或UCI包含的信息确定；DCI为用于指示所述UCI传输所对应的DCI。
可选的，所述DCI的目标参数包括下述至少一项：
DCI格式；
DCI所对应的无线网络临时标识(radio network temporary identity，RNTI)；
DCI所对应的控制资源集(control resource set，CORESET)；
DCI所对应的搜索空间；
DCI所对应的调制与编码策略(modulation and coding scheme，MCS)表；
DCI中携带的优先级指示信息；
DCI所对应的加扰比特信息；
DCI中携带的资源指示信息，所述资源指示新用于指示数据或者控制信息传输的时域资源和/或频域资源；以及
DCI中携带的用于指示数据或者控制信息传输的导频映射类型信息。
例如，用于指示高优先级的UCI传输所对应的DCI为下述DCI：
特定DCI格式的DCI；
使用特定RNTI(例如MCS-C-RNTI)加扰的DCI；
DCI中配置的MCS采用低频谱效率的MCS表(例如MCS table index 3，MCS表3)；
则，用于指示低优先级的UCI传输所对应的DCI为下述DCI：
除了上述特定DCI格式之外的其他DCI格式的DCI；
除了上述特定RNTI之外，使用其他RNTI加扰的DCI；
DCI中配置的MCS不采用低频谱效率的MCS表。
所述UCI包含的信息包括混合自动重传请求确认(Hybrid Automatic Repeat request-ACK，HARQ-ACK)，信道状态信息(Channel State Information，CSI)，调度请求(Scheduling Request，SR)等。
可选的，UCI的优先级也可称为与UCI的业务类型相关，例如，eMBB业务的UCI和URLLC业务的UCI为不同优先级的UCI。
需要说明的是，用于指示不同业务类型的UCI传输所对应的DCI的目标参数不同，例如，用于指示eMBB业务的UCI传输的DCI的格式为DCI格式1，用于指示URLLC业务的UCI传输的DCI的格式为DCI格式2，则终端可以根据不同的DCI格式确定不同业务类型的UCI的不同优先级。
可选的，本公开的上述实施例中，所述目标信道包括：物理上行控制信道PUCCH或物理上行共享信道PUSCH。
作为一个实施例，在所述目标信道为PUCCH的情况下，所述方法还包括：
对不同优先级的UCI分别进行编码时，不同优先级的UCI使用不同的码率。
相应的，所述方法还包括：
根据第一缩放因子以及PUCCH资源对应的码率，确定不同优先级的UCI使用的码率；
或者，
根据无线资源控制RRC配置的不同优先级的UCI对应的码率，确定不同优先级的UCI使用的码率。
其中，所述第一缩放因子由无线资源控制RRC配置，或者由DCI指示，或者由协议规定。可选的，上述PUCCH资源对应的码率具体为：网络侧设备通过RRC信令为PUCCH资源配置的码率。
例如，网络侧设备通过RRC信令为PUCCH资源配置的不同的码率，不同优先级的UCI分别对应不同的码率。
再例如，高优先级的UCI使用该PUCCH资源对应的码率，低优先级的UCI使用的码率为该PUCCH资源对应的码率与第一缩放因子的乘积，此种情况下，第一缩放因子小于1。
再例如，低优先级的UCI使用该PUCCH资源对应的码率，高优先级的UCI使用的码率为该PUCCH资源对应的码率与第一缩放因子的乘积，此种情况下，第一缩放因子大于1。
作为另一个可选实施例，在所述目标信道为PUCCH，所述UCI的优先级至少包括第一优先级和第二优先级的情况下，所述方法还包括：
对不同优先级的UCI分别进行编码时，根据RRC配置的码率分配用于传输第一优先级的UCI的资源，剩余资源用于传输第二优先级的UCI；即第一优先级的UCI和第二优先级的UCI共同使用RRC配置的物理资源块PRB数。
其中，第一优先级高于第二优先级。
例如，对不同优先级的UCI分别进行编码时，第一优先级的UCI使用RRC配置的最大码率确定传输第一优先级的UCI所需的资源单元RE，并确定所述RRC配置的物理资源块中除传输第一优先级的UCI所需的RE之外的剩余RE用于传输第二优先级的UCI；
当剩余的资源不足以传输第二优先级的UCI时，全部或者部分丢弃第二优先级UCI的传输。当部分丢弃的时候，按照某配置或者预定义的UCI丢弃规则进行丢弃，如优先丢弃CSI part 2(第2部分CSI)，然后CSI part 1(第1部分CSI)，然后HARQ-ACK或SR等。
作为另一个实施例，在所述目标信道为PUCCH的情况下，步骤101包括：
对不同优先级的UCI分别进行编码，编码之后的不同优先级的UCI采用 时域优先的映射方法映射到物理资源上并在所述目标信道上传输。
例如，不同优先级的UCI为低优先级HARQ-ACK(例如eMBB HARQ-ACK)和高优先级HARQ-ACK(例如URLLC HARQ-ACK)；当低优先级HARQ-ACK和高优先级HARQ-ACK复用在一起时，如果终端漏检了低优先级业务(例如eMBB业务)的最后一个PDSCH所对应的PDCCH，就会使得基站和终端对低优先级HARQ-ACK的比特数理解不一致，PUCCH所使用的PRB资源不一致，因此，为了减少低优先级PDCCH漏检对高优先级HARQ-ACK反馈的影响，将高优先级HARQ-ACK和低优先级HARQ-ACK分别编码，且采用时域优先的方式映射到物理资源上，可以保证基站正确接收到高优先级HARQ-ACK反馈。
需要说明的是，对于采用时域优先的映射方式映射到物理资源的UCI，本公开实施例不对UCI的编码速率和/或beta_offset进行限定，即对于对于采用时域优先的映射方式传输的不同优先级的UCI，不同优先级的UCI分开编码时，可以采用相同的码率，也可以采用不同的码率，可以采用相同的beta_offset，也可以采用不同的beta_offset。
如图2所示，承载低优先级HARQ-ACK的PUCCH与多个时分复用的承载高优先级HARQ-ACK(分别为HARQ-ACK 1和HARQ-ACK 2)的PUCCH时域重叠，为了减少高优先级HARQ-ACK的反馈时延，将低优先级HARQ-ACK复用在高优先级PUCCH上，同时考虑终端处理时间问题，将低优先级HARQ-ACK与第一个满足复用时间条件的高优先级PUCCH进行复用。
当低优先级HARQ-ACK与高优先级HARQ-ACK 2复用在一个PUCCH上传输时，低优先级HARQ-ACK与高优先级HARQ-ACK 2分别编码，两者使用不同的码率确定其使用的RE数目。低优先级HARQ-ACK复用在URLLC PUCCH上传输时，高优先级HARQ-ACK2采用RRC配置的该PUCCH资源对应的maxcoderate(最大码率)确定其所占用的RE，eMBB HARQ采用协议规定或RRC配置的scaling factor(第一缩放因子)确定其码率为maxcoderate*scaling factor，例如scaling factor＝0.1。终端通过URLCC HARQ-ACK比特数和其码率确定以及低优先级HARQ-ACK比特数和其码 率确定所使用的PRB数(确定的PRB数小于或者等于RRC配置的该PUCCH资源的最大PRB数)。
如果终端使用了最大PRB数量的PRB传输时，仍然超出上述各自的码率(此时表明终端需要更多的PRB)，则终端采用最大码率传输高优先级HARQ-ACK，并丢弃部分低优先级HARQ-ACK比特或者将低优先级HARQ-ACK比特压缩(如，码块组(code block group，CBG)粒度的HARQ-ACK回退至传输块(transmission block，TB)粒度的HARQ-ACK(按照TB数确定反馈HARQ-ACK比特数)；或者，将HARQ-ACK绑定至满足eMBB的HARQ-ACK码率要求。
另外，PDSCH反馈中，由于在同一时间需要反馈多个PDCCH调度PDSCH的HARQ-ACK，为了防止PDCCH漏检的情况，引入了累积下行分配指示(counter Downlink assignment index，counter DAI)的机制确定终端需要反馈的HARQ-ACK比特数，但是仍然有可能漏检了最后一个PDCCH，这样终端反馈的HARQ-ACK的比特数和基站的理解的比特数就不一致，导致基站无法正确接收HARQ-ACK反馈。例如，低优先级的BLER target(误块率目标值)为10^-2，高优先级的BLER target为10^-5/-6，则低优先级PDCCH漏检概率为1％，高优先级PDCCH的漏检概率为0.001％，因此如果低优先级最后一个PDCCH漏检，低优先级HARQ-ACK和高优先级HARQ-ACK复用在一起时，就会使得基站和UE对HARQ-ACK的比特数理解不一致，PUCCH所使用的PRB资源不一致，因此，为了减少低优先级PDCCH漏检对高优先级HARQ-ACK反馈的影响，如图3所示，将高优先级HARQ-ACK和低优先级HARQ-ACK分别编码，且采用时域优先的方式映射到物理资源上。保证基站能够正确接收到高优先级HARQ-ACK反馈。
作为又一个实施例，在所述目标信道为PUSCH的情况下，所述方法还包括：
对不同优先级的UCI分别进行编码时，不同优先级的UCI使用不同的资源占用比偏移值beta_offset，确定各个UCI所使用的资源粒子RE和码率。
相应的，所述方法还包括：
根据RRC配置或DCI指示的beta_offset以及预设beta_offset，确定不同 优先级的UCI使用的beta_offset；例如，高优先级的UCI采用RRC配置或DCI指示的beta_offset，低优先级的UCI采用预设beta_offset(预设beta_offset为固定beta_offset)，例如，预设beta_offset等于1。此种方式通常适用于低优先级的UCI和高优先级的UCI复用在高优先级PUSCH上。
或者，根据RRC配置的不同优先级的UCI对应的beta_offset，确定不同优先级的UCI使用的beta_offset；例如，RRC分别配置高优先级的UCI的beta_offset和低优先级的UCI的beta_offset。
或者，根据DCI(例如上行授权UL grant)中指示的不同优先级的UCI对应的beta_offset，确定不同优先级的UCI使用的beta_offset；例如，DCI分别指示高优先级的UCI的beta_offset和低优先级的UCI的beta_offset。例如，通过DCI通过表1的形式指示beta_offset，其中DCI中的beta_offset指示每个状态指示不同优先级(例如高优先级业务URLLC和低优先级业务eMBB)的beta_offset，同一优先级下又包含不同的UCI类型(如HARQ-ACK，CSI part1和CSI part 2)和比特数(如小于3比特，大于3比特且小于12比特，大于11比特等)，其中述优先级可以由用于指示所述UCI传输所对应的下行控制信息DCI的目标参数确定。表格中
Figure PCTCN2019126572-appb-000001
和
Figure PCTCN2019126572-appb-000002
分别表示小于等于2比特HARQ-ACK所对应的索引，大于2比特且小于12比特HARQ-ACK所对应的索引，大于11比特HARQ-ACK所对应的索引，
Figure PCTCN2019126572-appb-000003
和
Figure PCTCN2019126572-appb-000004
分别表示小于等于11比特CSI part 1和CSI part 2所对应的索引，
Figure PCTCN2019126572-appb-000005
和
Figure PCTCN2019126572-appb-000006
分别表示大于11比特CSI part 1和CSI part 2所对应的索引。
表1
Figure PCTCN2019126572-appb-000007
或者，根据DCI中指示的第一优先级的UCI对应的beta_offset以及RRC配置的第二优先级的UCI对应的beta_offset，确定不同优先级的UCI使用的 beta_offset；所述UCI的优先级至少包括第一优先级和第二优先级；例如，RRC配置低优先级的UCI的beta_offset，DCI中指示高优先级的UCI的beta_offset。
或者，根据第二缩放因子以及RRC配置或DCI指示的第一优先级的UCI的beta_offset，确定不同优先级的UCI使用的beta_offset；其中，所述第二缩放因子由RRC配置，或者由DCI指示，或者由协议规定；例如，RRC配置或DCI指示高优先级的UCI的beta_offset；低优先级的UCI的beta_offset等于RRC配置或DCI指示的beta_offset与第二缩放因子(scaling factor)的乘积；再例如，RRC配置或DCI指示低优先级的UCI的beta_offset；高优先级的UCI的beta_offset等于RRC配置或DCI指示的beta_offset与第二缩放因子(scaling factor)的乘积。
如图4所示，低优先级HARQ-ACK、高优先级HARQ-ACK以及高优先级PUSCH在时域重叠，将低优先级HARQ-ACK与高优先级HARQ-ACK复用在PUSCH上，终端使用不同的beta_offset确定高优先级HARQ-ACK和低优先级HARQ-ACK所占的RE，其中高优先级HARQ-ACK对应的beta_offset比高优先级HARQ-ACK对应的beta_offset大，并对低优先级HARQ-ACK与该高优先级HARQ-ACK分别编码、映射。
作为一种实现方式，上述提及的高优先级HARQ-ACK可以为URLLC HARQ-ACK，低优先级HARQ-ACK可以为eMBB HARQ-ACK；
上述提及的高优先级UCI可以为URLLC CSI，低优先级UCI可以为eMBB CSI。
上述提及的高优先级UCI可以为URLLC CSI，低优先级UCI可以为eMBB HARQ-ACK。
作为另一个实现方式，通过DCI格式、控制资源集和/或搜索空间等来确定HARQ-ACK的优先级，具体的确定UCI的优先级的方式在上述实施例中已详细描述，在此不重复赘述。
综上，本公开的上述实施例通过对不同优先级的UCI在同一目标信道传输时的编码方式、码率等进行定义或配置，可以实现高优先级的UCI的可靠性，提高资源利用率。
如图5所示，本公开实施例还提供一种终端500，包括：
编码传输模块501，用于在不同优先级的UCI在同一目标信道传输的情况下，对不同优先级的UCI分别进行编码之后在所述目标信道上传输；
其中，所述UCI的优先级由下行控制信息DCI的目标参数和/或UCI包含的信息确定；DCI为用于指示所述UCI传输所对应的DCI。
可选的，本公开的上述实施例中，所述目标信道包括：物理上行控制信道PUCCH或物理上行共享信道PUSCH。
可选的，本公开的上述实施例中，所述终端还包括：
第一编码模块，用于在所述目标信道为PUCCH的情况下，对不同优先级的UCI分别进行编码时，不同优先级的UCI使用不同的码率。
可选的，本公开的上述实施例中，所述终端还包括：
码率确定模块，用于根据第一缩放因子以及PUCCH资源对应的码率，确定不同优先级的UCI使用的码率；或者，用于根据无线资源控制RRC配置的不同优先级的UCI对应的码率，确定不同优先级的UCI使用的码率；
其中，所述第一缩放因子由无线资源控制RRC配置，或者由DCI指示，或者由协议规定。
可选的，本公开的上述实施例中，所述终端还包括：
第二编码模块，用于在所述目标信道为PUCCH，所述UCI的优先级至少包括第一优先级和第二优先级的情况下，对不同优先级的UCI分别进行编码时，根据RRC配置的码率分配用于传输第一优先级的UCI的资源，剩余资源用于传输第二优先级的UCI；
其中，第一优先级高于第二优先级。
可选的，本公开的上述实施例中，所述编码传输模块包括：
编码传输子模块，用于对不同优先级的UCI分别进行编码，编码之后的不同优先级的UCI采用时域优先的映射方法映射到物理资源上并在所述目标信道上传输。
可选的，本公开的上述实施例中，所述终端还包括：
第三编码模块，用于在所述目标信道为PUSCH的情况下，对不同优先级的UCI分别进行编码时，不同优先级的UCI使用不同的资源占用比偏移值 beta_offset，确定各个UCI所使用的资源粒子和码率。
可选的，本公开的上述实施例中，所述终端还包括：
偏移值确定模块，用于根据RRC配置或DCI指示的beta_offset以及预设beta_offset，确定不同优先级的UCI使用的beta_offset；
或者，
用于根据RRC配置的不同优先级的UCI对应的beta_offset，确定不同优先级的UCI使用的beta_offset；
或者，
用于根据DCI中指示的不同优先级的UCI对应的beta_offset，确定不同优先级的UCI使用的beta_offset；
或者，
用于根据DCI中指示的第一优先级的UCI对应的beta_offset以及RRC配置的第二优先级的UCI对应的beta_offset，确定不同优先级的UCI使用的beta_offset；所述UCI的优先级至少包括第一优先级和第二优先级；
或者，
用于根据第二缩放因子以及RRC配置或DCI指示的第一优先级的UCI的beta_offset，确定不同优先级的UCI使用的beta_offset；其中，所述第二缩放因子由RRC配置，或者由DCI指示，或者由协议规定。
本公开实施例提供的终端能够实现图1至图4的方法实施例中终端实现的各个过程，为避免重复，这里不再赘述。
综上，本公开的上述实施例通过对不同优先级的UCI在同一目标信道传输时的编码方式、码率等进行定义或配置，可以实现高优先级的UCI的可靠性，提高资源利用率。
需要说明的是，本公开实施例提供的终端是能够执行上述上行控制信息UCI的传输方法的终端，则上述上行控制信息UCI的传输方法的所有实施例均适用于该终端，且均能达到相同或相似的有益效果。
图6为实现本公开各个实施例的一种终端的硬件结构示意图，该终端600包括但不限于：射频单元601、网络模块602、音频输出单元603、输入单元604、传感器605、显示单元606、用户输入单元607、接口单元608、存储器 609、处理器610、以及电源611等部件。本领域技术人员可以理解，图6中示出的终端结构并不构成对终端的限定，终端可以包括比图示更多或更少的部件，或者组合某些部件，或者不同的部件布置。在本公开实施例中，终端包括但不限于手机、平板电脑、笔记本电脑、掌上电脑、车载终端、可穿戴设备、以及计步器等。
处理器610，用于在不同优先级的UCI在同一目标信道传输的情况下，对不同优先级的UCI分别进行编码，
射频单元601，用于在对不同优先级的UCI分别进行编码之后在所述目标信道上传输；
其中，所述UCI的优先级由下行控制信息DCI的目标参数和/或UCI包含的信息确定；DCI为用于指示所述UCI传输所对应的DCI。
综上，本公开的上述实施例通过对不同优先级的UCI在同一目标信道传输时的编码方式、码率等进行定义或配置，可以实现高优先级的UCI的可靠性，提高资源利用率。
需要说明的是，本公开实施例提供的终端是能够执行上述上行控制信息UCI的传输方法的终端，则上述上行控制信息UCI的传输方法的所有实施例均适用于该终端，且均能达到相同或相似的有益效果。
应理解的是，本公开实施例中，射频单元601可用于收发信息或通话过程中，信号的接收和发送，具体的，将来自基站的下行数据接收后，给处理器610处理；另外，将上行的数据发送给基站。通常，射频单元601包括但不限于天线、至少一个放大器、收发信机、耦合器、低噪声放大器、双工器等。此外，射频单元601还可以通过无线通信系统与网络和其他设备通信。
终端通过网络模块602为用户提供了无线的宽带互联网访问，如帮助用户收发电子邮件、浏览网页和访问流式媒体等。
音频输出单元603可以将射频单元601或网络模块602接收的或者在存储器609中存储的音频数据转换成音频信号并且输出为声音。而且，音频输出单元603还可以提供与终端600执行的特定功能相关的音频输出(例如，呼叫信号接收声音、消息接收声音等等)。音频输出单元603包括扬声器、蜂鸣器以及受话器等。
输入单元604用于接收音频或视频信号。输入单元604可以包括图形处理器(Graphics Processing Unit，GPU)6041和麦克风6042，图形处理器6041对在视频捕获模式或图像捕获模式中由图像捕获装置(如摄像头)获得的静态图片或视频的图像数据进行处理。处理后的图像帧可以显示在显示单元606上。经图形处理器6041处理后的图像帧可以存储在存储器609(或其它存储介质)中或者经由射频单元601或网络模块602进行发送。麦克风6042可以接收声音，并且能够将这样的声音处理为音频数据。处理后的音频数据可以在电话通话模式的情况下转换为可经由射频单元601发送到移动通信基站的格式输出。
终端600还包括至少一种传感器605，比如光传感器、运动传感器以及其他传感器。具体地，光传感器包括环境光传感器及接近传感器，其中，环境光传感器可根据环境光线的明暗来调节显示面板6061的亮度，接近传感器可在终端600移动到耳边时，关闭显示面板6061和/或背光。作为运动传感器的一种，加速计传感器可检测各个方向上(一般为三轴)加速度的大小，静止时可检测出重力的大小及方向，可用于识别终端姿态(比如横竖屏切换、相关游戏、磁力计姿态校准)、振动识别相关功能(比如计步器、敲击)等；传感器605还可以包括指纹传感器、压力传感器、虹膜传感器、分子传感器、陀螺仪、气压计、湿度计、温度计、红外线传感器等，在此不再赘述。
显示单元606用于显示由用户输入的信息或提供给用户的信息。显示单元606可包括显示面板6061，可以采用液晶显示器(Liquid Crystal Display，LCD)、有机发光二极管(Organic Light-Emitting Diode,OLED)等形式来配置显示面板6061。
用户输入单元607可用于接收输入的数字或字符信息，以及产生与终端的用户设置以及功能控制有关的键信号输入。具体地，用户输入单元607包括触控面板6071以及其他输入设备6072。触控面板6071，也称为触摸屏，可收集用户在其上或附近的触摸操作(比如用户使用手指、触笔等任何适合的物体或附件在触控面板6071上或在触控面板6071附近的操作)。触控面板6071可包括触摸检测装置和触摸控制器两个部分。其中，触摸检测装置检测用户的触摸方位，并检测触摸操作带来的信号，将信号传送给触摸控制器； 触摸控制器从触摸检测装置上接收触摸信息，并将它转换成触点坐标，再送给处理器610，接收处理器610发来的命令并加以执行。此外，可以采用电阻式、电容式、红外线以及表面声波等多种类型实现触控面板6071。除了触控面板6071，用户输入单元607还可以包括其他输入设备6072。具体地，其他输入设备6072可以包括但不限于物理键盘、功能键(比如音量控制按键、开关按键等)、轨迹球、鼠标、操作杆，在此不再赘述。
进一步的，触控面板6071可覆盖在显示面板6061上，当触控面板6071检测到在其上或附近的触摸操作后，传送给处理器610以确定触摸事件的类型，随后处理器610根据触摸事件的类型在显示面板6061上提供相应的视觉输出。虽然在图6中，触控面板6071与显示面板6061是作为两个独立的部件来实现终端的输入和输出功能，但是在某些实施例中，可以将触控面板6071与显示面板6061集成而实现终端的输入和输出功能，具体此处不做限定。
接口单元608为外部装置与终端600连接的接口。例如，外部装置可以包括有线或无线头戴式耳机端口、外部电源(或电池充电器)端口、有线或无线数据端口、存储卡端口、用于连接具有识别模块的装置的端口、音频输入/输出(input/output，I/O)端口、视频I/O端口、耳机端口等等。接口单元608可以用于接收来自外部装置的输入(例如，数据信息、电力等等)并且将接收到的输入传输到终端600内的一个或多个元件或者可以用于在终端600和外部装置之间传输数据。
存储器609可用于存储软件程序以及各种数据。存储器609可主要包括存储程序区和存储数据区，其中，存储程序区可存储操作系统、至少一个功能所需的应用程序(比如声音播放功能、图像播放功能等)等；存储数据区可存储根据手机的使用所创建的数据(比如音频数据、电话本等)等。此外，存储器609可以包括高速随机存取存储器，还可以包括非易失性存储器，例如至少一个磁盘存储器件、闪存器件、或其他易失性固态存储器件。
处理器610是终端的控制中心，利用各种接口和线路连接整个终端的各个部分，通过运行或执行存储在存储器609内的软件程序和/或模块，以及调用存储在存储器609内的数据，执行终端的各种功能和处理数据，从而对终端进行整体监控。处理器610可包括一个或多个处理单元；可选的，处理器 610可集成应用处理器和调制解调处理器，其中，应用处理器主要处理操作系统、用户界面和应用程序等，调制解调处理器主要处理无线通信。可以理解的是，上述调制解调处理器也可以不集成到处理器610中。
终端600还可以包括给各个部件供电的电源611(比如电池)，可选的，电源611可以通过电源管理系统与处理器610逻辑相连，从而通过电源管理系统实现管理充电、放电、以及功耗管理等功能。
另外，终端600包括一些未示出的功能模块，在此不再赘述。
可选的，本公开实施例还提供一种终端，包括处理器，存储器，存储在存储器上并可在所述处理器上运行的计算机程序，该计算机程序被处理器执行时实现上述上行控制信息UCI的传输方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
本公开实施例还提供一种计算机可读存储介质，计算机可读存储介质上存储有计算机程序，该计算机程序被处理器执行时实现上述上行控制信息UCI的传输方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。其中，所述的计算机可读存储介质，如只读存储器(Read-Only Memory，简称ROM)、随机存取存储器(Random Access Memory，简称RAM)、磁碟或者光盘等。
需要说明的是，在本文中，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、物品或者装置不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、物品或者装置所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括该要素的过程、方法、物品或者装置中还存在另外的相同要素。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到上述实施例方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件，但很多情况下前者是更佳的实施方式。基于这样的理解，本公开的技术方案本质上或者说对相关技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中，包括若干指令用以使得一台终端(可以是手机，计算机，服务器， 空调器，或者网络设备等)执行本公开各个实施例所述的方法。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本公开的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的实施例中，应该理解到，所揭露的装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些要素可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本公开各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本公开的技术方案本质上或者说对相关技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本公开各个实施例所述方法的全部或部分步骤。而前述的存储 介质包括：U盘、移动硬盘、ROM、RAM、磁碟或者光盘等各种可以存储程序代码的介质。
本领域普通技术人员可以理解实现上述实施例方法中的全部或部分流程，是可以通过计算机程序来控制相关的硬件来完成，所述的程序可存储于计算机可读取存储介质中，该程序在执行时，可包括如上述各方法的实施例的流程。其中，所述的存储介质可为磁碟、光盘、只读存储器(Read-Only Memory，ROM)或随机存取存储器(Random Access Memory，RAM)等。
可以理解的是，本公开实施例描述的这些实施例可以用硬件、软件、固件、中间件、微码或其组合来实现。对于硬件实现，处理单元可以实现在一个或多个专用集成电路(Application Specific Integrated Circuits，ASIC)、数字信号处理器(Digital Signal Processor，DSP)、数字信号处理设备(DSP Device，DSPD)、可编程逻辑设备(Programmable Logic Device，PLD)、现场可编程门阵列(Field-Programmable Gate Array，FPGA)、通用处理器、控制器、微控制器、微处理器、用于执行本公开所述功能的其它电子单元或其组合中。
对于软件实现，可通过执行本公开实施例所述功能的模块(例如过程、函数等)来实现本公开实施例所述的技术。软件代码可存储在存储器中并通过处理器执行。存储器可以在处理器中或在处理器外部实现。
上面结合附图对本公开的实施例进行了描述，但是本公开并不局限于上述的具体实施方式，上述的具体实施方式仅仅是示意性的，而不是限制性的，本领域的普通技术人员在本公开的启示下，在不脱离本公开宗旨和权利要求所保护的范围情况下，还可做出很多形式，均属于本公开的保护之内。
以上所述，仅为本公开的具体实施方式，但本公开的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本公开揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本公开的保护范围之内。因此，本公开的保护范围应以权利要求的保护范围为准。

Claims (18)

  1. 一种上行控制信息UCI的传输方法，应用于终端，包括：
    在不同优先级的UCI在同一目标信道传输的情况下，对不同优先级的UCI分别进行编码之后在所述目标信道上传输；
    其中，所述UCI的优先级由下行控制信息DCI的目标参数和/或UCI包含的信息确定；DCI为用于指示所述UCI传输所对应的DCI。
  2. 根据权利要求1所述的方法，其中，所述目标信道包括：物理上行控制信道PUCCH或物理上行共享信道PUSCH。
  3. 根据权利要求2所述的方法，其中，在所述目标信道为PUCCH的情况下，所述方法还包括：
    对不同优先级的UCI分别进行编码时，不同优先级的UCI使用不同的码率。
  4. 根据权利要求3所述的方法，还包括：
    根据第一缩放因子以及PUCCH资源对应的码率，确定不同优先级的UCI使用的码率；其中，所述第一缩放因子由无线资源控制RRC配置，或者由DCI指示，或者由协议规定；
    或者，
    根据无线资源控制RRC配置的不同优先级的UCI对应的码率，确定不同优先级的UCI使用的码率。
  5. 根据权利要求2所述的方法，其中，在所述目标信道为PUCCH，所述UCI的优先级至少包括第一优先级和第二优先级的情况下，所述方法还包括：
    对不同优先级的UCI分别进行编码时，根据RRC配置的码率分配用于传输第一优先级的UCI的资源，剩余资源用于传输第二优先级的UCI；
    其中，第一优先级高于第二优先级。
  6. 根据权利要求2所述的方法，其中，在所述目标信道为PUCCH的情况下，所述对不同优先级的UCI分别进行编码之后在所述目标信道上传输，包括：
    对不同优先级的UCI分别进行编码，编码之后的不同优先级的UCI采用时域优先的映射方法映射到物理资源上并在所述目标信道上传输。
  7. 根据权利要求2所述的方法，其中，在所述目标信道为PUSCH的情况下，所述方法还包括：
    对不同优先级的UCI分别进行编码时，不同优先级的UCI使用不同的资源占用比偏移值beta_offset，确定各个UCI所使用的资源粒子和码率。
  8. 根据权利要求7所述的方法，还包括：
    根据RRC配置或DCI指示的beta_offset以及预设beta_offset，确定不同优先级的UCI使用的beta_offset；
    或者，
    根据RRC配置的不同优先级的UCI对应的beta_offset，确定不同优先级的UCI使用的beta_offset；
    或者，
    根据DCI中指示的不同优先级的UCI对应的beta_offset，确定不同优先级的UCI使用的beta_offset；
    或者，
    根据DCI中指示的第一优先级的UCI对应的beta_offset以及RRC配置的第二优先级的UCI对应的beta_offset，确定不同优先级的UCI使用的beta_offset；所述UCI的优先级至少包括第一优先级和第二优先级；
    或者，
    根据第二缩放因子以及RRC配置或DCI指示的第一优先级的UCI的beta_offset，确定不同优先级的UCI使用的beta_offset；其中，所述第二缩放因子由RRC配置，或者由DCI指示，或者由协议规定。
  9. 一种终端，包括：
    编码传输模块，用于在不同优先级的上行控制信息UCI在同一目标信道传输的情况下，对不同优先级的UCI分别进行编码之后在所述目标信道上传输；
    其中，所述UCI的优先级由下行控制信息DCI的目标参数和/或UCI包含的信息确定；DCI为用于指示所述UCI传输所对应的DCI。
  10. 根据权利要求9所述的终端，其中，所述目标信道包括：物理上行控制信道PUCCH或物理上行共享信道PUSCH。
  11. 根据权利要求10所述的终端，还包括：
    第一编码模块，用于在所述目标信道为PUCCH的情况下，对不同优先级的UCI分别进行编码时，不同优先级的UCI使用不同的码率。
  12. 根据权利要求11所述的终端，还包括：
    码率确定模块，用于根据第一缩放因子以及PUCCH资源对应的码率，确定不同优先级的UCI使用的码率；或者，用于根据无线资源控制RRC配置的不同优先级的UCI对应的码率，确定不同优先级的UCI使用的码率；
    其中，所述第一缩放因子由无线资源控制RRC配置，或者由DCI指示，或者由协议规定。
  13. 根据权利要求10所述的终端，还包括：
    第二编码模块，用于在所述目标信道为PUCCH，所述UCI的优先级至少包括第一优先级和第二优先级的情况下，对不同优先级的UCI分别进行编码时，根据RRC配置的码率分配用于传输第一优先级的UCI的资源，剩余资源用于传输第二优先级的UCI；
    其中，第一优先级高于第二优先级。
  14. 根据权利要求10所述的终端，其中，所述编码传输模块包括：
    编码传输子模块，用于对不同优先级的UCI分别进行编码，编码之后的不同优先级的UCI采用时域优先的映射方法映射到物理资源上并在所述目标信道上传输。
  15. 根据权利要求10所述的终端，还包括：
    第三编码模块，用于在所述目标信道为PUSCH的情况下，对不同优先级的UCI分别进行编码时，不同优先级的UCI使用不同的资源占用比偏移值beta_offset，确定各个UCI所使用的资源粒子和码率。
  16. 根据权利要求15所述的终端，还包括：
    偏移值确定模块，用于根据RRC配置或DCI指示的beta_offset以及预设beta_offset，确定不同优先级的UCI使用的beta_offset；
    或者，
    用于根据RRC配置的不同优先级的UCI对应的beta_offset，确定不同优先级的UCI使用的beta_offset；
    或者，
    用于根据DCI中指示的不同优先级的UCI对应的beta_offset，确定不同优先级的UCI使用的beta_offset；
    或者，
    用于根据DCI中指示的第一优先级的UCI对应的beta_offset以及RRC配置的第二优先级的UCI对应的beta_offset，确定不同优先级的UCI使用的beta_offset；所述UCI的优先级至少包括第一优先级和第二优先级；
    或者，
    用于根据第二缩放因子以及RRC配置或DCI指示的第一优先级的UCI的beta_offset，确定不同优先级的UCI使用的beta_offset；其中，所述第二缩放因子由RRC配置，或者由DCI指示，或者由协议规定。
  17. 一种终端，包括处理器、存储器及存储在所述存储器上并可在所述处理器上运行的计算机程序，所述计算机程序被所述处理器执行时实现如权利要求1至8中任一项所述的上行控制信息UCI的传输方法的步骤。
  18. 一种计算机可读存储介质，所述计算机可读存储介质上存储计算机程序，所述计算机程序被处理器执行时实现如权利要求1至8中任一项所述的上行控制信息UCI的传输方法的步骤。
PCT/CN2019/126572 2018-12-25 2019-12-19 上行控制信息uci的传输方法及终端 WO2020135214A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
KR1020217021383A KR102512967B1 (ko) 2018-12-25 2019-12-19 상향 링크 제어 정보 (uci)의 전송 방법 및 단말
JP2021535231A JP7225405B2 (ja) 2018-12-25 2019-12-19 上りリンク制御情報ｕｃｉの伝送方法及び端末
EP19901441.6A EP3905570A4 (en) 2018-12-25 2019-12-19 METHOD AND APPARATUS FOR TRANSMITTING UPLINK CONTROL (UCI) INFORMATION
US17/356,890 US11968676B2 (en) 2018-12-25 2021-06-24 Uplink control information transmission method and terminal

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201811594137.9 2018-12-25
CN201811594137.9A CN111314033B (zh) 2018-12-25 2018-12-25 一种上行控制信息uci的传输方法及终端

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/356,890 Continuation US11968676B2 (en) 2018-12-25 2021-06-24 Uplink control information transmission method and terminal

Publications (1)

Publication Number Publication Date
WO2020135214A1 true WO2020135214A1 (zh) 2020-07-02

Family

ID=71126333

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/126572 WO2020135214A1 (zh) 2018-12-25 2019-12-19 上行控制信息uci的传输方法及终端

Country Status (6)

Country Link
US (1) US11968676B2 (zh)
EP (1) EP3905570A4 (zh)
JP (1) JP7225405B2 (zh)
KR (1) KR102512967B1 (zh)
CN (1) CN111314033B (zh)
WO (1) WO2020135214A1 (zh)

Cited By (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113498195A (zh) * 2021-03-18 2021-10-12 上海移远通信技术股份有限公司 一种被用于无线通信的节点中的方法和装置
CN114257360A (zh) * 2020-09-24 2022-03-29 维沃移动通信有限公司 Harq-ack处理方法、装置及相关设备
CN114902602A (zh) * 2020-08-06 2022-08-12 Lg 电子株式会社 在无线通信系统中发送和接收信号的方法和设备
WO2022234515A1 (en) * 2021-05-05 2022-11-10 Lenovo (Singapore) Pte. Ltd. Determining a number of prbs for a pucch transmission
WO2023052134A1 (en) * 2021-09-30 2023-04-06 Sony Group Corporation Communications devices, network nodes, circuitry, systems and methods
EP4171146A4 (en) * 2020-07-13 2023-12-20 Vivo Mobile Communication Co., Ltd. METHOD AND APPARATUS FOR INFORMATION MULTIPLEXING, AND USER EQUIPMENT
EP4190099A4 (en) * 2020-07-27 2024-02-21 Samsung Electronics Co Ltd MULTIPLEXING OF INFORMATION WITH DIFFERENT PRIORITY VALUES
EP4195839A4 (en) * 2020-08-06 2024-03-06 Ntt Docomo Inc TERMINAL, WIRELESS COMMUNICATION METHOD AND BASE STATION

Families Citing this family (38)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11323231B2 (en) * 2019-02-12 2022-05-03 Samsung Electronics Co., Ltd. Adapting a number of repetitions for a physical uplink control channel
US11451284B2 (en) * 2019-03-28 2022-09-20 Qualcomm Incorporated Multiplexing codebooks generated for transmissions having different service types
EP3949190A1 (en) * 2019-04-02 2022-02-09 Telefonaktiebolaget LM Ericsson (publ) Priority-dependent uci resource determination
US20210037555A1 (en) * 2019-07-29 2021-02-04 Samsung Electronics Co., Ltd. Scheduling for services with multiple priority types
WO2022006878A1 (en) * 2020-07-10 2022-01-13 JRD Communication (Shenzhen) Ltd. Intra-user equipment multiplexing method, user equipment, and radio node for enabling the method
CN113949483B (zh) * 2020-07-18 2023-04-07 上海朗帛通信技术有限公司 一种被用于无线通信的节点中的方法和装置
CN113965301B (zh) * 2020-07-21 2023-04-18 维沃移动通信有限公司 物理上行控制信道资源重叠的处理方法及装置
CN114070483A (zh) * 2020-08-03 2022-02-18 北京三星通信技术研究有限公司 上行传输方法和相应设备
CN114071744A (zh) * 2020-08-07 2022-02-18 中国移动通信有限公司研究院 物理上行控制信道的传输方法、终端及基站
CN114070525B (zh) * 2020-08-07 2023-06-06 维沃移动通信有限公司 传输方法及装置
CN114070526B (zh) * 2020-08-07 2023-04-25 维沃移动通信有限公司 信息确定方法、信息指示方法、终端及网络侧设备
CN114071585A (zh) * 2020-08-07 2022-02-18 中国移动通信有限公司研究院 物理上行控制信道的传输方法、终端及基站
CN114079553B (zh) * 2020-08-19 2023-02-21 维沃移动通信有限公司 上行传输方法、设备及可读存储介质
US11943805B2 (en) * 2020-09-18 2024-03-26 Qualcomm Incorporated Beta offset factor configuration for uplink control information multiplexing on a physical uplink shared channel
US20220095324A1 (en) * 2020-09-18 2022-03-24 Qualcomm Incorporated Transmission time implicitly triggering uci multiplexing on pusch with different priorities
CN114285536A (zh) * 2020-09-27 2022-04-05 上海朗帛通信技术有限公司 一种被用于无线通信的节点中的方法和装置
CN114257346B (zh) * 2020-09-23 2023-04-28 上海朗帛通信技术有限公司 一种被用于无线通信的节点中的方法和装置
EP4210408A4 (en) * 2020-09-23 2024-03-06 Shanghai Langbo Comm Tech Co Ltd METHOD AND APPARATUS FOR USE IN A WIRELESS COMMUNICATIONS NODE
WO2022082499A1 (zh) * 2020-10-21 2022-04-28 华为技术有限公司 一种上行控制信息的传输方法及装置
CN114614953A (zh) * 2020-12-09 2022-06-10 维沃移动通信有限公司 上行控制信息传输方法、装置、终端及网络侧设备
US11617166B2 (en) * 2021-01-04 2023-03-28 Qualcomm Incorporated Multiplexing higher priority and lower priority uplink control information on a physical uplink control channel
CN114765478B (zh) * 2021-01-11 2023-09-26 维沃移动通信有限公司 编码调制符号数的确定方法、装置及通信设备
WO2022151137A1 (en) * 2021-01-14 2022-07-21 Zte Corporation Multiplexing techniques for uplink control channels with different priorities
CN114765484A (zh) * 2021-01-15 2022-07-19 北京紫光展锐通信技术有限公司 Harq-ack传输方法、装置、用户侧设备和存储介质
WO2022155924A1 (zh) * 2021-01-22 2022-07-28 Oppo广东移动通信有限公司 无线通信方法、终端设备和网络设备
CN114793152A (zh) * 2021-01-26 2022-07-26 北京紫光展锐通信技术有限公司 一种上行控制信息的传输方法及相关装置
CN113489566B (zh) * 2021-03-31 2022-11-25 上海移远通信技术股份有限公司 一种用于无线通信的节点中的方法和装置
CN115174016B (zh) * 2021-04-02 2023-12-26 大唐移动通信设备有限公司 信息传输方法、装置、设备以及存储介质
CN115190599A (zh) * 2021-04-02 2022-10-14 大唐移动通信设备有限公司 一种上行信道的传输方法及装置
CN115225198A (zh) * 2021-04-16 2022-10-21 大唐移动通信设备有限公司 Uci的级联确定方法、装置、终端及网络侧设备
CN115250166A (zh) * 2021-04-26 2022-10-28 上海朗帛通信技术有限公司 一种被用于无线通信的节点中的方法和装置
CN115333681B (zh) * 2021-05-11 2024-05-07 大唐移动通信设备有限公司 信息传输方法、装置及存储介质
CN117178511A (zh) * 2021-06-25 2023-12-05 Oppo广东移动通信有限公司 无线通信方法、终端设备和网络设备
CN115603857B (zh) * 2021-07-08 2024-04-26 上海朗帛通信技术有限公司 一种被用于无线通信的节点中的方法和装置
CN115734375A (zh) * 2021-08-25 2023-03-03 中兴通讯股份有限公司 数据发送方法、数据接收方法、网络设备及存储介质
CN116489791A (zh) * 2022-01-11 2023-07-25 大唐移动通信设备有限公司 上行传输方法、终端设备和网络设备
CN117177375A (zh) * 2022-05-23 2023-12-05 中兴通讯股份有限公司 资源协调方法、电子设备、存储介质
WO2024072305A1 (en) * 2022-09-30 2024-04-04 Telefonaktiebolaget Lm Ericsson (Publ) Systems and methods for beta offset configuration for transmitting uplink control information

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102170647A (zh) * 2010-02-26 2011-08-31 电信科学技术研究院 上行数据信道资源复用类型的判断装置和方法
WO2015107600A1 (ja) * 2014-01-15 2015-07-23 日本電気株式会社 アップリンク制御情報を送信するための方法、無線端末、及び基地局

Family Cites Families (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
TWI628933B (zh) * 2009-10-01 2018-07-01 內數位專利控股公司 傳輸上鏈控制資訊的方法及系統
CN103391628B (zh) * 2012-05-09 2017-01-25 中国移动通信集团公司 一种载波聚合系统中信息传输方法及装置
WO2015139224A1 (en) 2014-03-19 2015-09-24 Telefonaktiebolaget L M Ericsson(Publ) Uplink power sharing in dual connectivity
CN106470089B (zh) * 2015-08-14 2021-05-11 中兴通讯股份有限公司 一种上行控制信息的发送方法及装置
EP3403362B1 (en) * 2016-01-13 2020-10-28 LG Electronics Inc. -1- Method and user equipment for receiving downlink channel, and method and base station for transmitting downlink channel
WO2017189034A1 (en) * 2016-04-29 2017-11-02 Intel IP Corporation Systems, methods and devices for uplink control information enhancement
US10492184B2 (en) * 2016-12-09 2019-11-26 Samsung Electronics Co., Ltd. Multiplexing control information in a physical uplink data channel
US10749640B2 (en) * 2017-03-24 2020-08-18 Electronics And Telecommunications Research Institute Method and apparatus for transmitting and receiving uplink control channel in communication system
KR102201265B1 (ko) * 2017-11-15 2021-01-11 엘지전자 주식회사 무선 통신 시스템에서 장치의 상향링크 제어 정보 전송/수신 방법 및 장치
US20210377991A1 (en) 2017-12-27 2021-12-02 Ntt Docomo, Inc. Radio base station and radio communication method
MX2020005527A (es) * 2018-01-24 2020-08-20 Guangdong Oppo Mobile Telecommunications Corp Ltd Aparato y procedimiento de asignacion de canal de transmision para controlar una transmision sobre un canal de transmision.
US10880895B2 (en) * 2018-05-27 2020-12-29 Brian Gordaychik Variable length downlink control information formats for next generation radio technologies
KR20200054086A (ko) * 2018-11-09 2020-05-19 한국전자통신연구원 높은 신뢰 조건을 가지는 데이터 또는 제어 정보의 전송 방법 및 이를 위한 장치

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102170647A (zh) * 2010-02-26 2011-08-31 电信科学技术研究院 上行数据信道资源复用类型的判断装置和方法
WO2015107600A1 (ja) * 2014-01-15 2015-07-23 日本電気株式会社 アップリンク制御情報を送信するための方法、無線端末、及び基地局

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
HUAWEI, HISILICON: "UCI enhancements for URLLC", 3GPP TSG RAN WG1 MEETING #95 R1-1812222, 3RD GENERATION PARTNERSHIP PROJECT (3GPP),, 11 November 2018 (2018-11-11), Spokane, USA; 20181112 - 20181116, XP051554094 *
INTERDIGITAL, INC.: "Potential UCI enhancements for URLLC", 3GPP TSG RAN WG1 MEETING #95 R1-1813163 (R16 NR WI AI 72612 UCI FOR URLLC), 3RD GENERATION PARTNERSHIP PROJECT (3GPP), 11 November 2018 (2018-11-11), Spokane, USA; 20181112 - 20181116, XP051555156 *
See also references of EP3905570A4 *

Cited By (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP4171146A4 (en) * 2020-07-13 2023-12-20 Vivo Mobile Communication Co., Ltd. METHOD AND APPARATUS FOR INFORMATION MULTIPLEXING, AND USER EQUIPMENT
EP4190099A4 (en) * 2020-07-27 2024-02-21 Samsung Electronics Co Ltd MULTIPLEXING OF INFORMATION WITH DIFFERENT PRIORITY VALUES
CN114902602A (zh) * 2020-08-06 2022-08-12 Lg 电子株式会社 在无线通信系统中发送和接收信号的方法和设备
EP4195839A4 (en) * 2020-08-06 2024-03-06 Ntt Docomo Inc TERMINAL, WIRELESS COMMUNICATION METHOD AND BASE STATION
CN114257360A (zh) * 2020-09-24 2022-03-29 维沃移动通信有限公司 Harq-ack处理方法、装置及相关设备
CN114257360B (zh) * 2020-09-24 2023-12-05 维沃移动通信有限公司 Harq-ack处理方法、装置及相关设备
CN113498195A (zh) * 2021-03-18 2021-10-12 上海移远通信技术股份有限公司 一种被用于无线通信的节点中的方法和装置
WO2022234515A1 (en) * 2021-05-05 2022-11-10 Lenovo (Singapore) Pte. Ltd. Determining a number of prbs for a pucch transmission
WO2023052134A1 (en) * 2021-09-30 2023-04-06 Sony Group Corporation Communications devices, network nodes, circuitry, systems and methods
GB2624815A (en) * 2021-09-30 2024-05-29 Sony Group Corp Communications devices, network nodes, circuitry, systems and methods

Also Published As

Publication number Publication date
EP3905570A4 (en) 2022-02-16
KR20210096273A (ko) 2021-08-04
KR102512967B1 (ko) 2023-03-22
JP2022514038A (ja) 2022-02-09
US20210321394A1 (en) 2021-10-14
CN111314033B (zh) 2021-08-27
EP3905570A1 (en) 2021-11-03
JP7225405B2 (ja) 2023-02-20
US11968676B2 (en) 2024-04-23
CN111314033A (zh) 2020-06-19

Similar Documents

Publication Publication Date Title
WO2020135214A1 (zh) 上行控制信息uci的传输方法及终端
JP7258041B2 (ja) サイドリンクの伝送方法及び端末
CN111277388B (zh) Harq-ack码本生成方法、信息发送方法及设备
WO2021004316A1 (zh) Uci传输方法、接收方法、终端和网络设备
WO2019154009A1 (zh) 信道状态信息报告的传输方法及终端
WO2021218742A1 (zh) 信息反馈、资源调度方法、终端及网络设备
WO2020192718A1 (zh) 传输块大小确定方法和通信设备
WO2020143656A1 (zh) 混合自动重传请求确认的发送方法和终端
CN111447686B (zh) 一种harq-ack反馈方法、终端和网络设备
WO2021017976A1 (zh) 信息传输方法、装置、终端、设备及介质
WO2021057779A1 (zh) 混合自动重传请求应答反馈的获取、发送、终端及网络侧设备
CN111836310A (zh) Uci传输方法、终端和网络设备
WO2020119243A1 (zh) 物理上行控制信道传输方法、网络侧设备和终端
WO2021228078A1 (zh) 传输处理方法、装置及电子设备
WO2020088188A1 (zh) 传输方法、发送端设备、接收端设备及网络侧设备
US20220174701A1 (en) Information processing method, device, and computer-readable storage medium
US20220015124A1 (en) Downlink assignment index determining method, terminal and network device
WO2021147764A1 (zh) 信道状态信息csi上报方法、终端及计算机可读存储介质
WO2021000774A1 (zh) 信息传输、接收方法、终端及网络侧设备
WO2020134223A1 (zh) 上行控制信息的传输方法及终端
WO2019154358A1 (zh) Harq-ack码本的确定方法和终端
CN112769521A (zh) 传输块大小的确定方法及终端
WO2021228080A1 (zh) 信息传输、harq-ack码本的生成、传输方法及设备
WO2020147812A1 (zh) 数据反馈信息处理方法、装置、移动终端及存储介质
WO2021098629A1 (zh) Harq-ack处理方法及相关设备

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

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2021535231

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 20217021383

Country of ref document: KR

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2019901441

Country of ref document: EP

Effective date: 20210726