WO2022148368A1 - 信息传输方法、装置、终端及网络设备 - Google Patents

信息传输方法、装置、终端及网络设备 Download PDF

Info

Publication number
WO2022148368A1
WO2022148368A1 PCT/CN2022/070274 CN2022070274W WO2022148368A1 WO 2022148368 A1 WO2022148368 A1 WO 2022148368A1 CN 2022070274 W CN2022070274 W CN 2022070274W WO 2022148368 A1 WO2022148368 A1 WO 2022148368A1
Authority
WO
WIPO (PCT)
Prior art keywords
uci
pusch
transmission opportunity
pusch transmission
time
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/CN2022/070274
Other languages
English (en)
French (fr)
Inventor
陈晓航
李娜
潘学明
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Vivo Mobile Communication Co Ltd
Original Assignee
Vivo Mobile Communication Co Ltd
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 Vivo Mobile Communication Co Ltd filed Critical Vivo Mobile Communication Co Ltd
Publication of WO2022148368A1 publication Critical patent/WO2022148368A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

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/0091—Signalling for the administration of the divided path, e.g. signalling of configuration information
    • H04L5/0094—Indication of how sub-channels of the path are allocated
    • 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
    • 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
    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • 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/21—Control channels or signalling for resource management in the uplink direction of a wireless link, i.e. towards the network

