WO2022028604A1 - Procédé et appareil de transmission de liaison montante, et dispositif terminal - Google Patents

Procédé et appareil de transmission de liaison montante, et dispositif terminal Download PDF

Info

Publication number
WO2022028604A1
WO2022028604A1 PCT/CN2021/111299 CN2021111299W WO2022028604A1 WO 2022028604 A1 WO2022028604 A1 WO 2022028604A1 CN 2021111299 W CN2021111299 W CN 2021111299W WO 2022028604 A1 WO2022028604 A1 WO 2022028604A1
Authority
WO
WIPO (PCT)
Prior art keywords
uplink
shared channel
channel
uplink shared
uplink control
Prior art date
Application number
PCT/CN2021/111299
Other languages
English (en)
Chinese (zh)
Inventor
陈晓航
潘学明
Original Assignee
维沃移动通信有限公司
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 维沃移动通信有限公司 filed Critical 维沃移动通信有限公司
Publication of WO2022028604A1 publication Critical patent/WO2022028604A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/21—Control channels or signalling for resource management in the uplink direction of a wireless link, i.e. towards the network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signaling, i.e. of overhead other than pilot signals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H04W72/044—Wireless resource allocation based on the type of the allocated resource
    • H04W72/0446—Resources in time domain, e.g. slots or frames

