CN114071571A

CN114071571A - Transmission method, device and storage medium for uplink channel conflict

Info

Publication number: CN114071571A
Application number: CN202010791105.9A
Authority: CN
Inventors: 高雪娟; 邢艳萍
Original assignee: Datang Mobile Communications Equipment Co Ltd
Current assignee: Datang Mobile Communications Equipment Co Ltd
Priority date: 2020-08-07
Filing date: 2020-08-07
Publication date: 2022-02-18

Abstract

The embodiment of the application provides a method, a device and a storage medium for transmitting conflict between uplink channels, wherein the method comprises the following steps: when an uplink channel carrying UCI is overlapped with a first type PUSCH in a time domain, one channel is selected autonomously for transmission, or one channel is selected for transmission according to a preset rule, wherein the first type PUSCH is a PUSCH in an RA process. According to the transmission method, the device and the storage medium for the conflict between the uplink channels, the UE autonomously selects one channel or selects one channel according to a specific rule for transmission, and the problem that no corresponding transmission scheme is defined is solved; multiplexing transmission of UCI on a PUSCH in the RA process is avoided, and correct receiving of the PUSCH in the RA process by a base station is ensured; and making reasonable channel selection according to the importance degree of the UCI type carried by the uplink channel, and reducing the failure probability of random access.

Description

Transmission method, device and storage medium for uplink channel conflict

Technical Field

The present application relates to the field of communications technologies, and in particular, to a method, an apparatus, and a storage medium for transmitting a collision between uplink channels.

Background

In a Random Access (RA) procedure, when an Uplink is originally in a synchronous state, a terminal may have a Physical Uplink Control CHannel (PUCCH) transmission or a Physical Uplink Shared CHannel (PUSCH) transmission carrying Uplink Control Information (UCI) on a cell performing the RA procedure, and the PUCCH and the PUSCH carrying the UCI may have a collision with the PUSCH in the RA procedure.

In the prior art, no transmission scheme is defined for this scenario. If the UCI on the PUCCH is transferred to the PUSCH in the RA procedure for transmission, the base station cannot expect what type of UCI is carried on the PUSCH and what number of UCI bits is carried when it does not know which UE sends the PUSCH in the RA procedure, and therefore, the PUSCH in the RA procedure cannot be correctly received, resulting in a failure of the RA procedure. When a collision occurs between uplink channels, how to transmit information is an urgent technical problem to be solved.

Disclosure of Invention

Embodiments of the present application provide a method, an apparatus, and a storage medium for transmitting an uplink inter-channel conflict, so as to solve the technical problem in the prior art that an RA procedure fails when an uplink inter-channel conflict occurs.

In a first aspect, an embodiment of the present application provides a method for transmitting a collision between uplink channels, including:

when an uplink channel carrying uplink control information UCI and a first type physical uplink shared channel PUSCH are overlapped in a time domain, a terminal UE autonomously selects one channel for transmission or selects one channel for transmission according to a preset rule, wherein the first type PUSCH is a PUSCH in a random access process.

Optionally, according to the transmission method for collision between uplink channels in an embodiment of the present application, when there is overlap between an uplink channel carrying uplink control information UCI and a first type of physical uplink shared channel PUSCH in a time domain, a UE autonomously selects one of the channels for transmission, which specifically includes:

when a Physical Uplink Control Channel (PUCCH) carrying UCI is overlapped with a first type PUSCH only in a time domain, the UE autonomously selects one channel and transmits the channel; and/or the presence of a gas in the gas,

when the PUSCHs carrying the UCI and the PUSCHs of the first type have time domain overlapping on the same carrier wave, the UE autonomously selects one of the channels for transmission.

Optionally, according to the transmission method for collision between uplink channels in an embodiment of the present application, when there is an overlap between an uplink channel carrying uplink control information UCI and a first type of physical uplink shared channel PUSCH in a time domain, one of the channels is selected according to a predetermined rule for transmission, which specifically includes one of the following rules:

rule 1: when the PUCCH carrying the UCI is only overlapped with the first PUSCH on the time domain, one channel is selected to be transmitted according to the type of the UCI carried by the PUCCH;

rule 2: when the PUCCH bearing UCI is only overlapped with the first PUSCH in the time domain, the first PUSCH is fixedly selected for transmission, and the PUCCH is discarded;

rule 3: when the PUCCH bearing UCI is only overlapped with the first PUSCH on the time domain, the PUCCH is fixedly selected for transmission, and the first PUSCH is discarded;

rule 4: when the PUCCH carrying the UCI only overlaps with the first type PUSCH in the time domain, one channel is selected for transmission according to whether a transport block TB is generated on the first type PUSCH.

Optionally, according to an embodiment of the present application, in the method for transmitting collision between uplink channels, rule 1 further includes one of the following:

if the UCI carried on the PUCCH at least comprises hybrid automatic repeat request acknowledgement (HARQ-ACK) and/or Scheduling Request (SR), the UE autonomously selects one channel for transmission; if UCI carried on the PUCCH is Channel State Information (CSI), selecting a first type of PUSCH and discarding the PUCCH; alternatively, the first and second electrodes may be,

if the UCI carried on the PUCCH at least comprises HARQ-ACK and/or SR, selecting the PUCCH and discarding the first type PUSCH; if UCI carried on the PUCCH is CSI, selecting a first type PUSCH, and discarding the PUCCH; alternatively, the first and second electrodes may be,

if the UCI carried on the PUCCH at least comprises HARQ-ACK, the UE autonomously selects one of the channels for transmission; if the UCI carried on the PUCCH is CSI and/or SR, selecting a first type PUSCH and discarding the PUCCH; alternatively, the first and second electrodes may be,

if the UCI carried on the PUCCH at least comprises HARQ-ACK, selecting the PUCCH and discarding the first type PUSCH; and if the UCI carried on the PUCCH is CSI and/or SR, selecting a first type PUSCH and discarding the PUCCH.

Optionally, according to an embodiment of the present application, in the method for transmitting collision between uplink channels, the rule 4 further includes:

when TB is generated on the first type PUSCH, one of the rules 1-3 is reused to select a channel for transmission; otherwise, selecting PUCCH and discarding the first type PUSCH.

Optionally, according to the transmission method for collision between uplink channels in an embodiment of the present application, when there is an overlap between an uplink channel carrying uplink control information UCI and a first type of physical uplink shared channel PUSCH in a time domain, selecting one of the channels according to a predetermined rule for transmission specifically includes:

when the PUCCH carrying the UCI is overlapped with a plurality of PUSCHs including a first class PUSCH in a time domain, transferring the UCI on the PUCCH to a target PUSCH for transmission, and discarding the PUCCH; the target PUSCH is one of the PUSCHs except the first type PUSCH.

Optionally, the method for transmitting collision between uplink channels according to an embodiment of the present application further includes: and the first type PUSCH and the target PUSCH are respectively transmitted on different carriers or are respectively transmitted on symbol sets with non-overlapping time domains on the same carrier.

rule 5: when the PUSCH carrying the UCI and the first class PUSCH have time domain overlapping on the same carrier wave, one channel is selected to transmit according to the type of the UCI carried by the PUSCH;

rule 6: when the time domain of the PUSCH bearing the UCI is overlapped with the time domain of the first type PUSCH on the same carrier wave, the first type PUSCH is selected for transmission, and the PUSCH bearing the UCI is not sent;

rule 7: when the time domain overlapping exists between the PUSCH bearing the UCI and the first-class PUSCH on the same carrier wave, the PUSCH bearing the UCI is selected for transmission, and the first-class PUSCH is not sent;

rule 8: when the PUSCH carrying the UCI and the first class PUSCH have time domain overlapping on the same carrier wave, one of the channels is selected for transmission according to whether the PUSCH carrying the UCI is scheduled to contain TB transmission.

Optionally, according to an embodiment of the present application, in the method for transmitting collision between uplink channels, the rule 5 further includes one of the following:

if UCI carried on the PUSCH at least comprises aperiodic channel state information A-CSI, the UE autonomously selects one channel for transmission; if UCI carried on the PUSCH is CSI, selecting a first type PUSCH, and discarding the PUCCH; alternatively, the first and second electrodes may be,

if the UCI carried on the PUSCH at least comprises A-CSI, selecting the PUSCH carrying the UCI, and discarding the first type PUSCH; if UCI carried on the PUSCH is semi-persistent scheduling channel state information SP-CSI, selecting a first class PUSCH and discarding the PUCCH; alternatively, the first and second electrodes may be,

if UCI carried on the PUSCH at least comprises A-CSI and the PUSCH comprises TB transmission, the UE autonomously selects one of the channels for transmission; if UCI carried on the PUSCH is SP-CSI or does not contain TB transmission, selecting a first type PUSCH and discarding the PUCCH; alternatively, the first and second electrodes may be,

if the UCI carried on the PUSCH at least comprises A-CSI and the PUSCH comprises TB transmission, selecting the PUSCH carrying the UCI and discarding the first type PUSCH; if UCI carried on the PUSCH is SP-CSI or does not contain TB transmission, selecting a first type PUSCH and discarding the PUCCH; alternatively, the first and second electrodes may be,

if UCI carried on the PUSCH at least comprises A-CSI and the PUSCH does not contain TB transmission, the UE autonomously selects one channel for transmission; if UCI carried on the PUSCH is SP-CSI or contains TB transmission, selecting a first type PUSCH and discarding the PUCCH; alternatively, the first and second electrodes may be,

if the UCI carried on the PUSCH at least comprises A-CSI and the PUSCH does not contain TB transmission, selecting the PUSCH carrying the UCI and discarding the first type PUSCH; and if the UCI carried on the PUSCH is SP-CSI or contains TB transmission, selecting the first type PUSCH and discarding the PUCCH.

Optionally, according to an embodiment of the present application, in the method for transmitting collision between uplink channels, the rule 8 further includes:

and if the PUSCH carrying the UCI is a PUSCH scheduled to contain TB transmission, the UE selects the PUSCH carrying the UCI and the PUSCH with the TB generated in the first type PUSCH for transmission, and discards the other PUSCH.

Optionally, according to the transmission method for collision between uplink channels in an embodiment of the present application, the first type of PUSCH includes a PUSCH scheduled by a random access response grant RAR grant, a retransmission of an Msg3 PUSCH, a PUSCH in a second type of random access, and a retransmission of a PUSCH in a second type of random access; and/or the random access procedure is a contention-based random access procedure.

In a second aspect, an embodiment of the present application further provides a method for transmitting a collision between uplink channels, including:

when an uplink channel carrying uplink control information UCI and a first type physical uplink shared channel PUSCH are overlapped in a time domain, determining that a terminal UE autonomously selects one channel for transmission, or determining that the UE selects one channel for transmission according to a preset rule, wherein the first type PUSCH is a PUSCH in a random access process.

Optionally, according to the transmission method for collision between uplink channels in an embodiment of the present application, when there is overlap between an uplink channel carrying uplink control information UCI and a first type of physical uplink shared channel PUSCH in a time domain, determining that the UE autonomously selects one of the channels for transmission specifically includes:

when a Physical Uplink Control Channel (PUCCH) carrying UCI is overlapped with a first type PUSCH only in a time domain, determining that the UE autonomously selects one channel and transmits the channel; and/or the presence of a gas in the gas,

and when the PUSCHs carrying the UCI and the first class PUSCHs have time domain overlapping on the same carrier wave, determining that the UE autonomously selects one of the channels for transmission.

Optionally, according to the transmission method for collision between uplink channels in an embodiment of the present application, when there is an overlap between an uplink channel carrying uplink control information UCI and a first type of physical uplink shared channel PUSCH in a time domain, it is determined that the UE selects one of the channels for transmission according to a predetermined rule, and specifically includes one of the following rules:

rule 1: when the PUCCH bearing the UCI is only overlapped with the first PUSCH on the time domain, determining that the UE selects one channel for transmission according to the type of the UCI borne by the PUCCH;

rule 2: when the PUCCH bearing UCI only overlaps with the first-class PUSCH in the time domain, determining that the UE fixedly selects the first-class PUSCH for transmission, and discarding the PUCCH;

rule 3: when the PUCCH bearing UCI only overlaps with the first type PUSCH in the time domain, determining that the UE fixedly selects the PUCCH for transmission, and discarding the first type PUSCH;

rule 4: when the PUCCH carrying the UCI only overlaps with the first type PUSCH in the time domain, the UE is determined to select one channel for transmission according to whether a transport block TB is generated on the first type PUSCH.

if the UCI carried on the PUCCH at least comprises hybrid automatic repeat request acknowledgement (HARQ-ACK) and/or Scheduling Request (SR), determining that the UE autonomously selects one channel for transmission; if UCI carried on the PUCCH is Channel State Information (CSI), determining that the UE selects a first type PUSCH for transmission, and discarding the PUCCH; alternatively, the first and second electrodes may be,

if the UCI carried on the PUCCH at least comprises HARQ-ACK and/or SR, determining that the UE selects the PUCCH for receiving, and discarding the first type PUSCH; if the UCI carried on the PUCCH is CSI, determining that the UE selects a first type PUSCH for transmission, and discarding the PUCCH; alternatively, the first and second electrodes may be,

if the UCI carried on the PUCCH at least comprises HARQ-ACK, determining that the UE autonomously selects one channel for transmission; if UCI carried on the PUCCH is CSI and/or SR, determining that the UE selects a first type PUSCH, and discarding the PUCCH; alternatively, the first and second electrodes may be,

if the UCI carried on the PUCCH at least comprises HARQ-ACK, determining that the UE selects the PUCCH, and discarding the first type PUSCH; and if the UCI carried on the PUCCH is CSI and/or SR, determining that the UE selects the PUSCH of the first type, and discarding the PUCCH.

when TB is generated on the first type PUSCH, determining that the UE reuses one of the rules 1-3 to select a channel for transmission; otherwise, determining that the UE selects the PUCCH and discarding the first type PUSCH.

Optionally, according to the transmission method for collision between uplink channels in an embodiment of the present application, when there is an overlap between an uplink channel carrying uplink control information UCI and a first type of physical uplink shared channel PUSCH in a time domain, determining that the UE selects one of the channels for transmission according to a predetermined rule, specifically includes:

when the PUCCH carrying the UCI is overlapped with a plurality of PUSCHs including a first class of PUSCHs in a time domain, determining that the UE transfers the UCI on the PUCCH to a target PUSCH for transmission, and discarding the PUCCH; the target PUSCH is one of the PUSCHs except the first type PUSCH.

rule 5: when the PUSCH carrying the UCI and the first class PUSCH have time domain overlapping on the same carrier wave, determining that the UE selects one channel for transmission according to the type of the UCI carried by the PUSCH;

rule 6: when the time domain overlapping exists between the PUSCH bearing the UCI and the first-class PUSCH on the same carrier wave, determining that the UE selects the first-class PUSCH for transmission and does not send the PUSCH bearing the UCI;

rule 7: when the time domain overlapping exists between the PUSCH bearing the UCI and the first-class PUSCH on the same carrier wave, determining that the UE selects the PUSCH bearing the UCI for transmission and does not send the first-class PUSCH;

rule 8: when the PUSCH bearing the UCI and the first class PUSCH have time domain overlapping on the same carrier wave, the UE is determined to select one channel to transmit according to whether the PUSCH bearing the UCI is scheduled to contain TB transmission.

if UCI carried on the PUSCH at least comprises aperiodic channel state information A-CSI, determining that the UE autonomously selects one channel for transmission; if UCI carried on the PUSCH is CSI, determining that the UE selects the first type PUSCH, and discarding the PUCCH; alternatively, the first and second electrodes may be,

if the UCI carried on the PUSCH at least comprises A-CSI, determining that the UE selects the PUSCH carrying the UCI, and discarding the first type PUSCH; if UCI carried on the PUSCH is semi-persistent scheduling channel state information SP-CSI, determining that the UCI selects a first type PUSCH, and discarding the PUCCH; alternatively, the first and second electrodes may be,

if UCI carried on the PUSCH at least comprises A-CSI and the PUSCH comprises TB transmission, determining that the UE autonomously selects one channel for transmission; if UCI carried on the PUSCH is SP-CSI or does not contain TB transmission, determining that the UE selects the first type PUSCH, and discarding the PUCCH; alternatively, the first and second electrodes may be,

if the UCI carried on the PUSCH at least comprises A-CSI and the PUSCH contains TB transmission, determining that the UE selects the PUSCH carrying the UCI, and discarding the first type PUSCH; if UCI carried on the PUSCH is SP-CSI or does not contain TB transmission, determining that the UE selects the first type PUSCH, and discarding the PUCCH; alternatively, the first and second electrodes may be,

if the UCI carried on the PUSCH at least comprises A-CSI and the PUSCH does not contain TB transmission, determining that the UE autonomously selects one channel for transmission; if UCI carried on the PUSCH is SP-CSI or contains TB transmission, determining that the UE selects the first type PUSCH, and discarding the PUCCH; alternatively, the first and second electrodes may be,

if the UCI carried on the PUSCH at least comprises A-CSI and the PUSCH does not contain TB transmission, determining that the UE selects the PUSCH carrying the UCI, and discarding the first type PUSCH; and if the UCI carried on the PUSCH is SP-CSI or contains TB transmission, determining that the UE selects the PUSCH of the first type, and discarding the PUCCH.

and if the PUSCH carrying the UCI is a PUSCH scheduled to contain TB transmission, determining that the UE selects the PUSCH carrying the UCI and the PUSCH with the TB generated in the first type PUSCH for transmission, and discarding the other PUSCH.

Optionally, according to the transmission method for collision between uplink channels in an embodiment of the present application, the first type of PUSCH includes a PUSCH scheduled by a RAR grant, a retransmission of an Msg3 PUSCH, a PUSCH in a second type of random access, and a retransmission of a PUSCH in a second type of random access; and/or the random access procedure is a contention-based random access procedure.

Optionally, according to the transmission method for collision between uplink channels in an embodiment of the present application, when there is overlap between an uplink channel carrying uplink control information UCI and a first type of physical uplink shared channel PUSCH in a time domain, it is determined that the UE autonomously selects one of the channels for transmission, or it is determined that the UE selects one of the channels for transmission according to a predetermined rule, which specifically includes:

and the base station blindly detects an uplink channel carrying UCI and a first class PUSCH, wherein when the first class PUSCH is detected, the receiving is carried out according to a mode that no UCI is transmitted on the first class PUSCH.

In a third aspect, an embodiment of the present application further provides a terminal, including a memory, a transceiver, and a processor;

a memory for storing a computer program; a transceiver for transceiving data under control of the processor; a processor for reading the computer program in the memory and performing the following operations:

Optionally, according to the terminal in an embodiment of the present application, when an uplink channel carrying uplink control information UCI overlaps with a first type of physical uplink shared channel PUSCH in a time domain, the UE autonomously selects one of the channels for transmission, which specifically includes:

Optionally, according to the terminal in an embodiment of the present application, when there is an overlap between an uplink channel carrying uplink control information UCI and a first type of physical uplink shared channel PUSCH in a time domain, one of the channels is selected according to a predetermined rule for transmission, which specifically includes one of the following rules:

Optionally, according to the terminal in an embodiment of the present application, the rule 1 further includes one of the following:

Optionally, according to the terminal in an embodiment of the present application, the rule 4 further includes:

Optionally, according to the terminal in an embodiment of the present application, when there is an overlap between an uplink channel carrying uplink control information UCI and a first type of physical uplink shared channel PUSCH in a time domain, selecting one of the channels for transmission according to a predetermined rule specifically includes:

Optionally, the terminal according to an embodiment of the present application further includes: and the first type PUSCH and the target PUSCH are respectively transmitted on different carriers or are respectively transmitted on symbol sets with non-overlapping time domains on the same carrier.

Optionally, according to the terminal in an embodiment of the present application, the rule 5 further includes one of the following:

Optionally, according to an embodiment of the terminal of the present application, the rule 8 further includes:

Optionally, according to the terminal in an embodiment of the present application, the first type of PUSCH includes a PUSCH scheduled by a random access response grant RAR grant, a retransmission of an Msg3 PUSCH, a PUSCH in a second type of random access, and a retransmission of a PUSCH in a second type of random access; and/or the random access procedure is a contention-based random access procedure.

In a fourth aspect, an embodiment of the present application further provides a base station, including a memory, a transceiver, and a processor;

Optionally, according to the base station of an embodiment of the present application, when there is an overlap between an uplink channel carrying uplink control information UCI and a first type of physical uplink shared channel PUSCH in a time domain, determining that the UE autonomously selects one of channels for transmission specifically includes:

Optionally, according to the base station in an embodiment of the present application, when there is an overlap between an uplink channel carrying uplink control information UCI and a first type of physical uplink shared channel PUSCH in a time domain, determining that the UE selects one of the channels for transmission according to a predetermined rule, specifically includes one of the following rules:

Optionally, according to the base station of an embodiment of the present application, the rule 1 further includes one of the following:

Optionally, according to the base station in an embodiment of the present application, the rule 4 further includes:

Optionally, according to the base station in an embodiment of the present application, when there is an overlap between an uplink channel carrying uplink control information UCI and a first type of physical uplink shared channel PUSCH in a time domain, determining that the UE selects one of the channels for transmission according to a predetermined rule includes:

Optionally, the base station according to an embodiment of the present application further includes: and the first type PUSCH and the target PUSCH are respectively transmitted on different carriers or are respectively transmitted on symbol sets with non-overlapping time domains on the same carrier.

Optionally, according to the base station of an embodiment of the present application, the rule 5 further includes one of the following:

Optionally, according to the base station in an embodiment of the present application, the rule 8 further includes:

Optionally, according to the base station in an embodiment of the present application, the first type of PUSCH includes a PUSCH scheduled by a RAR grant, a retransmission of an Msg3 PUSCH, a PUSCH in a second type of random access, and a retransmission of a PUSCH in a second type of random access; and/or the random access procedure is a contention-based random access procedure.

Optionally, according to the base station in an embodiment of the present application, when an uplink channel carrying uplink control information UCI overlaps with a first type of physical uplink shared channel PUSCH in a time domain, determining that the UE autonomously selects one of channels for transmission, or determining that the UE selects one of channels for transmission according to a predetermined rule, specifically includes:

In a fifth aspect, an embodiment of the present application further provides a device for transmitting a collision between uplink channels, where the device includes:

the transmission module is configured to autonomously select one of the channels for transmission or select one of the channels for transmission according to a predetermined rule when an uplink channel carrying uplink control information UCI overlaps with a first type of physical uplink shared channel PUSCH in a time domain, where the first type of PUSCH is a PUSCH in a random access process.

In a sixth aspect, an embodiment of the present application further provides a device for transmitting a collision between uplink channels, where the device includes:

the determining module is configured to determine that the terminal UE autonomously selects one of the channels for transmission when an uplink channel carrying uplink control information UCI overlaps with a first type of physical uplink shared channel PUSCH in a time domain, or determine that the UE selects one of the channels for transmission according to a predetermined rule, where the first type of PUSCH is a PUSCH in a random access process.

In a seventh aspect, an embodiment of the present application further provides a processor-readable storage medium, where the processor-readable storage medium stores a computer program, where the computer program is configured to enable the processor to execute the steps of the method for transmitting an uplink inter-channel collision according to the first aspect or the second aspect.

According to the transmission method, the device and the storage medium for the conflict between the uplink channels, the UE autonomously selects one channel or selects one channel according to a specific rule for transmission, and the problem that no corresponding transmission scheme is defined is solved; multiplexing transmission of UCI on a PUSCH in the RA process is avoided, and correct receiving of the PUSCH in the RA process by a base station is ensured; and making reasonable channel selection according to the importance degree of the UCI type carried by the uplink channel, and reducing the failure probability of random access.

Drawings

In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly described below, and it is obvious that the drawings in the following description are some embodiments of the present application, and other drawings can be obtained by those skilled in the art without creative efforts.

FIG. 1 is a schematic diagram of a first type of RA procedure;

FIG. 2 is a schematic diagram of a second type of RA procedure;

fig. 3 is a schematic diagram of a transmission method for collision between uplink channels according to an embodiment of the present application;

fig. 4 is a second schematic diagram of a transmission method for collision between uplink channels according to an embodiment of the present application;

fig. 5 is one of schematic diagrams of collision between uplink channels according to an embodiment of the present application;

fig. 6 is a second schematic diagram of collision between uplink channels according to an embodiment of the present application;

fig. 7 is a third schematic diagram illustrating an inter-uplink channel collision according to an embodiment of the present application;

fig. 8 is a schematic structural diagram of a terminal according to an embodiment of the present application;

fig. 9 is a schematic structural diagram of a base station according to an embodiment of the present application;

fig. 10 is a schematic diagram of an apparatus for transmitting uplink inter-channel collision according to an embodiment of the present application;

fig. 11 is a second schematic diagram of a transmission apparatus for collision between uplink channels according to an embodiment of the present application.

Detailed Description

In a New wireless communication system (i.e. 5G NR, 5Generation New RAT), a Terminal (Terminal, also called User Equipment, UE, User Equipment) may perform Random Access for multiple reasons, when a contention-based Random Access is used, a Physical Uplink Shared CHannel (PUSCH) transmission in a Random Access process may collide with other Uplink channels carrying Uplink Control Information (UCI) (e.g. overlap exists in a time domain), and when a collision occurs between the PUSCH in the Random Access process and the Uplink CHannel carrying the UCI, there is no clear method for how to perform transmission.

1) Random access procedure in 5G NR

When the UE is out of synchronization in uplink, or uplink data arrives but no Scheduling Request (SR) is configured, or the Scheduling Request reaches the maximum transmission times, or cell handover, or initial access system (Radio Resource Control (RRC) connection establishment or reestablishment), the terminal needs to perform RA, and implement uplink synchronization, or perform a Resource Request or access system for uplink data, etc. through an RA process. The RA process is divided into two categories: a first Type (Type1) of RA procedure and a second Type (Type2) of RA procedure.

Fig. 1 is a schematic diagram of a first type of RA procedure, which is a 4-step RA, as shown in fig. 1. The Message (Msg, Message)1 is a process of sending a preamble sequence by the terminal, and specifically is sent through a Physical Random Access CHannel (PRACH), and the base station may calculate a Timing Advance (TA) adjustment value of the terminal according to the received preamble; msg2 is a process of sending a Random Access Response (RAR) to a terminal by a base station, and specifically is to schedule a Physical Downlink Shared CHannel (PDSCH) carrying the RAR for transmission through a Physical Downlink Control CHannel (PDCCH) scrambled by a Random Access-Radio Network Temporary Identifier (RA-RNTI), wherein the RAR carries at least an uplink scheduling grant (UL grant) and a TA adjustment value for scheduling Msg3 for transmission, and the UL grant is carried in the RAR and may also be referred to as an RAR UL grant; msg3 is a process of performing PUSCH transmission based on RAR UL grant scheduling, where the PUSCH may carry related information for different RA purposes to help a base station to obtain UE information and perform contention resolution, and when a terminal has a Cell-Radio Network Temporary Identifier (C-RNTI), the PUSCH may carry the C-RNTI to indicate which terminal is performing PUSCH transmission; msg4 is a contention resolution procedure, i.e. scheduling one PDSCH for transmission to the terminal through PDCCH to help the terminal identify whether its RA procedure was successful.

Fig. 2 is a schematic diagram of a second type of RA procedure, which is a 2-step RA procedure as shown in fig. 2. The Msg A simultaneously comprises PRACH and Physical Uplink Shared CHannel (PUSCH) transmission, and when a terminal has a Cell-Radio Network Temporary Identifier (C-RNTI), the PUSCH can carry the C-RNTI to indicate which terminal PUSCH transmission is; msg B is then the combined step of RAR and contention resolution. The second class of RA compresses multiple steps in the RA process relative to the first class of RA, enabling a faster RA process. A typical application scenario of the second RA is for small data packet (small data) transmission, which may skip the SR process and directly perform uplink transmission, thereby implementing fast small data packet transmission.

Each RA procedure may be performed in a Contention (CBRA) or non-Contention (CFRA) manner. In the CBRA, that is, in the first RA and the second RA, the terminal may randomly select a preamble sequence when selecting the preamble sequence, and may also randomly select a PRACH resource on the PRACH resource configured by the system, so that it may occur that a plurality of terminals select the same preamble sequence and/or the same PRACH resource for RA, and at this time, when the base station receives Msg1 or Msg a, it may not be determined which UE or UEs transmit the preamble, and therefore, before the Msg3 in the first RA procedure and the PUSCH in the second RA Msg a procedure, the base station may not know which UE performs transmission, and contention resolution needs to be performed through the subsequent Msg 4. The CFRA is implemented by configuring a specific preamble sequence and a specific PRACH resource of the terminal by the base station, so that when the base station receives the preamble, it can identify which UE transmits the preamble, thereby identifying which UE the PUSCH comes from.

2) UCI transmission in 5G NR

The Uplink Control Information (UCI) includes Hybrid Automatic Repeat Request acknowledgement (HARQ-ACK), Channel State Information (CSI), Scheduling Request (SR), and other Information. Wherein, HARQ-ACK is a general term of positive Acknowledgement (ACK) and Negative Acknowledgement (NACK), and is used for feeding back a PDSCH or a PDCCH (also called SPS PDSCH release) indicating Semi-Persistent Scheduling (SPS) resource release, and informing a base station whether a PDSCH or the PDCCH indicating SPS PDSCH release is correctly received; the CSI is used for feeding back the quality of a downlink channel, so as to help a base station to perform downlink scheduling better, for example, selecting and configuring appropriate RB resources according to a Modulation and Coding Scheme (MCS) of the CSI; the SR is used to request a base station for transmission resources of a Physical Uplink Shared CHannel (PUSCH) carrying an Uplink service when the terminal has the Uplink service to transmit.

The HARQ-ACK can be transmitted on PUCCH resources pre-configured to SPS by a higher layer signaling for HARQ-ACK feedback of SPS PDSCH, namely semi-static HARQ-ACK feedback, the time slot or the sub-time slot in which the HARQ-ACK feedback is transmitted is relatively fixed, and the HARQ-ACK feedback is determined according to the transmission position of the SPS PDSCH and a predetermined feedback timing (namely K1 which is used for indicating the interval between the time slot or the sub-time slot in which the PDSCH or PDCCH for indicating the SPS resource release is transmitted and the time slot or the sub-time slot in which the HARQ-ACK is transmitted, and the K1 can be the only one K1 value notified in the PDCCH for activating the SPS PDSCH or pre-configured by RRC (namely, if a plurality of K1 values are pre-configured by RRC, a feedback timing indication field is contained in the PDCCH, and one K1 value is notified in the PDCCH, and if only one K1 value is configured by the RRC, the feedback timing indication field is not contained in the PDCCH, directly using this RRC configured value of K1). HARQ-ACK can also be feedback for PDSCH scheduled by PDCCH or PDCCH indicating SPS resource release, in which case PUCCH resource carrying HARQ-ACK is determined by PUCCH resource indication field in PDCCH, and feedback timing can also be signaled by feedback timing indication field in PDCCH (of course, it can be only one RRC configured K1 value), PUCCH transmission has the property of dynamic transmission, i.e. PUCCH carrying HARQ-ACK can occur on any one symbol in any slot or sub-slot depending on base station scheduling.

The CSI includes periodic CSI, Semi-persistent CSI (SP-CSI), and Aperiodic CSI (a-CSI). For periodic CSI and SR, with PUCCH transmission, the PUCCH resource it transmits is pre-configured by higher layer signaling, with the opportunity to transmit being a fixed symbol position in a fixed slot determined from the pre-configured period and offset value of the higher layer signaling. Therefore, the periodic CSI and SR are transmitted on specific symbols that fixedly occur in a specific slot, which is a relatively fixed transmission scheme. For SP-CSI and A-CSI, the SP-CSI is transmitted through a PUSCH, wherein the SP-CSI is activated through a PDCCH (UL grant) which is used for scheduling PUSCH transmission and scrambled by using an SP-CSI-RNTI, after the activation, the SP-CSI is transmitted on a PUSCH resource according to a pre-configured period, the transmission time slot and the symbol position of the PUSCH resource are relatively fixed, and the PUSCH carrying the SP-CSI does not contain any uplink data (UL-SCH or TB transmission) and only contains the SP-CSI; the A-CSI is used for indicating whether transmission is carried out or not through an A-CSI trigger indication domain in a PDCCH for scheduling PUSCH transmission, when the A-CSI is triggered, transmission is carried out on PUSCH resources scheduled by the PDCCH, the PUSCH can simultaneously carry uplink data transmission, or no uplink data transmission exists, and whether the uplink data transmission exists or not can be determined through a specific indication domain in the PDCCH.

When there is a collision between the PUCCH carrying UCI and the PUSCH in the time domain (for example, the PUCCH and the PUSCH are overlapped in the time domain, may be on the same carrier, or may be on different carriers), when a specific condition (for example, a time condition of multiplexing transmission, or the like) is satisfied, the UCI on the PUCCH may be transferred to the PUSCH for transmission, so that the PUCCH is no longer transmitted, and simultaneous transmission of the PUCCH and the PUSCH is avoided. Thus, in some cases, PUSCH may also carry UCI that was originally transmitted on PUCCH.

In the RA procedure, when an Uplink is originally in a synchronous state (for example, RA is only to obtain Uplink resources when there is no SR or when the number of SR transmissions reaches an upper limit or a second type RA directly transmits for small data skipping an SR request procedure), a terminal may have Physical Uplink Control CHannel (PUCCH) transmission or PUSCH transmission carrying UCI on a cell performing the RA procedure, and the PUCCH and the PUSCH carrying UCI may have a collision with a PUSCH in the RA procedure (for example, msg3 PUSCH in the first type RA procedure and MsgA PUSCH in the second type RA procedure). For example, when a PUCCH is configured on a Primary Cell (PCell, Primary Cell) or an SCell or a Secondary Cell (SCell, Secondary Cell) for transmission, an RA procedure for requesting uplink resources or an RA procedure for transmitting a small data packet occurs on the PCell, at this time, because an uplink state is synchronous, an uplink channel such as PUCCH and PUSCH can be normally transmitted, a base station may schedule PDSCH transmission in advance on the premise that which UE cannot expect the RA procedure, and this PDSCH needs to transmit HARQ-ACK through the PUCCH in a time slot for transmitting PUSCH in the RA procedure, or activate PUSCH transmission carrying SP-CSI on the PCell, and the SP-CSI PUSCH needs to be transmitted in a time slot for transmitting PUSCH in the RA procedure according to its period; at this time, symbols of a PUCCH or SP-CSI PUSCH carrying HARQ-ACK may overlap with symbols of a PUSCH in an RA process in the same slot, resulting in collision between uplink channels.

In the prior art, no transmission scheme is defined for this scenario. If the UCI on the PUCCH is transferred to the PUSCH in the RA procedure for transmission, the base station cannot expect what type of UCI is carried on the PUSCH and what number of UCI bits is carried when it does not know which UE sends the PUSCH in the RA procedure, and therefore cannot correctly receive the PUSCH in the RA procedure, resulting in failure of the RA procedure.

In order to make the objects, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.

In order to solve the technical problem, in the embodiment of the present application, when an uplink channel carrying UCI collides with a first type of PUSCH, transmission is performed according to a predetermined rule, where the first type of PUSCH is a PUSCH in a random access process.

Fig. 3 is a schematic diagram of a transmission method for uplink inter-channel collision according to an embodiment of the present disclosure, and as shown in fig. 3, an execution subject of the transmission method for uplink inter-channel collision according to the embodiment of the present disclosure may be a terminal. The method comprises the following steps:

step 301, when an uplink channel carrying uplink control information UCI overlaps with a first type of physical uplink shared channel PUSCH in a time domain, a terminal autonomously selects one of the channels for transmission, or selects one of the channels for transmission according to a predetermined rule, where the first type of PUSCH is a PUSCH in a random access process.

Specifically, when an uplink channel carrying uplink control information UCI overlaps with a first type physical uplink shared channel PUSCH in a time domain, an operation of transferring UCI to the first type PUSCH is not performed, and the terminal autonomously selects one of the channels for transmission or selects one of the channels for transmission according to a predetermined rule.

The uplink channel carrying the UCI may be a PUCCH and/or a PUSCH.

UE autonomous selection means that the UE decides itself, the UE may decide in a fixed manner, e.g., randomly or alternatively or according to the importance of UCI and PUSCH of the first type, and the selection result is not known by the base station in advance.

The first type of PUSCH is a PUSCH in a random access process. For example, the PUSCH scheduled by the RAR UL grant in the first type random access procedure or the MsgA PUSCH in the second type random access procedure may be used.

According to the transmission method for the conflict between the uplink channels, the UE autonomously selects one channel or selects one channel to transmit according to a specific rule, and the problem that no corresponding transmission scheme is defined is solved; multiplexing transmission of UCI on a PUSCH in the RA process is avoided, and correct receiving of the PUSCH in the RA process by a base station is ensured; and making reasonable channel selection according to the importance degree of the UCI type carried by the uplink channel, and reducing the failure probability of random access.

Based on any of the above embodiments, when there is an overlap between an uplink channel carrying uplink control information UCI and a first type of physical uplink shared channel PUSCH in a time domain, the UE autonomously selects one of the channels for transmission, specifically including:

Specifically, in this embodiment of the present application, when an uplink channel carrying uplink control information UCI overlaps with a first type of physical uplink shared channel PUSCH in a time domain, a UE autonomously selects one of the channels for transmission, which specifically includes at least one of the following scenarios:

scene 1: when the PUCCH carrying the UCI is overlapped with the first PUSCH only in the time domain, the UE autonomously selects one channel and transmits the channel; and/or the presence of a gas in the gas,

scene 2: when the PUSCHs carrying the UCI and the PUSCHs of the first type have time domain overlapping on the same carrier wave, the UE autonomously selects one of the channels for transmission.

It should be noted that: when the PUCCH carrying UCI overlaps with the first PUSCH only in the time domain, it means that the PUSCH overlapping with the PUCCH is only the first PUSCH, and there is no other PUSCH overlapping with the PUCCH.

It should be noted that: the PUSCH for carrying the UCI does not include the first-class PUSCH, the first-class PUSCH cannot carry the UCI, and the PUSCH capable of carrying the UCI is other PUSCHs except the first-class PUSCH, such as a PUSCH with PDCCH scheduling, a PUSCH for carrying SP-CSI, a PUSCH for carrying a-CSI, a CG-PUSCH, and the like.

The transmission method for the conflict between the uplink channels provided by the embodiment of the application fully considers the conflict between the uplink channels under two different conditions, improves the reliability and further reduces the failure probability of random access.

Based on any of the above embodiments, when there is an overlap between an uplink channel carrying uplink control information UCI and a first type of physical uplink shared channel PUSCH in a time domain, selecting one of the channels for transmission according to a predetermined rule, specifically including one of the following rules:

Specifically, in the embodiment of the present application, when there is an overlap between a PUCCH carrying UCI and a PUSCH of a first type in a time domain, UCI transfer is not performed, and one of channels is selected for transmission according to a predetermined rule as follows:

According to the transmission method for the conflict between the uplink channels, when the uplink channels conflict, one of the rules is selected to select the uplink channel for transmission, so that the reliability is improved, and the failure probability of random access is further reduced.

Based on any of the above embodiments, the rule 1 further includes one of the following:

Specifically, in the embodiment of the present application, regarding rule 1, one of the following is further included:

if the UCI carried on the PUCCH at least comprises HARQ-ACK and/or SR, the UE autonomously selects one of the channels for transmission; if UCI carried on the PUCCH is CSI, selecting a first type PUSCH, and discarding the PUCCH;

or, if the UCI carried on the PUCCH at least comprises HARQ-ACK and/or SR, selecting the PUCCH and discarding the first type PUSCH; if UCI carried on the PUCCH is CSI, selecting a first type PUSCH, and discarding the PUCCH;

or, if the UCI carried on the PUCCH at least comprises HARQ-ACK, the UE autonomously selects one of the channels for transmission; if the UCI carried on the PUCCH is CSI and/or SR, selecting a first type PUSCH and discarding the PUCCH;

or if the UCI carried on the PUCCH at least comprises HARQ-ACK, selecting the PUCCH and discarding the first type PUSCH; and if the UCI carried on the PUCCH is CSI and/or SR, selecting a first type PUSCH and discarding the PUCCH.

According to the transmission method for the conflict between the uplink channels, when the uplink channel conflict occurs, the selection is carried out according to the UCI type carried by the PUCCH, so that the reliability is improved, and the failure probability of random access is further reduced.

Based on any of the above embodiments, the rule 4 further includes:

Specifically, in the embodiment of the present application, regarding rule 4, further including:

selecting according to whether a Transport Block (TB) is generated on a first PUSCH (also referred to as an Uplink Shared CHannel (UL-SCH)), that is, whether a Media Access Control (MAC) of the UE transmits a Protocol Data Unit (PDU) to the PUSCH, and if the PDU is transmitted, the PDU is mapped to the TB on a physical layer, the TB is generated, and if the PDU is not transmitted, the TB is not generated:

when a first type of PUSCH generates a TB (that is, a Media Access Control (MAC) of the UE sends a Protocol Data Unit (PDU) to the PUSCH, and the PDU is mapped to the TB in a physical layer), further reusing the above rules 1-3; otherwise, selecting PUCCH and discarding the first type PUSCH.

According to the transmission method for the conflict between the uplink channels, when the uplink channel conflict occurs, the selection is carried out according to whether the first-class PUSCH generates the transmission block, so that the reliability is improved, and the failure probability of random access is further reduced.

Based on any of the above embodiments, when there is an overlap between an uplink channel carrying uplink control information UCI and a first type of physical uplink shared channel PUSCH in a time domain, selecting one of the channels for transmission according to a predetermined rule specifically includes:

Specifically, in the embodiment of the present application, when there is an overlap in the time domain between a PUCCH and a plurality of PUSCHs including a first type of PUSCH: selecting one PUSCH from PUSCHs except the first type PUSCH in the plurality of PUSCHs, transferring UCI on the PUCCH to the selected PUSCH for transmission, and not transmitting the PUCCH; (i.e. PUSCH carrying UCI on PUCCH is non first class PUSCH).

It should be noted that: the first type of PUSCH is not used as a candidate PUSCH for carrying UCI on the PUCCH, that is, the transmission of UCI on the first type of PUSCH is not supported, and then, according to the prior art, one PUSCH is selected from other PUSCHs overlapping with the PUCCH as a target PUSCH for carrying UCI on the PUCCH; in this process, it is not necessary to determine whether the time conditions for multiplexing transmission are satisfied between the first-class PUSCH and the PUCCH (the time conditions are the time calculated according to a specific formula, which is predefined in the prior art, and these time conditions need to be satisfied between the first symbol of the earliest channel in the PUCCH and the PDCCH corresponding to the PUCCH, the PDSCH corresponding to the PUCCH, or the SPS PDSCH release) to transfer UCI on the PUCCH to the target PUSCH).