Definitions

  • the present application belongs to the field of communication technologies, and specifically relates to an information transmission method, device, terminal and network equipment.
  • the Physical Uplink Sharing Channel can perform repeated transmissions (Repetitions) for multiple time slots or symbols in the time domain, in order to improve the reliability of transmission.
  • the terminal enables the function of skipping uplink transmission (ie UL skipping)
  • the PUSCH performs repeated transmission
  • the terminal will not perform repeated transmission of the PUSCH;
  • the terminal Even if there is no data to be transmitted in the terminal's data memory, the terminal still multiplexes the Uplink Control Information (UCI) on the PUSCH.
  • the PUSCH carries padding data.
  • the terminal determines whether to transmit the PUSCH repeated transmission, there is no conflict between the repeated transmission of the PUCCH and the PUSCH, and if there is no data transmission to be transmitted in the terminal data memory, the terminal will determine not to perform the repeated transmission of the PUSCH. However, if there is a conflict between the PUCCH and one or more of the PUSCH retransmission resources during the repeated PUSCH transmission, the terminal cannot multiplex the UCI on the conflicting PUSCH retransmission resources, resulting in the failure of the UCI transmission.
  • the embodiments of the present application provide an information transmission method, apparatus, terminal, and network equipment, which can solve the problem of UCI transmission failure caused by the conflict of retransmission resources between PUCCH and PUSCH carrying UCI.
  • an embodiment of the present application provides an information transmission method, and the method includes:
  • the first uplink control information UCI is transmitted on the first physical uplink shared channel PUSCH transmission opportunity, or the receiving timing of the downlink control signaling for scheduling the second UCI meets the preset conditions, if the physical uplink carrying the second UCI If there is a conflict between the control channel PUCCH and the second PUSCH transmission opportunity, the second UCI is sent on the second PUSCH transmission opportunity;
  • the first PUSCH transmission opportunity is an initial transmission opportunity for repeated PUSCH transmission
  • the second PUSCH transmission opportunity is a retransmission opportunity for the repeated PUSCH transmission.
  • the embodiments of the present application also provide an information transmission method, the method comprising:
  • the first uplink control information UCI is transmitted on the first physical uplink shared channel PUSCH transmission opportunity, or the receiving timing of the downlink control signaling for scheduling the second UCI meets the preset conditions, if the physical uplink carrying the second UCI If there is a conflict between the control channel PUCCH and the second PUSCH transmission opportunity, the second UCI is received on the second PUSCH transmission opportunity;
  • the first PUSCH transmission opportunity is an initial transmission opportunity for repeated PUSCH transmission
  • the second PUSCH transmission opportunity is a retransmission opportunity for the repeated PUSCH transmission.
  • an information transmission device comprising:
  • the first sending module is configured to, in the presence of the first uplink control information UCI transmitted on the first physical uplink shared channel PUSCH transmission opportunity, or the receiving moment of scheduling the downlink control signaling of the second UCI meets the preset condition, if If there is a conflict between the physical uplink control channel PUCCH carrying the second UCI and the second PUSCH transmission opportunity, the second UCI is sent on the second PUSCH transmission opportunity;
  • the first PUSCH transmission opportunity is an initial transmission opportunity for repeated PUSCH transmission
  • the second PUSCH transmission opportunity is a retransmission opportunity for the repeated PUSCH transmission.
  • an embodiment of the present application further provides an information transmission device, the device comprising:
  • the first receiving module is configured to, in the presence of the first uplink control information UCI transmitted on the first physical uplink shared channel PUSCH transmission opportunity, or the receiving moment of scheduling the downlink control signaling of the second UCI meets a preset condition, if If there is a conflict between the physical uplink control channel PUCCH carrying the second UCI and the second PUSCH transmission opportunity, the second UCI is received on the second PUSCH transmission opportunity;
  • the first PUSCH transmission opportunity is an initial transmission opportunity for repeated PUSCH transmission
  • the second PUSCH transmission opportunity is a retransmission opportunity for the repeated PUSCH transmission.
  • an embodiment of the present application further provides a terminal, the terminal includes a processor, a memory, and a program or instruction stored in the memory and executable on the processor, the program or instruction being When executed by the processor, the steps of the method according to the first aspect are implemented.
  • an embodiment of the present application further provides a network device, the network device includes a processor, a memory, and a program or instruction stored on the memory and executable on the processor, the program or instruction The steps of the method of the second aspect are implemented when executed by the processor.
  • an embodiment of the present application further provides a readable storage medium, where a program or an instruction is stored on the readable storage medium, and when the program or instruction is executed by a processor, the method according to the first aspect is implemented. steps, or steps for implementing the method according to the second aspect.
  • an embodiment of the present application further provides a chip, where the chip includes a processor and a communication interface, the communication interface is coupled to the processor, and the processor is configured to run a network device program or instruction to implement the following: The method described in the first aspect above, or the method described in the second aspect above is implemented.
  • an embodiment of the present application further provides a communication device, where the communication device is configured to perform the steps of the method according to the first aspect, or to perform the steps of the method according to the second aspect.
  • an embodiment of the present application further provides a computer program product, the computer program product is stored in a non-volatile storage medium, and the computer program product is executed by at least one processor to implement the first aspect the method, or implement the method according to the second aspect.
  • the first UCI is transmitted on the first PUSCH transmission opportunity, or the receiving moment of the downlink control signaling scheduling the second UCI meets the preset condition, if the PUCCH carrying the second UCI If there is a conflict with the second PUSCH transmission opportunity, the second UCI is sent on the second PUSCH transmission opportunity; wherein, the first PUSCH transmission opportunity is an initial transmission opportunity for repeated PUSCH transmission, and the second PUSCH transmission opportunity
  • the PUSCH transmission opportunity is a retransmission opportunity for repeated transmission of the PUSCH, so that the UCI transmission can be guaranteed in the case that the PUCCH carrying the UCI collides with the retransmission resources of the PUSCH.
  • FIG. 1 is a structural diagram of a network system to which an embodiment of the present application can be applied;
  • FIG. 2 is a schematic diagram of UCI multiplexing on PUSCH provided by an embodiment of the present application
  • FIG. 3 is a schematic diagram of uplink transmission skipping provided by an embodiment of the present application.
  • 5 is one of the schematic diagrams of PUSCH repeated transmission and UCI multiplexing provided by an embodiment of the present application
  • FIG. 6 is the second schematic diagram of PUSCH repeated transmission and UCI multiplexing provided by an embodiment of the present application.
  • FIG. 7 is the third schematic diagram of PUSCH repeated transmission and UCI multiplexing provided by an embodiment of the present application.
  • FIG. 8 is the fourth schematic diagram of PUSCH repeated transmission and UCI multiplexing provided by an embodiment of the present application.
  • FIG. 9 is a fifth schematic diagram of PUSCH repeated transmission and UCI multiplexing provided by an embodiment of the present application.
  • FIG. 10 is a sixth schematic diagram of PUSCH repeated transmission and UCI multiplexing provided by an embodiment of the present application.
  • 11 is a seventh schematic diagram of PUSCH repeated transmission and UCI multiplexing provided by an embodiment of the present application.
  • FIG. 13 is the eighth schematic diagram of PUSCH repeated transmission and UCI multiplexing provided by the embodiment of the present application.
  • FIG. 14 is the ninth schematic diagram of PUSCH repeated transmission and UCI multiplexing provided by an embodiment of the present application.
  • 15 is a structural diagram of an information transmission apparatus provided by an embodiment of the present application.
  • 16 is a structural diagram of another information transmission device provided by an embodiment of the present application.
  • FIG. 17 is a structural diagram of a terminal provided by an embodiment of the present application.
  • FIG. 18 is a structural diagram of a network device provided by an embodiment of the present application.
  • first, second and the like in the description and claims of the present application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It is to be understood that the terms so used are interchangeable under appropriate circumstances so that the embodiments of the present application can be practiced in sequences other than those illustrated or described herein, and that "first”, “second” distinguishes Usually it is a class, and the number of objects is not limited.
  • the first object may be one or multiple.
  • “and/or” in the description and claims indicates at least one of the connected objects, and the character “/" generally indicates that the contextual objects are in an "or” relationship.
  • LTE Long Term Evolution
  • LTE-Advanced LTE-Advanced
  • LTE-A Long Term Evolution
  • CDMA Code Division Multiple Access
  • TDMA Time Division Multiple Access
  • FDMA Frequency Division Multiple Access
  • OFDMA Orthogonal Frequency Division Multiple Access
  • SC-FDMA Single-carrier Frequency-Division Multiple Access
  • system and “network” in the embodiments of the present application are often used interchangeably, and the described technology can be used not only for the above-mentioned systems and radio technologies, but also for other systems and radio technologies.
  • NR New Radio
  • 6G most Generation
  • FIG. 1 shows a block diagram of a wireless communication system to which the embodiments of the present application can be applied.
  • the wireless communication system includes a terminal 11 and a network device 12 .
  • the terminal 11 may also be called a terminal device or a user terminal (User Equipment, UE), and the terminal 11 may be a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (Laptop Computer) or a notebook computer, a personal digital computer Assistant (Personal Digital Assistant, PDA), handheld computer, netbook, ultra-mobile personal computer (ultra-mobile personal computer, UMPC), mobile Internet device (Mobile Internet Device, MID), wearable device (Wearable Device) or vehicle-mounted device (VUE), pedestrian terminal (PUE) and other terminal-side devices, wearable devices include: bracelets, headphones, glasses, etc. It should be noted that, the embodiment of the present application does not limit the specific type of the terminal 11 .
  • the network device 12 may be a base station or a core network, where the base station may be referred to as a Node B, an evolved Node B, an access point, a Base Transceiver Station (BTS), a radio base station, a radio transceiver, a basic service set (Basic Service Set, BSS), Extended Service Set (Extended Service Set, ESS), Node B, Evolved Node B (eNB), Home Node B, Home Evolved Node B, WLAN Access Point, WiFi Node, Transmission and Reception Point (Transmitting Receiving Point, TRP) or some other suitable term in the field, as long as the same technical effect is achieved, the base station is not limited to specific technical vocabulary, it should be noted that in the embodiment of this application, only NR is used The base station in the system is taken as an example, but the specific type of the base station is not limited.
  • the UCI defined by the physical layer is multiplexed on the PUSCH
  • the UCI is transmitted on PUCCH. If the terminal is transmitting data on the PUSCH, in principle, the PUCCH and the PUSCH can be sent at the same time, that is, the UCI is reserved in the PUCCH. However, this will increase the Cubic Metric. In addition, if the requirement of out-of-band transmission is to be met at higher transmit power, and the interval in the frequency domain is large when PUSCH and PUCCH are transmitted at the same time, PUCCH is generally sent at both ends of the frequency band, which will affect the radio frequency (Radio Frequency , RF) implementation poses challenges.
  • Radio Frequency Radio Frequency
  • the base station will ensure that the conditions of the UCI multiplexing processing time are met when scheduling the PUSCH, and the UCI will be multiplexed with the data on the PUSCH. Avoid sending PUCCH at the same time, as shown in Figure 2.
  • NR Release 15 within a PUCCH group (PUCCH group), no matter whether PUCCH and PUSCH are in the same serving cell or in different serving cells, PUCCH and PUSCH are not supported Simultaneous transmission, so when the PUCCH time domain resources and the PUSCH time domain resources overlap (including partial overlap and full overlap), the UE will discard it according to the corresponding rules under the condition that certain time requirements are met, for example, Scheduling Request , SR) PUCCH overlaps with the PUSCH (ie PUSCH without UL-SCH) that does not carry the Uplink-Sharing Channel (UL-SCH), the UE discards the PUSCH to transmit the SR PUCCH, or multiplexes the UCI onto the PUSCH Transmission, for example, hybrid automatic repeat request response (Hybrid Automatic Repeat Request Acknowledge, HARQ-ACK)/channel state information (Channel State Information, CSI) PUCCH and PUSCH overlap, UE multiplex
  • SR Scheduling Request
  • the UE first handles the collision between multiple PUCCHs (if any), and the result of the processing is one or more non-overlapping PUCCHs, and then handles the collisions between the PUCCH and PUSCH. If the PUCCH only overlaps with one PUSCH, the UCI (excluding SR) multiplexing on the PUSCH, if the PUCCH overlaps with multiple PUSCHs, the UE selects a PUSCH for multiplexing according to the corresponding rules, wherein the rules for selecting the multiplexed PUSCH may be as follows:
  • PUSCH with aperiodic CSI ie A-CSI
  • Second priority PUSCH with the earliest start slot
  • the third priority Dynamically scheduled PUSCH>Configure authorized PUSCH or semiPersistentOnPUSCH;
  • the MAC layer defines the process for the terminal to perform uplink transmission skipping (UL skipping). As shown in Figure 3, if the following conditions are met, the MAC entity will not generate a MAC Protocol Data Unit (PDU) for the HARQ entity:
  • PDU MAC Protocol Data Unit
  • the MAC entity is configured with the parameter skipUplinkTxDynamic, and the value of the parameter is set to true (true), and the MAC locates the HARQ entity indicated in the uplink grant (UL grant);
  • the UL grant does not request aperiodic CSI for this PUSCH transmission
  • the MAC PDU includes zero MAC service data units (Service Data Unit, SDU);
  • the MAC PDU only contains the periodic buffer status report (Buffer Status Report, BSR), and there is no data available for any logical channel group (Logical Channel Group, LCG), or the MAC PDU only contains the padding BSR.
  • BSR Buffer Status Report
  • the UCI When the PUSCH is enabled with the uplink transmission skip function, and there is an overlap between the PUCCH and the PUSCH, the UCI will be multiplexed on the PUSCH. If the terminal has data to transmit, the MAC will generate a PDU carrying the data, and if the terminal has no data to transmit, the MAC will generate a padding PDU. Therefore, regardless of whether the terminal has data to transmit, the UCI will be multiplexed and transmitted on the PUSCH with the uplink transmission skip function enabled.
  • the PUSCH can last for multiple time slots or symbols in the time domain, and perform repeated transmission in the time domain, in order to improve the reliability of transmission. Specifically, a complete data packet can be transmitted in each time slot or symbol, and then repeated transmission is performed in multiple time slots or symbols, and different redundancy version numbers can be used during repeated transmission to improve performance. Among them, the number of time slots or symbols for repeated transmission is defined as the number of repeated transmissions, which can be denoted as K.
  • PUSCH/Physical Downlink Shared Channel that is, for a set of symbols allocated in a single time slot, a configuration-based aggregation factor (Aggregation Factor) , which occurs repeatedly in multiple consecutive time slots, that is, an identical set of symbols exists in N consecutive time slots specified by the aggregation factor N, which are used to carry the scheduled PUSCH/PDSCH.
  • PDSCH Physical Downlink Shared Channel
  • the PUSCH/PDSCH transmitted in these multiple timeslots are for the same HARQ process, and the redundancy version corresponding to the PUSCH/PDSCH transmission in each timeslot is based on the downlink control information (Downlink control information, DCI) indication value according to a predefined value value sequence to set.
  • DCI Downlink control information
  • the aggregated transmission of PUSCH is called PUSCH repetition type A (PUSCH repetition type A) in Ultra-Reliable and Low Latency Communications (URLLC) Release 16 (Release16, R16).
  • PUSCH repetition transmission type B PUSCH repetition transmission type B
  • PUSCH repetition type B PUSCH repetition transmission type B
  • a single non-Fallback DCI non-Fallback DCI, which can be DCI format 0_1 or DCI format 0_2
  • non-Fallback DCI can be scheduled by indicating the index of a certain row in the time-domain resource allocation table configured by the upper layer.
  • One or more nominal PUSCHs (Nominal PUSCH) that are consecutive in time are determined.
  • the first Nominal PUSCH in these Nominal PUSCHs is determined by the K2 parameter and SLIV in this row, and the remaining Nominal PUSCHs are followed by one by one Adjacent arrangement, that is, the DCI determines the time domain resource allocation of L*K consecutive symbols (here L is the number of consecutive symbols occupied by each Nominal PUSCH, and K is the number of consecutive Nominal PUSCHs in the time domain).
  • L is the number of consecutive symbols occupied by each Nominal PUSCH
  • K is the number of consecutive Nominal PUSCHs in the time domain.
  • the UE When the UE receives the scheduled PDSCH, it will indicate the K1 value (slot granularity), that is, it indicates the slot where the PUCCH corresponding to the scheduled PDSCH is located. At the same time, combined with the PRI indication in the DCI, it decodes the physical downlink control channel (Physical Downlink Shared Channel, PDCCH) of the DCI.
  • the specific control channel element Control Channel Element, CCE index (index) and the PUCCH transmission size (size) select the PUCCH resource (resource) according to the protocol rules.
  • the time between the symbol L where the first symbol (symbol) of the PUCCH resource is adjusted in the Tracking Area (TA) and the last symbol of the corresponding PDSCH needs to satisfy the following timeline (timeline) Tproc,1 :
  • T proc, 1 (N 1 +d 1,1 )(2048+144). ⁇ 2 ⁇ ⁇ T c
  • N1 is related to different UE capabilities (capability) and whether there is an additional demodulation reference signal (additional DMRS), as shown in Table 1 and Table 2.
  • Sub-Carrier Spacing (SCS) of the PDCCH that schedules the PDSCH are calculated to obtain different T proc,1 , take N1 and SCS corresponding to the maximum T proc,1 value;
  • the TA needs to consider multiple carriers;
  • d 1,1 and PDSCH type type
  • length and number of symbols overlapping with PDCCH
  • the UE When a single-slot PUCCH overlaps with a single-slot PUCCH or PUSCH, the UE will use the existing multiplexing rules to multiplex all UCIs on one PUCCH or PUSCH. If there are multiple PUSCH/PUCCH overlaps, the last symbol of any PDSCH will arrive at The time interval of the start symbol of the earliest PUCCH/PUSCH in the overlapping PUCCH/PUSCH is is the maximum value of the processing time of all PDSCHs, i.e. The processing time of the i-th PDSCH is:
  • d 1 , 1 is related to DMRS configuration, PDCCH and PDSCH configuration.
  • the time interval for the last symbol of any PDCCH to the start symbol of the earliest PUCCH/PUSCH in the overlapping PUCCH/PUSCH is is the maximum value of the processing time of all PUSCH, i.e.
  • the processing time of the i-th PUSCH is:
  • NR R15 introduced a scheduling and HARQ time limit, N3. It is defined as follows:
  • the UE receives the first PDCCH instructing the UE to feed back HARQ-ACK in the first PUCCH of a certain slot, and the UE receives the second PDCCH after the first PDCCH, it also instructs the UE to feed back the HARQ-ACK in this slot, and the HARQ-ACK is fed back.
  • the PUCCH resource is the second PUCCH, then the interval from the end symbol position of the second PDCCH to the start symbol position of the first PUCCH should be greater than or equal to N 3 ⁇ (2048+144) ⁇ 2 ⁇ ⁇ T C , Among them, N3 is related to the subcarrier spacing and UE capability.
  • the information transmission method provided by the embodiments of the present application will be described in detail below through specific embodiments and application scenarios with reference to the accompanying drawings. It should be noted that the information transmission method provided in this embodiment can be applied to, but not limited to, a scenario in which the terminal enables the uplink transmission skipping (UL skipping) function of the PUSCH and the PUSCH is repeatedly transmitted.
  • UL skipping uplink transmission skipping
  • FIG. 4 is a flowchart of an information transmission method provided by an embodiment of the present application. The method can be executed by a terminal. As shown in FIG. 4, the method includes the following steps:
  • Step 401 In the case that the first UCI is transmitted on the first PUSCH transmission opportunity, or the reception time of the downlink control signaling scheduling the second UCI meets the preset condition, if the PUCCH carrying the second UCI and the second PUSCH are transmitted If there is a conflict between the opportunities, the second UCI is sent on the second PUSCH transmission opportunity;
  • the first PUSCH transmission opportunity is an initial transmission opportunity for repeated PUSCH transmission
  • the second PUSCH transmission opportunity is a retransmission opportunity for the repeated PUSCH transmission.
  • the above-mentioned first UCI may be a dynamically scheduled or semi-statically configured UCI, for example, the above-mentioned first UCI may be HARQ-ACK, CSI, or SR, or the like.
  • the above-mentioned second UCI may also be a dynamically scheduled or semi-statically configured UCI, for example, the above-mentioned second UCI may also be HARQ-ACK, CSI, or SR, or the like.
  • the second UCI may be any UCI, and the number of the second UCI may be one or more.
  • the above-mentioned first PUSCH transmission opportunity is the initial transmission opportunity of the above-mentioned PUSCH repeated transmission, that is, the above-mentioned first PUSCH transmission opportunity is used for the initial transmission of the transmission block.
  • the first PUSCH repeated transmission corresponds to
  • the transmission opportunity is used for the initial transmission of the transmission block, that is, the transmission opportunity corresponding to the first PUSCH repeated transmission is the first PUSCH transmission opportunity.
  • the corresponding redundancy version (Redundancy Version, RV) is 0.
  • the transmission opportunity corresponding to the PUSCH repeated transmission is used for the initial transmission of the transport block, that is, the transmission opportunity corresponding to the PUSCH repeated transmission whose RV is 0 is the first PUSCH transmission opportunity.
  • the above-mentioned second PUSCH transmission opportunity is a retransmission opportunity for repeated PUSCH transmission, that is, the above-mentioned second PUSCH transmission opportunity is used for retransmission of the transport block.
  • the above-mentioned PUSCH repeated transmission may also be referred to as a Transport Block (Transport Block, TB) repeated transmission.
  • the second PUSCH transmission opportunity may be any PUSCH transmission opportunity used for retransmission of the transport block, and the number of the second PUSCH transmission opportunity may be one or more.
  • the above-mentioned PUSCH may be a dynamically scheduled PUSCH, for example, a dynamically authorized PUSCH (Dynamic Grant PUSCH, DG PUSCH), or may be a semi-statically configured PUSCH, for example, a configured grant PUSCH (Configured Grant PUSCH, CG PUSCH).
  • a dynamically scheduled PUSCH for example, a dynamically authorized PUSCH (Dynamic Grant PUSCH, DG PUSCH)
  • DG PUSCH dynamically authorized PUSCH
  • a semi-statically configured PUSCH for example, a configured grant PUSCH (Configured Grant PUSCH, CG PUSCH).
  • the PUSCH transmission opportunity involved in this embodiment may also be described as a PUSCH transmission opportunity, PUSCH transmission, or PUSCH repetition, or the like.
  • the above-mentioned presence of the first UCI transmitted on the first PUSCH transmission opportunity may also be described as the presence of the first UCI to be transmitted on the first PUSCH transmission opportunity, or described as the presence of the first UCI to be transmitted on the first PUSCH transmission, or described as There is a first UCI transmitted on the first PUSCH repetition, etc.
  • the above-mentioned conflict between the PUCCH carrying the second UCI and the second PUSCH transmission opportunity may be understood as an overlap in the time domain between the PUCCH carrying the second UCI and the second PUSCH transmission opportunity.
  • the terminal in the case where the first UCI is transmitted on the first PUSCH transmission opportunity, the terminal allows resource conflict between the PUCCH scheduled or configured to carry the second UCI and the second PUSCH transmission opportunity.
  • the network device may schedule or configure a resource conflict between the PUCCH carrying the second UCI and the second PUSCH transmission opportunity.
  • the terminal may send the second PUSCH transmission opportunity on the second PUSCH transmission opportunity UCI, that is, multiplexing the second UCI on the second PUSCH transmission opportunity, it should be noted that the terminal may send all or part of the information of the second UCI on the second PUSCH transmission opportunity.
  • PUSCH occasion#1 is used for TB initial transmission
  • PUSCH occasion#2, PUSCH occasion#3, and PUSCH occasion#4 are used for TB retransmission
  • PUCCH1 and PUSCH occasion#1 there is a conflict between PUCCH1 and PUSCH occasion#1
  • the UCI1 borne by PUCCH1 is transmitted on PUSCH occasion#1
  • the DCI scheduling PUCCH2 and PUSCH occasion#3 the UCI2 borne by PUCCH2 is transmitted on PUSCH occasion#3.
  • the terminal may not multiplex the second UCI Transmitted on the second PUSCH transmission opportunity, eg, the terminal may discard the second UCI, or may transmit the second UCI on the PUCCH.
  • the terminal may expect the existence of the first UCI to be transmitted on the first PUSCH transmission opportunity.
  • the terminal if the receiving moment of the downlink control signaling for scheduling the second UCI satisfies a preset condition, the terminal allows resources to exist between the PUCCH that is scheduled or configured to carry the second UCI and the second PUSCH transmission opportunity Conflict, that is, when the receiving moment of the downlink control signaling for scheduling the second UCI satisfies a preset condition, the network device may schedule or configure a resource conflict between the PUCCH carrying the second UCI and the second PUSCH transmission opportunity.
  • the terminal may use the second PUSCH transmission opportunity
  • the second UCI is sent on the second UCI, that is, the second UCI is multiplexed on the second PUSCH transmission opportunity. It should be noted that the terminal may send all or part of the information of the second UCI on the second PUSCH transmission opportunity.
  • PUSCH occasion#1 is used for initial transmission of TB
  • PUSCH occasion#2, PUSCH occasion#3, and PUSCH occasion#4 are used for retransmission of TB
  • the receiving time of DCI scheduling UCI1 is related to PUSCH
  • the interval T1 between the start times of occasion#1 is greater than or equal to the preset time interval, if there is a conflict between the PUCCH1 carrying the UCI1 and the PUSCH occasion#3, the UCI1 is transmitted on the PUSCH occasion#3.
  • the terminal may not send the The second UCI is multiplexed and transmitted on the second PUSCH transmission opportunity, eg, the terminal may discard the second UCI, or may transmit the second UCI on the PUCCH.
  • the terminal may expect to schedule the receiving moment of the downlink control signaling of the second UCI to satisfy a preset condition.
  • the terminal can generate a padding PDU; if the terminal has data to transmit, it can generate a PDU carrying data .
  • the terminal may only send the PUSCH on the PUSCH retransmission opportunity that collides with the PUCCH carrying the UCI, for example, for FIG. 5 , PUSCH can be sent only on PUSCH occasion#1 and PUSCH occasion#3, and no PUSCH can be sent on PUSCH occasion#2 and PUSCH occasion#4; for Figure 6, PUSCH can be sent only on PUSCH occasion#3, and PUSCH is not sent on PUSCH occasion#1, PUSCH occasion#2 and PUSCH occasion#4.
  • the terminal may also send the PUSCH on the first PUSCH transmission opportunity and all the PUSCH transmission opportunities after the first PUSCH transmission opportunity. For example, for FIG. 5 and FIG. PUSCH is sent on PUSCH occasion#4.
  • the second UCI is carried If there is a conflict between the PUCCH of the UCI and the second PUSCH transmission opportunity, the second UCI is sent on the second PUSCH transmission opportunity, so that the UCI can be guaranteed when the retransmission resources of the PUCCH carrying the UCI and the PUSCH conflict with each other. transmission and improve transmission efficiency.
  • the receiving moment of the downlink control signaling for scheduling the second UCI meets a preset condition, including at least one of the following:
  • the first time interval between the moment of receiving the downlink control signaling of the scheduling second UCI and the first time domain position satisfies a preset duration condition, wherein the first time domain position is based on the first PUSCH transmission opportunity and at least one of the starting time of the PUCCH carrying the second UCI is determined;
  • the receiving time of the downlink control signaling for scheduling the second UCI is located before the receiving time of the downlink control signaling for scheduling the PUSCH.
  • the terminal when the time interval (ie, the first time interval) between the time when the downlink control signaling of the second UCI is scheduled and the first time domain position satisfies the preset duration condition, the terminal A resource conflict between the PUCCH scheduled or configured to carry the second UCI and the second PUSCH transmission opportunity is allowed.
  • the reception time of the downlink control signaling of the second UCI may be the start time or the end time of the PDCCH carrying the downlink control signaling.
  • the above-mentioned first time-domain position may be determined according to at least one of the first PUSCH transmission opportunity and the start time of the PUCCH carrying the second UCI, for example, the above-mentioned first time-domain position may be the first PUSCH
  • the start time or end time of the transmission opportunity, or the above-mentioned first time domain position may be the start time of the PUCCH carrying the second UCI, or the like.
  • the above preset duration condition may be set according to at least one of PUSCH preparation time, UCI multiplexing time, and PDSCH processing time.
  • the terminal in the case that the receiving time of the downlink control signaling for scheduling the second UCI is before the receiving time of the downlink control signaling for scheduling the PUSCH, the terminal is allowed to be scheduled or configured to carry the second UCI There is a resource conflict between the PUCCH and the second PUSCH transmission opportunity.
  • the above PUSCH may be a dynamically scheduled PUSCH.
  • the first time domain location may be one of the following:
  • the terminal when the first time interval between the time when the downlink control signaling of the second UCI is scheduled and the start time of the first PUSCH transmission opportunity satisfies a preset time length condition, The terminal allows resource conflict between the PUCCH scheduled or configured to carry the second UCI and the second PUSCH transmission opportunity.
  • the first time interval between the reception moment of scheduling the downlink control signaling of the second UCI and the start moment of the PUCCH carrying the second UCI may satisfy a preset duration condition
  • the terminal allows a resource conflict between the PUCCH scheduled or configured to carry the second UCI and the second PUSCH transmission opportunity.
  • the receiving time of scheduling the downlink control signaling of the second UCI can be compared with the start time of the first PUSCH transmission opportunity and the start time of the PUCCH carrying the second UCI.
  • the terminal is allowed to be scheduled or configured to carry the second UCI and there is a resource conflict between the PUCCH and the second PUSCH transmission opportunity.
  • the first time interval satisfying a preset duration condition may include at least one of the following:
  • the first time interval is greater than or equal to the PUSCH preparation time
  • the first time interval is greater than or equal to the UCI multiplexing time
  • the first time interval is greater than or equal to the PDSCH processing time
  • the first time interval is greater than or equal to the PUCCH preparation time.
  • the above-mentioned PUSCH preparation time is Tproc,1.
  • the UCI multiplexing time may include at least one of a first multiplexing time and a second multiplexing time, wherein the first multiplexing time is Tproc, 1+1, and the second multiplexing time is Tproc ,2+1.
  • the above-mentioned PUCCH preparation time is also N3.
  • the first PUSCH transmission opportunity may be an initial transmission opportunity closest to the second PUSCH transmission opportunity in the repeated PUSCH transmission.
  • both CG PUSCH occasion#1 and CG PUSCH occasion#3 are used for initial transmission of transport blocks, that is, CG PUSCH occasion#1 and CG PUSCH occasion#3 are both initial transmissions in PUSCH repeated transmission CG PUSCH occasion#2 and CG PUSCH occasion#4 are both used for retransmission of transport blocks, that is, CG PUSCH occasion#2 and CG PUSCH occasion#4 are both retransmission opportunities in PUSCH repeated transmission.
  • CG PUSCH occasion#2 There is a resource conflict between occasion#4 and PUCCH2, and the first transmission opportunity closest to CG PUSCH occasion#4 is CG PUSCH occasion#3, that is, the first PUSCH transmission opportunity is CG PUSCH occasion#3.
  • both CG PUSCH occasion#1 and CG PUSCH occasion#3 are used for initial transmission of transport blocks
  • CG PUSCH occasion#2 and CG PUSCH occasion#4 are both used for retransmission of transport blocks
  • the closest initial transmission opportunity to CG PUSCH occasion#4 is CG PUSCH occasion#3, that is, the first PUSCH transmission opportunity is CG PUSCH occasion#3.
  • the method may also include:
  • the third PUSCH transmission opportunity is a PUSCH transmission opportunity located after the first PUSCH transmission opportunity in the repeated PUSCH transmission, and the third PUSCH transmission opportunity is different from the second PUSCH transmission opportunity.
  • the above-mentioned third PUSCH transmission opportunity does not conflict with the PUCCH.
  • the terminal may transmit all PUSCHs located after the first PUSCH transmission opportunity in the repeated PUSCH transmission.
  • the PUSCH is sent on the opportunity, that is, the PUSCH is sent on both the PUSCH transmission opportunity that collides with the PUCCH carrying the UCI and the PUSCH transmission opportunity that does not conflict with the PUCCH that carries the UCI.
  • the terminal may The PUSCH is sent on the transmission opportunity and all PUSCH transmission opportunities following the first PUSCH transmission opportunity. For example, for Figure 8, PUSCH may be sent on both CG PUSCH occasion#3 and CG PUSCH occasion#4.
  • the terminal does not expect the network device to schedule or configure a conflict between the PUCCH carrying the second UCI and the second PUSCH transmission opportunity.
  • the terminal in order to ensure the transmission of UCI, the terminal does not expect the network device to schedule or configure the relationship between the PUCCH carrying the second UCI and the second PUSCH transmission opportunity conflict exists.
  • the terminal since CG PUSCH occasion#3, that is, there is no UCI transmission on the first PUSCH transmission opportunity, the terminal does not expect a conflict between PUCCH2 scheduled by DCI and CG PUSCH occasion#4.
  • the terminal since PUSCH occasion#1, that is, there is no UCI transmission on the first PUSCH transmission opportunity, the terminal does not expect a conflict between PUCCH2 scheduled by DCI and CG PUSCH occasion#3.
  • the terminal does not expect the network device to schedule or configure the connection between the PUCCH carrying the second UCI and the second PUSCH transmission opportunity. There is a conflict.
  • the terminal in order to ensure the transmission of the UCI, the terminal does not expect the network device to schedule or configure the PUCCH carrying the second UCI and the second UCI. There are collisions between PUSCH transmission opportunities.
  • the terminal since the time interval between the receiving moment of the DCI scheduling PUCCH1 and the starting moment of the PUSCH occasion#1 does not satisfy the preset duration condition, the terminal does not expect the PUCCH1 and the CG PUSCH occasion# scheduled by the DCI to be There is a conflict between 3.
  • the terminal if there is no first UCI transmitted on the first PUSCH transmission opportunity or the reception time of the downlink control signaling for scheduling the second UCI does not meet the preset conditions, if the terminal is scheduled or configured to carry the second UCI There is a conflict between the PUCCH and the second PUSCH transmission opportunity, which may result in that the second UCI cannot be multiplexed on the second PUSCH transmission opportunity. For example, when the PUSCH of the terminal is enabled with the uplink transmission skip function and the terminal has no data to be transmitted, in the case where there is no first UCI to transmit on the first PUSCH transmission opportunity, the terminal will determine not to perform PUSCH transmission.
  • the terminal is scheduled or configured with a conflict between the PUCCH carrying the UCI and the PUSCH retransmission opportunity, the UCI cannot be multiplexed on the PUSCH retransmission opportunity that collides with the PUCCH carrying the UCI, resulting in UCI transmission failure. Therefore, when there is no first UCI transmitted on the first PUSCH transmission opportunity, there is no conflict between the PUCCH scheduled or configured by the network device to carry the second UCI and the second PUSCH transmission opportunity, and UCI transmission can be guaranteed.
  • the transmission priority of the second UCI is the same as the transmission priority of the PUSCH that collides with the second UCI;
  • the transmission priority of the second UCI is different from the transmission priority of the PUSCH colliding with the second UCI.
  • FIG. 12 is a flowchart of another information transmission method provided by an embodiment of the present application. The method is executed by a network device, as shown in FIG. 12, and includes the following steps:
  • Step 1201 Under the condition that the first UCI is transmitted on the first PUSCH transmission opportunity, or the reception timing of the downlink control signaling scheduling the second UCI meets the preset condition, if the PUCCH carrying the second UCI and the second PUSCH are transmitted If there is a conflict between the opportunities, the second UCI is received on the second PUSCH transmission opportunity;
  • the first PUSCH transmission opportunity is an initial transmission opportunity for repeated PUSCH transmission
  • the second PUSCH transmission opportunity is a retransmission opportunity for the repeated PUSCH transmission.
  • the network device may schedule or configure a resource conflict between the PUCCH carrying the second UCI and the second PUSCH transmission opportunity. Specifically, in the case where the first UCI is transmitted on the first PUSCH transmission opportunity, if there is a conflict between the PUCCH scheduled or configured by the network device to carry the second UCI and the second PUSCH transmission opportunity, the network device may transmit the second PUSCH on the second PUSCH transmission opportunity. The transmission opportunity receives the second UCI.
  • the network device may schedule or configure resources to exist between the PUCCH carrying the second UCI and the second PUSCH transmission opportunity conflict. Specifically, under the condition that the receiving moment of the downlink control signaling for scheduling the second UCI satisfies the preset condition, if there is a conflict between the PUCCH that the network device schedules or configures the PUCCH carrying the second UCI and the second PUSCH transmission opportunity, the network device may The second UCI is received on the second PUSCH transmission opportunity.
  • the network device may schedule or configure the bearer of the second UCI.
  • the PUCCH and the second PUSCH transmission opportunity There is a resource conflict between the PUCCH and the second PUSCH transmission opportunity, and it is also possible to schedule or configure that there is no resource conflict between the PUCCH carrying the second UCI and the second PUSCH transmission opportunity.
  • this embodiment is an implementation of the network device corresponding to the embodiment shown in FIG. 4 .
  • the network device when the first UCI is transmitted on the first PUSCH transmission opportunity, or the receiving moment of scheduling the downlink control signaling of the second UCI meets the preset condition, if the network device carries the first UCI If there is a conflict between the PUCCH of the two UCIs and the second PUSCH transmission opportunity, then receiving the second UCI on the second PUSCH transmission opportunity can ensure the transmission of the UCI.
  • the receiving moment of the downlink control signaling for scheduling the second UCI meets a preset condition, including at least one of the following:
  • the first time interval between the moment of receiving the downlink control signaling of the scheduling second UCI and the first time domain position satisfies a preset duration condition, wherein the first time domain position is based on the first PUSCH transmission opportunity and at least one of the starting time of the PUCCH carrying the second UCI is determined;
  • the receiving time of the downlink control signaling for scheduling the second UCI is located before the receiving time of the downlink control signaling for scheduling the PUSCH.
  • the first time domain position is one of the following:
  • the first time interval satisfying a preset duration condition includes at least one of the following:
  • the first time interval is greater than or equal to the PUSCH preparation time
  • the first time interval is greater than or equal to the UCI multiplexing time
  • the first time interval is greater than or equal to the PDSCH processing time
  • the first time interval is greater than or equal to the PUCCH preparation time.
  • the first PUSCH transmission opportunity is an initial transmission opportunity closest to the second PUSCH transmission opportunity in the repeated PUSCH transmission.
  • the method further includes:
  • the method further includes:
  • the method may also include:
  • the third PUSCH transmission opportunity is a PUSCH transmission opportunity located after the first PUSCH transmission opportunity in the repeated PUSCH transmission, and the third PUSCH transmission opportunity is different from the second PUSCH transmission opportunity.
  • the network device may be located after the first PUSCH transmission opportunity in the repeated PUSCH transmission.
  • the PUSCH is received on all PUSCH transmission opportunities, that is, the PUSCH is received on both the PUSCH transmission opportunities that conflict with the PUCCH carrying UCI and the PUSCH transmission opportunities that do not conflict with the PUCCH carrying UCI.
  • the network device can The PUSCH is received on the PUSCH transmission opportunity and all PUSCH transmission opportunities following the first PUSCH transmission opportunity.
  • the transmission priority of the second UCI is the same as the transmission priority of the PUSCH that collides with the second UCI;
  • the transmission priority of the second UCI is different from the transmission priority of the PUSCH colliding with the second UCI.
  • the terminal enables the PUSCH uplink transmission skipping (UL skipping) function, and the PUSCH performs repeated transmission .
  • the UE When the first UCI is multiplexed on the first CG PUSCH transmission opportunity, the UE is allowed to be scheduled or configured with a resource conflict between the second UCI and the second CG PUSCH transmission opportunity, and the UE multiplexes the second UCI on the second CG PUSCH transmission opportunity.
  • the above-mentioned CG PUSCH is a semi-statically configured PUSCH, where:
  • the second CG PUSCH transmission opportunity corresponds to the retransmission opportunity of the TB, that is, the CG PUSCH transmission opportunity corresponding to RV ⁇ 0;
  • the second UCI may include one or more UCIs, and the second PUSCH transmission opportunity may include one or more retransmission opportunities for repeated TB transmission.
  • CG PUSCH occasion#1 and CG PUSCH occasion#3 are both used for initial transmission of transport blocks, and CG PUSCH occasion#2 and CG PUSCH occasion#4 are both used for retransmission of transport blocks.
  • UCI1 is transmitted on CG PUSCH occasion#3, therefore, UE allows resource conflict between PUCCH2 scheduled by DCI and CG PUSCH occasion#4, and transmits UCI2 carried by PUCCH2 on CG PUSCH occasion#4. It should be noted that, for CG PUSCH occasion#1 and CG PUSCH occasion#2, since there is no data transmission and no PUCCH overlaps with them, PUSCH is not sent on CG PUSCH occasion#1 and CG PUSCH occasion#2.
  • CG PUSCH occasion#1 and CG PUSCH occasion#3 are both used for initial transmission of transport blocks
  • CG PUSCH occasion#2 and CG PUSCH occasion#4 are both used for retransmission of transport blocks.
  • UCI transmitted on CG PUSCH occasion#3 therefore, UE does not expect resource conflict between PUCCH2 scheduled by DCI and CG PUSCH occasion#4.
  • the UE When the first UCI is multiplexed on the first DG PUSCH transmission opportunity, the UE allows the second UCI to be scheduled to have a resource conflict with the second DG PUSCH transmission opportunity, and the UE multiplexes the second UCI on the second DG PUSCH On transmission opportunities, the above DG PUSCH can be dynamically scheduled PUSCH, where:
  • the first PUSCH transmission opportunity is the first transmission opportunity in the repeated PUSCH transmission
  • the second PUSCH transmission opportunity is a transmission opportunity other than the first transmission opportunity in the repeated PUSCH transmission.
  • the UE When there is no first UCI multiplexed on the first PUSCH transmission opportunity, the UE does not expect to be scheduled or configured with a resource conflict between the second UCI and the second PUSCH transmission opportunity, where:
  • the first PUSCH transmission opportunity corresponds to the initial transmission opportunity of the TB, and optionally, the first PUSCH transmission opportunity may be the last most recent initial transmission opportunity;
  • the second PUSCH transmission opportunity corresponds to the retransmission opportunity of the TB.
  • PUSCH occasion#1 is used for initial transmission of TB
  • PUSCH occasion#2 PUSCH occasion#3 and PUSCH occasion#4 are used for retransmission of TB, since PUSCH occasion#1, which is the first There is no UCI transmission on the PUSCH transmission opportunity, so the terminal does not expect a conflict between the DCI-scheduled PUCCH2 and the CG PUSCH occasion#3.
  • the UE When the first UCI is multiplexed on the first PUSCH transmission opportunity, the UE is allowed to be scheduled or configured with a resource conflict between the second UCI and the second PUSCH transmission opportunity, and the UE multiplexes the second UCI on the second PUSCH transmission opportunity, where:
  • the first PUSCH transmission opportunity corresponds to the initial transmission opportunity of the TB, and optionally, the first PUSCH transmission opportunity may be the last most recent initial transmission opportunity;
  • the second PUSCH transmission opportunity corresponds to the retransmission opportunity of the TB.
  • the UE may send the PUSCH on the first PUSCH transmission opportunity and send the PUSCH on the second PUSCH transmission opportunity that collides with the second UCI.
  • CG PUSCH occasion#1 and CG PUSCH occasion#3 are both used for initial transmission of transport blocks
  • CG PUSCH occasion#2 and CG PUSCH occasion#4 are both used for retransmission of transport blocks
  • the UE transmits the PUSCH at all PUSCH transmission opportunities after the first PUSCH transmission opportunity (including PUSCH transmission opportunities that collide or do not collide with the second UCI).
  • CG PUSCH occasion#1 and CG PUSCH occasion#3 are both used for initial transmission of transport blocks
  • CG PUSCH occasion#2 and CG PUSCH occasion#4 are both used for retransmission of transport blocks
  • the UE When the first time interval between the time when the downlink control signaling of the second UCI is scheduled and the first time domain position is greater than or equal to the first duration, the UE is allowed to be scheduled or configured for transmission of the second UCI and the second CG PUSCH There is a resource conflict between the opportunities, and the UE multiplexes the second UCI on the second CG PUSCH transmission opportunity, where:
  • the first time domain position is the start moment of the first CG PUSCH transmission opportunity
  • the second CG PUSCH transmission opportunity corresponds to the retransmission opportunity of the TB, that is, the CG PUSCH transmission opportunity corresponding to RV ⁇ 0;
  • the first duration is the UCI multiplexing time
  • the UE transmits the PUSCH only on the CG PUSCH transmission opportunity that collides with the second UCI, or transmits the PUSCH on the first CG PUSCH transmission opportunity and all CG PUSCH transmission opportunities after the first CG PUSCH transmission opportunity.
  • CG PUSCH occasion#1 and CG PUSCH occasion#3 are both used for initial transmission of transport blocks, and CG PUSCH occasion#2 and CG PUSCH occasion#4 are both used for retransmission of transport blocks, scheduling PUCCH2 If the time interval between the receiving moment of the DCI and the start moment of the CG PUSCH occasion#3 is greater than or equal to the UCI multiplexing time, the UE transmits the PUSCH on the CG occasion#4, or transmits the PUSCH on the CG PUSCH occasion#3 and #4 Both transmit PUSCH.
  • the UE When the time interval between the time when the downlink control signaling of the second UCI is scheduled and the first time domain position is greater than or equal to the first duration, the UE is allowed to be scheduled or configured with the second UCI and the second DG PUSCH transmission opportunity There is a resource conflict between them, and the UE multiplexes the second UCI on the second DG PUSCH transmission opportunity, where:
  • the first time domain position is the start moment of the first DG PUSCH transmission opportunity
  • the first PUSCH transmission opportunity is the first transmission opportunity in the repeated PUSCH transmission
  • the second PUSCH transmission opportunity is a transmission opportunity other than the first transmission opportunity in the PUSCH repeated transmission
  • the first duration is the UCI multiplexing time.
  • the UE When the time interval between the time of receiving the downlink control signaling for scheduling the second UCI and the first time domain position is less than the first duration, the UE does not expect to be scheduled or configured with resources for the second UCI and the second PUSCH transmission opportunity conflict, where:
  • the first time domain position is the start time of the PUCCH carrying the second UCI, or the first time domain position is the start time of the first PUSCH transmission opportunity, or the first time domain position is the start time of the PUCCH carrying the second UCI the earlier of the time instant and the start time of the first PUSCH transmission opportunity;
  • the first duration may be at least one of PUSCH preparation time, UCI multiplexing time, and PDSCH processing time;
  • the first PUSCH transmission opportunity corresponds to the initial transmission of the TB
  • the second PUSCH transmission opportunity corresponds to the retransmission of the TB.
  • the terminal since the time interval between the receiving time of the DCI scheduled for PUCCH1 and the start time of PUSCH occasion#1 is less than the first duration, the terminal does not expect any one of the DCI-scheduled PUCCH1 and CG PUSCH occasion#3 conflict exists.
  • the UE For dynamically scheduled PUSCH (including PUSCH repeated transmission), when the receiving time of the downlink control signaling for scheduling the second UCI is located before the receiving time of the downlink control signaling for scheduling the PUSCH, the UE is allowed to schedule the second UCI and the PUSCH. There is a resource conflict in any repeated transmission of , and the UE multiplexes the second UCI on the PUSCH transmission opportunity that collides with the PUCCH carrying the second UCI.
  • the UE transmits PUSCH only on PUSCH transmission opportunities that collide with UCI.
  • the PUSCH is sent on the first PUSCH transmission opportunity, and the PUSCH is sent on the PUSCH transmission opportunity that collides with the second UCI.
  • the UE transmits PUSCH on all PUSCH transmission opportunities (including PUSCH transmission opportunities that collide or do not collide with UCI).
  • the information transmission methods provided in the embodiments of the present application can be applied to single-carrier and multi-carrier, as well as licensed frequency bands or unlicensed frequency bands, that is, repeated PUSCH transmission and PUCCH can be on the same carrier or on different carriers.
  • FIG. 15 is a structural diagram of an information transmission apparatus provided by an embodiment of the present application. As shown in FIG. 15, the information transmission apparatus 1500 includes:
  • the first sending module 1501 is configured to, when there is the first uplink control information UCI to be transmitted on the first physical uplink shared channel PUSCH transmission opportunity, or the receiving moment of scheduling the downlink control signaling of the second UCI meets a preset condition, If there is a conflict between the physical uplink control channel PUCCH carrying the second UCI and the second PUSCH transmission opportunity, sending the second UCI on the second PUSCH transmission opportunity;
  • the first PUSCH transmission opportunity is an initial transmission opportunity for repeated PUSCH transmission
  • the second PUSCH transmission opportunity is a retransmission opportunity for the repeated PUSCH transmission.
  • the receiving moment of the downlink control signaling for scheduling the second UCI meets a preset condition, including at least one of the following:
  • the first time interval between the moment of receiving the downlink control signaling of the scheduling second UCI and the first time domain position satisfies a preset duration condition, wherein the first time domain position is based on the first PUSCH transmission opportunity and at least one of the starting time of the PUCCH carrying the second UCI is determined;
  • the receiving time of the downlink control signaling for scheduling the second UCI is located before the receiving time of the downlink control signaling for scheduling the PUSCH.
  • the first time domain position is one of the following:
  • the first time interval satisfying a preset duration condition includes at least one of the following:
  • the first time interval is greater than or equal to the PUSCH preparation time
  • the first time interval is greater than or equal to the UCI multiplexing time
  • the first time interval is greater than or equal to the PDSCH processing time of the physical downlink shared channel
  • the first time interval is greater than or equal to the PUCCH preparation time.
  • the first PUSCH transmission opportunity is an initial transmission opportunity closest to the second PUSCH transmission opportunity in the repeated PUSCH transmission.
  • the device further includes:
  • a second sending module configured to send a PUSCH on a third PUSCH transmission opportunity when there is a conflict between the PUCCH carrying the second UCI and the second PUSCH transmission opportunity;
  • the third PUSCH transmission opportunity is a PUSCH transmission opportunity located after the first PUSCH transmission opportunity in the repeated PUSCH transmission, and the third PUSCH transmission opportunity is different from the second PUSCH transmission opportunity.
  • the apparatus does not expect a conflict between the network device scheduling or configuring the PUCCH carrying the second UCI and the second PUSCH transmission opportunity.
  • the apparatus does not expect the network device to schedule or configure the connection between the PUCCH carrying the second UCI and the second PUSCH transmission opportunity. There is a conflict.
  • the transmission priority of the second UCI is the same as the transmission priority of the PUSCH that collides with the second UCI;
  • the transmission priority of the second UCI is different from the transmission priority of the PUSCH colliding with the second UCI.
  • the information transmission apparatus provided in this embodiment of the present application can implement each process in the method embodiment shown in FIG. 4 , which is not repeated here to avoid repetition.
  • the information transmission device in the embodiment of the present application may be a device, and may also be a component, an integrated circuit, or a chip in a terminal.
  • FIG. 16 is a structural diagram of another information transmission apparatus provided by an embodiment of the present application. As shown in FIG. 16, the information transmission apparatus 1600 includes:
  • the first receiving module 1601 is configured to, in the presence of the first uplink control information UCI transmitted on the first physical uplink shared channel PUSCH transmission opportunity, or when the receiving moment of the downlink control signaling for scheduling the second UCI meets a preset condition, If there is a conflict between the physical uplink control channel PUCCH carrying the second UCI and the second PUSCH transmission opportunity, receiving the second UCI on the second PUSCH transmission opportunity;
  • the first PUSCH transmission opportunity is an initial transmission opportunity for repeated PUSCH transmission
  • the second PUSCH transmission opportunity is a retransmission opportunity for the repeated PUSCH transmission.
  • the receiving moment of the downlink control signaling for scheduling the second UCI meets a preset condition, including at least one of the following:
  • the first time interval between the moment of receiving the downlink control signaling of the scheduling second UCI and the first time domain position satisfies a preset duration condition, wherein the first time domain position is based on the first PUSCH transmission opportunity and at least one of the starting time of the PUCCH carrying the second UCI is determined;
  • the receiving time of the downlink control signaling for scheduling the second UCI is located before the receiving time of the downlink control signaling for scheduling the PUSCH.
  • the first time domain position is one of the following:
  • the first time interval satisfying a preset duration condition includes at least one of the following:
  • the first time interval is greater than or equal to the PUSCH preparation time
  • the first time interval is greater than or equal to the UCI multiplexing time
  • the first time interval is greater than or equal to the PDSCH processing time of the physical downlink shared channel
  • the first time interval is greater than or equal to the PUCCH preparation time.
  • the first PUSCH transmission opportunity is an initial transmission opportunity closest to the second PUSCH transmission opportunity in the repeated PUSCH transmission.
  • the device further includes:
  • a first configuration module configured to schedule or configure that there is no conflict between the PUCCH carrying the second UCI and the second PUSCH transmission opportunity when the first UCI is not transmitted on the first PUSCH transmission opportunity.
  • the device further includes:
  • the second configuration module is configured to schedule or configure that there is no conflict between the PUCCH carrying the second UCI and the second PUSCH transmission opportunity when the reception time of the downlink control signaling for scheduling the second UCI does not meet the preset condition.
  • the device further includes:
  • a second receiving module configured to receive a PUSCH on a third PUSCH transmission opportunity when there is a conflict between the PUCCH carrying the second UCI and the second PUSCH transmission opportunity;
  • the third PUSCH transmission opportunity is a PUSCH transmission opportunity located after the first PUSCH transmission opportunity in the repeated PUSCH transmission, and the third PUSCH transmission opportunity is different from the second PUSCH transmission opportunity.
  • the transmission priority of the second UCI is the same as the transmission priority of the PUSCH colliding with the second UCI;
  • the transmission priority of the second UCI is different from the transmission priority of the PUSCH colliding with the second UCI.
  • the information transmission apparatus provided in this embodiment of the present application can implement each process in the method embodiment shown in FIG. 12 , which is not repeated here to avoid repetition.
  • the information transmission apparatus in the embodiments of the present application may be an apparatus, or may be a component, an integrated circuit, or a chip in a network device.
  • FIG. 17 is a structural diagram of a terminal provided by an embodiment of the present application.
  • the terminal 1700 includes but is not limited to: a radio frequency unit 1701, a network module 1702, an audio output unit 1703, an input unit 1704, a sensor 1705, a display unit 1706, a user input unit 1707, an interface unit 1708, a memory 1709, and The processor 1710 and other components.
  • the terminal 1700 may also include a power source (such as a battery) for supplying power to various components, and the power source may be logically connected to the processor 1710 through a power management system, so as to manage charging, discharging, and power consumption through the power management system management and other functions.
  • a power source such as a battery
  • the terminal structure shown in FIG. 17 does not constitute a limitation on the terminal, and the terminal may include more or less components than shown, or combine some components, or arrange different components, which will not be repeated here.
  • the input unit 1704 may include a graphics processor (Graphics Processing Unit, GPU) 17041 and a microphone 17042. Such as camera) to obtain still pictures or video image data for processing.
  • the display unit 1706 may include a display panel 17061, which may be configured in the form of a liquid crystal display, an organic light emitting diode, or the like.
  • the user input unit 1707 includes a touch panel 17071 and other input devices 17072 .
  • the touch panel 17071 is also called a touch screen.
  • the touch panel 17071 may include two parts, a touch detection device and a touch controller.
  • Other input devices 17072 may include, but are not limited to, physical keyboards, function keys (such as volume control keys, switch keys, etc.), trackballs, mice, and joysticks, which will not be repeated here.
  • the radio frequency unit 1701 receives the downlink data from the network device, and then processes it to the processor 1710; in addition, sends the uplink data to the network device.
  • the radio frequency unit 1701 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.
  • Memory 1709 may be used to store software programs or instructions as well as various data.
  • the memory 109 may mainly include a storage program or instruction area and a storage data area, wherein the stored program or instruction area may store an operating system, an application program or instruction required for at least one function (such as a sound playback function, an image playback function, etc.) and the like.
  • the memory 1709 may include a high-speed random access memory, and may also include a non-volatile memory, wherein the non-volatile memory may be a read-only memory (Read-Only Memory, ROM), a programmable read-only memory (Programmable ROM) , PROM), erasable programmable read-only memory (Erasable PROM, EPROM), electrically erasable programmable read-only memory (Electrically EPROM, EEPROM) or flash memory.
  • ROM Read-Only Memory
  • PROM programmable read-only memory
  • PROM erasable programmable read-only memory
  • Erasable PROM Erasable PROM
  • EPROM electrically erasable programmable read-only memory
  • EEPROM electrically erasable programmable read-only memory
  • flash memory for example at least one magnetic disk storage device, flash memory device, or other non-volatile solid state storage device.
  • the processor 1710 may include one or more processing units; optionally, the processor 1710 may integrate an application processor and a modem processor, wherein the application processor mainly processes the operating system, user interface, and application programs or instructions, etc. Modem processors mainly deal with wireless communications, such as baseband processors. It can be understood that, the above-mentioned modulation and demodulation processor may not be integrated into the processor 1710.
  • the radio frequency unit 1701 is configured to, in the presence of the first uplink control information UCI being transmitted on the first physical uplink shared channel PUSCH transmission opportunity, or when the reception moment of scheduling the downlink control signaling of the second UCI meets a preset condition, If there is a conflict between the physical uplink control channel PUCCH carrying the second UCI and the second PUSCH transmission opportunity, the second UCI is sent on the second PUSCH transmission opportunity; wherein the first PUSCH transmission opportunity is the PUSCH The first transmission opportunity of repeated transmission, and the second PUSCH transmission opportunity is the retransmission opportunity of the repeated PUSCH transmission.
  • the above-mentioned processor 1710 and radio frequency unit 1701 can implement each process implemented by the terminal in the method embodiment of FIG. 4 , and can achieve the same technical effect.
  • an embodiment of the present application further provides a terminal, including a processor 1710, a memory 1709, a program or instruction stored in the memory 17089 and executable on the processor 1710, and the program or instruction is executed by the processor 1710 During execution, each process of the above-mentioned embodiment of the information transmission method on the terminal side is implemented, and the same technical effect can be achieved. In order to avoid repetition, details are not described here.
  • Figure 18 is a structural diagram of a network device provided by an embodiment of the present application, the network device 1800 includes: a processor 1801, a transceiver 1802, a memory 1803 and a bus interface, wherein:
  • the transceiver 1802 is configured to transmit the first uplink control information UCI on the first physical uplink shared channel PUSCH transmission opportunity, or schedule the receiving moment of the downlink control signaling of the second UCI to meet a preset condition, if the bearer If there is a conflict between the physical uplink control channel PUCCH of the second UCI and the second PUSCH transmission opportunity, the second UCI is received on the second PUSCH transmission opportunity; wherein the first PUSCH transmission opportunity is PUSCH repeated transmission the first transmission opportunity, the second PUSCH transmission opportunity is the retransmission opportunity of the PUSCH repeated transmission.
  • processor 1801 and transceiver 1802 can implement each process implemented by the network device in the method embodiment of FIG. 12 , and can achieve the same technical effect. To avoid repetition, details are not repeated here.
  • the transceiver 1802 is configured to receive and transmit data under the control of the processor 1801, and the transceiver 1802 includes at least two antenna ports.
  • the bus architecture may include any number of interconnected buses and bridges, specifically one or more processors represented by processor 1801 and various circuits of memory represented by memory 1803 linked together.
  • the bus architecture may also link together various other circuits, such as peripherals, voltage regulators, and power management circuits, which are well known in the art and, therefore, will not be described further herein.
  • the bus interface provides the interface.
  • Transceiver 1802 may be a number of elements, including a transmitter and a receiver, that provide a means for communicating with various other devices over a transmission medium.
  • the user interface 1804 may also be an interface capable of externally connecting the required equipment, and the connected equipment includes but is not limited to a keypad, a display, a speaker, a microphone, a joystick, and the like.
  • the processor 1801 is responsible for managing the bus architecture and general processing, and the memory 1803 may store data used by the processor 1801 in performing operations.
  • an embodiment of the present application further provides a network device, including a processor 1801, a memory 1803, a program or instruction stored in the memory 1803 and executable on the processor 1801, the program or instruction being executed by the processor
  • a network device including a processor 1801, a memory 1803, a program or instruction stored in the memory 1803 and executable on the processor 1801, the program or instruction being executed by the processor
  • the embodiments of the present application further provide a readable storage medium, the readable storage medium may be non-volatile or volatile, and a program or an instruction is stored on the readable storage medium, and the program or instruction is stored in the readable storage medium.
  • the processor When executed, the processor implements each process of the foregoing embodiments of the terminal-side information transmission method or the network device-side information transmission method, and can achieve the same technical effect, which is not repeated here to avoid repetition.
  • the processor is the processor in the electronic device described in the foregoing embodiments.
  • the readable storage medium includes a computer-readable storage medium, such as a computer read-only memory (Read-Only Memory, ROM), a random access memory (Random Access Memory, RAM), a magnetic disk or an optical disk, and the like.
  • An embodiment of the present application further provides a chip, where the chip includes a processor and a communication interface, the communication interface is coupled to the processor, and the processor is used to run a network device program or instruction to implement the above information on the terminal side
  • the chip includes a processor and a communication interface
  • the communication interface is coupled to the processor
  • the processor is used to run a network device program or instruction to implement the above information on the terminal side
  • the chip mentioned in the embodiments of the present application may also be referred to as a system-on-chip, a system-on-chip, a system-on-a-chip, or a system-on-a-chip, or the like.
  • An embodiment of the present application further provides a computer program product, wherein the computer program product is stored in a non-transitory readable storage medium, and the computer program product is executed by at least one processor to implement the above terminal-side
  • the various processes of the embodiments of the information transmission method or the information transmission method on the network device side can achieve the same technical effect, and in order to avoid repetition, details are not repeated here.
  • An embodiment of the present application further provides a communication device, the communication device is configured to perform each process of implementing the above-mentioned embodiments of the terminal-side information transmission method or the network device-side information transmission method, and can achieve the same technical effect, In order to avoid repetition, details are not repeated here.

