WO2023272599A1

WO2023272599A1 - Uplink transmission methods, terminal, and network device

Info

Publication number: WO2023272599A1
Application number: PCT/CN2021/103655
Authority: WO
Inventors: 张轶
Original assignee: Oppo广东移动通信有限公司
Priority date: 2021-06-30
Filing date: 2021-06-30
Publication date: 2023-01-05
Also published as: CN116941301A

Abstract

Provided are uplink transmission methods, a terminal, and a network device. An uplink transmission method comprises: when a first condition is satisfied, a terminal does not generate a MAC PDU for a first HARQ entity, the first condition being determined by at least one of the following information: a PUCCH format of a first resource, the first resource being configured by a network device for an SR; a PUCCH format of a second resource, the second resource being a HARQ-ACK resource; whether the first resource and the second resource overlap; and whether the first resource and a third resource overlap, the third resource being a resource that carries a first PUSCH, and the first PUSCH being used for carrying the MAC PDU. In embodiments of the present application, the first condition is added to conditions for enabling uplink skipping, which helps to prevent behavior disorders in a terminal.

Description

Uplink transmission method, terminal and network equipment

technical field

The present application relates to the technical field of communications, and more specifically, to an uplink transmission method, a terminal and a network device.

Background technique

Uplink skipping (uplink skipping) means that a terminal or a media access control (media access control, MAC) entity may not perform a hybrid automatic repeat reQuest (HARQ) request if certain conditions are met. ) entity generates a MAC protocol data unit (protocol data unit, PDU), and then the terminal does not need to transmit the physical uplink shared channel (physical uplink shared channel, PUSCH) corresponding to the MAC PDU through the physical layer.

Before enabling uplink skipping, the MAC entity needs to determine whether a condition for enabling uplink skipping is met. The setting of conditions for enabling uplink skipping in the current protocol is not perfect, which leads to disordered behavior of the terminal in some scenarios.

Contents of the invention

The present application provides an uplink transmission method, a terminal, and a network device, so as to avoid behavior disorder of the terminal, thereby improving the certainty of uplink transmission.

In a first aspect, an uplink transmission method is provided, including: when a first condition is met, the terminal does not generate a MAC PDU for a 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 the first resource, wherein the first resource is configured by the network device for a scheduling request (scheduling request, SR); a PUCCH format of the second resource, wherein, The second resource is a resource bearing HARQ-ACK; whether the first resource overlaps with the second resource; and whether the first resource overlaps with a third resource, wherein the third resource is a resource bearing the second A PUSCH resource, the first PUSCH is used to bear the MAC PDU.

In a second aspect, an uplink transmission method is provided, including: a MAC entity acquires 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 to be delivered to the HARQ entity according to the first information, and 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 following: the physical layer priority of the first PUSCH; the physical layer priority of the second PUSCH; the first uplink The uplink grant type of the grant; the uplink grant type of the second uplink grant; 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 a network device; wherein the first PUSCH is determined by downlink control information (downlink control information, DCI) scheduling, the second PUSCH is configured by the network device (for example, the network device is configured through high-level signaling, the high-level signaling can be, for example, radio resource control (radio resource control, RRC) signaling), and the first The physical layer priority of the 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: when a first condition is met, the network device does not receive the first PUSCH; the first condition is determined by at least one of the following information: the first resource PUCCH format, wherein, the first resource is configured for SR by the network device; PUCCH format of the second resource, wherein the second resource is a resource bearing HARQ-ACK; the first resource and the second Whether the resources overlap; whether the first resource and the third resource overlap, wherein the third resource is a resource 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 PUSCH The information includes at least one of the following: the physical layer priority of the first PUSCH; the physical layer priority of the second PUSCH; the type of uplink grant corresponding to the first PUSCH; the uplink grant corresponding to the second PUSCH The type of grant; whether the first PUSCH has UCI multiplexing; and whether the second PUSCH has UCI multiplexing.

In the 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; wherein, the first PUSCH is scheduled by DCI, and the second PUSCH The 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, a terminal is provided, including: a generating unit configured to not generate a MAC PDU for a first HARQ entity when a first condition is met; the first condition is determined by at least one of the following information of: the PUCCH format of the first resource, wherein the first resource is configured by the network device for SR; the PUCCH format of the second resource, wherein the second resource is a resource bearing HARQ-ACK; the first resource and whether the second resource overlaps; and whether the first resource overlaps with the third resource, wherein the third resource is a resource that bears the first PUSCH, and the first PUSCH is used to bear the MAC PDU.

In an eighth aspect, a terminal is provided, including: an obtaining unit, configured to obtain 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 The determination unit is configured to determine the uplink grant delivered to the HARQ entity according to the first information, where the first PUSCH and the second PUSCH overlap, and the uplink grant delivered to the HARQ entity is the first uplink grant or the first uplink grant Two uplink grants; wherein, the first information includes at least one of the following: the physical layer priority of the first PUSCH; the physical layer priority of the second PUSCH; the uplink grant type of the first uplink grant; The uplink grant type of the second uplink grant; whether the first PUSCH has UCI multiplexing; and whether the second PUSCH has UCI multiplexing.

In a ninth aspect, a terminal is provided, including: a communication unit, configured to send the first PUSCH to a network device if the first PUSCH and the second PUSCH overlap; wherein, the first PUSCH is scheduled by DCI, and the second PUSCH The 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, a network device is provided, including: a communication unit configured not to receive the first PUSCH when a first condition is met; the first condition is determined by at least one of the following information: the first A PUCCH format of a resource, wherein the first resource is configured by a network device for SR; a PUCCH format of a second resource, wherein the second resource is a resource bearing HARQ-ACK; the first resource and the Whether the second resource overlaps; whether the first resource and the third resource overlap, wherein the third resource is a resource bearing the first PUSCH.

In an eleventh aspect, a network device is provided, including: a communication unit, configured to receive the first PUSCH or the 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 following: the physical layer priority of the first PUSCH; the physical layer priority of the second PUSCH; the type of uplink grant corresponding to the first PUSCH; the second PUSCH The type of the corresponding uplink grant; whether the first PUSCH has UCI multiplexing; and whether the second PUSCH has UCI multiplexing.

In a twelfth aspect, a network device is provided, including: a communication unit, configured to receive the first PUSCH from the terminal if the first PUSCH and the second PUSCH overlap; wherein, 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, a terminal is provided, including a memory and a processor, the memory is used to store programs, and the processor is used to call the programs in the memory to execute any of the first to third aspects A method as described in one aspect.

In a fourteenth aspect, there is provided a network device, including a memory and a processor, the memory is used to store a program, and the processor is used to call the program in the memory to execute as in the fourth aspect to the sixth aspect The method described in any aspect.

In a fifteenth aspect, an apparatus is provided, including a processor, configured to call a program from a memory, so as to execute the method according to any one of the first aspect to the third aspect.

In a sixteenth aspect, an apparatus is provided, including a processor, configured to call a program from a memory, so as to execute the method according to any one of the fourth aspect to the sixth aspect.

In a seventeenth aspect, there is provided a chip, including a processor, configured to call a program from a memory, so that a device installed with the chip executes the method described in any one of the first to third aspects.

In an eighteenth aspect, a chip is provided, including a processor, configured to call a program from a memory, so that a device installed with the chip executes the method according to any one of the fourth aspect to the sixth aspect.

In a nineteenth aspect, a computer-readable storage medium is provided, on which a program is stored, and the program causes a computer to execute the method described in any one of the first to third aspects.

In a twentieth aspect, a computer-readable storage medium is provided, on which a program is stored, and the program causes a computer to execute the method according to any one of the fourth aspect to the sixth aspect.

In a twenty-first aspect, a computer program product is provided, including a program, the program causes a computer to execute the method according to any one of the first aspect to the third aspect.

