CN116941301A

CN116941301A - Uplink transmission method, terminal and network equipment

Info

Publication number: CN116941301A
Application number: CN202180095053.4A
Authority: CN
Inventors: 张轶
Original assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Current assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority date: 2021-06-30
Filing date: 2021-06-30
Publication date: 2023-10-24
Also published as: WO2023272599A1

Abstract

An uplink transmission method, a terminal and a network device are provided. The uplink transmission method comprises the following steps: under the condition that the first condition is met, the terminal does not generate a MAC PDU for the first HARQ entity; the first condition is determined by at least one of the following information: a PUCCH format of a first resource, where the first resource is configured for SR by a network device; a PUCCH format of a second resource, wherein the second resource is a resource of HARQ-ACK; whether the first resource and the second resource overlap; and whether the first resource and the third resource overlap, wherein the third resource is a resource for bearing a first PUSCH, and the first PUSCH is used for bearing the MAC PDU. The embodiment of the application adds the first condition in the condition of enabling uplink skip, thereby being beneficial to avoiding the behavior disorder of the terminal.

Description

Uplink transmission method, terminal and network equipment

Technical Field

The present application relates to the field of communications technologies, and in particular, to an uplink transmission method, a terminal, and a network device.

Background

Uplink skip (uplink skip) means that in case that a certain condition is met, the terminal or the medium access control (media access control, MAC) entity may not generate a MAC protocol data unit (protocol data unit, PDU) for a certain hybrid automatic repeat request (hybrid automatic repeat reQuest, HARQ) entity, and further the terminal does not need to transmit a physical uplink shared channel (physical uplink shared channel, PUSCH) corresponding to the MAC PDU through a physical layer.

Before enabling upstream skip, the MAC entity needs to determine whether the condition for enabling upstream skip is satisfied. The condition for enabling uplink skip in the current protocol is not fully set, so that the terminal can perform disorder in some scenes.

Disclosure of Invention

The application provides an uplink transmission method, a terminal and network equipment, which are used for avoiding the behavior disorder of the terminal, so as to improve the certainty of uplink transmission.

In a first aspect, an uplink transmission method is provided, including: under the condition that the first condition is met, the terminal does not generate a MAC PDU for the first HARQ entity; the first condition is determined by at least one of the following information: a physical uplink control channel format (physical uplink control channel format, PUCCH format) of a first resource, wherein the first resource is configured by a network device for a scheduling request (scheduling request, SR); a PUCCH format of a second resource, wherein the second resource is a resource carrying HARQ-ACK; whether the first resource and the second resource overlap; and whether the first resource and the third resource overlap, wherein the third resource is a resource for bearing a first PUSCH, and the first PUSCH is used for bearing the MAC PDU.

In a second aspect, an uplink transmission method is provided, including: the MAC entity obtains a first uplink grant and a second uplink grant, wherein the first uplink grant corresponds to a first PUSCH, and the second uplink grant corresponds to a second PUSCH; if the first PUSCH and the second PUSCH overlap, the MAC entity determines an uplink grant delivered (reliver) to the HARQ entity according to the first information, where the uplink grant delivered to the HARQ entity is the first uplink grant or the second uplink grant; wherein the first information includes at least one of: the physical layer priority of the first PUSCH; the physical layer priority of the second PUSCH; the uplink authorization type of the first uplink authorization; the uplink authorization type of the second uplink authorization; whether the first PUSCH has uplink control information (uplink control information, UCI) multiplexing; and whether the second PUSCH has UCI multiplexing.

In a third aspect, an uplink transmission method is provided, including: if the first PUSCH and the second PUSCH overlap, the terminal sends the first PUSCH to the network device; wherein the first PUSCH is scheduled by downlink control information (downlink control information, DCI), the second PUSCH is configured by a network device (e.g., the network device is configured through higher layer signaling, which may be, for example, radio resource control (radio resource control, RRC) signaling), and the physical layer priority of the first PUSCH is higher than or equal to the physical layer priority of the second PUSCH.

In a fourth aspect, an uplink transmission method is provided, including: in the case that the first condition is satisfied, the network device does not receive the first PUSCH; the first condition is determined by at least one of the following information: a PUCCH format of a first resource, where the first resource is configured for SR by a network device; a PUCCH format of a second resource, wherein the second resource is a resource carrying HARQ-ACK; whether the first resource and the second resource overlap; whether the first resource and the third resource overlap or not, wherein the third resource is a resource for bearing the first PUSCH.

In a fifth aspect, an uplink transmission method is provided, including: if the first PUSCH and the second PUSCH overlap, the network device receives the first PUSCH or the second PUSCH from the terminal according to the first information; wherein the first information includes at least one of: the physical layer priority of the first PUSCH; the physical layer priority of the second PUSCH; the type of the uplink grant corresponding to the first PUSCH; the type of the uplink grant corresponding to the second PUSCH; whether the first PUSCH has UCI multiplexing or not; and whether the second PUSCH has UCI multiplexing.

In a sixth aspect, an uplink transmission method is provided, including: if the first PUSCH and the second PUSCH overlap, the network device receives the first PUSCH from the terminal; the first PUSCH is scheduled by DCI, the second PUSCH is configured by a network device, and the physical layer priority of the first PUSCH is higher than or equal to the physical layer priority of the second PUSCH.

In a seventh aspect, there is provided a terminal comprising: a generating unit, configured to not generate a MAC PDU for the first HARQ entity if the first condition is satisfied; the first condition is determined by at least one of the following information: a PUCCH format of a first resource, where the first resource is configured for SR by a network device; a PUCCH format of a second resource, wherein the second resource is a resource carrying HARQ-ACK; whether the first resource and the second resource overlap; and whether the first resource and the third resource overlap, wherein the third resource is a resource for bearing a first PUSCH, and the first PUSCH is used for bearing the MAC PDU.

An eighth aspect provides a terminal, including: an acquiring unit, configured to acquire a first uplink grant and a second uplink grant, where the first uplink grant corresponds to a first PUSCH and the second uplink grant corresponds to a second PUSCH; a determining unit, configured to determine, according to first information, an uplink grant delivered to an HARQ entity when the first PUSCH and the second PUSCH overlap, where the uplink grant delivered to the HARQ entity is a first uplink grant or a second uplink grant; wherein the first information includes at least one of: the physical layer priority of the first PUSCH; the physical layer priority of the second PUSCH; the uplink authorization type of the first uplink authorization; the uplink authorization type of the second uplink authorization; whether the first PUSCH has UCI multiplexing or not; and whether the second PUSCH has UCI multiplexing.

A ninth aspect provides a terminal, comprising: a communication unit, configured to send a first PUSCH to a network device if the first PUSCH and a second PUSCH overlap; the first PUSCH is scheduled by DCI, the second PUSCH is configured by a network device, and the physical layer priority of the first PUSCH is higher than or equal to the physical layer priority of the second PUSCH.

In a tenth aspect, there is provided a network device comprising: a communication unit configured to not receive the first PUSCH in a case where the first condition is satisfied; the first condition is determined by at least one of the following information: a PUCCH format of a first resource, where the first resource is configured for SR by a network device; a PUCCH format of a second resource, wherein the second resource is a resource carrying HARQ-ACK; whether the first resource and the second resource overlap; whether the first resource and the third resource overlap or not, wherein the third resource is a resource for bearing the first PUSCH.

In an eleventh aspect, there is provided a network device comprising: a communication unit configured to receive a first PUSCH or a second PUSCH from a terminal according to first information if the first PUSCH and the second PUSCH overlap; wherein the first information includes at least one of: the physical layer priority of the first PUSCH; the physical layer priority of the second PUSCH; the type of the uplink grant corresponding to the first PUSCH; the type of the uplink grant corresponding to the second PUSCH; whether the first PUSCH has UCI multiplexing or not; and whether the second PUSCH has UCI multiplexing.

In a twelfth aspect, there is provided a network device comprising: a communication unit configured to receive a first PUSCH from the terminal if the first PUSCH and a second PUSCH overlap; the first PUSCH is scheduled by DCI, the second PUSCH is configured by a network device, and the physical layer priority of the first PUSCH is higher than or equal to the physical layer priority of the second PUSCH.

In a thirteenth aspect, there is provided a terminal comprising a memory for storing a program and a processor for invoking the program in the memory to perform the method of any of the first to third aspects.

In a fourteenth aspect, there is provided a network device comprising a memory for storing a program and a processor for invoking the program in the memory to perform the method of any of the fourth to sixth aspects.

In a fifteenth aspect, there is provided an apparatus comprising a processor for invoking a program from memory to perform the method of any of the first to third aspects.

In a sixteenth aspect, there is provided an apparatus comprising a processor for invoking a program from memory to perform the method of any of the fourth to sixth aspects.

A seventeenth aspect provides a chip comprising a processor for calling a program from a memory, causing a device on which the chip is mounted to perform the method of any one of the first to third aspects.

An eighteenth aspect provides a chip comprising a processor for calling a program from a memory, causing a device on which the chip is mounted to perform the method of any one of the fourth to sixth aspects.

In a nineteenth aspect, there is provided a computer-readable storage medium having stored thereon a program that causes a computer to execute the method according to any one of the first to third aspects.

In a twentieth aspect, there is provided a computer-readable storage medium having stored thereon a program that causes a computer to execute the method according to any one of the fourth to sixth aspects.

In a twenty-first aspect, there is provided a computer program product comprising a program for causing a computer to perform the method of any one of the first to third aspects.

In a twenty-second aspect, there is provided a computer program product comprising a program for causing a computer to perform the method of any one of the fourth to sixth aspects.

In a twenty-third aspect, there is provided a computer program for causing a computer to perform the method of any one of the first to third aspects.

In a twenty-fourth aspect, there is provided a computer program that causes a computer to perform the method of any one of the fourth to sixth aspects.

The embodiment of the application adds a first condition in the condition of enabling uplink skipping. The setting of the first condition takes into account at least one of the following information: PUCCH format of SR resources; information such as PUCCH format of HARQ-ACK resources, whether SR resources and HARQ-ACK resources overlap, whether SR resources and PUSCH resources overlap, and the like. The above information is main information in the uplink skip scene, which may cause the behavior disorder of the terminal, and the information is considered when judging whether to enable uplink skip, so as to help avoid the behavior disorder of the terminal, thereby improving the certainty of uplink transmission.

Drawings

Fig. 1 is a schematic block diagram of a wireless communication system 100 to which an embodiment of the present application is applied.

Fig. 2 is an exemplary diagram of PUCCH and PUSCH colliding in the time domain.

Fig. 3 is a schematic flow chart of an uplink transmission method according to an embodiment of the present application.