Landscapes

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

Abstract

本申请公开了一种信息传输方法、装置、终端及网络设备，属于通信技术领域。该方法包括：在存在第一UCI在第一PUSCH传输机会上传输，或者调度第二UCI的下行控制信令的接收时刻满足预设条件的情况下，若承载第二UCI的PUCCH与第二PUSCH传输机会之间存在冲突，则在所述第二PUSCH传输机会上发送所述第二UCI；其中，所述第一PUSCH传输机会为PUSCH重复传输的初传机会，所述第二PUSCH传输机会为所述PUSCH重复传输的重传机会。

Description

信息传输方法、装置、终端及网络设备
相关申请的交叉引用
本申请主张在2021年01月08日在中国提交的中国专利申请No.202110026258.9的优先权，其全部内容通过引用包含于此。
技术领域
本申请属于通信技术领域，具体涉及一种信息传输方法、装置、终端及网络设备。
背景技术
物理上行共享信道(Physical Uplink Sharing Channel，PUSCH)可以在时域上持续多个时隙或符号进行重复传输(Repetitions)，目的是提高传输的可靠性。然而，在终端使能了上行传输跳过(即UL skipping)的功能的情况下，当PUSCH进行重复传输时，若终端没有需要传输的数据传输，则终端不会进行PUSCH的重复传输；当存在物理上行控制信道(Physical Uplink Control Channel，PUCCH)与PUSCH之间有资源冲突，即使终端数据存储器中没有需要传输的数据传输时，终端仍将上行控制信息(Uplink Control Information，UCI)复用在PUSCH上传输，此时PUSCH承载填充(padding)数据。
但是，若终端在确定是否传输PUSCH重复传输时，还不存在PUCCH与PUSCH的重复传输有冲突，此时若终端数据存储器中没有需要传输的数据传输，则终端会确定不进行PUSCH的重复传输。而若在PUSCH重复传输期间存在PUCCH与其中一个或多个PUSCH重传资源冲突，则终端无法将UCI复用在该冲突的PUSCH重传资源上，导致UCI传输失败。
发明内容
本申请实施例提供一种信息传输方法、装置、终端和网络设备，能够解决因承载UCI的PUCCH与PUSCH的重传资源冲突导致的UCI传输失败的问题。
第一方面，本申请实施例提供了一种信息传输方法，该方法包括：
在存在第一上行控制信息UCI在第一物理上行共享信道PUSCH传输机会上传输，或者调度第二UCI的下行控制信令的接收时刻满足预设条件的情况下，若承载第二UCI的物理上行控制信道PUCCH与第二PUSCH传输机会之间存在冲突，则在所述第二PUSCH传输机会上发送所述第二UCI；
其中，所述第一PUSCH传输机会为PUSCH重复传输的初传机会，所述第二PUSCH传输机会为所述PUSCH重复传输的重传机会。
第二方面，本申请实施例还提供了一种信息传输方法，该方法包括：
在存在第一上行控制信息UCI在第一物理上行共享信道PUSCH传输机会上传输，或者调度第二UCI的下行控制信令的接收时刻满足预设条件的情况下，若承载第二UCI的物理上行控制信道PUCCH与第二PUSCH传输机会之间存在冲突，则在所述第二PUSCH传输机会上接收所述第二UCI；
其中，所述第一PUSCH传输机会为PUSCH重复传输的初传机会，所述第二PUSCH传输机会为所述PUSCH重复传输的重传机会。
第三方面，本申请实施例提供了一种信息传输装置，该装置包括：
第一发送模块，用于在存在第一上行控制信息UCI在第一物理上行共享信道PUSCH传输机会上传输，或者调度第二UCI的下行控制信令的接收时刻满足预设条件的情况下，若承载第二UCI的物理上行控制信道PUCCH与第二PUSCH传输机会之间存在冲突，则在所述第二PUSCH传输机会上发送所述第二UCI；
其中，所述第一PUSCH传输机会为PUSCH重复传输的初传机会，所述第二PUSCH传输机会为所述PUSCH重复传输的重传机会。
第四方面，本申请实施例还提供了一种信息传输装置，该装置包括：
第一接收模块，用于在存在第一上行控制信息UCI在第一物理上行共享信道PUSCH传输机会上传输，或者调度第二UCI的下行控制信令的接收时刻满足预设条件的情况下，若承载第二UCI的物理上行控制信道PUCCH与第二PUSCH传输机会之间存在冲突，则在所述第二PUSCH传输机会上接收所述第二UCI；
其中，所述第一PUSCH传输机会为PUSCH重复传输的初传机会，所述 第二PUSCH传输机会为所述PUSCH重复传输的重传机会。
第五方面，本申请实施例还提供了一种终端，该终端包括处理器、存储器及存储在所述存储器上并可在所述处理器上运行的程序或指令，所述程序或指令被所述处理器执行时实现如第一方面所述的方法的步骤。
第六方面，本申请实施例还提供了一种网络设备，该网络设备包括处理器、存储器及存储在所述存储器上并可在所述处理器上运行的程序或指令，所述程序或指令被所述处理器执行时实现如第二方面所述的方法的步骤。
第七方面，本申请实施例还提供了一种可读存储介质，所述可读存储介质上存储程序或指令，所述程序或指令被处理器执行时实现如第一方面所述的方法的步骤，或者实现如第二方面所述的方法的步骤。
第八方面，本申请实施例还提供了一种芯片，所述芯片包括处理器和通信接口，所述通信接口和所述处理器耦合，所述处理器用于运行网络设备程序或指令，实现如上述第一方面所述的方法，或者实现如上面第二方面所述的方法。
第九方面，本申请实施例还提供了一种通信设备，所述通信设备被配置为执行如第一方面所述的方法的步骤，或执行如第二方面所述的方法的步骤。
第十方面，本申请实施例还提供了一种计算机程序产品，所述计算机程序产品被存储在非易失的存储介质中，所述计算机程序产品被至少一个处理器执行以实现如第一方面所述的方法，或实现如第二方面所述的方法。
在本申请实施例中，通过在存在第一UCI在第一PUSCH传输机会上传输，或者调度第二UCI的下行控制信令的接收时刻满足预设条件的情况下，若承载第二UCI的PUCCH与第二PUSCH传输机会之间存在冲突，则在所述第二PUSCH传输机会上发送所述第二UCI；其中，所述第一PUSCH传输机会为PUSCH重复传输的初传机会，所述第二PUSCH传输机会为所述PUSCH重复传输的重传机会，这样可以在承载UCI的PUCCH与PUSCH的重传资源冲突的情况下保证UCI的传输。
附图说明
图1是本申请实施例可应用的一种网络系统的结构图；
图2是本申请实施例提供的UCI复用在PUSCH上的示意图；
图3是本申请实施例提供的上行传输跳过的示意图；
图4是本申请实施例提供的一种信息传输方法的流程图；
图5是本申请实施例提供的PUSCH重复传输与UCI复用的示意图之一；
图6是本申请实施例提供的PUSCH重复传输与UCI复用的示意图之二；
图7是本申请实施例提供的PUSCH重复传输与UCI复用的示意图之三；
图8是本申请实施例提供的PUSCH重复传输与UCI复用的示意图之四；
图9是本申请实施例提供的PUSCH重复传输与UCI复用的示意图之五；
图10是本申请实施例提供的PUSCH重复传输与UCI复用的示意图之六；
图11是本申请实施例提供的PUSCH重复传输与UCI复用的示意图之七；
图12是本申请实施例提供的另一种信息传输方法的流程图；
图13是本申请实施例提供的PUSCH重复传输与UCI复用的示意图之八；
图14是本申请实施例提供的PUSCH重复传输与UCI复用的示意图之九；
图15是本申请实施例提供的一种信息传输装置的结构图；
图16是本申请实施例提供的另一种信息传输装置的结构图；
图17是本申请实施例提供的一种终端的结构图；
图18是本申请实施例提供的一种网络设备的结构图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚地描述，显然，所描述的实施例是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员所获得的所有其他实施例，都属于本申请保护的范围。
本申请的说明书和权利要求书中的术语“第一”、“第二”等是用于区别类似的对象，而不用于描述特定的顺序或先后次序。应该理解这样使用的术语在适当情况下可以互换，以便本申请的实施例能够以除了在这里图示或描述的那些以外的顺序实施，且“第一”、“第二”所区别的对象通常为一类，并不限定对象的个数，例如第一对象可以是一个，也可以是多个。此外，说明书以及权利要求中“和/或”表示所连接对象的至少其中之一，字符“/”一 般表示前后关联对象是一种“或”的关系。
值得指出的是，本申请实施例所描述的技术不限于长期演进型(Long Term Evolution，LTE)/LTE的演进(LTE-Advanced，LTE-A)系统，还可用于其他无线通信系统，诸如码分多址(Code Division Multiple Access，CDMA)、时分多址(Time Division Multiple Access，TDMA)、频分多址(Frequency Division Multiple Access，FDMA)、正交频分多址(Orthogonal Frequency Division Multiple Access，OFDMA)、单载波频分多址(Single-carrier Frequency-Division Multiple Access，SC-FDMA)和其他系统。本申请实施例中的术语“系统”和“网络”常被可互换地使用，所描述的技术既可用于以上提及的系统和无线电技术，也可用于其他系统和无线电技术。然而，以下描述出于示例目的描述了新空口(New Radio，NR)系统，并且在以下大部分描述中使用NR术语，这些技术也可应用于NR系统应用以外的应用，如第6代(6th Generation，6G)通信系统。
图1示出本申请实施例可应用的一种无线通信系统的框图。无线通信系统包括终端11和网络设备12。其中，终端11也可以称作终端设备或者用户终端(User Equipment，UE)，终端11可以是手机、平板电脑(Tablet Personal Computer)、膝上型电脑(Laptop Computer)或称为笔记本电脑、个人数字助理(Personal Digital Assistant，PDA)、掌上电脑、上网本、超级移动个人计算机(ultra-mobile personal computer，UMPC)、移动上网装置(Mobile Internet Device，MID)、可穿戴式设备(Wearable Device)或车载设备(VUE)、行人终端(PUE)等终端侧设备，可穿戴式设备包括：手环、耳机、眼镜等。需要说明的是，在本申请实施例并不限定终端11的具体类型。
网络设备12可以是基站或核心网，其中，基站可被称为节点B、演进节点B、接入点、基收发机站(Base Transceiver Station，BTS)、无线电基站、无线电收发机、基本服务集(Basic Service Set，BSS)、扩展服务集(Extended Service Set，ESS)、B节点、演进型B节点(eNB)、家用B节点、家用演进型B节点、WLAN接入点、WiFi节点、发送接收点(Transmitting Receiving Point，TRP)或所述领域中其他某个合适的术语，只要达到相同的技术效果，所述基站不限于特定技术词汇，需要说明的是，在本申请实施例中仅以NR系统 中的基站为例，但是并不限定基站的具体类型。
为了方便理解，以下对本申请实施例涉及的一些内容进行说明：
一、物理层定义的UCI复用在PUSCH上
UCI在PUCCH上传输。若终端正在PUSCH上传输数据，原则上是可以同时发送PUCCH和PUSCH，即UCI保留在PUCCH。但是，这样会增加立方度量(Cubic Metric)。此外，如果要在更高的发射功率下满足带外发射的要求，并且PUSCH和PUCCH同时传输时在频域上的间隔较大，PUCCH一般在频带的两端发送，这将对射频(Radio Frequency，RF)的实施带来挑战。因此，通常情况下，如果承载UCI的PUCCH的资源与PUSCH的资源在时间上有重合，基站会在调度该PUSCH时保证满足UCI复用处理时间的条件，UCI会和数据复用在PUSCH上，避免同时发送PUCCH，如图2所示。
二、PUCCH和PUSCH冲突处理
在新空口(New Radio，NR)第15版本(Release15，R15)中，在一个PUCCH组(PUCCH group)内，无论PUCCH和PUSCH在相同的服务小区或不同的服务小区，均不支持PUCCH和PUSCH同时传输，因此当PUCCH时域资源和PUSCH时域资源重叠时(包括部分重叠和全部重叠)，UE会在满足一定的时间要求的情况下，根据相应的规则丢弃，例如，调度请求(Scheduling Request，SR)PUCCH和未承载上行链路共享信道(Uplink-Sharing Channel，UL-SCH)的PUSCH(即PUSCH without UL-SCH)重叠，UE丢弃PUSCH传输SR PUCCH，或者，将UCI复用到PUSCH上传输，例如，混合自动重传请求响应(Hybrid Automatic Repeat Request Acknowledge，HARQ-ACK)/信道状态信息(Channel State Information，CSI)PUCCH和PUSCH重叠，UE将HARQ-ACK/CSI复用到PUSCH上传输。具体的，UE首先处理多个PUCCH之间的冲突(如果有)，处理的结果是一个或多个非重叠的PUCCH，然后处理PUCCH和PUSCH之间冲突，如果PUCCH只与一个PUSCH重叠，则UCI(不包括SR)复用在该PUSCH上，如果PUCCH与多个PUSCH重叠，则UE根据相应的规则选择一个PUSCH进行复用，其中，选择复用的PUSCH的规则可以如下：
第一优先级：有非周期CSI(即A-CSI)的PUSCH；
第二优先级：起始时隙最早的PUSCH；
第三优先级：动态调度的PUSCH>配置授权PUSCH或semiPersistentOnPUSCH；
第四优先级：所在服务小区索引(index)小的PUSCH>所在服务小区索引大的PUSCH；
第五优先级：传输早的PUSCH>传输晚的PUSCH。
三、媒体接入控制(Media Access Control，MAC)层定义的上行传输跳过功能
MAC层定义了终端实行上行传输跳过(UL skipping)的过程。如图3所示，如果满足以下条件，MAC实体将不会为HARQ实体生成MAC协议数据单元(Protocol Data Unit，PDU)：
1)、MAC实体配置了参数skipUplinkTxDynamic，并且该参数的值被设置为真(true)，MAC定位到了上行授权(UL grant)中指示的HARQ实体；
2)、该UL grant中没有为此PUSCH传输请求非周期性CSI；
3)、MAC PDU包括零个MAC服务数据单元(Service Data Unit，SDU)；
4)、MAC PDU仅包含周期性缓存状态报告(Buffer Status Report，BSR)，并且没有可用于任何逻辑信道组(Logical Channel Group，LCG)的数据，或者MAC PDU仅包含填充BSR。
四、PUSCH使能上行传输跳过功能时UCI的复用
当PUSCH使能了上行传输跳过功能，且有PUCCH与PUSCH重叠时，UCI将复用在该PUSCH上。如果终端有数据需要传输，MAC会生成承载数据的PDU，如果终端没有数据需要传输，MAC会生成填充(padding)PDU。因此，无论终端是否有数据需要传输，UCI都会在使能了上行传输跳过功能的PUSCH上复用传输。
五、PUSCH在时域上的重复(Repetitions)传输
PUSCH可以在时域上持续多个时隙或符号，进行时域上的重复传输，目的是提高传输的可靠性。具体的，每个时隙或符号上可以传输一个完整的数据包，然后在多个时隙或符号上进行重复传输，并且在重复传输期间可以采用不同的冗余版本号来提高性能。其中，重复传输的时隙或符号数量定义为 重复传输数量，可以记为K。
在NR Rel-15中，对于PUSCH/物理下行共享信道(Physical Downlink Shared Channel，PDSCH)引入了聚合传输的概念，即对于在单个时隙内分配的符号集合，基于配置的聚合因子(Aggregation Factor)，在连续的多个时隙内重复出现，即聚合因子N指定的N个连续时隙内都存在完全相同的符号集合，用于承载调度的PUSCH/PDSCH。这多个时隙内传输的PUSCH/PDSCH针对同一个HARQ进程，每个时隙内的PUSCH/PDSCH传输对应的冗余版本基于下行控制信息(Downlink control information，DCI)指示值按预定义的取值序列进行设定。PUSCH的聚合传输在超可靠和低时延通信(Ultra-Reliable and Low Latency Communications，URLLC)第16版本(Release16，R16)中被称为PUSCH重复传输类型A(PUSCH repetition type A)。
相应地，在URLLC R16中还引入了一种PUSCH重复传输方案，被称为PUSCH重复传输类型B(PUSCH repetition type B)。在这种方案中，单个非回退DCI(non-Fallback DCI，可以为DCI format 0_1或DCI format 0_2)可以通过指示高层配置的时域资源分配表中的某一行的索引，来调度由此行确定的一到多个在时间上连续的名义PUSCH(Nominal PUSCH)，这些Nominal PUSCH中的第一个Nominal PUSCH由此行中的K2参数和SLIV来确定，剩余的Nominal PUSCH紧接其后逐个相邻排列，即由此DCI确定了L*K个连续符号的时域资源分配(这里L为每个Nominal PUSCH占用的连续符号数，K为时域连续的Nominal PUSCH数目)。当某种non-Fallback DCI格式被配置为支持PUSCH repetition type B时，在为其独立配置的时域资源分配表中，相对于NR R15的时域资源分配表，新增了一列numberofrepetitions参数，资源分配表中每一行的numberofrepetitions参数可独立配置，用于指示此行对应的Nominal PUSCH数目。
六、PDSCH处理时间
UE接收到调度PDSCH中会指示K1值(slot粒度)，即指示调度PDSCH对应的PUCCH所在的slot，同时结合DCI中的PRI指示，解码该DCI的物理下行控制信道(Physical Downlink Shared Channel，PDCCH)的特定控制通道单元(Control Channel Element，CCE)索引(index)以及该PUCCH传输 大小(size)按照协议规则选定PUCCH资源(resource)。
同时该PUCCH resource的第一个符号(symbol)进行跟踪区(Tracking Area，TA)调整后的所在symbol L与其对应的PDSCH的最后一个symbol之间的时间需要满足以下时间线(timeline) Tproc,1：
T proc，1＝(N 1+d 1，1)(2048+144).κ2 -μ·T c
其中，N1根据不同的UE能力(capability)和是否有附加解调参考信号(additional DMRS)有关，如表1、表2所示。
表1 PDSCH处理能力1的PDSCH处理时间
Figure PCTCN2022070274-appb-000001
表2 PDSCH处理能力1的PDSCH处理时间
Figure PCTCN2022070274-appb-000002
对应(调度该PDSCH的PDCCH的子载波间隔(Sub-Carrier Spacing，SCS)，调度的PDSCH的SCS，HARQ-ACK传输的PUCCH所在的UL channel的SCS)分别计算得到不同的T proc,1,取最大T proc,1值对应的N1和SCS；
当l 1＝12时，N1,0＝14，其它情况下N1,0＝13；
当UE配置了多个成员载波(Component Carrier，CC)时，TA需要考虑多个Carrier；
d 1,1和PDSCH的类型(type)，长度以及与PDCCH重叠的symbol数相关。
七、物理层PUSCH调度时间
调度PUSCH的PDCCH的结束符号与PUSCH的起始符号的时间间隔至少为T proc,2＝max((N 2+d 2,1)(2048+144)·κ2 -μ·T C,d 2,2)
其中，N2与μ的对应关系如表3和表4所示，其中，表3和表4分别表示UE处理能力1和2，
如果PUSCH的第一个符号只由DM-RS构成d 2,1＝0,否则d 2,1＝1。
如果调度DCI触发一个带宽部分(Bandwidth Part，BWP)的切换,d 2,2等于切换时间，否则d 2,2＝0。
表3 PUSCH定时能力的准备时间1
μ PUSCH准备时间N2[符号]
0 10
1 12
2 23
3 36
表4 PUSCH定时能力的准备时间2
μ PUSCH准备时间N2[符号]
0 5
1 5.5
2 频率范围1为11
八、物理层UCI复用时间
当单slot PUCCH与单slot PUCCH或PUSCH重叠时，UE将使用现有的复用规则，复用所有UCI在一个PUCCH或PUSCH上，如果有多个PUSCH/PUCCH重叠，任何PDSCH的最后一个符号到重叠的PUCCH/PUSCH中最早的PUCCH/PUSCH的起始符号的时间间隔为
Figure PCTCN2022070274-appb-000003
为所有PDSCH的处理时间的最大值，即
Figure PCTCN2022070274-appb-000004
其中第i个PDSCH的处理时间为：
Figure PCTCN2022070274-appb-000005
其中，d 1,1跟DMRS配置，PDCCH和PDSCH配置相关。
同样，对于任何PDCCH的最后一个符号到重叠的PUCCH/PUSCH中最 早的PUCCH/PUSCH的起始符号的时间间隔为
Figure PCTCN2022070274-appb-000006
为所有PUSCH的处理时间的最大值，即
Figure PCTCN2022070274-appb-000007
其中第i个PUSCH的处理时间为：
Figure PCTCN2022070274-appb-000008
九、处理时间N3
NR R15引入了一种调度和HARQ时间限制，即N3。其定义如下：
如果UE接收到第一PDCCH指示UE在某个slot的第一PUCCH反馈HARQ-ACK，UE在第一PDCCH之后接收到第二PDCCH同样指示UE在该slot反馈HARQ-ACK，且反馈HARQ-ACK的PUCCH资源为第二PUCCH，则从第二PDCCH的结束符号位置到第一PUCCH的起始符号位置之间的间隔要大于等于N 3·(2048+144)·κ·2 -μ·T C，其中N3与子载波间隔和UE能力有关，如果第二个PDCCH所在服务小区以及HARQ-ACK复用在该slot的PUCCH的所有服务小区都配置了PDSCH处理能力2，则N3的取值为N 3＝3对应μ＝0,N 3＝4.5对应μ＝1,N 3＝9对应μ＝2，即UE按照PDSCH处理能力2的N1取值；否则N3取值为N 3＝8对应μ＝0,N 3＝10对应μ＝1,N 3＝17对应μ＝2,N 3＝20对应μ＝3，即按照PDSCH处理能力1的N1取值。
下面结合附图，通过具体的实施例及其应用场景对本申请实施例提供的信息传输方法进行详细地说明。需要说明的是，本实施例提供的信息传输方法可以应用于但不限于终端使能了PUSCH的上行传输跳过(UL skipping)功能且PUSCH进行重复传输的场景。
请参见图4，图4是本申请实施例提供的一种信息传输方法的流程图，该方法可以由终端执行，如图4所示，包括以下步骤：
步骤401、在存在第一UCI在第一PUSCH传输机会上传输，或者调度第二UCI的下行控制信令的接收时刻满足预设条件的情况下，若承载第二UCI的PUCCH与第二PUSCH传输机会之间存在冲突，则在所述第二PUSCH传输机会上发送所述第二UCI；
其中，所述第一PUSCH传输机会为PUSCH重复传输的初传机会，所述第二PUSCH传输机会为所述PUSCH重复传输的重传机会。
本实施例中，上述第一UCI可以是动态调度或半静态配置的UCI，例如， 上述第一UCI可以是HARQ-ACK、CSI或SR等。上述第二UCI也可以是动态调度或半静态配置的UCI，例如，上述第二UCI也可以是HARQ-ACK、CSI或SR等。需要说明的是，上述第二UCI可以为任意的UCI，且上述第二UCI的数量可以是一个或多个。
上述第一PUSCH传输机会为上述PUSCH重复传输的初传机会，也即上述第一PUSCH传输机会用于传输块的初传，例如，对于动态调度的PUSCH重复传输，第一个PUSCH重复传输对应的传输机会用于传输块的初传，即第一个PUSCH重复传输对应的传输机会为第一PUSCH传输机会，对于半静态配置的PUSCH重复传输，对应冗余版本(Redundancy Version，RV)为0的PUSCH重复传输对应的传输机会用于传输块的初传，即对应RV为0的PUSCH重复传输对应的传输机会为第一PUSCH传输机会。
上述第二PUSCH传输机会为PUSCH重复传输的重传机会，也即上述第二PUSCH传输机会用于传输块的重传。上述PUSCH重复传输也可以称为传输块(Transport Block，TB)重复传输。其中，上述第二PUSCH传输机会可以为任意的用于传输块重传的PUSCH传输机会，且上述第二PUSCH传输机会的数量可以为一个或多个。
上述PUSCH可以为动态调度的PUSCH，例如动态授权PUSCH(Dynamic Grant PUSCH，DG PUSCH)，或者可以为半静态配置的PUSCH，例如，配置授权PUSCH(Configured Grant PUSCH，CG PUSCH)。
需要说明的是，本实施例中涉及的PUSCH传输机会也可以描述为PUSCH传输时机、PUSCH传输或PUSCH重复等。例如，上述存在第一UCI在第一PUSCH传输机会上传输也可以描述为存在第一UCI在第一PUSCH传输时机上传输，或者描述为存在第一UCI在第一PUSCH传输上传输，或者描述为存在第一UCI在第一PUSCH重复上传输等。
上述承载第二UCI的PUCCH与第二PUSCH传输机会之间存在冲突，可以理解为承载第二UCI的PUCCH和第二PUSCH传输机会在时域上有重叠。
在一实施方式中，在存在第一UCI在第一PUSCH传输机会上传输的情况下，终端允许被调度或配置承载第二UCI的PUCCH与第二PUSCH传输 机会之间存在资源冲突，也即在存在第一UCI在第一PUSCH传输机会上传输的情况下，网络设备可以调度或配置承载第二UCI的PUCCH与第二PUSCH传输机会之间存在资源冲突。具体地，在存在第一UCI在第一PUSCH传输机会上传输的情况下，若承载第二UCI的PUCCH与第二PUSCH传输机会之间存在冲突，终端可以在第二PUSCH传输机会上发送第二UCI，也即将第二UCI复用在第二PUSCH传输机会上，需要说明的是，终端可以在第二PUSCH传输机会上发送第二UCI的全部或者部分信息。
例如，如图5所示，PUSCH occasion#1用于TB的初传，PUSCH occasion#2、PUSCH occasion#3和PUSCH occasion#4用于TB的重传，PUCCH1与PUSCH occasion#1之间存在冲突，且PUCCH1承载的UCI1在PUSCH occasion#1上传输，在DCI调度PUCCH2与PUSCH occasion#3之间存在冲突的情况下，在PUSCH occasion#3上传输PUCCH2承载的UCI2。
可选地，在不存在第一UCI在第一PUSCH传输机会上传输的情况下，若承载第二UCI的PUCCH与第二PUSCH传输机会之间存在冲突终端可以不将所述第二UCI复用在所述第二PUSCH传输机会上传输，例如，终端可以丢弃所述第二UCI，或者可以在所述PUCCH上传输所述第二UCI。
可选地，终端可以期望存在第一UCI在第一PUSCH传输机会上传输。
在另一实施方式中，在调度第二UCI的下行控制信令的接收时刻满足预设条件的情况下，终端允许被调度或配置承载第二UCI的PUCCH与第二PUSCH传输机会之间存在资源冲突，也即在调度第二UCI的下行控制信令的接收时刻满足预设条件的情况下，网络设备可以调度或配置承载第二UCI的PUCCH与第二PUSCH传输机会之间存在资源冲突。具体地，在调度第二UCI的下行控制信令的接收时刻满足预设条件的情况下，若承载第二UCI的PUCCH与第二PUSCH传输机会之间存在冲突，终端可以在第二PUSCH传输机会上发送第二UCI，也即将第二UCI复用在第二PUSCH传输机会上，需要说明的是，终端可以在第二PUSCH传输机会上发送第二UCI的全部或者部分信息。
例如，如图6所示，PUSCH occasion#1用于TB的初传，PUSCH occasion#2、PUSCH occasion#3和PUSCH occasion#4用于TB的重传，在调度UCI1的DCI 的接收时刻与PUSCH occasion#1的起始时刻之间的间隔T1大于或等于预设时间间隔的情况下，若承载UCI1的PUCCH1与PUSCH occasion#3之间存在冲突，则在PUSCH occasion#3上传输UCI1。
可选地，在调度第二UCI的下行控制信令的接收时刻不满足预设条件的情况下，若承载第二UCI的PUCCH与第二PUSCH传输机会之间存在冲突，终端可以不将所述第二UCI复用在所述第二PUSCH传输机会上传输，例如，终端可以丢弃所述第二UCI，或者可以在所述PUCCH上传输所述第二UCI。
可选地，终端可以期望调度第二UCI的下行控制信令的接收时刻满足预设条件。
需要说明的是，在终端需要在第二PUSCH传输机会上发送第二UCI的情况下，若终端没有数据需要传输，则终端可以生成填充PDU；若终端有数据需要传输，可以生成承载数据的PDU。
需要说明的是，在承载第二UCI的PUCCH与第二PUSCH传输机会之间存在冲突的情况下，终端可以仅在与承载UCI的PUCCH冲突的PUSCH重传机会上发送PUSCH，例如，对于图5，可以仅在PUSCH occasion#1和PUSCH occasion#3上发送PUSCH，而在PUSCH occasion#2和PUSCH occasion#4上不发送PUSCH；对于图6，可以仅在PUSCH occasion#3上发送PUSCH，而在PUSCH occasion#1、PUSCH occasion#2和PUSCH occasion#4上不发送PUSCH。终端也可以在第一PUSCH传输机会以及第一PUSCH传输机会之后的全部的PUSCH传输机会上发送PUSCH，例如，对于图5和图6，可以在PUSCH occasion#1、PUSCH occasion#2PUSCH occasion#3和PUSCH occasion#4上均发送PUSCH。
本申请实施例提供的信息传输方法，通过在存在第一UCI在第一PUSCH传输机会上传输，或者调度第二UCI的下行控制信令的接收时刻满足预设条件的情况下，若承载第二UCI的PUCCH与第二PUSCH传输机会之间存在冲突，则在所述第二PUSCH传输机会上发送所述第二UCI，这样可以在承载UCI的PUCCH与PUSCH的重传资源冲突的情况下保证UCI的传输，并可提高传输的效率。
可选地，所述调度第二UCI的下行控制信令的接收时刻满足预设条件， 包括如下至少一项：
调度所述第二UCI的下行控制信令的接收时刻与第一时域位置之间的第一时间间隔满足预设时长条件，其中，所述第一时域位置根据所述第一PUSCH传输机会和承载所述第二UCI的PUCCH的起始时刻中的至少一项确定；
调度所述第二UCI的下行控制信令的接收时刻位于调度所述PUSCH的下行控制信令的接收时刻之前。
在一实施方式中，可以在调度所述第二UCI的下行控制信令的接收时刻与第一时域位置之间的时间间隔(即第一时间间隔)满足预设时长条件的情况下，终端允许被调度或配置承载第二UCI的PUCCH与第二PUSCH传输机会之间存在资源冲突。
其中，上述第二UCI的下行控制信令的接收时刻可以是承载该下行控制信令的PDCCH的起始时刻或结束时刻。上述第一时域位置可以根据所述第一PUSCH传输机会和承载所述第二UCI的PUCCH的起始时刻中的至少一项确定，例如，上述第一时域位置可以为所述第一PUSCH传输机会的起始时刻或结束时刻，或者上述第一时域位置可以为承载所述第二UCI的PUCCH的起始时刻等。上述预设时长条件可以根据PUSCH准备时间、UCI复用时间和PDSCH处理时间等中的至少一项设置。
在另一实施方式中，在调度所述第二UCI的下行控制信令的接收时刻位于调度所述PUSCH的下行控制信令的接收时刻之前的情况下，终端允许被调度或配置承载第二UCI的PUCCH与第二PUSCH传输机会之间存在资源冲突。其中，上述PUSCH可以是动态调度的PUSCH。
可选地，所述第一时域位置可以为如下一项：
所述第一PUSCH传输机会的起始时刻；
承载所述第二UCI的PUCCH的起始时刻；
所述第一PUSCH传输机会的起始时刻和承载所述第二UCI的PUCCH的起始时刻中较早的时刻。
在一实施方式中，可以在调度所述第二UCI的下行控制信令的接收时刻与所述第一PUSCH传输机会的起始时刻之间的第一时间间隔满足预设时长 条件的情况下，终端允许被调度或配置承载第二UCI的PUCCH与第二PUSCH传输机会之间存在资源冲突。
在另一实施方式中，可以在调度所述第二UCI的下行控制信令的接收时刻与承载所述第二UCI的PUCCH的起始时刻之间的第一时间间隔满足预设时长条件的情况下，终端允许被调度或配置承载第二UCI的PUCCH与第二PUSCH传输机会之间存在资源冲突。
在另一实施方式中，可以在调度所述第二UCI的下行控制信令的接收时刻与所述第一PUSCH传输机会的起始时刻和承载所述第二UCI的PUCCH的起始时刻中较早的时刻之间的第一时间间隔满足预设时长条件的情况下，终端允许被调度或配置承载第二UCI的PUCCH与第二PUSCH传输机会之间存在资源冲突。
可选地，所述第一时间间隔满足预设时长条件可以包括如下至少一项：
所述第一时间间隔大于或等于PUSCH准备时间；
所述第一时间间隔大于或等于UCI复用时间；
所述第一时间间隔大于或等于PDSCH处理时间；
所述第一时间间隔大于或等于PUCCH准备时间。
本实施例中，上述PUSCH准备时间，也即Tproc,1。上述UCI复用时间可以包括第一复用时间和第二复用时间中的至少一项，其中，上述第一复用时间，也即Tproc,1+1，上述第二复用时间也即Tproc,2+1。上述PUCCH准备时间也即N3。
可选地，所述第一PUSCH传输机会可以为所述PUSCH重复传输中距离所述第二PUSCH传输机会最近的初传机会。
例如，如图7所示，CG PUSCH occasion#1和CG PUSCH occasion#3均用于传输块的初传，也即CG PUSCH occasion#1和CG PUSCH occasion#3均为PUSCH重复传输中的初传机会，CG PUSCH occasion#2和CG PUSCH occasion#4均用于传输块的重传，也即CG PUSCH occasion#2和CG PUSCH occasion#4均为PUSCH重复传输中的重传机会，其中，CG PUSCH occasion#4与PUCCH2之间存在资源冲突，距离CG PUSCH occasion#4最近的初传机会为CG PUSCH occasion#3，即第一PUSCH传输机会为CG PUSCH  occasion#3。
又例如，如图8所示，CG PUSCH occasion#1和CG PUSCH occasion#3均用于传输块的初传，CG PUSCH occasion#2和CG PUSCH occasion#4均用于传输块的重传，CG PUSCH occasion#4与PUCCH2之间存在资源冲突，距离CG PUSCH occasion#4最近的初传机会为CG PUSCH occasion#3，即第一PUSCH传输机会为CG PUSCH occasion#3。
可选地，所述方法还可以包括：
在承载所述第二UCI的PUCCH与所述第二PUSCH传输机会之间存在冲突的情况下，在第三PUSCH传输机会上发送PUSCH；
其中，所述第三PUSCH传输机会为所述PUSCH重复传输中位于所述第一PUSCH传输机会之后的PUSCH传输机会，且所述第三PUSCH传输机会与所述第二PUSCH传输机会不同。
本实施例中，上述第三PUSCH传输机会与PUCCH不冲突。具体地，在承载所述第二UCI的PUCCH与所述第二PUSCH传输机会之间存在冲突的情况下，终端可以在所述PUSCH重复传输中位于所述第一PUSCH传输机会之后的全部PUSCH传输机会上发送PUSCH，也即在与承载UCI的PUCCH冲突的PUSCH传输机会以及与承载UCI的PUCCH不冲突的PUSCH传输机会上均发送PUSCH。
可选地，在调度第二UCI的下行控制信令的接收时刻满足预设条件的情况下，若承载第二UCI的PUCCH与第二PUSCH传输机会之间存在冲突，则终端可以在第一PUSCH传输机会以及位于第一PUSCH传输机会之后的全部的PUSCH传输机会上均发送PUSCH。例如，对于图8，可以在CG PUSCH occasion#3和CG PUSCH occasion#4上均发送PUSCH。
可选地，在不存在第一UCI在第一PUSCH传输机会上传输的情况下，所述终端不期望网络设备调度或配置承载第二UCI的PUCCH与第二PUSCH传输机会之间存在冲突。
本实施例中，在不存在第一UCI在第一PUSCH传输机会上传输的情况下，为了保证UCI的传输，终端不期望网络设备调度或配置承载第二UCI的PUCCH与第二PUSCH传输机会之间存在冲突。
例如，如图9所示，由于CG PUSCH occasion#3，也即第一PUSCH传输机会上不存在UCI传输，因此，终端不期望DCI调度的PUCCH2与CG PUSCH occasion#4之间存在冲突。
又例如，如图10所示，由于PUSCH occasion#1，也即第一PUSCH传输机会上不存在UCI传输，因此，终端不期望DCI调度的PUCCH2与CG PUSCH occasion#3之间存在冲突。
可选地，在调度第二UCI的下行控制信令的接收时刻不满足预设条件的情况下，所述终端不期望网络设备调度或配置承载第二UCI的PUCCH与第二PUSCH传输机会之间存在冲突。
本实施例中，在调度第二UCI的下行控制信令的接收时刻不满足预设条件的情况下，为了保证UCI的传输，终端不期望网络设备调度或配置承载第二UCI的PUCCH与第二PUSCH传输机会之间存在冲突。
例如，如图11所示，由于调度PUCCH1的DCI的接收时刻与PUSCH occasion#1的起始时刻之间的时间间隔不满足预设时长条件，因此终端不期望DCI调度的PUCCH1与CG PUSCH occasion#3之间存在冲突。
实际应用中，在不存在第一UCI在第一PUSCH传输机会上传输或者调度第二UCI的下行控制信令的接收时刻不满足预设条件的情况下，若终端被调度或配置承载第二UCI的PUCCH与第二PUSCH传输机会之间存在冲突，可能会导致第二UCI无法复用在第二PUSCH传输机会上。例如，当终端的PUSCH使能了上行传输跳过功能且终端没有需要传输的数据时，在不存在第一UCI在第一PUSCH传输机会上传输的情况下，终端会确定不进行PUSCH传输，此时若终端被调度或配置承载UCI的PUCCH与PUSCH重传机会之间存在冲突，则该UCI无法复用在与承载该UCI的PUCCH冲突的PUSCH重传机会上，进而导致UCI发送失败。因此，在不存在第一UCI在第一PUSCH传输机会上传输的情况下，网络设备调度或配置承载第二UCI的PUCCH与第二PUSCH传输机会之间不存在冲突，可以保证UCI的传输。
可选地，所述第二UCI的传输优先级和与所述第二UCI冲突的PUSCH的传输优先级相同；
或者
所述第二UCI的传输优先级和与所述第二UCI冲突的PUSCH的传输优先级不相同。
请参见图12，图12是本申请实施例提供的另一种信息传输方法的流程图，该方法由网络设备执行，如图12所示，包括以下步骤：
步骤1201、在存在第一UCI在第一PUSCH传输机会上传输，或者调度第二UCI的下行控制信令的接收时刻满足预设条件的情况下，若承载第二UCI的PUCCH与第二PUSCH传输机会之间存在冲突，则在所述第二PUSCH传输机会上接收所述第二UCI；
其中，所述第一PUSCH传输机会为PUSCH重复传输的初传机会，所述第二PUSCH传输机会为所述PUSCH重复传输的重传机会。
在一实施方式中，在存在第一UCI在第一PUSCH传输机会上传输的情况下，网络设备可以调度或配置承载第二UCI的PUCCH与第二PUSCH传输机会之间存在资源冲突。具体地，在存在第一UCI在第一PUSCH传输机会上传输的情况下，若网络设备调度或配置承载第二UCI的PUCCH与第二PUSCH传输机会之间存在冲突，网络设备可以在第二PUSCH传输机会上接收第二UCI。
在另一实施方式中，在调度第二UCI的下行控制信令的接收时刻满足预设条件的情况下，网络设备可以调度或配置承载第二UCI的PUCCH与第二PUSCH传输机会之间存在资源冲突。具体地，在调度第二UCI的下行控制信令的接收时刻满足预设条件的情况下，若网络设备调度或配置承载第二UCI的PUCCH与第二PUSCH传输机会之间存在冲突，网络设备可以在第二PUSCH传输机会上接收第二UCI。
需要说明的是，在存在第一UCI在第一PUSCH传输机会上传输，或者调度第二UCI的下行控制信令的接收时刻满足预设条件的情况下，网络设备可以调度或配置承载第二UCI的PUCCH与第二PUSCH传输机会之间存在资源冲突，也可以调度或配置承载第二UCI的PUCCH与第二PUSCH传输机会之间不存在资源冲突。
需要说明的是，本实施例作为图4所示的实施例对应的网络设备的实施方式，其具体的实施方式可以参见图4所示的实施例相关说明，以及达到相同的有益效果，为了避免重复说明，此处不再赘述。
本申请实施例提供的信息传输方法，网络设备在存在第一UCI在第一PUSCH传输机会上传输，或者调度第二UCI的下行控制信令的接收时刻满足预设条件的情况下，若承载第二UCI的PUCCH与第二PUSCH传输机会之间存在冲突，则在所述第二PUSCH传输机会上接收所述第二UCI，可以保证UCI的传输。
可选地，所述调度第二UCI的下行控制信令的接收时刻满足预设条件，包括如下至少一项：
调度所述第二UCI的下行控制信令的接收时刻与第一时域位置之间的第一时间间隔满足预设时长条件，其中，所述第一时域位置根据所述第一PUSCH传输机会和承载所述第二UCI的PUCCH的起始时刻中的至少一项确定；
调度所述第二UCI的下行控制信令的接收时刻位于调度所述PUSCH的下行控制信令的接收时刻之前。
该实施方式的实现方式可以参见图4所示的实施例的相关说明，此处不作赘述。
可选地，所述第一时域位置为如下一项：
所述第一PUSCH传输机会的起始时刻；
承载所述第二UCI的PUCCH的起始时刻；
所述第一PUSCH传输机会的起始时刻和承载所述第二UCI的PUCCH的起始时刻中较早的时刻。
该实施方式的实现方式可以参见图4所示的实施例的相关说明，此处不作赘述。
可选地，所述第一时间间隔满足预设时长条件包括如下至少一项：
所述第一时间间隔大于或等于PUSCH准备时间；
所述第一时间间隔大于或等于UCI复用时间；
所述第一时间间隔大于或等于PDSCH处理时间；
所述第一时间间隔大于或等于PUCCH准备时间。
该实施方式的实现方式可以参见图4所示的实施例的相关说明，此处不作赘述。
可选地，所述第一PUSCH传输机会为所述PUSCH重复传输中距离所述第二PUSCH传输机会最近的初传机会。
该实施方式的实现方式可以参见图4所示的实施例的相关说明，此处不作赘述。
可选地，所述方法还包括：
在不存在第一UCI在第一PUSCH传输机会上传输的情况下，调度或配置承载第二UCI的PUCCH与第二PUSCH传输机会之间不存在冲突。
本实施例中，在不存在第一UCI在第一PUSCH传输机会上传输的情况下，网络设备调度或配置第二UCI的PUCCH与第二PUSCH传输机会之间不存在冲突，以保证UCI的传输。
可选地，所述方法还包括：
在调度第二UCI的下行控制信令的接收时刻不满足预设条件的情况下，调度或配置承载第二UCI的PUCCH与第二PUSCH传输机会之间不存在冲突。
本实施例中，在调度第二UCI的下行控制信令的接收时刻不满足预设条件的情况下，网络设备调度或配置承载第二UCI的PUCCH与第二PUSCH传输机会之间不存在冲突，以保证UCI的传输。
可选地，所述方法还可以包括：
在承载所述第二UCI的PUCCH与所述第二PUSCH传输机会之间存在冲突的情况下，在第三PUSCH传输机会上接收PUSCH；
其中，所述第三PUSCH传输机会为所述PUSCH重复传输中位于所述第一PUSCH传输机会之后的PUSCH传输机会，且所述第三PUSCH传输机会与所述第二PUSCH传输机会不同。
本实施例中，在承载所述第二UCI的PUCCH与所述第二PUSCH传输机会之间存在冲突的情况下，网络设备可以在所述PUSCH重复传输中位于所述第一PUSCH传输机会之后的全部PUSCH传输机会上接收PUSCH，也即在与承载UCI的PUCCH冲突的PUSCH传输机会以及与承载UCI的PUCCH不冲突的PUSCH传输机会上均接收PUSCH。
可选地，在调度第二UCI的下行控制信令的接收时刻满足预设条件的情 况下，若承载第二UCI的PUCCH与第二PUSCH传输机会之间存在冲突，则网络设备可以在第一PUSCH传输机会以及位于第一PUSCH传输机会之后的全部的PUSCH传输机会上均接收PUSCH。
可选地，所述第二UCI的传输优先级和与所述第二UCI冲突的PUSCH的传输优先级相同；
或者
所述第二UCI的传输优先级和与所述第二UCI冲突的PUSCH的传输优先级不相同。
为了便于理解，以下结合示例对本申请实施例提供的信息传输方法进行说明，需要说明的是，对于下述示例，终端使能了PUSCH的上行传输跳过(UL skipping)功能，且PUSCH进行重复传输。
示例一：
当存在第一UCI复用在第一CG PUSCH传输机会上时，则UE允许被调度或配置有第二UCI与第二CG PUSCH传输机会之间存在资源冲突，并且UE将第二UCI复用在第二CG PUSCH传输机会上，上述CG PUSCH为半静态配置的PUSCH，其中：
第一CG PUSCH传输机会对应TB的初传机会，也即对应RV＝0的CG PUSCH传输机会，可选地，第一CG PUSCH传输机会为上一个最近的RV＝0的CG PUSCH传输机会；
第二CG PUSCH传输机会对应TB的重传机会，也即对应RV≠0的CG PUSCH传输机会；
第二UCI可以包括一个或多个UCI，第二PUSCH传输机会可以包括一个或多个用于TB重复传输的重传机会。
例如，如图7所示，CG PUSCH occasion#1和CG PUSCH occasion#3均用于传输块的初传，CG PUSCH occasion#2和CG PUSCH occasion#4均用于传输块的重传，由于存在UCI1在CG PUSCH occasion#3上传输，因此，UE允许DCI调度的PUCCH2与CG PUSCH occasion#4之间存在资源冲突，并将PUCCH2承载的UCI2在CG PUSCH occasion#4上传输。需要说明的是，对于CG PUSCH occasion#1和CG PUSCH occasion#2，由于没有数据传输且 没有PUCCH与其重叠，则在CG PUSCH occasion#1和CG PUSCH occasion#2上不发送PUSCH。
需要说明的是，当不存在第一UCI复用在第一CG PUSCH传输机会上时，则UE不期望被调度或配置有第二UCI与第二CG PUSCH传输机会之间存在资源冲突。例如，如图9所示，CG PUSCH occasion#1和CG PUSCH occasion#3均用于传输块的初传，CG PUSCH occasion#2和CG PUSCH occasion#4均用于传输块的重传，由于不存在UCI在CG PUSCH occasion#3上传输，因此，UE不期望DCI调度的PUCCH2与CG PUSCH occasion#4之间存在资源冲突。
示例二：
当存在第一UCI复用在第一DG PUSCH传输机会上时，则UE允许被调度有第二UCI与第二DG PUSCH传输机会有资源冲突，并且UE将第二UCI复用在第二DG PUSCH传输机会上，上述DG PUSCH可动态调度的PUSCH，其中：
第一PUSCH传输机会为PUSCH重复传输中的第一个传输机会；
第二PUSCH传输机会为PUSCH重复传输中除了第一个传输机会以外的传输机会。
示例三：
当不存在第一UCI复用在第一PUSCH传输机会上时，则UE不期望被调度或配置有第二UCI与第二PUSCH传输机会之间存在资源冲突，其中：
第一PUSCH传输机会对应TB的初传机会，可选地，第一PUSCH传输机会可以为上一个最近的初传机会；
第二PUSCH传输机会对应TB的重传机会。
例如，如图10所示，PUSCH occasion#1用于TB的初传，PUSCH occasion#2、PUSCH occasion#3和PUSCH occasion#4用于TB的重传，由于PUSCH occasion#1，也即第一PUSCH传输机会上不存在UCI传输，因此，终端不期望DCI调度的PUCCH2与CG PUSCH occasion#3之间存在冲突。
示例四：
当存在第一UCI复用在第一PUSCH传输机会上时，则UE允许被调度 或配置有第二UCI与第二PUSCH传输机会之间存在资源冲突，UE将第二UCI复用在第二PUSCH传输机会上，其中：
第一PUSCH传输机会对应TB的初传机会，可选地，第一PUSCH传输机会可以为上一个最近的初传机会；
第二PUSCH传输机会对应TB的重传机会。
在一实施方式中，UE可以在第一PUSCH传输机会发送PUSCH，且在与第二UCI冲突的第二PUSCH传输机会上发送PUSCH。
例如，如图13所示CG PUSCH occasion#1和CG PUSCH occasion#3均用于传输块的初传，CG PUSCH occasion#2和CG PUSCH occasion#4均用于传输块的重传，CG PUSCH occasion#1与PUCCH1之间存在资源冲突，CG PUSCH occasion#4与PUCCH2之间存在资源冲突，则在CG PUSCH occasion#1和CG PUSCH occasion#4上发送PUSCH。
在另一实施方式中，UE在第一PUSCH传输机会之后的所有PUSCH传输机会(包括与第二UCI冲突或不冲突的PUSCH传输机会)均发送PUSCH。
例如，如图14所示，CG PUSCH occasion#1和CG PUSCH occasion#3均用于传输块的初传，CG PUSCH occasion#2和CG PUSCH occasion#4均用于传输块的重传，CG PUSCH occasion#1与PUCCH1之间存在资源冲突，CG PUSCH occasion#4与PUCCH2之间存在资源冲突，则在CG PUSCH occasion#1、CG PUSCH occasion#2、CG PUSCH occasion#3和CG PUSCH occasion#4上均发送PUSCH。
示例五：
当调度第二UCI的下行控制信令的接收时刻与第一时域位置之间的第一时间间隔大于或等于第一时长，则UE允许被调度或配置该第二UCI与第二CG PUSCH传输机会之间存在资源冲突，UE将第二UCI复用在第二CG PUSCH传输机会上，其中：
第一时域位置为第一CG PUSCH传输机会的起始时刻；
第一CG PUSCH传输机会对应TB的初传机会，也即对应RV＝0的CG PUSCH传输机会，可选地，第一PUSCH传输机会为上一个最近的RV＝0的CG PUSCH传输机会；
第二CG PUSCH传输机会对应TB的重传机会，也即对应RV≠0的CG PUSCH传输机会；
第一时长为UCI复用时间；
UE仅在与第二UCI冲突的CG PUSCH传输机会上传输PUSCH，或者在第一CG PUSCH传输机会以及第一CG PUSCH传输机会之后的所有CG PUSCH传输机会上均传输PUSCH。
例如，如图8所示，CG PUSCH occasion#1和CG PUSCH occasion#3均用于传输块的初传，CG PUSCH occasion#2和CG PUSCH occasion#4均用于传输块的重传，调度PUCCH2的DCI的接收时刻和CG PUSCH occasion#3的起始时刻之间的时间间隔大于或等于UCI复用时间，则UE在CG occasion#4上传输PUSCH，或在CG PUSCH occasion#3和#4上均传输PUSCH。
需要说明的是，对于CG PUSCH occasion#1和CG PUSCH occasion#2，由于没有数据传输且没有PUCCH与其重叠，则在CG PUSCH occasion#1和CG PUSCH occasion#2上不发送PUSCH。
示例六：
当调度第二UCI的下行控制信令的接收时刻与第一时域位置之间的时间间隔大于或等于第一时长时，则UE允许被调度或配置该第二UCI与第二DG PUSCH传输机会之间存在资源冲突，UE将第二UCI复用在第二DG PUSCH传输机会上，其中：
第一时域位置为第一DG PUSCH传输机会的起始时刻；
第一PUSCH传输机会为PUSCH重复传输中的第一个传输机会；
第二PUSCH传输机会为PUSCH重复传输中除第一个传输机会以外的传输机会；
第一时长为UCI复用时间。
示例七：
当调度第二UCI的下行控制信令的接收时刻与第一时域位置之间的时间间隔小于第一时长时，则UE不期望被调度或配置该第二UCI与第二PUSCH传输机会有资源冲突，其中：
第一时域位置为承载第二UCI的PUCCH的起始时刻，或者第一时域位 置为第一PUSCH传输机会的起始时刻，或者第一时域位置为承载第二UCI的PUCCH的起始时刻和第一PUSCH传输机会的起始时刻中较早的时刻；
第一时长可以为PUSCH准备时间、UCI复用时间和PDSCH处理时间中的至少一项；
第一PUSCH传输机会对应TB的初传，第二PUSCH传输机会对应TB的重传。
例如，如图11所示，由于调度PUCCH1的DCI的接收时刻与PUSCH occasion#1的起始时刻之间的时间间隔小于第一时长，因此终端不期望DCI调度的PUCCH1与CG PUSCH occasion#3之间存在冲突。
示例八：
对于动态调度的PUSCH(含PUSCH重复传输)，当调度第二UCI的下行控制信令的接收时刻位于调度该PUSCH的下行控制信令的接收时刻之前，则UE允许被调度第二UCI与该PUSCH的任一重复传输有资源冲突，UE将第二UCI复用在与承载该第二UCI的PUCCH冲突的PUSCH传输机会上。
在一实施方式中，UE仅在与UCI冲突的PUSCH传输机会上发送PUSCH。
具体地，在第一PUSCH传输机会发送PUSCH，且在与第二UCI冲突的PUSCH传输机会上发送PUSCH。
在另一实施方式中，UE在所有PUSCH传输机会(包括与UCI冲突或不冲突的PUSCH传输机会)上发送PUSCH。
需要说明的是，本申请实施例提供的信息传输方法，可适用于单载波和多载波，以及授权频段或非授权频段，即PUSCH重复传输和PUCCH可以是在同一个载波或不同载波上。
请参见图15，图15是本申请实施例提供的一种信息传输装置的结构图，如图15所示，信息传输装置1500包括：
第一发送模块1501，用于在存在第一上行控制信息UCI在第一物理上行共享信道PUSCH传输机会上传输，或者调度第二UCI的下行控制信令的接收时刻满足预设条件的情况下，若承载第二UCI的物理上行控制信道PUCCH与第二PUSCH传输机会之间存在冲突，则在所述第二PUSCH传输机会上发送所述第二UCI；
其中，所述第一PUSCH传输机会为PUSCH重复传输的初传机会，所述第二PUSCH传输机会为所述PUSCH重复传输的重传机会。
可选地，所述调度第二UCI的下行控制信令的接收时刻满足预设条件，包括如下至少一项：
调度所述第二UCI的下行控制信令的接收时刻与第一时域位置之间的第一时间间隔满足预设时长条件，其中，所述第一时域位置根据所述第一PUSCH传输机会和承载所述第二UCI的PUCCH的起始时刻中的至少一项确定；
调度所述第二UCI的下行控制信令的接收时刻位于调度所述PUSCH的下行控制信令的接收时刻之前。
可选地，所述第一时域位置为如下一项：
所述第一PUSCH传输机会的起始时刻；
承载所述第二UCI的PUCCH的起始时刻；
所述第一PUSCH传输机会的起始时刻和承载所述第二UCI的PUCCH的起始时刻中较早的时刻。
可选地，所述第一时间间隔满足预设时长条件包括如下至少一项：
所述第一时间间隔大于或等于PUSCH准备时间；
所述第一时间间隔大于或等于UCI复用时间；
所述第一时间间隔大于或等于物理下行共享信道PDSCH处理时间；
所述第一时间间隔大于或等于PUCCH准备时间。
可选地，所述第一PUSCH传输机会为所述PUSCH重复传输中距离所述第二PUSCH传输机会最近的初传机会。
可选地，所述装置还包括：
第二发送模块，用于在承载所述第二UCI的PUCCH与所述第二PUSCH传输机会之间存在冲突的情况下，在第三PUSCH传输机会上发送PUSCH；
其中，所述第三PUSCH传输机会为所述PUSCH重复传输中位于所述第一PUSCH传输机会之后的PUSCH传输机会，且所述第三PUSCH传输机会与所述第二PUSCH传输机会不同。
可选地，在不存在第一UCI在第一PUSCH传输机会上传输的情况下， 所述装置不期望网络设备调度或配置承载第二UCI的PUCCH与第二PUSCH传输机会之间存在冲突。
可选地，在调度第二UCI的下行控制信令的接收时刻不满足预设条件的情况下，所述装置不期望网络设备调度或配置承载第二UCI的PUCCH与第二PUSCH传输机会之间存在冲突。
可选地，所述第二UCI的传输优先级和与所述第二UCI冲突的PUSCH的传输优先级相同；
或者
所述第二UCI的传输优先级和与所述第二UCI冲突的PUSCH的传输优先级不相同。
本申请实施例提供的信息传输装置能够实现图4的方法实施例中各个过程，为避免重复，这里不再赘述。
需要说明的是，本申请实施例中的信息传输装置可以是装置，也可以是终端中的部件、集成电路、或芯片。
请参见图16，图16是本申请实施例提供的另一种信息传输装置的结构图，如图16所示，信息传输装置1600包括：
第一接收模块1601，用于在存在第一上行控制信息UCI在第一物理上行共享信道PUSCH传输机会上传输，或者调度第二UCI的下行控制信令的接收时刻满足预设条件的情况下，若承载第二UCI的物理上行控制信道PUCCH与第二PUSCH传输机会之间存在冲突，则在所述第二PUSCH传输机会上接收所述第二UCI；
其中，所述第一PUSCH传输机会为PUSCH重复传输的初传机会，所述第二PUSCH传输机会为所述PUSCH重复传输的重传机会。
可选地，所述调度第二UCI的下行控制信令的接收时刻满足预设条件，包括如下至少一项：
调度所述第二UCI的下行控制信令的接收时刻与第一时域位置之间的第一时间间隔满足预设时长条件，其中，所述第一时域位置根据所述第一PUSCH传输机会和承载所述第二UCI的PUCCH的起始时刻中的至少一项确定；
调度所述第二UCI的下行控制信令的接收时刻位于调度所述PUSCH的下行控制信令的接收时刻之前。
可选地，所述第一时域位置为如下一项：
所述第一PUSCH传输机会的起始时刻；
承载所述第二UCI的PUCCH的起始时刻；
所述第一PUSCH传输机会的起始时刻和承载所述第二UCI的PUCCH的起始时刻中较早的时刻。
可选地，所述第一时间间隔满足预设时长条件包括如下至少一项：
所述第一时间间隔大于或等于PUSCH准备时间；
所述第一时间间隔大于或等于UCI复用时间；
所述第一时间间隔大于或等于物理下行共享信道PDSCH处理时间；
所述第一时间间隔大于或等于PUCCH准备时间。
可选地，所述第一PUSCH传输机会为所述PUSCH重复传输中距离所述第二PUSCH传输机会最近的初传机会。
可选地，所述装置还包括：
第一配置模块，用于在不存在第一UCI在第一PUSCH传输机会上传输的情况下，调度或配置承载第二UCI的PUCCH与第二PUSCH传输机会之间不存在冲突。
可选地，所述装置还包括：
第二配置模块，用于在调度第二UCI的下行控制信令的接收时刻不满足预设条件的情况下，调度或配置承载第二UCI的PUCCH与第二PUSCH传输机会之间不存在冲突。
可选地，所述装置还包括：
第二接收模块，用于在承载所述第二UCI的PUCCH与所述第二PUSCH传输机会之间存在冲突的情况下，在第三PUSCH传输机会上接收PUSCH；
其中，所述第三PUSCH传输机会为所述PUSCH重复传输中位于所述第一PUSCH传输机会之后的PUSCH传输机会，且所述第三PUSCH传输机会与所述第二PUSCH传输机会不同。
可选地，所述第二UCI的传输优先级和与所述第二UCI冲突的PUSCH 的传输优先级相同；
或者
所述第二UCI的传输优先级和与所述第二UCI冲突的PUSCH的传输优先级不相同。
本申请实施例提供的信息传输装置能够实现图12的方法实施例中各个过程，为避免重复，这里不再赘述。
需要说明的是，本申请实施例中的信息传输装置可以是装置，也可以是网络设备中的部件、集成电路、或芯片。
请参见图17，图17是本申请实施例提供的一种终端的结构图。如图17所示，该终端1700包括但不限于：射频单元1701、网络模块1702、音频输出单元1703、输入单元1704、传感器1705、显示单元1706、用户输入单元1707、接口单元1708、存储器1709以及处理器1710等部件。
本领域技术人员可以理解，终端1700还可以包括给各个部件供电的电源(比如电池)，电源可以通过电源管理系统与处理器1710逻辑相连，从而通过电源管理系统实现管理充电、放电、以及功耗管理等功能。图17中示出的终端结构并不构成对终端的限定，终端可以包括比图示更多或更少的部件，或者组合某些部件，或者不同的部件布置，在此不再赘述。
应理解的是，本申请实施例中，输入单元1704可以包括图形处理器(Graphics Processing Unit，GPU)17041和麦克风17042，图形处理器17041对在视频捕获模式或图像捕获模式中由图像捕获装置(如摄像头)获得的静态图片或视频的图像数据进行处理。显示单元1706可包括显示面板17061，可以采用液晶显示器、有机发光二极管等形式来配置显示面板17061。用户输入单元1707包括触控面板17071以及其他输入设备17072。触控面板17071，也称为触摸屏。触控面板17071可包括触摸检测装置和触摸控制器两个部分。其他输入设备17072可以包括但不限于物理键盘、功能键(比如音量控制按键、开关按键等)、轨迹球、鼠标、操作杆，在此不再赘述。
本申请实施例中，射频单元1701将来自网络设备的下行数据接收后，给处理器1710处理；另外，将上行的数据发送给网络设备。通常，射频单元1701包括但不限于天线、至少一个放大器、收发信机、耦合器、低噪声放大 器、双工器等。
存储器1709可用于存储软件程序或指令以及各种数据。存储器109可主要包括存储程序或指令区和存储数据区，其中，存储程序或指令区可存储操作系统、至少一个功能所需的应用程序或指令(比如声音播放功能、图像播放功能等)等。此外，存储器1709可以包括高速随机存取存储器，还可以包括非易失性存储器，其中，非易失性存储器可以是只读存储器(Read-Only Memory，ROM)、可编程只读存储器(Programmable ROM，PROM)、可擦除可编程只读存储器(Erasable PROM，EPROM)、电可擦除可编程只读存储器(Electrically EPROM，EEPROM)或闪存。例如至少一个磁盘存储器件、闪存器件、或其他非易失性固态存储器件。
处理器1710可包括一个或多个处理单元；可选的，处理器1710可集成应用处理器和调制解调处理器，其中，应用处理器主要处理操作系统、用户界面和应用程序或指令等，调制解调处理器主要处理无线通信，如基带处理器。可以理解的是，上述调制解调处理器也可以不集成到处理器1710中。
其中，射频单元1701，用于在存在第一上行控制信息UCI在第一物理上行共享信道PUSCH传输机会上传输，或者调度第二UCI的下行控制信令的接收时刻满足预设条件的情况下，若承载第二UCI的物理上行控制信道PUCCH与第二PUSCH传输机会之间存在冲突，则在所述第二PUSCH传输机会上发送所述第二UCI；其中，所述第一PUSCH传输机会为PUSCH重复传输的初传机会，所述第二PUSCH传输机会为所述PUSCH重复传输的重传机会。
应理解，本实施例中，上述处理器1710和射频单元1701能够实现图4的方法实施例中终端实现的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
可选地，本申请实施例还提供一种终端，包括处理器1710，存储器1709，存储在存储器17089上并可在所述处理器1710上运行的程序或指令，该程序或指令被处理器1710执行时实现上述终端侧的信息传输方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
请参见图18，图18是本申请实施例提供的一种网络设备的结构图，该 网络设备1800包括：处理器1801、收发机1802、存储器1803和总线接口，其中：
收发机1802，用于在存在第一上行控制信息UCI在第一物理上行共享信道PUSCH传输机会上传输，或者调度第二UCI的下行控制信令的接收时刻满足预设条件的情况下，若承载第二UCI的物理上行控制信道PUCCH与第二PUSCH传输机会之间存在冲突，则在所述第二PUSCH传输机会上接收所述第二UCI；其中，所述第一PUSCH传输机会为PUSCH重复传输的初传机会，所述第二PUSCH传输机会为所述PUSCH重复传输的重传机会。
应理解，本实施例中，上述处理器1801和收发机1802能够实现图12的方法实施例中网络设备实现的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
需要说明的是，收发机1802，用于在处理器1801的控制下接收和发送数据，所述收发机1802包括至少两个天线端口。
在图18中，总线架构可以包括任意数量的互联的总线和桥，具体由处理器1801代表的一个或多个处理器和存储器1803代表的存储器的各种电路链接在一起。总线架构还可以将诸如外围设备、稳压器和功率管理电路等之类的各种其他电路链接在一起，这些都是本领域所公知的，因此，本文不再对其进行进一步描述。总线接口提供接口。收发机1802可以是多个元件，即包括发送机和接收机，提供用于在传输介质上与各种其他装置通信的单元。针对不同的用户设备，用户接口1804还可以是能够外接内接需要设备的接口，连接的设备包括但不限于小键盘、显示器、扬声器、麦克风、操纵杆等。
处理器1801负责管理总线架构和通常的处理，存储器1803可以存储处理器1801在执行操作时所使用的数据。
可选地，本申请实施例还提供一种网络设备，包括处理器1801，存储器1803，存储在存储器1803上并可在所述处理器1801上运行的程序或者指令，该程序或者指令被处理器1801执行时实现上述网络设备侧的信息传输方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
本申请实施例还提供一种可读存储介质，所述可读存储介质可以是非易失的，也可以是易失的，所述可读存储介质上存储有程序或指令，该程序或 指令被处理器执行时实现上述终端侧的信息传输方法或者网络设备侧的信息传输方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
其中，所述处理器为上述实施例中所述的电子设备中的处理器。所述可读存储介质，包括计算机可读存储介质，如计算机只读存储器(Read-Only Memory，ROM)、随机存取存储器(Random Access Memory，RAM)、磁碟或者光盘等。
本申请实施例另提供了一种芯片，所述芯片包括处理器和通信接口，所述通信接口和所述处理器耦合，所述处理器用于运行网络设备程序或指令，实现上述终端侧的信息传输方法或者网络设备侧的信息传输方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
应理解，本申请实施例提到的芯片还可以称为系统级芯片、系统芯片、芯片系统或片上系统芯片等。
本申请实施例另提供了一种计算机程序产品，其中，所述计算机程序产品被存储在非瞬态的可读存储介质中，所述计算机程序产品被至少一个处理器执行以实现上述终端侧的信息传输方法或者网络设备侧的信息传输方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
本申请实施例另提供了一种通信设备，所述通信设备被配置为执行实现上述终端侧的信息传输方法或者网络设备侧的信息传输方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
需要说明的是，在本文中，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、物品或者装置不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、物品或者装置所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括该要素的过程、方法、物品或者装置中还存在另外的相同要素。此外，需要指出的是，本申请实施方式中的方法和装置的范围不限按示出或讨论的顺序来执行功能，还可包括根据所涉及的功能按基本同时的方式或按相反的顺序来执行功能，例如，可以按不同于所描述的次序来执行所描述的方法，并且还可以添加、省 去、或组合各种步骤。另外，参照某些示例所描述的特征可在其他示例中被组合。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到上述实施例方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件，但很多情况下前者是更佳的实施方式。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中，包括若干指令用以使得一台终端(可以是手机，计算机，服务器，或者基站等)执行本申请各个实施例所述的方法。
上面结合附图对本申请的实施例进行了描述，但是本申请并不局限于上述的具体实施方式，上述的具体实施方式仅仅是示意性的，而不是限制性的，本领域的普通技术人员在本申请的启示下，在不脱离本申请宗旨和权利要求所保护的范围情况下，还可做出很多形式，均属于本申请的保护之内。

