WO2020164568A1 - 物理上行共享信道的传输方法、终端及网络设备 - Google Patents

物理上行共享信道的传输方法、终端及网络设备 Download PDF

Info

Publication number
WO2020164568A1
WO2020164568A1 PCT/CN2020/075203 CN2020075203W WO2020164568A1 WO 2020164568 A1 WO2020164568 A1 WO 2020164568A1 CN 2020075203 W CN2020075203 W CN 2020075203W WO 2020164568 A1 WO2020164568 A1 WO 2020164568A1
Authority
WO
WIPO (PCT)
Prior art keywords
pusch
repeatedly transmitted
stopped
group
discarded
Prior art date
Application number
PCT/CN2020/075203
Other languages
English (en)
French (fr)
Inventor
高雪娟
艾托尼
Original Assignee
电信科学技术研究院有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 电信科学技术研究院有限公司 filed Critical 电信科学技术研究院有限公司
Priority to US17/431,130 priority Critical patent/US12089206B2/en
Priority to KR1020217028011A priority patent/KR20210119521A/ko
Priority to EP20755126.8A priority patent/EP3927057A4/en
Publication of WO2020164568A1 publication Critical patent/WO2020164568A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling
    • H04W72/1263—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows
    • H04W72/1268—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows of uplink data flows
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1812—Hybrid protocols; Hybrid automatic repeat request [HARQ]
    • H04L1/1819—Hybrid protocols; Hybrid automatic repeat request [HARQ] with retransmission of additional or different redundancy
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/08—Arrangements for detecting or preventing errors in the information received by repeating transmission, e.g. Verdan system
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/1607—Details of the supervisory signal
    • H04L1/1642—Formats specially adapted for sequence numbers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1867—Arrangements specially adapted for the transmitter end
    • H04L1/1887—Scheduling and prioritising arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1867—Arrangements specially adapted for the transmitter end
    • H04L1/189—Transmission or retransmission of more than one copy of a message
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0044—Arrangements for allocating sub-channels of the transmission path allocation of payload
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signaling, i.e. of overhead other than pilot signals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0058—Allocation criteria
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/21—Control channels or signalling for resource management in the uplink direction of a wireless link, i.e. towards the network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/50—Allocation or scheduling criteria for wireless resources
    • H04W72/56—Allocation or scheduling criteria for wireless resources based on priority criteria
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/50—Allocation or scheduling criteria for wireless resources
    • H04W72/56—Allocation or scheduling criteria for wireless resources based on priority criteria
    • H04W72/566—Allocation or scheduling criteria for wireless resources based on priority criteria of the information or information source or recipient
    • H04W72/569—Allocation or scheduling criteria for wireless resources based on priority criteria of the information or information source or recipient of the traffic information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signaling, i.e. of overhead other than pilot signals
    • H04L5/0057—Physical resource allocation for CQI

Definitions

  • the present disclosure relates to the field of communication technology, and in particular to a transmission method, terminal and network equipment of a physical uplink shared channel.
  • the SR (Scheduling Request) is carried on the PUCCH (Physical Uplink Control Channel, physical uplink control channel) for transmission, and is transmitted on the configured PUCCH resource according to the configured period.
  • PUCCH Physical Uplink Control Channel, physical uplink control channel
  • MAC Medium Access Control
  • PDU Protocol Data Unit, protocol data unit
  • the PDU is determined to exist before the PUSCH (Physical Uplink Shared Channel, physical uplink shared channel) transmission
  • the MAC transmits the SR together with the data in the PUSCH through the BSR (Buffer Status Report) method, and the physical layer will not have a positive SR, so on the PUCCH resource corresponding to the SR PUCCH transmission is not performed.
  • the MAC determines that there is an SR when it has begun to build or complete the PDU build, the SR cannot be packaged into the PDU by BSR.
  • the MAC layer determines that the SR resource overlaps the PUSCH resource carrying the PDU, it will not Positive SR transmission will be triggered to the physical layer, so PUCCH transmission is not performed on the PUCCH resource corresponding to the SR. Therefore, for the PUSCH carrying data (that is, the PUSCH with UL-SCH), there will be no overlap between the PUCCH carrying the SR and the PUSCH at the physical layer.
  • the MAC layer When the MAC layer determines that there is SR transmission and the PUCCH resource carrying the SR does not overlap with the PUSCH, the MAC layer will trigger the physical layer to transmit positive SR. If the PUCCH carrying the positive SR overlaps with the PUCCH carrying other UCI (Uplink Control Information), for example, the PUCCH carrying HARQ-ACK (hybrid automatic repeat response)/CSI (channel state information), the PUCCH will be repeated according to UCI Using transmission rules, SR may be transferred to other PUCCH resources for transmission, as shown in Figure 1. The PUCCH may overlap with the PUSCH, thereby indirectly causing the SR to overlap with the PUSCH. Since the SR can no longer be packaged as a BSR into the data carried by the PUSCH, it is stipulated in the related technology that the SR is discarded and not transmitted.
  • UCI Uplink Control Information
  • HARQ-ACK hybrid automatic repeat response
  • CSI channel state information
  • the PUSCH does not carry UL-SCH (Uplink Shared Channel), that is, there is no MAC PDU packing process, so SR cannot be transmitted on PUSCH in the form of BSR. Since the PUSCH at this time is used to carry SP-CSI (semi-persistent CSI) or A-CSI (aperiodic CSI), considering that the importance of CSI is not as high as SR, it is stipulated to discard PUSCH without UL-SCH, and transmit SR.
  • SP-CSI sini-persistent CSI
  • A-CSI aperiodic CSI
  • PUSCH can be configured to use repeated transmission, for example, repeated transmission in units of time slots, a TB can be repeatedly transmitted through multiple PUSCHs, and each repeatedly transmitted PUSCH is transmitted in a different time slot, then a group of repeated transmissions
  • the PUSCH can occupy multiple time slots, and the PUSCH is transmitted on the same resource in each time slot.
  • the PUSCH in each time slot carries the same TB (Transport Block) information, so as to improve the uplink transmission performance and The purpose of uplink coverage.
  • the RV (Redundant Version) of the repeatedly transmitted PUSCH is determined according to the DCI (Downlink Control Information) notification or a predetermined initial RV in a predetermined RV sequence to sequentially determine the RV corresponding to each repeatedly transmitted PUSCH, such as a predetermined
  • multiple service types can exist simultaneously on the same terminal, such as eMBB (enhanced mobile broadband) and URLLC (ultra-reliable, low-latency communication).
  • eMBB enhanced mobile broadband
  • URLLC ultra-reliable, low-latency communication
  • the embodiments of the present disclosure provide a physical uplink shared channel transmission method, terminal and network equipment.
  • the repeatedly transmitted PUSCH and PUCCH overlap the normal transmission of the repeatedly transmitted PUSCH is guaranteed.
  • the embodiments of the present disclosure provide the following technical solutions:
  • a transmission method of a physical uplink shared channel, applied to a terminal, and the method includes:
  • At least one PUSCH using a preset redundancy version RV in a group of repeatedly transmitted physical uplink shared channels PUSCH is discarded or transmission is stopped, it is determined based on the preset RV that one of the group of repeatedly transmitted PUSCHs is discarded Or the RV of at least one PUSCH after the PUSCH whose transmission is stopped;
  • determining the RV of at least one PUSCH after the discarded or stopped PUSCH in the group of repeatedly transmitted PUSCHs includes:
  • the RV of the first PUSCH after the discarded or stopped PUSCH in the group of repeatedly transmitted PUSCHs is the preset RV; the first one in the group of repeatedly transmitted PUSCHs The RV of the PUSCH after the PUSCH remains unchanged.
  • determining the RV of at least one PUSCH after the discarded or stopped PUSCH in the group of repeatedly transmitted PUSCHs includes:
  • the RV of the subsequent PUSCH is: the RV determined in a backward order from the position of the preset RV in the predetermined RV sequence as a starting point.
  • determining the RV of at least one PUSCH after the discarded or stopped PUSCH in the group of repeatedly transmitted PUSCHs includes:
  • the RV of the PUSCH after the discarded or stopped transmission in the group of repeatedly transmitted PUSCHs is the preset RV.
  • the at least one PUSCH being dropped or the transmission is stopped includes at least one of the following:
  • the at least one PUSCH overlaps with the physical uplink control channel PUCCH that carries the first type of uplink control information UCI, the at least one PUSCH is discarded or transmission is stopped;
  • the at least one PUSCH overlaps with the PUCCH, and the priority or importance of the PUCCH is higher than the at least one PUSCH, the at least one PUSCH is discarded or transmission is stopped;
  • the at least one PUSCH overlaps with the repeatedly transmitted PUCCH, the at least one PUSCH is discarded or transmission is stopped.
  • the UCI of the first type is a scheduling request SR or a UCI corresponding to the first type of service or an SR corresponding to the first type of service;
  • the first type of service is: a service with high priority or importance, or an ultra-reliable low-latency communication URLLC service.
  • the repeatedly transmitted PUSCH corresponds to a second type of service; wherein, the second type of service is: a service with low priority or importance, or an enhanced mobile broadband eMBB service, or a non-URLLC service.
  • the priority or importance of the PUCCH is higher than the at least one PUSCH, including:
  • the priority or importance of the service type corresponding to the PUCCH is higher than the priority or importance of the service type corresponding to the at least one PUSCH.
  • the service type or the priority or importance of the service type is determined by corresponding at least one of the following information:
  • Downlink control information DCI Downlink control information DCI, wireless network temporary identification RNTI, search space, control resource set CORESET, beam, block error rate BLER, channel quality indicator CQI table, modulation and coding scheme MCS table, priority flag, PUCCH resource and SR configuration number.
  • the preset RV is a self-decoding RV.
  • the group of repeatedly transmitted PUSCHs is multiple PUSCHs that carry the repeated transmission of the same transport block TB.
  • the embodiment of the present disclosure also provides a physical uplink shared channel transmission method, which is applied to a network device, and the method includes:
  • determining the RV of at least one PUSCH after the discarded or stopped PUSCH in the group of repeatedly transmitted PUSCHs includes:
  • the RV of the first PUSCH after the discarded or stopped PUSCH in the group of repeatedly transmitted PUSCHs is the preset RV; the first one in the group of repeatedly transmitted PUSCHs The RV of the PUSCH after the PUSCH remains unchanged.
  • determining the RV of at least one PUSCH after the discarded or stopped PUSCH in the group of repeatedly transmitted PUSCHs includes:
  • the RV of the subsequent PUSCH is: the RV determined in a backward order from the position of the preset RV in the predetermined RV sequence as a starting point.
  • determining the RV of at least one PUSCH after the discarded or stopped PUSCH in the group of repeatedly transmitted PUSCHs includes:
  • the RV of the PUSCH after the discarded or stopped PUSCH in the group of repeatedly transmitted PUSCHs is the preset RV.
  • the at least one PUSCH being dropped or the transmission is stopped includes at least one of the following:
  • the at least one PUSCH overlaps with the physical uplink control channel PUCCH that carries the first type of uplink control information UCI, the at least one PUSCH is discarded or transmission is stopped;
  • the at least one PUSCH overlaps with the PUCCH, and the priority or importance of the PUCCH is higher than the at least one PUSCH, the at least one PUSCH is discarded or transmission is stopped;
  • the at least one PUSCH overlaps with the repeatedly transmitted PUCCH, the at least one PUSCH is discarded or transmission is stopped.
  • the UCI of the first type is a scheduling request SR or a UCI corresponding to the first type of service or an SR corresponding to the first type of service;
  • the first type of service is: a service with high priority or importance, or an ultra-reliable low-latency communication URLLC service.
  • the repeatedly transmitted PUSCH corresponds to the second type of service
  • the second type of service is: a service with low priority or importance, or an enhanced mobile broadband eMBB service, or a non-URLLC service.
  • the priority or importance of the PUCCH is higher than the at least one PUSCH, including:
  • the priority or importance of the service type corresponding to the PUCCH is higher than the priority or importance of the service type corresponding to the at least one PUSCH.
  • the priority or importance of the service type or service type is determined by at least one of the following corresponding information: downlink control information DCI, wireless network temporary identification RNTI, search space, control resource set CORESET, beam, block error rate BLER, channel quality indicator CQI table, modulation and coding scheme MCS table, priority flag, PUCCH resource and SR configuration number.
  • the preset RV is a self-decoding RV.
  • the group of repeatedly transmitted PUSCHs is multiple PUSCHs that carry the repeated transmission of the same transport block TB.
  • the embodiment of the present disclosure also provides a terminal, including: a processor, a transceiver, and a memory, the memory stores a program executable by the processor, and when the processor executes the program, it realizes:
  • At least one PUSCH using a preset redundancy version RV in a group of repeatedly transmitted physical uplink shared channels PUSCH is discarded or transmission is stopped, it is determined based on the preset RV that one of the group of repeatedly transmitted PUSCHs is discarded Or the RV of at least one PUSCH after the PUSCH whose transmission is stopped;
  • the transceiver transmits the corresponding PUSCH according to the determined RV.
  • the processor is specifically configured to: determine the RV of the first PUSCH after the discarded or stopped transmission in the group of repeatedly transmitted PUSCHs as the preset RV; The RV of the PUSCH after the first PUSCH in the transmitted PUSCH remains unchanged; or,
  • the RV of the subsequent PUSCH is: the position of the preset RV in the predetermined RV sequence is used as the starting point, and the RV is determined in a backward order; or,
  • the RV of the PUSCH after the discarded or stopped PUSCH in the group of repeatedly transmitted PUSCHs is the preset RV.
  • the at least one PUSCH being dropped or the transmission is stopped includes at least one of the following:
  • the at least one PUSCH overlaps with the physical uplink control channel PUCCH that carries the first type of uplink control information UCI, the at least one PUSCH is discarded or transmission is stopped;
  • the at least one PUSCH overlaps with the PUCCH, and the priority or importance of the PUCCH is higher than the repeatedly transmitted PUSCH, the at least one PUSCH is discarded or transmission is stopped;
  • the at least one PUSCH overlaps with the repeatedly transmitted PUCCH, the at least one PUSCH is discarded or transmission is stopped.
  • the UCI of the first type is a scheduling request SR or a UCI corresponding to the first type of service or an SR corresponding to the first type of service;
  • the first type of service is: a service with high priority or importance, or an ultra-reliable low-latency communication URLLC service.
  • the repeatedly transmitted PUSCH corresponds to the second type of service
  • the second type of service is: a service with low priority or importance, or an enhanced mobile broadband eMBB service, or a non-URLLC service.
  • the priority or importance of the PUCCH is higher than the at least one PUSCH, including: the priority or importance of the service type corresponding to the PUCCH is higher than the priority of the service type corresponding to the at least one PUSCH or importance.
  • the priority or importance of the service type or service type is determined by at least one of the following corresponding information: downlink control information DCI, wireless network temporary identification RNTI, search space, control resource set CORESET, beam, block error rate BLER, channel quality indicator CQI table, modulation and coding scheme MCS table, priority flag, PUCCH resource and SR configuration number.
  • the preset RV is a self-decoding RV.
  • the group of repeatedly transmitted PUSCHs is multiple PUSCHs that carry the repeated transmission of the same transport block TB.
  • the embodiment of the present disclosure also provides a terminal, including:
  • the processing module is configured to determine the group of repeated transmissions based on the preset RV when at least one PUSCH using the preset redundancy version RV in a group of repeatedly transmitted physical uplink shared channels PUSCH is discarded or stopped.
  • the transceiver module is used to send the corresponding PUSCH according to the determined RV.
  • the processing module is specifically configured to determine that the RV of the first PUSCH after the discarded or stopped transmission in the group of repeatedly transmitted PUSCHs is the preset RV;
  • the RV of the PUSCH after the first PUSCH in the transmitted PUSCH remains unchanged; or, it is determined that the RV of the first PUSCH after the PUSCH that is discarded or stopped in the group of repeatedly transmitted PUSCHs is determined
  • the preset RV is determined by determining the RV of the PUSCH after the first PUSCH in the group of repeatedly transmitted PUSCHs: starting from the position of the preset RV in the predetermined RV sequence, and determining in a backward order Or, determine the RV of the PUSCH after the discarded or stopped PUSCH in the group of repeatedly transmitted PUSCHs as the preset RV.
  • the embodiment of the present disclosure also provides a network device, including a processor, a transceiver, and a memory, the memory stores a program executable by the processor, and when the processor executes the program, it realizes:
  • the transceiver is used to receive the corresponding PUSCH according to the determined RV.
  • the processor is specifically configured to: determine the RV of the first PUSCH after the discarded or stopped transmission in the group of repeatedly transmitted PUSCHs as the preset RV; The RV of the PUSCH after the first PUSCH in the transmitted PUSCH remains unchanged; or,
  • the RV of the subsequent PUSCH is: the position of the preset RV in the predetermined RV sequence is used as the starting point, and the RV is determined in a backward order; or
  • the RV of the PUSCH after the discarded or stopped PUSCH in the group of repeatedly transmitted PUSCHs is the preset RV.
  • the at least one PUSCH being dropped or the transmission is stopped includes at least one of the following:
  • the at least one PUSCH overlaps with the physical uplink control channel PUCCH that carries the first type of uplink control information UCI, the at least one PUSCH is discarded or transmission is stopped;
  • the at least one PUSCH overlaps with the PUCCH, and the priority or importance of the PUCCH is higher than the at least one PUSCH, the at least one PUSCH is discarded or transmission is stopped;
  • the at least one PUSCH overlaps with the repeatedly transmitted PUCCH, the at least one PUSCH is discarded or transmission is stopped.
  • the first type of UCI is a scheduling request SR or a UCI corresponding to the first type of service or a scheduling request SR corresponding to the first type of service;
  • the first type of service is: a service with high priority or importance, or an ultra-reliable low-latency communication URLLC service.
  • the repeatedly transmitted PUSCH corresponds to the second type of service
  • the second type of service is: a service with low priority or importance, or an enhanced mobile broadband eMBB service, or a non-URLLC service.
  • the priority or importance of the PUCCH is higher than the at least one PUSCH, including:
  • the priority or importance of the service type corresponding to the PUCCH is higher than the priority or importance of the service type corresponding to the at least one PUSCH.
  • the service type or the priority or importance of the service type is determined by corresponding at least one of the following information:
  • Downlink control information DCI Downlink control information DCI, wireless network temporary identification RNTI, search space, control resource set CORESET, beam, block error rate BLER, channel quality indicator CQI table, modulation and coding scheme MCS table, priority flag, PUCCH resource and SR configuration number.
  • the preset RV is a self-decoding RV.
  • the group of repeatedly transmitted PUSCHs is multiple PUSCHs that carry the repeated transmission of the same transport block TB.
  • the embodiment of the present disclosure also provides a network device, including:
  • a processing module configured to determine the group of repeated transmissions based on the preset RV when it is determined that at least one PUSCH using the preset redundancy version RV in a group of repeatedly transmitted physical uplink shared channel PUSCHs is discarded or stopped.
  • the transceiver module is used to receive the corresponding PUSCH according to the determined RV.
  • the processing module is specifically configured to determine that the RV of the first PUSCH after the discarded or stopped PUSCH in the group of repeatedly transmitted PUSCHs is the preset RV; and the group of repeated transmissions The RV of the PUSCH after the first PUSCH in the PUSCH remains unchanged; or,
  • the RV of the subsequent PUSCH is: the position of the preset RV in the predetermined RV sequence is used as the starting point, and the RV is determined in a backward order; or
  • the RV of the PUSCH after the discarded or stopped PUSCH in the group of repeatedly transmitted PUSCHs is the preset RV.
  • Embodiments of the present disclosure also provide a computer storage medium, including instructions, which when run on a computer, cause the computer to execute the method described above.
  • Figure 1 is a schematic diagram of PUCCH that may overlap with PUSCH
  • FIG. 2 is a flowchart of a method for transmitting a physical uplink shared channel on a terminal side according to an embodiment of the disclosure
  • FIG. 3 is a schematic diagram of a configuration of 4 repeated transmissions of PUSCH in an embodiment of the disclosure
  • FIG. 4 is a schematic diagram of an implementation manner of determining the RV of at least one PUSCH after the discarded or stopped PUSCH in the group of repeatedly transmitted PUSCHs in an embodiment of the disclosure
  • FIG. 5 is a schematic diagram of another implementation manner of determining the RV of at least one PUSCH after the discarded or stopped PUSCH in the group of repeatedly transmitted PUSCHs in an embodiment of the disclosure
  • FIG. 6 is a schematic diagram of still another implementation manner of determining the RV of at least one PUSCH after the discarded or stopped PUSCH in the group of repeatedly transmitted PUSCHs in an embodiment of the disclosure;
  • FIG. 7 is a flowchart of a method for transmitting a physical uplink shared channel on a network device side according to an embodiment of the disclosure
  • FIG. 8 is a schematic structural diagram of a terminal according to an embodiment of the disclosure.
  • FIG. 9 is a schematic structural diagram of a network device according to an embodiment of the disclosure.
  • an embodiment of the present disclosure provides a physical uplink shared channel transmission method, which is applied to a terminal, and the method includes:
  • Step 21 When at least one PUSCH using a preset redundancy version RV in a group of repeatedly transmitted physical uplink shared channels PUSCH is discarded or transmission is stopped, determine the group of repeatedly transmitted PUSCHs based on the preset RV The RV of at least one PUSCH after the discarded or stopped PUSCH; the preset RV is a self-decoding RV, such as RV0; the group of repeatedly transmitted PUSCHs is a group of multiple repeated transmissions that carry the same transport block TB PUSCH;
  • Step 22 Send the corresponding PUSCH according to the determined RV.
  • the RV of at least one PUSCH using the first type of RV in a group of repeatedly transmitted PUSCHs is dropped or transmission is stopped, it is determined based on the first type of RV that the group of repeatedly transmitted PUSCHs.
  • the RV of at least one PUSCH after the discarded or stopped transmission of the PUSCH; the corresponding PUSCH is sent according to the determined RV, which ensures the normal transmission of the repeatedly transmitted PUSCH.
  • the RV of the repeatedly transmitted PUSCH after the discarded PUSCH is changed to include the self-decodable version of the RV.
  • determining the RV of at least one PUSCH after the discarded or stopped PUSCH in the group of repeatedly transmitted PUSCHs may include:
  • Step 211 Determine that the RV of the first PUSCH after the discarded or stopped PUSCH in the group of repeatedly transmitted PUSCHs is the preset RV; and the RV of the first PUSCH in the group of repeatedly transmitted PUSCHs The RV of the PUSCH after the first PUSCH remains unchanged.
  • the RV of the PUSCH after the first PUSCH in the group of repeatedly transmitted PUSCHs is the RV of the first PUSCH in the group of repeatedly transmitted PUSCHs in a predetermined RV sequence
  • the position of is the starting point, the RV determined in the backward order, that is, only the RV of the first PUSCH after the PUSCH that is discarded or stopped transmission is changed, and the RV of other PUSCHs is not changed;
  • the RV of the first PUSCH is RV0, according to RV0 as the starting point, the RV sequence is determined backward.
  • the RV of the second PUSCH is RV2
  • the RV of the third PUSCH is RV3
  • the RV of the fourth PUSCH is RV1.
  • the first PUSCH is discarded because it overlaps with PUCCH. Since its RV is RV0, it is more important and cannot be To discard, the original RV2 of the second PUSCH needs to be changed to RV0 to ensure that there is RV0 transmission in the repeated PUSCH transmission.
  • the other PUSCHs, that is, the RV of the third and fourth PUSCH are still the originally determined RV. do not change.
  • determining the RV of at least one PUSCH after the PUSCH that is discarded or stopped in the group of repeatedly transmitted PUSCHs may also include:
  • Step 212 Determine the RV of the first PUSCH after the discarded or stopped PUSCH in the group of repeatedly transmitted PUSCHs as the preset RV, and determine the first PUSCH in the group of repeatedly transmitted PUSCHs
  • the RV of the PUSCH after one PUSCH is: the RV determined in a backward order with the position of the preset RV in the predetermined RV sequence as a starting point.
  • the RV of the first PUSCH is RV0, according to RV0 as the starting point, the RV sequence is determined backward.
  • the RV of the second PUSCH is RV2
  • the RV of the third PUSCH is RV3
  • the RV of the fourth PUSCH is RV1.
  • the first PUSCH is discarded because it overlaps with PUCCH.
  • the original RV2 of the second PUSCH needs to be changed to RV0 during the second PUSCH transmission to ensure that there is RV0 transmission in the repeated PUSCH transmission, and the second PUSCH RV0 is used as the starting point, according to the subsequent PUSCH and the second PUSCH Relative position, determine the RV of each PUSCH in the predetermined RV sequence backwards, that is, determine the RV of the third PUSCH is RV2, the RV of the fourth PUSCH is RV3, and the RV of the third and fourth PUSCHs As the RV of the second PUSCH changes, the RV is no longer the originally determined RV.
  • determining the RV of at least one PUSCH after the discarded or stopped PUSCH in the group of repeatedly transmitted PUSCHs may further include:
  • Step 213 Determine the RV of the PUSCH after the discarded or stopped PUSCH in the group of repeatedly transmitted PUSCHs as the preset RV.
  • the RV of the first PUSCH is RV0, according to RV0 as the starting point, the RV sequence is determined backward.
  • the RV of the second PUSCH is RV2
  • the RV of the third PUSCH is RV3
  • the RV of the fourth PUSCH is RV1.
  • the first PUSCH is discarded because it overlaps with PUCCH.
  • RV0 Since its RV is RV0, it is more important and cannot be To discard, it is necessary to change its original RV to RV0 in subsequent PUSCH transmissions to ensure that there is RV0 transmission in the repeated PUSCH transmission, so as to determine that the RVs of the second, third, and fourth PUSCH are all RV0. , The RV of the four PUSCHs is changed because the first PUSCH that uses RV0 is discarded, and is no longer the originally determined RV.
  • the first type of uplink control information UCI is a scheduling request SR or a UCI corresponding to the first type of service or a scheduling request SR corresponding to the first type of service; wherein, the first type of service is: priority High-level or important services, or ultra-reliable and low-latency communication URLLC.
  • the repeatedly transmitted PUSCH corresponds to the second type of service; wherein, the second type of service is: a service with low priority or importance, or, enhanced mobile broadband eMBB, or non- URLLC business.
  • the first type of UCI is SR or UCI corresponding to the first type of service or SR corresponding to the first type of service
  • the repeatedly transmitted PUSCH corresponds to the second type of service, where the first The priority or importance of the type of business is higher than the priority or importance of the second type of business.
  • the above-mentioned service type or priority or importance can be determined by at least one of the following corresponding information: downlink control information DCI, wireless network temporary identification RNTI, search space, control resource set CORESET, beam, block error rate BLER, channel Quality indicator CQI table, modulation and coding scheme MCS table, priority flag, PUCCH resource and SR configuration number. That is, based on at least one of the above information, the service type or the priority and importance of the service type corresponding to the first type UCI and PUSCH can be determined, so that it can be distinguished which is more important between the first type UCI and PUSCH. When the priority of the first type UCI is higher or the priority of the first type UCI and the PUSCH are equal, follow the above rules; otherwise, just discard the first type UCI.
  • the first type of UCI corresponds to the first type of DCI format
  • the first type of DCI size corresponds to the first type of DCI format
  • the first type of RNTI corresponds to the first type of search space
  • the first type of CORESET the first type of beam
  • the first type of BLER ((e.g. 10- 5 or 10-6)
  • the first type of CQI table e.g. URLLC CQI table
  • the first type of MCS table e.g.
  • the first type of priority flag the first type of PUCCH resource (e.g., the resource with a small number) Or a resource with a specific number or a resource corresponding to a specific SR configuration number) and a first-type SR configuration number (for example, when multiple SR configurations are configured, the SR configuration with a lower number is considered to correspond to URLLC),
  • the first type of UCI has a high priority (the priority or importance of the service corresponding to the PUSCH is not considered at this time, that is, whether the PUSCH also corresponds to the high priority service, that is, even if the priority of the PUSCH is equivalent to the first type of UCI, it is still necessary Discard or stop PUSCH), then PUSCH is discarded or transmission is stopped.
  • PUSCH corresponds to the second type of DCI format, the second type of DCI size, the second type of RNTI, the second type of search space, the second type of CORESET, the second type of beam, the second type of block error rate BLER (such as 10- 2 or 10-1), the second type of CQI table (e.g. 64QAM/256QAM CQI table), the second type of MCS table (e.g. non-URLLC MCS table), the second type of priority flag, the second type of PUCCH resource (e.g. a large number SR configuration number of the second type (for example, when multiple SR configurations are configured, the SR configuration with a higher number is considered to correspond to eMBB or non-URLLC).
  • the second type of PUCCH resource e.g. a large number SR configuration number of the second type (for example, when multiple SR configurations are configured, the SR configuration with a higher number is considered to correspond to eMBB or non-URLLC).
  • the PUSCH priority is low (the priority or importance of the service corresponding to the PUCCH is not considered at this time, that is, whether the PUCCH also corresponds to the low priority service, that is, even if the priority of the PUSCH is equivalent to the first type of UCI, If the PUSCH is still to be discarded or stopped), the PUSCH is discarded or the transmission is stopped.
  • the first type of UCI corresponds to the first type of DCI format
  • the first type of DCI size corresponds to the first type of DCI format
  • the first type of RNTI corresponds to the first type of search space
  • the first type of CORESET the first type of beam
  • the first type of BLER ((for example, 10 -5 or 10-6)
  • first-type CQI table e.g. URLLC CQI table
  • first-type MCS table e.g.
  • first-type priority flag corresponds to the second type of DCI format, the second type of DCI size, the second type of RNTI, the second type of search space, the second type of CORESET, the second type of beam, the second type of block error rate BLER (such as 10-2 or 10 -1), the second type of CQI table (e.g.
  • the second type of MCS table e.g. non-URLLC MCS table
  • the second type of priority flag e.g., the second type of PUCCH resource (e.g., the resource with a large number or At least one of a specific numbered resource or a resource corresponding to a specific SR configuration number), a second type of SR configuration number (for example, when multiple SR configurations are configured, the SR configuration with a higher number is considered to correspond to eMBB or non-URLLC) If the priority of the first type of UCI is higher than that of the PUSCH, the PUSCH is discarded or the transmission is stopped.
  • the UCI carried by the above PUCCH may be at least one of SR or HARQ-ACK or channel state information CSI.
  • the priority or importance of the service type corresponding to the PUCCH is higher than the priority or importance of the service type corresponding to the at least one PUSCH; for example, the PUCCH corresponds to the URLLC service, the PUSCH corresponds to the eMBB service, or the PUCCH corresponds to the URLLC service with priority 1, and the PUSCH corresponds to URLLC service with priority 2, where priority 1 is greater than priority 2.
  • the priority or importance of the service type can be based on at least one of the corresponding information below: One way to determine: DCI format, DCI size, RNTI, search space, CORESET, beam, BLER, CQI table, MCS table, priority flag, PUCCH resource and SR configuration number.
  • the priority or importance of PUCCH is high. ⁇ PUSCH.
  • a group of repeated PUSCH transmissions contains 4 PUSCH transmissions.
  • the predetermined RV sequence is ⁇ 0,2,3,1 ⁇
  • the PUSCH is scheduled for repeated transmissions
  • the RV indicator field in the DCI indicates RV0
  • the first PUSCH is transmitted in time slot n, and its RV is RV0.
  • the RV of the second PUSCH can be determined backwards in the RV sequence as RV2.
  • the RV of the three PUSCHs is RV3, and the RV of the fourth PUSCH is RV1.
  • Terminal side Determine the RV of the subsequent PUSCH in the following manner, and send the corresponding PUSCH with the corresponding RV;
  • the RV of the second PUSCH is determined to be RV0, that is, the original RV2 of the second PUSCH is changed to RV0 to ensure that there is RV0 transmission in the repeated PUSCH transmission, the third and fourth The RV of a PUSCH remains unchanged from the original RV;
  • Step 212 When the above step 212 is used, as shown in Figure 5: Determine the RV of the second PUSCH to be RV0, change the original RV2 of the second PUSCH to RV0, to ensure that there is RV0 transmission in the repeated PUSCH, and the second PUSCH corresponds to RV0 is the starting point.
  • the RV of each PUSCH is determined backward in the predetermined RV sequence, that is, the RV of the third PUSCH is determined to be RV2, and the RV of the fourth PUSCH is RV3.
  • the RV of the third and fourth PUSCH changes due to the change of the RV of the second PUSCH, and is no longer the originally determined RV;
  • step 213 it is determined that the RVs of the second, third, and fourth PUSCHs are all RV0. At this time, the RVs of the second, third, and fourth PUSCHs occur because the first PUSCH is dropped. Change, it is no longer the originally determined RV;
  • Base station side Determine the RV of the subsequent PUSCH in a manner corresponding to the terminal side, and receive the corresponding PUSCH according to the corresponding RV.
  • the above embodiments only take URLLC SR PUCCH and PUSCH overlap as an example.
  • PUCCH carrying other UCI overlaps with PUSCH if the processing rule for overlapping transmission is drop PUSCH, the above method is also applicable; because of any other When the reason causes at least one of the repeatedly transmitted PUSCHs to be discarded, the above method can be used. For example, when the repeatedly transmitted PUCCH overlaps with the PUSCH, the overlapped PUSCH is always discarded in the related technology, and the PUSCH of RV0 may be due to the repeated transmission of PUCCH. Overlapped and discarded.
  • the above PUSCH can be the PUSCH of eMBB, then it is obvious that the priority and importance of URLLC SR is higher than that of eMBB, and the above PUSCH is also But the same is URLLC PUSCH.
  • it belongs to the URLLC service as SR considering that the repeated transmission of PUSCH occupies a long time domain, if the SR is discarded, the delay of SR will be too large. At this time, it will also be caused by SR and repeated transmission.
  • the PUSCH overlaps and discards one or more of the repeated PUSCH transmissions;
  • the above repeated PUSCH transmission in the unit of time slot is an example, if there can be multiple PUSCHs corresponding to the same TB transmission in a time slot, that is, in the time slot For repeated transmissions, the above method is also applicable.
  • the difference is that there may be a PUCCH that carries SR overlaps with multiple repeated PUSCHs. For example, if it overlaps with the first and second PUSCHs at the same time, both of them need to be discarded.
  • the third PUSCH is the first channel after the PUSCH is discarded, and its RV is determined to be RV0; the above discarded PUSCH may also be partially discarded, that is, cancel or terminate a PUSCH transmission, which may be stopped after the PUSCH has been partially transmitted Transmission; the above PUSCH is not limited to a PUSCH with DCI scheduling or a scheduling-free PUSCH. If it is a scheduling-free PUSCH, its RV sequence may be different from the above sequence, for example, it may be ⁇ 0,0,0,0 ⁇ , ⁇ 0,3,0 ,3 ⁇ etc.
  • the RV of the repeatedly transmitted PUSCH after the discarded PUSCH is changed to include the self-decodable version RV to ensure the reliability of PUSCH repeated transmission.
  • a physical uplink shared channel transmission method which is applied to a network device, the method includes:
  • Step 71 When it is determined that at least one PUSCH using a preset redundancy version RV in a group of repeatedly transmitted physical uplink shared channels PUSCH is discarded or transmission is stopped, determine the group of repeatedly transmitted PUSCHs based on the preset RV The RV of at least one PUSCH after the PUSCH that is discarded or stopped for transmission in, the preset RV is a self-decoding RV; the group of repeatedly transmitted PUSCHs are multiple PUSCHs that carry the same transmission block TB repeatedly;
  • Step 72 Receive the corresponding PUSCH according to the determined RV.
  • determining the RV of at least one PUSCH after the discarded or stopped PUSCH in the group of repeatedly transmitted PUSCHs may include:
  • Step 711 Determine that the RV of the first PUSCH after the discarded or stopped PUSCH in the group of repeatedly transmitted PUSCHs is the preset RV; and the RV of the first PUSCH in the group of repeatedly transmitted PUSCHs The RV of the PUSCH after the first PUSCH remains unchanged.
  • determining the RV of at least one PUSCH after the discarded or stopped PUSCH in the group of repeatedly transmitted PUSCHs includes:
  • Step 712 Determine the RV of the first PUSCH after the discarded or stopped PUSCH in the group of repeatedly transmitted PUSCHs as the preset RV, and determine the first PUSCH in the group of repeatedly transmitted PUSCHs
  • the RV of the PUSCH after one PUSCH is: the RV determined in a backward order with the position of the preset RV in the predetermined RV sequence as a starting point.
  • determining the RV of at least one PUSCH after the discarded or stopped PUSCH in the group of repeatedly transmitted PUSCHs includes:
  • Step 713 Determine the RV of the PUSCH after the discarded or stopped PUSCH in the group of repeatedly transmitted PUSCHs as the preset RV.
  • the at least one PUSCH being dropped or the transmission is stopped includes at least one of the following:
  • the at least one PUSCH overlaps with the physical uplink control channel PUCCH carrying the first type of uplink control information UCI, the at least one PUSCH is discarded or transmission is stopped;
  • the first type of uplink control information UCI is a scheduling request SR or a UCI corresponding to the first type of service or a scheduling request SR corresponding to the first type of service; wherein, the first type of service is: priority High-level or important services, or ultra-reliable and low-latency communication URLLC.
  • the repeatedly transmitted PUSCH corresponds to the second type of service; wherein, the second type of service is: a service with low priority or importance, or, enhanced mobile broadband eMBB, or non- URLLC business.
  • the first type of UCI is SR or UCI corresponding to the first type of service or SR corresponding to the first type of service
  • the repeatedly transmitted PUSCH corresponds to the second type of service, where the first The priority or importance of the type of business is higher than the priority or importance of the second type of business.
  • the above-mentioned service type or priority or importance can be determined by at least one of the following corresponding information: downlink control information DCI, wireless network temporary identification RNTI, search space, control resource set CORESET, beam, block error rate BLER, channel Quality indicator CQI table, modulation and coding scheme MCS table, priority flag, PUCCH resource and SR configuration number. That is, based on at least one of the above information, the service type or the priority and importance of the service type corresponding to the first type UCI and PUSCH can be determined, so that it can be distinguished which is more important between the first type UCI and PUSCH. When the priority of the first type UCI is higher or the priority of the first type UCI and the PUSCH are equal, follow the above rules; otherwise, just discard the first type UCI.
  • the UCI carried by the PUCCH may be at least one of a scheduling request SR, a hybrid automatic repeat response HARQ-ACK, or a channel state information CSI.
  • the priority or importance of the PUCCH is higher than the at least one PUSCH, including:
  • the priority or importance of the service type corresponding to the PUCCH is higher than the priority or importance of the service type corresponding to the at least one PUSCH.
  • the RV of the repeatedly transmitted PUSCH after the discarded PUSCH is changed to include the self-decodable version RV to ensure the reliability of PUSCH repeated transmission.
  • an embodiment of the present disclosure further provides a terminal 80, which includes a processor 82, a transceiver 81, and a memory 83.
  • the memory 83 stores a program executable by the processor 82.
  • the processor 82 executes the program, it realizes that: when at least one PUSCH using a preset redundancy version RV in a group of repeatedly transmitted physical uplink shared channel PUSCH is discarded or transmission is stopped, it determines all based on the preset RV.
  • the transceiver transmits the corresponding PUSCH according to the determined RV.
  • the processor 82 is specifically configured to: determine the RV of the first PUSCH after the discarded or stopped transmission in the group of repeatedly transmitted PUSCHs as the preset RV; The RV of the PUSCH after the first PUSCH in the repeatedly transmitted PUSCH remains unchanged; or,
  • the RV of the subsequent PUSCH is: the position of the preset RV in the predetermined RV sequence is used as the starting point, and the RV is determined in a backward order; or
  • the RV of the PUSCH after the discarded or stopped PUSCH in the group of repeatedly transmitted PUSCHs is the preset RV.
  • the at least one PUSCH being dropped or the transmission is stopped includes at least one of the following:
  • the at least one PUSCH overlaps with the physical uplink control channel PUCCH carrying the first type of uplink control information UCI, the at least one PUSCH is discarded or transmission is stopped;
  • the at least one PUSCH overlaps with the PUCCH, and the priority or importance of the PUCCH is higher than the repeatedly transmitted PUSCH, the at least one PUSCH is discarded or transmission is stopped;
  • the at least one PUSCH overlaps with the repeatedly transmitted PUCCH, the at least one PUSCH is discarded or transmission is stopped.
  • the UCI of the first type is a scheduling request SR or a UCI corresponding to the first type of service or an SR corresponding to the first type of service;
  • the first type of service is: a service with high priority or importance, or an ultra-reliable low-latency communication URLLC service.
  • the repeatedly transmitted PUSCH corresponds to the second type of service
  • the second type of service is: a service with low priority or importance, or an enhanced mobile broadband eMBB service, or a non-URLLC service.
  • the priority or importance of the PUCCH is higher than the at least one PUSCH, including: the priority or importance of the service type corresponding to the PUCCH is higher than the priority of the service type corresponding to the at least one PUSCH or importance.
  • the priority or importance of the service type or service type is determined by at least one of the following corresponding information: downlink control information DCI, wireless network temporary identification RNTI, search space, control resource set CORESET, beam, block error rate BLER, channel quality indicator CQI table, modulation and coding scheme MCS table, priority flag, PUCCH resource and SR configuration number.
  • the preset RV is a self-decoding RV.
  • the group of repeatedly transmitted PUSCHs is multiple PUSCHs that carry the repeated transmission of the same transport block TB.
  • the terminal is a terminal corresponding to the method shown in FIG. 2 above, and all implementation manners in the above method embodiment are applicable to the terminal embodiment, and the same technical effect can also be achieved.
  • the transceiver 81 and the processor 82, as well as the transceiver 81 and the memory 83, can be connected through a bus interface.
  • the functions of the transceiver 81 can be implemented by the processor 82, and the functions of the processor 82 can also be implemented by the transceiver 81. achieve.
  • the embodiment of the present disclosure also provides a terminal, including:
  • the processing module is configured to determine the group of repeated transmissions based on the preset RV when at least one PUSCH using the preset redundancy version RV in a group of repeatedly transmitted physical uplink shared channels PUSCH is discarded or stopped.
  • the transceiver module is used to send the corresponding PUSCH according to the determined RV.
  • the processing module is specifically configured to determine that the RV of the first PUSCH after the discarded or stopped PUSCH in the group of repeatedly transmitted PUSCHs is the preset RV; the group of repeatedly transmitted PUSCHs The RV of the PUSCH after the first PUSCH in the PUSCH remains unchanged; or, it is determined that the RV of the first PUSCH after the PUSCH that is discarded or stopped in the group of repeatedly transmitted PUSCHs is the predetermined
  • RV the RV of the PUSCH after the first PUSCH in the group of repeatedly transmitted PUSCHs is determined as: the position of the preset RV in the predetermined RV sequence is used as the starting point, and the RV is determined in a backward order Or, determining the RV of the PUSCH after the discarded or stopped PUSCH in the group of repeatedly transmitted PUSCHs as the preset RV.
  • the at least one PUSCH being dropped or the transmission is stopped includes at least one of the following:
  • the at least one PUSCH overlaps with the physical uplink control channel PUCCH that carries the first type of uplink control information UCI, the at least one PUSCH is discarded or transmission is stopped;
  • the at least one PUSCH overlaps with the PUCCH, and the priority or importance of the PUCCH is higher than the repeatedly transmitted PUSCH, the at least one PUSCH is discarded or transmission is stopped;
  • the at least one PUSCH overlaps with the repeatedly transmitted PUCCH, the at least one PUSCH is discarded or transmission is stopped.
  • the UCI of the first type is a scheduling request SR or a UCI corresponding to the first type of service or an SR corresponding to the first type of service;
  • the first type of service is: a service with high priority or importance, or an ultra-reliable low-latency communication URLLC service.
  • the repeatedly transmitted PUSCH corresponds to the second type of service
  • the second type of service is: a service with low priority or importance, or an enhanced mobile broadband eMBB service, or a non-URLLC service.
  • the priority or importance of the PUCCH is higher than the at least one PUSCH, including: the priority or importance of the service type corresponding to the PUCCH is higher than the priority of the service type corresponding to the at least one PUSCH or importance.
  • the priority or importance of the service type or service type is determined by at least one of the following corresponding information: downlink control information DCI, wireless network temporary identification RNTI, search space, control resource set CORESET, beam, block error rate BLER, channel quality indicator CQI table, modulation and coding scheme MCS table, priority flag, PUCCH resource and SR configuration number.
  • the preset RV is a self-decoding RV.
  • the group of repeatedly transmitted PUSCHs is multiple PUSCHs that carry the repeated transmission of the same transport block TB.
  • the terminal is a terminal corresponding to the method shown in FIG. 2 above, and all implementation manners in the above method embodiment are applicable to the terminal embodiment, and the same technical effect can also be achieved.
  • the embodiment of the present disclosure also provides a network device 90, including: a processor 92, a transceiver 91, and a memory 93.
  • the memory 93 stores a program executable by the processor 93.
  • the processor 93 executes the program, it is realized: when it is determined that at least one PUSCH using a preset redundancy version RV in a group of repeatedly transmitted physical uplink shared channel PUSCH is discarded or transmission is stopped, based on the preset RV Determining the RV of at least one PUSCH after the discarded or stopped PUSCH in the group of repeatedly transmitted PUSCHs;
  • the transceiver 91 is configured to receive the corresponding PUSCH according to the determined RV.
  • the processor 92 is specifically configured to determine that the RV of the first PUSCH after the discarded or stopped transmission in the group of repeatedly transmitted PUSCHs is the preset RV; The RV of the PUSCH after the first PUSCH in the transmitted PUSCH remains unchanged; or,
  • the RV of the subsequent PUSCH is: the position of the preset RV in the predetermined RV sequence is used as the starting point, and the RV is determined in a backward order; or
  • the RV of the PUSCH after the discarded or stopped PUSCH in the group of repeatedly transmitted PUSCHs is the preset RV.
  • the at least one PUSCH being dropped or the transmission is stopped includes at least one of the following:
  • the at least one PUSCH overlaps with the physical uplink control channel PUCCH carrying the first type of uplink control information UCI, the at least one PUSCH is discarded or transmission is stopped;
  • the at least one PUSCH overlaps with the PUCCH, and the priority or importance of the PUCCH is higher than the at least one PUSCH, the at least one PUSCH is discarded or transmission is stopped;
  • the at least one PUSCH overlaps with the repeatedly transmitted PUCCH, the at least one PUSCH is discarded or transmission is stopped.
  • the first type of UCI is a scheduling request SR or a UCI corresponding to the first type of service or a scheduling request SR corresponding to the first type of service;
  • the first type of service is: a service with high priority or importance, or an ultra-reliable low-latency communication URLLC service.
  • the repeatedly transmitted PUSCH corresponds to the second type of service
  • the second type of service is: a service with low priority or importance, or an enhanced mobile broadband eMBB service, or a non-URLLC service.
  • the priority or importance of the PUCCH is higher than the at least one PUSCH, including:
  • the priority or importance of the service type corresponding to the PUCCH is higher than the priority or importance of the service type corresponding to the at least one PUSCH.
  • the service type or the priority or importance of the service type is determined by corresponding at least one of the following information:
  • Downlink control information DCI Downlink control information DCI, wireless network temporary identification RNTI, search space, control resource set CORESET, beam, block error rate BLER, channel quality indicator CQI table, modulation and coding scheme MCS table, priority flag, PUCCH resource and SR configuration number.
  • the preset RV is a self-decoding RV.
  • the group of repeatedly transmitted PUSCHs is multiple PUSCHs that carry the repeated transmission of the same transport block TB.
  • the terminal is a terminal corresponding to the method shown in FIG. 7 above, and all implementation manners in the above method embodiment are applicable to the embodiment of the terminal, and the same technical effect can also be achieved.
  • the transceiver 91 and the processor 92, as well as the transceiver 91 and the memory 93, can be connected via a bus interface.
  • the functions of the transceiver 91 can be implemented by the processor 92, and the functions of the processor 92 can also be implemented by the transceiver 91. achieve.
  • the embodiment of the present disclosure also provides a network device, including:
  • a processing module configured to determine the group of repeated transmissions based on the preset RV when it is determined that at least one PUSCH using the preset redundancy version RV in a group of repeatedly transmitted physical uplink shared channel PUSCHs is discarded or stopped.
  • the transceiver module is used to receive the corresponding PUSCH according to the determined RV.
  • the processing module is specifically configured to determine that the RV of the first PUSCH after the discarded or stopped PUSCH in the group of repeatedly transmitted PUSCHs is the preset RV; and the group of repeated transmissions The RV of the PUSCH after the first PUSCH in the PUSCH remains unchanged; or,
  • the RV of the subsequent PUSCH is: the position of the preset RV in the predetermined RV sequence is used as the starting point, and the RV is determined in a backward order; or
  • the RV of the PUSCH after the discarded or stopped PUSCH in the group of repeatedly transmitted PUSCHs is the preset RV.
  • the at least one PUSCH being dropped or the transmission is stopped includes at least one of the following:
  • the at least one PUSCH overlaps with the physical uplink control channel PUCCH that carries the first type of uplink control information UCI, the at least one PUSCH is discarded or transmission is stopped;
  • the at least one PUSCH overlaps with the PUCCH, and the priority or importance of the PUCCH is higher than the at least one PUSCH, the at least one PUSCH is discarded or transmission is stopped;
  • the at least one PUSCH overlaps with the repeatedly transmitted PUCCH, the at least one PUSCH is discarded or transmission is stopped.
  • the first type of UCI is a scheduling request SR or a UCI corresponding to the first type of service or a scheduling request SR corresponding to the first type of service;
  • the first type of service is: a service with high priority or importance, or an ultra-reliable low-latency communication URLLC service.
  • the repeatedly transmitted PUSCH corresponds to the second type of service
  • the second type of service is: a service with low priority or importance, or an enhanced mobile broadband eMBB service, or a non-URLLC service.
  • the priority or importance of the PUCCH is higher than the at least one PUSCH, including:
  • the priority or importance of the service type corresponding to the PUCCH is higher than the priority or importance of the service type corresponding to the at least one PUSCH.
  • the priority or importance of the service type or service type is determined by at least one of the following corresponding information: downlink control information DCI, wireless network temporary identification RNTI, search space, control resource set CORESET, beam, block error rate BLER, channel quality indicator CQI table, modulation and coding scheme MCS table, priority flag, PUCCH resource and SR configuration number.
  • the preset RV is a self-decoding RV.
  • the group of repeatedly transmitted PUSCHs is multiple PUSCHs that carry the repeated transmission of the same transport block TB.
  • the network device is a network device corresponding to the method shown in FIG. 7, and all the implementation manners in the foregoing method embodiment are applicable to the embodiment of the network device, and the same technical effect can also be achieved.
  • the embodiment of the present disclosure further provides a computer storage medium, including instructions, which when the instructions are executed on the computer, cause the computer to execute the method described in FIG. 2 or the method described in FIG. 7.
  • the methods shown in FIGS. 3 to 6 described above are also applicable to this embodiment, and the same technical effect can be achieved.
  • the disclosed device and method may be implemented in other ways.
  • the device embodiments described above are only illustrative.
  • the division of the units is only a logical function division, and there may be other divisions in actual implementation, for example, multiple units or components can be combined or It can be integrated into another system, or some features can be ignored or not implemented.
  • the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, and may be in electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the solutions of the embodiments.
  • the functional units in the various embodiments of the present disclosure may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit.
  • the function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer readable storage medium.
  • the technical solution of the present disclosure essentially or the part that contributes to the related technology or the part of the technical solution can be embodied in the form of a software product.
  • the computer software product is stored in a storage medium, including several
  • the instructions are used to make a computer device (which may be a personal computer, a server, or a network device, etc.) execute all or part of the steps of the methods described in the various embodiments of the present disclosure.
  • the aforementioned storage media include: U disk, mobile hard disk, ROM, RAM, magnetic disk or optical disk and other media that can store program codes.
  • each component or each step can be decomposed and/or recombined.
  • decomposition and/or recombination should be regarded as equivalent solutions of the present disclosure.
  • the steps of performing the above series of processing can naturally be performed in a time sequence in the order of description, but do not necessarily need to be performed in a time sequence, and some steps can be performed in parallel or independently of each other.
  • the purpose of the present disclosure can also be realized by running a program or a group of programs on any computing device.
  • the computing device may be a well-known general-purpose device. Therefore, the purpose of the present disclosure can also be achieved only by providing a program product containing program code for implementing the method or device. That is, such a program product also constitutes the present disclosure, and a storage medium storing such a program product also constitutes the present disclosure.
  • the storage medium may be any well-known storage medium or any storage medium developed in the future. It should also be pointed out that, in the device and method of the present disclosure, obviously, each component or each step can be decomposed and/or recombined.
  • the embodiments described in the embodiments of the present disclosure may be implemented by hardware, software, firmware, middleware, microcode, or a combination thereof.
  • the processing unit can be implemented in one or more application specific integrated circuits (ASICs), digital signal processors (Digital Signal Processing, DSP), digital signal processing devices (DSP Device, DSPD), programmable Logic Device (Programmable Logic Device, PLD), Field-Programmable Gate Array (Field-Programmable Gate Array, FPGA), general-purpose processors, controllers, microcontrollers, microprocessors, and others for performing the functions described in this disclosure Electronic unit or its combination.
  • ASICs application specific integrated circuits
  • DSP digital signal processors
  • DSP Device digital signal processing devices
  • DPD digital signal processing devices
  • PLD programmable Logic Device
  • Field-Programmable Gate Array Field-Programmable Gate Array
  • FPGA Field-Programmable Gate Array
  • the technology described in the embodiments of the present disclosure can be implemented through modules (for example, procedures, functions, etc.) that perform the functions described in the embodiments of the present disclosure.
  • the software codes can be stored in the memory and executed by the processor.
  • the memory can be implemented in the processor or external to the processor.

Landscapes

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

Abstract

本公开公开了一种物理上行共享信道的传输方法、终端及网络设备。终端侧的方法包括：当一组重复传输的物理上行共享信道PUSCH中存在至少一个使用预设冗余版本RV的PUSCH被丢弃或停止传输时，基于所述预设RV确定所述一组重复传输的PUSCH中的被丢弃或停止传输的PUSCH之后的至少一个PUSCH的RV；按照确定的RV发送对应的PUSCH。

Description

物理上行共享信道的传输方法、终端及网络设备
相关申请的交叉引用
本申请主张在2019年2月15日在中国提交的中国专利申请No.201910118136.5的优先权，其全部内容通过引用包含于此。
技术领域
本公开涉及通信技术领域，尤其涉及一种物理上行共享信道的传输方法、终端及网络设备。
背景技术
SR(Scheduling Request，调度请求)承载在PUCCH(Physical Uplink Control Channel，物理上行控制信道)上传输，按照配置的周期在配置的PUCCH资源上传输。
在NR R15中，当MAC(Medium Access Control，媒体接入控制)在组建PDU(Protocol Data Unit，协议数据单元，该PDU在PUSCH(Physical Uplink Shared Channel，物理上行共享信道)上传输)之前确定存在SR需要传输时，MAC将SR通过BSR(Buffer Status Report，缓存状态报告)的方式与PUSCH中的数据一同传输，则物理层不会出现positive(肯定的)SR，因此在SR对应的PUCCH资源上不进行PUCCH传输。
当MAC在已经开始组建或完成PDU组建时才确定存在SR，则该SR无法通过BSR的方式打包到PDU中，此时MAC层如果确定该SR的资源与承载PDU的PUSCH资源存在重叠，则不会向物理层触发positive SR传输，因此在SR对应的PUCCH资源上不进行PUCCH传输。因此，对于承载数据的PUSCH(即with UL-SCH的PUSCH)，在物理层不会出现承载SR的PUCCH与PUSCH的重叠。
当MAC层确定有SR传输，且承载SR的PUCCH资源与PUSCH不重叠时，MAC层会触发物理层传输positive SR。如果该承载positive SR的PUCCH与承载其他UCI(Uplink Control Information，上行控制信息)的 PUCCH，例如承载HARQ-ACK(混合自动重传应答)/CSI(信道状态信息)的PUCCH重叠，则根据UCI复用传输规则，SR可能会被转移到其他PUCCH资源上传输，如图1所示。该PUCCH可能与PUSCH重叠，从而间接导致SR与PUSCH重叠，由于SR已经不能作为BSR打包到该PUSCH承载的数据中，在相关技术中规定SR被丢弃不传输。
当PUSCH没有承载UL-SCH(Uplink Shared Channel，上行共享信道)时，即没有MAC PDU的打包过程，因此SR不能以BSR的形式在PUSCH上传输。由于此时的PUSCH是用来承载SP-CSI(半持续CSI)或A-CSI(非周期性CSI)的，考虑到CSI的重要性不如SR高，此时规定丢弃PUSCH without UL-SCH，传输SR。
PUSCH可以被配置采用重复传输，例如以时隙为单位的重复传输，则一个TB可以通过多个PUSCH进行重复传输，每个重复传输的PUSCH在不同的时隙中传输，则一组重复传输的PUSCH可占用多个时隙，在每个时隙中的相同资源上传输PUSCH，每个时隙中的PUSCH承载的是相同的TB(Transport Block，传输块)信息，从而达到提高上行传输性能和上行覆盖的目的。重复传输的PUSCH的RV(Redundant Version，冗余版本)按照DCI(下行控制信息)通知或预先确定的一个初始RV在预定的RV序列中顺序确定每个重复传输的PUSCH对应的RV，例如预定的RV序列为{0,2,3,1}，调度PUSCH传输的DCI中通知的RV＝0，则重复传输的第一个PUSCH的RV＝0，第二PUSCH的RV＝2，以此类推。
5G NR系统中，同一个终端可以同时存在多种业务类型，如eMBB(增强移动宽带)和URLLC(超可靠、低时延通信)。在R16URLLC中，考虑到URLLC的优先级高于eMBB，如果出现上述SR与PUSCH的重叠，当SR为对应URLLC的SR时，考虑到URLLC的高优先级，SR不能被丢弃，一种可能的方式是丢弃与SR重叠的PUSCH。但此时如果丢弃的PUSCH为重复传输中的RV＝0的PUSCH，则可能导致后续重复传输的PUSCH即使进行合并也无法得到准确的有效信息。
此外，当配置了重复传输的PUCCH与PUSCH重叠时，为了保证PUCCH的传输性能，与重复传输的PUCCH重叠的PUSCH被丢弃，此时同样可能存 在上述问题。
当重复传输的PUSCH与PUCCH之间重叠时，如何保证重复传输的PUSCH的正常传输，还没有明确方法。
发明内容
本公开实施例提供了一种物理上行共享信道的传输方法、终端及网络设备。当重复传输的PUSCH与PUCCH之间重叠时，保证了重复传输的PUSCH的正常传输。
为解决上述技术问题，本公开的实施例提供如下技术方案：
一种物理上行共享信道的传输方法，应用于终端，所述方法包括：
当一组重复传输的物理上行共享信道PUSCH中存在至少一个使用预设冗余版本RV的PUSCH被丢弃或停止传输时，基于所述预设RV确定所述一组重复传输的PUSCH中的被丢弃或停止传输的PUSCH之后的至少一个PUSCH的RV；
按照确定的RV发送对应的PUSCH。
其中，确定所述一组重复传输的PUSCH中的被丢弃或停止传输的PUSCH之后的至少一个PUSCH的RV，包括：
确定所述一组重复传输的PUSCH中的所述被丢弃或停止传输的PUSCH之后的第一个PUSCH的RV为所述预设RV；所述一组重复传输的PUSCH中的所述第一个PUSCH之后的PUSCH的RV保持不变。
其中，确定所述一组重复传输的PUSCH中的被丢弃或停止传输的PUSCH之后的至少一个PUSCH的RV，包括：
确定所述一组重复传输的PUSCH中的被丢弃或停止传输的PUSCH之后的第一个PUSCH的RV为所述预设RV，确定所述一组重复传输的PUSCH中的所述第一个PUSCH之后的PUSCH的RV为：以所述预设RV在预定的RV序列中的位置为起点，向后顺序确定的RV。
其中，确定所述一组重复传输的PUSCH中的被丢弃或停止传输的PUSCH之后的至少一个PUSCH的RV，包括：
确定所述一组重复传输的PUSCH中的所述被丢弃或停止传输的PUSCH 之后的PUSCH的RV为所述预设RV。
其中，所述至少一个PUSCH被丢弃或停止传输，包括以下至少一种：
当所述至少一个PUSCH与承载第一类上行控制信息UCI的物理上行控制信道PUCCH重叠时，所述至少一个PUSCH被丢弃或停止传输；
当所述至少一个PUSCH与PUCCH重叠，且所述PUCCH的优先级或重要性高于所述至少一个PUSCH时，所述至少一个PUSCH被丢弃或停止传输；
当所述至少一个PUSCH与重复传输的PUCCH重叠时，所述至少一个PUSCH被丢弃或停止传输。
其中，所述第一类UCI为调度请求SR或者为对应第一类业务的UCI或者对应第一类业务的SR；
其中，所述第一类业务为：优先级或重要性高的业务，或者，超可靠低时延通信URLLC业务。
其中，所述重复传输的PUSCH对应第二类业务；其中，所述第二类业务为：优先级或重要性低的业务，或者，为增强移动宽带eMBB业务，或者，为非URLLC业务。
其中，所述PUCCH的优先级或重要性高于所述至少一个PUSCH，包括：
所述PUCCH对应的业务类型的优先级或重要性高于所述至少一个PUSCH对应的业务类型的优先级或重要性。
其中，所述业务类型或业务类型的优先级或重要性通过对应的以下信息中至少一种确定：
下行控制信息DCI、无线网络临时标识RNTI、搜索空间、控制资源集CORESET、波束、误块率BLER、信道质量指示CQI表格、调制和编码方案MCS表格、优先级标志、PUCCH资源和SR配置编号。
其中，所述预设RV为自解码RV。
其中，所述一组重复传输的PUSCH为承载同一个传输块TB的重复传输的多个PUSCH。
本公开的实施例还提供一种物理上行共享信道的传输方法，应用于网络设备，所述方法包括：
当确定一组重复传输的物理上行共享信道PUSCH中存在至少一个使用 预设冗余版本RV的PUSCH被丢弃或停止传输时，基于所述预设RV确定所述一组重复传输的PUSCH中的被丢弃或停止传输的PUSCH之后的至少一个PUSCH的RV；
按照确定的RV接收对应的PUSCH。
其中，确定所述一组重复传输的PUSCH中的被丢弃或停止传输的PUSCH之后的至少一个PUSCH的RV，包括：
确定所述一组重复传输的PUSCH中的所述被丢弃或停止传输的PUSCH之后的第一个PUSCH的RV为所述预设RV；所述一组重复传输的PUSCH中的所述第一个PUSCH之后的PUSCH的RV保持不变。
其中，确定所述一组重复传输的PUSCH中的被丢弃或停止传输的PUSCH之后的至少一个PUSCH的RV，包括：
确定所述一组重复传输的PUSCH中的被丢弃或停止传输的PUSCH之后的第一个PUSCH的RV为所述预设RV，确定所述一组重复传输的PUSCH中的所述第一个PUSCH之后的PUSCH的RV为：以所述预设RV在预定的RV序列中的位置为起点，向后顺序确定的RV。
其中，确定所述一组重复传输的PUSCH中的被丢弃或停止传输的PUSCH之后的至少一个PUSCH的RV，包括：
确定所述一组重复传输的PUSCH中的所述被丢弃或停止传输的PUSCH之后的PUSCH的RV为所述预设RV。
其中，所述至少一个PUSCH被丢弃或停止传输，包括以下至少一种：
当所述至少一个PUSCH与承载第一类上行控制信息UCI的物理上行控制信道PUCCH重叠时，所述至少一个PUSCH被丢弃或停止传输；
当所述至少一个PUSCH与PUCCH重叠，且所述PUCCH的优先级或重要性高于所述至少一个PUSCH时，所述至少一个PUSCH被丢弃或停止传输；
当所述至少一个PUSCH与重复传输的PUCCH重叠时，所述至少一个PUSCH被丢弃或停止传输。
其中，所述第一类UCI为调度请求SR或者为对应第一类业务的UCI或者对应第一类业务的SR；
其中，所述第一类业务为：优先级或重要性高的业务，或者，超可靠低 时延通信URLLC业务。
其中，所述重复传输的PUSCH对应第二类业务；
其中，所述第二类业务为：优先级或重要性低的业务，或者，为增强移动宽带eMBB业务，或者，为非URLLC业务。
其中，所述PUCCH的优先级或重要性高于所述至少一个PUSCH，包括：
所述PUCCH对应的业务类型的优先级或重要性高于所述至少一个PUSCH对应的业务类型的优先级或重要性。
其中，所述业务类型或业务类型的优先级或重要性通过对应的以下信息中至少一种确定：下行控制信息DCI、无线网络临时标识RNTI、搜索空间、控制资源集CORESET、波束、误块率BLER、信道质量指示CQI表格、调制和编码方案MCS表格、优先级标志、PUCCH资源和SR配置编号。
其中，所述预设RV为自解码RV。
其中，所述一组重复传输的PUSCH为承载同一个传输块TB的重复传输的多个PUSCH。
本公开的实施例还提供一种终端，包括：处理器，收发机，存储器，所述存储器上存有所述处理器可执行的程序，所述处理器执行所述程序时，实现：
当一组重复传输的物理上行共享信道PUSCH中存在至少一个使用预设冗余版本RV的PUSCH被丢弃或停止传输时，基于所述预设RV确定所述一组重复传输的PUSCH中的被丢弃或停止传输的PUSCH之后的至少一个PUSCH的RV；
所述收发机按照确定的RV发送对应的PUSCH。
其中，所述处理器具体用于：确定所述一组重复传输的PUSCH中的所述被丢弃或停止传输的PUSCH之后的第一个PUSCH的RV为所述预设RV；所述一组重复传输的PUSCH中的所述第一个PUSCH之后的PUSCH的RV保持不变；或者，
确定所述一组重复传输的PUSCH中的被丢弃或停止传输的PUSCH之后的第一个PUSCH的RV为所述预设RV，确定所述一组重复传输的PUSCH中的所述第一个PUSCH之后的PUSCH的RV为：以所述预设RV在预定的 RV序列中的位置为起点，向后顺序确定的RV；或者，
所述一组重复传输的PUSCH中的所述被丢弃或停止传输的PUSCH之后的PUSCH的RV为所述预设RV。
其中，所述至少一个PUSCH被丢弃或停止传输，包括以下至少一种：
当所述至少一个PUSCH与承载第一类上行控制信息UCI的物理上行控制信道PUCCH重叠时，所述至少一个PUSCH被丢弃或停止传输；
当所述至少一个PUSCH与PUCCH重叠，且所述PUCCH的优先级或重要性高于重复传输的PUSCH时，所述至少一个PUSCH被丢弃或停止传输；
当所述至少一个PUSCH与重复传输的PUCCH重叠时，所述至少一个PUSCH被丢弃或停止传输。
其中，所述第一类UCI为调度请求SR或者为对应第一类业务的UCI或者对应第一类业务的SR；
其中，所述第一类业务为：优先级或重要性高的业务，或者，超可靠低时延通信URLLC业务。
其中，所述重复传输的PUSCH对应第二类业务；
其中，所述第二类业务为：优先级或重要性低的业务，或者，为增强移动宽带eMBB业务，或者，为非URLLC业务。
其中，所述PUCCH的优先级或重要性高于所述至少一个的PUSCH，包括：所述PUCCH对应的业务类型的优先级或重要性高于所述至少一个PUSCH对应的业务类型的优先级或重要性。
其中，所述业务类型或业务类型的优先级或重要性通过对应的以下信息中至少一种确定：下行控制信息DCI、无线网络临时标识RNTI、搜索空间、控制资源集CORESET、波束、误块率BLER、信道质量指示CQI表格、调制和编码方案MCS表格、优先级标志、PUCCH资源和SR配置编号。
其中，所述预设RV为自解码RV。
其中，所述一组重复传输的PUSCH为承载同一个传输块TB的重复传输的多个PUSCH。
本公开的实施例还提供一种终端，包括：
处理模块，用于当一组重复传输的物理上行共享信道PUSCH中存在至 少一个使用预设冗余版本RV的PUSCH被丢弃或停止传输时，基于所述预设RV确定所述一组重复传输的PUSCH中的被丢弃或停止传输的PUSCH之后的至少一个PUSCH的RV；
收发模块，用于按照确定的RV发送对应的PUSCH。
其中，所述处理模块具体用于：确定所述一组重复传输的PUSCH中的所述被丢弃或停止传输的PUSCH之后的第一个PUSCH的RV为所述预设RV；所述一组重复传输的PUSCH中的所述第一个PUSCH之后的PUSCH的RV保持不变；或者，确定所述一组重复传输的PUSCH中的被丢弃或停止传输的PUSCH之后的第一个PUSCH的RV为所述预设RV，确定所述一组重复传输的PUSCH中的所述第一个PUSCH之后的PUSCH的RV为：以所述预设RV在预定的RV序列中的位置为起点，向后顺序确定的RV；或者，确定所述一组重复传输的PUSCH中的所述被丢弃或停止传输的PUSCH之后的PUSCH的RV为所述预设RV。
本公开的实施例还提供一种网络设备，包括：处理器，收发机，存储器，所述存储器上存有所述处理器可执行的程序，所述处理器执行所述程序时，实现：
当确定一组重复传输的物理上行共享信道PUSCH中存在至少一个使用预设冗余版本RV的PUSCH被丢弃或停止传输时，基于所述预设RV确定所述一组重复传输的PUSCH中的被丢弃或停止传输的PUSCH之后的至少一个PUSCH的RV；
所述收发机用于按照确定的RV接收对应的PUSCH。
其中，所述处理器具体用于：确定所述一组重复传输的PUSCH中的所述被丢弃或停止传输的PUSCH之后的第一个PUSCH的RV为所述预设RV；所述一组重复传输的PUSCH中的所述第一个PUSCH之后的PUSCH的RV保持不变；或者，
确定所述一组重复传输的PUSCH中的被丢弃或停止传输的PUSCH之后的第一个PUSCH的RV为所述预设RV，确定所述一组重复传输的PUSCH中的所述第一个PUSCH之后的PUSCH的RV为：以所述预设RV在预定的RV序列中的位置为起点，向后顺序确定的RV；或者，
确定所述一组重复传输的PUSCH中的所述被丢弃或停止传输的PUSCH之后的PUSCH的RV为所述预设RV。
其中，所述至少一个PUSCH被丢弃或停止传输，包括以下至少一种：
当所述至少一个PUSCH与承载第一类上行控制信息UCI的物理上行控制信道PUCCH重叠时，所述至少一个PUSCH被丢弃或停止传输；
当所述至少一个PUSCH与PUCCH重叠，且所述PUCCH的优先级或重要性高于所述至少一个的PUSCH时，所述至少一个PUSCH被丢弃或停止传输；
当所述至少一个PUSCH与重复传输的PUCCH重叠时，所述至少一个PUSCH被丢弃或停止传输。
其中，所述第一类UCI为调度请求SR或者为对应第一类业务的UCI或者对应第一类业务的调度请求SR；
其中，所述第一类业务为：优先级或重要性高的业务，或者，超可靠低时延通信URLLC业务。
其中，所述重复传输的PUSCH对应第二类业务；
其中，所述第二类业务为：优先级或重要性低的业务，或者，为增强移动宽带eMBB业务，或者，为非URLLC业务。
其中，所述PUCCH的优先级或重要性高于所述至少一个的PUSCH，包括：
所述PUCCH对应的业务类型的优先级或重要性高于所述至少一个PUSCH对应的业务类型的优先级或重要性。
其中，所述业务类型或业务类型的优先级或重要性通过对应的以下信息中至少一种确定：
下行控制信息DCI、无线网络临时标识RNTI、搜索空间、控制资源集CORESET、波束、误块率BLER、信道质量指示CQI表格、调制和编码方案MCS表格、优先级标志、PUCCH资源和SR配置编号。
其中，所述预设RV为自解码RV。
其中，所述一组重复传输的PUSCH为承载同一个传输块TB的重复传输的多个PUSCH。
本公开的实施例还提供一种网络设备，包括：
处理模块，用于当确定一组重复传输的物理上行共享信道PUSCH中存在至少一个使用预设冗余版本RV的PUSCH被丢弃或停止传输时，基于所述预设RV确定所述一组重复传输的PUSCH中的被丢弃或停止传输的PUSCH之后的至少一个PUSCH的RV；
收发模块，用于按照确定的RV接收对应的PUSCH。
其中，所述处理模块具体用于确定所述一组重复传输的PUSCH中的所述被丢弃或停止传输的PUSCH之后的第一个PUSCH的RV为所述预设RV；所述一组重复传输的PUSCH中的所述第一个PUSCH之后的PUSCH的RV保持不变；或者，
确定所述一组重复传输的PUSCH中的被丢弃或停止传输的PUSCH之后的第一个PUSCH的RV为所述预设RV，确定所述一组重复传输的PUSCH中的所述第一个PUSCH之后的PUSCH的RV为：以所述预设RV在预定的RV序列中的位置为起点，向后顺序确定的RV；或者，
确定所述一组重复传输的PUSCH中的所述被丢弃或停止传输的PUSCH之后的PUSCH的RV为所述预设RV。
本公开的实施例还提供一种计算机存储介质，包括指令，当所述指令在计算机运行时，使得计算机执行如上所述的方法。
本公开实施例的有益效果是：
本公开的上述实施例中，当一组重复传输的PUSCH中存在至少一个使用第一类RV的PUSCH被丢弃或停止传输时，基于所述第一类RV确定所述一组重复传输的PUSCH中的所述被丢弃或停止传输的PUSCH之后的至少一个PUSCH的RV；按照确定的RV发送对应的PUSCH，保证了重复传输的PUSCH的正常传输。
附图说明
为了更清楚地说明本公开实施例的技术方案，下面将对本公开实施例的描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本公开的一些实施例，对于本领域普通技术人员来讲，在不付出创造性 劳动的前提下，还可以根据这些附图获得其他的附图。
图1为PUCCH可能与PUSCH重叠的示意图；
图2为本公开的实施例终端侧的物理上行共享信道的传输方法流程图；
图3为本公开的实施例中，PUSCH进行4次重复传输的配置示意图；
图4为本公开的实施例中，确定所述一组重复传输的PUSCH中的被丢弃或停止传输的PUSCH之后的至少一个PUSCH的RV的一种实现方式示意图；
图5为本公开的实施例中，确定所述一组重复传输的PUSCH中的被丢弃或停止传输的PUSCH之后的至少一个PUSCH的RV的另一种实现方式示意图；
图6为本公开的实施例中，确定所述一组重复传输的PUSCH中的被丢弃或停止传输的PUSCH之后的至少一个PUSCH的RV的再一种实现方式示意图；
图7为本公开的实施例网络设备侧的物理上行共享信道的传输方法流程图；
图8为本公开的实施例终端的架构示意图；
图9为本公开的实施例网络设备的架构示意图。
具体实施方式
下面将参照附图更详细地描述本公开的示例性实施例。虽然附图中显示了本公开的示例性实施例，然而应当理解，可以以各种形式实现本公开而不应被这里阐述的实施例所限制。相反，提供这些实施例是为了能够更透彻地理解本公开，并且能够将本公开的范围完整的传达给本领域的技术人员。
如图2所示，本公开的实施例提供一种物理上行共享信道的传输方法，应用于终端，所述方法包括：
步骤21，当一组重复传输的物理上行共享信道PUSCH中存在至少一个使用预设冗余版本RV的PUSCH被丢弃或停止传输时，基于所述预设RV确定所述一组重复传输的PUSCH中的被丢弃或停止传输的PUSCH之后的至少一个PUSCH的RV；所述预设RV为自解码RV，如RV0；所述一组重复传 输的PUSCH为承载同一个传输块TB的重复传输的多个PUSCH；
步骤22，按照确定的RV发送对应的PUSCH。
本公开的该实施例中，当一组重复传输的PUSCH中存在至少一个使用第一类RV的PUSCH被丢弃或停止传输时，基于所述第一类RV确定所述一组重复传输的PUSCH中的所述被丢弃或停止传输的PUSCH之后的至少一个PUSCH的RV；按照确定的RV发送对应的PUSCH，保证了重复传输的PUSCH的正常传输。进一步地，当一组重复传输的PUSCH中的至少一个使用自解码RV的PUSCH被丢弃时，改变被丢弃的PUSCH之后的重复传输的PUSCH的RV，以包含可自解码版本的RV。
本公开的一具体实施例中，上述步骤21中，确定所述一组重复传输的PUSCH中的被丢弃或停止传输的PUSCH之后的至少一个PUSCH的RV，可以包括：
步骤211，确定所述一组重复传输的PUSCH中的所述被丢弃或停止传输的PUSCH之后的第一个PUSCH的RV为所述预设RV；所述一组重复传输的PUSCH中的所述第一个PUSCH之后的PUSCH的RV保持不变。
也就是说，所述一组重复传输的PUSCH中的所述第一个PUSCH之后的PUSCH的RV，为以所述一组重复传输的PUSCH中的第一个PUSCH的RV在预定的RV序列中的位置为起点，向后顺序确定的RV，即只改变被丢弃或停止传输的PUSCH之后的第一个PUSCH的RV，不改变其他PUSCH的RV；
例如，预定的RV序列为{0,2,3,1}，则如果一组中包含4个PUSCH，第一个PUSCH的RV为RV0，按照RV0为起点，在RV序列中向后顺序确定第二个PUSCH的RV为RV2，第三个PUSCH的RV为RV3，第四个PUSCH的RV为RV1，假设第一个PUSCH由于与PUCCH重叠而被丢弃，由于其RV为RV0，较为重要，不能被丢弃，则需要在第二个PUSCH传输时改变其原本的RV2为RV0，以保证重复传输的PUSCH中存在RV0传输，其他PUSCH，即第三个和第四个PUSCH的RV还是原本确定的RV，不改变。
本公开的一具体实施例中，上述步骤21中，确定所述一组重复传输的PUSCH中的被丢弃或停止传输的PUSCH之后的至少一个PUSCH的RV，也可以包括：
步骤212，确定所述一组重复传输的PUSCH中的被丢弃或停止传输的PUSCH之后的第一个PUSCH的RV为所述预设RV，确定所述一组重复传输的PUSCH中的所述第一个PUSCH之后的PUSCH的RV为：以所述预设RV在预定的RV序列中的位置为起点，向后顺序确定的RV。
例如，预定的RV序列为{0,2,3,1}，则如果一组中包含4个PUSCH，第一个PUSCH的RV为RV0，按照RV0为起点，在RV序列中向后顺序确定第二个PUSCH的RV为RV2，第三个PUSCH的RV为RV3，第四个PUSCH的RV为RV1，假设第一个PUSCH由于与PUCCH重叠而被丢弃，由于其RV为RV0，较为重要，不能被丢弃，则需要在第二个PUSCH传输时改变其原本的RV2为RV0，以保证重复传输的PUSCH中存在RV0传输，并以第二个PUSCH的RV0为起点，根据后续PUSCH与第二个PUSCH的相对位置，在预定的RV序列中向后顺序确定每个PUSCH的RV，即确定第三个PUSCH的RV为RV2，第四个PUSCH的RV为RV3，此时第三和第四个PUSCH的RV因第二个PUSCH的RV改变而随之发生改变，不再是最初确定的RV。
本公开的一具体实施例中，上述步骤21中，确定所述一组重复传输的PUSCH中的被丢弃或停止传输的PUSCH之后的至少一个PUSCH的RV，还可以包括：
步骤213，确定所述一组重复传输的PUSCH中的所述被丢弃或停止传输的PUSCH之后的PUSCH的RV为所述预设RV。
例如，预定的RV序列为{0,2,3,1}，则如果一组中包含4个PUSCH，第一个PUSCH的RV为RV0，按照RV0为起点，在RV序列中向后顺序确定第二个PUSCH的RV为RV2，第三个PUSCH的RV为RV3，第四个PUSCH的RV为RV1，假设第一个PUSCH由于与PUCCH重叠而被丢弃，由于其RV为RV0，较为重要，不能被丢弃，则需要在后续PUSCH传输时改变其原本的RV为RV0，以保证重复传输的PUSCH中存在RV0传输，从而确定第二、三、四个PUSCH的RV都为RV0，此时第二、三、四个PUSCH的RV因第一个使用RV0的PUSCH被丢弃而随之发生改变，不再是最初确定的RV。
本公开的上述实施例中，当一组重复传输的PUSCH中的至少一个PUSCH被丢弃或停止传输时，包括以下至少一种：
1)当一组重复传输的PUSCH中的至少一个PUSCH与承载第一类上行控制信息UCI的物理上行控制信道PUCCH重叠时，所述至少一个PUSCH被丢弃或停止传输；
一种实现方式中，所述第一类上行控制信息UCI为调度请求SR或者为对应第一类业务的UCI或者对应第一类业务的调度请求SR；其中，所述第一类业务为：优先级或重要性高的业务，或者，超可靠低时延通信URLLC。
另一种实现方式中，所述重复传输的PUSCH对应第二类业务；其中，所述第二类业务为：优先级或重要性低的业务，或者，为增强移动宽带eMBB，或者，为非URLLC业务。
再一种实现方式中，所述第一类UCI为SR或者为对应第一类业务的UCI或者对应第一类业务的SR，且所述重复传输的PUSCH对应第二类业务，其中，第一类业务的优先级或重要性高于第二类业务的优先级或重要性。
其中，上述业务类型或优先级或重要性可以通过对应的以下信息中至少一种确定：下行控制信息DCI、无线网络临时标识RNTI、搜索空间、控制资源集CORESET、波束、误块率BLER、信道质量指示CQI表格、调制和编码方案MCS表格、优先级标志、PUCCH资源和SR配置编号。即基于上述信息中的至少一种可以确定第一类UCI和PUSCH分别对应的业务类型或业务类型的优先级和重要性，从而可以区分出第一类UCI和PUSCH之间哪个更重要，当判定第一类UCI优先级更高或第一类UCI和PUSCH优先级相当时，按照上述规则执行，否则，直接丢弃第一类UCI即可。
例如，当第一类UCI对应第一类DCI格式、第一类DCI大小、第一类RNTI、第一类搜索空间、第一类CORESET、第一类波束、第一类BLER((例如10-5或10-6))、第一类CQI表格(例如URLLC CQI table)、第一类MCS表格(例如URLLC MCS table)、第一类优先级标志、第一类PUCCH资源(例如编号小的资源或者特定编号的资源或者对应特定SR配置编号的资源)、第一类SR配置编号(例如配置了多个SR配置时，较低编号的SR配置认为是对应URLLC的)中的至少一种时，说明第一类UCI优先级高(此时不考虑PUSCH对应的业务的优先级或重要性，即不论PUSCH是否也对应高优先级业务，即即使PUSCH的优先级与第一类UCI相当，还是要丢弃或停止 PUSCH)，则PUSCH被丢弃或停止传输。
又例如，当PUSCH对应第二类DCI格式、第二类DCI大小、第二类RNTI、第二类搜索空间、第二类CORESET、第二类波束、第二类误块率BLER(例如10-2或10-1)、第二类CQI表格(例如64QAM/256QAM CQI table)、第二类MCS表格(例如非URLLC MCS table)、第二类优先级标志、第二类PUCCH资源(例如编号大的资源或者特定编号的资源或者对应特定SR配置编号的资源)、第二类SR配置编号(例如配置了多个SR配置时，较高编号的SR配置认为是对应eMBB或非URLLC的)中的至少一种时，说明PUSCH优先级低(此时不考虑PUCCH对应的业务的优先级或重要性，即不论PUCCH是否也对应低优先级业务，即即使PUSCH的优先级与第一类UCI相当，还是要丢弃或停止PUSCH)，则PUSCH被丢弃或停止传输。
又例如，当第一类UCI对应第一类DCI格式、第一类DCI大小、第一类RNTI、第一类搜索空间、第一类CORESET、第一类波束、第一类BLER((例如10-5或10-6))、第一类CQI表格(例如URLLC CQI table)、第一类MCS表格(例如URLLC MCS table)、第一类优先级标志、第一类PUCCH资源(例如编号小的资源或者特定编号的资源或者对应特定SR配置编号的资源)、第一类SR配置编号(例如配置了多个SR配置时，较低编号的SR配置认为是对应URLLC的)中的至少一种，且PUSCH对应第二类DCI格式、第二类DCI大小、第二类RNTI、第二类搜索空间、第二类CORESET、第二类波束、第二类误块率BLER(例如10-2或10-1)、第二类CQI表格(例如64QAM/256QAM CQI table)、第二类MCS表格(例如非URLLC MCS table)、第二类优先级标志、第二类PUCCH资源(例如编号大的资源或者特定编号的资源或者对应特定SR配置编号的资源)、第二类SR配置编号(例如配置了多个SR配置时，较高编号的SR配置认为是对应eMBB或非URLLC的)中的至少一种时，说明第一类UCI的优先级高于PUSCH的优先级，则PUSCH被丢弃或停止传输。
需要说明的是，上述三种实现方式可以至少一种存在。
2)当一组重复传输的PUSCH中的至少一个PUSCH与PUCCH重叠，且所述PUCCH的优先级或重要性高于所述至少一个PUSCH时，所述至少一 个PUSCH被丢弃或停止传输；
上述PUCCH所承载的UCI可以为SR或混合自动重传应答HARQ-ACK或信道状态信息CSI中的至少一种。
所述PUCCH的优先级或重要性高于所述至少一个PUSCH，包括：
所述PUCCH对应的业务类型的优先级或重要性高于所述至少一个PUSCH对应的业务类型的优先级或重要性；例如，所述PUCCH对应URLLC业务，所述PUSCH对应eMBB业务，或者所述PUCCH对应优先级为1的URLLC业务，所述PUSCH对应优先级为2的URLLC业务，其中优先级1大于优先级2；其中，业务类型的优先级或重要性可以根据对应的如下信息中的至少一种来确定：DCI格式、DCI大小、RNTI、搜索空间、CORESET、波束、BLER、CQI表格、MCS表格、优先级标志、PUCCH资源和SR配置编号。例如，根据PUCCH和PUSCH对应的DCI格式、DCI大小、RNTI、搜索空间、CORESET、波束、BLER、CQI表格、MCS表格、优先级标志中的至少一种，可以确定PUCCH的优先级或重要性高于PUSCH。
3)当一组重复传输的PUSCH中的至少一个PUSCH与重复传输的PUCCH重叠时，所述至少一个PUSCH被丢弃或停止传输。
下面结合具体的PUSCH传输说明上述实施例的具体实现：
如图3，假设配置了PUSCH进行4次重复传输，则一组重复传输的PUSCH中包含4个PUSCH传输，假设预定的RV序列为{0,2,3,1}，假设调度PUSCH重复传输的DCI中的RV指示域指示RV0，则第一个PUSCH在时隙n中传输，其RV为RV0，按照RV0为起点，可在RV序列中向后顺序确定第二个PUSCH的RV为RV2，第三个PUSCH的RV为RV3，第四个PUSCH的RV为RV1。假设在时隙n中存在一个承载URLLC SR的PUCCH与第一个PUSCH重叠，则确定丢弃第一个PUSCH，即在时隙n中通过PUCCH传输SR，由于丢弃了重复传输的PUSCH组中的能够自解码的RV0的PUSCH，为了保证重复传输的PUSCH组中存在使用RV0的PUSCH传输，则：
终端侧：按照下述方式确定后续PUSCH的RV，并以对应的RV发送对应的PUSCH；
采用上述步骤211时，如图4所示：确定第二PUSCH的RV为RV0，即 改变第二个PUSCH原本的RV2为RV0，以保证重复传输的PUSCH中存在RV0传输，第三个和第四个PUSCH的RV还是原本的RV不变；
采用上述步骤212时，如图5所示：确定第二PUSCH的RV为RV0，改变第二个PUSCH原本的RV2为RV0，以保证重复传输的PUSCH中存在RV0传输，并以第二个PUSCH对应RV0为起点，根据后续PUSCH与第二个PUSCH的相对位置，在预定的RV序列中向后顺序确定每个PUSCH的RV，即确定第三个PUSCH的RV为RV2，第四个PUSCH的RV为RV3，此时第三和第四个PUSCH的RV因第二个PUSCH的RV改变而随之发生改变，不再是最初确定的RV；
采用上述步骤213时，如图6所示：确定第二、三、四个PUSCH的RV都为RV0，此时第二、三和四个PUSCH的RV因第一个PUSCH被drop而随之发生改变，不再是最初确定的RV；
基站侧：采用与终端侧对应的方式确定后续PUSCH的RV，按照对应的RV接收对应的PUSCH。
需要说明的是，上述实施例中仅以URLLC SR PUCCH与PUSCH重叠为例，承载其他UCI的PUCCH与PUSCH重叠时，如果按照重叠传输的处理规则是drop PUSCH，则上述方法同样适用；由于任何其他原因导致丢弃重复传输的PUSCH中的至少一个时，都可以使用上述方法，例如重复传输的PUCCH与PUSCH重叠时，相关技术中总是丢弃重叠的PUSCH，则RV0的PUSCH可能由于与重复传输的PUCCH重叠而被丢弃，此时，需要修改后续不与PUCCH重叠的重复传输的PUSCH传输RV0；上述PUSCH可以为eMBB的PUSCH，则此时显然URLLC SR的优先级和重要性高于eMBB，上述PUSCH也可是同样是URLLC PUSCH，虽然与SR同属于URLLC业务，但考虑到重复传输的PUSCH占用时域长度较长，如果丢弃SR会导致SR的时延过大，此时，也会因为SR与重复传输的PUSCH重叠而丢弃重复传输的PUSCH中的一个或多个；上述仅以时隙为单位的PUSCH重复传输为例，如果在一个时隙中可以存在多个PUSCH对应同一个TB传输，即时隙内的重复传输，则上述方法同样适用，所不同的是，可能会存在一个承载SR的PUCCH与多个重复传输的PUSCH重叠，例如同时与第一个和第二个PUSCH重叠， 则需要丢弃两个PUSCH，则第三个PUSCH为丢弃PUSCH之后的第一个信道，确定其RV为RV0；上述丢弃PUSCH也可能是部分丢弃，即取消或终止一个PUSCH传输，可能是PUSCH已经传输了一部分之后开始停止传输；上述PUSCH不限于具有DCI调度的PUSCH还是免调度PUSCH，如果为免调度PUSCH，其RV序列可以不同于上述序列，例如可能为{0,0,0,0}、{0,3,0,3}等。
本公开的上述实施例中，当一组重复传输的PUSCH中的至少一个使用自解码RV的PUSCH被丢弃时，通过改变被丢弃的PUSCH之后的重复传输的PUSCH的RV，以包含可自解码版本的RV，保证PUSCH重复传输的可靠性。
如图7所示，一种物理上行共享信道的传输方法，其中，应用于网络设备，所述方法包括：
步骤71，当确定一组重复传输的物理上行共享信道PUSCH中存在至少一个使用预设冗余版本RV的PUSCH被丢弃或停止传输时，基于所述预设RV确定所述一组重复传输的PUSCH中的被丢弃或停止传输的PUSCH之后的至少一个PUSCH的RV；所述预设RV为自解码RV；所述一组重复传输的PUSCH为承载同一个传输块TB的重复传输的多个PUSCH；
步骤72，按照确定的RV接收对应的PUSCH。
一种实施例中，步骤71中，确定所述一组重复传输的PUSCH中的被丢弃或停止传输的PUSCH之后的至少一个PUSCH的RV，可以包括：
步骤711，确定所述一组重复传输的PUSCH中的所述被丢弃或停止传输的PUSCH之后的第一个PUSCH的RV为所述预设RV；所述一组重复传输的PUSCH中的所述第一个PUSCH之后的PUSCH的RV保持不变。
另一种实施例中，步骤71中，确定所述一组重复传输的PUSCH中的被丢弃或停止传输的PUSCH之后的至少一个PUSCH的RV，包括：
步骤712，确定所述一组重复传输的PUSCH中的被丢弃或停止传输的PUSCH之后的第一个PUSCH的RV为所述预设RV，确定所述一组重复传输的PUSCH中的所述第一个PUSCH之后的PUSCH的RV为：以所述预设RV在预定的RV序列中的位置为起点，向后顺序确定的RV。
另一种实施例中，步骤71中，确定所述一组重复传输的PUSCH中的被丢弃或停止传输的PUSCH之后的至少一个PUSCH的RV，包括：
步骤713，确定所述一组重复传输的PUSCH中的所述被丢弃或停止传输的PUSCH之后的PUSCH的RV为所述预设RV。
上述实施例中，所述至少一个PUSCH被丢弃或停止传输，包括以下至少一种：
1)当所述至少一个PUSCH与承载第一类上行控制信息UCI的物理上行控制信道PUCCH重叠时，所述至少一个PUSCH被丢弃或停止传输；
一种实现方式中，所述第一类上行控制信息UCI为调度请求SR或者为对应第一类业务的UCI或者对应第一类业务的调度请求SR；其中，所述第一类业务为：优先级或重要性高的业务，或者，超可靠低时延通信URLLC。
另一种实现方式中，所述重复传输的PUSCH对应第二类业务；其中，所述第二类业务为：优先级或重要性低的业务，或者，为增强移动宽带eMBB，或者，为非URLLC业务。
再一种实现方式中，所述第一类UCI为SR或者为对应第一类业务的UCI或者对应第一类业务的SR，且所述重复传输的PUSCH对应第二类业务，其中，第一类业务的优先级或重要性高于第二类业务的优先级或重要性。
其中，上述业务类型或优先级或重要性可以通过对应的以下信息中至少一种确定：下行控制信息DCI、无线网络临时标识RNTI、搜索空间、控制资源集CORESET、波束、误块率BLER、信道质量指示CQI表格、调制和编码方案MCS表格、优先级标志、PUCCH资源和SR配置编号。即基于上述信息中的至少一种可以确定第一类UCI和PUSCH分别对应的业务类型或业务类型的优先级和重要性，从而可以区分出第一类UCI和PUSCH之间哪个更重要，当判定第一类UCI优先级更高或第一类UCI和PUSCH优先级相当时，按照上述规则执行，否则，直接丢弃第一类UCI即可。
上述三种实现方式可以独立实现，也可以任意组合实现。
2)当一组重复传输的PUSCH中的至少一个PUSCH与PUCCH重叠，且所述PUCCH的优先级或重要性高于重复传输的PUSCH时，所述至少一个PUSCH被丢弃或停止传输；
上述PUCCH所承载的UCI可以为调度请求SR或混合自动重传应答HARQ-ACK或信道状态信息CSI中的至少一种。
所述PUCCH的优先级或重要性高于所述至少一个的PUSCH，包括：
所述PUCCH对应的业务类型的优先级或重要性高于所述至少一个PUSCH对应的业务类型的优先级或重要性。
3)当一组重复传输的PUSCH中的至少一个PUSCH与重复传输的PUCCH重叠时，所述至少一个PUSCH被丢弃或停止传输。
本公开的该实施例中，当一组重复传输的PUSCH中的至少一个使用自解码RV的PUSCH被丢弃时，通过改变被丢弃的PUSCH之后的重复传输的PUSCH的RV，以包含可自解码版本的RV，保证PUSCH重复传输的可靠性。
如图8所示，本公开的实施例还提供一种终端80，包括：处理器82，收发机81，存储器83，所述存储器83上存有所述处理器82可执行的程序，所述处理器82执行所述程序时，实现：当一组重复传输的物理上行共享信道PUSCH中存在至少一个使用预设冗余版本RV的PUSCH被丢弃或停止传输时，基于所述预设RV确定所述一组重复传输的PUSCH中的被丢弃或停止传输的PUSCH之后的至少一个PUSCH的RV；
所述收发机按照确定的RV发送对应的PUSCH。
其中，所述处理器82具体用于：确定所述一组重复传输的PUSCH中的所述被丢弃或停止传输的PUSCH之后的第一个PUSCH的RV为所述预设RV；所述一组重复传输的PUSCH中的所述第一个PUSCH之后的PUSCH的RV保持不变；或者，
确定所述一组重复传输的PUSCH中的被丢弃或停止传输的PUSCH之后的第一个PUSCH的RV为所述预设RV，确定所述一组重复传输的PUSCH中的所述第一个PUSCH之后的PUSCH的RV为：以所述预设RV在预定的RV序列中的位置为起点，向后顺序确定的RV；或者，
所述一组重复传输的PUSCH中的所述被丢弃或停止传输的PUSCH之后的PUSCH的RV为所述预设RV。
其中，所述至少一个PUSCH被丢弃或停止传输，包括以下至少一种：
当所述至少一个PUSCH与承载第一类上行控制信息UCI的物理上行控 制信道PUCCH重叠时，所述至少一个PUSCH被丢弃或停止传输；
当所述至少一个PUSCH与PUCCH重叠，且所述PUCCH的优先级或重要性高于重复传输的PUSCH时，所述至少一个PUSCH被丢弃或停止传输；
当所述至少一个PUSCH与重复传输的PUCCH重叠时，所述至少一个PUSCH被丢弃或停止传输。
其中，所述第一类UCI为调度请求SR或者为对应第一类业务的UCI或者对应第一类业务的SR；
其中，所述第一类业务为：优先级或重要性高的业务，或者，超可靠低时延通信URLLC业务。
其中，所述重复传输的PUSCH对应第二类业务；
其中，所述第二类业务为：优先级或重要性低的业务，或者，为增强移动宽带eMBB业务，或者，为非URLLC业务。
其中，所述PUCCH的优先级或重要性高于所述至少一个的PUSCH，包括：所述PUCCH对应的业务类型的优先级或重要性高于所述至少一个PUSCH对应的业务类型的优先级或重要性。
其中，所述业务类型或业务类型的优先级或重要性通过对应的以下信息中至少一种确定：下行控制信息DCI、无线网络临时标识RNTI、搜索空间、控制资源集CORESET、波束、误块率BLER、信道质量指示CQI表格、调制和编码方案MCS表格、优先级标志、PUCCH资源和SR配置编号。
其中，所述预设RV为自解码RV。
其中，所述一组重复传输的PUSCH为承载同一个传输块TB的重复传输的多个PUSCH。
需要说明的是，该终端是与上述图2所示方法对应的终端，上述方法实施例中所有实现方式均适用于该终端的实施例中，也能达到相同的技术效果。收发机81与处理器82，以及，收发机机81与存储器83之间，均可以通过总线接口连接，收发机81的功能可以由处理器82实现，处理器82的功能也可以由收发机81实现。
本公开的实施例还提供一种终端，包括：
处理模块，用于当一组重复传输的物理上行共享信道PUSCH中存在至 少一个使用预设冗余版本RV的PUSCH被丢弃或停止传输时，基于所述预设RV确定所述一组重复传输的PUSCH中的被丢弃或停止传输的PUSCH之后的至少一个PUSCH的RV；
收发模块，用于按照确定的RV发送对应的PUSCH。
所述处理模块具体用于：确定所述一组重复传输的PUSCH中的所述被丢弃或停止传输的PUSCH之后的第一个PUSCH的RV为所述预设RV；所述一组重复传输的PUSCH中的所述第一个PUSCH之后的PUSCH的RV保持不变；或者，确定所述一组重复传输的PUSCH中的被丢弃或停止传输的PUSCH之后的第一个PUSCH的RV为所述预设RV，确定所述一组重复传输的PUSCH中的所述第一个PUSCH之后的PUSCH的RV为：以所述预设RV在预定的RV序列中的位置为起点，向后顺序确定的RV；或者，确定所述一组重复传输的PUSCH中的所述被丢弃或停止传输的PUSCH之后的PUSCH的RV为所述预设RV。
其中，所述至少一个PUSCH被丢弃或停止传输，包括以下至少一种：
当所述至少一个PUSCH与承载第一类上行控制信息UCI的物理上行控制信道PUCCH重叠时，所述至少一个PUSCH被丢弃或停止传输；
当所述至少一个PUSCH与PUCCH重叠，且所述PUCCH的优先级或重要性高于重复传输的PUSCH时，所述至少一个PUSCH被丢弃或停止传输；
当所述至少一个PUSCH与重复传输的PUCCH重叠时，所述至少一个PUSCH被丢弃或停止传输。
其中，所述第一类UCI为调度请求SR或者为对应第一类业务的UCI或者对应第一类业务的SR；
其中，所述第一类业务为：优先级或重要性高的业务，或者，超可靠低时延通信URLLC业务。
其中，所述重复传输的PUSCH对应第二类业务；
其中，所述第二类业务为：优先级或重要性低的业务，或者，为增强移动宽带eMBB业务，或者，为非URLLC业务。
其中，所述PUCCH的优先级或重要性高于所述至少一个的PUSCH，包括：所述PUCCH对应的业务类型的优先级或重要性高于所述至少一个 PUSCH对应的业务类型的优先级或重要性。
其中，所述业务类型或业务类型的优先级或重要性通过对应的以下信息中至少一种确定：下行控制信息DCI、无线网络临时标识RNTI、搜索空间、控制资源集CORESET、波束、误块率BLER、信道质量指示CQI表格、调制和编码方案MCS表格、优先级标志、PUCCH资源和SR配置编号。
其中，所述预设RV为自解码RV。
其中，所述一组重复传输的PUSCH为承载同一个传输块TB的重复传输的多个PUSCH。需要说明的是，该终端是与上述图2所示方法对应的终端，上述方法实施例中所有实现方式均适用于该终端的实施例中，也能达到相同的技术效果。
如图9所示，本公开的实施例还提供一种网络设备90，包括：处理器92，收发机91，存储器93，所述存储器93上存有所述处理器93可执行的程序，所述处理器93执行所述程序时，实现：当确定一组重复传输的物理上行共享信道PUSCH中存在至少一个使用预设冗余版本RV的PUSCH被丢弃或停止传输时，基于所述预设RV确定所述一组重复传输的PUSCH中的被丢弃或停止传输的PUSCH之后的至少一个PUSCH的RV；
所述收发机91用于按照确定的RV接收对应的PUSCH。
其中，所述处理器92具体用于确定所述一组重复传输的PUSCH中的所述被丢弃或停止传输的PUSCH之后的第一个PUSCH的RV为所述预设RV；所述一组重复传输的PUSCH中的所述第一个PUSCH之后的PUSCH的RV保持不变；或者，
确定所述一组重复传输的PUSCH中的被丢弃或停止传输的PUSCH之后的第一个PUSCH的RV为所述预设RV，确定所述一组重复传输的PUSCH中的所述第一个PUSCH之后的PUSCH的RV为：以所述预设RV在预定的RV序列中的位置为起点，向后顺序确定的RV；或者，
确定所述一组重复传输的PUSCH中的所述被丢弃或停止传输的PUSCH之后的PUSCH的RV为所述预设RV。
其中，所述至少一个PUSCH被丢弃或停止传输，包括以下至少一种：
当所述至少一个PUSCH与承载第一类上行控制信息UCI的物理上行控 制信道PUCCH重叠时，所述至少一个PUSCH被丢弃或停止传输；
当所述至少一个PUSCH与PUCCH重叠，且所述PUCCH的优先级或重要性高于所述至少一个的PUSCH时，所述至少一个PUSCH被丢弃或停止传输；
当所述至少一个PUSCH与重复传输的PUCCH重叠时，所述至少一个PUSCH被丢弃或停止传输。
其中，所述第一类UCI为调度请求SR或者为对应第一类业务的UCI或者对应第一类业务的调度请求SR；
其中，所述第一类业务为：优先级或重要性高的业务，或者，超可靠低时延通信URLLC业务。
其中，所述重复传输的PUSCH对应第二类业务；
其中，所述第二类业务为：优先级或重要性低的业务，或者，为增强移动宽带eMBB业务，或者，为非URLLC业务。
其中，所述PUCCH的优先级或重要性高于所述至少一个的PUSCH，包括：
所述PUCCH对应的业务类型的优先级或重要性高于所述至少一个PUSCH对应的业务类型的优先级或重要性。
其中，所述业务类型或业务类型的优先级或重要性通过对应的以下信息中至少一种确定：
下行控制信息DCI、无线网络临时标识RNTI、搜索空间、控制资源集CORESET、波束、误块率BLER、信道质量指示CQI表格、调制和编码方案MCS表格、优先级标志、PUCCH资源和SR配置编号。
其中，所述预设RV为自解码RV。
其中，所述一组重复传输的PUSCH为承载同一个传输块TB的重复传输的多个PUSCH。
需要说明的是，该终端是与上述图7所示方法对应的终端，上述方法实施例中所有实现方式均适用于该终端的实施例中，也能达到相同的技术效果。收发机91与处理器92，以及，收发机机91与存储器93之间，均可以通过总线接口连接，收发机91的功能可以由处理器92实现，处理器92的功能也 可以由收发机91实现。
本公开的实施例还提供一种网络设备，包括：
处理模块，用于当确定一组重复传输的物理上行共享信道PUSCH中存在至少一个使用预设冗余版本RV的PUSCH被丢弃或停止传输时，基于所述预设RV确定所述一组重复传输的PUSCH中的被丢弃或停止传输的PUSCH之后的至少一个PUSCH的RV；
收发模块，用于按照确定的RV接收对应的PUSCH。
其中，所述处理模块具体用于确定所述一组重复传输的PUSCH中的所述被丢弃或停止传输的PUSCH之后的第一个PUSCH的RV为所述预设RV；所述一组重复传输的PUSCH中的所述第一个PUSCH之后的PUSCH的RV保持不变；或者，
确定所述一组重复传输的PUSCH中的被丢弃或停止传输的PUSCH之后的第一个PUSCH的RV为所述预设RV，确定所述一组重复传输的PUSCH中的所述第一个PUSCH之后的PUSCH的RV为：以所述预设RV在预定的RV序列中的位置为起点，向后顺序确定的RV；或者，
确定所述一组重复传输的PUSCH中的所述被丢弃或停止传输的PUSCH之后的PUSCH的RV为所述预设RV。
其中，所述至少一个PUSCH被丢弃或停止传输，包括以下至少一种：
当所述至少一个PUSCH与承载第一类上行控制信息UCI的物理上行控制信道PUCCH重叠时，所述至少一个PUSCH被丢弃或停止传输；
当所述至少一个PUSCH与PUCCH重叠，且所述PUCCH的优先级或重要性高于所述至少一个的PUSCH时，所述至少一个PUSCH被丢弃或停止传输；
当所述至少一个PUSCH与重复传输的PUCCH重叠时，所述至少一个PUSCH被丢弃或停止传输。
其中，所述第一类UCI为调度请求SR或者为对应第一类业务的UCI或者对应第一类业务的调度请求SR；
其中，所述第一类业务为：优先级或重要性高的业务，或者，超可靠低时延通信URLLC业务。
其中，所述重复传输的PUSCH对应第二类业务；
其中，所述第二类业务为：优先级或重要性低的业务，或者，为增强移动宽带eMBB业务，或者，为非URLLC业务。
其中，所述PUCCH的优先级或重要性高于所述至少一个的PUSCH，包括：
所述PUCCH对应的业务类型的优先级或重要性高于所述至少一个PUSCH对应的业务类型的优先级或重要性。
其中，所述业务类型或业务类型的优先级或重要性通过对应的以下信息中至少一种确定：下行控制信息DCI、无线网络临时标识RNTI、搜索空间、控制资源集CORESET、波束、误块率BLER、信道质量指示CQI表格、调制和编码方案MCS表格、优先级标志、PUCCH资源和SR配置编号。
其中，所述预设RV为自解码RV。
其中，所述一组重复传输的PUSCH为承载同一个传输块TB的重复传输的多个PUSCH。需要说明的是，该网络设备是与上述图7所示方法对应的网络设备，上述方法实施例中所有实现方式均适用于该网络设备的实施例中，也能达到相同的技术效果。
本公开的实施例还提供一种计算机存储介质，包括指令，当所述指令在计算机运行时，使得计算机执行如图2所述的方法或者图7所述的方法。上述图3至图6所示的方法也同样适用该实施例中，也能达到相同的技术效果。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本公开的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本公开所提供的实施例中，应该理解到，所揭露的装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例 如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本公开各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本公开的技术方案本质上或者说对相关技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本公开各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、ROM、RAM、磁碟或者光盘等各种可以存储程序代码的介质。
此外，需要指出的是，在本公开的装置和方法中，显然，各部件或各步骤是可以分解和/或重新组合的。这些分解和/或重新组合应视为本公开的等效方案。并且，执行上述系列处理的步骤可以自然地按照说明的顺序按时间顺序执行，但是并不需要一定按照时间顺序执行，某些步骤可以并行或彼此独立地执行。对本领域的普通技术人员而言，能够理解本公开的方法和装置的全部或者任何步骤或者部件，可以在任何计算装置(包括处理器、存储介质等)或者计算装置的网络中，以硬件、固件、软件或者它们的组合加以实现，这是本领域普通技术人员在阅读了本公开的说明的情况下运用他们的基本编程技能就能实现的。
因此，本公开的目的还可以通过在任何计算装置上运行一个程序或者一组程序来实现。所述计算装置可以是公知的通用装置。因此，本公开的目的也可以仅仅通过提供包含实现所述方法或者装置的程序代码的程序产品来实现。也就是说，这样的程序产品也构成本公开，并且存储有这样的程序产品的存储介质也构成本公开。显然，所述存储介质可以是任何公知的存储介质或者将来所开发出来的任何存储介质。还需要指出的是，在本公开的装置和方法中，显然，各部件或各步骤是可以分解和/或重新组合的。这些分解和/或重新组合应视为本公开的等效方案。并且，执行上述系列处理的步骤可以自然地按照说明的顺序按时间顺序执行，但是并不需要一定按照时间顺序执行。某些步骤可以并行或彼此独立地执行。
可以理解的是，本公开实施例描述的这些实施例可以用硬件、软件、固件、中间件、微码或其组合来实现。对于硬件实现，处理单元可以实现在一个或多个专用集成电路(Application Specific Integrated Circuits，ASIC)、数字信号处理器(Digital Signal Processing，DSP)、数字信号处理设备(DSP Device，DSPD)、可编程逻辑设备(Programmable Logic Device，PLD)、现场可编程门阵列(Field-Programmable Gate Array，FPGA)、通用处理器、控制器、微控制器、微处理器、用于执行本公开所述功能的其它电子单元或其组合中。
对于软件实现，可通过执行本公开实施例所述功能的模块(例如过程、函数等)来实现本公开实施例所述的技术。软件代码可存储在存储器中并通过处理器执行。存储器可以在处理器中或在处理器外部实现。
以上所述的是本公开的可选的实施方式，应当指出对于本技术领域的普通人员来说，在不脱离本公开所述的原理前提下还可以作出若干改进和润饰，这些改进和润饰也在本公开的保护范围内。

Claims (45)

  1. 一种物理上行共享信道的传输方法，应用于终端，包括：
    当一组重复传输的物理上行共享信道PUSCH中存在至少一个使用预设冗余版本RV的PUSCH被丢弃或停止传输时，基于所述预设RV确定所述一组重复传输的PUSCH中的被丢弃或停止传输的PUSCH之后的至少一个PUSCH的RV；
    按照确定的RV发送对应的PUSCH。
  2. 根据权利要求1所述的物理上行共享信道的传输方法，其中，确定所述一组重复传输的PUSCH中的被丢弃或停止传输的PUSCH之后的至少一个PUSCH的RV，包括：
    确定所述一组重复传输的PUSCH中的所述被丢弃或停止传输的PUSCH之后的第一个PUSCH的RV为所述预设RV；所述一组重复传输的PUSCH中的所述第一个PUSCH之后的PUSCH的RV保持不变。
  3. 根据权利要求1所述的物理上行共享信道的传输方法，其中，确定所述一组重复传输的PUSCH中的被丢弃或停止传输的PUSCH之后的至少一个PUSCH的RV，包括：
    确定所述一组重复传输的PUSCH中的被丢弃或停止传输的PUSCH之后的第一个PUSCH的RV为所述预设RV，确定所述一组重复传输的PUSCH中的所述第一个PUSCH之后的PUSCH的RV为：以所述预设RV在预定的RV序列中的位置为起点，向后顺序确定的RV。
  4. 根据权利要求1所述的物理上行共享信道的传输方法，其中，确定所述一组重复传输的PUSCH中的被丢弃或停止传输的PUSCH之后的至少一个PUSCH的RV，包括：
    确定所述一组重复传输的PUSCH中的所述被丢弃或停止传输的PUSCH之后的PUSCH的RV为所述预设RV。
  5. 根据权利要求1所述的物理上行共享信道的传输方法，其中，所述至少一个PUSCH被丢弃或停止传输，包括以下至少一种：
    当所述至少一个PUSCH与承载第一类上行控制信息UCI的物理上行控 制信道PUCCH重叠时，所述至少一个PUSCH被丢弃或停止传输；
    当所述至少一个PUSCH与PUCCH重叠，且所述PUCCH的优先级或重要性高于所述至少一个PUSCH时，所述至少一个PUSCH被丢弃或停止传输；
    当所述至少一个PUSCH与重复传输的PUCCH重叠时，所述至少一个PUSCH被丢弃或停止传输。
  6. 根据权利要求5所述的物理上行共享信道的传输方法，其中，所述第一类UCI为调度请求SR或者为对应第一类业务的UCI或者对应第一类业务的SR；
    其中，所述第一类业务为：优先级或重要性高的业务，或者，超可靠低时延通信URLLC业务。
  7. 根据权利要求5所述的物理上行共享信道的传输方法，其中，所述重复传输的PUSCH对应第二类业务；其中，所述第二类业务为：优先级或重要性低的业务，或者，为增强移动宽带eMBB业务，或者，为非URLLC业务。
  8. 根据权利要求5所述的物理上行共享信道的传输方法，其中，所述PUCCH的优先级或重要性高于所述至少一个PUSCH，包括：
    所述PUCCH对应的业务类型的优先级或重要性高于所述至少一个PUSCH对应的业务类型的优先级或重要性。
  9. 根据权利要求6至8中任一项所述的物理上行共享信道的传输方法，其中，所述业务类型或所述业务类型的优先级或重要性通过对应的以下信息中至少一种确定：
    下行控制信息DCI、无线网络临时标识RNTI、搜索空间、控制资源集CORESET、波束、误块率BLER、信道质量指示CQI表格、调制和编码方案MCS表格、优先级标志、PUCCH资源和SR配置编号。
  10. 根据权利要求1至8任一项所述的物理上行共享信道的传输方法，其中，所述预设RV为自解码RV。
  11. 根据权利要求1至8任一项所述的物理上行共享信道的传输方法，其中，所述一组重复传输的PUSCH为承载同一个传输块TB的重复传输的多个PUSCH。
  12. 一种物理上行共享信道的传输方法，应用于网络设备，包括：
    当确定一组重复传输的物理上行共享信道PUSCH中存在至少一个使用预设冗余版本RV的PUSCH被丢弃或停止传输时，基于所述预设RV确定所述一组重复传输的PUSCH中的被丢弃或停止传输的PUSCH之后的至少一个PUSCH的RV；
    按照确定的RV接收对应的PUSCH。
  13. 根据权利要求12所述的物理上行共享信道的传输方法，其中，确定所述一组重复传输的PUSCH中的被丢弃或停止传输的PUSCH之后的至少一个PUSCH的RV，包括：
    确定所述一组重复传输的PUSCH中的所述被丢弃或停止传输的PUSCH之后的第一个PUSCH的RV为所述预设RV；所述一组重复传输的PUSCH中的所述第一个PUSCH之后的PUSCH的RV保持不变。
  14. 根据权利要求12所述的物理上行共享信道的传输方法，其中，确定所述一组重复传输的PUSCH中的被丢弃或停止传输的PUSCH之后的至少一个PUSCH的RV，包括：
    确定所述一组重复传输的PUSCH中的被丢弃或停止传输的PUSCH之后的第一个PUSCH的RV为所述预设RV，确定所述一组重复传输的PUSCH中的所述第一个PUSCH之后的PUSCH的RV为：以所述预设RV在预定的RV序列中的位置为起点，向后顺序确定的RV。
  15. 根据权利要求12所述的物理上行共享信道的传输方法，其中，确定所述一组重复传输的PUSCH中的被丢弃或停止传输的PUSCH之后的至少一个PUSCH的RV，包括：
    确定所述一组重复传输的PUSCH中的所述被丢弃或停止传输的PUSCH之后的PUSCH的RV为所述预设RV。
  16. 根据权利要求12所述的物理上行共享信道的传输方法，其中，所述至少一个PUSCH被丢弃或停止传输，包括以下至少一种：
    当所述至少一个PUSCH与承载第一类上行控制信息UCI的物理上行控制信道PUCCH重叠时，所述至少一个PUSCH被丢弃或停止传输；
    当所述至少一个PUSCH与PUCCH重叠，且所述PUCCH的优先级或重 要性高于所述至少一个PUSCH时，所述至少一个PUSCH被丢弃或停止传输；
    当所述至少一个PUSCH与重复传输的PUCCH重叠时，所述至少一个PUSCH被丢弃或停止传输。
  17. 根据权利要求16所述的物理上行共享信道的传输方法，其中，所述第一类UCI为调度请求SR或者为对应第一类业务的UCI或者对应第一类业务的SR；
    其中，所述第一类业务为：优先级或重要性高的业务，或者，超可靠低时延通信URLLC业务。
  18. 根据权利要求16所述的物理上行共享信道的传输方法，其中，所述重复传输的PUSCH对应第二类业务；
    其中，所述第二类业务为：优先级或重要性低的业务，或者，为增强移动宽带eMBB业务，或者，为非URLLC业务。
  19. 根据权利要求16所述的物理上行共享信道的传输方法，其中，所述PUCCH的优先级或重要性高于所述至少一个PUSCH，包括：
    所述PUCCH对应的业务类型的优先级或重要性高于所述至少一个PUSCH对应的业务类型的优先级或重要性。
  20. 根据权利要求17至19任一项所述的物理上行共享信道的传输方法，其中，所述业务类型或业务类型的优先级或重要性通过对应的以下信息中至少一种确定：
    下行控制信息DCI、无线网络临时标识RNTI、搜索空间、控制资源集CORESET、波束、误块率BLER、信道质量指示CQI表格、调制和编码方案MCS表格、优先级标志、PUCCH资源和SR配置编号。
  21. 根据权利要求12至19任一项所述的物理上行共享信道的传输方法，其中，所述预设RV为自解码RV。
  22. 根据权利要求12至19任一项所述的物理上行共享信道的传输方法，其中，所述一组重复传输的PUSCH为承载同一个传输块TB的重复传输的多个PUSCH。
  23. 一种终端，包括：处理器，收发机，存储器，所述存储器上存有所述处理器可执行的程序，所述处理器执行所述程序时，实现：
    当一组重复传输的物理上行共享信道PUSCH中存在至少一个使用预设冗余版本RV的PUSCH被丢弃或停止传输时，基于所述预设RV确定所述一组重复传输的PUSCH中的被丢弃或停止传输的PUSCH之后的至少一个PUSCH的RV；
    所述收发机按照确定的RV发送对应的PUSCH。
  24. 根据权利要求23所述的终端，其中，所述处理器具体用于：
    确定所述一组重复传输的PUSCH中的所述被丢弃或停止传输的PUSCH之后的第一个PUSCH的RV为所述预设RV；所述一组重复传输的PUSCH中的所述第一个PUSCH之后的PUSCH的RV保持不变；或者，
    确定所述一组重复传输的PUSCH中的被丢弃或停止传输的PUSCH之后的第一个PUSCH的RV为所述预设RV，确定所述一组重复传输的PUSCH中的所述第一个PUSCH之后的PUSCH的RV为：以所述预设RV在预定的RV序列中的位置为起点，向后顺序确定的RV；或者，
    所述一组重复传输的PUSCH中的所述被丢弃或停止传输的PUSCH之后的PUSCH的RV为所述预设RV。
  25. 根据权利要求23所述的终端，其中，所述至少一个PUSCH被丢弃或停止传输，包括以下至少一种：
    当所述至少一个PUSCH与承载第一类上行控制信息UCI的物理上行控制信道PUCCH重叠时，所述至少一个PUSCH被丢弃或停止传输；
    当所述至少一个PUSCH与PUCCH重叠，且所述PUCCH的优先级或重要性高于重复传输的PUSCH时，所述至少一个PUSCH被丢弃或停止传输；
    当所述至少一个PUSCH与重复传输的PUCCH重叠时，所述至少一个PUSCH被丢弃或停止传输。
  26. 根据权利要求25所述的终端，其中，所述第一类UCI为调度请求SR或者为对应第一类业务的UCI或者对应第一类业务的SR；
    其中，所述第一类业务为：优先级或重要性高的业务，或者，超可靠低时延通信URLLC业务。
  27. 根据权利要求25所述的终端，其中，所述重复传输的PUSCH对应第二类业务；
    其中，所述第二类业务为：优先级或重要性低的业务，或者，为增强移动宽带eMBB业务，或者，为非URLLC业务。
  28. 根据权利要求25所述的终端，其中，所述PUCCH的优先级或重要性高于所述至少一个的PUSCH，包括：
    所述PUCCH对应的业务类型的优先级或重要性高于所述至少一个PUSCH对应的业务类型的优先级或重要性。
  29. 根据权利要求26至28中任一项所述的终端，其中，所述业务类型或业务类型的优先级或重要性通过对应的以下信息中至少一种确定：
    下行控制信息DCI、无线网络临时标识RNTI、搜索空间、控制资源集CORESET、波束、误块率BLER、信道质量指示CQI表格、调制和编码方案MCS表格、优先级标志、PUCCH资源和SR配置编号。
  30. 根据权利要求23至28任一项所述的终端，其中，所述预设RV为自解码RV。
  31. 根据权利要求23至28任一项所述的终端，其中，所述一组重复传输的PUSCH为承载同一个传输块TB的重复传输的多个PUSCH。
  32. 一种终端，其中，包括：
    处理模块，用于当一组重复传输的物理上行共享信道PUSCH中存在至少一个使用预设冗余版本RV的PUSCH被丢弃或停止传输时，基于所述预设RV确定所述一组重复传输的PUSCH中的被丢弃或停止传输的PUSCH之后的至少一个PUSCH的RV；
    收发模块，用于按照确定的RV发送对应的PUSCH。
  33. 根据权利要求32所述的终端，其中，所述处理模块具体用于：
    确定所述一组重复传输的PUSCH中的所述被丢弃或停止传输的PUSCH之后的第一个PUSCH的RV为所述预设RV；所述一组重复传输的PUSCH中的所述第一个PUSCH之后的PUSCH的RV保持不变；或者，
    确定所述一组重复传输的PUSCH中的被丢弃或停止传输的PUSCH之后的第一个PUSCH的RV为所述预设RV，确定所述一组重复传输的PUSCH中的所述第一个PUSCH之后的PUSCH的RV为：以所述预设RV在预定的RV序列中的位置为起点，向后顺序确定的RV；或者，
    确定所述一组重复传输的PUSCH中的所述被丢弃或停止传输的PUSCH之后的PUSCH的RV为所述预设RV。
  34. 一种网络设备，包括：处理器，收发机，存储器，所述存储器上存有所述处理器可执行的程序，所述处理器执行所述程序时，实现：
    当确定一组重复传输的物理上行共享信道PUSCH中存在至少一个使用预设冗余版本RV的PUSCH被丢弃或停止传输时，基于所述预设RV确定所述一组重复传输的PUSCH中的被丢弃或停止传输的PUSCH之后的至少一个PUSCH的RV；
    所述收发机用于按照确定的RV接收对应的PUSCH。
  35. 根据权利要求34所述的网络设备，其中，所述处理器具体用于：确定所述一组重复传输的PUSCH中的所述被丢弃或停止传输的PUSCH之后的第一个PUSCH的RV为所述预设RV；所述一组重复传输的PUSCH中的所述第一个PUSCH之后的PUSCH的RV保持不变；或者，
    确定所述一组重复传输的PUSCH中的被丢弃或停止传输的PUSCH之后的第一个PUSCH的RV为所述预设RV，确定所述一组重复传输的PUSCH中的所述第一个PUSCH之后的PUSCH的RV为：以所述预设RV在预定的RV序列中的位置为起点，向后顺序确定的RV；或者，
    确定所述一组重复传输的PUSCH中的所述被丢弃或停止传输的PUSCH之后的PUSCH的RV为所述预设RV。
  36. 根据权利要求34所述的网络设备，其中，所述至少一个PUSCH被丢弃或停止传输，包括以下至少一种：
    当所述至少一个PUSCH与承载第一类上行控制信息UCI的物理上行控制信道PUCCH重叠时，所述至少一个PUSCH被丢弃或停止传输；
    当所述至少一个PUSCH与PUCCH重叠，且所述PUCCH的优先级或重要性高于所述至少一个的PUSCH时，所述至少一个PUSCH被丢弃或停止传输；
    当所述至少一个PUSCH与重复传输的PUCCH重叠时，所述至少一个PUSCH被丢弃或停止传输。
  37. 根据权利要求36所述的网络设备，其中，所述第一类UCI为调度 请求SR或者为对应第一类业务的UCI或者对应第一类业务的调度请求SR；
    其中，所述第一类业务为：优先级或重要性高的业务，或者，超可靠低时延通信URLLC业务。
  38. 根据权利要求36所述的网络设备，其中，所述重复传输的PUSCH对应第二类业务；
    其中，所述第二类业务为：优先级或重要性低的业务，或者，为增强移动宽带eMBB业务，或者，为非URLLC业务。
  39. 根据权利要求36所述的网络设备，其中，所述PUCCH的优先级或重要性高于所述至少一个的PUSCH，包括：
    所述PUCCH对应的业务类型的优先级或重要性高于所述至少一个PUSCH对应的业务类型的优先级或重要性。
  40. 根据权利要求37至39任一项所述的网络设备，其中，所述业务类型或业务类型的优先级或重要性通过对应的以下信息中至少一种确定：
    下行控制信息DCI、无线网络临时标识RNTI、搜索空间、控制资源集CORESET、波束、误块率BLER、信道质量指示CQI表格、调制和编码方案MCS表格、优先级标志、PUCCH资源和SR配置编号。
  41. 根据权利要求34至39任一项所述的网络设备，其中，所述预设RV为自解码RV。
  42. 根据权利要求34至39任一项所述的网络设备，其中，所述一组重复传输的PUSCH为承载同一个传输块TB的重复传输的多个PUSCH。
  43. 一种网络设备，包括：
    处理模块，用于当确定一组重复传输的物理上行共享信道PUSCH中存在至少一个使用预设冗余版本RV的PUSCH被丢弃或停止传输时，基于所述预设RV确定所述一组重复传输的PUSCH中的被丢弃或停止传输的PUSCH之后的至少一个PUSCH的RV；
    收发模块，用于按照确定的RV接收对应的PUSCH。
  44. 根据权利要求43所述的网络设备，其中，所述处理模块具体用于：确定所述一组重复传输的PUSCH中的所述被丢弃或停止传输的PUSCH之后的第一个PUSCH的RV为所述预设RV；所述一组重复传输的PUSCH中的 所述第一个PUSCH之后的PUSCH的RV保持不变；或者，
    确定所述一组重复传输的PUSCH中的被丢弃或停止传输的PUSCH之后的第一个PUSCH的RV为所述预设RV，确定所述一组重复传输的PUSCH中的所述第一个PUSCH之后的PUSCH的RV为：以所述预设RV在预定的RV序列中的位置为起点，向后顺序确定的RV；或者，
    确定所述一组重复传输的PUSCH中的所述被丢弃或停止传输的PUSCH之后的PUSCH的RV为所述预设RV。
  45. 一种计算机存储介质，其中，包括指令，当所述指令在计算机运行时，使得计算机执行如权利要求1至11任一项所述的方法或者12至22任一项所述的方法。
PCT/CN2020/075203 2019-02-15 2020-02-14 物理上行共享信道的传输方法、终端及网络设备 WO2020164568A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
US17/431,130 US12089206B2 (en) 2019-02-15 2020-02-14 Transmission method for physical uplink shared channel, terminal, and network device
KR1020217028011A KR20210119521A (ko) 2019-02-15 2020-02-14 물리 업링크 공유 채널의 전송 방법, 단말 및 네트워크 기기
EP20755126.8A EP3927057A4 (en) 2019-02-15 2020-02-14 TRANSMISSION METHOD FOR HIGH LINK SHARED CHANNEL, TERMINAL AND NETWORK DEVICES

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910118136.5 2019-02-15
CN201910118136.5A CN111586854B (zh) 2019-02-15 2019-02-15 物理上行共享信道的传输方法、终端及网络设备

Publications (1)

Publication Number Publication Date
WO2020164568A1 true WO2020164568A1 (zh) 2020-08-20

Family

ID=72044281

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/075203 WO2020164568A1 (zh) 2019-02-15 2020-02-14 物理上行共享信道的传输方法、终端及网络设备

Country Status (5)

Country Link
US (1) US12089206B2 (zh)
EP (1) EP3927057A4 (zh)
KR (1) KR20210119521A (zh)
CN (1) CN111586854B (zh)
WO (1) WO2020164568A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220039140A1 (en) * 2020-07-28 2022-02-03 Comcast Cable Communications, Llc Control Channel Repetition Using Multiple Coresets