Fig. 4 is an example diagram of SR, HARQ-ACK, and PUSCH transmission methods.

Fig. 5 is a schematic flow chart of an uplink transmission method according to another embodiment of the present application.

Fig. 6 is an exemplary diagram of two PUSCHs in an overlapped state.

Fig. 7 is a schematic flowchart of an uplink transmission method according to another embodiment of the present application.

Fig. 8 is another example diagram of two PUSCHs in an overlapped state.

Fig. 9 is a schematic block diagram of a terminal according to an embodiment of the present application.

Fig. 10 is a schematic block diagram of a terminal according to another embodiment of the present application.

Fig. 11 is a schematic block diagram of a terminal according to still another embodiment of the present application.

Fig. 12 is a schematic block diagram of a network device according to an embodiment of the present application.

Fig. 13 is a schematic block diagram of a network device according to another embodiment of the present application.

Fig. 14 is a schematic block diagram of a network device according to still another embodiment of the present application.

Fig. 15 is a schematic structural view of an apparatus provided by an embodiment of the present application.

Detailed Description

The technical scheme of the application will be described below with reference to the accompanying drawings.

Fig. 1 is a wireless communication system 100 to which embodiments of the present application are applied. The wireless communication system 100 may include a network device 110 and a terminal 120. Network device 110 may be a device in communication with terminal 120. Network device 110 may provide communication coverage for a particular geographic area and may communicate with terminals 120 located within the coverage area.

Fig. 1 exemplarily shows one network device and two terminals 120. Alternatively, the wireless communication system 100 may include a plurality of network devices and one or more terminals may be included in a coverage area of each network device, which is not limited by the embodiment of the present application.

Optionally, the wireless communication system 100 may further include a network controller, a mobility management entity, and other network entities, which are not limited by the embodiment of the present application.

It should be understood that the present application can be applied to various communication systems. For example, the present application may be applied to one or more of the following communication systems: global system for mobile communications (global system of mobile communication, GSM), code division multiple access (code division multiple access, CDMA) system, wideband code division multiple access (wideband code division multiple access, WCDMA) system, general packet radio service (general packet radio service, GPRS), long term evolution (long term evolution, LTE) system, long term evolution advanced (advanced long term evolution, LTE-a) system, universal mobile telecommunications system (universal mobile telecommunication system, UMTS), new Radio (NR), fifth generation mobile telecommunications system (5th generation,5G), and the like.

It should also be appreciated that in embodiments of the present application, a terminal may also include, but is not limited to, a Mobile Station (MS), a mobile terminal (mobile terminal), a mobile phone (mobile phone), a User Equipment (UE), a handset (handset), a portable device (portable equipment), etc., which may communicate with one or more core networks via a radio access network (radio access network, RAN). For example, the terminal may be a mobile telephone (or "cellular" telephone), a computer with wireless communication capabilities, or the like. In some embodiments, the terminal may also be a portable, pocket, hand-held, computer-built-in or vehicle-mounted mobile device.

In the embodiment of the present application, the network device may be an access network device, for example, a base station, a transmission/reception point (TRP), or an access point. The base station may be a base station (base transceiver station, BTS) in GSM or CDMA, a base station (NodeB) in WCDMA, an evolved Node B (eNB or e-NodeB) in LTE, or a base station (gNB) in NR or 5G, which is not particularly limited in the embodiment of the present application.

Example 1:

embodiment 1 is intended to solve the problem in the uplink skip scenario, and some concepts related to embodiment 1 are explained below for ease of understanding.

Uplink skipping

Uplink skipping means that under the condition that a certain condition is met, the terminal or the MAC entity may not generate a MAC PDU for a certain HARQ entity, and then the PUSCH corresponding to the MAC PDU is not required to be transmitted to the network device through the physical layer. The current protocol specifies that a MAC entity may not generate a MAC PDU for a certain HARQ entity if either of the following two conditions is met.

Case 1:

if the MAC entity is configured with the parameter enhanced skip uplink txdate and indicates that the uplink grant to the HARQ entity is a "true" and the uplink grant to the HARQ entity is scrambled by a cell-radio network temporary identifier (cell-radio network temporary identifier, C-RNTI), or if the MAC entity is configured with the parameter enhanced skip uplink txconfigure and indicates that the uplink grant to the HARQ entity is configured, the MAC PDU is not generated for the HARQ entity if the following condition is satisfied:

1. the MAC entity does not configure a logical channel based priority (lch-basedpriority);

2. if no UCI is to be multiplexed on this PUSCH according to the description in the relevant protocol (such as TS 38.213); and is also provided with

3. If there is no aperiodic channel state information (channel state information, CSI) request on this PUSCH according to the description in the relevant protocol, such as TS 38.212; and is also provided with

4. If this MAC PDU contains 0 MAC service data units (service data unit, SDU); and is also provided with

5. If this MAC PDU contains only periodic buffer status reports (buffer status report, BSR) and no data is available for any logical channel group (logical channel group, LCG), or this MAC PDU contains only padding (padding) BSR.

Case 2:

the MAC entity configures the parameter skip uplink txdata to be "true" and indicates that the uplink grant to the HARQ entity is scrambled by the C-RNTI, or indicates that the uplink grant to the HARQ entity is configured uplink grant,

1. if there is no aperiodic CSI request on this PUSCH according to the description in the relevant protocol (such as TS 38.212); and is also provided with

2. If this MAC PDU contains 0 MAC SDUs; and is also provided with

3. If this MAC PDU contains only a periodic BSR and no data is available for any LCG, or this MAC PDU contains only a padding BSR.

In both cases, condition 2 of case 1 describes that: if a case similar to the case of overlap of PUCCH and PUSCH shown in fig. 2 occurs, this represents UCI multiplexing on PUSCH. At this time, even if the MAC PDU corresponding to the PUSCH has no data, the MAC entity still needs to generate the MAC PDU, so as to ensure that UCI can be multiplexed and transmitted on the PUSCH, thereby reducing the blind detection times of the base station. Condition 2 of case 1 is a condition that the present application needs to pay attention to, because the technical problem to be solved by the embodiment hereinafter mainly occurs in the uplink skip scene corresponding to the condition.

Multiplexing transmission in PUCCH for SR and HARQ-ACK/CSI

UCI of some communication systems (e.g., NR) may include: HARQ-ACK (or HARQ information or HARQ feedback information), which may include, for example, acknowledgements (ACKs) and negative acknowledgements (negative acknowledgement, NACKs)), SR, and CSI. Some communication systems (e.g., NRs) support transmission of UCI using multiple PUCCH formats. The format of PUCCH and related parameters can be seen in table 1 below.

TABLE 1

PUCCH format	Number of time domain symbols	Number of bits carrying UCI	Number of physical resource blocks
0	1-2	≤2	1
1	4-14	≤2	1
2	1-2	＞2	1-16
3	4-14	＞2	1-16
4	4-14	＞2	1

As can be seen from table 1, PUCCH formats 0, 1 are used to carry 1 or 2 bits UCI, and PUCCH format 0 occupies 1 or 2 time domain symbols. PUCCH format 1 occupies 4 to 14 time domain symbols.

In some communication systems (e.g., NR Rel-15), if the resources of the PUCCH carrying the SR overlap (e.g., overlap in the time domain) with the resources of the PUCCH carrying the HARQ-ACK/CSI, the communication system supports the SR and the HARQ-ACK (or SR and CSI) multiplexing for transmission within the same PUCCH. The communication system specifies a number of different multiplexing rules for SR and HARQ-ACK/CSI. These multiplexing rules are described below in the context of the following.

Case a: the first PUCCH carrying the SR adopts PUCCH format 0, and the second PUCCH carrying the HARQ-ACK adopts PUCCH format 0

In case a, if SR is positive (active), the terminal transmits one PUCCH within the physical resource block (physical resource block, PRB) where the second PUCCH is located, the cyclic shift offset m used by the PUCCH _cs (see tables 2 and 3) is different from the cyclic shift offset used when transmitting HARQ-ACKs alone. However, the time domain resource and the frequency domain resource occupied by the PUCCH are the same as those of the second PUCCH.

TABLE 2 transmission of 1-bit HARQ-ACK and Positive SR Using PUCCH Format 0

HARQ-ACK value	0	1
Cyclic shift offset	m _cs ＝3	m _cs ＝9

TABLE 3 transmission of 2-bit HARQ-ACK and positive SR using PUCCH Format 0

HARQ-ACK value

{0,0}

{0,1}

{1,1}

{1,0}

Cyclic shift offset

m _cs ＝1

m _cs ＝4

m _cs ＝7

m _cs ＝10

In case a, if the SR is negative (negative), the terminal transmits the HARQ-ACK through the second PUCCH and continues to use the cyclic shift used when transmitting the HARQ-ACK alone.

Case b: the first PUCCH carrying SR adopts PUCCH format 0 and the second PUCCH carrying HARQ-ACK adopts PUCCH format 1

In case b, the terminal transmits only HARQ-ACK through the second PUCCH and does not transmit SR.

Case c: the first PUCCH carrying an SR adopts PUCCH format 1 and the second PUCCH carrying an HARQ-ACK adopts PUCCH format 1.

In case c, if the SR is positive, the terminal transmits the HARQ-ACK through the first PUCCH.

In case c, if the SR is negative, the terminal transmits the HARQ-ACK through the second PUCCH.

In case c, the SR and HARQ-ACK multiplex transmission on which PUCCH, depending on the state of the SR. The presence of this case c is a major source of technical problems to be solved by the embodiment hereinafter.

Case d: the first PUCCH carrying an SR adopts PUCCH format 1 and the second PUCCH carrying an HARQ-ACK adopts PUCCH format 0.

The current protocol does not support multiplexed transmission of SR and HARQ-ACK/CSI in PUCCH in this case. This is because the time domain resources occupied by the PUCCH transmitting the 1-bit SR should not be longer than the time delay resources occupied by the PUCCH transmitting the 1-or 2-bit HARQ-ACK.

Case e: the second PUCCH carrying HARQ-ACK/CSI adopts PUCCH format 2/3/4

In this case, the terminal may add after the bits carrying the HARQ-ACK/CSIBits SR (each bit representing one positive SR or negative SR). K denotes an SR transmission opportunity overlapping (time domain overlapping) a PUCCH carrying HARQ-ACK/CSI, which is configured in one slot (slot)/sub-slot. The terminal can determine the total number of bits of UCI according to HARQ-ACK/CSI and SROr alternativelyAnd determining PUCCH resources. As can be seen from the above formula, for K SRs, the total number of bits of UCI is fixed regardless of whether the SR is positive or negative, so the PUCCH resource determined by the terminal is also fixed.

