WO2022028604A1

WO2022028604A1 - Uplink transmission method and apparatus, and terminal device

Info

Publication number: WO2022028604A1
Application number: PCT/CN2021/111299
Authority: WO
Inventors: 陈晓航; 潘学明
Original assignee: 维沃移动通信有限公司
Priority date: 2020-08-07
Filing date: 2021-08-06
Publication date: 2022-02-10
Also published as: CN114071743A

Abstract

The present application belongs to the technical field of communications, and discloses an uplink transmission method and apparatus, and a network device. Said method comprises: in cases where time domain resources of at least one configured grant uplink shared channel overlap with time domain resources of at least one uplink control channel, generating an MAC PDU at an MAC layer according to any one of the following processing methods: if the MAC layer learns that the time domain resources of the uplink shared channel overlap with the time domain resources of the uplink control channel, generating an MAC PDU; and generating an MAC PDU according to multiplexing information notified to the MAC layer by a physical layer, at least one piece of uplink control information being borne on the at least one uplink control channel.

Description

Uplink transmission method, device and terminal equipment

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims priority to Chinese Patent Application No. 202010790993.2 filed in China on Aug. 7, 2020, the entire contents of which are incorporated herein by reference.

technical field

The present application belongs to the field of communication technologies, and in particular relates to an uplink transmission method, apparatus and terminal equipment.

Background technique

When the uplink shared channel of the terminal device (for example, the Physical Uplink Shared Channel (PUSCH)) is a channel authorized by the configuration, and there is no data to be transmitted in the data memory of the terminal device, the terminal can also ignore the configuration authorization ( configured grant) PUSCH, no uplink transmission.

In the related art, when the uplink shared channel of the terminal device (eg, Physical Uplink Shared Channel (PUSCH)) is a channel authorized by configuration, if the uplink control channel (eg, Physical Uplink Control Channel (Physical Uplink Control Channel) , PUCCH)) time domain resources and the time domain resources of the dynamically scheduled uplink shared channel have resource conflicts, since PUSCH may have no data to send, the medium access control (Medium Access Control, MAC) layer based on whether there is data to generate protocol data Unit (Protocol Data Unit, PDU), cannot generate PDU according to whether there is uplink control information (Uplink Control Information, UCI) to be multiplexed.

SUMMARY OF THE INVENTION

The purpose of the embodiments of the present application is to provide an uplink transmission method, apparatus, and terminal device, so that the MAC layer can generate PDUs based on whether there is UCI to be multiplexed.

In a first aspect, an uplink transmission method is provided, applied to a terminal device, and the above method includes:

Under the situation that the time domain resource of the uplink shared channel of at least one configuration authorization overlaps with the time domain resource of at least one uplink control channel, then at the medium access control MAC layer, according to any one of the following processing methods, generate the MAC protocol data unit PDU:

If the MAC layer learns that the time domain resources of the uplink shared channel overlap with the time domain resources of the uplink control channel, generate a MAC PDU;

According to the multiplexing information notified to the MAC layer by the physical layer, a MAC PDU is generated;

Wherein, the at least one uplink control channel is used to carry uplink control information.

In a second aspect, an uplink transmission apparatus is provided, and the apparatus includes: an execution module configured to, in the case that the time domain resources of at least one configuration authorized uplink shared channel overlap with the time domain resources of at least one uplink control channel, then The MAC protocol data unit PDU is generated at the media access control MAC layer according to any of the following processing methods:

In a third aspect, a terminal device is provided, the terminal device includes a processor, a memory, and a program or instruction stored in the memory and executable on the processor, the program or instruction being executed by the processor When executed, the steps of the method as described in the first aspect are implemented.

In a fourth aspect, a readable storage medium is provided, and a program or an instruction is stored on the readable storage medium, and when the program or instruction is executed by a processor, the steps of the method according to the first aspect are implemented.

A fifth aspect provides a chip, the chip includes a processor and a communication interface, the communication interface is coupled to the processor, and the processor is configured to run a network-side device program or instruction, implementing the method described in the first aspect. method described.

In a sixth aspect, a program product is provided, the program product is stored in a non-volatile storage medium, the program product is configured to be executed by at least one processor to implement the method of the first aspect above.

In a seventh aspect, a terminal device is provided, the terminal device being configured to perform the method of the first aspect.

In the embodiment of the present application, in the case where the time domain resources of at least one configuration authorized uplink shared channel overlap with the time domain resources of at least one uplink control channel, the medium access control MAC layer is processed according to any one of the following methods: Generate MAC protocol data unit PDU: Mode 1, if the MAC layer learns that the time domain resources of the uplink shared channel overlap with the time domain resources of the uplink control channel, then generate a MAC PDU; Mode 2, notify the MAC layer according to the physical layer. The multiplexing information is generated, and a MAC PDU is generated; wherein, the at least one uplink control channel is used to carry the uplink control information, so that in the case of a conflict between the uplink shared channel and the uplink control channel, the MAC PDU can be generated by the MAC layer, so that the terminal Even in the absence of data transmission, the device can also support that the uplink control information carried on the uplink control channel can be multiplexed to the configured and authorized uplink shared channel, so that the network side device can accurately determine without blind detection. The resources reused by the uplink control channel are used to reduce the complexity of blind detection on the network side and improve the energy efficiency of system communication.

Description of drawings

1 is a system architecture diagram of a communication system provided by an embodiment of the present application;

FIG. 2 is a method flowchart of an uplink transmission method provided by an embodiment of the present application;

3 is a schematic structural diagram of an uplink transmission apparatus provided by an embodiment of the present application;

FIG. 4 is a schematic structural diagram of a terminal device provided by an embodiment of the present application;

FIG. 5 is a schematic structural diagram of a terminal device provided by an embodiment of the present application.

detailed description

The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative work fall within the protection scope of the present application.

The technical terms involved in the technical solutions provided by the embodiments of the present application will be explained below:

1. Time-domain overlap of transmission resources (or time-domain conflict)

Compared with the previous mobile communication system, the fifth generation (5th ^Generation , 5G) mobile communication system needs to adapt to more diverse scenarios and service requirements. The main scenarios of 5G include Enhanced Mobile Broad Band (eMBB), Massive Machine Type Communications (mMTC) and Ultra-Reliable and Low Latency Communications (URLLC), These scenarios require high reliability, low latency, large bandwidth, and wide coverage for mobile communication systems. The UE can support different services, for example, the UE supports not only the URLLC service with low latency and high reliability, but also the eMBB service with large capacity and high speed. In a new radio technology (New Radio, NR) system, since different channels may have different start symbols and lengths, the time domain overlap of transmission resources may occur. Generally, in order to maintain the uplink single-carrier characteristic, when a time slot has multiple overlapping uplink transmission resources for transmission, the single-carrier characteristic of the UE will be destroyed, and the difference of the transmit power will cause the deterioration of the channel estimation performance. This situation is usually regarded as a conflict, and a corresponding conflict resolution needs to be designed, merging or discarding some information.

2. Upstream channel

The uplink control channel includes: physical uplink control channel (physical uplink control channel, PUCCH).

The uplink shared channel includes: physical uplink shared channel (PUSCH).

3. The UCI defined by the physical layer is multiplexed on the PUSCH

Uplink control information (eg, UCI) is typically transmitted on an uplink control channel (eg, PUCCH). If the terminal device is transmitting data on the uplink shared channel (eg, PUSCH), in principle, the PUCCH and the PUSCH can be sent at the same time, that is, the UCI is reserved in the PUCCH. However, this will increase the Cubic Metric; in addition, if the requirement of out-of-band transmission is to be met at a higher transmit power, and the PUSCH and PUCCH are transmitted simultaneously, the interval in the frequency domain is large (PUCCH is generally in transmit at both ends of the frequency band), which will bring challenges to the implementation of radio frequency (RF). Therefore, under normal circumstances, if the PUCCH resources that need to transmit UCI and the PUSCH resources overlap in time, and the base station will ensure that the conditions of the UCI multiplexing processing time are met when scheduling the PUSCH, the UCI will be multiplexed with the data on the PUSCH. above, avoid sending PUCCH at the same time.

4. PUCCH and PUSCH conflict handling

In NR R15, within a PUCCH group (PUCCH group), no matter whether PUCCH and PUSCH are in the same serving cell or in different serving cells, simultaneous transmission of PUCCH and PUSCH is not supported. When PUCCH and PUSCH time domain resources overlap (including partial time domain resource overlap and all time domain resource overlap), the UE will discard or combine according to corresponding rules under the condition that certain time requirements are met.