Claims (39)

  1. 一种信息传输方法，由终端执行，所述方法包括：
    在存在第一上行控制信息UCI在第一物理上行共享信道PUSCH传输机会上传输，或者调度第二UCI的下行控制信令的接收时刻满足预设条件的情况下，若承载第二UCI的物理上行控制信道PUCCH与第二PUSCH传输机会之间存在冲突，则在所述第二PUSCH传输机会上发送所述第二UCI；
    其中，所述第一PUSCH传输机会为PUSCH重复传输的初传机会，所述第二PUSCH传输机会为所述PUSCH重复传输的重传机会。
  2. 根据权利要求1所述的方法，其中，所述调度第二UCI的下行控制信令的接收时刻满足预设条件，包括如下至少一项：
    调度所述第二UCI的下行控制信令的接收时刻与第一时域位置之间的第一时间间隔满足预设时长条件，其中，所述第一时域位置根据所述第一PUSCH传输机会和承载所述第二UCI的PUCCH的起始时刻中的至少一项确定；
    调度所述第二UCI的下行控制信令的接收时刻位于调度所述PUSCH的下行控制信令的接收时刻之前。
  3. 根据权利要求2所述的方法，其中，所述第一时域位置为如下一项：
    所述第一PUSCH传输机会的起始时刻；
    承载所述第二UCI的PUCCH的起始时刻；
    所述第一PUSCH传输机会的起始时刻和承载所述第二UCI的PUCCH的起始时刻中较早的时刻。
  4. 根据权利要求2所述的方法，其中，所述第一时间间隔满足预设时长条件包括如下至少一项：
    所述第一时间间隔大于或等于PUSCH准备时间；
    所述第一时间间隔大于或等于UCI复用时间；
    所述第一时间间隔大于或等于物理下行共享信道PDSCH处理时间；
    所述第一时间间隔大于或等于PUCCH准备时间。
  5. 根据权利要求1所述的方法，其中，所述第一PUSCH传输机会为所述 PUSCH重复传输中距离所述第二PUSCH传输机会最近的初传机会。
  6. 根据权利要求1所述的方法，其中，所述方法还包括：
    在承载所述第二UCI的PUCCH与所述第二PUSCH传输机会之间存在冲突的情况下，在第三PUSCH传输机会上发送PUSCH；
    其中，所述第三PUSCH传输机会为所述PUSCH重复传输中位于所述第一PUSCH传输机会之后的PUSCH传输机会，且所述第三PUSCH传输机会与所述第二PUSCH传输机会不同。
  7. 根据权利要求1所述的方法，其中，在不存在第一UCI在第一PUSCH传输机会上传输的情况下，所述终端不期望网络设备调度或配置承载第二UCI的PUCCH与第二PUSCH传输机会之间存在冲突。
  8. 根据权利要求1所述的方法，其中，在调度第二UCI的下行控制信令的接收时刻不满足预设条件的情况下，所述终端不期望网络设备调度或配置承载第二UCI的PUCCH与第二PUSCH传输机会之间存在冲突。
  9. 根据权利要求1所述的方法，其中，所述第二UCI的传输优先级和与所述第二UCI冲突的PUSCH的传输优先级相同；
    或者
    所述第二UCI的传输优先级和与所述第二UCI冲突的PUSCH的传输优先级不相同。
  10. 一种信息传输方法，由网络设备执行，所述方法包括：
    在存在第一上行控制信息UCI在第一物理上行共享信道PUSCH传输机会上传输，或者调度第二UCI的下行控制信令的接收时刻满足预设条件的情况下，若承载第二UCI的物理上行控制信道PUCCH与第二PUSCH传输机会之间存在冲突，则在所述第二PUSCH传输机会上接收所述第二UCI；
    其中，所述第一PUSCH传输机会为PUSCH重复传输的初传机会，所述第二PUSCH传输机会为所述PUSCH重复传输的重传机会。
  11. 根据权利要求10所述的方法，其中，所述调度第二UCI的下行控制信令的接收时刻满足预设条件，包括如下至少一项：
    调度所述第二UCI的下行控制信令的接收时刻与第一时域位置之间的第一时间间隔满足预设时长条件，其中，所述第一时域位置根据所述第一 PUSCH传输机会和承载所述第二UCI的PUCCH的起始时刻中的至少一项确定；
    调度所述第二UCI的下行控制信令的接收时刻位于调度所述PUSCH的下行控制信令的接收时刻之前。
  12. 根据权利要求11所述的方法，其中，所述第一时域位置为如下一项：
    所述第一PUSCH传输机会的起始时刻；
    承载所述第二UCI的PUCCH的起始时刻；
    所述第一PUSCH传输机会的起始时刻和承载所述第二UCI的PUCCH的起始时刻中较早的时刻。
  13. 根据权利要求11所述的方法，其中，所述第一时间间隔满足预设时长条件包括如下至少一项：
    所述第一时间间隔大于或等于PUSCH准备时间；
    所述第一时间间隔大于或等于UCI复用时间；
    所述第一时间间隔大于或等于物理下行共享信道PDSCH处理时间；
    所述第一时间间隔大于或等于PUCCH准备时间。
  14. 根据权利要求10所述的方法，其中，所述第一PUSCH传输机会为所述PUSCH重复传输中距离所述第二PUSCH传输机会最近的初传机会。
  15. 根据权利要求10所述的方法，其中，所述方法还包括：
    在不存在第一UCI在第一PUSCH传输机会上传输的情况下，调度或配置承载第二UCI的PUCCH与第二PUSCH传输机会之间不存在冲突。
  16. 根据权利要求10所述的方法，其中，所述方法还包括：
    在调度第二UCI的下行控制信令的接收时刻不满足预设条件的情况下，调度或配置承载第二UCI的PUCCH与第二PUSCH传输机会之间不存在冲突。
  17. 根据权利要求10所述的方法，其中，所述方法还包括：
    在承载所述第二UCI的PUCCH与所述第二PUSCH传输机会之间存在冲突的情况下，在第三PUSCH传输机会上接收PUSCH；
    其中，所述第三PUSCH传输机会为所述PUSCH重复传输中位于所述第一PUSCH传输机会之后的PUSCH传输机会，且所述第三PUSCH传输机会 与所述第二PUSCH传输机会不同。
  18. 根据权利要求10所述的方法，其中，所述第二UCI的传输优先级和与所述第二UCI冲突的PUSCH的传输优先级相同；
    或者
    所述第二UCI的传输优先级和与所述第二UCI冲突的PUSCH的传输优先级不相同。
  19. 一种信息传输装置，所述装置包括：
    第一发送模块，用于在存在第一上行控制信息UCI在第一物理上行共享信道PUSCH传输机会上传输，或者调度第二UCI的下行控制信令的接收时刻满足预设条件的情况下，若承载第二UCI的物理上行控制信道PUCCH与第二PUSCH传输机会之间存在冲突，则在所述第二PUSCH传输机会上发送所述第二UCI；
    其中，所述第一PUSCH传输机会为PUSCH重复传输的初传机会，所述第二PUSCH传输机会为所述PUSCH重复传输的重传机会。
  20. 根据权利要求19所述的装置，其中，所述调度第二UCI的下行控制信令的接收时刻满足预设条件，包括如下至少一项：
    调度所述第二UCI的下行控制信令的接收时刻与第一时域位置之间的第一时间间隔满足预设时长条件，其中，所述第一时域位置根据所述第一PUSCH传输机会和承载所述第二UCI的PUCCH的起始时刻中的至少一项确定；
    调度所述第二UCI的下行控制信令的接收时刻位于调度所述PUSCH的下行控制信令的接收时刻之前。
  21. 根据权利要求20所述的装置，其中，所述第一时域位置为如下一项：
    所述第一PUSCH传输机会的起始时刻；
    承载所述第二UCI的PUCCH的起始时刻；
    所述第一PUSCH传输机会的起始时刻和承载所述第二UCI的PUCCH的起始时刻中较早的时刻。
  22. 根据权利要求20所述的装置，其中，所述第一时间间隔满足预设时长条件包括如下至少一项：
    所述第一时间间隔大于或等于PUSCH准备时间；
    所述第一时间间隔大于或等于UCI复用时间；
    所述第一时间间隔大于或等于物理下行共享信道PDSCH处理时间；
    所述第一时间间隔大于或等于PUCCH准备时间。
  23. 根据权利要求19所述的装置，其中，所述第一PUSCH传输机会为所述PUSCH重复传输中距离所述第二PUSCH传输机会最近的初传机会。
  24. 根据权利要求19所述的装置，其中，所述装置还包括：
    第二发送模块，用于在承载所述第二UCI的PUCCH与所述第二PUSCH传输机会之间存在冲突的情况下，在第三PUSCH传输机会上发送PUSCH；
    其中，所述第三PUSCH传输机会为所述PUSCH重复传输中位于所述第一PUSCH传输机会之后的PUSCH传输机会，且所述第三PUSCH传输机会与所述第二PUSCH传输机会不同。
  25. 根据权利要求19所述的装置，其中，在不存在第一UCI在第一PUSCH传输机会上传输的情况下，所述装置不期望网络设备调度或配置承载第二UCI的PUCCH与第二PUSCH传输机会之间存在冲突。
  26. 根据权利要求19所述的装置，其中，在调度第二UCI的下行控制信令的接收时刻不满足预设条件的情况下，所述装置不期望网络设备调度或配置承载第二UCI的PUCCH与第二PUSCH传输机会之间存在冲突。
  27. 根据权利要求19所述的装置，其中，所述第二UCI的传输优先级和与所述第二UCI冲突的PUSCH的传输优先级相同；
    或者
    所述第二UCI的传输优先级和与所述第二UCI冲突的PUSCH的传输优先级不相同。
  28. 一种信息传输装置，所述装置包括：
    第一接收模块，用于在存在第一上行控制信息UCI在第一物理上行共享信道PUSCH传输机会上传输，或者调度第二UCI的下行控制信令的接收时刻满足预设条件的情况下，若承载第二UCI的物理上行控制信道PUCCH与第二PUSCH传输机会之间存在冲突，则在所述第二PUSCH传输机会上接收所述第二UCI；
    其中，所述第一PUSCH传输机会为PUSCH重复传输的初传机会，所述第二PUSCH传输机会为所述PUSCH重复传输的重传机会。
  29. 根据权利要求28所述的装置，其中，所述调度第二UCI的下行控制信令的接收时刻满足预设条件，包括如下至少一项：
    调度所述第二UCI的下行控制信令的接收时刻与第一时域位置之间的第一时间间隔满足预设时长条件，其中，所述第一时域位置根据所述第一PUSCH传输机会和承载所述第二UCI的PUCCH的起始时刻中的至少一项确定；
    调度所述第二UCI的下行控制信令的接收时刻位于调度所述PUSCH的下行控制信令的接收时刻之前。
  30. 根据权利要求29所述的装置，其中，所述第一时域位置为如下一项：
    所述第一PUSCH传输机会的起始时刻；
    承载所述第二UCI的PUCCH的起始时刻；
    所述第一PUSCH传输机会的起始时刻和承载所述第二UCI的PUCCH的起始时刻中较早的时刻。
  31. 根据权利要求29所述的装置，其中，所述第一时间间隔满足预设时长条件包括如下至少一项：
    所述第一时间间隔大于或等于PUSCH准备时间；
    所述第一时间间隔大于或等于UCI复用时间；
    所述第一时间间隔大于或等于物理下行共享信道PDSCH处理时间；
    所述第一时间间隔大于或等于PUCCH准备时间。
  32. 根据权利要求28所述的装置，其中，所述第一PUSCH传输机会为所述PUSCH重复传输中距离所述第二PUSCH传输机会最近的初传机会。
  33. 根据权利要求28所述的装置，其中，所述装置还包括：
    第一配置模块，用于在不存在第一UCI在第一PUSCH传输机会上传输的情况下，调度或配置承载第二UCI的PUCCH与第二PUSCH传输机会之间不存在冲突。
  34. 根据权利要求28所述的装置，其中，所述装置还包括：
    第二配置模块，用于在调度第二UCI的下行控制信令的接收时刻不满足 预设条件的情况下，调度或配置承载第二UCI的PUCCH与第二PUSCH传输机会之间不存在冲突。
  35. 根据权利要求28所述的装置，其中，所述装置还包括：
    第二接收模块，用于在承载所述第二UCI的PUCCH与所述第二PUSCH传输机会之间存在冲突的情况下，在第三PUSCH传输机会上接收PUSCH；
    其中，所述第三PUSCH传输机会为所述PUSCH重复传输中位于所述第一PUSCH传输机会之后的PUSCH传输机会，且所述第三PUSCH传输机会与所述第二PUSCH传输机会不同。
  36. 根据权利要求28所述的装置，其中，所述第二UCI的传输优先级和与所述第二UCI冲突的PUSCH的传输优先级相同；
    或者
    所述第二UCI的传输优先级和与所述第二UCI冲突的PUSCH的传输优先级不相同。
  37. 一种终端，包括：存储器、处理器及存储在所述存储器上并可在所述处理器上运行的程序或指令，其中，所述程序或指令被所述处理器执行时实现如权利要求1至9中任一项所述的信息传输方法中的步骤。
  38. 一种网络设备，包括：存储器、处理器及存储在所述存储器上并可在所述处理器上运行的程序或指令，其中，所述程序或指令被所述处理器执行时实现如权利要求10至18中任一项所述的信息传输方法中的步骤。
  39. 一种可读存储介质，所述可读存储介质上存储程序或指令，其中，所述程序或指令被处理器执行时实现如权利要求1至9中任一项所述的信息传输方法的步骤，或者所述程序或指令被处理器执行时实现如权利要求10至18中任一项所述的信息传输方法的步骤。
