CN113965997A - Uplink transmission method, device and equipment - Google Patents

Uplink transmission method, device and equipment Download PDF

Info

Publication number
CN113965997A
CN113965997A CN202010701845.9A CN202010701845A CN113965997A CN 113965997 A CN113965997 A CN 113965997A CN 202010701845 A CN202010701845 A CN 202010701845A CN 113965997 A CN113965997 A CN 113965997A
Authority
CN
China
Prior art keywords
uplink
uplink control
uplink shared
shared channel
control channel
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202010701845.9A
Other languages
Chinese (zh)
Inventor
陈晓航
潘学明
李娜
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Vivo Mobile Communication Co Ltd
Original Assignee
Vivo Mobile Communication Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Vivo Mobile Communication Co Ltd filed Critical Vivo Mobile Communication Co Ltd
Priority to CN202010701845.9A priority Critical patent/CN113965997A/en
Priority to PCT/CN2021/107230 priority patent/WO2022017342A1/en
Publication of CN113965997A publication Critical patent/CN113965997A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W72/00Local resource management
    • H04W72/20Control channels or signalling for resource management
    • H04W72/21Control channels or signalling for resource management in the uplink direction of a wireless link, i.e. towards the network
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W28/00Network traffic management; Network resource management
    • H04W28/02Traffic management, e.g. flow control or congestion control
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W72/00Local resource management
    • H04W72/04Wireless resource allocation
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W72/00Local resource management
    • H04W72/04Wireless resource allocation
    • H04W72/044Wireless resource allocation based on the type of the allocated resource
    • H04W72/0446Resources in time domain, e.g. slots or frames
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W72/00Local resource management
    • H04W72/12Wireless traffic scheduling
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W72/00Local resource management
    • H04W72/50Allocation or scheduling criteria for wireless resources
    • H04W72/54Allocation or scheduling criteria for wireless resources based on quality criteria
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W72/00Local resource management
    • H04W72/50Allocation or scheduling criteria for wireless resources
    • H04W72/54Allocation or scheduling criteria for wireless resources based on quality criteria
    • H04W72/541Allocation or scheduling criteria for wireless resources based on quality criteria using the level of interference

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Quality & Reliability (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

The application discloses an uplink transmission method, device and equipment, which belong to the technical field of communication and aim to realize that a MAC layer can generate PDU (protocol data unit) based on whether UCI (uplink control information) needs to be multiplexed or not. The method comprises the following steps: under the condition that the terminal equipment enables an uplink transmission skip function, if the time domain resource of at least one uplink shared channel is overlapped with the time domain resource of at least one uplink control channel, generating the MAC PDU according to any one of the following processing modes at the MAC layer: if the MAC layer learns that the time domain resources of the uplink shared channel are overlapped with the time domain resources of the uplink control channel, generating MAC PDU; generating MAC PDU according to the multiplexing information notified to the MAC layer by the physical layer; wherein, at least one uplink control channel carries at least one uplink control information.

Description

Uplink transmission method, device and equipment
Technical Field
The present application belongs to the field of communications technologies, and in particular, to an uplink transmission method, apparatus, and device.
Background
When an uplink shared channel (e.g., a Physical Uplink Shared Channel (PUSCH)) of a terminal device enables an uplink transmission skip (UL skip) function and there is no data to be transmitted in a data memory of the terminal device, even if a base station schedules a user for data transmission, the UL skip function allows the user to ignore the scheduling of the base station and not perform uplink transmission.
In the related art, in a case where the UL blanking function is enabled in the uplink shared channel of the terminal device, if there is a resource conflict between a time domain resource of an uplink control channel (e.g., a Physical Uplink Control Channel (PUCCH)) and a time domain resource of a dynamically scheduled uplink shared channel, since the PUSCH may have no data to transmit, the MAC layer cannot generate a PDU based on whether there is data, depending on whether there is UCI to multiplex the PDU.
Disclosure of Invention
An object of the embodiments of the present application is to provide an uplink transmission method, apparatus, and device, so as to enable a MAC layer to generate a PDU based on whether there is UCI to be multiplexed.
In a first aspect, an uplink transmission method is provided, which is applied to a terminal device, and the method includes: under the condition that the terminal equipment enables an uplink transmission skip function, if the time domain resource of at least one uplink shared channel is overlapped with the time domain resource of at least one uplink control channel, generating the MAC PDU according to any one of the following processing modes at the MAC layer: if the MAC layer learns that the time domain resources of the uplink shared channel are overlapped with the time domain resources of the uplink control channel, generating MAC PDU; generating MAC PDU according to the multiplexing information notified to the MAC layer by the physical layer; wherein, at least one uplink control channel carries at least one uplink control information.
In a second aspect, an uplink transmission apparatus is provided, where the apparatus includes: an execution module, configured to, if the terminal device enables an uplink transmission skip 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, generate, at an MAC layer, a MAC PDU according to any one of the following processing manners: if the MAC layer learns that the time domain resources of the uplink shared channel are overlapped with the time domain resources of the uplink control channel, generating MAC PDU; generating MAC PDU according to the multiplexing information notified to the MAC layer by the physical layer; wherein, at least one uplink control channel carries at least one uplink control information.
In a third aspect, a terminal device is provided, which comprises a processor, a memory and a program or instructions stored on the memory and executable on the processor, which when executed by the processor implements the steps of the method according to the first aspect.
In a fourth aspect, a readable storage medium is provided, on which a program or instructions are stored, which when executed by a processor, implement the steps of the method according to the first aspect.
In a fifth aspect, a chip is provided, where the chip includes a processor and a communication interface, where the communication interface is coupled to the processor, and the processor is configured to execute a network-side device program or instruction to implement the method according to the first aspect.
In a sixth aspect, a program product stored on a non-volatile storage medium, the program product configured to be executed by at least one processor to implement the method of the first aspect described above is provided.
In this embodiment of the present application, in a case that the terminal device enables an uplink transmission skip 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 may be generated in a MAC layer according to any one of the following processing manners: 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, an MAC PDU is generated; mode 2, according to the multiplexing information notified to the MAC layer by the physical layer, generating MAC PDU; wherein, at least one uplink control channel carries at least one uplink control information. Therefore, under the condition that the uplink shared channel conflicts with the uplink control channel, the MAC PDU can be generated through the MAC layer, so that even if the terminal equipment has no data transmission, the terminal equipment can also support that the uplink control information carried on the uplink control channel can be multiplexed onto the uplink shared channel which enables the uplink transmission skipping function, and further, the network side equipment can accurately determine the multiplexing resources of the uplink control channel without two assumed blind detections, the complexity of the network side blind detection is reduced, and the system communication energy efficiency is improved.
Drawings
Fig. 1 is a system architecture diagram of a communication system according to an embodiment of the present application;
fig. 2 is a flowchart of a method for uplink transmission according to an embodiment of the present application;
fig. 3 is a schematic structural diagram of an uplink transmission apparatus according to an embodiment of the present application;
fig. 4 is a schematic structural diagram of a communication device according to an embodiment of the present application;
fig. 5 is a schematic structural diagram of a terminal device according to an embodiment of the present application.
Detailed Description
The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some, but not all, embodiments of the present application. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
Technical terms related to technical solutions provided by embodiments of the present application will be explained below:
1. time domain overlapping of transmission resources (or called time domain collision)
Compared with the existing mobile communication system, the future 5G mobile communication system needs to adapt to more diversified scenes and service requirements. The main scenarios of 5G include enhanced mobile broadband (eMBB), massive machine type communications (mtc), and ultra-reliable and low latency communications (URLLC), which have requirements for high reliability, low latency, large bandwidth, wide coverage, and the like on a mobile communication system. The UE may support different services, for example, the UE may support both a URLLC service with low latency and high reliability and an eMBB service with large capacity and high rate. New Radio (NR) systems may have overlapping transmission resource time domains due to different channels having different starting symbols and lengths. In general, in order to maintain uplink single carrier characteristics, when a plurality of overlapping uplink transmission resources are transmitted in one slot, the single carrier characteristics of the UE are destroyed, and a difference in transmission power causes deterioration of channel estimation performance. For this case, usually considered as a conflict, a corresponding conflict solution needs to be designed, and some information needs to be merged or discarded.
2. Uplink channel
The uplink control channel includes: a Physical Uplink Control Channel (PUCCH).
The uplink shared channel includes: a Physical Uplink Shared Channel (PUSCH).
3. Physical layer defined UCI multiplexing on PUSCH
Uplink control information (e.g., UCI) is transmitted on an uplink control channel (e.g., PUCCH). If the terminal device is transmitting data on an uplink shared channel (e.g., PUSCH), in principle, PUCCH and PUSCH may be transmitted simultaneously, i.e., UCI is retained in PUCCH. However, this increases the Cubic Metric (Cubic Metric); furthermore, if the requirements for out-of-band transmission are to be met at higher transmit power and the PUSCH and PUCCH are transmitted simultaneously with a large separation in the frequency domain (PUCCH is typically transmitted at both ends of the band), this can present challenges for Radio Frequency (RF) implementations. Therefore, in general, if there is time coincidence between the PUCCH resource requiring UCI transmission and the PUSCH resource, and the base station guarantees that the condition of UCI multiplexing processing time is satisfied when scheduling the PUSCH, UCI and data are multiplexed on the PUSCH, avoiding simultaneous transmission of PUCCH.
4. PUCCH and PUSCH collision handling
In NR R15, simultaneous transmission of PUCCH and PUSCH is not supported within one PUCCH group (PUCCH group) regardless of whether the PUCCH and PUSCH are in the same serving cell or different serving cells. When the PUCCH and PUSCH time domain resources overlap (including partial time domain resource overlap and full time domain resource overlap), the UE may discard or merge according to the corresponding rule under the condition that a certain time requirement is met.
For example, if a PUCCH carrying a Scheduling Request (SR) overlaps with a PUSCH not carrying an uplink shared channel (UL-SCH), the UE discards the PUSCH and transmits the SR PUCCH. Or the UE multiplexes Uplink Control Information (UCI) (except for SR) carried on the PUCCH into the PUSCH and transmits the uplink control information. For example, if PUCCH1 carrying hybrid automatic repeat request acknowledgement (HARQ-ACK) or PUSCH 2 carrying Channel State Information (CSI) overlaps with PUCCH1 carrying PUSCH 2, the UE multiplexes HARQ-ACK/CSI carried on PUCCH1 into PUSCH 2 for transmission.
Specifically, the UE firstly processes time domain resource overlapping (if any) between multiple PUCCHs, and the processing result is one or multiple PUCCHs with non-time domain resource overlapping, and then the UE processes time domain resource overlapping between the PUCCH and a PUSCH, if the PUCCH is only overlapped with one PUSCH, the UE multiplexes UCI (excluding SR) in the PUSCH, and if the PUCCH is only overlapped with multiple PUSCHs, the UE selects one PUSCH for multiplexing according to a multiplexing rule in the related art, where the first multiplexing rule (i.e., the sequence of PUSCHs for instructing the UE to select the multiplexed UCI) is as follows:
rule 1: PUSCH carrying Aperiodic channel state information (A-CSI).
Rule 2: PUSCH with the earliest starting slot.
Rule 3: dynamically scheduled PUSCH > configures a granted PUSCH or a semi-persistent (semi-persistent) PUSCH.
Rule 4: PUSCH with small serving cell index (index) > PUSCH with large serving cell index.
Rule 5: PUSCH early in transmission symbol > PUSCH late in transmission symbol.
Illustratively, the physical layer priority of the PUCCH is determined by the priority of the UCI carried thereby. For example, the priority of the SR is configured by Radio Resource Control (RRC), the periodic CSI and semi-persistent CSI (SP-CSI) priorities are predefined as low priority, and the priority of the HARQ-ACK is indicated by its corresponding DCI or determined according to the configuration of semi-Persistent Scheduling (SPs). The transmission priority of the PUSCH is indicated by scheduling Downlink Control Information (DCI) corresponding to the PUSCH, or the priority of the PUSCH for which the grant is configured by RRC.
When the time domain resources of the PUCCH and the PUCCH are overlapped or the time domain resources of the PUCCH and the PUSCH are overlapped, the UE processes the transmission with the same priority (the rule is same as R15) firstly and then processes the transmission with different priorities, and when the different priorities are processed, the UE cancels (or is called to discard) the transmission of the uplink resource with low priority and transmits the uplink resource with high priority under the condition of meeting a certain time requirement.
5. MAC layer defined uplink transmission skip function
The MAC layer defines the procedure for the terminal to carry out an uplink transmission skip (ulskiping) in the protocol TS 38.321. The MAC entity will not generate a MAC PDU for the HARQ entity if the following conditions are met:
condition 1: the MAC entity is configured with a parameter skippelinktxdynamic and the value of this parameter is set to true (true), and the MAC locates to the HARQ entity indicated in the uplink grant (UL grant).
Condition 2: there is no aperiodic CSI requested for this PUSCH transmission in the UL grant as specified in TS 38.212.
Condition 3: a MAC PDU includes zero MAC SDUs.
Condition 4: the MAC PDU contains only a periodic Buffer Status Report (BSR) and no data available for any Logical Channel Group (LCG), or the MAC PDU contains only a padding BSR.
In the related art, in a case where the uplink shared channel of the terminal device enables the UL blanking function, if there is a resource conflict between a time domain resource of an uplink control channel (e.g., PUCCH) and a time domain resource of a dynamically scheduled uplink shared channel, since the PUSCH may not have data to transmit, the MAC layer cannot generate a PDU based on whether there is data or not to be multiplexed according to whether there is UCI.
Specifically, in the case that the time domain resource of the uplink control channel (e.g., PUCCH) and the time domain resource of the dynamically scheduled uplink shared channel have resource conflict, the terminal device may choose not to generate PUSCH to transmit the uplink control information (e.g., UCI) on the PUCCH, or may choose to generate PUSCH to multiplex the uplink control information on the PUSCH for transmission.
Therefore, the resource multiplexed by the UCI cannot be determined at the network side, 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 on each carrier based on two assumptions of whether uplink control information is multiplexed on the PUSCH of the carrier, which increases the complexity of blind detection on the network side and causes a large burden on the network side.
In order to solve the above problem, embodiments of the present application provide an uplink transmission method, apparatus, and device, where if a terminal device enables an uplink transmission skip 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 may be generated in an MAC layer according to any one of the following processing manners: 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, an MAC PDU is generated; mode 2, according to the multiplexing information notified to the MAC layer by the physical layer, generating MAC PDU; wherein, at least one uplink control channel carries at least one uplink control information. Therefore, under the condition that the uplink shared channel conflicts with the uplink control channel, the MAC PDU can be generated through the MAC layer, so that even if the terminal equipment has no data transmission, the terminal equipment can also support that the uplink control information carried on the uplink control channel can be multiplexed onto the uplink shared channel which enables the uplink transmission skipping function, and further, the network side equipment can accurately determine the multiplexing resources of the uplink control channel without two assumed blind detections, the complexity of the network side blind detection is reduced, and the system communication energy efficiency is improved.
6. Other terms
The terms first, second and the like in the description and in the claims of the present application are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It should be understood that the data so used are interchangeable under appropriate circumstances such that embodiments of the application can be practiced in sequences other than those illustrated or described herein, and the terms "first" and "second" used herein generally do not denote any order, nor do they denote any order, for example, the first object may be one or more. In addition, "and/or" in the specification and the claims means at least one of connected objects, and a character "/" generally means that a preceding and succeeding related objects are in an "or" relationship.
It is noted that the techniques described in the embodiments of the present application are not limited to Long Term Evolution (LTE)/LTE Evolution (LTE-Advanced) systems, but may also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency-Division Multiple Access (SC-FDMA), and other systems. The terms "system" and "network" in the embodiments of the present application are often used interchangeably, and the described techniques can be used for both the above-mentioned systems and radio technologies, as well as for other systems and radio technologies. However, the following description describes a New Radio (NR) system for purposes of example, and NR terminology is used in much of the description below, although the techniques may also be applied to applications other than NR system applications, such as 6 th generation (6 th generation)thGeneration, 6G) communication system.
Fig. 1 shows a block diagram of a wireless communication system to which embodiments of the present application are applicable. The wireless communication system includes a terminal 11 and a network-side device 12. Wherein, the terminal 11 may also be called as a terminal Device or a User Equipment (UE), the terminal 11 may be a Mobile phone, a Tablet Personal Computer (Tablet Personal Computer), a Laptop Computer (Laptop Computer) or a notebook Computer, a Personal Digital Assistant (PDA), a palmtop Computer, a netbook, a super-Mobile Personal Computer (UMPC), a Mobile Internet Device (MID), a Wearable Device (Wearable Device) or a vehicle-mounted Device (VUE), a pedestrian terminal (PUE), and other terminal side devices, the Wearable Device includes: bracelets, earphones, glasses and the like. It should be noted that the embodiment of the present application does not limit the specific type of the terminal 11. The network-side device 12 may be a Base Station or a core network, where the Base Station may be referred to as a node B, an evolved node B, an access Point, a Base Transceiver Station (BTS), a radio Base Station, a radio Transceiver, a Basic Service Set (BSS), an Extended Service Set (ESS), a node B, an evolved node B (eNB), a home node B, a WLAN access Point, a WiFi node, a Transmit Receiving Point (TRP), or some other suitable terminology in the field, as long as the same technical effect is achieved, the Base Station is not limited to a specific technical vocabulary, and it should be noted that, in the embodiment of the present application, only the Base Station in the NR system is taken as an example, but a specific type of the Base Station is not limited.
The uplink transmission method provided by the embodiment of the present application is described in detail below with reference to the accompanying drawings through specific embodiments and application scenarios thereof.
In other words, the uplink transmission method may be executed by software or hardware installed in the terminal device. As shown in fig. 2, a data transmission method provided in an embodiment of the present application may include the following step 201.
Step 201: and under the condition that the terminal equipment enables an uplink transmission skip function, if the time domain resource of at least one uplink shared channel is overlapped with the time domain resource of at least one uplink control channel, generating the MAC PDU at the MAC layer according to any one of the following processing modes.
The first processing mode is as follows: and under the condition that the terminal equipment enables an uplink transmission skipping function, if the time domain resource of at least one uplink shared channel is overlapped with the time domain resource of at least one uplink control channel, and if the MAC layer learns that the time domain resource of at least one uplink shared channel is overlapped with the time domain resource of at least one uplink control channel, generating the MAC PDU at the MAC layer.
The second processing mode is as follows: in the MAC Layer (or Layer 2, Layer 2), a MAC PDU is generated based on the multiplexing information notified to the MAC Layer by the physical Layer (or Layer 1, Layer 1).
In this embodiment, the at least one uplink control channel carries at least one uplink control information.
In this embodiment, the at least one uplink shared channel is located on one or more carriers.
It should be noted that the overlapping of the time domain resource of the at least one uplink shared channel and the time domain resource of the at least one uplink control channel refers to: there is a collision in time between the at least one uplink shared channel and the at least one uplink control channel. Illustratively, the time domain resource may be one or more slots/sub-slots/symbols/subframes.
In the embodiment of the present application, the terminal device enabling the uplink transmission skip function may be considered as the terminal device enabling the uplink transmission skip function of the uplink shared channel.
In the embodiment of the present application, the following relationship exists between the MAC PDU and uplink control information (e.g., UCI): 1) if the target uplink shared channel is overlapped with the uplink control channel resource, the MAC PDU and the UCI are multiplexed on the target uplink shared channel for transmission; or, 2) if the target uplink shared channel is not overlapped 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.
Optionally, in this embodiment of the present application, the multiplexing information may 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.
Optionally, in this embodiment of the present application, the multiplexing information may also be used to indicate a target uplink shared channel. Among the at least one uplink shared channel, an uplink shared channel for carrying uplink control information of the at least one uplink control channel is provided. Further, at this time, the MAC layer may not need the physical layer to notify that there is a collision between the current uplink control channel and the 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 an embodiment of the present application, the multiplexing information is used to indicate at least one of the following:
a target uplink control channel for carrying uplink control information of the at least one uplink control channel, among the at least one uplink control channel;
a target uplink shared channel for carrying uplink control information of the at least one uplink control channel, among the at least one uplink shared channel;
the at least one uplink shared channel;
the at least one uplink control channel.
It should be noted that, in this embodiment of the present application, one or more target uplink shared channels may be used, and one or more target uplink control channels may be used, which is not limited in this embodiment of the present application.
Optionally, in this embodiment of the present application, the multiplexing information may be notified to the MAC layer by the physical layer when the terminal device receives a scheduling grant (a downlink scheduling grant or an uplink scheduling grant).
Further optionally, in this embodiment of the application, when the scheduling grant is a downlink scheduling grant, the downlink scheduling grant is DCI for scheduling a part or all of the uplink control channels in the at least one uplink control channel. Illustratively, the downlink scheduling grant is a latest DCI for scheduling the one or more PUCCHs carrying the UCI.
Further optionally, in this embodiment of the application, when the scheduling grant is an uplink scheduling grant, the uplink scheduling grant is DCI for scheduling a part or all of the at least one uplink shared channel, or the uplink shared channel scheduled by the uplink scheduling grant and the at least one uplink control channel overlap in a time unit.
For example, in a case that the uplink scheduling grant schedules a DCI of a part of or all uplink shared channels in the at least one uplink shared channel, the uplink scheduling grant schedules a DCI of a PUSCH on a PCell.
For example, the time unit may be: subframe, slot, sub-slot, symbol, etc.
Further, when receiving the ending time slot or symbol of the DCI of the scheduling grant, the terminal device is notified to the MAC layer by the physical layer; or, the terminal device notifies the MAC layer by the physical layer X time units after receiving the ending slot or symbol of the DCI of the scheduling grant. Wherein X is predefined or network configuration or related to UE capability, and further, X may be a processing time of a downlink control channel (PDCCH).
Optionally, in this embodiment of the present application, the process of generating the MAC PDU by the terminal device in step 201 may further include the following step 201 a:
step 201 a: and generating the MAC PDU and transmitting the MAC PDU on the target uplink shared channel.
Wherein, the target uplink shared channel is: and the at least one uplink shared channel is used for carrying uplink control information of the at least one uplink control channel.
Illustratively, a MAC padding pdu (MAC padding pdu) is generated when the terminal device has no data. The terminal device has no data, and specifically, the terminal device may have no data in a Logical channel group (Logical channel group) corresponding to the PUSCH.
Illustratively, when the MAC layer generates a MAC PDU for the at least one PUSCH according to the multiplexing information, the MAC generates a MAC padding PDU when there is no UL-SCH on any one PUSCH.
Illustratively, when the MAC layer generates a MAC PDU according to the multiplexing information, the MAC layer generates a MAC padding PDU if there is no UL-SCH or no data on the target PUSCH.
Further optionally, in this embodiment, the uplink transmission method provided in this embodiment may further include the following step a 1:
step A1: and on the target carrier, forbidding to enable the uplink transmission skipping function.
Wherein, the target carrier is: and the carrier where the uplink shared channel is located is overlapped with the time domain resource of the uplink control channel.
Illustratively, the UE disables the enabled (disable) PUSCH UL blanking function when at least one PUCCH overlaps the PUSCH in time. Furthermore, on the carrier where the PUSCH with the conflict with the PUCCH is located, the PUSCH UL clipping function is forbidden to be enabled.
Optionally, in this embodiment of the application, for the processing mode 2, the uplink transmission method provided in this embodiment of the application may further include the following step B1, step B2, or step B3:
step B1: and under the condition that the at least one uplink control channel comprises a plurality of uplink control channels, determining the target uplink control channel from the plurality of uplink control channels according to a first multiplexing rule in a physical layer or an MAC layer.
Step B2: and under the condition that the at least one uplink shared channel comprises a plurality of uplink shared channels, determining the target uplink shared channel from the plurality of uplink shared channels according to a second multiplexing rule in a physical layer or an MAC layer.
Step B3: and when 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, determining the target uplink shared channel from the plurality of uplink shared channels according to a second multiplexing rule and the target uplink control channel in a physical layer or an MAC layer.
For example, the first multiplexing rule may be a PUCCH multiplexing rule of UCI on PUCCH.
In one example, the multiplexing rule of HARQ-ACK on PUCCH and the multiplexing rule of Scheduling Request (SR) on PUCCH are as shown in table 1 below:
TABLE 1
Figure BDA0002593098560000131
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: transmitting SR and CSI on CSI PUCCH [1og ]2(K+1)]bits is preset before the periodic/semi-static CSI information bit, and indicates the corresponding SR state (active or inactive) in the SR resource Id in an ascending manner.
For HARQ-ACK/SR/CSI: if HARQ-ACK is feedback on PDSCH without PDCCH scheduling, HARQ-ACK or HARQ-ACK + SR will be multiplexed on CSI PUCCH transmission.
If HARQ-ACK is feedback for PDSCH scheduled with PDCCH, HARQ-ACK or HARQ-ACK + SR + CSI will be multiplexed on one PUCCH for transmission. The PUCCH is determined in a plurality of resource sets configured by RRC based on HARQ-ACK, CSI and SR bit number.
For example, in step B2, in a case that the at least one uplink shared channel includes multiple uplink shared channels and the multiple uplink shared channels are located on a single carrier, the target uplink shared channel is determined based on at least one of the following:
an uplink shared channel with the earliest initial time domain position in the plurality of uplink shared channels;
triggering an uplink shared channel reported by aperiodic CSI from the plurality of uplink shared channels;
the physical layer informs the MAC layer to multiplex the uplink control information on the target uplink shared channel;
and the physical layer informs the MAC layer whether each uplink shared channel in the plurality of uplink shared channels multiplexes the uplink control information.
For example, taking the uplink shared channel as the PUSCH, when there are multiple PUSCHs and a single carrier, the PHY layer needs to determine the target PUSCH for carrying the UCI according to the second multiplexing rule. The specific multiplexing mode comprises the following steps: multiplexing mode 1: the target PUSCH is the PUSCH with the earliest starting time in a plurality of PUSCHs on the carrier wave; multiplexing mode 2: the target PUSCH is a PUSCH which triggers Aperiodic CSI reporting (A-CSI) in a plurality of PUSCHs on the carrier wave.
For example, in step B2, in a case that the at least one uplink shared channel includes multiple uplink shared channels and the multiple uplink shared channels are located on multiple carriers, the target uplink shared channel satisfies at least one of the following conditions:
an uplink shared channel with the earliest initial time domain position in a plurality of uplink shared channels on a first carrier;
triggering an uplink shared channel reported by aperiodic CSI from a plurality of uplink shared channels on a first carrier;
an uplink shared channel on a second carrier;
an uplink control channel on a third carrier.
Wherein the first carrier is a carrier whose number satisfies a predetermined condition (e.g., the number is the smallest) among the plurality of carriers; the second carrier is a carrier which is scheduled in an uplink manner among the plurality of carriers and has a serial number meeting the predetermined condition; the third carrier is a carrier which triggers aperiodic CSI reporting and has a number meeting the predetermined condition among the plurality of carriers.
For example, taking the uplink shared channel as the PUSCH, when there are multiple PUSCH, the PHY layer needs to determine the target PUSCH for carrying the UCI and the carrier where the target PUSCH is located according to the second multiplexing rule. Specifically, the multiplexing method includes: multiplexing mode 1: the target PUSCH is the PUSCH with the earliest starting time in a plurality of PUSCHs on the carrier wave with the smallest number; multiplexing mode 2: the target PUSCH is a PUSCH which triggers Aperiodic CSI reporting (A-CSI) in a plurality of PUSCHs on a carrier wave with the smallest number; multiplexing mode 3: the target PUSCH is a PUSCH of a carrier which is positioned in dynamic UL scheduling and has the smallest number in a plurality of carriers; and a multiplexing mode 4: the target PUSCH is a PUSCH of a carrier which triggers the aperiodic CSI reporting and has the smallest number, among the plurality of carriers.
Illustratively, the MAC layer or the physical layer determines 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 conflicts with the at least one PUSCH, the MAC layer may determine the target PUSCH for carrying the UCI according to the multiplexing rule of the target PUCCH and the UCI on PUSCH.
Optionally, in this embodiment, for the processing mode 1, if the MAC layer knows 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 in this embodiment may further include the following step C1:
step C1: and determining a target uplink shared channel from the at least one uplink shared channel at the MAC layer according to a second multiplexing rule.
For example, taking the uplink shared channel as the PUSCH, when the MAC layer determines a target PUCCH carrying the one or more UCIs according to a second multiplexing rule (i.e., a PUCCH multiplexing rule of UCI on PUSCH), if the target PUCCH collides with at least one PUSCH, the MAC layer determines the target PUSCH carrying the UCI according to the target PUCCH and the second multiplexing rule.
For example, taking the uplink shared channel as the PUSCH, when at least one PUSCH on one or more carriers is located on multiple carriers, the MAC layer determines, according to the second multiplexing rule, a target PUSCH for carrying the UCI and a carrier on which the target PUSCH is located.
Illustratively, for example, when the uplink shared channel is PUSCH and the uplink control channel is PUCCH, the MAC layer determines a target PUCCH carrying the one or more UCI according to a first multiplexing rule (i.e., PUCCH multiplexing rule of UCI on PUCCH).
Illustratively, if the MAC layer knows that one or more PUCCHs carrying UCI are colliding 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 will be explained below with three examples, where the uplink shared channel is a PUSCH and the uplink control channel is a PUCCH.
Example 1:
in the case that the UE enables the PUSCH UL blanking 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, and schedules one or more PUCCHs carrying UCI, the UE may determine transmission of UCI according to the following steps:
step 11: decoding the DL grant and/or the UL grant.
Step 12: and if a plurality of PUCCHs exist, the PHY layer determines the resources of a target PUCCH carrying the UCI according to the multiplexing rule of the UCI on PUCCH.
Step 13: and if the target PUCCH resources conflict with at least one PUSCH on the one or more carriers, the PHY layer determines the resources of the target PUSCH for bearing the UCI in the at least one PUSCH according to the UCI on PUSCH multiplexing priority.
Step 14: the PHY layer informs the MAC layer of UCI multiplexing information (i.e., the content in step 13), and the MAC layer generates a MAC PDU according to the UCI multiplexing information.
Step 15: if there is no UL-SCH, the MAC layer generates padding PDUs.
Step 16: and mapping UCI on the target PUSCH.
And step 17: and mapping (padding) data on the target PUSCH.
It should be noted that, in this embodiment, the execution sequence between the step 16 and the step 17 is not limited, and the step 16 may be executed first and then the step 17 is executed (i.e., the UCI mapping is performed first and then the data mapping is performed), or the step 17 may be executed first and then the step 16 is executed (i.e., the data mapping is performed first and then the UCI mapping is performed).
Example 2:
in the case that the UE enables the PUSCH UL blanking 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 transmission of UCI according to the following steps:
step 21: decoding the DL grant and/or the UL grant.
Step 22: and if a plurality of PUCCHs exist, the PHY layer determines the resources of a target PUCCH carrying the UCI according to the multiplexing rule of the UCI on PUCCH.
Step 23: the PHY layer informs the MAC layer of UCI multiplexing information (i.e., the content in step 12), and the MAC layer generates a MAC PDU according to the UCI multiplexing information.
Step 24: and if the target PUCCH resource conflicts with at least one PUSCH on one or more carriers, the MAC layer determines the resource of the target PUSCH for carrying UCI in the at least one PUSCH according to the UCI on PUSCH multiplexing rule.
Step 25: the MAC generates a PDU for the target PUSCH, and if the UL-SCH does not exist, a padding PDU is generated.
Step 26: and mapping UCI on the target PUSCH.
Step 27: and mapping (padding) data on the target PUSCH.
It should be noted that, in this embodiment, the execution sequence between the step 26 and the step 27 is not limited, and the step 26 may be executed first and then the step 27 is executed (i.e., the UCI mapping is performed first and then the data mapping is performed), or the step 27 may be executed first and then the step 26 is executed (i.e., the data mapping is performed first and then the UCI mapping is performed).
Example 3:
in case that the UE enables a PUSCH UL blanking 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 transmission of UCI according to the following steps:
step 31: decoding the DL grant and/or the UL grant.
Step 32: the PHY layer informs the MAC layer after step 31 that the one or more PUCCHs carrying the UCI collide with at least one PUSCH on the one or more carriers.
Step 33: and the MAC generates a MAC PDU for the first PUSCH (set) with conflict according to the UCI multiplexing information.
Step 34: if there is no UL-SCH, the MAC generates a padding PDU.
Step 35: and if a plurality of PUCCHs exist, the PHY layer determines the resources of a target PUCCH carrying the UCI according to the multiplexing rule of the UCI on PUCCH.
Step 36: and if the target PUCCH resources conflict with at least one PUSCH on one or more carriers, the PHY layer determines the resources of the target PUSCH for carrying UCI in the at least one PUSCH according to a UCI on PUSCH multiplexing rule.
Step 37: if the target PUSCH has the UL-SCH, mapping of UCI and data (data) is carried out on the target PUSCH.
Step 38: otherwise, mapping UCI and padding data on the target PUSCH.
Step 39: and if the target PUSCH does not belong to the first PUSCH (set), mapping (padding) data on the first PUSCH (set).
Step 40: if one PUSCH in the first PUSCH (set) has no data, mapping of padding data is carried out.
It should be noted that, in this embodiment, the execution order of the UCI mapping and the data mapping is not limited, and the UCI mapping may be performed first and then the data mapping is performed, or the data mapping may be performed first and then the UCI mapping is performed.
In the uplink transmission method provided in the embodiment of the present application, when the terminal device enables the uplink transmission skip 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 PDU may be generated in the MAC layer according to any one of the following processing manners: 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, an MAC PDU is generated; mode 2, according to the multiplexing information notified to the MAC layer by the physical layer, generating MAC PDU; wherein, at least one uplink control channel carries at least one uplink control information. Therefore, under the condition that the uplink shared channel conflicts with the uplink control channel, the MAC PDU can be generated through the MAC layer, so that even if the terminal equipment has no data transmission, the terminal equipment can also support that the uplink control information carried on the uplink control channel can be multiplexed onto the uplink shared channel which enables the uplink transmission skipping function, and further, the network side equipment can accurately determine the multiplexing resources of the uplink control channel without two assumed blind detections, the complexity of the network side blind detection is reduced, and the system communication energy efficiency is improved.
It should be noted that, in the uplink transmission method provided in the embodiment of the present application, the execution main body may be an uplink transmission device, or a control module in the uplink transmission device for executing the uplink transmission method. In the embodiment of the present application, an uplink transmission apparatus is taken as an example to execute an uplink transmission method, and an apparatus of the uplink transmission method provided in the embodiment of the present application is described.
As shown in fig. 3, the uplink transmission device 300 provided in this embodiment of the present application may include: an execution module 301, wherein:
an executing module 301, configured to, when the terminal device enables an uplink transmission skip 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, generate, at a MAC layer, a MAC PDU according to any one of the following processing manners: if the MAC layer learns that the time domain resources of the uplink shared channel are overlapped with the time domain resources of the uplink control channel, generating MAC PDU; generating MAC PDU according to the multiplexing information notified to the MAC layer by the physical layer; wherein, at least one uplink control channel carries at least one uplink control information.
Optionally, in this embodiment of the present application, the multiplexing information is used to indicate: the time domain resource of the at least one uplink shared channel is overlapped with the time domain resource of the at least one uplink control channel.
Optionally, in this embodiment of the present application, the at least one uplink shared channel is located on one or more carriers.
Optionally, in an embodiment of the present application, the multiplexing information is used to indicate at least one of the following: a target uplink control channel for carrying uplink control information of the at least one uplink control channel, among the at least one uplink control channel; a target uplink shared channel for carrying uplink control information of the at least one uplink control channel, among the at least one uplink shared channel; the at least one uplink shared channel; the at least one uplink control channel.
Optionally, in this embodiment of the application, the executing module 301 is further configured to: determining the target uplink control channel from the plurality of uplink control channels according to a first multiplexing rule in a physical layer or an MAC layer under the condition that the at least one uplink control channel comprises the plurality of uplink control channels; or, when the at least one uplink shared channel includes a plurality of uplink shared channels, determining, at a physical layer or an MAC layer, the target uplink shared channel from the plurality of uplink shared channels according to a second multiplexing rule; or, when 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 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 a second multiplexing rule and the target uplink control channel.
Optionally, in this embodiment of the present application, the multiplexing information is notified to the MAC layer by the physical layer when the terminal device receives the scheduling grant.
Optionally, in this embodiment of the present application, when the scheduling grant is a downlink scheduling grant, the downlink scheduling grant is DCI for scheduling the uplink control channel; when the scheduling grant is an uplink scheduling grant, the uplink scheduling grant is DCI for scheduling the uplink shared channel, or the uplink shared channel scheduled by the uplink scheduling grant and the at least one uplink control channel overlap in one time unit.
Optionally, in this embodiment of the application, the executing module 301 is further configured to: forbidding to enable the uplink transmission skipping function on the target carrier; wherein, the target carrier is: and the carrier where the uplink shared channel is located is overlapped with the time domain resource of the uplink control channel.
Optionally, in this embodiment of the application, the executing module 301 is further configured to: and if the MAC layer learns that the time domain resource of the at least one uplink shared channel is overlapped 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.
Optionally, in this embodiment of the present application, as shown in fig. 3, the apparatus 300 further includes: a transmission module 302, wherein: a transmission module 302, configured to transmit the MAC PDU on a target uplink shared channel; wherein, the target uplink shared channel is: and the at least one uplink shared channel is used for carrying uplink control information of the at least one uplink control channel.
In the uplink transmission apparatus provided in the embodiment of the present application, when the terminal device enables the uplink transmission skip 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 PDU may be generated in the MAC layer according to any one of the following processing manners: 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, an MAC PDU is generated; mode 2, according to the multiplexing information notified to the MAC layer by the physical layer, generating MAC PDU; wherein, at least one uplink control channel carries at least one uplink control information. Therefore, under the condition that the uplink shared channel conflicts with the uplink control channel, the MAC PDU can be generated through the MAC layer, so that even if the terminal equipment has no data transmission, the terminal equipment can also support that the uplink control information carried on the uplink control channel can be multiplexed onto the uplink shared channel which enables the uplink transmission skipping function, and further, the network side equipment can accurately determine the multiplexing resources of the uplink control channel without two assumed blind detections, the complexity of the network side blind detection is reduced, and the system communication energy efficiency is improved.
The uplink transmission device in the embodiment of the present application may be a device, or may be a component, an integrated circuit, or a chip in a terminal. The device can be a mobile terminal or a non-mobile terminal. By way of example, the mobile terminal may include, but is not limited to, the above-listed type of terminal 11, and the non-mobile terminal may be a server, a Network Attached Storage (NAS), a Personal Computer (PC), a Television (TV), a teller machine, a kiosk, or the like, and the embodiments of the present application are not limited in particular.
The uplink transmission device in the embodiment of the present application may be a device having an operating system. The operating system may be an Android (Android) operating system, an ios operating system, or other possible operating systems, and embodiments of the present application are not limited specifically.
The uplink transmission device provided in the embodiment of the present application can implement each process implemented by the above method embodiment, and achieve the same technical effect, and for avoiding repetition, the details are not repeated here.
Optionally, as shown in fig. 4, an embodiment of the present application further provides a communication device 400, which includes a processor 401, a memory 402, and a program or an instruction stored in the memory 402 and executable on the processor 401, for example, when the communication device 400 is a terminal device, the program or the instruction is executed by the processor 401 to implement the processes of the uplink transmission method embodiment, and the same technical effect can be achieved.
Fig. 5 is a schematic diagram of a hardware structure of a terminal device for implementing the embodiment of the present application.
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.
Those skilled in the art will appreciate that the terminal device 100 may further include a power supply (e.g., a battery) for supplying power to various components, and the power supply may be logically connected to the processor 110 through a power management system, so as to implement functions of managing charging, discharging, and power consumption through the power management system. The terminal device structure shown in fig. 5 does not constitute a limitation of the terminal device, and the terminal device may include more or less components than those shown, or combine some components, or arrange different components, and thus, the description is omitted here.
It should be understood that, in the embodiment of the present application, the input Unit 104 may include a Graphics Processing Unit (GPU) 1041 and a microphone 1042, and the Graphics Processing Unit 1041 processes image data of a still picture or a video obtained by an image capturing device (such as a camera) in a video capturing mode or an image capturing mode. The display unit 106 may include a display panel 1061, and the display panel 1061 may be configured in the form of a liquid crystal display, an organic light emitting diode, or the like. The user input unit 107 includes a touch panel 1071 and other input devices 1072. The touch panel 1071 is also referred to as a touch screen. The touch panel 1071 may include two parts of a touch detection device and a touch controller. Other input devices 1072 may include, but are not limited to, a physical keyboard, function keys (e.g., volume control keys, switch keys, etc.), a trackball, a mouse, and a joystick, which are not described in detail herein.
In the embodiment of the present application, the radio frequency unit 101 receives downlink data from a network side device and then processes the downlink data to the processor 110; in addition, the uplink data is sent to the network side equipment. Typically, 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, and the like.
The memory 109 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 storage program or instruction area may store an operating system, an application program or instruction (such as a sound playing function, an image playing function, etc.) required for at least one function, and the like. In addition, the Memory 109 may include a high-speed random access Memory, and may further include a nonvolatile Memory, wherein the nonvolatile Memory may 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. Such as at least one magnetic disk storage device, flash memory device, or other non-volatile solid state storage device.
Processor 110 may include one or more processing units; alternatively, the processor 110 may integrate an application processor, which primarily handles operating systems, user interfaces, and applications or instructions, etc., and a modem processor, which primarily handles wireless communications, such as a baseband processor. It will be appreciated that the modem processor described above may not be integrated into the processor 110.
Wherein, the processor 110 is configured to, 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 when the terminal device enables the uplink transmission skip function, 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 resources of the uplink shared channel are overlapped with the time domain resources of the uplink control channel, generating MAC PDU; generating MAC PDU according to the multiplexing information notified to the MAC layer by the physical layer; wherein, at least one uplink control channel carries at least one uplink control information.
Optionally, in this embodiment of the present application, the multiplexing information is used to indicate: the time domain resource of the at least one uplink shared channel is overlapped with the time domain resource of the at least one uplink control channel.
Optionally, in this embodiment of the present application, the at least one uplink shared channel is located on one or more carriers.
Optionally, in an embodiment of the present application, the multiplexing information is used to indicate at least one of the following:
a target uplink control channel for carrying uplink control information of the at least one uplink control channel, among the at least one uplink control channel;
a target uplink shared channel for carrying uplink control information of the at least one uplink control channel, among the at least one uplink shared channel;
the at least one uplink shared channel;
the at least one uplink control channel.
Optionally, in this embodiment of the application, the processor 110 is further configured to: determining the target uplink control channel from the plurality of uplink control channels according to a first multiplexing rule in a physical layer or an MAC layer under the condition that the at least one uplink control channel comprises the plurality of uplink control channels; or, when the at least one uplink shared channel includes a plurality of uplink shared channels, determining, at a physical layer or an MAC layer, the target uplink shared channel from the plurality of uplink shared channels according to a second multiplexing rule; or, when 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 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 a second multiplexing rule and the target uplink control channel.
Optionally, in this embodiment of the present application, the multiplexing information is notified to the MAC layer by the physical layer when the terminal device receives the scheduling grant.
Optionally, in this embodiment of the present application, when the scheduling grant is a downlink scheduling grant, the downlink scheduling grant is DCI for scheduling the uplink control channel; when the scheduling grant is an uplink scheduling grant, the uplink scheduling grant is DCI for scheduling the uplink shared channel, or the uplink shared channel scheduled by the uplink scheduling grant and the uplink shared channel for carrying the uplink control information overlap each other in a time unit.
Optionally, in this embodiment of the application, the processor 110 is further configured to: forbidding to enable the uplink transmission skipping function on the target carrier; wherein, the target carrier is: and the carrier where the uplink shared channel is located is overlapped with the time domain resource of the uplink control channel.
Optionally, in this embodiment of the application, the processor 110 is further configured to: and if the MAC layer learns that the time domain resource of the at least one uplink shared channel is overlapped 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.
Optionally, in this 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: and the at least one uplink shared channel is used for carrying uplink control information of the at least one uplink control channel.
In the terminal device provided in the embodiment of the present application, when the terminal device enables an uplink transmission skip 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 may be generated in a MAC layer according to any one of the following processing manners: 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, an MAC PDU is generated; mode 2, according to the multiplexing information notified to the MAC layer by the physical layer, generating MAC PDU; wherein, at least one uplink control channel carries at least one uplink control information. Therefore, under the condition that the uplink shared channel conflicts with the uplink control channel, the MAC PDU can be generated through the MAC layer, so that even if the terminal equipment has no data transmission, the terminal equipment can also support that the uplink control information carried on the uplink control channel can be multiplexed onto the uplink shared channel which enables the uplink transmission skipping function, and further, the network side equipment can accurately determine the multiplexing resources of the uplink control channel without two assumed blind detections, the complexity of the network side blind detection is reduced, and the system communication energy efficiency is improved.
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 the instruction is executed by a processor, the program or the instruction implements each process of the uplink transmission method embodiment, and can achieve the same technical effect, and in order to avoid repetition, details are not repeated here.
Wherein, the processor is the processor in the terminal described in the above embodiment. The readable storage medium includes a computer readable storage medium, such as a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and so on.
The embodiment of the present application further provides a chip, where the chip includes a processor and a communication interface, the communication interface is coupled to the processor, and the processor is configured to run a network-side device program or an instruction, to implement each process of the uplink transmission method embodiment, and can achieve the same technical effect, and details are not repeated here to avoid repetition.
The present application further provides a program product, which is stored in a non-volatile storage medium and configured to be executed by at least one processor to implement the processes of the uplink transmission method embodiment, and the same technical effects can be achieved, and details are not repeated herein to avoid repetition.
It should be understood that the chips mentioned in the embodiments of the present application may also be referred to as a system-on-chip, a system-on-chip or a system-on-chip, etc.
It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element. Further, it should be noted that the scope of the methods and apparatus of the embodiments of the present application is not limited to performing the functions in the order illustrated or discussed, but may include performing the functions in a substantially simultaneous manner or in a reverse order based on the functions involved, e.g., the methods described may be performed in an order different than that described, and various steps may be added, omitted, or combined. In addition, features described with reference to certain examples may be combined in other examples.
Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner. Based on such understanding, the technical solutions of the present application may be embodied in the form of a software product, which is stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk) and includes instructions for enabling a terminal (such as a mobile phone, a computer, a server, an air conditioner, or a network device) to execute the method according to the embodiments of the present application.
While the present embodiments have been described with reference to the accompanying drawings, it is to be understood that the invention is not limited to the precise embodiments described above, which are meant to be illustrative and not restrictive, and that various changes may be made therein by those skilled in the art without departing from the spirit and scope of the invention as defined by the appended claims.