In the above description, uplink skip and multiplexing transmission of multiple UCI are described in detail, and it can be seen from the above description that if a terminal or a MAC entity of the terminal configures enhanced skip uplink txd dynamic to "true", or configures enhanced skip uplink txconfigured to "true", and does not configure priority based on a logical channel, the terminal may perform the following steps from the point of view of terminal implementation:

1. if a plurality of UCI overlaps, the physical layer multiplexes the plurality of UCI onto one PUCCH. If the PUCCH overlaps (e.g., overlaps in the time domain) with the PUSCH, the physical layer sends an indication of UCI multiplexing (UCI multiplexing) to the MAC layer (which may specifically be a MAC entity in the MAC layer); if the PUCCH does not overlap with the PUSCH (e.g., does not overlap in the time domain), the physical layer does not send an indication of UCI multiplexing to the MAC layer.

2. If the MAC layer does not receive an indication of UCI multiplexing from the physical layer and satisfies the other conditions enabling uplink skip mentioned previously, the MAC layer does not generate a MAC PDU; if the MAC layer receives the indication of UCI multiplexing, the MAC layer generates a MAC PDU.

It follows that whether the MAC layer generates MAC PDUs depends on whether an indication of UCI multiplexing will be received from the physical layer, i.e. the MAC layer's decision requires input information from the physical layer.

In addition, as mentioned above, when the physical layer multiplexes a plurality of UCI into one PUCCH, it is necessary to know the state of SR. Referring to the section of "SR and HARQ-ACK/CSI multiplexed transmission in PUCCH", in case c, the state of SR affects the multiplexing result. For example, when the first PUCCH carrying the SR is PUCCH format 1 and the second PUCCH carrying the HARQ-ACK is PUCCH format 1, the SR is positive, and the terminal transmits the HARQ-ACK through the first PUCCH; if the SR is negative, the terminal transmits the HARQ-ACK through the second PUCCH. The terminal selects whether the first PUCCH or the second PUCCH transmits HARQ-ACK to influence the conclusion whether the PUCCH and the PUSCH are overlapped or not, and further influence whether the physical layer can send UCI multiplexing instructions to the MAC layer or not.

However, the state of SR is required to be determined according to whether the MAC layer delivers SR/MAC PDU (positive SR) to the physical layer, and the MAC layer is required to determine whether to deliver SR/MAC PDU to the physical layer according to the priority based on the logical channel and the result of checking whether to perform uplink skip. It follows that the decision of whether the physical layer performs UCI multiplexing or not needs to be based on input information of the MAC layer. In this way, the MAC layer and the physical layer may generate an interdependence relationship due to the uncertain information of the SR state, and the interdependence between the MAC layer and the physical layer on the uncertain information may cause misbehavior of the terminal.

For example, interdependence of uncertain information between the MAC layer and the physical layer easily leads to the occurrence of: the indication of UCI multiplexing output by the physical layer to the MAC layer is made based on state 1 (positive or negative) of SR, but based on this result, the MAC layer outputs to the physical layer that the SR state is state 2 (negative or positive). If this occurs, uncertainty in the transmission between the terminal and the network device may be caused, and thus the number of blind tests of the network device may be increased.

As can be seen from the reason why the above problems occur by comprehensive analysis, the above-mentioned mutual dependence between the MAC layer and the physical layer mainly relates to the following information:

1. the method comprises the steps that a network device configures a PUCCH format of a first resource for SR (the first resource can be configured by the network device through RRC signaling, and the PUCCH format of the first resource can be determined according to PUCCH-Resourceid in a SchedulingRequestResourceConfig of RRC configuration);

2. PUCCH format of a second resource carrying HARQ-ACK (the second resource may be a resource for transmitting HARQ-ACK determined by the terminal according to configuration/indication of the network device);

3. whether or not the first resource overlaps with the second resource (overlapping herein may refer to overlapping in the time domain, which may sometimes be replaced by a "collision"); and

4. Whether the first resource and a third resource carrying the first PUSCH overlap (the first PUSCH may be any PUSCH, in some embodiments the third resource overlaps with the second resource mentioned above (e.g. overlaps in the time domain)).

For example, only in the case where the first resource and the second resource overlap, the influence of the positive and negative of the SR on UCI multiplexing decision of the physical layer needs to be considered, and if the first resource and the second resource do not overlap, the physical layer does not perform UCI multiplexing. For another example, even if the first resource and the second resource overlap, only if the PUCCH formats of the first resource and the second resource are PUCCH format 1, the influence of the positive and negative of the SR on the UCI multiplexing decision of the physical layer needs to be considered, and otherwise, the positions of the PUCCHs multiplexing the SR and the HARQ-ACK may be predetermined, regardless of the positive and negative of the SR.

Based on the above analysis, the embodiment of the present application adds the first condition to the conditions enabling upstream skip. The first condition may be determined by at least one of the following information: PUCCH format of the first resource; PUCCH format of the second resource; whether the first resource and the second resource overlap; and whether the first resource and the third resource overlap. The addition of the first condition enables the terminal or the MAC entity of the terminal to take into account information that may cause the above-mentioned terminal to act as a disorder when deciding whether to enable uplink skipping, so as to better make a decision whether to enable uplink skipping.

For ease of understanding, the first resource will be referred to as SR resource, the second resource will be referred to as HARQ-ACK resource, and the third resource will be referred to as PUSCH resource.

In the following, referring to fig. 3, an uplink transmission procedure is taken as an example, and a determination timing of the first condition and a possible setting manner of the first condition are illustrated in more detail.

As shown in fig. 3, step S310a and step S320a are performed by the terminal, for example, may be performed by a MAC entity of the terminal. The MAC entity may configure enhanced skip uplink txd dynamic as "true" or enhanced skip uplink txconfiguration as "true". Therefore, in the case where the condition for enabling uplink skip is satisfied, the terminal may enable uplink skip or perform an uplink skip operation. The conditions that enable upstream skip may include the conditions mentioned above when introducing the concept of upstream skip, as may include one or more of the following:

3. If there is no aperiodic CSI request on this PUSCH according to the description in the relevant protocol (such as TS 38.212); and is also provided with

4. If this MAC PDU contains 0 MAC SDUs; and is also provided with

5. If this MAC PDU contains only a periodic BSR and no data is available for any LCG, or this MAC PDU contains only a padding BSR.

On this basis, the conditions for enabling uplink skip may further include the first conditions introduced in the embodiments of the present application, that is, conditions related to information such as PUCCH format of SR resources, PUCCH format of HARQ-ACK resources, whether SR resources overlap with HARQ-ACK resources, and whether SR resources overlap with PUSCH resources. For brevity, fig. 3 is mainly described around the judgment process of the first condition. It will be appreciated that in some embodiments, whether upstream skipping is enabled may also require a comprehensive consideration of the determination results of the above conditions 1-5. For example, the terminal may enable uplink skipping or perform uplink skipping operation on the basis that the above conditions 1 to 5 and the first condition mentioned in the embodiment of the present application are satisfied.

Referring to fig. 3, in step S310a, the terminal determines whether a first condition is satisfied. If the first condition is satisfied, the terminal (or the MAC entity) does not generate a MAC PDU for the first HARQ entity. If the first condition is not satisfied, the terminal (or the MAC entity) continues to perform step S320a, generating a MAC PDU for the first HARQ entity. In step S330, after the terminal generates a MAC PDU for the first HARQ entity, the terminal may transmit a first PUSCH corresponding to the MAC PDU to the network device.

Accordingly, the network device may also determine whether to receive the first PUSCH according to the first condition. For example, with continued reference to fig. 3, in step S310b, the network device determines whether the first condition is satisfied. If the first condition is satisfied, the network device does not receive the first PUSCH. It should be understood that the network device does not receive the first PUSCH, which means that the network device determines that the terminal will not transmit the first PUSCH, so there is no need to detect and receive the first PUSCH. If the first condition is not satisfied, the network device continues to perform step S330, and receives the first PUSCH. It should be noted that, in the embodiment of the present application, the execution sequence of the step S310a, the step S320a at the terminal side and the step S310b at the network device side is not strictly limited, and may be executed in parallel or may be executed sequentially.

In some embodiments, the first condition may include that the SR resource and the HARQ-ACK resource do not overlap. Alternatively, the first condition may include that the SR resource and the PUSCH resource do not overlap. Alternatively, the first condition may be a combination of the two conditions.

The following description will take an example that the first condition includes that the SR resource and the HARQ-ACK resource are not overlapped, and that the SR resource and the PUSCH resource are not overlapped. Referring to fig. 4, SR resources in the first slot (slot) overlap with both HARQ-ACK resources and PUSCH resources. Therefore, in the first slot, the first condition is not satisfied and the terminal cannot enable uplink skipping on the PUSCH 1. Therefore, the MAC entity of the terminal needs to generate a MAC PDU for the HARQ entity, and transmit PUSCH 1 corresponding to the MAC PDU to the network device through the physical layer. Similarly, the SR resource in the fourth slot overlaps with the PUSCH resource. Therefore, in the fourth slot, the first condition is not satisfied either, and the terminal cannot enable uplink skipping on PUSCH 4. Therefore, the MAC entity of the terminal needs to generate a MAC PDU for the HARQ entity, and then transmit the PUSCH 4 corresponding to the MAC PDU to the network device through the physical layer.

With continued reference to fig. 4, in the second slot and the third slot, there is neither a case where SR resources and HARQ-ACK resources overlap, nor a case where SR resources and PUSCH resources overlap. Therefore, in the second slot and the third slot, the first condition is satisfied and the terminal can enable uplink skipping on PUSCH 2 and PUSCH 3. Therefore, in the second time slot, the MAC entity of the terminal may not generate the MAC PDU, and further, there is no need to send PUSCH 2 corresponding to the MAC PDU to the network device through the physical layer; similarly, in the third time slot, the MAC entity of the terminal may not generate the MAC PDU, and further, need not send PUSCH 3 corresponding to the MAC PDU to the network device through the physical layer.

Based on the foregoing analysis, once the SR resources and HARQ-ACK resources are carried and/or the SR resources and PUSCH resources overlap, the aforementioned problem of the MAC layer and physical layer interdependence may occur to the terminal. In this embodiment, a judgment condition related to resource overlapping is added to a condition for enabling uplink skip, so that the terminal does not enable uplink skip once it finds that at least one of HARQ-ACK resources and PUSCH resources overlaps with SR resources. Although the judgment condition is strict (the judgment condition is strict, that is, even if the above-mentioned resource overlap occurs, the problem that the MAC layer and the physical layer are mutually dependent does not necessarily occur in practice, and whether the problem occurs or not is also dependent on factors such as the PUCCH format of the SR resource and the HARQ-ACK resource, but the present embodiment does not continue to judge the PUCCH format of the SR resource and/or the HARQ-ACK resource, and once the above-mentioned resource overlap occurs, uplink skip is not performed, so that the condition is strict), but the judgment condition has the advantage of simple implementation and does not need to add complex judgment logic. Therefore, the embodiment can reduce the implementation complexity of the terminal on the premise of solving the problem that the MAC layer and the physical layer are mutually dependent.

In some embodiments, the first condition may include that PUCCH format of the SR resource is PUCCH format 0. Alternatively, the first condition may include that PUCCH format of SR resources is PUCCH format 1, and at least one of HARQ-ACK resources and PUSCH resources does not overlap with SR resources. Alternatively, the first condition may be a combination of the two conditions.

The following description will take an example in which the first condition is that the PUCCH format including the SR resource is PUCCH format 0 and the PUCCH format including the SR resource is PUCCH format 1, and at least one of the HARQ-ACK resource and the PUSCH resource is not overlapped with the SR resource. Referring to fig. 4, if the PUCCH format of the SR resource is PUCCH format 0, the first condition is satisfied in the first to fourth slots, and the terminal may enable uplink skip on PUSCH 1 to PUSCH 4. That is, in the first time slot to the fourth time slot, the terminal may not generate the MAC PDU, and further, the PUSCH 1 to PUSCH 4 may not be transmitted to the network device through the physical layer.

With continued reference to fig. 4, if the PUCCH format of the SR resource is PUCCH format 1, since the HARQ-ACK resource and the PUSCH resource in the first slot overlap, the first condition is not satisfied, and thus the terminal cannot enable uplink skip on PUSCH 1. Therefore, in the first time slot, the MAC entity of the terminal needs to generate a MAC PDU for the HARQ entity, and then transmit PUSCH 1 corresponding to the MAC PDU to the network device through the physical layer.

The first condition provided in this embodiment is more relaxed than in the previous embodiment, so that it is possible for the terminal to perform the uplink skip operation in the first slot and the fourth slot where there is resource overlap.

In some embodiments, the first condition may include that PUCCH format of the SR resource is PUCCH format 0. Alternatively, the first condition may include that PUCCH format of SR resource is PUCCH format 1, PUCCH format of HARQ-ACK resource is PUCCH format 1, and at least one of HARQ-ACK resource and PUSCH resource is not overlapped with SR resource. Alternatively, the first condition may be a combination of the two conditions.

The following describes an example in which the first condition is that the PUCCH format including the SR resource is PUCCH format 0, the PUCCH format including the SR resource is PUCCH format 1, the PUCCH format including the HARQ-ACK resource is PUCCH format 1, and at least one of the HARQ-ACK resource and the PUSCH resource does not overlap with the SR resource. Referring to fig. 4, if the PUCCH format of the SR resource is PUCCH format 0, the first condition is satisfied in the first to fourth slots, and the terminal may enable uplink skip on PUSCH 1 to PUSCH 4. That is, in the first time slot to the fourth time slot, the terminal may not generate the MAC PDU, and further, the PUSCH 1 to PUSCH 4 may not be transmitted to the network device through the physical layer.

With continued reference to fig. 4, if the PUCCH format of the SR resource is PUCCH format 1, the first condition is satisfied in the second to fourth slots, and the terminal may enable uplink skip on PUSCH 2 to PUSCH 4. That is, in the second time slot to the fourth time slot, the terminal may not generate the MAC PDU, and further, the PUSCH 2 to PUSCH 4 may not be transmitted to the network device through the physical layer. For the first slot, whether the first condition can be met depends on the PUCCH format of the HARQ-ACK resource. If the PUCCH format of the HARQ-ACK resource is PUCCH format 1, the first condition cannot be met, and the terminal cannot enable uplink skip on the PUSCH 1; if the HARQ-ACK resource is other PUCCH formats than PUCCH format 1, the first condition is satisfied, and the terminal may enable uplink skipping on PUSCH 1.

The first condition provided by the present embodiment is more relaxed than the previous embodiment, so that it is possible for the terminal to perform an uplink skip operation in the first slot even in the case where the PUCCH format of the SR resource is PUCCH format 1.

In some embodiments, the first condition may further include that the PUCCH format of the HARQ-ACK resource is not PUCCH format 1, e.g., PUCCH format of the HARQ-ACK resource is PUCCH format 0/2/3/4. Referring to fig. 4, if the PUCCH format of the HARQ-ACK resource is not PUCCH format 1, the first condition is satisfied in all of the first to fourth slots, and the terminal may enable uplink skip on PUSCH 1 to PUSCH 4. That is, in the first time slot to the fourth time slot, the terminal may not generate the MAC PDU, and further, the PUSCH 1 to PUSCH 4 may not be transmitted to the network device through the physical layer.

It should be appreciated that the first conditions mentioned in the above embodiments may be combined arbitrarily without conflict. For example, the first condition may include that PUCCH format of SR resource is PUCCH format 0 or PUCCH format of HARQ-ACK resource is not PUCCH format 1. Alternatively, in some embodiments, the first condition may have a plurality of optional setting manners, and the network device may configure, according to actual needs, an appropriate first condition for the terminal through signaling.

The corresponding embodiments of fig. 3 add a first condition to the enable condition of upstream skipping to release the interdependence of uncertainty information between the physical layer and the MAC layer. In other words, each embodiment corresponding to fig. 3 may remove the scene affected by the SR state from the scene that enables uplink skipping, so as to remove the interdependence between the physical layer and the MAC layer on the uncertainty information, thereby better achieving the purpose of deterministic transmission.

Example 2:

embodiment 2 is intended to solve the problem caused by the introduction of physical layer priority, and some concepts related to embodiment 2 are explained below for ease of understanding.

Physical layer priority

In some communication systems (NR Rel-16), the concept of physical layer priority is introduced in the physical layer for the uplink channel in order to better support ultra-reliable low latency (URLLC) communication traffic. The physical layer priority may be represented by a parameter priority index, wherein priority index 0 indicates that the physical layer priority is a low priority, and priority index 1 indicates that the physical layer priority is a high priority.

For the configured uplink channel, the corresponding physical layer priority can be configured by the network device, such as configured through RRC signaling; for dynamically scheduled uplink channels, their corresponding physical layer priorities may be indicated by the network device through priority indicator carried in the DCI. Some communication systems, such as NR, do not support simultaneous transmission of two overlapping (overlapping in the time domain) uplink channels. Therefore, in the case that the uplink channels with different physical layer priorities overlap, the terminal only transmits the uplink channel with the higher physical layer priority, and the uplink channel with the lower physical layer priority is discarded. In other words, the terminal preferentially guarantees the transmission of the uplink channel with higher physical layer priority. For PUCCH (carrying UCI) and PUSCH with the same physical layer priority, the UCI may be multiplexed on PUSCH for transmission.

Logical channel priority

The MAC entity may configure priorities based on the logical channels. For one MAC entity, if a logical channel-based priority (lch-based priority) is configured, the priority of one uplink grant (uplink grant) may be determined according to the highest priority among priorities of logical channels multiplexed in a corresponding MAC PDU of the uplink grant (the MAC PDU in which the logical channel data is multiplexed representing that the MAC PDU is already stored in the HARQ buffer), or the MAC PDU in which the logical channel data is multiplexed (the MAC PDU in which the logical channel data is multiplexed representing that the MAC PDU is not yet stored in the HARQ buffer). For an uplink grant, if no logical channel data is multiplexed in its corresponding MAC PDU or no logical channel data can be multiplexed in the MAC PDU, the priority of the uplink grant is lower than the priority of any uplink grant in which logical channel data is multiplexed or can be multiplexed in the MAC PDU.

Dynamic uplink grant and configuration uplink grant

The PUSCH scheduled by the network device through the DCI may be referred to as a dynamic grant PUSCH (DG PUSCH). The PUSCH configured by the network device through RRC signaling may be referred to as a configured grant PUSCH (CG PUSCH). The uplink grant corresponding to DG PUSCH may be referred to as dynamic uplink grant (dynamic uplink grant). The uplink grant corresponding to the CG PUSCH may be referred to as a configured uplink grant (configured uplink grant).

The current MAC layer protocol provides that, in the case where the MAC entity does not configure a logical channel priority, but an uplink skip is configured, the dynamic uplink grant takes precedence over the configured uplink grant (or dynamic uplink grant override configured uplink grant). In other words, in the case where DG PUSCH and CG PUSCH overlap (may also be referred to as time domain overlap, or collision), the priority of uplink grant corresponding to DG PUSCH is higher than that of uplink grant corresponding to CG PUSCH. Therefore, in the actual transmission process, in the case where DG PUSCH and CG PUSCH overlap, the MAC entity may deliver a dynamic uplink grant to the HARQ entity.

However, if the terminal configures the physical layer priority, and the DG PUSCH is a low physical layer priority, and the CG PUSCH is a high physical layer priority, the above-mentioned provision of the current MAC layer protocol will cause the CG PUSCH with a higher physical layer priority to be unable to be transmitted, thereby affecting the reliability of the high priority service.

The embodiment of the application provides two schemes from the two angles of the MAC layer and the physical layer so as to solve the problems. These two schemes are illustrated in detail below by examples 2.1 and 2.2, respectively.

Example 2.1

In the embodiment of the present application, when the MAC entity obtains two uplink grants (including a first uplink grant and a second uplink grant, where the first uplink grant corresponds to a first PUSCH and the second uplink grant corresponds to a second PUSCH), if the first PUSCH and the second PUSCH overlap, the MAC entity may comprehensively consider at least one of the following information and then determine which uplink grant of the first uplink grant and the second uplink grant is delivered to the HARQ entity:

1. Physical layer priority of the first PUSCH;

2. physical layer priority of the second PUSCH;

3. an uplink grant type of the first uplink grant;

4. the uplink authorization type of the second uplink authorization;

5. whether the first PUSCH has UCI multiplexing; and

6. whether the second PUSCH has UCI multiplexing.

The introduction of the first information can help the MAC entity to make a more accurate decision, so that the problem that the PUSCH with high physical layer priority cannot be transmitted can be avoided.

The specific manner of using the first information will be described in more detail with reference to fig. 5, taking the uplink transmission procedure as an example.