A twenty-second aspect provides a computer program product, including a program, the program causes a computer to execute the method according to any one of the fourth aspect to the sixth aspect.

In a twenty-third aspect, a computer program is provided, the computer program causes a computer to execute the method according to any one of the first to third aspects.

In a twenty-fourth aspect, a computer program is provided, the computer program causes a computer to execute the method according to any one of the fourth aspect to the sixth aspect.

In the embodiment of the present application, a first condition is added to the conditions for enabling uplink skipping. The setting of the first condition considers at least one of the following information: the PUCCH format of the SR resource; the PUCCH format of the HARQ-ACK resource, whether the SR resource and the HARQ-ACK resource overlap, and whether the SR resource and the PUSCH resource overlap. The above information is the main information that may cause terminal behavior disorder in the uplink skip scenario. Considering this information when judging whether to enable uplink skip can help avoid terminal behavior disorder, thereby improving the certainty of uplink transmission.

Description of drawings

FIG. 1 is a schematic structural diagram of a wireless communication system 100 applied in an embodiment of the present application.

FIG. 2 is an example diagram of PUCCH and PUSCH colliding in the time domain.

Fig. 3 is a schematic flowchart of an uplink transmission method provided by an embodiment of the present application.

FIG. 4 is an example diagram of transmission schemes of SR, HARQ-ACK, and PUSCH.

Fig. 5 is a schematic flowchart of an uplink transmission method provided by another embodiment of the present application.

FIG. 6 is an example diagram of two PUSCHs in an overlapping state.

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

FIG. 8 is another example diagram of two PUSCHs in an overlapping state.

Fig. 9 is a schematic structural diagram of a terminal provided by an embodiment of the present application.

Fig. 10 is a schematic structural diagram of a terminal provided by another embodiment of the present application.

Fig. 11 is a schematic structural diagram of a terminal provided by another embodiment of the present application.

Fig. 12 is a schematic structural diagram of a network device provided by an embodiment of the present application.

Fig. 13 is a schematic structural diagram of a network device provided by another embodiment of the present application.

Fig. 14 is a schematic structural diagram of a network device provided by another embodiment of the present application.

Fig. 15 is a schematic structural diagram of a device provided by an embodiment of the present application.

detailed description

The technical solution in this application will be described below with reference to the accompanying drawings.

FIG. 1 is a wireless communication system 100 applied in an embodiment of the present application. The wireless communication system 100 may include a network device 110 and a terminal 120 . The network device 110 may be a device that communicates with the terminal 120 . The network device 110 may provide communication coverage for a specific geographic area, and may communicate with the terminals 120 located within the coverage area.

FIG. 1 exemplarily shows one network device and two terminals 120 . Optionally, the wireless communication system 100 may include multiple network devices and each network device may include one or more than two terminals within the coverage area, which is not limited in this embodiment of the present application.

Optionally, the wireless communication system 100 may further include other network entities such as a network controller and a mobility management entity, which is not limited in this 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 can be applied to one or more of the following communication systems: global system of mobile communication (GSM) system, 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 (GPRS), long term evolution (long term evolution, LTE) system, advanced long term evolution (advanced long term evolution, LTE-A) system , universal mobile telecommunications system (UMTS), new radio (new radio, NR), fifth generation mobile communication system (5th generation, 5G), etc.

It should also be understood that, in this embodiment of the present application, a terminal may also include, but not limited to, a mobile station (mobile station, MS), a mobile terminal (mobile terminal), a mobile phone (mobile telephone), a user equipment (user equipment, UE), Mobile phone (handset), portable equipment (portable equipment), etc., the terminal can communicate with one or more core networks via a radio access network (radio access network, RAN). For example, a 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, built-in computer or vehicle-mounted mobile device.

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

Example 1:

Embodiment 1 aims to solve the problems existing in the uplink skipping scenario. For ease of understanding, some concepts involved in Embodiment 1 are firstly explained below.

upstream skip

Uplink skipping means that if certain conditions are met, the terminal or MAC entity may not generate a MAC PDU for a certain HARQ entity, and then does not need to transmit the PUSCH corresponding to the MAC PDU to the network device through the physical layer. The current protocol stipulates that if any one of the following two conditions is met, the MAC entity may not generate a MAC PDU for a certain HARQ entity.

Case 1:

If the MAC entity configures the parameter enhancedSkipUplinkTxDynamic as "true (true)", and the uplink authorization indicated to the HARQ entity is scrambled by the cell-radio network temporary identifier (C-RNTI), or if the MAC entity configures If the parameter enhancedSkipUplinkTxConfigured is "true", and the uplink authorization indicated to the HARQ entity is the configured uplink authorization, if the following conditions are met, no MAC PDU will be generated for the HARQ entity:

1. The MAC entity is not configured with logical channel-based priority (lch-basedPrioritization);

2. If there is no UCI to be multiplexed on this PUSCH according to the description in related protocols (such as TS 38.213); and

3. If there is no aperiodic channel state information (CSI) request on this PUSCH according to the description in related protocols (such as TS 38.212); and

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

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

Case 2:

The MAC entity configures the parameter SkipUplinkTxDynamic as "true", and the uplink grant indicated to the HARQ entity is C-RNTI scrambling, or the uplink grant indicated to the HARQ entity is the configured uplink grant,

1. If there is no aperiodic CSI request on this PUSCH according to the description in related protocols (such as TS 38.212); and

2. If this MAC PDU contains 0 MAC SDUs; and

3. If this MAC PDU only contains periodic BSR and any LCG has no data, or this MAC PDU only contains padding BSR.

In the above two cases, the condition 2 of the case 1 describes that: if the overlapping of the PUCCH and the PUSCH similar to that shown in FIG. 2 occurs, it means that there is UCI multiplexing on the PUSCH. At this time, even if the MAC PDU corresponding to the PUSCH has no data, the MAC entity still needs to generate a MAC PDU to ensure that UCI can be multiplexed and transmitted on the PUSCH, thereby reducing the number of blind detections of the base station. Condition 2 of Case 1 is a condition that this application needs to focus on, because the technical problem to be solved in Embodiment 1 below mainly occurs in the uplink skip scenario corresponding to this condition.

SR and HARQ-ACK/CSI are multiplexed and transmitted in PUCCH

The UCI of some communication systems (such as NR) may include: HARQ-ACK (or HARQ information or HARQ feedback information, for example, may include acknowledgment (acknowledgment, ACK) and negative acknowledgment (negative acknowledgment, NACK)), SR and CSI. Some communication systems (such as NR) support UCI transmission using multiple PUCCH formats. For the format and related parameters of the PUCCH, please refer to Table 1 below.

Table 1

PUCCH格式PUCCH format	时域符号的数量number of time domain symbols	承载UCI的比特数量Number of bits carrying UCI	物理资源块的数量Number of physical resource blocks
00	1-21-2	≤2≤2	11
11	4-144-14	≤2≤2	11
22	1-21-2	＞2>2	1-161-16
33	4-144-14	＞2>2	1-161-16
44	4-144-14	＞2>2	11

It can be seen from Table 1 that PUCCH formats 0 and 1 are used to carry 1 or 2-bit 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 (such as NR Rel-15), if the resources of the PUCCH carrying SR overlap with the resources of the PUCCH carrying HARQ-ACK/CSI (such as overlapping in the time domain), the communication system supports SR and HARQ- ACK (or SR and CSI) are multiplexed and transmitted in the same PUCCH. The communication system specifies various multiplexing rules for SR and HARQ-ACK/CSI. These multiplexing rules are introduced in the following sections.

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