Claims (22)

1. An uplink transmission method is applied to a terminal device, and is characterized in that the method comprises the following steps:
under the condition that the terminal equipment enables an uplink transmission skip function, if the time domain resource of at least one uplink shared channel is overlapped with the time domain resource of at least one uplink control channel, generating a protocol data unit (MAC PDU) on an MAC layer according to any one of the following processing modes:
if the MAC layer learns that the time domain resources of the uplink shared channel are overlapped with the time domain resources of the uplink control channel, generating MAC PDU;
generating MAC PDU according to the multiplexing information notified to the MAC layer by the physical layer;
wherein, at least one uplink control information is carried on the at least one uplink control channel.
2. The method of claim 1, wherein the multiplexing information is used to indicate: the time domain resource of the at least one uplink shared channel is overlapped with the time domain resource of the at least one uplink control channel.
3. The method of claim 1, wherein the at least one uplink shared channel is located on one or more carriers.
4. The method of claim 1, wherein the multiplexing information is used to indicate at least one of:
in the at least one uplink control channel, a target uplink control channel for carrying uplink control information of the at least one uplink control channel;
in the at least one uplink shared channel, a target uplink shared channel for carrying uplink control information of the at least one uplink control channel;
the at least one uplink shared channel;
the at least one uplink control channel.
5. The method of claim 4, further comprising:
under the condition that the at least one uplink control channel comprises a plurality of uplink control channels, determining the target uplink control channel from the plurality of uplink control channels according to a first multiplexing rule in a physical layer or an MAC layer;
or,
determining the target uplink shared channel from the plurality of uplink shared channels according to a second multiplexing rule on a physical layer or an MAC layer under the condition that the at least one uplink shared channel comprises the plurality of uplink shared channels;
or,
and under the condition that the at least one uplink shared channel comprises a plurality of uplink shared channels, and the time domain resources of the target uplink control channel are overlapped with the time domain resources of the plurality of uplink shared channels, determining the target uplink shared channel from the plurality of uplink shared channels according to a second multiplexing rule and the target uplink control channel on a physical layer or an MAC layer.
6. The method of claim 1, wherein the multiplexing information is signaled by a physical layer to a MAC layer by the terminal device upon receiving a scheduling grant.
7. The method of claim 6,
when the scheduling grant is a downlink scheduling grant, the downlink scheduling grant is DCI for scheduling the uplink control channel;
and if the scheduling grant is an uplink scheduling grant, the uplink scheduling grant is DCI for 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.
8. The method of claim 7, further comprising:
forbidding enabling the uplink transmission skipping function on a target carrier;
wherein the target carrier is: and the carrier where the uplink shared channel is located is overlapped with the time domain resource of the uplink control channel.
9. The method of claim 1, wherein if the MAC layer knows 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 method further comprises:
and determining a target uplink shared channel from the at least one uplink shared channel at the MAC layer according to a second multiplexing rule.
10. The method according to any of claims 1 to 9, wherein the generating the MAC PDU comprises:
generating MAC PDU and transmitting the MAC PDU on a target uplink shared channel;
wherein the target uplink shared channel is: and the at least one uplink shared channel is used for carrying uplink control information of the at least one uplink control channel.
11. An uplink transmission apparatus, comprising:
an execution module, configured to, if the terminal device enables an uplink transmission skip 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, generate, at an MAC layer, a protocol data unit MAC PDU according to any one of the following processing manners:
if the MAC layer learns that the time domain resources of the uplink shared channel are overlapped with the time domain resources of the uplink control channel, generating MAC PDU;
generating MAC PDU according to the multiplexing information notified to the MAC layer by the physical layer;
wherein, at least one uplink control information is carried on the at least one uplink control channel.
12. The apparatus of claim 11, wherein the multiplexing information is configured to indicate: the time domain resource of the at least one uplink shared channel is overlapped with the time domain resource of the at least one uplink control channel.
13. The apparatus of claim 11, wherein the at least one uplink shared channel is located on one or more carriers.
14. The apparatus of claim 11, wherein the multiplexing information is used to indicate at least one of:
in the at least one uplink control channel, a target uplink control channel for carrying uplink control information of the at least one uplink control channel;
in the at least one uplink shared channel, a target uplink shared channel for carrying uplink control information of the at least one uplink control channel;
the at least one uplink shared channel;
the at least one uplink control channel.
15. The apparatus of claim 14, wherein the execution module is further configured to:
under the condition that the at least one uplink control channel comprises a plurality of uplink control channels, determining the target uplink control channel from the plurality of uplink control channels according to a first multiplexing rule in a physical layer or an MAC layer;
or,
determining the target uplink shared channel from the plurality of uplink shared channels according to a second multiplexing rule on a physical layer or an MAC layer under the condition that the at least one uplink shared channel comprises the plurality of uplink shared channels;
or,
and under the condition that the at least one uplink shared channel comprises a plurality of uplink shared channels, and the time domain resources of the target uplink control channel are overlapped with the time domain resources of the plurality of uplink shared channels, determining the target uplink shared channel from the plurality of uplink shared channels according to a second multiplexing rule and the target uplink control channel on a physical layer or an MAC layer.
16. The apparatus of claim 11, wherein the multiplexing information is signaled by a physical layer to a MAC layer by the terminal device upon receiving a scheduling grant.
17. The apparatus of claim 16,
when the scheduling grant is a downlink scheduling grant, the downlink scheduling grant is DCI for scheduling the uplink control channel;
and if the scheduling grant is an uplink scheduling grant, the uplink scheduling grant is DCI for 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.
18. The apparatus of claim 17, wherein the execution module is further configured to: forbidding enabling the uplink transmission skipping function on a target carrier;
wherein the target carrier is: and the carrier where the uplink shared channel is located is overlapped with the time domain resource of the uplink control channel.
19. The apparatus of claim 11, wherein the execution module is further configured to: and if the MAC layer learns that the time domain resource of the at least one uplink shared channel is overlapped 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.
20. The apparatus of any one of claims 11 to 19, further comprising:
a transmission module, configured to transmit the MAC PDU on a target uplink shared channel;
wherein the target uplink shared channel is: and the at least one uplink shared channel is used for carrying uplink control information of the at least one uplink control channel.
21. A terminal device comprising a processor, a memory and a program or instructions stored on the memory and executable on the processor, the program or instructions when executed by the processor implementing the steps of the upstream transmission method according to any one of claims 1 to 10.
22. A readable storage medium, on which a program or instructions are stored, which when executed by a processor implement the steps of the upstream transmission method according to any one of claims 1 to 10.
CN202010701845.9A 2020-07-20 2020-07-20 Uplink transmission method, device and equipment Pending CN113965997A (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN202010701845.9A CN113965997A (en) 2020-07-20 2020-07-20 Uplink transmission method, device and equipment
PCT/CN2021/107230 WO2022017342A1 (en) 2020-07-20 2021-07-20 Uplink transmission method and apparatus, and device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202010701845.9A CN113965997A (en) 2020-07-20 2020-07-20 Uplink transmission method, device and equipment

Publications (1)

Publication Number Publication Date
CN113965997A true CN113965997A (en) 2022-01-21

Family

ID=79459566

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202010701845.9A Pending CN113965997A (en) 2020-07-20 2020-07-20 Uplink transmission method, device and equipment

Country Status (2)

Country Link
CN (1) CN113965997A (en)
WO (1) WO2022017342A1 (en)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109802813A (en) * 2017-11-17 2019-05-24 华为技术有限公司 Uplink control information transmission method and equipment
WO2020110244A1 (en) * 2018-11-28 2020-06-04 株式会社Nttドコモ User terminal and wireless communication method

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017170677A1 (en) * 2016-03-31 2017-10-05 株式会社Nttドコモ User terminal, wireless base station, and wireless communications method
CN111316736B (en) * 2017-09-07 2023-08-29 株式会社Ntt都科摩 User terminal and wireless communication method
CN110248383B (en) * 2019-06-28 2023-05-12 海能达通信股份有限公司 Uplink channel scheduling method and device, medium, base station and user terminal

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109802813A (en) * 2017-11-17 2019-05-24 华为技术有限公司 Uplink control information transmission method and equipment
WO2020110244A1 (en) * 2018-11-28 2020-06-04 株式会社Nttドコモ User terminal and wireless communication method

Non-Patent Citations (5)

* Cited by examiner, † Cited by third party
Title
ASUSTEK: "R2-2005551 "PDU generation for UL spatial multiplexing"", 3GPP TSG_RAN\\WG2_RL2, no. 2, 22 May 2020 (2020-05-22) *
HUAWEI, HISILICON: "Clarification on UCI multiplexing on PUSCH", 3GPP TSG RAN WG1 MEETING #100BIS-E R1-2002581, 11 April 2020 (2020-04-11), pages 2 - 5 *
HUAWEI, HISILICON: "Clarification on UCI multiplexing on PUSCH", 3GPP TSG RAN WG1 MEETING #101-E R1-2004614, 16 May 2020 (2020-05-16), pages 2 - 3 *
VIVO: "R2-2002780 "Discussion on the UL skipping"", 3GPP TSG_RAN\\WG2_RL2, no. 2, 10 April 2020 (2020-04-10) *
ZTE, SANECHIPS: "R2-2003594 "CR to 38.321 on UCI transmission in the case the overlapping PUSCH transmission is skipped"", 3GPP TSG_RAN\\WG2_RL2, no. 2, 10 April 2020 (2020-04-10) *

Also Published As

Publication number Publication date
WO2022017342A1 (en) 2022-01-27

Similar Documents

Publication Publication Date Title
CN113965301B (en) Method and device for processing physical uplink control channel resource overlapping
CN114374486A (en) HARQ-ACK transmission method, terminal and network side equipment
CN114521019A (en) Uplink control information transmission method and related equipment
US20230171751A1 (en) Collision processing method and apparatus
CN113939036A (en) Channel monitoring and transmission method, terminal and network side equipment
EP4221394A1 (en) Uplink channel transmission method and apparatus, and terminal
US20230354343A1 (en) Communication transmission method and apparatus and communication device
CN113890701A (en) Side link transmission method, transmission device and terminal
CN113965998A (en) Uplink transmission method, device and related equipment
CN113839728A (en) DCI detection method, DCI transmission method and related equipment
EP4369741A1 (en) Method and apparatus for processing overlapping pucch time domain resources
WO2022028604A1 (en) Uplink transmission method and apparatus, and terminal device
CN113938259B (en) HARQ-ACK feedback method and device
CN114745083B (en) Information transmission method, device, terminal and network equipment
CN115334676A (en) Multiplexing indication method, device, terminal and network side equipment for uplink transmission
CN115333690A (en) Information transmission method, device, terminal and network side equipment
CN114374955A (en) Transmission method, priority definition method, device and communication equipment
CN115175332A (en) Uplink channel transmission method, device, terminal and network side equipment
CN114285534A (en) Transmission information determining method, device and terminal
CN114337950A (en) Transmission processing method, device, terminal and readable storage medium
CN113890698A (en) Side link transmission method, transmission device and communication equipment
CN113965997A (en) Uplink transmission method, device and equipment
WO2024140634A1 (en) Transmission method, device and readable storage medium
CN115173907B (en) Codebook determining and receiving method and device, terminal and network side equipment
CN115052344A (en) Uplink transmission processing method and terminal

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination