CN114521019A

CN114521019A - Uplink control information transmission method and related equipment

Info

Publication number: CN114521019A
Application number: CN202011296090.5A
Authority: CN
Inventors: 鲁智; 陈晓航; 潘学明; 李娜; 蔡日开
Original assignee: Vivo Mobile Communication Co Ltd
Current assignee: Vivo Mobile Communication Co Ltd
Priority date: 2020-11-18
Filing date: 2020-11-18
Publication date: 2022-05-20
Also published as: WO2022105842A1

Abstract

The application discloses an uplink control information transmission method and related equipment. The method comprises the following steps: receiving configuration information sent by network side equipment, wherein the configuration information enables an uplink transmission skipping function of a terminal; under the condition that resources of a Physical Uplink Shared Channel (PUSCH) and a Physical Uplink Control Channel (PUCCH) are overlapped on a time domain, determining the transmission behavior of Uplink Control Information (UCI) borne by the PUCCH according to a target priority principle and the priority sequence of an uplink transmission skipping function; wherein the target priority principle comprises a logical channel priority principle or a Media Access Control (MAC) priority principle. When the PUSCH enables the UL skiping function and the resource overlapping exists between the PUSCH and the PUCCH bearing the UCI in the time domain, the transmission behavior of the UCI is determined based on the target priority principle and the priority sequence of the uplink transmission skipping function, so that the transmission of the UCI is realized.

Description

Uplink control information transmission method and related equipment

Technical Field

The present application belongs to the field of communications technologies, and in particular, to an uplink control information transmission method and related devices.

Background

In a communication system, Uplink Control Information (UCI) is transmitted on an Uplink Control Channel (PUCCH). Generally, when there is resource overlap between the PUCCH and the PUSCH in the time domain, UCI is generally multiplexed on the PUSCH. However, with the development of communication technology, an uplink transmission skip (UL skip) function is introduced, which allows a terminal to ignore scheduling of a network-side device and not perform uplink PUSCH transmission. However, in the above case, when there is resource conflict between PUCCH and dynamically scheduled PUSCH, the terminal may choose to include the following two:

1. not generating PUSCH, and transmitting UCI on PUCCH;

2. and generating a PUSCH, and multiplexing UCI to be transmitted on the generated PUSCH.

Therefore, in the prior art, when there is resource overlap between the PUSCH and the PUCCH carrying the UCI in the time domain and the PUSCH enables the UL blanking function, how the terminal performs UCI transmission becomes a problem that needs to be solved urgently.

Disclosure of Invention

The embodiment of the application provides an uplink control information transmission method and related equipment, which can solve the problem that a terminal cannot clearly determine the transmission behavior of UCI under the condition that resources are overlapped on a PUSCH and a PUCCH carrying the UCI in a time domain and the PUSCH enables a UL clipping function.

In a first aspect, a method for transmitting uplink control information is provided, where the method is performed by a terminal, and includes:

receiving configuration information sent by network side equipment, wherein the configuration information enables an uplink transmission skipping function of the terminal;

under the condition that resources of a Physical Uplink Shared Channel (PUSCH) and a Physical Uplink Control Channel (PUCCH) are overlapped on a time domain, determining the transmission behavior of Uplink Control Information (UCI) borne by the PUCCH according to a target priority principle and the priority sequence of the uplink transmission skipping function;

wherein the target priority principle comprises a logical channel priority principle or a Media Access Control (MAC) priority principle.

In a second aspect, an uplink control information transmission apparatus is provided, including:

a receiving module, configured to receive configuration information sent by a network side device, where the configuration information enables an uplink transmission skip function of the terminal;

a processing module, configured to determine, according to a target priority principle and a priority order of the uplink transmission skip function, a transmission behavior of uplink control information UCI carried on a physical uplink shared channel PUSCH and the physical uplink control channel PUCCH when there is resource overlap in a time domain;

In a third aspect, a terminal is provided, the terminal comprising a processor, a memory and a program or instructions stored on the memory and executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the method according to the first aspect.

In a fourth aspect, a readable storage medium is provided, on which a program or instructions are stored, which when executed by a processor, implement the steps of the method according to the first aspect.

In a fifth aspect, an embodiment of the present application provides a chip, where the chip includes a processor and a communication interface, where the communication interface is coupled to the processor, and the processor is configured to execute a program or instructions to implement the method according to the first aspect.

According to the method and the device, the configuration information sent by the network side equipment is received, and the configuration information enables the uplink transmission skipping function of the terminal; under the condition that resources of a Physical Uplink Shared Channel (PUSCH) and a Physical Uplink Control Channel (PUCCH) are overlapped on a time domain, determining the transmission behavior of Uplink Control Information (UCI) borne by the PUCCH according to a target priority principle and the priority sequence of the uplink transmission skipping function; wherein the target priority principle comprises a logical channel priority principle or a Media Access Control (MAC) priority principle. Therefore, when the PUSCH enables the UL clipping function and the PUSCH carrying the UCI has resource overlapping in the time domain, the transmission behavior of the UCI is determined based on the target priority principle and the priority sequence of the uplink transmission skipping function, so that the transmission of the UCI is realized. Therefore, in the embodiment of the present application, it can be avoided that the transmission of UCI is affected because PUSCH is not transmitted due to the uplink transmission skip function, and thus, the reliability of UCI transmission is improved.

Drawings

Fig. 1 is a block diagram of a network-side device system to which an embodiment of the present application is applicable;

fig. 2 is a flowchart of an uplink control information transmission method according to an embodiment of the present application;

fig. 3 is a diagram illustrating an example of uplink transmission in an embodiment of the present application;

fig. 4 is a second exemplary diagram of uplink transmission in the embodiment of the present application;

fig. 5 is a third exemplary diagram of uplink transmission in the embodiment of the present application;

fig. 6 is a fourth illustration of an example of uplink transmission in the embodiment of the present application;

fig. 7 is a fifth exemplary diagram of uplink transmission in the embodiment of the present application;

fig. 8 is a sixth exemplary diagram of uplink transmission in the embodiment of the present application;

fig. 9 is a structural diagram of an uplink control information transmission apparatus according to an embodiment of the present application;

fig. 10 is a block diagram of a communication device according to an embodiment of the present application;

fig. 11 is a structural diagram of a terminal according to an embodiment of the present application.

Detailed Description

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 some, but not all, of the embodiments of the present application. All other embodiments that can be derived from the embodiments given herein by a person of ordinary skill in the art are intended to be within the scope of the present disclosure.

The terms first, second and the like in the description and in the claims of the present application are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It should be understood that the data so used are interchangeable under appropriate circumstances such that embodiments of the application can be practiced in sequences other than those illustrated or described herein, and the terms "first" and "second" used herein generally do not denote any order, nor do they denote any order, for example, the first object may be one or more. In addition, "and/or" in the specification and the claims means at least one of connected objects, and a character "/" generally means that a preceding and succeeding related objects are in an "or" relationship.

It is noted that the techniques described in the embodiments of the present application are not limited to Long Term Evolution (LTE)/LTE-Advanced (LTE-a) systems, but may also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency Division Multiple Access (SC-FDMA), and other systems. The terms "system" and "network-side device" in the embodiments of the present application are often used interchangeably, and the described techniques can be used for both the above-mentioned systems and radio technologies, as well as for other systems and radio technologies. The following description describes a New Radio (NR) system for purposes of example, and NR terminology is used in much of the description below, but the techniques may also be applied to applications other than NR system applications, such as 6th Generation (6G) communication systems.

Fig. 1 shows a block diagram of a wireless communication system to which embodiments of the present application are applicable. The wireless communication system includes a terminal 11 and a network-side device 12. Wherein, the terminal 11 may also be called as a terminal Device or a User Equipment (UE), the terminal 11 may be a Mobile phone, a Tablet Personal Computer (Tablet Personal Computer), a Laptop Computer (Laptop Computer) or a notebook Computer, a Personal Digital Assistant (PDA), a palmtop Computer, a netbook, a super-Mobile Personal Computer (UMPC), a Mobile Internet Device (MID), a Wearable Device (Wearable Device) or a vehicle-mounted Device (VUE), a pedestrian terminal (PUE), and other terminal side devices, the Wearable Device includes: bracelets, earphones, glasses and the like. It should be noted that the embodiment of the present application does not limit the specific type of the terminal 11. The network-side device 12 may be a Base Station or a core network, where the Base Station may be referred to as a node B, an evolved node B, an access Point, a Base Transceiver Station (BTS), a radio Base Station, a radio Transceiver, a Basic Service Set (BSS), an Extended Service Set (ESS), a node B, an evolved node B (eNB), a home node B, a WLAN access Point, a WiFi node, a Transmit Receiving Point (TRP), or some other suitable terminology in the field, as long as the same technical effect is achieved, the Base Station is not limited to a specific technical vocabulary, and it should be noted that, in the embodiment of the present application, only the Base Station in the NR system is taken as an example, but a specific type of the Base Station is not limited.

For convenience of understanding, some contents related to the embodiments of the present application are described below:

firstly, UCI defined by a physical layer is multiplexed on a PUSCH.