In case a, if SR is positive (positive), the terminal transmits a PUCCH in the physical resource block (physical resource block, PRB) where the second PUCCH is located, and the cyclic shift offset m _cs used by the PUCCH (see Table 2 and 3) are different from the cyclic shift offset used when HARQ-ACK is transmitted alone. However, the time domain resources and frequency domain resources 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取值HARQ-ACK value	00	11
循环移位偏移cyclic shift offset	m _cs＝3 m _cs =3	m _cs＝9 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 only transmits HARQ-ACK through the second PUCCH and does not transmit SR.

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

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

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

In case c, the PUCCH on which the SR and HARQ-ACK are multiplexed and transmitted is related to the state of the SR. The existence of the situation c is the main source of the technical problem to be solved in Embodiment 1 below.

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

The current protocol does not support the multiplexed transmission of SR and HARQ-ACK/CSI in the PUCCH in this case. This is because the time-domain resource occupied by the PUCCH transmitting 1-bit SR should not be longer than the delay resource occupied by the PUCCH transmitting 1-bit 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 can add

Bits SR (each bit represents a positive SR or negative SR). K represents an SR transmission opportunity configured in a slot (slot)/sub-slot (sub-slot) and overlapping with a PUCCH carrying HARQ-ACK/CSI (overlapping in time domain). The total number of bits that the terminal can use according to the UCI of HARQ-ACK/CSI and SR

or

Determine PUCCH resources. It can be seen from the above formula that for K SRs, regardless of whether the SRs are positive or negative, the total number of UCI bits is fixed, so the PUCCH resource determined by the terminal is also fixed.

The above describes the multiplexing transmission of uplink skipping and multiple UCIs in detail. According to the content introduced above, it can be seen that if the terminal or the MAC entity of the terminal configures enhancedSkipUplinkTxDynamic as "true", or configures enhancedSkipUplinkTxConfigured as "true", and there is no To configure the priority based on the logical channel, from the perspective of terminal implementation, the terminal may perform the following steps:

1. If multiple UCIs overlap, the physical layer multiplexes multiple UCIs onto one PUCCH. If the PUCCH overlaps with the PUSCH (such as overlapping in the time domain), the physical layer sends an indication of UCI multiplexing (UCI multiplexing) to the MAC layer (specifically, the MAC entity in the MAC layer); if the PUCCH does not overlap with the PUSCH (If there is no 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 meets the other conditions for enabling uplink skipping mentioned above, the MAC layer does not generate a MAC PDU; if the MAC layer receives an indication of UCI multiplexing , the MAC layer generates a MAC PDU.

It can be seen that whether the MAC layer generates a MAC PDU depends on whether it will receive an indication of UCI multiplexing from the physical layer, that is, the decision of the MAC layer requires the input information of the physical layer.

In addition, as mentioned above, when the physical layer multiplexes multiple UCIs into one PUCCH, it needs to know the state of the SR. Refer to the part of "SR and HARQ-ACK/CSI Multiplexed Transmission in PUCCH", it can be seen that in case c, the state of SR will affect the result of multiplexing. For example, when the first PUCCH carrying SR is PUCCH format 1, and the second PUCCH carrying HARQ-ACK is PUCCH format 1, and SR is positive, the terminal transmits HARQ-ACK through the first PUCCH; if SR is negative, the terminal passes The second PUCCH transmits HARQ-ACK. Whether the terminal chooses the first PUCCH or the second PUCCH to transmit HARQ-ACK will affect the conclusion of whether the PUCCH and PUSCH overlap, and further affect whether the physical layer will send a UCI multiplexing indication to the MAC layer.

However, the status of the SR needs to be determined according to whether the MAC layer has delivered the SR/MAC PDU (positive SR) to the physical layer, and the MAC layer needs to determine whether it is based on the priority of the logical channel and whether to perform uplink skipping. Deliver SR/MAC PDU to physical layer. It can be seen that the decision of whether to implement UCI multiplexing at the physical layer needs to be determined based on the input information of the MAC layer. In this way, the MAC layer and the physical layer will have an interdependent relationship due to the uncertain information of the SR state, and the interdependence of the uncertain information between the MAC layer and the physical layer will lead to disordered behavior of the terminal.

For example, the interdependence of uncertain information between the MAC layer and the physical layer can easily lead to the following situation: the indication of UCI multiplexing output by the physical layer to the MAC layer is made based on the state 1 (positive or negative) of the SR , but according to this result, the MAC layer outputs to the physical layer that the SR state is state 2 (negative or positive). If this happens, there will be uncertainty in the transmission between the terminal and the network device, which may increase the number of blind detection times of the network device.

Through a comprehensive analysis of the causes of the above problems, it can be seen that whether the above-mentioned interdependence relationship will appear between the MAC layer and the physical layer is mainly related to the following information:

1. The PUCCH format of the first resource configured by the network device for the SR (the first resource may be configured by the network device through RRC signaling, and the PUCCH format of the first resource may be determined according to the PUCCH-ResourceId in the SchedulingRequestResourceConfig configured by the RRC);

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

3. Whether the first resource overlaps with the second resource (overlap here may refer to overlap in the time domain, and "overlap" may sometimes be replaced with "conflict"); and

4. Whether the first resource overlaps with the third resource carrying the first PUSCH (the first PUSCH can be any PUSCH, and in some embodiments, the third resource overlaps with the second resource mentioned above (such as overlap in the time domain)).

For example, only when the first resource and the second resource overlap, the impact of the positive and negative SR on the UCI multiplexing decision of the physical layer needs to be considered. If the first resource and the second resource do not overlap, the physical layer will not perform UCI multiplexing. For another example, even if the first resource and the second resource overlap, only when the PUCCH formats of the first resource and the second resource are both PUCCH format 1, it is necessary to consider the influence of the positive and negative SR on the UCI multiplexing decision of the physical layer , in other cases, the position of the PUCCH that multiplexes SR and HARQ-ACK can be determined in advance, regardless of whether the SR is positive or negative.

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

For ease of understanding, the first resources are referred to as SR resources, the second resources are referred to as HARQ-ACK resources, and the third resources are referred to as PUSCH resources.

In the following, with reference to FIG. 3 , taking the uplink transmission process as an example, the judging timing of the first condition and the possible setting manner of the first condition will be 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 can configure enhancedSkipUplinkTxDynamic as "true", or configure enhancedSkipUplinkTxConfigured as "true". Therefore, if the condition for enabling uplink skipping is satisfied, the terminal may enable uplink skipping, or perform an uplink skipping operation. The condition for enabling uplink skipping may include the conditions mentioned above when introducing the concept of uplink skipping, for example, it may include one or more of the following conditions:

3. If there is no aperiodic CSI request on this PUSCH according to the description in related protocols (such as TS 38.212); and

4. If this MAC PDU contains 0 MAC SDUs; and

5. If this MAC PDU only contains periodic BSR and any LCG has no data, or this MAC PDU only contains padding BSR.

On this basis, the condition for enabling uplink skipping may also include the first condition introduced in the embodiment of the present application, that is, whether the PUCCH format of the SR resource, the PUCCH format of the HARQ-ACK resource, and the SR resource and the HARQ-ACK resource overlap, and conditions related to information such as whether the SR resource and the PUSCH resource overlap. For the sake of brevity, FIG. 3 is mainly described around the judging process of the first condition. It can be understood that, in some embodiments, whether to enable uplink skipping also needs to comprehensively consider the judgment results of the above conditions 1-5. For example, the terminal will enable uplink skipping or perform an uplink skipping operation on the basis of satisfying the above conditions 1-5 and the first condition mentioned in the embodiment of the present application.

Referring to Fig. 3, in step S310a, the terminal judges whether the first condition is satisfied. If the first condition is met, the terminal (or MAC entity) does not generate a MAC PDU for the first HARQ entity. If the first condition is not met, then the terminal (or MAC entity) continues to perform step S320a to generate 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 the first PUSCH corresponding to the MAC PDU to the network device.

Correspondingly, the network device may also judge whether to receive the first PUSCH according to the first condition. For example, continuing to refer to FIG. 3 , in step S310b, the network device determines whether the first condition is met. If the first condition is met, the network device does not receive the first PUSCH. It should be understood that the fact that the network device does not receive the first PUSCH means that the network device determines that the terminal will not send the first PUSCH, so there is no need to detect and receive the first PUSCH. If the first condition is not met, the network device continues to execute step S330 to receive the first PUSCH. It should be noted that, in this embodiment of the present application, there is no strict limitation on the execution order of step S310a, step S320a on the terminal side, and step S310b on the network device side, and may be executed in parallel or sequentially.

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

In the following, description will be made by taking as an example that the first condition includes not overlapping SR resources and HARQ-ACK resources, but also including not overlapping SR resources and PUSCH resources. Referring to FIG. 4 , the SR resource in the first slot (slot) overlaps both the HARQ-ACK resource and the PUSCH resource. Therefore, in the first time slot, the first condition is not met, 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 the PUSCH 1 corresponding to the MAC PDU to the network device through the physical layer. Similarly, the SR resource in the fourth time slot overlaps with the PUSCH resource. Therefore, in the fourth time slot, the first condition is not satisfied, 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.

Continuing to refer to FIG. 4 , in the second time slot and the third time slot, neither SR resource and HARQ-ACK resource overlap nor SR resource and PUSCH resource overlap. Therefore, in the second time slot and the third time slot, the first condition is met, 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 does not need to generate a MAC PDU, and thus does not need to send the 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 The MAC PDU may not be generated, and the PUSCH 3 corresponding to the MAC PDU does not need to be sent to the network device through the physical layer.

Based on the above analysis, it can be known that once the bearer SR resource overlaps with the HARQ-ACK resource and/or the SR resource overlaps with the PUSCH resource, the terminal may have the problem of interdependence between the MAC layer and the physical layer mentioned above. In this embodiment, judging conditions related to resource overlap are added to the conditions for enabling uplink skipping, so that once the terminal finds that at least one of the HARQ-ACK resource and the PUSCH resource overlaps with the SR resource, the uplink skipping is not enabled. Although the judgment condition is relatively strict (the judgment condition is relatively strict, it means that even if the above resource overlap occurs, the problem of interdependence between the MAC layer and the physical layer may not necessarily occur in fact, and whether this problem will occur depends on the SR resources and the PUCCH format of HARQ-ACK resources, but this embodiment does not continue to judge the PUCCH format of SR resources and/or HARQ-ACK resources. Once the above resources overlap, uplink skipping is not performed. Therefore, this condition relatively strict), but the advantage of this judgment condition is that it is simple to implement and does not need to add complicated judgment logic. Therefore, this embodiment can reduce the implementation complexity of the terminal on the premise of solving the problem of interdependence between the MAC layer and the physical layer.

In some embodiments, the first condition may include that the PUCCH format of the SR resource is PUCCH format 0. Alternatively, the first condition may include that the PUCCH format of the SR 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. Alternatively, the first condition may be a combination of the above two conditions.

In the following, the first condition includes that the PUCCH format of the SR resource is PUCCH format 0, and the PUCCH format of the SR 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 as an example. . Referring to Figure 4, if the PUCCH format of the SR resource is PUCCH format 0, then the first condition is satisfied from the first to the fourth time slot, and the terminal can enable uplink hopping on PUSCH 1 to PUSCH 4 Pass. That is, in the first time slot to the fourth time slot, the terminal does not need to generate a MAC PDU, and thus does not need to send PUSCH 1 to PUSCH 4 to the network device through the physical layer.

Continue to refer to Figure 4, if the PUCCH format of the SR resource is PUCCH format 1, since the HARQ-ACK resource in the first time slot overlaps with the PUSCH resource, the first condition is not met, so the terminal cannot be enabled on PUSCH 1 Skip upstream. 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 the PUSCH 1 corresponding to the MAC PDU to the network device through the physical layer.

Compared with the previous embodiment, the first condition provided by this embodiment is looser, so that the terminal may also perform an uplink skip operation in the first time slot and the fourth time slot where resources overlap.

In some embodiments, the first condition may include that the PUCCH format of the SR resource is PUCCH format 0. Alternatively, the first condition may include that the PUCCH format of the SR resource is PUCCH format 1, the PUCCH format of 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. Alternatively, the first condition may be a combination of the above two conditions.

The following first condition includes that the PUCCH format of the SR resource is PUCCH format 0, and the PUCCH format of the SR resource is PUCCH format 1, and the PUCCH format of the HARQ-ACK resource is PUCCH format 1, and the HARQ-ACK resource and the PUSCH resource At least one of resources that do not overlap with the SR resource will be described as an example. Referring to Figure 4, if the PUCCH format of the SR resource is PUCCH format 0, then the first condition is satisfied from the first to the fourth time slot, and the terminal can enable uplink hopping on PUSCH 1 to PUSCH 4 Pass. That is, in the first time slot to the fourth time slot, the terminal does not need to generate a MAC PDU, and thus does not need to send PUSCH 1 to PUSCH 4 to the network device through the physical layer.

Continue to refer to Figure 4, if the PUCCH format of the SR resource is PUCCH format 1, then the first condition is satisfied from the second to the fourth time slot, and the terminal can enable uplink on PUSCH 2 to PUSCH 4 jump over. That is, in the second to fourth time slots, the terminal does not need to generate a MAC PDU, and thus does not need to send PUSCH 2 to PUSCH 4 to the network device through the physical layer. For the first time slot, whether the first condition can be satisfied 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 is not met, and the terminal cannot enable uplink skipping on PUSCH 1; if the HARQ-ACK resource is a PUCCH format other than PUCCH format 1 , then the first condition is met, and the terminal can enable uplink skipping on PUSCH 1.

Compared with the previous embodiment, the first condition provided by this embodiment is more relaxed, so that even when the PUCCH format of the SR resource is PUCCH format 1, the terminal may perform an uplink skip operation in the first time slot .

In some embodiments, the first condition may also include that the PUCCH format of the HARQ-ACK resource is not PUCCH format 1, for example, the PUCCH format of the HARQ-ACK resource is PUCCH format 0/2/3/4. Referring to Figure 4, if the PUCCH format of the HARQ-ACK resource is not PUCCH format 1, the first condition is satisfied from the first to the fourth time slot, and the terminal can be enabled on PUSCH 1 to PUSCH 4 Skip upstream. That is, in the first time slot to the fourth time slot, the terminal does not need to generate a MAC PDU, and thus does not need to send PUSCH 1 to PUSCH 4 to the network device through the physical layer.

It should be understood that, on the premise of no conflict, the first conditions mentioned in the above embodiments may be combined arbitrarily. For example, the first condition may include that the PUCCH format of the SR resource is PUCCH format 0, or that the PUCCH format of the HARQ-ACK resource is not PUCCH format 1. Alternatively, in some embodiments, the first condition may be set in multiple optional ways, and the network device may configure an appropriate first condition for the terminal through signaling according to actual needs.

In each embodiment corresponding to FIG. 3 , a first condition is added to the enabling condition of uplink skipping, so as to release the interdependence on uncertain information between the physical layer and the MAC layer. In other words, each embodiment corresponding to FIG. 3 can remove the scenario in which the uplink skip conclusion is affected by the SR state from the scenario in which the uplink skip is enabled, so as to release the uncertain information between the physical layer and the MAC layer. The interdependence of each other can better achieve the purpose of deterministic transmission.

Example 2:

Embodiment 2 aims to solve the problems caused by the introduction of physical layer priority. For ease of understanding, some concepts involved in Embodiment 2 are firstly explained below.

physical layer priority

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

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

logical channel priority

The MAC entity can configure priority based on logical channels. For a MAC entity, if the logical channel-based priority (lch-basedPrioritization) is configured, the priority of an uplink grant (uplink grant) can be based on the logical channel data (MAC PDU) multiplexed in the MAC PDU corresponding to the uplink grant. Logical channel data multiplexed in the MAC PDU means that the MAC PDU has been stored in the HARQ buffer), or logical channel data that can be multiplexed in the MAC PDU (logic channel data that can be multiplexed in the MAC PDU means that the MAC PDU has not been stored in the HARQ buffer Middle) determines the highest priority among the priorities of the corresponding logical channel. For an uplink grant, if there is no logical channel data 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 multiplexed over any logical channel data Or the priorities of the uplink grants that can be multiplexed in the MAC PDU are all low.

Dynamic Uplink Authorization and Configuring Uplink Authorization

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

The current MAC layer protocol stipulates that when the MAC entity does not configure logical channel priority but configures uplink skipping, dynamic uplink authorization takes precedence over configured uplink authorization (or called dynamic uplink authorization override configuration uplink authorization). In other words, when DG PUSCH and CG PUSCH overlap (also called time domain overlap, or conflict), compared with the uplink grant corresponding to CG PUSCH, the priority of the uplink grant corresponding to DG PUSCH is higher. Therefore, in the actual transmission process, when the DG PUSCH and the CG PUSCH overlap, the MAC entity will deliver a dynamic uplink grant to the HARQ entity.

However, if the terminal is configured with physical layer priority, and DG PUSCH has a low physical layer priority, while CG PUSCH has a high physical layer priority, the above provisions of the current MAC layer protocol will result in CG PUSCH with a higher physical layer priority Cannot be transmitted, thereby affecting the reliability of high-priority services.

The embodiment of the present application proposes two solutions from the perspectives of the MAC layer and the physical layer to solve the above problems. The two schemes are illustrated in detail below through Examples 2.1 and 2.2 respectively.

Example 2.1

In this embodiment of the application, when the MAC entity obtains two uplink grants (including the first uplink grant and the second uplink grant, wherein the first uplink grant corresponds to the first PUSCH, and the second uplink grant corresponds to the second PUSCH), if the first The PUSCH and the second PUSCH overlap, and the MAC entity will decide which of the first uplink grant and the second uplink grant to deliver to the HARQ entity after comprehensively considering at least one of the following information:

1. The physical layer priority of the first PUSCH;

2. The physical layer priority of the second PUSCH;

3. The uplink authorization type of the first uplink authorization;

4. Uplink authorization type of the second uplink authorization;

5. Whether the first PUSCH has UCI multiplexing; and

6. Whether the second PUSCH is multiplexed with UCI.

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

In the following, with reference to FIG. 5 , taking the uplink transmission process as an example, the specific application manner of the first information will be illustrated in more detail.

As shown in Fig. 5, in step S510, the terminal (or the MAC entity of the terminal) acquires the first uplink grant and the 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; or, in some embodiments, both the first uplink grant and the second uplink grant may be configuration 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 the HARQ entity delivered to the HARQ entity according to the first information. Uplink authorization (first uplink authorization or second uplink authorization). In step S530, the terminal sends 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 the first PUSCH to the network device; if the MAC entity delivers the second uplink grant to the HARQ entity, the terminal sends the second PUSCH to the network device.

Taking the first information as an example including 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, FIG. 5 Step S520 in 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. Correspondingly, the network device receives the PUSCH with higher management layer 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, then the terminal or the MAC entity of the terminal delivers the dynamic uplink grant to the HARQ entity. Correspondingly, the network device receives the DG PUSCH in the first PUSCH and the second PUSCH.

By adopting the above solution, there will be no problem that the PUSCH with high physical layer priority cannot be transmitted, so the transmission performance of high priority services can be guaranteed. In addition, if the physical layer priorities of the first PUSCH and the second PUSCH are the same, the solution is compatible with the current protocol.

Take Figure 6 as an example for description. 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 a CG PUSCH, and the second PUSCH is a DG PUSCH. In addition, in Figure 6, the PUSCH with higher physical layer priority is called HP PUSCH, and the PUSCH with lower physical layer priority is called LP PUSCH; if two PUSCHs have the same physical layer priority, the two PUSCH Both are called HP PUSCH.

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

In (b) of Figure 6, CG PUSCH and DG PUSCH have the same priority, therefore, CG PUSCH and DG PUSCH are HP CG PUSCH and HP DG PUSCH respectively. In this case, the MAC entity of the terminal will deliver the dynamic uplink grant to the HARQ entity, and then transmit the HP DG PUSCH to the network device side through the physical layer.