Exemplarily, if the PUCCH carrying the Scheduling Request (SR) and the PUSCH not carrying the Uplink Shared Channel (UL-SCH) overlap in time domain, the UE discards the PUSCH and transmits the SR PUCCH. Or the UE multiplexes the uplink control information (Uplink Control Information, UCI) (except SR) carried on the PUCCH into the PUSCH for transmission. For example, if the PUCCH 1 and PUSCH 2 that carry the Hybrid Automatic Repeat Request Acknowledgement (HARQ-ACK) or the Channel State Information (CSI) overlap, the UE will use the HARQ- ACK/CSI is multiplexed into PUSCH 2 for transmission.

Specifically, the UE first processes the time-domain resource overlap between multiple PUCCHs (if any), and the result of the processing is one or more PUCCHs with non-time-domain resources overlapping, and then the UE processes the time-domain resources between the PUCCH and the PUSCH. Overlapping, if the PUCCH overlaps with only one PUSCH, the UE multiplexes the UCI (excluding the SR) in the PUSCH. If the PUCCH overlaps with multiple PUSCHs, the UE selects a PUSCH for multiplexing according to the multiplexing rules in the related art. The first multiplexing rule (that is, instructing the UE to select the PUSCH for multiplexing UCI) is as follows:

Rule 1: PUSCH carrying aperiodic channel state information (Aperiodic CSI, A-CSI).

Rule 2: The PUSCH with the earliest start slot.

Rule 3: Dynamically scheduled PUSCH>Configure granted PUSCH or semi-persistent PUSCH.

Rule 4: PUSCH with a small serving cell index > PUSCH with a large serving cell index.

Rule 5: PUSCH with earlier transmission symbol > PUSCH with later transmission symbol.

Exemplarily, the physical layer priority of the PUCCH is determined by the priority of the UCI carried by the PUCCH. For example, the priority of SR is configured through Radio Resource Control (RRC), the priority of periodic CSI and semi-persistent CSI (SP-CSI) is predefined as low priority, and the priority of HARQ-ACK is determined by its corresponding DCI Indicated or determined according to the configuration of Semi-Persistent Scheduling (SPS). The transmission priority of the PUSCH is indicated by the scheduling downlink control information (Downlink Control Information, DCI) corresponding to the PUSCH, or for the PUSCH with the configuration authorization, the priority is configured by the RRC.

When the time domain resources of PUCCH and PUCCH overlap or the time domain resources of PUCCH and PUSCH overlap, the UE first processes transmissions with the same priority (the rules are the same as R15), and then processes transmissions with different priorities. When a certain time requirement is met, the UE cancels transmission (or is called discarding) the uplink resources of low priority and transmits uplink resources of high priority.

In the carrier aggregation (Carrier Aggregation) scenario, the rules are as follows:

First priority: PUSCH with A-CSI;

Second priority: Dynamically scheduled PUSCH (DG PUSCH)>Configure authorized PUSCH (CG-PUSCH) or semiPersistentOnPUSCH (SP-CSI on PUSCH);

The third priority: PUSCH with a small carrier index (CC index)> PUSCH with a large CC index;

Fourth priority: In terms of time, the PUSCH that is transmitted earlier > the PUSCH that is transmitted later.

5. The uplink transmission skip function defined by the MAC layer

The MAC layer defines the process that the terminal implements uplink transmission skipping (UL skipping) in the protocol TS38.321. The MAC entity will not generate a MAC PDU for the HARQ entity if the following conditions are met:

Condition 1: If the MAC entity is configured with the parameter skipUplinkTxDynamic and the value of this parameter is set to true (true), the MAC locates the HARQ entity indicated in the uplink grant (UL grant).

Condition 2: No aperiodic CSI is requested for this PUSCH transmission as specified in TS 38.212 in this UL grant.

Condition 3: The MAC PDU includes zero MAC service data units (SDUs).

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

In the related art, when the UL skipping function is enabled on the uplink shared channel of the terminal device, if there is a resource conflict between the time domain resources of the uplink control channel (eg, PUCCH) and the time domain resources of the dynamically scheduled uplink shared channel, Since the PUSCH may not have data to be sent, the MAC layer generates PDUs based on whether there is data or not, and cannot generate PDUs based on whether there is UCI to be multiplexed.

Specifically, in the case of resource conflict between the time domain resources of the uplink control channel (such as PUCCH) and the time domain resources of the dynamically scheduled uplink shared channel, the terminal device may choose not to generate the PUSCH, so that the uplink control information (such as, UCI) is transmitted on the PUCCH, and the PUSCH can also be selected to be generated, so that the uplink control information is multiplexed and transmitted on the PUSCH.

In this way, the resources multiplexed by the UCI cannot be determined on the network side, and the network side cannot receive the UCI accurately. Especially when the number of carriers is large, the network side equipment needs to perform blind detection on each carrier based on the two assumptions of whether the uplink control information is multiplexed in the PUSCH of the carrier, which will increase the complexity of the network side blind detection, which is a problem for the network side. cause a greater burden.

6. Uplink configuration authorization

To meet the requirements of low-latency services or periodic services, NR supports the transmission mode of uplink semi-static configuration grant (Configured Grant), which reduces the signaling interaction process and ensures low-latency requirements. The resources for configuring the authorized transmission can be configured semi-statically through RRC signaling. When there are high-priority services such as URLLC service data, the UE can send data on the configured and authorized uplink channel (PUSCH).

There are two types of Configured grant transfers, type 1 and type 2. Among them, the characteristic of type 1 configuration authorization transmission is that all transmission parameters are configured by RRC; when RRC is configured with type 1 configuration authorization, the configuration is activated. The characteristic of the type 2 configuration authorization transmission is that the RRC configures some parameters, such as the period, and at the same time, the type 2 configuration authorization configuration needs to be activated by the downlink activation signaling.

Specifically, in the case of resource conflict between the time domain resources of the uplink control channel (eg, PUCCH) and the time domain resources of the configured and authorized uplink shared channel, the terminal device may choose not to generate the PUSCH, so that the uplink control information (eg, UCI) is transmitted on the PUCCH, and the PUSCH can also be selected to be generated, so that the uplink control information is multiplexed and transmitted on the PUSCH.

In order to solve the above problem, the embodiments of the present application provide an uplink transmission method, apparatus, and device. If the time domain resources of at least one configuration authorized uplink shared channel overlap with the time domain resources of at least one uplink control channel, the MAC layer The MAC PDU can be generated according to any one of the following processing methods: Mode 1, if the MAC layer learns that the time domain resources of the above-mentioned uplink shared channel overlap with the time domain resources of the above-mentioned uplink control channel, then the MAC PDU is generated; Mode 2, according to the physical layer The multiplexing information notified to the MAC layer generates a MAC PDU; wherein, the above-mentioned at least one uplink control channel carries uplink control information (one or more).

In this way, in the case of conflict between the uplink shared channel and the uplink control channel, the MAC PDU can be generated through the MAC layer, so that the terminal device can support the uplink control information carried on the uplink control channel even in the absence of data transmission. It is multiplexed to the configured and authorized uplink shared channel, so that the network-side equipment can accurately determine the uplink control channel multiplexing resources without blind detection, which reduces the complexity of the network-side blind detection and improves the system communication energy efficiency.

7. Other terms

The terms "first", "second" and the like in the description and claims of the present application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It is to be understood that the terms so used are interchangeable under appropriate circumstances so that the embodiments of the present application can be practiced in sequences other than those illustrated or described herein, and that "first", "second" distinguishes Usually it is a class, and the number of objects is not limited. For example, the first object may be one or multiple. In addition, "and/or" in the description and claims indicates at least one of the connected objects, and the character "/" generally indicates that the associated objects are in an "or" relationship.

It is worth noting that the technologies described in the embodiments of this application are not limited to Long Term Evolution (LTE)/LTE-Advanced (LTE-Advanced, LTE-A) systems, and can also be used in other wireless communication systems, such as code Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (Orthogonal Frequency Division Multiple Access, OFDMA), Single-carrier Frequency-Division Multiple Access (SC-FDMA) and other systems. The terms "system" and "network" in the embodiments of the present application are often used interchangeably, and the described technology can be used not only for the above systems and radio technologies, but also for other systems and radio technologies. However, the following description describes a New Radio (NR) system for example purposes, and uses NR terminology in most of the following description, these techniques are also applicable to applications other than NR system applications, such as 6th generation (6 ^th Generation, 6G) communication system.

FIG. 1 shows a block diagram of a wireless communication system to which the embodiments of the present application can be applied. The wireless communication system includes a terminal 11 and a network-side device 12 . The terminal 11 may also be called a terminal device or a user terminal (User Equipment, UE), and the terminal 11 may be a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (Laptop Computer) or a notebook computer, a personal digital computer Assistant (Personal Digital Assistant, PDA), handheld computer, netbook, ultra-mobile personal computer (ultra-mobile personal computer, UMPC), mobile Internet device (Mobile Internet Device, MID), wearable device (Wearable Device) or vehicle-mounted device (Vehicle user equipment, VUE), pedestrian terminal (pedestrian user equipment, PUE) and other terminal-side equipment, wearable devices include: bracelets, headphones, glasses, etc. However, the embodiment of the present application does not limit the specific type of the terminal 11 . The network side device 12 may be a base station or a core network, wherein the base station may be referred to as a Node B, an evolved Node B, an access point, a Base Transceiver Station (BTS), a radio base station, a radio transceiver, a basic service Set (Basic Service Set, BSS), Extended Service Set (Extended Service Set, ESS), Node B, Evolved Node B (evolved Node B, eNB), Home Node B, Home Evolved Node B, Wireless Local Area Network (wireless local area network) area network, WLAN) access point, wireless fidelity (WiFi) node, Transmitting Receiving Point (TRP) or some other appropriate term in the field, as long as the same technical effect is achieved, all The base station described above is not limited to specific technical vocabulary. It should be noted that, in the embodiments of the present application, only the base station in the NR system is used as an example, but the specific type of the base station is not limited.

The uplink transmission method provided by the embodiments of the present application will be described in detail below with reference to the accompanying drawings through specific embodiments and application scenarios thereof.

An uplink transmission method provided by an embodiment of the present application can be applied to a terminal device, in other words, the uplink transmission method can be executed by software or hardware installed in the terminal device. As shown in FIG. 2 , the data transmission method provided by this embodiment of the present application may include the following step 201 .

Step 201: When the time domain resource of at least one configuration authorized uplink shared channel overlaps with the time domain resource of at least one uplink control channel, the MAC layer generates a MAC PDU according to any one of the following processing methods.

The first processing method: if the time domain resource of at least one configuration authorized uplink shared channel overlaps with the time domain resource of at least one uplink control channel, and if the MAC layer learns that the time domain resource of the at least one uplink shared channel is the same as the time domain resource of the at least one uplink shared channel If the time domain resources of the uplink control channel overlap, the MAC PDU is generated at the MAC layer.

The second processing method: The MAC layer (or Layer 2, Layer 2) generates MAC PDUs according to the multiplexing information notified to the MAC layer by the physical layer (or Layer 1, Layer 1).

The above configuration authorization can be non-authorized configuration, authorization-free configuration, semi-static scheduling, configured grant, etc.

In this embodiment of the present application, the at least one uplink control channel carries at least one uplink control information.

In this embodiment of the present application, the at least one configured and authorized uplink shared channel is located on one or more carriers.

It should be noted that the overlapping of the time domain resources of the at least one uplink shared channel and the time domain resources of the at least one uplink control channel means that there is a time conflict between the at least one uplink shared channel and the at least one uplink control channel. Exemplarily, the above-mentioned time domain resource may be one or more time slots/subslots/symbols/subframes.

In the embodiment of the present application, the following relationship exists between the above-mentioned MAC PDU and uplink control information (such as UCI): 1) If the target uplink shared channel and uplink control channel resources overlap, the MAC PDU and UCI are multiplexed on the target uplink shared channel or, 2) if the target uplink shared channel and the target uplink control channel resources do not overlap, the UCI is transmitted on the target uplink control channel, and the MAC PDU is transmitted on the target uplink shared channel.

Optionally, in this embodiment of the present application, the above multiplexing information is used to indicate that: the time domain resources of the at least one configuration-granted uplink shared channel overlap with the time domain resources of the at least one uplink control channel.

Optionally, in this embodiment of the present application, the above multiplexing information may also be used to indicate a target uplink shared channel, that is: in the above at least one configuration authorized uplink shared channel, the uplink control channel used to carry the above at least one uplink control channel is used. information on the uplink shared channel. Further, at this time, the MAC layer may not need the physical layer to notify that there is currently a conflict between the uplink control channel and the above-mentioned shared channel, and the MAC layer only needs to directly generate the MAC PDU according to the multiplexing information notified by the physical layer.

Optionally, in this embodiment of the present application, the foregoing multiplexing information may also be used to indicate at least one of the following:

Among the at least one uplink control channel, a target uplink control channel for carrying the uplink control information;

In the at least one configuration authorized uplink shared channel, the target uplink shared channel used to carry the uplink control information;

In the at least one configuration authorized uplink shared channel, there is a channel with overlapping time domain resources with the at least one uplink control channel;

In the at least one uplink control channel, there is a channel with overlapping time domain resources with the at least one configuration authorized uplink shared channel.

The first two methods for determining the target uplink shared channel can directly inform the MAC layer which one is the target uplink shared channel, and the latter two target uplink shared channels need to be determined by the MAC layer which is the target uplink shared channel.

The above-mentioned target PUSCH may be the PUSCH with the earliest start time among the multiple PUSCHs on the carrier with the smallest number, or the target PUSCH is the PUSCH that triggers aperiodic CSI reporting among the multiple PUSCHs on the carrier with the smallest number, or, the target PUSCH It is the PUSCH of the carrier with the smallest number in the dynamic UL scheduling among multiple carriers, or, the target PUSCH is the PUSCH of the carrier with the smallest number that triggers aperiodic CSI reporting, or the target PUSCH is the PUSCH of the carrier with the smallest number that triggers aperiodic CSI reporting. Among the at least one configuration grant, the PUSCH of the configuration grant with the smallest or largest number, or the target PUSCH is the PUSCH of the configuration grant located on the carrier with the smallest or largest number in the at least one configuration grant.

Wherein, the priority of the target uplink shared channel is the same as or different from the priority corresponding to the at least one configuration authorized uplink shared channel, for example, the priority of the target uplink shared channel may be greater than, equal to or smaller than the at least one configuration authorized uplink shared channel corresponding priority. The priority of the PUSCH of the configuration grant may be the priority corresponding to the PUSCH of the configuration grant or the priority corresponding to the configuration grant.

The priority corresponding to the PUCCH may be the priority of the UCI carried by the PUCCH, the priority of the physical downlink shared channel corresponding to the UCI carried by the PUCCH, or the priority of the HARQ-ACK codebook corresponding to the PDSCH corresponding to the PUCCH.

It should be noted that, in the embodiment of the present application, the target uplink shared channel may be one or multiple, and the target uplink control channel may be one or multiple, which is not limited in the embodiment of the present application.

Optionally, in this embodiment of the present application, the above multiplexing information may be notified by the physical layer to the MAC layer when the terminal device receives a scheduling grant (downlink scheduling grant or uplink scheduling grant).

Further optionally, in the embodiment of the present application, in the case that the scheduling grant is a downlink scheduling grant, the downlink scheduling grant is DCI for scheduling part or all of the uplink control channels in the at least one uplink control channel. Exemplarily, the downlink scheduling grant is the latest (latest) DCI for scheduling the above-mentioned one or more PUCCHs carrying UCI.

Further optionally, in the embodiment of the present application, in the case where the above-mentioned scheduling grant is an uplink scheduling grant, the above-mentioned uplink scheduling grant is the DCI for scheduling the uplink shared channel overlapping the time domain resource of the at least one uplink control channel,

Or, when the scheduling grant is an uplink scheduling grant, the uplink shared channel scheduled by the uplink scheduling grant overlaps with the at least one uplink control channel in one time unit,

Or, in the case where the scheduling grant is an uplink scheduling grant, the uplink shared channel scheduled by the uplink scheduling grant overlaps with the uplink shared channel of the at least one configuration grant in one time unit, wherein the uplink shared channel scheduled by the uplink scheduling grant The priority of the shared channel is the same or different from that of the uplink shared channel granted by the at least one configuration.

Exemplarily, in the case that the above-mentioned uplink scheduling grant is the DCI for scheduling part or all of the above-mentioned at least one uplink shared channel, the above-mentioned uplink scheduling grant is the DCI for scheduling the PUSCH on the PCell.

Exemplarily, the above-mentioned time unit may be: a subframe, a time slot, a sub-slot, a symbol, and the like.

Further, when the terminal device receives the end time slot or symbol of the DCI of the scheduling grant, the physical layer notifies the MAC layer; or, the terminal device receives X time units after the end time slot or symbol of the DCI of the scheduling grant. , notified by the physical layer to the MAC layer. Wherein, X is a predefined or network configuration or is related to the UE capability, and further, X may be the processing time of a downlink control channel (physical downlink control channel, PDCCH).

Optionally, in this embodiment of the present application, the process of generating the MAC PDU by the terminal device in the foregoing step 201 may further include the following step 201a:

Step 201a: In the at least one configuration authorized uplink shared channel, in the case that the target uplink shared channel has no data to be transmitted, generate a MAC padding PDU.

The target uplink shared channel is an uplink shared channel used to carry the uplink control information of the at least one uplink control channel in the at least one configuration authorized uplink shared channel.

Exemplarily, when the terminal device has no data, a MAC padding PDU (MAC padding PDU) is generated. The terminal device has no data, specifically, there is no data in the logical channel group (Logical Channel Group) corresponding to the PUSCH.

Exemplarily, when the MAC layer generates a MAC PDU for the at least one PUSCH according to the multiplexing information, when there is no UL-SCH on any PUSCH, the MAC generates a MAC padding PDU.

Exemplarily, when the MAC layer generates the MAC PDU according to the multiplexing information, if there is no UL-SCH or no data on the target PUSCH, the MAC layer generates the MAC padding PDU.

Further optionally, in the embodiment of the present application, the uplink transmission method provided by the embodiment of the present application may further include the following step A1:

Step A1: on the conflicting channel or the target carrier, it is forbidden to enable the uplink transmission skip function;

The conflicting channel is: in the at least one configured uplink shared channel, a channel overlapping with the time domain resources of the uplink control channel scheduled by the downlink scheduling grant, or, in the uplink shared channel scheduled by the uplink scheduling grant. , the uplink shared channel that overlaps with the time domain resource of the at least one uplink control channel, or the uplink shared channel scheduled by the uplink scheduling grant that overlaps the time domain resource of the at least one configuration authorized uplink shared channel channel;

The target carrier is the carrier where the conflicting channel is located.

Exemplarily, when at least one PUCCH and PUSCH overlap in time, the UE disables the PUSCH UL skipping function. Further, on the carrier where the PUSCH conflicting with the PUCCH is located, the PUSCH UL skipping function is prohibited from being enabled.

Optionally, in the embodiment of the present application, for the above processing mode 2, the uplink transmission method provided by the embodiment of the present application may further include the following step B1 or step B2 or step B3:

Step B1: In the case that the uplink control channel includes multiple channels, the physical layer or the MAC layer determines the target uplink control channel from the multiple uplink control channels according to the first multiplexing rule.

Step B2: In the case that the at least one configuration-authorized uplink shared channel includes multiple channels, the physical layer or the MAC layer determines from the multiple configuration-authorized uplink shared channels according to the second multiplexing rule. the target uplink shared channel.

Step B3: In the case that the at least one uplink shared channel includes multiple uplink shared channels, and the time domain resources of the target uplink control channel overlap with the time domain resources of the multiple uplink shared channels, the physical layer or the MAC layer is based on the first step. The two multiplexing rules and the above-mentioned target uplink control channel determine the above-mentioned target uplink shared channel from the above-mentioned multiple uplink shared channels.

Exemplarily, the above-mentioned first multiplexing rule may be a PUCCH multiplexing rule of UCI on PUCCH.

In an example, the multiplexing rule of HARQ-ACK on PUCCH and the multiplexing rule of Scheduling request (SR) on PUCCH are shown in Table 1 below:

Table 1

It should be noted that PF0 in the above table is PUCCH Format 0, PF1 in the above table is PUCCH Format 1, and PF2/3/4 in the above table is PUCCH Format 2/3/4.

For CSI+SR

SR and CSI are transmitted on the PUCCH of CSI, [log ₂ (K+1)] bits are preset before the periodic/semi-static CSI information bits, and in ascending order, indicate the corresponding SR status (active or inactive) in the SR resource Id activation).

For HARQ-ACK/SR/CSI

If HARQ-ACK is feedback to PDSCH without PDCCH scheduling, HARQ-ACK or HARQ-ACK+SR will be multiplexed on CSI PUCCH for transmission.

If HARQ-ACK is feedback to PDSCH scheduled with PDCCH, HARQ-ACK or HARQ-ACK+SR+CSI will be multiplexed on one PUCCH for transmission. The PUCCH is a PUCCH determined in multiple resource sets configured by RRC based on HARQ-ACK, CSI and SR bits.

Exemplarily, for the above-mentioned step B2, in the case that the above-mentioned at least one configuration-authorized uplink shared channel includes multiple uplink shared channels, and the plurality of uplink shared channels are located on a single carrier, the above-mentioned target uplink shared channel is based on at least the following: A certain:

The uplink shared channel with the earliest start time domain position among the above-mentioned multiple uplink shared channels;

The uplink shared channel for which aperiodic CSI reporting is triggered in the above-mentioned multiple uplink shared channels;

The physical layer notifies the MAC layer to multiplex the uplink control information on the target uplink shared channel;

The physical layer notifies the MAC layer whether each of the multiple uplink shared channels multiplexes the uplink control information.

For example, taking the uplink shared channel as the PUSCH as an example, when there is a single carrier and there are multiple PUSCHs, the physical layer (physical, PHY) layer needs to determine the target PUSCH carrying the UCI according to the second multiplexing rule.

Specific reuse methods include:

Multiplexing mode 1: The target PUSCH is the PUSCH with the earliest start time among the multiple PUSCHs on the carrier;

Multiplexing mode 2: The target PUSCH is a PUSCH for which aperiodic CSI reporting (Aperiodic-CSI, A-CSI) is triggered among multiple PUSCHs on the carrier.

Exemplarily, for the above step B2, in the case that the above-mentioned at least one configuration authorized uplink shared channel includes multiple uplink shared channels, and the above-mentioned multiple uplink shared channels are located on multiple carriers, the above-mentioned target uplink shared channel satisfies at least the following: One:

The uplink shared channel with the earliest start time domain position among the plurality of uplink shared channels on the first carrier;

An uplink shared channel for which aperiodic CSI reporting is triggered among the multiple uplink shared channels on the first carrier;

an uplink shared channel on the second carrier;

Uplink control channel on the third carrier.

The above-mentioned first carrier is a carrier whose number satisfies a predetermined condition (for example, the number is the smallest) among the above-mentioned multiple carriers; the above-mentioned second carrier is an uplink scheduled carrier among the above-mentioned multiple carriers and whose number satisfies the above-mentioned predetermined condition; the above-mentioned third carrier The carrier is a carrier for which aperiodic CSI reporting is triggered and whose number satisfies the above-mentioned predetermined condition among the above-mentioned multiple carriers.

For example, taking the uplink shared channel as PUSCH as an example, when there are multiple carriers and there are multiple PUSCHs, the PHY layer needs to determine the target PUSCH carrying the UCI and the carrier where the target PUSCH is located according to the second multiplexing rule.

Specifically, the multiplexing mode includes: multiplexing mode 1: the target PUSCH is the PUSCH with the earliest start time among the multiple PUSCHs on the carrier with the smallest number;

Multiplexing mode 2: The target PUSCH is the PUSCH that triggers aperiodic CSI reporting (Aperiodic-CSI, A-CSI) among multiple PUSCHs on the carrier with the smallest number;

Multiplexing mode 3: The target PUSCH is the PUSCH of the carrier with the smallest number in the dynamic UL scheduling among multiple carriers;

Multiplexing mode 4: The target PUSCH is the PUSCH of the carrier with the smallest number that triggers aperiodic CSI reporting among multiple carriers;

Multiplexing mode 5: The target PUSCH is the PUSCH with the smallest or largest number of the configuration authorized PUSCH among the at least one configuration authorized PUSCH;

Multiplexing mode 6: The target PUSCH is the PUSCH with the minimum or maximum number of the carrier on which the corresponding configuration grant is located among the at least one PUSCH with the configuration grant.

In addition, the multiplexing method may further include: the target PUSCH is the channel with the earliest start time among the at least one configuration authorized uplink shared channel located on a single carrier; or, the at least one configuration authorized channel located on multiple carriers Among the uplink shared channels, the channel with the earliest start time is located on the carrier with the lowest number; or, in the at least one configuration authorized uplink shared channel located on the multi-carrier, it is located on the carrier with the lowest number among the dynamically scheduled carriers Channel.

Exemplarily, the MAC layer or the physical layer will determine the target uplink shared channel according to the second multiplexing rule. In an example, when the PHY layer notifies the MAC layer that the target PUCCH collides with the above at least one PUSCH, the MAC layer will determine the target PUSCH carrying the UCI according to the above-mentioned multiplexing rule of the target PUCCH and the UCI on PUSCH.