Definitions

  • the present application belongs to the field of communication technologies, and in particular relates to an uplink transmission method, apparatus and terminal equipment.
  • the terminal device When the uplink shared channel of the terminal device (for example, the Physical Uplink Shared Channel (PUSCH)) is a channel authorized by the configuration, and there is no data to be transmitted in the data memory of the terminal device, the terminal can also ignore the configuration authorization ( configured grant) PUSCH, no uplink transmission.
  • PUSCH Physical Uplink Shared Channel
  • the uplink shared channel of the terminal device eg, Physical Uplink Shared Channel (PUSCH)
  • the uplink control channel eg, Physical Uplink Control Channel (Physical Uplink Control Channel) , PUCCH
  • the medium access control (Medium Access Control, MAC) layer based on whether there is data to generate protocol data Unit (Protocol Data Unit, PDU), cannot generate PDU according to whether there is uplink control information (Uplink Control Information, UCI) to be multiplexed.
  • MAC Medium Access Control
  • PDU Protocol Data Unit
  • the purpose of the embodiments of the present application is to provide an uplink transmission method, apparatus, and terminal device, so that the MAC layer can generate PDUs based on whether there is UCI to be multiplexed.
  • an uplink transmission method is provided, applied to a terminal device, and the above method includes:
  • the medium access control MAC layer Under the situation that the time domain resource of the uplink shared channel of at least one configuration authorization overlaps with the time domain resource of at least one uplink control channel, then at the medium access control MAC layer, according to any one of the following processing methods, generate the MAC protocol data unit PDU:
  • the MAC layer learns that the time domain resources of the uplink shared channel overlap with the time domain resources of the uplink control channel, generate a MAC PDU;
  • a MAC PDU is generated
  • the at least one uplink control channel is used to carry uplink control information.
  • an uplink transmission apparatus includes: an execution module configured to, in the case that the time domain resources of at least one configuration authorized uplink shared channel overlap with the time domain resources of at least one uplink control channel, then The MAC protocol data unit PDU is generated at the media access control MAC layer according to any of the following processing methods:
  • the MAC layer learns that the time domain resources of the uplink shared channel overlap with the time domain resources of the uplink control channel, generate a MAC PDU;
  • a MAC PDU is generated
  • the at least one uplink control channel is used to carry uplink control information.
  • a terminal device in a third aspect, includes a processor, a memory, and a program or instruction stored in the memory and executable on the processor, the program or instruction being executed by the processor When executed, the steps of the method as described in the first aspect are implemented.
  • a readable storage medium is provided, and a program or an instruction is stored on the readable storage medium, and when the program or instruction is executed by a processor, the steps of the method according to the first aspect are implemented.
  • a fifth aspect provides a chip, the chip includes a processor and a communication interface, the communication interface is coupled to the processor, and the processor is configured to run a network-side device program or instruction, implementing the method described in the first aspect. method described.
  • a program product is provided, the program product is stored in a non-volatile storage medium, the program product is configured to be executed by at least one processor to implement the method of the first aspect above.
  • a terminal device configured to perform the method of the first aspect.
  • the medium access control MAC layer is processed according to any one of the following methods: Generate MAC protocol data unit PDU: Mode 1, if the MAC layer learns that the time domain resources of the uplink shared channel overlap with the time domain resources of the uplink control channel, then generate a MAC PDU; Mode 2, notify the MAC layer according to the physical layer.
  • the multiplexing information is generated, and a MAC PDU is generated; wherein, the at least one uplink control channel is used to carry the uplink control information, so that in the case of a conflict between the uplink shared channel and the uplink control channel, the MAC PDU can be generated by the MAC layer, so that the terminal Even in the absence of data transmission, the device can also support that the uplink control information carried on the uplink control channel can be multiplexed to the configured and authorized uplink shared channel, so that the network side device can accurately determine without blind detection.
  • the resources reused by the uplink control channel are used to reduce the complexity of blind detection on the network side and improve the energy efficiency of system communication.
  • FIG. 1 is a system architecture diagram of a communication system provided by an embodiment of the present application.
  • FIG. 2 is a method flowchart of an uplink transmission method provided by an embodiment of the present application
  • FIG. 3 is a schematic structural diagram of an uplink transmission apparatus provided by an embodiment of the present application.
  • FIG. 4 is a schematic structural diagram of a terminal device provided by an embodiment of the present application.
  • FIG. 5 is a schematic structural diagram of a terminal device provided by an embodiment of the present application.
  • the fifth generation (5th Generation , 5G) mobile communication system needs to adapt to more diverse scenarios and service requirements.
  • the main scenarios of 5G include Enhanced Mobile Broad Band (eMBB), Massive Machine Type Communications (mMTC) and Ultra-Reliable and Low Latency Communications (URLLC), These scenarios require high reliability, low latency, large bandwidth, and wide coverage for mobile communication systems.
  • eMBB Enhanced Mobile Broad Band
  • mMTC Massive Machine Type Communications
  • URLLC Ultra-Reliable and Low Latency Communications
  • the UE can support different services, for example, the UE supports not only the URLLC service with low latency and high reliability, but also the eMBB service with large capacity and high speed.
  • New Radio, NR New Radio, since different channels may have different start symbols and lengths, the time domain overlap of transmission resources may occur.
  • the single-carrier characteristic of the UE will be destroyed, and the difference of the transmit power will cause the deterioration of the channel estimation performance. This situation is usually regarded as a conflict, and a corresponding conflict resolution needs to be designed, merging or discarding some information.
  • the uplink control channel includes: physical uplink control channel (physical uplink control channel, PUCCH).
  • the uplink shared channel includes: physical uplink shared channel (PUSCH).
  • PUSCH physical uplink shared channel
  • the UCI defined by the physical layer is multiplexed on the PUSCH
  • Uplink control information (eg, UCI) is typically transmitted on an uplink control channel (eg, PUCCH).
  • PUCCH uplink control channel
  • the terminal device is transmitting data on the uplink shared channel (eg, PUSCH)
  • the PUCCH and the PUSCH can be sent at the same time, that is, the UCI is reserved in the PUCCH.
  • this will increase the Cubic Metric; in addition, if the requirement of out-of-band transmission is to be met at a higher transmit power, and the PUSCH and PUCCH are transmitted simultaneously, the interval in the frequency domain is large (PUCCH is generally in transmit at both ends of the frequency band), which will bring challenges to the implementation of radio frequency (RF).
  • RF radio frequency
  • the base station will ensure that the conditions of the UCI multiplexing processing time are met when scheduling the PUSCH, the UCI will be multiplexed with the data on the PUSCH. above, avoid sending PUCCH at the same time.
  • PUCCH group within a PUCCH group (PUCCH group), no matter whether PUCCH and PUSCH are in the same serving cell or in different serving cells, simultaneous transmission of PUCCH and PUSCH is not supported.
  • PUCCH and PUSCH time domain resources overlap including partial time domain resource overlap and all time domain resource overlap
  • the UE will discard or combine according to corresponding rules under the condition that certain time requirements are met.
  • the UE discards the PUSCH and transmits the SR PUCCH. Or the UE multiplexes the uplink control information (Uplink Control Information, UCI) (except SR) carried on the PUCCH into the PUSCH for transmission.
  • UCI Uplink Control Information
  • the UE will use the HARQ- ACK/CSI is multiplexed into PUSCH 2 for transmission.
  • the UE first processes the time-domain resource overlap between multiple PUCCHs (if any), and the result of the processing is one or more PUCCHs with non-time-domain resources overlapping, and then the UE processes the time-domain resources between the PUCCH and the PUSCH.
  • the UE Overlapping, if the PUCCH overlaps with only one PUSCH, the UE multiplexes the UCI (excluding the SR) in the PUSCH. If the PUCCH overlaps with multiple PUSCHs, the UE selects a PUSCH for multiplexing according to the multiplexing rules in the related art.
  • the first multiplexing rule that is, instructing the UE to select the PUSCH for multiplexing UCI is as follows:
  • Rule 1 PUSCH carrying aperiodic channel state information (Aperiodic CSI, A-CSI).
  • Rule 2 The PUSCH with the earliest start slot.
  • the physical layer priority of the PUCCH is determined by the priority of the UCI carried by the PUCCH.
  • the priority of SR is configured through Radio Resource Control (RRC)
  • the priority of periodic CSI and semi-persistent CSI (SP-CSI) is predefined as low priority
  • the priority of HARQ-ACK is determined by its corresponding DCI Indicated or determined according to the configuration of Semi-Persistent Scheduling (SPS).
  • the transmission priority of the PUSCH is indicated by the scheduling downlink control information (Downlink Control Information, DCI) corresponding to the PUSCH, or for the PUSCH with the configuration authorization, the priority is configured by the RRC.
  • DCI Downlink Control Information
  • the UE When the time domain resources of PUCCH and PUCCH overlap or the time domain resources of PUCCH and PUSCH overlap, the UE first processes transmissions with the same priority (the rules are the same as R15), and then processes transmissions with different priorities. When a certain time requirement is met, the UE cancels transmission (or is called discarding) the uplink resources of low priority and transmits uplink resources of high priority.
  • DG PUSCH Dynamically scheduled PUSCH
  • CG-PUSCH Configure authorized PUSCH
  • SP-CSI on PUSCH SP-CSI on PUSCH
  • the third priority PUSCH with a small carrier index (CC index)> PUSCH with a large CC index;
  • the MAC layer defines the process that the terminal implements uplink transmission skipping (UL skipping) in the protocol TS38.321.
  • the MAC entity will not generate a MAC PDU for the HARQ entity if the following conditions are met:
  • Condition 1 If the MAC entity is configured with the parameter skipUplinkTxDynamic and the value of this parameter is set to true (true), the MAC locates the HARQ entity indicated in the uplink grant (UL grant).
  • the MAC PDU includes zero MAC service data units (SDUs).
  • the MAC PDU contains only periodic Buffer Status Report (BSR) and no data is available for any Logical Channel Group (LCG), or the MAC PDU contains only padding BSR.
  • BSR Buffer Status Report
  • the MAC layer when the UL skipping function is enabled on the uplink shared channel of the terminal device, if there is a resource conflict between the time domain resources of the uplink control channel (eg, PUCCH) and the time domain resources of the dynamically scheduled uplink shared channel, Since the PUSCH may not have data to be sent, the MAC layer generates PDUs based on whether there is data or not, and cannot generate PDUs based on whether there is UCI to be multiplexed.
  • the uplink control channel eg, PUCCH
  • the terminal device may choose not to generate the PUSCH, so that the uplink control information (such as, UCI) is transmitted on the PUCCH, and the PUSCH can also be selected to be generated, so that the uplink control information is multiplexed and transmitted on the PUSCH.
  • the uplink control information such as, UCI
  • the resources multiplexed by the UCI cannot be determined on the network side, and the network side cannot receive the UCI accurately.
  • the network side equipment needs to perform blind detection on each carrier based on the two assumptions of whether the uplink control information is multiplexed in the PUSCH of the carrier, which will increase the complexity of the network side blind detection, which is a problem for the network side. cause a greater burden.
  • NR supports the transmission mode of uplink semi-static configuration grant (Configured Grant), which reduces the signaling interaction process and ensures low-latency requirements.
  • Configured Grant The resources for configuring the authorized transmission can be configured semi-statically through RRC signaling.
  • the UE can send data on the configured and authorized uplink channel (PUSCH).
  • type 1 There are two types of Configured grant transfers, type 1 and type 2.
  • type 1 configuration authorization transmission is that all transmission parameters are configured by RRC; when RRC is configured with type 1 configuration authorization, the configuration is activated.
  • type 2 configuration authorization transmission is that the RRC configures some parameters, such as the period, and at the same time, the type 2 configuration authorization configuration needs to be activated by the downlink activation signaling.
  • the terminal device may choose not to generate the PUSCH, so that the uplink control information (eg, UCI) is transmitted on the PUCCH, and the PUSCH can also be selected to be generated, so that the uplink control information is multiplexed and transmitted on the PUSCH.
  • the uplink control information eg, UCI
  • the resources multiplexed by the UCI cannot be determined on the network side, and the network side cannot receive the UCI accurately.
  • the network side equipment needs to perform blind detection on each carrier based on the two assumptions of whether the uplink control information is multiplexed in the PUSCH of the carrier, which will increase the complexity of the network side blind detection, which is a problem for the network side. cause a greater burden.
  • the embodiments of the present application provide an uplink transmission method, apparatus, and device. If the time domain resources of at least one configuration authorized uplink shared channel overlap with the time domain resources of at least one uplink control channel, the MAC layer The MAC PDU can be generated according to any one of the following processing methods: Mode 1, if the MAC layer learns that the time domain resources of the above-mentioned uplink shared channel overlap with the time domain resources of the above-mentioned uplink control channel, then the MAC PDU is generated; Mode 2, according to the physical layer The multiplexing information notified to the MAC layer generates a MAC PDU; wherein, the above-mentioned at least one uplink control channel carries uplink control information (one or more).
  • the MAC PDU can be generated through the MAC layer, so that the terminal device can support the uplink control information carried on the uplink control channel even in the absence of data transmission. It is multiplexed to the configured and authorized uplink shared channel, so that the network-side equipment can accurately determine the uplink control channel multiplexing resources without blind detection, which reduces the complexity of the network-side blind detection and improves the system communication energy efficiency.
  • first, second and the like in the description and claims of the present application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It is to be understood that the terms so used are interchangeable under appropriate circumstances so that the embodiments of the present application can be practiced in sequences other than those illustrated or described herein, and that "first”, “second” distinguishes Usually it is a class, and the number of objects is not limited.
  • the first object may be one or multiple.
  • “and/or” in the description and claims indicates at least one of the connected objects, and the character “/" generally indicates that the associated objects are in an "or” relationship.
  • LTE Long Term Evolution
  • LTE-Advanced LTE-Advanced
  • LTE-A Long Term Evolution
  • CDMA Code Division Multiple Access
  • TDMA Time Division Multiple Access
  • FDMA Frequency Division Multiple Access
  • OFDMA Orthogonal Frequency Division Multiple Access
  • SC-FDMA Single-carrier Frequency-Division Multiple Access
  • NR New Radio
  • FIG. 1 shows a block diagram of a wireless communication system to which the embodiments of the present application can be applied.
  • the wireless communication system includes a terminal 11 and a network-side device 12 .
  • the terminal 11 may also be called a terminal device or a user terminal (User Equipment, UE), and the terminal 11 may be a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (Laptop Computer) or a notebook computer, a personal digital computer Assistant (Personal Digital Assistant, PDA), handheld computer, netbook, ultra-mobile personal computer (ultra-mobile personal computer, UMPC), mobile Internet device (Mobile Internet Device, MID), wearable device (Wearable Device) or vehicle-mounted device (Vehicle user equipment, VUE), pedestrian terminal (pedestrian user equipment, PUE) and other terminal-side equipment, wearable devices include: bracelets, headphones, glasses, etc.
  • the network side device 12 may be a base station or a core network, wherein the base station may be referred to as a Node B, an evolved Node B, an access point, a Base Transceiver Station (BTS), a radio base station, a radio transceiver, a basic service Set (Basic Service Set, BSS), Extended Service Set (Extended Service Set, ESS), Node B, Evolved Node B (evolved Node B, eNB), Home Node B, Home Evolved Node B, Wireless Local Area Network (wireless local area network) area network, WLAN) access point, wireless fidelity (WiFi) node, Transmitting Receiving Point (TRP) or some other appropriate term in the field, as long as the same technical effect is achieved, all
  • the base station described above is not limited to specific technical vocabulary. It should be noted that, in the embodiments of the present application, only the base station in the NR system is used as an
  • An uplink transmission method provided by an embodiment of the present application can be applied to a terminal device, in other words, the uplink transmission method can be executed by software or hardware installed in the terminal device.
  • the data transmission method provided by this embodiment of the present application may include the following step 201 .
  • Step 201 When the time domain resource of at least one configuration authorized uplink shared channel overlaps with the time domain resource of at least one uplink control channel, the MAC layer generates a MAC PDU according to any one of the following processing methods.
  • the first processing method if the time domain resource of at least one configuration authorized uplink shared channel overlaps with the time domain resource of at least one uplink control channel, and if the MAC layer learns that the time domain resource of the at least one uplink shared channel is the same as the time domain resource of the at least one uplink shared channel If the time domain resources of the uplink control channel overlap, the MAC PDU is generated at the MAC layer.
  • the second processing method The MAC layer (or Layer 2, Layer 2) generates MAC PDUs according to the multiplexing information notified to the MAC layer by the physical layer (or Layer 1, Layer 1).
  • the above configuration authorization can be non-authorized configuration, authorization-free configuration, semi-static scheduling, configured grant, etc.
  • the at least one uplink control channel carries at least one uplink control information.
  • the at least one configured and authorized uplink shared channel is located on one or more carriers.
  • the overlapping of the time domain resources of the at least one uplink shared channel and the time domain resources of the at least one uplink control channel means that there is a time conflict between the at least one uplink shared channel and the at least one uplink control channel.
  • the above-mentioned time domain resource may be one or more time slots/subslots/symbols/subframes.
  • uplink control information such as UCI
  • the above multiplexing information is used to indicate that: the time domain resources of the at least one configuration-granted uplink shared channel overlap with the time domain resources of the at least one uplink control channel.
  • the above multiplexing information may also be used to indicate a target uplink shared channel, that is: in the above at least one configuration authorized uplink shared channel, the uplink control channel used to carry the above at least one uplink control channel is used. information on the uplink shared channel.
  • the MAC layer may not need the physical layer to notify that there is currently a conflict between the uplink control channel and the above-mentioned shared channel, and the MAC layer only needs to directly generate the MAC PDU according to the multiplexing information notified by the physical layer.
  • the foregoing multiplexing information may also be used to indicate at least one of the following:
  • a target uplink control channel for carrying the uplink control information
  • the target uplink shared channel used to carry the uplink control information
  • the at least one configuration authorized uplink shared channel there is a channel with overlapping time domain resources with the at least one uplink control channel;
  • the at least one uplink control channel there is a channel with overlapping time domain resources with the at least one configuration authorized uplink shared channel.
  • the first two methods for determining the target uplink shared channel can directly inform the MAC layer which one is the target uplink shared channel, and the latter two target uplink shared channels need to be determined by the MAC layer which is the target uplink shared channel.
  • the above-mentioned target PUSCH may be the PUSCH with the earliest start time among the multiple PUSCHs on the carrier with the smallest number, or the target PUSCH is the PUSCH that triggers aperiodic CSI reporting among the multiple PUSCHs on the carrier with the smallest number, or, the target PUSCH It is the PUSCH of the carrier with the smallest number in the dynamic UL scheduling among multiple carriers, or, the target PUSCH is the PUSCH of the carrier with the smallest number that triggers aperiodic CSI reporting, or the target PUSCH is the PUSCH of the carrier with the smallest number that triggers aperiodic CSI reporting.
  • the PUSCH of the configuration grant with the smallest or largest number, or the target PUSCH is the PUSCH of the configuration grant located on the carrier with the smallest or largest number in the at least one configuration grant.
  • the priority of the target uplink shared channel is the same as or different from the priority corresponding to the at least one configuration authorized uplink shared channel, for example, the priority of the target uplink shared channel may be greater than, equal to or smaller than the at least one configuration authorized uplink shared channel corresponding priority.
  • the priority of the PUSCH of the configuration grant may be the priority corresponding to the PUSCH of the configuration grant or the priority corresponding to the configuration grant.
  • the priority corresponding to the PUCCH may be the priority of the UCI carried by the PUCCH, the priority of the physical downlink shared channel corresponding to the UCI carried by the PUCCH, or the priority of the HARQ-ACK codebook corresponding to the PDSCH corresponding to the PUCCH.
  • the target uplink shared channel may be one or multiple, and the target uplink control channel may be one or multiple, which is not limited in the embodiment of the present application.
  • the above multiplexing information may be notified by the physical layer to the MAC layer when the terminal device receives a scheduling grant (downlink scheduling grant or uplink scheduling grant).
  • the scheduling grant is a downlink scheduling grant
  • the downlink scheduling grant is DCI for scheduling part or all of the uplink control channels in the at least one uplink control channel.
  • the downlink scheduling grant is the latest (latest) DCI for scheduling the above-mentioned one or more PUCCHs carrying UCI.
  • the above-mentioned scheduling grant is an uplink scheduling grant
  • the above-mentioned uplink scheduling grant is the DCI for scheduling the uplink shared channel overlapping the time domain resource of the at least one uplink control channel
  • the scheduling grant is an uplink scheduling grant
  • the uplink shared channel scheduled by the uplink scheduling grant overlaps with the at least one uplink control channel in one time unit
  • the scheduling grant is an uplink scheduling grant
  • the uplink shared channel scheduled by the uplink scheduling grant overlaps with the uplink shared channel of the at least one configuration grant in one time unit, wherein the uplink shared channel scheduled by the uplink scheduling grant
  • the priority of the shared channel is the same or different from that of the uplink shared channel granted by the at least one configuration.
  • the above-mentioned uplink scheduling grant is the DCI for scheduling part or all of the above-mentioned at least one uplink shared channel
  • the above-mentioned uplink scheduling grant is the DCI for scheduling the PUSCH on the PCell.
  • the above-mentioned time unit may be: a subframe, a time slot, a sub-slot, a symbol, and the like.
  • the terminal device when the terminal device receives the end time slot or symbol of the DCI of the scheduling grant, the physical layer notifies the MAC layer; or, the terminal device receives X time units after the end time slot or symbol of the DCI of the scheduling grant. , notified by the physical layer to the MAC layer.
  • X is a predefined or network configuration or is related to the UE capability, and further, X may be the processing time of a downlink control channel (physical downlink control channel, PDCCH).
  • the process of generating the MAC PDU by the terminal device in the foregoing step 201 may further include the following step 201a:
  • Step 201a In the at least one configuration authorized uplink shared channel, in the case that the target uplink shared channel has no data to be transmitted, generate a MAC padding PDU.
  • the target uplink shared channel is an uplink shared channel used to carry the uplink control information of the at least one uplink control channel in the at least one configuration authorized uplink shared channel.
  • a MAC padding PDU (MAC padding PDU) is generated.
  • the terminal device has no data, specifically, there is no data in the logical channel group (Logical Channel Group) corresponding to the PUSCH.
  • the MAC layer when the MAC layer generates a MAC PDU for the at least one PUSCH according to the multiplexing information, when there is no UL-SCH on any PUSCH, the MAC generates a MAC padding PDU.
  • the MAC layer when the MAC layer generates the MAC PDU according to the multiplexing information, if there is no UL-SCH or no data on the target PUSCH, the MAC layer generates the MAC padding PDU.
  • the uplink transmission method provided by the embodiment of the present application may further include the following step A1:
  • Step A1 on the conflicting channel or the target carrier, it is forbidden to enable the uplink transmission skip function
  • the conflicting channel is: in the at least one configured uplink shared channel, a channel overlapping with the time domain resources of the uplink control channel scheduled by the downlink scheduling grant, or, in the uplink shared channel scheduled by the uplink scheduling grant. , the uplink shared channel that overlaps with the time domain resource of the at least one uplink control channel, or the uplink shared channel scheduled by the uplink scheduling grant that overlaps the time domain resource of the at least one configuration authorized uplink shared channel channel;
  • the target carrier is the carrier where the conflicting channel is located.
  • the UE when at least one PUCCH and PUSCH overlap in time, the UE disables the PUSCH UL skipping function. Further, on the carrier where the PUSCH conflicting with the PUCCH is located, the PUSCH UL skipping function is prohibited from being enabled.
  • the uplink transmission method provided by the embodiment of the present application may further include the following step B1 or step B2 or step B3:
  • Step B1 In the case that the uplink control channel includes multiple channels, the physical layer or the MAC layer determines the target uplink control channel from the multiple uplink control channels according to the first multiplexing rule.
  • Step B2 In the case that the at least one configuration-authorized uplink shared channel includes multiple channels, the physical layer or the MAC layer determines from the multiple configuration-authorized uplink shared channels according to the second multiplexing rule. the target uplink shared channel.
  • Step B3 In the case that the at least one uplink shared channel includes multiple uplink shared channels, and the time domain resources of the target uplink control channel overlap with the time domain resources of the multiple uplink shared channels, the physical layer or the MAC layer is based on the first step.
  • the two multiplexing rules and the above-mentioned target uplink control channel determine the above-mentioned target uplink shared channel from the above-mentioned multiple uplink shared channels.
  • the above-mentioned first multiplexing rule may be a PUCCH multiplexing rule of UCI on PUCCH.
  • the multiplexing rule of HARQ-ACK on PUCCH and the multiplexing rule of Scheduling request (SR) on PUCCH are shown in Table 1 below:
  • PF0 in the above table is PUCCH Format 1
  • PF1 in the above table is PUCCH Format 1
  • PF2/3/4 in the above table is PUCCH Format 2/3/4.
  • SR and CSI are transmitted on the PUCCH of CSI, [log 2 (K+1)] bits are preset before the periodic/semi-static CSI information bits, and in ascending order, indicate the corresponding SR status (active or inactive) in the SR resource Id activation).
  • HARQ-ACK is feedback to PDSCH without PDCCH scheduling, HARQ-ACK or HARQ-ACK+SR will be multiplexed on CSI PUCCH for transmission.
  • the PUCCH is a PUCCH determined in multiple resource sets configured by RRC based on HARQ-ACK, CSI and SR bits.
  • the above-mentioned target uplink shared channel is based on at least the following: A certain:
  • the physical layer notifies the MAC layer to multiplex the uplink control information on the target uplink shared channel
  • the physical layer notifies the MAC layer whether each of the multiple uplink shared channels multiplexes the uplink control information.
  • the physical layer (physical, PHY) layer needs to determine the target PUSCH carrying the UCI according to the second multiplexing rule.
  • the target PUSCH is the PUSCH with the earliest start time among the multiple PUSCHs on the carrier;
  • the target PUSCH is a PUSCH for which aperiodic CSI reporting (Aperiodic-CSI, A-CSI) is triggered among multiple PUSCHs on the carrier.
  • aperiodic CSI reporting Aperiodic-CSI, A-CSI
  • the above-mentioned target uplink shared channel satisfies at least the following:
  • the above-mentioned first carrier is a carrier whose number satisfies a predetermined condition (for example, the number is the smallest) among the above-mentioned multiple carriers;
  • the above-mentioned second carrier is an uplink scheduled carrier among the above-mentioned multiple carriers and whose number satisfies the above-mentioned predetermined condition;
  • the above-mentioned third carrier is a carrier for which aperiodic CSI reporting is triggered and whose number satisfies the above-mentioned predetermined condition among the above-mentioned multiple carriers.
  • the PHY layer needs to determine the target PUSCH carrying the UCI and the carrier where the target PUSCH is located according to the second multiplexing rule.
  • the multiplexing mode includes: multiplexing mode 1: the target PUSCH is the PUSCH with the earliest start time among the multiple PUSCHs on the carrier with the smallest number;
  • the target PUSCH is the PUSCH that triggers aperiodic CSI reporting (Aperiodic-CSI, A-CSI) among multiple PUSCHs on the carrier with the smallest number;
  • the target PUSCH is the PUSCH of the carrier with the smallest number in the dynamic UL scheduling among multiple carriers;
  • the target PUSCH is the PUSCH of the carrier with the smallest number that triggers aperiodic CSI reporting among multiple carriers;
  • the target PUSCH is the PUSCH with the smallest or largest number of the configuration authorized PUSCH among the at least one configuration authorized PUSCH;
  • the target PUSCH is the PUSCH with the minimum or maximum number of the carrier on which the corresponding configuration grant is located among the at least one PUSCH with the configuration grant.
  • the multiplexing method may further include: the target PUSCH is the channel with the earliest start time among the at least one configuration authorized uplink shared channel located on a single carrier; or, the at least one configuration authorized channel located on multiple carriers Among the uplink shared channels, the channel with the earliest start time is located on the carrier with the lowest number; or, in the at least one configuration authorized uplink shared channel located on the multi-carrier, it is located on the carrier with the lowest number among the dynamically scheduled carriers Channel.
  • the MAC layer or the physical layer will determine the target uplink shared channel according to the second multiplexing rule.
  • the MAC layer when the PHY layer notifies the MAC layer that the target PUCCH collides with the above at least one PUSCH, the MAC layer will determine the target PUSCH carrying the UCI according to the above-mentioned multiplexing rule of the target PUCCH and the UCI on PUSCH.
  • the embodiment of the present application may further include the following step C1:
  • Step C1 The MAC layer determines a target uplink shared channel for carrying the uplink control information from the at least one uplink shared channel according to the second multiplexing rule.
  • the MAC layer determines the target PUCCH carrying these one or more UCIs according to the second multiplexing rule (that is, the PUCCH multiplexing rule of UCI on PUSCH), if the above When the target PUCCH collides with at least one PUSCH, the MAC layer determines the target PUSCH bearing the UCI according to the target PUCCH and the second multiplexing rule.
  • the second multiplexing rule that is, the PUCCH multiplexing rule of UCI on PUSCH
  • the MAC layer determines the target PUSCH used to carry the UCI and where the target PUSCH is located according to the second multiplexing rule.
  • the MAC layer determines, according to the first multiplexing rule (that is, the PUCCH multiplexing rule of UCI on PUCCH), the target PUCCH that carries these one or more UCIs. .
  • the MAC layer if the MAC layer knows that one or more PUCCHs carrying UCI are in conflict with at least one PUSCH on one or more carriers, and when there is no UL-SCH on the target PUSCH, the MAC generates a MAC padding PDU.
  • the uplink transmission method provided by the embodiment of the present application is explained below by taking the uplink shared channel as the PUSCH and the uplink control channel as the PUCCH as an example, and using three examples.
  • the UE can determine the transmission of UCI according to the following steps:
  • Step 11 Decode DL grant and/or UL grant.
  • Step 12 If there are multiple PUCCHs, the PHY layer determines the resource of the target PUCCH bearing UCI according to the multiplexing rule of UCI on PUCCH.
  • Step 13 If the target PUCCH resource collides with at least one PUSCH on the above-mentioned one or more carriers, the PHY layer determines the target PUSCH resource for carrying UCI according to the UCI on PUSCH multiplexing priority in at least one PUSCH .
  • Step 14 The PHY layer notifies the MAC layer of the UCI multiplexing information (that is, the content in step 13), and the MAC generates a MAC PDU according to the UCI multiplexing information.
  • Step 15 If there is no UL-SCH, the MAC layer generates a padding PDU.
  • Step 16 Perform UCI mapping on the target PUSCH.
  • Step 17 Perform (padding) data mapping on the target PUSCH.
  • Step 16 may be executed first and then step 17 (that is, the UCI mapping is performed first, and the data mapping is performed later), or the execution may be performed first. 17 and then execute 16 (that is, first perform data mapping, and then perform UCI mapping).
  • the UE When the UE is on one or more carriers and is configured with at least one PUSCH with a configuration grant, if the UE receives one or more UL grants, at least one PUSCH on one or more carriers is scheduled, and the UE receives one or more UL grants DL grants, one or more PUCCHs carrying UCI are scheduled, and the UE determines the transmission of UCI according to the following steps:
  • Step 21 Decode DL grant and/or UL grant.
  • Step 22 If there are multiple PUCCHs, the PHY layer determines the resource of the target PUCCH bearing UCI according to the multiplexing rule of UCI on PUCCH.
  • Step 23 The PHY layer notifies the MAC layer of the UCI multiplexing information (that is, the content in step 12), and the MAC layer generates a MAC PDU according to the UCI multiplexing information.
  • Step 24 If the target PUCCH resource collides with at least one PUSCH on one or more carriers, the MAC layer determines the target PUSCH resource for carrying UCI in at least one PUSCH according to the UCI on PUSCH multiplexing rule.
  • Step 25 The MAC generates a PDU for the target PUSCH, and generates a padding PDU if there is no UL-SCH.
  • Step 26 Perform UCI mapping on the target PUSCH.
  • Step 27 Perform (padding) data mapping on the target PUSCH.
  • Step 26 may be executed first and then step 27 (that is, the UCI mapping is performed first, and then the data mapping is performed), or the execution may be performed first.
  • step 27 and then execute 26 that is, first perform data mapping, and then perform UCI mapping).
  • the UE determines the transmission of UCI according to the following steps:
  • Step 31 Decode DL grant and/or UL grant.
  • Step 32 After step 31, the PHY layer notifies the MAC layer that the one or more PUCCHs carrying the UCI collide with at least one PUSCH on the one or more carriers.
  • Step 33 The MAC generates a MAC PDU for the first PUSCH (set) in conflict according to the UCI multiplexing information.
  • Step 34 If there is no UL-SCH, the MAC generates a padding PDU.
  • Step 35 If there are multiple PUCCHs, the PHY layer determines the resource of the target PUCCH bearing UCI according to the multiplexing rule of UCI on PUCCH.
  • Step 36 If the target PUCCH resource collides with at least one PUSCH on one or more carriers, the PHY layer determines the target PUSCH resource for carrying UCI in at least one PUSCH according to the UCI on PUSCH multiplexing rule.
  • Step 37 If the target PUSCH has UL-SCH, perform UCI and data (data) mapping on the target PUSCH.
  • Step 38 Otherwise, perform UCI and padding data mapping on the target PUSCH.
  • Step 39 If the target PUSCH does not belong to the first PUSCH (set), perform (padding) data mapping on the first PUSCH (set).
  • Step 40 If one PUSCH in the first PUSCH (set) has no data, perform mapping of padding data.
  • the UCI mapping may be performed first, and then the data mapping may be performed, or the data mapping may be performed first, and then the UCI mapping may be performed.
  • the present application also provides a method for generating MAC PDUs, including:
  • the target physical uplink shared channel used to carry the uplink control information is configured to be repeatedly transmitted M times, N MAC PDUs are generated, and the M is a positive integer , the N is a positive integer less than or equal to M.
  • the internal layer ie inter-layer
  • the physical layer of the terminal learns that a configuration authorized PUSCH and PUCCH resources overlap in the time domain, the physical layer of the terminal will notify The MAC layer unconditionally generates a MAC PDU for the current Hybrid Automatic Repeat Request (HARQ) entity.
  • HARQ Hybrid Automatic Repeat Request
  • the internal signaling submitted by the physical layer to the MAC layer may be:
  • the MAC PDU is nominal PUSCH, that is, in the case where the target uplink shared channel for carrying the uplink control information in the at least one configuration authorized uplink shared channel is configured as the repeated transmission type B , the MAC PDU is a PDU for nominal uplink shared channel.
  • the MAC entity will not generate a MAC PDU for the HARQ entity:
  • the MAC entity is configured with the parameter skipUplinkTxDynamic, and the value of this parameter is set to true (true), and the MAC locates the HARQ entity indicated in the uplink grant (UL grant);
  • the UL grant does not request aperiodic CSI for this PUSCH transmission, and the HARQ entity corresponds to a configured uplink grant (configured uplink grant), and no UCI will be multiplexed to the PUSCH transmission of the configuration grant;
  • a MAC PDU contains zero MAC SDUs; and a MAC PDU contains only periodic Buffer Status Reports (BSRs) and no data is available for any Logical Channel Group (LCG), or a MAC PDU contains only periodic Buffer Status Reports (BSRs) Fill BSR.
  • BSRs Buffer Status Reports
  • the MAC layer will generate multiple repeated MAC PDUs.
  • solutions in this application can be applied to single-carrier and multi-carrier, as well as licensed or unlicensed frequency bands.
  • the MAC layer can follow any one of the following Item processing mode, generate MAC PDU: Mode 1, if the MAC layer knows that the time domain resources of the above-mentioned uplink shared channel overlap with the time domain resources of the above-mentioned uplink control channel, then generate a MAC PDU; Mode 2, according to the physical layer notified to the MAC layer. Multiplexing information to generate a MAC PDU; wherein, at least one uplink control information is carried on the at least one uplink control channel.
  • the MAC PDU can be generated through the MAC layer, so that the terminal device can support the uplink control information carried on the uplink control channel even in the absence of data transmission. It is multiplexed to the configured and authorized uplink shared channel, so that the network-side equipment can accurately determine the uplink control channel multiplexing resources without blind detection, which reduces the complexity of the network-side blind detection and improves the system communication energy efficiency.
  • the execution body may be an uplink transmission apparatus, or a control module in the uplink transmission apparatus for executing the uplink transmission method.
  • the uplink transmission method performed by the uplink transmission apparatus is taken as an example to describe the apparatus of the uplink transmission method provided by the embodiments of the present application.
  • the uplink transmission device 300 provided by the embodiment of the present application can include: an execution module 301, wherein:
  • the execution module 301 is configured to, when the time domain resource of at least one configuration authorized uplink shared channel overlaps with the time domain resource of at least one uplink control channel, then at the medium access control MAC layer according to any one of the following processing methods, generate MAC Protocol Data Unit PDU:
  • MAC PDU is generated
  • a MAC PDU is generated
  • the at least one uplink control channel is used to carry uplink control information.
  • the multiplexing information is used to indicate that: the time domain resources of the at least one configuration granted uplink shared channel overlap with the time domain resources of the at least one uplink control channel.
  • the at least one configured and authorized uplink shared channel is located on one or more carriers.
  • the multiplexing information is used to indicate at least one of the following:
  • a target uplink control channel for carrying the uplink control information
  • the target uplink shared channel used to carry the uplink control information
  • the at least one configuration authorized uplink shared channel there is a channel with overlapping time domain resources with the at least one uplink control channel;
  • the at least one uplink control channel there is a channel with overlapping time domain resources with the at least one configuration authorized uplink shared channel.
  • the uplink transmission device 300 also includes:
  • the first determining module is configured to, in the case that the at least one uplink control channel includes a plurality of uplink control channels, at the physical layer or the MAC layer, according to a first multiplexing rule, determine from the plurality of uplink control channels. the target uplink control channel;
  • the physical layer or the MAC layer determines from the plurality of configuration-authorized uplink shared channels according to the second multiplexing rule outputting the target uplink shared channel;
  • the target uplink shared channel is determined from the at least one configuration authorized uplink shared channel according to the second multiplexing rule and the target uplink control channel at the physical layer or the MAC layer.
  • target uplink shared channel is:
  • the corresponding channel with the largest configuration authorization number the corresponding channel with the largest configuration authorization number
  • the corresponding channel with the smallest configuration authorization number the corresponding channel with the smallest configuration authorization number
  • the channel with the largest number of the carrier where the corresponding configuration authorization is located In the uplink shared channel of the at least one configuration authorization, the channel with the largest number of the carrier where the corresponding configuration authorization is located;
  • the channel with the lowest number of the carrier where the corresponding configuration grant is located is located.
  • the multiplexing information is notified to the MAC layer by the physical layer when the terminal device receives the scheduling grant.
  • the scheduling grant is a downlink scheduling grant
  • the downlink scheduling grant is downlink control information DCI for scheduling the uplink control channel
  • the uplink scheduling grant is the DCI for scheduling the uplink shared channel overlapping the time domain resource of the at least one uplink control channel;
  • the scheduling grant is an uplink scheduling grant
  • the uplink shared channel scheduled by the uplink scheduling grant overlaps with the at least one uplink control channel in one time unit
  • the scheduling grant is an uplink scheduling grant
  • the uplink shared channel scheduled by the uplink scheduling grant overlaps with the uplink shared channel of the at least one configuration grant in one time unit.
  • the uplink transmission apparatus 300 further includes a disabling and enabling module for disabling the enabling of the uplink transmission skipping function on the conflicting channel or the target carrier;
  • the conflicting channel is: in the at least one configured uplink shared channel, a channel overlapping with the time domain resources of the uplink control channel scheduled by the downlink scheduling grant, or, in the uplink shared channel scheduled by the uplink scheduling grant. , the uplink shared channel that overlaps with the time domain resource of the at least one uplink control channel, or the uplink shared channel scheduled by the uplink scheduling grant that overlaps the time domain resource of the at least one configuration authorized uplink shared channel channel;
  • the target carrier is the carrier where the conflicting channel is located.
  • the uplink transmission apparatus 300 further includes a second determining module for:
  • a target uplink shared channel for carrying the uplink control information is determined from the at least one uplink shared channel at the MAC layer according to the second multiplexing rule.
  • execution module 301 includes:
  • a MAC padding PDU is generated.
  • execution module 301 includes:
  • the target uplink shared channel used to carry the uplink control information when configured to be repeatedly transmitted M times, N MAC PDUs are generated, and the M is a positive integer, so The N is a positive integer less than or equal to M.
  • the terminal provided in the embodiment of the present application can implement each process in the method embodiment of FIG. 2 and achieve the same technical effect. To avoid repetition, details are not repeated here.
  • the uplink transmission device shown in FIG. 3 may be a device, and may also be a component, an integrated circuit, or a chip in a terminal.
  • the device may be a mobile terminal or a non-mobile terminal.
  • the mobile terminal may include, but is not limited to, the types of terminals 11 listed above, and the non-mobile terminal may be a server, a network attached storage (NAS), a personal computer (personal computer, PC), a television ( television, TV), teller machine, or self-service machine, etc., which are not specifically limited in the embodiments of the present application.
  • the uplink transmission device shown in FIG. 3 may be a device with an operating system.
  • the operating system may be an Android (Android) operating system, an ios operating system, or other possible operating systems, which are not specifically limited in the embodiments of the present application.
  • an embodiment of the present application further provides a terminal 700, including a processor 701, a memory 702, a program or instruction stored in the memory 702 and executable on the processor 701, the When the program or the instruction is executed by the processor 701, each process of the above-mentioned embodiments of the uplink transmission method is implemented, and the same technical effect can be achieved.
  • FIG. 5 is a schematic diagram of a hardware structure of a terminal implementing various embodiments of the present application.
  • the terminal 1000 includes but is not limited to: a radio frequency unit 1001, a network module 1002, an audio output unit 1003, an input unit 1004, a sensor 1005, a display unit 1006, a user input unit 1007, an interface unit 1008, a memory 1009, a processor 1010 and other components.
  • the terminal 1000 may also include a power supply (such as a battery) for supplying power to various components, and the power supply may be logically connected to the processor 1010 through a power management system, so as to manage charging, discharging, and power consumption through the power management system management and other functions.
  • a power supply such as a battery
  • the terminal structure shown in FIG. 5 does not constitute a limitation to the terminal, and the terminal may include more or less components than shown, or combine some components, or arrange different components, which will not be repeated here.
  • the input unit 1004 may include a graphics processor (Graphics Processing Unit, GPU) 10041 and a microphone 10042. Such as camera) to obtain still pictures or video image data for processing.
  • the display unit 1006 may include a display panel 10061, which may be configured in the form of a liquid crystal display, an organic light emitting diode, or the like.
  • the user input unit 1007 includes a touch panel 10071 and other input devices 10072 .
  • the touch panel 10071 is also called a touch screen.
  • the touch panel 10071 may include two parts, a touch detection device and a touch controller.
  • Other input devices 10072 may include, but are not limited to, physical keyboards, function keys (such as volume control keys, switch keys, etc.), trackballs, mice, and joysticks, which will not be repeated here.
  • the radio frequency unit 1001 receives the downlink data from the network side device, and then processes it to the processor 1010; in addition, sends the uplink data to the network side device.
  • the radio frequency unit 1001 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, and the like.
  • Memory 1009 may be used to store software programs or instructions as well as various data.
  • the memory 109 may mainly include a storage program or instruction area and a storage data area, wherein the stored program or instruction area may store an operating system, an application program or instruction required for at least one function (such as a sound playback function, an image playback function, etc.) and the like.
  • the memory 1009 may include a high-speed random access memory, and may also include a non-volatile memory, wherein the non-volatile memory may be a read-only memory (Read-Only Memory, ROM), a programmable read-only memory (Programmable ROM) , PROM), erasable programmable read-only memory (Erasable PROM, EPROM), electrically erasable programmable read-only memory (Electrically EPROM, EEPROM) or flash memory.
  • ROM Read-Only Memory
  • PROM programmable read-only memory
  • PROM erasable programmable read-only memory
  • Erasable PROM Erasable PROM
  • EPROM electrically erasable programmable read-only memory
  • EEPROM electrically erasable programmable read-only memory
  • flash memory for example at least one magnetic disk storage device, flash memory device, or other non-volatile solid state storage device.
  • the processor 1010 may include one or more processing units; optionally, the processor 1010 may integrate an application processor and a modem processor, wherein the application processor mainly processes the operating system, user interface, and application programs or instructions, etc. Modem processors mainly deal with wireless communications, such as baseband processors. It can be understood that, the above-mentioned modulation and demodulation processor may not be integrated into the processor 1010.
  • the processor 1010 is configured to, in the case where the time domain resources of at least one configuration authorized uplink shared channel overlap with the time domain resources of at least one uplink control channel, perform any one of the following processing methods at the medium access control MAC layer , generate the MAC protocol data unit PDU:
  • MAC PDU is generated
  • a MAC PDU is generated
  • the at least one uplink control channel is used to carry uplink control information.
  • the multiplexing information is used to indicate that: the time domain resources of the at least one configuration granted uplink shared channel overlap with the time domain resources of the at least one uplink control channel.
  • the at least one configured and authorized uplink shared channel is located on one or more carriers.
  • the multiplexing information is used to indicate at least one of the following:
  • a target uplink control channel for carrying the uplink control information
  • the target uplink shared channel used to carry the uplink control information
  • the at least one configuration authorized uplink shared channel there is a channel with overlapping time domain resources with the at least one uplink control channel;
  • the at least one uplink control channel there is a channel with overlapping time domain resources with the at least one configuration authorized uplink shared channel.
  • the processor 1010 is further configured to, in the case that the at least one uplink control channel includes multiple uplink control channels, at the physical layer or the MAC layer according to the first multiplexing rule, from the multiple uplink control channels determining the target uplink control channel;
  • the physical layer or the MAC layer determines from the plurality of configuration-authorized uplink shared channels according to the second multiplexing rule outputting the target uplink shared channel;
  • the target uplink shared channel is determined from the at least one configuration authorized uplink shared channel according to the second multiplexing rule and the target uplink control channel at the physical layer or the MAC layer.
  • target uplink shared channel is:
  • the corresponding channel with the largest configuration authorization number the corresponding channel with the largest configuration authorization number
  • the corresponding channel with the smallest configuration authorization number the corresponding channel with the smallest configuration authorization number
  • the channel with the largest number of the carrier where the corresponding configuration authorization is located In the uplink shared channel of the at least one configuration authorization, the channel with the largest number of the carrier where the corresponding configuration authorization is located;
  • the channel with the lowest number of the carrier where the corresponding configuration grant is located is located.
  • the multiplexing information is notified to the MAC layer by the physical layer when the terminal device receives the scheduling grant.
  • the scheduling grant is a downlink scheduling grant
  • the downlink scheduling grant is downlink control information DCI for scheduling the uplink control channel
  • the uplink scheduling grant is the DCI for scheduling the uplink shared channel overlapping the time domain resource of the at least one uplink control channel;
  • the scheduling grant is an uplink scheduling grant
  • the uplink shared channel scheduled by the uplink scheduling grant overlaps with the at least one uplink control channel in one time unit
  • the scheduling grant is an uplink scheduling grant
  • the uplink shared channel scheduled by the uplink scheduling grant overlaps with the uplink shared channel of the at least one configuration grant in one time unit.
  • processor 1010 is further configured to disable the uplink transmission skipping function on the conflicting channel or the target carrier;
  • the conflicting channel is: in the at least one configured uplink shared channel, a channel overlapping with the time domain resources of the uplink control channel scheduled by the downlink scheduling grant, or, in the uplink shared channel scheduled by the uplink scheduling grant. , the uplink shared channel that overlaps with the time domain resource of the at least one uplink control channel, or the uplink shared channel scheduled by the uplink scheduling grant that overlaps the time domain resource of the at least one configuration authorized uplink shared channel channel;
  • the target carrier is the carrier where the conflicting channel is located.
  • the processor 1010 is further configured to, at the MAC layer, according to the second multiplexing rule, from A target uplink shared channel for carrying the uplink control information is determined in the at least one uplink shared channel.
  • the processor 1010 is further configured to, in the at least one configured and authorized uplink shared channel, generate a MAC padding PDU when the target uplink shared channel used to carry the uplink control information has no data to be transmitted.
  • the processor 1010 is further configured to, in the at least one configuration authorized uplink shared channel, in the case that the target uplink shared channel for carrying the uplink control information is configured to be repeatedly transmitted M times, generate N number of MAC PDU, the M is a positive integer, and the N is a positive integer less than or equal to M.
  • the above-mentioned processor 1010 and the radio frequency unit 1001 can implement each process implemented by the terminal in the method embodiment of FIG. 2 , which is not repeated here to avoid repetition.
  • An embodiment of the present application further provides a readable storage medium, where a program or an instruction is stored on the readable storage medium, and when the program or instruction is executed by a processor, each process of the uplink transmission method embodiment shown in FIG. 2 is implemented, And can achieve the same technical effect, in order to avoid repetition, it is not repeated here.
  • the processor is the processor in the electronic device described in the foregoing embodiments.
  • the readable storage medium includes a computer-readable storage medium, such as a computer read-only memory (Read-Only Memory, ROM), a random access memory (Random Access Memory, RAM), a magnetic disk or an optical disk, and the like.
  • An embodiment of the present application further provides a chip, where the chip includes a processor and a communication interface, the communication interface is coupled to the processor, and the processor is used to run a network-side device program or instruction to implement the above-mentioned FIG. 2
  • the chip includes a processor and a communication interface
  • the communication interface is coupled to the processor
  • the processor is used to run a network-side device program or instruction to implement the above-mentioned FIG. 2
  • the chip mentioned in the embodiments of the present application may also be referred to as a system-on-chip, a system-on-chip, a system-on-a-chip, or a system-on-a-chip, or the like.
  • the disclosed apparatus and method may be implemented in other manners.
  • the apparatus embodiments described above are only illustrative.
  • the division of the units is only a logical function division. In actual implementation, there may be other division methods.
  • multiple units or components may be combined or Can be integrated into another system, or some features can be ignored, or not implemented.
  • the shown or discussed mutual coupling or direct coupling or communication connection may be through some interfaces, indirect coupling or communication connection of devices or units, and may be in electrical, mechanical or other forms.
  • each functional unit in each embodiment of the present disclosure may be integrated into one processing unit, or each unit may exist physically alone, or two or more units may be integrated into one unit.
  • modules, units, and subunits can be implemented in one or more Application Specific Integrated Circuits (ASIC), Digital Signal Processor (DSP), Digital Signal Processing Device (DSP Device, DSPD) ), Programmable Logic Device (PLD), Field-Programmable Gate Array (FPGA), general-purpose processor, controller, microcontroller, microprocessor, in other electronic units or combinations thereof.
  • ASIC Application Specific Integrated Circuits
  • DSP Digital Signal Processor
  • DSP Device Digital Signal Processing Device
  • DSPD Digital Signal Processing Device
  • PLD Programmable Logic Device
  • FPGA Field-Programmable Gate Array
  • the technologies described in the embodiments of the present disclosure may be implemented through modules (eg, procedures, functions, etc.) that perform the functions described in the embodiments of the present disclosure.
  • Software codes may be stored in memory and executed by a processor.
  • the memory can be implemented in the processor or external to the processor.

Landscapes

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

Abstract

La présente demande relève du domaine technique des communications et concerne un procédé et un appareil de transmission de liaison montante, ainsi qu'un dispositif de réseau. Ledit procédé comprend : dans les cas où des ressources de domaine temporel d'au moins un canal partagé de liaison montante d'autorisation configurée se chevauchent avec des ressources de domaine temporel d'au moins un canal de commande de liaison montante, générer une PDU MAC au niveau d'une couche MAC selon l'un quelconque des procédés de traitement suivants : si la couche MAC apprend que les ressources de domaine temporel du canal partagé de liaison montante se chevauchent avec les ressources de domaine temporel du canal de commande de liaison montante, générer une PDU MAC ; et générer une PDU MAC en fonction d'informations de multiplexage notifiées à la couche MAC par une couche physique, au moins une information de commande de liaison montante étant portée sur l'au moins un canal de commande de liaison montante.
PCT/CN2021/111299 2020-08-07 2021-08-06 Procédé et appareil de transmission de liaison montante, et dispositif terminal WO2022028604A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202010790993.2 2020-08-07
CN202010790993.2A CN114071743A (zh) 2020-08-07 2020-08-07 上行传输方法、装置及终端设备

Publications (1)

Publication Number Publication Date
WO2022028604A1 true WO2022028604A1 (fr) 2022-02-10

Family

ID=80117082

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/111299 WO2022028604A1 (fr) 2020-08-07 2021-08-06 Procédé et appareil de transmission de liaison montante, et dispositif terminal

Country Status (2)

Country Link
CN (1) CN114071743A (fr)
WO (1) WO2022028604A1 (fr)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108521885A (zh) * 2018-04-28 2018-09-11 北京小米移动软件有限公司 上行传输的方法及装置
US10212732B2 (en) * 2015-04-28 2019-02-19 Lg Electronics Inc. Method for transmitting and receiving uplink data using contention based resources in wireless communication system and apparatus therefor
CN110149726A (zh) * 2018-02-12 2019-08-20 电信科学技术研究院有限公司 一种信息传输方法及终端
CN110650535A (zh) * 2018-06-26 2020-01-03 中国信息通信研究院 一种非授权频段上行信号复用发送方法和装置
CN110972286A (zh) * 2018-09-28 2020-04-07 电信科学技术研究院有限公司 一种上行控制信息uci的传输方法、用户终端及基站

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10212732B2 (en) * 2015-04-28 2019-02-19 Lg Electronics Inc. Method for transmitting and receiving uplink data using contention based resources in wireless communication system and apparatus therefor
CN110149726A (zh) * 2018-02-12 2019-08-20 电信科学技术研究院有限公司 一种信息传输方法及终端
CN108521885A (zh) * 2018-04-28 2018-09-11 北京小米移动软件有限公司 上行传输的方法及装置
CN110650535A (zh) * 2018-06-26 2020-01-03 中国信息通信研究院 一种非授权频段上行信号复用发送方法和装置
CN110972286A (zh) * 2018-09-28 2020-04-07 电信科学技术研究院有限公司 一种上行控制信息uci的传输方法、用户终端及基站

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
QUALCOMM INCORPORATED: "Summary of remaining issues for UCI piggyback on PUSCH", 3GPP DRAFT; R1-1801092 SUMMARY OF REMAINING ISSUES FOR UCI MULTIPLEXING ON PUSCH - TUE V3, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. Vancouver, Canada; 20180122 - 20180126, 24 January 2018 (2018-01-24), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051385312 *