According to the transmission method for the conflict between the uplink channels, when the uplink channel conflict occurs, the UCI on the PUCCH is transferred to the selected PUSCH for transmission, so that the reliability is improved, and the failure probability of random access is further reduced.

Based on any embodiment above, further include: and the first type PUSCH and the target PUSCH are respectively transmitted on different carriers or are respectively transmitted on symbol sets with non-overlapping time domains on the same carrier.

Specifically, in the embodiment of the present application, the selected one PUSCH and the PUSCH of the first type are transmitted on different carriers, or transmitted on symbol sets on the same carrier, where time domains are not overlapped.

The first-class PUSCH does not need to satisfy the definition of the time condition for multiplexing with the PUCCH, that is, the UE does not need to determine whether the time condition for multiplexing between the first-class PUSCH and the PUCCH is satisfied.

According to the transmission method for the uplink channel conflict provided by the embodiment of the application, when the uplink channel conflict occurs, the UCI on the PUCCH is transferred to the selected PUSCH for transmission, the first-class PUSCH and the selected PUSCH are respectively transmitted on different carriers, or are respectively transmitted on symbol sets with non-overlapping time domains on the same carrier, so that the reliability is improved, and the failure probability of random access is further reduced.

Specifically, in the embodiment of the present application, when there is time domain overlap between a PUSCH carrying UCI and a PUSCH of a first type on the same carrier, one of the channels is selected for transmission according to the following predetermined rules:

Based on any of the above embodiments, the rule 5 further includes one of the following:

Specifically, in the embodiment of the present application, for rule 5, one of the following is further included:

if the UCI carried on the PUSCH at least comprises A-CSI, the UE autonomously selects one of the channels for transmission; if UCI carried on the PUSCH is CSI, selecting a first type PUSCH, and discarding the PUCCH;

or if the UCI carried on the PUSCH at least comprises the A-CSI, selecting the PUSCH carrying the UCI, and discarding the first type PUSCH; if UCI carried on the PUSCH is SP-CSI, selecting a first class of PUSCH, and discarding the PUCCH;

or if the UCI carried on the PUSCH at least comprises A-CSI and the PUSCH comprises TB transmission, the UE autonomously selects one of the channels for transmission; if UCI carried on the PUSCH is SP-CSI or does not contain TB transmission, selecting a first type PUSCH and discarding the PUCCH;

or if the UCI carried on the PUSCH at least comprises A-CSI and the PUSCH comprises TB transmission, selecting the PUSCH carrying the UCI and discarding the first type PUSCH; if UCI carried on the PUSCH is SP-CSI or does not contain TB transmission, selecting a first type PUSCH and discarding the PUCCH;

or, if the UCI carried on the PUSCH at least comprises A-CSI and the PUSCH does not contain TB transmission, the UE autonomously selects one of the channels for transmission; if UCI carried on the PUSCH is SP-CSI or contains TB transmission, selecting a first type PUSCH and discarding the PUCCH;

or if the UCI carried on the PUSCH at least comprises A-CSI and the PUSCH does not contain TB transmission, selecting the PUSCH carrying the UCI and discarding the first type PUSCH; and if the UCI carried on the PUSCH is SP-CSI or contains TB transmission, selecting the first type PUSCH and discarding the PUCCH.

According to the transmission method for the conflict between the uplink channels, when the uplink channel conflict occurs, one of the channels is selected for transmission according to the type of the UCI carried by the PUSCH, so that the reliability is improved, and the failure probability of random access is further reduced.

Based on any of the above embodiments, the rule 8 further includes:

Specifically, in the embodiment of the present application, if the PUSCH carrying the UCI is a PUSCH scheduled to include TB transmission (for example, fallback DCI scheduling, i.e., PDCCH scheduling using fallback DCI transmission, or non-fallback DCI scheduling, and an indication field in the DCI indicates that there is a UL-SCH, the fallback DCI is, for example, DCI format 0-0, and the non-fallback DCI is, for example, DCI format 0-1, 0-2, etc.), the UE selects the PUSCH with the TB generated for transmission (i.e., the MAC of the UE transmits a PDU to this PUSCH, and the PDU is mapped to the TB in the physical layer), and does not transmit the PUSCH without the TB generated.

According to the transmission method for the conflict between the uplink channels, when the uplink channel conflict occurs, the PUSCH bearing the UCI is selected for the PUSCH scheduled to include TB transmission, so that the reliability is improved, and the failure probability of random access is further reduced.

Based on any of the above embodiments, the first type of PUSCH includes a PUSCH scheduled by a random access response permission RAR grant, a retransmission of Msg3 PUSCH, a PUSCH in a second type of random access, and a retransmission of PUSCH in a second type of random access; and/or the random access procedure is a contention-based random access procedure.

Specifically, in the embodiment of the present application, the PUSCH of the first type includes a PUSCH scheduled by a RAR grant, a retransmission of the Msg3 PUSCH, a PUSCH in a random access of the second type, and a retransmission of the PUSCH in a random access of the second type; and/or the random access procedure is a contention-based random access procedure.

And the PUSCH scheduled by the RAR grant is the msg3 PUSCH in the first-type random access.

And the PUSCH in the second type random access is the PUSCH in msg A in the second type random access.

If the retransmission of the Msg3 PUSCH, namely the PUSCH initial transmission scheduled by the RAR grant, fails, the PUSCH retransmission scheduled by the DCI dynamic scheduling (using TC-RNTI scrambling) mode is performed on the PUSCH.

According to the transmission method for the uplink channel conflict provided by the embodiment of the application, the first-class PUSCH comprises the retransmission of the PUSCH scheduled by the RAR grant and the Msg3 PUSCH, the retransmission of the PUSCH in the second-class random access and the retransmission of the PUSCH in the second-class random access, so that the reliability is improved, and the failure probability of the random access is further reduced.

The specification is as follows: the above embodiments can be summarized into three cases:

case 1: when there is overlap of PUCCH only with the first type PUSCH in the time domain: the UE autonomously selects one of the channels for transmission or selects one of the channels for transmission according to a predetermined rule.

Case 2: when the PUCCH overlaps with a plurality of PUSCHs including the first type PUSCHs in a time domain: and selecting one PUSCH from the PUSCHs except the first type PUSCH from the plurality of PUSCHs, transferring the UCI on the PUCCH to the selected PUSCH for transmission, and not transmitting the PUCCH.

Case 3: when the time domain overlapping exists between the PUSCHs carrying the UCI and the PUSCHs of the first type on the same carrier wave, the UE autonomously selects one of the channels for transmission or selects one of the channels for transmission according to a preset rule.

For case 1 and case 2, the UCI may be at least one of HARQ-ACK, SR, periodic CSI.

For case 3, the UCI may be at least one of SP-CSI, a-CSI; if the UCI on the PUSCH originally is transferred from the PUCCH, at least one of HARQ-ACK, SR, and periodic CSI may be included.

When the contention random access is adopted, processing according to the mode; when non-contention random access is adopted, the processing is not required to be performed according to the above method, that is, under the non-contention random access, for

cases

1 and 2, a first-class PUSCH under the non-contention random access can also be used for carrying UCI on a PUCCH, one PUSCH is selected to carry UCI on the PUCCH in all PUSCHs overlapped with the PUCCH according to the method of the prior art, the first-class PUSCH is not required to be specially treated, and for case 3, the UE does not expect the overlapping situation, that is, the base station avoids the overlapping situation by scheduling or configuration; of course, it is also possible to consider that the PUSCH of the first type in any random access case is processed in the above manner without the above limitation.

Based on any of the above embodiments, fig. 4 is a second schematic diagram of a transmission method for uplink inter-channel collision according to the embodiment of the present application, and as shown in fig. 4, an execution subject of the transmission method for uplink inter-channel collision according to the embodiment of the present application may be a base station. The method comprises the following steps:

step 401, when an uplink channel carrying uplink control information UCI overlaps with a first type of physical uplink shared channel PUSCH in a time domain, determining that a terminal UE autonomously selects one of the channels for transmission, or determining that the UE selects one of the channels for transmission according to a predetermined rule, where the first type of PUSCH is a PUSCH in a random access process.

Specifically, the method for transmitting a collision between uplink channels according to the embodiment of the present application is the same as the method described in the corresponding embodiment, and can achieve the same technical effect, except that the execution main bodies are different, and detailed descriptions of the same parts and beneficial effects as those of the corresponding method embodiment in this embodiment are not repeated herein.

Based on any of the above embodiments, when there is an overlap between an uplink channel carrying uplink control information UCI and a first type of physical uplink shared channel PUSCH in a time domain, determining that the UE autonomously selects one of the channels for transmission specifically includes:

Based on any of the above embodiments, when there is an overlap between an uplink channel carrying uplink control information UCI and a first type of physical uplink shared channel PUSCH in a time domain, determining that the UE selects one of the channels for transmission according to a predetermined rule, specifically including one of the following rules:

Based on any of the above embodiments, the rule 4 further includes:

Based on any of the above embodiments, when there is an overlap between an uplink channel carrying uplink control information UCI and a first type of physical uplink shared channel PUSCH in a time domain, determining that the UE selects one of the channels for transmission according to a predetermined rule specifically includes:

Based on any of the above embodiments, the rule 8 further includes:

Based on any of the above embodiments, the first type of PUSCH includes a PUSCH scheduled by a RAR grant, a retransmission of Msg3 PUSCH, a PUSCH in a second type of random access, and a retransmission of PUSCH in a second type of random access; and/or the random access procedure is a contention-based random access procedure.

Based on any of the above embodiments, when there is an overlap between an uplink channel carrying uplink control information UCI and a first type of physical uplink shared channel PUSCH in a time domain, determining that the UE autonomously selects one of the channels for transmission, or determining that the UE selects one of the channels for transmission according to a predetermined rule, specifically includes:

Specifically, in the embodiments of the present application:

when the PUCCH only overlaps with the PUSCH of the first type in the time domain, for a situation where the terminal selects one of the channels for transmission according to a predetermined rule, when the base station side knows which UE the PUSCH of the first type is transmitted (for example, when CFRA is used), the base station may detect only the selected channel according to the rule and does not detect the dropped channel, and when the base station side does not know which UE the PUSCH of the first type is transmitted (for example, when CBRA is used), the base station side blindly detects the PUCCH and the PUSCH of the first type for the terminal that needs to transmit the PUCCH; when receiving the first type PUSCH, the receiving is carried out in a mode that no UCI is transmitted on the PUSCH.

When the PUCCH only overlaps with the first-class PUSCH in a time domain, aiming at the condition that the terminal autonomously selects one channel for transmission, namely the UE arbitrarily selects one channel from the PUCCH and the first-class PUSCH for transmission, the base station side blindly detects the PUCCH and the first-class PUSCH for the terminal needing to send the PUCCH, and receives the first-class PUSCH in a mode that no UCI is transmitted on the terminal when receiving the first-class PUSCH.

When there is time domain overlap between the PUSCH carrying UCI and the PUSCH of the first type on the same carrier, for a situation that a terminal selects one of the channels for transmission according to a predetermined rule, when the base station side knows which UE the PUSCH of the first type is sent (for example, when CFRA is used), the base station may detect only the selected channel according to the rule, and does not detect the dropped channel, and when the base station side does not know which UE the PUSCH of the first type is sent (for example, when CBRA is used), the base station side blindly detects the PUSCH carrying UCI and the PUSCH of the first type to the PUSCH terminal that needs to send the PUSCH carrying UCI; when receiving the first type PUSCH, the receiving is carried out in a mode that no UCI is transmitted on the PUSCH.

When the time domain of the PUSCH bearing the UCI and the first class of PUSCHs are overlapped on the same carrier wave, aiming at the condition that the terminal autonomously selects one of the channels for transmission, namely UE randomly selects one of the PUSCHs bearing the UCI and the first class of PUSCHs for transmission, the base station side blindly detects the PUSCHs bearing the UCI and the first class of PUSCHs for the terminal needing to send the PUSCHs bearing the UCI; when receiving the first type PUSCH, the receiving is carried out in a mode that no UCI is transmitted on the PUSCH.

The method in each of the above embodiments is described in three specific embodiments as follows:

example 1:

fig. 5 is a schematic diagram of an uplink inter-channel collision provided in an embodiment of the present application, and as shown in fig. 5, it is assumed that a UE transmits msg1 in a certain slot of a PCell, a contention mode is used for random access, and a PUSCH to be subjected to RAR UL grant scheduling in a slot n +8 is determined according to a received msg2 and a timing relationship, and a base station does not know that the UE enters a random access process, schedules a PDSCH transmission in a slot before the slot n +8, and needs to perform HARQ-ACK feedback through a PUCCH in the slot n +8, so that a collision (i.e., an overlap in transmission time) occurs between a PUCCH carrying HARQ-ACK and a PUSCH scheduled by a RAR UL grant, according to the method of the present application:

the UE side:

if rule 1 is employed: assuming that HARQ-ACK is prior, when UE selects PUCCH carrying HAR Q-ACK or UE autonomously selects one transmission from PUCCH and PUSCH scheduled by RAR UL grant, the UE selects PUCCH carrying HARQ-ACK; the UE transmits a PUCCH carrying HARQ-ACK in a time slot n +8 and does not transmit a PUSCH scheduled by an RA R UL grant;

if rule 2 is employed: always selecting PUSCH scheduled by RAR UL grant, and not transmitting PUCCH; the UE transmits the PUSCH scheduled by the RAR UL grant and does not transmit the PUCCH carrying the HARQ-ACK in the time slot n + 8;

if rule 3 is employed: always selecting PUCCH, not transmitting PUSCH scheduled by RAR UL grant; the UE transmits a PUCCH carrying HARQ-ACK in a time slot n +8 and does not transmit a PUSCH scheduled by an RAR UL grant;

if rule 4 is employed: firstly, determining whether the PUSCH scheduled by the RAR UL grant generates a TB, if the TB generates, reusing one of the rules 1-3 to determine which channel is selected, if the TB does not generate the TB, selecting the PUCCH, and not transmitting the PUSCH scheduled by the RAR UL grant;

if a mode of UE autonomous selection is adopted, the UE can autonomously select one transmission from the PUCCH and the PUSCH scheduled by the RAR UL grant, for example, the PUSCH scheduled by the RAR UL grant is selected by the UE, the UE only transmits the PUSCH scheduled by the RAR UL grant in the time slot n +8, and does not transmit the PUCCH;

a base station side:

in the contention mode, it is not known which UE this PUSCH is from before the PUSCH scheduled by the RAR UL grant is not received, and it is also not known whether the MAC of the UE has issued a PDU to the PUSCH scheduled by the RAR UL grant, and certainly, in the UE autonomous selection mode, even in the non-contention mode, the base station does not know which channel the UE has selected for transmission, and the base station needs to detect the UE that originally wants to transmit the PUCCH in this slot on the corresponding PUCCH resource, and also needs to receive the PUSCH scheduled by the RAR UL grant in msg2 on the PUSCH resource that is indicated to the terminal performing random access by the RAR UL grant, and receive this PUSCH in a manner without UCI multiplexing, so that the PUSCH scheduled by the RAR UL grant can be correctly obtained.

Example 2:

fig. 6 is a second schematic diagram of collision between uplink channels according to the embodiment of the present application, and as shown in fig. 6, assuming that a terminal is configured with 3 carriers, in a PCell (CC1), as in the above-mentioned embodiment 1, further, in a slot 8, there is also one PUSCH and PUCCH overlapping on each of the other two scells (CC2, CC 3), according to the method of the present application:

the UE side:

when multiplexing transmission when the PUCCH and the PUSCH are overlapped is considered, the PUSCH scheduled by the RAR UL grant overlapped with the PUCCH is not considered, that is, the UE selects one PUSCH only in the PUSCHs overlapped with the PUCCH on

CCs

2 and 3 according to a predetermined selection rule (the selection rule is the prior art, for example, according to whether the PUSCH carries a-CSI, according to whether the PUSCH has DCI scheduling, according to the CC number where the PUSCH is located, and the like, which is not described in detail), for example, the PUSCH on CC2 is selected to carry the UCI on the PUCCH, the UE transfers HARQ-ACK on the PUCCH to the PUSCH on CC2 for transmission, and when the Pcell does not need to transmit the PUCCH any more, the Pcell does not have overlap with the PUSCH scheduled by the RAR UL grant, so that the UE can transmit the PUSCH on

CCs

1, 2, and 3 in slot n +8, respectively.

A base station side:

because the base station does not know whether PUSCH transmission scheduled by RAR UL grant of the UR exists in slot n +8 in contention RA, the base station only selects one PUSCH from PUSCHs on

CCs

2 and 3 according to the above rules similar to the UE side, and determines that the PUSCH carries UCI on PUCCH, then the base station receives the PUSCH on CC2 in slot n +8 in a manner of carrying UCI, receives the PUSCH on CC3, does not need to receive the PUCCH on CC1, and further needs to receive the PUSCH scheduled by RAR UL grant in msg2 on a PUSCH resource indicated to a terminal performing random access by the RAR UL grant, and receives the PUSCH in a manner of not multiplexing UCI, so that the PUSCH scheduled by RAR UL grant can be correctly obtained.

Example 3:

fig. 7 is a third schematic diagram of an uplink inter-channel collision provided in the embodiment of the present application, as shown in fig. 7, assuming that a UE sends msg1 in a certain timeslot of a PCell, a contention mode is used for random access, and a PUSCH to be subjected to RAR UL grant scheduling in a timeslot n +8 is determined according to a received msg2 and a timing relationship, and a base station does not know that the UE enters a random access process, an SP-CSI transmission transmitted on the PUSCH is activated through a PDCCH in a timeslot before the timeslot n +8, and the timeslot n +8 is a transmission opportunity of a PUSCH (SP-CSI PUSCH for short) carrying the SP-CSI, and a collision of the PUSCH carrying the SP-CSI and the PUSCH scheduled by the RAR UL grant occurs (i.e., there is an overlap in transmission time on the same carrier), according to the method of the present application:

the UE side:

if rule 5 is employed: assuming that the SP-CSI priority is lower than the PUSCH scheduled by the RAR UL grant, the UE selects the PUSCH scheduled by the RAR UL grant, or when the UE selects one from the master-slave SP-CSI PUSCH and the PUSCH scheduled by the RAR UL grant for transmission, the UE selects the PUSCH scheduled by the RAR UL grant; the UE transmits the PUSCH scheduled by the RAR UL grant and does not transmit the SP-CSI PUSCH in the time slot n + 8;

if rule 6 is employed: always selecting a PUSCH scheduled by RAR UL grant, and not transmitting a SP-CSI PUSCH; the UE transmits the PUSCH scheduled by the RAR UL grant and does not transmit the SP-CSI PUCCH in the time slot n + 8;

if rule 7 is employed: always selecting a PUSCH carrying UCI, and not transmitting a PUSCH scheduled by RAR UL grant; the UE transmits the SP-CSI PUSCH in the time slot n +8, and does not transmit the PUSCH scheduled by the RAR UL grant;

if a mode of UE autonomous selection is adopted, the UE can autonomously select one transmission from an SP-CSI PUSCH and a PUSCH scheduled by an RAR UL grant, for example, the PUSCH scheduled by the RAR UL grant is selected by the UE, and the UE only transmits the PUSCH scheduled by the RAR UL grant in a time slot n +8 and does not transmit the SP-CSI PUSCH;

a base station side:

in a contention mode, it is not known which UE this PUSCH is from before the PUSCH scheduled by the RAR UL grant is not received, nor is it known whether the MAC of the UE has issued a PDU to the PUSCH scheduled by the RAR UL grant, and certainly, if the PUSCH is selected autonomously by the UE, even in a non-contention mode, the base station does not know which channel the UE has selected for transmission, the base station needs to detect the UE that originally wants to transmit the SP-CSI PUSCH in this slot on the corresponding SP-CSI PUSCH resource, and also needs to receive the PUSCH scheduled by the RAR UL grant in msg2 on the PUSCH resource indicated to the terminal performing random access, and receive this PUSCH in a manner without UCI multiplexing, so that the PUSCH scheduled by the RAR UL grant can be obtained correctly.

It should be noted that, in embodiments 1 and 2, only the PUCCH and the PUSCH scheduled by the RAR grant are taken as an example, and when the PUCCH and the PUSCH are transmitted in different cells, if time overlapping occurs, the above method is also applicable; in the above embodiments 1 and 2, only one of the rules 1 is taken as an example, and the other methods are also applicable; in the above embodiments 1 and 2, only the PUCCH is used to carry the HARQ-ACK as an example, if the PUCCH carries one of CSI and SR, for example, the final selection result may be the PUSCH scheduled for transmitting the RAR UL grant, and the PUCCH carrying the CSI and SR is not transmitted; in the above embodiment 3, only taking the case that the PUSCH carrying the SP-CSI overlaps with the PUSCH scheduled by the RAR UL grant as an example, and the case that the PUSCH carrying the UCI overlaps with the PUSCH scheduled by the RAR UL grant is similar, which is not described again, for example, in the case of the a-CSI PUSCH, except for the above manner, the rule 8 may be adopted: determining which one of an A-CSI PUSCH and a PUSCH scheduled by an RAR UL grant generates a TB, and transmitting only a channel generating the TB, for example, determining that the PUSCH scheduled by the RAR UL grant generates the TB, transmitting only the PUSCH scheduled by the RAR UL grant, and not transmitting the A-CSI PUSCH; in the above embodiments 1 to 3, only the PUSCH scheduled by the RAR grant is taken as an example, and the same applies to the replacement with the Msg a PUSCH.

The application provides a transmission method when PUSCH in the random access process conflicts with PUCCH/PUSCH bearing UCI, one channel is selected autonomously by UE or one channel is selected according to a specific rule for transmission, or PUSCH in the non-random access process is selected to bear UCI transmission from PUCCH, on one hand, the problem that no transmission scheme is defined aiming at the scene in the prior art is solved, on the other hand, multiplexing transmission of UCI on PUSCH in the random access process is avoided, correct reception of PUSCH in the random access process by a base station is ensured, and on the third hand, reasonable channel selection is made according to the importance degree of UCI type borne by an uplink channel, and the failure probability of random access is reduced.

Based on any of the above embodiments, fig. 8 is a schematic structural diagram of a terminal provided in an embodiment of the present application, and as shown in fig. 8, the terminal includes a memory 820, a transceiver 800, and a processor 810:

a memory 820 for storing a computer program; a transceiver 800 for transceiving data under the control of the processor 810; a processor 810 for reading the computer program in the memory 820 and performing the following operations:

And in particular transceiver 800, for receiving and transmitting data under the control of processor 810.

Where in fig. 8, the bus architecture may include any number of interconnected buses and bridges, with one or more processors, represented by processor 810, and various circuits, represented by memory 820, being linked together. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, will not be described any further herein. The bus interface provides an interface. The transceiver 800 may be a number of elements including a transmitter and a receiver that provide a means for communicating with various other apparatus over transmission media including wireless channels, wired channels, fiber optic cables, and the like. The user interface 830 may also be an interface capable of interfacing with a desired device for different user devices, including but not limited to a keypad, a display, a speaker, a microphone, a joystick, etc.

The processor 810 is responsible for managing the bus architecture and general processing, and the memory 820 may store data used by the processor 810 in performing operations.

Optionally, the processor 810 may be a CPU (central processing unit), an ASIC (Application Specific Integrated Circuit), an FPGA (Field-Programmable Gate Array), or a CPLD (Complex Programmable Logic Device), and the processor may also have a multi-core architecture.

The processor is used for executing any one of the methods provided by the embodiment of the application according to the obtained executable instructions by calling the computer program stored in the memory. The processor and memory may also be physically separated.

It should be noted that, the terminal provided in the embodiment of the present application can implement all the method steps implemented by the method embodiment and achieve the same technical effect, and detailed descriptions of the same parts and beneficial effects as the method embodiment in this embodiment are omitted here.

Specifically, the terminal provided in the embodiment of the present application can implement all the method steps implemented by the method embodiment and achieve the same technical effect, and details of the same parts and beneficial effects as those of the method embodiment in this embodiment are not repeated herein.

Based on any of the above embodiments, the rule 4 further includes:

Based on any of the above embodiments, the rule 8 further includes:

Based on any of the above embodiments, fig. 9 is a schematic structural diagram of a base station provided in this embodiment, as shown in fig. 9, the base station includes a memory 920, a transceiver 900, and a processor 910:

a memory 920 for storing a computer program; a transceiver 900 for transceiving data under the control of the processor 910; a processor 910 configured to read the computer program in the memory 920 and perform the following operations:

And in particular transceiver 900, for receiving and transmitting data under control of processor 910.

Wherein in fig. 9, the bus architecture may include any number of interconnected buses and bridges, with one or more processors, represented by processor 910, and various circuits, represented by memory 920, being linked together. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, will not be described any further herein. The bus interface provides an interface. The transceiver 900 may be a number of elements including a transmitter and a receiver that provide a means for communicating with various other apparatus over a transmission medium including wireless channels, wired channels, fiber optic cables, and the like. The processor 910 is responsible for managing the bus architecture and general processing, and the memory 920 may store data used by the processor 910 in performing operations.

The processor 910 may be a Central Processing Unit (CPU), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA), or a Complex Programmable Logic Device (CPLD), and may also have a multi-core architecture.

It should be noted that, the base station provided in the embodiment of the present application can implement all the method steps implemented by the method embodiment and achieve the same technical effect, and detailed descriptions of the same parts and beneficial effects as the method embodiment in this embodiment are not repeated herein.

Specifically, the base station provided in the embodiment of the present application can implement all the method steps implemented by the method embodiment and achieve the same technical effect, and details of the same parts and beneficial effects as those of the method embodiment in this embodiment are not repeated herein.

Based on any of the above embodiments, the rule 4 further includes:

Based on any of the above embodiments, the rule 8 further includes:

Based on any of the above embodiments, fig. 10 is a schematic diagram of an apparatus for transmitting an uplink inter-channel collision according to an embodiment of the present application, and as shown in fig. 10, the apparatus for transmitting an uplink inter-channel collision includes a transmission module 1001.

A transmission module 1001, configured to autonomously select one of the channels for transmission or select one of the channels for transmission according to a predetermined rule when an uplink channel carrying uplink control information UCI overlaps with a first type of physical uplink shared channel PUSCH in a time domain, where the first type of PUSCH is a PUSCH in a random access process.

Specifically, the transmission apparatus for collision between uplink channels according to the embodiment of the present application can implement all the method steps implemented by the method embodiment and achieve the same technical effect, and details of the same parts and beneficial effects as those of the method embodiment in this embodiment are not described herein again.

Based on any of the above embodiments, the rule 4 further includes:

Based on any of the above embodiments, the rule 8 further includes:

Based on any of the above embodiments, fig. 11 is a second schematic diagram of a transmission apparatus for uplink inter-channel collision according to the embodiment of the present application, and as shown in fig. 11, the transmission apparatus for uplink inter-channel collision includes a determining module 1101.

A determining module 1101, configured to determine that a terminal UE autonomously selects one of channels for transmission when an uplink channel carrying uplink control information UCI overlaps with a first type of physical uplink shared channel PUSCH in a time domain, or determine that the UE selects one of channels for transmission according to a predetermined rule, where the first type of PUSCH is a PUSCH in a random access process.

Based on any of the above embodiments, the rule 4 further includes:

Based on any of the above embodiments, the rule 8 further includes:

It should be noted that, in the foregoing embodiments of the present application, the division of the units/modules is schematic, and is only a logic function division, and another division manner may be used in actual implementation. In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.

The integrated unit, if implemented as a software functional unit and sold or used as a stand-alone product, may be stored in a processor readable storage medium. Based on such understanding, the technical solution of the present application may be substantially implemented or contributed by the prior art, or all or part of the technical solution may be embodied in a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, a network device, or the like) or a processor (processor) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.

Based on any one of the foregoing embodiments, an embodiment of the present application further provides a processor-readable storage medium, where the processor-readable storage medium stores a computer program, where the computer program is configured to cause the processor to execute the method provided in each of the foregoing embodiments, and the method includes:

Or comprises the following steps:

It should be noted that: the processor-readable storage medium can be any available medium or data storage device that can be accessed by a processor, including, but not limited to, magnetic memory (e.g., floppy disks, hard disks, magnetic tape, magneto-optical disks (MOs), etc.), optical memory (e.g., CDs, DVDs, BDs, HVDs, etc.), and semiconductor memory (e.g., ROMs, EPROMs, EEPROMs, non-volatile memory (NAND FLASH), Solid State Disks (SSDs)), etc.

In addition, it should be noted that: in the embodiment of the present application, the term "and/or" describes an association relationship of associated objects, and means that there may be three relationships, for example, a and/or B, which may mean: a exists alone, A and B exist simultaneously, and B exists alone. The character "/" generally indicates that the former and latter associated objects are in an "or" relationship.

In the embodiments of the present application, the term "plurality" means two or more, and other terms are similar thereto.

The technical scheme provided by the embodiment of the application can be suitable for various systems, particularly 5G systems. For example, the applicable system may be a global system for mobile communication (GSM) system, a Code Division Multiple Access (CDMA) system, a Wideband Code Division Multiple Access (WCDMA) General Packet Radio Service (GPRS) system, a long term evolution (long term evolution, LTE) system, an LTE Frequency Division Duplex (FDD) system, an LTE Time Division Duplex (TDD) system, an LTE-a (long term evolution) system, a universal mobile system (universal mobile telecommunications system, UMTS), a Worldwide Interoperability for Mobile Access (WiMAX) system, a New Radio network (NR 5) system, etc. These various systems include terminal devices and network devices. The System may further include a core network portion, such as an Evolved Packet System (EPS), a 5G System (5GS), and the like.

The terminal device referred to in the embodiments of the present application may refer to a device providing voice and/or data connectivity to a user, a handheld device having a wireless connection function, or another processing device connected to a wireless modem. In different systems, the names of the terminal devices may be different, for example, in a 5G system, the terminal device may be called a User Equipment (UE). A wireless terminal device, which may be a mobile terminal device such as a mobile telephone (or "cellular" telephone) and a computer having a mobile terminal device, for example, a portable, pocket, hand-held, computer-included, or vehicle-mounted mobile device, may communicate with one or more Core Networks (CNs) via a Radio Access Network (RAN). Examples of such devices include Personal Communication Service (PCS) phones, cordless phones, Session Initiation Protocol (SIP) phones, Wireless Local Loop (WLL) stations, and Personal Digital Assistants (PDAs). The wireless terminal device may also be referred to as a system, a subscriber unit (subscriber unit), a subscriber station (subscriber station), a mobile station (mobile), a remote station (remote station), an access point (access point), a remote terminal device (remote terminal), an access terminal device (access terminal), a user terminal device (user terminal), a user agent (user agent), and a user device (user device), which are not limited in this embodiment of the present application.

The network device according to the embodiment of the present application may be a base station, and the base station may include a plurality of cells for providing services to a terminal. A base station may also be referred to as an access point, or a device in an access network that communicates over the air-interface, through one or more sectors, with wireless terminal devices, or by other names, depending on the particular application. The network device may be configured to exchange received air frames with Internet Protocol (IP) packets as a router between the wireless terminal device and the rest of the access network, which may include an Internet Protocol (IP) communication network. The network device may also coordinate attribute management for the air interface. For example, the network device according to the embodiment of the present application may be a Base Transceiver Station (BTS) in a Global System for Mobile communications (GSM) or a Code Division Multiple Access (CDMA), may be a network device (NodeB) in a Wideband Code Division Multiple Access (WCDMA), may be an evolved Node B (eNB or e-NodeB) in a Long Term Evolution (LTE) System, may be a 5G Base Station (gbb) in a 5G network architecture (next evolution System), may be a Home evolved Node B (HeNB), a relay Node (relay Node), a Home Base Station (femto), a pico Base Station (pico Base Station), and the like, which are not limited in the embodiments of the present application. In some network architectures, a network device may include a Centralized Unit (CU) node and a Distributed Unit (DU) node, which may also be geographically separated.

Multiple Input Multiple Output (MIMO) transmission may be performed between the network device and the terminal device by using one or more antennas, where the MIMO transmission may be Single User MIMO (SU-MIMO) or Multi-User MIMO (MU-MIMO). The MIMO transmission may be 2D-MIMO, 3D-MIMO, FD-MIMO, or massive-MIMO, or may be diversity transmission, precoding transmission, beamforming transmission, or the like, depending on the form and number of root antenna combinations.

As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, optical storage, and the like) having computer-usable program code embodied therein.

The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer-executable instructions. These computer-executable instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These processor-executable instructions may also be stored in a processor-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the processor-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These processor-executable instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

It will be apparent to those skilled in the art that various changes and modifications may be made in the present application without departing from the spirit and scope of the application. Thus, if such modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is intended to include such modifications and variations as well.

Claims

1. A method for transmitting collision between uplink channels, comprising:

2. The method according to claim 1, wherein when there is an overlap in a time domain between an uplink channel carrying uplink control information UCI and a first type of physical uplink shared channel PUSCH, the UE autonomously selects one of the channels for transmission, specifically comprising:

3. The method according to claim 1, wherein when there is an overlap between an uplink channel carrying uplink control information UCI and a first type physical uplink shared channel PUSCH in a time domain, one of the channels is selected according to a predetermined rule for transmission, and specifically includes one of the following rules:

4. The method of claim 3, wherein the rule 1 further comprises one of the following:

5. The method for transmitting an uplink interchannel collision according to claim 3, wherein said rule 4 further comprises:

6. The method according to claim 1, wherein when there is an overlap between an uplink channel carrying uplink control information UCI and a first type physical uplink shared channel PUSCH in a time domain, selecting one of the channels for transmission according to a predetermined rule includes:

7. The method for transmitting an uplink interchannel collision according to claim 6, further comprising: and the first type PUSCH and the target PUSCH are respectively transmitted on different carriers or are respectively transmitted on symbol sets with non-overlapping time domains on the same carrier.

8. The method according to claim 1, wherein when there is an overlap between an uplink channel carrying uplink control information UCI and a first type physical uplink shared channel PUSCH in a time domain, one of the channels is selected according to a predetermined rule for transmission, and specifically includes one of the following rules:

9. The method of claim 8, wherein the rule 5 further comprises one of the following:

10. The method for transmitting an uplink interchannel collision according to claim 8, wherein said rule 8 further comprises:

11. The transmission method according to any of claims 1-10, wherein the PUSCH of the first type includes PUSCH scheduled by a random access response grant RAR grant, retransmission of Msg3 PUSCH, PUSCH in random access of the second type, retransmission of PUSCH in random access of the second type; and/or the random access procedure is a contention-based random access procedure.

12. A method for transmitting collision between uplink channels, comprising:

13. The method according to claim 12, wherein when there is an overlap in a time domain between an uplink channel carrying uplink control information UCI and a first type of physical uplink shared channel PUSCH, determining that the UE autonomously selects one of the channels for transmission specifically includes:

14. The method according to claim 12, wherein when there is an overlap in a time domain between an uplink channel carrying uplink control information UCI and a first type of physical uplink shared channel PUSCH, determining that the UE selects one of the channels for transmission according to a predetermined rule, specifically includes one of the following rules:

15. The method of claim 14, wherein the rule 1 further comprises one of the following:

16. The method for transmitting an uplink interchannel collision according to claim 14, wherein said rule 4 further comprises:

17. The method according to claim 12, wherein when there is an overlap in a time domain between an uplink channel carrying uplink control information UCI and a first type of physical uplink shared channel PUSCH, determining that the UE selects one of the channels for transmission according to a predetermined rule specifically includes:

18. The method for transmitting an uplink interchannel collision according to claim 17, further comprising: and the first type PUSCH and the target PUSCH are respectively transmitted on different carriers or are respectively transmitted on symbol sets with non-overlapping time domains on the same carrier.

19. The method according to claim 12, wherein when there is an overlap in a time domain between an uplink channel carrying uplink control information UCI and a first type of physical uplink shared channel PUSCH, determining that the UE selects one of the channels for transmission according to a predetermined rule, specifically includes one of the following rules:

20. The method of claim 19, wherein the rule 5 further comprises one of the following:

21. The method for transmitting an uplink interchannel collision according to claim 19, wherein said rule 8 further comprises:

22. The method according to any of claims 12-21, wherein the PUSCH of the first type includes PUSCH scheduled by RAR grant, retransmission of Msg3 PUSCH, PUSCH in random access of the second type, retransmission of PUSCH in random access of the second type; and/or the random access procedure is a contention-based random access procedure.

23. The method according to any of claims 12-21, wherein when there is an overlap between an uplink channel carrying uplink control information UCI and a first type physical uplink shared channel, PUSCH, in a time domain, determining that the UE autonomously selects one of the channels for transmission, or determining that the UE selects one of the channels for transmission according to a predetermined rule, specifically includes:

24. A terminal comprising a memory, a transceiver, a processor;

25. The terminal according to claim 24, wherein when there is an overlap between an uplink channel carrying uplink control information UCI and a first type physical uplink shared channel PUSCH in a time domain, the UE autonomously selects one of the channels for transmission, specifically including:

26. The terminal according to claim 24, wherein when there is an overlap between an uplink channel carrying uplink control information UCI and a first type physical uplink shared channel PUSCH in a time domain, one of the channels is selected according to a predetermined rule for transmission, which specifically includes one of the following rules:

27. The terminal of claim 26, wherein the rule 1 further comprises one of:

28. The terminal of claim 26, wherein the rule 4 further comprises:

29. The terminal according to claim 24, wherein when there is an overlap between an uplink channel carrying uplink control information UCI and a first type physical uplink shared channel PUSCH in a time domain, selecting one of the channels for transmission according to a predetermined rule specifically includes:

30. The terminal of claim 29, further comprising: and the first type PUSCH and the target PUSCH are respectively transmitted on different carriers or are respectively transmitted on symbol sets with non-overlapping time domains on the same carrier.

31. The terminal according to claim 24, wherein when there is an overlap between an uplink channel carrying uplink control information UCI and a first type physical uplink shared channel PUSCH in a time domain, one of the channels is selected according to a predetermined rule for transmission, which specifically includes one of the following rules:

32. The terminal of claim 31, wherein the rule 5 further comprises one of:

33. The terminal of claim 31, wherein the rule 8 further comprises:

34. The terminal according to any of claims 24-33, wherein the PUSCH of the first type comprises a PUSCH scheduled by a random access response grant RAR grant, a retransmission of Msg3 PUSCH, a PUSCH in a random access of the second type, a retransmission of PUSCH in a random access of the second type; and/or the random access procedure is a contention-based random access procedure.

35. A base station comprising a memory, a transceiver, a processor;

36. The base station of claim 35, wherein the determining that the UE autonomously selects one of the channels for transmission when an uplink channel carrying the uplink control information UCI overlaps with a first type of physical uplink shared channel, PUSCH, in detail includes:

37. The base station of claim 35, wherein when there is an overlap between an uplink channel carrying uplink control information UCI and a first type physical uplink shared channel PUSCH in a time domain, determining that the UE selects one of the channels for transmission according to a predetermined rule specifically includes one of the following rules:

38. The base station of claim 37, wherein the rule 1 further comprises one of:

39. The base station of claim 37, wherein the rule 4 further comprises:

40. The base station of claim 35, wherein when there is an overlap between an uplink channel carrying uplink control information UCI and a first type physical uplink shared channel PUSCH in a time domain, determining that the UE selects one of the channels for transmission according to a predetermined rule specifically includes:

41. The base station of claim 40, further comprising: and the first type PUSCH and the target PUSCH are respectively transmitted on different carriers or are respectively transmitted on symbol sets with non-overlapping time domains on the same carrier.

42. The base station of claim 35, wherein when there is an overlap between an uplink channel carrying uplink control information UCI and a first type physical uplink shared channel PUSCH in a time domain, determining that the UE selects one of the channels for transmission according to a predetermined rule specifically includes one of the following rules:

43. The base station of claim 42, wherein the rule 5 further comprises one of:

44. The base station of claim 42, wherein the rule 8 further comprises:

45. The base station according to any of claims 35-44, wherein the PUSCH of the first type comprises a RAR grant scheduled PUSCH, a retransmission of Msg3 PUSCH, a PUSCH in a second type of random access, a retransmission of PUSCH in a second type of random access; and/or the random access procedure is a contention-based random access procedure.

46. The base station according to any of claims 35 to 44, wherein when there is an overlap between an uplink channel carrying uplink control information UCI and a first type physical uplink shared channel PUSCH in a time domain, determining that the UE autonomously selects one of the channels for transmission, or determining that the UE selects one of the channels for transmission according to a predetermined rule, specifically includes:

47. An apparatus for transmitting a collision between uplink channels, comprising:

48. An apparatus for transmitting a collision between uplink channels, comprising:

49. A processor-readable storage medium, characterized in that the processor-readable storage medium stores a computer program for causing a processor to perform the method of any one of claims 1 to 23.