PCT/CN2022/070274 2021-01-08 2022-01-05 信息传输方法、装置、终端及网络设备 Ceased WO2022148368A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202110026258.9A CN114745083B (zh) 2021-01-08 2021-01-08 信息传输方法、装置、终端及网络设备
CN202110026258.9 2021-01-08

Publications (1)

Publication Number Publication Date
WO2022148368A1 true WO2022148368A1 (zh) 2022-07-14

Family

ID=82274264

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/070274 Ceased WO2022148368A1 (zh) 2021-01-08 2022-01-05 信息传输方法、装置、终端及网络设备

Country Status (2)

Country Link
CN (1) CN114745083B (zh)
WO (1) WO2022148368A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116744460A (zh) * 2023-07-17 2023-09-12 南京星思半导体有限公司 物理上行控制信道pucch的确定方法与装置

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20250136406A (ko) * 2023-02-16 2025-09-16 노키아 테크놀로지스 오와이 구성된 그랜트 동작

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190349917A1 (en) * 2018-05-11 2019-11-14 Qualcomm Incorporated Uplink control information multiplexing on physical uplink shared channels in new radio
CN110474747A (zh) * 2018-05-11 2019-11-19 中兴通讯股份有限公司 一种信号传输方法和装置、及终端
CN111756506A (zh) * 2019-03-29 2020-10-09 华为技术有限公司 传输上行信息的方法和通信装置
US20200329486A1 (en) * 2019-04-09 2020-10-15 Qualcomm Incorporated Handling collisions between uplink data repetitions and an uplink control transmission

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110299976B (zh) * 2018-03-21 2022-04-08 大唐移动通信设备有限公司 一种信息传输方法、接收方法、终端及网络设备
CN110351049B (zh) * 2018-04-04 2020-10-20 电信科学技术研究院有限公司 一种上行控制信息传输的方法与设备

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190349917A1 (en) * 2018-05-11 2019-11-14 Qualcomm Incorporated Uplink control information multiplexing on physical uplink shared channels in new radio
CN110474747A (zh) * 2018-05-11 2019-11-19 中兴通讯股份有限公司 一种信号传输方法和装置、及终端
CN111756506A (zh) * 2019-03-29 2020-10-09 华为技术有限公司 传输上行信息的方法和通信装置
US20200329486A1 (en) * 2019-04-09 2020-10-15 Qualcomm Incorporated Handling collisions between uplink data repetitions and an uplink control transmission

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
ERICSSON: "On Remaining Issues on UCI Multiplexing on PUSCH", 3GPP DRAFT; R1-1802908 ON REMAINING ISSUES ON UCI MULTIPLEXING ON PUSCH, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. Athens, Greece; 20180226 - 20180302, 17 February 2018 (2018-02-17), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051398297 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116744460A (zh) * 2023-07-17 2023-09-12 南京星思半导体有限公司 物理上行控制信道pucch的确定方法与装置