As shown in fig. 5, in step S510, the terminal (or the MAC entity of the terminal) acquires a first uplink grant and a second uplink grant. One of the first uplink grant and the second uplink grant is a dynamic uplink grant, and the other is a configuration uplink grant; alternatively, in some embodiments, the first uplink grant and the second uplink grant may both be configured uplink grants.

If the first PUSCH (corresponding to the first uplink grant) and the second PUSCH (corresponding to the second uplink grant) overlap, the terminal (or the MAC entity of the terminal) continues to perform step S520, and determines an uplink grant (first uplink grant or second uplink grant) delivered to the HARQ entity according to the first information. In step S530, the terminal transmits the first PUSCH or the second PUSCH to the network device. For example, if the MAC entity delivers the first uplink grant to the HARQ entity, the terminal sends a first PUSCH to the network device; if the MAC entity delivers the second uplink grant to the HARQ entity, the terminal sends a second PUSCH to the network device.

Taking the example that the first information includes the physical layer priority of the first PUSCH and/or the physical layer priority of the second PUSCH, and the uplink grant type of the first uplink grant and/or the uplink grant type of the second uplink grant, step S520 in fig. 5 may include the following two steps:

step 1: if the physical layer priorities of the first PUSCH and the second PUSCH are different, the terminal or the MAC entity of the terminal delivers the uplink grant corresponding to the PUSCH with higher physical layer priority to the HARQ entity. Accordingly, the network device receives PUSCH with higher priority.

Step 2: if the physical layer priorities of the first PUSCH and the second PUSCH are the same, and one of the first uplink grant and the second uplink grant is a dynamic uplink grant, the terminal or the MAC entity of the terminal delivers the dynamic uplink grant to the HARQ entity. Accordingly, the network device receives DG PUSCH in the first PUSCH and the second PUSCH.

By adopting the scheme, the problem that the PUSCH with high physical layer priority cannot be transmitted does not occur, so that the transmission performance of the high-priority service can be ensured. Furthermore, if the first PUSCH and the second PUSCH physical layer priorities are the same, the scheme is compatible with the current protocol.

An example of this is illustrated in fig. 6. In fig. 6, the first uplink grant is a configuration uplink grant, and the second uplink grant is a dynamic uplink grant, so the first PUSCH is CG PUSCH and the second PUSCH is DG PUSCH. In fig. 6, PUSCH having a higher physical layer priority is referred to as HP PUSCH, and PUSCH having a lower physical layer priority is referred to as LP PUSCH; if the physical layer priorities of the two PUSCHs are the same, both PUSCHs are referred to as HP PUSCHs.

In fig. 6 (a), CG PUSCH has a higher priority than DG PUSCH, and therefore CG PUSCH is HP CG PUSCH and DG PUSCH is LP DG PUSCH. In this case, the MAC entity of the terminal may deliver the uplink grant corresponding to the HP CG PUSCH with a higher priority to the HARQ entity, and further transmit the HP CG PUSCH to the network device side through the physical layer.

In fig. 6 (b), CG PUSCH has the same priority as DG PUSCH, and thus CG PUSCH and DG PUSCH are HP CG PUSCH and HP DG PUSCH, respectively. In this case, the MAC entity of the terminal may deliver the dynamic uplink grant to the HARQ entity, and further transmit the HP DG PUSCH to the network device side through the physical layer.

Further, in some embodiments, step S520 in fig. 5 may further include the following step 3: if the physical layer priorities of the first PUSCH and the second PUSCH are the same, and the dynamic uplink grant is not included in the first uplink grant and the second uplink grant (i.e., neither the first uplink grant nor the second uplink grant is a dynamic uplink grant), the terminal or the MAC entity of the terminal may deliver the first uplink grant or the second uplink grant to the HARQ entity according to the terminal implementation (UE implementation). By "according to terminal implementation" it is meant that it may be decided by the terminal itself whether to deliver the first uplink grant to the HARQ entity or the second uplink grant to the HARQ entity.

Taking the example that the first information includes the physical layer priority of the first PUSCH and/or the physical layer priority of the second PUSCH, the uplink grant type of the first uplink grant and/or the uplink grant type of the second uplink grant, and whether the first PUSCH has UCI multiplexing and/or whether the second PUSCH has UCI multiplexing, step S520 in fig. 5 may include the following 3 steps:

Step 2: if the physical layer priorities of the first PUSCH and the second PUSCH are the same, and one of the first PUSCH and the second PUSCH has UCI multiplexing, the terminal or the MAC entity of the terminal delivers uplink grant corresponding to the PUSCH having UCI multiplexing to the HARQ entity. Accordingly, the network device receives the PUSCH with UCI multiplexing.

Step 3: if the first PUSCH and the second PUSCH both have UCI multiplexing and one of the first uplink grant and the second uplink grant is a dynamic uplink grant, the terminal or the MAC entity of the terminal delivers the dynamic uplink grant to the HARQ entity. Correspondingly, the network device is connected with the DG PUSCH.

Still taking fig. 6 as an example, in (c) of fig. 6, HP CG PUSCH overlaps PUCCH, so HP CG PUSCH has UCI multiplexed. In this case, although the priorities of the HP CG PUSCH and the HP DG PUSCH are the same, the MAC entity of the terminal may deliver the uplink grant corresponding to the HP CG PUSCH with UCI multiplexing to the HARQ entity, thereby transmitting the HP CG PUSCH to the network device side.

The advantages of this embodiment are: on the basis of ensuring the transmission performance of the service with high physical layer priority, the condition that the physical layer priority is the same is optimized, and the PUSCH with UCI multiplexing is ensured to be transmitted, so that the blind detection times of the base station can be reduced.

Further, in some embodiments, step S520 in fig. 5 may further include the following step 4: if the physical layer priorities of the first PUSCH and the second PUSCH are the same, the first PUSCH and the second PUSCH have UCI multiplexing or have no UCI multiplexing, and the first uplink grant and the second uplink grant do not include dynamic uplink grant, the terminal or the MAC entity of the terminal may deliver the first uplink grant or the second uplink grant to the HARQ entity according to the terminal implementation (UE implementation). By "according to terminal implementation" it is meant that it may be decided by the terminal itself whether to deliver the first uplink grant to the HARQ entity or the second uplink grant to the HARQ entity.

Example 2.2

The first PUSCH in embodiment 2.2 is scheduled by DCI, i.e. DG PUSCH. The second PUSCH is configured by the network device, CG PUSCH. If DG PUSCH and CG PUSCH overlap, embodiment 2.2 wishes to guarantee transmission of DG PUSCH. In order to ensure that transmission of DG PUSCH and ensure that the aforementioned problem that CG PUSCH with high physical layer priority cannot be transmitted does not exist, embodiment 2.2 requires that the physical layer priority of DG PUSCH is higher than or equal to that of CG PUSCH (the physical layer priority of DG PUSCH is higher than or equal to that of CG PUSCH means that the physical layer priority of DG PUSCH is higher than that of CG PUSCH, or that the physical layer priority of DG PUSCH is the same as that of CG PUSCH). In other words, the terminal does not expect the DG PUSCH to have a lower physical layer priority than the CG PUSCH. Since the terminal does not expect the DG PUSCH to have a physical layer priority lower than that of the CG PUSCH (i.e., the terminal does not expect the DG PUSCH to be a PUSCH with a low physical layer priority, and the CG PUSCH is a PUSCH with a high physical layer priority), the network device may avoid this from the scheduling point of view. With this embodiment 2.2, the terminal or the MAC entity of the terminal does not need to set an additional judgment condition as in embodiment 2.1, and only needs to directly process according to the current protocol, so that the implementation manner of the terminal or the MAC layer of the terminal can be simplified.

In the following, with reference to fig. 7, the uplink transmission procedure is taken as an example, and embodiment 2.2 is illustrated in more detail.

As shown in fig. 7, in step S710a, the terminal determines whether to configure a priority based on a logical channel, and DG PUSCH and CG PUSCH overlap. If DG PUSCH and CG PUSCH overlap, the terminal continues to execute step S720, and transmits DG PUSCH to the network device. Accordingly, in step S710b, the network device determines whether the terminal is configured with a priority based on a logical channel, and DG PUSCH and CG PUSCH overlap. If DG PUSCH and CG PUSCH overlap, the network device continues to step S720, and receives the DG PUSCH.

Taking fig. 8 as an example, the terminal does not expect the situation shown in fig. 8 (a), that is, the terminal does not expect CG PUSCH to be HP CG PUSCH and DG PUSCH to be LP DG PUSCH. The network device will avoid this from a scheduling point of view.

Alternatively, in some embodiments, if the physical layer priorities of DG PUSCH and CG PUSCH are the same, the terminal does not expect DG PUSCH without UCI multiplexing, while CG PUSCH has UCI multiplexing. In other words, the terminal is expected to only occur in one of several cases: the first PUSCH and the second PUSCH are multiplexed by UCI; the first PUSCH has UCI multiplexing, and the second PUSCH has no UCI multiplexing; neither the first PUSCH nor the second PUSCH has UCI multiplexing. Since the terminal does not expect no UCI multiplexing on DG PUSCH, but UCI multiplexing on CG PUSCH, the network device may avoid this from the scheduling point of view. The scheme has the advantages that the DGPUSCH without UCI multiplexing is ensured not to block (block) the transmission of the CG PUSCH with UCI multiplexing, so that the blind detection times of the base station can be reduced.

Taking fig. 8 as an example, the terminal does not expect the situation shown in fig. 8 (b), that is, the terminal does not expect the HP CG PUSCH and the HP DG PUSCH with the same physical layer priority to overlap the HP PUCCH (i.e., the HP CG PUSCH has UCI multiplexing), but the HP DG PUSCH does not overlap the HP PUCCH (i.e., the HP DG PUSCH has no UCI multiplexing). The network device will avoid this from a scheduling point of view.

It should be noted that, embodiment 2 is mainly illustrated on the premise that the first PUSCH and the second PUSCH overlap, and in some embodiments, the preconditions may further include one or more of the following conditions: the terminal or MAC entity is not configured with priority based on the logical channel and configured with uplink skipping. The terminal or MAC entity configures uplink skip, which may mean that the parameter enhanced skip uplink txdate or enhanced skip uplink txconfiguration is configured as "true".

It should be noted that, the overlapping of two resources in each embodiment of the present application may refer to that two resources overlap entirely or may refer to that two resources overlap partially. In some embodiments, two resources overlap may refer to two resources overlapping in the time domain.

Example 3

The method embodiment of the present application is described in detail above in connection with examples 1 and 2, and the apparatus embodiment of the present application is described in detail below in connection with example 3. It is to be understood that the description of the method embodiments corresponds to the description of the device embodiments, and that parts not described in detail can therefore be seen in the preceding method embodiments.

