Uplink transmission method, apparatus and device
By generating MAC PDUs at the MAC layer to handle time-domain resource conflicts between the uplink shared channel and the uplink control channel, the resource conflict problem under the uplink transmission skip function in the terminal device is resolved, thereby improving the system's communication efficiency and accuracy.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2020-07-20
- Publication Date
- 2026-03-20
AI Technical Summary
When the uplink transmission skip function is enabled on the terminal device, there is a conflict between the time domain resources of the uplink shared channel and the uplink control channel, which prevents the MAC layer from generating PDUs. This affects the multiplexing of uplink control information and the complexity of blind detection on the network side, thus reducing the system communication efficiency.
At the MAC layer, MAC PDUs are generated either based on the multiplexing information notified by the physical layer or directly, ensuring that the control information on the uplink control channel can be multiplexed onto the uplink shared channel, avoiding blind detection on the network side, and handling time-domain resource conflicts by generating MAC PDUs.
It reduces the complexity of network side blind detection, improves system communication efficiency, and ensures that uplink control information can be accurately processed even when there is no data transmission.
Smart Images

Figure CN113965997B_ABST
Abstract
Description
TECHNICAL FIELD
[0001] The present application belongs to the technical field of communication, and particularly relates to an uplink transmission method, device and equipment. BACKGROUND
[0002] When an uplink shared channel (such as a physical uplink shared channel (PUSCH)) of a terminal device enables an uplink transmission skipping (UL skipping) function, and there is no data to be transmitted in a data storage of the terminal device, even if a base station schedules a user to perform data transmission, the UL skipping function allows the user to ignore the scheduling of the base station and not to perform uplink transmission.
[0003] In the related art, in the case where the uplink shared channel of the terminal device enables the UL skipping function, if there is a resource conflict between a time domain resource of an uplink control channel (such as a physical uplink control channel (PUCCH)) and a time domain resource of a dynamically scheduled uplink shared channel, since the PUSCH can have no data to be sent, the MAC layer cannot generate a PDU according to whether there is UCI to be multiplexed, based on whether there is data to generate a PDU. SUMMARY
[0004] The purpose of the embodiments of the present application is to provide an uplink transmission method, device and equipment, so that the MAC layer can generate a PDU based on whether there is UCI to be multiplexed.
[0005] In a first aspect, an uplink transmission method is provided, applied to a terminal device, and the method comprises: in the case where the terminal device enables an uplink transmission skipping function, if a time domain resource of at least one uplink shared channel overlaps with a time domain resource of at least one uplink control channel, a MAC PDU is generated at a MAC layer according to any one of the following processing manners: if the MAC layer learns that the time domain resource of the uplink shared channel overlaps with the time domain resource of the uplink control channel, the MAC PDU is generated; the MAC PDU is generated according to multiplexing information informed by a physical layer to the MAC layer; wherein the at least one uplink control channel carries at least one uplink control information.
[0006] In a second aspect, an uplink transmission apparatus is provided, the apparatus comprising: an execution module configured to, in the case that the terminal device enables the uplink transmission skipping function, if the time domain resource of the at least one uplink shared channel overlaps with the time domain resource of the at least one uplink control channel, generate a MAC PDU at the MAC layer according to any one of the following processing manners: if the MAC layer learns that the time domain resource of the uplink shared channel overlaps with the time domain resource of the uplink control channel, generate the MAC PDU; generate the MAC PDU according to the multiplexing information informed by the physical layer to the MAC layer; wherein the at least one uplink control channel carries at least one uplink control information.
[0007] In a third aspect, a terminal device is provided, the terminal device comprising a processor, a memory, and a program or instructions stored in the memory and executable on the processor, and the program or instructions, when executed by the processor, implement the steps of the method according to the first aspect.
[0008] In a fourth aspect, a readable storage medium is provided, the readable storage medium storing a program or instructions, and the program or instructions, when executed by a processor, implement the steps of the method according to the first aspect.
[0009] In a fifth aspect, a chip is provided, the chip comprising a processor and a communication interface, the communication interface and the processor being coupled, and the processor being configured to execute a network side device program or instructions to implement the method according to the first aspect.
[0010] In a sixth aspect, a program product is provided, the program product being stored in a non-volatile storage medium, and the program product being configured to be executed by at least one processor to implement the method according to the first aspect.
[0011] In the embodiment of the present application, in the case that the terminal device enables the uplink transmission skipping function, if the time domain resource of at least one uplink shared channel overlaps with the time domain resource of at least one uplink control channel, the MAC layer can generate the MAC PDU in the following any one processing mode: mode 1, generating the MAC PDU if the MAC layer learns that the time domain resource of the uplink shared channel overlaps with the time domain resource of the uplink control channel; mode 2, generating the MAC PDU according to the multiplexing information informed by the physical layer to the MAC layer; wherein the at least one uplink control channel carries at least one uplink control information. In this way, in the case of conflict between the uplink shared channel and the uplink control channel, the MAC layer can generate the MAC PDU, so that the terminal device can support multiplexing the uplink control information carried on the uplink control channel to the uplink shared channel that enables the uplink transmission skipping function even in the case of no data transmission, thereby enabling the network side device to accurately determine the resource of the uplink control channel multiplexing without two kinds of blind detection, reducing the complexity of blind detection of the network side, and improving the system communication efficiency. BRIEF DESCRIPTION OF DRAWINGS
[0012] Figure 1 is a system architecture diagram of a communication system provided by an embodiment of the present application;
[0013] Figure 2 is a method flowchart of an uplink transmission method provided by an embodiment of the present application;
[0014] Figure 3 is a structural schematic diagram of an uplink transmission device provided by an embodiment of the present application;
[0015] Figure 4 is a structural schematic diagram of a communication device provided by an embodiment of the present application;
[0016] Figure 5 is a structural schematic diagram of a terminal device provided by an embodiment of the present application. DETAILED DESCRIPTION
[0017] The technical solutions in the embodiments of the present application will be described clearly and completely below with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, rather than all the embodiments of the present application. Based on the embodiments in the present application, all other embodiments obtained by those skilled in the art without creative labor fall within the scope of protection of the present application.
[0018] The technical terms related to the technical solutions provided by the embodiments of the present application will be explained below:
[0019] 1, time domain overlap (or time domain conflict) of transmission resources
[0020] Compared with the mobile communication system in the past, the future 5G mobile communication system needs to adapt to more diversified scenarios and service requirements. The main scenarios of 5G include enhanced mobile broadband (eMBB), massive machine type communications (mMTC) and ultra-reliable and low latency communications (URLLC), which put forward the requirements of high reliability, low delay, large bandwidth and wide coverage for the mobile communication system. The UE can support different services, for example, the UE supports both low latency and high reliability URLLC services and large capacity and high speed eMBB services. The new radio (NR) system can have different starting symbols and lengths due to different channels, so the time domain overlap of transmission resources may occur. Generally, in order to maintain the single carrier characteristics of uplink, when there are multiple overlapping uplink transmission resources in a time slot, the single carrier characteristics of the UE will be destroyed, and the different transmission powers will cause the deterioration of channel estimation performance. For this situation, it is usually considered as a conflict, and a corresponding conflict solution needs to be designed to merge or discard some information.
[0021] 2、Uplink channel
[0022] The uplink control channel includes a physical uplink control channel (PUCCH).
[0023] The uplink shared channel includes a physical uplink shared channel (PUSCH).
[0024] 3、UCI multiplexing on PUSCH defined by physical layer
[0025] Uplink control information (e.g., UCI) is transmitted on the uplink control channel (e.g., PUCCH). If the terminal device is transmitting data on the uplink shared channel (e.g., PUSCH), in principle, PUCCH and PUSCH can be transmitted simultaneously, i.e., UCI is retained on PUCCH. However, this will increase the Cubic Metric; in addition, if the requirement of out-of-band emission is to be met at a higher transmission power, and the interval in the frequency domain is large when PUSCH and PUCCH are transmitted simultaneously (PUCCH is generally transmitted at both ends of the frequency band), this will bring challenges to the implementation of radio frequency (RF). Therefore, in general, if the PUCCH resource required to transmit UCI overlaps in time with the resource of PUSCH, and the base station ensures that the condition of UCI multiplexing processing time is met when scheduling the PUSCH, UCI will be multiplexed on PUSCH to avoid transmitting PUCCH at the same time.
[0026] 4. PUCCH and PUSCH collision handling
[0027] In NR R15, within one PUCCH group, simultaneous transmission of PUCCH and PUSCH is not supported, regardless of whether PUCCH and PUSCH are in the same serving cell or different serving cells. When PUCCH and PUSCH time domain resources overlap (including partial time domain resource overlap and full time domain resource overlap), the UE will discard or combine according to the corresponding rules under certain time requirements.
[0028] For example, 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 (UCI) (except SR) carried on the PUCCH into the PUSCH for transmission. For example, PUCCH 1 carrying hybrid automatic repeat request acknowledgement (HARQ-ACK) or channel state information (CSI) and PUSCH 2 overlap, the UE multiplexes the HARQ-ACK / CSI carried on PUCCH 1 into PUSCH 2 for transmission.
[0029] Specifically, the UE first processes the time domain resource overlapping between multiple PUCCHs (if any), and the result of the processing is one or multiple PUCCHs without time domain resource overlapping. Then the UE processes the time domain resource overlapping between PUCCH and PUSCH. If the PUCCH only overlaps with one PUSCH, the UE multiplexes the UCI (excluding SR) in the PUSCH. If the PUCCH only overlaps with multiple PUSCHs, the UE selects one PUSCH to multiplex according to the multiplexing rule in the related art. The first multiplexing rule (i.e., indicating the order of selecting PUSCH to multiplex UCI) is as follows:
[0030] Rule 1: PUSCH carrying Aperiodic Channel State Information (A-CSI).
[0031] Rule 2: PUSCH with the earliest starting slot.
[0032] Rule 3: Dynamically scheduled PUSCH > configured grant PUSCH or semi-persistent PUSCH.
[0033] Rule 4: PUSCH in the serving cell with smaller index > PUSCH in the serving cell with larger index.
[0034] Rule 5: PUSCH with earlier transmission symbol > PUSCH with later transmission symbol.
[0035] For example, the physical layer priority of PUCCH is determined by the priority of the UCI it carries. The priority of SR is configured by radio resource control (RRC), and the priority of periodic CSI and semi-persistent CSI (SP-CSI) is predefined as low priority. The priority of HARQ-ACK is indicated by the corresponding DCI or determined according to the semi-persistent scheduling (SPS) configuration. The transmission priority of PUSCH is indicated by the corresponding scheduling downlink control information (DCI) of PUSCH, or for configured grant PUSCH, the priority is configured by RRC.
[0036] When the time domain resources of PUCCH and PUCCH overlap or the time domain resources of PUCCH and PUSCH overlap, the UE first processes the transmissions with the same priority (the rule is the same as R15), and then processes the transmissions with different priorities. In the processing of transmissions with different priorities, the UE cancels (or discards) the low-priority uplink resource and transmits the high-priority uplink resource under the condition of meeting certain time requirements.
[0037] 5. Uplink skipping function defined by MAC layer
[0038] The MAC layer defines a procedure for the terminal to perform uplink skipping (UL skipping) in the protocol TS 38.321. If the following conditions are met, the MAC entity will not generate a MAC PDU for the HARQ entity:
[0039] Condition 1: The MAC entity is configured with the parameter skipUplinkTxDynamic and the value of this parameter is set to true, and the MAC locates the HARQ entity indicated in the uplink grant (UL grant).
[0040] Condition 2: There is no aperiodic CSI requested for this PUSCH transmission in the UL grant as specified in TS 38.212.
[0041] Condition 3: The MAC PDU includes zero MAC SDUs.
[0042] Condition 4: The MAC PDU contains only a periodic Buffer Status Report (BSR) and has no data available for any Logical Channel Group (LCG), or the MAC PDU contains only a padding BSR.
[0043] In the related art, in the case that the uplink shared channel of the terminal device enables the UL skipping function, if there is a resource conflict between the time domain resource of the uplink control channel (such as PUCCH) and the time domain resource of the dynamically scheduled uplink shared channel, since the PUSCH can have no data to send, the MAC layer cannot generate a PDU based on whether there is data to generate a PDU, and cannot generate a PDU according to whether there is UCI to multiplex.
[0044] Specifically, in the case that there is a resource conflict between the time domain resource of the uplink control channel (such as PUCCH) and the time domain resource of the dynamically scheduled uplink shared channel, the terminal device can choose not to generate a PUSCH to transmit the uplink control information (such as UCI) on the PUCCH, or can choose to generate a PUSCH to multiplex the uplink control information on the PUSCH.
[0045] Thus, the resource for UCI multiplexing cannot be determined at the network end, and the network side cannot accurately receive the UCI. Especially when the number of carriers is large, the network side device needs to perform blind detection based on two assumptions that the uplink control information is multiplexed on the PUSCH of the carrier or not on each carrier, which increases the complexity of blind detection of the network side and causes a large burden to the network side.
[0046] To solve the above problems, the embodiment of the present application provides an uplink transmission method, device and equipment. In the case that a terminal device enables an uplink transmission skipping function, if time domain resources of at least one uplink shared channel overlap with time domain resources of at least one uplink control channel, a MAC layer can generate a MAC PDU according to any one of the following processing manners: manner 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, the MAC PDU is generated; manner 2, the MAC PDU is generated according to multiplexing information informed by a physical layer to the MAC layer; wherein the at least one uplink control channel carries at least one uplink control information. In this way, in the case that the uplink shared channel and the uplink control channel conflict, the MAC PDU can be generated by the MAC layer, so that the terminal device can support multiplexing of the uplink control information carried on the uplink control channel to the uplink shared channel which enables the uplink transmission skipping function even in the case that there is no data transmission, and further, the network side device can accurately determine the resource multiplexed by the uplink control channel without two kinds of blind detection assumptions, thereby reducing the complexity of blind detection of the network side and improving the system communication efficiency.
[0047] 6. Other terms
[0048] The terms "first", "second", etc. in the specification and claims of the present application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the data used in this way can be exchanged under appropriate circumstances, so that the embodiments of the present application can be implemented in an order other than those illustrated or described herein, and the objects distinguished by "first", "second" are usually a class, and are not limited to the number of objects, for example, the first object can be one or more. In addition, "and / or" in the specification and claims means at least one of the connected objects, and the character " / " generally represents that the objects before and after are in an "or" relationship.
[0049] It is worth noting that the technology described in the embodiments of the present application is not limited to Long Term Evolution (LTE) / LTE-Advanced (LTE-A) systems, but can also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency-Division Multiple Access (SC-FDMA) and other systems. The terms "system" and "network" in the embodiments of the present application are often used interchangeably, and the described technology can be used in the above-mentioned systems and radio technologies, as well as in other systems and radio technologies. However, the following description describes a New Radio (NR) system for example purposes, and NR terminology is used in most of the following description, although these technologies can also be applied outside the NR system application, such as 6th Generation (6G) communication systems. th
[0050] Figure 1 A block diagram of a wireless communication system to which embodiments of the present application can be applied is shown. The wireless communication system includes a terminal 11 and a network side device 12. The terminal 11 can also be referred to as a terminal device or a user terminal (UE). The terminal 11 can be a terminal side device such as a mobile phone, a tablet personal computer, a laptop computer, a personal digital assistant (PDA), a palmtop computer, a netbook, an ultra-mobile personal computer (UMPC), a mobile Internet device (MID), a wearable device, or a vehicle user equipment (VUE), a pedestrian user equipment (PUE), etc. The wearable device includes a bracelet, an earphone, glasses, etc. It should be noted that the specific type of the terminal 11 is not limited in the embodiments of the present application. The network side device 12 can be a base station or a core network. The base station can be referred to as a node B, an evolved node B, an access point, a base transceiver station (BTS), a radio base station, a radio transceiver, a basic service set (BSS), an extended service set (ESS), a node B, an evolved node B (eNB), a home node B, a home evolved node B, a WLAN access point, a WiFi node, a transmitting receiving point (TRP), or some other appropriate terminology in the art, as long as the same technical effects are achieved. The base station is not limited to a specific technical term, and it should be noted that only a base station in an NR system is taken as an example in the embodiments of the present application, but the specific type of the base station is not limited.
[0051] The uplink transmission method provided by the embodiments of the present application will be described in detail below with reference to the accompanying drawings, specific embodiments and application scenarios.
[0052] The uplink transmission method provided by the embodiments 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 Figure 2 The data transmission method provided by the embodiments of the present application can include the following step 201.
[0053] Step 201: In the case that the terminal device enables the uplink transmission skipping function, if the time domain resource of at least one uplink shared channel overlaps with the time domain resource of at least one uplink control channel, a MAC PDU is generated at the MAC layer in any one of the following processing manners.
[0054] The first processing manner: In the case that the terminal device enables the uplink transmission skipping function, if the time domain resource of at least one 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 overlaps with the time domain resource of the at least one uplink control channel, a MAC PDU is generated at the MAC layer.
[0055] The second processing manner: A MAC PDU is generated at the MAC layer (or Layer 2) according to multiplexing information notified by the physical layer (or Layer 1) to the MAC layer.
[0056] In the embodiments of the present application, the at least one uplink control channel carries at least one uplink control information.
[0057] In the embodiments of the present application, the at least one uplink shared channel is located on one or more carriers.
[0058] It should be noted that the overlap of the time domain resource of the at least one uplink shared channel with the time domain resource of the at least one uplink control channel means that there is a conflict in time between the at least one uplink shared channel and the at least one uplink control channel. For example, the time domain resource can be one or more time slots / sub-time slots / symbols / sub-frames.
[0059] In the embodiments of the present application, the terminal device enabling the uplink transmission skipping function can be considered as the terminal device enabling the uplink transmission skipping function of the uplink shared channel.
[0060] In the embodiments of the present application, the following relationship exists between the MAC PDU and the uplink control information (such as UCI): 1) if the target uplink shared channel overlaps with the uplink control channel resource, the MAC PDU and the UCI are multiplexed and transmitted on the target uplink shared channel; or 2) if the target uplink shared channel does not overlap with the target uplink control channel resource, the UCI is transmitted on the target uplink control channel, and the MAC PDU is transmitted on the target uplink shared channel.
[0061] Optionally, in the embodiments of the present application, the multiplexing information can be used to indicate that the time domain resource of the at least one uplink shared channel overlaps with the time domain resource of the at least one uplink control channel.
[0062] Optionally, in the embodiments of the present application, the multiplexing information can also be used to indicate the target uplink shared channel. Among the at least one uplink shared channel, the uplink shared channel used to carry the uplink control information of the at least one uplink control channel. Further, at this time, the MAC layer can not need the physical layer to inform that there is a conflict between the uplink control channel and the shared channel, and the MAC layer only needs to generate the MAC PDU according to the multiplexing information informed by the physical layer.
[0063] Optionally, in the embodiments of the present application, the multiplexing information is used to indicate at least one of the following:
[0064] Among the at least one uplink control channel, the target uplink control channel used to carry the uplink control information of the at least one uplink control channel;
[0065] Among the at least one uplink shared channel, the target uplink shared channel used to carry the uplink control information of the at least one uplink control channel;
[0066] The at least one uplink shared channel;
[0067] The at least one uplink control channel.
[0068] It should be noted that in the embodiments of the present application, the target uplink shared channel can be one or multiple, and the target uplink control channel can be one or multiple, which are not limited by the embodiments of the present application.
[0069] Optionally, in the embodiments of the present application, the multiplexing information can be informed by the physical layer to the MAC layer when the terminal device receives the scheduling grant (downlink scheduling grant or uplink scheduling grant).
[0070] Further optionally, in the embodiments of the present application, in the case that the scheduling grant is a downlink scheduling grant, the downlink scheduling grant is a DCI scheduling part or all of the at least one uplink control channel. For example, the downlink scheduling grant is the latest DCI scheduling the PUCCH carrying the UCI.
[0071] Further optionally, in the embodiments of the present application, in the case that the scheduling grant is an uplink scheduling grant, the uplink scheduling grant is a DCI scheduling part or all of the at least one uplink shared channel, or the uplink shared channel scheduled by the uplink scheduling grant overlaps with the at least one uplink control channel in a time unit.
[0072] Exemplarily, in the case that the uplink scheduling grant is DCI scheduling part or all of the at least one uplink shared channel, the uplink scheduling grant is DCI scheduling PUSCH on the PCell.
[0073] Exemplarily, the time unit can be a subframe, a slot, a sub-slot, a symbol, etc.
[0074] Further, the terminal device is informed by the physical layer to the MAC layer when receiving the ending time slot or symbol of the DCI of the scheduling grant, or the terminal device is informed by the physical layer to the MAC layer X time units after receiving the ending time slot or symbol of the DCI of the scheduling grant. The X is predefined or network configured or related to the UE capability, and further, the X can be the processing time of the downlink control channel (PDCCH).
[0075] Optionally, in the embodiment of the present application, the process of generating the MAC PDU by the terminal device in step 201 can further include the following step 201a:
[0076] Step 201a: generating the MAC PDU and transmitting the MAC PDU on the target uplink shared channel.
[0077] The target uplink shared channel is the uplink shared channel in the at least one uplink shared channel for carrying the uplink control information of the at least one uplink control channel.
[0078] Exemplarily, when the terminal device has no data, a MAC padding PDU is generated. The terminal device has no data, which can be specifically that there is no data in the logical channel group (Logical channel group) corresponding to the PUSCH.
[0079] Exemplarily, when the MAC layer generates the MAC PDU according to the multiplexing information, the MAC generates the MAC padding PDU when there is no UL-SCH on any one of the PUSCHs.
[0080] Exemplarily, when the MAC layer generates the MAC PDU according to the multiplexing information, the MAC layer generates the MAC padding PDU if there is no UL-SCH or no data on the target PUSCH.
[0081] Further optionally, in the embodiment of the present application, the uplink transmission method provided by the present application can further include the following step A1:
[0082] Step A1: disabling the uplink transmission skipping function on the target carrier.
[0083] The target carrier is a carrier on which an uplink shared channel overlaps in time domain resources with the uplink control channel.
[0084] For example, when at least one PUCCH overlaps in time with a PUSCH, the UE disables PUSCH UL skipping. Further, the UE disables PUSCH UL skipping on a carrier on which a PUSCH conflicts with a PUCCH.
[0085] Optionally, for the processing mode 2, the uplink transmission method provided in the embodiments of the present application can further include the following step B1 or step B2 or step B3.
[0086] Step B1: In the case that the at least one uplink control channel includes a plurality of uplink control channels, the physical layer or the MAC layer determines the target uplink control channel from the plurality of uplink control channels according to a first multiplexing rule.
[0087] Step B2: In the case that the at least one uplink shared channel includes a plurality of uplink shared channels, the physical layer or the MAC layer determines the target uplink shared channel from the plurality of uplink shared channels according to a second multiplexing rule.
[0088] Step B3: In the case that the at least one uplink shared channel includes a plurality of uplink shared channels, and the time domain resources of the target uplink control channel overlap with the time domain resources of the plurality of uplink shared channels, the physical layer or the MAC layer determines the target uplink shared channel from the plurality of uplink shared channels according to the second multiplexing rule and the target uplink control channel.
[0089] For example, the first multiplexing rule can be a PUCCH multiplexing rule for UCI on PUCCH.
[0090] In an example, the multiplexing rule for HARQ-ACK on PUCCH and the multiplexing rule for scheduling request (SR) on PUCCH are shown in Table 1 as follows:
[0091] Table 1
[0092]
[0093] 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.
[0094] For CSI+SR: Transmit SR and CSI on the PUCCH of CSI, [log2(K+1)] bits are prepended to the periodic / semi-static CSI information bits in ascending order to indicate the corresponding SR state (activated or non-activated) in the SR resource Id.
[0095] For HARQ-ACK / SR / CSI: If the HARQ-ACK is the feedback to the PDSCH without PDCCH scheduling, the HARQ-ACK or HARQ-ACK+SR will be multiplexed on the CSI PUCCH for transmission.
[0096] If the HARQ-ACK is the feedback to the PDSCH with PDCCH scheduling, the HARQ-ACK or HARQ-ACK+SR+CSI will be multiplexed on one PUCCH for transmission. Wherein, the PUCCH is determined based on the number of HARQ-ACK, CSI and SR bits in the RRC configured multiple resource sets.
[0097] For example, for the above step B2, in the case that the above at least one uplink shared channel includes multiple uplink shared channels, and the multiple uplink shared channels are located on a single carrier, the above target uplink shared channel is determined based on at least one of the following:
[0098] The uplink shared channel with the earliest starting time domain position in the above multiple uplink shared channels;
[0099] The uplink shared channel in the above multiple uplink shared channels that triggers aperiodic CSI reporting;
[0100] The physical layer informs the MAC layer to multiplex the above uplink control information on the above target uplink shared channel;
[0101] The physical layer informs the MAC layer whether each of the above multiple uplink shared channels multiplexes the above uplink control information.
[0102] For example, taking PUSCH as an example of the above uplink shared channel, when there are multiple PUSCHs on a single carrier, the PHY layer needs to determine the target PUSCH carrying UCI according to the second multiplexing rule. The specific multiplexing mode includes: multiplexing mode 1: the target PUSCH is the PUSCH with the earliest starting time among the multiple PUSCHs on the carrier; multiplexing mode 2: the target PUSCH is the PUSCH that triggers aperiodic-CSI (A-CSI) among the multiple PUSCHs on the carrier.
[0103] For example, for the above step B2, in the case that the at least one uplink shared channel comprises a plurality of uplink shared channels, and the plurality of uplink shared channels are located on a plurality of carriers, the target uplink shared channel satisfies at least one of the following:
[0104] the uplink shared channel with the earliest starting time domain position in the plurality of uplink shared channels on the first carrier;
[0105] the uplink shared channel on which aperiodic CSI reporting is triggered in the plurality of uplink shared channels on the first carrier;
[0106] the uplink shared channel on the second carrier;
[0107] the uplink control channel on the third carrier.
[0108] The first carrier is a carrier with a number satisfying a predetermined condition (e.g., the smallest number) in the plurality of carriers; the second carrier is a carrier on which uplink scheduling is performed and with a number satisfying the predetermined condition in the plurality of carriers; and the third carrier is a carrier on which aperiodic CSI reporting is triggered and with a number satisfying the predetermined condition in the plurality of carriers.
[0109] For example, taking PUSCH as an example of the uplink shared channel, when there are a plurality of PUSCHs in a plurality of carriers, the PHY layer needs to determine the target PUSCH and the carrier on which the target PUSCH is located according to the second multiplexing rule. Specifically, the multiplexing modes include: multiplexing mode 1: the target PUSCH is the PUSCH with the earliest starting time in the plurality of PUSCHs on the carrier with the smallest number; multiplexing mode 2: the target PUSCH is the PUSCH on which aperiodic-CSI (A-CSI) is triggered in the plurality of PUSCHs on the carrier with the smallest number; multiplexing mode 3: the target PUSCH is the PUSCH on the carrier with the smallest number and on which dynamic UL scheduling is performed in the plurality of carriers; and multiplexing mode 4: the target PUSCH is the PUSCH on the carrier with the smallest number and on which aperiodic CSI reporting is triggered in the plurality of carriers.
[0110] For example, the MAC layer or the PHY layer will determine the target uplink shared channel according to the second multiplexing rule. In one example, when the PHY layer informs the MAC layer that the target PUCCH conflicts with the at least one PUSCH, the MAC layer will determine the target PUSCH carrying the UCI according to the multiplexing rule of the target PUCCH and UCI on PUSCH.
[0111] Optionally, in the embodiments of the present application, for the processing mode 1, if the MAC layer learns that the time domain resource of the at least one uplink shared channel overlaps with the time domain resource of the at least one uplink control channel, the uplink transmission method provided by the embodiments of the present application can further include the following step C1:
[0112] Step C1: determining a target uplink shared channel from the at least one uplink shared channel according to the second multiplexing rule at the MAC layer.
[0113] For example, taking the PUSCH as the uplink shared channel, when the MAC layer determines the target PUCCH carrying the one or more UCIs according to the second multiplexing rule (i.e., the PUCCH multiplexing rule of UCI on PUSCH), if the target PUCCH conflicts with the at least one PUSCH, the MAC layer determines the target PUSCH carrying the UCI according to the target PUCCH and the second multiplexing rule.
[0114] For example, taking the PUSCH as the uplink shared channel, when the at least one PUSCH on one or more carriers is located in multiple carriers, the MAC layer determines the target PUSCH carrying the UCI and the carrier where the target PUSCH is located according to the second multiplexing rule.
[0115] For example, taking the PUSCH as the uplink shared channel and the PUCCH as the uplink control channel, the MAC layer determines the target PUCCH carrying the one or more UCIs according to the first multiplexing rule (i.e., the PUCCH multiplexing rule of UCI on PUCCH).
[0116] For example, if the MAC layer learns that the one or more PUCCHs carrying the UCI conflict with the 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.
[0117] The following takes the PUSCH as the uplink shared channel and the PUCCH as the uplink control channel, and explains the uplink transmission method provided by the embodiments of the present application through three examples.
[0118] Example 1:
[0119] In the case where the PUSCH UL skipping function is enabled at the UE, if the UE receives one or more UL grants, schedules the at least one PUSCH on one or more carriers, and receives one or more DL grants, schedules one or more PUCCHs carrying the UCI, the UE can determine the transmission of the UCI according to the following steps:
[0120] Step 11: Decode DL grant and / or UL grant.
[0121] Step 12: If there are multiple PUCCHs, the PHY layer determines the resource of the target PUCCH carrying UCI according to the multiplexing rule of UCI on PUCCH.
[0122] Step 13: If the target PUCCH resource conflicts with at least one PUSCH on one or more carriers, the PHY layer determines the resource of the target PUSCH carrying UCI according to the multiplexing priority of UCI on PUSCH in at least one PUSCH.
[0123] Step 14: The PHY layer informs the MAC layer of the UCI multiplexing information (i.e., the content in step 13), and the MAC generates a MAC PDU according to the UCI multiplexing information.
[0124] Step 15: If there is no UL-SCH, the MAC layer generates a padding PDU.
[0125] Step 16: Perform mapping of UCI on the target PUSCH.
[0126] Step 17: Perform mapping of (padding) data on the target PUSCH.
[0127] It should be noted that the execution order between steps 16 and 17 in the above embodiment is not limited, and steps 16 can be executed first and then step 17 (i.e., UCI mapping is performed first and then data mapping), or step 17 can be executed first and then step 16 (i.e., data mapping is performed first and then UCI mapping).
[0128] Example 2:
[0129] In the case where the UE is enabled with PUSCH UL skipping function, if the UE receives one or more UL grants scheduling at least one PUSCH on one or more carriers, and the UE receives one or more DL grants scheduling one or more PUCCHs carrying UCI, the UE determines the transmission of UCI according to the following steps:
[0130] Step 21: Decode DL grant and / or UL grant.
[0131] Step 22: If there are multiple PUCCHs, the PHY layer determines the resource of the target PUCCH carrying UCI according to the multiplexing rule of UCI on PUCCH.
[0132] Step 23: The PHY layer informs the MAC layer of the UCI multiplexing information (i.e. the content in step 12), and the MAC layer generates a MAC PDU according to the UCI multiplexing information.
[0133] Step 24: If the target PUCCH resource collides with at least one PUSCH on one or more carriers, the MAC layer determines the resource of the target PUSCH for carrying UCI according to the UCI on PUSCH multiplexing rule in the at least one PUSCH.
[0134] Step 25: The MAC generates a PDU for the target PUSCH, and generates a padding PDU if there is no UL-SCH.
[0135] Step 26: The mapping of UCI is performed on the target PUSCH.
[0136] Step 27: The mapping of (padding) data is performed on the target PUSCH.
[0137] It should be noted that the execution order between step 26 and step 27 in the above embodiment is not limited, and step 26 can be executed first and then step 27 (i.e. UCI mapping is performed first and then data mapping), or step 27 can be executed first and then step 26 (i.e. data mapping is performed first and then UCI mapping).
[0138] Example 3:
[0139] In the case where the UE is enabled with the PUSCH UL skipping function, if the UE receives one or more UL grants, schedules at least one PUSCH on one or more carriers, and the UE receives one or more DL grants, schedules one or more PUCCHs carrying UCI, the UE determines the transmission of UCI according to the following steps:
[0140] Step 31: Decode the DL grant and / or the UL grant.
[0141] Step 32: The PHY layer informs the MAC layer after step 31 that the one or more PUCCHs carrying UCI collide with the at least one PUSCH on the one or more carriers.
[0142] Step 33: The MAC generates a MAC PDU for the first PUSCH (set) with collision according to the UCI multiplexing information.
[0143] Step 34: The MAC generates a padding PDU if there is no UL-SCH.
[0144] Step 35: If multiple PUCCHs exist, the PHY layer determines the resources of the target PUCCH carrying the UCI according to the UCI on PUCCH multiplexing rules.
[0145] Step 36: If the target PUCCH resource conflicts with at least one PUSCH on one or more carriers, the PHY layer determines the resource for carrying the target PUSCH in at least one PUSCH according to the UCI on PUSCH multiplexing rule.
[0146] Step 37: If the target PUSCH has a UL-SCH, then perform UCI and data mapping on the target PUSCH.
[0147] Step 38: Otherwise, map the UCI and padding data on the target PUSCH.
[0148] Step 39: If the target PUSCH does not belong to the first PUSCH (set), then perform data mapping on the first PUSCH (set).
[0149] Step 40: If a PUSCH in the first PUSCH (set) has no data, then perform padding data mapping.
[0150] It should be noted that this embodiment does not limit the execution order of UCI mapping and data mapping. UCI mapping can be performed first and then data mapping, or data mapping can be performed first and then UCI mapping.
[0151] The uplink transmission method provided in the embodiments of the present application can be executed by an uplink transmission device or a control module in the uplink transmission device. The uplink transmission device is taken as an example to illustrate the uplink transmission method provided in the embodiments of the present application.
[0152] It should be noted that the execution subject of the uplink transmission method provided in the embodiments of the present application can be an uplink transmission device, or a control module in the uplink transmission device for executing the uplink transmission method. The uplink transmission device is taken as an example to illustrate the uplink transmission method provided in the embodiments of the present application.
[0153] The uplink transmission device provided in the embodiments of the present application can be used for the uplink transmission method provided in the embodiments of the present application. Figure 3 The uplink transmission device 300 provided in the embodiments of the present application can include an execution module 301, in which:
[0154] The execution module 301 is configured to, in the case that the terminal device is enabled with the uplink transmission skipping function, if the time domain resource of the at least one uplink shared channel overlaps with the time domain resource of the at least one uplink control channel, generate a MAC PDU at the MAC layer according to any one of the following processing manners: if the MAC layer learns that the time domain resource of the uplink shared channel overlaps with the time domain resource of the uplink control channel, generate the MAC PDU; or generate the MAC PDU according to multiplexing information notified by the physical layer to the MAC layer; wherein the at least one uplink control channel carries at least one uplink control information.
[0155] Optionally, in the embodiments of the present application, the multiplexing information is used to indicate that the time domain resource of the at least one uplink shared channel overlaps with the time domain resource of the at least one uplink control channel.
[0156] Optionally, in the embodiments of the present application, the at least one uplink shared channel is located on one or more carriers.
[0157] Optionally, in the embodiments of the present application, the multiplexing information is used to indicate at least one of the following: a target uplink control channel in the at least one uplink control channel, which is used to carry uplink control information of the at least one uplink control channel; a target uplink shared channel in the at least one uplink shared channel, which is used to carry uplink control information of the at least one uplink control channel; the at least one uplink shared channel; and the at least one uplink control channel.
[0158] Optionally, in the embodiments of the present application, the execution module 301 is further configured to: in the case that the at least one uplink control channel comprises a plurality of uplink control channels, determine the target uplink control channel from the plurality of uplink control channels according to a first multiplexing rule at the physical layer or the MAC layer; or in the case that the at least one uplink shared channel comprises a plurality of uplink shared channels, determine the target uplink shared channel from the plurality of uplink shared channels according to a second multiplexing rule at the physical layer or the MAC layer; or in the case that the at least one uplink shared channel comprises a plurality of uplink shared channels, and the time domain resource of the target uplink control channel overlaps with the time domain resources of the plurality of uplink shared channels, determine the target uplink shared channel from the plurality of uplink shared channels according to the second multiplexing rule and the target uplink control channel at the physical layer or the MAC layer.
[0159] Optionally, in the embodiments of the present application, the multiplexing information is notified by the physical layer to the MAC layer when the terminal device receives the scheduling grant.
[0160] Optionally, in the embodiments of the present application, in the case that the scheduling grant is a downlink scheduling grant, the downlink scheduling grant is DCI scheduling the uplink control channel; in the case that the scheduling grant is an uplink scheduling grant, the uplink scheduling grant is DCI scheduling the uplink shared channel, or the uplink shared channel scheduled by the uplink scheduling grant overlaps with the at least one uplink control channel in a time unit.
[0161] Optionally, in the embodiments of the present application, the execution module 301 is further configured to: disable the uplink transmission skipping function on a target carrier; wherein the target carrier is a carrier on which an uplink shared channel overlapping with the time domain resource of the uplink control channel is located.
[0162] Optionally, in the embodiment of the present application, the execution module 301 is further configured to: if the MAC layer learns that the time domain resource of the at least one uplink shared channel overlaps with the time domain resource of the at least one uplink control channel, determining a target uplink shared channel from the at least one uplink shared channel according to a second multiplexing rule at the MAC layer.
[0163] Optionally, in the embodiment of the present application, as shown in Figure 3 the device 300 further includes a transmission module 302, where the transmission module 302 is configured to: transmit the MAC PDU on the target uplink shared channel; and the target uplink shared channel is an uplink shared channel from the at least one uplink shared channel that is used to carry the uplink control information of the at least one uplink control channel.
[0164] The uplink transmission device provided by the embodiment of the present application can generate a MAC PDU at the MAC layer in the following manner: manner 1, generating the MAC PDU if the MAC layer learns that the time domain resource of the uplink shared channel overlaps with the time domain resource of the uplink control channel; and manner 2, generating the MAC PDU according to the multiplexing information notified by the physical layer to the MAC layer; and the at least one uplink control channel carries at least one uplink control information. In this way, in the case of conflict between the uplink shared channel and the uplink control channel, the MAC PDU can be generated, so that the terminal device can support multiplexing the uplink control information carried on the uplink control channel to the uplink shared channel that enables the uplink transmission skip function even in the case of no data transmission, and thus the network side device can accurately determine the resource of the uplink control channel multiplexing without two blind detections, thereby reducing the complexity of blind detection at the network side and improving the system communication efficiency.
[0165] The uplink transmission device in the embodiment of the present application can be a device, or a component, an integrated circuit, or a chip in a terminal. The device can be a mobile terminal, or a non-mobile terminal. Exemplarily, the mobile terminal can include, but is not limited to, the types of the terminal 11 listed above, and the non-mobile terminal can be a server, a network attached storage (NAS), a personal computer (PC), a television (TV), a teller machine, or a self-service machine, etc., which are not limited in the embodiment of the present application.
[0166] The uplink transmission apparatus in the embodiments of the present application can be an apparatus with an operating system. The operating system can be an Android operating system, an ios operating system, or other possible operating systems, and the embodiments of the present application do not make specific limitations.
[0167] The uplink transmission apparatus provided in the embodiments of the present application can implement each process achieved by the method embodiments and achieve the same technical effects. To avoid repetition, the processes will not be described here again.
[0168] Optionally, as shown in Figure 4 The embodiments of the present application also provide a communication device 400, which includes a processor 401, a memory 402, programs or instructions stored in the memory 402 and executable on the processor 401. For example, when the communication device 400 is a terminal device, the programs or instructions are executed by the processor 401 to implement each process of the uplink transmission method embodiments and achieve the same technical effects.
[0169] Figure 5 To implement the hardware structure of a terminal device according to an embodiment of the present application.
[0170] The terminal device 100 includes but is not limited to a radio frequency unit 101, a network module 102, an audio output unit 103, an input unit 104, a sensor 105, a display unit 106, a user input unit 107, an interface unit 108, a memory 109, and a processor 110, etc.
[0171] Those skilled in the art can understand that the terminal device 100 can also include a power supply (such as a battery) for supplying power to each component. The power supply can be logically connected to the processor 110 through a power management system, so as to realize functions such as management of charging, discharging, and power consumption management through the power management system. Figure 5 The terminal device structure shown in the above figure does not constitute a limitation on the terminal device. The terminal device can include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements, which will not be described here again.
[0172] It should be understood that in the embodiments of the present application, the input unit 104 can include a graphics processing unit (GPU) 1041 and a microphone 1042. The graphics processing unit 1041 processes image data of a still picture or a video obtained by an image capture device (such as a camera) in a video capture mode or an image capture mode. The display unit 106 can include a display panel 1061, which can be configured in the form of a liquid crystal display, an organic light-emitting diode, etc. The user input unit 107 includes a touch panel 1071 and other input devices 1072. The touch panel 1071 is also called a touch screen. The touch panel 1071 can include two parts of a touch detection device and a touch controller. The other input devices 1072 can include, but are not limited to, a physical keyboard, function keys (such as volume control keys, on-off keys, etc.), a trackball, a mouse, a joystick, and the like, which will not be described here.
[0173] In the embodiments of the present application, the radio frequency unit 101 receives downlink data from a network side device and processes the data by the processor 110. In addition, the radio frequency unit 101 sends uplink data to the network side device. Generally, the radio frequency unit 101 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, etc.
[0174] The memory 109 can be used to store software programs or instructions and various data. The memory 109 can mainly include a storage program or instruction area and a storage data area, wherein the storage program or instruction area can store an operating system, application programs or instructions required by at least one function (such as a sound playing function, an image playing function, etc.), etc. In addition, the memory 109 can include a high-speed random access memory, and can also include a non-volatile memory, which can be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM) or a flash memory. For example, at least one magnetic disk storage device, a flash memory device, or other non-volatile solid-state memory device.
[0175] The processor 110 can include one or more processing units; optionally, the processor 110 can integrate an application processor and a modem processor, wherein the application processor mainly processes an operating system, a user interface and application programs or instructions, etc., and the modem processor mainly processes wireless communication, such as a baseband processor. It can be understood that the above-mentioned modem processor can also not be integrated into the processor 110.
[0176] The processor 110 is configured to, in the case that the terminal device enables the uplink transmission skipping function, if the time domain resource of the at least one uplink shared channel overlaps with the time domain resource of the at least one uplink control channel, generate a MAC PDU according to any one of the following processing manners at the MAC layer: generating the MAC PDU if the MAC layer knows that the time domain resource of the uplink shared channel overlaps with the time domain resource of the uplink control channel; and generating the MAC PDU according to multiplexing information notified by the physical layer to the MAC layer, wherein the at least one uplink control channel carries at least one uplink control information.
[0177] Optionally, in the embodiment of the present application, the multiplexing information is used to indicate that the time domain resource of the at least one uplink shared channel overlaps with the time domain resource of the at least one uplink control channel.
[0178] Optionally, in the embodiment of the present application, the at least one uplink shared channel is located on one or more carriers.
[0179] Optionally, in the embodiment of the present application, the multiplexing information is used to indicate at least one of the following:
[0180] The target uplink control channel in the at least one uplink control channel, which is used to carry the uplink control information of the at least one uplink control channel;
[0181] The target uplink shared channel in the at least one uplink shared channel, which is used to carry the uplink control information of the at least one uplink control channel;
[0182] The at least one uplink shared channel;
[0183] The at least one uplink control channel.
[0184] Optionally, in the embodiment of the present application, the processor 110 is further configured to, in the case that the at least one uplink control channel includes a plurality of uplink control channels, determine the target uplink control channel from the plurality of uplink control channels according to a first multiplexing rule at the physical layer or the MAC layer; or, in the case that the at least one uplink shared channel includes a plurality of uplink shared channels, determine the target uplink shared channel from the plurality of uplink shared channels according to a second multiplexing rule at the physical layer or the MAC layer; or, in the case that the at least one uplink shared channel includes a plurality of uplink shared channels and the time domain resource of the target uplink control channel overlaps with the time domain resource of the plurality of uplink shared channels, determine the target uplink shared channel from the plurality of uplink shared channels according to the second multiplexing rule and the target uplink control channel at the physical layer or the MAC layer.
[0185] Optionally, in the embodiment of the present application, the multiplexing information is informed by the physical layer to the MAC layer when the terminal device receives the scheduling grant.
[0186] Optionally, in the embodiment of the present application, when the scheduling grant is a downlink scheduling grant, the downlink scheduling grant is DCI scheduling the uplink control channel; when the scheduling grant is an uplink scheduling grant, the uplink scheduling grant is DCI scheduling the uplink shared channel, or the uplink shared channel scheduled by the uplink scheduling grant overlaps with the uplink shared channel used to carry the uplink control information in a time unit.
[0187] Optionally, in the embodiment of the present application, the processor 110 is further configured to: disable the uplink transmission skipping function on a target carrier; wherein the target carrier is a carrier on which an uplink shared channel overlapping in time domain with the uplink control channel is located.
[0188] Optionally, in the embodiment of the present application, the processor 110 is further configured to: if the MAC layer learns that the time domain resource of the at least one uplink shared channel overlaps with the time domain resource of the at least one uplink control channel, determine a target uplink shared channel from the at least one uplink shared channel according to a second multiplexing rule at the MAC layer.
[0189] Optionally, in the embodiment of the present application, the radio frequency unit 101 is configured to: transmit the MAC PDU on a target uplink shared channel; wherein 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 among the at least one uplink shared channel.
[0190] The terminal device provided in the embodiments of the present application, in the case that the terminal device enables the uplink transmission skipping function, if the time domain resource of at least one uplink shared channel overlaps with the time domain resource of at least one uplink control channel, the MAC layer can generate a MAC PDU in the following any one processing mode: mode 1, if the MAC layer learns that the time domain resource of the uplink shared channel overlaps with the time domain resource of the uplink control channel, a MAC PDU is generated; mode 2, a MAC PDU is generated according to multiplexing information informed by the physical layer to the MAC layer; wherein the at least one uplink control channel carries at least one uplink control information. In this way, in the case of conflict between the uplink shared channel and the uplink control channel, the MAC layer can generate a MAC PDU, so that the terminal device can support multiplexing the uplink control information carried on the uplink control channel to the uplink shared channel that enables the uplink transmission skipping function even in the case of no data transmission, and further the network side device can accurately determine the resource multiplexed by the uplink control channel without two kinds of blind detection, thereby reducing the complexity of blind detection on the network side and improving the system communication efficiency.
[0191] The embodiments of the present application also provide a readable storage medium, the readable storage medium stores a program or instructions, the program or instructions are executed by a processor to realize the processes of the above uplink transmission method embodiments, and the same technical effects can be achieved. To avoid repetition, details are not described here.
[0192] The processor is the processor in the terminal in the above embodiments. The readable storage medium includes a computer readable storage medium, such as a computer readable memory (Read-Only Memory, ROM), a random access memory (Random Access Memory, RAM), a magnetic disk or an optical disk, etc.
[0193] The embodiments of the present application further provide a chip, which includes a processor and a communication interface, the communication interface is coupled with the processor, and the processor is configured to run a network side device program or instructions to realize the processes of the above uplink transmission method embodiments, and the same technical effects can be achieved. To avoid repetition, details are not described here.
[0194] The embodiments of the present application further provide a program product stored in a non-volatile storage medium, the program product is configured to be executed by at least one processor to realize the processes of the uplink transmission method embodiments, and the same technical effects can be achieved. To avoid repetition, details are not described here.
[0195] It should be understood that the chip mentioned in the embodiments of the present application can also be referred to as a system chip, a system chip, a chip system or a system on chip, etc.
[0196] It should be noted that, as used in this application, the terms "comprises", "comprising", or any other variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but can also include other elements not expressly listed or inherent to such process, method, article, or apparatus. An element proceeded by "comprises... a" does not, without more constraints, exclude the presence of additional identical elements in the process, method, article, or apparatus that comprises the element. Furthermore, it should be noted that the methods and apparatuses of the present application are not limited by the order of the steps or the sequence for performing the steps, as some steps can occur simultaneously, be performed in different orders, or be performed concurrently, unless expressly by the context required otherwise. Also, features described with respect to certain examples can be combined in other examples.
[0197] Those skilled in the art can clearly understand that the above-mentioned embodiment method can be realized by means of software and necessary general hardware platform, of course, it can also be realized by hardware, but in many cases, the former is a better embodiment. Based on such understanding, the technical solutions of the present application can be embodied in the form of a software product, which is stored in a storage medium (such as a ROM / RAM, a magnetic disk, or an optical disc) and includes a plurality of instructions for causing a terminal (which can be a mobile phone, a computer, a server, an air conditioner, or a network device) to execute the methods described in the various embodiments of the present application.
[0198] The embodiments of the present application are described above with reference to the accompanying drawings, but the present application is not limited to the above-described specific embodiments, and the above-described specific embodiments are merely illustrative, not restrictive. Those skilled in the art can make many forms under the inspiration of the present application without departing from the scope of the present application and the scope of protection of the claims.
Claims
1. An uplink transmission method, applied to a terminal device, characterized in that, The method includes: When the uplink transmission skip function is enabled in the terminal device, 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, a MAC PDU is generated at the MAC layer according to the multiplexing information notified to the MAC layer by the physical layer. The at least one uplink control channel carries at least one uplink control information. The multiplexing information is used to indicate 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 reuse information is also used to indicate at least one of the following: Among the at least one uplink control channel, the target uplink control channel is used to carry the uplink control information of the at least one uplink control channel; In the at least one uplink shared channel, the target uplink shared channel is used to carry uplink control information of the at least one uplink control channel; Wherein, the at least one uplink shared channel is located on multiple carriers; The method further includes: In the case where the at least one uplink control channel includes multiple uplink control channels, the target uplink control channel is determined from the multiple uplink control channels at the physical layer or MAC layer according to a first multiplexing rule; or, In the case where the at least one uplink shared channel includes multiple uplink shared channels, the target uplink shared channel is determined from the multiple uplink shared channels at the physical layer or MAC layer according to the second multiplexing rule; or, In the case where 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 target uplink shared channel is determined from the multiple uplink shared channels at the physical layer or MAC layer according to the second multiplexing rule and the target uplink control channel. The first reuse rule includes at least one of the following: The target uplink control channel is a hybrid automatic repeat request-acknowledge (HACK-ACK) uplink control channel; The target uplink control channel is the uplink control channel of the scheduling request (SR). The second reuse rule includes at least one of the following: The target uplink shared channel is the uplink shared channel with the earliest start time among multiple uplink shared channels on the carrier with the smallest number; The target uplink shared channel is the uplink shared channel of the carrier with the smallest number in the dynamic uplink scheduling among multiple carriers.
2. The method according to claim 1, characterized in that, The method further includes: If the terminal device enables the uplink transmission skip function, and if 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, and 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, then a MAC PDU is generated at the MAC layer.
3. The method according to claim 1, characterized in that, The reuse information is provided by the physical layer to the MAC layer when the terminal device receives a scheduling authorization.
4. The method according to claim 3, characterized in that, When the scheduling authority is a downlink scheduling authority, the downlink scheduling authority is the DCI that schedules the uplink control channel; When the scheduling authorization is an uplink scheduling authorization, the uplink scheduling authorization is to schedule the DCI of the uplink shared channel, or the uplink shared channel scheduled by the uplink scheduling authorization overlaps with the at least one uplink control channel in one time unit.
5. The method according to claim 4, characterized in that, The method further includes: On the target carrier, the uplink transmission skip function is disabled; The target carrier is the carrier of the uplink shared channel that overlaps with the time domain resources of the uplink control channel.
6. The method according to claim 1 or 2, characterized in that, 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 method further includes: At the MAC layer, the target uplink shared channel is determined from the at least one uplink shared channel according to the second multiplexing rule.
7. The method according to any one of claims 1 to 6, characterized in that, The generation of the MAC PDU includes: Generate a MAC PDU and transmit the MAC PDU on the target uplink shared channel; The target uplink shared channel is: an uplink shared channel among the at least one uplink shared channels used to carry uplink control information of the at least one uplink control channel.
8. An uplink transmission device, characterized in that, Applied to a terminal device, the device includes: The execution module is configured to generate a MAC PDU at the MAC layer based on the multiplexing information notified to the MAC layer by the physical layer 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 when the uplink transmission skip function is enabled by the terminal device. The at least one uplink control channel carries at least one uplink control information. The multiplexing information is used to indicate 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 reuse information is also used to indicate at least one of the following: Among the at least one uplink control channel, the target uplink control channel is used to carry the uplink control information of the at least one uplink control channel; In the at least one uplink shared channel, the target uplink shared channel is used to carry uplink control information of the at least one uplink control channel; Wherein, the at least one uplink shared channel is located on multiple carriers; The execution module is further configured to: In the case where the at least one uplink control channel includes multiple uplink control channels, the target uplink control channel is determined from the multiple uplink control channels at the physical layer or MAC layer according to a first multiplexing rule; or, In the case where the at least one uplink shared channel includes multiple uplink shared channels, the target uplink shared channel is determined from the multiple uplink shared channels at the physical layer or MAC layer according to the second multiplexing rule; or, In the case where 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 target uplink shared channel is determined from the multiple uplink shared channels at the physical layer or MAC layer according to the second multiplexing rule and the target uplink control channel. The first reuse rule includes at least one of the following: The target uplink control channel is a HACK-ACK uplink control channel; The target uplink control channel is the uplink control channel of SR; The second reuse rule includes at least one of the following: The target uplink shared channel is the uplink shared channel with the earliest start time among multiple uplink shared channels on the carrier with the smallest number; The target uplink shared channel is the uplink shared channel of the carrier with the smallest number in the dynamic uplink scheduling among multiple carriers.
9. The apparatus according to claim 8, characterized in that, The execution module is further configured to: when the terminal device enables the uplink transmission skip function, if 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, and 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, then generate a MAC PDU at the MAC layer.
10. The apparatus according to claim 8, characterized in that, The reuse information is provided by the physical layer to the MAC layer when the terminal device receives a scheduling authorization.
11. The apparatus according to claim 10, characterized in that, When the scheduling authority is a downlink scheduling authority, the downlink scheduling authority is the DCI that schedules the uplink control channel; When the scheduling authorization is an uplink scheduling authorization, the uplink scheduling authorization is to schedule the DCI of the uplink shared channel, or the uplink shared channel scheduled by the uplink scheduling authorization overlaps with the at least one uplink control channel in one time unit.
12. The apparatus according to claim 11, characterized in that, The execution module is further configured to: disable the uplink transmission skip function on the target carrier; The target carrier is the carrier of the uplink shared channel that overlaps with the time domain resources of the uplink control channel.
13. The apparatus according to claim 8 or 9, characterized in that, The execution module is further configured to: 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, determine the target uplink shared channel from the at least one uplink shared channel in the MAC layer according to the second multiplexing rule.
14. The apparatus according to any one of claims 9 to 13, characterized in that, The device further includes: The transmission module is used to transmit the MAC PDU on the target uplink shared channel; The target uplink shared channel is: an uplink shared channel among the at least one uplink shared channels used to carry uplink control information of the at least one uplink control channel.
15. A terminal device, characterized in that, It includes a processor, a memory, and a program or instructions stored in the memory and executable on the processor, wherein the program or instructions, when executed by the processor, implement the steps of the uplink transmission method as described in any one of claims 1 to 7.
16. A readable storage medium, characterized in that, The readable storage medium stores a program or instructions that, when executed by a processor, implement the steps of the uplink transmission method as described in any one of claims 1 to 7.