Optionally, in the embodiment of the present application, for the above processing mode 1, if the MAC layer learns that the time domain resources of the at least one uplink shared channel overlap with the time domain resources of the at least one uplink control channel, the embodiment of the present application The provided uplink transmission method may further include the following step C1:

Step C1: The MAC layer determines a target uplink shared channel for carrying the uplink control information from the at least one uplink shared channel according to the second multiplexing rule.

Exemplarily, taking the uplink shared channel as PUSCH as an example, when the MAC layer determines the target PUCCH carrying these one or more UCIs according to the second multiplexing rule (that is, the PUCCH multiplexing rule of UCI on PUSCH), if the above When the target PUCCH collides with at least one PUSCH, the MAC layer determines the target PUSCH bearing the UCI according to the target PUCCH and the second multiplexing rule.

Exemplarily, taking the uplink shared channel as the PUSCH as an example, when at least one PUSCH on one or more carriers is located on a multi-carrier, the MAC layer determines the target PUSCH used to carry the UCI and where the target PUSCH is located according to the second multiplexing rule. carrier

Exemplarily, taking the uplink shared channel as PUSCH and the uplink control channel as PUCCH as an example, the MAC layer determines, according to the first multiplexing rule (that is, the PUCCH multiplexing rule of UCI on PUCCH), the target PUCCH that carries these one or more UCIs. .

Exemplarily, if the MAC layer knows that one or more PUCCHs carrying UCI are in conflict with at least one PUSCH on one or more carriers, and when there is no UL-SCH on the target PUSCH, the MAC generates a MAC padding PDU.

The uplink transmission method provided by the embodiment of the present application is explained below by taking the uplink shared channel as the PUSCH and the uplink control channel as the PUCCH as an example, and using three examples.

Example 1:

When the UE is configured with at least one PUSCH configured on one or more carriers, if the UE receives one or more UL grants, at least one PUSCH on one or more carriers is scheduled, and the UE receives one or more UL grants DL grant, when one or more PUCCHs carrying UCI are scheduled, the UE can determine the transmission of UCI according to the following steps:

Step 11: Decode DL grant and/or UL grant.

Step 12: If there are multiple PUCCHs, the PHY layer determines the resource of the target PUCCH bearing UCI according to the multiplexing rule of UCI on PUCCH.

Step 13: If the target PUCCH resource collides with at least one PUSCH on the above-mentioned one or more carriers, the PHY layer determines the target PUSCH resource for carrying UCI according to the UCI on PUSCH multiplexing priority in at least one PUSCH .

Step 14: The PHY layer notifies the MAC layer of the UCI multiplexing information (that is, the content in step 13), and the MAC generates a MAC PDU according to the UCI multiplexing information.

Step 15: If there is no UL-SCH, the MAC layer generates a padding PDU.

Step 16: Perform UCI mapping on the target PUSCH.

Step 17: Perform (padding) data mapping on the target PUSCH.

It should be noted that this embodiment does not limit the execution order between the above steps 16 and 17. Step 16 may be executed first and then step 17 (that is, the UCI mapping is performed first, and the data mapping is performed later), or the execution may be performed first. 17 and then execute 16 (that is, first perform data mapping, and then perform UCI mapping).

Example 2:

When the UE is on one or more carriers and is configured with at least one PUSCH with a configuration grant, if the UE receives one or more UL grants, at least one PUSCH on one or more carriers is scheduled, and the UE receives one or more UL grants DL grants, one or more PUCCHs carrying UCI are scheduled, and the UE determines the transmission of UCI according to the following steps:

Step 21: Decode DL grant and/or UL grant.

Step 22: If there are multiple PUCCHs, the PHY layer determines the resource of the target PUCCH bearing UCI according to the multiplexing rule of UCI on PUCCH.

Step 23: The PHY layer notifies the MAC layer of the UCI multiplexing information (that is, the content in step 12), and the MAC layer generates a MAC PDU according to the UCI multiplexing information.

Step 24: If the target PUCCH resource collides with at least one PUSCH on one or more carriers, the MAC layer determines the target PUSCH resource for carrying UCI in at least one PUSCH according to the UCI on PUSCH multiplexing rule.

Step 25: The MAC generates a PDU for the target PUSCH, and generates a padding PDU if there is no UL-SCH.

Step 26: Perform UCI mapping on the target PUSCH.

Step 27: Perform (padding) data mapping on the target PUSCH.

It should be noted that this embodiment does not limit the execution order between the above steps 26 and 27. Step 26 may be executed first and then step 27 (that is, the UCI mapping is performed first, and then the data mapping is performed), or the execution may be performed first. 27 and then execute 26 (that is, first perform data mapping, and then perform UCI mapping).

Example 3:

When the UE is configured with at least one PUSCH configured on one or more carriers, if the UE receives one or more UL grants, at least one PUSCH on one or more carriers is scheduled, and the UE receives one or more UL grants DL grant, one or more PUCCHs carrying UCI are scheduled, and the UE determines the transmission of UCI according to the following steps:

Step 31: Decode DL grant and/or UL grant.

Step 32: After step 31, the PHY layer notifies the MAC layer that the one or more PUCCHs carrying the UCI collide with at least one PUSCH on the one or more carriers.

Step 33: The MAC generates a MAC PDU for the first PUSCH (set) in conflict according to the UCI multiplexing information.

Step 34: If there is no UL-SCH, the MAC generates a padding PDU.

Step 35: If there are multiple PUCCHs, the PHY layer determines the resource of the target PUCCH bearing UCI according to the multiplexing rule of UCI on PUCCH.

Step 36: If the target PUCCH resource collides with at least one PUSCH on one or more carriers, the PHY layer determines the target PUSCH resource for carrying UCI in at least one PUSCH according to the UCI on PUSCH multiplexing rule.

Step 37: If the target PUSCH has UL-SCH, perform UCI and data (data) mapping on the target PUSCH.

Step 38: Otherwise, perform UCI and padding data mapping on the target PUSCH.

Step 39: If the target PUSCH does not belong to the first PUSCH (set), perform (padding) data mapping on the first PUSCH (set).

Step 40: If one PUSCH in the first PUSCH (set) has no data, perform mapping of padding data.

It should be noted that this embodiment does not limit the execution order of the UCI mapping and the data mapping. The UCI mapping may be performed first, and then the data mapping may be performed, or the data mapping may be performed first, and then the UCI mapping may be performed.

In addition to the above methods of generating MAC PDUs, the present application also provides a method for generating MAC PDUs, including:

In the physical uplink shared channel authorized by the at least one configuration, when the target physical uplink shared channel used to carry the uplink control information is configured to be repeatedly transmitted M times, N MAC PDUs are generated, and the M is a positive integer , the N is a positive integer less than or equal to M.

Define the internal layer (ie inter-layer) signaling from the internal physical layer of the terminal to the MAC layer. When the physical layer of the terminal learns that a configuration authorized PUSCH and PUCCH resources overlap in the time domain, the physical layer of the terminal will notify The MAC layer unconditionally generates a MAC PDU for the current Hybrid Automatic Repeat Request (HARQ) entity. If the PUSCH authorized by the configuration is configured with repeated K transmissions, the internal signaling submitted by the physical layer to the MAC layer may be:

Unconditionally generate K identical MAC PDUs; or

Unconditionally generate M out of K MAC PDUs, where 1≤M≤K.

If the repeated transmission type is B, the MAC PDU is nominal PUSCH, that is, in the case where the target uplink shared channel for carrying the uplink control information in the at least one configuration authorized uplink shared channel is configured as the repeated transmission type B , the MAC PDU is a PDU for nominal uplink shared channel.

Further, it is also possible to define the relevant MAC PDU generation conditions directly at the MAC layer without defining any air interface or signaling inside the terminal, so that the overlap of the physical layer PUCCH and PUSCH transmission resources is visible to the MAC layer.

Specifically, if the following conditions are met, the MAC entity will not generate a MAC PDU for the HARQ entity:

The MAC entity is configured with the parameter skipUplinkTxDynamic, and the value of this parameter is set to true (true), and the MAC locates the HARQ entity indicated in the uplink grant (UL grant);

The UL grant does not request aperiodic CSI for this PUSCH transmission, and the HARQ entity corresponds to a configured uplink grant (configured uplink grant), and no UCI will be multiplexed to the PUSCH transmission of the configuration grant;

A MAC PDU contains zero MAC SDUs; and a MAC PDU contains only periodic Buffer Status Reports (BSRs) and no data is available for any Logical Channel Group (LCG), or a MAC PDU contains only periodic Buffer Status Reports (BSRs) Fill BSR.

If the scheduled PUSCH configuration or the uplink transmission grant (UL grant) indicates repeated K times of transmission, correspondingly, the MAC layer will generate multiple repeated MAC PDUs.

The solutions in this application can be applied to single-carrier and multi-carrier, as well as licensed or unlicensed frequency bands.

In the uplink transmission method provided by the embodiment of the present application, in the case of the terminal equipment configuration authorization, if the time domain resources of at least one uplink shared channel overlap with the time domain resources of at least one uplink control channel, the MAC layer can follow any one of the following Item processing mode, generate MAC PDU: Mode 1, if the MAC layer knows that the time domain resources of the above-mentioned uplink shared channel overlap with the time domain resources of the above-mentioned uplink control channel, then generate a MAC PDU; Mode 2, according to the physical layer notified to the MAC layer. Multiplexing information to generate a MAC PDU; wherein, at least one uplink control information is carried on the at least one uplink control channel. In this way, in the case of conflict between the uplink shared channel and the uplink control channel, the MAC PDU can be generated through the MAC layer, so that the terminal device can support the uplink control information carried on the uplink control channel even in the absence of data transmission. It is multiplexed to the configured and authorized uplink shared channel, so that the network-side equipment can accurately determine the uplink control channel multiplexing resources without blind detection, which reduces the complexity of the network-side blind detection and improves the system communication energy efficiency.

It should be noted that, in the uplink transmission method provided by the embodiment of the present application, the execution body may be an uplink transmission apparatus, or a control module in the uplink transmission apparatus for executing the uplink transmission method. In the embodiments of the present application, the uplink transmission method performed by the uplink transmission apparatus is taken as an example to describe the apparatus of the uplink transmission method provided by the embodiments of the present application.

A kind of uplink transmission device provided by the embodiment of the present application, as shown in Figure 3, the uplink transmission device 300 provided by the embodiment of the present application can include: an execution module 301, wherein:

The execution module 301 is configured to, when the time domain resource of at least one configuration authorized uplink shared channel overlaps with the time domain resource of at least one uplink control channel, then at the medium access control MAC layer according to any one of the following processing methods, generate MAC Protocol Data Unit PDU:

If the MAC layer learns that the time domain resources of the uplink shared channel overlap with the time domain resources of the uplink control channel, a MAC PDU is generated;

Further, the multiplexing information is used to indicate that: the time domain resources of the at least one configuration granted uplink shared channel overlap with the time domain resources of the at least one uplink control channel.

Further, the at least one configured and authorized uplink shared channel is located on one or more carriers.

Further, the multiplexing information is used to indicate at least one of the following:

Further, the uplink transmission device 300 also includes:

The first determining module is configured to, in the case that the at least one uplink control channel includes a plurality of uplink control channels, at the physical layer or the MAC layer, according to a first multiplexing rule, determine from the plurality of uplink control channels. the target uplink control channel;

or,

When the at least one configuration-authorized uplink shared channel includes multiple configuration-authorized uplink shared channels, the physical layer or the MAC layer determines from the plurality of configuration-authorized uplink shared channels according to the second multiplexing rule outputting the target uplink shared channel;

or,

When the at least one configuration-authorized uplink shared channel includes multiple configuration-authorized uplink shared channels, and the time-domain resources of the target uplink control channel overlap with the time-domain resources of the at least one configuration-authorized uplink shared channel Next, the target uplink shared channel is determined from the at least one configuration authorized uplink shared channel according to the second multiplexing rule and the target uplink control channel at the physical layer or the MAC layer.

Further, the target uplink shared channel is:

Among the at least one configuration authorized uplink shared channel, the corresponding channel with the largest configuration authorization number;

or

Among the at least one configuration authorized uplink shared channel, the corresponding channel with the smallest configuration authorization number;

or

In the uplink shared channel of the at least one configuration authorization, the channel with the largest number of the carrier where the corresponding configuration authorization is located;

or

Among the at least one uplink shared channel of the configuration grant, the channel with the lowest number of the carrier where the corresponding configuration grant is located.

Further, the multiplexing information is notified to the MAC layer by the physical layer when the terminal device receives the scheduling grant.

Further, when the scheduling grant is a downlink scheduling grant, the downlink scheduling grant is downlink control information DCI for scheduling the uplink control channel;

or

In the case where the scheduling grant is an uplink scheduling grant, the uplink scheduling grant is the DCI for scheduling the uplink shared channel overlapping the time domain resource of the at least one uplink control channel;

or

In the case that the scheduling grant is an uplink scheduling grant, the uplink shared channel scheduled by the uplink scheduling grant overlaps with the at least one uplink control channel in one time unit;

or

When the scheduling grant is an uplink scheduling grant, the uplink shared channel scheduled by the uplink scheduling grant overlaps with the uplink shared channel of the at least one configuration grant in one time unit.

Further, the uplink transmission apparatus 300 further includes a disabling and enabling module for disabling the enabling of the uplink transmission skipping function on the conflicting channel or the target carrier;

The target carrier is the carrier where the conflicting channel is located.

Further, if the MAC layer learns that the time domain resources of the at least one uplink shared channel overlap with the time domain resources of the at least one uplink control channel, the uplink transmission apparatus 300 further includes a second determining module for:

A target uplink shared channel for carrying the uplink control information is determined from the at least one uplink shared channel at the MAC layer according to the second multiplexing rule.

Further, the execution module 301 includes:

In the at least one configured and authorized uplink shared channel, when the target uplink shared channel used to carry the uplink control information has no data to be transmitted, a MAC padding PDU is generated.

Further, the execution module 301 includes:

In the at least one configuration authorized uplink shared channel, when the target uplink shared channel used to carry the uplink control information is configured to be repeatedly transmitted M times, N MAC PDUs are generated, and the M is a positive integer, so The N is a positive integer less than or equal to M.

The terminal provided in the embodiment of the present application can implement each process in the method embodiment of FIG. 2 and achieve the same technical effect. To avoid repetition, details are not repeated here.

The uplink transmission device shown in FIG. 3 may be a device, and may also be a component, an integrated circuit, or a chip in a terminal. The device may be a mobile terminal or a non-mobile terminal. Exemplarily, the mobile terminal may include, but is not limited to, the types of terminals 11 listed above, and the non-mobile terminal may be a server, a network attached storage (NAS), a personal computer (personal computer, PC), a television ( television, TV), teller machine, or self-service machine, etc., which are not specifically limited in the embodiments of the present application.

The uplink transmission device shown in FIG. 3 may be a device with an operating system. The operating system may be an Android (Android) operating system, an ios operating system, or other possible operating systems, which are not specifically limited in the embodiments of the present application.

Optionally, as shown in FIG. 4 , an embodiment of the present application further provides a terminal 700, including a processor 701, a memory 702, a program or instruction stored in the memory 702 and executable on the processor 701, the When the program or the instruction is executed by the processor 701, each process of the above-mentioned embodiments of the uplink transmission method is implemented, and the same technical effect can be achieved.

FIG. 5 is a schematic diagram of a hardware structure of a terminal implementing various embodiments of the present application.

The terminal 1000 includes but is not limited to: a radio frequency unit 1001, a network module 1002, an audio output unit 1003, an input unit 1004, a sensor 1005, a display unit 1006, a user input unit 1007, an interface unit 1008, a memory 1009, a processor 1010 and other components.

Those skilled in the art can understand that the terminal 1000 may also include a power supply (such as a battery) for supplying power to various components, and the power supply may be logically connected to the processor 1010 through a power management system, so as to manage charging, discharging, and power consumption through the power management system management and other functions. The terminal structure shown in FIG. 5 does not constitute a limitation to the terminal, and the terminal may include more or less components than shown, or combine some components, or arrange different components, which will not be repeated here.

It should be understood that, in this embodiment of the present application, the input unit 1004 may include a graphics processor (Graphics Processing Unit, GPU) 10041 and a microphone 10042. Such as camera) to obtain still pictures or video image data for processing. The display unit 1006 may include a display panel 10061, which may be configured in the form of a liquid crystal display, an organic light emitting diode, or the like. The user input unit 1007 includes a touch panel 10071 and other input devices 10072 . The touch panel 10071 is also called a touch screen. The touch panel 10071 may include two parts, a touch detection device and a touch controller. Other input devices 10072 may include, but are not limited to, physical keyboards, function keys (such as volume control keys, switch keys, etc.), trackballs, mice, and joysticks, which will not be repeated here.

In the embodiment of the present application, the radio frequency unit 1001 receives the downlink data from the network side device, and then processes it to the processor 1010; in addition, sends the uplink data to the network side device. Generally, the radio frequency unit 1001 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, and the like.

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

The processor 1010 may include one or more processing units; optionally, the processor 1010 may integrate an application processor and a modem processor, wherein the application processor mainly processes the operating system, user interface, and application programs or instructions, etc. Modem processors mainly deal with wireless communications, such as baseband processors. It can be understood that, the above-mentioned modulation and demodulation processor may not be integrated into the processor 1010.

Wherein, the processor 1010 is configured to, in the case where the time domain resources of at least one configuration authorized uplink shared channel overlap with the time domain resources of at least one uplink control channel, perform any one of the following processing methods at the medium access control MAC layer , generate the MAC protocol data unit PDU:

Further, the processor 1010 is further configured to, in the case that the at least one uplink control channel includes multiple uplink control channels, at the physical layer or the MAC layer according to the first multiplexing rule, from the multiple uplink control channels determining the target uplink control channel;

or,

Further, the target uplink shared channel is:

or

Further, the processor 1010 is further configured to disable the uplink transmission skipping function on the conflicting channel or the target carrier;

The target carrier is the carrier where the conflicting channel is located.

Further, if the MAC layer learns that the time domain resources of the at least one uplink shared channel overlap with the time domain resources of the at least one uplink control channel, the processor 1010 is further configured to, at the MAC layer, according to the second multiplexing rule, from A target uplink shared channel for carrying the uplink control information is determined in the at least one uplink shared channel.

Further, the processor 1010 is further configured to, in the at least one configured and authorized uplink shared channel, generate a MAC padding PDU when the target uplink shared channel used to carry the uplink control information has no data to be transmitted.

Further, the processor 1010 is further configured to, in the at least one configuration authorized uplink shared channel, in the case that the target uplink shared channel for carrying the uplink control information is configured to be repeatedly transmitted M times, generate N number of MAC PDU, the M is a positive integer, and the N is a positive integer less than or equal to M.

It should be understood that, in this embodiment, the above-mentioned processor 1010 and the radio frequency unit 1001 can implement each process implemented by the terminal in the method embodiment of FIG. 2 , which is not repeated here to avoid repetition.

An embodiment of the present application further provides a readable storage medium, where a program or an instruction is stored on the readable storage medium, and when the program or instruction is executed by a processor, each process of the uplink transmission method embodiment shown in FIG. 2 is implemented, And can achieve the same technical effect, in order to avoid repetition, it is not repeated here.

Wherein, the processor is the processor in the electronic device described in the foregoing embodiments. The readable storage medium includes a computer-readable storage medium, such as a computer read-only memory (Read-Only Memory, ROM), a random access memory (Random Access Memory, RAM), a magnetic disk or an optical disk, and the like.

An embodiment of the present application further provides a chip, where the chip includes a processor and a communication interface, the communication interface is coupled to the processor, and the processor is used to run a network-side device program or instruction to implement the above-mentioned FIG. 2 Each process of the shown uplink transmission method embodiment can achieve the same technical effect, so to avoid repetition, details are not repeated here.

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

It should be noted that, herein, the terms "comprising", "comprising" or any other variation thereof are intended to encompass non-exclusive inclusion, such that a process, method, article or device comprising a series of elements includes not only those elements, It also includes other elements not expressly listed or inherent to such a process, method, article or apparatus. Without further limitation, an element qualified by the phrase "comprising a..." does not preclude the presence of additional identical elements in a process, method, article or apparatus that includes the element. Furthermore, it should be noted that the scope of the methods and apparatus in the embodiments of the present application is not limited to performing the functions in the order shown or discussed, but may also include performing the functions in a substantially simultaneous manner or in the reverse order depending on the functions involved. To perform functions, for example, the described methods may be performed in an order different from that described, and various steps may also be added, omitted, or combined. Additionally, features described with reference to some examples may be combined in other examples.

Those of ordinary skill in the art can realize that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Skilled artisans may implement the described functionality using different methods for each particular application, but such implementations should not be considered beyond the scope of this disclosure.

Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working process of the above-described systems, devices and units may refer to the corresponding processes in the foregoing method embodiments, which will not be repeated here.

In the embodiments provided in this application, it should be understood that the disclosed apparatus and method may be implemented in other manners. For example, the apparatus embodiments described above are only illustrative. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored, or not implemented. On the other hand, the shown or discussed mutual coupling or direct coupling or communication connection may be through some interfaces, indirect coupling or communication connection of devices or units, and may be in electrical, mechanical or other forms.

In addition, each functional unit in each embodiment of the present disclosure may be integrated into one processing unit, or each unit may exist physically alone, or two or more units may be integrated into one unit.

From the description of the above embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus a necessary general hardware platform, and of course hardware can also be used, but in many cases the former is better implementation. Based on this understanding, the technical solution of the present application can be embodied in the form of a software product in essence or in a part that contributes to the prior art, and the computer software product is stored in a storage medium (such as ROM/RAM, magnetic disk, CD-ROM), including several instructions to make a terminal (which may be a mobile phone, a computer, a server, an air conditioner, or a base station, etc.) execute the methods described in the various embodiments of this application.

It can be understood that the embodiments described in the embodiments of the present disclosure may be implemented by hardware, software, firmware, middleware, microcode, or a combination thereof. For hardware implementation, modules, units, and subunits can be implemented in one or more Application Specific Integrated Circuits (ASIC), Digital Signal Processor (DSP), Digital Signal Processing Device (DSP Device, DSPD) ), Programmable Logic Device (PLD), Field-Programmable Gate Array (FPGA), general-purpose processor, controller, microcontroller, microprocessor, in other electronic units or combinations thereof.

For software implementation, the technologies described in the embodiments of the present disclosure may be implemented through modules (eg, procedures, functions, etc.) that perform the functions described in the embodiments of the present disclosure. Software codes may be stored in memory and executed by a processor. The memory can be implemented in the processor or external to the processor.

The embodiments of the present application have been described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific embodiments, which are merely illustrative rather than restrictive. Under the inspiration of this application, without departing from the scope of protection of the purpose of this application and the claims, many forms can be made, which all fall within the protection of this application.

Claims

An uplink transmission method, applied to terminal equipment, includes:

In the case where the time domain resources of at least one configuration authorized uplink shared channel overlap with the time domain resources of at least one uplink control channel, the MAC layer of the medium access control generates a MAC protocol data unit PDU according to any one of the following processing methods:

If the MAC layer learns that the time domain resources of the uplink shared channel overlap with the time domain resources of the uplink control channel, generate a MAC PDU;

According to the multiplexing information notified to the MAC layer by the physical layer, a MAC PDU is generated;

Wherein, the at least one uplink control channel is used to carry uplink control information.
The method according to claim 1, wherein the multiplexing information is used to indicate that the time domain resources of the at least one configuration granted uplink shared channel overlap with the time domain resources of the at least one uplink control channel.
The method of claim 1 , wherein the at least one configuration granted uplink shared channel is located on one or more carriers.
The method of claim 1, wherein the multiplexing information is used to indicate at least one of the following:

Among the at least one uplink control channel, a target uplink control channel for carrying the uplink control information;

In the at least one configuration authorized uplink shared channel, the target uplink shared channel used to carry the uplink control information;

In the at least one configuration authorized uplink shared channel, there is a channel with overlapping time domain resources with the at least one uplink control channel;

In the at least one uplink control channel, there is a channel with overlapping time domain resources with the at least one configuration authorized uplink shared channel.
The method of claim 4, further comprising:

When the at least one uplink control channel includes multiple channels, the physical layer or the MAC layer determines the target uplink control channel from the multiple uplink control channels according to a first multiplexing rule;

or,

When the at least one configuration-authorized uplink shared channel includes multiple channels, the physical layer or the MAC layer determines the target uplink from the plurality of configuration-authorized uplink shared channels according to a second multiplexing rule shared channel;

or,

In the case that the at least one configuration authorized uplink shared channel includes multiple, and the time domain resources of the target uplink control channel overlap with the time domain resources of the at least one configuration authorized uplink shared channel, at the physical layer or The MAC layer determines the target uplink shared channel from the at least one configured and authorized uplink shared channel according to the second multiplexing rule and the target uplink control channel.
The method according to claim 4, wherein the target uplink shared channel is:

Among the at least one configuration authorized uplink shared channel, the corresponding channel with the largest configuration authorization number;

or

Among the at least one configuration authorized uplink shared channel, the corresponding channel with the smallest configuration authorization number;

or

In the uplink shared channel of the at least one configuration authorization, the channel with the largest number of the carrier where the corresponding configuration authorization is located;

or

Among the at least one uplink shared channel of the configuration grant, the channel with the lowest number of the carrier where the corresponding configuration grant is located.
The method according to claim 1, wherein the multiplexing information is notified by the physical layer to the MAC layer when the terminal device receives the scheduling grant.
The method of claim 7, wherein:

In the case that the scheduling grant is a downlink scheduling grant, the downlink scheduling grant is downlink control information DCI for scheduling the uplink control channel;

or

When the scheduling grant is an uplink scheduling grant, the uplink scheduling grant is a DCI for scheduling an uplink shared channel overlapping with the time domain resources of the at least one uplink control channel;

or

In the case that the scheduling grant is an uplink scheduling grant, the uplink shared channel scheduled by the uplink scheduling grant overlaps with the at least one uplink control channel in one time unit;

or

When the scheduling grant is an uplink scheduling grant, the uplink shared channel scheduled by the uplink scheduling grant overlaps with the uplink shared channel of the at least one configuration grant in one time unit.
The method of claim 8, further comprising:

On the conflicting channel or the target carrier, it is forbidden to enable the uplink transmission skip function;

The conflicting channel is: in the at least one configured uplink shared channel, a channel overlapping with the time domain resources of the uplink control channel scheduled by the downlink scheduling grant, or, in the uplink shared channel scheduled by the uplink scheduling grant. , the uplink shared channel that overlaps with the time domain resource of the at least one uplink control channel, or the uplink shared channel scheduled by the uplink scheduling grant that overlaps the time domain resource of the at least one configuration authorized uplink shared channel channel;

The target carrier is the carrier where the conflicting channel is located.
The method according to claim 1, wherein if the MAC layer knows that the time domain resources of the at least one uplink shared channel overlap with the time domain resources of the at least one uplink control channel, the method further comprises:

A target uplink shared channel for carrying the uplink control information is determined from the at least one uplink shared channel at the MAC layer according to the second multiplexing rule.
The method according to any one of claims 1 to 10, wherein the generating a MAC PDU comprises:

In the at least one configured and authorized uplink shared channel, when the target uplink shared channel used to carry the uplink control information has no data to be transmitted, a MAC padding PDU is generated.
The method according to any one of claims 1 to 10, wherein the generating a MAC PDU comprises:

In the uplink shared channel authorized by the at least one configuration, when the target uplink shared channel for carrying the uplink control information is configured to transmit M times repeatedly, N MAC PDUs are generated, where M is a positive integer and N is less than or a positive integer equal to M.
An uplink transmission device, comprising:

The execution module is configured to, in the case where the time domain resources of at least one configuration authorized uplink shared channel overlap with the time domain resources of at least one uplink control channel, generate a MAC at the medium access control MAC layer according to any one of the following processing methods Protocol Data Unit PDU:

If the MAC layer learns that the time domain resources of the uplink shared channel overlap with the time domain resources of the uplink control channel, a MAC PDU is generated;

According to the multiplexing information notified to the MAC layer by the physical layer, a MAC PDU is generated;

Wherein, the at least one uplink control channel is used to carry uplink control information.
The apparatus according to claim 13, wherein the multiplexing information is used to indicate that the time domain resources of the at least one configuration granted uplink shared channel overlap with the time domain resources of the at least one uplink control channel.
14. The apparatus of claim 13, wherein the at least one configuration granted uplink shared channel is located on one or more carriers.
The apparatus of claim 13, wherein the multiplexing information is used to indicate at least one of the following:

Among the at least one uplink control channel, a target uplink control channel for carrying the uplink control information;

In the at least one configuration authorized uplink shared channel, the target uplink shared channel used to carry the uplink control information;

In the at least one configuration authorized uplink shared channel, there is a channel with overlapping time domain resources with the at least one uplink control channel;

In the at least one uplink control channel, there is a channel with overlapping time domain resources with the at least one configuration authorized uplink shared channel.
The apparatus according to claim 16, further comprising a first determining module for:

When the at least one uplink control channel includes multiple channels, the physical layer or the MAC layer determines the target uplink control channel from the multiple uplink control channels according to a first multiplexing rule;

or,

When the at least one configuration-authorized uplink shared channel includes multiple channels, the physical layer or the MAC layer determines the target uplink from the plurality of configuration-authorized uplink shared channels according to a second multiplexing rule shared channel;

or,

When the at least one configuration authorized uplink shared channel includes multiple, and the time domain resource of the target uplink control channel overlaps with the time domain resource of the at least one configuration authorized uplink shared channel, at the physical layer or The MAC layer determines the target uplink shared channel from the at least one configured and authorized uplink shared channel according to the second multiplexing rule and the target uplink control channel.
The apparatus of claim 16, wherein the target uplink shared channel is:

Among the at least one configuration authorized uplink shared channel, the corresponding channel with the largest configuration authorization number;

or

Among the at least one configuration authorized uplink shared channel, the corresponding channel with the smallest configuration authorization number;

or

In the at least one uplink shared channel of the configuration authorization, the channel with the largest number of the carrier where the corresponding configuration authorization is located;

or

Among the at least one uplink shared channel of the configuration grant, the channel with the lowest number of the carrier where the corresponding configuration grant is located.
The apparatus according to claim 13, wherein the multiplexing information is notified to the MAC layer by the physical layer when the terminal device receives the scheduling grant.
The apparatus of claim 19, wherein:

In the case that the scheduling grant is a downlink scheduling grant, the downlink scheduling grant is downlink control information DCI for scheduling the uplink control channel;

or

In the case where the scheduling grant is an uplink scheduling grant, the uplink scheduling grant is the DCI for scheduling the uplink shared channel overlapping the time domain resource of the at least one uplink control channel;

or

In the case that the scheduling grant is an uplink scheduling grant, the uplink shared channel scheduled by the uplink scheduling grant overlaps with the at least one uplink control channel in one time unit;

or

When the scheduling grant is an uplink scheduling grant, the uplink shared channel scheduled by the uplink scheduling grant overlaps with the uplink shared channel of the at least one configuration grant in one time unit.
The apparatus of claim 20, further comprising a disable enable module for:

On the conflicting channel or the target carrier, it is forbidden to enable the uplink transmission skip function;

The conflicting channel is: in the at least one configured uplink shared channel, a channel overlapping with the time domain resources of the uplink control channel scheduled by the downlink scheduling grant, or, in the uplink shared channel scheduled by the uplink scheduling grant. , the uplink shared channel that overlaps with the time domain resource of the at least one uplink control channel, or the uplink shared channel scheduled by the uplink scheduling grant that overlaps the time domain resource of the at least one configuration authorized uplink shared channel channel;

The target carrier is the carrier where the conflicting channel is located.
The apparatus according to claim 13, wherein if the MAC layer learns that the time domain resources of the at least one uplink shared channel overlap with the time domain resources of the at least one uplink control channel, the apparatus further comprises a second determining module, Used for:

A target uplink shared channel for carrying the uplink control information is determined from the at least one uplink shared channel at the MAC layer according to the second multiplexing rule.
The apparatus according to any one of claims 13 to 22, wherein the executing module is configured to: in the at least one configuration authorized uplink shared channel, the target uplink shared channel for carrying the uplink control information does not have When data needs to be transmitted, a MAC padding PDU is generated.
The apparatus according to any one of claims 13 to 22, wherein the executing module is configured to, in the at least one configuration authorized uplink shared channel, the target uplink shared channel used to carry the uplink control information is When configured to repeat transmission M times, generate N MAC PDUs, where M is a positive integer, and N is a positive integer less than or equal to M.
A terminal device, comprising a processor, a memory, and a program or instruction stored on the memory and executable on the processor, the program or instruction being executed by the processor to achieve as claimed in claims 1 to 12 The steps of any one of the uplink transmission methods.
A readable storage medium, on which a program or an instruction is stored, and when the program or instruction is executed by the processor, the steps of the uplink transmission method according to any one of claims 1-12 are implemented .
A chip, the chip includes a processor and a communication interface, the communication interface is coupled to the processor, and the processor is used to run a network-side device program or instruction to implement the method as claimed in any one of claims 1-12 The uplink transmission method described above.
A program product, the program product being stored in a non-volatile storage medium, the program product being configured to be executed by at least one processor to implement the uplink transmission of any one of claims 1-12 method.
A terminal device configured to perform the uplink transmission method of any one of claims 1-12.