Fig. 9 is a schematic block diagram of a terminal according to an embodiment of the present application. The terminal 900 in fig. 9 includes a judging unit 910 and a generating unit 920. The judging unit 910 is configured to judge whether the first condition is satisfied. The generating unit 920 is configured to not generate a MAC PDU for the first HARQ entity if the first condition is satisfied.

The first condition is determined by at least one of the following information: a PUCCH format of a first resource, where the first resource is configured for SR by a network device; a PUCCH format of a second resource, wherein the second resource is a resource carrying HARQ-ACK; whether the first resource and the second resource overlap; and whether the first resource and the third resource overlap, wherein the third resource is a resource for bearing a first PUSCH, and the first PUSCH is used for bearing the MAC PDU.

Optionally, the first condition includes: the first resource and the second resource do not overlap; and/or the first resource and the third resource do not overlap.

Optionally, the first condition includes: the PUCCH format of the first resource is PUCCH format 0, and/or the PUCCH format of the first resource is PUCCH format 1, and at least one of the second resource and the third resource is not overlapped with the first resource.

Optionally, the first condition includes: the PUCCH format of the first resource is PUCCH format 0, and/or the PUCCH format of the first resource is PUCCH format 1, the PUCCH format of the second resource is PUCCH format 1, and at least one of the second resource and the third resource is not overlapped with the first resource.

Optionally, the first condition includes: the PUCCH format of the second resource is not PUCCH format 1.

Optionally, the second resource and the third resource overlap.

Fig. 10 is a schematic block diagram of a terminal according to another embodiment of the present application. Terminal 1000 of fig. 10 includes acquisition unit 1010 and determination unit 1020.

The obtaining unit 1010 is configured to obtain a first uplink grant and a second uplink grant, where the first uplink grant corresponds to a first PUSCH and the second uplink grant corresponds to a second PUSCH.

The determining unit 1020 is configured to determine, according to the first information, an uplink grant delivered to the HARQ entity if the first PUSCH and the second PUSCH overlap, where the uplink grant delivered to the HARQ entity is the first uplink grant or the second uplink grant.

The first information includes at least one of: the physical layer priority of the first PUSCH; the physical layer priority of the second PUSCH; the uplink authorization type of the first uplink authorization; the uplink authorization type of the second uplink authorization; whether the first PUSCH has UCI multiplexing or not; and whether the second PUSCH has UCI multiplexing.

Optionally, the determining unit 1020 is configured to, if the physical layer priorities of the first PUSCH and the second PUSCH are different, deliver an uplink grant corresponding to a PUSCH with a higher physical layer priority to the HARQ entity.

Optionally, the determining unit 1020 is configured to deliver the dynamic uplink grant to the HARQ entity if the physical layer priorities of the first PUSCH and the second PUSCH are the same and one of the first uplink grant and the second uplink grant is the dynamic uplink grant.

Optionally, the determining unit 1020 is configured to deliver the first uplink grant or the second uplink grant to the HARQ entity according to the terminal implementation if the physical layer priorities of the first PUSCH and the second PUSCH are the same and the dynamic uplink grant is not included in the first uplink grant and the second uplink grant.

Optionally, the determining unit 1020 is configured to, if the physical layer priorities of the first PUSCH and the second PUSCH are the same, and one of the first PUSCH and the second PUSCH has UCI multiplexing, transmit an uplink grant corresponding to the PUSCH having UCI multiplexing to the HARQ entity.

Optionally, the determining unit 1020 is configured to deliver the dynamic uplink grant to the HARQ entity if the first PUSCH and the second PUSCH have UCI multiplexing and one of the first uplink grant and the second uplink grant is a dynamic uplink grant.

Optionally, one of the first uplink grant and the second uplink grant is a dynamic uplink grant, and the other is a configured uplink grant.

Optionally, the MAC entity of the terminal is not configured based on the priority of the logical channel.

Fig. 11 is a schematic block diagram of a terminal according to still another embodiment of the present application. The terminal 1100 of fig. 11 includes a judging unit 1110 and a communication unit 1120.

The determining unit 1110 is configured to determine whether the first PUSCH and the second PUSCH overlap.

The communication unit 1120 is configured to send the first PUSCH to the network device if the first PUSCH and the second PUSCH overlap; the first PUSCH is scheduled by DCI, the second PUSCH is configured by a network device, and the physical layer priority of the first PUSCH is higher than or equal to the physical layer priority of the second PUSCH.

Optionally, the terminal does not expect the physical layer priority of the first PUSCH to be lower than the physical layer priority of the second PUSCH.

Optionally, the first PUSCH and the second PUSCH satisfy at least one of the following conditions: the first PUSCH and the second PUSCH are multiplexed by UCI; the first PUSCH has UCI multiplexing, and the second PUSCH has no UCI multiplexing; the first PUSCH and the second PUSCH are both free of UCI multiplexing.

Alternatively, the terminal does not expect the first PUSCH without UCI multiplexing, and the second PUSCH with UCI multiplexing.

Fig. 12 is a schematic block diagram of a network device according to an embodiment of the present application. The network device 1200 of fig. 12 includes a determination unit 1210 and a communication unit 1220.

The determining unit 1210 is configured to determine whether the first condition is satisfied.

The communication unit 1220 is configured to not receive the first PUSCH in the case where the first condition is satisfied.

The first condition is determined by at least one of the following information: a PUCCH format of a first resource, where the first resource is configured for SR by a network device; a PUCCH format of a second resource, wherein the second resource is a resource carrying HARQ-ACK; whether the first resource and the second resource overlap; whether the first resource and the third resource overlap or not, wherein the third resource is a resource for bearing the first PUSCH.

Optionally, the second resource and the third resource overlap.

Optionally, the terminal is not configured based on the priority of the logical channel.

Fig. 13 is a schematic block diagram of a network device according to another embodiment of the present application. The network device 1300 of fig. 13 includes a judging unit 1310 and a communication unit 1320.

The determining unit 1310 is configured to determine whether the first PUSCH and the second PUSCH overlap.

The communication unit 1320 is configured to receive the first PUSCH or the second PUSCH from the terminal according to the first information if the first PUSCH and the second PUSCH overlap.

The first information includes at least one of: the physical layer priority of the first PUSCH; the physical layer priority of the second PUSCH; the type of the uplink grant corresponding to the first PUSCH; the type of the uplink grant corresponding to the second PUSCH; whether the first PUSCH has UCI multiplexing or not; and whether the second PUSCH has UCI multiplexing.

Optionally, the communication unit 1320 is configured to receive a PUSCH with a higher physical layer priority if the physical layer priorities of the first PUSCH and the second PUSCH are different.

Optionally, the communication unit 1320 is configured to receive a dynamically authorized PUSCH if the physical layer priorities of the first PUSCH and the second PUSCH are the same, and one of the first PUSCH and the second PUSCH is a dynamically authorized PUSCH.

Optionally, the communication unit 1320 is configured to receive the PUSCH with UCI multiplexing if the physical layer priorities of the first PUSCH and the second PUSCH are the same, and one of the first PUSCH and the second PUSCH has UCI multiplexing.

Optionally, the communication unit 1320 is configured to receive the dynamically authorized PUSCH if the first PUSCH and the second PUSCH are both UCI multiplexed, and one of the first PUSCH and the second PUSCH is a dynamically authorized PUSCH.

Fig. 14 is a schematic block diagram of a network device according to another embodiment of the present application. The network device 1400 of fig. 14 includes a determination unit 1410 and a communication unit 1420.

The determining unit 1410 is configured to determine whether the first PUSCH and the second PUSCH overlap.

The communication unit 1420 is configured to receive a first PUSCH from the terminal if the first PUSCH and a second PUSCH overlap; the first PUSCH is scheduled by DCI, the second PUSCH is configured by a network device, and the physical layer priority of the first PUSCH is higher than or equal to the physical layer priority of the second PUSCH.

Optionally, the physical layer priority of the first PUSCH is higher than or equal to the physical layer priority of the second PUSCH is configured by the network device. In other words, the relationship between the physical layer priority of the first PUSCH and the physical layer priority of the second PUSCH is configured by the network device, i.e., the physical layer priority of the first PUSCH is configured by the network device to be higher than or equal to the physical layer priority of the second PUSCH.

Optionally, the first PUSCH has no UCI multiplexing, and the case where the second PUSCH has UCI multiplexing is avoided by the network device in a scheduled manner.

Fig. 15 is a schematic block diagram of an apparatus for uplink transmission according to an embodiment of the present application. The dashed lines in fig. 15 indicate that the unit or module is optional. The apparatus 1500 may be used to implement the methods described in the method embodiments above. The apparatus 1500 may be a chip, a terminal or a network device.

The apparatus 1500 may include one or more processors 1510. The processor 1510 may support the apparatus 1500 to implement the methods described in the method embodiments above. The processor 1510 may be a general-purpose processor or a special-purpose processor. For example, the processor may be a central processing unit (central processing unit, CPU). Alternatively, the processor may be another general purpose processor, a digital signal processor (digital signal processor, DSP), an application specific integrated circuit (application specific integrated circuit, ASIC), an off-the-shelf programmable gate array (field programmable gate array, FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware components, or the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.

The apparatus 1500 may also include one or more memories 1520. The memory 1520 has stored thereon a program that can be executed by the processor 1510 such that the processor 1510 performs the methods described in the method embodiments above. The memory 1520 may be separate from the processor 1510 or may be integrated within the processor 1510.

The apparatus 1500 may also include a transceiver 1530. The processor 1510 may communicate with other devices or chips through a transceiver 1530. For example, the processor 1510 may transmit data to and receive data from other devices or chips through the transceiver 1530.

The embodiment of the application also provides a computer readable storage medium for storing a program. The computer-readable storage medium may be applied to a terminal or a network device provided in an embodiment of the present application, and the program causes a computer to execute the method performed by the terminal or the network device in the respective embodiments of the present application.

The embodiment of the application also provides a computer program product. The computer program product includes a program. The computer program product may be applied to a terminal or a network device provided in an embodiment of the present application, and the program causes a computer to execute the method executed by the terminal or the network device in the respective embodiments of the present application.

The embodiment of the application also provides a computer program. The computer program can be applied to a terminal or a network device provided in an embodiment of the present application, and cause a computer to perform a method performed by the terminal or the network device in each embodiment of the present application.

It should be understood that in embodiments of the present application, "B corresponding to a" means that B is associated with a, from which B may be determined. It should also be understood that determining B from a does not mean determining B from a alone, but may also determine B from a and/or other information.

It should be understood that the term "and/or" is merely an association relationship describing the associated object, and means that three relationships may exist, for example, a and/or B may mean: a exists alone, A and B exist together, and B exists alone. In addition, the character "/" herein generally indicates that the front and rear associated objects are an "or" relationship.

It should be understood that, in various embodiments of the present application, the sequence numbers of the foregoing processes do not mean the order of execution, and the order of execution of the processes should be determined by the functions and internal logic thereof, and should not constitute any limitation on the implementation process of the embodiments of the present application.

The foregoing is merely illustrative of the present application, and the present application is not limited thereto, and any person skilled in the art will readily recognize that variations or substitutions are within the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

An uplink transmission method, comprising:

under the condition that the first condition is met, the terminal does not generate a media access control protocol data unit (MAC PDU) for the first hybrid automatic repeat request (HARQ) entity;

the first condition is determined by at least one of the following information:

a physical uplink control channel format (PUCCH) format of a first resource, wherein the first resource is configured for a Scheduling Request (SR) by a network device;

a Physical Uplink Control Channel (PUCCH) format of a second resource, wherein the second resource is a resource for bearing hybrid automatic repeat request-acknowledgement (HARQ-ACK);

whether the first resource and the second resource overlap; and

whether the first resource and the third resource overlap or not, wherein the third resource is a resource for carrying a first physical uplink shared channel PUSCH, and the first PUSCH is used for carrying the MAC PDU.
The method of claim 1, wherein the first condition comprises:

the first resource and the second resource do not overlap; and/or

The first resource and the third resource do not overlap.
The method according to claim 1 or 2, wherein the first condition comprises:

the PUCCH format of the first resource is PUCCH format 0, and/or,

the PUCCH format of the first resource is PUCCH format 1, and at least one of the second resource and the third resource is not overlapped with the first resource.
The method of claim 1, wherein the first condition comprises:

the PUCCH format of the first resource is PUCCH format 0, and/or,

the PUCCH format of the first resource is PUCCH format 1, the PUCCH format of the second resource is PUCCH format 1, and at least one of the second resource and the third resource is not overlapped with the first resource.
The method of any one of claims 1-4, wherein the first condition comprises:

the PUCCH format of the second resource is not PUCCH format 1.
The method of any of claims 1-5, wherein the second resource and the third resource overlap.
An uplink transmission method, comprising:

a Media Access Control (MAC) entity obtains a first uplink grant and a second uplink grant, wherein the first uplink grant corresponds to a first Physical Uplink Shared Channel (PUSCH), and the second uplink grant corresponds to a second PUSCH;

if the first PUSCH and the second PUSCH overlap, the MAC entity determines, according to first information, an uplink grant delivered to a hybrid automatic repeat request HARQ entity, where the uplink grant delivered to the HARQ entity is the first uplink grant or the second uplink grant;

wherein the first information includes at least one of:

the physical layer priority of the first PUSCH;

the physical layer priority of the second PUSCH;

the uplink authorization type of the first uplink authorization;

the uplink authorization type of the second uplink authorization;

whether the first PUSCH has uplink control information UCI multiplexing or not; and

and whether the second PUSCH has UCI multiplexing or not.
The method of claim 7 wherein the MAC entity determining the uplink grant to deliver to the HARQ entity based on the first information comprises:

and if the physical layer priorities of the first PUSCH and the second PUSCH are different, the MAC entity transmits uplink authorization corresponding to the PUSCH with higher physical layer priority to the HARQ entity.
The method of claim 7 wherein the MAC entity determining the uplink grant to deliver to the HARQ entity based on the first information comprises:

and if the physical layer priorities of the first PUSCH and the second PUSCH are the same and one of the first uplink grant and the second uplink grant is a dynamic uplink grant, the MAC entity transmits the dynamic uplink grant to the HARQ entity.
The method of claim 7 wherein the MAC entity determining the uplink grant to deliver to the HARQ entity based on the first information comprises:

and if the physical layer priorities of the first PUSCH and the second PUSCH are the same and the dynamic uplink grant is not included in the first uplink grant and the second uplink grant, the MAC entity delivers the first uplink grant or the second uplink grant to the HARQ entity according to the terminal implementation.
The method of claim 7 wherein the MAC entity determining the uplink grant to deliver to the HARQ entity based on the first information comprises:

and if the physical layer priorities of the first PUSCH and the second PUSCH are the same and one of the first PUSCH and the second PUSCH has UCI multiplexing, the MAC entity transmits uplink authorization corresponding to the PUSCH with UCI multiplexing to the HARQ entity.
The method of claim 11 wherein the MAC entity determining an uplink grant to deliver to the HARQ entity based on the first information, further comprising:

and if the first PUSCH and the second PUSCH both have UCI multiplexing and one of the first uplink grant and the second uplink grant is a dynamic uplink grant, the MAC entity delivers the dynamic uplink grant to the HARQ entity.
The method of any of claims 7-9, 11-12, wherein one of the first and second upstream grants is a dynamic upstream grant and the other is a configured upstream grant.
The method according to any of claims 7-13, wherein the MAC entity is not configured to be based on a priority of a logical channel.
An uplink transmission method, comprising:

if the first Physical Uplink Shared Channel (PUSCH) and the second PUSCH are overlapped, the terminal sends the first PUSCH to the network equipment;

the first PUSCH is scheduled by downlink control information DCI, the second PUSCH is configured by the network device, and a physical layer priority of the first PUSCH is higher than or equal to a physical layer priority of the second PUSCH.
The method of claim 15, wherein the terminal does not expect the physical layer priority of the first PUSCH to be lower than the physical layer priority of the second PUSCH.
The method of claim 15 or 16, wherein the first PUSCH and the second PUSCH satisfy at least one of the following conditions:

the first PUSCH and the second PUSCH are multiplexed by uplink control information UCI;

the first PUSCH has UCI multiplexing, and the second PUSCH has no UCI multiplexing;

the first PUSCH and the second PUSCH are both free of UCI multiplexing.
The method of claim 15 or 16, wherein the terminal does not expect the first PUSCH without UCI multiplexing and the second PUSCH with UCI multiplexing.
The method according to any of claims 15-18, wherein the terminal is not configured based on a priority of a logical channel.
An uplink transmission method, comprising:

under the condition that the first condition is met, the network equipment does not receive a first Physical Uplink Shared Channel (PUSCH);

the first condition is determined by at least one of the following information:

a physical uplink control channel format (PUCCH) format of a first resource, wherein the first resource is configured for a Scheduling Request (SR) by a network device;

A Physical Uplink Control Channel (PUCCH) format of a second resource, wherein the second resource is a resource for bearing hybrid automatic repeat request-acknowledgement (HARQ-ACK);

whether the first resource and the second resource overlap;

whether the first resource and the third resource overlap or not, wherein the third resource is a resource for bearing the first PUSCH.
The method of claim 20, wherein the first condition comprises:

the first resource and the second resource do not overlap; and/or

The first resource and the third resource do not overlap.
The method of claim 20 or 21, wherein the first condition comprises:

the PUCCH format of the first resource is PUCCH format 0, and/or,

the PUCCH format of the first resource is PUCCH format 1, and at least one of the second resource and the third resource is not overlapped with the first resource.
The method of claim 20, wherein the first condition comprises:

the PUCCH format of the first resource is PUCCH format 0, and/or,

the PUCCH format of the first resource is PUCCH format 1, the PUCCH format of the second resource is PUCCH format 1, and at least one of the second resource and the third resource is not overlapped with the first resource.
The method of any one of claims 20-23, wherein the first condition comprises:

the PUCCH format of the second resource is not PUCCH format 1.
The method of any of claims 20-24, wherein the second resource and the third resource overlap.
An uplink transmission method, comprising:

if the first Physical Uplink Shared Channel (PUSCH) and the second PUSCH are overlapped, the network equipment receives the first PUSCH or the second PUSCH from the terminal according to the first information;

wherein the first information includes at least one of:

the physical layer priority of the first PUSCH;

the physical layer priority of the second PUSCH;

the type of the uplink grant corresponding to the first PUSCH;

the type of the uplink grant corresponding to the second PUSCH;

whether the first PUSCH has uplink control information UCI multiplexing or not; and

and whether the second PUSCH has UCI multiplexing or not.
The method of claim 26, wherein the network device receiving the first PUSCH or the second PUSCH from a terminal according to first information comprises:

and if the physical layer priorities of the first PUSCH and the second PUSCH are different, the network device receives the PUSCH with higher physical layer priority.
The method of claim 26, wherein the network device receiving the first PUSCH or the second PUSCH from a terminal according to first information comprises:

and if the physical layer priorities of the first PUSCH and the second PUSCH are the same and one of the first PUSCH and the second PUSCH is a dynamically authorized PUSCH, the network device receives the dynamically authorized PUSCH.
The method of claim 26, wherein the network device receiving the first PUSCH or the second PUSCH from a terminal according to first information comprises:

and if the physical layer priorities of the first PUSCH and the second PUSCH are the same and one of the first PUSCH and the second PUSCH is UCI multiplexed, the network device receives the PUSCH with UCI multiplexing.
The method of claim 29, wherein the network device receives the first PUSCH or the second PUSCH from a terminal according to first information, further comprising:

and if the first PUSCH and the second PUSCH are both UCI multiplexed and one of the first PUSCH and the second PUSCH is a dynamically authorized PUSCH, the network device receives the dynamically authorized PUSCH.
The method of any of claims 26-30, wherein one of the first and second upstream grants is a dynamic upstream grant and the other is a configured upstream grant.
The method according to any of claims 26-31, wherein the terminal is not configured based on a priority of a logical channel.
An uplink transmission method, comprising:

if the first Physical Uplink Shared Channel (PUSCH) and the second PUSCH are overlapped, the network device receives the first PUSCH from the terminal;

the first PUSCH is scheduled by downlink control information DCI, the second PUSCH is configured by a network device, and a physical layer priority of the first PUSCH is higher than or equal to a physical layer priority of the second PUSCH.
The method of claim 33, wherein the physical layer priority of the first PUSCH is higher than or equal to the physical layer priority of the second PUSCH is configured by the network device.
The method of claim 33 or 34, wherein the first PUSCH and the second PUSCH satisfy at least one of the following conditions:

the first PUSCH and the second PUSCH are multiplexed by uplink control information UCI;

The first PUSCH has UCI multiplexing, and the second PUSCH has no UCI multiplexing;

the first PUSCH and the second PUSCH are both free of UCI multiplexing.
The method of claim 33 or 34, wherein the first PUSCH has no UCI multiplexing and the second PUSCH has UCI multiplexing is avoided by the network device in a scheduled manner.
The method according to any of claims 33-36, wherein the terminal is not configured based on a priority of a logical channel.
A terminal, comprising:

a generating unit, configured to, when the first condition is met, not generate a media access control protocol data unit MAC PDU for the first hybrid automatic repeat request HARQ entity;

the first condition is determined by at least one of the following information:

a physical uplink control channel format (PUCCH) format of a first resource, wherein the first resource is configured for a Scheduling Request (SR) by a network device;

a Physical Uplink Control Channel (PUCCH) format of a second resource, wherein the second resource is a resource for bearing hybrid automatic repeat request-acknowledgement (HARQ-ACK);

whether the first resource and the second resource overlap; and

whether the first resource and the third resource overlap or not, wherein the third resource is a resource for carrying a first physical uplink shared channel PUSCH, and the first PUSCH is used for carrying the MAC PDU.
The terminal of claim 38, wherein the first condition comprises:

the first resource and the second resource do not overlap; and/or

The first resource and the third resource do not overlap.
The terminal according to claim 38 or 39, wherein the first condition comprises:

the PUCCH format of the first resource is PUCCH format 0, and/or,

the PUCCH format of the first resource is PUCCH format 1, and at least one of the second resource and the third resource is not overlapped with the first resource.
The terminal of claim 38, wherein the first condition comprises:

the PUCCH format of the first resource is PUCCH format 0, and/or,

the PUCCH format of the first resource is PUCCH format 1, the PUCCH format of the second resource is PUCCH format 1, and at least one of the second resource and the third resource is not overlapped with the first resource.
The terminal according to any of the claims 38-41, wherein the first condition comprises:

the PUCCH format of the second resource is not PUCCH format 1.
The terminal of any of claims 38-42, wherein the second resource and the third resource overlap.
A terminal, comprising:

an obtaining unit, configured to obtain a first uplink grant and a second uplink grant, where the first uplink grant corresponds to a first physical uplink shared channel PUSCH and the second uplink grant corresponds to a second PUSCH;

a determining unit, configured to determine, according to first information, an uplink grant delivered to a hybrid automatic repeat request HARQ entity if the first PUSCH and the second PUSCH overlap, where the uplink grant delivered to the HARQ entity is the first uplink grant or the second uplink grant;

wherein the first information includes at least one of:

the physical layer priority of the first PUSCH;

the physical layer priority of the second PUSCH;

the uplink authorization type of the first uplink authorization;

the uplink authorization type of the second uplink authorization;

whether the first PUSCH has uplink control information UCI multiplexing or not; and

and whether the second PUSCH has UCI multiplexing or not.
The terminal of claim 44, wherein the determining unit is configured to transmit an uplink grant corresponding to a PUSCH with a higher physical layer priority to the HARQ entity if the physical layer priorities of the first PUSCH and the second PUSCH are different.
The terminal of claim 44, wherein the determining unit is configured to deliver the dynamic uplink grant to the HARQ entity if the physical layer priorities of the first PUSCH and the second PUSCH are the same and one of the first uplink grant and the second uplink grant is a dynamic uplink grant.
The terminal of claim 44, wherein the determining unit is configured to deliver the first uplink grant or the second uplink grant to the HARQ entity according to a terminal implementation if the physical layer priorities of the first PUSCH and the second PUSCH are the same and the dynamic uplink grant is not included in the first uplink grant and the second uplink grant.
The terminal of claim 44, wherein the determining unit is configured to deliver an uplink grant corresponding to a PUSCH with UCI multiplexing to a HARQ entity if physical layer priorities of the first PUSCH and the second PUSCH are the same and one of the first PUSCH and the second PUSCH has UCI multiplexing.
The terminal of claim 48, wherein the determining unit is configured to deliver the dynamic uplink grant to the HARQ entity if the first PUSCH and the second PUSCH are both UCI multiplexed and one of the first uplink grant and the second uplink grant is a dynamic uplink grant.
The terminal of any of claims 44-46, 48-49, wherein one of the first and second upstream grants is a dynamic upstream grant and the other is a configured upstream grant.
The terminal according to any of claims 44-50, characterized in that the medium access control, MAC, entity of the terminal is not configured for logical channel based priority.
A terminal, comprising:

a communication unit, configured to send a first physical uplink shared channel PUSCH and a second PUSCH to a network device if the first PUSCH and the second PUSCH overlap;

the first PUSCH is scheduled by downlink control information DCI, the second PUSCH is configured by a network device, and a physical layer priority of the first PUSCH is higher than or equal to a physical layer priority of the second PUSCH.
The terminal of claim 52, wherein the terminal does not expect the physical layer priority of the first PUSCH to be lower than the physical layer priority of the second PUSCH.
The terminal of claim 52 or 53, wherein the first PUSCH and the second PUSCH satisfy at least one of:

The first PUSCH and the second PUSCH are multiplexed by uplink control information UCI;

the first PUSCH has UCI multiplexing, and the second PUSCH has no UCI multiplexing;

the first PUSCH and the second PUSCH are both free of UCI multiplexing.
The terminal of claim 52 or 53, wherein the terminal does not expect the first PUSCH without UCI multiplexing and the second PUSCH with UCI multiplexing.
The terminal according to any of claims 52-55, wherein the terminal is not configured to be based on a priority of a logical channel.
A network device, comprising:

a communication unit, configured to not receive a first physical uplink shared channel PUSCH when a first condition is satisfied;

the first condition is determined by at least one of the following information:

a physical uplink control channel format (PUCCH) format of a first resource, wherein the first resource is configured for a Scheduling Request (SR) by a network device;

a Physical Uplink Control Channel (PUCCH) format of a second resource, wherein the second resource is a resource for bearing hybrid automatic repeat request-acknowledgement (HARQ-ACK);

whether the first resource and the second resource overlap;

whether the first resource and the third resource overlap or not, wherein the third resource is a resource for bearing the first PUSCH.
The network device of claim 57, wherein the first condition comprises:

the first resource and the second resource do not overlap; and/or

The first resource and the third resource do not overlap.
The network device of claim 57 or 58, wherein the first condition comprises:

the PUCCH format of the first resource is PUCCH format 0, and/or,

the PUCCH format of the first resource is PUCCH format 1, and at least one of the second resource and the third resource is not overlapped with the first resource.
The network device of claim 57, wherein the first condition comprises:

the PUCCH format of the first resource is PUCCH format 0, and/or,

the PUCCH format of the first resource is PUCCH format 1, the PUCCH format of the second resource is PUCCH format 1, and at least one of the second resource and the third resource is not overlapped with the first resource.
The network device of any one of claims 57-60, wherein the first condition comprises:

the PUCCH format of the second resource is not PUCCH format 1.
The network device of any of claims 57-61, wherein the second resource and the third resource overlap.
A network device, comprising:

a communication unit, configured to receive, from a terminal, a first PUSCH or a second PUSCH according to first information if the first physical uplink shared channel PUSCH and the second PUSCH overlap;

wherein the first information includes at least one of:

the physical layer priority of the first PUSCH;

the physical layer priority of the second PUSCH;

the type of the uplink grant corresponding to the first PUSCH;

the type of the uplink grant corresponding to the second PUSCH;

whether the first PUSCH has uplink control information UCI multiplexing or not; and

and whether the second PUSCH has UCI multiplexing or not.
The network device of claim 63, wherein the communication unit is configured to receive a PUSCH with a higher priority for physical layers if the first PUSCH and the second PUSCH have different priorities.
The network device of claim 63, wherein the communication unit is configured to receive a dynamically granted PUSCH if the physical layer priorities of the first PUSCH and the second PUSCH are the same, and one of the first PUSCH and the second PUSCH is a dynamically granted PUSCH.
The network device of claim 63, wherein the communication unit is configured to receive the UCI-multiplexed PUSCH if the physical layer priorities of the first PUSCH and the second PUSCH are the same, and one of the first PUSCH and the second PUSCH has UCI multiplexing.
The network device of claim 66, wherein the communication unit is configured to receive the dynamically granted PUSCH if the first PUSCH and the second PUSCH are both UCI multiplexed and one of the first PUSCH and the second PUSCH is a dynamically granted PUSCH.
The network device of any of claims 63-67, wherein one of the first and second upstream grants is a dynamic upstream grant and the other is a configured upstream grant.
The network device of any one of claims 63-68, wherein the terminal is not configured to be based on a priority of a logical channel.
A network device, comprising:

a communication unit, configured to receive a first physical uplink shared channel PUSCH from the terminal if the first PUSCH overlaps with a second PUSCH;

The first PUSCH is scheduled by downlink control information DCI, the second PUSCH is configured by a network device, and a physical layer priority of the first PUSCH is higher than or equal to a physical layer priority of the second PUSCH.
The network device of claim 70, wherein the physical layer priority of the first PUSCH is higher than or equal to the physical layer priority of the second PUSCH is configured by the network device.
The network device of claim 70 or 71, wherein the first PUSCH and the second PUSCH satisfy at least one of:

the first PUSCH and the second PUSCH are multiplexed by uplink control information UCI;

the first PUSCH has UCI multiplexing, and the second PUSCH has no UCI multiplexing;

the first PUSCH and the second PUSCH are both free of UCI multiplexing.
The network device of claim 70 or 71, wherein the first PUSCH has no UCI multiplexing and the second PUSCH has UCI multiplexing is avoided by the network device in a scheduled manner.
The network device of any of claims 70-73, wherein the terminal is not configured to be based on a priority of a logical channel.
A terminal comprising a memory for storing a program and a processor for invoking the program in the memory to perform the method of any of claims 1-19.
A network device comprising a memory for storing a program and a processor for invoking the program in the memory to perform the method of any of claims 20-37.
An apparatus comprising a processor configured to invoke a program from memory to perform the method of any of claims 1-19.
An apparatus comprising a processor configured to invoke a program from memory to perform the method of any of claims 20-37.
A chip comprising a processor for calling a program from a memory, causing a device on which the chip is mounted to perform the method of any one of claims 1-19.
A chip comprising a processor for calling a program from a memory, causing a device on which the chip is mounted to perform the method of any of claims 20-37.
A computer-readable storage medium, having stored thereon a program that causes a computer to perform the method of any of claims 1-19.
A computer-readable storage medium, having stored thereon a program that causes a computer to perform the method of any of claims 20-37.
A computer program product comprising a program for causing a computer to perform the method of any one of claims 1-19.
A computer program product comprising a program for causing a computer to perform the method of any one of claims 20-37.
A computer program, characterized in that the computer program causes a computer to perform the method according to any one of claims 1-19.
A computer program, characterized in that the computer program causes a computer to perform the method according to any of claims 20-37.