UCI is transmitted on PUCCH. If the terminal is transmitting data on the PUSCH, the PUCCH and the PUSCH may be simultaneously transmitted in principle, that is, the UCI is retained in the PUCCH. However, this increases the Cubic Metric (Cubic Metric); furthermore, if the requirement of out-of-band transmission is to be met at a higher transmission power and the PUSCH and PUCCH are transmitted simultaneously, the interval in the frequency domain is large, which may pose a challenge to Radio Frequency (RF) implementation. Therefore, in general, if there is time coincidence between the PUCCH resource requiring UCI transmission and the PUSCH resource, and the base station guarantees that the condition of UCI multiplexing processing time is satisfied when scheduling the PUSCH, UCI and data are multiplexed on the PUSCH, avoiding simultaneous transmission of PUCCH.

And secondly, an uplink transmission skipping function defined by a Medium Access Control (MAC) layer.

The MAC layer defines a procedure in which the terminal performs uplink transmission skip (UL skip). The MAC entity will not generate a MAC Protocol Data Unit (PDU) for a Hybrid automatic repeat request (HARQ) entity if the following conditions are met:

1. the MAC entity configures a parameter skippelinktxdynamic, and the value of the parameter is set to true (true), and the MAC locates to the HARQ entity indicated in the uplink grant (UL grant).

2. The UL grant does not have an aperiodic Channel State Indication (CSI) request for this PUSCH transmission.

3. A MAC PDU includes zero MAC Service Data Units (SDUs).

4. The MAC PDU contains only a periodic Buffer Status Report (BSR) and no data available for any Logical Channel Group (LCG), or the MAC PDU contains only a padding BSR.

And thirdly, scheduling time of a physical layer PUSCH.

The time interval between the ending symbol of PDCCH for scheduling PUSCH and the starting symbol of PUSCH is at least T_proc,2＝max((N₂+d_2,1)(2048+144)·κ2^-μ·T_C,d_2,2)；

Wherein N is₂Determined based on the values of μ in tables one and two below.

If the first symbol of PUSCH consists of only Demodulation Reference Signal (DMRS), d_2,10, otherwise d_2,1＝1；

If DCI triggers a Bandwidth Part (BWP) switch, d_2,2Equal to the switching time, otherwise d_2,2＝0。

Table one:

table two:

μ	PUSCH preparation time N₂(number of symbols)
		0	5
1	5.5
		2	Frequency range 1 of 11

And fourthly, multiplexing time of the UCI of the physical layer.

When a single slot (slot) PUCCH overlaps with a single slot PUCCH or PUSCH, the UE will multiplex all UCI on one PUCCH or PUSCH using the existing multiplexing rule, if there are multiple PUSCH/PUCCHs overlapping, the time interval from the last symbol of any PDSCH to the start symbol of the earliest PUCCH/PUSCH in the overlapping PUCCH/PUSCH is

As the maximum value of the processing time of all PDSCHs, i.e.

Wherein the processing time of the ith PDSCH is as follows:

wherein d is_1,1Related to DMRS configuration, PDCCH, and PDSCH configuration.

Likewise, the time interval from the last symbol of any PDCCH to the starting symbol of the earliest PUCCH/PUSCH in the overlapping PUCCH/PUSCHsIs composed of

Is the maximum value of the processing time of all PUSCHs, i.e.

Wherein the processing time of the ith PUSCH is

When the PUSCH of the terminal enables the UL blanking function and there is no data transmission required to be transmitted in the terminal data memory, the UL blanking function allows the user to ignore the scheduling of the base station and not perform uplink transmission even if the base station schedules the user for data transmission. However, in the above case, when there is a resource conflict between the PUCCH and the dynamically scheduled PUSCH, the terminal may choose to include the following two:

1. not generating PUSCH, and transmitting UCI on PUCCH;

In the existing MAC layer protocol, since the resource overlap between the physical layer PUCCH and the PUSCH is not visible to the MAC layer, the MAC layer cannot judge whether to generate a MAC PDU for multiplexing UCI when there is no data in the terminal data memory and UL blanking is enabled. Particularly, when a logical channel priority principle is configured and/or a protocol agrees on a MAC priority principle, the uplink control information transmission method is provided for the situation.

The uplink control information transmission method provided by the embodiments of the present application is described in detail below with reference to the accompanying drawings through some embodiments and application scenarios thereof.

Referring to fig. 2, fig. 2 is a flowchart of an uplink control information transmission method provided in an embodiment of the present application, where the method is executed by a terminal, and as shown in fig. 2, the method includes the following steps:

step 201, receiving configuration information sent by a network side device, wherein the configuration information enables an uplink transmission skipping function of the terminal;

in this embodiment of the present application, a parameter skippalinktxdynamic may be configured by an MAC entity of a network side device, and when a value of the parameter is set to true (true), it may be understood that a terminal is configured with an uplink transmission skip function. Under the condition of configuring the uplink transmission skipping function, if the terminal has no data to be transmitted, and the network side equipment performs dynamic scheduling, the terminal can ignore the dynamic scheduling of the network side equipment and skip the uplink transmission scheduled this time, thereby avoiding resource waste.

Step 202, determining the transmission behavior of the uplink control information carried on the Physical Uplink Shared Channel (PUSCH) and the Physical Uplink Control Channel (PUCCH) according to a target priority principle and the priority sequence of the uplink transmission skip function under the condition that resources are overlapped on the time domain;

In this embodiment of the application, the PUSCH to be transmitted may be a PUSCH with Dynamic Grant (DG), or a PUSCH with Configured Grant (CG).

It should be understood that the time domain resource overlapping may be understood as resource collision, for example, there is resource overlapping of the PUSCH and the PUCCH in the time domain, and it may be understood that resource collision occurs in the PUSCH and the PUCCH.

The logical channel priority rule refers to a priority of the MAC layer, and may be understood as a logical channel prioritization (LCH-based prioritization) rule, and the logical channel prioritization rule may be configured for the terminal by the network side device. For example, in one embodiment, the logical channel priority principle includes: and the MAC determines a target uplink authorization with priority according to the priority of the logical channel mapped by the data, and generates an MAC Protocol Data Unit (PDU) according to the target uplink authorization, wherein the target uplink authorization is dynamic scheduling or configuration authorization. For example, in some embodiments, the MAC layer may determine that the CG or the DG is prioritized (prioritized) or de-prioritized (de-prioritized) according to the priority of the logical channel to which the data is mapped, and may generate the MAC PDU according to the prioritized uplink grant.

The MAC priority principle described above can be understood as a MAC priority principle. Optionally, in some embodiments, the MAC priority principle includes: and when the dynamically scheduled PUSCH is overlapped with the PUSCH resource with the authorization configuration, the PDU of the dynamically scheduled PUSCH is preferentially generated.

And according to the target priority principle and the priority order of the uplink transmission skipping function, the corresponding terminal has different operation behaviors executed on the PUSCH based on the target priority principle and the uplink transmission skipping, so that the transmission behaviors of the UCI are different. Optionally, in some embodiments, the transmission behavior of the UCI may include any one of:

discarding the uplink control information;

carrying the uplink control information on the PUCCH for transmission;

multiplexing the uplink control information on a dynamically scheduled PUSCH for transmission;

and multiplexing the uplink control information on a PUSCH with configuration authorization for transmission.

Optionally, in some embodiments, the determining, according to the target priority rule and the uplink transmission skip function priority order, a transmission behavior of the uplink control information carried on the PUCCH includes any one of:

under the condition that the terminal is configured with the logical channel priority principle, determining the transmission behavior of the uplink control information according to the logical channel priority principle and the priority sequence of the uplink transmission skipping function;

and under the condition that the terminal is not configured with the logical channel priority principle, determining the transmission behavior of the uplink control information according to the MAC priority principle and the priority sequence of the uplink transmission skipping function.

In this embodiment of the present application, the protocol may agree with the MAC priority principle or may not agree with the MAC priority principle, and in the case that the terminal is configured with the logical channel priority principle, it can be understood that, no matter whether the protocol agrees with the MAC priority principle, only the logical channel priority principle is considered at this time, that is, in the case that the protocol agrees with the MAC priority principle, the logical channel priority principle takes precedence over the MAC priority principle. And determining the transmission behavior of the uplink control information according to the MAC priority principle and the priority sequence of the uplink transmission skipping function aiming at the condition that the terminal is not configured with the logical channel priority principle and the MAC priority principle is agreed by a default protocol.

Optionally, in some embodiments, the determining, according to the logical channel priority rule and the priority order of the uplink transmission skip function, the transmission behavior of the uplink control information includes any one of:

determining the transmission behavior of the uplink control information in priority order of the logical channel priority principle prior to the uplink transmission skipping function;

and determining the transmission behavior of the uplink control information according to the priority order of the priority principle of the uplink transmission skipping function prior to the logical channel.

In this application, the priority order may be understood as that a logical channel priority rule takes precedence over the uplink transmission skip function, or that the uplink transmission skip function takes precedence over the logical channel priority rule. Specifically, the priority may be determined by a protocol convention, a network side device, or a terminal, which is not further limited herein. It should be understood that, when autonomously determined by the terminal, the terminal may report the determined priority order to the network side device. When the network side device determines, the network side device may configure the priority order to the terminal.

Optionally, the PUSCH includes a CG PUSCH having a configuration grant with resource overlapping in a time domain and a DG PUSCH having a dynamically scheduled physical uplink shared channel, and priorities of the CG PUSCH, the DG PUSCH and the PUCCH are the same in a physical layer, and only in a case where the CG PUSCH and the PUCCH have resource overlapping in the time domain, a transmission behavior of the UCI satisfies at least one of the following:

if the logical channel priority principle is prior to the uplink transmission skipping function, and the logical channel priority of the DG PUSCH is higher than that of the CG PUSCH, the transmission behavior of the UCI is a first transmission behavior;

if the logical channel priority principle is prior to the uplink transmission skipping function and the logical channel priority of the CG PUSCH is higher than the logical channel priority of the DG PUSCH, the transmission behavior of the UCI is to multiplex the UCI on the CG PUSCH for transmission;

if the uplink transmission skipping function is prior to the logical channel priority principle and the logical channel priority of the DG PUSCH is higher than that of the CG PUSCH, the transmission behavior of the UCI is a second transmission behavior;

if the uplink transmission skipping function is prior to the logical channel priority principle and the logical channel priority of the CG PUSCH is higher than the logical channel priority of the DG PUSCH, the transmission behavior of the UCI is to multiplex the UCI on the DG PUSCH for transmission;

wherein the first transmission behavior comprises any one of: transmitting the UCI bearer on the PUCCH, dropping the UCI, and multiplexing the UCI for transmission on the CG PUSCH; the second transmission behavior comprises any of: transmitting the UCI bearer on the PUCCH, dropping the UCI, and multiplexing the UCI for transmission on the CG PUSCH.

It should be noted that, in the physical layer, the PUSCH or PUCCH may be configured as priority index 0 or priority index 1, and is low priority when configured as 0 and high priority when configured as 1; when not configured, the priority index is 0. When the PUSCH and PUCCH are configured with the same priority index, it can be understood that the PUSCH and PUCCH have the same physical layer priority.

Optionally, the PUSCH includes a CG PUSCH and a DG PUSCH having resource overlapping in a time domain, and priorities of the CG PUSCH, the DG PUSCH and the PUCCH are the same in a physical layer, and only in a case where the DG PUSCH and the PUCCH have resource overlapping in the time domain, a transmission behavior of the UCI satisfies at least one of:

if the logical channel priority principle is prior to the uplink transmission skipping function and the logical channel priority of the DG PUSCH is higher than that of the CG PUSCH, the transmission behavior of the UCI is to multiplex the UCI on the DG PUSCH for transmission;

if the logical channel priority principle has priority over the uplink transmission skipping function and the logical channel priority of the CG PUSCH is higher than that of the DG PUSCH, the transmission behavior of the UCI is a third transmission behavior;

if the uplink transmission skipping function is prior to the logical channel priority principle and the logical channel priority of the DG PUSCH is higher than that of the CG PUSCH, multiplexing the UCI on the DG PUSCH for transmission by the transmission behavior of the UCI;

if the uplink transmission skipping function is prior to the logical channel priority principle and the logical channel priority of the CG PUSCH is higher than the logical channel priority of the DG PUSCH, if the MAC does not generate a Protocol Data Unit (PDU) for the CG PUSCH, the transmission behavior of the UCI is to multiplex the UCI on the DG PUSCH for transmission;

wherein the third transmission behavior comprises any one of: transmitting the UCI bearer on the PUCCH, discarding the UCI, and multiplexing the UCI on the DG PUSCH.

Optionally, the PUSCH includes CG PUSCH and DG PUSCH with resource overlapping in a time domain, and a transmission behavior of the UCI satisfies at least one of:

transmitting the UCI on the low priority CG PUSCH and the high priority PUCCH only if there is an overlap in the time domain;

the transmission behavior of the UCI is a fourth transmission behavior only in the case that a CG PUSCH with high priority and the PUCCH with low priority overlap in a time domain;

the transmission behavior of the UCI is a fifth transmission behavior only if there is an overlap in the time domain of the CG PUSCH of low priority and the PUCCH of low priority;

transmitting the UCI in a manner that the UCI is multiplexed on a CG PUSCH only in the case that the CG PUSCH with high priority overlaps with the PUCCH with high priority in a time domain;

transmitting the UCI by carrying the UCI on a PUCCH only under the condition that a DG PUSCH with low priority and the PUCCH with high priority overlap on a time domain;

the transmission behavior of the UCI is a sixth transmission behavior only in a case where there is an overlap in a time domain between a high-priority DG PUSCH and a low-priority PUCCH;

the transmission behavior of the UCI is a seventh transmission behavior only if there is an overlap of a low-priority DG PUSCH and a low-priority PUCCH in a time domain;

the transmission behavior of the UCI multiplexes the UCI for transmission on a DG PUSCH only if there is an overlap in the time domain of a high priority DG PUSCH and a high priority the PUCCH;

wherein the fourth act of transmitting comprises: transmitting the UCI carried on the PUCCH, or discarding the UCI; the fifth transmission behavior comprises any one of: transmitting the UCI bearer on the PUCCH, discarding the UCI, and multiplexing the UCI on a CG PUSCH; the sixth transmission behavior comprises any one of: discarding the UCI and carrying the UCI on PUCCH for transmission; the seventh transmission behavior comprises any one of: transmitting the UCI bearer on the PUCCH, discarding the UCI, and multiplexing the UCI on a DG PUSCH.

Optionally, in some embodiments, determining the transmission behavior of the uplink control information according to the MAC priority rule and the uplink transmission skip function priority order includes any one of:

determining the transmission behavior of the uplink control information according to the priority order of the MAC priority principle prior to the uplink transmission skipping function;

and determining the transmission behavior of the uplink control information according to the priority order of the uplink transmission skipping function prior to the MAC priority principle.

In this application, the priority order may be understood as that the MAC priority rule takes precedence over the uplink transmission skip function, or that the uplink transmission skip function takes precedence over the MAC priority rule. Specifically, the priority order may be determined by a protocol convention, a network side device or a terminal, and is not further limited herein. It should be understood that, when autonomously determined by the terminal, the terminal may report the determined priority to the network side device. When the network side device determines, the network side device may configure the priority order to the terminal.

if the MAC priority principle has priority over the uplink transmission skip function, the transmission behavior of the UCI is to carry the UCI on a PUCCH for transmission;

and if the uplink transmission skipping function has priority over the MAC priority principle, the UCI is transmitted by multiplexing the UCI on a CG PUSCH.

Optionally, the PUSCH includes a CG PUSCH and a DG PUSCH having resource overlapping in a time domain, and priorities of the CG PUSCH, the DG PUSCH, and the PUCCH are the same in a physical layer, and only in a case where the DG PUSCH and the PUCCH have resource overlapping in the time domain, the transmission behavior of the UCI multiplexes the UCI on the DG PUSCH for transmission.

Optionally, the PUSCHs include CG PUSCHs and DG PUSCHs with resource overlapping in a time domain, and a transmission behavior of the UCI satisfies at least one of:

transmitting the UCI over the PUCCH only if there is overlap in the time domain between the CG PUSCH of low priority and the PUCCH of high priority;

the transmission behavior of the UCI is an eighth transmission behavior only in the case that there is an overlap in the time domain between a CG PUSCH of high priority and the PUCCH of low priority;

transmitting the UCI on the low priority PUCCH only if there is an overlap in the time domain of the CG PUSCH and the PUCCH;

transmitting the UCI by carrying the UCI on a PUCCH only under the condition that the DG PUSCH with low priority and the PUCCH with high priority have overlap on a time domain;

the transmission behavior of the UCI is a ninth transmission behavior only in a case where there is an overlap in a time domain between a high-priority DG PUSCH and a low-priority PUCCH;

the transmission behavior of the UCI is a tenth transmission behavior only if there is an overlap in a time domain of a low-priority DG PUSCH and a low-priority PUCCH;

transmitting the UCI in a manner of multiplexing the UCI on a DG PUSCH only in the case that the high-priority DG PUSCH and the high-priority PUCCH are overlapped on a time domain;

wherein the eighth transmission behavior comprises any one of: transmitting and discarding the UCI carried on a PUCCH; the ninth transmission behavior comprises any one of: discarding the UCI and carrying the UCI on PUCCH for transmission; the tenth transmission behavior comprises any of: discarding the UCI and multiplexing the UCI for transmission on a DG PUSCH.

The PUSCH may be the first PUSCH dynamically scheduled or may be a PUSCH configured with an authorization. In the embodiment of the present application, the first PUSCH may be dynamically scheduled by the first DCI; the above-mentioned configuration authorized PUSCHs may include a second PUSCH authorized by a second DCI activation (enable) configuration authorization, or a third PUSCH authorized by a network side device through RRC configured configuration.

In this embodiment of the present application, the second DCI may be a DCI Configured with a Scheduling Radio Network Temporary identity (CS-RNTI) scrambling code.

It should be understood that after the network side device activates a second PUSCH configured with the grant through the second DCI, the network side device may periodically configure resources of the second PUSCH for the terminal. For a third PUSCH configured by the network side device and authorized by configuration, the network side device may periodically configure a resource of the third PUSCH for the terminal.

Optionally, in some embodiments, a suspended PUSCH transmission indication field for indicating information of PUSCH suspended transmission may be added in DCI for UL scheduling DG PUSCH; a PUSCH transmission indication field for indicating information of PUSCH transmission suspension may be added to DCI scrambled by CS-RNTI. For example, in some optional embodiments, the method may further include:

receiving target DCI, wherein the target DCI carries first indication information, the first indication information is used for indicating pause of target transmission, the target transmission is PUSCH transmission of dynamic scheduling or PUSCH transmission of configuration authorization scheduling, and the target DCI is DCI used for dynamic scheduling of PUSCH or DCI used for configuring and scheduling radio network temporary identifier scrambling CS-RNTI.

In this embodiment of the application, the first indication information may be information in the suspended PUSCH transmission indication field, and may include N bits, where N is a positive integer, for example. Specifically, the higher layer may configure a deactivation status list (config grant type2 deactivating statelist) parameter, and determine one or more PUSCH sets corresponding to each code point (codepoint) according to the parameter, where the first indication information is used to indicate a corresponding code point value. In an embodiment, taking the above target transmission as CG PUSCH, and taking the value of N as 4 as an example, the CG PUSCH which needs to be suspended corresponding to the code point indicated by the first indication information may be determined based on table three below.

A third table:

code point	Pausing
		0000	UL CG PUSCHs 1 and 2
0001	UL CG PUSCHs 3 and 4
		0010	UL CG PUSCH 5
···	···

It should be understood that if the higher layer is not configured with the configuredgmentconfigtype 2 deactivating statelist parameter, each code point corresponds to one CG PUSCH.

Optionally, the targeted DCI may suspend CG PUSCH transmission 1 time, may suspend CG PUSCH transmission multiple times, and if the PUSCH transmission is suspended multiple times, the suspended transmission times also need to be indicated in the DCI. In other words, in some optional embodiments, the target DCI further carries second indication information, where the second indication information is used to indicate the number of times that the target transmission is suspended.

In the embodiment of the present application, the second indication information and the first indication information may be located in the same indication field or in different indication fields, and when the second indication information and the first indication information are located in the same indication field, the second indication information may belong to information in the suspended PUSCH transmission indication field.

Further, in an optional embodiment, a priority change indication field may be added in DCI for UL scheduling of DG PUSCH or DCI scrambled by CS-RNTI. The priority change indication field is used to change the priority of CG PUSCHs, e.g., change a CG PUSCH of high priority to a CG PUSCH of low priority. In other words, in the embodiment of the present application, third indication information for indicating a change in priority of CG PUSCH is included in DCI for UL scheduling DG PUSCH or DCI scrambled by CS-RNTI. Of course, the indication may also be used to change the priority of the DG PUSCH.

Further, when the network side device determines that the PUSCH to be transmitted by the terminal and the PUCCH have resource overlap in the time domain, the time-frequency resource of the PUSCH to be transmitted may be re-indicated through the first DCI. Taking the PUSCH to be transmitted as the CG PUSCH as an example for explanation, as shown in fig. 3, when there is resource overlap between the CG PUSCH and the PUCCH in the time domain and there is resource overlap with the DG PUSCH in the time domain, the time-frequency resource of the CG PUSCH may be re-indicated by the first DCI, for example, the existing time-frequency resource indication domain may be added or reused, and the transmission resource of the CG PUSCH is updated, so that the updated CG PUSCH and the DG PUSCH are not overlapped.

Generally, the first DCI may be understood as a DCI scheduling CG PUSCH transmission, but may be other DCIs, which is not further limited herein.

For better understanding of the present application, the transmission behavior of UCI carried on PUCCH is described in detail below for different priorities.

In the first embodiment, for the PUSCH and the PUCCH having the same priority in the physical layer, the following cases are included:

in case 1, as shown in fig. 4, CG PUSCH and DG PUSCH time domain resources of the same physical layer priority are overlapped, CG PUSCH overlaps PUCCH time domain resources of the same priority, DG PUSCH does not overlap PUCCH time domain resources of the same priority, and PUCCH precedes DG PUSCH.

Optionally, in some embodiments, if the terminal is configured with a logical channel priority rule, and the logical channel priority rule takes precedence over the UL skiping function, the transmission behavior of the UCI satisfies at least one of the following:

if the logic channel priority of the DG PUSCH is higher than that of the CG PUSCH and the DG PUSCH has data, if the execution sequence of multiplexing the CG PUSCH and the PUCCH is that a physical layer waits for the MAC to generate the PDU first and then determines whether UCI multiplexing is carried out or not, the UCI is carried on the PUCCH for transmission; if the execution sequence of multiplexing the CG PUSCH and the PUCCH is that the physical layer firstly carries out UCI multiplexing and then waits for the MAC to generate PDU, the UCI is discarded because the CG PUSCH and the DG PUSCH collide;

if the logic channel priority of the DG PUSCH is higher than that of the CG PUSCH and the DG PUSCH has no data, the MAC generates a PDU for the CG PUSCH, and UCI is multiplexed on the CG PUSCH for transmission;

and if the priority of the logic channel of the CG PUSCH is higher than that of the logic channel of the DG PUSCH, the UCI is multiplexed and transmitted on the CG PUSCH.

It should be understood that, when there is resource overlap between CG PUSCH and DG PUSCH in the time domain, if the logical channel priority of DG PUSCH is higher than that of CG PUSCH, CG PUSCH is dropped or cancelled.

It should be noted that, if there is no data in the DG PUSCH, the MAC will not generate a PDU for the DG PUSCH. In other words, in the embodiment of the present application, if the logical channel priority of the DG PUSCH is higher than the logical channel priority of the CG PUSCH, and the DG PUSCH has no data, the MAC will generate a PDU for the CG PUSCH, and the UCI multiplexing is transmitted on the CG PUSCH, or it can be understood that if the logical channel priority of the DG PUSCH is higher than the logical channel priority of the CG PUSCH and the MAC does not generate a PDU for the DG PUSCH, the MAC will generate a PDU for the CG PUSCH, and the UCI multiplexing is transmitted on the CG PUSCH.

Optionally, in some embodiments, if the terminal is configured with a logical channel priority rule, and the UL skiping function takes precedence over the logical channel priority rule, the transmission behavior of the UCI satisfies at least one of the following:

under the condition that the MAC generates the PDU for the CG PUSCH and the logic channel priority of the DG PUSCH is higher than that of the CG PUSCH (namely the priority of the DG PUSCH is high), and the DG PUSCH has no data, the UCI is multiplexed on the CG PUSCH, and the DG PUSCH is not sent at the moment;

generating PDU for CG PUSCH by MAC, wherein the priority of a logic channel of the CG PUSCH is higher than that of the logic channel of the DG PUSCH, and the UCI is multiplexed on the CG PUSCH under the condition that the DG PUSCH has data, and the DG PUSCH is not sent at the moment;

and under the condition that the MAC generates the PDU for the CG PUSCH, the logic channel priority of the CG PUSCH is higher than that of the DG PUSCH, and the DG PUSCH has no data, the UCI multiplexing is transmitted on the CG PUSCH.

Optionally, in some embodiments, if the terminal is not configured with the logical channel priority rule, and the MAC priority rule takes precedence over the UL skiping function, the transmission behavior of the UCI is: UCI is carried on PUCCH for transmission.

Optionally, in some embodiments, if the terminal is not configured with the logical channel priority rule and the UL skiping function takes precedence over the MAC priority rule, the transmission behavior of the UCI is: UCI multiplexing is transmitted on CG PUSCH.

Optionally, there is also an error case in case 1, for example, the MAC generates PDU for CG PUSCH, and the logical channel priority of DG PUSCH is higher than that of CG PUSCH, and DG PUSCH has data. It should be understood that in the case of error case, UCI transmission is based on terminal implementation, e.g., the terminal determines itself whether to discard or multiplex.

In case 2, as shown in fig. 5, CG PUSCH and DG PUSCH time domain resources of the same physical layer priority overlap, DG PUSCH overlaps with PUCCH time domain resources of the same priority, CG PUSCH does not overlap with PUCCH time domain resources of the same priority, and CG PUSCH precedes.

if the logic channel priority of the DG PUSCH is higher than that of the CG PUSCH, UCI multiplexing is transmitted on the DG PUSCH;

if the priority of the logic channel of the CG PUSCH is higher than that of the logic channel of the DG PUSCH and the MAC generates one PDU (driver) for the CG PUSCH, if the execution sequence of multiplexing the DG PUSCH and the PUCCH is that a physical layer firstly waits for the MAC to generate the PDU and then determines whether UCI multiplexing is carried out or not, the UCI is carried on the PUCCH for transmission; if the execution sequence of multiplexing the DG PUSCH and the PUCCH is that the physical layer firstly carries out UCI multiplexing and then waits for the MAC to generate the PDU, the UCI is discarded because the CG PUSCH conflicts with the DG PUSCH;

and if the logic channel priority of the CG PUSCH is higher than that of the DG PUSCH and the MAC is not one PDU (protocol data unit) of the CG PUSCH driver, the UCI multiplexing is transmitted on the DG PUSCH.

if the priority of the logic channel of the DG PUSCH is higher than that of the logic channel of the CG PUSCH, the UCI is multiplexed and transmitted on the DG PUSCH;

and if the priority of the logic channel of the CG PUSCH is higher than that of the logic channel of the DG PUSCH and the MAC is not a PDU of the CG PUSCH driver, the UCI is multiplexed and transmitted on the DG PUSCH.

Optionally, in some embodiments, if the terminal is not configured with the logical channel priority rule, and the MAC priority rule takes precedence over the UL skiping function, the transmission behavior of the UCI is: UCI multiplexing is transmitted on DG PUSCH.

Optionally, in some embodiments, if the terminal is not configured with the logical channel priority rule and the UL skiping function takes precedence over the MAC priority rule, the transmission behavior of the UCI is: UCI multiplexing is transmitted on DG PUSCH.

Optionally, in case 2, there is also an error condition, for example, the CG PUSCH has a higher logical channel priority than the DG PUSCH, and the MAC is a CG PUSCH driver PDU.

In case 3, as shown in fig. 6, CG PUSCH and DG PUSCH time domain resources of the same physical layer priority are overlapped, and DG PUSCH does not overlap with PUCCH time domain resources of the same priority, CG PUSCH overlaps with PUCCH time domain resources of the same priority, and DG PUSCH precedes by PUCCH.

if the logic channel priority of the DG PUSCH is higher than that of the CG PUSCH and the DG PUSCH has data, if the execution sequence of multiplexing the CG PUSCH and the PUCCH is that a physical layer waits for the MAC to generate the PDU first and then determines whether UCI multiplexing is carried out or not, the UCI is carried on the PUCCH for transmission; if the execution sequence of CG PUSCH and PUCCH multiplexing is that the physical layer firstly carries out UCI multiplexing and then waits for the MAC to generate PDU, the UCI is discarded;

if the logic channel priority of the DG PUSCH is higher than that of the CG PUSCH and the DG PUSCH has no data, the MAC generates a PDU for the CG PUSCH and the UCI is multiplexed on the CG PUSCH;

and if the priority of the logic channel of the CG PUSCH is higher than that of the logic channel of the DG PUSCH, the UCI multiplexing is transmitted on the CG PUSCH.

if the logic channel priority of the DG PUSCH is higher than that of the CG PUSCH and the DG PUSCH has no data, the UCI is multiplexed and transmitted on the CG PUSCH;

if the priority of the logic channel of the CG PUSCH is higher than that of the logic channel of the DG PUSCH, UCI multiplexing is transmitted on the CG PUSCH;

In case 4, as shown in fig. 7, CG PUSCH and DG PUSCH time domain resources of the same physical layer priority overlap, DG PUSCH overlaps with PUCCH time domain resources of the same priority, CG PUSCH does not overlap with PUCCH time domain resources of the same priority, and CG PUSCH precedes PUCCH succeeds.

if the priority of the logic channel of the CG PUSCH is higher than that of the logic channel of the DG PUSCH and the MAC is a CG PUSCH driver PDU, if the execution sequence of multiplexing the DG PUSCH and the PUCCH is that a physical layer waits for the MAC to generate the PDU first and then determines whether UCI multiplexing is carried out or not, the UCI is carried on the PUCCH for transmission; if the execution sequence of multiplexing the DG PUSCH and the PUCCH is that the physical layer firstly carries out UCI multiplexing and then waits for the MAC to generate the PDU, the UCI is discarded because the CG PUSCH conflicts with the DG PUSCH;

if the logic channel priority of the DG PUSCH is higher than that of the CG PUSCH, the UCI is multiplexed and transmitted on the DG PUSCH;

and if the priority of the logic channel of the CG PUSCH is higher than that of the logic channel of the DG PUSCH and the MAC does not give a PDU to the CG PUSCH driver, the UCI is multiplexed on the DG PUSCH.

Optionally, in some embodiments, if the terminal is not configured with the logical channel priority rule, and the MAC priority rule takes precedence over the UL skiping function, the transmission behavior of the UCI satisfies: UCI multiplexing is transmitted on DG PUSCH.

Optionally, in some embodiments, if the terminal is not configured with the logical channel priority rule, and the UL skiping function takes precedence over the MAC priority rule, the transmission behavior of the UCI satisfies: UCI multiplexing is transmitted on DG PUSCH.

Optionally, there is also an error case in case 4, for example, the MAC generates a PDU for CG PUSCH and the CG PUSCH has a higher logical channel priority than the DG PUSCH.

Embodiment two, for the PUSCHs and PUCCHs of different priorities. The following cases are included:

in case 5, as shown in fig. 8, for CGPUSCH and DG PUSCH time domain resources of Low Priority (LP) in the physical layer overlap, and LP CG PUSCH overlaps with PUCCH time domain resources of High Priority (HP), LP DG PUSCH does not overlap with PUCCH time domain resources of HP, and HP PUCCH precedes LP DG PUSCH and lags LP DG PUSCH. At this time, the transmission behavior of the UCI corresponding to at least one priority order is: UCI is carried on PUCCH for transmission.

In case 6, for the physical layer LP, CG PUSCH and DG PUSCH time domain resources overlap, LP CG PUSCH overlaps with HP PUCCH time domain resources, LP DG PUSCH does not overlap with HP PUCCH time domain resources, LP DG PUSCH precedes, and HP PUCCH succeeds. At this time, the transmission behavior of the UCI corresponding to at least one priority order is: UCI is carried on PUCCH for transmission.

In case 7, for the physical layer LP CG PUSCH and HP DG PUSCH time domain resources overlap, and LP CG PUSCH overlaps with HP PUCCH time domain resources, HP DG PUSCH does not overlap with HP PUCCH time domain resources, and HP PUCCH is first and HP DG PUSCH is second. At this time, the transmission behavior of the UCI corresponding to at least one priority order is: UCI is carried on PUCCH for transmission.

In case 8, for the physical layer LP CG PUSCH and HP DG PUSCH time domain resources overlap, and LP CG PUSCH overlaps with HP PUCCH time domain resources, HP DG PUSCH does not overlap with HP PUCCH time domain resources, and HP DG PUSCH is before, and HP PUCCH is after. At this time, the transmission behavior of the UCI corresponding to at least one priority order is: UCI is carried on PUCCH for transmission.

In case 9, for the CG PUSCH and LP DG PUSCH time domain resources of the physical layer HP overlap, and HP CG PUSCH overlaps with the PUCCH time domain resources of the HP, LP DG PUSCH does not overlap with the PUCCH time domain resources of the HP, and HP PUCCH is before and LP DG PUSCH is after. At this time, the transmission behavior of the UCI corresponding to at least one priority order is: UCI multiplexing is transmitted on CG PUSCH.

In case 10, for the CG PUSCH and LP DG PUSCH time domain resources of the physical layer HP overlap, and the HP CG PUSCH overlaps with the PUCCH time domain resources of the HP, the LP DG PUSCH does not overlap with the PUCCH time domain resources of the HP, and the LP DG PUSCH is before and the HP PUCCH is after. At this time, the transmission behavior of the UCI corresponding to at least one priority satisfies: UCI multiplexing is transmitted on CG PUSCH.

In case 11, for the physical layer LP, DG PUSCH and HP CG PUSCH time domain resources overlap, and HP CG PUSCH overlaps with LP PUCCH time domain resources, LP DG PUSCH does not overlap with LP PUCCH time domain resources, and LP PUCCH is before and LP DG PUSCH is after.

if the MAC generates PDU for CG PUSCH, then UCI is discarded;

if the MAC does not generate a PDU for the CG PUSCH, the UCI bearer is transmitted on the PUCCH.

if the MAC generates PDU for CG PUSCH, then UCI is discarded;

Optionally, in some embodiments, if the terminal is not configured with the logical channel priority rule, and the MAC priority rule takes precedence over the UL skiping function, the transmission behavior of the UCI satisfies at least one of the following:

if the MAC generates PDU for CG PUSCH, UCI is carried on PUCCH for transmission;

if the MAC does not generate a PDU for the CG PUSCH, the UCI is discarded.

Optionally, in some embodiments, if the terminal is not configured with the logical channel priority rule and the UL skiping function takes precedence over the MAC priority rule, the transmission behavior of the UCI satisfies at least one of:

if the MAC generates PDU for CG PUSCH, then UCI is discarded;

In case 12, for the physical layer HP CG PUSCH and LP DG PUSCH time domain resources overlap, and HP CG PUSCH overlaps with LP PUCCH time domain resources, LP DG PUSCH does not overlap with LP PUCCH time domain resources, and LP DG PUSCH is before and LP PUCCH is after. At this time, the transmission behavior of the UCI corresponding to at least one priority satisfies at least one of the following:

if the MAC generates PDU for CG PUSCH, then UCI is discarded;

In case 13, for the physical layer HP and LP CG PUSCH time domain resources overlap, and HP DG PUSCH and LP PUCCH time domain resources do not overlap, LP CG PUSCH and LP PUCCH time domain resources overlap, and LP PUCCH is before and HP DG PUSCH is after.

if the DG PUSCH has data, if the execution sequence of multiplexing the CG PUSCH and the PUCCH is that a physical layer waits for the MAC to generate the PDU first and then determines whether UCI multiplexing is carried out or not, the UCI is carried on the PUCCH for transmission; if the execution sequence of CG PUSCH and PUCCH multiplexing is that the physical layer firstly carries out UCI multiplexing and then waits for the MAC to generate PDU, the UCI is discarded;

if the DG PUSCH has no data, the UCI is multiplexed and transmitted on the CG PUSCH under the condition that the MAC generates the PDU for the CG PUSCH.

if the DG PUSCH has data, the UCI is discarded;

if the DG PUSCH has no data, the UCI is multiplexed and transmitted on the CG PUSCH.

if the DG PUSCH has data, the UCI is discarded;

In case 14, for the physical layer HP and LP CG PUSCH time domain resources overlap, and HP DG PUSCH and LP PUCCH time domain resources do not overlap, LP CG PUSCH and LP PUCCH time domain resources overlap, and HP DG PUSCH is before and LP PUCCH is after.

if the DG PUSCH has data, the UCI is discarded;

Optionally, in some embodiments, if the terminal is not configured with the logical channel priority rule, and the MAC priority rule takes precedence over the UL skiping function, the transmission behavior of the UCI satisfies: UCI is carried on PUCCH for transmission.

Optionally, in some embodiments, if the terminal is not configured with the logical channel priority rule, and the UL skiping function takes precedence over the MAC priority rule, the transmission behavior of the UCI satisfies at least one of the following:

if the DG PUSCH has data, the UCI is discarded;

In case 15, for the physical layer HP and HP CG PUSCH time domain resources overlap, and HP DG PUSCH does not overlap with LP PUCCH time domain resources, HP CG PUSCH overlaps with LP PUCCH time domain resources, and LP PUCCH precedes and HP DG PUSCH follows.

if the MAC generates PDU for CG PUSCH, then UCI is discarded;

if the MAC generates PDU for CG PUSCH, then the UCI is discarded;

if the CG PUSCH has data, the UCI is discarded;

if CG PUSCH has no data, the UCI is carried on PUCCH for transmission.

In case 16, for the physical layer HP and HP CG PUSCH time domain resources overlap, and HP DG PUSCH and LP PUCCH time domain resources do not overlap, HP CG PUSCH and LP PUCCH time domain resources overlap, and HP DG PUSCH precedes and LP PUCCH succeeds. At this time, the transmission behavior of UCI is consistent with the case 15.

In case 17, for the physical layer HP CG PUSCH and LP DG PUSCH time domain resources overlap, and HP CG PUSCH does not overlap with LP PUCCH time domain resources, LP DG PUSCH overlaps with LP PUCCH time domain resources, and HP CG PUSCH precedes and LP PUCCH follows.

if the MAC sends a PDU to the CG PUSCH driver, if the execution sequence of multiplexing the DG PUSCH and the PUCCH is that the physical layer firstly waits for the MAC to generate the PDU and then determines whether UCI multiplexing is carried out or not, the UCI is carried on the PUCCH for transmission; if the execution sequence of multiplexing the DG PUSCH and the PUCCH is that the physical layer firstly carries out UCI multiplexing and then waits for the MAC to generate the PDU, the UCI is discarded;

if the MAC does not give a PDU to the CG PUSCH driver, the UCI multiplexing is transmitted on the DG PUSCH.

if the MAC is a PDU of CG PUSCH deliverer, the UCI is multiplexed and transmitted on a DG PUSCH;

if the MAC is not CG PUSCH driver PDU, then the UCI is discarded.

if the MAC is CG PUSCH driver PDU, the UCI is carried on the PUCCH for transmission;

if the MAC is not CG PUSCH driver PDU, the UCI multiplexing is transmitted on the DG PUSCH.

if the MAC is CG PUSCH driver PDU, the UCI is discarded;

In case 18, for the CG PUSCH and LP DG PUSCH time domain resources of the physical layer HP overlap, and the HP CG PUSCH does not overlap with the PUCCH time domain resources of the HP, the LP DG PUSCH overlaps with the PUCCH time domain resources of the HP, and the HP CG PUSCH precedes and the HP PUCCH succeeds. At this time, the transmission behavior of the UCI corresponding to at least one priority satisfies: UCI is carried on PUCCH for transmission.

In case 19, for the physical layer HP and HP CG PUSCH time domain resources overlap, and HP CG PUSCH does not overlap with LP PUCCH time domain resources, HP DG PUSCH overlaps with LP PUCCH time domain resources, and HP CG PUSCH precedes and LP succeeds PUCCH. At this time, the transmission behavior of the UCI corresponding to at least one priority satisfies at least one of the following:

if the DG PUSCH has data, the UCI is discarded;

if the DG PUSCH has no data, the UCI bearer is transmitted on the PUCCH.

In case 20, for the physical layer HP and LP CG PUSCH time domain resources overlap, and LP CG PUSCH and LP PUCCH time domain resources do not overlap, HP DG PUSCH and LP PUCCH time domain resources overlap, and LP CG PUSCH is before and LP PUCCH is after. At this time, the transmission behavior of UCI coincides with case 19.

In case 21, for the physical layer LP CG PUSCH and LP DG PUSCH time domain resources overlap, and LP CG PUSCH does not overlap with HP PUCCH time domain resources, LP DG PUSCH overlaps with HP PUCCH time domain resources, and LP CG PUSCH precedes and HP succeeds. At this time, the transmission behavior of the UCI corresponding to at least one priority satisfies: UCI is carried on PUCCH for transmission.

In case 22, for the physical layer LP CG PUSCH and HP DG PUSCH time domain resources overlap, and LP CG PUSCH does not overlap with HP PUCCH time domain resources, HP DG PUSCH overlaps with HP PUCCH time domain resources, and LP CG PUSCH precedes and HP PUCCH succeeds. At this time, the transmission behavior of the UCI corresponding to at least one priority satisfies: UCI multiplexing is transmitted on DG PUSCH.

Optionally, for the error case, the UE does not expect network side device scheduling. For example, the UE does not want to configure LCH-prioritization, and the UL puncturing principle takes precedence over the LCH-prioritization principle: the UE does not expect that the logic channel priority of DG PUSCH configured by the network side equipment is higher than that of the CG PUSCH, the MAC generates PDU for the CG PUSCH, and the DG PUSCH has data.

It should be noted that, for the CG PUSCH or DG PUSCH repetition scheme, it needs to be considered whether the above overlapping situation is the first transmission or other transmission. In the above case 9, the CG PUSCH is repeated 4 times, and transmission of each CG PUSCH is described as an example.

If the overlapping CG PUSCH is the first transmission. For the first transmission, the HP PUCCH is carried on the CG PUSCH, then for other transmissions, in an embodiment, it may be that each transmission carries the same UCI. In another embodiment, UCI may be transmitted only on the CG PUSCH for the first time, and other CG PUSCHs repeatedly transmitted do not carry UCI.

Alternatively, if CG PSUCH dropping is caused according to a certain priority order in the above case, in some embodiments, only the CG PUSCH transmitted for the first time may be dropped without affecting the transmission of other CG PUSCHs. In other embodiments, all other repeatedly transmitted CG PUSCHs may be dropped.

Alternatively, if the CG PUSCH has no data, a MAC PDU of padding bits is generated according to the UL padding principle. In some embodiments, it may be the first time a padding bit MAC PDU is generated, when UCI is transmitted with this PDU over the CG PUSCH. In other embodiments, all CG PUSCHs may transmit PDUs of UCI and padding bits.

If the overlaid CG PUSCH is not the first transmission, assume the overlaid CG PUSCH is the second transmission of the CG PUSCH. At this time, optionally, in some embodiments, UCI is only carried in the overlapped transmission bearer, i.e., UCI is carried in the second transmission bearer, and other CG PUSCHs are not carried. In other embodiments, UCI is carried on both overlapping transmissions and thereafter, i.e., UCI is carried on the second, third, and fourth CG PUSCHs.

Alternatively, if the overlapping CG pscchs are dropped according to a certain priority order in the above case, in some embodiments, only the CG PUSCHs of the overlapping transmission may be dropped without affecting the transmission of other CG PUSCHs, i.e. the first, third, and fourth CG PUSCHs are still transmitted. In other embodiments, it is also possible to drop all remaining CG PUSCHs of other repeated transmissions, i.e. only transmitted for the first time.

Alternatively, if the CG PUSCH has no data, a MAC PDU of padding bit is generated according to the UL padding principle. In some embodiments, the MAC PDU of padding bits is generated only at the overlapping CG PUSCH, at which time UCI is transmitted over the CG PUSCH along with the PDU. In other embodiments, the PDU including UCI and padding bit transmitted by the repeated and following CG PUSCHs may also be used.

It should be noted that, in the uplink control information transmission method provided in the embodiment of the present application, the execution main body may be an uplink control information transmission device, or a control module in the uplink control information transmission device, configured to execute the uplink control information transmission method. In the embodiment of the present application, an uplink control information transmission apparatus performs an uplink control information transmission method as an example, and the uplink control information transmission apparatus provided in the embodiment of the present application is described.

Referring to fig. 9, fig. 9 is a structural diagram of an uplink control information transmission apparatus according to an embodiment of the present application, and as shown in fig. 9, the uplink control information transmission apparatus 900 includes:

a receiving module 901, configured to receive configuration information sent by a network device, where the configuration information enables an uplink transmission skip function of the terminal;

a processing module 902, configured to determine, according to a target priority principle and a priority order of the uplink transmission skip function, a transmission behavior of uplink control information carried on a physical uplink shared channel PUSCH and the physical uplink control channel PUCCH when there is resource overlap in a time domain;

Optionally, the processing module 902 is configured to perform any of:

Optionally, the processing module 902 is specifically configured to execute any one of the following: determining the transmission behavior of the uplink control information in priority order of the logical channel priority principle prior to the uplink transmission skipping function;

if the uplink transmission skipping function has priority over the logical channel priority principle and the priority of the logical channel of the CG PUSCH is higher than that of the DG PUSCH, the transmission behavior of the UCI is to multiplex the UCI on the DG PUSCH for transmission;

wherein the first transmission behavior comprises any one of: transmitting the UCI bearer on the PUCCH, dropping the UCI, and multiplexing the UCI for transmission on the CG PUSCH; the second transmission behavior comprises any one of: transmitting the UCI bearer on the PUCCH, discarding the UCI, and multiplexing the UCI for transmission on the CG PUSCH.

if the logical channel priority principle is prior to the uplink transmission skipping function and the logical channel priority of the CG PUSCH is higher than the logical channel priority of the DG PUSCH, the transmission behavior of the UCI is a third transmission behavior;

wherein the fourth transmission behavior comprises: transmitting the UCI carried on the PUCCH, or discarding the UCI; the fifth transmission behavior comprises any one of: transmitting the UCI bearer on the PUCCH, discarding the UCI, and multiplexing the UCI on a CG PUSCH; the sixth transmission behavior comprises any one of: discarding the UCI and carrying the UCI on PUCCH for transmission; the seventh transmission behavior comprises any one of: transmitting the UCI bearer on the PUCCH, discarding the UCI, and multiplexing the UCI on a DG PUSCH.

Optionally, the processing module 902 is specifically configured to execute any one of the following: determining the transmission behavior of the uplink control information according to the priority order of the MAC priority principle prior to the uplink transmission skipping function;

transmitting the UCI in a manner of multiplexing the UCI on a CG PUSCH only in the case that the CG PUSCH with high priority overlaps with the PUCCH with high priority in a time domain;

wherein the eighth transmission behavior comprises any one of: transmitting and discarding the UCI carried on a PUCCH; the ninth transmission behavior comprises any one of: discarding the UCI and carrying the UCI on PUCCH for transmission; the tenth transmission behavior comprises any of: dropping the UCI and multiplexing the UCI for transmission on a DG PUSCH.

Optionally, the transmission behavior of the uplink control information includes any one of:

discarding the uplink control information;

carrying the uplink control information on the PUCCH for transmission;

Optionally, the logical channel priority principle includes: and the MAC determines a target uplink authorization with priority according to the priority of the logical channel mapped by the data, and generates an MAC Protocol Data Unit (PDU) according to the target uplink authorization, wherein the target uplink authorization is dynamic scheduling or configuration authorization.

Optionally, the MAC priority principle includes: and when the dynamically scheduled PUSCH is overlapped with the PUSCH resource configured with the authorization, the PDU of the dynamically scheduled PUSCH is preferentially generated.

Optionally, the receiving module 901 is further configured to: receiving target DCI, wherein the target DCI carries first indication information, the first indication information is used for indicating pause of target transmission, the target transmission is PUSCH transmission of dynamic scheduling or PUSCH transmission of configuration authorization scheduling, and the target DCI is DCI used for dynamic scheduling of PUSCH or DCI used for configuring and scheduling radio network temporary identifier scrambling CS-RNTI.

Optionally, the target DCI further carries second indication information, where the second indication information is used to indicate the number of times of suspension of the target transmission.

The uplink control information transmission apparatus provided in the embodiment of the present application can implement each process in the method embodiment of fig. 2, and is not described here again to avoid repetition.

The uplink control information transmission device in the embodiment of the present application may be a device, or may be a component, an integrated circuit, or a chip in a terminal. The device can be a mobile terminal or a non-mobile terminal. For example, the mobile terminal may include, but is not limited to, the type of the terminal 11 listed above, and the non-mobile terminal may be a server, a Network Attached Storage (NAS), a Personal Computer (PC), a television (television), a teller machine (teller machine), or a self-service machine (kiosk), and the embodiments of the present application are not limited in particular.

The uplink control information transmission device in the embodiment of the present application may be a device having an operating system. The operating system may be an Android (Android) operating system, an ios operating system, or other possible operating systems, and embodiments of the present application are not limited specifically.

The uplink control information transmission device provided in the embodiment of the present application can implement each process implemented by the method embodiments of fig. 2 to fig. 8, and achieve the same technical effect, and is not described here again to avoid repetition.

Optionally, as shown in fig. 10, an embodiment of the present application further provides a communication device 1000, which includes a processor 1001, a memory 1002, and a program or an instruction that is stored in the memory 1002 and is executable on the processor 1001, for example, when the program or the instruction is executed by the processor 1001, the process of the uplink control information transmission method embodiment is implemented, and the same technical effect can be achieved, and is not described herein again to avoid repetition.

Fig. 11 is a schematic hardware structure diagram of a terminal implementing various embodiments of the present application.

The terminal 1100 includes, but is not limited to: radio frequency unit 1101, network side device module 1102, audio output unit 1103, input unit 1104, sensor 1105, display unit 1106, user input unit 1107, interface unit 1108, memory 1109, processor 1110, and the like.

Those skilled in the art will appreciate that terminal 1100 can also include a power supply (e.g., a battery) for powering the various components, which can be logically coupled to processor 1110 via a power management system to facilitate managing charging, discharging, and power consumption via the power management system. The terminal structure shown in fig. 11 does not constitute a limitation of the terminal, and the terminal may include more or less components than those shown, or combine some components, or have a different arrangement of components, and thus will not be described again.

It should be understood that in the embodiment of the present application, the input Unit 1104 may include a Graphics Processing Unit (GPU) 11041 and a microphone 11042, and the Graphics processor 11041 processes image data of still pictures or video obtained by an image capturing device (such as a camera) in a video capturing mode or an image capturing mode. The display unit 1106 may include a display panel 11061, and the display panel 11061 may be configured in the form of a liquid crystal display, an organic light emitting diode, or the like. The user input unit 1107 includes a touch panel 11071 and other input devices 11072. A touch panel 11071, also called a touch screen. The touch panel 11071 may include two portions of a touch detection device and a touch controller. Other input devices 11072 may include, but are not limited to, a physical keyboard, function keys (e.g., volume control keys, switch keys, etc.), a trackball, a mouse, and a joystick, which are not described in detail herein.

In this embodiment of the application, the radio frequency unit 1101 receives downlink data from a network side device and then processes the downlink data to the processor 1110; in addition, the uplink data is sent to the network side equipment. In general, radio frequency unit 1101 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, and the like.

The memory 1109 may be used for storing software programs or instructions as well as various data. The memory 109 may mainly include a stored program or instruction area and a stored data area, wherein the stored program or instruction area may store an operating system, an application program or instruction (such as a sound playing function, an image playing function, etc.) required for at least one function, and the like. In addition, the Memory 1109 may include a high-speed random access Memory and may also include a nonvolatile Memory, which may be a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable Programmable PROM (EPROM), an Electrically Erasable Programmable ROM (EEPROM), or a flash Memory. Such as at least one magnetic disk storage device, flash memory device, or other non-volatile solid state storage device.

Processor 1110 may include one or more processing units; alternatively, processor 1110 may integrate an application processor that primarily handles operating systems, user interfaces, and applications or instructions, etc. and a modem processor that primarily handles wireless communications, such as a baseband processor. It will be appreciated that the modem processor described above may not be integrated into processor 1110.

The radio frequency unit 1101 is configured to receive configuration information sent by a network side device, where the configuration information is used to configure an uplink transmission skip function for the terminal;

a processor 1110, configured to receive configuration information sent by a network side device, where the configuration information enables an uplink transmission skip function of the terminal; under the condition that resources of a Physical Uplink Shared Channel (PUSCH) and a Physical Uplink Control Channel (PUCCH) are overlapped on a time domain, determining the transmission behavior of uplink control information carried on the PUCCH according to a target priority principle and the priority sequence of the uplink transmission skipping function;

It should be understood that, in this embodiment, the processor 1110 and the radio frequency unit 1101 can implement each process implemented by the terminal in the method embodiment of fig. 2, and are not described herein again to avoid repetition.

The embodiment of the present application further provides a readable storage medium, where a program or an instruction is stored on the readable storage medium, and when the program or the instruction is executed by a processor, the program or the instruction implements each process of the above uplink control information transmission method embodiment, and can achieve the same technical effect, and in order to avoid repetition, details are not repeated here.

The processor is the processor in the electronic device described in the above embodiment. The readable storage medium includes a computer readable storage medium, such as a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and so on.

The embodiment of the present application further provides a chip, where the chip includes a processor and a communication interface, the communication interface is coupled to the processor, and the processor is configured to run a network-side device program or an instruction, so as to implement each process of the above uplink control information transmission method embodiment, and achieve the same technical effect, and in order to avoid repetition, the details are not repeated here.

It should be understood that the chips mentioned in the embodiments of the present application may also be referred to as system-on-chip, system-on-chip or system-on-chip, etc.

It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element. Further, it should be noted that the scope of the methods and apparatus of the embodiments of the present application is not limited to performing the functions in the order illustrated or discussed, but may include performing the functions in a substantially simultaneous manner or in a reverse order based on the functions involved, e.g., the methods described may be performed in an order different than that described, and various steps may be added, omitted, or combined. In addition, features described with reference to certain examples may be combined in other examples.

Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner. Based on such understanding, the technical solutions of the present application may be embodied in the form of a software product, which is stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk) and includes instructions for enabling a terminal (such as a mobile phone, a computer, a server, an air conditioner, or a base station) to execute the method according to the embodiments of the present application.

While the present embodiments have been described with reference to the accompanying drawings, it is to be understood that the invention is not limited to the precise embodiments described above, which are meant to be illustrative and not restrictive, and that various changes may be made therein by those skilled in the art without departing from the spirit and scope of the invention as defined by the appended claims.

Claims

1. An uplink control information transmission method, executed by a terminal, includes:

wherein the target priority principle comprises: a logical channel priority principle or a medium access control, MAC, priority principle.

2. The method according to claim 1, wherein the determining the transmission behavior of the uplink control information carried on the PUCCH according to a target priority rule and the uplink transmission skip function priority order includes any one of:

under the condition that the terminal is configured with the logical channel priority principle, determining the transmission behavior of the UCI according to the logical channel priority principle and the priority order of the uplink transmission skipping function;

and under the condition that the terminal is not configured with the logical channel priority principle, determining the transmission behavior of UCI according to the MAC priority principle and the priority sequence of the uplink transmission skipping function.

3. The method as claimed in claim 2, wherein the determining the transmission behavior of the UCI according to the logical channel priority rule and the priority order of the uplink transmission skip function comprises any one of:

determining the transmission behavior of UCI according to the priority order of the logical channel priority principle prior to the uplink transmission skipping function;

and determining the transmission behavior of the UCI according to the priority order of the priority principle of the uplink transmission skipping function prior to the logical channel.

4. The method according to claim 3, wherein the PUSCHs comprise a CG PUSCH (physical uplink shared channel) with configuration grant and a DG PUSCH with dynamic scheduling, and the CG PUSCH, the DG PUSCH and the PUCCH have the same priority in a physical layer, and the transmission behavior of the UCI satisfies at least one of the following conditions only if the CG PUSCH and the PUCCH have resource overlap in a time domain:

wherein the first transmission behavior comprises any one of: transmitting the UCI bearer on the PUCCH, dropping the UCI, and multiplexing the UCI for transmission on the CG PUSCH; the second transmission behavior comprises any of: transmitting the UCI bearer on the PUCCH, discarding the UCI, and multiplexing the UCI for transmission on the CG PUSCH.

5. The method of claim 3, wherein the PUSCHs comprise CG PUSCH and DG PUSCH with resource overlapping in a time domain, and wherein the CG PUSCH, the DG PUSCH and the PUCCH have the same priority in a physical layer, and wherein a transmission behavior of the UCI satisfies at least one of the following only if the DG PUSCH and the PUCCH have resource overlapping in the time domain:

6. The method of claim 3, wherein the PUSCHs comprise CG PUSCHs and DG PUSCHs with resource overlap in a time domain, and wherein a transmission behavior of the UCI satisfies at least one of:

wherein the fourth transmission behavior comprises: transmitting the UCI carried on the PUCCH, or discarding the UCI; the fifth transmission behavior comprises any one of: transmitting the UCI bearer on the PUCCH, discarding the UCI, and multiplexing the UCI on a CG PUSCH; the sixth transmission behavior comprises any one of: discarding the UCI and carrying the UCI on PUCCH for transmission; the seventh transmission behavior comprises any one of: transmitting the UCI carried on the PUCCH, discarding the UCI, and multiplexing the UCI on a DG PUSCH.

7. The method according to claim 2, wherein the determining the transmission behavior of the UCI according to the MAC priority rule and the priority order of the uplink transmission skip function comprises any one of:

determining the transmission behavior of the UCI according to the priority order of the MAC priority principle prior to the uplink transmission skipping function;

and determining the transmission behavior of the UCI according to the priority order of the uplink transmission skipping function prior to the MAC priority principle.

8. The method according to claim 7, wherein the PUSCHs include a CG PUSCH (physical uplink shared channel) with configuration grant and a DG PUSCH with dynamic scheduling, and the CG PUSCH, the DG PUSCH and the PUCCH have the same priority in a physical layer, and only if the CG PUSCH and the PUCCH have resource overlap in a time domain, the transmission behavior of the UCI satisfies at least one of the following:

if the MAC priority principle has priority over the uplink transmission skipping function, the UCI is transmitted by bearing the UCI on a PUCCH;

and if the uplink transmission skipping function is prior to the MAC priority principle, the transmission behavior of the UCI is to multiplex the UCI on a CG PUSCH for transmission.

9. The method of claim 7, wherein the PUSCHs comprise a CG PUSCH and a DG PUSCH with resource overlap in a time domain, and wherein the CG PUSCH, the DG PUSCH, and the PUCCH have a same priority in a physical layer, and wherein the transmission behavior of the UCI multiplexes the UCI for transmission on the DG PUSCH only if the DG PUSCH and the PUCCH have resource overlap in the time domain.

10. The method of claim 7, wherein the PUSCHs comprise CG PUSCHs and DG PUSCHs with resource overlap in a time domain, and wherein a transmission behavior of the UCI satisfies at least one of:

the transmission behavior of the UCI is an eighth transmission behavior only under the condition that a CG PUSCH with high priority and the PUCCH with low priority overlap on a time domain;

11. The method of claim 1, wherein the logical channel priority principle comprises: and the MAC determines a target uplink authorization with priority according to the priority of the logical channel mapped by the data, and generates an MAC Protocol Data Unit (PDU) according to the target uplink authorization, wherein the target uplink authorization is dynamic scheduling or configuration authorization.

12. The method of claim 1, wherein the MAC priority principle comprises: and when the dynamically scheduled PUSCH is overlapped with the PUSCH resource with the authorization configuration, the PDU of the dynamically scheduled PUSCH is preferentially generated.

13. The method of claim 1, further comprising:

receiving target DCI, wherein the target DCI carries first indication information, the first indication information is used for indicating suspension of target transmission, the target transmission is PUSCH transmission of dynamic scheduling or PUSCH transmission of configuration authorization scheduling, and the target DCI is DCI used for dynamic scheduling of PUSCH or DCI scrambled by configuration scheduling radio network temporary identifier CS-RNTI.

14. The method of claim 13, wherein the target DCI further carries second indication information, and wherein the second indication information is used to indicate the number of times of the target transmission suspension.

15. An uplink control information transmission apparatus, comprising:

the terminal comprises a receiving module, a sending module and a receiving module, wherein the receiving module is used for receiving configuration information sent by network side equipment, and the configuration information is used for configuring an uplink transmission skipping function for the terminal;

the processing module is used for determining the transmission behavior of uplink control information UCI borne by a Physical Uplink Shared Channel (PUSCH) to be transmitted by a terminal and the priority sequence of the uplink transmission skipping function according to a target priority principle and the resource overlapping condition of the PUSCH and the PUCCH on the time domain;

16. The apparatus of claim 15, wherein the processing module is configured to perform any one of:

17. The apparatus of claim 15, wherein the logical channel priority principle comprises: and the MAC determines a target uplink authorization with priority according to the priority of the logical channel mapped by the data, and generates an MAC Protocol Data Unit (PDU) according to the target uplink authorization, wherein the target uplink authorization is dynamic scheduling or configuration authorization.

18. The apparatus of claim 15, wherein the MAC priority principle comprises: and when the dynamically scheduled PUSCH is overlapped with the PUSCH resource with the authorization configuration, the PDU of the dynamically scheduled PUSCH is preferentially generated.

19. A terminal, comprising: a memory, a processor and a program stored on the memory and executable on the processor, the program, when executed by the processor, implementing the steps in the uplink control information transmission method according to any one of claims 1 to 14.

20. A readable storage medium, storing thereon a program or instructions, which when executed by a processor, implement the steps of the uplink control information transmission method according to any one of claims 1 to 14.