Further, in some embodiments, step S520 in FIG. 5 may also include the following step 3: if the physical layer priorities of the first PUSCH and the second PUSCH are the same, and the first uplink grant and the second uplink grant do not include Dynamic uplink grant (that is, 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 UE according to the UE implementation. HARQ entity. The so-called "implemented according to the terminal" means that the terminal itself can decide whether to deliver the first uplink grant to the HARQ entity or to deliver the second uplink grant to the HARQ entity.

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 There is UCI multiplexing and/or whether the second PUSCH has UCI multiplexing as an example, step S520 in FIG. 5 may include the following three 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 will have the uplink corresponding to the UCI multiplexing PUSCH The authorization is delivered to the HARQ entity. Correspondingly, the network device receives the PUSCH multiplexed with UCI.

Step 3: If both 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, then the terminal or the MAC entity of the terminal delivers the dynamic uplink grant to the HARQ entity . Correspondingly, the network equipment is connected to DG PUSCH.

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

The advantage of this embodiment is that: on the basis of ensuring the transmission performance of services with high physical layer priority, the situation of the same physical layer priority is optimized to ensure that the PUSCH with UCI multiplexing will be transmitted, thereby reducing the number of base stations. number of blind checks.

Further, in some embodiments, step S520 in FIG. 5 may also include the following step 4: if the physical layer priorities of the first PUSCH and the second PUSCH are the same, both the first PUSCH and the second PUSCH have UCI multiplexing or There is no UCI multiplexing, and the first uplink grant and the second uplink grant do not include dynamic uplink grants, then the terminal or the MAC entity of the terminal can deliver the first uplink grant or the second uplink grant according to the terminal implementation (UE implementation). to the HARQ entity. The so-called "implemented according to the terminal" means that the terminal itself can decide whether to deliver the first uplink grant to the HARQ entity or to deliver the second uplink grant to the HARQ entity.

Example 2.2

The first PUSCH in embodiment 2.2 is scheduled by DCI, that is, DG PUSCH. The second PUSCH is configured by the network device, that is, CG PUSCH. Embodiment 2.2 wishes to guarantee the transmission of DG PUSCH if DG PUSCH and CG PUSCH overlap. In order to ensure the transmission of DG PUSCH, and to ensure that there will be no problem that the CG PUSCH with high physical layer priority mentioned above cannot be transmitted, embodiment 2.2 requires that the physical layer priority of DG PUSCH is higher than or equal to the physical layer priority of CG PUSCH. Layer priority (the physical layer priority of DG PUSCH is higher than or equal to the physical layer priority of CG PUSCH means that the physical layer priority of DG PUSCH is higher than the physical layer priority of CG PUSCH, or the physical layer priority of DG PUSCH Same as the physical layer priority of CG PUSCH). In other words, the terminal does not expect the physical layer priority of DG PUSCH to be lower than that of CG PUSCH. Since the terminal does not expect the physical layer priority of DG PUSCH to be lower than the physical layer priority of CG PUSCH (that is, the terminal does not expect DG PUSCH to be a PUSCH with low physical layer priority, while CG PUSCH is a PUSCH with high physical layer priority), the network The device will avoid this situation from the perspective of scheduling. With this embodiment 2.2, the terminal or the MAC entity of the terminal does not need to set additional judgment conditions as in embodiment 2.1, and can be processed directly according to the current protocol, thereby simplifying the implementation of the terminal or the MAC layer of the terminal.

In the following, the embodiment 2.2 will be described in more detail by taking the uplink transmission process as an example in combination with FIG. 7 .

As shown in Figure 7, in step S710a, the terminal judges whether to configure priority based on logical channels, and DG PUSCH and CG PUSCH overlap. If the DG PUSCH and the CG PUSCH overlap, the terminal proceeds to step S720, sending the DG PUSCH to the network device. Correspondingly, in step S710b, the network device judges whether the terminal is configured with priority based on logical channels, and the DG PUSCH and CG PUSCH overlap. If the DG PUSCH and the CG PUSCH overlap, the network device continues to perform step S720 to receive the DG PUSCH.

Taking Figure 8 as an example, the terminal does not expect the situation shown in (a) of Figure 8, that is, the terminal does not expect the CG PUSCH to be HP CG PUSCH, and the DG PUSCH to be LP DG PUSCH. Network devices will avoid this situation from the perspective of scheduling.

Optionally, in some embodiments, if the physical layer priorities of DG PUSCH and CG PUSCH are the same, the terminal does not expect that DG PUSCH does not have UCI multiplexing, but CG PUSCH has UCI multiplexing. In other words, the terminal only expects one of the following situations: both the first PUSCH and the second PUSCH have UCI multiplexing; the first PUSCH has UCI multiplexing, and the second PUSCH has no UCI multiplexing; The second PUSCH is not multiplexed with UCI. Since the terminal does not expect that DG PUSCH does not have UCI multiplexing, but CG PUSCH has UCI multiplexing, the network equipment will avoid this situation from the perspective of scheduling. The advantage of this solution is to ensure that the DG PUSCH without UCI multiplexing will not block the transmission of the CG PUSCH with UCI multiplexing, which can reduce the number of blind detection times of the base station.

Taking Figure 8 as an example, the terminal does not expect the situation shown in (b) of Figure 8, that is, the terminal does not expect that among the HP CG PUSCH and HP DG PUSCH with the same physical layer priority, the HP CG PUSCH overlaps with the HP PUCCH (that is, the HP CG PUSCH overlaps with the HP PUCCH CG PUSCH has UCI multiplexing), while HP DG PUSCH does not overlap with HP PUCCH (that is, HP DG PUSCH has no UCI multiplexing). Network devices will avoid this situation from the perspective of scheduling.

It should be noted that Embodiment 2 is mainly exemplified on the premise that the first PUSCH and the second PUSCH overlap. In some embodiments, the premise may also include one or more of the following conditions: the terminal or The MAC entity is not configured with logical channel-based priority, and the terminal or MAC entity is configured with uplink skipping. The terminal or MAC entity is configured with uplink skipping, which may mean that the parameter enhancedSkipUplinkTxDynamic or enhancedSkipUplinkTxConfigured is configured as "true".

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

Example 3

The method embodiment of the present application is described in detail above in conjunction with Embodiments 1 and 2, and the device embodiment of the present application is described in detail below in conjunction with Embodiment 3. It should be understood that the descriptions of the method embodiments correspond to the descriptions of the device embodiments, therefore, for parts not described in detail, reference may be made to the foregoing method embodiments.

Fig. 9 is a schematic structural diagram of a terminal provided by 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 used for judging whether the first condition is met. The generating unit 920 is configured not to generate a MAC PDU for the first HARQ entity when the first condition is met.

The first condition is determined by at least one of the following information: PUCCH format of the first resource, wherein the first resource is configured by the network device for SR; PUCCH format of the second resource, wherein the first resource Two resources are resources bearing 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 the resource bearing the first PUSCH resource, the first PUSCH is used to bear the MAC PDU.

Optionally, the first condition includes: the first resource does not overlap with the second resource; and/or the first resource does not overlap with the third 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, and the second resource and the At least one of the third resources does not overlap 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, and the PUCCH format of the second resource is PUCCH format 1, and at least one of the second resource and the third resource does not overlap 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 overlaps with the third resource.

Fig. 10 is a schematic structural diagram of a terminal provided by another embodiment of the present application. The terminal 1000 in FIG. 10 includes an acquiring unit 1010 and a determining unit 1020 .

The acquiring unit 1010 is configured to acquire a first uplink grant and a second uplink grant, wherein the first uplink grant corresponds to the first PUSCH, and the second uplink grant corresponds to the second PUSCH.

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

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

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

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 uplink grant and the second uplink grant is a dynamic uplink grant, Then deliver the dynamic uplink grant to the HARQ entity.

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 the first uplink grant and the second uplink grant do not include a dynamic uplink grant, then According to the implementation of the terminal, deliver the first uplink grant or the second uplink grant to the HARQ entity.

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, then Deliver the uplink grant corresponding to the PUSCH multiplexed with UCI to the HARQ entity.

Optionally, the determining unit 1020 is configured to if both 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 , then deliver the dynamic uplink grant to the HARQ entity.

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 with a logical channel-based priority.

Fig. 11 is a schematic structural diagram of a terminal provided by another embodiment of the present application. The terminal 1100 in FIG. 11 includes a judging unit 1110 and a communication unit 1120.

The judging unit 1110 is configured to judge 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; wherein, the first PUSCH is scheduled by DCI, the second PUSCH is configured by the network device, and the first PUSCH The physical layer priority of the 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 meet at least one of the following conditions: both the first PUSCH and the second PUSCH have UCI multiplexing; the first PUSCH has UCI multiplexing, The second PUSCH is not multiplexed with UCI; neither the first PUSCH nor the second PUSCH is multiplexed with UCI.

Optionally, the terminal does not expect that the first PUSCH is not multiplexed with UCI, but the second PUSCH is multiplexed with UCI.

Fig. 12 is a schematic structural diagram of a network device provided by an embodiment of the present application. The network device 1200 in FIG. 12 includes a judging unit 1210 and a communication unit 1220 .

The judging unit 1210 is used for judging whether the first condition is met.

The communication unit 1220 is configured not to receive the first PUSCH when the first condition is met.

The first condition is determined by at least one of the following information: PUCCH format of the first resource, wherein the first resource is configured by the network device for SR; PUCCH format of the second resource, wherein the first resource The second resource is the resource bearing HARQ-ACK; whether the first resource overlaps with the second resource; whether the first resource overlaps with the third resource, wherein the third resource bears the first PUSCH Resources.

Optionally, the second resource overlaps with the third resource.

Optionally, the terminal is not configured with a logical channel-based priority.

Fig. 13 is a schematic structural diagram of a network device provided by another embodiment of the present application. The network device 1300 in FIG. 13 includes a judging unit 1310 and a communication unit 1320 .

The judging unit 1310 is configured to judge 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 following: the physical layer priority of the first PUSCH; the physical layer priority of the second PUSCH; the type of uplink grant corresponding to the first PUSCH; the second PUSCH The type of the corresponding uplink grant; whether the first PUSCH has UCI multiplexing; 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 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 dynamically authorized PUSCH is received.

Optionally, the communication unit 1320 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, then Receive PUSCH multiplexed with UCI.

Optionally, the communication unit 1320 is configured to if both the first PUSCH and the second PUSCH have UCI multiplexing, and one of the first PUSCH and the second PUSCH is a dynamically authorized PUSCH, Then receive the dynamically granted PUSCH.

Fig. 14 is a schematic structural diagram of a network device provided by another embodiment of the present application. The network device 1400 in FIG. 14 includes a judging unit 1410 and a communication unit 1420 .

The judging unit 1410 is configured to judge whether the first PUSCH and the second PUSCH overlap.

The communication unit 1420 is configured to receive the first PUSCH from the terminal if the first PUSCH and the second PUSCH overlap; wherein, the first PUSCH is scheduled by DCI, the second PUSCH is configured by a network device, and the first PUSCH The physical layer priority of a 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 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, that is, the physical layer priority of the first PUSCH is configured by the network device to be higher than or equal to the second PUSCH physical layer priority.

Optionally, the situation that the first PUSCH is not multiplexed with UCI and the second PUSCH is multiplexed with UCI is avoided by the network device in a scheduling manner.

Fig. 15 is a schematic structural diagram of an apparatus for uplink transmission according to an embodiment of the present application. The dashed line in Figure 15 indicates that the unit or module is optional. The apparatus 1500 may be used to implement the methods described in the foregoing method embodiments. Apparatus 1500 may be a chip, a terminal or a network device.

Apparatus 1500 may include one or more processors 1510 . The processor 1510 may support the apparatus 1500 to implement the methods described in the foregoing method embodiments. 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 can also be other general-purpose processors, digital signal processors (digital signal processors, DSPs), application specific integrated circuits (application specific integrated circuits, ASICs), off-the-shelf programmable gate arrays (field programmable gate arrays, FPGAs) Or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor, or the processor may be any conventional processor, or the like.

Apparatus 1500 may also include one or more memories 1520 . A program is stored in the memory 1520, and the program can be executed by the processor 1510, so that the processor 1510 executes the methods described in the foregoing method embodiments. The memory 1520 may be independent from the processor 1510 or may be integrated in the processor 1510 .

Apparatus 1500 may also include a transceiver 1530 . The processor 1510 can communicate with other devices or chips through the transceiver 1530 . For example, the processor 1510 may send and receive data with other devices or chips through the transceiver 1530 .

The embodiment of the present application also provides a computer-readable storage medium for storing programs. The computer-readable storage medium can be applied to the terminal or the network device provided in the embodiments of the present application, and the program enables the computer to execute the methods performed by the terminal or the network device in the various embodiments of the present application.

The embodiment of the present application also provides a computer program product. The computer program product includes programs. The computer program product can be applied to the terminal or the network device provided in the embodiments of the present application, and the program enables the computer to execute the methods performed by the terminal or the network device in the various embodiments of the present application.

The embodiment of the present application also provides a computer program. The computer program can be applied to the terminal or the network device provided in the embodiments of the present application, and the computer program enables the computer to execute the methods performed by the terminal or the network device in the various embodiments of the present application.

It should be understood that in this embodiment of the present application, "B corresponding to A" means that B is associated with A, and B can be determined according to A. However, it should also be understood that determining B according to A does not mean determining B only according to A, and B may also be determined according to A and/or other information.

It should be understood that the term "and/or" in this article is only an association relationship describing associated objects, which means that there may be three relationships, for example, A and/or B may mean: A exists alone, and A and B exist at the same time , there are three cases of B alone. In addition, the character "/" in this article generally indicates that the contextual objects are an "or" relationship.

It should be understood that, in various embodiments of the present application, the sequence numbers of the above-mentioned processes do not mean the order of execution, and the execution order of the processes should be determined by their functions and internal logic, and should not be used in the embodiments of the present application. The implementation process constitutes any limitation.

The above is only a specific implementation of the application, but the scope of protection of the application is not limited thereto. Anyone familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed in the application. Should be covered within the protection scope of this application. Therefore, the protection scope of the present application should be determined by the protection scope of the claims.

Claims

A kind of uplink transmission method, is characterized in that, comprises:

When the first condition is met, the terminal does not generate a medium 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:

The physical uplink control channel format PUCCH format of the first resource, wherein the first resource is configured by the network device for the scheduling request SR;

The PUCCH format of the second resource, wherein the second resource is a resource bearing hybrid automatic repeat request-acknowledgment HARQ-ACK;

whether the first resource and the second resource overlap; and

Whether the first resource overlaps with the third resource, where the third resource is a resource that bears the first physical uplink shared channel PUSCH, and the first PUSCH is used to bear the MAC PDU.
The method according to claim 1, wherein the first condition comprises:

said first resource and said 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 does not overlap with the first resource.
The method according to 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 does not overlap with the first resource .
The method according to 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 according to any one of claims 1-5, wherein the second resource overlaps with the third resource.
A kind of uplink transmission method, is characterized in that, comprises:

The medium access control MAC entity acquires 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;

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

Wherein, the first information includes at least one of the following:

The physical layer priority of the first PUSCH;

The physical layer priority of the second PUSCH;

an uplink grant type of the first uplink grant;

an uplink grant type of the second uplink grant;

Whether the first PUSCH is multiplexed with uplink control information UCI; and

Whether the second PUSCH is multiplexed with UCI.
The method according to claim 7, wherein the MAC entity determines the uplink grant delivered to the HARQ entity according to the first information, comprising:

If the physical layer priorities of the first PUSCH and the second PUSCH are different, the MAC entity delivers the uplink grant corresponding to the PUSCH with higher physical layer priority to the HARQ entity.
The method according to claim 7, wherein the MAC entity determines the uplink grant delivered to the HARQ entity according to the first information, comprising:

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 delivers the dynamic uplink grant to HARQ entity.
The method according to claim 7, wherein the MAC entity determines the uplink grant delivered to the HARQ entity according to the first information, comprising:

If the physical layer priorities of the first PUSCH and the second PUSCH are the same, and the first uplink grant and the second uplink grant do not include a dynamic uplink grant, then the MAC entity, according to the implementation of the terminal, assigns the The first uplink grant or the second uplink grant is delivered to the HARQ entity.
The method according to claim 7, wherein the MAC entity determines the uplink grant delivered to the HARQ entity according to the first information, comprising:

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, then the MAC entity will have UCI multiplexing The uplink grant corresponding to the PUSCH is delivered to the HARQ entity.
The method according to claim 11, wherein the MAC entity determines the uplink grant delivered to the HARQ entity according to the first information, further comprising:

If both 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, then the MAC entity assigns the dynamic uplink The authorization is delivered to the HARQ entity.
The method according to any one of claims 7-9, 11-12, wherein one of the first uplink grant and the second uplink grant is a dynamic uplink grant, and the other is a configuration uplink grant .
The method according to any one of claims 7-13, wherein the MAC entity is not configured with a logical channel-based priority.
A kind of uplink transmission method, is characterized in that, comprises:

If the first physical uplink shared channel 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 DCI, the second PUSCH is configured by the 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 class.
The method according to 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 according to claim 15 or 16, wherein the first PUSCH and the second PUSCH meet at least one of the following conditions:

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

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

Neither the first PUSCH nor the second PUSCH is multiplexed with UCI.
The method according to claim 15 or 16, wherein the terminal does not expect that the first PUSCH is not multiplexed with UCI, but the second PUSCH is multiplexed with UCI.
The method according to any one of claims 15-18, wherein the terminal is not configured with a priority based on a logical channel.
A kind of uplink transmission method, is characterized in that, comprises:

When the first condition is met, the network device does not receive the first physical uplink shared channel PUSCH;

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

The physical uplink control channel format PUCCH format of the first resource, wherein the first resource is configured by the network device for the scheduling request SR;

The PUCCH format of the second resource, wherein the second resource is a resource bearing hybrid automatic repeat request-acknowledgment HARQ-ACK;

whether the first resource and the second resource overlap;

Whether the first resource overlaps with the third resource, where the third resource is a resource bearing the first PUSCH.
The method according to claim 20, wherein the first condition comprises:

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

The first resource and the third resource do not overlap.
The method according to 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 does not overlap with the first resource.
The method according to 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 does not overlap with the first resource .
The method according to 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 according to any one of claims 20-24, wherein the second resource overlaps with the third resource.
A kind of uplink transmission method, is characterized in that, comprises:

If the first physical uplink shared channel 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 following:

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 is multiplexed with uplink control information UCI; and

Whether the second PUSCH is multiplexed with UCI.
The method according to claim 26, wherein the network device receives the first PUSCH or the second PUSCH from the terminal according to the first information, comprising:

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

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 a dynamically authorized PUSCH .
The method according to claim 26, wherein the network device receives the first PUSCH or the second PUSCH from the terminal according to the first information, comprising:

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 receives the PUSCH with UCI multiplexing .
The method according to claim 29, wherein the network device receives the first PUSCH or the second PUSCH from the terminal according to the first information, further comprising:

If both the first PUSCH and the second PUSCH have UCI multiplexing, and one of the first PUSCH and the second PUSCH is a dynamically authorized PUSCH, then the network device receives the dynamically authorized PUSCH PUSCH.
The method according to any one of claims 26-30, wherein one of the first uplink grant and the second uplink grant is a dynamic uplink grant, and the other is a configuration uplink grant.
The method according to any one of claims 26-31, wherein the terminal is not configured with logical channel-based priority.
A kind of uplink transmission method, is characterized in that, comprises:

If the first physical uplink shared channel PUSCH and the second PUSCH overlap, the network device receives the first PUSCH from the terminal;

Wherein, the first PUSCH is scheduled by downlink control information 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.
The method according to 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 configured by the network device.
The method according to claim 33 or 34, wherein the first PUSCH and the second PUSCH meet at least one of the following conditions:

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

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

Neither the first PUSCH nor the second PUSCH is multiplexed with UCI.
The method according to claim 33 or 34, characterized in that the first PUSCH is not multiplexed with UCI, and the situation that the second PUSCH is multiplexed with UCI is avoided by the network device in a scheduling manner.
The method according to any one of claims 33-36, wherein the terminal is not configured with logical channel-based priority.
A terminal, characterized in that, comprising:

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

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

The physical uplink control channel format PUCCH format of the first resource, wherein the first resource is configured by the network device for the scheduling request SR;

The PUCCH format of the second resource, wherein the second resource is a resource that bears hybrid automatic repeat request-acknowledgment 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 that bears the first physical uplink shared channel PUSCH, and the first PUSCH is used to bear the MAC PDU.
The terminal according to claim 38, wherein the first condition includes:

said first resource and said 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 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 does not overlap with the first resource.
The terminal according to claim 38, wherein 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 does not overlap with the first resource .
The terminal according to any one of claims 38-41, wherein the first condition includes:

The PUCCH format of the second resource is not PUCCH format 1.
The terminal according to any one of claims 38-42, wherein the second resource overlaps with the third resource.
A terminal, characterized in that, comprising:

An acquiring unit, configured to acquire 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;

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

Wherein, the first information includes at least one of the following:

The physical layer priority of the first PUSCH;

The physical layer priority of the second PUSCH;

an uplink grant type of the first uplink grant;

an uplink grant type of the second uplink grant;

Whether the first PUSCH is multiplexed with uplink control information UCI; and

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

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

Wherein, the first PUSCH is scheduled by downlink control information 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.
The terminal according to 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 according to claim 52 or 53, wherein the first PUSCH and the second PUSCH meet at least one of the following conditions:

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

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

Neither the first PUSCH nor the second PUSCH is multiplexed with UCI.
The terminal according to claim 52 or 53, wherein the terminal does not expect that the first PUSCH is not multiplexed with UCI, but the second PUSCH is multiplexed with UCI.
The terminal according to any one of claims 52-55, wherein the terminal is not configured with a logical channel-based priority.
A network device, characterized in that it includes:

A communication unit, configured to not receive the first physical uplink shared channel PUSCH when the first condition is met;

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

The physical uplink control channel format PUCCH format of the first resource, wherein the first resource is configured by the network device for the scheduling request SR;

The PUCCH format of the second resource, wherein the second resource is a resource bearing hybrid automatic repeat request-acknowledgment HARQ-ACK;

whether the first resource and the second resource overlap;

Whether the first resource overlaps with the third resource, where the third resource is a resource bearing the first PUSCH.
The network device according to claim 57, wherein the first condition comprises:

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

The first resource and the third resource do not overlap.
The network device according to 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 does not overlap with the first resource.
The network device according to 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 does not overlap with the first resource .
The network device according to any one of claims 57-60, wherein the first condition includes:

The PUCCH format of the second resource is not PUCCH format 1.
The network device according to any one of claims 57-61, wherein the second resource overlaps with the third resource.
A network device, characterized in that it includes:

A communication unit, configured to receive the first PUSCH or the second PUSCH from the terminal according to the 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 following:

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 is multiplexed with uplink control information UCI; and

Whether the second PUSCH is multiplexed with UCI.
The network device according to claim 63, wherein the communication unit 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.
The network device according to claim 63, wherein the communication unit is configured to if the physical layer priorities of the first PUSCH and the second PUSCH are the same, and the first PUSCH and the second PUSCH One of the PUSCHs is a dynamically granted PUSCH, and the dynamically granted PUSCH is received.
The network device according to claim 63, wherein the communication unit is configured to if the physical layer priorities of the first PUSCH and the second PUSCH are the same, and the first PUSCH and the second PUSCH One of the PUSCHs is multiplexed with UCI, and then the PUSCH with UCI multiplexed is received.
The network device according to claim 66, wherein the communication unit is configured to if both the first PUSCH and the second PUSCH have UCI multiplexing, and the first PUSCH and the second PUSCH If one of them is a dynamically granted PUSCH, the dynamically granted PUSCH is received.
The network device according to any one of claims 63-67, wherein one of the first uplink grant and the second uplink grant is a dynamic uplink grant, and the other is a configuration uplink grant.
The network device according to any one of claims 63-68, wherein the terminal is not configured with a logical channel-based priority.
A network device, characterized in that it includes:

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

Wherein, the first PUSCH is scheduled by downlink control information 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.
The network device according to 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 configured by the network device.
The network device according to claim 70 or 71, wherein the first PUSCH and the second PUSCH meet at least one of the following conditions:

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

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

Neither the first PUSCH nor the second PUSCH is multiplexed with UCI.
The network device according to claim 70 or 71, wherein the first PUSCH is not multiplexed with UCI, and the situation that the second PUSCH is multiplexed with UCI is avoided by the network device in a scheduling manner.
The network device according to any one of claims 70-73, wherein the terminal is not configured with a logical channel-based priority.
A terminal, characterized by comprising a memory and a processor, the memory is used to store programs, and the processor is used to call the programs in the memory to execute the method described in any one of claims 1-19 method.
A network device, characterized in that it includes a memory and a processor, the memory is used to store programs, and the processor is used to call the programs in the memory to execute any one of claims 20-37 Methods.
An apparatus, characterized by comprising a processor, configured to call a program from a memory to execute the method according to any one of claims 1-19.
An apparatus, characterized by comprising a processor, configured to call a program from a memory to execute the method according to any one of claims 20-37.
A chip, characterized by comprising a processor, configured to call a program from a memory, so that a device installed with the chip executes the method according to any one of claims 1-19.
A chip, characterized by comprising a processor, configured to call a program from a memory, so that a device installed with the chip executes the method according to any one of claims 20-37.
A computer-readable storage medium, characterized in that a program is stored thereon, the program causes a computer to execute the method according to any one of claims 1-19.
A computer-readable storage medium, which is characterized in that a program is stored thereon, and the program causes a computer to execute the method according to any one of claims 20-37.
A computer program product, characterized by comprising a program, the program causes a computer to execute the method according to any one of claims 1-19.
A computer program product, characterized by comprising a program, the program causes a computer to execute the method according to any one of claims 20-37.
A computer program, characterized in that the computer program causes a computer to execute the method according to any one of claims 1-19.
A computer program, characterized in that the computer program causes a computer to execute the method according to any one of claims 20-37.