Families Citing this family (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111586854B (zh) * 2019-02-15 2024-03-08 大唐移动通信设备有限公司 物理上行共享信道的传输方法、终端及网络设备
WO2020197258A1 (ko) * 2019-03-27 2020-10-01 엘지전자 주식회사 무선 통신 시스템에서 물리 상향링크 공유 채널 송수신 방법 및 장치
WO2020222292A1 (en) * 2019-05-02 2020-11-05 Sharp Kabushiki Kaisha User equipments, base stations and methods for uplink transmission in interrupted transmission indication
US11917689B2 (en) * 2020-07-07 2024-02-27 Qualcomm Incorporated Redundancy version (RV) determination for message repetition
US11996941B2 (en) * 2020-09-11 2024-05-28 Qualcomm Incorporated Techniques for providing dedicated demodulation reference signals for transmission repetitions
CN112311517A (zh) * 2020-10-16 2021-02-02 紫光展锐(重庆)科技有限公司 上行信息发送方法及相关产品
KR102603464B1 (ko) * 2021-04-05 2023-11-17 엘지전자 주식회사 무선 통신 시스템에서 신호 송수신 방법 및 장치

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108282274A (zh) * 2017-01-06 2018-07-13 中兴通讯股份有限公司 数据传输方法及装置，终端和基站
CN108631960A (zh) * 2017-03-24 2018-10-09 华为技术有限公司 一种数据传输方法和相关设备

Family Cites Families (22)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103974422A (zh) * 2013-02-05 2014-08-06 电信科学技术研究院 一种通信处理方法及装置
CN105850057B (zh) * 2013-12-03 2019-04-09 Lg 电子株式会社 在支持机器型通信的无线接入系统中发送上行链路的方法和设备
CN106658742B (zh) * 2015-11-03 2020-07-03 中兴通讯股份有限公司 数据调度及传输的方法、装置及系统
US11177853B2 (en) * 2015-11-13 2021-11-16 Xi'an Zhongxing New Software Co., Ltd. Information transmission method and apparatus
US10070425B2 (en) * 2016-02-26 2018-09-04 Telefonaktiebolaget Lm Ericsson (Publ) Multi-subframe grant with scheduling of both data and control channels
CN107295676B (zh) * 2016-03-31 2019-07-23 中兴通讯股份有限公司 数据传输方法及装置
CN107801246B (zh) * 2016-09-06 2019-12-17 北京佰才邦技术有限公司 一种上行控制信息的传输方法、装置及用户终端
CN108282879B (zh) * 2017-01-06 2022-11-18 中兴通讯股份有限公司 数据传输方法及装置
JP6705938B2 (ja) 2017-03-16 2020-06-03 エルジー エレクトロニクス インコーポレイティド 無線通信システムにおける端末及び基地局の動作方法並びにそれをサポートする装置
US10925082B2 (en) * 2017-03-24 2021-02-16 Apple Inc. Sub-PRB resource allocation for pusch in even further enhanced MTC
DE112018000167T5 (de) * 2017-06-12 2019-08-01 Intel IP Corporation KANALDESIGN FÜR EINE VERBESSERTE MACHINE TYPE COMMUNICATION IN EINEM UNLIZENZIERTEN SPEKTRUMSYSTEM (eMTC-U)
US11032844B2 (en) * 2017-06-22 2021-06-08 Qualcomm Incorporated Physical shared channel transmission to acknowledgement delay optimization
AU2018315141B2 (en) * 2017-08-11 2021-10-21 Telefonaktiebolaget Lm Ericsson (Publ) Autonomous transmission of uplink control information
EP3682576A4 (en) * 2017-09-11 2021-04-28 Nokia Technologies Oy UPRIGHT LINK TRANSMISSION PROCESS AND APPARATUS
WO2019134098A1 (zh) * 2018-01-04 2019-07-11 北京小米移动软件有限公司 数据传输方法、装置及用户设备
CA3029227A1 (en) * 2018-01-04 2019-07-04 Comcast Cable Communications, Llc Methods and systems for information reporting
CN110034893A (zh) * 2018-01-12 2019-07-19 维沃移动通信有限公司 一种uci发送方法和移动终端
WO2019138016A1 (en) * 2018-01-12 2019-07-18 Telefonaktiebolaget Lm Ericsson (Publ) Channel state information reporting without uplink shared channel
WO2019213907A1 (zh) * 2018-05-10 2019-11-14 北京小米移动软件有限公司 信息复用传输方法及装置、信息接收方法及装置
CN114245464A (zh) * 2018-12-26 2022-03-25 北京小米移动软件有限公司 时域资源分配方法、数据发送方法、基站及终端
CN111586854B (zh) * 2019-02-15 2024-03-08 大唐移动通信设备有限公司 物理上行共享信道的传输方法、终端及网络设备
CN111585722B (zh) * 2019-02-15 2022-05-24 大唐移动通信设备有限公司 物理上行共享信道的传输方法、终端及网络设备

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108282274A (zh) * 2017-01-06 2018-07-13 中兴通讯股份有限公司 数据传输方法及装置，终端和基站
CN108631960A (zh) * 2017-03-24 2018-10-09 华为技术有限公司 一种数据传输方法和相关设备

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
See also references of EP3927057A4 *
ZTE: "Enhancement for UL Grant-free Transmissions", 3GPP TSG RAN WG1 MEETING#94BIS, R1-1810347, 29 September 2018 (2018-09-29), pages 1 - 6, XP051517757, DOI: 20200327163047X *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220039140A1 (en) * 2020-07-28 2022-02-03 Comcast Cable Communications, Llc Control Channel Repetition Using Multiple Coresets

Also Published As

Publication number Publication date
US20220150924A1 (en) 2022-05-12
EP3927057A1 (en) 2021-12-22
EP3927057A4 (en) 2022-03-23
US12089206B2 (en) 2024-09-10
CN111586854A (zh) 2020-08-25
CN111586854B (zh) 2024-03-08
KR20210119521A (ko) 2021-10-05

Similar Documents

Publication Publication Date Title
WO2020164568A1 (zh) 物理上行共享信道的传输方法、终端及网络设备
WO2020164570A1 (zh) 物理上行共享信道的传输方法、终端及网络设备
US12101190B2 (en) Transmission priority determination method and apparatus, and computer readable storage medium
WO2020143839A1 (zh) 上行控制信息复用的方法和装置
WO2019144833A1 (zh) Dai的指示方法、用户终端和网络侧设备
US12009935B2 (en) Feedback information sending method and device
WO2020143428A1 (zh) 传输上行信息的方法和通信装置
US11388702B2 (en) Resource determining method, apparatus, network element, and system
WO2020192609A1 (zh) 资源的确定、接收方法、装置、电子装置及存储介质
US11057923B2 (en) Transmission method, terminal device and base station
CN111510260B (zh) Harq编号确定方法、网络设备、终端和计算机存储介质
WO2021027627A1 (zh) 上行控制信息uci的处理方法、终端及基站
WO2020164347A1 (zh) 一种传输方法和设备
TW201931798A (zh) 通道狀態資訊傳輸方法、通訊設備及裝置
JP7408833B2 (ja) アップリンクチャネルの多重化方法及び装置、並びに端末
WO2019114504A1 (zh) 传输方法、终端及基站
WO2018170745A1 (zh) 一种基于载波聚合的解调方法及装置
WO2021233146A1 (zh) 一种数据调度方法及装置
US20210410006A1 (en) Method for determining transport block size and communications apparatus
US20220103308A1 (en) Feedback information processing method and related device
WO2017015855A1 (zh) 一种数据通信的方法及装置

Legal Events

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

Ref document number: 20755126

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 20217028011

Country of ref document: KR

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2020755126

Country of ref document: EP

Effective date: 20210915