Also Published As

Publication number Publication date
CN114745083A (zh) 2022-07-12
CN114745083B (zh) 2024-01-30

Similar Documents

Publication Publication Date Title
WO2023011454A1 (zh) 旁链路资源确定方法、装置、终端及存储介质
CN115225217B (zh) 旁链路反馈资源的确定方法、装置、终端及存储介质
WO2022078288A1 (zh) Harq-ack的传输方法、终端及网络侧设备
WO2022063072A1 (zh) 上行信道传输方法、装置及终端
CN114079553B (zh) 上行传输方法、设备及可读存储介质
WO2022078451A1 (zh) 配置授权的重复传输方法、装置、设备及可读存储介质
WO2022152072A1 (zh) 信道信息发送方法、信道信息接收方法及相关设备
WO2022068869A1 (zh) 传输处理方法、装置及相关设备
CN113965998B (zh) 上行传输方法、装置及相关设备
WO2022012417A1 (zh) 冲突处理方法及装置
WO2022105842A1 (zh) 上行控制信息传输方法及相关设备
WO2023011286A1 (zh) 反馈方法、相关设备及可读存储介质
JP2024501711A (ja) Ｕｃｉ多重化の方法、装置、機器及び可読記憶媒体
WO2022028604A1 (zh) 上行传输方法、装置及终端设备
WO2022148368A1 (zh) 信息传输方法、装置、终端及网络设备
CN113965301B (zh) 物理上行控制信道资源重叠的处理方法及装置
WO2022012433A1 (zh) Harq-ack的反馈方法和设备
WO2022012414A1 (zh) 信息复用方法、装置及用户设备
CN114375012A (zh) 上行传输处理方法、装置及终端
CN113890701B (zh) 旁链路传输方法、传输装置和终端
WO2022063163A1 (zh) Harq-ack处理方法、装置及相关设备
CN115333690A (zh) 信息传输方法、装置、终端及网络侧设备
WO2024140634A1 (zh) 传输方法、设备及可读存储介质
CN113890698B (zh) 旁链路传输方法、传输装置和通信设备
WO2023280211A1 (zh) Pucch时域资源重叠的处理方法及装置

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 22736530

Country of ref document: EP

Kind code of ref document: A1