Also Published As

Publication number Publication date
CN114071743A (zh) 2022-02-18

Similar Documents

Publication Publication Date Title
KR102379953B1 (ko) 감소된 레이턴시로 업링크 전송들을 스케줄링하기 위한 방법 및 장치
WO2022152176A1 (fr) Procédé de traitement de transmission et dispositif associé
WO2022105842A1 (fr) Procédé de transmission d'informations de commande de liaison descendante et dispositif associé
WO2022218368A1 (fr) Procédé et appareil de détermination d'une ressource de renvoi en liaison latérale, terminal et support de stockage
WO2022152072A1 (fr) Procédé d'envoi d'informations de canal, procédé de réception d'informations de canal et dispositif associé
WO2022078451A1 (fr) Procédé et appareil de transmission répétitive pour une autorisation configurée, dispositif et support de stockage lisible
WO2022063072A1 (fr) Procédé et appareil de transmission de canal de liaison montante, et terminal
WO2022017353A1 (fr) Procédé et appareil pour le traitement d'un chevauchement de ressources de canal de commande de liaison montante physique
WO2022002259A1 (fr) Procédé et appareil de transmission de liaison latérale, et terminal
WO2022012417A1 (fr) Procédé et appareil de traitement de collision
WO2022143491A1 (fr) Procédé et appareil de multiplexage d'uci, dispositif et support d'enregistrement lisible
WO2022078288A1 (fr) Procédé de transmission harq-ack, terminal et dispositif côté réseau
WO2022213899A1 (fr) Procédé et appareil de transmission de canal de liaison montante, terminal et dispositif côté réseau
WO2022148389A1 (fr) Procédé et appareil de détermination de nombre de symboles de modulation codés, et dispositif de communication
WO2022188794A1 (fr) Procédé et terminal de génération de livre de codes harq-ack semi-statique
WO2022143979A1 (fr) Procédé et appareil de transmission de communication, et dispositif de communication
WO2022012433A1 (fr) Procédé et dispositif de rétroaction harq-ack
WO2022002248A1 (fr) Procédé et appareil de transmission de liaison latérale, et dispositif de communication
WO2022028583A1 (fr) Procédé et appareil de transmission
WO2022028604A1 (fr) Procédé et appareil de transmission de liaison montante, et dispositif terminal
WO2021204257A1 (fr) Procédé de transmission en liaison montante, terminal et dispositif de réseau
WO2022017342A1 (fr) Procédé et appareil de transmission de liaison montante, et dispositf
CN115334676A (zh) 上行传输的复用指示方法、装置、终端及网络侧设备
WO2022152039A1 (fr) Procédé d'envoi de données de liaison montante, procédé de configuration, terminal et dispositif côté réseau
WO2022237743A1 (fr) Procédé et dispositif de répétition pusch

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 21852838

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 21852838

Country of ref document: EP

Kind code of ref document: A1

122 Ep: pct application non-entry in european phase

Ref document number: 21852838

Country of ref document: EP

Kind code of ref document: A1

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 01/08/2023)